Related
Hi, I am unable to change the Google+ app's notification sound. When I go into Google+ Settings -> My Account Settings -> Notifications -> Ringtone, I get the dropdown selector for the different sounds, but when I choose one and hit "OK", the dropdown closes and the setting doesn't change. I have no idea if this is a fault in the Google+ app itself or something else, like a failure with the dropdown menu system.
Has anyone else experienced something like this and/or can think of a fix?
My setup:
- Verizon Samsung Galaxy S4
- MI1 firmware, rooted with RDLV
- Using Safestrap and running Google Edition 4.2.2
- Using XPosed Framework with GravityBox, XBlast Tools, and XPrivacy
- XPrivacy is NOT restricting Google+ nor any Google apps or System apps at all
Thanks for any help!
Hope someone knows of a solution as this has been annoying me for a couple of weeks now. No matter what I do the notification tone will not change.
I have seen one other guy mention it on Google+ as well but nobody had a solution.
Same issue
mickeyjaydee said:
Hope someone knows of a solution as this has been annoying me for a couple of weeks now. No matter what I do the notification tone will not change.
I have seen one other guy mention it on Google+ as well but nobody had a solution.
Click to expand...
Click to collapse
I have the same issue. It is stuck on"Tethys". I previously had it set to "None" forever. This must have happened with the latest update to Google+, which it says was Nov 15th, but it seems like it started a few days ago. I was still on 4.4 when it started. Now I am at 4.4.2 and it is still happening.
The Google+ update I downloaded today fixed the issue.
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Same issue here
Hi there.
Unfortunately I don't have a solution but just wanted to let you know that I have exactly the same problem. My Sony Xperia Z2 updated to Lollipop last friday and since then I get this annoying "capaciteit voor NFC-services is vol" message (it's in Dutch ) When I click on 'change settings' a new window is opened where it is not possible to change any setting. Switched NFC on and off but doesn't seem to do anything. The message keeps popping up irregularly...
Very annoying issue. Hope someone finds a solution.
Exaclty the same issue here
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Unfortunately I am also haveing the same issue. It's very annoying.
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Try Factory Reset
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
dreamoo said:
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
Click to expand...
Click to collapse
Just got this problem myself this morning on my Z2 running Lollipop. Did you manage to find a fix?
I can't seem to find anything other than this post concerning this issue.
Thanks.
Same Problem
I did a factory restore and I am still getting the same issue.
Same here
I'm experiencing the same thing. Upgraded to Lollipop last month, but this only started a couple days ago. Not after installing a new app. Got low on disk space, which triggered a back up alert. Cleaned out my pics, but then started getting this error.
Xperzia Z3 Compact
Model D5803
Bell Mobility Canada
Android 5.0.2
Kernel version
3.4.0-perf-g72984dd
[email protected] #1
Fri Feb 27 18:06:32 2015
Build Number 23.1.A.0.726
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
I think I figured it out. Suggested a bunch of apps that had bee recently updated on reddit, and the common denominator was the Scotiabank app, updated a few days ago.
Uninstalled, no NFC errors. I have written the dev, and hope for a response soon. That seems to be the cause, so check it out and post if it works for you.
Solution: Clear Google Play Services and NFC Service Data in Safe Mode
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
thanx, worked for me as well. remainings of android pay caused the problem on my mobile.
Hi Guy !
Same problem here.
Unfortunately no Scotia Bank, noting...
And when i get this message, it says that is current capacity used is.... 0%!!!
I begin to hate this phone :s
Thanks if you have any tip.
Laurent
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
PuffDaddy_d said:
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
Click to expand...
Click to collapse
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Makiavell said:
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Click to expand...
Click to collapse
Yeah, I figured Google Play Services was the issue, but if I uninstall and roll back to the original version the phone ships with, it isn't compatible with Google apps (music, youtube, etc). I was just hoping there was a better fix. For now, I've simply disabled NFC and turn it on before I use Android Pay. The extra clicks aren't really a big deal since I don't have a fingerprint scanner and need to touch the screen to unlock anyway. Plus, I don't use AP often enough to bother me. Thanks for the confirmation though!
Edit - after further thought, if Google Play Services is the cause, then why aren't more people affected by this and why wasn't my device affected all along. I only recently rolled back to KK and this issue started. The Google Play Services version is still the same, right?
As an Android developer who is working on NFC payment in a mobile wallet, I can tell that our team identified the source of the problem to reside in Sony's Android modifications. No other platform produces these errors. I can't yet link the forum thread, but google for "sony xperia off host apdu service capacity full", the result from talk.sonymobile.com will show further details.
So you can probably stop looking for the cause in Google products, or 3rd party wallet/banking apps. They (we) also suffer from this issue.
Sony isn't responding in the referenced thread, so this may not be fixed soon.
Sorry to tell bad news.
my phone has this issue today, it began right AFTER i did a factory reset... just wanted to clear it off and start again... now this??
davidkeithhaines said:
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
Click to expand...
Click to collapse
The scary thing is this post was made 30-JAN-2016 and it's still being experienced.
Bought a Chinese Refurb Xperia Z3 Compact.
Android 4.4.4
Build 23.0.A.2.98
I'd only installed FTP Server Pro (to test 802.11ac bandwidth) by The Olive tree on an otherwise stock Z3C and after enabling NFC, the "NFC full" error message started popping up.
I followed the instructions above and managed to clear the cache/data on everything except one Twitter service which I couldn't stop.
After a reboot from safe mode, the phone is not showing the NFC error message.
I have enabled NFC and used it with a couple of NFC Bluetooth speakers and NFC tags around the house and it's working without errors.
Fingers cross, I won't see this message again.
Thnx
My Z3 Compact was running Android 5.0.2 since 2.5 years and I never encountered this pop-up. I never used NFC.
I changed to another mobile operator, and as soon as I replaced the SIM in my phone, I started getting this pop-up, saying that the space is 174% used.
I suspect the SIM being pre-configured for Orange Cash, although the application is not installed on my phone.
I tried the various workarounds mentioned in this thread and on Sony's forum, but none worked.
This phone is rooted, and I often get this pop-up when some "sudo" tasks are launched (kill process, freeze application, ...).
I have run out of ideas...
For those who still strugle with this shi* and clearing cache is not working:
1. Download and install any payment app, doesn't matter, won't use. I have Tap & go
2. Enable NFC
3. Go to Touch & pay in device section
4. Change from google play to installed app.
You can now disable NFC, no popup should occure
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?
Greetings,
I have an Infinix Note 3 Pro updated to Nougat and rooted. I'm not new to rooting and you can consider me a power user. I have many rules programmed via tasker and various tools that must be active at all times like everywhere launcher. As you know, Android as of Marshmallow introduced Doze, which is the most frustrating system I've ever come across. It's intended purpose mercilessly kills any background running task once the phone is idle. Yes there are supposed to be settings that can exempt certain apps, but it does not work. Additionally , the accessibility option also keeps going off for selected apps like tasker and everywhere launcher. IN fact all accessibility settings revert back to the off state after some time.You set it now, in a little while it's back to off. In short, apps like tasker, and sidebar launchers continue to disappear when Doze kicks end.
I've search the net for over a year and have tried every method I've found to solve this but the problems are persistent.
Can anyone please tell me how to solve this problem which has made my phone frustrate me for so long. I find it hard to believe that Android designed Doze to work the way it has worked against me.
Thanks for reading this long rant
iomari