Related
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!
Hi guys,
I've tried searching about the problem I have but I don't even know how to search it. I've rooted and installed custom rom on my Galaxy Note tonight, but have a rather serious problem. When I try to turn the screen on after the screen turns off automatically, I don't get the unlock screen but instead get black screen with speckles/pixels starting to appear. If I leave it like that, the screen is eventually filled with these speckles and becomes very bright. I have to turn off the screen with power button and back on several times before the unlock screen would appear.
Does anyone know what is causing this problem and how it can be fixed?
I've tried both Rocket ROM v22 and CheckRom and it happens in both.
Please help! It's driving me crazy!
maybe try another kernel.
i had same problem before, and only abbys 4.2 kernel help me! so flash abbys kernel!
Sent from my GT-N7000 using xda premium
keejoonc said:
I don't get the unlock screen but instead get black screen with speckles/pixels starting to appear. If I leave it like that, the screen is eventually filled with these speckles and becomes very bright. I have to turn off the screen with power button and back on several times before the unlock screen would appear.
Does anyone know what is causing this problem and how it can be fixed?
I've tried both Rocket ROM v22 and CheckRom and it happens in both.
Please help! It's driving me crazy!
Click to expand...
Click to collapse
I guess you are using franco kernel it is working out beautifully for some and for some it is generating pixel salad issue (ya thats the term given to ur issue)
Flash a different kernel try abyss kernel its the second best than franco!!
If you are not on franco kernel then read last couple of pages from franco kernel thread many are plagued with the same issue.
If it helps press thanks.!!
SHOT from my LOADED GT-N7000!!
Thanks guys.
I tried flashing AbyssNote 4.2 and that seems to have fixed it.
Shame franco kernel doesn't work for me.
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
lonehunter65 said:
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
Click to expand...
Click to collapse
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Miniloaf said:
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Click to expand...
Click to collapse
Do you know if devs are aware of this problem or working on it at all?
That's the only reason why I switched to DeSensed. It got annoying after a while.
I have been using 1.2 since it came out, and I have not experienced any random reboots or issues. I am using his kernel and am S-ON.
Sent from my HTC PH39100 using xda premium
I'm s-on and I've flashed with wcx recovery. Ive tried different methods of flashing the boot.img. Flashing it before and flashing the sd card copy afterward. I have also tried flashing either before or after. I did not select any UV. I chose the nonsense version of the install and am running apex launcher pro. I selected vram during install and disabled s2w. My CPU range is 384-1512 on setCPU, I am not running any profiles. I do use juicedefender ultimate and avast full time. I also have adaway installed. I can post a list of my other installed apps too if that would be relevant. Does any of this raise a red flag? Would the sense version of the Rom be more stable? Can anyone recommend another kernel if you believe that may be an issue? Any help would be appreciated as I do not have enough posts to state this problem in the dev forum.
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk