i rooted my htc evo GB and flashed cm7. had all kinds of problems with the touch screen and keyboard. the pull down bar for notifications is still not working. i have since flashed myn's warm 2.2. everything works fine except the pull down bar still wont work.
any thoughts? your help is greatly appreciated.
Possible touch screen failure for that part of the screen.
Try returning to stock and see if you still have the issue.
I've seen this problem talked about a few times before so it's definitely possible.
Turn on auto-rotate if it's off, rotate the screen, then try to pull down the notifications. If it'll work that way, it's your screen.
I really can't think of anything else that it could be. If you need a temporary solution, you can use auto-rotate to open your notifications or put the status bar at the bottom if you're on CM7.
You'll need to unroot & take it to Sprint or try to fix it yourself.
Sent from my PC36100 using Tapatalk
the pull down does work when screen rotates. i should clarify that i am currently using the myn's warm twopointtwo mod right now.
My first thought is did you do a thorough and proper wipe before you flashed the ROM?
trappedndroid said:
the pull down does work when screen rotates. i should clarify that i am currently using the myn's warm twopointtwo mod right now.
Click to expand...
Click to collapse
Every so often the top half of my screen will become completely unresponsive. I either wait about 5 mins, or do a hot restart, and it starts working again.
Edit: It has been doing it with every rom, Eclair, froyo, and gingerbread. It could be an overheating issue, or the hardware could be starting it's descent.
if i'm reading right a fresh wipe is wiping the user data and delvik right?
trappedndroid said:
if i'm reading right a fresh wipe is wiping the user data and delvik right?
Click to expand...
Click to collapse
Data/Cache/Dalvik
I would recommend doing each 3x just to be sure.
Elw00d said:
Data/Cache/Dalvik
Click to expand...
Click to collapse
I would include /system /boot as well for good measure.
android.secure and sd-ext [if it's used] as well.
if the "stupid person of the year" is still up for grabs i'll take it. you see, i often get drunk and wake up with my phone acting all funny. this problem had nothing to do with hardware, firmware, or software. it happened bcuz i changed the swipe settings!
i'll take that award now
sorry xda!
How do you change the swipe settings..?
Deck's + SZ + SuperCharger script + ViperMod script.
Related
This is my first time posting. I know how annoying reposts are, so I tried to find if anyone else had the same problems I have. Unable to find an answer, I seek a solution to my strange problem...
I flashed CM7 three days ago. Before flashing, I did a full factory reset, wiped cache, etc. I also performed a backup of rom, which was at the time CM6. Everything worked without a hitch for these past three days. I installed new programs, really enjoyed the new features. However, today, the screen suddenly became unresponsive.
It acts as though I am long-pressing something when I am not. It will not register even hard taps and when I try to hit the home key it brings up the most recent apps list as though I long-pressed. I have reset, but it keeps doing this. When I try to use an app where scrolling is required, it bounces back to the spot I started scrolling. Very frustrating. Any solutions?
At first I thought it was from installing swype beta, but after removing it completely, resetting, and reflashing, the screen continues to act up.
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hey thanks for your suggestion. I've tried it but the screen problem continues. I even tried going back to the stock rom. Do you think it's a hardware issue?
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
magus57 said:
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
Click to expand...
Click to collapse
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
wronskishin said:
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
Click to expand...
Click to collapse
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
magus57 said:
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
Click to expand...
Click to collapse
How do you change the screen density?
So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.
Sounds like a bad flash. Flash it again only wipe before you do. Do a nand restore>advanced restore data from a known good nand.
Sent from my SPH-D700 using XDA App
and dont forget to calibrate your battery after a fresh rom flash.
This has happened to me on sfr 1.2, 3 times now. For no good reason. I ended up having to reinstall rom a few times when other fixes failed. Since I enabled journaling its been a good boy though.
Sent from my SPH-D700 using XDA Premium App
Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.
libracolo said:
Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.
Click to expand...
Click to collapse
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.
Goodroid said:
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.
Click to expand...
Click to collapse
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!
libracolo said:
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!
Click to expand...
Click to collapse
At this point, I would try downloading the ROM again. I would also check out different Kernel. I'm using Genocide 2.0 and it works perfectly.
Genocide 2.0 Kernel: http://forum.xda-developers.com/showthread.php?t=961614&highlight=genocide
libracolo said:
So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.
Click to expand...
Click to collapse
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?
Snowdog1967 said:
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?
Click to expand...
Click to collapse
That's how I got it back to working. The 2nd time was from Launcher Pro FC'ing, but I wiped it again and re-imaged the Rom and Kernel. Then turned Journaling back on. I think it just gets in a "weird" state sometimes. It takes me about 3 minutes to re-run everything (including the backup once I re-image) and I guess I just don't see it as any worst than stuff I have to do to PC's all day long when testing....haha
Same happened to me. Just reinstalled rom and kernel
Sent from my SPH-D700 using XDA App
Ok to make a long story short, after I themed a whole bunch of themes I did not like the end result so i wanted to go back to where I was before. I loaded my backup and everything backed up but its like the backup was not clean or something because my phone has just been to unstable and acting stupid. It force closes some things and I have to pull the batt about once a day because I can't answere the phone. Also something about google services framework keeps popping up when I call someone. I am fed up. I am on srf 1.2 with the genocide 2.0 kernal.
Any thoughts on what I should do? Odin back and start over? Or is there anything better out there with gingerbread? I have not looked into anything current. Seems like there is a lot of stuff I have not seen before. Looks rather cofusing. Cwm5, selfkang cm7, acs rom manager. I am at. A loss for words. Can anyone help me.
Led4lyf said:
Ok to make a long story short, after I themed a whole bunch of themes I did not like the end result so i wanted to go back to where I was before. I loaded my backup and everything backed up but its like the backup was not clean or something because my phone has just been to unstable and acting stupid. It force closes some things and I have to pull the batt about once a day because I can't answere the phone. Also something about google services framework keeps popping up when I call someone. I am fed up. I am on srf 1.2 with the genocide 2.0 kernal.
Any thoughts on what I should do? Odin back and start over? Or is there anything better out there with gingerbread? I have not looked into anything current. Seems like there is a lot of stuff I have not seen before. Looks rather cofusing. Cwm5, selfkang cm7, acs rom manager. I am at. A loss for words. Can anyone help me.
Click to expand...
Click to collapse
Do you know if you have journaling on? If no or not sure restore again from your nan and flash journaling on from here:
http://forum.xda-developers.com/showthread.php?t=1071723
Go to settings>applications>manage applications>all scroll down to Google Framework Services, click it and hit clear data.
tazfanatic said:
Do you know if you have journaling on? If no or not sure restore again from your nan and flash journaling on from here:
http://forum.xda-developers.com/showthread.php?t=1071723
Click to expand...
Click to collapse
this. No really!
if youre looking to start over i can tell you i went from stock to acs ics v5.5 right before marcusant stopped dev and did his red revival rom. it was smooth, just a little buggy, but was eating my battery alive. I then switched to legendary 2.1 which was ok but in the end i opted for cleangb. its just simpler and i dont really need all that much. good luck
Ok so I cleared data and that solved the google.framework issues. But my gps button on the pulldown bar does not turn gps on. I also still can not send audio messages with the stock messanger.
Any thoughts? Should I be looking at gingerbread at this point or should I wait for a while?
Led4lyf said:
Ok so I cleared data and that solved the google.framework issues. But my gps button on the pulldown bar does not turn gps on. I also still can not send audio messages with the stock messanger.
Any thoughts? Should I be looking at gingerbread at this point or should I wait for a while?
Click to expand...
Click to collapse
Toggle GPS a couple of times within Settings menu and then reboot and try the button.
Sent from my SPH-D700 using XDA App
Toggled and reboooted, still did not help gps still does not work.
Led4lyf said:
Toggled and reboooted, still did not help gps still does not work.
Click to expand...
Click to collapse
Does it work if you turn it on in settings? If not then Odin back to EC05, check GPS, if it works root and flash your ROM. Check it. If it works THEN do an advanced data restore from your nandroid and see if it still works. If it is broken then, try a factory data reset. If it is working again then reinstall apps from the market and set everything up again without restoring the bad data, or restore from an older nandroid where it was working.
The gps symbol does not show up when I turn it on in settings, but I have noticed that if I use an app that requires gps to be on it will take me to the settings menue where I can turn it on. Depending on the app the symbol sometimes shows up. Gps always seems to work when a gps app needs it. It just really bothers me that the button does not work in the pull down bar.
Led4lyf said:
The gps symbol does not show up when I turn it on in settings, but I have noticed that if I use an app that requires gps to be on it will take me to the settings menue where I can turn it on. Depending on the app the symbol sometimes shows up. Gps always seems to work when a gps app needs it. It just really bothers me that the button does not work in the pull down bar.
Click to expand...
Click to collapse
You will probably have to Odin to EC05, check your button, if working root and flash ROM and check it. Should still work. Do not restore all your data. You will need to do a Titanium backup and pick and choose apps and data you must have.
Sent from my SPH-D700 using XDA App
Led4lyf said:
The gps symbol does not show up when I turn it on in settings, but I have noticed that if I use an app that requires gps to be on it will take me to the settings menue where I can turn it on. Depending on the app the symbol sometimes shows up. Gps always seems to work when a gps app needs it. It just really bothers me that the button does not work in the pull down bar.
Click to expand...
Click to collapse
You do realize that the GPS icon will only appear on the status bar when GPS is being used, right? Just because you have it turned on, whether with the pull-down menu or not, does not mean it will appear on the status bar. It may be on, but in standby waiting for an app that uses it. GPS kills battery, thus standby mode when not in use.
That said, while I don't know which ROM you've been using, most--if not all--generally "light up" the toggle buttons when something is turned on, even if it's in standby mode. Does the toggle button change state, i.e., light up, change color, or switch between "ON" and "OFF" when you toggle it?
I am on srf 1.2 and genocide 2 kernal. That makes sense, yes the button changes color and says on and off. I just thought that the icon used to appear when I pushed it. Maybe not.
Led4lyf said:
I am on srf 1.2 and genocide 2 kernal. That makes sense, yes the button changes color and says on and off. I just thought that the icon used to appear when I pushed it. Maybe not.
Click to expand...
Click to collapse
I don't remember SRF 1.2 doing that, but it's been a few months since I was on SRF or Android 2.2. What's important to know is that as long as the icon switches state and GPS works when you need it, everything is functioning properly. IIRC, for the past few ROMs I've used the icon is only present when GPS is actively functioning, not when in standby mode. This is a good thing, it lets you know when it's burning up battery.
BTW, SRF 1.2 with Genocide 2 was my ROM of choice for Android 2.2! I recommend you upgrade to a 2.3 ROM these days though. To be honest, I've only used EpicMTD CM7, but it's awesome. The devs are knocking out issues very quickly, and we should be an officially supported CyanogenMod device soon.
Thanks for all your help. I guess I will not worry about it then. So I am kind of new to all the gingerbread roms and stuff. Is there or can you post some links that would be helpful for me to read? I have heard about acs rom manager and selfkang cm7 and cwm 5. I know nothing about any of this stuff. Ever since I rooted and romed with srf and genocide I never kept up to date with all this new stuff. Thanks
All of a sudden regions of my screen are not responding to touch and it seems like the calibration is off. For instance, when typing, the backspace is always typing the letter 'L' above and I'm unable to pull the notification bar down (it thinks I'm touching below it).
Is my phone toast, or is there a way to recalibrate the screen?
Did you try the touch calibration under language and keyboard? Are you stock, rooted sense, or AOSP?
Sent from my Droid.
I'm rooted, on Aerovan's CM7.2. About 5 minutes ago the notification bar was working fine, but then I locked the phone and it stopped working again. When I touch the notification bar, it thinks I'm touching below it.
I've tried formatting and loading default CM7.2 to no avail. Dipped phone in dry rice all last night to no avail.
Not sure what to try at this point. I can't find any calibration tools in the Settings, including the one in the keyboard/input area.
also happening for me
brymaster5000 said:
Did you try the touch calibration under language and keyboard? Are you stock, rooted sense, or AOSP?
Sent from my Droid.
Click to expand...
Click to collapse
Tkanks for the post I was having the same issue and saw ur post to calibrate the screen and that works so thanks
jheathco said:
I'm rooted, on Aerovan's CM7.2. About 5 minutes ago the notification bar was working fine, but then I locked the phone and it stopped working again. When I touch the notification bar, it thinks I'm touching below it.
I've tried formatting and loading default CM7.2 to no avail. Dipped phone in dry rice all last night to no avail.
Not sure what to try at this point. I can't find any calibration tools in the Settings, including the one in the keyboard/input area.
Click to expand...
Click to collapse
I haven't run CM7.2 for a while, so I can't remember if there is a keyboard calibration like in Sense (I'm on SkyRaider Zeus). Hopefully someone running it can chime in.
Unfortunately I can't even find Skyraider to download. But this screen issue is bugging me BIG TIME. I have a dialer in the launcher bar at the bottom left that responds when I touch it. If I'm in an app however and touch that area, it doesn't respond.
WTF is going on?!
I've tried reformatting on clean CM7.2 and CM9. Stock is my last hope...
brymaster5000 said:
I haven't run CM7.2 for a while, so I can't remember if there is a keyboard calibration like in Sense (I'm on SkyRaider Zeus). Hopefully someone running it can chime in.
Click to expand...
Click to collapse
I got skyraider 1.3 from their website but pull down goggles and set up just force closes. I am not the only one. Think they uploaded a bad zip I would love to try again if it worked. I downloaded twice and seen a post today I am not the only one with this issue.
Dude I have so many issues like that, even on pure stock. Idk...but on cm9 I had some serious issues
Sent from my HTC Incredible 2 using XDA
I rooted my galaxy s3 when I got it. sometimes the screen turns on and it is unresponsive to touch. As soon as I turn the screen off and back on with the lock button then it works fine. It does it randomly, for instance when somebody calls I can't answer it sometimes I have to hurry up and turn the screen off and back on so I can swipe to answer. Also when I'm playing a game like hill climb racing it works then after a minute it stops responding completely until I lock and unlock the screen. Everything was working fine until I rooted it. That is my only issue. Any suggestions? Thanks
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Spark91 said:
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Click to expand...
Click to collapse
No i am rooted only no rom or custom recovery just went back to stock and updated to 4.1.2 and re rooted and it still does the same thing.
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
bump
CNexus said:
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
Click to expand...
Click to collapse
Ok I turned the developer option on to track touchs and sure enough when the screen touch "freezes" it is still responsive to touch it's just way off. And even though it is way off I can get it right about where I originally am trying to touch, and it still does respond. Also when it freezes, there are two touch spots and they are way off of where I am touching..! Any Ideas???
I am having an issue on 4.1.2 TW; has happened on both TPR and JellyBomb... when phone boots or I wake it up with home or power button, lockscreen is in landscape mode and unresponsive to touch. Have to pull battery and wipe cache/Dalvik. Is this just from multiview?
Using CWM with KT Kernel (it has happened on various KT builds, including 14MAR, 27MAR and 11APR).
Anyone know what's causing this?
EDIT: well, as usual, a quick PM to Kennyglass123 has solved the issue! I forgot to uncheck the "ripple effect" and I'm using AOSP lockscreen. Nothing like feeling like a schmuck to start your weekend!
Mucho thanks to Kenny, as per usual...