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.
Related
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.
I have a serious problem.
I have HTC Evo 4G, My screen is getting dim (NOT BLANK), I cant see screen in bright sun, It's really dark.
But this happen only Sense based ROMs, but this doesn't happen with Cyanogen or MIUI.
I have tried many sense-based ROMS ( Infected, Runny, MikG, ICS,...etc).
With every Rom, I flashed it many times, sometimes with wipe everything. I though it's hardware problem why this doesn't happen with ASOP ROM. (I don't like Cyanogen, or MIUI... LOL), Also, I tried every setting related to brightness But the problem still.
I've read every thread, article about similar problem, but useless.
For additional info about my problem: after starting up my phone, Every thing is OK, but after screen off for first time the screen getting so dark.
(Only one workaround I found, Just set "Screen always on") I'm going to kill my Evo.
Please Help me, I'm getting Crazy.
Forgive my week English.
I'm not going anyway, I'll stay here, Refresh this page every 5 Seconds, till i get a solution.
Please help me.
menu-settings-display-turn off automatic brightness and turn brightness all the way up....?
Thank you for your replay.
Sorry I forget to tell you I tried this, I set brightness so high, but nothing happen.
beezy69 said:
menu-settings-display-turn off automatic brightness and turn brightness all the way up....?
Click to expand...
Click to collapse
Sorry I forget to tell you I tried this, I set brightness so high(100%), but nothing happen.
Please help me, I still waiting for replay
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard
-EViL-KoNCEPTz- said:
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard
Click to expand...
Click to collapse
sorry for double post, I thought the other place is better, and I really suffer from this proble.
It's Ok, the other post is enough.
http://forum.xda-developers.com/showthread.php?p=21324350#post21324350
Yea always remember to only post once and in the proper section or some ppl will flame you up and troll your thread ;-)
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
abubakr125 said:
Hello everyone,
Before people start asking me to search the forums, I have searched for months about this issue and I'm hoping that we'll finally get a proper answer from some kind devs who are willing to take time to really debug and trace this issue.
I got a Nexus 7 2013 a looong time ago, used it on pure stock, locked boot loader, no root, no recovery, nothing. All the way until KitKat and the issue was never resolved. Can't remember when it started but the rotation gets stuck just randomly throughout use and doesn't work anymore, sensors show no data as others have reported, etc. Reboot and voila it works again. Rinse and repeat.
So I tried unlocking and flashing CM11 M7 at last. Same thing.
The thing that drives me up the wall is how little attention the issue is being given. Google barely acknowledges it, and not a single hint in the XDA forums of where the issue originates. Kernel, ROM? It's obviously most likely fixable via software if a simple reboot can fix it... We just need someone to start debugging.
I'd appreciate it if anyone who has the same issue or info about it post it below
Thanks
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No ideas other than to suggest that you do an RMA with ASUS. I just looked and I pre-ordered mine through Best Buy and it shipped July 26 of last year so you might still have time left on the one year warranty.
Hey, I hope this topic is still alive. Mine has exactly same issue as yours. It all started after I re- clean flashed Mahdi ROM (I messed up some stuff so I had to do it). Ive tried clean flash again, but it doesn't work. I've also tried different settings and apps but nothing helped. The only thing I found working is turning on lockscreen blur. For some reason, it makes the rotation work for a bit longer.