yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] verygreen:
this is a multicore setup, we do not have cpu hotplug either, so the only time a cpu #1 goes away is at deep sleep and it's coming back on wakeup anyway.

so far all the stutter I have seen looks like IO-related (like early after boot while scrolling the app list) and it's very sporadic.

I'll look into trying to see if we can do something about separate gpu clocking and see if that helps anything.

I am still interested how much of a battery life drop is there with elevated cpu speed with screen on, so if anybody can assess, that would be great.

I imagine alternative approach is to just increase the boost quantum for elevated frequency after input.
[Nook HD, HD+ Android Development] drakester09:
The oddity to me is that the normal stutter that I used to experience went away once I started using a live wallpaper.

It improves the animation fluidity, which makes me guess that the GPU itself might be responsible of the jerky animations and frame drops. Min frequency might not be enough for the screen res.

A solution *could* be to increase min GPU clock or tune the thresholds for GPU clock increase more aggressively.
[Nook HD, HD+ Android Development] foolforfood:
Thanks for the response, I don't really understand the part about not having hotplug and how that affects what's going on, I did some reading on it but I am a little too dense to understand it. Any recommendations on reading material to understand this better?

As far as cpu1 disappearing I was remarking on it happening while my nook was awake, while I was making adjustments in kernel tuner. On the cpu screen it would go from showing both cpu0 and cpu 1 and all of a sudden cpu1 would disappear and only options for cpu0 were available. Maybe I have something wrong with my setup, I'm planning on flashing the 6/26 build a little later today.

Thanks again for your excellent work on this device :good:
[Nook HD, HD+ Android Development] rushless:
Probably a semantics issue, but IMO there are a few issues with the Nook HD+:

1. Random lag that can sometimes also accumulate to the point of needing a restart. CM seems no better than the stock rom, though stock did not seem to have as much lag issues with Google Play market when updating or installing apps. The lag results in long delays from starting an app, closing an app and also navigating in the apps. Apparently regardless of scenario, the device can be smooth one minute and laggy the next, regardless of stock or CM. Play market can trigger it, but not the only apparent cause.

2. Stutter while playing games. The stutter was in most games and really got bad with library sync (which kicked in way too much). With CM, there appears to be no stutter when playing games, beyond the usual average Android device occasional stutter (due to the OS and happens with every device I have used- iPad included). Night and day as far as stutter with CM.

3. Slow loading of apps and really noticed with large size games. This is also gone from CM, besides one game that I notice: Asphalt 7, it takes sometimes a few minutes to load a level (several seconds on the S3, Excite 7.7 and TF300). All other games that took a LOOOONNNG time on stock, now load fast with CM. Must be some data table format that freaks the Nook out with A7. Two Nook HD+ with same result.

The one odd issue though is after testing two Nook HD+ tablets, I can confirm that stock 2.1 installs and updates apps much faster than CM and does not lag as much during that process. Using Google Play market tends to be a laggy experience with CM and usually best to leave the device alone and let it update the apps and not try to multi-task. The market issue seems to happen a lot, but not all the time.

Update: As I mentioned in a review, stock 2.1 updated apps and was smoother in that process than most devices I had owned. Some Android devices can be kind of slow to install and update apps, but the Nook HD+ with CM seem slower than normal. The TF300 is also slow updating apps, but not as bad with the lag. Still, the game stutter and slow game loading is gone with CM and those were IMO the worst of the three apparent evils. On second thought, the lag is equally evil, but good to be rid of the other two.
[Nook HD, HD+ Android Development] verygreen:
these you can safely ignore (I guess I can just comment them out).

I *think* wifi with bt don't work all that well, and the range is greatly degraded, s oyou might want to try to position your headphones closer to the Nook and see how much would that help.

hard to tell. I wonder how well does it work in stock?

Also it seems all traces of "bt coexist" code (that is bt working with wifi at the same time) have disappeared from kernel drivers. Either because they are no longer needed or for some other reason.

The only a2dp device I have is Sony Rolly, and it only works reliably over BT if it's very very close to the Nook, as in, standing on the nook or is withing a couple of inches from it. (though I did not try with newer wifi drivers).

Strangely enough my bt mouse works from quite a distance, though (required bandwidth is much less too of course).
[Nook HD, HD+ Android Development] Jd6J0r:
Thanks for your response, vg.

From the link I posted earlier, it looks like it's this logging line in the github source:

ALOGI("vendor op - %d", opcode);

in libbt-vendor:

int ti_op(bt_vendor_opcode_t opcode, void **param) {

From what I can tell (I'm not an Android programmer), op code 7 maps to:

BT_VND_OP_LPM_WAKE_SET_STATE

in:

https://source.android.com/devices/reference/bt__vendor__lib_8h.html

(I wonder if it needs to do this every 14-70ms??)

I tested it very close to the Nook and that doesn't stop the messages or the audio cutting out. I don't have a problem with the headset with my phone so it points to either a hardware or software issue with the Nook.

I couldn't get this particular device to work on stock (Sony MW600). That's one of the reasons that I jumped into CM quickly and haven't regretted it! I do listen to music a lot and Bluetooth is very convenient, when it works.

Thanks for your observations on your Rolly. If anyone else has feedback on other devices, I appreciate it.
[Nook HD, HD+ Android Development] verygreen:
It does not, just a leftover debug from initial implementation, it seems.

That commit you reference removes it, though it does not change any logic.
[Nook HD, HD+ Android Development] Jd6J0r:
Thanks. You're right, looking at the source, it looks like BT_VND_OP_LPM_WAKE_SET_STATE is a no-op. If you can remove the ALOGI line in your next drop, I'll test it out and see if it makes any difference (other than making my log file a lot cleaner, LOL).
[Nook HD, HD+ Android Development] verygreen:
Well, so for those who absolutely must have ability to play vector unit games like beach buggy, here's sgx driver rollback. Try it and let me know if it broke anything, I know it fixes beach buggy blitz because I specifically tried it.

(I also wrote an email to their support asking them to look into their incompatibility, so hopefully they'll fix it).

Grab your fix here: oldsgx-ovation.zip
[Nook HD, HD+ Android Development] :
On the 6/26 ver. Not sure it makes a difference - at least nothing noticeable. Battery life could be worse but didn't notice that either.
[Nook HD, HD+ Android Development] ipilcher:
FYI, I believe I figured out what is causing this error (and a possible fix/workaround). See http://xdaforums.com/showpost.php?p=43032710&postcount=834.
[Nook HD, HD+ Android Development] rushless:
Kind of disturbing the dev blamed an audio issue and the Nook. Thanks for the effort :)
[Nook HD, HD+ Android Development] verygreen:
So, I just tested, with yesterday's binary drop my sony rolly actually works about7 ft from the Nook, any more and it starts to stutter.

That's with wifi on and connected too.
[Nook HD, HD+ Android Development] renthispace:
It is an issue with android 4.2.x. I have audio cutout on my galaxy s3 through Bluetooth to my deck in cm10.1 rc5. Google admitted Bluetooth issues and will (hopefully) fix it in 4.3. Google for android issue 39633.
[Nook HD, HD+ Android Development] bakageta:
I've got a pair of Motorola S805's laying around that I'll charge up and poke around with too, I haven't used them in quite some time but they had excellent range when I did.
[Nook HD, HD+ Android Development] dbrickg:
I've got one of those little Divoom bluetooth speakers, a Bluetune Solo, and it seems to work just fine with the nook about 10 feet away. It did start to cut out when I took the nook into the other room, maybe 20 feet away, especially when I was standing between the nook and the speaker. There doesn't appear to be any wifi time out, either. I've only been running it for about 15 minutes. When you say it times out "after a while", how long is your "while"?
[Nook HD, HD+ Android Development] Jd6J0r:
Thanks for your feedback. I should have been clearer. The WiFi connection fails after a few hours. The dropouts in audio start within the first half hour.

Are you seeing the "vendor op - 7" log messages every 14-70ms?
[Nook HD, HD+ Android Development] dbrickg:
Yes, lots of vendor op - 7 messages... pretty obnoxious. running logcat gives me a nearly continuous stream of them. logging like that doesn't contribute any useful information. it should be turned off. or have something like some unix logs, "the previous error occurred 4568 times"...

I've got bluetooth running now and will let it run for a few hours. For the wifi, how do you have it configured? Mine's set up to keep wifi on during sleep only when plugged in. Do you have your nook plugged in? Is the screen turned on?
[Nook HD, HD+ Android Development] Jd6J0r:
I agree on the log. Hopefully, verygreen can comment the obnoxious line out.

My WiFi is always on during sleep (verified with Battery Stats+ (dl'd from fdroid.org)). The Nook is not plugged in when the problem occurs, the screen is not turned on after I start the music.
[Nook HD, HD+ Android Development] dbrickg:
So, after a couple of hours of running music via bluetooth to my Bluetune Solo about 3 feet away, I haven't noticed any audio drops. But I do see the wifi connection stop working after 15 to 30 minutes. I reset the wifi during sleep to "always on", but I find that the connection would drop and Settings / Wifi would show my AP as "out of range". If I turn wifi off and back on, it picks up again.
[Nook HD, HD+ Android Development] :
I might be reading into this wrong but it really does sound like only an Interference problem. Only not being a great word, as interference is a total pain.

I do not have wifi drop outs without bluetooth unless from bad signal. If you have two plus competing APs with unique logins CM can get stuck on the weaker AP during various times if both are remembered.. but I don't think your set up this way.

Never had to deal with it (at home only rare use of ps3 controller). But wifi is absolutely fine working here.

http://www.dbriers.com/tutorials/2012/08/wifi-interference-with-bluetooth-mouse-speakers/

"How to fix Bluetooth and WiFi interference

Move Closer - Another solution is to move Bluetooth device (mouse, printer, keyboard, etc..) closer and directly in the line of site of its USB access point. The less physical interference there is the better the device may perform.

Switch channels – Your Bluetooth device may allow you to switch channels and avoid interference. This method is primarily used to avoid interference with other Bluetooth devices so this method may have limited success.

Use Wireless USB - To solve these interference woes you could stop using Bluetooth and purchase wireless USB devices which occupy a different frequency range(3.1 – 10.6 GHz), and can avoid wireless interference with WiFi Ethernet connections.

One last consideration is to purchase a different brand Bluetooth device or go back to wired USB instruments. No one option is guaranteed to work, but hopefully this gives you a decent foundation to why WiFi and Bluetooth interference occurs."
[Nook HD, HD+ Android Development] fredfishstick:
Is there any way to enable tablet ui with this ROM? Thanks in advance.
[Nook HD, HD+ Android Development] dbrickg:
See this thread... new versions are released from time to time, but it's currently a bit out of date:

http://xdaforums.com/showthread.php?t=2275939
[Nook HD, HD+ Android Development] jamus28:
Doesn't seem to make a difference. Reading through the thread, other people seem to notice the same. Or maybe I've read wrong?

Granted, I've never noticed lag. My biggest issue is a crash I get with webview browsers (naked and boat browser), but it may be the apps themselves and 4.2.2.

My obsessive-compulsive self (regarding the battery) hopes that you revert to the 400 mhz idle for future builds. I've yet to get a full battery readout for you, but soon. Other devices with the same processor have no problem idling at 384mhz and lower
[Nook HD, HD+ Android Development] verygreen:
try sgx rollback to see if that helps any?

well, it does not help indeed, so I am reverting the change anyway.

The problem seems to be in a bus bottleneck somewhere.
[Nook HD, HD+ Android Development] verygreen:
New binary snapshot. cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip

Changes:

- Rolled back increased cpu speed when screen is on change.

- a bit different omapzoom-based kernel. Decreased voltage at highest clockspeed as per TI documentation (they also recommend to raise voltage at low speed, but I imagine we don't want any of those).

- switched external bluetooth to in-kernel one. Also removed logcat spam when using bluetooth.

- included zram module
[Nook HD, HD+ Android Development] Rycon33:
Just received my Nook yesterday and today flashed this ROM. Thanks for this. Keep up the good work.

OP, is the zip changed? I downloaded it 2 hours ago.

Tapatalked from my bricked TX
[Nook HD, HD+ Android Development] Golf_4711:
Thanks for this ....

Hey m8,

Thanks for this huge ROM for HD+

Regards from germany

Golf ;)
[Nook HD, HD+ Android Development] DyDx:
How's the stability of the latest ROMs? I've been hesitant to install this until I'm sure I want to keep the HD+ (I've had it for < 1 week), but I'm finding I like it quite a bit and even the stock ROM is quicker than I expected. However, I've been having too many random reboots, which seems to be a widespread-ish problem for the HD+. Do the latest ROM builds have random reboot issues, anyone?
[Nook HD, HD+ Android Development] thegracious:
I have no doubt about that. The random reboot is solved for several months ago.
[Nook HD, HD+ Android Development] :
Still testing... edit... removed stuff... still have reboots & tweaks did little to nothing where they are probably not worth anything.

Shame I can't find any tweak apps for the gpu besides one paid app with a setting or more- not buying it.

I see the word solved and know for sure its a constant occurrence that is unsolved.
[Nook HD, HD+ Android Development] izi975:
I have rooted my wifes HD+ on the 16th. It is currently running the 6/24 ROM. She has been playing games and doing a little FB. No random reboots except once, probably caused by me trying to do something (can't remember what). It has been running great. I have also not noticed any lag, but it has been runnign Nova Launcher Prime since CM 10.1 was put on it.

Haven't tried the Bluetooth yet, but overall it has been fast and reliable device since running CM 10.1.
[Nook HD, HD+ Android Development] thegracious:
well, i do agree with you that it is a constant occurence. however, I satisfy with the current version of this rom, no reboot for some months, and the battery is good. For me, that is enough (am I too easygoing? :angel:). But you couldn't ask for a better things with that price.

Whatsoever, the choice is yours. :D
[Nook HD, HD+ Android Development] rushless:
A few questions to avoid me reading wrong and misunderstanding :)

1. Does the 6/29 version change the low while screen on back to 400 mhz?

2. Does this version use internal storage for apps and external is the micro sd?

3. I am still on the 6/8 version, are there any performance improvements compared to 6/8 beyond USB related drivers that might not be listed?

Thanks
[Nook HD, HD+ Android Development] verygreen:
yes.

yes and always had.

It's very hard to judge really.

my benchmark numbers are all over the place from 9500 to 10100 on antutu. The 3d performance might be a bit better with the yesterday's changes.

The battery might be a bit better, but again not much and would need long testing to accurately determine.
[Nook HD, HD+ Android Development] rushless:
Thanks! I have a feeling the driver downgrade will make the Vector games work and the Zen Star Wars tables stop working. That is how it was with stock 2.1.

BTW, I just discovered that since the last update, Asphalt 7 loads slower on all devices.
[Nook HD, HD+ Android Development] dbrickg:
Thanks much, verygreen. Installed 20130629 and running for an hour or so now.

Just a note for Jd6J0r: I'm not having any trouble with bluetooth audio cutting out... but I never have had that problem. I'll be interested to see if this rom fixes your bluetooth headset's problems. I am, however, still losing wifi after half an hour or so of running bluetooth. It just occurred to me that I'm not sure if wifi dropped out before without bluetooth. I'm going to turn off bluetooth and test again, see if wifi stays up.
[Nook HD, HD+ Android Development] Jadefalkon:
I've been on this Rom for three weeks after playing with stock for a few hours. It has worked flawlessly for me, no reboots or lockups and fantastic battery life. I was the CM10 I've tried on my phone worked like this. Someone suggested that the Nook is a perfect platform for CM since it doesn't have all the bells and whistles, I think they were correct based how well its working for me.
[Nook HD, HD+ Android Development] Jd6J0r:
It seems to me that it is working better with the new ROM. I've only used it for an hour or so but I've only had a couple of drops. I was able to get around 30' away without any drops because of the distance. Big thanks to verygreen. Also for commenting out the annoying logging message (I verified it's not in the log file). I also found a toggle setting on my router, ASUS RT66U running TomatoUSB, for Bluetooth Coexistence. I was going to set my AP to only use 5 GHz but then found that the HD+ doesn't support 5 GHz. Anyway, worth checking if your router has the Coexistence setting (under Advanced -> Wireless in TomatoUSB).
[Nook HD, HD+ Android Development] rushless:
Silly question time. If just updating from 6/8 to 6/29 version, do I need to add the Google apps again, or simply install 6/29 over 6/8?
[Nook HD, HD+ Android Development] dbrickg:
Sounds like an improvement. Glad to hear it.

I just checked my wifi, and, though it's hardly a conclusive test, it was still up after about an hour without bluetooth. So it sounds like it could well be an interference problem of some sort. Just looked at my (older) wifi router, and didn't see any option for bluetooth coexistence. At any rate, it's not really a problem for me, since I almost never use bluetooth.
[Nook HD, HD+ Android Development] Jd6J0r:
No, you just install the new ROM. It will go through an update app phase the first time you boot it which takes a minute or so.

---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------

It's looking good. I highly recommend TomatoUSB or another open source ROM, if your router's capable. Many more features than stock and more secure.

I just finished up another hour or so of video and audio testing with Bluetooth without problems. I did switch AP's at one point [damn plaster walls with wire mesh!] and that went smoothly.
[Nook HD, HD+ Android Development] rushless:
I see now what you mean by, "- /sdcard now points to internal storage". Though a lot of apps install no problem, some get lost when installing data files. Quake 3 now needs the data files in the internal storage (as normal). With your 6/8 version, I had to have the Quake 3 data files in the micro sd card. I will test now and see if NBA 2013 now works, since that appears to be the problem with that game and a few others.

This would mean only the Vector games do not work of what I tested.

BTW, what was the build prop change you mentioned to get other games working? Also, do you change the prop to get them to install and then change it back to get sound working?

Thanks!
[Nook HD, HD+ Android Development] dbrickg:
Once again, inconclusive, but I just ran bluetooth music from my Samsung Note to the Bluetune Solo for an hour or so, and wifi never dropped. So, if the Nook's problem is due to interference, the Note deals with it more effectively.
[Nook HD, HD+ Android Development] rushless:
Yep! The the sdcard change, post 6/08 release fixed games that kept trying to read the micro sd for data and would crash. Mini Motor Racing, NBA 2013 and others that did not work now do! :)

Now the only games that do not work are the Vector games. I prefer the Star Wars pinball games to work (they do with the newer drivers) than the Vector games.

Very, Bravo! :)
[Nook HD, HD+ Android Development] fredfishstick:
Has anyone tried to use the update to switch to tablet ui? Hate to flash it and wind up screwing up my HD+ its awesome w cm10.1
[Nook HD, HD+ Android Development] data2318:
OK, for whoever that has wifi disconnect issues, here's the way to fix it:

Add this line to your build.prop:

ro.platform.has.sleeppolicy=false

This will make your wifi always on unless you turn off wifi. Tested for 24 hours, working.

You can add this line into the build.prop in the rom file to flash or used a text editor or buildprop editor to do so, but for the second option you have to reboot to make it effective.
[Nook HD, HD+ Android Development] leapinlar:
Just turn it to landscape before you disable auto-rotation and it will be locked in landscape rather than portrait. Turning off auto-rotation is supposed to lock it in the mode it is in.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] YOUCANNOTDENY:
I have a problem with the Nook getting stuck on the spinning CyanogenMod logo after a reboot. I found that the problem can be fixed temporarily when I wipe cache in CWM, but of course it is inconvenient to do every time. This happens after a clean flash and after Google downloads all my apps and restores their settings. Could it be linked to a single app? I don't think it happens when there are no apps on the Nook.
[Nook HD, HD+ Android Development] KDHaro:
I had the same issue. I think it was because I forgot to clear /data the first time around. Flashing was useless. I ended up formatting everything from inside the Mounts & Storage Menu (which was overkill but I was really annoyed with it). Since clean flashing everything back, I have not had a single boot issue. I would start with the "format /data and /data/media (/sdcard)" option and then do another clean flash.

Afterwards, I did restore all my apps from TIBU to see if it was app-related but even with everything back in place there were no further boot issues.
[Nook HD, HD+ Android Development] Ogre6473:
Hey guys. I have some apps that refuse to see my SD card. I know there's a fix somewhere in the threads, but it'd take forever to hunt it down. Can anyone repost the link to the zip? Also, why isn't it on the main page of this thread as an option?
[Nook HD, HD+ Android Development] dpham00:
i am using the 6/29 build, I am using a Logitech iPad case/keyboard, which works fine. but when i use my Motorola bluetooth keyboard, it cuts out wifi. as soon as i disconnect the Motorola keyboard, wifi works fine again. i tried rebooting and no difference. anyone else have this problem?
[Nook HD, HD+ Android Development] leapinlar:
It is on my HD/HD+ CWM thread linked in my signature. See item 4 there.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] verygreen:
new update : cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip

This time usb audio actually works, I tested it personally ;)

also finally got around to passing serial number in a way that android can find it. No more 1234567890ABCDEF ;)