yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] datas0ft:
Without charger I get these boot failures. They are just random. Sometime 6-7 times. Then i just booted once to stock (without sdcard) and then back again to sd boot. Anyway ... this is strange behavior at nook side.

One interesting situation what i got yesterday. I had three days (maybe more) on sleep my test item running on CM10.1. I opened and got warning, that my battery is low. Actually only 1% to go. I managed to unlock item and let it on table. After some seconds (5-10) my circle battery widget shows 0%. I started search at my hardly tangled table charger and cable. It lasted forever. I think 3 min. My screen off is set to 30 min. And this nook not made shut down due to 0% battery. Very frugal item this Nook HD+ is.
[Nook HD, HD+ Android Development] Zachinater:
bugs that bug me

there a few bugs that have not been mentioned on this forum so i figured i should shout them out.

before i start i am using the hd+ dual booting from the hybrid method on cm10.1

one bug that really annoys me is how the wallpaper messes up. every once in a while the wallpaper has a screw up and doesn't show in full.

the only fix for this that i have found is to reboot or just use a live wallpaper which is not effected by this bug

also it would be nice if in the next release you could kick up the brightness

also the speaker volume seems to be much quieter than stock so if that could be fixed in the next rom update that would be nice

i also just wanted to say thanks for all the work you have done on this rom

it has been my daily driver for over a month now and i really love it
[Nook HD, HD+ Android Development] datas0ft:
I run different devices on CM10.1 and can say that all these have same bug when you just installed it. You can change it then to another wall paper and reboot. Then its ok for some time (actually it can be messed up after this when some program touches this wallpaper side again. But reboot helps.

I have replaced on all my devices default CM10.1 launcher Trebuchet with Nova or TSF Shell and no more wallpaper problems.
[Nook HD, HD+ Android Development] LucaToo:
One further issue I have - I cannot access quick setting via swiping top right of notification bar on the primary user (although it works for other users). The only difference I can think of is that I am a 'developer' on the primary user account. Either that or I have changed a setting somewhere..?

Any ideas - as it then makes it a bit long-winded to access other user accounts if my wife wants to play candy crush (or check her e-mails)..?
[Nook HD, HD+ Android Development] datas0ft:
Look to Settings -> Interface -> System -> Satus bar and Notification drawer settings. Try different things on/off. Also this can depend at launcher settings side.
[Nook HD, HD+ Android Development] someone0:
I have been away from the scene for quite sometime. And I just play w/ CM10.1 Hybrid this week. I experience similar to your. I was thinking about where to post my finding, and I thought probably in the development section is the correct one but I guess you beat me to it. Anyway here is what I experience and what I think happen.

The hardware is basically a Nook HD+ with Sandisk Ultra U1 Class 10 64GB card.

1. With CM10.1 Hybrid w/o power attach at boot, it will stuck at cyanoboot logo.

2. With CM10.1 Hybrid w/ power attach (either via 2A Nook power adapter or 500mA USB port from a notebook) it will boot just fine

Something else I found was during the initial inital booting, if power is remove past cyanoboot logo, it can still fail and corrupt the sdcard. None of this was happening when I was testing probably the first or second build of CM10.

After the unit is fully on, the external power source is no longer necessary.

Power drop much quicker than stock, but I guess that's because the sdcard was being use close to 100% of the time.

Orientation change much slower than stock, And some app just refuse to rotate.

Touch screen doesn't always recognize the input. Say, at certain point, an app may recognize some touch input in the top half of the screen, but won't recognize bottom half. Hitting the power button to turn off and on again will solve the problem.

Wireless card won't see any thing; putting the unit into air plane mode and out of it will solve that problem also.

I have tried running stuff like SuperPi in the background afterward to see if I could crash it, but that didn't happend. So, my guess is that it's not the sdcard spec(certain speed or volume) that cause the card to be incompatible with CM10/10.1, but rather that certain card use more juice than the hardware can handle without proper power management. Meaning that after Android is fully booted, its power management solve that problem. So, I guess it's also possible if there is some basic power management build into the loader and CM boot process, more card could compatible and less likely to corrupt. Again this is just assumption based on my finding.
[Nook HD, HD+ Android Development] LucaToo:
Have you tried a 32gb Class 4 card..?

I had very similar booting/hanging issues with both 10 and 10.1 - most of which were solved by reverting back to the Class 4 from a 64gb Class 10 card. I am currently on Hybrid CM10 with Sandisk 32gb Class 4 card which gives a much more stable environment (which for me outweighs the loss of 32gb of storage space).
[Nook HD, HD+ Android Development] someone0:
I don't have any class 4 card, but I do have a 32GB class 10 w/o U1. But I may try running the 64GB card again in SD mode rather than hybrid. But the true is it's quite stable other than boot up, as long as I have no need to reboot I'm fine. As I have stated, I even tried running SuperPi in the background just to attempt to load up the process, which I can feel the back was getting hot, still it won't crash.
[Nook HD, HD+ Android Development] tdnookhd:
Is there any chance at getting the Wake/Sleep feature for Nook cases from stock working?
[Nook HD, HD+ Android Development] tuanda82:
Look like developers are busy at the time. Please wait.
[Nook HD, HD+ Android Development] someone0:
Now that Android 5.0(Key Lime Pie) is around the corner or two, and maybe that's what CM11 will be based on. I would be wonder if verygreen will make a move to that. It's quite exciting this year, now that there will be mobile device with more open source OS. I'm very interested to see what ubuntu will bring to the mobile device. If the Ubuntu 13.04 will have Mir I'll take a test drive as well. On the other hand, Ubuntu has been relatively supportive toward older hardware is kinda make it harder to test(referring to requirement of PAE CPU).
[Nook HD, HD+ Android Development] leapinlar:
I recently bought a newer 32GB HD+. It had 2.0.5 on it factory. I have been having a lot of trouble getting it to boot to SD from a cold start. It will boot, but only after many tries. It always boots to SD from rooted stock using Quick Boot. But the biggest difference is it will not run this CM10.1 ROM, either with verygreen's Original SD or my Hybrid. It hangs on the dimmed cyanoboot logo. CM10 runs fine, both on Original SD and Hybrid, but the cold booting issue remains. There must be some hardware difference.

EDIT: It was the kernel. I put the CM10 1/20 kernel on it and it boots fine. Something in the hardware is different enough that the CM10.1 1/07 kernel would not boot.

EDIT2: And it only boots with the 1/20 CM10 kernel on the Original SD. When I try it on my Hybrid, the kernel gets paired with my modified CM10.1 ramdisk so it can boot to the Hybrid. They do not seem to work together. And going to the CM10 kernel and modified CM10 ramdisk, it boots but immediately starts having force closings. So it looks like the CM10.1 ROM so far does not run on my Hybrid and with the new hardware.

EDIT3: I'm not so sure it is a hardware difference now. See my post below.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] Darrian:
I just recently bought a 32GB HD+ too and was pulling my hair out trying to make bootable sdcards. I finally did get your hybrid to work with the latest CM10 build from February, but it only boots off my 32 GB sdcard and not my 4 GB or 8 GB. For a while I thought it was that I was messing up somewhere in the process, so I'm glad to know that I'm not the only one. I would really like to try 10.1 but I'm waiting for a newer build.
[Nook HD, HD+ Android Development] sorrowuk:
If you erase the stock software and go back to the setup screen then hold volume up and tap bottom right then click the factory button that appears does any of those hardware details appear different in this hd+ compared to your old one ?

Maybe something has changed, or if might be something more slight like sd slot changed or something.
[Nook HD, HD+ Android Development] leapinlar:
I looked at that screen (you can get to it without erasing) and nothing changed. I thought maybe it had a different screen or touchpad, but they are the same. I also read the dmesg file and only found the ram chip to be different.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] leapinlar:
I am now having trouble running CM10.1 on my old HD+. So I'm not sure it is a hardware difference causing the problem. Verygreen warned in the OP that the boot may fail with a dimmed cyanoboot logo due to a crash in hwc. I don't know what is different now that it does not boot. It used to. I thought it could be my revised cwm ramdisk, but I tested with the old cwm ramdisk and started with a fresh burn and it would still not boot. The only way I could get it to boot was to change kernels. And even that did not work on my Hybrid.

I guess we just have to wait for an updated build.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] someone0:
I had similar problem. And now I have a bad card unsure of its cause. Nonetheless I RMA it. In your case, I think what happened is that once your realize the SD card won't boot into the new HD+ you put the same card into the old HD+ instead of remaking it. Maybe with a new card altogether. My educational guess is that the CM10.1 somehow slowly corrupting the card, and I don't necessary mean physically, but at least the data on the card. Normally on a Linux PC, when mounting ext filesystem it does a quick check to see if it was unmount correctly and may do some fsck. At least 2nd partition is an ext filesystem. Hence at this point I'm unsure of what is wrong w/ CM10.1 and I would rather say for most people, stick w/ CM10 or stock. I don't think many people have cold boot problem in CM10.1 is pure coincident or just incompatible card.
[Nook HD, HD+ Android Development] leapinlar:
I did remake the card several times with other images, etc. But I did always use the same card. I will try a different card and see if that helps.

EDIT: You were right! It was the card. I used a different card and CM10.1 worked on both my new and my old HD+. Strange, the other card was a SanDisk 16GB class 4 and it works fine with CM10 on both hybrid and original SD. But it only works with CM10.1 if I put an older kernel on it. There may be something to the idea that the CM10.1 kernel is messing with the card.

Edit2: By messing with the card, I don't mean destroying it, I mean writing something to it so that the only way to get it working properly is to full overwrite format it.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] rfryar:
GApps?

What version of Google Apps do you need to flash with this rom?

I tried this version: gapps-jb-20121011-signed

But got instant force close loop. Was there some other set up to get GApps to work with the rom? I come from a long background of phone CMs, not much experience with the hybrid setups, so please forgive if I am missing something obvious.

I followed the setup on this thread and there was no mention of Google Apps.

Thanks,

Rick
[Nook HD, HD+ Android Development] leapinlar:
CM10.1 needs 20121212 or higher.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] verygreen:
Sorry all, got real busy with work.

Spent this weekend getting up to speed on CM10.1 on hd+ an the result is here: http://nook.rootshell.ru/hd/cm-10.1-20130422-UNOFFICIAL-ovation.zip

it's pretty much somewhere around cm10 on hd+ I would suspect, but did not do any extensive testing yet. I know the logo is distorted at first during bootup ;)

what I did try: angry birds space and youtube both work, wifi works, bt does not (need to look into it).

I assume booting from emmc is still a winner? Any other important revelations from the past month or two that I missed (don't really have time to read past discussions)?

With B&N unlikely to release another omap-based reader, I guess there's no harm in releasing a native uboot that boots from emmc now (unless somebody beat me to it already)
[Nook HD, HD+ Android Development] 9v9:
We so desperately NEED an unlocked bootloader! It would be so nice to not have to boot from the sd card, or have to deal with messing up the internal data on B&N's native OS.

I remember reading back about a month ago someone releasing a proof of concept...but I was not sure if they were reporting anything fancy...just booting from an sd card to keep it "unlocked."
[Nook HD, HD+ Android Development] testlab:
Thanks very green. Waiting on a new SD card and I'll do some testing...
[Nook HD, HD+ Android Development] leapinlar:
For those of you interested, this new build works on my Hybrid SD on my new HD+ device. (The 01/07 build was failing in my new device before).

Thanks verygreen. And BTW, Nook Color was able to fix the distorted boot animation by putting the rotation in the kernel instead of through the surfaceflinger at 270 degrees. Apparently any device that used the 270 rotation got that CM10.1 distortion. See steven676's discussion on the Nook Color CM10.1 thread.

And I will be watching with much anticipation for the new emmc bootloader. No one has beat you.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] someone0:
There are a few reporting to have bad sd card after running cm10.1. Not saying that your kernel cause it after running for quite sometime, but there is a colloration to that. I already got mine RMA so I can't do any test now. But it need to be look into.
[Nook HD, HD+ Android Development] verygreen:
What do you mean "bad sdcard"? my cards all certainly seem to be totally fine (and I never turn off my nooks, so they stay booted into whatever they happen to boot on power on with sdcard inserted)
[Nook HD, HD+ Android Development] someone0:
For me, I never to my nook to stay on stable. Maybe every few days or after taking it out of the bag I found it powered off/rebooted. After some time, I start having problem reboot into cm10.1. The story didn't stop there, but even after attempting to recreate the cm10.1 card it still couldn't get successful boot. Usually stop at the circle logo. Then it hit me after trying to do a full format on the card and it give me error. remaking cm10/10.1 on another card will be fine though. And no the card didn't had problem to begin	with. When I get a new card, I do what I do the same way I get new hdd. I do a full format. So I know this card didn't have bad spot to start with. I didn't do a full test as I would on a hdd but that's because it's flash memory technology otherwise I would. I figure a full format is good enough.
[Nook HD, HD+ Android Development] dbrickg:
Woo woo! Thanks so much, verygreen. This is fabulous.

I've been using leapinlar's hybrid sdcard with your hd+ cm10 rom. From there, I just downloaded your new cm10.1 rom and the appropriate gapps package, booted into cwm recovery, cleared cache and dalvik cache, flashed the new cm10.1 zip, leapinlar's hybrid rom modifier, and gapps, and rebooted. So far it's looking really good. Didn't lose any apps or settings from cm10. Super!
[Nook HD, HD+ Android Development] fcanha:
Welcome Back VeryGreen!

Can you please turn BT back on? See below just like in Nook Color days remember?

BT works like a CHAMP by doing the following (Using 12/31/2012 build.)

1. Turn off WiFi

2. Turn on BT

3. BE SURE THE NOOK IS VISIBLE

4. Turn on your BT device

5. Pair

6. Enjoy

Also, I would not waste time on reports of kernel corrupting the card over time. Seems like an isolated case. I have made several cards using Sandisk Class 4 and all are running fine.

Thanks!
[Nook HD, HD+ Android Development] vishaljh:
I installed the latest CM10.1 using the Hybrid method. I have come across one issue. The Battery is draining very fast and if I look into the batter section under settings, about 60% of the battery is taken up by mobile standby which is strange. For some reason, the CM10.1 is considering my tabled as a phone and tring to use the mobile.

As a temporary measure, I have eabled airplane mode which has fixed the issue. Not sure if anyone has better suggestion.

P.s. Thanks VeryGreen & Leapinlar for all your work on this rom
[Nook HD, HD+ Android Development] dbrickg:
Thanks for pointing that out. How weird. I hadn't even noticed. I looked throught a bunch of the settings, didn't see any way to turn it off. Turning on airplane mode kills the wifi, too, which isn't optimal....
[Nook HD, HD+ Android Development] testlab:
Same here. Left it on for half a day. I'm using SD method. I have Cm10 on hybrid working nicely and didn't want to override it
[Nook HD, HD+ Android Development] RustedRoot:
Is this 10.1 build based on the CM-M2 release, which in turn is based on Android 4.2.2? See http://www.cyanogenmod.org/blog/cyanogenmod-10-1-m2-release
[Nook HD, HD+ Android Development] vishaljh:
Hi dbrickg,

You can enable airplane mode which will switch off wifi. Then you can manually switch on wifi which works fine. Battery life is back to normal.
[Nook HD, HD+ Android Development] dbrickg:
Hah, thanks. Who would'a thunk it. But doesn't that kind of defeat the purpose of airplane mode, which is supposed, as I understand it, to turn off all radio transmission?
[Nook HD, HD+ Android Development] fcanha:
Disable Mobile Standby

1. Start your explorer. Navigate to the "/system/app" folder. Tap "read/write" or "RW" if read-write mode is not already activated. Tap "OK" if your Superuser app asks for permission.

2. Tap and hold the file marked "phone.apk." Tap "Rename." Change the file name to "phone.old." This disables the without actually removing it; you may need it if you want to upgrade your Nook software later. Tap "OK."

3. Tap and hold the file marked "telephonyprovider.apk." Tap "Rename." Change the file name to "telephonyprovider.old" and tap "OK."
[Nook HD, HD+ Android Development] dbrickg:
Excellent. Seems like that'd be even better than turning on airplane mode and then returning on wifi

EDIT: after running it with those files renamed for several hours, and rebooting, just for good measure, I'm not seeing any difference in the battery usage. Settings / Battery still shows "Cell Standby" hogging 75% of the battery
[Nook HD, HD+ Android Development] bpaulien:
Would freezing the same app in titanium backup do the same thing?
[Nook HD, HD+ Android Development] someone0:
Normally, I would advise against renaming something.apk to something.old I think a better convention would be rename it to something.apk.old that way you know what was the previous file extension. In fact I made a habit of avoiding using .old alltogether because in PC, some cleaning up software will misunderstood amd remove the file. So it would normally rename to something.apk.orig or something-apk.orig
[Nook HD, HD+ Android Development] leapinlar:
It would if they showed up there, but they don't. You could also disable them in settings, apps, but they don't show there either. I'm sure verygreen will find the issue and fix it permanently.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] bpaulien:
Thanks. I was not near the Nook when I asked so thanks for the answer. I plan on putting the new CM10.1 on my hybrid system tonight. I'll be sure to turn on airplane mode until verygreen get it fixed.
[Nook HD, HD+ Android Development] verygreen:
Sorry, still have only very limited time to play with this, so progress is slow.

This snapshot only (hopefully) has "phone mode" fixed.

http://nook.rootshell.ru/hd/cm-10.1-20130424-UNOFFICIAL-ovation.zip
[Nook HD, HD+ Android Development] vishaljh:
Enabling the Airplane mode is not helping and I am still seeing mobile standby hgging battery. Will give VeryGreen's new snapshot a try tonight. If anyone manages to try before me, can you please let me know if the new snapshot fixes the issues.

Thanks
[Nook HD, HD+ Android Development] sorrowuk:
If you can release a uboot which can boot from emmc and totally get rid of needing to have an sd card that would be amazing .

:)
[Nook HD, HD+ Android Development] vishaljh:
+1 to the uboot and getting rid of SD card completely :)
[Nook HD, HD+ Android Development] dbrickg:
Yes, thanks much, verygreen. That seems to have fixed it. My tablet is no longer listening for a phone connection on hardware that doesn't exist!
[Nook HD, HD+ Android Development] leapinlar:
I just posted on my Hybrid thread a link to maybe get the tablet interface to show on CM10.1. See here:

http://xdaforums.com/showthread.php?p=40660697

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] fcanha:
Zinio Fix

Not sure if I mentioned this already....but changing the manufacturer to "asus" and the model to "Nexus 7" without the quotes of course in system/build.prop will fix Zinio from not working. I used ROM ToolBox's build.prop Editor.

Change following properties:

ro.product.manufacturer = asus

ro.product.model = Nexus 7
[Nook HD, HD+ Android Development] golizza:
I've just build new one via AutoPatch, but not work
[Nook HD, HD+ Android Development] vishaljh:
Out of curiosity, can anyone please tell me what is the difference between CM10.1 posted on this thread compared to another thread for CM10/10.1. The reason I ask is that this has a CM10.1 rom with last update of 04/24 and the other main thread has a Cm10.1 with 04/25.

Any help would be greatly appreciated.

---------- Post added at 06:11 PM ---------- Previous post was at 05:44 PM ----------

Please ignore this question. Just realized the other thread was for HD and not HD+.
[Nook HD, HD+ Android Development] champrock:
hi

from the past couple of days i am facing an issue. i am unable to reboot into CM 10.1. it gets stuck at circular CM 10.1 logo. i can only boot back into the OS after i clear cache from CWM.

any way to solve this?

thanks!
[Nook HD, HD+ Android Development] leapinlar:
Are you running the CM10.1 from Hybrid or the Original SD from this thread? Anyway, try clearing the dalvik-cache in the advanced CWM menu. If that does not fix it, you may need to do a wipe data/factory reset. That will cause you to lose all installed apps and settings.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook HD, HD+ Android Development] champrock:
i am running Hybrid SD (CM10.1 04/24 ROM from this thread).

when i go to wipe cache from CWM it gives the following:

1. Wipe cache (on the main menu of CWM) occurs successfully.

2. Wipe Dalvik cache (in advanced settings of CWM) gives the following error : ":unknown volume for path [/sd-ext]"

I read that the above error occurs on unpartitioned SD cards but that is clearly not the case with me.

any ideas?