I've either frozen or moved a number of apps out of the /system/app/ and /system/priv-app/ directories into a backup folder on the sd-card.
By doing this, is it possible that I've broken something and it's preventing the phone from entering deep sleep?
Although battery life still seems ok, Wake Lock Detector is showing 0.0 seconds in deep sleep. Basically the phone has been awake for the entire 3 hours since I removed it from the charger.
I thought it was the Facebook app to begin with at it had almost 600 wakeup triggers in around half a day. I removed it but still it doesn't enter deep sleep.
Has anyone got any tips/tricks for tracking down what could be causing this?
This is my first ever Note device so I'm not sure if this is normal behavior or not. I've been using Nexus devices for the past 4 years and never come across anything like this.
Maybe a old bug in Android System. Maybe a App or service hangs. Just restart your device. Sometimes this will happen . Many Android devices have this.
Gesendet von meinem SM-N910F mit Tapatalk
Related
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
Hey, for about one month i'm having this problem:
sometimes my screen goes on (I turn it on and then putt the phone down without locking it, or i'm getting a call and the phone screen turns on)
and never goes off, my timeout option is set to 30 seconds and the screen will stay on for hours if i won't turn it off manually.
A restart solves the problem but then after a while it comes back and stays until the next restart.
I tried greenfiying apps, tried reflashing (using Omega rom v35 on my i9509) and basically anything,
including wakelock detector and BetterBatteryStats but even after i leave the apps that shows in the top of the list the problem stays.
FYI i tried turning "Smart Stay" off, it doesn't help.
Does anyone has some solution?
Fullwiped your devise?
Gesendet von meinem GT-I9505 mit Tapatalk
I think I just found what's causing it to happen,
Tried force closing apps and wait to see if the time out is fixed and when I got
To the "Peek" app the time out was fixed.
There's a big chance it's that app for two reasons:
1. This app is basically about turning screen on and off and it has administration rights.
2. That app is one of the first apps I install after a wide and a fresh rom installation.
I'll update here of the problem comes back,
Meantime I sent an email to the developer of the app.
Hope I helped someone,
So am I the only one who has this lock screen clock "stuck" at a time time problem?
I am literally disgusted by this issue! It happened on the S4 I had, and I thought Samsung definitely has solved the problem but nah they didn't.
The problem is, the lock screen clock gets stuck at a time, and doesn't update with system time. No, it doesn't happen always, but it could happen at a time which could be really important, just like it happened today. I went to bed at 1 a.m, checked the phone when I temporarily woke up, the lock screen clock showed 3:44 a.m. I went back to sleep, suddenly I felt that there's a glimpse of sunlight on my windows, and checked the phone again, and it was actually 6:44 a.m.
Seriously speaking, I am fukcing tired of this problem. No I don't depend on the phone's lock screen clock, but the only time I check it is when I am in bed, sleeping, and that's when the problem has happened today.
Is there really no solution of this? Using a third party lock screen app or what?
Damn I am annoyed!
Maybe get a note 4?
pierrekid said:
Maybe get a note 4?
Click to expand...
Click to collapse
I am considering the Note 7 actually
:good:
I am using stock ROM and I never had this kind of problem.
devilsdouble said:
I am literally disgusted by this issue! It happened on the S4 I had, and I thought Samsung definitely has solved the problem but nah they didn't.
The problem is, the lock screen clock gets stuck at a time, and doesn't update with system time. No, it doesn't happen always, but it could happen at a time which could be really important, just like it happened today. I went to bed at 1 a.m, checked the phone when I temporarily woke up, the lock screen clock showed 3:44 a.m. I went back to sleep, suddenly I felt that there's a glimpse of sunlight on my windows, and checked the phone again, and it was actually 6:44 a.m.
Seriously speaking, I am fukcing tired of this problem. No I don't depend on the phone's lock screen clock, but the only time I check it is when I am in bed, sleeping, and that's when the problem has happened today.
Is there really no solution of this? Using a third party lock screen app or what?
Damn I am annoyed!
Click to expand...
Click to collapse
Most likely you have Greenify-ed something that you should have not.
This happens sometimes, yes. Annoyed me to no end on my S3.
Personally I use Zooper Widget as a lockscreen. (if you set multiple widgets and create a second widget page, you can delete the default lockscreen page by longpressing and dragging it to the bin at the top..) I've not seen Zooper have this bug
Sent from my SM-N9005 using Tapatalk 2
Check any battery save application that you might use. I had the same problem and it was due to an application that was saving battery. Sometimes this happens when i had the power saving mode too.
ShadowLea said:
This happens sometimes, yes. Annoyed me to no end on my S3.
Personally I use Zooper Widget as a lockscreen. (if you set multiple widgets and create a second widget page, you can delete the default lockscreen page by longpressing and dragging it to the bin at the top..) I've not seen Zooper have this bug
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
All right. Does this Zooper Widget support SMS pop up and missed call notifications like stock Samsung lock screen?
I have no idea how to use a widget as a lock screen anyway
tasked28m said:
Check any battery save application that you might use. I had the same problem and it was due to an application that was saving battery. Sometimes this happens when i had the power saving mode too.
Click to expand...
Click to collapse
I do NOT have any battery saving applications installed. If there's one thing I don't care about in mobile phones, that's battery life. So Greenify, and all those apps are not in my phone obviously.
Just updating the topic with a screenshot of the problem which I was talking about. Was lucky to snap the screenshot yesterday before going to bed, cause usually as soon as I press the home button to take the screenshot the time use to update.
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Japultra said:
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Click to expand...
Click to collapse
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
FiddleGoose said:
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
Click to expand...
Click to collapse
My S6 didn't do this though. I could go for a couple weeks without restarting it and it would still enter deep sleep.
I had a similar problem. For me it wasn't every three days, but usually 24-36 hours. But same issue, suddenly wouldn't go into deep sleep and a restart would fix it.
I found my issue to be gas buddy app and it trying to poll locations via bluetooth. Google it, there are lots of threads on it, but basically due to bad programming it would just jam on.
I figured this out as i could get my phone to go into deep sleep by turning off bluetooth, so that might be a quick easy test for you.
Also remember my in case (and unfortunately for a lot of other people) it was the gas buddy app. but others have reported the same issue with other apps.
i don't know if android's implementation on bluetooth location is busted, or the way the apps are using it.
On every rom based on lineage I have had pretty much constant awake time even thru the overnight hours and with greenify aggressive doze. I've tried just about all I can think of, I'll lose about 7 or 8 percent overnight where on stock it's around 3 percent
Is anyone else experiencing this? Is it common? Also the only thing to come up on wake lock detector is a Google service on wake up triggers
Any insight would be appreciated.
I don't know if it applies to all ROMs, but make sure you delete the systemapp for NFC. It's likely trying to communicate with your nonexistent NFC chip. I noticed my phone would never enter deep sleep, deleted it, and now it enters deep sleep seconds after shutting the screen off.
username8611 said:
I don't know if it applies to all ROMs, but make sure you delete the systemapp for NFC. It's likely trying to communicate with your nonexistent NFC chip. I noticed my phone would never enter deep sleep, deleted it, and now it enters deep sleep seconds after shutting the screen off.
Click to expand...
Click to collapse
I'm trying to locate it, found the around nfc app but it doesn't come up in titanium
I used Link2sd to unistall it. It's called NfcNci.apk. once i unistalled it, the phone went to sleep.
isTos said:
I used Link2sd to unistall it. It's called NfcNci.apk. once i unistalled it, the phone went to sleep.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
This def fixed my deep sleep issues. Thanks!
Here's a flashable zip you can use to remove NFC. I made it for use with ROMs that have a built in updater with a flash after update feature. This way ROM updates won't re-enable NFC. Tested it on AospExtended but should work on other ROMs as its designed to just remove the NFC apk from system.
Flash from recovery:
https://drive.google.com/file/d/0B3WSJXjA-ygYUjNoZ3F3c0VIWDg/view?usp=sharing
I did not create this zip but edited one that I found from here:
https://forums.oneplus.net/threads/flashable-zip-to-remove-apps.419810/