Hi All,
I've got my HD+ running CM10.1 using the emmc method (works great by the way, really smooth and responsive) but the device seems to be rebooting overnight when left plugged in and charging.
I used to get quite a few reboots with CM10.1 using the hydrib method as well (emmc seems far more stable for me).
Is there anyway of debugging what might be causing the reboots?
I just left chrome running last night so I could see if it had rebooted by the time I got up.
Thanks
Paul
BigMacca said:
Hi All,
I've got my HD+ running CM10.1 using the emmc method (works great by the way, really smooth and responsive) but the device seems to be rebooting overnight when left plugged in and charging.
I used to get quite a few reboots with CM10.1 using the hydrib method as well (emmc seems far more stable for me).
Is there anyway of debugging what might be causing the reboots?
I just left chrome running last night so I could see if it had rebooted by the time I got up.
Thanks
Paul
Click to expand...
Click to collapse
It is probably an installed app. I have no reboots. I would suspect chrome, which I don't have installed.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It is probably an installed app. I have no reboots. I would suspect chrome, which I don't have installed.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks for the reply .
Is simply having the app installed enough to cause issues or does it actually have to be running?
BigMacca said:
Thanks for the reply .
Is simply having the app installed enough to cause issues or does it actually have to be running?
Click to expand...
Click to collapse
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Cheers mate,
I've found where you can check to see what services are running, I'll start shutting things down and do a little trail and error over the next few nights to see if I can track down which app is the culprit
leapinlar said:
Some apps run services in the background even if not active at the moment. It may be one of those.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I still seem to be having reboots now and again (never whilst actually using the device though...)
It's no the end of the world as the only way I can tell the nook has rebooted is that there are no apps loaded when I go to use it, but I've not been able to track down what app / apps are causing it yet.
Is there any kind of debug logging I can get at / enable?
Cheers
Macca
Related
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
excalibar001 said:
I am opening this thread for people to discuss issues with the CM10.1 and share solution and fixes that they have found to solve these issues.
I have noted that the auto brightness does not work for me. I do not notice any change in brightness in different light settings and it seems to be frozen. Does HD+ comes with a light sensor and is it supported by CM10.1.
Another thing I wanted to ask. Can we use MHL adapters to connect a Nook to a tv through HDMI. I was looking for an alternative to Nook branded adapter.
Thanks
Click to expand...
Click to collapse
I'm pretty sure there is no light sensor on a tablet that has no camera.
Overall CM 10.1 is a whole lot better than stock 2.1. Some games do not work that did with stock (Buggy Blitz, Moonshiners and NBA 2013), but all the Zen Pinball Star Wars games work (they did not with 2.1).
With CM 10.1, you can not get any more less intrusive with Android, especially compared to stock on the Nook HD+. The good news is there is no more stutter with apps and a lot of apps load faster. The bad news is some apps still load slow and there is intermittent lag when pressing to start apps or navigate. Tapatalk is an example. There can sometimes be a 5 to 10 second delay from the time the app is activated to the time there is an action. Same with navigating and with other apps as far as lag such as browsers and games. The weird thing is when games play, there is no lag or signs of touch response problems. Games play well and so do virtual pads for game emulators. The issue is not touch sensitivity, since the press registers, but sometimes takes a while before an action happens.
For whatever reason, the Nook HD+ has an intermittent lag problem that also existed with stock 2.1, though the app stutter has thankfully gone away. The lag really stands out when comparing to my S3 and Excite 7.7. Those both are stock, but respond instantly when activating and navigating apps and only have slight issues if updating apps in the background.
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Bad memory management, perhaps? Added: Nope, if so, games in action would be laggy as well.
channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
You are right, there is no light sensor so autobrightness does not work.
Sent from my Nook HD+ running CM10.1 on emmc.
rushless said:
My Razr had a 4430 and was not laggy. The higher display res should not be a factor for such dramatic lag issue with the HD+. The lag seems to happen about 30% of the time, if I were to guess. For what I want it for, the lag is not a big issue, but seems to make no sense. Both HD+ I have used have the issue, but was hoping CM 10.1 would be the answer to fix it.
Click to expand...
Click to collapse
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
Tapatalk seems to be a poster child app for the issue. It does seem like a wait state issue. Added: That said, it does not do it all the time, so probably not app specific. I just use Taptalk a lot. The lag seems to happen with most apps, but not all the time. 30% of the time seems about right. The good news is the stutter issue that was them main problem IMO with stock 2.1 is gone. No sign yet, in spite of the intermittent app start and navigation lag.
What app can I install to log the issue?
Thanks
rushless said:
What app can I install to log the issue?
Click to expand...
Click to collapse
I don't think there is a good one for logging.
I just need to be able to reproduce myself so I can poke at it from multiple angles.
It does seem to be an app start/stop and navigation lag. No lag when using touch or virtual controls in games.
Not having the stutter in the GTA games is nice. It was GTA Stutter City with stock 2.1. as in many other games. Smooth now, while playing a game.
channeledbymodem said:
I'm pretty sure there is no light sensor on a tablet that has no camera.
Click to expand...
Click to collapse
While I agree that HD+ may not have a light sensors, however, a light sensor has nothing to do with camera and primarily used to control the screen brightness. A camera can detect brightness through its image sensors which is separate from a light sensor.
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
verygreen said:
I need precise steps to see the lag, then I can profile it and if stars align right - fix.
Hashccode encountered some bad lag on KFireHD on (what he thinks) is some bad unnecessary waiting in kernel.
I do not see any of it, though, so cannot do anything about it.
Click to expand...
Click to collapse
I would like to thank you first verygreen for your efforts. You have made the HD+ such a useful tablet.
I have noticed that sometimes my screen would turn off momentarily for no reason. This happen more frequently when I am using and charging he tablet at the same time. I believe that it is due to the magnetic cover flap sensors which goes awry for some reason. Is there a way to turn this sensor off for those of us who are not using a cover with magnetic flap?
rushless said:
Does stock firmware have auto brightness setting? Can not remember, but I thought it did.... I tend to not use it.
Click to expand...
Click to collapse
No, as many have said here, including me, there is NO hardware sensor, so auto brightness cannot work.
Sent from my Nook HD+ running CM10.1 on emmc.
As mentioned, I do not use it, but would not be the first time for a phantom setting. Look at stock 2.1 and the slow app loading, stuttering state that it is. Not exactly a model for strict user experience QA.
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Not had a random reboot yet.
Must be some misbehaving apps since I have never had random reboots. However, my screen flicker once in a while if I charge and use it at the same time.
mrpunk2u said:
Getting about 4 or 5 random reboots per day but everything else seems fine. Using greenify to hibernate apps
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You might want to check to see if you have GPS checked in location services. If you have that checked and an app like Google Maps runs in the background, that sometimes causes reboots.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
GPS is off - not sure what's causing it - Also, i keep getting Google Sign in errors and asks for my password at least 2x daily
Intermittent lag aside, I use the Nook now more than the iPad 4. Same nice display clarity and not locked down.
Wild how an OS mod can change perspective on a device so much.
My biggest problem has been with touch, it's not that responsive sometimes and sometimes I have my finger hovering over a button and it clicks it (is that phantom clicking?).. Overall it's MUCH better than stock and mad props to all the developers. My girlfriends tablet has been getting random reboots as well, i'll check to see if GPS is on.
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm doing this right now. I just got the N+ with the 06/15 emmc build. It certainly does not feel as smooth as the Nexus 7 around the Launcher and apps: it feels like the whole system is running at 20FPS(exception is Boat Browser, Youtube, and other minority apps). I'm still looking at this time hoping that the higher resolution isn't the limiting factor on the OMAP4 hardware.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks Leapinlar! :good:
The post that is most meaningful in for this issue in that thread is #834:
http://forum.xda-developers.com/showpost.php?p=42645288&postcount=834
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Tom2112 said:
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Click to expand...
Click to collapse
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
That's useful to know about the recalibrate app, I may use in the future.
This is a bit obvious but I've found a good clean of the screen helps.
srgibbs99 said:
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
Click to expand...
Click to collapse
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Tom2112 said:
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Click to expand...
Click to collapse
Thanks Tom, i have noticed that having fingers/screen very clean helps.
Open up the developer options in settings and enable "Show touches" and "pointed location." Use the device with these options on to see a trace of how the touchscreen registers your touches. You start to get an idea of how sensitive the touchscreen is. You can also clearly see why some touches don't register sometimes. I touched the screen to click a button but it thinks I want to scroll because the trace shows I made the slightest of a line when I pushed down on the screen.
Sent from my Barnes & Noble Nook HD+ using Tapatalk HD
I installed a matte/non-reflective screen protector on my Nook HD+ because I had read elsewhere that it would help the touch sensitivity issues.
It didn't. So I will probably remove it.
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
bckrupps said:
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
Click to expand...
Click to collapse
Thanks! I will check it out.
Here's a link for those that find this thread first:
http://forum.xda-developers.com/showthread.php?t=2347003
I found on my Nook HD+ that when the touchscreen starts acting wonky like this it wants to be cleaned. *Especially* ( and sometimes only ) where the glass meets the bezel. I wrap the cleaning cloth around my finger and angle my nail in at about 45 degrees, and gently but firmly 'scrub' around the bezel edge. I can actually feel a buildup there physically from the varying friction of my movement. After that is starts acting like it did ootb.
Tom2112 said:
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Click to expand...
Click to collapse
I'm on CM10.1 too and faced the same tapping lag - third time is very slow. I lost almost 40 hours of testing, testing and more testing of this nasty lag and there is no result for now, maybe it's some option in the phone that eliminates the lag but I can't find it for 40 hours... But I'm sure for one thing - if the slow tap is ALWAYS the third time, then the reason is some setting. There is nothing in your hardware/performance, be sure about that. Just searching for solution......
Hi,
On a Nook HD+ 32GB CM10.1 (6/15) on emmc. I am getting random reboots, perhaps once or twice a day. Is this normal ?
Thanks
I ran that build for about 1 week and had 2 or 3 random reboots total. I am currently running killersloth's Carbon ROM for about 24 hours, and so far no reboots. Not a lot of data to go off yet. The devs are doing awesome and I can only think (hope) it will continue since there are so many Nooks flooding the market right now
I've had quite many android devices (all on customROMs), so I've seen many unexpected reboots.
But no reboot is considered normal.
I flashed the same ROM on six different HD+ (all 16GB, from 5 different stores. Three are mine and other three are for my friends).
I've never seen (or heard complains about) an unexpected reboot.
For my own HD+, I tried CARBON B1/B2 and now back to latest CM10.1 and still haven't seen a reboot.
Maybe some app you're running ?
Usually caused by being overburdened, out of memory. Unfortunately most people report this as "random"
I haven't experienced an unexpected reboot on the HD with verygreens cm10.1 or with my carbon build. However I never keep going if the device becomes sluggish, I let it finish whatever task I told it to do that's using up all the available memory.
Sent from my Galaxy Nexus using xda premium
I've actually switched from CM10.1 EMMC (last build I tried was early August) to CarbonRom (B11).
I don't know if my Nook HD+ was over burdened, but I've seen it charging on my desk and it decides to reboot. I started "tracking" the reboots and noticed that they happened fairly often (once a day or more some times). I'd open Chrome and Nook reader just so they would show up in my recent apps menu. Then I'd leave it and check it later, sometimes the recent apps would be empty which means at some point the tablet rebooted.
Regardless, Carbonrom works well for me since I'm not usually doing anything critical with my tablet just email, web browsing, and reading.
Occasionally I'll bust out FreeCell or Trapped as far as games go. The best part is that I'm not getting the reboots.
Not sure what was happening with CM10.1, but I'll probably give it a shot again when 10.2 isn't experimental because I do like the Trebuchet launcher (which I can put on carbon, but Trebuchet crashes when I try to change the number of screens and a few other settings).
My Nook also randomly reboots. Just lying on the table without me touching it, or when I read comics or surf the web. It does seem *completely* random. I am beginning to think it is a hardware issue B&N cannot fix.
I was using EMMC Carbon B11 for a time in my HD+ because it offered the Tablet UI among other features. I also experienced occasional unexpected reboots while using that ROM but their low rate was nothing that made the ROM unusable. A few weeks ago I switched from B11 to a 4.3 EMMC ROM from iamafanof that also offers the Tablet UI and seems in my experience so far to have noticeably fewer unexpected reboots or restarts. For anyone who is experiencing "excessive" reboot rates using another ROM, iamafanof's 4.3 ROM might be worth a try. He also has a 4.3 ROM for the Nook Tablet. His ROMs can be found at his WordPress.com page.
Hi All,
I was experiencing random reboot issue on my Nook HD+ for a long time.
Only thing that helped is rooting my device and installation of CPU with max frequency 1300 MHz. I haven't noticed degradation of performance but reboots went away.
I assume root cause was CPU overheating
Hope this will be useful for someone
Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard
wahidx said:
Hi,
I have a NOOK HD+ (with CM 10.2 stable), my device reboot very very often, i don't think it is normal and would like if a expert check my last_kmsg.dat and tell me what is going wrong on my device.
I also set my CPU @1300MHz to avoid overheating but it doesn't helped
thanks in advance
btw. I don't use a SDCard
Click to expand...
Click to collapse
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Edit:
Also here's an example of omap thermal opp throttling.
http://pastebin.com/gA2vFt1e
(this was before I reduced the voltages)
Jon Lee said:
Yes. I was seeing this one a lot on CM10.1.3. Definite kernel bug.
I made some kernel changes to /drivers/mmc and haven't seen it since.
If you want to try it, check out my 'overclock omap4470' thread (use one of the last two kernels; I made the touchscreen I2C fixes and mmc fixes at the same time).
FWIW this morning I had a random reboot with ABE Power Management (first reboot in awhile though). So I'm trying to chase that one down.
Click to expand...
Click to collapse
Thx Jon for replay, i will try that and report how that gone
btw. can i use your kernel with CM10.2 or should i downgrade to CM 10.1.3 first?
Using stock Nook HD+...everything was working fine for a few weeks, but now scrolling (in firefox, chrome, etc) is jerky. Killing apps didn't help. Rebooting didn't help.
Any ideas?
ntice said:
Using stock Nook HD+...everything was working fine for a few weeks, but now scrolling (in firefox, chrome, etc) is jerky. Killing apps didn't help. Rebooting didn't help.
Any ideas?
Click to expand...
Click to collapse
You are probably suffering from need of an emmc trim. It is akin to defragging on a PC. But the issue with some HD+'s is you can brick your device doing that as some HD+ emmc chips are buggy. Read about this in the CM10.2 thread.
I don't know if this will help or not, but you could try going to my HD/HD+ CWM thread and make a bootable CWM SD, backup your device, and do an immediate restore. That re-writes everything to emmc. Then see if it helps.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You are probably suffering from need of an emmc trim. It is akin to defragging on a PC. But the issue with some HD+'s is you can brick your device doing that as some HD+ emmc chips are buggy. Read about this in the CM10.2 thread.
I don't know if this will help or not, but you could try going to my HD/HD+ CWM thread and make a bootable CWM SD, backup your device, and do an immediate restore. That re-writes everything to emmc. Then see if it helps.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Do you mean the trim is buggy on the hardware side of nook hd+?
I also experienced the slow down on stock rom and today flashed to cm10.1.3. smooth so far with occasionally screen flickering (going black and come back on). Is trim supported in cm10.1.3? And if not, can we run the lagfix in the playstore?
loveleo said:
Do you mean the trim is buggy on the hardware side of nook hd+?
I also experienced the slow down on stock rom and today flashed to cm10.1.3. smooth so far with occasionally screen flickering (going black and come back on). Is trim supported in cm10.1.3? And if not, can we run the lagfix in the playstore?
Click to expand...
Click to collapse
You can run the one from Play Store, but I'm telling you that the internal memory chip may be buggy and you could brick your device. It is a problem with the hardware.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You can run the one from Play Store, but I'm telling you that the internal memory chip may be buggy and you could brick your device. It is a problem with the hardware.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Sure do not want to risk bricking the device, not worth it. Maybe doing back ups and refresh every a few months then. Hardware problem usually means there is nothing we can do though. Too bad.
I don't think scrolling has anything to do with the storage (everything is in RAM after all). It's like some internal Android graphics setting got changed somehow. Could an ordinary app make a permanent change like that?
Deleted. Question posed in a new thread.
ntice said:
I don't think scrolling has anything to do with the storage (everything is in RAM after all). It's like some internal Android graphics setting got changed somehow. Could an ordinary app make a permanent change like that?
Click to expand...
Click to collapse
Actually it could very well do with not trimming flash RAM, as lots of things go one in the background, including reading from/writing to DBs. After I did CWM backup/restore, my Nook HD+ 16GB was a lot smoother on browser/launcher/etc. What a sucky eMMC bug.
I've reflashed my new Nook HD+ with CyanogenMod 10.1.3 stable and for the most part it's working great. However, occasionally when using the Apps screen, for some reason I get "stuck" there. The Nook button and soft Home button stop responding and won't take me back to the Home screen. Has anyone else seen this? When this occurs, is there anything I can do to get some debug info for the developers? Thanks.
PS: While I'm very technically competent in most computer areas, I'm a complete noob to both Android and CM, fair warning! I do know Linux though.
Try a different launcher like ADW or Nova.
Sent from my Nook HD+ running CM10.1 on emmc.