yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] PocketSmiley:
Two Tiny Requests

verygreen: I just want to add to the noise of the cheering crowds that you're an insanely amazing person.

CM10.1 for Nook HD+ is already perfect for most of our needs, thanks to you; I do have two minor requests:

How do I set default screen orientation to landscape? Using ro.sf.hwrotation=0 in build.prop does this but the touchscreen is not oriented as well. Disabling auto-rotate always returns to portrait mode. We mount tablets on overhead stands above the beds, and the tablets can be rotated but are fixed to face downward (almost parallel to the ground) so the accelerometer does not rotate the screen. (The accelerometer needs the device to be nearly perpendicular to the ground.)

I wish to use DSP Manager with JetAudio (and any other app). In early CM10 and below, DSP Manager used to work for all audio output by any app. In CM10.1, DSP Manager only works with Apollo, Google Play Music, and a rare few audio players that pop up DSP Manager when you select the "Equalizer" setting inside the app. Installing the older DSP Manager apk has no effect.

That's all.

BTW, I don't know if this is supposed to happen, but I accidentally reverted CM10.1 to stock rom while trying to boot an SD card! I always hold the power button until I see the Cyanoboot logo; that's how I boot to SD. It's not always successful so I just do it again--hold power button for 10 seconds to turn off, hold power button when turning on. Somehow, I couldn't boot to SD and I had to hold the power button multiple times until suddenly instead of the Cyanoboot logo, the original Nook boot screen showed up and started loading. After restarting automatically, my tablet booted in stock rom. I thought the CM10.1 native emmc install wiped everything? Does this mean that the stock rom is built into the device?
[Nook HD, HD+ Android Development] Ogre6473:
Not so easily done on the app. Definitely needs work. Could you post a link of some kind?

EDIT: Found it, just had to do a lot more poking.
[Nook HD, HD+ Android Development] lancorp:
Cheering crowds are nice, but don't pay the bills (or buy the beer!). Click the DONATE TO ME button on the first post and send a few bucks to verygreen to show your appreciation. ;)

That is supposed to happen. It's the auto-recovery to stock ROM after a certain number of unsuccessful boots. It's a fail-safe feature. Officially, it's supposed to start recovery to stock ROM after 8 unsuccessful boots, but I counted it on mine one time, and it was after 5. It's a bittersweet feature, especially when you can't count on when it's going to do it and you wind up losing all your stuff!!
[Nook HD, HD+ Android Development] leapinlar:
Yes, it is the stock recovery that formats and reinstalls the stock after 8 failed reboots. If you replace the stock recovery with either CWM or TWRP on emmc, this can't happen.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] warunamail:
But its not. I having the same problem. But what I did enable auto rotation and just check 90 and 270 degree in rotation modes under display. That worked. Now its only in landscape mode.
[Nook HD, HD+ Android Development] king200:
I wonder if Play Store identifies a different HD+? "My Phone Explorer" will.
[Nook HD, HD+ Android Development] dbrickg:
I haven't tried a bluetooth keyboard yet, but there's a whole subthread here about bluetooth interfering with wifi. When I output audio via bluetooth my wifi drops, not immediately, but within 10 or 15 minutes.
[Nook HD, HD+ Android Development] darknetone:
I just tried the a PS3 controller with cm-10.1-20130630-UNOFFICIAL-ovation-emmc, no dice. Which is a bummer. Hopefully this will get fixed at some point.
[Nook HD, HD+ Android Development] verygreen:
use it in usb mode, that way it certainly works.
[Nook HD, HD+ Android Development] PocketSmiley:
Spoiler content hidden.
[Nook HD, HD+ Android Development] BigMacca:
I'm interested in this as well - Stock supports exfat on SD cards and I've seen other references that CM10.1 can be made to support exfat as well.

I've not worked out how to do it yet though.....

p.s. I just want to echo what everyone else has said and thank verygreen for all his hard work - the emmc install is amazing!
[Nook HD, HD+ Android Development] racer25x:
It's very awesome to see native install. I hope I'm not being "that guy" but, would it be a simple matter of editing the build.prop file (setting the correct device name/id and screen settings) in order to be able to install this on the HD?

[Edit]

Oh, I almost forgot: Thanks to verygreen (and anyone else) for all of the hard work getting this working!
[Nook HD, HD+ Android Development] verygreen:
I remain very-time limited, so cannot do a lot of stuff all at once, unfortunately.

New build cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip:

Updated wifi drivers to _R5.SP3.01 - this fixed wifi battery drain when sleeping in my testing. 9 hours on battery with wifi on, 0% battery loss.

Next I'll probably spend a bit of time to have recovery that works from emmc too. Final CM10 version with all the recent fixes and wifi battery drain fixed is forthcoming too.

About exfat support. Nook-shipped kernel module is a commercial software by Tuxera, I contacted them to see if it is ok for me to ship their module with my builds and they did not give their permissions, so I'll take a more time-consuming approach of extracting this module from stock ROM eventually, as such this is going to be on a backburner for some time.

BT audio not working - I can replicate the issue, but I do not see an immediate solution yet, will continue investigations.

On Nook cover not waking up or not sleeping on close/open, whoever has one of those, please run "getevents" from adb shell, filter out accelerometer noise and then open/close the cover several times to see what sort of keycodes does it send?
[Nook HD, HD+ Android Development] sorrowuk:
Are we able to take this exfat kernel model ourselfs from the nook firmware and insert it somewhere into cm10.1 to get exfat support.

Is there any format at present that works and allows greater than 4gb files on sd card ?
[Nook HD, HD+ Android Development] dbrickg:
Yowza... rebooting to new ROM now.... Hmm, must have done something wrong. Just sitting there at the the cyanoboot logo....

Reinstalling.... Now rebooting.... And there's the lovely Cyanogenmod logo... and now Android is upgrading.... Looks good.

Thanks so much! Looking foward to an emmc recovery so I don't have to keep switching sdcards. Have a great weekend
[Nook HD, HD+ Android Development] aszid:
boot issues

I've only managed to get this rom past the cyanoboot screen once so far (initial dirty flash), and that time google apps setup was stuck in a crash loop, so i had to restart anyhow.

AFAIK I'm doing everything i should for a clean install, but still no luck here.

clear data

clear cache

clear dalvik-cache

install rom

install gapps

remove cwm sd

reboot

cyanoboot sceen *freeze*

Reinstalling the 5/5 build has no issues and boots right away. I even tried to re-dirty flash from 5/5 to 5/10, with no luck.

Anyone else having issues? Anyone notice anything I'm neglecting to do?

Thanks!
[Nook HD, HD+ Android Development] verygreen:
Is device still visible on your host pc via USB? (e.g. what's in dmesg if you run Linux)

Can you adb shell in and check dmesg/logcat there?
[Nook HD, HD+ Android Development] aszid:
I need to let my battery charge, then i'll give it another go and see what i can see.
[Nook HD, HD+ Android Development] leapinlar:
I had that problem also. It was stuck on the dimmed cyanoboot forever. Took several reboots to finally get it to take. I have not tried to reboot since. I will though. Could it be related to that HWA failure that verygreen had before?

Edit: Just rebooted, no issues.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] verygreen:
the HWA init race is real and is there, I'll include a patch for it in next build, but for me the symptoms now are that every once in a while on bootup I get a garbled screen after cyanoboot logo and that is then replaced by undistorted bootanim.

I do not think I have ever seen a total failure to boot.
[Nook HD, HD+ Android Development] xdatoast:
Great news and thanks....I'm going to hold off installing until the Bluetooth issue is fixed but just one other question.

Would there be a way to still use the BN Reader app? It really is good.
[Nook HD, HD+ Android Development] verygreen:
You mean the one from stock or the one from Market? The market one, we just need to figure out what is it unhappy about.
[Nook HD, HD+ Android Development] leapinlar:
The Nook for Android app does work good on your ROM. The issues is to figure out how to make it so that Play Store thinks it is compatible so it can be installed. Either that or install it from another device.

The stock version cannot be put on CM10.1.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] dbrickg:
I've got it just fine on mine, but I must have gotten it before I converted to the emmc version... oh, no, wait... I lost all my apps when I did that, had to reinstall from scratch. So maybe one of the earlier versions of verygreen's emmc rom could download the nook app? or maybe the store just recently changed its mind about our device? or...?
[Nook HD, HD+ Android Development] BigMacca:
I've got the same issue, it just gets stuck on the dimmed cyanoboot screen - I rebooted 7 times before restoring my backup of the previous version of the rom.

All back up and running now, I might have another go later.....

Thanks again for all the updates verygreen (and leapinlar as well)
[Nook HD, HD+ Android Development] concept0:
I've tried a clean install multiple times of the 5/10 with no luck. 5/5 appears to work great. As with you, no luck with dirty flash either. Just keeps sticking at Cyanoboot screen. If I reboot too many times, it restores to stock.

I just bought the hardware a few days ago if that matters.

Regardless, thanks to the OP for bringing CM to the HD+. Even with a launcher, the stock firmware wasn't doing it for me.
[Nook HD, HD+ Android Development] aszid:
Ok, tried again. I did a dirty flash from 5/5 again, installed gapps rebooted. It got stuck on the darkened cyanoboot logo, it was not connecting to my pc for ADB, so i could not shell and get a logcat.

On reboot, it worked and booted up. I have rebooted it from the power menu, and it has booted back up.

Cold boots seem to be an issue for me still, as i have not been able to get it to boot back up since i shut it down after the successful reboot. Stock restore is currently processing for me, after hitting the limit.

Unfortunately I wasn't able to get a logcat, and i'm not running linux so i'm not sure how i could get a dmesg (if i could).
[Nook HD, HD+ Android Development] verygreen:
I just tried a cold boot and met no problems.
[Nook HD, HD+ Android Development] docfreed:
Update WiFi Drivers

With respect to the following from verygreen "Updated wifi drivers to _R5.SP3.01 - this fixed wifi battery drain when sleeping in my testing. 9 hours on battery with wifi on, 0% battery loss".

Is there a way to extract the WiFi drivers from the 5/10 build and use them in the 5/5 build?
[Nook HD, HD+ Android Development] xdatoast:
I mean the one from stock. If BT is sorted out, then this won't be a deal killer for me but I really do like the BN stock reader.
[Nook HD, HD+ Android Development] thatdude90210:
HD widgets' tilt locker toggle holds after a reboot, landscape or portrait. It's a paid app, but with tons of functions - including lockscreen widgets - that makes it worth it.
[Nook HD, HD+ Android Development] leapinlar:
Maybe it is how you are toggling the auto-rotate. I use a notification bar widget to toggle it and it works perfectly.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] data2318:
this is not going to work. Need some mod in the roms

---------- Post added at 02:56 AM ---------- Previous post was at 02:55 AM ----------

[/COLOR]

any way to embed the tablet UI into the framework.apk? wanted the status bar and navigation buttons to be at the bottom so bad. I have that in my phone's rom, but not sure if decompiling that will work with this rom?
[Nook HD, HD+ Android Development] leapinlar:
There is a thread in development that puts the tablet UI on the ROM (which is what you are looking for).

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] LucaToo:
CM 10.1 vs CARBONROM

Wil ask this in both threads - but is there any particular advantage in CM 10.1 vs carbon Rom..?
[Nook HD, HD+ Android Development] rushless:
Based on comparing content of roms and issues, here "is" perhaps a top level summary:

1. Very's CM 10.1 is as pure vanilla CM 10.1 as you can get and have all functionality of the Nook. Carbon has a lot of extra features you may or may not want.

2. People seems to have more issues with Carbon. but no way to apply objectivity to that assertion (Correlation with extra features?). Just comparing traffic and evolving apparent issues noted in the two threads.
[Nook HD, HD+ Android Development] jamus28:
2 things:

cm must have adjusted their audio.primary.ovation.so because the revert/quiet volume version no longer produces any sound at all. I dont know if very green kept the higher amp values or its all back to default. I don't have my laptop with me to check.

At risk of sounding like an idiot to anyone in the know, Im almost convinced that the heapgrowthlimit at 64m produces a noticeable decrease in the lag. I've run each of the builds on default settings for a day or two then make the prop edit. The difference is noticeable immediately on reboot. My evidence is all anecdotal, but so far it doesn't sound like anyone else has tried. I don't know why a garbage collection limit value would make such a difference.
[Nook HD, HD+ Android Development] verygreen:
Ah, right, that's my change in the kernel throwing old audio hal of.

Here's an updated one.

quietvolume-2.zip

does it help even more if you decrease it further?
[Nook HD, HD+ Android Development] sean_nj:
Does the ROM support exFAT?

Hi,

I just found out that my Nook HD+ with the 0630 ROM cannot read microSD in exFAT. This is the first time I tried, so I am not sure it's the ROM's problem or it's the way it is.

Thanks a lot,

Sean:D
[Nook HD, HD+ Android Development] verygreen:
exFat is a proprietary, patent-encumbered filesystem, so I don't think I can include any support in the ROM itself. that said, there's exFat module in the stock that we can likely use, but we'd still miss vold support. Overall it's on my todo list to figure something out, but it's way down that list.

Meanwhile you can flash one of those exfat suport zips floating around.
[Nook HD, HD+ Android Development] sean_nj:
Thanks a lot for the quick reply and the ROM :o!

exFAT is not a must-have to me. I just tried to see how my Blu-ray ripper looks on my Nook HD+.

Thanks,

Sean
[Nook HD, HD+ Android Development] jamus28:
48m: hard to the the difference to 64m. Things felt sluggish at first but sped up a lot with more use

32m: Apps load significantly quicker. Even scrolling and clicking on settings feels more responsive. Typing too. I'm not sure what this means.

Scrolling may have a tiny bit of tearing, maybe not.

Only negative so far is the Wallpaper image on apex is distorted/ cut off. I'm sure there are more drawbacks with such a restrictive allocation.

Edit: Well maybe I'm not really onto something. I think it was fast at 32m because it disabled my wallpaper. Going back to 96m with wallpaper disabled and it feels almost as fast. Maybe 75%. Strange that the slowdown would occur with both the normal stock wallpapers and my custom high resolution one.

So far very inconclusive. The setting definitely has an effect somewhere.

At the very least the lesson for others is to try a lower resolution wallpaper if you're lagging.
[Nook HD, HD+ Android Development] rkeller62:
At 32m static wallpapers do not scale properly for me. There are black borders on top and bottom as well as on far left and right home screens. Live wallpapers appeared normal.

48m setting fixed this issue and static wallpapers display normal. Can't comment definitively yet on performance, but appears better than original setting.
[Nook HD, HD+ Android Development] verygreen:
Hm, so I wonder if all the "have live wallpaper and lag disappears" reports are just that - "removing high res wallpaper speeds things up" ;)
[Nook HD, HD+ Android Development] verygreen:
recovery update for a change.

Updated TWRP to 2.5.0

usb device id now matches that of stock ROM, so hopefully that makes life of those on Windows a little bit easier.

backups now work (both to internal storage and to sdcard).

Two options to install:

- Flashable zip for EMMC: twrp-recovery-ovation-3.zip

- Files to place to FAT32-formatted sdcard (otherwise empty) ovation-sdcard-twrp-files.zip (to install: format an sdcard as FAT, unzip content of this zip into the root of that sdcard. Make sure the first partition is marked as bootable (does windows format do this by default I wonder?).
[Nook HD, HD+ Android Development] Rycon33:
Nice:)

Just tried a base backup and everything seems fine but I noticed this error - Unable to mount "/bootdata" but it still said Backup complete and Succesful in the end.

I hope that error is nothing.

And yup the /sdcard(internal memory is recognized) now, very nice.:)
[Nook HD, HD+ Android Development] leapinlar:
I don't think it does. You have to set the first partition as "active". I still use Windows XP and it cannot set it. You can do this with partitioning software like Mini-Tool Partition Wizard or EaseUs Partition Manager. I have heard that newer Windows can do it, but I don't know the commands.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] verygreen:
That's a pity.

I was thinking of doing a self-expanding card image too, btu somehow all versions of mkfs.vfat and mkdosfs that I can build for arm platform create a filesystem that makes omap hang on boot.

Using x86 versions of the same works fine, though. fsck finds nothing wrong too.

I guess I might need to expend more efforts into that after all :(
[Nook HD, HD+ Android Development] deckoff:
What file and setting do you edit ? I am eager to try :) what exactly is the reasoning behind the improvement
[Nook HD, HD+ Android Development] panchokoster:
verygreen, could you add fuse.ko to your rom?
[Nook HD, HD+ Android Development] CubeCloudOS:
Sorry for noob reply what does that module do again? :confused:
[Nook HD, HD+ Android Development] Jack45:
http://www.google.com/url?sa=t&rct=j&q=python%20papers%20fuse&source=web&cd=2&ved=0CDQQFjAB&url=http%3A%2F%2Fojs.pythonpapers.org%2Findex.php%2Ftpp%2Farticle%2Fdownload%2F244%2F215&ei=BjzTUf-uJtXd4AOp6YCgDw&usg=AFQjCNF4RwHXakSgKilUyocQb9rSHtSI2g&cad=rja

http://www.ibm.com/developerworks/library/l-fuse/

http://sysdocs.stu.qmul.ac.uk/sysdocs/Comment/FuseUserFileSystems/FuseBase.html
[Nook HD, HD+ Android Development] DicKan:
please make the tabletUI and originalUI as an option like the carbonROM.

I like USB Host funtion of your ROM. But I cannot flash your ROM until the tabletUI mod for the newest version is released every time.
[Nook HD, HD+ Android Development] Danrarbc:
I'm trying to something about another switchable UI ROM, but it's primarily based on AOSP so I'm not sure USB Host will work there either.
[Nook HD, HD+ Android Development] NotShorty:
No link handy, but I'm somewhat familiar with this in regards to the Galaxy Nexus. Someone noticed that from 4.1 to 4.2 Google changed these "cache" settings (technically more complex than that) in the build.prop file. Some speculated this was to better accommodate devices with 2GB of RAM like the Nexus 4, though it compromised performance on 1GB devices such as the Galaxy Nexus and the Nook HD+.

Anecdotally, applying the proposed fix didn't do squat for my phone.
[Nook HD, HD+ Android Development] verygreen:
It's built into kernel already, JB requires it for quite a while for emulated sdcards.
[Nook HD, HD+ Android Development] jamus28:
Anyone else having trouble connecting the latest build to windows 7 with MTP? I get a "could no open MTP driver, errno: 16" in logcat. I can use PTP mode and ADB in recovery, but MTP constantly disconnects.
[Nook HD, HD+ Android Development] verygreen:
New experimental binary release cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip

This one has experiments touchscreen changes in by default since I've yet to hear any negatives about it and it's about ready for more wide testing, I guess.

Changes:

- experimental touchscreen sensitivity change

- usb ids changed to match stock

- swap support enabled
[Nook HD, HD+ Android Development] Elmoglick:
Another Nook App Workaround

The Nook app can be successfully downloaded and installed via the 1Mobile.com app.
[Nook HD, HD+ Android Development] webdroidmt:
Since we know that the current version of Google Earth doesn't work on our device, for anyone who needs/wants to have it on their HD+, I found an older version that seems to work ok. I tried 3 different versions and two displayed sluggishness as well as a graphical glitch, while version 7.0.1.8239 looks good.

I'm currently running Carbon rom but It should work fine on CM10.1. Here's a link: https://dl.dropboxusercontent.com/u/98505171/Earth_7.0.1.8239.apk

EDIT: Been playing around with this and while it finds your location and you can somewhat use the earth gallery, the search always come up "not found." So, it seems that the apk is pretty much useless...Sorry about that.

Mike T
[Nook HD, HD+ Android Development] rushless:
To get it to install, the current version of GE probably needs uninstalled first. Was the case for me at least...... I had not yet unistalled (in case a rom made it work).
[Nook HD, HD+ Android Development] webdroidmt:
Yes, that's correct but see the edit in my OP. Unfortunately, the apk isn't working correctly, kinda' rendering it useless except to play around with it. Too bad, I thought we had something here..

Mike T
[Nook HD, HD+ Android Development] verygreen:
new experimental sgx drivers

Ok, good news and heavy testing required! ;)

my contacts at TI indicated that google earth problem is a generic DDK bug (op updated), there's a fix in unreleased DDK.

The problem is, the unreleased DDK has buggy drivers and I imagine it had otherwise very little testing too.

I took a stab at fixing most obvious crashes that I was able to hit, and I hope there are no more, but please test this and let me know.

This fixes both Vector unit games and Google Earth from market.

You need to flash these drivers: new-sgx-ovation.zip

Please give it some good testing in 2D and 3D heavy workloads and let me know if you see problems (and most definitely please let me know if you don't! ;) )

If you experience crashes, gather /proc/last_kmsg for me, also a description of how did you trigger it.
[Nook HD, HD+ Android Development] webdroidmt:
You pop up like a magic genie. LOL Will test this and as always, thanks for your outstanding work!

Mike T
[Nook HD, HD+ Android Development] rushless:
All three Vector games work and Google Earth appears to work as well. I also tested a few other 3D games and all played fine, but only tested each a few seconds. Star Wars pinball games still work too.

I will test later with more games, Flash, browsers and video to see if current stability hold true :)