http://www.youtube.com/watch?v=f3s5MnhNVBI

As you know, I work on the kernel side of things. I was able to get the touchscreen patch ported from the N810 touchscreen driver to the N800's one.

Sorry for the lowres, jerky video.

I've got a question though, is double taps hard to use on N810? I have to tap really hard for a double tap. single tap & dragging works like a dream though.

If there is a problem, I'd like to fix it before releasing the kernel image

qwerty,
any chance its because of the code running speed.
I've heard android runs like a dog and so isn't identifying double clicks in time?

good point, i don't know if there actually any double taps. after pressing power (yes, i'm ? too), single taps worked to launch apps.

Im just curious if you know that once this is installed that mplayer (and full screen in Canola because of mplayer) are not functioning properly? Just thought that I would throw that out there.

Absolutely excellent work, man. I'm using an n800 running Chinook, Debian beta 3, and now Android. You and penguinbait have done some amazing stuff.

Can't wait for the released touchscreen fix.

Just checked, and mplayer isn't working; it looks like it's not going into a correct video mode or something, like the second or two after it's taken out of full screen normally.

Sound works fine, though.

Curiosity speaking: How long till you release the n800 TS kernel image?

I am by no means trying to rush you! I'm very grateful for the work that you're doing, and I would prefer that you do a good job over a rushed one. But a little timeframe wouldn't hurt for those that are stuck using the dpad to move around

--Jon

I plan on releasing it soon, just got to add rotation and fix the N810 touchscreen again. I also need to fix the mplayer.


, I feel your pain, I had to use the d-pad. Infact, I didn't realise that the touchscreen patch on the site was for N810 so I was tapping and was upset when it worked on penguinbait's N810

But I got me a tissue and a text editor :P

Yes, I am aware of the problems . It basically happens because the framebuffer is set to be automatic in this kernel which basically means programs can write to there and have their screen drawn straight away (don't quote me on that) and android needs it because it uses framebuffer rather than x-server to show stuff on the screen.

mplayer uses framebuffer in some way and having it set to automatic throws it off, I plan on fixing that in the next kernel

(For now, you can use fanoush's fb_update_mode and set it to manual, only if you aren't using android, in that case use fb_update_mode to set it to manual)

Even after removing it MPlayer is mussed. Reflashing and rebuilding now. Great work though.

fb_update_mode works like a charm - with set to manual at boot and to auto in the init script i have a working mplayer, liqbase and android... Not simultaneously, but without kernel reflash. Mplayer is slow of course