I've tried searching around for solutions, but perhaps you guys know how I can enable my Nook Color to recognize more than 2 touches.
This would particularly be useful in my piano and drums apps I often use when I jam around. Currently using Phiremod v6.1.
Thanks.
I looked into it, the touchscreen is capable of 4 touches and the driver from cypress is also configured for 4 touches but when B&N implemented the driver they probably made some change to limit it to 2 or failed to adapt it correctly and only two touches worked. Either way u wont really be able to do anything unless u know how to write linux drivers
i also am a musician and i have yet to see anything anywhere about setting up the nook for more than 2 touches.. just learn howto use piano roll programming and use software that supports piano roll.
OK, thanks guys.
Related
http://www.youtube.com/watch?v=Qrzku6wF_DE
As you can see, Atrix have problem on touch.
(Sorry for video is not clear.)
It recognize rapid touch as drag and it make users to experience mistouch.
(Especially when you use keyboard with touch)
What I want to tell is, HP touchpad had same issue and solved problem.
You can find the source of it in here.
https://github.com/CyanogenMod/android_device_hp_tenderloin/commit/2a2aa87ce6a45d383c413c656eb103fc1e0bddf7
But since HP touchpad's driver is completely different, it can't be directly used to Atrix.
I think Atrix's touch driver is this one.
https://github.com/Atrix-Dev-Team/kernel-moto-atrix4g/blob/CM_kernel/drivers/input/touchscreen/qtouch_obp_ts.c
Is there anyone can use this info and make some change on it?
This issue gets most annoying when playing Shadowgun, it moves or rotates when I actually don't won't it to, just because I quickly tapped L-R or R-L
I'd donate to the one who fixes this.
Hey guys I always knew that multitouch on HD2 isn't pefect at all, but now I noticed a peculiar behavior which I was not aware (tnx to ICS)...
enabling a function in developer settings to show pointers position I discovered that multitouch is working in a wrong way.
When you put the second finger over the screen it is recognized correctly but when you move it close to the same axis of the first one (both vertical and horizontal axis), it automatically get aligned on the same abscissa or ordinate (depends which axis was closer) even if the fingers are not aligned.
This is frustrating when I use some apps that take advantage of multitouch, such as games or emulators, because while I'm pressing a key on the screen and I need to press another one on the opposite side, but not perfectly aligned, I get a wrong recognition and often I press another key or a blank space.
I hope I was clear, but to understand better the problem you should activate that function in developer settings and try yourself.
Please give me a hope to think it is a solvable problem... maybe with a better driver :fingers-crossed:
That's just the screen I'm afraid. I've had the same issue with every ROM I've tried, and there's nothing you can do to solve it. At the very least, it's nice for me to hear some confirmation that I'm not the only one who experiences this.
Nigeldg said:
That's just the screen I'm afraid. I've had the same issue with every ROM I've tried, and there's nothing you can do to solve it. At the very least, it's nice for me to hear some confirmation that I'm not the only one who experiences this.
Click to expand...
Click to collapse
I read around the forum that HD2 has hardware capabilities, so I think we need to get better input driver
The hardware doesn't support more than 2 points, and it does this rather poorly too. It's not so bad when using things like pinch to zoom or using two fingers to turn the map in Google Maps but when gaming it can be a bit of a pain. There's no driver that can increase the number of points the HW can support (if there was one then surely it would already have been implemented in Android) so afaik there's genuinely nothing that can be done about this. If there is, I'm sure someone will correct me soon.
It's a known issue and we can do nothing about it because of not so good touchscreen. Hardware problem, you know. It's present in every OS and in every ROM. For gaming I'd recommend getting a PS3 controller or using OTG cable and some other gamepads, like the X360 one.
Spaqin said:
It's a known issue and we can do nothing about it because of not so good touchscreen. Hardware problem, you know. It's present in every OS and in every ROM. For gaming I'd recommend getting a PS3 controller or using OTG cable and some other gamepads, like the X360 one.
Click to expand...
Click to collapse
Maybe you're right, an external controller is the best choice, but I don't want to bring with me other accessory when I'm outside... for the wrong recognition I think it's just driver fault because the problem is software side. When I use one finger is really precise the issue is when I try to use two fingers, because the driver is written wrong and read a fake position
Maybe this makes things a bit clearer. http://www.tactyl.com/fr/telecharger/39-drivers
Back in the days, there weren't that many "multitouch" apps out there for android.
If you look at the nexus one, it's even worse. http://www.youtube.com/watch?v=5puAvPqXpuc
From reading one of the booklets that came with the HD2 it all comes down to single-touch and a pinch-to-zoom gesture which both work most of the time.
Some people who developed emulators at that time, tried to avoid this "autoalignment" by putting the pads in opposite corners.
While still many people don't know that pressing on the edge of the screen, of the HD2, with at least one finger can cause
a swap in the y-axis once the second input is on the screen. (almost like in the nexus one video)
In very good light you can see this "edge-area", it's about ~4mm thick on each edge.
You can always download MVT and test it yourself. https://play.google.com/store/apps/details?id=com.batterypoweredgames.mtvistest&hl=en
Some time ago tatsumaki made a decent virtual gamepad for fpse which got rid of the alignment by incorporating it in the way he/she arranged the buttons and button mask.
No one is going to fix this by a new driver,
End of story.
After my digitizer broke, I purchased a new LCD and digitizer combination. I've got it installed and the new LCD and digitizer seems to be working well enough, it's just the the digitizer doesn't seem to be calibrated properly.
My first question is how would I go about calibrating the digitizer? Is that even possible? My wife also has a Nexus 4 and I've search around her settings and couldn't find anything related to calibrating the touchscreen. I see various things on the web about special numbers to input into the dialer (*#0*# , *#2664#) to test the touchscreen, but those don't seem to work on my wife's Nexus 4.
The second, and more important question I have is when I go to calibrate the screen, how do I get to the calibration software opened on my Nexus 4 since the basically unusable digitizer? I've tried the Android Screencast thing and while it will mirror my phone display, it will not allow me to supply any input. My phone is rooted and I've tried a couple of suggestions from the web, but none of them seem to allow the software to proxy my input from my computer to the phone. I've installed Webkey on the phone through the Play Store, but it seems as though I have to start the software to get it to work. Is there anything I can install that will automatically install and start itself so that I can interact with the phone via my computer?
This whole screen replacement ordeal has been interesting and educational, but I'm ready for it to be over now. Thanks in advance for your help.
I've got a simple touch that got stepped on, now Joseph Conrad has an interesting hairdo (can see where the crack is).
I've got ADB installed and working well for my other (various) Android devices, so using that is an option if I can figure out the Nook side.
The light next to the USB port goes on when I plug the Nook in, so there's some logic working in there.
Questions:
Can someone suggest a way to test if the device is good excepting the screen?
Is it worth replacing the screen on this device and if so, where could I find one?
Assuming screen replacement isn't an option, I'm considering random fun projects for this hardware. Anyone got recommendations?
The first random fun project I'm thinking of would be a WiFi repeater, mostly because I need one in the house here. Total awesomeness would be getting DD-WRT working on it
if u expert in adb ... then u can use and install program named "screenshot" and then run it and take print screen from ur nook and pull pic from ur sd card from screenshot directory .... all that via adb
but i dont know how ... it's just a theory ..... but it will make sure that ur device working or not and is it screen Issue or not
thx
That's a good idea, speedman.
You don't actually have to install any software.
The stock "screenshot" works well enough.
Ok, the colors are all screwed up, but still.
Code:
screenshot /sdcard/snap.png
Oh, yes you can buy screens from NST's gutted for parts.
It just that they cost about as much as a used NST.
If it were mine, I'd do some hacking.
I've already got a console UART connector soldered to the board.
I'd see about expanding the key matrix and seeing if I could get some I/O pins going.
JTAG would be fun to play with.
Hi All,
I have a dual monitor setup with one touch and one non-touch. The problem that I had was in-order to make my touch screen work I had to make it the default. I did not want that as my other monitor (non-touch) was larger. I have been searching all the various forums for a solution. I found it on the Surface Geek web site. The instructions follow:
-----------------------------------------------------------------------------------------------------------
So, I know that you guys are going to think I am crazy, but I recently bought a new machine that has a touchscreen. I had already bought a touchscreen for my old machine and decided I wanted to go dual monitors with each a touchscreen. I found an interesting problem. It appears that Window 8 sees the touchscreen input differently than the monitor. Sorta makes sense, how is it supposed to know which touchscreen goes to which monitor. I looked on the web to see if I could find a solution and nothing could be found except others complaining about this as well. Well, I am happy to say that I figured out how to associate the touchscreen of each monitor to the correct one.
You have to go into your control panel. Click on Hardware and Sound. Click on Tablet PC Settings. Click on Setup under Configure your pen and touch displays. Then you have to touch the screen that is showing the text. Click OK or Next and then click the next one when the words come on this one. This allows the computer to know which screen is which screen. Otherwise it appears that it just thinks that both are one. Hope this helps.
--------------------------------------------------------------------------------------------------------------
Regards.