Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkg(scope): Emergency Power saving launcher does not start after removing com.sec.android.provider.badge #461

Closed
3 tasks done
ticklemyIP opened this issue May 14, 2024 · 0 comments · Fixed by #473
Closed
3 tasks done
Assignees
Labels
package::breakage Phone has unexpected issues after debloating

Comments

@ticklemyIP
Copy link

Describe the problem

On Samsung devices there is a function called Power saving. The user has the option to select which behaviors to block or reduce in order to save battery power when this mode is enabled. There is an additional setting called 'Limit apps and Home screen' which basically modifies or replaces the default launcher to have a black background and only have selected apps enabled in addition to liming background activity. On other (older) android OS versions and OEM skins (probably One UI too) this was called Emergency Power saving mode and it was separate from Power saving, but it's included under the same function.

If the com.sec.android.provider.badge package is removed, when enabling Power saving and this alternate Home function is enabled, the Launcher either crashes and the feature does not remain turned on through the quick function, or alternatively it will get turned on but no launcher elements are shown, only a black background. This stays until the user turns off Power saving. The user can still access the notification bar and open apps like the settings app. This issue has been present for a while I think.

One UI: 6.0
Android: 14
Model: Samsung Galaxy A52s 5G (SM-A528B/DS)

You have a solution?

Do not remove the com.sec.android.provider.badge package.

Provide logs

I don't see why mandatory logs for an issue like this would be needed but here it is I guess

2024-05-14 [DELETED] DEBUG [src/core/update.rs:180] Checking for UAD-ng update
2024-05-14 [DELETED] INFO  [src/gui/views/list.rs:144] -----------------------------------------------------------------
2024-05-14 [DELETED] INFO  [src/gui/views/list.rs:145] ANDROID_SDK: 34 | DEVICE: samsung SM-A528B
2024-05-14 [DELETED] INFO  [src/gui/views/list.rs:149] -----------------------------------------------------------------
2024-05-14 [DELETED] INFO  [src/core/sync.rs:123] [Advanced] pm uninstall --user 0 com.sec.android.provider.badge -> Success
2024-05-14 [DELETED] INFO  [src/core/sync.rs:123] [Advanced] pm uninstall --user 11 com.sec.android.provider.badge -> Success
2024-05-14 [DELETED] INFO  [src/core/sync.rs:123] [Advanced] cmd package install-existing --user 0 com.sec.android.provider.badge -> Package com.sec.android.provider.badge installed for user: 0
2024-05-14 [DELETED] INFO  [src/core/sync.rs:123] [Advanced] cmd package install-existing --user 11 com.sec.android.provider.badge -> Package com.sec.android.provider.badge installed for user: 11

Acknowledgements

  • This issue is not a duplicate of an existing one.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@ticklemyIP ticklemyIP added the package::breakage Phone has unexpected issues after debloating label May 14, 2024
@AnonymousWP AnonymousWP self-assigned this May 14, 2024
Blitz517 added a commit that referenced this issue May 21, 2024
issues #299, #450, #454, #461, #464, #465, #467 and "com.samsung.android.globalpostprocmgr", "com.samsung.android.audiomirroring", "com.aura.jet.att", "com.aura.oobe.att" from discord
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package::breakage Phone has unexpected issues after debloating
Projects
None yet
2 participants