yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] Sherip:
The first time I tried to edit the prop file in /system (for LCD density) I had the same problem. I resolved it by going into Tools - Root Explorer - Mount R/W (in es explorer) and enabling RW for system. I never understood why others apparently had no problem editing that file.

Sent from my HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] ItsDon:
Verygreen I must be the odd ball here. 7/16 is running spot on. WiFi seems stronger and more responsive than 7/12, battery drains slowly when sleeping and except for the occasional black screen when unlocking everything is working very nicely. Thanks dude :)
[Nook HD, HD+ Android Development] rushless:
I finally got it to work with an app in the market called build.prop.editor. Device seems to be working better now. Will test wifi more to see if a fluke. Rebooted and the settings are changed.

Update:

So far so good. The lag is back to "normal" and seems the wifi was a fluke, since nowhere near the intermittent dial-up like speed of 7/12. :)
[Nook HD, HD+ Android Development] paaco:
EDIT:: this looks completely off topic and out of nowhere quoting from so far back, just realized that haha

Found this thread when searching for overclock stuff for Nook HD+. Maybe a stupid sounding question, if GPU OCing isn't feasible with our hardware. Is it possible to set an HD+ to run at a slightly lower resolution? Similar to how you can change it in your GPU settings on your computer. Since the 1080P resolution is pretty much the limit of the GPU in the device, if it would be possible to make the screen run at 720p instead it seems like that would help a ton, and I seriously doubt 9 out of 10 people could even tell a difference on a screen so small between 1080p and 720p.
[Nook HD, HD+ Android Development] Danrarbc:
It's likely possible, but you wouldn't want to do this.

It'd look horrible.
[Nook HD, HD+ Android Development] paaco:
I really know nothing about our screens at all, but it doesn't seem like it would be that bad. If you can get a 42" TV to run at 720p and it looks crystal clear why cant a much smaller screen run at that same resolution and look good?

I'm not saying you're wrong, I honestly don't know, I'm just curious.
[Nook HD, HD+ Android Development] stephencwl:
Thank you. Here's a link to my last_kmsg after crash from transferring big files over WIFI.

It's too big for attaching here and I don't want to post the big big text dump in a post.

So here's the link:

https://app.box.com/s/0oi5uou4jpm6mc23eb6k

Thank you.
[Nook HD, HD+ Android Development] SCWells72:
Similar to the question above about targeting 720p on the 1080p display, if the HD+ really is constrained on the GPU, especially if it's I/O bound, would it help to lower the color depth to 16 bit? That would certainly decrease the amount of data being pushed by 33-50% (depending on whether it's 24-bit or 32-bit now) with only a slight lowering of image quality...unless I'm wrong about how this image data is encoded as it's being passed around, of course...
[Nook HD, HD+ Android Development] rushless:
I have a TF300 and Excite 7.7 that are both 720p. I do notice a big difference. If the Nook HD+ was 720p, I would not own it. The lure is the display IMO. Catch 22: Sexy display, but some lag- profoundly offset by the price :)

That said, if this is a person's only tablet, I can see your point :) Be nice if there was a 720p / 1080p on the fly, scaling switch :) That way we could switch to 720p when we need it. 3D gaming is a good example. Some games choke with the 1080p, since no down scaling in a lot of games.
[Nook HD, HD+ Android Development] bckrupps:
i agree the screen makes a huge difference. load up a pdf or a magazine in zinio. night and day but i think the option would be cool when you need speed over looks
[Nook HD, HD+ Android Development] geraldcheyne:
Sandisk Ultra 16 GB working

Just to say I reverted to using a Sandisk Ultra Class 10 16GB SD card approx 3 weeks ago - started with 20130615 updating each improvement, so now using 20130712. The SD card works perfectly although very occasionally the Nook automatically reboots into stock ( it might have happened 2 times in a week of every day use and not in the middle of doing something). So I am happy to continue using the card.
[Nook HD, HD+ Android Development] Ogre6473:
On a display this size, you could definitely drop it down to 720 without it being very noticeable. You should be able to do that by changing the DPI in the buildprop I think, unless I'm misunderstanding the correlation between resolution and DPI. As far as testing, someone just needs to do the math for what to set it to.
[Nook HD, HD+ Android Development] paaco:
I was gonna be the guinea pig and try that, but I see no DPI or resolution settings in build.prop :(
[Nook HD, HD+ Android Development] verygreen:
Thanks.

This crash does not seem to be related to wifi itself, your sdcard is one of those that the Nook does not like, and so there's a bunch of IO errors in the logs trying to write to it and then something in the driver eventually trips on a NULL pointer and dies (people never check the error exit paths are correct, sigh).
[Nook HD, HD+ Android Development] old_fart:
Crystal Disk Mark does an excellent test / benchmark on the SD Cards. One consistent lapse in understanding of its results is that people go "ooh & aah" over the speed benchmark ( the sequential speed one . . . and it not all that important, imho ), when they REALLY must pay attention to the third and fourth test ( the 4K and 4KQD32 - I/O ones ).

hth
[Nook HD, HD+ Android Development] phammichael:
I exchanged my Nook HD+ today under warranty. My new Nook is a lot faster! And my touchscreen doesn't jitter as much when I long-touch something.

I did a restore of my apps from the Google Play store, so I don't think it was an app that was slowing down my old Nook. Maybe one of my partitions was corrupted on the old Nook? Or maybe I got a newer revision of the Nook?

One thing that I did differently this time was that when I got the Nook, I immediately installed CWM and CM. On my old Nook, I had loaded the B&N OTA firmware before I installed CM. Maybe the OTA firmware from B&N was causing slowness and poor touchscreen performance with the CM ROM?
[Nook HD, HD+ Android Development] verygreen:
New binary update cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip

Changes:

- Picked a bunch of changes from omapzoom 3.0 tree: voltage updates, some fixes and such.

- Reverted davlik vm changes implemented on 7/12 that seem to do more bad than good

- ro.hwui.disable_scissor_opt=true by default, seems to have some slight positive effect on scrolling in my testing.
[Nook HD, HD+ Android Development] renthispace:
Just wanted tofollow up, flashed to 7/16 and battery usage is back to being flat (no usage) during screen off. Wifi seems normal and is going to sleep normally while screen is off.
[Nook HD, HD+ Android Development] stephencwl:
Great. Thank you for the hint. I swap another SD card and it's all working good now.

By the way, the not so 'Nook' friendly Sd was Kinston 64GB SDXC formatted in exFat.
[Nook HD, HD+ Android Development] paaco:
Thanks for taking the time to make improvements for us. One question though, did you make any more changes to the wifi for this update? Getting really slow speeds. it seems to connect and work just fine. I downloaded an app from the play store and it seemed to take forever. After it finished i ran a speed test and got less than 1mbit down, rebooted nook, waited 5 mins and repeated test with same result. This is on a 50mbit connection with the nook 20' from the router showing full bars of signal strength up top.
[Nook HD, HD+ Android Development] e.mote:
Speaking of wifi, I'm wondering if the Nook can be made to accommodate external USB wifi adapters. It's already doable for other tabs, and having an external dual-band unit would be a big boost to the Nook's range and bandwidth. I'm not talking about wardriving with BT5 (although that's of course a use case) but for simple extended range uses. The benefit isn't from having a different radio as much as a higher gain external antenna.

I understand that drivers for popular chipsets can be added to the kernel via modprobe, but am curious as to how Android 4.2 (more to the point, CM 10.1) allows for secondary wifi adapters in its interface.

Here's a couple of setups I'm envisioning: a basic 2dBi rubber ducky antenna for omni coverage,

or a higher gain 12dBi mini-sector cube antenna for more directional coverage (60-deg arc).
[Nook HD, HD+ Android Development] thirumalkumaran:
Why TF we need to do that?
[Nook HD, HD+ Android Development] Jack45:
1. I thought that e.mote clearly presented the benefit he believes the modification would have.

2. Rather than "Why TF we need to do that?", a respectful request for clarification would be more appropriate.

We're all in this together, and based on his knowledgeable HD+ contributions, I suspect that his suggestion has merit.
[Nook HD, HD+ Android Development] Ogre6473:
It's not ro.sf.lcd_density?
[Nook HD, HD+ Android Development] williamlaw:
fixed
[Nook HD, HD+ Android Development] old_fart:
.

A few months back I installed a directional on the center coaxial post of my 'dark knight'. Before I did it, I thought long and hard about it being stupid and wasting a lot of money... Imho, they charge triple what they should for a simple chunk of plastic. There are probably websites for people who wish to build a directional themselves. But because I'm a guy, I bought one anyway... I used wifi analyser before and after to validate that it worked. But it wasn't a ( Woo Hoo, Wow ) big change. I should have kept my money.

hth.
[Nook HD, HD+ Android Development] tebra:
go to settings > system > on/off menu options
[Nook HD, HD+ Android Development] paaco:
I'm far from an expert on the topic but I didnt think they were the same thing. Gonna look into it more I suppose =/

Now that I think about what pixel density is, I guess you could effectively change the resolution by changing that. Boy am I slow today haha.
[Nook HD, HD+ Android Development] williamlaw:
thanks
[Nook HD, HD+ Android Development] verygreen:
In fact underlying number of pixels would not change, it's just the high level idea of resolution would change in Android, but he kernel and hardware would still push around the full amount.

Unlike with movies where there is hardware scaling, for UI we push he entire picture around.

It might be possible to enable some sort of scaling so that we use a smaller framebuffer , but I have not looked into feasibility of any of that yet.

Even if it's possible, it would be highly unlikely to be switchable on the fly without a reboot.
[Nook HD, HD+ Android Development] paaco:
Thanks for clearing up exactly how that works. Learn something new here every day :) While I think it could be useful in certain circumstances to be able to scale resolution easily. I don't know that it would be worth the time and effort to get it working. I would assume that for 99% of people stock works fine and the small amount of interface lag and impact on gaming the 1080p resolution causes probably doesn't matter to most people.
[Nook HD, HD+ Android Development] e.mote:
>A few months back I installed a directional on the center coaxial post of my 'dark knight'

I'm assuming you're talking about the Asus router. Directionals generally don't work well indoors, ie when there is no direct LOS. Because of signal deflection, there's no guarantee that a signal will come from any particular direction. Omnis are generally better for indoors; directionals are best for open-air use.

IMO, boosting sensitivity on the router end isn't as productive as doing it on the device end (hence my suggestion), or using any of several alternatives, eg bridge/repeater/powerline/MoCA, for areas of weak reception.

What you say is true, that many (most?) of the so-called high-gain antennas marketed to consumers are placebo garbage. Many of the standalones come with long, thin pigtails that cause more signal loss than whatever gain the ant can achieve. The screw-in 'replacement' types are almost always worthless. It's not hard to find surplus/used commercial antennas, however.

Getting back to the Nook. In my experience, the Nook's 2.4GHz wifi is consistent but low bandwidth, assuming no congestion. It's good enough to deliver compressed 720p (eg a typical MKV video), but 1080p or any high-bandwidth use is off-limits. Jumping onto the 5GHz band would help. Likewise, range can be greatly boosted with an external directional. For the person who asked why, wifi coverage isn't everywhere, and being able to aim a directional out the window to pick up a signal can be the difference between Internet or no Internet.
[Nook HD, HD+ Android Development] :
Unfortunately, I have no error logs for this... 7/19 version

Browsing Play Store

Lost use of back, home, recent buttons

Slowly lost use of status bar and main screen

Managed to reboot through power button

Found it started in safe mode. Minimal access to apps.

Reboot from power button.

Back to normal other than missing widgets from three different apps.
[Nook HD, HD+ Android Development] rushless:
What rom were you using before? I have not had these issues going from a specific rom update to update, but have if jumped to a different rom without starting from scratch.

I am using 7/16 at the moment.
[Nook HD, HD+ Android Development] stegg:
Is it possibile to have a transparent navbar? :) with exposed framework I got transparent top-bar, but for the bottom bar there's nothing

Inviato dal mio BN NookHD+ con Tapatalk 2
[Nook HD, HD+ Android Development] :
Have used verygreens emmc rom for weeks now and have done a clean install of it. Dirty update to 7/19 this morning.

Reverted back to 7/10 backup for now - it worked well enough though 7/16 appeared ok enough.

Always forced reboots, that's the norm here. The widget loss is nothing new just rare. Safe mode is new. Loss of touch not new but how it happened was new. Too much to keep track of.

It just might need new clean install going forward - don't stay on a version long enough to find out =) - think the widget loss still could be an issue not related to cleaning. If anything I will just use the widgets on my phone and remove those apps from here to see what occurs here.
[Nook HD, HD+ Android Development] verygreen:
Hm I don't even know what is a safe mode in Android ;)

So turning the screen off and on did not bring the touchscreen back I assume?
[Nook HD, HD+ Android Development] rushless:
So, are the issues posted about the 7/19 rom correct, or a fluke to Northreign?

Update:

Must be a fluke, since all good with 7/19 here. I cleared the partition and dalvik caches before installing, but left my apps alone (as always with this rom). I notice this update for some reason booted back up much quicker. Typing this message on the Nook.

Seems like a lot less lag than the last several updates. Maybe best yet. Testing more to confirm.
[Nook HD, HD+ Android Development] Danrarbc:
Is there a way to adjust memory clock alone? Memory bandwidth has a huge impact on performance with high resolution displays.
[Nook HD, HD+ Android Development] rushless:
Very, I think you nailed it with this one. This along with a slight sensitivity adjustment with the touch app so far seems a hit. For me at least, this rom has given me the best experience with this device.
[Nook HD, HD+ Android Development] bckrupps:
I agree it is an outstanding build. I can't imagine there is to much more tweaking that can be done but verygreen continues to find more ways to get the most out of the hardware. thanks.
[Nook HD, HD+ Android Development] spartan4585:
Thanks verygreen. I loaded the latest 0719 rom and it make my Nook a little snapier.

Props and gratitude for all the work you do for us.
[Nook HD, HD+ Android Development] Evanescense:
I have also noticed the improvements in 0719s update. It's much more smoother and looks better. Thanks.

Sent from my Nook HD+ running CM 10.1
[Nook HD, HD+ Android Development] schahr01:
It appears that the codec/file/files for handling AC3 audio are missing. I checked with both MX Player and BSPlayer and while the video plays beautifully, I get no audio specifically for files where the audio stream is AC3.

Here's the audio stream info from VLC -

Codec: A52 Audio (aka AC3) (a52 )

Channels: 3F2R/LFE

Sample rate: 48000 Hz

PS - I have CM10.1 on my kindle fire and the same video plays fine there
[Nook HD, HD+ Android Development] Sherip:
Mine's been running very well on the 7/19 update other than the occasional spontaneous reboot.

Q: There was a 3d game free on amazon today 7/20 that downloads and installs, but when I tried to run it, it says "Device is not supported", and doesn't run. Any way to figure out why? Think the game is called Inverse Universe.

Sent from my HD+ Running CM 10.1 from emmc
[Nook HD, HD+ Android Development] Jd6J0r:
The latest version of BS Player has AC3 removed because of a licensing conflict with Dolby Labs.

"What's New

TEMPORARILY REMOVED SUPPORT FOR DOLBY TECHNOLOGIES (AC3, E-AC3, MLP) DUE TO LICENSING CLAIM BY DOLBY"

You may be able to revert to a previous version if you have a backup.

Not sure about MX Player, that one hasn't worked well on the HD+ for me.
[Nook HD, HD+ Android Development] deckoff:
Can I turn off quick settings drop down menu or configure double tap to open the settings page for appropriate setting - double taping on Wi-Fi button to open the Wi-Fi page, etc.

Now I use a plugin and the setting page is useless for me
[Nook HD, HD+ Android Development] Yianaki:
Reboots. Any older versions that are more stable?

I just did a clean install last week of cm-10.1-20130712 and I am getting random reboots every other day. It reboots after five ten minutes of use after leaving the tablet alone for a day or so. Wifi is set to turn itself off after 15 min inactivity.

If anyone could point me to a stable old evergreen ROM for this tablet until reboot is fixed, I would appreciate it. Reboots only happen every other day or third day so am very happy with this ROM. Will try the latest rom and see if that fixes things. Is the reboot issue something that will probably get fixed or is it just one of those things that would be very difficult to fix due to time or missing docs?

Thanks so much for this wonderful ROM. I had a lot of epubs and stock kept on showing syncing library drove me nuts. Also on stock Bluetooth never turns off once you use a BT device *(even if you actually turn off BT), would drain battery in a day. Am so happy with my purchase. Hope I don't go do something stupid like buy more of these just because they are such a great value. You can't find a nice 1080 9-10 tablet for cheaper.
[Nook HD, HD+ Android Development] verygreen:
Our memory is at 466MHz already, so I doubt it can run any faster.
[Nook HD, HD+ Android Development] pbassjunk:
Someone made a comment earlier about whether 16bit graphics in developer options\performance would help? Do it - makes a world of difference. While you're in there, check the 'purge bitmaps' option and turn on 18% compressed memory.

Other than the screen jitter, it's a whole new tablet, again.

On the jitter front.. 3-4 years ago I had an old crappy imported tablet from Pandawill. Had the same jitter though much more pronounced than on the nook. It ended up being a manufacturing problem where the touchscreen panel layers were sandwiched too tightly together. The Nook panel has far more sensors closer together than my old tablet did, which is probably why the effect is lessened.

Fixing it would require a hard hack, ts.conf didn't do much.
[Nook HD, HD+ Android Development] verygreen:
Returning back to this one, I cnanot even see where find_first_bit could be called from omap4_enter_idle, looks like straight for loop to me, so this one is a bit of a mistery.

Do you see this exact one often?
[Nook HD, HD+ Android Development] dbrickg:
Mine used to do something like this. I fixed it by turning off "Settings / Location access / GPS satellites". Google maps was continually trying to use GPS, which, of course, the Nook HD+ doesn't have, and it would finally "soft" crash the system. I say "soft" because it didn't completely reboot the system. It would just go from a sleeping state to the spinning CM10 logo for a couple seconds, and then back to my regular home screen. All my recent apps had been dropped. So, rather than a full reboot, it was more like I'd just logged out and back in.
[Nook HD, HD+ Android Development] ArcSmurf:
Wonder if this is also cause of my high battery use, looking at app usage and "google services" is this biggest user and said had wifi on for 19hours. This is with the 0719 update. Wikl turn off location services and see if makes a difference.
[Nook HD, HD+ Android Development] rushless:
Well, I thought 7/19 really was gold, but games are locking up. GTA Vice City and others lock the device up and have to reboot. Drats.
[Nook HD, HD+ Android Development] UnionBlvd:
Same here, but killing GPS access did not fix the problem for me. Installing the latest version of Google Maps seems to be the cure, no soft reboots since I upgraded a few days ago.
[Nook HD, HD+ Android Development] thewhiteknight:
Can someone point me to a different mirror or site to download this file? cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip

I've been trying for hours and it starts downloading stating it will take anywhere from 9-11 hours, after it downloads about 15 MB's it comes up with a network error, however any/all other files I try/tried downloading are just fine.

Thanks in advance for any help with the download link.
[Nook HD, HD+ Android Development] rushless:
I noticed no difference with games or emulators. Would have been nice if it did :) Bummer GTA Vice City does not work with the 7/19. It starts, but within a few seconds the game slows down until freezes and the device has to be hard button restarted. Tried it with the changes and without. Same lock up result. Vice City until now has worked good with CM 10.1 and the Nook.
[Nook HD, HD+ Android Development] spartan4585:
I am on 0719 and looking at the screen my fonts have gotten smaller.

Anyone else got this?
[Nook HD, HD+ Android Development] verygreen:
Hm.

I have no idea what might be the reason.

Can you run it with logcat in parallel to see what the last messages are?

then the same with dmesg in a loop to see what the last kernel messages are?
[Nook HD, HD+ Android Development] rushless:
I will try tomorrow. GTA 3 works, but has a little stutter. Vice City locks the device up hard.
[Nook HD, HD+ Android Development] renthispace:
Where is the 16bit option? I have developer options enabled but don't see the items you mentioned.
[Nook HD, HD+ Android Development] robertchow:
ebookdroid crash

verygreen

Could you try ebookdroid on nook hd+?

https://play.google.com/store/apps/details?id=org.ebookdroid

seeing how this app crash may be helpful for figuring out I/O bottleneck on nook hd+

ebookdroid 2.0 can open several pdf ebooks simultaneously.

In the app performance setting( under all setting) ,set pages in memory to 1 ,then open three or more pdf books, simply switching among these books from navigation panel will crash the app, I do nothing between switching.

to be able to switch among these books, pages in memory must be set to 0

or you can open only two books simultaneously.

my nook hd has not this problem
[Nook HD, HD+ Android Development] gidal:
I upgraded to 7/19 yesterday. Noitced that Candy Crush Saga runs at crawling speed now. Can't be the HW since my slower LG Optimus L9 has no issues with it.

Perhaps another app to use when debugging?

Is there any debugger used while running apps?

I could help by running it as long as any one would point me to the right direction.