yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] systoxity:
alright, ill give that a shot later. I'll post back here the result. Thanks for trying to help me out.
[Nook HD, HD+ Android Development] verygreen:
Ok, so regarding touchscreen, I uncovered this manual, that does not seem to be 100% matching wrt defaults, but otherwise seems to be pretty much spot on: http://newhavendisplay.com/app_notes/FT5x06.pdf

Now people that have issues can experiment with values and report their findings and we might devise new defaults from it.

Registers are accessible from userspace too. The first table is controlled by:

/sys/bus/i2c/drivers/ft5x06/3-0038/wmreg and /sys/bus/i2c/drivers/ft5x06/3-0038/wmval

so in adb shell do echo 0xXX >/sys/bus/i2c/drivers/ft5x06/3-0038/wmreg (replace XX with register number) to set register you are interested in

then you can do cat /sys/bus/i2c/drivers/ft5x06/3-0038/wmval to inspect the value, or echo 0xXX >/sys/bus/i2c/drivers/ft5x06/3-0038/wmval to set the new value.

cat /sys/bus/i2c/drivers/ft5x06/3-0038/tpreset seems to mostly reset controller, but not to 100% default state.

If you screwed up, just press the power button twice (so suspend/resume) and the thing will reset into the default state.

When experimenting with all of this, make sure your screen is actually on too.

There's some sort of autocalibration that you can perform by doing cat /sys/bus/i2c/drivers/ft5x06/3-0038/storecalibrateflash but I do not see any change after it.

Anyway, what I found so far:

the 0x80 register controls touch sensitivity in a way, the smaller the value, the higher the sensitivity. default 0x11, at 0x50 I can no longer register any input, at 0x40 input is very sporadic. So people that complain about oversensitivity might want to give this one a try.

There are registers for temperature compensation, water on the surface compensation and such that I cannot seem to see make any difference, but it might for others?

register 0xA0 for autocalibration, if you enable that - touchscreen goes crazy with tons of phantom events, dong cat on tpreset stops it, but the ts is still somewhat in weird state as you will be able to see if you decide to try it.

Anyway, the documentation is very lightweight so there's a lot of experimenting to be done by interested parties, please share your results!
[Nook HD, HD+ Android Development] verygreen:
New binary drop: cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip

Not many changes this time:

- Added elecom bt devices support

- Added a bunch of usb 3g modem and gps kernel drivers into default config

This is my first build with the new repo layout, hopefully nothing is missing, but if something is, please let me know.
[Nook HD, HD+ Android Development] Apk07:
I wish I was a little more savvy so I could mess around with with my touchscreen...

Here's to wishing for some sort of apk/noob-friendly slider/presets to adjust it. The "water on the screen" sounds interesting if it actually does anything. I imagine "water" would be their broad term for any liquid (such as the oil in your fingers). Come to think of it, is skin-oil conductive?
[Nook HD, HD+ Android Development] golizza:
I got t boot loop when turn on wifi (06-24 version). Any ideas?
[Nook HD, HD+ Android Development] Zippy Dufus:
New repo layout?

I spotted your new repo layout and tied to build but ran into this problem: http://xdaforums.com/showthread.php?p=42861797#post42861797 I found some other developer having the same issue with a different device. How did you workaround or avoid it?

==//==

BTW, with your old repo layout, I would get a working build but could never get the wifi working. I'm hopeful that I will be more successful now that you have included the binary firmware.
[Nook HD, HD+ Android Development] verygreen:
Well, since it's something unlikely caused by my new repo layout, I just patched it out for now:

diff --git a/media/libstagefright/ACodec.cpp b/media/libstagefright/ACodec.cpp
index a9e344d..e761630 100644
--- a/media/libstagefright/ACodec.cpp
+++ b/media/libstagefright/ACodec.cpp
@@ -1587,7 +1587,7 @@ status_t ACodec::setSupportedOutputFormat() {
|| format.eColorFormat == OMX_TI_COLOR_FormatYUV420PackedSemiPlanar
|| format.eColorFormat == OMX_QCOM_COLOR_FormatYVU420SemiPlanar
|| format.eColorFormat == OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar32m );
+/* || format.eColorFormat == OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar32m*/ );

return mOMX->setParameter(
mNode, OMX_IndexParamVideoPortFormat,
diff --git a/media/libstagefright/OMXCodec.cpp b/media/libstagefright/OMXCodec.cpp
index c7b4617..bb5a368 100644
--- a/media/libstagefright/OMXCodec.cpp
+++ b/media/libstagefright/OMXCodec.cpp
@@ -1548,7 +1548,7 @@ status_t OMXCodec::setVideoOutputFormat(
|| format.eColorFormat == OMX_TI_COLOR_FormatYUV420PackedSemiPlanar
|| format.eColorFormat == OMX_QCOM_COLOR_FormatYVU420SemiPlanar
|| format.eColorFormat == OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar64x32Tile2m8ka
- || format.eColorFormat == OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar32m
+/* || format.eColorFormat == OMX_QCOM_COLOR_FormatYUV420PackedSemiPlanar32m*/
#ifdef USE_SAMSUNG_COLORFORMAT
|| format.eColorFormat == OMX_SEC_COLOR_FormatNV12TPhysicalAddress
|| format.eColorFormat == OMX_SEC_COLOR_FormatNV12Tiled
[Nook HD, HD+ Android Development] excarnate:
Relock on unlock

Both my wife's and my HD+ often have a problem where, using the default unlock, it will relock immediately. It is intermittent but seems to be after it has gone asleep due to a timeout. It doesn't happen as often as not, but once it happens sometimes the only way to get out of it is to reboot. I had this happen from a completely fresh install (using the slide to the right in a circle) of 6/15 and changing the unlock choices didn't help. I haven't tried alternate lock screens yet. On installing the 6/24 it happened on the first boot (I wasn't watching it, so the screen did time out).

It is hard to force it to duplicate, so I don't have a logcat, but I'm trying. I've searched and kept up with the thread, but I wonder if perhaps this is a known issue?
[Nook HD, HD+ Android Development] mikelav456:
Are you guys using the B&N Nook case (with the magnet to shut off the screen when closed)? If so, I had the same problem. What worked for me is to close the cover again and reopen and that should fix it.
[Nook HD, HD+ Android Development] MadMikeSS:
I got boot looping after reinstalling the tablet ui after installing 6/24. Before tablet ui it booted fine. I just re installed without tablet ui and it booted fine again.
[Nook HD, HD+ Android Development] verygreen:
This is best discussed in the TabletUI thread, I don't really test with it and don't know what's inside of those patches.
[Nook HD, HD+ Android Development] excarnate:
No, we have the MoKo Slim case. It does have a magnet. We'll try to see if it is that simple.

That brings up the next few questions:

Is the problem hardware (magnet too strong? sensor too sensitive? other?)? Or is the problem software (Does the stock Nook HD+ have this problem? Is this something that can be calibrated? Would a logcat even help?)? My Nexus 7 with a similar (Poetic) case works reliably with the magnetic detection, so it seems it isn't an intrinsic problem of 4.2.2.

It seems like the magnet is in the top left corner (portrait). With the case open and the cover folded back, pressing the magnet to the back does not trigger a sleep, so it would seem the magnet is the right power in this case :)
[Nook HD, HD+ Android Development] Azurael:
I didn't know the Nook was supposed to sleep/wake with a magnetic case... I just checked, the case that came with my secondhand Nook wakes and sleeps my Nexus 7 (I assume it's a genuine one, it's a nicely made leather/neoprene thing with a nook badge on the inside left bottom corner, just a shame it's a vile shade or turquoise.)

I wonder why it doesn't affect my Nook... Nothing in any system logs when I wave the case in front of it, I'm assuming the hall effect sensor must be dead or disconnected... Where is it?

Edit: Actually the sensor works fine, it's in the top left as stated by somebody before, my case just doesn't have a magnet there, it was just the magnet for the magnetic latch which worked on my Nexus 7. This is the case... My whole post seems like a bit of a waste of space. Sorry.
[Nook HD, HD+ Android Development] ipilcher:
Live wallpaper reset on boot

Running the 6/23 build (dirty flashed from 6/15 with cache wipe).

If I select a live wallpaper, my wallpaper is reset to the default leaf background when I reboot. This does not happen if I select a non-live wallpaper.

(I've seen this with both Trebuchet and Apex.)

Anyone else seeing this?
[Nook HD, HD+ Android Development] Jack45:
This was brought up before in the forum. Search for the word "leaf." Possibly the most worthwhile reply (not mine): "Do you have an app that clears (systemapp) cache? That resets the wallpaper for me."
[Nook HD, HD+ Android Development] ipilcher:
D'oh! I read that a couple of days ago; not sure why I didn't make the connection.

I did just do a system wipe and verified that the problem doesn't occur with a "clean" load... And after restoring my backup, wiping caches, and fixing permissions it booted back up to my live wallpaper. Interesting.
[Nook HD, HD+ Android Development] Zippy Dufus:
I commented-out the lines as you instructed above and the build completes but boot-loops before it even gets to the boot animation. (Before the repo reorg, I would get a bootable build but the wifi would not work. I see that you include the firmware now so I assume that I don't have to drop in the B&N code and compile it anymore?).

Question: I produce a file called cm-10.1-20130624-UNOFFICIAL-ovation.zip while your zip file is called cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip. Am I building the right ROM?

I've tried brunch ovation and brunch cm_ovation-userdebug and I am using your local_manifest.xml.

My apologies for being a pest.
[Nook HD, HD+ Android Development] verygreen:
Do you see cyanoboot picture? If no, did you forget to reapply the build/ patch? If yes, what's in the logcat?

I manually add them to avoid confusion between the emmc and sdcard versions, so it's normal.
[Nook HD, HD+ Android Development] mikelav456:
Did the fix I mentioned work for you and your wife?
[Nook HD, HD+ Android Development] data2318:
Wifi Always on not working.

verygreen, the Wifi Always on in wifi option is not working, it will always turn off after an hour or so if screen is off. Apps like GrooVe IP to call the tablet won't receive the call after an hour of screen off. The other tablets devices I have with CM roms don't have this problem. Does that have anything to do with the governor or is it the problem of the kernel? Have tried all the roms you uploaded and same issue. Clean wiped install.
[Nook HD, HD+ Android Development] verygreen:
well, I cannot replicate that. I have one nook sitting by my side all the time and it dutifully informs me of all incoming gtalk messages whenever they come.
[Nook HD, HD+ Android Development] data2318:
I noticed that email and Gtalk message works fine too. Maybe that is the problem of the app itself then.
[Nook HD, HD+ Android Development] SCWells72:
I noticed some comments on the carbon rom thread about smoother performance, apparently due to the compiler configuration, but perhaps some other things as well. Any chance those could make it into this rom easily? I've always been a fan of cyanogenmod roms and would prefer to stick with it.
[Nook HD, HD+ Android Development] data2318:
Reboot to Recovery

verygreen, may I request "reboot to recovery" to be included in the power menu options so then I don't need to install Rom manger or use an SD card to boot into recovery.
[Nook HD, HD+ Android Development] SCWells72:
It's there. Enable it through system settings.
[Nook HD, HD+ Android Development] wy1d:
I see Reboot Menu but it only adds Reboot as an option in the power menu. When I choose reboot, I do not get a menu of options that allow different types of reboot (like reboot recovery) only a pop-up stating that the tablet will reboot now.
[Nook HD, HD+ Android Development] mcord11758:
From emote guide

c) Within CM10.1: select Settings > 'About tablet' > 'Build number' (repeatedly tap on it until 'Developer options' appears in the left column). Once Developer options is enabled, select it, enable 'Advanced reboot' to allow reboot to recovery. Then, to access the reboot-to-recovery option, long-press the Power button for the Power menu to appear, select 'reboot', then select 'recovery' at the second menu.

check out XBMC the future of TV

http://www.xbmchub.com/forums/register.php?referrerid=5757
[Nook HD, HD+ Android Development] verygreen:
I doubt compiler would make any noticeable difference.

If you can point at any other specific changes I can adopt, I might give it a try.
[Nook HD, HD+ Android Development] bckrupps:
Glad you cleared that up Verygreen. i think many people myself included assumed the reboot to recovery would show up on the main menu. i feel dumb now lol as i always shut down then reboot with the power button. just an ocd thing i guess to guarantee a full clean boot lol. i never knew about the second menu and always assumed mine was just wacky
[Nook HD, HD+ Android Development] robertchow:
Can app opening and closing animation be made more smooth?

My only dissatisfaction about 06/24 rom is that app opening and closing animation is not so smooth. the screen flickers more or less during transtion. I have tried several launcher . none is satisfactory . My nook hd with hybrid cm10.1 installation is much more snappy.

Are there anyway we can make app opening and closing animation more smooth.
[Nook HD, HD+ Android Development] rushless:
That is nice to know. I would not have stumbled on that.
[Nook HD, HD+ Android Development] thegracious:
Did anyone notice that the battery use for this update is really bad? the app named "media" take account of 97% of the battery. It stay awake all the time. I didn't use my nook for this day but it go down from 80% to 19%.

is there any way to solve it (except uninstall cuz it is the pre-installed app).
[Nook HD, HD+ Android Development] verygreen:
Certainly not on my end.

I loaded it on 24th shortly before uploading and it lost 11% of battery in the last 2 days and 12 hours.
[Nook HD, HD+ Android Development] panchokoster:
hey [MENTION=3654172]verygreen[/MENTION], nook color is officially supported by cyanogenmod. What would be the steps to follow for you to become the official maintainer of HD/HD+.

it would be great if you could make use of gerrit and CM build servers, if so, we could get your updates officialy by CM-updater :highfive:
[Nook HD, HD+ Android Development] verygreen:
I applied via the official channels already, waiting a word back now.
[Nook HD, HD+ Android Development] cruthck7:
I'm having an issue with youtube . I've tried both the app and accessing through chrome and neither will load any videos. It just says cannot load video at this time. I'm currently on the 6/24 build but it didn't work in previous builds either. Anyone else having this issue?
[Nook HD, HD+ Android Development] excarnate:
The problem of relocking on unlock has happened twice to me since then; both times closing the cover (and making sure it turns off the screen) and reopening it has worked. My wife hasn't had enough free time to use the tablet since then.

It makes me think that the problem may be software. I don't code or I'd look into it. Probably something just a bit different in the B&N implementation.</guess>
[Nook HD, HD+ Android Development] KDHaro:
You can reduce the animation scale values from the Developer options tab of the settings.
[Nook HD, HD+ Android Development] Wolfkmann:
Hi,

I'm trying to create a flashable zip because I want to customize the battery icons on my status bar. I've done this often on my phone. The problem is that on my phone the status bar battery icons can be found in the systemui.apk file, but that is not the case or the nook HD+. Does anyone know where the circle battery icons are?

Thanks,

-Wolf
[Nook HD, HD+ Android Development] Escaperoute:
Just an Advise

Hi,

After installing your latest BUILD, the RAM is so low only 300 mb left. Can you optimize some of the programs to reduce the RAM load. I remove the stock launcher with Smart Launcher it seem to reduce the ram load to 345 mb but i think some system level optimization can be done.

I just love your work.

Thanks for all your hardwork
[Nook HD, HD+ Android Development] data2318:
just turn the whole animation off for good, but still it feels laggy in comparison to other tablets with a little lower resolution. Too many pixels to be driven by the graphics chip.
[Nook HD, HD+ Android Development] verygreen:
Well, here's a small experimental build to see if boosting default clock helps any lag issues.

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

Changes:

- Default io sheduler: deadline (cfq kind of does not make sense for nvram type devices in my view).

- When screen is on, cpu idles at 800Mhz instead of 400MHz, on input it boosts to 1.1Ghz for a short 80ms. (screen off is still at 400MHz)

- added nls_utf8 into default kernel config: for people outside of US that need it (both for vfat and cifs).

- Updated sgx blobs to the latest - I do not see any changes from it (i.e. beach buggy still crashes), but who knows what might be affected.

So points of testing: see if battery drainage with screen on becomes much worse than it was before

battery drainage with screen off should not really change.

graphics should not become any worse.

no io performance degradation (not that I think there should be any, but still).
[Nook HD, HD+ Android Development] jptesar:
Thanks for taking the time to try and improve the rom. Your hard work and time is appreciated.
[Nook HD, HD+ Android Development] robertchow:
just try build 6/26,not noticeable change in animation speed. app opening and closing transition smoothness is just as 6/24.

maybe I can live with animation turned off.
[Nook HD, HD+ Android Development] rushless:
Seems a fair assumption. The TF700 has the same issues to some degree and also pushing too many pixels for the gpu to handle. They upped the frequency, but still a bottleneck for the two year old Tegra 3 gpu.

I am glad the Developers options were pointed out, since I missed that in the emote thread. :o

Ironic Developer options are hidden like this when in stock roms for the G3, Excite, TF300, etc they are not. Unless there are more "dangerous" things in this version...
[Nook HD, HD+ Android Development] Raul027:
Is there anyway to over clock the GPU? Its odd that heavy graphics games work flawlessly but the ui animation lags. Maybe the GPU is too conservative in its clock speeds.
[Nook HD, HD+ Android Development] ndttung8487:
my nook just get better and better every time verygreen upgrade his build!! Thanks alot!!
[Nook HD, HD+ Android Development] king200:
I notice a difference in screen sensitivity with the 06/26 build. I use "Screen Off" and double tap the home screen to activate sleep/lock. With this build, the taps can be faster and with less finger pressure. The shortcuts for "Beautiful Widgets" work faster too. That means tapping the time to open contacts or calendar. I use Nova Launcher. I look at this change as positive.

The screen roatation appears faster too.
[Nook HD, HD+ Android Development] rushless:
Though CM 10.1 is a much better overall experience than stock and the stutter in games is gone, the lag still remains. Not understanding this and the gpu should not be causing apps to take five to ten seconds (or more) sometimes to respond or navigate within. It got so bad last night I turned it off. This was after already restarting for the same thing. As others have mentioned, the Play market as example gets very laggy to the point screens appear to blend together during transition from one to the other. I turned all animations off and this has not helped. It is the worst when updating apps and seems to stick around after updating or installing.

Since you can not get any more plain than CM 10.1 (OEM bloat free), there must be some IO issue or other hardware bottleneck. Something causes the lag and it was in stock 2.0 and 2.1 as well. At least CM 10.1 gets rid of the stutter in apps and games so they are smooth.

Added: I am not on the 1/26 version and on the one from about two weeks ago. Seems though that if idle is set to 800mhz while display is on, that would drain more battery. The display eats the most battery, but from a weighted standpoint, I would expect 15% more battery drain at 800mhz. Depending on screen time and type of use, this could go up or down. An example would be web browsing, reading and video, since the battery drain would be greater at 800mzh for low cpu resource tasks, but most games it would make little difference (unless playing solitaire like games).

Could it be possible to release two versions? One with the increased idle and one without? Seems a battery waste for web browsing (non Flash), reading and also video that leverages the hardware (gpu).
[Nook HD, HD+ Android Development] Wolfkmann:
Couldn't you just use something like trickster mod to adjust this yourself?
[Nook HD, HD+ Android Development] jasonv1:
TweetCaster + lock screen bug

Just a heads up for something I found when running TweetCaster on my Nook HD+/CM10.1 (latest version). This problem does not occur until you have loaded TweetCaster, and happens whether or not you have notifications enabled.

When you attempt to unlock the device, either with a password or without the unlock action proceeds, the screen blinks, and you are returned to the unlock screen. You cannot unlock the device at all, and are forced to reboot (which does work). I was able to reproduce this issue after a device wipe and with no other "non stock" apps running.

I switched Twitter clients and have had no issues since. I don't experience this behavior on my Nexus 7, so it appears specific to the Nook+CM10.1 combo. Not a big deal, but I tried a lot of things before figuring out what the cause was.
[Nook HD, HD+ Android Development] psygn:
Coming from Nexus 7 and HP Touchpad (your work is remembered and appreciated there, verygreen!), the Nook HD+ does indeed feel laggy with animation. Then again, they are outputting much less pixels to the screen.

verygreen, I'm sure you notice this lag transitioning between apps. Is this due to hardware limitation?
[Nook HD, HD+ Android Development] rushless:
Is this a governor mod that works with the Nook HD+? I like the standard settings since good battery life when reading and browsing, and video. Increasing the clock 100% seems no need for me. The issues with the lag seems like something else going on. It seems random, but Play market is a good example of what can trigger it and not be too random.

Since the device can be smooth and fast and then not while using the same applications, a clock increase seems moot. IMO, it has to be either an IO issue, or some weird cache process going amuck at bios/kernel level. I have used two other tablets with the 4470 and this issue appears unique to the Nook HD+. Even the Archos tablet was smooth and did not have the lag like the Nook, but the display and build is weak.

The lag is prevalent on stock and CM on the Nook HD+. Odd, this be.
[Nook HD, HD+ Android Development] foolforfood:
So there are two things I've noticed, they might be related but I'll leave that for somebody with more experience than I to discern.

1. I use the Kobo app for reading and the swiping from page to page is very stuttery, even though in other epub readers this doesn't happen (nook, mantano, etc.) Not sure why but just throwing it out there

2. In kernel tuner, I was studying the CPU settings and while cpu0 remained, cpu1 disappears and cannot be seen or adjusted at all. I'm thinking that this might be the cause perhaps for the occasional lag the second core going completely offline sporadically. I'm going to try some other oc apps to see if they give me the same results. Can anybody confirm on their devices?

Edit: this is multi core right?