[Q] TOUCHSCREEN has stopped working - Wildfire Q&A, Help & Troubleshooting

Upgraded to CM 7.2 Stable last week.
My phone was alive till 1:00AM before going to bed.
This morning touch screen stopped working.I can't even unlock my phone by sliding it.Every time I have to remove the battery to boot in HBOOT.
I have tried to factory reset my device 6 times till now.
Do i need to downgrade to stock/Unroot and root again ?
I have been loyal to CM but now it seems it's is a real pain in the ass.Already ****ed GPS,Wi-fi and Bluetoot and you need to patch everything from A-GPS to Wi-fi.What's the point of releasing such crap stable release.I don't get the point.
Obviously very ****ed up!!!!
Any suggetions ???
HTC Buzz(Wildfire)
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
MICROP-0622
TOUCH PANEL-SYN3KY_01
RADIO-3.35.20.10
Mod :CM 7.2 Stable
kernal :2.6.35.14-nFinity arco
Recovery :5.0.2.8

Try flashing a different ROM.
Also CM7.2 stable is working just fine for me.
Sent from my HTC Wildfire using xda premium

The gps, wifi and bt problems are caused by a bug in the radio i believe, not in cm7........
Sent from my GT-I9100 using xda premium

Scratch0805 said:
The gps, wifi and bt problems are caused by a bug in the radio i believe, not in cm7........
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That's not the help I was looking for.

optimusodd said:
That's not the help I was looking for.
Click to expand...
Click to collapse
You have to run GPS and Wi-fi patches everytime you flash a CM ROM.
Here is one :http://forum.xda-developers.com/showthread.php?t=1447591
CM screws your GPS,Wi-fi and BT and even reflashing the RADIO doesn't help.
It's not only me,eveybody is facing the same problem.
And guess that was not enough,right now I am banging my head over this "Touchscreen problem".Sometimes i wonder are these the fruits of ROOTING your device.Gah!It sucks!

optimusodd said:
You have to run GPS and Wi-fi patches everytime you flash a CM ROM.
Here is one :http://forum.xda-developers.com/showthread.php?t=1447591
CM screws your GPS,Wi-fi and BT and even reflashing the RADIO doesn't help.
It's not only me,eveybody is facing the same problem.
And guess that was not enough,right now I am banging my head over this "Touchscreen problem".Sometimes i wonder are these the fruits of ROOTING your device.Gah!It sucks!
Click to expand...
Click to collapse
Moreover,you know what's the irony ? I am not bragging but you get all this crap after donating them periodically.It's so sad.

optimusodd said:
You have to run GPS and Wi-fi patches everytime you flash a CM ROM.
Here is one :http://forum.xda-developers.com/showthread.php?t=1447591
CM screws your GPS,Wi-fi and BT and even reflashing the RADIO doesn't help.
It's not only me,eveybody is facing the same problem.
And guess that was not enough,right now I am banging my head over this "Touchscreen problem".Sometimes i wonder are these the fruits of ROOTING your device.Gah!It sucks!
Click to expand...
Click to collapse
Just calm down, mistakes are easily made when running on anger.
I have never experienced the issues you state from cm7 to the extent you are suggesting. Ok i have had to flash sense rom a few times to re-trigger the gps but thats it and its as simple as flashing a nandroid.
Some users report running a stock eclair ruu fixes the touch screen. Search around and try it and if it fixes your problem and you get back up and running i would personally recommend lewaos rom. Good luck.
LeWaOs Rom

P. S to answer your rude post in agps thread....... the gps patch is a tweak not a necessity, google specific cwm is the version i use,
The freeze you experience can be due to overclocking your phone too much!!
Failing an ruu fix, my screen got extremely scratched and damaged at work so i replaced my digitizer i.e touch screen very easy see here http://forum.xda-developers.com/showthread.php?p=24197344
Replacement cost me £8 from ebay and it took me like 10 minutes to do it.
LeWaOs Rom

slymobi said:
P. S to answer your rude post in agps thread....... the gps patch is a tweak not a necessity, google specific cwm is the version i use,
The freeze you experience can be due to overclocking your phone too much!!
LeWaOs Rom
Click to expand...
Click to collapse
Sorry if i sound rude.I am REALLY sorry if anyone is going to take offense in this.I am really ****ed up right now.
Since the day i updated to CM 7.2 not even a single day went without any trouble.
I am not able to use my phone for last 17 days and I am pretty sure we don't buy a device to flashing ROMs and then spending our time tweaking and troubleshooting the issues.That is exactly what I have been going through.Already done Hard reset more than 20 times for no avail.
Sometimes it's market prob,then GPS,Wi-fi teethering issues and now this Touchscreen problem.
Anyways,Thanks for your reply.
Found this WF-S thread,is this gonna work ?what do you think ?http://forum.xda-developers.com/showthread.php?t=1436314
Nope,I never overclocked my phone.It didn't fall down either.

optimusodd said:
Sorry if i sound rude.I am REALLY sorry if anyone is going to take offense in this.I am really ****ed up right now.
Since the day i updated to CM 7.2 not even a single day went without any trouble.
I am not able to use my phone for last 17 days and I am pretty sure we don't buy a device to flashing ROMs and then spending our time tweaking and troubleshooting the issues.That is exactly what I have been going through.Already done Hard reset more than 20 times for no avail.
Sometimes it's market prob,then GPS,Wi-fi teethering issues and now this Touchscreen problem.
Anyways,Thanks for your reply.
Found this WF-S thread,is this gonna work ?what do you think ?http://forum.xda-developers.com/showthread.php?t=1436314
Nope,I never overclocked my phone.It didn't fall down either.
Click to expand...
Click to collapse
I dont know and i personally wouldnt try it. Is the touch totally gone or is it only in certain areas of the screen? For the price it costs id just get a new digitizer. You could just have a loose connection too? Check by following guide in link i gave.
Cant help any further really, sorry.
LeWaOs Rom

optimusodd said:
Upgraded to CM 7.2 Stable last week.
My phone was alive till 1:00AM before going to bed.
This morning touch screen stopped working.I can't even unlock my phone by sliding it.Every time I have to remove the battery to boot in HBOOT.
I have tried to factory reset my device 6 times till now.
Do i need to downgrade to stock/Unroot and root again ?
I have been loyal to CM but now it seems it's is a real pain in the ass.Already ****ed GPS,Wi-fi and Bluetoot and you need to patch everything from A-GPS to Wi-fi.What's the point of releasing such crap stable release.I don't get the point.
Obviously very ****ed up!!!!
Any suggetions ???
HTC Buzz(Wildfire)
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
MICROP-0622
TOUCH PANEL-SYN3KY_01
RADIO-3.35.20.10
Mod :CM 7.2 Stable
kernal :2.6.35.14-nFinity arco
Recovery :5.0.2.8
Click to expand...
Click to collapse
This is totally a ROM's issue... If trully you can see MICROP-0622 and TOUCH PANEL-SYN3KY_01 on HBOOT then reflash a new ROM. Probably the ROM you flashed is broken. I've had my Touch Screen not working but then on HBOOT what I saw was TOUCH PANEL-FAIL.
Do a Nandroid, Wipe Memory from "HBOOT", download a new ROM (You still can give CM7 Stable a chance as not everybody is experiencing this) and Flash.
If that never worked, Flash an RUU via FASTBOOT, as you are S-OFF, you can downgrade and upgrade at anytime.
Seriously, as you are not seeing TOUCH PANEL-FAIL, you Touch Screen SHOULD work or the HBOOT is corrupt and not giving you the correct info.
Hope this helps.

slymobi said:
Is the touch totally gone or is it only in certain areas of the screen?You could just have a loose connection too?
LeWaOs Rom
Click to expand...
Click to collapse
As I said,it was alive before i went to bed.
In the morning touch screen stopped working.I can't even unlock my phone by sliding it.Every time I have to remove the battery to boot in HBOOT.
What do you mean by loose connection ?

My optical trackball is working though.

olu.danNY said:
If trully you can see MICROP-0622 and TOUCH PANEL-SYN3KY_01 on HBOOT then reflash a new ROM. Probably the ROM you flashed is broken. I've had my Touch Screen not working but then on HBOOT what I saw was TOUCH PANEL-FAIL.
Seriously, as you are not seeing TOUCH PANEL-FAIL, you Touch Screen SHOULD work or the HBOOT is corrupt and not giving you the correct info.
Hope this helps.
Click to expand...
Click to collapse
ROM is not broken coz I have verified the md5sum.
Wiped the memory from "HBOOT" and reflashed CM 7.2 ,25th time or so..still same unresponsive touchscreen.
Yes,it's showing MICROP-0622 and TOUCH PANEL-SYN3KY_01 on HBOOT

optimusodd said:
Sorry if i sound rude.I am REALLY sorry if anyone is going to take offense in this.I am really ****ed up right now.
Since the day i updated to CM 7.2 not even a single day went without any trouble.
I am not able to use my phone for last 17 days and I am pretty sure we don't buy a device to flashing ROMs and then spending our time tweaking and troubleshooting the issues.That is exactly what I have been going through.Already done Hard reset more than 20 times for no avail.
Sometimes it's market prob,then GPS,Wi-fi teethering issues and now this Touchscreen problem.
Anyways,Thanks for your reply.
Found this WF-S thread,is this gonna work ?what do you think ?http://forum.xda-developers.com/showthread.php?t=1436314
Nope,I never overclocked my phone.It didn't fall down either.
Click to expand...
Click to collapse
Don't come whining here about how your phone doesn't work and its all cm's fault, this is a developers website i.e not intended for your average everyday user as there may and most likely will be bugs. The only person to blame for your phone being broken is yourself for flashing it in the first place......
I also never experienced any of the bugs you mention except the gps which i figured out how to fix in 5 minutes by searching this forum. By all means ask questions if you need help but don't complain that something from xda broke your phone as it didn't.... You did!!
Edit: run an ruu, if its a software problem and that doesn't fix your touch then you may need a new digi.....
Sent from my GT-I9100 using xda premium

Scratch0805 said:
Don't come whining here about how your phone doesn't work and its all cm's fault, this is a developers website i.e not intended for your average everyday user as there may and most likely will be bugs. The only person to blame for your phone being broken is yourself for flashing it in the first place......
I also never experienced any of the bugs you mention except the gps which i figured out how to fix in 5 minutes by searching this forum. By all means ask questions if you need help but don't complain that something from xda broke your phone as it didn't.... You did!!
Edit: run an ruu, if that doesn't fix your touch then you may need a new digi.....
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for your pearls of wisdom but your post didn’t solve my problem…I think one should not preach if he can’t be any sort of help.
With all due respect,lemme tell you one thing,I understand what XDA is and I didn’t accuse XDA for anything.I didn't even mention “XDA” even a single time in my queries.Guess you didn’t even bother to go through my posts.Your thanks meter readings might be higher than me but that doesn’t prove me “ignorant”.
All I want to say is I am really disappointed with CM as I never faced such problem with CM 7.1.0.1 except GPS,BT and Wi-Fi...and now their so called "STABLE" release CM 7.2 which has still got some bugs is troubling so many users (visit CM 7.2 Stable forum http://forum.cyanogenmod.com/forum/138-htc-wildfire-stable-mod/) and that is what screwed my touchscreen.Anyways,thanks, your post was really helpful 0_O
P.S. If you can’t help wildy users please visit galaxy s2 forum and share your knowledge there.

optimusodd said:
Thanks for your pearls of wisdom but your post didn’t solve my problem…I think one should not preach if he can’t be any sort of help.
With all due respect,lemme tell you one thing,I understand what XDA is and I didn’t accuse XDA for anything.I didn't even mention “XDA” even a single time in my queries.Guess you didn’t even bother to go through my posts.Your thanks meter readings might be higher than me but that doesn’t prove me “ignorant”.
All I want to say is I am really disappointed with CM as I never faced such problem with CM 7.1.0.1 except GPS,BT and Wi-Fi...and now their so called "STABLE" release CM 7.2 which has still got some bugs is troubling so many users (visit CM 7.2 Stable forum http://forum.cyanogenmod.com/forum/138-htc-wildfire-stable-mod/) and that is what screwed my touchscreen.Anyways,thanks, your post was really helpful 0_O
P.S. If you can’t help wildy users please visit galaxy s2 forum and share your knowledge there.
Click to expand...
Click to collapse
Woaahhh....... Someone needs to get down from their high horse......
If you look through my posts you'll see i don't help people for the thanks, and most of the thanks i have came from helping people to solve their problems but its all irrelavant. I don't care if anyone clicks the button or not, i get enough satisfaction knowing i helped to make their phones better. Until 2 weeks ago i was using a wildfire and still have one but obviously dont use it as my daily phone anymore so who are you to tell me to leave these forums? I also never implied you are ignorant you're doing a fine job of proving that yourself. Like i said before you chose to mess with your phone so don't complain to us, if you'd like help all you have to do is ask. The problems with wifi,gps and most likely bluetooth are NOT cm related its a problem in our radios which can only be solved by reflashing the radio or with the sense method. Flashing a radio probably isn't working correctly for you if you're using any other method than fastboot if it isn't fixing your problem. The agps patch is not cm related or made by them so why would they include it in their rom?
All that said i don't think flashing a rom will solve your problem and as i said in my brief message if an ruu doesn't solve it then its most likely a hardware problem i.e a loose connection or the digi has gone altogether.
Please do some research yourself and learn exactly what you're doing to your phone before you actually do it. You'll value the experience when you upgrade and learn there is a real possibility of bricking your phone completely by flashing something wrong.
Sent from my GT-I9100 using xda premium

As I've asked before, did you try flashing another ROM, or a previous version of CM, to see if the touchscreen problem is still there?
Also, Scratch is still an important part of our little community here, even though upgraded to an S2.

ooooooooooh i think im gonna have to get an s2 !!!!! slim os - sylm os

I think most "new" phones have SlimICS

Related

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?
Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..
Which ROM?
I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?
Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):
Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....
Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone
Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.
rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks
rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.
are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...
Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).
I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...
After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.
You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

[Q] Touchscreen stops working

Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5
When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!
First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...
I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.
ok, even if i hope to solve the problem by myself...
News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??
Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk
the whole phone?
Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
I wonder when it happens ,are you charging?
nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...

Sleep Of Death (SOD)

my HTC desire has suffered the worst SOD case in the past few days.
This morning I tried all possible troubleshooting and to my surprise after 3 days its working normal again.
I'm still unsure of what the issue was. Anybody else dealing with this?
andrd_ said:
I'm still unsure of what the issue was.
Click to expand...
Click to collapse
It will most likely remain that way until you at least provide which rom and kernel you use.
andrd_ said:
my HTC desire has suffered the worst SOD case in the past few days.
This morning I tried all possible troubleshooting and to my surprise after 3 days its working normal again.
I'm still unsure of what the issue was. Anybody else dealing with this?
Click to expand...
Click to collapse
Do you just wanna know who else is dealing with the same issue or expect to find a solution? You aint gonna get any solution if you don't even provide readers with your device info. Is it rooted? Is it on stock? Is it running sense? Is it running AOSP? Is it running those beta roms? Is it on froyo? Is it on gingerbread? Is it overclocked? Is it undervolted? Does if have an ext partition? etc etc yada yada yada,
Best way I've found to recover quickly from a sleep of death is to take out the battery and plug it into a charger. Wait a few seconds and you should see the LED indicator flash from orange to green. You can now out the battery back in a power up normally.
I've only had this issue with sandvolds ics. But I haven't tried the latest
my phone is rooted n s-off too.
SOD started when i was on sandvold's ics. So i did the most sensible thing, switched back to android 2.3.
I'm currently on GB from Cool Droid v3|2.3.4|. The problem with SOD followed me on this rom as well but i seemed to have solved it for now, thanks to all the troubleshooting methods in the forum. I'm really happy to see it working normal again.
andrd_ said:
The problem with SOD followed me on this rom as well but i seemed to have solved it for now, thanks to all the troubleshooting methods in the forum. I'm really happy to see it working normal again.
Click to expand...
Click to collapse
Care to share how you tried to fix it?
dvsk69 said:
Care to share how you tried to fix it?
Click to expand...
Click to collapse
The reasons for the problem can be countless. I guess my SD card was the culprit this time. previously, I had partitioned the card using gparted but on 4ext touch recovery the card's partition alignment check said I have some alignment issues with my fat32 partition.
I repartitioned the SD card, now I have 1gb ext4 partition n around 14gb of fat32, perfectly aligned.
I thought I had solved the problem.
Then I came across someone saying that it could be the radio too. I am using the latest version of radio for some time now but I decided to switch to some previous versions and see if that helps. Installation got aborted, may be because I wasn't connected to the pc. But this time when I booted up my phone, no more SOD so far.
I would like to add that I probably just got lucky. I'm using a fake Chinese battery on this phone. Lost the original one as it got drenched in the rain.
Please share if anyone else is dealing with this issue too. Would be glad to help you guys out.
dvsk69 said:
Care to share how you tried to fix it?
Click to expand...
Click to collapse
Also I'm not overclocking or underclocking the processor. Not using gps. it is also recommended to stay on 'gsm only' or 'cdma only' mode. So basically I tried all the troubleshooting options out there.

Help? Wifi issue :(

Hi.
For about two weeks ago my Wi-Fi signal and radio signal drop a lot. I don't know what caused it, it had been laying over the night and when I turmed the Wi-Fi on, the signal was terrible. Going from 2-3 bars to almost not conecting at all at the same spot. I am quite sure it is not the antenna hardware fault. In my opinion I have pressed the area I am described to press pretty hard. I have an unlocked bootloader.
I don't think it is any software related thing I have done because it was several days since I had flashed anything or installed any mod. I have removed some of the things I considerd unnecessary, such as live walpapers. As far as I know I haven't removed any important parts. After that I installed a stock ARHD 9.3.2 to check if that could help, after that I checked with several AOSP roms. Nothing worked as far as I know.
At that point I used ARHD 9.1.0
-I might have installed faux06b mainline (repacked)
-I had installed:
APM
EQM
Faster gps fix
supercharger
soundrecorder txt mod
Hope any of you bright heads can help me. In advance thanks.
By pressing you made it worse unfortunately.
Look here:
http://forum.xda-developers.com/showthread.php?t=1688538
Extensive thread about your issue and what to do in detail explained :good:
Well, the problem is that the signal was bad before I pressed to check if i had the hardeware fault. When the pressing didn't work, well as you said I guess it didn't help. If thwt would have been the problem it would be easier.
Sent from my HTC One X using Tapatalk 2
For the love of god/drugs/beer/etc. put a more descriptive title. Forum etiquette.
And yes by pressing you might have created the problem if it didn't exist. In my opinion, that whole pressing the antenna scene should be removed from that WiFi defect thread. I've messed up mine for the same reason, I tried checking for a problem that didn't exist and end up bending the antenna pins.
Sometimes people get weak wifi because of a weird flash of rom or kernel. I remember seeing posts in a JB rom thread where people were experiencing weak wifi, but you've knocked that off anyway since you tried different roms. I suggest relocking and giving it to HTC Service Center. Wait for more 'bright heads' to post though . Good Luck.
As I have tried to say, I had the problem before I pressed. But I installed AOSP to check if it made a difference. But thank you for the tip.
Sent from my HTC One X using Tapatalk 2
Any bright head got a clue? I would appreciate it a lot.

4.2.2: Bluetooth won't turn on

OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...

Categories

Resources