When I first encountered the problem that my Hero device lower part touchscreen stop work "unresponsive" I tried a bunch of other roms, even stock from HTC.COM.
I have read a fair amount of threads with people that has the same problem. As far as I can tell there is no one at this time that know the solution or the root of the problem.
PLEAS everyone that have this problem post in this thread so that we are able to solve this irritating problem ones for all.
/Gekn
Things that I have tried
Flashed: Villian 10.2, Feeyo 1.7, 1.5.1, Modaco 2.1 r3, Stock hero unrooted, Modaco 3.2. Located the touch screens unresponsiveness with multi touch sensor apps.
GeknGekn said:
When I first encountered the problem that my Hero device lower part touchscreen stop work "unresponsive" I tried a bunch of other roms, even stock from HTC.COM.
I have read a fair amount of threads with people that has the same problem. As far as I can tell there is no one at this time that know the solution or the root of the problem.
PLEAS everyone that have this problem post in this thread so that we are able to solve this irritating problem ones for all.
/Gekn
Things that I have tried
Flashed: Villian 10.2, Feeyo 1.7, 1.5.1, Modaco 2.1 r3, Stock hero unrooted, Modaco 3.2. Located the touch screens unresponsiveness with multi touch sensor apps.
Click to expand...
Click to collapse
i also face the same issue. Intially i thought it was a ROM problem and flashed all the possible Rom's i can lay my Hands On but nothing seems to work. Its a hardware fault; digitzer or something it is called as.
Now my Hero just sits there without doing anything.
Its Hardware related. Had this too, tried also different ROMs with no help. Then i sent my device to Htc Support, they replaced the Touchscreen. After i got it back it was working for 3 weeks.
Now the same issue again. Have to send it back to htc.
-------------------------------------
Sent via the XDA Tapatalk App
If I remember right tou have to remove the fastboot or something "the thing that make the root paoosible" if your sending it to HTC.
Mine was send to HTC too for a new touchscreen.
No problems any more for 6 months now.
HTC told me its a very common problem.
Related
Morning, Fellow Forumers!
I've been using my HD2 for a few months now, and every day my frustration grows. This thing is unstable as hell. It either stops responding completely, or the phone application hangs (sometimes it's impossible to hang up a call), or just the backlight works, or the UMTS stops working... PAIN AND MISERY! I have it upgraded to the latest official firmware, but it doesn't help at all. Tried the Touch Tools to turn off unneccesary stuff - still no good.
It's even worse when it's BT'd to my Audi MMI. Every 10 seconds or so it's completely stuck for like 2-3 seconds. It looks like the BT firmware has not been optimized at all and whenever it refreshes the phonebook/calls list/etc with my car, the GUI is dead. Fixing that would be great stuff.
So, I'm asking to point me in the right direction. I don't care about warranty or anything, just want this device to be stable! Since the official FAQ is like 10 pages long... is there a FAQ's FAQ?
Basically - what's my first step? Thanks in advance!
PS: It's a retail version (non-branded) purchased in Poland.
Your solution Must be somewhere here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=534
And Here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=735
As for me I am very happy with my stock Rom,so far...!!
I have no problems with stock and with most of cooked ROMs
Have you tried re flashing the latest stock rom off the htc website?
task29 can solve most problems, however if you have done all those steps and still getting problams, you may have a faulty unit and it might need to be sent back for repair/replacement.
Really sorry to hear about your problems. Wish I could give you a good solution, other than to do a hard reset and then upgrade to the latest ROM. I am running a stock ROM and the HD2 is the best phone I have ever had. And I have had a few. Good luck.
I used my hd2 on a stock rom for ages, and it was stable enough, with the odd crash occassionally. I recommend using a custom rom. Since a custom rom, my battery life has improved dramatically, my hd2 runs faster and is so stable, i cant crash it if i really try!
Duttys V9 is a personal favourite
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
tompken said:
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
Click to expand...
Click to collapse
Bt calls are still unstable for everyone... work in peogress.....
Sent from my HTC HD2 using Tapatalk
I have had VirusRom installed for about a week now. Overall I love it.
Here is my problem though. When I am making a call the screen will lock. I have to push the power button to bring back up the screen in order to hang up the call.
Shouldn't the proximity sensor know when I pull it away from my face so I can hang up the call? It did before I went to this rom, was still using stock rom at that point.
Anyone know of a way to fix this problem? I have tried to post this question on the VirusRom forum, Since I think it is a bug with the rom, but am not allowed. It says you need 10 posts to be able to do that, Still I get that too even though I am over ten posts. Oh well on that though.
This could be a deal breaker for me and VirusRom. As it is quite frustrating to me. If anyone has any thoughts on how to get around this I would be thankful.
It's due to the kernel Virus installed in teh rom. It's one of Ziggy's first kernels and it has a bug that prevents the screen from turning on after/during a call as you describe.
Fix: Install a new kernel.
There are several on here to use, or you can search PPCGeeks / Ziggy to find his new kernels, which he has now fixed the proximity sensor issue.
Thanks for the answer. I downloaded kernal manager from the market. Any specific recommendations for a kernel? Adrynalyne's seem to be the most stable, but maybe I should stick with a stock kernal.
You can't go wrong with one of Adry's kernels. You should start with one those.
Sent from my BAMF'd T-Bolt
I had the same problem. I installed the new radio which was supposed to fix it and it did. But Im having trouble with the data connection, so I flashed back to the stock radio.
Ziggy's new kernal upgrade has fixed this issue. Id suggest downloading that. It works great and super crisp and fast over the version that came with the ROM and the proximity issue is fixed, been testing it for myself and all is good.
Check the VirusRom thread for info.
Ok, So I flashed one of Adrynalyne's kernals and now I don't have 3g or 4g. Just 1x. So do I flash another kernal, maybe the stock one, and the problem is solved? That will put it back the way it was right?
nope that did not work, I flashed Adrynalyne's stock rom and still just 1x. What have I done? What do I need to do to put it back? SInce I keep rom backups everytime I flash a ROM, I am going to flash back to the previous version that did have 3g and 4g working. I hope that works. The kernal is part of the ROM, correct?
Now this is getting frustrating. Flashed back to the previous working virus rom the one I had before the kernel update, and it still is only 1x. Wouldn't the kernel be part of the rom? Why did this not work? What can I do now?
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Use Adrynalyne's kernel
http://forum.xda-developers.com/showthread.php?t=1024338
I use the 4.3 and it runs perfectly fine and the prox sensor works, his are in Kernel Manager also so it will be an easy fix.
oscar615 said:
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Click to expand...
Click to collapse
verizon 3g might still be down?
Hi,
I read in Known Issues with this rom there are rare random reboots when turning WiFi on/off, but for me it's 4/5 times. Almost every time I turn on WiFi my Legend reboots.
Anyone having same issue?
For thousand times, yes.
Any clue what might be a problem? I haven't seen that many users are complaining about restarts, so it must be something else other than ROM
We don't have drivers for wlan chip (HTC drivers are not open source) compiled for gingerbread, so they are kinda buggy.
Nidzge said:
Any clue what might be a problem? I haven't seen that many users are complaining about restarts, so it must be something else other than ROM
Click to expand...
Click to collapse
Have you read all 237 pages of the tread?
This is a known issue with enough users reporting the issue to make it a common problem, if you haven't updated the kernel yet, I suggest you do, as this does help quite a bit regarding many FC's and other probs.
the new kernel can be found here http://forum.xda-developers.com/showpost.php?p=18184470&postcount=2228
ranger4740 said:
Have you read all 237 pages of the tread?
This is a known issue with enough users reporting the issue to make it a common problem, if you haven't updated the kernel yet, I suggest you do, as this does help quite a bit regarding many FC's and other probs.
the new kernel can be found here http://forum.xda-developers.com/showpost.php?p=18184470&postcount=2228
Click to expand...
Click to collapse
Thanks for your response mate. The problem is I already got that version of kernel in the first place when I installed mentioned ROM (latest version of Gingerbread 2.3.3). I don't know if there is something I can do to fix (or at least minimize that problem) since my WiFi is almost useless.
Nidzge said:
Thanks for your response mate. The problem is I already got that version of kernel in the first place when I installed mentioned ROM (latest version of Gingerbread 2.3.3). I don't know if there is something I can do to fix (or at least minimize that problem) since my WiFi is almost useless.
Click to expand...
Click to collapse
Oh dear, not so good then, not sure if there is a fix, the new kernel was supposed to be 'A' fix for the issue, perhaps the root cuase is still the drivers for wifi? When I was using OGO's gingerbread, even before the kernel update, I didn't have any wifi reboots, I wounder if there might be some regional reason for the issue? maybe there is something different hardware wise from country to country, I don't believe that standards are uniform accross every country?
I think this issue is definitely something for the DEVS.
Since XDA hates noobs i cant post this in ogo's thread..Just read about this. Maybe there are some wifi drivers to be drawed out of this update on the wildfire s or chacha or even salsa.
A round of Android updates has been found on on HTC Turkey's Facebook page, for European devices:
HTC Incredible S: Android 2.3.5 with HTC Sense 3.0: December 10th
HTC Wildfire S: Android 2.3.5 with HTC 2.1 and new lock-screen: December 10th
HTC Desire HD: Android 2.3.5 with HTC Sense 3.0: December 15th
HTC Desire S: Android 2.3.5 with HTC Sense 3.0: December 15th
HTC Flyer: Android 3.2 Honeycomb: December
HTC ChaCha and HTC Salsa: update to improve WiFi and Twitter functionalities: December
Okay so this is my first post on XDA and I hope it's in the right section. Anyways I bought an HTC Incredible off a collegue of mine about two weeks ago. I got the phone and immediately rooted and installed a custom rom (MIUIv4 to be exact) I noticed after a lil while that the touch screen would randomly go berserk clicking things, calling people, etc (usually right after turning screen on) When the screen starts doing it I'd turn it off and back on and it would be completely fine. I thought to myself "maybe it's just a problem with MIUI and installed PONS CM7. I still had the same issue. Now whats strange about all of this is if I'm running an RUU or Stock based rom the screen NEVER acts up. I've read on several forums that this is a hardware issue but most people still experience it on stock roms, this is not the case with me. I won't deny that it could be a hardware issue, but it's an issue that can be solved with kerenl/dirvers/software. I'm wondering if I can use the drivers and software from a stock based rom to combat the issue and make custom roms run like they are supposed to. In all of my research I found this link which seems to be pretty promising but I don't know where to begin with it. Unfortuneately I can't post a link until I've posted 8 times, uuugh.
Edit: It seems the longer I run a custom rom the more frequently the issue happens.
If anybody is intrested in helping it would be greatly appreciated. I've been racking my head for over a week on this one. You can look up the blog I read on google. It looks like it could solve my problem.
Unresponsive touchscreen of Nexus S solved by tuning kernel
Welp, title says it all.
The infamous, unresolved issue of Wi-Fi saying "error" under it in the settings.
Issue occurred first on unrooted stock(when I was give the phone), so I rooted it in hope I could somehow fix it via kernel flash, rom flash, or by other means.
I've practically flashed every kernel, every rom, tried several apps, and still running into this issue.
I would rely souly on Wi-Fi for internet access, seeing how I do not want Big Red up my arse with a contract(sticking to my Optimus V on Virgin Mobile running JellyBean).
The phone has no SIMcard, a 2GB sd-card, and is running the newly leaked BAMF ICS rom(installed in hopes of at least using bluetooth tether with my Optimus V for internet, but BT is broken on the leak).
I've searched every android forums on the web, read several dead end threads, saw even more that were unanswered.
Its as if this issue is purposely avoided being resolved.
I at least want someone to attempt to help, or give me the definitive answer of "you're poop out of luck, and there is no solution."
sent from my Zom-"Bean'(CM10 JellyBean).
It's usually fixed by a kernel flash so im assuming its a hardware error
trter10 said:
It's usually fixed by a kernel flash so im assuming its a hardware error
Click to expand...
Click to collapse
I've flashed several different kernels(mixing and matching several froyo & gingerbread kernel/ROM combos), which would you recommend?
BT working on the ICS leak with the .19 radios.
Sent from my ADR6400L using xda premium