Hi,
I have been a smartphone (non touchscreen) user for years, I had a pocket pc (universal) for a while but didn't get on with it due to its size and flakyness and this very same issue, though at least its screen would switch off.
My trusty old s710 started corrupting its memory cards at regular intervals (every couple of days) so I decided to go for a pro. so far its been a big mistake can anyone please make any suggestions?
I managed to work out most of the issues, very poor performance, etc were down to a very old rom, though the very poor cellular and gps performance i guess there is no fixing but I have an issue where your help/comments would be appreciated before it goes back to /usr/ebay/
The main issue is with the power management, I want to be able to pick up my email at regular intervals and leave nimbuzz (chat client) running on wifi or cellular, with my old s710 this isnt a problem but I cant find out how to get the wifi to stay on or programs stay running when it goes into standby. If I tell it not to switch off the backlight stays on dim and the screen stays on. It seems to be the power state modes on PPC are some what different. On a smartphone when it goes into standby everything still runs, wifi is on etc.. but this thing just grinds to a halt so to me its useless as it stands. Can anyone tell me how to keep the phone running but switch off the backlight? and will this seriously impact battery life (will it still do 18hrs like my s710 would)?
If this isn't fixable is there another smartphone I should be looking at? I like the s710 but it hasn't enough memory. Just not the rose its just too big.
Many thanks
j
Haven't tried this myself, but I saw it. Try installing Advance Config, then go to the More settings (right softkey) then hit connections. There's a check box for enabling wifi on standy. I've noticed though, even on standby, wifi kicks in at certain intervals to retrive mail, but I have my mail through exchange, so I don't know if that's the reason why. Hope that helps.
There's no way you gonna get 18hrs with wifi turned on continuously.
TP's battery life is crap
Pro driving me miss daisy
Hi
thanks for that one, yes it works as far as keeping the wifi on but the programs still stop or at least no longer make a noise when a message comes in....
re battery, bummer, maybe an extended battery would help?
I used juice defender a few times, but could not find any other feature besides the enabling/disabling of the wifi and 3g.
I found it not reliable, and I ended up doing this manually.
Does this app do anything else besides that?
Cpu throttling?
any other battery saving "things"?
Thanks
It *can* make a huge difference with just the default settings. However, recent updates seem to have really knackered it for some people.
It stopped working for me and would not work again, even after uninstall - reinstall, until my phone was re-rooted for some reason.
supposedly.
but what does it actually do?
Disable/enable wifi/data based on your criteria to save battery.
Problem is, wifi part is not really working for me.
Sometime JD won't enable wifi because "user disabled wifi" but i didn't disable anything.
I PMed the developer and he never answered.
Did i mention i bought ultimate juice and i shouldn't have because no fix means crap app?
I tried using it for a little while with default settings but after 2 days I found it drained my battery more, and my data would not always re-enable itself when the screen came on. Sometimes it would even put itself in airplane mode.
Hopefully someday it gets updated. A lot of people swear it works great.
yeah after reboot i'm having the same problem.. JD not working and shows error.. boring.. hope they fix it a.s.a.p
di you guys have any issues while wifi or 3g get enabled?
When i used it I had a lot of problems with wifi not connecting or 3G not connecting after I strated the phone.
thats why I decided to do it manually.
It seems to me this app is overrated, and it's name is tricky.
names seems like it does more than it actually does.
Yes, i have problems with WIFI when i use JD.
The app is good if you don't have a data plan as you don't have to keep wifi always on and waste battery.
The wifi policy to turn wifi off when screen is off doesn't help either because you won't get updates.
JD works fine about 70% of the time but when i see i don't get any updates for 30min then something is wrong and i have to turn wifi on manually because JD believes is disabled by user which is not.
As i said, i sent an email to developer and i was ignored.
Hey guys-
Just upgraded to the FR008 Liberated and I dig everything about it but one thing. The battery life was immediately radically reduced from what I was getting with Eclair, and after turning off push and doing everything else to preserve battery life, it seems clear now that the problem is that it is searching for wifi hotspots everywhere.
The Y5 "Battery Saver" utility worked brilliantly on Eclair to turn off the wifi unless I was in a location where I used wifi, and then remembered if I manually turned on wifi in a certain location. I bet this tool increased my battery life by 50% on Eclair. But it totally doesn't work at all on Froyo.
Is there any way to get equivalent functionality from Froyo? Or does anyone know of an update to Y5 that will fix it with Froyo? It doesn't crash, it just doesn't do anything on Froyo.
I tried searching for this but it won't match "Y5" since the word is too short.
I've tried the various things and they all lag the hell out of my phone. And yup, the battery will drain terribly, no one believes it's a problem though, everyone seems to cite "check your apps" and don't realize that people aren't dumb and that the ROM drains battery.
the ROM doesn't drain the battery, but constantly searching for wifi hotspots does. Y5 solved that problem by turning on wifi only when you are in a location where you have configured it to use wifi.
As an example, when I go for a 2-hour bike ride with my phone, it drains the battery about 60% during that two hours, just because I happen to ride through neighborhoods where there are a ton of wifi networks (people's home networks). With Y5 working, it just stopped looking for wifi once I left my house and it only went down about 5-10% during that same 2 hour period.
I'm not sure about liberated, but on cm6 froyo if you go to settings> wireless & networks> wi-fi settings, and then press your menu button three is an advanced option. From in there you can set your wifi sleep policy to disconnect wifi while the screen is off. The phone shouldn't search for a wifi connection when the screen is off in this mode.
Sent from my cm6.1 Aria using XDA App
I suppose that'll help a little bit, but won't help much if the screen is on... like I am using the phone (say, in the car, especially while using navigation)...
Still would be nice if Y5 worked. It was a brilliantly simple solution. Not exactly in the mood to pay $10 for an app to do this but I might have to if it gets too frustrating.
check out Settings Profiles Lite - limited to one rule in the free version and should be able to do what you want.
T
looks like that MIGHT do it, but what a pain to set up for something so simple.
THe wifi sleep thing won't help me, mostly because when wifi goes off and on the network seems to be a bit flaky.
At the moment the only thing that'll work is manually disabling/enabling wifi. However, the widget seems to turn it off only to have it come back on.
sorry to bump, but wondering, does anyone else has a suggestion or a way to get Y5 to work in Froyo?
Hello there guys ..just wanted to post a quick question / add some findings i've seen with respect to the effect of toggling edge/wifi / 3G
I've had my phone for just around 10 days now, and have been noticing how quickly my battery life drops..
Until now, I had kept 3G + Wifi switched on (wifi toggled automatically with Y5-battery saver app), and, no matter how hard I policed background applications, my battery life would automatically fall at the rate of about 1% every 5 minutes (even if I were not using the phone, and it was just lying idle)...
Today, I tried switching off Wifi altogether, and forcing my network data to 2G ...my (probably flawed ) logic being that push notifications can happen even over edge/GPRS, and when I need to use more internet heavy applications, I could switch wifi/ 3G back on for the duration I needed it ..
I have been seeing pretty decent results over the past few hours ... battery has dropped just about 4% in the last 2 hours...i've attached a (crude) image of my battery usage screen, and on it, you can see the usage curve changing to a lower rate from about the same time I turned wifi off completely..
Could anyone with more knowledge about wifi/edge/3g battery usage pls let me know if this is a genuine improvement, or if its just some placebo effect
I'll continue monitoring it over the day and keep you guys posted
I believe battery usage from most to least goes:
3G
EDGE
Wifi
Sent from my Nexus S using Tapatalk
Thx hfm ... i think that's generally the order in which battery is consumed as well - EXCEPT when wifi reception is spotty..
I think what was happening until now was that the 'Y5 Battery saver' app was recognizing my 'home' as a location with a known wifi connection..and was constantly switching on / searching for wifi connections whenever I'm at home..
but the problem is that in some parts of my home, wifi reception is a bit spotty...so all that 'scanning' would happen for no good, and no connection would be fixed..
the battery saver didnt really save much battery then
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
mongoose3800 said:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.
I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.
My battery life is again fantastic and I am happy now that I know the cause.
Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
Click to expand...
Click to collapse
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers!
Agree with stanley, this is not the only cause.
39089665568
vndnguyen said:
Agree with stanley, this is not the only cause.
Click to expand...
Click to collapse
Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
I don't get it. What am I supposed to do exactly?
aydc said:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
Click to expand...
Click to collapse
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?
Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.
HS2.0 can let client and AP sort of talk without associating.
Nazty111 said:
I don't get it. What am I supposed to do exactly?
Click to expand...
Click to collapse
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
aydc said:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.
Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.
Click to expand...
Click to collapse
This is very true. Back on my old GNex i used to have crazy wifi wakelocks and I couldn't for the life of me figure it out. I never figured it out, actually. But I am positive it is one of the two PC's on my network that are broadcasting packets across the network, waking my phone up. I haven't had time to extensively test the wifi wakelock in the environment i've previously encountered it in to see if it still applies, but since I haven't changed anything regarding any of the two computers involved on that network, I'm positive I will have the same wifi wakelock issue when I get back and test. Is there a way (besides using Shark) to see what programs are broadcasting packets across the network?
But to get back on topic, I am experiencing battery drain connected to ONE router with ONE AP. I am in an apartment building with several other routers nearby, though. Maybe they are broadcasting packets somehow that the kernel is interpreting and keeping the phone awake? However it seems as though the Android OS bug keeps coming back for everyone no matter what, even in airplane mode.
Wifi has evolved a lot the last decade, not just by technology standards but into integration as well. carriers use them as small cells, we'll see them more often in the future (malls, stadiums, etc), and HS2.0 adds to make it a bit more seamless, they call it offload, taking your data needs through small wifi cells rather then the macro cells (3g, 4g), hence offload.
my point is that they would have never invested in that if the wifi chips inside consumer products were not efficient enough, so nearby APs shouldnt be a problem at all. But im still puzzled for what would one need the waking up process through wifi?
If Wifi is the general bugger, then somebody throw an eye on the Passport service, thats the consumer name for HS 2.0 services.
PS, tested AP Isolation on my sh!tty WRT120N, no difference unfortuantely.
Will there be a future update from Sammy or will we get Kitkat directly
Sent from my SM-N900 using Tapatalk
Just a follow up. I have still had no battery drain since avoiding connecting to wifi networks that use multiple APs. Now, i only connect to wifi networks where i know there is only one AP. Before I stumbled across this the drain and Android os wake lock was bad, really bad, after I had connected to large wifi networks - I just hadn't put two and two together. This is more than coincidence - my testing is sound and replicable. And, this week I have been in remote areas with weak to no 3g signal and the battery life has still been fantastic and no wake locks so that sort of rules that out - Sure there is a little increase in battery usage but nothing dramatic, something to be expected and certainly not something to complain about. I have seen many claims to fix battery drain but these are just fine tuning and not addressing the major drain caused by Android OS wake locks. Clearly, there must be an issue with the wifi software driver in MJ7/MK2 and I hope Samsung/Google are aware of it. The annoying thing is getting Samsung to acknowledge the issue and take feedback.
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
EddieN said:
I get wake locks even if I manually turn wifi off and only use data. When I use wifi i am connected to only one AP and I still get wake locks. The wake locks aren't apps, they are "Powermanager.wakelocks" and "Powermanager.Display" and show up as "Android OS" in battery settings.
I am still not convinced avoiding multiple AP wifi networks is the one-for-all solution for everyone.
However, I have put "wifi on during sleep" to "never," yet my phone slept maybe 50% yesterday but wifi was on 100% of the time. Why is this? Shouldn't it have turned off the 50% that the phone was sleeping?
Something is weird with the wifi module..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
mongoose3800 said:
Have you ruled out any other wifi connections? Have you tried rebooting if you have connected to another wifi network? Have you tried forgetting all wifi networks? Reboot after forgetting all networks. Then give it a couple of days with out connecting to any wifi network - just a test to confirm it is wifi related. I tend to think setting wifi to never on during sleep makes no difference - I had previously tried it too. Once the drain starts the only way to stop it is to reboot.
Click to expand...
Click to collapse
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
EddieN said:
Yes, just last week I was on another Wifi AP about ~300km away (totally different environment) and I still had the same wake locks. I have rebooted when connecting to another wifi network. I have tried forgetting all wifi networks i have connected to, and reconnecting to them. I have also rebooted once forgetting networks. During this time I also took the liberty of doing the normal rounds of disabling location services etc. before rebooting, but nevertheless i did reboot once forgetting the network. All networks I have been connected to have been single-AP wifi networks.
I have not let it sit for a few days without connecting to any wifi networks. That's the only thing I haven't tried. However I have let it go a whole day with wifi turned off (and only data enabled), but the same wakelocks persisted. For me it's always "Powermanage.Display" and "Powermanager.Wakelocks" no matter how long i just let my phone sit around with the screen turned off. I have it right beside me so I always have visual access to the screen in case the phone wakes up on its own, but it never has. I guess I could try turning wifi off for a few days and seeing how it fares, but I doubt I will see any difference (wake lock wise).
I'm thinking something is strange with the wifi module anyway. Surely wifi should turn off by itself once the phone sleeps, right? Like I said in my other post, my phone slept maybe 50-60% of the time on a 14 hour day. That means Wifi should have been on 40-50% of that time, and off 50-60% since the phone technically should have been sleeping. Yet I can see in the battery settings menu that wifi is a solid green bar all across the 14 hours.
Click to expand...
Click to collapse
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
mongoose3800 said:
Well that's interesting. At least in both cases we know it's Wi Fi. I wonder if it's something if it comes down to the type of connection. Eg 2.4 vs 5ghz
Click to expand...
Click to collapse
It could be. Both networks I have been connected to have been 2.4GHz Wireless-N capable routers. I just find it odd that a lot of things don't add up when looking at awake times in Settings -> Battery and comparing it to kernel/partial wakelocks in BBS/WLD/CPU Spy. All of the times seem to be roughly in the same ballpark, but they never add up to correspond to each other. Surely there must be information missing in this regard.
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
duffmannr3 said:
I can confirm the WiFi issue on my N9005 but there's another one.
1. Wifi: I experienced this at my university, where we have good Wifi coverage on the whole campus. They use Radius for logging in. After using Wifi for about 15min, I had these wakelocks, which didn't stop until I rebooted the phone. Since I knew this, I haven't been using Wifi there any more. But: In the meantime, I did a factory reset and got this little stability update. A few days ago, I gave it a try again. Used Wifi at university for ~25min and hat no issues. Maybe it's gone, I will test again some day.
2. I had an app called "gentle alarm". On my GNexus, which I used before my Note 3, I also had wakelocks, but couldn't figure out what it was, since wakelock detector, better battery stats etc. didn't show more than PowermanagerService.Wakelocks/Display. So I got my new Note 3 and still had these Wakelocks - I did much Monitoring and: It was this tiny alarm app. Very funny: After having excluded every other possibility and having the wakelocks active I uninstalled the app on my Note 3 and it instantly rebooted!
Great battery life now.
Hope this helps someone. BTW: The Wifi issue on larger networks seems to be a problem not only on Samsung phones, many people are experiencing this (e.g. found similar reports for Nexus 5...).
Click to expand...
Click to collapse
Thanks for your input. Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
EddieN said:
Is the wifi issue you are talking about the fact that it doesnt turn off when having "wifi on during sleep -> never" set? Or the multiple-AP issue the thread is talking about?
Click to expand...
Click to collapse
It's the issue about "multiple" APs, but I don't think that it is about the number of APs. What I have read is that there is so much traffic on those big networks, e.g. broadcasts from other devices. I don't know how it should be with your problem that wifi doesn't turn off - can you see if it's reconnecting after some standby time? If yes, then wifi is turned off during sleep, but is just not shown in statistics.
EddieN said:
What stability update is it that you have received? What country are you in and what firmware are you using? Did you get this stability update while on MJ7/MK2 firmware? I haven't received any notification for a stability update OTA...
Click to expand...
Click to collapse
I'm currently on MJ7/MK2. My device is unbranded and I'm living in Germany. It came on 26th of December and was about 30MB or so.
EddieN said:
Thanks for the Powermanager.Display/Wakelock issue. I guess I will have to sift through my apps and uninstall each, one by one, to see if the wakelocks disappear. If not, there is some other issue
Click to expand...
Click to collapse
It's definitely worth a try! There was absolutely no hint that pointed to this one app. I started with having a look at the battery statistics ~every 30min after a fresh reboot. After a few days it was clear that it only could be the alarm app, battery draining started only in the morning.