I'm pretty sure I saw this discussed somewhere but ... My TP2 is making a very annoying buzzing noise from the speaker, or from what ever is plugged into the ext2 connector.
It does it almost all the time and it's getting worse.
This is the stock ROM.
Is this a known problem or is there a fix?
That almost sounds like a hardware problem...
I guess for fun, have you tried doing a hard reset? Basically reflashing the stock ROM if you will. Obviously this will cause you to lose everything, so backup anything important.
I assume you rebooted, but you really didn't detail what you've tried (if anything).
arrrghhh said:
That almost sounds like a hardware problem...
I guess for fun, have you tried doing a hard reset? Basically reflashing the stock ROM if you will. Obviously this will cause you to lose everything, so backup anything important.
Click to expand...
Click to collapse
I'm trying to stay away from a Hard Reset - for now, I've got a Tilt/2 coming this week, so that way I'll be able to get that working BEFORE I do that and give this to the wife.
arrrghhh said:
I assume you rebooted, but you really didn't detail what you've tried (if anything).
Click to expand...
Click to collapse
Yeah,I did miss a lot; rebooted several times, have noticed that if I play a mp3 it will slowly go away - as opposed to streaming via data connection. Both Coreplayer and TCPMP cause the problem, in fact when I boot, not doing anything it's there.
It's getting worse, so short of a hard reset, I'm just trying to see if it could be anything else.
I do believe you're right though - it being hardware - as it's there with Froyo 7.x.
It's actually getting worse.
------------------------------------
It's coming from the data connection. When on, it buzzes, when off, not. Using WiFi and it's fine.
Related
Hi all,
I have a 2011 335xi w/ iDrive that I paired my Sprint/HTC Evo 4G to (running Android 2.2 w/ latest patches). My phone connects fine and transfers contacts and all but randomly during calls will disconnect and the sound goes back to the phone. In order to get it back working, I have to turn off and on my bluetooth a couple times (on the phone) then go back into the telephone screen, try connecting a couple times and eventually it works. It's so frustrating as this can happen like 3 or 4 times during a one hour drive and seems like more of a distraction to me as the driver than a way to avoid distractions (not so hands free when I am switching on/off bt). Any ideas? Thanks.
WE GOT IT!!! YOU OWN A BMW!!! JEEEEEZZZ
(just wanted to do that... have no idea what your issue is... cause I drive a Ford)
reedsw said:
WE GOT IT!!! YOU OWN A BMW!!! JEEEEEZZZ
(just wanted to do that... have no idea what your issue is... cause I drive a Ford)
Click to expand...
Click to collapse
Lol, I only mentioned the car model and year because people familiar with BMW would want to know that since the iDrive gets updated all the time. I have a September 2010 build too if anyone wants to know (so fall update is included...guessing the issue isn't on the car's end).
Haha... I know dood. Like I said... just wanted to do that.
reedsw said:
Haha... I know dood. Like I said... just wanted to do that.
Click to expand...
Click to collapse
yup, all good
Got the same issue here with 2011 328. I've read on some other forums people are having these BT issues with other vehicles and various ROMs. I have not been able to find a solution yet.
http://forum.androidcentral.com/htc-evo-4g/17083-evo-bluetooth-issue.html
6uPMAH said:
Got the same issue here with 2011 328. I've read on some other forums people are having these BT issues with other vehicles and various ROMs. I have not been able to find a solution yet.
http://forum.androidcentral.com/htc-evo-4g/17083-evo-bluetooth-issue.html
Click to expand...
Click to collapse
I def know I never had wifi on, which seems to be the most common response on that thread. I haven't tried to hard reset yet, no time to reload all my apps and such (although contacts just sync). If you do figure it out, let me know. Things went well after the recent update to the stock rom, but now they are worse than ever...its not even really connecting, and I've tried completely removing and re-pairing the phone, changing the phone name, turning bluetooth audio off and just keeping phone connection, etc, idk what else to do, very frustrating phone.
Did you try to use the phone without ANY of your apps, bone stock? My friend had a similiar problem in an 11' S4 and we finally figured that the problem was with one of his apps, he tried goin stock and it would be fine, but when he restored all his apps using TB it would do the same. The last thing i could think about is that the BT is somehow going in to sleep mode, try having the power plugged in in the car if you haven't done so already.
lacrossev said:
Did you try to use the phone without ANY of your apps, bone stock? My friend had a similiar problem in an 11' S4 and we finally figured that the problem was with one of his apps, he tried goin stock and it would be fine, but when he restored all his apps using TB it would do the same. The last thing i could think about is that the BT is somehow going in to sleep mode, try having the power plugged in in the car if you haven't done so already.
Click to expand...
Click to collapse
Hey, I haven't had much time to hard reset my phone and reload things, but that may be my last resort. Do you know by any chance which App was causing the problems for your friend? I tried using the phone plugged in but no luck either.
This is my first time posting. I know how annoying reposts are, so I tried to find if anyone else had the same problems I have. Unable to find an answer, I seek a solution to my strange problem...
I flashed CM7 three days ago. Before flashing, I did a full factory reset, wiped cache, etc. I also performed a backup of rom, which was at the time CM6. Everything worked without a hitch for these past three days. I installed new programs, really enjoyed the new features. However, today, the screen suddenly became unresponsive.
It acts as though I am long-pressing something when I am not. It will not register even hard taps and when I try to hit the home key it brings up the most recent apps list as though I long-pressed. I have reset, but it keeps doing this. When I try to use an app where scrolling is required, it bounces back to the spot I started scrolling. Very frustrating. Any solutions?
At first I thought it was from installing swype beta, but after removing it completely, resetting, and reflashing, the screen continues to act up.
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hey thanks for your suggestion. I've tried it but the screen problem continues. I even tried going back to the stock rom. Do you think it's a hardware issue?
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
magus57 said:
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
Click to expand...
Click to collapse
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
wronskishin said:
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
Click to expand...
Click to collapse
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
magus57 said:
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
Click to expand...
Click to collapse
How do you change the screen density?
Hey everyone,
I'm currently running the latest Jackos and I believe everyone was fine with the speaker you hold to your ear in conversation until about 2 weeks ago. Maybe a week or so after I installed the newest Jackos. Now I can't hear anything on it, but the microphone works fine. Speakerphone works fine, and my bluetooth earpiece works fine. I've searched for help on this and can't find anything to fix this problem.
The other problem is right when I boot the phone, instead of getting the black screen with the red diagnostic text, I get a white screen with colored speckles all over the screen. The speckles don't move at all and if I let it sit for 20 seconds or so, it will then show the HTC logo on black and continue booting. I can't get into the bootloader, I can't hard reset the phone, etc. Any ideas how to fix this? I haven't tried flashing the same/another ROM yet, but I don't know if that's even possible with this snow screen problem.
I've run Task29 and all the usual stuff every time I've flashed and I have never seen this happen until a couple of weeks ago. It does it NEARLY every time I soft reset or shutdown and boot or pull the battery and boot. The battery charges fine and it runs fine otherwise.
The screen will get random glitches in it, even when the battery is full and it makes me suspect maybe the battery's going bad but it'll run all day without problems and it doesn't get warmer than usual or anything like that.
Also, sometimes it says there's no SIM inserted and I've pulled it out, the contacts are nice and gold and nothing seems wrong.
Any ideas?
My sig is out of date but I have to head out right now and can't switch it yet, but it's the latest Jackos with 6.5.
Thanks,
Eric
I would flash a different/stock ROM and see if anything changes.
If no, hardware problem. If yes, software problem .
You seem to think you cannot, but AFAIK if you can task29, you can flash a ROM. Either way, putting an nbh on the SD card and doing power+vol up+reset should work regardless, unless the device is really bricked - in which case it wouldn't be booting.
Okay thanks, I'll see what I can do with it.. It does boot fine, though for a week I thought it was bricked because of the snow, but I decided to just let it sit for a week and gave it a shot, and poof! no snow on the first boot. It had the regular red text on black. Then I reset it from the slide to reset menu item and it went to snow again. I let it sit there and about the duration that it would be on the diagnostic screen, it was snow, then magically showed me the HTC logo and booted normally.
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Thanks again,
Eric
shep2112 said:
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Click to expand...
Click to collapse
Flash stock, it re-flashes everything... Make sure it works, then flash back to Jacko's.
shep2112 said:
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
Click to expand...
Click to collapse
This is what we're trying to troubleshoot .
shep2112 said:
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Click to expand...
Click to collapse
Talk about loaded questions! I haven't found anything that's appealing with a hardware keyboard yet... The supposed TP3 (on Sprint it's the "Arrive"...) was a real disappointment.
MT4GS looks decent, if you can live with tmo...
Thanks for your replies, I'm going to try to flash to stock in a little while and see how that goes.
The new Glide phone that AT&T has sounded promising until I read a review of it. Slow camera, 480x800 on a larger screen, etc. It didn't seem as cool as I had hoped it would be after that.
I'll write back with my progress or lack thereof with this TP2.
Eric
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
shep2112 said:
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
Click to expand...
Click to collapse
The stock ROM should've come with a radio as well...
task29 & flash stock? Otherwise perhaps you have a hardware problem... I don't know what to make of this snow .
The earpiece/loudspeaker thing isn't fixed either. I'll try a Task29 tomorrow or tonight if I can't sleep (thinking about this stupid phone! ) and then flash this ROM again and see what happens and let you know.
Thanks again
Well, gone and searched through the threads, and I'm not sure if people have been having the same issue or not but I made a quick video to detail this issues. I've had to restart the phone several times to stop this but it just comes back later and this sound interupts anything I do such as using the camera or listening to music.
Any help diagnosing this issue would be greatly appreciated, thanks.
That's really weird ! Never seen or better heard something like that. Are you on stock or custom ROM? Did this just start out of nothing or did you flash something before?
I would do a wipe and start from scratch.
Sent from my HTC One X using XDA
Yeah completely stock, not done anything at all to it.
Another weird thing about it, it only seems to happen when the phone is laid flat and happens more often when plugged into the computer but set to charge only.
try running some tests on the phone. there is a way to access the test features but i cant remember on which thread it was to access it. or may be try recalibrate features on the phone?
I figured out what the problem was, you'll probably laugh. It's NFC!
I had my phone resting ontop of a library book and they have those RFID tags in them so you can't steal them, so when I rested my phone ontop of the book, it would start making that noise, probably a "connected" sound.
Turned NFC off or moved my phone away from the book, problem gone!
I've had my HOX for about 4 months now, working like a charm, and doing what they say its supposed to do.. Now however, it has changed to an unusable brick..
I Rooted my phone about a month ago, and ran with a near stock ROM (I can't really remember what it is anymore), and about a week ago, I upgraded to the latest patches. The phone now has its own life, where it seemes like picture it tries to show, is distorted, unreadable, sometimes one of the three primary colors goes missing and it looks like it refreshes a small portion of the screen every second. The touch system still works fine, and if I could work it blind, it wouldnt be a problem.. I can get to recovery/fastboot without any problem, and if I reboot the phone, it works like it should from 10 seconds-1 hour. I've tried to restore to defaults, tried the Viper ROM, but nothing seemes to work. Also, if I lock the phone while it is doing the bug, I get the "dark screen" bug as well..
I suspect it must have something to do with the update, since the phone have been handled with great care, and not dropped on the floor/pressed hard on the screen. I'm now turning to you guys, since you know pretty much about this phone. I can take a picture with another phone to illustrate what its doing, if that helps, or my explenation is a bit vague.
so you actually tried to get the phone right back to stock? flashing a RUU?
matt95 said:
so you actually tried to get the phone right back to stock? flashing a RUU?
Click to expand...
Click to collapse
Yes, I tried that as well, but it didn't work as far as I could tell. It would last longer before it started to bug out, but it would happen still..
hmmm, well it could also be a HW issue...
matt95 said:
hmmm, well it could also be a HW issue...
Click to expand...
Click to collapse
It might be, but it would be so strange that it first came right after an update.. Might be some overheating that have caused bad connectivity on a lead, can be some plug that isnt right, but I have a sneaking suspicion that the update did this..
well if even the RUU didn't solve this then it could only be HW related... just one question, how could you run a RUU if there ins' any RUU for the latest update yet?