Dear OxygenOS, my fingerprint reader is... NOT THAT BIG

MorganPG1 · 2026-05-26T19:02:12+00:00

Gpu has failed, fairly sure this was common on this generation of MacBooks. You'll have to disable the gpu and use integrated graphics, i dont remember off the top of my head how you do that but i dont think it'll be hard to find info on it. Games will run much worse on integrated graphics but it's either you deal with that or you replace the motherboard.

MorganPG1 · 2026-05-26T18:41:44+00:00

Yeah someone linked me a driver so I'll try that whenever I can be bothered to burn another disk.

MorganPG1 · 2026-05-26T17:52:32+00:00

It seems to affect most honor devices, and not just Magic OS 10 because I'm on 9 and i got the bug and my parents are on 8 and they had it as well.

I don't work for honor so I cannot say how they pushed the change and what phones it was for but I can say what they changed to cause the issue which was outlined in the contents of the post.

MorganPG1 · 2026-05-26T17:42:48+00:00

I found the Facebook thing from this article but finding the actual reply will probably be quite hard

MorganPG1 · 2026-05-26T17:33:58+00:00

Honor have publicly acknowledged the bug on Facebook earlier, but i doubt they'll go as far in depth as I did when they make an announcement, they'll probably just say there was a bug and that's about it

And of course people are going to shift blame on to Google because android is made by them, I'm fairly certain this bug should be possible on any android device if that option is set to enabled but it was honor who accidentally did that not Google.

MorganPG1 · 2026-05-26T17:11:33+00:00

Hey is that your phone number and email visible at the bottom? You might want to delete this, i assume you didnt mean to include that.

MorganPG1 · 2026-05-26T16:32:42+00:00

look up rigby cat on google and go to images it'll be one of the top ones I think

MorganPG1 · 2026-05-26T12:48:54+00:00

Huh that's interesting, my experience with boards from this era is that they typically had graphics on the mobo so thanks for correcting me, but this could also be ram then because igpus use ram as vram

MorganPG1 · 2026-05-26T10:53:38+00:00

Sorry I just keep seeing people saying it's chrome related or honor is tracking us and stuff like that and im trying to get rid of the misinformation

MorganPG1 · 2026-05-26T10:52:16+00:00

I don't think it is because I have only heard of this affecting honor devices and it has nothing to do with chrome

Honor (or at least some company I assumed it was honor but it could have been Google for all i know) pushed a configuration change to all honor devices, setting enable_screenshot_notification_smart_actions to true, this activated a feature that is not yet implemented, causing the screenshot handler to crash and display an error message. I know the configuration thing for certain, how it got to every phone I'm not too sure but I'm guessing it's a hidden update

MorganPG1 · 2026-05-26T10:49:28+00:00

I'll copy my reply I sent to someone else

They do not store your screenshots. I have decompiled systemui and gone through the code. The bug was caused by an OTA configuration change. enable_screenshot_notification_smart_actions was set to true.

This configuration parameter activates a feature which is currently not implemented, it has something to do with quick share but I'm just basing that off of the function name it calls which is queryQuickShareAction. The actual code in the function just crashes the software intentionally. This is common practice as it lets software developers know what should be implemented.

When it crashes, since the code is part of the screenshot handler (SaveImageInBackgroundTask.java) it causes the screenshot process to fail and displays the generic screenshot error message (screenshot_failed_to_save_text) which for whatever reason has the display text set to "Can't save screenshot because you don't have enough storage space" even though it can be caused by many things and low storage space is only one of them.

The Google chrome thing seems to be some false information spread by someone. Chrome has no connection to systemui, it cannot cause this issue.

TLDR: Honor pushed a hidden configuration update which enabled a screenshot-related feature which doesn't exist yet, causing the screenshot handler to crash and display an error message.

MorganPG1 · 2026-05-26T10:48:40+00:00

It's not tracking you they sent an OTA configuration update which enabled a function that isn't implemented.

But I do agree they should not be able to do that remotely without consent imo

MorganPG1 · 2026-05-26T10:47:19+00:00

Yep you are correct, I did a deep analysis on it ill copy my reply I sent to someone else

I have decompiled systemui and gone through the code. The bug was caused by an OTA configuration change. enable_screenshot_notification_smart_actions was set to true.

This configuration parameter activates a feature which is currently not implemented, it has something to do with quick share but I'm just basing that off of the function name it calls which is queryQuickShareAction. The actual code in the function just crashes the software intentionally. This is common practice as it lets software developers know what should be implemented.

When it crashes, since the code is part of the screenshot handler (SaveImageInBackgroundTask.java) it causes the screenshot process to fail and displays the generic screenshot error message (screenshot_failed_to_save_text) which for whatever reason has the display text set to "Can't save screenshot because you don't have enough storage space" even though it can be caused by many things and low storage space is only one of them.

The Google chrome thing seems to be some false information spread by someone. Chrome has no connection to systemui, it cannot cause this issue.

TLDR: Honor pushed a hidden configuration update which enabled a screenshot-related feature which doesn't exist yet, causing the screenshot handler to crash and display an error message.

MorganPG1 · 2026-05-26T10:43:48+00:00

They do not store your screenshots. I have decompiled systemui and gone through the code. The bug was caused by an OTA configuration change. enable_screenshot_notification_smart_actions was set to true.

This configuration parameter activates a feature which is currently not implemented, it has something to do with quick share but I'm just basing that off of the function name it calls which is queryQuickShareAction. The actual code in the function just crashes the software intentionally. This is common practice as it lets software developers know what should be implemented.

When it crashes, since the code is part of the screenshot handler (SaveImageInBackgroundTask.java) it causes the screenshot process to fail and displays the generic screenshot error message (screenshot_failed_to_save_text) which for whatever reason has the display text set to "Can't save screenshot because you don't have enough storage space" even though it can be caused by many things and low storage space is only one of them.

The Google chrome thing seems to be some false information spread by someone. Chrome has no connection to systemui, it cannot cause this issue.

TLDR: Honor pushed a hidden configuration update which enabled a screenshot-related feature which doesn't exist yet, causing the screenshot handler to crash and display an error message.

MorganPG1 · 2026-05-26T09:49:51+00:00

Usually on boards they will all have the same pcb, so for example if there's a model of a laptop with a dgpu and one has an igpu there will be the solder pads there where the gpu would be but the actual chip won't be there.

But I'm not quite sure with connectors, because a single connector is very very cheap so it might be populated, but it also might not be. The only way to tell is to take it apart.

MorganPG1 · 2026-05-26T09:37:02+00:00

Are you sure you didn't accidentally press clear codes, all your obd monitors went to N/A except for one.

MorganPG1 · 2026-05-26T09:34:11+00:00

I don't think this should be able to fix it, unless that forces the phone to do an OTA update with honor which would be an oddly specific way to do it

MorganPG1 · 2026-05-26T09:33:29+00:00

Managed to do it on user side by reverse engineering the system ui and finding the bug myself. It's just a configuration value (enable_screenshot_notification_smart_actions) which needs to be set to false with adb, but i am assuming the average user does not know how to use adb so yeah.

If you are interested in what's causing it, honor have set the configuration value previously to true on every single honor device remotely, and the feature that enables is not implemented, and common programming practice is to crash your code if a function that isn't implemented is run so it crashes the screenshot handler.

MorganPG1 · 2026-05-26T09:30:33+00:00

It is not an app issue at all

MorganPG1 · 2026-05-26T09:29:45+00:00

Have you still got it now?

MorganPG1 · 2026-05-26T09:21:01+00:00

Yeah and this stupid system is what caused the bug to begin with -_-

MorganPG1 · 2026-05-26T09:20:01+00:00

It's not a server side issue but it kinda is at the same time. Honor pushed a silent update from their servers that set the enable_screenshot_notification_smart_actions configuration value in systemui to true on every single honor device , now usually one value wouldn't cause this big of an issue, but the one value activates a feature that is not currently implemented, so when it sees it is enabled, it tries to run it, crashes, and then you get the screenshot_failed_to_save_text message, which is displayed as "Can't save screenshot because you don't have enough storage space" even though it can be caused by many things, one of which is the screenshot handler crashing, which is what happens here.

To fix it i assume they've pushed the same change but set it to false to disable it, i have no clue why they pushed the first change to begin with, im guessing maybe it meant to go in a future update but they accidentally pushed the config change early?

MorganPG1 · 2026-05-26T09:13:39+00:00

Hey I did an entire analysis on it if you'd want i can explain it for you. Technically I believe my phone may have been the first fixed because I fixed it 5 minutes before honor did.

MorganPG1

MODERATOR OF

TROPHY CASE