I don't know if this had been mentioned before on another thread, but it seems that aggressive doze on Beta 2 causes my system clock to lag behind the actual time (it will display the correct time in Google's clock app). A few other users of my ROM, PureNexus for the Nexus 6p, have reported the same issue.
As suggested by another user, I de-optomized the Clock app in battery settings and rolled back to Beta 1. All is well but the problem appears again if I update to Beta 2. Does anyone have any experience with this or know a workaround for 2.8 Beta 2? Thanks!
Same here
also having the same issue on Beta 2, I've downgraded to Beta 1 for the time being. If you toggle airplane mode it forces a re-sync of the clock
i'm having the same problem here i'm on cataclysm MM beta and greenify beta 2...i've just diseabled aggresive doze and it looks like it has solved the problem but i've to test for a longer time
I had the same problem, trying to remember what I did to fix it
I updated to Beta 3 and this issue is still present. @oasisfeng, do you know why the clock "freezes" while the screen is on? Doze only functions when the screen is off, correct?
Ahh, this was happening to me but I didn't connect the dots to Greenify. The other day I was lying in bed on my phone thinking I still had plenty of time before I had to get up and go to work... oops.
marbertshere said:
I updated to Beta 3 and this issue is still present. @oasisfeng, do you know why the clock "freezes" while the screen is on? Doze only functions when the screen is off, correct?
Click to expand...
Click to collapse
This issue should have been fixed in beta 7. Could you confirm that?
oasisfeng said:
This issue should have been fixed in beta 7. Could you confirm that?
Click to expand...
Click to collapse
It is, atleast for me. Thank you.
Related
This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
v2.95 beta 3
Aggressive Doze now works in non-root mode on Android 7. (Manual privilege granting via USB required)
Improved GCM Wake-up (Xposed) for some misbehaving apps. (e.g. WeChat)
Improved the stability of accessibility service.
Fixed Wake-up Cut-off on Android 6+.
Fixed Shallow Hibernation (Android 6+) in boost mode (Xposed).
Fixed alarm analysis on Android 6+.
Fixed the false "Root privilege not granted" notification.
Fixed the verification failure in a short time after donation package is installed.
v2.95 beta 2
Wake-up cut-off now works on Android 7.0 (root).
Improved the overall stability and smoothness of non-root auto-hibernation.
v2.95 beta 1
Auto-hibernation in non-root mode is now compatible with secured key-guard. No more compromise for device security!
Screen-off by Greenify no longer invalidates fingerprint unlock and Smart Lock. Be sure to enable "Alternative Screen Off" in settings.
Aggressive Doze and doze notification is now compatible with Android 7.0 in root and boost mode. (support for non-root mode on the way)
Tasker plug-ins for toggling Auto-Hibernation and Aggressive Doze.
Improved app state detection on Android 6.0+.
Click to expand...
Click to collapse
Known issues
Doze on the Go is not yet compatible with Android 7.0 in non-root mode. We are seeking for a proper solution.
Get beta versions
Opt-in to beta channel or download the apk file.
oasisfeng said:
This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
Known issues
None.
Get beta versions
Opt-in to beta channel or download the apk file.
Click to expand...
Click to collapse
Works on my Nexus 6! awesome stuff!
italia0101 said:
Tried the aggressive doze on my Nexus 6 ,,
Had it plugged into my PC with a logcat running . i used the " battery unplug " command .
I can see it go into Doze on screen off . a new notification says " entered doze mode" , but with a bit of shaking a movement it wakes up , so on the Nexus 6 at least it still gets awoken with motion
Click to expand...
Click to collapse
Have you granted the DUMP permission manually?
oasisfeng said:
Have you granted the DUMP permission manually?
Click to expand...
Click to collapse
No i have root, but with your suggestion from the other thread it seems to work! so thanks for that, i've edited my post above
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
naudmick said:
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
Click to expand...
Click to collapse
Sorry, I messed up with Android 4.x & 5.x in beta 1, a fix is pushing out.
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Pupet_Master said:
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
Click to expand...
Click to collapse
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
oasisfeng said:
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
Click to expand...
Click to collapse
Thanks, i can't wait for it
draggehn said:
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Click to expand...
Click to collapse
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
oasisfeng said:
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
Click to expand...
Click to collapse
Disabling aggressive doze right now, I'll report back.
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
arunkafley said:
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
Click to expand...
Click to collapse
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
lusto170859 said:
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
Click to expand...
Click to collapse
It's usually inaccurate for the first a few percentages from 100% downwards.
I'm going to prepare for and celebrate the Chinese New Year in the following two weeks. The next beta release is probably not going to be released soon.
I'll check and reply to posts here occasionally during the holiday.
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
even if i have root ?
thanks for the hard work
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
Yeah I did that. But before without granting the DUMP permission it was working fine
oasisfeng said:
It's usually inaccurate for the first a few percentages from 100% downwards.
Click to expand...
Click to collapse
Yes I know. But without Aggressive Doze I lost 12% in this period. Normal Doze does not work with my device. (Samsung Galaxy S2plus CM13)
I'm using greenify on my Galaxy tab s2 and also on my note 4. No problems at all on my s2 but when I push the sleep button to hibernate my apps it puts the apps to sleep but after that my home and recent apps do nothing. They'll beep to acknowledge being touched but they no longer show the fan of open apps or return me to the home screen.
I cannot get the buttons to work unless I go to accessibility and turn off hibernate automation and then reboot.
Very frustrating. Can anyone help me with this? Any thoughts?
Tesgin
Similar issue just happened with my Note 4. Moved to Marshmallow last September. Battery would run down much faster then Lollipop, so installed Greenify. Everything was fine until installation of AT&T update to kernal version dated 1/2/17. Home and recent apps keys would stop working shortly after restarting the phone. Updating again to latest kernal version dated 2/15/17 and clearing cache data on all apps didn’t help. Rebooting in safe mode made the issue go away, so it pointed to an app I downloaded. It was only then I remembered that I had turned on setting Aggressive Doze (experimental) when setting up Greenify. Disabling Agressive Doze fixed my issues.
Davemp40 said:
Similar issue just happened with my Note 4. Moved to Marshmallow last September. Battery would run down much faster then Lollipop, so installed Greenify. Everything was fine until installation of AT&T update to kernal version dated 1/2/17. Home and recent apps keys would stop working shortly after restarting the phone. Updating again to latest kernal version dated 2/15/17 and clearing cache data on all apps didn’t help. Rebooting in safe mode made the issue go away, so it pointed to an app I downloaded. It was only then I remembered that I had turned on setting Aggressive Doze (experimental) when setting up Greenify. Disabling Agressive Doze fixed my issues.
Click to expand...
Click to collapse
Yep - this is a potential side effect of Aggressive Doze which is why it's labeled "experimental". Gains associated with AG are minimal; I simply avoid it. Rogue app wakeups can be handled via advanced tracking and cutoff options if using the donate version w/Xposed.
Aggressive Doze is off. Home and recent keys (and slide key panel) still don't work on my android 6.0.1 Galaxy Note 4.
Interesting that this problem is affecting just Samsung Note 4s based on the posts so far. I'm not seeing it in my 6.0.1 phones.
SqueakyDog said:
Aggressive Doze is off. Home and recent keys (and slide key panel) still don't work on my android 6.0.1 Galaxy Note 4.
Click to expand...
Click to collapse
divineBliss said:
Interesting that this problem is affecting just Samsung Note 4s based on the posts so far. I'm not seeing it in my 6.0.1 phones.
Click to expand...
Click to collapse
Possibly related: https://forum.xda-developers.com/apps/greenify/long-press-action-navbar-doesnt-anymore-t3605238
Hey !
I just received a new update on my Mi 9, version 11.0.8.0
The update changelog only mention the January Security Patch
Region : France / EEA
Edit 1 : Camera app no longer FC when entering pro mode in certain languages
System
Updated Android Security Patch to January 2020. Increased system security.
Status bar, Notification shade
Fix: Couldn't open notification settings in the Notification shade in Second space
Fix: Couldn't open the Notification shade in some cases
Other
Fix: Images overlapped in scrolling screenshots
Wysłane z mojego MI 9 przy użyciu Tapatalka
Dou you also feel like the scrolling on Chrome changed?
Gokh said:
Dou you also feel like the scrolling on Chrome changed?
Click to expand...
Click to collapse
I use Chrome and I have just as smooth scrolls now with this update as before.
---------- Post added at 07:14 AM ---------- Previous post was at 07:06 AM ----------
_Nexus8_ said:
Hey !
I just received a new update on my Mi 9, version 11.0.8.0
The update changelog only mention the January Security Patch
Region : France / EEA
Edit 1 : Camera app no longer FC when entering pro mode in certain languages
Click to expand...
Click to collapse
The ones that didn't catch the 11.0.7.0 update, and that was a lot of users, have a longer change log.
And they still didn't solved Mi Sound Enhancer and Bluetooth peripherals collaboration albeit big part of population have exactly those peripherals!
January ?? It's a joke ?
Why they don't have the security update of february.... ?
quadeur06 said:
January ?? It's a joke ?
Why they don't have the security update of february.... ?
Click to expand...
Click to collapse
If you just look a little bit further than your nose you might understand the reasons for delay.
I was not expecting an update this soon since many has to stay at home in China.
I updated yesterday and for some reason my stock wallpaper (the one with the mountain) used to be dynamic and change throughout the day (sunrise, sunset, night, etc) and now it's fixed on the night time, if I disable dark mode the wallpaper goes back to being daytime. So it's pretty much a static wallpaper instead of a dynamic one, is there a way to re-activate the dynamic one?
Pires96 said:
I updated yesterday and for some reason my stock wallpaper (the one with the mountain) used to be dynamic and change throughout the day (sunrise, sunset, night, etc) and now it's fixed on the night time, if I disable dark mode the wallpaper goes back to being daytime. So it's pretty much a static wallpaper instead of a dynamic one, is there a way to re-activate the dynamic one?
Click to expand...
Click to collapse
I believe that factory reset will solve Your problems, unfortunately.
Jehonan said:
I believe that factory reset will solve Your problems, unfortunately.
Click to expand...
Click to collapse
Just did that, at first it seemed to be working fine but after setting up the phone at some point I disabled dark mode and enabled again it went back to the same thing.
Pires96 said:
Just did that, at first it seemed to be working fine but after setting up the phone at some point I disabled dark mode and enabled again it went back to the same thing.
Click to expand...
Click to collapse
Did You look at \Settings > Account & Sync > Xiaomi Cloud > Home screen backup ?!
If not, then "old" and "broken" Home screen is always restored so my advice will be to delete those backups and then try again and see will You have any issue with this!
Jehonan said:
Did You look at \Settings > Account & Sync > Xiaomi Cloud > Home screen backup ?!
If not, then "old" and "broken" Home screen is always restored so my advice will be to delete those backups and then try again and see will You have any issue with this!
Click to expand...
Click to collapse
I'm pretty sure I had no backup because I had to setup everything from scratch again, google did restore apps, contacts and such, but home screen, system settings and such I had to do from scratch.
Pires96 said:
I'm pretty sure I had no backup because I had to setup everything from scratch again, google did restore apps, contacts and such, but home screen, system settings and such I had to do from scratch.
Click to expand...
Click to collapse
In Your place I would check this more closely because if I remember correctly this restore behavior is set as"default" for "Home screen" and this item is constantly restored during ROM upgrade or reset.
Just checked, it's disabled. Right now if I disable dark mode the background stays at night time (its almost 8pm so that's normal) i'm going to check tomorrow to see if the problem persists.
Pires96 said:
Just checked, it's disabled. Right now if I disable dark mode the background stays at night time (its almost 8pm so that's normal) i'm going to check tomorrow to see if the problem persists.
Click to expand...
Click to collapse
OK
Do you have the download link please?
boubougaming said:
Do you have the download link please?
Click to expand...
Click to collapse
Try this!
[QUOTE=Jehonan;81935811]Try this![/QUOTE]
Thank you.
Just checked the issue with the wallpaper, if I disable dark mode the wallpaper works just fine and cycles throughout the day as it should, as soon as I enable the dark mode it forces the wallpaper into night mode. Happened with this update, factory reset didn't fix it and I tried to look for an option but couldn't find anything. Extremely annoying but hopefully it gets fixed.
Pires96 said:
Just checked the issue with the wallpaper, if I disable dark mode the wallpaper works just fine and cycles throughout the day as it should, as soon as I enable the dark mode it forces the wallpaper into night mode. Happened with this update, factory reset didn't fix it and I tried to look for an option but couldn't find anything. Extremely annoying but hopefully it gets fixed.
Click to expand...
Click to collapse
Hmm maybe this is logical and intended behavior?!
If You look more closely if one activate dark mode then whole OS "thinks" that You are actually using Your phone during night time and You have exactly this kind of behavior!
I believe that there lies Your "problem" and in fact You don't have problem at all and this function works like it should i believe!
Do you guys experience same thing? Most of the time it shows normal lockscreen, but sometimes it's showing an AOD look (I have AOD off). would prefer to use this second look tbh.
same problem for me, hope this will be fixed in next update
Having the same issue here. Glad I'm not the only user with this problem. Try writing a descriptive report to Google and send them some feedback so they can hopefully fix it.
just applied december update and the bug is still here
azerty11 said:
just applied december update and the bug is still here
Click to expand...
Click to collapse
Same here. Maybe next time.
Yeah,, it has not been fixed
Fix: Pixel 6 Screen randomly wakes up even if AOD is Disabled
In this guide, we will show you the detailed steps to fix the issue Pixel 6 screen randomly waking up even if AOD is disabled.
www.droidwin.com
That fixes it for me.
HSD-Pilot said:
Fix: Pixel 6 Screen randomly wakes up even if AOD is Disabled
In this guide, we will show you the detailed steps to fix the issue Pixel 6 screen randomly waking up even if AOD is disabled.
www.droidwin.com
That fixes it for me.
Click to expand...
Click to collapse
Ah so it's a feature for/of the fingerprint reader, rather than a bug!?
HSD-Pilot said:
Fix: Pixel 6 Screen randomly wakes up even if AOD is Disabled
In this guide, we will show you the detailed steps to fix the issue Pixel 6 screen randomly waking up even if AOD is disabled.
www.droidwin.com
That fixes it for me.
Click to expand...
Click to collapse
Looks like it is working for me too. Thanks so much. I hate this bug.
Some background app or server update overnight seems to have fixed this...
WibblyW said:
Some background app or server update overnight seems to have fixed this...
Click to expand...
Click to collapse
Spoke too soon
WibblyW said:
Spoke too soon
Click to expand...
Click to collapse
I used to have this annoyance, but de ADB method pointed earlier solved it for me.
cyberdionisio said:
I used to have this annoyance, but de ADB method pointed earlier solved it for me.
Click to expand...
Click to collapse
I'm so grateful for this ADB method. This is such an annoying bug. Thanks @HSD-Pilot for sharing this solution.
Has anyone found an ADB method for forcing the lockscreen clock to stay small? I use a persistent weather notification to keep the clock small, but I'd love to find a permanent fix for this. I really hate the big clock.
The April 2022 update includes bug fixes and improvements for Pixel users – see below for details.
Battery & Power
Additional improvements for wireless charging performance with certain accessories *[2].
Camera
Fix for issue causing front-facing camera preview in certain apps to appear zoomed in *[2].
Fix for issue occasionally causing green screen to appear in camera preview *[2].
User Interface
Fix for crash in System UI while using apps in Picture-in-Picture (PIP) mode in certain conditions *[1].
Fix for issue causing error message to display when setting up certain live wallpapers *[1].
Fix for issue causing notification shade and Quick Settings to appear invisible after changing wallpaper in certain conditions *[1].
Fix for issue occasionally causing animation to display incorrectly when canceling a search in the app drawer *[1].
Fix for issue occasionally preventing navigation in overview screen while TalkBack is active *[1].
Fix for issue occasionally preventing recents button to show the overview while using 3-button navigation with third party launchers *[1].
---------------------------------------------------------------
Device Applicability
*[1] Included on Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a (5G), Pixel 6 & Pixel 6 Pro
*[2] Included on Pixel 6 & Pixel 6 Pro
ill be waiting to see if this adds bugs as it fixes nothing serious thati can see. and no mention of The Dirty Pipe Vulnerability which i really hope is fixed.
It's still kernel 5.10.66, so looks like no dirty pipe fix yet
poit said:
It's still kernel 5.10.66, so looks like no dirty pipe fix yet
Click to expand...
Click to collapse
flagship phone with monthly updates and a seriously vulnerability not fixed for 2 months? WTF google?
I can confirm that the exploit still works on the April update (with the -f flag).
capntrips said:
I can confirm that the exploit still works on the April update (with the -f flag).
Click to expand...
Click to collapse
Astounding. So the way to avoid it is to not install any apps you don't get from the play store, or they say don't install any apps at all. Are they kidding?
beware that all hackers are looking for how to compromise your phone and your super important information such as your memes, your photos of your pet, etc.
You forgot my bank account and angry birds data.
Same sentiment. I know tons of people who do banking on their phones.
hypermetuljason said:
Same sentiment. I know tons of people who do banking on their phones.
Click to expand...
Click to collapse
And who wants others to have email access, authentication app, text messages etc. It's absurd that this is not fixed zero day.
you can flash blu spark kernel. it has the dirty pipe vulnerability patched.
Is it just me or some one else also has the issue with swipe up to see recent apps? Sometimes when i swipe up system glitches and app doesn't get minimized. I have to wait few seconds before trying again.
This issue has been present since March update.
paratox said:
you can flash blu spark kernel. it has the dirty pipe vulnerability patched.
Click to expand...
Click to collapse
You mean unlock the bootloader, wipe the device, root, install a kernel, then figure out how to get my banking app working, hope that Gpay works and... No thanks. That's really not the right answer for those with a locked bootloader. The answer is to have the patch rolled out to users in a timely manner. But thanks for the info.
Bug: my always on is missing
djsonicdh said:
beware that all hackers are looking for how to compromise your phone and your super important information such as your memes, your photos of your pet, etc.
Click to expand...
Click to collapse
**** me man...last thing I want is the hacker to steal my hairy ass picture...DAMN IT
bige93 said:
Is it just me or some one else also has the issue with swipe up to see recent apps? Sometimes when i swipe up system glitches and app doesn't get minimized. I have to wait few seconds before trying again.
This issue has been present since March update.
Click to expand...
Click to collapse
I have the same. I tought it was because of my custom launcher hmm
rolarocka said:
I have the same. I tought it was because of my custom launcher hmm
Click to expand...
Click to collapse
I was about to go with the factory reset because of that, but since you also report that then I'll just wait for May update with my fingers crossed.
I also get another recents bug while using 3-buttons navigation: whenever I open a new app from the launcher and I hit recents button, recents are focused on the previously active app, not the one I just opened. Frustrating
bige93 said:
Is it just me or some one else also has the issue with swipe up to see recent apps? Sometimes when i swipe up system glitches and app doesn't get minimized. I have to wait few seconds before trying again.
This issue has been present since March update.
Click to expand...
Click to collapse
I might have fixed it by accident:
I`ve disabled first two types of animations in the dev options and left the last one at x1.
Didn`t have this bug for couple of hours now even after turning those animations on later.
Could you check this at your end?
Edit: I take that back. It was fine for around 12h and then it's glitching again. Now, for me, there's no system navigation method without any glitch after March update. Job well done ...
The pixel stand 2 stops telling me to reposition for better charging with my case on so that's better, the camera still randomly crashes the phone though. I factory reset my phone after the April update in the hope the crashing would stop.
GoNz0 said:
The pixel stand 2 stops telling me to reposition for better charging with my case on so that's better, the camera still randomly crashes the phone though. I factory reset my phone after the April update in the hope the crashing would stop.
Click to expand...
Click to collapse
In my case Gcam was crashing after the March update. There were also new screen problems that included disappearing nav buttons and the fingerprint sensor went from lousy to horrible. After a clean start (rather than factory reset I flashed the March factory image) it's all back to normal and the fingerprint sensor has been working better than it ever did before. The April update has been stable.