I'm happy to see DS gone from now on it created alot of confusion for some people

Sent from my LG-G2x using Tapatalk 2

Gone? I hope not! It was nice to have the additional 5-9 percent battery life...... :(

Sent from my LG-P999 using xda premium

Originally Posted by jwuerz

Gone? I hope not! It was nice to have the additional 5-9 percent battery life...... :(

Sent from my LG-P999 using xda premium

Yea after 50 b4. DS was deprecated

Sent from my LG-G2x using Tapatalk 2

So I decided to give this kernel another try after having everything run smooth & well on CM7 nightly ROM & included kernel. I flashed the 50b5-sv.zip version (both before & after cache & dalvik-cache wipes in CWM 5.0.2.8, the touchscreen seems to not register swipes, as if all touches are held too long. In keyboard, I couldn't type regular characters, only the alternate long-touch chars. Restored back to my Nandroid backup and everything's back to normal.

Originally Posted by Whyzor

So I decided to give this kernel another try after having everything run smooth & well on CM7 nightly ROM & included kernel. I flashed the 50b5-sv.zip version (both before & after cache & dalvik-cache wipes in CWM 5.0.2.8, the touchscreen seems to not register swipes, as if all touches are held too long. In keyboard, I couldn't type regular characters, only the alternate long-touch chars. Restored back to my Nandroid backup and everything's back to normal.

What nightly are you on? I'm using the same setup and its working great..

Sent from my LG-G2x using Tapatalk 2

New beta is out!

https://twitter.com/faux123/status/213856678842597376

Happy Friday!

Thanks faux testing this now on my gf phone

Sent from my HTC Sensation using Tapatalk 2

The swiping issue only occurs after using the browser. Still broken on the new beta 6 version.

Sent from my LG-P999 using XDA

Originally Posted by DJLamontagneIII

What nightly are you on? I'm using the same setup and its working great..

Sent from my LG-G2x using Tapatalk 2

I was on latest 0610 build yesterday, and now just installed 0616 build and made sure everything's running ok stock CM7.2, then flashed the 50b6-sv kernel and still the same problem with touches not registering swipes. It seems that it's registering my first touch action, then before waiting or looping back to service the interrupt again, registers as another at the same location. Looking at faux's github files, the touchscreen driver hasn't been updated since CM's default kernel build, I can only guess that other kernel optimizations are making it seem like the timing is "too fast", instead of "real-time".

I've read the rootzwiki thread (just haven't bothered to register an account there) so I'll just post here. I appreciate faux's work, even though I've been late to the G2x, but there may be some problems that others have overlooked in previous testing, and the bug may be too hard to fix now with so many changes that were commited in recent months.

Another area worth looking into is making sure the hardware voltage & timing specs are standard, as there may be some hardware variations and any remaining undervolted or overclocked components can mess things up for some phones like mine.

Also posting a md5sum check string with the binary is a good idea to rule out download problems. I've flashed lots of roms & kernels so that's unlikely the issue here.

---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------

Originally Posted by TarHeelTrigger

The swiping issue only occurs after using the browser. Still broken on the new beta 6 version.

Sent from my LG-P999 using XDA

My swiping problem happens right after a fresh bootup, no browser loaded, or maybe another app that uses the same trigger code loads on my phone as your browser.

Originally Posted by Whyzor

I was on latest 0610 build yesterday, and now just installed 0616 build and made sure everything's running ok stock CM7.2, then flashed the 50b6-sv kernel and still the same problem with touches not registering swipes. It seems that it's registering my first touch action, then before waiting or looping back to service the interrupt again, registers as another at the same location. Looking at faux's github files, the touchscreen driver hasn't been updated since CM's default kernel build, I can only guess that other kernel optimizations are making it seem like the timing is "too fast", instead of "real-time".

I've read the rootzwiki thread (just haven't bothered to register an account there) so I'll just post here. I appreciate faux's work, even though I've been late to the G2x, but there may be some problems that others have overlooked in previous testing, and the bug may be too hard to fix now with so many changes that were commited in recent months.

Another area worth looking into is making sure the hardware voltage & timing specs are standard, as there may be some hardware variations and any remaining undervolted or overclocked components can mess things up for some phones like mine.

Also posting a md5sum check string with the binary is a good idea to rule out download problems. I've flashed lots of roms & kernels so that's unlikely the issue here.

---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------



My swiping problem happens right after a fresh bootup, no browser loaded, or maybe another app that uses the same trigger code loads on my phone as your browser.

This is first time I heard of this bug. I don't have any issues regarding touch screens... I've used the browser and played temple run and I haven't encountered any touch related issues (esp with swiping motions since temple run is completely dependent on it)/