well hi everyone, I didn't know you guys know it or not. that the cm7 always a multi touch problem after a few weeks since the first boot. but stocks isn't. and this problem is comfirmed i guess cuz i tried many roms. but i always tried it at maximum 2 finger(our phone can only support 2 finger touch). and i used many roms for a few weeks without modding it. after a few weeks, i found out every cm7 will respond to touch screen extremely slow sometimes when 2 fingers taps on the screen quickly at the same time, 2 fingers draw or keep pressing on the screen works normally. stock doesn't has this problem. or you can try it out. this bug will not occur all the time. it's kinda rounding bug(occurs in a certain time), the multitouch will working perfectly without any kind bugs on cm7 for a few hours per day. i don't wanna flash new roms again cuz the bug will occur again if i download, install or even launch apps and i got too much of important conversations/data in my current os. im a music lover so if i flash stock roms the sound isn't that good and loud enough even with patches. it's very irritating when playing multi touch games.
have you experienced this bug before on cm7?
any solutions?
thx for your help
Related
Im running ZenHeroFX 2.1 Lite ROM with 710 Darchstar kernel... my phone is so annoying with it. At times it is lightning fast and everything works perfectly. And other times, (often but not always) during and after recharging from a low battery (ie. <15%) the touchscreen becomes super laggy.
For instance, while clicking on an icon on my homescreen, it will light up but not start the app. Rather, it will freeze for a sec or two and then as if I held the icon it would try to move it around the screen. Or when dialing a number the numbers would show up literally 20 seconds or so after the keypress.
Today the same thing happened but after a few minutes of this the touchscreen became totally unresponsive. I realized tho, that I could use the menu, home search, back and power keys and the phone responded almost at normal speed. But I was unable to enter any type or anything else involving the touch screen. After several reboots and one long reboot after clearing the cache, it finally is back to normal. This happens to me every few days or so, however, and is very annoying. Any suggestions as to why this is and/or how to stop it?
Change roms buddy. Sounds like your having a ****ty time with that one
Best very is to go with cyanogen. Have yet to have a problem with it not have I found a faster rom. My 2 cents
Sent from my HERO200 using XDA App
I fell in love with Konikub's Pure Hero rom but after the discovery of the bug in Toasts BFS #89 kernel that force closed the phone from time to time i had to reconsider. I know they make the updated kernel for roms that had that issue but without BFS the speed of the rom just isn't the same even overclocked. That is until i revisited Froyo after the first shrewd attempts back in the day lol. Let me tell u Darch and team r a dedicated group of talented individuals who know what they r doing when it comes to ROM development. His CyanogenMod 6 though it's still in the final testing stages is way good enough as an everyday ROM for me. It's fast without the complexity of BFS and is customizable to all ends. If u love senseless roms then u will love CM 6.
my touch screen was crazy when I get my phone out of my pants. I did not touch the screen but it still automatically run the app and drag the taskbar up and down .........
nobody is like me???
care to share more details and/or what ROm you're running? 2.2?
it happened randomly to me too, with any rom 2.1 2.2, but I still didn't figure the reason out yet..
Same for me.I have cronos 1.6.1 on phone with adw launcher.But happens only ones or twice.
Sent from my Milestone using Tapatalk
You guys probably overclocked it too much damaging the touchscreen.
Crypto_ahash said:
You guys probably overclocked it too much damaging the touchscreen.
Click to expand...
Click to collapse
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
lapy said:
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
Click to expand...
Click to collapse
I used to have that issue with stock 2.1 roms.
CM6, Sense mod, fastest Eclare and now MIUI does not bring that night mare back to me.
Also, if you charge using a 2-pin socket [the one without the earthed pin, popular in Asia], it'll show up.
OP needs to be a little more clear, but let me say my results.
Ever since flashing 2.2.1 SBF and then applying a few Froyo Mods and even goign back to ECLAIR,
I noticed that multitouch screws up. Sometimes it things I have a finger on the screen already, so by putting a finger on, it does a pinch zoom on me even though I only have 1 finger on it. Then sometimes it doesn't let me press an icon on my screen insisting my finger is elsewhere. Other times the notification bar starts getting pulled down randomly.
Perhaps Kadalban can explain his Multitouch fix, but for me it seemed to solve a lot of issues. Granted it was only pushed out in CM6 12/4/2010, which gives me 1 day to test so far, but some of those freak-incidents have been disappearing. You'd have to give me 3-5 days to conclude anything, but for now it seems to have done the trick.
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
duytrum444 said:
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
Click to expand...
Click to collapse
Update to the new CM6. 12.04.2010 solves it for me.
i'm using it....and now,i don't have issue again. i testing it.
Sent from my Milestone using XDA App
how did you fix your screen.my homebutton does not respond
I just changed to some mod roms and the problem disappeared for me.
Some of my friends got really big issue with the touch panel and when they came to Motorola service point, the technicians said there is a known issue with the panel they used but not all customers are affected (hence some people are OK after trying different roms).
So if one experiences it then just needs to go to Moto and they'll change to a healthy-guaranteed panel obviously, if you're still under warranty, it's free!
hey guys!
Well i was trawling the android forums and found this!
http://www.neopeek.com/viewtopic.php?t=7524
All thanks yo neopeek for the rom.
I decided to test it out on my kovsky. This coupled with I believe duckkly's kernels worked like a charm!! ill post the kernels up here too as I experimented with quite a few to see what worked best!
Battery life: 8 hours on full blast so i rekon around 11 on normal usage
Wifi: never ever ever dropped on me so far! thou it does seem to be weak in some places around my house where i usually should be getting more signals and strong at places where i get little signal :S.confusing
phone: well calls come in and stuff but sometimes ull see a black screen and cant see who's calling! :S
Bluetooth: paired with my mw600s just fine dont know about file transfer
market:works just fine a bit slow though..could be my internet speeds out here in pakistan.
Apart from that using whatsapp like a charm. facebook apps. gaaps everything works!! not a single sod to date been using it for around about 5 days or so.
Sorry for the spelling errors! big thanks goes out to neopeek and duckkly or whoever compiled those kernels !
PS: oh and the keys will freeze up as you hit around 20% battery. I simply reboot. Also terminal doesnt seem to be working. keeps crashing on me but i dont really ever use it in daily use so it seems to be pretty stable apart from these flaws. Also you'll need to reinstall quickpic from market
Also im on radio 1.16 i believe. 1.14 seemed to drop calls randomly.
please read all of neopeek's instructions before flashing ! happy flashing
can't confirm 20% battery being the point where keys stop working. for me 4 hours of uptime seems the be magic point...
i stopped restarting modules via script (how to has been explained many times in here) and simply restart. most of the time it happens when an app is running - now what good is it if you have a shortcut somewhere, but can't get there because back- and home-key isn't working?!
but yeah, neofroyo is a big step forwards. first time using android on x1 is fun!
for terminal to work you have to reinstall it just like quickpic.
i just hope we'll see some kernel-update soon. without it the whole thing is pointless.
lol truee..thanks for the terminal update. oh if u press the camera button it will take you back to your home screen. than i guess u could load the keyboard modules..annoying i never bother with it. try my combination of kernel it gives me decent battery lifee but yea its the kernel with all the problems. tried the new kernels but they dont seem to work properly
hm, which kernel-version is that?
might try if i know which it is. just had to step down from ygge-monster to ygge-turbo. monster made my touchscreen getting unprecise in left half.
thx for the update with cam-button - never bothered to press that, since camera doesn't work anyway.
yeah, new kernels suck for our device, especially since they're missing the specific battery-driver for x1. the only guy still working on x1-kernel has been silent for months, but i can see he's still at it (porting 2.6.35.7).
Just tried pressing cam-button.
Falls back to lockscreen, after unlock shows homescreen. But system is frozen and after some time reboots directly to android. But lots of stuff doesn't work, especially phone-stuff. So i have to reboot winmo anyway.
Sent from my X1i using Tapatalk
i think its the ducckly's keyboard not loaded as modules turbo verison. I believe it should be that because i remember the msm drivers werent really working properly on it
Sent from my Transformer TF101 using Tapatalk
So I started noticing lag on games with a virtual pad. As in, jump works fine if im standing in game for example, but im running and I try to jump, either it doesnt do it at all, or it does it with some lag.
So I downloaded a multitouch tester and pretty much confirmed that there's an issue there.
If I just touch with one finger at a time, it works fine. If I press with two fingers and keep them there moving them around and whatnot, it also works fine.
BUT, if I keep pressing with one finger and use the other one to do a fast light tap, half of the time it doesnt register it.
Im using the ROM posted here: http://forum.xda-developers.com/showthread.php?t=1583871
wich im finding to be great, but I thought of originally posting my issue there since I gather it is more likely to be caused by software and not hardware.. right? considering simple touch works completely fine.
Any ideas?
Ace supports only 2 fingers at a time. But i did not find any types of lags while using 2 fingers. But it wont work if u use 3 or more fingers at once.
REPLY
Hey I got 100% same issue too. On original cm7 nightly.
But I found out sometimes it works and sometime it doesn't seems to work. I think it's similar to the rounding bug.
Maybe it's the kernel problem. Just don't overclock and it will work well. Or, reboot your phone and wait for a night without touching it, and the problem is gone. However, the bug will occur again after you install an app or launch an app. This multi-touch bug always occur on cm7. If you don't want this problem you can use stock roms. But if you say touch making it lags, it doesn't make our phone lags or the game you play using this phone is a bit slow. Just the second finger is responding slowly if the first finger is pressed/touched on the screen.
And I've tested this bug using the dev tools in the cm7 rom. dev tools/pointer location. All of the stock rom doesn't have this bug except cm7. CM7 will not have this problem on the first few weeks since the first boot. hope it helps
It's a Ace Hardware issue. Nothing to do about it.
King of the mashed potatoes©
Getting a faster device is the only solution
I got transformed into a potato while writing this post..
Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.
using CandyRom 5.0.2
I never faced any touch freezes issue
@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?
im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english
Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.
I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.
1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)
I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.