like others, i have experienced my first sleep of death.
running go launcher with a modified built.prop and rooted.
i did notice that it happened the one time when i left the amazon browser up and let it go to sleep ...
i have noticed some weird behavior from the amazon browser in general: often, it will reopen previously closed tabs when started up for the first time (eg after waking the kf)
There is already a thread about the 'sleep of death' like four down from this...
http://forum.xda-developers.com/showthread.php?t=1366794
jolars said:
There is already a thread about the 'sleep of death' like four down from this...
http://forum.xda-developers.com/showthread.php?t=1366794
Click to expand...
Click to collapse
Well, OP of the thread should change the title since it is not an accurate description ... SOD is.
brucestouder said:
It only happens to mine (rooted, adb, Go Launcher) when I put it to sleep while it is in "Go Launcher", if I put it to sleep from Kindle Launcher it wakes right up. Hope this helps.
Bruce
Click to expand...
Click to collapse
Similar but different scenario:
I have no problems with Go Launcher but if I leave the Amazon browser up, it went SOD on me.
installed twrp and did full wipe, flashed cm7 and i'm still getting SOD
Related
I've been getting "android.process.acore" messages for the last couple of weeks. It happens whenever I rotate the homescreen.
One thing I've read said it could be the widgets, but I've removed each one and am still having the issue.
Any ideas?
Vindolanda said:
I've been getting "android.process.acore" messages for the last couple of weeks. It happens whenever I rotate the homescreen.
One thing I've read said it could be the widgets, but I've removed each one and am still having the issue.
Any ideas?
Click to expand...
Click to collapse
I get that sometimes randomly, but I'm not sure what it means.
I'm just going to wipe everything and start from scratch. I'm getting it constantly now, and it's starting to be a real pain.
Vindolanda said:
I'm just going to wipe everything and start from scratch. I'm getting it constantly now, and it's starting to be a real pain.
Click to expand...
Click to collapse
I wiped it clean, went back to cyanogen, and added everything back.
It worked for awhile but came back. When it does it now, it takes me to the previous app I was in before going to the homescreen.
If it's the widgets (on ADW Launcher btw), I have:
NewsPro Reuters App
Advanced Task Killer
TM World Clock
Power Control
Icons w/ Desktop Visualizer
Oh dear, sadness is overtaking me! (sorta melodramatic but still very true)
Any help would be appreciated.
Vindolanda said:
I wiped it clean, went back to cyanogen, and added everything back.
It worked for awhile but came back. When it does it now, it takes me to the previous app I was in before going to the homescreen.
If it's the widgets (on ADW Launcher btw), I have:
NewsPro Reuters App
Advanced Task Killer
TM World Clock
Power Control
Icons w/ Desktop Visualizer
Oh dear, sadness is overtaking me! (sorta melodramatic but still very true)
Any help would be appreciated.
Click to expand...
Click to collapse
Rule them out...remove them all and add them back one at a time, over time, until you can reproduce the problem...that is, of course, assuming that you don't get the error when you don't have any widgets...
To solve the score force closes, first back up your contacts or make sure they are synced to Google. Next go to settings-> applications-> manage applications->all-> and select contacts storage. Once you have done this hit Force Stop, then clear data. Reboot and resync your contacts and you should be free of your issue. I had the same problem until I found an article ellaborating this process. Hope this helps.
Sent from my HTC Liberty using XDA App
Thanks for the responses.
I tried both the widget and contacts fix but it didn't work. Only when I updated to cyanogen RC2 (released today) has the error gone away. Weird.
Since the last update my Kindle had suffered an annoying bug that pop-ups intermittently a notification, changes to black the background picture of ADW Launcher, and avoids me to enter to Configuration by sliding the finger at the upper part of the screen. Fortunately it stops a minute if I reboot. Then it begins its cycles
The only cure I've found is to set off all the notifications of all the apps and reboot. Then again I can put back all notifications on until, after a few days, the error returns. It has happened to me four times.
The alleged offender appears to be the Dolphin browser, that now hangs every now and then, but as the error happens occasionally I have not been able to do more tests.
I think I found the cause of the bug. Immediately to the update I installed the Google environment, and it appears that Gmail app notifications are not very compatible with Kindle.
The solution has been to cancel them from within the program, which has a setting to prevent them.
gflorezarroyo said:
I think I found the cause of the bug. Immediately to the update I installed the Google environment, and it appears that Gmail app notifications are not very compatible with Kindle.
The solution has been to cancel them from within the program, which has a setting to prevent them.
Click to expand...
Click to collapse
marked.
may be helpful later.
Marked yes. Now, reading the "fixes" of Kinology, psych0phobia) says that:
"Fixed crash on Gmail notifications (this is an Amazon bug, not Google)"
gflorezarroyo said:
Marked yes. Now, reading the "fixes" of Kinology, psych0phobia) says that:
"Fixed crash on Gmail notifications (this is an Amazon bug, not Google)"
Click to expand...
Click to collapse
See also: http://forum.xda-developers.com/showthread.php?p=38600115
Hi,
I have a strange issue with my galaxy s4 i9505, lollipop. My clock get stuck when I lock my screen. And time does not update even when screen is unlocked i.e the clock starts from the same time when screen was locked. For example if I lock my screen at 10:00 am, and if after one hour I unlock the screen, the clock will start from 10:00 am instead of 11:00 am. I tried searching on the internet but I could not find any help regarding this. However there were discussion about the lag of one or two second about the time update when screen unlocks. Any ideas about this??
Factory reset, I guess.
GDReaper said:
Factory reset, I guess.
Click to expand...
Click to collapse
Factory reset didn't work
Bob_s4 said:
Factory reset didn't work
Click to expand...
Click to collapse
Do you have automatic date & time enabled?
I had something a little similar, but it included all my widgets. are you using go launcher or a go product like next3d launcher ? the problem persisted thru different firmwares and launcher updates. I had to go into the launcher and stop it so that it would restart itself. sorry that I don't have a solution, I never got to the bottom of the issue, it simply stopped happening at some point and I'm not even sure why...
GDReaper said:
Do you have automatic date & time enabled?
Click to expand...
Click to collapse
Yes, I tried both enabling and disabling it, issue stays as it is. Currently it is enabled. I have no clue what's wrong. It is so annoying
3mel said:
I had something a little similar, but it included all my widgets. are you using go launcher or a go product like next3d launcher ? the problem persisted thru different firmwares and launcher updates. I had to go into the launcher and stop it so that it would restart itself. sorry that I don't have a solution, I never got to the bottom of the issue, it simply stopped happening at some point and I'm not even sure why...
Click to expand...
Click to collapse
I am not using any go launcher or go product. All things/apps are default that come with lollipop.
It about stops me from doing uploading pictures, downloading. It's driving me crazy anyone else having this problem?
Yea lots of people are. Anything that changes the status of the screen like some kind of screen filter like twilight, night owl, any of those things, can mess with this. It's been pretty annoying. I have Twilight set to a timer to eliminate blue light on the screen before sleeping and I have to freeze and defrost it several times a day. Apparently it's an issue with ZTE. There is a thread over there about it.
presley07 said:
It about stops me from doing uploading pictures, downloading. It's driving me crazy anyone else having this problem?
Click to expand...
Click to collapse
I guess that it should actually be a security feature to prevent an overlay app from abusing any open apps below it... but it is really annoying that the ZTE integrated feature Mi-POP will also make this warnings display... you can simply deactivate it through its notification bar shortcut but it's still annoying...
Gachmuret said:
I guess that it should actually be a security feature to prevent an overlay app from abusing any open apps below it... but it is really annoying that the ZTE integrated feature Mi-POP will also make this warnings display... you can simply deactivate it through its notification bar shortcut but it's still annoying...
Click to expand...
Click to collapse
Well for now I am backup and running, I shot down the phone and restated posting ok
presley07 said:
Well for now I am backup and running, I shot down the phone and restated posting ok
Click to expand...
Click to collapse
I'm going to guess you have MiPop enabled? is so turn it off and your screen overlay issue might go away.
Gatorguy2 said:
I'm going to guess you have MiPop enabled? is so turn it off and your screen overlay issue might go away.
Click to expand...
Click to collapse
I an checked everything and it did no good, mipop and all else. Restarted phone and all was OK, hope this helps others with the same issue
presley07 said:
I an checked everything and it did no good, mipop and all else. Restarted phone and all was OK, hope this helps others with the same issue
Click to expand...
Click to collapse
Screen overlay is new in 6.0 to prevent apps from creating an overlay and giving permissions to themselves. It's not an issue with ZTE.
Yes screen overlay is new. Came from a N6 and never had this problem on stock 6.0 from Google. Facebook messenger will not do anything other than message can't call, or send pictures. Yes it is a problem with ZTE
Sent from my ZTE A2017U using Tapatalk
Go to the "Apps" setting, and then click on the "gear-shaped" setting button to go to the "Draw over other apps" menu and turn off all apps that are enabled. Go back to the "Apps" setting and click on the app that needs permissions modified. When all the permissions are updated, go back and enable the "Draw over other apps" for those apps you disabled.
Use this app it will get rid of that annoying overlay issue.
https://play.google.com/store/apps/details?id=jp.sfapps.installbuttonunlocker
Sometimes when I pick up my phone after it's been sitting at my desk neither the double tap to wake or the power button will wake my device. Anyone else experienced this?
(I did search for this to see if it was asked already but did not find a thread)
canemaxx said:
Sometimes when I pick up my phone after it's been sitting at my desk neither the double tap to wake or the power button will wake my device. Anyone else experienced this?
(I did search for this to see if it was asked already but did not find a thread)
Click to expand...
Click to collapse
Prefer single tap over double and disable deep optimization and sleep standby optimization in battery optimizations :good:
Funk Wizard said:
Prefer single tap over double and disable deep optimization and sleep standby optimization in battery optimizations :good:
Click to expand...
Click to collapse
Thank you ....will see how this works
https://forum.xda-developers.com/oneplus-6t/help/touch-to-doesnt-t3877245
https://forum.xda-developers.com/oneplus-6t/help/lock-screen-freezes-t3869001
Been having this issue since I got it. None of the updates have resolved it. 9.0.7 hasn't been as bad as 9.0.6 was, but it still happens at least once a day. Haven't updated to 9.0.10 yet. This is my only real gripe I have with this device so far.
I have mine set to tap once on screen to wake up. Sometimes I get this where I need to press power button to wake up.
borijess said:
I have mine set to tap once on screen to wake up. Sometimes I get this where I need to press power button to wake up.
Click to expand...
Click to collapse
Me to
I have checked with both single tap and double tap, both of them aren't perfect. Miss mostly when phone is idle for too long. Have to use power button in those cases.
I have had the same issue on both 9.0.7 and beta 1. Sometimes tapping the screen does nothing. The phone does not wake up and i have to got the power button (I have it set on single tap to wake).
I suspect it could have something to do with pocket mode.
I have the same problem. Disabling pocket mode did not resolve the problem.
canemaxx said:
Sometimes when I pick up my phone after it's been sitting at my desk neither the double tap to wake or the power button will wake my device. Anyone else experienced this?
(I did search for this to see if it was asked already but did not find a thread)
Click to expand...
Click to collapse
Using any launcher?
rob!n said:
Using any launcher?
Click to expand...
Click to collapse
Didn't think about that. In my case Nova Launcher, as usual.
Inciter said:
Didn't think about that. In my case Nova Launcher, as usual.
Click to expand...
Click to collapse
That's it then. I had the same issue from the start. Even replaced my unit for it. But its basically oos killing apps in order to save battery. And it kills our beloved nova too. It was solved for me after i root my device and grant nova root permissions. If u dont wanna root try using the default launcher for few days and see if the problem still persists.
rob!n said:
That's it then. I had the same issue from the start. Even replaced my unit for it. But its basically oos killing apps in order to save battery. And it kills our beloved nova too. It was solved for me after i root my device and grant nova root permissions. If u dont wanna root try using the default launcher for few days and see if the problem still persists.
Click to expand...
Click to collapse
Well, I thought about rooting but don't feel the need anymore. I'll try some other launchers and see what happens.
Inciter said:
Well, I thought about rooting but don't feel the need anymore. I'll try some other launchers and see what happens.
Click to expand...
Click to collapse
I guess only default launcher will work that's oneplus launcher. Other launcher might get killed as well. All the best.
rob!n said:
I guess only default launcher will work that's oneplus launcher. Other launcher might get killed as well. All the best.
Click to expand...
Click to collapse
This happens, in my case, with the default launcher from OnePlus.
I'm on full stock unrooted beta1, and had the same issue on 9.0.7.
Hasn't happened in a few days though.
joaste said:
This happens, in my case, with the default launcher from OnePlus.
I'm on full stock unrooted beta1, and had the same issue on 9.0.7.
Hasn't happened in a few days though.
Click to expand...
Click to collapse
I get this issue as well, same phone configuration, all stock, only an icon pack installed. For me fingerprint and faceunlock become unresponsive as well, and when it does wake it self, i have to type in an unlock.
rob!n said:
Using any launcher?
Click to expand...
Click to collapse
Just the stock launcher
rob!n said:
That's it then. I had the same issue from the start. Even replaced my unit for it. But its basically oos killing apps in order to save battery. And it kills our beloved nova too. It was solved for me after i root my device and grant nova root permissions. If u dont wanna root try using the default launcher for few days and see if the problem still persists.
Click to expand...
Click to collapse
Using Nova with root permissions doesn't fix this.
xgerryx said:
Using Nova with root permissions doesn't fix this.
Click to expand...
Click to collapse
I guess fixed for me. I havn't faced it since i rooted. And i have used nova from the start.
joaste said:
This happens, in my case, with the default launcher from OnePlus.
I'm on full stock unrooted beta1, and had the same issue on 9.0.7.
Hasn't happened in a few days though.
Click to expand...
Click to collapse
I must have jinxed-it. It just happened again...