What is Reddit's opinion of
Wake Lock - PowerManager?
From 3.5 billion Reddit comments
Popularity Score: 40
This app was mentioned in 53 comments, with an average of 5.13 upvotes
Best Comments
> My old Note4 reboots every time I try to use the camera when it's cold out.
Here you go, set it to Partial_wake_lock #4 and say goodbye to all your Note 4 problems:
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
See all those reviews? See how each and every one of them says "wtf why did this magically fix my note 4?" - we're still not really sure, but it does.
Hey, I had the same problem with my Note 4, I was eventually able to rescue it by taking the battery out for a while, pressing on the power button for about 10 secs to discharge it fully, waiting about half an hour and then putting the battery back in. Once it booted I installed the Wake Lock app, (if you look at the reviews for this app, you'll notice that they're almost all from grateful Note 4 users), put it on setting 4 ('partial wake lock') and it prevents the phone from randomly shutting off and refusing to boot as it did before. Hope this helps!
The reason why your phone is rebooting constantly is because it has trouble waking up the cores.
download the app "wake lock - power manager" and set it to partial wakelock.
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
This should stop your phone from rebooting. This works by keeping the cores on at all times at a very low state. The con of this is that your phone will no longer go into deep sleep, which means a decrease in battery life.
I had this issue for a few months before I finally got tired of it when my second battery gave up on me too.
Supposedly the issue is with the SOC when it goes into sleep mode, so you need to stop it from going into sleep mode to stop the lag and restart issues.
You will need to download Wake Lock and then choose option 4. You have to do this everytime the device is rebooted. Kind of a pain, but it works.
I admit it's been a while since I watched the video and I don't really feel like going through it all again, and everything you said does sound like it makes sense, but I thought the guy was pretty clear about identifying the eMMc chip. And also seemed to indicate it was pressure that was fixing it, that his note 4 turned on as long as he held a finger down on it.
Also, these Note 4 issues are not characteristic of overheating:
Putting it in the freezer is only necessary to turn it on. Once you have it on you can fire up a game and let it get to 40C without issue.
Turning on CPU partial wakelock fixes most of the issues for people, which if anything should increase CPU temperature, but certainly doesn't sound like it's related to it
The issues, aside from being able to power it on from cold, don't seem to correlate to temperature. You don't get more freezes or more failures with higher temperatures.
The phone itself pretty clearly states there's something wrong with the eMMc when it can't boot. "Could not do normal boot, MMC read fail". If it were CPU, GPU, or RAM issue, I would expect it to not display anything on the screen at all, I know my PC's BIOS sure as shit won't if any of those 3 fail. And I'm pretty sure the Note 4's SoC does not contain the flash MMC, and keeps that on a separate chip.
> My Note4 reboots randomly a couple times a week.. I'm not even actively using it at the time.
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
PARTIAL_WAKE_LOCK #4
Read the reviews.
Install Wake Lock by darken and use on Setting 4, PARTIAL_WAKE_LOCK.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
It'll use around 10% extra battery a day but will hopefully extend its useful life.
If you're in the US it's worth contacting Samsung and paying the $70 for a repair.
If you can get it to boot you could try installing Wake Lock and using setting 4, PARTIAL_WAKE_LOCK
https://play.google.com/store/apps/details?id=eu.thedarken.wl
If it is the mmc_read fail problem then you might get a temporary respite using that.
I had the same issues. I downloaded Wake Lock and set it to "partial wake lock" and that has fixed all the constant reboots. It's still a bit laggy but much better than before.
Yup. Just run this app:
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
You'll notice all the reviews are about it magically fixing the Note 4's freezing issues.
Select "PARTIAL_WAKE_LOCK"
And check "Autostart on boot"
Your battery life will be 5-10% shorter, enough that you don't want to do this if you don't have the issue, but not enough that it totally ruins the usability of the device.
RIP.
This is likely a common and well documented thing for note4 owners. Look up the EMMC failure bug. Some note4s are more affected and others arent. But it is very common. Looks like you are experiencing the early stages. There are some supposed "fixes" but they are mostly just workarounds. It may alleviate the issues short term, but it's only a matter of time till your phone dies completely. There is no pattern in the errors I have seen.. no change seems to have any effect. I will list a few, in no particular order. Do your own research. Source: OG note4 owner, owned 5 of them, 3/5 have had the emmc error.
factory reset the phone. temporary
use Wake Lock - PowerManager (level 4). best bet for mitigating symptoms
Use the brickbug app to check if you have a bad chip. I get false negatives on known-bad phones so ymmv
dont let the phone battery get low or the phone die completely. makes the issue worse
there was a post here a few weeks ago about a celophane bag + freezer fix. this allowed me to boot a previously bricked phone. no change on the lagging tho.
another post about inserting a small piece of foam behind the emmc chip itself to press the contacts firmly onto the pcb. this seems fucky. Id rather hit it with a hot air gun, but i digress.
Any other fixes anyone else has found? Thoughts?
Ok i had the same problem a few weeks ago after the tmobile update. Basically the note 4 is now "obsolete" because of an update. Download and install Wake Lock, and turn on Partial Wake Lock, this will prevent it from bootlooping. It's this one: https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en . If your battery ever drains completely, you will basically have a bricked phone (at least I did). I found a solution online from another person who said to put the phone in the freezer in a bag (remove the battery before doing this) for about 20 minutes, take it out, put the battery back in, charge the phone for a bit, and then turn it on and enable the wake lock app. It's a total disaster.
You have the mmc_read fail error. Install Wake Lock and use Setting 4, PARTIAL_WAKE_LOCK
https://play.google.com/store/apps/details?id=eu.thedarken.wl
It won't fix the problem but it might give you a few more weeks or months before total failure. It's hardware fault that requires a new motherboard. If you're in the US then you should be able to get it fixed by Samsung for around $70.
It's likely your phone struggling to either get a GPS signal or cell signal. My G5 Plus had the same thing happen when it was on Sprint. (Also had the phone get quite hot, like 100°+ normally and even hotter when charging) I would still submit it to Motorola, taking up 60% of the battery is not remotely normal.
EDIT: Use Wakelock and see exactly what the culprit is. Here's a link: https://play.google.com/store/apps/details?id=eu.thedarken.wl
EDIT: Yep, now I'm seeing it on my device. 15% so far.
The reason why your phone is rebooting constantly is because it has trouble waking up the cores.
download the app "wake lock - power manager" and set it to partial wakelock. https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
This should stop your phone from rebooting. This works by keeping the cores on at all times at a very low state. The con of this is that your phone will no longer go into deep sleep, which means a decrease in battery life.
I have the T-Mobile (SM-N910T) variant with similar issues; my occasional lag and random reboots started in late August.
Have you also experienced “mmc_read failed” or “kernel panic upload panic” errors where the phone won’t successfully boot? The common theory is that this is a symptom of a failing internal memory, meaning that it’s a hardware issue not a software issue (I’ve found reports of the issue on Lollipop and Marshmallow). If you’re still within the 1 year warranty, you can try to have Samsung replace your phone’s motherboard.
I’ve tried a factory reset on Marshmallow 6.0.1 and a new Anker battery, but like in your case, that did not solve the issue. Like you, I also noticed that the issues disappear when plugged into a charger. From what I’ve read online, the problems seems to occur when the phone attempts to “wake up” from a deep sleep mode. One of the suggested workarounds is to use the Wake Lock - PowerManager app. By enabling the PARTIAL_WAKE_LOCK setting, your CPU will always be partially running so that your phone never fully enters an idle mode. I actually just found this bandage solution earlier this week, and it’s stabilized my phone over the past 3-4 days (which I know isn’t long enough to determine anything conclusive). The downside is that since your phone never fully idles, your battery life will take a slight hit.
WakeLock: https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
I am now using Odin to re-flash the thingy. If i succeed and find a very good ROM, I will let you and future readers and Google searchers know.
Edit: I found a stock ROM that works perfectly for me. It didn't require much.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-n910f-stock-odexed-bloated-rom-v1-t3216390
1) CF root flash via odin
2) Recovery flash via odin (while flashing the recovery, when the progress bar starts moving instantly press and hold the recovery buttons) let the odin finish.
3) ROM goes into the SD
4) ROM flash via recovery ...complete
5) ...without booting up... back to download mode
6) odin flash bootloader and modem
7) let it boot. All your apps, passwords and settings are saved and phone ain't lagging no more.
Update:Tested it out for a day and the lag is back! Trying to go back to 5.1.1 today.
Update2: I won't downgrade. The wake lock (as suggested here in this thread by /u/orcaporca) helps a lot! It made all the difference! The stock ROM was a lot slower though and I don't know if the impact would have been as great, yet please try wake lock beforehand. Here's a link https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en_GB
I do have the same stuttering problem with my Sony AptX enabled SBH80 bluetooth headset. Upgraded my Sony Z5 Compact to Marshmallow, at first this was okay but after a few days the stuttering came back. It also happens with my other bluetooth headset (not AptX), a Sony MW600 (though less than the SBH80).
Somebody on XDA Developers suggested using a wakelock app. I will try this one: https://play.google.com/store/apps/details?id=eu.thedarken.wl
This is a common MM bug.
On my tablet, I installed Wake Lock PowerManager and it seems to work, at least when I do all the app store updates.
YMMV, but it's a free app at least
https://play.google.com/store/apps/details?id=eu.thedarken.wl
I had the same issue with PocketCasts and the default music app, turns out (my issue) was related to turning the screen of while listening to audio. Putting the phone in partial wake-lock with the following app eliminates this bug.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Hope this helps.
This is the app: https://play.google.com/store/apps/details?id=eu.thedarken.wl
I saw it mentioned on a google forums thread. Just run it on the partial wake lock setting and no more SoDs. It'll drain the battery faster, but at least the phone is reliable for now.
Likely what's happening is a bug with the Home app or Chromecast, that when your phone's CPU goes to sleep on your phone it's causing the Home app to stop playback. Or for Home or the Chromecast to just act funny when it receives a strange ping signal. Eg, Chromecast pings the Home app, receives weird signal (due to your specific model.of phone or android version) and this triggers the bug and shuts the playback down. Semantics are off here but hopefully you see what I'm getting at.
There are several solutions...some you may have tried already. One or more will probably work ...
try keeping your screen on full time (settings > display > never turn off (if that's an option)
keep Display to turn off as normal (5min or whatever) try with phone plugged in and screen on AND off. Obviously off is better here. Because it's plugged in it may not go to sleep regardless screen on or off.
try this wakelock app. This should stop your phone from sleeping. There are a couple different on Play https://play.google.com/store/apps/details?id=eu.thedarken.wl
>Google will most likely never fix this.
If we all put a lot of pressure they'll need to deliver.
> Install Wakelock.
Oh, sideloading makes me feel lazy, this app should be on ATV as well.
If it'll start up then you could try the Wake Lock app on Setting 4, PARTIAL_WAKE_LOCK if you haven't already done so. It might give you a few extra weeks or months at the expense of slightly increased battery usage.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
If it's still under warranty contact Samsung. Depending where you are they may have parts in stock. I believe that out of warranty Note 4s can have the motherboard replaced for $70 in the US.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
When all set and downloaded, set it to level 4. And I know what you're talking about for eMMC check - it's outdated and gives a false positive on the Note 4. You'll know quite soon after using this wakelock app if it's gone bad. Which it sounds like it has.
Reflow is unlikely to work if it's the mmc_fail problem as it's the eMMC (internal storage) that's failed.
Everyone with the problem uses the Wakelock App which will likely delay the inevitable failure.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
The fact it was sold for cheap though is likely to mean that the previous owner tried everything.
I installed and ran this app at partial Wake Lock:https://play.google.com/store/apps/details?id=eu.thedarken.wl
I kept it on for a full day. I then turned the wake lock off, and the the wake delay is gone.
I'm assuming you mean this app?. How does it extend the life? I just experienced the first failure today and am looking to extend the life of my phone as long as I can.
edit: Alright, googled all the info. Hopefully I have similar results.
I have kept observing this problem on my OnePlus One since Cyanogen OS 13, so it is perhaps nothing new.
My suspicion is that it is a deep-seated Android defect, because it happens on all kinds of phones, and that it is triggered by certain actions of certain apps, but I don't know which. It is definitely an Android defect though, not an app defect, because no action of any app should be able to cause Android to reboot.
On my OPO it only happens when the phone sleeps. In this case I can circumvent the problem by always running the app Wake Lock and keeping the phone in a PARTIAL_WAKE_LOCK. Unfortunately this increases power consumption somewhat, but for me this is still the best way. I have never had a spontaneous reboot since I do this.
On other phones and phone types it can happen under different conditions. In that case a wake lock may not help, but other workarounds might.
Eventually, I got mine to boot and ran this, just keep trying or try 20mins later. try power down+volume
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
it won't turn off the phone, but the battery will drain it faster
I forget if you need root or not.
RedEye Stay Awake didn't keep my Fire TV box awake, either.
I was finally able to keep it awake and out of sleep mode with Wake Lock:
https://play.google.com/store/apps/details?id=eu.thedarken.wl
I'm guessing burn in (temporary or otherwise) is a risk, which is why the Samsung's always on display doesn't sit in one spot (it moves around every so often to avoid using the same pixels all the time).
Something that might help with this would be using a wakelock app instead of the battery saver mode on pokemon go. I don't play pokemon go much, but I assume the battery saver mode is used to keep the screen on so the pokemon go app will still have access to GPS and keep the processor running. With the wakelock app, you should be able to do all that, but do it while the screen is off, which would stop burn in. You'll have to play around with it to see if it works well with pokemon go or not.
- Go to the wakelock app and activate partial wakelock
- Open up the pokemon go app
- Do what you gotta do in the pokemon go app (make sure to disable battery saving mode, just leave it on the normal map screen)
- Press power button to turn off screen (or if that's causing the app to become suspended in the background, allow the screen to turn off from the normal screen timeout before putting it in your pocket)
- ????
- Profit
Fixed the stuttering issue. It's the dumb (stock) kernel on 5.02 that stutters the playback as soon as screen is off. I used a partial wakelock so the cpu stays active after screen off with this app. It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance. It's a workaround but the partial wakelock should work especially on bluetooth headphones. Here's the app's link https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
Brilliant... Absolutely brilliant!
Just installed this on phone and pc... takes a bit of tweaking, I needed to adjust the curves for yaw and pitch (did the same curves for both) in the Opentrack software on the pc to get it to work smoothly with my head movement.
Also, to stop android turning off, install Wake Lock and set it to "PARTIAL_WAKE_LOCK"... this will prevent your phone from going to sleep... (obvs turn it off once you've finished playing.)
I've mounted my phone to headphones with a thick elasticated hair tie, working well. :) .
.
.
Here's a bit more in depth install instructions .
.
Solution 1: set a custom time interval for the screen saver to begin at (for example, less than 5 minutes)
http://www.aftvnews.com/how-to-set-a-custom-screensaver-start-time-on-a-fire-tv-or-fire-tv-stick/
Solution 2: prevent Fire TV standby mode:
Either sideload Wake Lock (probably easiest/best solution)
https://apkpure.com/wake-lock-powermanager/eu.thedarken.wl
or set custom time for standby mode:
https://www.reddit.com/r/fireTV/comments/5huwg9/is_there_a_screensaver_mode_in_firetv/db3985x/
(May or may not have upper limit)
cc: /u/FoxRiver
> My note4 crashes
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
PARTIAL_WAKE_LOCK #4
Read the reviews.
Yes, there are apps or it's implemented within apps. Examples are:
https://play.google.com/store/apps/details?id=eu.thedarken.wl
https://play.google.com/store/apps/details?id=com.dambara.wakelocker
https://play.google.com/store/apps/details?id=eu.thedarken.wldonate
Download this app: Wake Lock After you download it, turn on "partial_wake_lock"
This fixed my random rebooting problem.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Use the PARTIAL_WAKE_LOCK setting.
If I were in your shoes, I'd do the following: https://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
This should repartition, format and install a clean system.
Then if it regains life, at least in part, try these others tricks:
Install the Wake Lock app from https://play.google.com/store/apps/details?id=eu.thedarken.wl and set it to partial wakelock
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821/post70349958
This one made my note 4 fly again after 6.0.1 update.
Please report your results here.
EDIT: if your phone is apparently dead, there's still hope, with the debrick image method: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Google will most likely never fix this. Install Wakelock. This will fix your problem
> Holy shit, your note 4 does that too?
https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
PARTIAL_WAKE_LOCK #4
Read the reviews.
I couldn't get the adb command to work awhile back, so I found this app and it works great on my firetv.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
This is the one I have installed.
https://play.google.com/store/apps/details?id=eu.thedarken.wl
Maybe this helps:
- Use PARTIAL_WAKE_LOCK: Wakelock Detektor [Root]
I use Wake Lock by Darken.
Download this app: Wake Lock
After you download it, turn on "partial_wake_lock"
This fixed my random rebooting problem.
Have you tried fixing the wake locks using this app? - Wake Lock
Sounds like your phone is having many of the issues I was having on mine. I was also having sudden reboots (started out happening when just using the camera, but began happening more frequently and at random). Sometimes the phone would go into a boot loop, sometimes it would fail to boot to this screen. Sometimes, the phone would be on, but completely unresponsive to any button input. Phone was very laggy overall and I thought I was going to have to upgrade before I was ready.
Someone here recommended installing the Wake Lock PowerManager app, which I had heard about, but thought it required root. It doesn't and it fixed almost all of the previously mentioned issues.
All you have to do is install it, start the app, and select the "PARTIAL_WAKE_LOCK" mode, which "Ensures that the CPU is running. The screen might not be on."
This is absolutely the first thing I would try. The app is free and you can read review after review of people who were saved from an early upgrade, just from using this app. I purchased the "donate version" to support the creator of the app. I can't recommend it enough.
At the same time, I would recommend looking at an upgrade path and backup all important data, as I believe that this is a temporary fix to the deeper issue of failing hardware.
Btw, I'm also running 6.0.1 - on the AT&T version of the Note 4, just so you know what I'm working with.
I hope that works for you. But, since it's free, there's no reason not to try it.
Also, After installing the app, you probably should keep the phone reboots at a minimum, as my phone still struggles to boot, sometimes requiring several battery pulls to get it back up and running. If you do reboot, you'll have to relaunch the Wake Lock app and set the "PARTIAL_WAKE_LOCK" mode again. As far as I can tell, there isn't a way to have this launch at startup. That may require root, I'm not sure.
Same thing happened to me today. Phone slow to respond, and finally in reboot hell, with the occasional mmc_read fail Odin screen. I'm going to attempt the Wake Lock suggestion from earlier, and also reading through this thread on Sprint forum: https://community.sprint.com/baw/message/1035916
Not sure if it's the one everyone recommended I use, but I'm using https://play.google.com/store/apps/details?id=eu.thedarken.wl
It's worked for me for a month without incident.
Try a app called 'wake Lock' from the app store, I use it to keep my phone from freezing due to mmc failure.
https://play.google.com/store/apps/details?id=eu.thedarken.wl