Hi Manjunatha, It looks like idc file didn't load correctly, maybe you can check it first? Please also check the 'mDeviceMode' should be 'DEVICE_MODE_DIRECT' which is used for touch events.
If it still not working, please help to capture log for us to check. Regards, viral ----- Original Message ----- From: "Manjunatha M" <[email protected]> To: "Viral Wang" <[email protected]> Cc: "Marco Chen" <[email protected]>, [email protected] Sent: Monday, November 18, 2013 12:59:56 PM Subject: Re: [b2g] Touch not working Hi Viral, When I put the logs, I see the events getting printed in InputReader.cpp. But the events are not going to the setup screen during the initial bootup. But some times Whereever we click, input goes to only certain co-ordinates on the screen. Regards, Manjunatha On Fri, Nov 15, 2013 at 1:45 PM, Viral Wang <[email protected]> wrote: > Hi Manjunatha, > > If the patch still not working, we may need more information to identify > the problem since there are variant touch event formats from driver side. > > Firstly, I would like to make sure the idc file can be loaded successful. > (gecko/widget/gonk/libui/InputDevice.cpp) > You can check the log below from logcat to see if your idc is loaded. > > I/EventHub( 1271): New device: id=3, fd=56, path='/dev/input/eventX', > name='touch_name', classes=0x14, > configuration='/system/usr/idc/touch_name.idc', keyLayout='', > keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=true, > usingClockIoctl=false > > Secondly, you can check the events in > gecko/widget/gonk/libui/InputReader.cpp (one easy way is to enable > DEBUG_RAW_EVENTS) > Maybe you can capture some of touch events such as "getevent -p" and > "getevent -l" for us to dig out why touch not working on your device. > > Regards, > viral > > ----- Original Message ----- > From: "Manjunatha M" <[email protected]> > To: "Marco Chen" <[email protected]> > Cc: [email protected] > Sent: Friday, November 15, 2013 3:32:37 PM > Subject: Re: [b2g] Touch not working > > In InputReader.cpp > > The following code wasn't there in v1.2 > // Mozilla bug 739417 > if (!outPointer.touchMajor) > continue; > > > We tried applied this patch and tried the new build. There is no change > with the Touch behavior. > > Can someone get me pointers to fix this? > > > > On Fri, Nov 15, 2013 at 10:46 AM, Marco Chen <[email protected]> wrote: > > > Hi, > > > > Maybe you hit the compatibility issue on touch event between kernel > driver > > and Gecko. > > You can try to merge the removed codes from link as below. > > > > > https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=852400&attachment=737078 > > > > Sincerely yours. > > > > ----- 原始郵件 ----- > > 寄件者: "Manjunatha M" <[email protected]> > > 收件者: [email protected] > > 寄件備份: 2013 11 月 15 星期五 下午 12:51:04 > > 主旨: [b2g] Touch not working > > > > Hi, > > > > I have a device working with FFOS 1.1 and Android ICS 4.0.4. Now that I > > moved to FFOS 1.2 with the same Android ICS 4.0.4. The device is booting, > > but has touch issues. Most of the times touch doesn't work and few times, > > touch anywhere on the screen, the input goes to the single point on the > > screen (Example/- After the first time boot, touch anywhere on the > screen, > > the input goes to the next button) > > > > I need inputs to fix this issue. > > > > Thanks > > > > -- > > Regards, > > Manjunatha > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g > > > > > > -- > Regards, > Manjunatha > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > -- Regards, Manjunatha _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
