Related
Ok I dont know if anyone else has this problem but its really annoying.
I just unlocked and rooted my Nexus 7 yesterday. My problem is that my Wifi sleep policy isnt honored. I like keeping it on "Always" so I recieve notifications and such. No matter what I try doing the wifi always turns off when the device is in sleep (Device is locked and screen is off). Ive tried countless Wifi keep alive apps and wifi fixers but nothing seems to work. Its terribly annoying and I hope someone can help. Also just out of coincedence I put my nexus 7 into safe mode and this problem didnt arise.
Plllllllllllllllllleeeeeeeeaaaaaassssssseeeeeee help me I'd greatly appreciate it.
Thanks :laugh:
Do you have 'battery saver' apps installed?
settings->wifi->uncheck optimize wifi, check always keep wifi on (or something like that)
or
theres an option in trickster mod app from google play store that also forces the wifi to stay on when the device is asleep.
not sure if these options are one in the same but hey worth a try i guess
Yes battery saver apps might creating problem,it happened with me,so I removed them.
Sent from my Nexus 7 using xda premium
THANKS!
Thanks you guys for the help! I appreciate it. I feel so dumb I should have known it was the battery saver app XD Yall are awesome!
Hi all,
EDIT2: MAIN PROBLEM FIXED!
I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.
I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.
Lo and behold, I rebooted three times now and NO KNOCK LOOP!
I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.
As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?
EDIT: Not Greenify causing this, but some other combo of rooting and system file changes. Could also be the proximity sensor misbehaving or just a bad copy of the phone.
Just a friendly PSA, but Greenify (the popular hibernation app that is really awesome) will gimp your knock-on feature for good. As in: returning to stock does not fix it. Myself and at least one other user have had this problem. I'm now having to swap out my phone after just getting it how I like it, which is infuriating.
I'd rather wait until somebody gets a fix up, but I'm within 14-days so I'm not risking it.
Note: This is CLEARLY not the fault of Greenify. It's some bizarre file system/sensor error. Greenify is great.
Related thread where the problem was thought to be fixed... but is not for people who installed Greenify.
I'm using the Verizon variant, so I don't know if this applies to GSM models.
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
I've been using greenify since the day after I got the phone and rooted it, so 2 weeks now, and knock on works perfectly every single time.
Sent from my VS980 4G using Tapatalk 4
---------- Post added at 12:14 PM ---------- Previous post was at 12:14 PM ----------
and I'm on the Verizon version. what app are you guys hibernating that's causing this?
Sent from my VS980 4G using Tapatalk 4
burningembers said:
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
Click to expand...
Click to collapse
I'd have to agree with this!!
Sent from my GT-N7100 using xda app-developers app
Knock on seems to work on mine (most of the time anyway) while using Greenify for a couple of weeks now. If it was going to gimp it, I'm thinking it would have by now. I have the T-Mobile variant. Its basically just hibernating apps from the market, not any system apps so I guess I don't see the correlation.
Greenify works for me
I'm stock rooted and I heavily use Greenify with my Verizon G2. No problems with Knock On at all!
Edit: Stock rooted (not the chinese way), no OTA, auto-hibernation feature works perfectly too.
um question... did you guys who have the problem use the Chinese root method? someone brought it up and now I'm curious....
i did but then flashed back to stock to reroot the good way. you guys who aren't having the issue with me, you use Chinese or regular?
Sent from my VS980 4G using Tapatalk 4
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Sent from my VS980 4G using XDA Premium 4 mobile app
lattiboy said:
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Click to expand...
Click to collapse
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
burningembers said:
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
Click to expand...
Click to collapse
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
You should really rename this thread. I have not experienced any knock issues and I've installed this app since I bought the phone. False psa
---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------
lattiboy said:
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
Click to expand...
Click to collapse
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
SysAdmNj said:
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
Click to expand...
Click to collapse
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?
The issue might be caused by misuse of Greenify. Have you greenified any system apps related to the Knock-on feature?
Greenify should never "damage" your device in a non-recoverable way since it never touches any system files. Just simply de-greenify the app and manually relaunch it once to restore everything to normal.
Hope one of you G2 users could find out that key greenified app which caused this terrible issue, thus we could warn others in a more effective way.
lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
burningembers said:
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
Click to expand...
Click to collapse
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
lattiboy said:
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
Click to expand...
Click to collapse
So flashing back to pre-OTA doesn't clear the problem at all?
burningembers said:
So flashing back to pre-OTA doesn't clear the problem at all?
Click to expand...
Click to collapse
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
lattiboy said:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
Click to expand...
Click to collapse
What's your Baseband and Kernel version in Software Information?
I know for a *fact* that the OTA changed the cpu scheduler. What I'm curious is if their scheduler changes have somehow caused service-level applications like the KnockOn APK to die/hibernate during a lengthy deep sleep. This makes way more sense to me than merely using Greenify causing a permanent breaking of software/kernel interactions.
burningembers said:
What's your Baseband and Kernel version in Software Information?.
Click to expand...
Click to collapse
This is it. No root, fresh stock 15 minutes ago.
Hi all,
for the last few days I keep having random reboots with my N10, as well as random lock-ups.
Started a few days after the 4.4.3 OTA update.
happens like this:
I'm trying to wake up my tablet with the power button but nothing happens so I have to reboot.
Or, I am just normally using my tablet ant it spontaneously reboots, without warning, and also without any kind of lockup before that.
What is really annoying is that after such a reboot the tablet is not actually usable: none of the normal autostart apps initialize properly;
flipboard doesnt refresh, calendar widget does not show any entries, mail widget does not show anything, etc etc etc.
I'm on stock 4.4.3, but rooted with SuperSU.
it did not start right after the 4.4.3 OTA, only a few days later (actually, i think on friday or saturday).
Is there a way to get into the system logs to see what is up?
...turn on auditing, maybe?
Any other suggestions that might help me? What kind of details do you need?
Hi,
It looks like someone got a possible solution. I didn't test because I don't face random reboots on my Nexus.
http://forum.xda-developers.com/showthread.php?t=2741084
~Lord
XxLordxX said:
Hi,
It looks like someone got a possible solution. I didn't test because I don't face random reboots on my Nexus.
http://forum.xda-developers.com/showthread.php?t=2741084
~Lord
Click to expand...
Click to collapse
...I'm not quite sure what I am supposed to do with that app... So I've installed it, and now?
[Lemmy] said:
...I'm not quite sure what I am supposed to do with that app... So I've installed it, and now?
Click to expand...
Click to collapse
Hi,
It looks like the person in the other thread set it to always display on notification bar, nothing other than that... As I said I didn't test so I can't tell you how possible it is for working or anything, sorry. I just gave this solution for now, if it doesn't work then I'd have to think a bit further .
~Lord
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
I just got a new S7 edge 935f. I rooted it with magisk after installing twrp. I have tried a few Nougat stock roms and in all of them, my alarm clock fails to go off first thing in the morning. It will come on when I push the home button and for the rest of the day all alarms work fine. It is only the first morning alarm that fails.
I wonder if this is due to something wrong with the kernel, and if installing a custom kernel may fix this. Or is the a lib file that may be corrupt.
Anyone else experience this kind of problem? I read in a few articles and forums that it is linked possibly to a SOD (sleep of death) bug. Hoping some information can come from anyone else who knows of this.
Thanks in advance.
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
bobfrantic said:
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
Click to expand...
Click to collapse
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
jaimep01 said:
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
Click to expand...
Click to collapse
yes I have and all have same issue. For the first alarm I have to manually wake up the phone, all others work through the day.
Surely I am not the only one to have this trouble....
bobfrantic said:
Surely I am not the only one to have this trouble....
Click to expand...
Click to collapse
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
jaimep01 said:
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
Click to expand...
Click to collapse
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
bobfrantic said:
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
Click to expand...
Click to collapse
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
jaimep01 said:
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
Click to expand...
Click to collapse
No I haven't tried that. I have mine working now. It woke me up this morning. What did it is the app "SOD Killer" which is on google play. It increases battery useage a little but until I find out which file is keeping phone asleep, it's a small price imho.
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
yaibakt said:
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
Click to expand...
Click to collapse
I don't kill or freeze anything. Only thing I have to make alarm work is the SOD Killer app that keeps phone from going into deep sleep.
So a funny thing happened on the way back to Marshmallow 6.0.1 as I had just finished getting through setup and was about to start doing things on my phone, I got a notification that there was a firmware update downloading. It was taking me back to 7.0 and it upgraded my phone to the first version of Nougat for Luxembourg. Then a few minutes later another system update was downloading and I installed it and my phone now had the latest Nougat for Luxembourg. So first thing I checked was the alarm. I set one for 4 hours later, and it worked. I also tested an overnight alarm and it also worked. So now I have working alarms. Still going to downgrade back to 6.0.1 though, just feels better than Nougat to me.