Hey everyone, today i want to share a not so pretty but working workaround about an issue that seems to be happening on some GSI images on this device (and its predecessor as well, the Note 10S which i used to own!), and i also want to collect some data from some more knowledgeable people about this so we could get a proper solution.
The issue is that when the device is left locked and idle for around 5 minutes, apps lose network connectivity so not only you get issues like Spotify not playing anything anymore after the last played song before the phone lost connectivity, but most importantly app notifications can be delayed by a few minutes, sometimes even an hour or more, or just never get to you until you unlock the phone and either wait a bit or open that app yourself. After the device enters Doze, and after it is unlocked to exit it, it takes a bit but not too long before your notifications all come in again. This does NOT happen when the device is connected to a power source.
If you have this issue, a not-so-pretty solution i found at least for now is running the following ADB command from a computer:
adb shell dumpsys deviceidle disable
Click to expand...
Click to collapse
This disables Doze entirely until the next reboot (after every reboot you need to run this again or Doze will kick back in).
Now your device will never enter Doze for your current Android session, battery life doesn't seem to be impacted much if at all, but it's better to have less battery life than not getting important messages.
EDIT: At first i was blaming Doze being broken directly, but this seems to be related to a BPF bug in the MediaTek kernel, and it depends on the device manufacturer if they have merged the fix or not. I tested the same GSI on A12 MIUI, and it still has the bug (along with many other bugs which is why everyone tells you to flash A11 before you flash any GSI), so Xiaomi did not fix it yet.
This bug causes mostly networking issues, some ROMs like LineageOS 20 not having network due to Restricted Network Mode causing no network like that post says (workaround for that too there), Battery Saver completely killing the network and probably this issue. After some thinking, Doze actually is working fine (Spotify only stops playing when it tries to get a new song from the network, the song it already got keeps playing even on Doze), it's just the network in apps while on Doze that dies. I tried the same exact GSI on a SD device, and there are zero issues there. There also were no issues on A11 and A12 GSIs on my old Redmi Note 10s, which is also affected by the same sleep bug on A13!
For this particular issue, you can use that adb command, but be aware that other networking issues like the above might exist.
There are some other workarounds like unlocking the phone ever so often before it exceeds 5 minutes staying locked, which is just painful, or leaving it always connected to a power source which isn't always viable, so those are out of the question.
If anyone with more knowledge knows the cause of this and/or a less "bandaid" fix, feel free to reply here, it would be much appreciated both for me and other users with the same issue!
U are my man. i thought its a problem like that, but i dont figured out how to prevent.
i will test this and report if its working.
isnt it possible to run it as bootscript?
lurchiii said:
U are my man. i thought its a problem like that, but i dont figured out how to prevent.
i will test this and report if its working.
isnt it possible to run it as bootscript?
Click to expand...
Click to collapse
I think it's possible to run it as bootscript but i think it requires root and i don't know how to do either of these yet, sorry. Hopefully someone more experienced can help us
I tried this using termux(with su) and It works for now, I'll write in a few days if it still works
i tried to make a magisk-bootscript and it will be executed (according on magisk log) but when i checked with "adb shell dumpsys deviceidle enabled" it shows "1" but when i executed it manually with termux it shows "0". Idk why it dont worked on boot.
lurchiii said:
i tried to make a magisk-bootscript and it will be executed (according on magisk log) but when i checked with "adb shell dumpsys deviceidle enabled" it shows "1" but when i executed it manually with termux it shows "0". Idk why it dont worked on boot.
Click to expand...
Click to collapse
Hm that is weird, i have no idea. I never tried running the command from the phone itself, i usually just used adb on a computer. The output i got from the command was something along the lines of
"Light idle mode disabled
Deep idle mode disabled"
(may not be exact message but you get the point)
Try running the command from a computer and see if it works, should work fine there.
from pc or from termux its np but from a bootscript it wont work. i think dumsys command can only be executed after boot or something?
it seems im not alone on the whole wide world:
Execute a script at boot
Hello, I'd like to execute a easy script at every boot of the phone so basically I've placed the script in the folder /sbin/.magisk/img/.core/service.d/doze.disable.sh I've tried also putting it in...
forum.xda-developers.com
but i found these interesting commands + module:
Universal GMS Doze - Magisk
Systemlessly prevent unnecessary GMS running in the background, optimized and adjusted with additional modified services.
themagisk.com
lurchiii said:
it seems im not alone on the whole wide world:
Execute a script at boot
Hello, I'd like to execute a easy script at every boot of the phone so basically I've placed the script in the folder /sbin/.magisk/img/.core/service.d/doze.disable.sh I've tried also putting it in...
forum.xda-developers.com
but i found these interesting commands + module:
Universal GMS Doze - Magisk
Systemlessly prevent unnecessary GMS running in the background, optimized and adjusted with additional modified services.
themagisk.com
Click to expand...
Click to collapse
Hm, that module actually looks like it limits some apps in the background, which is what exactly triggers this issue. Basically whenever the OS tries to limit network for some apps, it's bugged due to the kernel and instead of limiting it only for some apps it limits it on all apps and it happens on Doze, battery saver and restrictive network mode. About trying to run it as boot script, i haven't tried, but yeah it probably needs to be ran once the OS is fully booted.
SuperLolMine said:
Hm, that module actually looks like it limits some apps in the background, which is what exactly triggers this issue. Basically whenever the OS tries to limit network for some apps, it's bugged due to the kernel and instead of limiting it only for some apps it limits it on all apps and it happens on Doze, battery saver and restrictive network mode. About trying to run it as boot script, i haven't tried, but yeah it probably needs to be ran once the OS is fully booted.
Click to expand...
Click to collapse
i mean that command under "Troubleshooting"
lurchiii said:
i mean that command under "Troubleshooting"
Click to expand...
Click to collapse
Oh yeah, that still controls doze, but basically the issue with BPF bug is that the OS can't restrict network for only some apps because then all apps lose network connectivity. I'm not sure if adding an app to the Doze whitelist may work, and even if it did you'd have to do it for every app you want notifications for. At least adding to the whitelist is permanent instead of the disable command which is temporary, but i'm not sure it will work, i think the best thing for now is trying to find a way to run the command at boot or at least from the phone itself without needing a computer.
Thanks for the idea though, sadly i can't test the whitelist right now as i'm back on MIUI (probably going back to PE soon)
SuperLolMine said:
Oh yeah, that still controls doze, but basically the issue with BPF bug is that the OS can't restrict network for only some apps because then all apps lose network connectivity. I'm not sure if adding an app to the Doze whitelist may work, and even if it did you'd have to do it for every app you want notifications for. At least adding to the whitelist is permanent instead of the disable command which is temporary, but i'm not sure it will work, i think the best thing for now is trying to find a way to run the command at boot or at least from the phone itself without needing a computer.
Thanks for the idea though, sadly i can't test the whitelist right now as i'm back on MIUI (probably going back to PE soon)
Click to expand...
Click to collapse
to run the command without PC and without repeatedly typing it, i use Script Manager:
Script Manager | F-Droid - Free and Open Source Android App Repository
An application to manage shell scripts!
f-droid.org
Add a new Script and type:
#!/system/bin/sh
dumpsys deviceidle disable
Hit save and apply.. done
lurchiii said:
to run the command without PC and without repeatedly typing it, i use Script Manager:
Script Manager | F-Droid - Free and Open Source Android App Repository
An application to manage shell scripts!
f-droid.org
Add a new Script and type:
#!/system/bin/sh
dumpsys deviceidle disable
Hit save and apply.. done
Click to expand...
Click to collapse
Oh, i didn't know about this application, thank you! I usually had to use a pc when i reboot my phone for whatever reason so it's nice to at least be able to do it from the phone. I wonder if a boot script can be made with maybe another app that runs a little bit after startup
i tried with :"sleep xx" but it wont help.
Related
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
peste19 said:
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
Click to expand...
Click to collapse
Do you have experimental mode enabled? I think you need the donation pack as well as root to greenify system apps.
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Has anyone noticed some improvements using greenify with s6?
peste19 said:
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Click to expand...
Click to collapse
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
isangelous said:
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
Click to expand...
Click to collapse
how did you use tasker to enable the hibernation? i am a bit new at this
peste19 said:
how did you use tasker to enable the hibernation? i am a bit new at this
Click to expand...
Click to collapse
I just had a look but unfortunately I don't have the profile anymore to export it for you.
Doing it from scratch would be a bit daunting if you have never used Tasker before.
You basically need to:
1. Set a variable for the display state (ie, on, off and unlocked). %DisplayState
2. Have a task for the screen unlock which sets a variable %NeedToGreenify or similar.
3. Have a task for the when screen off event triggers and %NeedToGreenify is set. This task waits 10 minutes. Then check if the screen is still off - this is what %DisplayState is for (Stop if it is not). Clear %NeedToGreenify. Trigger Hibernate (Greenify is a 3rd Party Plugin). Wait 30 seconds. Turn the screen off "SecureSettings - LockDevice".
I think I may have also used SecureSettings to keep the screen on while the process is running. You will also need to set the task options to "abort existing task" if it is already running.
I think this is how it worked, but it was a while ago :/
SuperSU doesn't seem to be working the way it always has on my other devices in the past. After successfully flashing TWRP 2.8.7.0 [6.0] EN (by Sminki *xda* repack) on my Honor 7 with multi-tool and then installing SuperSU via TWRP and gaining root access, I rebooted my phone and immediately Google Play wanted me to update the SuperSU app. I updated the SuperSU app and also installed SuperSU Pro that I had purchased previously on another device. I then installed terminal emulator so I could confirm that I had root access by running the su command. However after running the terminal emulator and attempting to use the su command nothing happened. I didn't get an error that I would expect if root wasn't present such as su not found, it just seems to sit there waiting. It then occurred to me that I hadn't received the usual popup from SuperSU asking me whether I wanted to grant root permission.
From what I have been able to work out I do have root access but for whatever reason SuperSU is not displaying its message asking me to grant or deny access. I have managed to establish that I do have root by going into the SuperSU settings and setting the default access as grant rather than prompt after which terminal emulator is able to use the su command.
Does anyone know how I can get the prompt to work? I would rather have SuperSU prompt me when an app requests root access for security reasons since giving any app that requests root unfettered access probably isn't the best idea.
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
adxuser said:
If your problem has anything to do with SSU Pro then I dont say nothing cause dont use it.
Anyway going the same procedure as you I had, after GPlay update, the problem when trying to open SSU with message "SSU binary cant be found" or sth like this. However my SSU has been working (at least it did look alike) giving prompts.
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
It looks like it is H7 speciality ;p. You need to flash B330 twice for 100% and you need to install SSU twice ;p
ps. Also "Draw over other apps" on but it was automatic - at least for me
Click to expand...
Click to collapse
Thanks. Seems to be working now. Also disabling doze altogether on marshmallow seems to have solved a lot of other issues I was having since the marshmallow update and subsequent custom recovery and root install.
Squall88uk said:
disabling doze altogether on marshmallow
Click to expand...
Click to collapse
By "Doze" you mean those switches to kill apps after screen lock or not?
adxuser said:
By "Doze" you mean those switches to kill apps after screen lock or not?
Click to expand...
Click to collapse
No I mean Marshmallows built in doze feature. I have the switches you're talking about set to let the app keep running for important apps like SuperSU anyway but they only affect EMUIs own power manager. Doze and EMUIs power manager seem to fight each other anyway and I don't like how doze stops my notifications coming through with some apps and interferes with other apps that I like to leave running all the time like AcDisplay.
I completely disabled doze altogether using "dumpsys deviceidle disable" in terminal emulator or using adb shell. The only problem is that it will be re-enabled after a reboot so I used the universal init.d app to run an init.d script on every boot to disable it again since the honor 7 kernel doesn't natively support init.d. I have all the apps that I had on lollipop (plus some more that I didn't have on lollipop, since I didn't have root when I used lollipop) set up exactly the way they were then and let EMUI handle the power management. I get about the same battery life that I had in lollipop which is fine for me since I charge it fully every night anyway.
I am just in process of developing opinion on that. For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
adxuser said:
For sure made one mistake prefering Google Clock over Huawei (and uninstalling the latter) but now even with adequate settings (for example it should have auto-start set by PM Plus add-on for Phone Manager) I am not so sure of my alarms ; ) I have been accustomed to Vanilla Android till now.
Click to expand...
Click to collapse
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
adxuser said:
Ok. I had to do my lecture on MM Doze & App Standby functions. Also I am newbie on EMUI.
It looks like that many important things (background GPS runnings apps, notifications, alarms) can be double complicated on MM Huawei :/ (not to mention other EMUI problems e.g. with lock screen)
We have clean MM Android with its problems even for Nexus owners, then we have EMUI with its own background / notifications problems.
Click to expand...
Click to collapse
Agreed. While EMUI does have some of its own features that can be useful a lot of things are twice as complicated as they need to be. I have generally found that just allowing all apps that have notifications you want to receive e.g. twitter set to be allowed to autostart and run in the background as much as they like seems to reduce issues with notifications (still not worked out if it completely stopped any issues), and even then if I want notifications to display correctly on the lockscreen, not only do I need to allow them for each particular app on the lockscreen through the notification manager I still have to use a lockscreen replacement which in my case is AcDisplay. To be honest I have every app set to run on autostart and in the background and I still haven't found that it has much impact on battery life and this seems to solves a lot of these kinds of issues for me. My previous phone (Samsung Galaxy A3) used touchwiz and never had any of these options so I've always assumed that touchwiz/android allowed apps to run when they wanted and access what they wanted within the scope of their permissions and everything always worked fine, admittedly battery life was an issue on that phone but it had a much smaller battery capacity than the Honor 7 and it still lasted me most of a day.
adxuser said:
So 'Ignore optimisations' switch is by Google. You do not use it but maybe know which Google / Huawei apps should have optimizations off? (I have there Android System WebView - why? Google product should have it invisible, Fused Locations - the same, HiSuite ?, HwAps ?)
Anyway people report that it does not help for GPS tracking apps shutdown problems, but it is rather related to EMUI I think.
Click to expand...
Click to collapse
I tried messing with the Ignore optimisations switch when I first upgraded to Marshmallow and it didn't seem to make any difference apps were still being afflicted with issues. I asked honor uk exactly what it did and whether it was for doze or not and they didn't know. I'm sure if I spoke Chinese and asked the Chinese customer service they would be able to tell me straight away but I never managed to find out. Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
adxuser said:
PS. 1. I do not think Huawei / Google power managers fight in any way. Huawei power manager stricly speaking these are drivers for hardware needed + basic user power handling setup.
What they did on higher level is this "keeps running after screen off" switch but I would not be so sure if this, set one or the other way (and Huawei soft in general), works properly with GCM messages and other wakeups. One should keep in mind that Huawei sells a lot without Google apps at all.
Click to expand...
Click to collapse
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
adxuser said:
PS.1.b. Some apps need some changes to work properly with Doze. They are not allowed now to do what they like and when they like. And if they have to say sth they must use GCM message , if they have sth important to say they must use GCM high priority message. Android 5.1 API level 22 alarms do not fire now, there are 2 new methods from what I read. And Google could block spamming "high priority messages". So idea & direction is good I think. For not MM updated apps put them in Ignored.
Click to expand...
Click to collapse
I like the idea of doze in general and I'm generally a fan of most things that google do with android. If i was running a nexus or an AOSP rom I would definitely leave doze activated and only disable its optimization for apps that either coded with doze in mind or apps which I personally consider to be high priority regardless of whether google agrees such as twitter. I lie to get twitter notification that I have enabled as soon as the tweet they link to is tweeted not at the intervals that doze allows apps to update at. But that's a personal thing rather than an issue with the idea. So for YouTube notifications for example I would be quite happy for doze to run the show.
adxuser said:
PS2. In my opinion also you should not confuse B330 power handling issues with Doze.
It could be just Huawei optimizing things: taking away fast charging switch because it is on default now, making changes to power handling etc. or not making changes needed so now it could be the problem with Android. People claiming worse battery life for B330 claim mostly best on B320.
Click to expand...
Click to collapse
My intention has never been to confuse EMUI's power handling with Doze. I have just been trying to simplify the issue for me. as I have already said I generally allow any apps to do what they want both in EMUI's settings and by disabling doze as its simpler that way for me. Battery has never been an issue for me with either lollipop (B180) or marshmallow (B330) for me personally but i'm sure for some people it can be.
Squall88uk said:
What's wrong with the Google clock? And what problems did you have after uninstalling the Huawei clock? I use the Google clock as my main clock app and have had no issues with it on either lollipop or marshmallow even after uninstalling the Huawei clock.
Click to expand...
Click to collapse
nothing wrong, in fact I've chosen it deliberately.
Basically prefer Google apps cause they can be updated and whats more new features are added from time to time, with let's say B330 stock you are left with B330 stock unless and if Huawei pushes sth new.
Just for some producers ROM's there are sometimes apps good enough and also interconnected on some levels with launcher / lock screen / power management that it is better to leave them & even make use of them.
Squall88uk said:
Even with doze disabled completely on my device I still have it set to ignore optimisations for all apps in case its something to do with EMUI.
Click to expand...
Click to collapse
Rather strange for me what you're doing.
Squall88uk said:
What I meant by fight is that the 2 have their own settings rather than these being integrated with each other. So for example when specify that I want an app to be able to run in the background while the screen is off in an ideal world this would also tell Google's doze that I do not want it to doze that app. otherwise I have to effectively set the same thing twice even though it may be called different things.
Click to expand...
Click to collapse
It cant be integrated, it is Google licensed system. Doze & App standby these are powerfull, long-term features.
This EMUI function is just easy switch to kill sth after screen off. Not sure of it
Also not sure of this auto-start PM Plus utility It is not only auto-start on system start but also start on events. Powerfull mess with many apps without granular controls.
However I use both ;p
edit. ok, it looks you're right about Doze. I.e. Huawei Doze problem. Here for Mate 8:
http://forum.xda-developers.com/showpost.php?p=64827731&postcount=15
Not solved as I see (but no time to read everything)
So Paul @paulobrien solution is with his ROM, your solution is to shut down Doze, I would prefer Doze properly working on (rooted) stock solution
adxuser said:
The solution was SSU cleanup, copying and installing SSU once again. If you check some threads here you will find some kinds of initial problems with SSU are quite common.
Click to expand...
Click to collapse
I have the same problem on my tablet Huawei MediaPad T1 8.0 Pro.
Please explain exactly what supposed to mean is "SSU cleanup, copying and installing SSU once again".
If one makes SSU cleanup then root access will flee for good and installing SSU again encounter the stark barrier, right?
If of course by "cleanup" you mean SuperSU's SETTINGS -> CLEANUP -> Reinstall (?)
@ioy
Do you have EMUI 4.0 on your tablet?
Some tips & tricks work between some Huawei models but for sure not each on everyone...
Anyway I made (in SSU) cleanup for full unroot (if I remember correctly :/) and by "copying & installing" I mean H7 procedure to copy and install via TWRP.
So full unroot and full root once again and in my case it solved my problem.
@adxuser, and what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Please, respond...
How to use cleanup options in SuperSu, there're several ones intended for switching to another su application - all of them work the way they need TWRP or maybe it is possible to switchin the system (booted)?
@ioy
what is EMUI 4.0 and how to check if it is on the tablet?
Where to learn about these tip & tricks?
I do not have TWRP because I wanted to have warranty still intact so not unlocked bootloader, and that's why I have unrooted with KingRooot and afterwards switched to SuperSU with SuperSume.
Click to expand...
Click to collapse
Emotion^^ User Interfece - Huawei visual & control overlay over Android.
For your http://www.gsmarena.com/huawei_mediapad_t1_8_0-6705.php 4.3 not upgradeble Android it is probably 2.0? (settings > about).
Tips & tricks those are some common to EMUI solutions - working on many Huawei models. They are nowhere together to be found, you have to search in all Huawei models if you are looking for sth. special. Anyway as you probably understand from JellyBean EMUI no.x to MM EMUI no.4.0 (or 4.1) that is a long way (some common things could even work however).
And also I am not a root specialist but if you have a locked bootloader SSU will never work so make a full cleanup and do not try again
Maybe this KingRoot will work but search for info on that.
ps. in most "normal" countries unlocked bootloader hasn't got anything to warranty.
Yes, KingRoot worked normally, prompt popup windows worked neatly.
However, Huawei itself warns if you unlock the bootloader then they will not help you anymore in case of trouble. And as you maybe know already, Huawei official assistance is needed in doing unlocking bootloader, it is done through their site and first this terrible warning is displayed... (presumably they register phone's IMEI, serial number and these data is then spread to warranty service outposts worldwide)
Yes, they can track and they probably track a lot more easily
Regarding warranty it may and it vary from continent/country to continent/country but local (e.g. european) regulations take effect on that matter.
So Huawei China can even track what I did with the phone yesterday at 6pm but when I am able to relock the phone (even with status relocked) and it could be seen that it is malfunctioning because of hardware failure then I am talking to Huawei in Europe and I am totally not interested what Huawei China has to say.
So sometimes there are some commom myths and you should check (in a proper way ) what are the possibilities.
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Please try to provide any clue, about those tips& tricks in respect of popup windows, as as I can see usual popups for any application are not present in this Huawei model... Apparently something must block them in a regular manner...
ioy said:
And you have cited wrong model, this one is Huawei MediaPad T1 PRO LTE:
http://www.gsmchoice.com/en/catalogue/huawei/mediapadt18.0lte/Huawei-MediaPad-T1-8.0-LTE.html
Click to expand...
Click to collapse
Quite possibly. Just a quick look.
As you probably understand we are on H7 subforum and I am not interested in other devices with its variants.
ioy said:
It has 4.4.4 Android version, and Emotion UI version 2.3, so what are these tips & tricks for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66946525&postcount=12
Allright, how is it possible to switch off / disable this EMUI? What to freeze without bricking the phone? Presumably indeed this blocks popup windows itself and at all it seems providing no gain, plain Android is better and there are many apps on PlayStore with genius functions and full user's control, so please which system or internal memory apks are responsible for this EMUI and one normally can freeze them thus freeing the 'core' Android system from this dubious attraction?
Every time I disable "Find My Device" under device administrators, it re-enables itself whenever I reboot my phone. In the phone settings, I turned off location and went to Google->security->Find My Device and toggled off. Then I went to my Google account on my PC to remove the device. Nope! Makes no difference. WTH?! Come on, Google! you creep up on my phone. I have to disable it because when it's enabled, it causes issues with MacroDroid app. My phone is rooted. I'm on Marshmallow 6.0.1 Any solutions? Google makes me wanna rip out my hair. Ugh, this is a nightmare. Same issue on another phone
Can confirm this too.
See that since Yesterday... Android Oreo and/or Pie! Makes no difference... Zte Axon7...
Thanks to Google for this funny new Feature :good:
It might help if you mention either of the phones you're talking about, just in case this is a device specific issue.
If it's re-enabling itself on reboot, it doesn't sound like you're disabling it properly. Try freezing it using Root Uninstaller to freeze the app.
free_axon said:
Can confirm this too.
See that since Yesterday... Android Oreo and/or Pie! Makes no difference... Zte Axon7...
Thanks to Google for this funny new Feature :good:
Click to expand...
Click to collapse
Thank you for confirming this. The feature disappears when I disable Google Play services but I can't leave it disabled
Redline said:
It might help if you mention either of the phones you're talking about, just in case this is a device specific issue.
If it's re-enabling itself on reboot, it doesn't sound like you're disabling it properly. Try freezing it using Root Uninstaller to freeze the app.
Click to expand...
Click to collapse
Firstly, my device and running system are in my post, as you meant me too. I'm quite sure it's not device related... This "issue" appears as soon as i update to the new beta of gplayservices and disappears as soon as I downgrade!
One after another in by friendships have it now, too. So it's rolling out with stable, because none of them is beta tester or it comes over another backdoors...
Redline said:
It might help if you mention either of the phones you're talking about, just in case this is a device specific issue.
If it's re-enabling itself on reboot, it doesn't sound like you're disabling it properly. Try freezing it using Root Uninstaller to freeze the app.
Click to expand...
Click to collapse
Right now I'm using LG Volt. Another one is ZTE Warp 7. It's the feature, not the app. If It were the app, I would uninstall it. I tried disabling the feature under Google Play services via the app called "Disable Application [ROOT]" by BIZKAI Apps but it asked me to pay for it pfftt
Hi, did anyone manage to solve this issue? I'm trying to disable Google's device admin access but it keeps turning on by itself
The settings might not be saved to your Google account properly , try connecting your device to a stable internet connection and disabling it .. might work, usually same happens with my device when enabling adb(debug security settings) if internet connectivity is poor.
If you're still looking for a fix, I've finally found one! https://forum.xda-developers.com/apps/magisk/module-universal-gms-doze-t3853710
Fyi...it seems the GmsIntentOperationService service in GooglePlayServices is what is causing it to re-enable at boot. If you are rooted and disable this service it stops re-enabling at boot. Google should fix this....not cool Google.
fish312 said:
If you're still looking for a fix, I've finally found one! https://forum.xda-developers.com/apps/magisk/module-universal-gms-doze-t3853710
Click to expand...
Click to collapse
I've tested that Magisk module on a Blu Life One X3 phone, rooted with TWRP as bootloader and Magisk as root. It does indeed permanently disable 'Find My Device' (and removes it from the Device Administrators list), but on this particular phone, it messes up the WiFi connection... it flips between 'Connected' and 'Connected, No Internet', and doesn't transit any data.
I uninstalled the 'Universal GMS Doze' Magisk module, and WiFi functionality returned to normal, but 'Find My Device' was re-enabled. I did this three times, just to be sure, same each time.
For now, to save battery, I'm using 'Enable Doze for GMS Magisk Module' Magisk module, but it doesn't disable 'Find My Device' like 'Universal GMS Doze' does.
I'm now looking at using Disable Application [ROOT] (package:/data/app/com.iamaner.oneclickfreeze-1/base.apk=com.iamaner.oneclickfreeze) to stop the Google Play Services from setting a Device Administrator... you should check out that program, it's awesome. It's a paid program, but it's well worth the coinage.
Here's the Google Play Services activities:
https://github.com/alt236/apkdetails/blob/master/sample_output/google_play_services_11.9.49.md
We have a few avenues to explore in turning off 'Find My Device' permanently:
com.google.android.gms.mdm.receivers.ActivateDeviceAdminUponUnlockReceiver
com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
android.permission.MANAGE_DEVICE_ADMINS
{forgive the spaces in the above... the xda-developers.com editor adds them, for some reason}
s00thsayer said:
GmsIntentOperationService service in GooglePlayServices is what is causing it to re-enable at boot.
Click to expand...
Click to collapse
How's it possible to fetch that Service, with non-root? Best I can get on Android One is:
I'm not sure you can do it, non-root. I'm trying to figure out the ADB command to disable 'Find My Device' permanently... it's got to be related to what I posted above. Still experimenting.
Turn off the find my "device"
If you would like to remotely locate, lock, ring or erase your device, view this info.
Notes:
Find My Device Android allows you to remotely locate, lock, ring or erase your device.
A GmailTM account must be set up on the device to utilize Find My Device.
Log in to the Find My Device Device (URL: google.com/android/find) to access these services.
From a Home screen, navigate: Apps > Settings > Google (Google services).
To allow the device to be remotely located:
Tap Location.
Ensure the Location switch (located in the upper-right) is set to the ON position.
Tap Security.
Tap the following switches to turn on or off:
Remotely locate this device
Allow remote lock and erase
Hope: It will helps.
That doesn't work for me, as I've disabled Google location features in build.prop and disabled Captive Portal Login connectivity checking (which checks with a Google server to switch your WiFi icon to 'Connected' from 'Connected, No Internet'), as I explicate here:
https://forum.xda-developers.com/ge...bootloader-t3812910/post79374402#post79374402
So Google can only see if the phone is online or not. It can't locate it, nor can it communicate with 'Find My Device'.
But good news! If you install AFWall+ and disable:
[10014] Google Play Services, Google Services Framework, Google Account Manager
[10023] Google Play Store
for both Data and Wifi in the firewall, Google can't even tell when your phone is online.
What I did was to set up three profiles in AFWall+, one with the basic connectivity enabled and Google enabled, one with basic connectivity only, and one lockdown profile (nothing enabled). Set up AFWall+ so it shows a notification, press that notification to take you to the AFWall+ window. Just below the green header, you'll see a drop-down box where you can quickly switch the profile. Or set up the widget to do the same thing.
Heh, leave it to Google to make permanently disabling "Find My Device" as unintuitive as possible.
Go to Settings > Google > Security > Find My Device > Turn it off
If you simply go to Settings > Security > Device Administrators and disable Find My Device, it'll re-enable itself upon reboot.
futuretricks
very informative
---------- Post added at 05:50 AM ---------- Previous post was at 05:47 AM ----------
very wonderful
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
wonderful
Lusty Rugnuts said:
We have a few avenues to explore in turning off 'Find My Device' permanently:
com.google.android.gms.mdm.receivers.ActivateDeviceAdminUponUnlockReceiver
com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver
android.permission.MANAGE_DEVICE_ADMINS
{forgive the spaces in the above... the xda-developers.com editor adds them, for some reason}
Click to expand...
Click to collapse
I can't find any of them to disable.
i had the same problem, every reboot option returned on. i fixed with this command from terminal emulator. i use TERMUX APP.
type "su" then enter and allow root
type "pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver" then enter.
this makes DISAPPEAR the total row of the option find my device. and disable 4ever. tested now on lenovo p2, havoc 2.9 pie
realista87 said:
i had the same problem, every reboot option returned on. i fixed with this command from terminal emulator. i use TERMUX APP.
type "su" then enter and allow root
type "pm disable com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver" then enter.
this makes DISAPPEAR the total row of the option find my device. and disable 4ever. tested now on lenovo p2, havoc 2.9 pie
Click to expand...
Click to collapse
I did this, worked for 3 days then my phone rebooted by itself (which has never happened before). When it powered back on, Find My Device came right back in an enabled state. I have a HTC 10 and almost positive this is what causes the horrific battery life. Once its disabled, my battery history is fairly flat. Every 3 days or so it will re-enable itself and its fairly obvious when it happens -- my battery starts draining much faster. There has to be another way to block this completely, I've already disabled it in my Google account, on the phone, and unchecked it in device admins but again, 3 days later its enabled again like a bad virus.
Do not worry, this is not the old TicSystem trick - this is better
/!\ Only for TicWatch Users /!\
Hello,
While attempting to change my Wear OS accent color via ADB, I discovered a way to speed up the watch around 2.5 times (measurements done lazily, could be wrong. Still makes it faster, though.) - It does not cripple the watch at all (I have not tested battery life)
While everyone knows the one with disabling TicSystem (for you curious souls, it does not cripple the watch at all), I believe I may be the first one to do this. It revolves around Mobvoi's Wear OS overlay. Doing this trick made my watch really fast. The watch is around 2.5 times more responsive now and no matter what I do, I can not get the watch performance to slow, as it normally would.
It runs even better if you disable TicSystem too (Bottom power menu - you can literally use the top power menu instead, if you remove TicSystem)
Here is a step by step instructional tutorial:
1.) Enable Developer Options
---
2.) Disable All Animations (you can enable those again later)
---
3.) Enable ADB Debugging
---
4.) Hook your Watch up to your computer with ADB and all that stuff (I really do not want to go in depth on how to hook up your watch to your PC, You can google that)
---
5.) Type "adb devices" to connect your watch and start daemon
---
6.) Type "adb shell cmd overlay list"
---
7.) If there is a com.mobvoi.ticwatch.jupiter.home (or something containing the same words in a different order) continue with this guide. If there is not, leave this guide
---
8.) Type "adb shell cmd overlay disable com.mobvoi.ticwatch.jupiter.home"
(or however else your overlay is called)
---
9.) Type "adb reboot"
to reboot the watch
---
OPTIONAL 10. Enable animations again)
---
That is it, the watch now runs very much faster without any usability difference. To be honest, I am still not exactly sure why it works, but it works.
I have been doing a lot of testing and I just can not find anything that went wrong when I disabled it. There simply seems to be nothing. Everything works.
If some issue does come up, please let me know. Also, if there is an issue, you can just reproduce all the steps here, but replace the command in step #8 with "adb shell cmd overlay enable com.mobvoi.ticwatch.jupiter.home"
(Also, if any other fellow android developers are reading this, please help me understand why in the world uninstalling the package itself slows the watch down again. I have been scratching my head at this for a while now. Maybe it is placebo?)
(Disclaimer: I am not responsible for any damage to your watch. Even if this is unlikely to cause any damage, you are responsible for anything that might happen)
I don't have those mobvoi overlay, only google's
Code:
com.google.android.gms
[x] com.google.android.wearable.overlay.gms
com.google.android.wearable.app
[x] com.google.android.wearable.overlay.home
I don't feel lag actually since the first I use ticwatch E, of course after disable most system app. The latest change only to disable ticsystem which render the battery life longer, approx 20%.
You most likely just disabled the Jupiter home app. This guide is directed at people, who do not want to get rid of the whole Mobvoi experience, but still want a faster watch
I only disabled these
com.mobvoi.companion.aw
com.mobvoi.wear.account.aw
com.mobvoi.wear.fitness.aw
com.mobvoi.wear.health.aw
com.mobvoi.wear.heartrate.aw
com.mobvoi.wear.social.aw
com.mobvoi.wear.system.aw
It seems the jupiter home app only available in ticwatch pro, not in my ticwatch e.
Thanks for the sharing.
with your method. i lost esential mode
Clarification
I am just adding an update here.
There is no correlation between essential mode and the Jupiter app. The person who said this was simply making it up.
Thank you.
Honza368 said:
I am just adding an update here.
There is no correlation between essential mode and the Jupiter app. The person who said this was simply making it up.
Thank you.
Click to expand...
Click to collapse
Confirmed.
I can't seem to find mobvoi overlay on my ticwatch S
In something unrelated, I wanted to ask if anyone could share the latest ticpulse apk, as my one doesn't update through the play store anymore
I've deleted all from com.mobvoi packages, and lost essential mode/second screen with always on display on TicWatch PRO3. Anyone konw how's called a packgage which controls essential/second screen.
Thanks
Tried on Ticwatch pro 3 GPS - significant change in responsiveness! Thank you
On my Ticwatch Pro 3 GPS there is no option to switch on ADB over WiFi.....only via Bluetooth.
Where did you find it?
bikerhammer said:
On my Ticwatch Pro 3 GPS there is no option to switch on ADB over WiFi.....only via Bluetooth.
Where did you find it?
Click to expand...
Click to collapse
First enable developer options. Then you should see.
Developer options are enabled in settings/system/information/build version. You have to tap on build version 5 times or more.
I know and I did it. But there is no option for this.....
There only is a switch for ADB-Debugging and another for Debugging over bluetooth.
Thats weird. Never the less, why don't you try to do it via bluetooth?
How to do this?
Luciano_Hradsky said:
Tried on Ticwatch pro 3 GPS - significant change in responsiveness! Thank you
Click to expand...
Click to collapse
did you use the charger cable to run the commands via pc or over wifi? because when i do that my pc only charges the watch , i can't see it under adb devices. thanks.
Thanks man, definitely faster now
Good find, but this doesnt need dev options nor ADB. Goto Settings > Apps and Notifications > App Info > System Apps; find com.mobvoi.ticwatch.jupiter.home and disable it there.
Bazzeil said:
Good find, but this doesnt need dev options nor ADB. Goto Settings > Apps and Notifications > App Info > System Apps; find com.mobvoi.ticwatch.jupiter.home and disable it there.
Click to expand...
Click to collapse
After disabling com.mobvoi.ticwatch.jupiter.home via adb, a restart resulted in it enabled again. Maybe i did something wrong this way?
Following quoted method was permanent after restart.
Hi admins
Why android system takes 52% of my battery? Is this normal?
Device: Samsung A10s running android 10 2/32
Thank you.
It's NOT Android OS itself that consumes this amount of battery charge.
My guess is that Android OS only takes ~10%.
The programs / services which run on top of Android OS are using device's CPU what is draining device's battery.
To get an idea what is actually running on your phone you use ADB and run the following commands
Code:
adb devices
adb shell top
or install & run BetterBatteryStats APK that allows users to monitor how the battery is being used by the operating system and apps.
go to the battery options and enable "adaptive power saving"
some of it surely is samsungs bloatware
you can remove them without root using adb commands
search for the apps that are most consuming
also enable developer options, and limit the background process to 2
jwoegerbauer said:
It's NOT Android OS itself that consumes this amount of battery charge.
My guess is that Android OS only takes ~10%.
The programs / services which run on top of Android OS are using device's CPU what is draining device's battery.
To get an idea what is actually running on your phone you use ADB and run the following commands
Code:
adb devices
adb shell top
or install & run BetterBatteryStats APK that allows users to monitor how the battery is being used by the operating system and apps.
Click to expand...
Click to collapse
How about adb codes to reduce battery drain or some diy tricks cuz i already ysed greenify and still the same, any helps will be appreciated thank you sir❤
ZodiacFam said:
How about adb codes to reduce battery drain or some diy tricks cuz i already ysed greenify and still the same, any helps will be appreciated thank you sir❤
Click to expand...
Click to collapse
greenify faitly useless...
battery drain also depends a lot on the device, some processors are more power hungry (even in idle) then others,
but some things help:
use 50% or less brightness, limit backgroud apps to 1 or 2 maximum, enable the adaptive battery mode
put all less frequent apps into sleep mode
debloat your device - and not only crap apps, use as little aps as you can
search for battery draining apps on your device that can be disabled or removed, for example the samsung "AASAservice"
and snapchat, tinder and other dating apps, any news app, facebook, streaming apps, microsoft apps etc. Use the website instead of the app whenever possible (this also fights telemetry)
widgets help draining battery, avoid using them as much as you can
disable bluetooth when you dont need it
and avoid getting your mobile phone hot - like leaving it on a cars dashboard, a place with direct sunlight, high temperature stresses the device, and drains more battery
cheers
Turn off all power management except screen/ power mode, set to optimize.
Android can manage it's self fine.
Clear Google Play Services clear its data as needed.
It can be disabled with a package blocker but is needed for gmail, Playstore; enable as needed.
Disable Google Backup Transport and Framework, clear their data as needed.
Disable all cloud stuff, carrier, Samsung, Google feedback.
Karma Firewall can be used to block the above system apks and reduce battery usage.
agonoize said:
some of it surely is samsungs bloatware
you can remove them without root using adb commands
Click to expand...
Click to collapse
This statement is wrong: On non-rooted devices you by means of ADB can only hide apps to user, but not remove them, hence they still last on storage memory.
WhatsApp is half the problem...
jwoegerbauer said:
This statement is wrong: On non-rooted devices you by means of ADB can only hide apps to user, but not remove them, hence they still last on storage memory.
Click to expand...
Click to collapse
i currently have a samsung A01, and my mobile is not rooted, yet i removed all apps i do not want, including system apps, all google apps aside from playstore, i do not recall the exact numbers but i did get more space afterwards
if i try the command to enable them it fails telling me the app does not exist, if i look trough adb shell pm list packages the ones i 'uninstalled' are not listed, the apps are really gone
so maybe it depends on the brand and model? on some it can be done, on others not?
although i tought it could be done on all of them
agonoize said:
i currently have a samsung A01, and my mobile is not rooted, yet i removed all apps i do not want, including system apps, all google apps aside from playstore, i do not recall the exact numbers but i did get more space afterwards
if i try the command to enable them it fails telling me the app does not exist, if i look trough adb shell pm list packages the ones i 'uninstalled' are not listed, the apps are really gone
so maybe it depends on the brand and model? on some it can be done, on others not?
although i tought it could be done on all of them
Click to expand...
Click to collapse
Code:
adb uninstall
internally runs
Code:
pm uninstall
So
Code:
adb uninstall --user 0 com.android.service
internally runs
Code:
pm uninstall --user 0 com.android.service
Bloatware housed in /system/priv-app obviously can get tracelessly removed, but surely not all that what is located in /system because essential apps in /system have FLAG_SYSTEM set. I'm pretty sure those apps can't get removed without root rights. But as always: I may err.
jwoegerbauer said:
Bloatware housed in /system/priv-app obviously can get tracelessly removed, but surely not all that what is located in /system because essential apps in /system have FLAG_SYSTEM set. I'm pretty sure those apps can't get removed without root rights. But as always: I may err.
Click to expand...
Click to collapse
well now i am really curious about this, is there some adb command to check? or an app? to verify if they are really gone?
i know for sure the unbloated uses 0.3 less ram and about 2gb less storage space
thanks
jwoegerbauer said:
Bloatware housed in /system/priv-app obviously can get tracelessly removed, but surely not all that what is located in /system because essential apps in /system have FLAG_SYSTEM set. I'm pretty sure those apps can't get removed without root rights. But as always: I may err.
Click to expand...
Click to collapse
well now i am really curious about this, is there some adb command to check? or an app? to verify if they are really gone?
i know for sure the unbloated uses 0.3 less ram and about 2gb less storage space
thanks
You use Android's package manager (pm) tool to perform actions and queries on app packages installed on the device.
Synthax:
Code:
adb shell "pm list packages [options] filter"
agonoize said:
well now i am really curious about this, is there some adb command to check? or an app? to verify if they are really gone?
Click to expand...
Click to collapse
Nothing will go away really. Root access is needed if making changes into the system. They are just hiding from the current user.
agonoize said:
greenify faitly useless...
battery drain also depends a lot on the device, some processors are more power hungry (even in idle) then others,
but some things help:
use 50% or less brightness, limit backgroud apps to 1 or 2 maximum, enable the adaptive battery mode
put all less frequent apps into sleep mode
debloat your device - and not only crap apps, use as little aps as you can
search for battery draining apps on your device that can be disabled or removed, for example the samsung "AASAservice"
and snapchat, tinder and other dating apps, any news app, facebook, streaming apps, microsoft apps etc. Use the website instead of the app whenever possible (this also fights telemetry)
widgets help draining battery, avoid using them as much as you can
disable bluetooth when you dont need it
and avoid getting your mobile phone hot - like leaving it on a cars dashboard, a place with direct sunlight, high temperature stresses the device, and drains more battery
cheers
Click to expand...
Click to collapse
Oh when you say "limit background apps to 1 or 2" what does it means and how would i do it?
ZodiacFam said:
Oh when you say "limit background apps to 1 or 2" what does it means and how would i do it?
Click to expand...
Click to collapse
You can do that in Developer Options. Or simple close apps out when done with them.
Some apps may refuse to do so and run in the background instead, connecting with the internet a few times a minute. Brave browser does this sometimes and force stopping it is the only thing that works. Swell.
blackhawk said:
Turn off all power management except screen/ power mode, set to optimize.
Android can manage it's self fine.
Clear Google Play Services clear its data as needed.
It can be disabled with a package blocker but is needed for gmail, Playstore; enable as needed.
Disable Google Backup Transport and Framework, clear their data as needed.
Disable all cloud stuff, carrier, Samsung, Google feedback.
Karma Firewall can be used to block the above system apks and reduce battery usage.
Click to expand...
Click to collapse
By carrier you mean carrier services? What is its function?