yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] webdroidmt:
Did some preliminary testing. I don't have many games but I tested Bard's Tale and it's working with no problems. Also tested my streaming apps, Netflix, HBO Go and Hulu Plus, all working well. I did have to clear app data/cache on Netflix and it was fine.

As for Google Earth, it force closes if you choose to do the quick tutorial on startup instead of saying No Thanks. It also force closes every time you click the "My Location" icon in the upper right corner next to the north indicator. However, with search working properly, Earth is very functional.

Btw, since I'm currently on Carbon rom, I did a clean install of the 7/3 CM10.1 so as to be playing on the same ballfield and the results were the same for Earth.

Thanks,

Mike T.
[Nook HD, HD+ Android Development] verygreen:
This is because we don't really have a gps unit inside.

It should be able to use wifi, but lack of gps seems to throw it off still. This crash has nothing to do with graphics, just lack of gps provider, it's happening on other devices too, so a workaround might emerge eventually.
[Nook HD, HD+ Android Development] webdroidmt:
Understood but the funny thing is, with those older version apks that I posted earlier, "my location" worked, or at least appeared to be working, as well as the quick tutorial at startup. However, the search function was a no go. So, I'd rather have it as is with search working and if an eventual workaround happens, all the better.

Thanks,

Mike T
[Nook HD, HD+ Android Development] rushless:
All systems appear go for the sgx update :)

I only use Earth to locate places and general info, so do not use "my location" anyway. :)

Very,

VERY good!
[Nook HD, HD+ Android Development] webdroidmt:
Actually, it automatically finds my location on startup from the wifi. It's just that it will force close if you click the my location icon, which is really no big deal. Just wanted to report results to verygreen.

EDIT:Scratch that, it goes to the last place visited on startup. LOL

Mike T
[Nook HD, HD+ Android Development] sorrowuk:
Where would this exfat support zip be ?

Does ntfs still work for microsd ? Or any filesystem that supports 4+ gb files?
[Nook HD, HD+ Android Development] dbrickg:
No problems with it so far. I've run extensive tests... for about 5 seconds :)

As always, thanks much and more
[Nook HD, HD+ Android Development] YOUCANNOTDENY:
After around 7 clean installs, with everything wiped, both in TWRP and CWM, I have finally identified the infinite boot problem app: Trebuchet! I can consistently produce and revert the problem now by changing one setting in Trebuchet: Wallpaper Quick Render.

Oh the headaches! No wonder I didn't have the same issue when using a Live Wallpaper; I hadn't even bothered to enable Wallpaper Quick Render!

Well, at least now I can set up my Nook in peace. Remember, if you have the infinite CyanogenMod boot logo problem, just go into recovery, wipe cache, and disable Wallpaper Quick Render when you are booted.

Green, any idea as to why this is?
[Nook HD, HD+ Android Development] Jd6J0r:
See:

http://xdaforums.com/showthread.php?t=2155363

From earlier in the thread:

Remember after flashing to shutdown then put in the exFat formatted microsd card in before booting up. My SanDisk uhs-1 class 10 64GB exFat working fine.
[Nook HD, HD+ Android Development] razzbaronz:
So far using newest beta and the patch you made for Google Earth everything is stable and running smoothly on my end. Great work!
[Nook HD, HD+ Android Development] ipilcher:
ext4 works just fine (in CyanogenMod; ClockWorkMod Recovery need to be tweaked to work with anything other than FAT32). You'll want to create the filesystem without a journal to make the card last longer.
[Nook HD, HD+ Android Development] KDHaro:
Nice catch and so easy to replicate. Here's a logcat from a Quick Render induced boot loop if it helps anyone track down the problem: Boot Loop Logcat
[Nook HD, HD+ Android Development] verygreen:
I guess this is going to be the stable build for some time, CM baseline is starts to get some drastic changes, plus I'll probably experiment with some riskier stuff too.

cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip

Changes:

- reduced heap growth limit to 64m

- upgraded to fixed SGX DDK 1.9@2291151 (this fixes Google Earth, and a bunch of games)
[Nook HD, HD+ Android Development] rkeller62:
Have been meaning to say that I'm not sure the heap growth limit setting is really doing anything for performance. I think the perceived improvement may be prophylactic from the reboot required to achieve the settings change. Also, even at 64, the static wallpaper sizing issue happens after using the tablet for a while. Reboot fixes the wallpaper for a while, then it sizes wrong with black borders on all sides until another reboot. Easy to see what I am talking about by setting heap growth limit to 32 as the static wallpapers will always size wrong, even after a reboot. I am using the the stock wallpapers and cyanogen wallpapers included in the ROM.
[Nook HD, HD+ Android Development] NotShorty:
Any way to remove the experimental touchscreen sensitivity tweaks? May be great for some people, but in landscape and portrait I get a very noticeable "judder" up and down if I click and hold on my screen. At least in the browsers I tried and the Reddit News app.

If there's a way to log this behavior for error reporting purposes, I'd be happy to do so, but if I can't remove the tweak I'll be flashing to the 6/30 build (before the 7/4 build I was on 6/13).

Thanks for any help. I'd like to keep the new graphics/driver tweak if possible...

Edit: developer options, input, pointer location

When tapping and holding on the right side of the screen in portrait (the edge with the power button), X: varies by + or - a pixel or two, Y: varies by a wider range, closer to + or - 5 pixels (I.e. 10 pixels of variation). Practically non-existant juddering like this on the left side...

Sorry if this would have been more appropriate if posted in the thread that is specifically for the touchscreen sensitivity tweak.

Edit2: thanks for the reply :)

Edit3 (sorry): yep, much better after flashing touchscreen-revert.zip for me.
[Nook HD, HD+ Android Development] verygreen:
Here you go, flash this touchscreen-revert.zip and it should restore previous behavior.

I am still gathering feedback on this
[Nook HD, HD+ Android Development] jamus28:
I dislike fake fixes as much as you do, but I honestly believe there's a small difference not due to reboots alone. I don't experience any wallpaper issues at 64m. Ive used hd and stock wallpapers for days.

I'm not invested in it being 64m or 96m, since its so easy to change for myself. I just one person, n=1. But Try going "no wallpaper" and testing for yourself the scrolling speed and app loading at the 2 values.

If you read on other forums, this issue is very contentious. The Google code page about it is very interesting, but still no consensus. One thing to say about 64m is many big ROMs for similar hw setups have gone to 64m with no ill effects.
[Nook HD, HD+ Android Development] verygreen:
In fact my reversal to 64m is just using standard tablet presets from CM (vs custom ones in the past), also fixed incorrect heap size limit that was too small.
[Nook HD, HD+ Android Development] jawain:
When switching to CM 10.1 is it possible to keep Barnes and Nobbles ereader?
[Nook HD, HD+ Android Development] verygreen:
Not the stock one. You might get the one from google play market, but I think the reports are, it's not at feature parity.

In theory it should be possible to resign the nook apps from stock so they work in CM, I saw a similar project goin on in Nook Tablet forums some time ago, though I don't know if they succeeded.

(resigning is needed to allow the nook app to access shared media stoarge, otherwise android framework complains about permission problems and marks the app as invalid).
[Nook HD, HD+ Android Development] Elmoglick:
Until you press the "My Location" button in the upper right. It immediately crashes.
[Nook HD, HD+ Android Development] mcord11758:
Due to no GPS in nook

check out XBMC the future of TV

http://www.xbmchub.com/forums/register.php?referrerid=5757
[Nook HD, HD+ Android Development] verygreen:
Well, with so much speculations about what overclocking of gpu might do for us on the HD+ front (I think it's not pressing on NookHD, as it's plenty fast there already), I decided to give this a good try.

Overclocking to 512MHz (from stock 384MHz, so 33%) is only stable if you disable voltage scaling (a non recommended mode of operation that TI claims will shorten life of your CPU).

Overclocking GPU to 1GHz is too unstable to even finish booting at around nominal voltage and I don't really want to play with jacking it into the sky, as I am way past my 30 days return period ;)

Never the less I can report to you that there's no noticeable improvement in the UI from this increased gpu 2d/3d cores (clocked separately).

Also antutu benchmark does not show any noticeable (to the naked eye) performance boost in 2d/3d. The "Sword swinging" scene still caps out at around 57 fps (so no change at all). The "ninja fight" scene seems to gain an fps or two here or there, but nothing major. In any case the total increase in 2d/3d total number is between 350 to 500, pretty minuscule.

The picture is much more bright in Nenamark2 where the stock fps of around 33.5 improves to 41.5 - nothing to sneeze at (the overall smoothness also increases), though still way less than 50.9 on Nook HD.

Overall I think there's no real benefit in doing this, as the cost in battery life is likely going to be pretty drastic (I did not measure that), and the potential impact of the chip life is also unknown.

BTW, I also noticed the nook gets a bit warm after those benchmarking runs, certainly more so than on stock kernel.

If you want to see the numbers for yourself and to try other workloads that might be important for you, I am providing this flashable zip (to revert, flash back the full cm zip), but be warned that I am highly not recommending you to try it, and if something breaks while you are playing with it, that's your fault alone, and I am not responsible in any way.

This will only properly work on my cm binary snapshots for ovation, other roms would likely not work if they use a different kernel than me.

overclock-kernel-ovation-1.zip
[Nook HD, HD+ Android Development] webdroidmt:
@verygreen

Since there isn't a separare thread for TWRP, I thought I'd ask here. My apologies in advance if this has already been addressed. Do you have plans to improve the interface?

The 2 things that stick out, overall response is slow and probably related, the nav buttons most times require multiple taps to engage. When I first started using this TWRP, a couple of times I thought it was freezing up on me but the button presses seemed to finally catch up and work.

I'm guessing it may have something to do with touchscreen sensitivity. Thanks for building TWRP and thanks in advance for your response.

EDIT: Found this theme for TWRP 2.5 on the TF700, probably the one and only theme available that would work with Nook HD+ resolution and it appears to be snappier than stock TWRP UI. The nav buttons on this theme are on the bottom left, as opposed to top right in stock, not sure if this makes some sort of difference in screen sensitivity??? Here's a link for the Holo theme if you're interested in taking a look.

http://xdaforums.com/showthread.php?t=2226679

Thanks,

Mike T
[Nook HD, HD+ Android Development] panchokoster:
mmm I see, I wonder why the usb otg-helper app is not working for me.
[Nook HD, HD+ Android Development] :
Thanks for testing that. Good stuff - despite the end result.
[Nook HD, HD+ Android Development] verygreen:
there is certainly some lag to ui updates, present on other devices, so I guess I cannot do much about it.

I cannot really develop all things that I run into, I barely hold my head above water with all the other broken things that need fixing.

I did a small experiment and applying the same ts sensitivity value adjustment as in the rom seems to help quite a bit, redoing the image just for that seems to be a bit overkill.
[Nook HD, HD+ Android Development] webdroidmt:
NP, I understand. I have a lot of respect and a great deal of confidence in your ability, figured it couldn't hurt to ask. :)

Thanks for your response,

Mike T
[Nook HD, HD+ Android Development] data2318:
I notice some gaming framerate increase, but after playing some games like Need for Speed Most Wanted and afterwards open the stock browser, the screen will flash (go off to black and go back on repeatedly), have to reboot to fix it. Any ideas what's wrong with the new sgx binary?
[Nook HD, HD+ Android Development] verygreen:
Framerate increase? new sgx drivers should not offer anything like that. I hope you are not using the overclocked kernel image?

check dmesg during this, do you have any unusual messages there?
[Nook HD, HD+ Android Development] robertchow:
reboot during sleep

my nook hd plus would reboot if leaving sleep for extended period of time.

never encounter reboot when using it.

I think some nooks do have this problem, but people just don't notice it.

to check if your nook has the same problem. just press reccent app button after wake-up from sleep for extended period of time, if recent app is empty, it is very likely that your nook has rebooted during sleep.
[Nook HD, HD+ Android Development] foolforfood:
I am having this exact issue as well. My battery also takes a nosedive after it reboots. What type of log should I try to find to give better detail?
[Nook HD, HD+ Android Development] ItsDon:
I have been using CM10.1 on m HD+ since I picked it up around Fathers Day. First let me say that I am very impressed, very. It is so much better than the stock ROM it shipped with, I am experiencing very few issues and I love that is it basically a 9" Nexus with a 1080p screen and an SD card slot. My biggest peeve tough probably has nothing to do with the ROM at all.

With the brightness set to max this thing gets hot, I'm talking Sophia Vergara hot. Lowering the brightness seems to be then only solution but I use it mostly outdoors where full bright is needed. Is this simply something I need to live with or am I missing a magical setting somewhere?
[Nook HD, HD+ Android Development] rushless:
Very,

I suggest reverting back to the default touch settings for now in your rom. I updated with 7/4 and then used the revert touch patch. All seems as good as it can to this point at least.

Seems there are two issues and they get blended into the same perception: UI lag and touch response. Regardless of rom, there can be a lag from the point an icon is pressed and an action takes place. The odd thing is this does not seem to ever happen when playing games using virtual pads or touch response in general when playing a game. The good news is the lag is not as bad as with stock and the stutter is gone (stock is BAD with stutter in apps and games).

For whatever reason, it appears to only "randomly" happen when activating (or closing) apps, navigating in the launchers or navigating sometimes in browsers/readers (Dolphin & Tapatalk are examples). The "UI lag" does not happen all the time, but a process that seems to trigger it is when in the Play market and when installing or updating apps. Bottleneck city then.
[Nook HD, HD+ Android Development] jawain:
Is there a rooting method with this ROM if so could someone be kind enough and point me in the right direction?

Sent from my NookHD+ running CM10.1 native emmc Thanks to Verygreen
[Nook HD, HD+ Android Development] mcord11758:
rom is already rooted
[Nook HD, HD+ Android Development] jawain:
Well slap me in the face and call me silly lol thanks!
[Nook HD, HD+ Android Development] dbrickg:
This sounds a lot like the problem several people were having with "soft reboots", where the nook would be asleep, and suddenly the cyanogen mod logo would be spinning, and you'd lose all your recent apps. The problem looked like it was with google maps trying to use gps. I think it can be solved by turning off "GPS satellites" in Settings / Location access. Here's a link to one of the eariler posts:

http://xdaforums.com/showpost.php?p=42143793&postcount=494
[Nook HD, HD+ Android Development] robertchow:
already turn off gps
[Nook HD, HD+ Android Development] dbrickg:
You might try uninstalling google maps completely. Originally I uninstalled maps, and that fixed the problem. But I really wanted to have maps, so I reinstalled it and turned off gps, and it continued to work. So, I thought maybe you could get away with simply turning off gps. But maybe you have to uninstall maps, too. Or, maybe your problem is totally unrelated to what we were seeing earlier.
[Nook HD, HD+ Android Development] grinch247:
how do I go about installing clockwork mod permenantly on internal sdcard?
[Nook HD, HD+ Android Development] dbrickg:
see the third paragraph in the first post in this thread:

"Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one...."
[Nook HD, HD+ Android Development] verygreen:
There is certainly some touch oversensitivity, at least on my device.

It's VERY noticeable in e.g. TWRP, where using sliders and scrollers is pretty frustrating unless the change to controller is added.

This has nothing to do with UI lag. Way too often if slowly sliding a slider, it would register a liftoff event prematurely, followed by instant touchdown and liftoff, pressing more buttons than what's asked.

I do not see any bad sideeffects from the touch on my device, there's a ton of positive feedback on that too. So I imagine what this means is different devices are a bit differently sensitive, or people have different tastes, or both. So the end result is I guess I need to move the touch sensitivity control app higher on my list so people could change sensitivity to where they need it.

Interesting that on NookHD touch in CM feels just right even without any changes (that I cannot make anyway), until I drop into TWRP, where it's even more of a nightmare than on NookHD+, huh.
[Nook HD, HD+ Android Development] jamus28:
Hi verygreen: The latest 7/4 build isn't booting for me. I've downloaded it twice. It's just stuck on the cyanboot universal bootloader screen.

7/3 boots fine.

EDIT: Even I fall for the stupid stuff. I was trying to flash the sdcard version.
[Nook HD, HD+ Android Development] Jd6J0r:
I'm running the July 4 build without any noticeable difference in accuracy, maybe a little better sensitivity but it's harder to tell after a reboot.

Today, got a Moto Android BT keyboard and mouse. They both paired easily. The Gmail key doesn't work for some reason but that's not a big deal.
[Nook HD, HD+ Android Development] verygreen:
Another binary release, this one does not have anything major, I am reshuffling touchscreen sensitivity framework now.

Also reverted accidentally included frequency boost patch that crept into 07/04 release somehow.

We still default at the new sensitivity, but the sensitivity rollback zip will not help you anymore.

Instead I spent entire day figuring how to do more things in android apps, and here's my next terrible UI attempt: NookTouchscreenSensitivityAdjuster-1.apk

This minimalistic tool would allow you to change various touchscreen parameters in GUI, so not need to play with adb.

There's a lot to be improved there, like autostart and saving values across reboots (both planned for the next release once I figure out how to do that in Android), also need to show values numerically not for just last update.

Right now this tool just lets you to play with values, the new values persist until the screen turns off (and the touchscreen resets restoring to default values).

The "save" button only saves the sensitivity setting at this time (i.e. the very top slider), but it only persists until next reboot, everything else is not save anywhere (since I am not sure there's any value in that and only incuded the other settings so you can experiment with them and perhaps get back to me with your awesome finds).

save button only works with this release, in previous releases save button does not persist anything.

the "reset" button resets values to the "old" values in the touchscreen, meaning pre-sensitivity change (so to 0x11, instead of the new 0x16).

So if you don't like the new sensitivity setting, your current reversal (Assuming you'll run this release at all) steps are: run the app, press "reset" press "save".

You will need to grant it root access, but only once per reboot.

Enjoy.
[Nook HD, HD+ Android Development] stephencwl:
Your sensitivity app has great UI. Simple and to the point.
[Nook HD, HD+ Android Development] BigMacca:
I'm still on the 07/04 release and it's been running faultlessly for a couple of days now.

To me it's definitely running smoother, I've not really noticed any lag to speak of - What frequency was left boosted in this build (CPU or GPU)?

Thanks again for all you brilliant work

Macca
[Nook HD, HD+ Android Development] verygreen:
I take it you did not try landscape mode yet ;)
[Nook HD, HD+ Android Development] verygreen:
Ok, after some struggles, here's the NookTouchscreenSensitivityAdjuster-2.apk

This version actually remembers the sensitivity setting (but not the other ones as I am not sure they are important yet) and retains it across reboots too.

It is important that you grant it permanent superuser permissions when you run it first, so that it's actually able to perform those actions.
[Nook HD, HD+ Android Development] samomamo:
Without you this rom Nook is history. Thank you for all you do. Thank you.

How can we donate? Is there a link or something?

I never donated so I don't know how it works.

Edit: OK found out how to donate.

TID 0XD66996XJ9356030 next vodka or beer is on me.

Thanx again.
[Nook HD, HD+ Android Development] benengyj:
I'm having trouble after updating from a previous install to 07/06 - the device keeps booting in TWRP only. "E:Unable to mount /boot" appears during the installation of CM as well. Help please?
[Nook HD, HD+ Android Development] stephencwl:
I guess you can always start from scratch with the bootable sd and install again.
[Nook HD, HD+ Android Development] benengyj:
I've tried that too. CWM doesn't show any errors but it still doesn't boot into CM.
[Nook HD, HD+ Android Development] stephencwl:
Bad download? Did you backup the stock 2.1?
[Nook HD, HD+ Android Development] leapinlar:
Are you using the emmc version of the CM10.1 zip? Sounds like you may be using the SD version.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] benengyj:
Redownloaded and tried again. This time it's also telling me that it's unable to mount bootdata. Currently stuck on the nook logo screen.
[Nook HD, HD+ Android Development] Rycon33:
The error "unable to mount /bootdata" doesn't do harm on my case. I've tried installing up to the 07-04 Rom and always encountered that error message in TWRP but seems no effect in ROM install at all. I haven't tried this 07-06 though.

Maybe try wiping user data.

Tapatalked from my bricked TX
[Nook HD, HD+ Android Development] benengyj:
Yes I'm using the emmc version that I got from the 1st page of this thread "cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip".

EDIT: Tried 07/04 and it doesn't work either. Just keeps booting into TWRP without sdcard.
[Nook HD, HD+ Android Development] drakester09:
[MENTION=3654172]verygreen[/MENTION]

Just had a reboot while Play Music was indexing some files from the SD card.

I'll send you the full last_kmsg in a PM.

The last_kmsg error says:

[ 6403.230682] kernel BUG at /home/green/nookhd/android/system/kernel/bn/ovation-ozoom/drivers/mmc/host/omap_hsmmc.c:1756!

[ 6403.230773] Unable to handle kernel NULL pointer dereference at virtual address 00000000

Damaged or corrupted SD Card could be the culprit? It's a 16GB PNY Class 10