Guest BigBearMDC Posted April 3, 2010 Report Share Posted April 3, 2010 Hi guys I got some very bad news: I tried to get MT working, so its usable at least for Dolphin Browser etc. When I realized that one touchpoint stays at the edge of the screen, I decided to print the coordinates to the console using printk: printk("\nx %4d, y %4d, z %3d, w %2d, F %d, \n2nd: x %4d, y %4d, z %3d, w %2d, F %d", x, y, z, w, finger, x2, y2, z2, w2, finger2);[/code] And that's the output when I have 2 fingers on the screen: [code]x 3442, y 1609, z 104, w 1, F 1, 2nd: x 256, y 0, z 0, w 0, F 0 x2 stays at 256, no matter what I do. Looks like were just looking at a empty/unallocated piece of memory... sorry... badword Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 3, 2010 Report Share Posted April 3, 2010 Tried the 1167 driver too, which will not report any touch input as it receives an "bad read" error: synaptics_ts_work_func: 11 59 8 9e 8 6f 0 0 40 0 0 0 0 0 0, ret 2 synaptics_ts_work_func: bad read 11 59 8 9e 8 6f 0 0 40 0 0 0 0 0 0, ret 2[/code] Let's hope I messed a #DEFINE that tells the synaptics controller to report the second touchpoint too! Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest Azurren Posted April 3, 2010 Report Share Posted April 3, 2010 you've been going at this for ages now. Perhaps you should give it a break and come back with a fresh perspective later. :P I'm sure you will get it working eventually! Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 5, 2010 Report Share Posted April 5, 2010 Hi guys Update: I will compile the kernel once again tomorow, but now with CONFIG_TOUCHSCREEN_GESTRUE=y in the kernel config. BTW this looks promising, because I think the Pulse uses the ClearPad 2000 - which is mentioned as dualtouch display with Gesture support. This has been tried earlier, without success, but its woth a try anyway. I don't really know what I could try else. I also made up a thread @huawei support forum, but it seems like they have a bug or something likw that on their site because i can't view the thread anymore ?? Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest jmmL Posted April 5, 2010 Report Share Posted April 5, 2010 Hi guys Update: I will compile the kernel once again tomorow, but now with CONFIG_TOUCHSCREEN_GESTRUE=y in the kernel config. BTW this looks promising, because I think the Pulse uses the ClearPad 2000 - which is mentioned as dualtouch display with Gesture support. This has been tried earlier, without success, but its woth a try anyway. I don't really know what I could try else. I also made up a thread @huawei support forum, but it seems like they have a bug or something likw that on their site because i can't view the thread anymore ?? Greetings, BigBear I can't view your thread either. What's weird is that I can view every other thread I tried looking at.. Link to comment Share on other sites More sharing options...
Guest John Hamelink Posted April 5, 2010 Report Share Posted April 5, 2010 I can't view your thread either. What's weird is that I can view every other thread I tried looking at.. They like to delete threads they don't want to answer over at huawei forums. Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 5, 2010 Report Share Posted April 5, 2010 (edited) They like to delete threads they don't want to answer over at huawei forums. Thats not very customer friendly .... :P But the weird thing is that I think they didn't delete it because I couldn't view the thread at all ... Not even directly after I started it. Update: Hey, I can view my thread at Huawei forum now :( Greetings, BigBear Edited April 5, 2010 by BigBearMDC Link to comment Share on other sites More sharing options...
Guest John Hamelink Posted April 5, 2010 Report Share Posted April 5, 2010 Thats not very customer friendly .... :P But the weird thing is that I think they didn't delete it because I couldn't view the thread at all ... Not even directly after I started it. Greetings, BigBear Well, also notice that every user in the forum is marked as staff... Their forum must have some serious problems :S Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 5, 2010 Report Share Posted April 5, 2010 Well, also notice that every user in the forum is marked as staff... Their forum must have some serious problems :S So, I, as an official Huawei employee, promis you that Android 2.1 is coming to the Pulse :P Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 6, 2010 Report Share Posted April 6, 2010 Okay, adding CONFIG_TOCHSCREEN_GESTURE=y does not change anything :P I'm now waiting for the reply of an Huawei dev at the Huawei support forum... Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 6, 2010 Report Share Posted April 6, 2010 Hey, I have an idea: There have been troubles with non-Pulse U8220 models, on which the touchscreen didn't work after they applied our boot.img (with our kernel). I'm pretty sure that both devices have the same HW. What is, if those devices use the synaptics_rmi_tm driver instead of the [...]_tm1319? Maybe that's the key? What do you think? Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest MarcusHenrique Posted April 6, 2010 Report Share Posted April 6, 2010 Hey, I have an idea: There have been troubles with non-Pulse U8220 models, on which the touchscreen didn't work after they applied our boot.img (with our kernel). I'm pretty sure that both devices have the same HW. What is, if those devices use the synaptics_rmi_tm driver instead of the [...]_tm1319? Maybe that's the key? What do you think? Greetings, BigBear I think that If you think my u8220 will have more support to Multitouch you're probably right :( Nah, if you need anything from my phone just ask! :P Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 6, 2010 Report Share Posted April 6, 2010 I think that If you think my u8220 will have more support to Multitouch you're probably right :( Nah, if you need anything from my phone just ask! :P It would be indeed useful if you could maybe pull your config.gz off your device and upload it: adb pull /proc/config.gz config.gz :( Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest MarcusHenrique Posted April 6, 2010 Report Share Posted April 6, 2010 It would be indeed useful if you could maybe pull your config.gz off your device and upload it: adb pull /proc/config.gz config.gz :P Greetings, BigBear No prob, just wait 7 hours till I get home :( If you need anything else just make the list Att, MH Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 6, 2010 Report Share Posted April 6, 2010 No prob, just wait 7 hours till I get home :P If you need anything else just make the list Att, MH Thanks! :( Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest Rizzly Posted April 6, 2010 Report Share Posted April 6, 2010 Thanks! :P Greetings, BigBear Well, this is what my config looks like (with a screen that stops working with modaco). Still need the file? # CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI is not set # CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI_TM1167 is not set # CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set # CONFIG_TOUCHSCREEN_TOUCHWIN is not set # CONFIG_TOUCHSCREEN_UCB1400 is not set # CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set # CONFIG_TOUCHSCREEN_TOUCHIT213 is not set # CONFIG_TOUCHSCREEN_MSM is not set CONFIG_TOUCHSCREEN_CYPRESS_CPT=y CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI_TM1319=y Link to comment Share on other sites More sharing options...
Guest MarcusHenrique Posted April 6, 2010 Report Share Posted April 6, 2010 Hm.. in fact looks like our screen uses the synaptics driver he mentioned. Is that good news bear? Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 6, 2010 Report Share Posted April 6, 2010 Hm.. in fact looks like our screen uses the synaptics driver he mentioned. Is that good news bear? Unfortunately not at all :P But maybe because he flashed our boot.img he has the same kernel config? Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest MarcusHenrique Posted April 6, 2010 Report Share Posted April 6, 2010 Unfortunately not at all :P But maybe because he flashed our boot.img he has the same kernel config? Greetings, BigBear Hah I haven't read the "instead of" part when you said it couple posts ago. But I don't believe he's still using your boot.img, he just pointed that his version doesn't work with modaco roms; Anyway, I'll upload my config later. Cya Link to comment Share on other sites More sharing options...
Guest MarcusHenrique Posted April 6, 2010 Report Share Posted April 6, 2010 Here it is, hope it helps!config.gz Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 7, 2010 Report Share Posted April 7, 2010 Here it is, hope it helps! Thanks! At the first look, it looks exaclty the same :P Greetings, BigBear Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 8, 2010 Report Share Posted April 8, 2010 (edited) Dear BigBear Sorry to inform you both the touchscreen & hardware driver do not support Multitouch,so any work you have done,there is no any effect. Everything we were working for so hard just falls appart :P Edited April 8, 2010 by BigBearMDC Link to comment Share on other sites More sharing options...
Guest le_lutin Posted April 8, 2010 Report Share Posted April 8, 2010 Everything we were working for so hard just falls appart :P Yikes! Sorry to hear that. I thought you got the screen to register two separate (but simultaneous) touches though, no? Link to comment Share on other sites More sharing options...
Guest BigBearMDC Posted April 8, 2010 Report Share Posted April 8, 2010 (edited) Yikes! Sorry to hear that. I thought you got the screen to register two separate (but simultaneous) touches though, no? I thought that too, but I was wrong. I though lost not all of my hope, maybe I find a way to calculate the 2nd point out of the movement of the first point... Just don't know, how can the device register up to 3 fingers when it's not able to lacate their position? There must be a way ... somhow, sometime ... Greetings, BigBear Edited April 8, 2010 by BigBearMDC Link to comment Share on other sites More sharing options...
Guest le_lutin Posted April 8, 2010 Report Share Posted April 8, 2010 I thought that too, but I was wrong. I though lost not all of my hope, maybe I find a way to calculate the 2nd point out of the movement of the first point... Just don't know, how can the device register up to 3 fingers when it's not able to lacate their position? There must be a way ... somhow, sometime ... Greetings, BigBear Was it able to simultaneously track two finger presses (ie if you put two fingers on the screen and move both fingers around at the same time) ? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now