I''ve never turned Zen Mode on.
I've disabled it in several places.
Despite disabling it everywhere, if I am on my phone continuously for 2 hours, I get a notification from Zen Mode telling me to put my phone down and enjoy my day.
I don't like that.
I'm rooted
I went into a root Uninstaller app to delete it, but it is considered a "key module"
Because the app keeps a recycle bin, and decided to Uninstall it anyway.
It wouldn't let me.
Uninstall failed.
Any suggestions?
Dew Me said:
I''ve never turned Zen Mode on.
I've disabled it in several places.
Despite disabling it everywhere, if I am on my phone continuously for 2 hours, I get a notification from Zen Mode telling me to put my phone down and enjoy my day.
I don't like that.
I'm rooted
I went into a root Uninstaller app to delete it, but it is considered a "key module"
Because the app keeps a recycle bin, and decided to Uninstall it anyway.
It wouldn't let me.
Uninstall failed.
Any suggestions?
Click to expand...
Click to collapse
Remove OPBreathMode and it should be gone.
I use the Root Essential program to remove unwanted programs eg. ZEN MODE
Use ADB to disable it
There is an option it Zen mode to disable the notification, no need to mess around with freezing apps and ADB.
Uninstalling system apps is no longer possible in Android 10 without a Magisk Module or through TWRP. Disabling it is much easier
In ADB type the following:
adb shell pm disable-user com.oneplus.brickmode
-- this is zen mode and this command will disable it.
Change from magisk Canary build 19.4 to magisk stable 19.3 and you can delete anything you want.
Dew Me said:
I''ve never turned Zen Mode on.
I've disabled it in several places.
Despite disabling it everywhere, if I am on my phone continuously for 2 hours, I get a notification from Zen Mode telling me to put my phone down and enjoy my day.
I don't like that.
I'm rooted
I went into a root Uninstaller app to delete it, but it is considered a "key module"
Because the app keeps a recycle bin, and decided to Uninstall it anyway.
It wouldn't let me.
Uninstall failed.
Any suggestions?
Click to expand...
Click to collapse
Imo, do this.
Use the Debloat magisk mod
You can uninstall it.
If you happen to run Into any problems, the Debloat mod allows you to bring the uninstalled app right back the same way you removed it.
Hopefully you won't need to, but it's a good backup in case your system doesn't like it.
Good luck.
Thanks so much guys.
To start I took Eagles advise & DL'd Root Essentials. I went into Zen Mode planning to delete. Was given pause when I saw it was first installed in 2008. Made me wonder what else is in there since Zen Mode is less than a year old AFAIK. So instead I disabled it, since I didn't see a built-in recycling bin to easily add back if needed.
Root Essentials already seems much better than the other one I'd DL'd. Thank you.
I'm gonna do what Sheetzie suggested & use the Deblote Magisk Module in the next couple days. After I've spent 2 hours straight on my phone again to make sure the pause had an affect.
__NBH__ said:
There is an option it Zen mode to disable the notification, no need to mess around with freezing apps and ADB.
Click to expand...
Click to collapse
Like I said, I disabled it in several places already. Plus had never activated it.
If you haven't spent 2 hours straight on your phone, you wouldn't experience what is bothering me. After 2 hours it sends you a notification to get off your phone and go play catch outside. Or something like that. I think the message changes.
No amount of disabling seems to make this stop, so I'm trying to get more serious about it using root access. The responses in this thread have been exactly what I was looking for.
The Root Essential app said it disabled Zen Mode...it didn't
So I went back to Root Essential to delete Zen Mode...it didn't. It couldn't complete the task.
So I got the Magisk Debloater, went into the terminal, and deleted it.
Looks like it is really gone. Went back into Root Essential app and I no longer see it.
When I deleted it showed Zen Mode and OPBreathMode to be one and the same as this thread suggests.
Thank you everyone for your help.
I used ADB to first of all disable Zen Mode. Then I used ADB to uninstall it without issue. I am not rooted. It was simple. It is no longer on my phone at all. OnePlus appears to allow system apps to be uninstalled using this method. Whether they will come back at the next update remains to be seen. I am sure they will come back during a factory reset!
On a side note I wanted my Gmail to be available to remove it from battery optimization because it comes from the factory installed as a service. So I uninstalled Gmail using ADB and it worked just fine. I rebooted and it remained gone. I then installed Gmail from the Play Store and it went back to being installed as a service app, not a user app? Not sure why?
Because, logically, you simply can't remove system apps while not being rooted. They will reside on the phone in a kind of dormant state. Not actually "removed".
Pfeffernuss said:
Because, logically, you simply can't remove system apps while not being rooted. They will reside on the phone in a kind of dormant state. Not actually "removed".
Click to expand...
Click to collapse
I cannot argue with your logic about system apps not "truly" being deleted using ADB without root. However, I cannot find it anywhere on my phone. So I am happy to not even see it. Granted, I am not removing certain apps because of storage space concerns, I am removing Zen Mode because to me it is the epitome of BLOAT!
taanh1412 said:
Use ADB to disable it
Click to expand...
Click to collapse
With root he can just do pm disable. No need for ADB.
I used Titanium backup to freeze it.
i also really dislike zenmode
I also really dislike zenmode, I left a comment saying as much on the google play store after i saw it on the update list on google play. I suggest that others also leave bad reviews for this app and maybe it will help get the message across that it should not be forced upon people. It should be optional if it is even bunduled with the os at all.
Related
Hey. I seem to have a problem with my phone.
Last night I was playing with my Sensation XE, and noticed that there was an app called "Wallpaper" taking up 60mb of memory, which was the biggest app at the time. I closed this app, and everything was fine, but it appeared again later. This time I cautiously disabled the app, and then checked that my wallpaper was still working OK, and I changed it a few times to make sure that was fine still, then carried on playing some games, and everything was peachy.
However, this morning I unlocked my screen to find a black screen where my phone used to be. The status bar at the top is there, and still works fine, and can be pulled down showing notifications, but even clicking on those notifications does not bring up the associated app onto the black screen below. Accessing the settings menu via the status bar also does not work, although it appears to open somewhere, as it appears in the recently used apps on the status bar menu.
Does anyone have any suggestions how I can re-enable this wallpaper app? Or any way to recover my phone? I have a previous backup from 1 month ago. Can the system state be recovered from that?
Thanks in advance for any help.
HTC Sensation XE
Flashed with Android Revolution HD 6.5.5
possible solution
hmmmm. have you used a task killer to keep the app disabled??
you could try to use adb ro remove the app entirely, and then use adb to reinstall it followed by a reboot. best make a full backup though incase it goes tits up. worst comes to worst do a backup of your rom, wipe and start fresh and reinstall apps from the backup.( i think thats possible )
heavy_metal_man said:
hmmmm. have you used a task killer to keep the app disabled??
you could try to use adb ro remove the app entirely, and then use adb to reinstall it followed by a reboot. best make a full backup though incase it goes tits up. worst comes to worst do a backup of your rom, wipe and start fresh and reinstall apps from the backup.( i think thats possible )
Click to expand...
Click to collapse
Thanks for the quick reply!
I haven't used a task killer for the disabling. I disabled it in the system page for the app. Where it usually has Force Stop, Uninstall, Clear Data etc. The uninstall option had changed to Disable.
I have used adb a couple of times in the past, but not extensively. Any chance you could run through the commands required?
al090187 said:
Thanks for the quick reply!
I haven't used a task killer for the disabling. I disabled it in the system page for the app. Where it usually has Force Stop, Uninstall, Clear Data etc. The uninstall option had changed to Disable.
I have used adb a couple of times in the past, but not extensively. Any chance you could run through the commands required?
Click to expand...
Click to collapse
I think the best thing for you to do would be plug into computer with usb debugging enabled.
Then run "adb reboot recovery"
from there reflash your ROM (a full wipe shouldnt be necessary)
then reboot and you should be good
Fixed
After many hours trawling google to try and find an answer, I finally found something.
http://forum.xda-developers.com/archive/index.php/t-1151150.html
I had no idea what the disabled app name was though, so I used the following to list the disabled packages.
Code:
pm list packages -d
The command needed to enable the apps was
Code:
pm enable APPNAME
Did a restart, and now everything seems fine again. That's possibly the last time I play with things on my phone.... Or maybe not.
Thanks for your help and time =]
Edit: Just to let anyone know, these commands are performed using a remote shell interactively through adb.
glad you got sorted buddy, and thats handy to know!
I am removing things like Kindle, Google TV, etc.....When I open the Playstore it all pushes back down. Any way to stop this?
EVOme said:
I am removing things like Kindle, Google TV, etc.....When I open the Playstore it all pushes back down. Any way to stop this?
Click to expand...
Click to collapse
Try disabling or freezing them instead. We only have limited root access, and I haven't checked, but I'm pretty sure we don't have root access to where the system apps "live". I disabled some, and froze others (by that I mean disabled through Android-Settings-App Manager, or froze through TiBu), and they're still frozen after a reboot.
Yeah right now root can only write to system/xbin I believe so freezing and disabling is gonna be your only option for right now. Any appearance of deleting apps will revert if you refresh the app or reboot the phone, is what I've read.
Freeze works fine. I de-bloated my M8 and it seems to stick after reboot.
I've never turned Zen Mode on.
I've disabled it in several places.
Despite disabling it everywhere, if I am on my phone continuously for 2 hours, I get a notification from Zen Mode telling me to put my phone down and enjoy my day.
I don't like that.
I'm rooted
I went into a root Uninstaller app to delete it, but it is considered a "key module"
Because the app keeps a recycle bin, and decided to Uninstall it anyway.
It wouldn't let me.
Uninstall failed.
Any suggestions?
Am I not posting things in the right place?
Thought this was the right place to post stuff, but I never get any responses to anything.
I "upgraded" to Android 11 and, among the myriad of other issues, I can't open accessibility settings at all. The ROM is stock, not rooted, and opening the accessibility app via the app info screen with the button in the bottom left pulls up a full screen notification that vibrates my phone telling me it detected a baby crying. Accessibility settings don't work at all.
Is anyone else experiencing this? Is there anything I can do that isn't a factory reset in order to fix this? I tried restarting to safe mode and the behavior doesn't change.
WiggleCat said:
I "upgraded" to Android 11 and, among the myriad of other issues, I can't open accessibility settings at all. The ROM is stock, not rooted, and opening the accessibility app via the app info screen with the button in the bottom left pulls up a full screen notification that vibrates my phone telling me it detected a baby crying. Accessibility settings don't work at all.
Is anyone else experiencing this? Is there anything I can do that isn't a factory reset in order to fix this? I tried restarting to safe mode and the behavior doesn't change.
Click to expand...
Click to collapse
Prior to your andoid 11 upgrade did you use adb to remove anything?
Limeybastard said:
Prior to your andoid 11 upgrade did you use adb to remove anything?
Click to expand...
Click to collapse
Yes, and the accessibility settings were working fine afterwards. I uninstalled things llke Chrome, Facebook services, and the default Samsung browser to name a few. I didn't full on debloat the phone, I only removed things that were actually bloatware I'd never used in the past and won't use in the future. And Facebook. If it matters, I have the unlocked variant of the N20U.
Edit: My next move was going to be pulling up a list of packages somehow that tells me which are installed for user 0 and which aren't to see where the problem lies. But again, I only uninstalled the obvious bloatware such as browsers that other apps would open over my default. Various background services, fonts, themes, etc that are just there but don't use resources, such as the car mode stuff I know I'll never use, was left alone.
WiggleCat said:
Yes, and the accessibility settings were working fine afterwards. I uninstalled things llke Chrome, Facebook services, and the default Samsung browser to name a few. I didn't full on debloat the phone, I only removed things that were actually bloatware I'd never used in the past and won't use in the future. And Facebook. If it matters, I have the unlocked variant of the N20U.
Edit: My next move was going to be pulling up a list of packages somehow that tells me which are installed for user 0 and which aren't to see where the problem lies. But again, I only uninstalled the obvious bloatware such as browsers that other apps would open over my default. Various background services, fonts, themes, etc that are just there but don't use resources, such as the car mode stuff I know I'll never use, was left alone.
Click to expand...
Click to collapse
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
I did disable the Samsung keyboard. That could be it. I'll give that a go when I get a chance.
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
WiggleCat said:
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
Click to expand...
Click to collapse
Glad it helped. It puzzled me originally also., Found it in the end by backtracking on all the apps I'd uninstalled via adb one by one.
Im having the same problem, how you guys solve this cant install the apk and look like on my case adb is not picking up my ui 3.0 s20+ maybe a complete wipe (which im trying to avoid) thanks in advance
Limeybastard said:
The reason I mentioned this was because I had a similar issue whereby selecting accessibility within the settings menu would result in null,meaning nothing would happen. If memory serves me correctly it was related to samsung keyboard that I had removed, but can't be sure. But I believe you're on the right track to figure it out.
Click to expand...
Click to collapse
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
User1038572 said:
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
Click to expand...
Click to collapse
My pleasure. Enjoy your stay here. Some nice folks.
User1038572 said:
Made an account just to say thank you so much for this. This was the perfect fix for me and I can use half of my apps again since I can use the accessibility app now. Never expected a keyboard uninstallation to scuff half of my apps.
WiggleCat as well for the honeyboard package name.
For anyone needing an easy copy paste into command prompt, it's:
adb shell
cmd package install-existing com.samsung.android.honeyboard
Click to expand...
Click to collapse
Thanks for the command. It fixed it for me!
Wow, i fixed successful, thanks thread.
Awesome the command fixed this issue on my S20 FE. Thanks so much for sharing!
Damn! that went smoothly. Accessibility fixed after reinstalling the Samsung keyboard. Anyways if someone still doesn't want that annoying keyboard shown, you can disable it via ADB. The command is
adb shell pm disable-user --user 0 com.samsung.android.honeyboard
Thank you for pointing out that the Samsung Keyboard was the issue.
For those of you without immediate access to ADB, you can also redownload the
Samsung Keyboard via the Galaxy Store.
WiggleCat said:
That was it. It was the Samsung keyboard. What a weird outcome for disabling something so trivial. I was trying to reinstall it with the old package name com.sec.android.inputmethod and it took me a while to figure out it is now called com.samsung.android.honeyboard. But once I reinstalled that for user 0 accessibility settings started working again. Thanks for the tip! I guess I'll have to leave that installed then.
Click to expand...
Click to collapse
This saved me by inches from factory resetting my phone. However not long enough to save my whole Macrodroid macros library that i had already uninstalled because it was no longer working since it depends on accessibility services and i was desperate to get a solution. However, i have learnt a big lesson that debloating need to be done carefully if not at all. some apps are critical bindles of other critical functions
Is the information here safe to be used for removing bloatware on my 8T?
edit: grammar error
imcrazyz said:
Is the information here safe to be used for removing bloatware on my 8T?
edit: grammar error
Click to expand...
Click to collapse
This isn't really removing, more hiding from the main user those apps, thus making them not start. But the apks are still here, and after a reset the apps will be there again.
This is totally safe tho, and it's a great way to get rid of them if you don't reset every 2 days, so feel free to try
i just tried using titanium backup paid version to freeze some apps. it still works. you won't see the apps in the drawer until you defrost them again.
issuing those adb commands will modify system settings, so it might be a pita to get updates after you do that. you'll have to remember which apps you deleted and reinstall them again. i could be wrong and this might be a non-issue, i just remember earlier days and modifying system data and then having to make sure all the stock apps were still there to take an ota.
ADB will not stop OTA's from taking place unless you uninstall/disable something relevant to the app that is needed to search/find/download/install the said OTA. After the OTA is applied the apps you uninstalled/disabled (whichever worked) will not come back. As mentioned, using ADB itself without root does not really uninstall them like you think it does. They're still there. So although an OTA will not show them to still be there, a factory reset will bring them back. So the only real way to completely uninstall bloat is to have root. But even then a factory reset will bring them back because they are built in to the native OS.
Raiz said:
This isn't really removing, more hiding from the main user those apps, thus making them not start. But the apks are still here, and after a reset the apps will be there again.
This is totally safe tho, and it's a great way to get rid of them if you don't reset every 2 days, so feel free to try
Click to expand...
Click to collapse
Disabling the app is just as good as removing it completely. There isn't really any reason to delete the apps like this (if no uninstall option exists) because once they're disabled they will not run.
I know people have a fascination with deleting system apps, but it's not like you can free up space this way.
Factory reset should bring them back. But this is safer for the integrity of the firmware.
Freezing system apps that do not have the disable option (with TB) is always preferred over deleting them, in my opinion.
Ultimately, you can always save yourself by using the MSM tool to restore.