Hello,
I have a strange problem with my HTC Hero GSM, no SIM lock running either stock 2.1 with latest OTA, or rooted in VillainRom 12.
When I use my phone the touchscreen randomly becomes totally unresponsive at all or it marks things on the bottom when I press the screen in the upper half. This is very frustrating when you want to write messages or just want to navigate through webpages or a menu. When they keyboard is active it starts warping between letters and I have to turn off the screen and turn it on again in order to be able to continue writing on it. It works for a random amount of time and then starts acting on its own again.
During surfing I've also noticed that it randomly started to pinch-to-zoom in and out when trying to scroll with my finger up and down. It also breaks the scrolling inside menus and kinda lets the slide movement getting stuck and bouncing back at random spots.
All in all it's totally frustrating, because I treat my phones really good and don't throw em around or abuse em in any other way. My warranty is also already over that's why I tried to root my phone to find out if this still persists in other roms.
I rooted my phone with UniversalAndroot.apk and used recovery-RA-hero-v1.7.0.1.img in order to be able to flash custom roms.
I have also tried FroydVillain 1.6.1, Floyo 1.1.9. and Froyo 2.2 and while running these roms I had no problems at all with my screen being unresponsive or not reacting at all.
All those roms are really very very nice and I'd also like to thank the developers for their great job. I was astonished what my Hero can do and how much it still rocks. But I miss HTC Sense, because I'm used to it for more than a year now and I just don't want to work without it. I know it's not perfectly coded and costs some performance, but to my knowledge there ain't anything on the market that comes close to the fancy widgets and addons.
I would really highly appreciate if you have any idea what I could do in order to get a 2.1 rom with HTC Sense up and running properly.
I don't want to buy a new phone yet, because I want to wait for the new Nexus S. Yeah I know it will not have HTC Sense, but I don't want to wait for any update for more than a year again.
Thanks in advance for your kind help and assistance in this matter.
Cheers!
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.
OK, so far I have resisted the urge to root my Xoom because I don't have an extra SD Card, and am not really feeling any slowness on the system to want to overclock.
But then it occurred to me...
Does anyone have the latest Tiamat kernel installed and have the Motorola Bluetooth keyboard? If so, do you still have the stuck/repeating key problem, or is it fixed? To be able to actually use the keyboard again (I pretty much don't since getting a stuck repeat eliminates any speed advantage from touch typing) would be worth rooting my Xoom.
Please let me know one way or the other!
FWIW, I've been building my own kernels from upstream (i.e, with all the latest new stuff from Linus/NVidia/Google/Motorola) and I haven't seen the repeating key problem with my Apple Aluminum keyboard, so maybe there is something to that.
Can now confirm that after rooting and flashing Tiamat 1.4.0 that my Bluetooth problem with my keyboard is history. Feel free to spread the word
im running tiamat 1.4.1 and i havent seen the issue come back since.
kcrudup said:
FWIW, I've been building my own kernels from upstream (i.e, with all the latest new stuff from Linus/NVidia/Google/Motorola) and I haven't seen the repeating key problem with my Apple Aluminum keyboard, so maybe there is something to that.
Click to expand...
Click to collapse
I've found that the bluetooth problem only creeps up if the Xoom hasn't been rebooted for a while... in like four or five days. I have no idea what this means. Since I got in the habit of shutting it off from time to time, it's been much less of a problem (though it still occurs).
Perhaps, but my X only gets rebooted if I have a new kernel to load, so maybe there is something to the new kernels (but admittedly, I've only seen the issue once).
Hi, my DROID 2 has a keyboard issue, it seems that whenever I type, it'll randomly type the same letter multiple times. Thinking it was a Liberty GB issue, I used it as an excuse to jump ship to CM7. I'm running CM7, it's amazing. But, I still have the multiple entry problem. It's really bugging me, as my DROID 2 has never been better, and I don't think I can send it in for a warranty replacement due to it's cracked LCD, and I don't want to switch to my Xperia Play for messaging, because it doesn't have a hardware keyboard. I looked around, and it seems that it's a gingerbread problem, not specifically my phone, although I've not noticed the problem when using the soft keyboard, only the hard one, and only since I've started using Liberty and CM7. I was running an old version of Zombiestomped before, and I did not have that problem.
I'm running Miui and have never run into that problem. So it shouldn't be a GB problem. My guess is that it is either a CM/Liberty problem or a hardware problem (sticky keyboard).
I've been having the same problem. I used to use Fission, then I bumped up to CyanogenMod nightly #4, and last night I updated to #40. I THINKKKK I had the problem towards the end of using Fission, but I could be mistaken, that was a while ago and I can't really remember. It seems to have gotten progressively worse over the time that I've noticed it, which has led me to believe there might be something like dust in the keyboard which is causing it to fidget, or something along those lines.