Related
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.
As a new nexus 4 owner, I am trying to get a handle on how many people are getting issues with there Nexus after the 4.3 update, therefore a quick poll might help me and others in this area. I realize that this forum is not a completely representative selection but it's better than nothing.
Before you reply please check the terms I have used:
Stock = as you got the device from the store, no root, no custom ROM, no hacks. OTA update.
Modified = root access, customer ROM used, update from 4.3 ROM
Problem = any of the issues in the problem post (signal, reboot, heating up, battery, netflix)
No Problem = no obvious issue, including things that have known work around (like Play store issue)
Hope this helps.
Yes a very few of the N4 users are having problems with 4.3.
I only find the DEADLOCK ISSUE(Phone hangs for 5-6 secs)annoying and that is a JSS issue not with JRW..
Hope PA team solves this bug(partially solved). :good:
Have battery drain until restart. Then it's fine for unknown time. Phone can't go deep sleep. Better Battery Stats says phone is awake 95.6% of the time after unplugged.
Android OS is keeping the phone awake. Just installed Wakelock Detector to see what causing it.
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
Hello everyone.
A friend of mine sent me this.
" Google addresses Android 4.4.2 camera bug, says fix arriving in a future update
There’s a nasty little bug some users have been experiencing since updating their Nexus 5′s (and other devices) to Android 4.4.2. The big involves the camera application in Android 4.4.2 that when either opened by the user or triggered in the background from another app (Skype for instance), causes the device’s CPU to max out, resulting in abnormally high battery drain.
It’s not a good time for anyone, but try not to worry too much because Google is hot on the case. They’ve officially acknowledged the issue in their bug tracking forum and have promised to address this issues (and others) in a future maintenance update (likely Android 4.4.3).
Keep in mind that Google was only able to verify this issue on the Nexus 5 and recommends that Android users with other devices report the bug to their respective manufacturers. This has to due to with custom Android software (Sense, TouchWiz) that could also be triggering the camera bug, and will need to be addressed separately.
To find out if you have the bug, you’ll need to jump into your Settings > Battery and check to see if “mm-qcamera-daemon” is consuming a good chuck of your battery percentage. If it is, a reboot is said to help but it’s only a temporary fix. Also, uninstalling apps like Skype, Tango, etc. that use the camera may also help. It’s not the best solution, but it might be your only option until Android 4.4.3 is pushed out sometime in the future.
https://code.google.com/p/android/issues/detail?id=60058#c475 "
Anyone has the updates on this?
Regards,
This is specific to the Nexus 5, not the Nexus 4..
I have an I9505 running lollipop and struggling to address intermittent lag.
Broadly speaking the phone starts off working well, snappy.. but after a while can start to lag. By this I mean a press on the home button may result in a 20s+ delay for the task manager to come up. Switching a task may be slow, the keyboard may take 10-20s to appear, the screen may be mostly blank for a while. It doesn't crash, and does "come back" but it's nearly unusable. Usually once switched to a task and settled down scrolling is ok. then it may work just fine, snappy for a while
I don't see oddly high figures in the various stats I can see - cpu time isn't excessive. memory is harder to interpret and at times I do see kswapd busy just after a wakeup.. so my suspicion is it's a memory leak but one I can't prove
I've tried alternative kernels - hulk, imperium, and they don't appear to help matters at all.
The lollipop build was clean & Current firmware is I9505XXUHOD7, BTU
I am rooted and have progressively disabled various packages I don't use in an effort to lighten the environment
I've disabled animations (a cause of memory leaks in 5.0.1, though supposedly not affecting samsung touchwiz)
I am a software engineer and very familar with better battery stats, gsam, even a quick peruse through dumps via adb yet still haven't got to the bottom of my issue. I'm also very aware there's little in the way of solid facts to help debug a problem in this posting......
The next step is going to be a strip back - clean install, slow addition of apps. In the meantime can anyone identify any issues they've seen with any particular apps?
planetf1 said:
I have an I9505 running lollipop and struggling to address intermittent lag.
Broadly speaking the phone starts off working well, snappy.. but after a while can start to lag. By this I mean a press on the home button may result in a 20s+ delay for the task manager to come up. Switching a task may be slow, the keyboard may take 10-20s to appear, the screen may be mostly blank for a while. It doesn't crash, and does "come back" but it's nearly unusable. Usually once switched to a task and settled down scrolling is ok. then it may work just fine, snappy for a while
I don't see oddly high figures in the various stats I can see - cpu time isn't excessive. memory is harder to interpret and at times I do see kswapd busy just after a wakeup.. so my suspicion is it's a memory leak but one I can't prove
I've tried alternative kernels - hulk, imperium, and they don't appear to help matters at all.
The lollipop build was clean & Current firmware is I9505XXUHOD7, BTU
I am rooted and have progressively disabled various packages I don't use in an effort to lighten the environment
I've disabled animations (a cause of memory leaks in 5.0.1, though supposedly not affecting samsung touchwiz)
I am a software engineer and very familar with better battery stats, gsam, even a quick peruse through dumps via adb yet still haven't got to the bottom of my issue. I'm also very aware there's little in the way of solid facts to help debug a problem in this posting......
The next step is going to be a strip back - clean install, slow addition of apps. In the meantime can anyone identify any issues they've seen with any particular apps?
Click to expand...
Click to collapse
I should add that I did previously use CM12 and that left a little laggy too, though not tried CM12.1 . The two factors holding me back - a) better/reliable camera in TW b) Beep'n'go - love the app. works everywhere unlike every other loyalty card app I've tried (uses proximity sensor pulsing, Samsung TW specific)
planetf1 said:
I should add that I did previously use CM12 and that left a little laggy too, though not tried CM12.1 . The two factors holding me back - a) better/reliable camera in TW b) Beep'n'go - love the app. works everywhere unlike every other loyalty card app I've tried (uses proximity sensor pulsing, Samsung TW specific)
Click to expand...
Click to collapse
Hi,
try to disable swap devices, if there is any. If I know well, stock Lollipop ROM uses compressed swap devices in memory, like in stock KitKat ROM (zram).
In a terminal/shell:
- List currently used swap devices:
Code:
cat /proc/swaps
- Switch to root:
Code:
su
- Disable swap devices:
Code:
swapoff /dev/swapdevice
or if you have Busybox installed:
Code:
busybox swapoff /dev/swapdevice
Where /dev/swapdevice is the swap device/partition, which you want to disable.
It's the best to do this in some kind of init.d scripts before the system starts.
I am on still KitKat+rooted, but this should work on Lollipop, too.
Good luck!
planetf1 said:
The next step is going to be a strip back - clean install, slow addition of apps. In the meantime can anyone identify any issues they've seen with any particular apps?
Click to expand...
Click to collapse
I think this is the best thing to do. I suffered a weird wifi issue that no else had. A fresh/clean install of the same lollipop ROM and kernel fixed it. Haven't noticed any apps causing lag on lollipop.