+++ This bug was initially created as a clone of Bug #852400 +++ On the Leo device, i am unable to use the touch screen when installing a master build. this sounds very much like 852400, but for the 1.2 branch. https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-leo/latest/ mwu thinks this that the leo device is using a touchscreen driver that is breaking other deprecated features. if we want to fix this and use the leo phones for 1.2 testing, the right thing to do is to request Leo fix this issue. This is blocking us from testing any of our devices against master at this time. Repro: 1) install Leo 6/24/2013 master nightly on device 2) when phone starts up in FTU mode, notice the touch screen is busted and you cannot tap any buttons. Expected: - touchscreen works on leo master Actual: - touchscreen broken

What exactly is breaking here?

A while ago, bug 739417 added support for the old melfas ts driver (on gb sgs2) which was compatible with gingerbread touch input code but not ICS touch input code. This was during the period when we attempted to support both GB and ICS. Newer melfas ts drivers that work on ICS and newer do not have this problem, but the leo device is using the old driver (or maybe driver config) which just happened to work because we had this old GB only workaround. The GB workaround was removed in bug 852400 in order to support the tara device, but it breaks the old melfas ts driver used on Leo. See https://bugzilla.mozilla.org/show_bug.cgi?id=852400#c11 for more details on the exact nature of the incompatibility.

The result of the incompatibility is that touch up events are never registered.

Leo, is this something you can help with?

I need to clarify Michael Wu's comment. What you said "newer melfas ts drivers", does it work on ICS with protocol type A? And does 'old driver' mean that works on GB with type B?

(In reply to leo.bugzilla.fw from comment #5) > I need to clarify Michael Wu's comment. > > What you said "newer melfas ts drivers", does it work on ICS with protocol > type A? Yes. > And does 'old driver' mean that works on GB with type B? Yes. Though, I think GB may have also worked with type A. GB supported multiple ways of indicating the end of a touch (IIRC), but ICS standardized on type A.

(In reply to Michael Wu [:mwu] from comment #6) > (In reply to leo.bugzilla.fw from comment #5) > > I need to clarify Michael Wu's comment. > > > > What you said "newer melfas ts drivers", does it work on ICS with protocol > > type A? > > Yes. > > > And does 'old driver' mean that works on GB with type B? > > Yes. Though, I think GB may have also worked with type A. GB supported > multiple ways of indicating the end of a touch (IIRC), but ICS standardized > on type A. Leo, is this what you need?

i am checking V1.2 build. $> BRANCH=master ./config.sh leo $> ./build.sh $> ./flash.sh after flashing, LEO can't tap any menu or buttons. Anyway, it maybe caused by Bug 908797. currently, input device of master branch updated as JB MR2. So, i thinks the touchscreen driver of kernel also should be updated with JB's one. in my testing, after update kernel's touch driver, it's good. i will share boot.img which is included JB's touch driver to :tchung and :mwu in using email. please check this.

Leo, Did you get a chance to post the results? Tony, Please re-test per Leo's results.

Reproducible on m-c latest builds; rendering device useless at this point.

(In reply to leo.bugzilla.gecko from comment #8) > i am checking V1.2 build. > > $> BRANCH=master ./config.sh leo > $> ./build.sh > $> ./flash.sh > after flashing, LEO can't tap any menu or buttons. > > Anyway, it maybe caused by Bug 908797. currently, input device of master > branch updated as JB MR2. > So, i thinks the touchscreen driver of kernel also should be updated with > JB's one. > > in my testing, after update kernel's touch driver, it's good. > i will share boot.img which is included JB's touch driver to :tchung and > :mwu in using email. > please check this. Thanks! We've received the boot image and flashing it has fixed the touch driver on the 1.2 builds. This issue is not resolved.