Related
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
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.
Hey guys,
I've test ICS and came across the need to do a supercharge.
Now I'm back to CM7.1 and I've been wondering what the method is to get it supercharged as well (and 7.2 KANG along the way).
The shell script part is pretty understandable, but I'm unable to understand whether or not I need to replace services.jar in the update zip. If I do need to do so, then which services.jar file do I need to put in there (there's a quite a few and some of them didn't work for me when I jumped and tried to do it myself).
Thanks in advance.
I made a guide for supercharging ICS with the proper services.jar for the nook here:
http://forum.xda-developers.com/showthread.php?t=1508481
Works like a charm, really.
If you want to use the script on any version of CM7, the ROM needs no modification. Leave the services.jar as is. The guide still works, skip to step 5 but just remember to unselect Lock Home in Memory in the device settings.
Look at the second post if you would rather the short and sweet version. The top post attempts to explain exactly what you are doing to your device and why.
Thanks for the quick reply.
It just so happens that I have followed (and bookmarked) your guide when getting my ICS
Unfortunately, I have tried the 3/3 Opengl and it had many lockups.
Any ICS you would recommend? (I know it's a bit off-topic, sorry).
Yeah, I know what you mean. I can't run OpenGL on a daily basis yet either. But the b
Yeah, I know what you mean. I can't run OpenGL on a daily basis yet either. But the builds without OpenGL work great. The threads can be a little hard to follow, what with their length and all the custom zips, I know, but he actual builds themselves are great.
I kept going back to 7.2 after checking in and trying a nightly. But maybe ten days ago, the audio from Nook Tweaks got patched, and know I can listen to movies and music at an acceptable level and I realized it was ready enough for me.
Really, the last thing on my list would be an enabled net filter, to run a firewall. But I am super-impressed with ROM.
Hope that helps. Just all of a sudden, it seemed ready.
Just to clarify, you're satisfied with the 3/3 rom w/o opengl?
Sent from my NookColor using XDA
Yep, I have been testing a bunch of programs on ICS over the last three weeks or so, and while flashing the nightlies over that time, the last couple things that I needed came through the repo. When the patch for the audio boost in Nook tweaks came through, I could use the movie and music players and finally hear them, which was a huge gain for the users. The VPN that I use works, Sync works. Almost every system app has been greatly improved.
Don't get me wrong, there are some big holes to be filled. Flash works only with OpenGL, which I find still to be too buggy and slow for daily use (although some have been reporting fine daily use), and I can't seem to find a firewall that blocks apps from the internet, which is a pet issue of mine. If you want to customize your launcher and overall look and feel, then those features will likely be the last to come around. I don use YouTube and the like hardly ever, but nonHD videos play only.
The progress is brisk, though. I spend maybe fifteen minutes upgrading the nightly as I go to bed at night, the builds seem to add a huge chunk of functionality every day.
One last tip I only recently discovered: people have complained about battery life, but I found it mostly analagous to cm7 with the major exception that deep sleep seemed fitful at best. I just realized that deep sleep doesn't seem to work when I shut the screen off manually. If I let it time out naturally (if it can be said to be natural, then it sleeps with no problem. Now battery life seems totally acceptable.
Just depends what you need to work, I guess, but this is my only real computer when I am away from home for work, and I use it daily now.
Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey
voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey
voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'
I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey
voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.
voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.
Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey
Hi, I'm really sorry if this is considered cross posting, but I'm starting to get desperate here and really need help. I'm on a deadline and running out of time, I need to figure this out somehow and have been bashing away for almost 24 hours now.
My question is in this thread - and is the last post.
I am actively online and working on this. I'm starting to consider just reverting to stock from the recovery partition and then building everything from scratch, but if I can avoid that time vampire I would like to. Does anyone know what's going on, have some ideas, or anything?
Next step, I'm going to try the 1Gb 5Gb repartition that Dean originally developed. Though with my Nook broken already and my inability to restore it to a working state despite having a ton of perfectly fine Nan backups, I have doubts as to whether anything will change there.
I'll monitor both threads. Thanks in advance for any guidance/help.
Edit: Still plugging away, last steps mentioned above didn't work. Next steps: I'm reading Leaping Lar's partition fix thread and getting some ideas. am going to try:
Flash Partition > Boot to CWR
Format > Flash to CWR
Flash Dizzy Den's signed 4.1 zip > Boot to CWR
Flash my Registered Nan backup of Stock 4.1. > Boot to MMC, get a look around
I think I already did this, but left out the last step. Might work as it should restore my registration data instead of starting me from an unregistered account. If it seems worth trying at that stage, I will then flash my registered Nan of 1.4.2 and get a look at that.
Speculation: I just realized, I've been trying to restore a backup of a rooted 1.4.2 over an unregistered 1.4.1 - which is what I keep getting reverted to. I don't know if that matters, but my hope is if I flash my registered backup over what I'm reverted to, then build up to registered 1.4.2, that will help things... We'll see.
Failing all of this, I will try Leapin' Lar's partition repair.
I have finished reading the Partition thread I linked to above (where my original post is) and found that one other person reported my issue, almost to the T. His/Her user name is Blondie. Blondie seems to have quit without a fix, or if ever got a fix it was never posted. It was quite some time ago, but if any of those who helped him/her can remember if there was a fix would you let me know what it was?
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
sagirfahmid3 said:
Screw the original nook firmware. Go install CM7 Mirage ROM.
Rooting a stock nook is pointless. CM7 is better, faster, more efficient than stock and it comes rooted by default.
Now that your serial number is probably gone or corrupted in the /rom partition, you most likely cannot register your nook with the B&N servers, and that is probably why you can't install apps.
If you need a complete partition table wipe, follow this guide. http://forum.xda-developers.com/showthread.php?t=1759558
Next time you decide to mess around, be sure you backup your ROM and factory partition before doing anything.
Click to expand...
Click to collapse
I do have backups of everything. As I said above, they aren't wholly functional.
I never said I was completely unable to install apps, or that I couldn't register with B&N. I can register fine, and in some scenarios I can indeed download my apps just fine, just not if I try and restore a MN Nan backup. That is not because of a missing SN but because of a registration issue that can be caused by the MN process - otherwise I would not be able to download them at all in any scenario.
Also, if you know the MN process you know my factory partition is intact. Perhaps the partitioning messed with it a little, I'm not sure - but nowhere did I say I have yet tried to reset to stock from the factory partition, so we have no real way of knowing yet.
I understand that my OP is starting to get tl;dr because I don't want to double-post, but actually reading what has been done so far and reading the post at the original thread I linked to might be more useful in trying to give people advice. A little less snark would be useful too, I am not a n00b at this by a long shot and talking down to people tends to get hackles up instead of being productive - especially when you clearly haven't read their thread - as an example, if you had read it, you would have seen I already know about Leapin' Lar's partition fix and it's one of the next things I plan to try..
On the other hand, I may take your suggestion about installing CM7 Mirage. Honestly, I had my reasons for not doing that in the past, but those reasons are largely moot today. I will get a look at the thread. Thank you for the suggestion.
You're right, I apologize for not reading thoroughly. I had a derp moment.
No worries Sagirfahmid, I owe you an apology too. I'm sorry to have jumped on you, I am a little bit... stressed, and tired. Not that it's any great excuse. I need to take my own advice about talking to people. Sorry.
And fwiw, I believe you are right and the original partition did mess with the factory partitions, I've just been avoiding facing it. I really ought to get off the fence and run the repair and then follow Dean's guide to using fdisk on the emmc, but I'm getting OCD about trying every other thing first - even down to considering a flat reset to factory and rebuild from scratch. Stupid, I know.
Thing is, there is at least one other person out there who had this exact problem, and it didn't sound like her issue ended up being a corrupt partition as the partition repair didn't help her. Unless it was too corrupted. I know there were a lot of people running the same system as me, and it was very stable. Someone besides me and one other person has to know what this is and how to deal with it. That's what I'm hoping anyway. LOL
And seriously, thank you again for the reminder that there are other options out there that might better suit me now. The more I read the more I think if I can just reset the darned thing to a fully working state, I may well just do an SD CM10... or should I just stick with Mirage? Is there an advantage to Mirage over 10.2?
Yes definitely. It's faster--that's the most obvious advantage. (I disabled all the fancy animations and removed a lot of useless system apps like the phone, contacts, calendar, camera, and GPS app via adb).
Also, CM7 Mirage has USB host mode, so if you get a male microUSB to female standard USB port, it is very possible to use a keyboard or mouse, or a flashdrive or harddrive (if you get a powered hub). AFAIK, the max current it can supply without a powered hub is 100mA (enough for a flashdrive or keyboard/mouse that isn't too fancy--skip the ones with LEDs; each LED uses around 15mA).
Oh yeah, CM10 runs in phone UI (there's an extra bar on top taking up space).
In CM7, there's only 1 bar, so you have a bigger area on the screen. Of course, there is a patch to get CM10 into tablet mode, but I don't like all the hassle.
On CM7, you can overclock the CPU to 1.2GHz, but on CM10, it's limited to 1.1GHz AFAIK.
=====================================================
Right now, I'm hoping to get Debian ARM natively installed on the Nook Color. I've been making progress thanks to the devs and users here. Android is still required, but it will be on top (instead of the other way around, which is Android on top and Debian chrooted). SInce they'll be using the same kernel, I think I can get Debian to use the Nook Color's USB port to connect devices like printers or scanners (that would be so awesome...).
If you're interested in running full blown Debian on the NC, and assuming that you are able to fix yours, you can check out this thread: http://forum.xda-developers.com/showthread.php?t=2422518
Solved
Sorry for the double post. Need to separate this from the wall o text above. Problem is solved and since I never did find a spelled out definite answer while I was reading the last 2 days, I want to post it here where someone who might be looking in the future might easily find it.
To reiterate the problem concisely for those who don't have time for the diatribe above:
My device is a Green dot Nook Color:
* Running a stable Manual Nooter 5.08.20 over a Stock B&N 1.4.2 ROM, and using > This < method to block OTA Updates - basically use a SQLite Editor for Andriod to modify the fota mode in the nook's registry.
I recently started getting the Low Memory message asking me to please archive some of my apps to SD. Am about to go on a long trip abroad and I not only needed what apps I had but also need a couple more. Solution: Repartition the Data and Media partitions.
Full backups: have a whole slew of backed up NC B&N Update zips, Flashable updates created by several awesome people here, and step-by step Nan Backups of every single time I have re-rooted my device after a B&N Update - signed and registered stock configs, roots and final images, and finally a whole store of dated backups of my Tibu backups off of my SD card.
So, I repartition following steps exactly.
* At first reboot, CWR freezes on load. This makes me thing something went horribly wrong.
* Reboot again, everything seems to Format fine, reboot into Nook
* Unlike most people, my nook has reverted to an unregistered stock 1.4.1, no root.
* Flash my latest Nan-backup of my rooted NC, doesn't take properly and B&N is a mess because (duh) I didn't register it before flashing - But I shouldn't have needed to because all of those settings were in my Nan Backup. Okayyyy... weird.
* Flash back to a Registered stock NC nan backup of 1.4.2 since that was the last version I used. I was able to DL books and read them, and could DL apps - but my apps couldn't install at all and there were a couple of new B&N Apps that were stuck in a DL/Install loop too. Hm.
* Flash an earlier root Nan over that. Now my Nook can't download anything, I get an error message that it cannot execute. Lovely.
* Bash around in this fashion trying to make it work, occasionally trying different partition schemes in the process, while reading every thread I can find on the subject of what issues I'm having.
I begin to suspect that my partitions might be all messed up, especially considering the original freeze from CWR, but have no real way to check that and don't want to give up, so I post in the instruction thread and later here to see if anyone has any guidance or knows what this is.
A whole slew of people have endorsed this method and had no problems.
A few people had some problems, but only one user has reported exactly my problem off of the exact build I was running, no less. (1st link is that user's first post and 2nd is the page where her posts begin). However, that thread ended with no real answer - or so I thought.
At once point before the issue ended with no further response from the poster with the issues, Leapinlar (who had been assisting her, or at least trying to) tells her that if his Partition Repair didn't solve anything, then it likely wasn't the problem. If she cannot get her B&N Apps to DL & Install, then it's most likely the version of the B&N Stock that she is on and she needs to flash to the most recent - he even points her to a signed CWR Flashable one that he created for 1.4.3. She argues that can't be the issue - and I get that, because the apps installed and worked before in 1.4.1 right? So why all of a not now simply because she's back on 1.4.1 again?
I don't know why B&N would have made it so that you can't install any older apps on your device even though they installed on older ROM versions, forcing people to move up to 1.4.3, but it appears to me that this is exactly the case and Leapinlar is once again correct.
Took me a long time to internalize that and have it click. After running his Partition Repair with the same results as her, I left it on a registered 1.4.1 Stock, put the NC down and stepped away for a while to do other things. when I came back I was fixated on what Leapinlar said about flashing to a newer version of B&N Stock. So I did. And when that didn't really fix it I flashed up to the next ans last version, 1.4.3.
Hallelujah, problem solved!
For my own apps to download, I had to wait for a couple of new ones sent to Nooks from B&N for version 1.4.3 to download and install - and they were not able to do that on earlier versions. I propose that their inability to install was what was blocking my other apps. but it could be that the others were also made version specific once B&N stopped making NCs in favor of HD's and the Tablet, and released the final update.
Regardless, that is the final answer. If you are on MN and repartition, and then find when you boot you are taken to unregistered stock, and upon registering you can access your books but your apps will not install after downloading and you have a couple of new ones that seem stuck at dlownload and install, all you need to do is Update your NC to the final release, 1.4.3, and the re-root. I think you will need to re-root from scratch, unless maybe your last root backup was from 1.4.3 - which mine was not.
Next dilemma: Stick with root or start running a CM ROM from SD...
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because:
1. B&N wants you to REGISTER with your CREDIT CARD to be able to actually USE the Nook Color. Why the hell?
2. B&N possibly has BACK DOORS to your Nook Color. They might DRM lock apps or something. They can obviously force updates onto their users unless they root. They might also decide it's time to brick your tablet if they wanted, so you would go buy another one (yes, this is more of a conspiracy theory, but hey, if they can force updates, they surely can also do this).
3. B&N's custom Android is crippled unless you root. You can't use the 5GBs of space. Why the hell not?
etc etc...there are more reasons I don't stick with any stock firmware, be it for a tablet or phone.
(I use Debian on my computer most of the time now because Windows is a piece of crap. You can't do whatever you want on it, except game. Did I mention the useless startup services and apps you need, especially antivirus, for Windows to function without worries of getting a keylogger or some nasty virus? Valve has made Steam for Linux very usable, and I rarely use Windows for gaming now. Linux is tons faster, and I can do almost anything on it).
Have you ever used a T-Mobile smartphone? the apps that come installed are numerous! It makes me want to puke every time I use a stock Android phone from a phone company. I like and want my devices to only contain the apps I want. That means NO BACKDOORS, NO FISHY BACKGROUND PROCESSES, NO **** APPS, NO RESTRICTIONS.
======================================================
Backup the documents and whatever you have on your B&N firmware. Install CM7.2 Mirage onto INTERNAL SD card.
Stop being a wuss :silly: and start enjoying a better Android experience.
sagirfahmid3 said:
I'm a cheapskate, that's the truth. I am a geek, I want to do **** with my devices and I don't care if I end up bricking them so long as there are ways to recover. I also care about my privacy. I don't stick with the stock firmware because....
Click to expand...
Click to collapse
I completely understand! I have many of the same concerns and make workarounds and otherwise try to frustrate the usual 'Big Brother' tactic that are becoming so prevalent. I don't think you've gone into the realm of conspiracy theory at all, what you're talking about is a long term goal I think. Think of the marketing and capital profit possibilities of that kind of control over a still largely unregulated market - 'largely unregulated' because the technologies and the possibilities they allow are evolving so quickly.
I also am a 'computer geek', prefer control of my own devices and am very strict about personal security. So then why does B&N have my personal data? Largely because they had it far earlier than there was ever a blip on the tech radar of 'e-readers'. I'm also incredibly bookish and there haven't been a whole lot of B&N in my region, but I prefer their company as a book retailer, so I was a member that had begun ordering from them online as soon as they had a website to order from. So, it wasn't a huge loss for me to keep the stock and use it as intended. here are some things about this that do grate with me, yes, but they wouldn't have lost my data history anyway, so wth, I might as well get a really elegant e-reader interface from a company I mostly like and support. This is definitely not a situation that applies for everyone, I know.
I use windows on a secondary boot partition and funnily enough, largely for gaming. I also use it on a work laptop because I have to. I run Suse most of the time, myself.
As far as DRM, it' something we need to fight in the courts and through making our own backups for experimentation, and that's all I can really say.
When I bought my NC over two years ago, tablets were still pretty uncommon and e-ink readers all the rage. I splurged on this even though I was still using a flip phone because I felt it would serve multi needs well:
a) The need for an e-reader (I travel at least 1ce a year and I read a lot while traveling. Books are HEAVY! and I'm getting oilder...)
b) The desire for an e-reader that could read color and comics - so I could DL comics and fan creations and manga as well as books on the same device - and one that isn't an Apple (I dislike Apple as much as I dislike MS).
c) The desire to have a good interface in a size that is more readable than most phones on the market, to surf the web on or read the above during my long commutes.
d) The desire to have all of the above in one item that would also not tie me to a single seller - in other words I also wanted to run the Kindle App and Google books.
At the time, Kindle Fire had not been released and the next best machine (actually, tied as of the time I bought this nook) was an iPad. Other tablets out there were more expensive and glitchy and without that quality - some didn't even expect to ever update their android ROM. There was nothing on the market close to the NC in that price range - and I knew I could root it or otherwise replace the original ROM if I didn't like it, to do what I wanted, and essentially never brick it!
I chose MN over CM or Nightlies because I didn't have to mess with the factory partition at all or ever worry about replacing it, and it let me use my nook directly from system in a two-sided boot that had a tablet on one end and a Nook on the other. Very neat. I got the 3 yr warranty when I bought it because at that time they stated that you could return the NC within that time for a lower price on the next new thing. I plan to use that, so I wanted the original factory partition intact.
There are only two things today that would keep me from running a CM install or SD right now. The most important of those two is Battery Life.
The trip I'm about to go on is to India from the east coast of the US. We'll be gone about a month and my NC/Rooted or flashed tablet will be my ONLY mobile device. I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case? We will have a lot of devices to try and keep charged, one plug adapter, and the NC will have a central role in our keeping in touch with family and friends. We we go for a day without a charge but with about 8 hours of use including wifi time on a MN root, I know I will still have enough charge the next day till we get to the next location where we can try and charge everything.
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
I am still interested in running CM, can you point me to info on these? For the second, I need to link to Canon Image Gateway wirelessly and also a Bloggie. I love that CM7 can run a USB interface! That's a huge advantage that I could use!
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
As to smartphones... LOL. I still have a pay-as-you-go flip phone, wanna talk about being cheap and having security paranoia? XD Seriously, I spend a lot on my computers - which I prefer to build - and spent a lot on my tablet back when I bought it and when I replace it will consider carefully and spend on that again. =) Smartphones? I will get one eventually, it's a matter of time, but I'm holding out as long as I can. LOL
...I need something stable, and that if I am not already familiar with it will be fairly intuitive, and most important - Good Battery Life. As far as I know, the CM ROMs for NC are energy hogs - is that still the case?
Click to expand...
Click to collapse
Nah, CM ROMs have great battery life these days. I get 10 hours on my Nook Tablet (CM10, 4700mAH battery AFAIK); 8 hours on my Nook Color (CM7, 4000mAH battery. Obviously, it's going to have a slightly lower battery life). Also, keep in mind the li-ion battery is almost a year older than the Nook Tablet, so it has a decreased charge capacity. Li-ion's have a lifespan of 3 to 5 years--after than, you're gonna get crappy runtime on battery. Good news is li-ions are very recycle-able and non-toxic. I think most major electronics stores accept li-ions for free.
The only issue with stability is that, if you have wi-fi set to "always on" in CM7, sometimes you'll get a SOD (screen of death) after an extended period of sleep. Basically, your screen will fail to turn on--you must force power off and restart the NC. The guaranteed workaround is to set the wi-fi setting to "only when screen is on." You can safely overclock your CPU to 1GHz (+200MHz past stock 800MHz) guaranteed, and 1.2GHz almost guaranteed (I have mine at 1.2GHz, no freezes or crashes at all, and I run Debian chrooted in it currently, which takes a lot of power).
My other concern is more about running apps and what apps will work with the setup I'm planning - which I already know would work on my NC had I not hit the "Low Memory" wall and started all of this.
Click to expand...
Click to collapse
All CM builds can transfer apps' storage location to the external microSD if you wish. I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT. Again, don't forget, the CM7 build for NC has USB host mode (so if you were really crazy, you could possibly plug in a 3TB+ mechanical harddrive, with a powered hub of course). Don't forget, the Nook Color also has bluetooth (which isn't there on B&N software). I have successfully transferred files between my netbook and my NC via bluetooth (but you have to be within 1 to 2 feet distance lol, unless you tear apart the NC and mod an antenna or something). You can also use an external bluetooth GPS receiver and bluetooth headset. Go look on the NC accessories thread if interested.
Even if I don't use it for this trip, I may change it when I get back to a CM7 sd boot to play with till I'm used to it. Also, I am rooting a NC for a Niece before I leave, and I think I'm going to change tactics and put CM on it instead.
Click to expand...
Click to collapse
Good idea. Install CM7 on your niece's NC (INTERNALLY :silly: ) and see how you like it. I guarantee you'll like it, and so will she. Since you messed with the partitions, I would suggest you visit the CM7.2 Mirage thread and post if the changes in partition sizes should make any problems with flashing.
Thank you for all this great info! I had read about the SOD issue, but I usually keep my wifi off when not using it, so I'm not too worried about that - it helps battery life some too. Interesting, I hadn't realized lion batts had that limited a lifespan. I haven't noticed a whole lot of change in my own NC's life, but to be honest I haven't looked either. I should.
Regardless, great to know CM is better at battery life.
sagirfahmid3 said:
I have all my games and non-essential apps on my 32GB class 10 microSD, both on my NC and NT.
Click to expand...
Click to collapse
Actually, that brings up the issue of class 2 vs class 10 cards and stability. There are a few threads that have benchmarked SD cards for running CM ROMS and have found the best and most stable - especially for large cards - is a 16 Gb Cl2 SanDisk... it looked by recent discussions that this is still the case, have you noticed this at all? My card is also Cl10, and as of now I think I would want to run CM off of an SD, at least until I'm used to it.
Turns out I didn't mess with my partitions after all. Gotta love computer systems! LOL Turns out the issue was version of stock I was running, and only that. I re-registered, updated to 4.3 stock and all is fine. You would think I would learn one day to read, step away and consider, instead of banging my head against a wall repeatedly. I should have figured it out much sooner, Leapinlar basically spelled it out for the other member who had this problem. And it completely explains the issues I had too. I may end up messing with them correctly again though.
I did not know the NC ended up having a blue tooth after all! I remember the speculation but the teardowns had only begun then and I never followed up on them. Now that IS interesting!
My Niece's on the other hand does have a corrupted partition, but from something she did to it. I think I will flash CM to the emmc, nice idea!