I'm currently having intermittent problems with random freezes. My nook freezes up and becomes unresponsive to input. I'm forced to manually shut down the nook by holding the power button for 4-5 seconds, and restart.
The last time the nook froze was when I tried to download the doubletwist player app from the market. After it froze, i restarted, and then the installation went on just fine.
I'm currently running CM 7.1 stable on a sandisk 32gb class 4 card using verygreen's method. I got the latest gapps (i think 0828), and the market is at version 3.3.11. I don't have much loaded on the nook just yet since it's still new to me, so it's strange that I'm having instability issues so early. I have also tried fixing permissions by using ROM Manager without much effect.
Also, on a side note, it seems like my nook does not update any accounts (gmail, imap email, facebook, etc) when my screen is off - is that normal? My wifi is always on and active, but the accounts don't update/sync until the screen is turned on.
Hmmm... so no one has experienced freezing issues for the Nook Color? My nook seems to freeze at least once a day - it ranges from downloading apps, playing games, all the way to typing an email...
Any insight would be greatly appreciated!
I rooted and had my Nook all for a day, but rooted it immediately.
Only thing I can think of:
1. Are you OCing?
2. Did you format data before installing the rom?
3. Did you flash a different kernel?
Sent from my SPH-D700 using XDA App
About the syncing issues, I don't know if the nook is setup to sync like that? It has wifi but I don't believe it is on all the time to save battery... in all honesty its all new to me, but we can learn together.
Sent from my SPH-D700 using XDA App
Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.
switch81 said:
Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.
Click to expand...
Click to collapse
1. OC to 1100. OC'ing to 1200 has no noticeable increase in performance, it overheats the device, and burns through battery like no tomorrow. I also suggest setting your minimum frequency to 1100. It sounds counter-intuitive, but the minimum frequency shows no real effect on battery. LeslieAnn (Harmonia dev) linked to a thread about the effects of overclocking on the battery (The OP was testing on the LG Optimus V to be precise). This person benchmarked and tested at different clocking speeds and found that if you set your CPU to it's highest stable clock speed (806 for the Optimus, 1100 for the Nook) it's actually better on battery life. So, my suggestion is set it to 1100/1100 min/max.
2. *facepalm* Tsk, tsk, tsk. I tried the Mirage port for the Nook and found it to be very buggy. The keyboard was always glitching, apps FC'd, etc. I'm not necessarily putting Mirage down, but it has quite a way to go before it's ready to be run on Nook. ATM I'm running Dalingrin & Fattire's CM9/ICS build (though it's only an early build, an RC maybe an alpha build at most at this point), it is amazing, aside from some bugs (you have to use a bootable microSD to utilize recovery) it's superb. If you feel a need to change ROMs, I'd go with either CM9/ICS: http://tinyurl.com/7ny5r5c Or one of the CM7 nightlies (they are fairly stable for nightlies and include plenty of goodies).
3. SOD... never had that. So I have no advice there, apparently you got it patched. I'm running Fattire's 2.6.32.9 kernel for ICS (comes standard with the ROM), no problems so far.
Edit: Clock to 1100/1100 on the interactive or interactiveX governor. Forgot to write that.
Edit #2: I'm a bit unattentive today (3.5 hours of sleep...). To address your email sync issue, I'd go into settings and see what your sync interval is (mine is set to every 15 minutes, screenshot here: http://tinyurl.com/cgkjnxe). If you have it set to something low like that and still have sync issues, it may be due to ROM bugs, or a plethora of other reasons (possibly WiFi speed?). If setting it to a lower sync interval helps, so be it, but if not, I'll look further into the problem. And by the way, check out that sexy ICS interface. This shall be my last edit.
worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.
switch81 said:
worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.
Click to expand...
Click to collapse
By default, the way Dal and Fattire have it set up, it automatically installs the boot to eMMC. Which means the loss of 5GB of storage space. But with another .9GB on internal, and up to 32GB of external, app and media storage should be no problem. So there is a con, but the pro is that you never have to worry about inserting SD to get into it.
Take heed to a few warnings:
1. Don't try to boot into recovery by using ROM manager or by Power+Home button. Use a CWR bootable. Otherwise, you corrupt your boot and have to restart.
2. GApps is still a bit buggy (unless you build straight off from their most current source) so it can/will FC on you.
3. Make sure you flash the proper version of GApps: http://db.tt/ujcVWK1U All other versions of GApps for ICS have nfc (Nook doesn't have nfc) which leaves you with a completely unusable device due to cont.force close of nfc service.
4. USB transfer DOES NOT WORK! D: If you want to put files on your SD, either use a phone or use a microSD adapter.
Note: Took down the link because something in the ZIP (not quite sure what) may have corrupted. Now I say this, but don't freak out if you already downloaded it. Whatever happened within the ZIP wont harm your Nook so don't worry about it.
The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.
bobtidey said:
The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.
Click to expand...
Click to collapse
I've found it to be more stable on eMMC. Installing via recovery menu by default put it on my eMMC. The loss of space doesn't bother me, even on other ROMs. There is actually a way to trick the device into thinking that eMMC is an SD card (basically the ability to install apps on "SD" without a mounted SD card, as well as media storage)
So I have not yet tried CM9, or putting the OS on the emmc... however I did switch over to LauncherPro recently.
I have to say... I've been having a lot less issues with LauncherPro... and not to mention, there is a HUGE performance difference. The scrolling of the home screens are so much smoother with LauncherPro than ADW. So I would recommend anyone to give that a shot!
Related
I am using CMYLXGO's NAND stock Desire HD build. Its great. However, I am having so many lag issues. I seem to be one of the few that is experiencing this with the build so i turn to some of you to see if you have had similar issues with your phones.
Problems:
1. when auto populating apps (like using installer, uninstaller, managing applications in the system tab) the phone will take forever to pull up all the apps , the screen will cut off (because the screen times out) and when I hit the home button or any button to cut the phone back on it stays black.
2. every action makes the cpu run high. adding a widget to the home screen (apps populating issue again), changing screens really fast and other assorted minor processed.
I have stopped auto sync
I do not use auto rotate any more
I do not have any rogue processes for the most part
I don't understand why I seem to have these lag issues. Everyone else talks about how fast and fluid the build is. I am under the impression that with the build NOT being run from the memory card NAND would add to speed. This is not happening for me. If anyone has any idea why this is happening. I am convinced it is something on my end but I don't know where to start. I am open to suggestions.
I have 2.15 radio, 16 gig class 2 memory card.
Hmmm, not sure but have you tried another ROM similar to see if it does the same? You can also go into MAGLDR and wipe dalvik cache. I used this ROM and all was good for me. I have sense been using this one which is also working very well.
http://forum.xda-developers.com/showthread.php?t=976384&page=1
every version of this build has been tried. That is the part that gets me. differnt kernels don't help either. i have even used SetCPU and overcloced to try and get through some of the lag. it works, but it is only when I play games not when I need to perform uninstall or widget selection for the home pages. I use SeePU which is ususally shows my cpu strain in the bright orange (for high use). most of my processes/actions raise the cpu use to high levels. I never really operate in a green (or low) usage level no matter what the action is. I would really like to capitalize on the speed NAND is supposed to offer.
Personally I would try something else (a totally different ROM) and see if you are still getting the same results, maybe even revert back to a windows mobile rom just to see if you are still getting the hang up. Last option would be to restore your phone to stock and start over, reinstall HSPL 2.08 new radio, etc...etc...
do you use an app killer?
XthelordinatorX said:
do you use an app killer?
Click to expand...
Click to collapse
yeah. but i did not at first. however, it is needed to stop some of the rogue processes. android.process.acore comes to mind.
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
WorldWide60 said:
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
Click to expand...
Click to collapse
Believe me, I know. Everything is working in his build. GPS, MMS, easy to install - the works. This is why i really want this to work properly so I can use it, without the hiccups, as my daily build. It has to be something with my phone but I can't figure out what it is yet....
On Cmylxgo's build, the first time I loaded it, I had the laggy and unresponsiveness you described for the same reasons. What I found is that rebooting the system to off/on a couple of times when I first loaded the build, addressed the first initial lag and unresponsiveness. After doing a couple of reboots, I found the build as smooth as everyone says it is. I am now trying the GL Core v11 kernel and it gives an extra 300 pts to the Quadrant Score and seems to be a bit quicker than the Rafpigna 1.8 kernel that comes with the build. Also, standby battery drain seems to be a bit better with the hourly peaks at half what I see with Rafpigna. If rebooting a couple of times doesn't do it for you, I know trying another build which may not have all the bells and whistles as Cmylxgo, but it is worth a try to see if it makes a difference. For me at least Cmylxgo's stock Desire (HD)2 build is much faster and smoother than any of the MDJ SD builds I was using.
Should I back up what I feel to be a problematic installation and copy it to another (higher-quality) SD card, or just start with a clean slate?
Here's the situation: Up until about 2 weeks ago, my installations of CM7 nightlies (using vergreen's SD installer) were working relatively well, albeit with the occasional crash and PBD. But recently, I've been having issues that just don't go away. I average maybe a day and half of battery life under what I feel to be light-to-moderate use, I get kernel panics (sometimes when my NC is just sitting there doing nothing), every third reboot or startup the CM7 logo animation just cycles, and when it does boot up it's a coin toss as to whether it'll run smoothly or I get a ton of FCs of downloaded apps and/or Framework.
As you can guess, this is getting frustrating and serves to make my friends with iPads be all smug about how stable their devices are. On the one hand, yes, I'm using nightlies and those come with a large risk of instability. But on the other hand, I had been using said nightlies for a while with few problems. Plus, I've heard of the issues people have with lower-quality SD cards, and a lot of those issues match what I'm getting with my current build. I've already gone ahead and bought one of the recommended Sandisk cards, which is currently sitting idle. In the meantime, I haven't made a lot of tweaks to either my CM7 installation or my apps, and very few of them have any data that I feel is even worthy of a backup. However, if a clean install could affect, say, any future devices being able to connect to my Google account, then I would be a lot queasier about just blowing everything away and starting again on a new card.
So, what's the opinion of the group? Either way, the install will be going on the new card, I'm just trying to figure out if it's worth it to keep things the way they are.
I would start from scratch. Things always work better that way.
Actually, I would also recommend you run cm7 from the EMMC. I was never satisfied with cm7 on an sdcard. Runs smoother, and less headaches/issues with sdcard management - transferring files, updating nightlies etc.
If you like the stock software, look into the dual-boot option ...
jasoraso said:
I would start from scratch. Things always work better that way.
Click to expand...
Click to collapse
That's what I've been leaning towards (if that wasn't obvious in the post), but I'm just seeing how others feel. Thanks.
Actually, I would also recommend you run cm7 from the EMMC. I was never satisfied with cm7 on an sdcard. Runs smoother, and less headaches/issues with sdcard management - transferring files, updating nightlies etc.
If you like the stock software, look into the dual-boot option ...
Click to expand...
Click to collapse
I do use the CM7 boot menu, but I've chosen SD because (a) I can use more space with a bigger SD card, and (b) I like having an immediate "out" if something goes pear-shaped. If my SD card stops working, at least with stock I can still get on the internet and read e-books.
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Also where do I download the following Flashable zips: (there is no dowload link)
Update 5/4/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL
Update 3/26/12 Flashable zip for Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL / MIUI GB & ICS
Update 3/6/12 Flashable zip for Mirage CM7.2 / ICS CM9
Update 3/2/12 Flashable zip for Mirage CM7.2 / ICS CM9 / MIUI v2.2.24
ZueKary said:
Last night I followed the steps on the following thread:
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [5/4] http://forum.xda-developers.com/showthread.php?t=1448186
I was amazed by how easy it was to do it and how nice both CM7 & CM9 worked. Unfortunately CM9 only comes ups in landscape mode at the home level, which is inconvenient, but not terrible and I would like to thank "racks11479" :victory::good: for such a nice a detailed job.
Now, since I'm new to this forum. I'm a bit confuse about a few things and if someone could help me I would really appreciate it. Sorry if some of these questions were asked before. I did search for answers but didn't find it.
1. I follow steps 1 to 8 and everything seems to work. I'm suppose to make all 11 updates?
2. If so, can I do all of them at the same time and then do the gapps?
3. Is this how the flashing are done? : "6-Now power on nook again and this time hold down the button to get to the boot menu and choose SD Boot --> uRecImg/uRecRam. 7-Choose to 'Install zip from SDcard --> Choose zip from SDcard --> Now choose, gapps-GB-20110828-signed-DualbootSD.zip. Once that's completed now choose, gapps-ICS-20111125-2-DualbootSD.zip" Obviusly using the specif zip in each update.
4. What does V6 SuperCharger does? Makes it faster?
5. Does any of these updates helps with the landscape/portrait issue in CM9?
Thanks in advance for the attention and please excuse me if I'm making dumb questions,but I'm no expert
Zue
Click to expand...
Click to collapse
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
RASTAVIPER said:
Been using Racks dual boot since a long time and definitely it's a good option for anyone who like to try both ICS and also use the more stable CM7.
SO concerning your questions:
1) No need to install all updates. Only the latest one will be fine
2-3) concerning flashing roms and gapps. Just remember this: for every Rom you flash (either the mirage[gb] or the ICS, then you must install corresponding gapps.every time you change Rom, you should do that
4) this script is Supposed to make system a bit faster, but with ICS ROM didn't work always much better and also sometimes creates boot problems. Personally I don't use it
Powered by my IceCold 8.3 DHD
Click to expand...
Click to collapse
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
ZueKary said:
Thanks a lot for answering my questions. I was really concern about applying all those updates specially because I can't see the folder sdcard folder in my laptop. I only c the partition with the Barnes and Noble folders. I think I'll just do all over again without botting BN while the card is in.
Also I found out where the updates are downloaded. It was a bit confusing because it don't have a corresponding name, just the date makes sense.
Are the gapps you talking about the 2 gapps that are flashed during the initial installation?
Thanks again
Zue:cyclops:
Click to expand...
Click to collapse
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
RASTAVIPER said:
Yes, you should install appropriate gapps after installing each rom.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thank you
Thanks (& battery drain issue)
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
pandachilli said:
Hi
Just to say this is fantastic OS update to the Nook - I'm a UK user and imported mine specifically with this ROM in mind. Really cool so far!
I do have a slight issue with battery use that's a niggling me. I took the basic Mirage CM7.2 / ICS CM9 OpenGL & Non-OpenGL ROM (ie the last update on the thread) and had no trouble getting it on my SD card. It all boots and works beautifully with gapps etc.
BUT... running in CM9 I find that unless it's plugged in, battery is draining fast even when it's in 'sleep mode' - ie I usually do a quick click on the side button, or when the device is set to switch display off after 10 mins. A bit of an issue as after a full charge at midnight, in the morning it's about 65% already. Basically with no actually use the device is often dead and needs to charge again.
Am I doing something wrong?? I've spent a few days searching threads and the Nook forums generally before posting here. I'm using Juice Defender and attempting to find a good technical reason. I'm wondering it's a voltage problem between UK and US? Should be using an adapter or just a standard microUSB mobile (cell) phone charger?
Regardless - still want to say a HUGE THANKS to the developers of this particular ROM and the Nook forum users generally. I'm truly amazed at the dedication and effort that's going into this stuff - great bunch of technical know-how made available to beginners. Amazing.
Click to expand...
Click to collapse
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
battery issues [PARTIAL FIXES]
ZueKary said:
I'm having the same problem with both CM7 and CM9 and while I love how everything works and looks. I'm sad to say I'm considering going back to stock, which is a real shame, but unless I keep it plugged in, the battery just drains at a dramatic speed. Turning the Wi-Fi off helps, but I use the internet a lot, so that is not an option
Click to expand...
Click to collapse
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
pandachilli said:
Zuekary
I'm not sure if this is any help to you (or anyone else??) but I've significantly reduced the battery drain in the last day or so by identifying and addressing a few issues (and basically using these forum search to 'thread title' to get a few more ideas).
NB: This does not constitute a perfect resolution, but has helped me regain use of the Nook, when I was beginning to wonder if I might have to sell it
1. BATTERY DRAIN whilst in 'sleep' mode: [PARTIAL FIX]
Upgraded to Juice defender to Pro. This enables: Turn off wifi when screen is off, schedule wifi usage off overnight.
Use Juice defender to dissallow certain apps web access.
Turn off Google Maps - I read this is a battery drain.
Disallow Google Calendar Syncing - yet another culprit apparently.
2. "Sleep of Death / SOD - Nook seems to randomly turn off completely [PARTIAL FIX]
When the Nook turns off and won't start press the power button for 5 seconds or so 3 times in a row, with a slight pause in between.
3. Perpetual Battery Drain [UNRESOLVED]
Return Nook to charge between uses
Reduce Screen brightness to 30%
4. Unsure of issues generally
Install Spare Parts+ and log battery killing apps
Click to expand...
Click to collapse
ZueKary said:
Thanks for the suggestion!
I'll try Juice defender.
As of now I'm going to Install just CM7.2 and see how that works:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
Interesting - if possible let us know how it goes. I'm keen to find a nice stable build, Cm7/CM9 seems like the "best of both" however, if I find out Cm7.2 has a healthier battery experience, I'm likely to switch, or prep an alternative sd just in case!
I'll update back here if I find anything more re: battery on ROM
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
ingdebso England
RASTAVIPER said:
There is no way to make CM9 to reach the fine battery consumption of CM7.
On the other hand it's not normal to have problems like drainage during sleep.
Install Betterbatterystats and check the Partial Wake locks for possible reasons that create the problem.
Produced by NookColor at ICS AOKP 4.0.4
Click to expand...
Click to collapse
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
RASTAVIPER said:
For stable CM7, Mirage kang is the way to go.
Check here :
http://forum.xda-developers.com/showthread.php?t=1344873
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wish you had posted that before. I installed 7.2 (stable) according to this link: http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html which is suppose to be based on this post: http://forum.xda-developers.com/show....php?t=1000957 with a newer image file. I did this on Friday and so far everything works wonderfully. Battery life is excellent. I think even better that when I was using the Stock and I have NOT installed any kind of battery saving app.
The only problem I keep having, which I also had with the previous installation is the status bar disappearing randomly. I get an error message "the application statusbar (process com.android.systemui) has stopped unexpectedly)". The only suggestion I have found is to wipe the card which did wipe before installing this version using "EaseUS Partition Master 9.1.1". If you have any suggestion on how to fix that issue I would feel very happy with the performance I have.
Even a tip on how to reopen the status bar without rebooting will be greatly appreciated.
pandachilli said:
Thanks Rastaviper - going to look into this further, meanwhile if possible can you recommend the most reliable / "vanilla" / commonly used CM7 ROM for SD cards?
I'm nervous about flashing the whole device and installing on the internal HD but still want something with good battery.... possible?
Thanks in advance!
Click to expand...
Click to collapse
My current installation is wonderful with battery life. If I can get a fix for the "the application statusbar (process com.android.systemui) has stopped unexpectedly)" error. It will be the closest to perfection I have tested so far and I had tested 3 different installations so far plus I used the stock for nearly a year.
I found the following recommendation in the link posted by RASTAVIPER (thank you!). I'm giving it a try right now. Will report tomorrow how it is working after unchecking "disable full screen".
Recommendations:
1) Regarding the status/notification bar force close issues, I recommend unchecking the "disable full screen" option in the Tablet Tweaks to avoid the status bar crashes. This also improves the app behavior especially movies and games that need full screen.
Click to expand...
Click to collapse
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
ZueKary said:
So far working excellent, no status bar crash, battery is not draining any faster than expected, but enableling full screen is annoying in certain application including book readers, so installing the button savior is a must.
Click to expand...
Click to collapse
Great news - thanks for feeding back.. so you're using "[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards." ??
RE: battery - no drainage during sleep, random power off's etc?
Going to wipe my SD and start again this evening BUT...can't decide between your recommend ROM or RastsVipers's suggestion of "CM7, Mirage"
Confused.
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
satya-1998 said:
I experience only 3 percent drain Max overnight. I recommend you use a Task Killer and clean your RAM and turn off the screen when you do not need it. Another handy tip is to use System App Remover and delete the phone.apk to stop battery drain due to cell standby..
Click to expand...
Click to collapse
I like the handy tip of removing the phone.apk
Now can you tell me where is that thank you button? (Never mind. I found it )
I have a Nook color wiped with a full version of the last stable release of CM7. It works well, but with that irritating problem of wifi reliability.
I would like to upgrade to CM10.1. The goal is to use the Nook as a development platform, while still sharing it with my wife to actually read books.
Here is the questions: Is release candidate two (RC2) of Cyanogenmod 10.1 stable enough on the Nook for daily use? I want the latest and greatest, but I don't have the time to constantly be chasing down problems, nor do I want my wife to kill me because her "book reader" has become unstable.
Do I hold out for RC3, wait for a stable release, or jump right in with RC2?
All comments and suggestions are welcome.
While CM10/4.1 was promising, CM10.1/4.2 has been a pain.
The interface seems all weird (it use a Phone interface instead of Tablet), and the performance makes the Nook Color nearly unusable. I'm talking single-digit framerates and choppy scrolling.
Personally, I found PA to be smoothest I tried... surprisingly smooth for the NC.
YMMV
I don't know about the others, I lost WiFi connections once every 2-3 hours using the most recent builds including rc2.
The fix is just turning the eifi off and on again.
However I never got sod so it is acceptable for me.
Thanks for the info guys, but the question is still up in the air. What condition is CM10 in for the nook? The wifi issues in CM7 make it useless as a connected device anywhere except with my home router (go figure). Is anyone using CM10 as their daily driver, and if so what build are you using, and where would you place the frustration level on a scale from one to 10?
codingCat said:
Thanks for the info guys, but the question is still up in the air. What condition is CM10 in for the nook? The wifi issues in CM7 make it useless as a connected device anywhere except with my home router (go figure). Is anyone using CM10 as their daily driver, and if so what build are you using, and where would you place the frustration level on a scale from one to 10?
Click to expand...
Click to collapse
I'm using CM10.1, RC2, and I'm having only very minor issues that are probably due to the ancient hardware (Flipboard sometimes freezes on me after 10 minutes, and browsers are slow, except for the very light Naked Browser). Everything I need works great, including wifi. I took it on a three week business trip to South America recently and only used my laptop once, doing email every day with no hiccups. I think it helps to tweak some settings, and use the Seeder app. Scrolling isn't butter smooth, but it's very good. Frustration level close to 0. Go figure.
I used CM10.1 for few months, it worked very good. I would say my frustration level maybe 1, and pretty much nothing compared to the satisfaction. I liked the key board, wifi connection, HD video play (for example in youtube), Browser and new UI in CM10.1 over 7.2.
recently I upgraded to CM10.1 RC4. I also did the following things to make it better. after boot up, it still has close to 150 MB memory.
1. tablet UI by autopatcher.
2. V6 SuperCharger
3. ES Task Manager to disable some startup services like Email, Email Exchange and etc.
4. Seeder.
The result is very good. It runs very smooth.
Only frustration is the speaker's volume which is low. I am using Speaker Boost, looks like helped little ( but not very sure).
xflier said:
1. tablet UI by autopatcher.
Click to expand...
Click to collapse
Has anybody posted a zipfile for this version?
Only frustration is the speaker's volume which is low. I am using Speaker Boost, looks like helped little ( but not very sure).
Click to expand...
Click to collapse
I find that it works for some apps, DSP Manager works for others.
Sent from my NookColor using xda premium
I uploaded RC4's tabletUI patches, and you can get them in my signature link for My 4 Shared.
I tried one of the RC's back in the day for CM10 and didn't like it much. It seemed slow and glitchy, and it kept corrupting my SD card, so I went back to CM7 for a while, and then tried the CM10.1 nightly for 6-17 yesterday and had SD card problems again. Switching to a higher quality SD card fixed that problem, seems 4.x's file access methods make it more finicky with external media than 2.3's. According to LMT's status bar, my NC is running at 1000mhz, and everything has been fairly stable, although there are a few apps that seem to grind it to a halt, most notably the new Opera browser, although I hear that may just be an issue with their new version, using Opera classic seems to run fairly well. As far as getting the true tablet experience, I had to switch the launcher over to Apex, which has a tablet mode that removes the phone-style dock. On another note, I have two Android phones, an older one running CM7, and a new one running ICS out of the box, tried wireless tethering on each and found that my NC could Ad-hoc into the newer one and share it's internet at remarkable speeds, but couldn't maintain a connection to the CM7 phone even if I skipped DHCP and manually set the IP. I tried Bluetooth on this one and found that neither Sixaxis or Wiimotecontroller worked, but the NC did detect the Wiimote I tried, so I know Bluetooth is working. If I can find my BT headset, I'll give it a try and see if I can't make some internet phone calls. At this point, I'm going to be using CM10.1 as a daily driver, I think it's VERY usable, with my only annoyance being that it's a little slow to boot - any custom boot animations I use other than the one that comes with it are choppy and freeze up, and once the OS has loaded, I have to wait 10-20 seconds while the lock screen says (WIDGET LOADING) to even get the lock screen clock, but after that it's smooth sailing.
On the subject of reading books, I installed Moonreader+ and read some books on it yesterday, so that's still working just fine.
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!