Related
When I first got my TP2 the battery life was great. Then I started adding tons of applications and tweaks and then suddenly one day the battery started to go crazy, it would drain in under 4 hours, with absolutely nothing running.
I started trying to track down the culprit. One thing I noticed right away is that my data connection would come on randomly. I'd shut it down, then a little while later is was on again. I turned off all the automatic updates I could think if (email, weather, stock, Windows update). With data, BT, wifi all turned off, screen off, nothing running, the battery would get hot and every minute would lose a few more percent. The phone was at this point basically useless. Because task manager showed nothing running I figured the battery had gone bad, or horrors, some fault maybe in the TP2. I took it to TMobile and got a replacement.
On my new phone, battery life seemed OK again. So, I did my Resco restore but it didn't work because I had password protection on the phone when I did the backup (not the TMobile password, but the one before that you get during boot up), so on restore it wouldn't let me into the phone saying the password was invalid (apparently something I should have known. grrr, bad Resco!).
So, I manually reinstalled everything again, not thinking to do it one piece at a time because I thought my battery troubles were over. I was wrong. Once it was all loaded up again, the exact same battery sucking began, and the data connection coming on again.
One thing I had noticed is that if I turned off TF3D I could see the icon for ESET virus protection running (it doesn't show in task manager). I knew I'd installed it, but because the TouchFlo screen hid the icon I'd forgotten about it. So, I went to that and clicked 'update' wondering if it was automatically checking for updates and so accessing the internet. But 'update' just gave an error message. So I figured the anti-virus wasn't going to be much use to me until updates were working, so uninstalled the application. BAM! (c) Emeril, battery problems ended!
I did a little googling and saw a couple of other references to ESET and battery drain on other phones, so I think that's been the problem. I don't know if the problem was the software itself draining the battery in its normal state, or if it was maybe constantly trying to make an internet connection to check for updates (but because that feature wasn't working it just kept trying).
I'd like to point out that I am in no way maligning ESET, it's totally my fault: 1) they do not yet claim compatibility for the TP2 ( http://www.eset.com/products/mobileantivirus.php ), and 2) I picked up the .cab from a link from one of the phone forums (not sure where or how any more, I have loaded up so much stuff), not from the ESET web site, so I could well have an older or bad version. I thought the software was freeware, but looking on the site I see it's just a free 30 day trial, so it's quite possible I had a cracked version. Their official version may well work with no problems.
But I did want to post this warning in case anyone else runs into battery drain issues.
Hi Iam an official reseller for the Eset antivirus. Just installed a version on my phone, will report back if drains my battery. How quick did it drain. If any probs i will report back to eset, to get sorted. Could just be the patched version. Funny enough the very firts pc version i got was a pirated version. Liked it so much much i thought sod it and paid for it.
Let me know if you wish to purchase it I can do a bit of a forum discount for you. same goes for pc version.
Hi, thanks for helping to try to get this resolved. The software ran very fast and I think could become a valuable addition once the WM6 viruses become more prominent.
The drain was *rapid* I'd say from 100 to 0 in about 3 hours, so if you do have the same problem, you should know right away. Also, the battery got warm to extremely warm, I might even say hot to the point that it was getting uncomfortable to hold. That certainly leads me to believe there were possibly two problems. One being that the software was for some reason maybe running aggressively in the background. The other that it appears to have been trying to connect to the internet every so often. I'm not sure exactly how often, it seemed somewhat random, but I'd say at least every 15 minutes (I would keep turning off the data connection whenever I saw it running). So I don't know if these are one and the same problem (that the software was trying to update and that was the code that was going out of control). Now that I have the phone working well again, I can have the data on constantly without anywhere near the drain I was experiencing, so the data alone was probably only a minor part of the issue.
When I tried to 'update' I got an error (I can't remember what it said). Is this still the case with the current version? If not then I can assume I have an old version and maybe the battery issue is gone now.
If you like I'd be willing to dl the 30 day trial and see what the latest version does.
Several hours later no battery drain. The software should only update itself 1 a week by default and at most every 3 days if set. Download the trial give a whirl. PM me if you want to buy and I can get a cuople of quid off, same goes for pc based one. This is extended to anyone else aslo.
Don't use any antivirus program on your phone. I've tried several antivirus trials on several htc phones (s620, s710, touch pro) and they all showed extreme battery drain. Since then I've stood clear of any antivirus program on my phone.
Well nearly 24hrs later and no significant bettery drain. I even ran a couple of scans. There is no reason why an antivirus should drain a battery, otherwise no one would have them on laprops either. It was probably down to the pirated version you had.
Let me know if you have any probs.
I never used a pirated one, I only used trials (that's why I tried so many ).
Maybe it's a different story these days, might have to try one again some time...
hi. I just found out that cellular radio is taking up most of my battery on the NST. its strange, considering the fact that nook does not have telephoning capabilities. I went a bit deeper and found out that a process named DemoModeService is present, as all as WaveFormDownloaderService and DeviceManagerService, all of which are bn services. I wonder if they have a role in battery drainage and if anything will happen if I stop them.
I would start with switching nook completely off and on again. Solved all my battery drain issues in the past.
cceerrtt said:
I would start with switching nook completely off and on again. Solved all my battery drain issues in the past.
Click to expand...
Click to collapse
Is yours unregistered as well?
Increased battery drain on unregistered devices is a known issue and most likely caused by B&N services that, in lack of a better description, "wont settle down" due to the device not being registered and logged on to B&N
Stopping those services might be worth a try, and I doubt doing so will cause any major problems.
I'm not sure what causes the battery drain, but i'm betting it has to do with the Google apps.
I rooted my nook with both the methods listed here and my battery life was awful.
I restored to stock manual rooted with out adding any Google apps just manually installed what i wanted and my battery life is awesome.
The other methods might be easier but they install way too much junk that causes battery life issue.
persichini said:
I'm not sure what causes the battery drain, but i'm betting it has to do with the Google apps.
I rooted my nook with both the methods listed here and my battery life was awful.
I restored to stock manual rooted with out adding any Google apps just manually installed what i wanted and my battery life is awesome.
The other methods might be easier but they install way too much junk that causes battery life issue.
Click to expand...
Click to collapse
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)
I don't think gapps have to do with anything. they do get automatically installed even when the device is registered and rooted they don't cause any major problems then. they do take up a lot of battery , but its not as much as unregistered and rooted NSTs. I am sure this has to do with those bn services.
I don't want to reroot it and go through all that nonsense again. just tell me if stopping those useless services would cause any problems, and if anyone has tried it. I am not too enterprising, and would be glad if some ambitious developer did it first.
ros87 said:
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)
Click to expand...
Click to collapse
by the way, thanks @ros87 for your help the other day. I reached the technical team and the only thing they'd say was to use their bloody chat room that's always offline in my time zone, or to call them on their international number. they are not very helpful. so, I just bypassed the registeration.
ros87 said:
You're off topic
This is a topic about increased battery drain on devices that are not registered with B&N. (i.o.w., the user skipped the registration process)
Click to expand...
Click to collapse
Actually, is there a way to find out which app drains CPU?
Same Q I asked already: how to convince ps to display cumulated CPU time
ros87 said:
Is yours unregistered as well?
Increased battery drain on unregistered devices is a known issue and most likely caused by B&N services that, in lack of a better description, "wont settle down" due to the device not being registered and logged on to B&N
Stopping those services might be worth a try, and I doubt doing so will cause any major problems.
Click to expand...
Click to collapse
How do you stop the B&N services?
I uninstall system apk
Phone.apk & TelephonyProvider.apk
and after that my nst works fine
look at http://forum.xda-developers.com/showthread.php?t=887957
Thanks for that latuk. I think I'm one step ahead of myself here. Presumably in order to do these things the NST needs to be rooted. I now need to investigate how to root the NST.
My wife and I have each got an NST Glow. I operated them both unregistered. We both experienced battery drain of about 6% overnight (10 hours) in screen saver mode. I was about to embark on the rooting/apk removal solution as discussed above.
Before I started that process I thought I might as well try registering one of the NSTG's as a test. The result was conclusive.
Again overnight in screen saver mode the unregistered NSTG experienced 6% battery drain, the registered NSTG experienced zero battery drain.
I can only conclude that B&N have got built in processes that use a great deal of battery power if the nook is unregistered.
So it appears to me that for simpletons like myself the easy answer is to register. They simply require your email address and name, no credit card details. So registering isn't so bad.
Unfortunately, the time has come where B&N have taken their e-store and their registration servers offline. Even if your device isn't rooted, rom'd or otherwise customised, it is now an absolute necessity to know how to bypass the registration screen, the Out Of Box Experience*.
1. Turn on your NOOK.
2. At the welcome screen hold down the button on the top right (page turn button) and at the same time slide your finger across the top of the screen from left to right.
3. You should now see a Factory link on the top left of the screen, press this link.
4. On the factory screen hold down the same button (top right) and at the same time tap the bottom right of the screen.
5. You should now see a Skip Oobe link on the bottom right, press this link.
So it is still really a good idea to know how to work around the battery drain, as it is still an issue with this custom ROM I'm presently using, retired in 2015 [NST/NSTG][ROM] Tweaked Modded ROM Final
With Superuser installed, I used this ROM's Clean Master app to remove
com.adome.air.apk
com.benhirashima.nookcolorsettings.apk
com.android.email.apk
com.bndeviceregistrator.apk
com.bn.nook.affiledownloadservice.apk
com.bn.nook.cloud.service.apk
com.bn.nook.community.apk
com.bn.nook.shop.apk
Will report back if battery drain fixed.
This is the second time I tried to fix battery drain on a custom ROM, last time was using the 1337 ROM that came out in 2014. It was preloaded with too many utilities imho and I removed too many apks that I broke the dictionary app while fixing the battery drain.
*Uech! Out of Box. Experience. Remember when an experience was something worthwhile, like the first time you heard The Jimi Hendrix Experience or how much practice you've had in your profession.
Anne-d'Royd said:
Unfortunately, the time has come where B&N have taken their e-store and their registration servers offline. Even if your device isn't rooted, rom'd or otherwise customised, it is now an absolute necessity to know how to bypass the registration screen, the Out Of Box Experience*.
Click to expand...
Click to collapse
Maybe. If you update the firmware to 1.2.2 everything will work as before--assuming you have a US ROM. If not, you can change ROMs to a US version and then update the firmware. Either way, you don't need to skip oobe unless you want to for some reason.
I tried it recently on a second NST I got to experiment with. I thought I was doing really well, just keeping enough to allow the Reader/Library/Dictionary to function. Then I had occasion to look at a logcat to track down a problem. There was an endless string of system wails over this and that which could not be found or not be contacted. I could hardly find what I was actually looking for. In the end I decided it was better to update to 1.2.2, register, and just ignore the B&N stuff (except for the Reader/Library/Dictionary)--oh, all except for the NookCommunity app. That I did disable because it constantly nags you in the notification area.
OK, now having said that, I am still using my original NST which is running FW 1.2.1 (and is rooted and much modified). I've had no issues with it despite the dire warnings from B&N about June 29, although I did turn off the automatic update a few weeks before because attempts to update OTA were causing reboots.
But I've never bought any books from them, so I've not done anything that needs intentional connection to their servers since the change.
Hi, I live in the UK and I recently bought a Nook ST for cheap on eBay, planning to use it bypassing the registration. Little did I know about the battery drain and processes of the stock unregistered ROM. Mine runs under 1.2.1 I firmly believe UK version as I tried to reset and register but only got errors, forcing me to use the bypass sequence of buttons. Obviously I didn't even register any WiFi spot and the module is always off.
Based on your experiences, what is the best way and quickest to solve this battery drain? I'd use the Nook just as a e-reader, so I'm not interested about added functionality - if anything I'd like it as simple and little distracting as possible.
Is the US firmware a good fix for the problem? I wouldn't mind using stock US firmware as long as you confirm it still lets you register... Do you need root? Is there any particular procedure to switch to a different firmware? Is the ROM available on the internet?
If that doesn't even require rooting, I'd probably go for it... Otherwise what are the best things to do to fix the issue in a rooted UK device?
EmaTheMirror said:
Based on your experiences, what is the best way and quickest to solve this battery drain? I'd use the Nook just as a e-reader, so I'm not interested about added functionality - if anything I'd like it as simple and little distracting as possible.
Is the US firmware a good fix for the problem? I wouldn't mind using stock US firmware as long as you confirm it still lets you register... Do you need root? Is there any particular procedure to switch to a different firmware? Is the ROM available on the internet?
If that doesn't even require rooting, I'd probably go for it... Otherwise what are the best things to do to fix the issue in a rooted UK device?
Click to expand...
Click to collapse
You can reset the device to factory and then flash the US firmware. This will allow you to register and avoid the power drain issue which, to my knowledge, has never been fully resolved. Actually, you probably don't even need to reset the device, just flash the US firmware. That will put you at 1.2.1. (US firmware flash: https://sites.google.com/site/xcdguides/nook/nookregion)
As you may know, there is a new firmware, version 1.2.2 which incorporates updated TLS standards--but only for B&N transactions. However, even if you don't transact any business with B&N, a registered device will be constantly nagged until it is updated, and rooting will disable updating, but not the nagging. For that reason I recommend that after you flash the US firmware (but before rooting) you do the 1.2.2 update manually and get it over with. (update download and instructions: https://help.barnesandnoble.com/app...tware-updates-for-tls-1.2-compliance#ManualDL scroll waaaaay down.....)
If you want to root the device after updating, I recommend Nook Manager, but you need to make a minor change to the files on the SD card before you use it with 1.2.2. This is described here: https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566
Hi, thanks for the reply, I solved the solved the problem changing the firmware to US following this simple guide:
https://sites.google.com/site/xcdguides/nook/nookregion
Then updated to the latest firmware manually, which solves the connectivity issues among others, with these official instructions:
https://help.barnesandnoble.com/app...evice-software-updates-for-tls-1.2-compliance
Otherwise it wouldn't even connect. I didn't know at first and registered a new account via browser, signing in from nook later - then it connected just to register the device, don't ask me why - but it's always best to have the firmware up to date anyways.
The battery seems now fine, so far.
Just for the lulz, I tried to link a card to the shop but can only have US addresses for billing... Lol, eBook DRMs have always amazed me. Luckily, you can easily download Google Play purchases and sideload them (among others) via Calibre.
Thanks anyway, hopefully this post will be useful for future reference.
I'm trying to track down some wlan_rx_wake issue.
My understanding is that what is supposed to happen is that multicast is normally enabled when a device is awake, or perhaps with the screen on, but when the screen blanks, or more likely the system suspends, the broadcom chip is set to ignore multicast
This allows the device to sleep peacefully without being woken up by local lan broadcast traffic.
Does anyone know if the stock samsung 4.3 kernel (J9/VIA) does this?
How about alternative kernels/roms - do any explicitly enable or disable this?
It may also be an app that has the multicast lock... but I've disabled all apps I can with this permission leaving just stock samsung apps that can't be disabled. I can't root as I need sky go. I'm reluctant to replace with non standard rom due to knox, but will consider it (I've replaced firmware many times on other devices inc. s3)
The reason I ask is on my local lan I was seeing my S4 (and note 10.1) have this wakelock active for far too long. I've now removed most broadcasts from the network (most were netbios related!) and this wakelock is well under control now (6 minutes out of 1:16 isn't bad). However I have the same issue in the office where I can't fix the lan....
One way or the other I have a suspicion this is an oversigh in samsung's 4.3 rom.
I should say broadcast more generally....
So far the only mentions I can find are
- This modified 4.3 google edition kernel http://forum.xda-developers.com/showthread.php?t=2342298&highlight=multicast+suspend
More battery life tests and use of Better battery stats etc, along with network traces rather convinces me this is an increasing problem. At home I have some control over my network. at a place of work, less so.
Public wifi access points are usually ok as inter-device broadcasts are blocked. But home with uPNP, lots of devices doing arp requests etc is nearly impossible to manage - though I did cut mine down by about half. I'm looking at whether ddwrt could help with some filtering in a seperate wireless AP just for the phone/tablet!
The only real fix is for the device to implement filtering, which from the kernel source it looks as if it might but the only way to try for sure is either to root (breaking sky go) or do a custom rom (breaking KNOX, and possibly sky go). I wish I knew if there's some app/config causing my broadcast filter not to be active, or if it's a samsung kernel build choice.
I've continued to see this across my S4 (4.3) and Note 10.1 (4.1) running official samsung roms. It's been frustrating as it equates to sigificant power drain.
My sons' nexus 5 / 10 does not show this issue.
A few days ago I decided to flash a port of OmniROM 4.4.2 onto my note 10.1 . Same network, same apps - the problem has basically gone. There is still some wifi wake time but nothing like the amount previously.
My guess is the omnirom/aosp kernel is correctly filtering broadcasts, or just maybe it's because it's missing some samsung bloatware.
Possible fixes on the S4 are more awkward
- Any rooting, flashing a non-official rom etc will result in a KNOX 0x1 flag. Not really an issue to me, but annoying
- Whilst I *love* Omnirom on the tablet it may not be stable enough for phone use yet
- The samsung S4 camera is very good. Much better than alternatives
My current thought therefore is to
- hold out for samsung s4 build to see if the issue is addressed
- If not try rooting and disabling all samsung bloat, and try alternative kernels (if any) on the TW rom
- if all else fails consider OmniRom or CM11 , or Samsung's GE rom (by this point KNOX will be tripped anyway)
ANy thoughts?
Anyone else seeing this issue?
Any kernel devs care to comment?
So another check. Phone sat idle for an hour, of which 47 minutes was awake.
Apps did account for around 13 minutes of this - the big proportion being skype which I just installed earlier today. What a surprise. That's getting deinstalled (again), but most of the rest was just wlan_rx_wake ie the device being woken up to deal with packets. If asleep that should be minimal, as it is when running 4.4 on the tablet, yet it isn't - clearly samsung are not implementing the broadcast/multicast filter on sleep. AARGGH
I'm slightly bemused I see so few people mentioning this. Is it that they don't look? Don't care? Or is it just me......
I'd be tempted to do a complete reinstall... it would be a lot easier if I could easily backup (titanium backup or CWM backup) yet do either and I trickt the KNOX switch. thanks Samsung. Not. It's not a big deal as everthing is cloudified, but it would cost me a few hours getting things setup again, even things like the desktop layout ...
So is anyone using an S4 on 4.3 and NOT seeing this issue when on wifi (with multiple devices around) ? If so, just perhaps I'll try a factory reset, but I already did that coming from 4.2 anyway. Or perhaps you are using a custom rom/kernel and not seeing this or noticed it improved?
See also http://forum.xda-developers.com/showthread.php?t=2133176&page=3
Still on stock rom, and still puzzling this.
Most samsung value add that can be disabled in a stock, unrooted rom, is.
Yet a wireless network packet trace (run on an attached PC) shows a significant amount of activity - not being *received* by the phone, but actually being sent
Packets like this show up around every second! Hardly surprising the device is kept awake a lot
24631 888.950873000 android-295fdb686877cc14.home 239.255.255.250 SSDP 167 M-SEARCH * HTTP/1.1
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 1
ST: urn:dial-multiscreen-org:service:dial:1
In fact in 10 minutes idle this was pretty much the only traffic to or from the phone!
This looks very chromecast-ish -- which I don't have. presumably it's something screen share related from samsung -- even though no devices are connected/setup to cast screen
This must also be from a non-disable-able app - but I'm unsure how to categorically pin it down without root access
I've actually been here before on my note 10.1 - where my resolution was to switch to omnirom. That's less easy on the S4 due to knox concerns, and camera & other more esoteric features (spen is fine with omnirom on the note 10.1!)
Went through trying to kill processes/tasks that I could (I'm not root) and nothing stopped these SSDP broadcasts.
Checked settings - no changes made any difference.
Played with adb shell, dumpsys, logcat & finally ddms - but no jobs.
Wish I could find out the process that is initiating these packets!
An update.......
I decided to try one more time with the stock 4.3 BTU rom and did a full factory reset
WIth no google or samsung account, and no apps I had no wlan_rx_lock
I then configured google accounts (inc. gmail etc) with sync and added only minimal apps (zedge, chrome, mysms, kii keyboard)
still no wakelock issue
This would suggest it's app related, though by not configuring my samsung account (I don't need to) that could affect the way the bloatware works too.
Quite happy now! Wish I could take a "snapshot" backup. Of course that would need a custom recovery and break the KNOX flag. Oh samsung. that's annoying.
The plan is to leave it like this until after work, then to add tweetings & spotify. I'm going to slowly add apps back so hopefully help in identifying when (if at all) the problem reduces. Of course there could be a latent affect which would just be painful.
Annoying too I wasn't able to find the cause with adb, better battery stats, dumpsys etc without doing it the basic way.
planetf1 said:
An update.......
I decided to try one more time with the stock 4.3 BTU rom and did a full factory reset
WIth no google or samsung account, and no apps I had no wlan_rx_lock
I then configured google accounts (inc. gmail etc) with sync and added only minimal apps (zedge, chrome, mysms, kii keyboard)
still no wakelock issue
This would suggest it's app related, though by not configuring my samsung account (I don't need to) that could affect the way the bloatware works too.
Quite happy now! Wish I could take a "snapshot" backup. Of course that would need a custom recovery and break the KNOX flag. Oh samsung. that's annoying.
The plan is to leave it like this until after work, then to add tweetings & spotify. I'm going to slowly add apps back so hopefully help in identifying when (if at all) the problem reduces. Of course there could be a latent affect which would just be painful.
Annoying too I wasn't able to find the cause with adb, better battery stats, dumpsys etc without doing it the basic way.
Click to expand...
Click to collapse
Awe I was reading your monologue breathlessly while hoping for a solution. I've been at work 8 hours, and I have 4h 43m of awake time. All of it minus 10 mins was due wlan_wake
I'm on omega with ktoonz
hi MI A1 owners.
for those brave enough to use the latest vanilla, official OTA rom, what change did you notice?
does the battery still suffer huge drain that appeared in 2018 roms?
it's a big "NOPE" for me to update, i'm still on official DEC rom because of this drain issue.
Battery life is good on 8.1 no issue for me getting 5-6 hours SOT on gaming.
Never had battery drain problems. Only "issue" is notification led not blinking.
Just noticed that led light is no longer blinking when notifications arrive. Light stays on only when screen is off. Also Bluetooth is constantly disconnecting.
Ambient display isn't working for me.
Led notifier is also not blinking anymore!
Led not blinking, proximity sensor doesn't work properly all the time, some scrolling lag. That's what I've got so far
dudes thanks for your answers.
i'm just more convinced to not doing the update.
maybe the drain i had was magisk-related. (?)
Nothing for me, even got ten hours of screen after some cycles. Led doesn't bother me and it's the only thing i noticed.
Yes, the LED is always on, which is annoying, but the bigger issue is there is no change in the battery drain. I charged to 100%, set the phone down and did not move it or use it overnight. 8 hours later almost 14% of battery was drained. I have tried everything I can think of to try, including turning off high accuracy location, not allowing any location things like safe area, etc. and still I get this drain even when the phone is not in use. Android kernel and system consumed 85% of that usage, and System UI, Play Store and Phone Services accounted for 7%! SO basically, basic Android paired with the A1 hardware seems to be the issue and I don't know that there is any fix for that.
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
KB_Thailand said:
8 hours later almost 14% of battery was drained.
Click to expand...
Click to collapse
Dunno what to say man. Mine is below.
2-3% at most over night.
And now it would appear that there is an issue with airplane mode.
I put the phone into Airplane mode at 2300 last night with 90% battery and did not pay attention to it. This morning I turned to phone on to find there was only 69% battery left, and WiFi was working. (see screen shot) WTF???? I have started using airplane mode to keep the battery drain to a minimum when the phone is not in use, and now it would appear that this doesn't work either.
I am REALLY getting frustrated with Android and Xiaomi as it seems that every time they do an update, something else goes bump! I have gone from totally happy with the AI when I first got it to being ready to write off Xiaomi as a company I would consider for purchase.
IjazCI said:
Is your WiFi scanning is on. ( Under location / scanning)
Play services also cause these type of sudden battery losses.
Try downloading latest play services apk from apkmirror . Latest one is
"com.google.android.gms_12.8.74_(090408-204998136)-12874034_minAPI26(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk"
Uninstall your current one. Install this .
Power off your phone for a few seconds and reboot.
Click to expand...
Click to collapse
Thanks for the thoughts, but unless I totally misunderstand what airplane mode is, WiFi should not be active when airplane mode is invoked. You can see by the screen cap that airplane mode is on AND WiFi is active. This seems to be a one off as it has not happened again for the last two days. I turn airplane mode on to stop the overnight battery drain while the phone is doing nothing. I have location set to GPS Only. IIRC play services was just updated 3 days or so ago, so it should have the latest version. I will check it and see though. Again, thanks for the thoughts.
KB_Thailand said:
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
Click to expand...
Click to collapse
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
ludditefornow said:
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
Click to expand...
Click to collapse
Actually, I think it is a combination of hardware/software, but that is just a WAG. Others have noted the exact same issue without running the same software. My bet would be on the RCS services stuff.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
Click to expand...
Click to collapse
Those icons are my Email client and GSAM Battery Monitor (presently 0.1% and 0.8%) and are the only two constantly running programs other than the stock apps and Sophos (0.3%). Neither use much battery compared to the Android stuff. Presently Kernel is 41.6%, RCS/Phone is 30.3%. SystemUI is 3.3%, Play Services is 2.0% and Phone Services is 1.8%
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
Click to expand...
Click to collapse
Good advice. I will do this when I have a few days to play with it. In the interim, it's airplane mode every night. Thanks for the reply. If it turns out to be one of these apps, let me know where to send the Singhas.
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
For me, night light auto schedule not working properly.
I can't tether via wifi/bluetoth/usb
Made another post with the problem.
ludditefornow said:
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
Click to expand...
Click to collapse
Just for grins and giggles, I uninstalled my email client, GSAM, and Sophos, the only programs that run constantly other than system and Line. I then turned my phone off and back on, forced stopped Line, charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed, but still not close to what I would consider normal. When I first got the phone, it easily lasted 2-3 days between charges, with 6-7 hours SoT. Overnight would use MAYBE 2% of the battery. Now if I want it to last 2 days I need to turn on airplane mode overnight and then I can make it through a day.
So I guess the next step is to do as you recommended and load up the fresh rom when I have time to mess with it. At least I am now pretty sure that those apps aren't the culprits causing the biggest part of the battery drain. I hate to do it, but I am seriously thinking of a factory reset and seeing if that clears the issue. Would that put me back to Nougat?
IjazCI said:
I always disable carrier services apk. As rcs is not here in India.
Click to expand...
Click to collapse
How do you disable this apk? I seriously think this is the major culprit in the battery drain.
KB_Thailand said:
charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed,
Click to expand...
Click to collapse
So those apps were causing 40% of of the 20% of the battery drain. That is a good start. I am confident there are software issues with your phone. I see you have some GPS app on your home screen, if that was running askew, it might be constantly pinging. That is just a guess.
In things like this, work methodically through it. But of cause a hard reset would be the best way to go. I see no reason why you wouldn't stay on your current version after a hard reset.
If you want to go make to version 7 you would need to use the MiFlash program and a downloaded standard fastboot rom. You may need to do something else to the phone to go back to 7, but I would not think so.
Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:
I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.
I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.
I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now