yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] dbrickg:
Thanks. That's what I thought. So I went ahead and did it while I was waiting for your response. So far it seems just fine. I guess I don't notice any great deal of difference. But I'm not sure what the symptoms were that you were trying to cure. I can't figure out how to read any of the context around the link to the post you mention in the OP
[Nook HD, HD+ Android Development] verygreen:
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.

The goal here is to arrive at a different set of defaults that would improve the situation for people that feel there is a problem and at the same time don't make situation worse for everybody else who feels current settings are ok.
[Nook HD, HD+ Android Development] bckrupps:
mine personally was very insensitive. when i'm on slickdeals and i know you are also or bleacher report clicking on links such as hot deals and my subscriptions would take multiple tries. i didn't notice much system wide but mostly on the internet clicking smaller links. whatever he did with this zip made mine personally much much better.
[Nook HD, HD+ Android Development] dbrickg:
Aha... then I guess I *did* know about the problem. I noticed it most when reading books. After a few minutes, the page turning touches on the lower right margin would seem to stop. I finally just gave up even trying to use them, and substituted a swiping movement. Anyway, with this zip installed, the sensitivity doesn't seem to be any worse, and might well be better. It hasn't been very long, but I'll keep an eye open for differences.

PS: Just read some of the other people's posts, and see that they were complaining of difficulty in clicking links in web pages. I had certainly noticed that, but hadn't even thought of the possibility of fixing it, so had just ignored it. With this new zip, it does seem like web link sensitivity is much improved.
[Nook HD, HD+ Android Development] bckrupps:
mine is much improved. whatever adjustments were made I feel like mine could go even a little more in that direction. I'm at like 85% now lol
[Nook HD, HD+ Android Development] psygn:
Thanks, alal690! I think he deserves to get some "Thanks", too, but he doesn't have any posts! And thanks to verygreen for providing the tools for alal690 to tweak with, of course!
[Nook HD, HD+ Android Development] bckrupps:
I have noticed more mistypes on the keyboard verygreen if you are still needing input but the positives outweigh that in my book. it really is much better on websites. please thank the other dev that worked on this also alal690.
[Nook HD, HD+ Android Development] Azurael:
Big improvement for me, thanks :) I suspect the issue with pressing ui elements was caused by jitter and phantom touches that may have been caused by oversensitivity even though it seems somewhat counterintuitive... Selecting text was the big issue for me and it's now vastly improved. As has my accuracy on they keyboard - normally I'd have had to retype half of a post this length :P
[Nook HD, HD+ Android Development] verygreen:
BTW, it woul be great if people with some sort of a protective film over the touchscreen will give this a try to make sure it's also ok for them (I know those screen protectors are really popular amongst some people).
[Nook HD, HD+ Android Development] phammichael:
I've spent the last week trying to fix this, but it looks like it could be a problem with a driver or the actual hardware itself. If you go to Dev tools, then Pointer Location, you can see the reported values for touch pressure and size. When holding down my finger anywhere on the top 2/3 of my screen, the xy and size values jitter like crazy. If I touch the bottom 1/3 of my screen, there is no jittering and the size value is constant.

I think people that are complaining about low sensitivity are mistaken. I think the touch screen response is actually too sensitive, thus causing the jitter and making it hard to click on hyperlinks.

Reducing the touch sensitivity scale and increasing the touch size in the IDC file has helped a lot, but the jitter is still a problem that I hope someone can figure out how to fix.
[Nook HD, HD+ Android Development] pins2u:
I agree with phammichael that the real issue here would be jittering, but my symptom is different.

This is what I found so far.

- Pinch out to zoom in something (in gallery or web browser) and hold the 2 fingers on the screen.

- If my fingers are on the right side of the screen surface (portrait mode), the screen jitters. You can see the touch values changing fast and continuously by tiny values.

- If my fingers are on the left side of the screen surface, the screen won't jitter and stay calm.

Am I the only one experiencing this issue?

BTW, this is before I applied verygreen's touch screen patch. I will report back after applying it.
[Nook HD, HD+ Android Development] BigMacca:
The jittery right hand side of the screen in portrait mode is the problem - I have this on my HD+ (which was new) and my Dad has it on his (which was new) as does my friend (again a new unit)

There have also been lots of others reporting the same thing on here.

Put the HD+ into landscape mode and the issue disappears.

I've just applied verygreen's 'fix' zip and I have to say that touch response is loads better - clicking links etc works far more reliably :) (but right hand side of the screen in portrait mode jitters still exist)

Great work as usual verygreen
[Nook HD, HD+ Android Development] tebra:
With this patch screen sensitivity is improve on my HD+. Especially for text selection.

I don't have screen protection and use last Carbon rom.

Thanks verygreen
[Nook HD, HD+ Android Development] lancorp:
How do you uninstall this patch if it turns out that it causes other issues? I don't mind trying it, but I'd like a way out! :)
[Nook HD, HD+ Android Development] verygreen:
flash your original rom back.
[Nook HD, HD+ Android Development] lancorp:
If I flash back to the original ROM, do my apps and settings stay or is a complete wipe/flash necessary?
[Nook HD, HD+ Android Development] verygreen:
normal apps and settings will stay.

only stuff that is also installed into /system would be wiped (except gapps that will be retained).
[Nook HD, HD+ Android Development] bpaulien:
I'm not sure if it disappears in landscape mode. (at least not on mine) I noticed that on XBMC, which automatically pulls up in landscape mode, I sometimes have jitteriness while trying to select an episode. And if you're saying it's the righthand side in portrait, that would be the top portion in landscape, right? I think that it does seem harder to select an episode when it's toward the top of the list than the lower episodes...

Anyway, I haven't had a chance to flash this "fix" yet, so I'm not sure if it makes it easier in landscape mode or not, on XBMC. Hope to have a go at it tonight.
[Nook HD, HD+ Android Development] tebra:
my feedback with this patch: 1 reboot after a black and unresponsive screen

never had crash with carbon rom before...
[Nook HD, HD+ Android Development] leapinlar:
Verygreen, I think you meant this zip to be only for CM10.1 or it's derivatives, not stock, since stock does not support init.d. A user just tried and it messed up his stock. You might put a warning in the OP.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] keever25:
Is there any way to try a version of this on the HD?
[Nook HD, HD+ Android Development] verygreen:
Ok, done

Yes, I just need to make a version for it.

Or if you cannnot wait, flash it, then in adb rename /system/lib/hw/lights.ovation.so into /system/lib/hw/lights.hummingbird.so
[Nook HD, HD+ Android Development] rkeller62:
Touch response much better after applying this zip. Using the Nook branded matte screen protector.
[Nook HD, HD+ Android Development] dbrickg:
So, after a couple of days, it seems to me like the reader page turning touch is slightly better, but nothing to rave about. Unfortunately I don't know enough about it to give you any better diagnostics. Still, it's better than a real book, having to lick my fingers each time I turn a page :-\
[Nook HD, HD+ Android Development] phammichael:
The IDC file I changed was /system/usr/idc/ft5x06-i2c.idc

I added these lines:

touch.pressure.calibration = amplitude

touch.pressure.source = default

touch.pressure.scale = .00005

touch.size.calibration = geometric

touch.size.scale = 20

touch.size.bias = 0

Android documentation:

http://source.android.com/tech/input/touch-devices.html

I tested these settings before flashing verygreen's file, and I had positive results. After flashing verygreen's file, I did not notice any additional improvements. My results from the Pointer Location Dev tool are better, but there is still some jitter in the xy values on certain parts of my screen. I'm getting jitter on the same parts of the screen from my gf's Nook too.
[Nook HD, HD+ Android Development] keever25:
It wouldn't flash. CWM put out an error a point the device not being ovation and it said aborted. If you ever do have time to throw an HD zip together, I would love to try of out. Thanks.
[Nook HD, HD+ Android Development] verygreen:
Hm, I guess its' a real option to just change sensitivity of the framework too.

It's not entirely clear if you get better results from my chnges or your changes.

Also it seems the controller offers quite a few extra options that we'll need to play with.

Just need to find some time to write a user-friendly tool, hopefully this coming holiday will allow for that.
[Nook HD, HD+ Android Development] verygreen:
surprisingly, my experiments show that the NookHD controller does not accept sensitivity register changes, I'll dig into it later.
[Nook HD, HD+ Android Development] rkeller62:
Wouldn't the sensor recalibration procedure that was talked about in another thread work for the HD? I thought that was written for the HD, or was it for the original Nook color?
[Nook HD, HD+ Android Development] verygreen:
It was for the Nook Color, that has different touschscreen controller altogether. The app was a noop on Nook HDs, even though it was widely reported as great success (mostly due to reboot resetting some state, I imagine).
[Nook HD, HD+ Android Development] Ravynmagi:
I installed the CM 10.1 7/3 update with this fix included. And I don't think I've seen any difference. I'm still having issues with screen jitter.

Since you mentioned you see this mostly on the right side in portrait mode, that is usually where I notice it too since the problem seems to mostly occur for me reading Kindle or manga and I right tap to navigate to the next page. With this fix, I still get screen jitter on the right side. I started testing all the edges and it seems I only have the jitter on the lower area of the right side. What is weird though is if I remove the SD card and go back to Stock, I don't have the issue at all with any jittering on any sides.

I guess I'll just flip my Nook upside down when I'm reading Kindle and mangas. :)
[Nook HD, HD+ Android Development] phammichael:
I'm certain that the changes I made to the idc file has significantly improved usability on my Nook and my gf's Nook. I used the same settings for our tablets. But yes, you're right that we could tweak some more settings for further refinement.
[Nook HD, HD+ Android Development] Tom2112:
Just an FYI for people:

Don't flash the touchscreen-test.zip file AFTER updating to cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip.

I got stuck in a boot loop where it wouldn't go past the spinning CyanogenMod circle screen.

I tried flashing the cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip back over top of the touchscreen-test.zip, but that didn't help. Finally I tried wiping the Davlik cache and wiping the cache partition (but not wiping to a factory reset) and that allowed my Nook HD+ to continue though the boot. It ended up updating the files as if I had just installed the cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip, which I suppose is not surprising.
[Nook HD, HD+ Android Development] mcord11758:
The fix is already included in the rom

check out XBMC the future of TV

http://www.xbmchub.com/forums/register.php?referrerid=5757
[Nook HD, HD+ Android Development] dealpapa1:
can verygreen make one for hd? thanks
[Nook HD, HD+ Android Development] verygreen:
Nook HD does not allow parameters to be changed, only to see them. I guess the controller firware is a bit different.
[Nook HD, HD+ Android Development] verygreen:
Let me rephrase my question.

Do you feel that the idc file changes improved the situation more than the controller register change, less or about the same?
[Nook HD, HD+ Android Development] blautens:
Awesome! You made my day! My week! It was so insensitive I almost regretted buying this...until I flashed your zip. Just about perfect now...maybe a touch fidgety, but I could not complain nor care. Kudos to you, sir, another stellar effort. Thanks!
[Nook HD, HD+ Android Development] jpisini:
Is this already in the SDcard only 07/04 version?
[Nook HD, HD+ Android Development] verygreen:
Yes.
[Nook HD, HD+ Android Development] phammichael:
I've only tested your register changes on top of my idc changes, so I unfortunately cannot answer your question.

With that said, idc + register changes is the same as just idc changes by itself.

Sorry if my earlier post wasn't clear.
[Nook HD, HD+ Android Development] jpisini:
Personal preference I find the stock way much better after having played with this for a day. Yes this helps in the browser but if you use another browser like Dolphin this isn't needed. I compared CM10.1 SD card only installs with and without this patch and the ones without are much more responsive. I don't see the jitter others are talking about so maybe that is why I prefer stock. It is not just touch either apps seem to launch faster without this installed.

Thanks for all the work you have done for the HD+ so far very helpful.
[Nook HD, HD+ Android Development] verygreen:
I made a new gui tool now that you can use to play with sensitivity and other parameters: NookTouchscreenSensitivityAdjuster-2.apk.

see OP for more detailed instructions. Please report your findings.
[Nook HD, HD+ Android Development] jpisini:
I made one small adjustment to touch focus detection as you can see my tablet works much better now. Great job man.
[Nook HD, HD+ Android Development] verygreen:
What parts are better, I do not see any effect of this parameter in my testing, but perhaps I am not looking closely enough or maybe I am not looking in the right place? Your "surface water" value is also significantly higher than what I have here.

BTW, updated the app, now it displays numerical value for each setting to be more easily see what is set where.

Also the layout is now scrollable, so should work in landscape and on Nook HD (to the degree that the different controller firmware allows.

NookTouchscreenSensitivityAdjuster-3.apk

If more people give it a try and the increased focus setting is useful, I can make that one to be more permanently changeable so it persists across display sleeps/reboots.

Edit: Whoa, I just noticed "lib version" field in your controller is much newer than what I have, even newer than what's in my Nook HD.

So, I wonder if people that are dissatisfied by the recent sensitivity change have a different controller firmware version than the rest of us? Can we get some samples from such people?
[Nook HD, HD+ Android Development] jpisini:
That could be I have not noticed any real lag on my Nook even under stock. It is not perfect but nothing like I see from others. I don't know why my changes made a difference for me but there was real bad lag with your settings before I made the changes (was just goofing around cause I saw the defaults button) now CM is damn near perfect even with a stock browser. I bought my HD+ in Hingham MA on father's day so it is pretty new to me.
[Nook HD, HD+ Android Development] dbrickg:
Just to clarify, it looks like jpisini's lib version is 0x7D 0xD4, whereas mine is 0x21 0x85. Is that what you, verygreen, and other people are seeing?
[Nook HD, HD+ Android Development] verygreen:
I see "0x10 0x04" in the attached picture from jpsini, I don't think it's D there because letters are lowercase.

I have 0x7c 0x2e on my Nook HD+

0x0b 0xd3 in my Nook HD, also firmware version is 0x10 in HD (where as it's 0xb2 in HD+)
[Nook HD, HD+ Android Development] jazzaddict:
I received my nook hd+ like 2 weeks ago

FW Ver: 0xb2

FocalTech ID: 0x5c

Product ID: 0x06

Lib Version: 0xd1 0xdb
[Nook HD, HD+ Android Development] jpisini:
I wonder if slight differences in hardware also account for why some people can boot to SD reliably and others can't?
[Nook HD, HD+ Android Development] infra_red_dude:
I haven't played around with the settings at all and the "stock" touchscreen response is very good. My Nook HD+ has:

FW Ver: 0xb2

FocalTech ID: 0x5c

Product ID: 0x06

Lib Version: 0xd4 0x7a

I can relate the first 3 entries as "HW related" and the last as something software related. What does this lib represent? Is it is the driver for the touchscreen controller? If so then shouldn't everybody have the same lib version if they are using the same ROM?

My Nook HD+ runs verygreen's 07/06 CM10.1.
[Nook HD, HD+ Android Development] verygreen:
The library version is "Firmware Library Version" according to the very fragmented manual we have on the controller. It's reported by the firmware itself when queried.
[Nook HD, HD+ Android Development] infra_red_dude:
I see. Thanks for the info verygreen. Since we have APIs to query the version, do we also have APIs to dump the lib? If we can dump and flash those libs on other devices maybe that's the end to all touchscreen woes! :)
[Nook HD, HD+ Android Development] verygreen:
Nope.

The driver has a way of writing new firmware, but the documentation we have does not even document that way, and there's no way I see to dump the firmware either.

Interesting that nothing in the ROM I can see uses the firmware update capability, might be there is some sort of a factory app somewhere that does the writing on first imaging boot or something.
[Nook HD, HD+ Android Development] dbrickg:
Ahah. Yes. No doubt you're right. Thanks.
[Nook HD, HD+ Android Development] infra_red_dude:
What intrigues me is that except the lib version the HW IDs are same in these two cases. How does the Driver know which lib to load at boot? Surely there must be some ID that the Driver reads that directs it to load different firmware on different hardware.
[Nook HD, HD+ Android Development] verygreen:
Driver does not load any lib.

firmware lib is some internal firmware property, they all behave the same otherwise API-wise.
[Nook HD, HD+ Android Development] sorrowuk:
verygreen, are you able to take a look at changing the White Balance of the screen. There is an app that does it but it only seems to work on stock on android 4.0 however you can do it manually without the app as explained below.

I have had a few different Nook HD and Nook HD+ and all have different shades of white. Sometimes the white does not look great and looks yellow greeny coloured.

There was a way of changing it on stock nook using that app that was included.

WhiteBalanceSetting.apk on stock Nook HD - DOWNLOAD : http://d-h.st/xbr

That application is just a GUI which seems to edit 2 files in

/sys/devices/platform/omapdss/manager0

I am not sure what manager1 and manager2 does.

cpr_enable and cpr_coef

cpr_coef contains something like this : 255 0 0 0 214 0 0 0 252

Changing those numbers changes how the white color displays.

Found this :

You then need to write 1 into cpr_enable for the changes to take effect.

Doing this manually works perfectly on the Nook HD and Nook HD+ running CM10.1 but when you restart the tablet these files reset and go back to defaults.

Is an app needed to run at startup to set these values each time ? Maybe this is what that WhiteBalanceSetting.apk does ?

Any chance you can maybe take a look at that WhiteBalanceSetting.apk and create an app similarly to what you have done with this touchscreen sensitivity app, or maybe you could add this into that app?
[Nook HD, HD+ Android Development] leapinlar:
That app only comes with and works on the HD. I tried running it on the HD+ and it failed. The screen panels are different. But maybe we can gleen some info from it to understand how the HD calibration is done.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook HD, HD+ Android Development] sorrowuk:
The app doesn't work on Nook HD+ correct, but we know what the app does, it changes those 2 files explained above.

If you do the above manually on Nook HD+ you get the same result and you can change the white balance.

Its just the app that doesn't work. However the method works on both

You can try it if you want on your Nook HD+ if you modify those 2 files you will see the white balance changes. If you mess up and can't see anything just restart tablet and it will reset
[Nook HD, HD+ Android Development] verygreen:
sounds like you might want to contact the author so he can fix the app to work on HD+ as well? he's best equipped to resolve it fast.
[Nook HD, HD+ Android Development] sorrowuk:
The author is B&N , it is a preloaded app on the Nook HD on stock rom, so we can't go to the author.

Currently it doesn't work on Nook HD or Nook HD+ at all on CM10.1. It doesn't install. When you try to sideload the apk it just says Install Failed or Could not install or something.

I am not sure how to find out why it does this or why it fails.

I extracted the apk and looked at what it seemed to be doing and found out the above. Thats how it was changing the white balance by changing those files.

You can still change the white balance on cm10.1 by doing it manually editing the files directly (as I explained above, same as the app does), so the feature is there on cm10.1 just we don't have an app to help and we need a way to keep the changes persistant as they are lost currently on reboot ,

I guess it would have to work how your touchscreen sensitive app works to keep the changes persistant.

Unfortunatly I can't make android apps at all.
[Nook HD, HD+ Android Development] verygreen:
Ok, I see now. same signature issue as with stock Nook app. They had a special shared use to write to /bootdata and /rom without requesting root access and signature of the key does not match.

I imagine it's pretty trivial to decompile the java part of the app, add in necessary calls to su and recompile with updated signature, but I have never done it, so perhaps somebody else can do it?
[Nook HD, HD+ Android Development] sorrowuk:
Cool thanks for that,

If anyone has done this before and is able to take a look that would be great.
[Nook HD, HD+ Android Development] Tom2112:
For what it's worth, here's my defaults for the Touchscreen app. This is before making any changes.
[Nook HD, HD+ Android Development] verygreen:
New version of the updater app, now also allows you to save touchfocus value too if you run 7/11 or newer release (as it seems to be useful for some people, try larger values).

This will even work on Nook HD (though the UI is still not pretty there).

NookTouchscreenSensitivityAdjuster-4.apk
[Nook HD, HD+ Android Development] bckrupps:
Question verygreen. as far as the touch screen goes and with your particular device is there a point where it is as good as its gonna get per say. I have made several adjustments and it is much much better but on some websites and such I still need multiple touches. is yours the same? I guess I don't want to go nuts adjusting it much more if there is always going to be a certain amount of inaccuracy based on hardware limitations. like your ROM and the hard work to make it perfect. as far as the touchscreen it seems to be what it is lol.
[Nook HD, HD+ Android Development] ItsDon:
I am unable to download the apk, is the link down?
[Nook HD, HD+ Android Development] verygreen:
Backup link for now: http://d-h.st/wIm