I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?
Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.
Related
For some odd reason, my wife's phone will randomly lose sound output and input.
For instance, cannot make calls because no sound is heard through speaker and it seems the mic becomes non-functioning, therefore the person on the other line hears nothing.
I've noticed at the same time that no other sounds (system, media, key presses, etc.) can be heard as well.
If the phone is rebooted the problem is fixed. This problem occurs usually once or twice a day. Its running a nearly stock 2.1 w/ root (although no root apps used or installed), I have also tried a different custom rom and have the same issue.
Any ideas? (I have searched and read up on some things, but did not see a definitive answer)
** Working on a fix now **
DrewX2, I'm having the same exact problem. Thought I was crazy! So I have the Damageless 2.08.1 (Android 2.1) ROM installed, and I thought I was being punished for not using Sprint's official ROM image . But you say that your wife's phone exhibited this behavior in more than one setup? What do you mean by "nearly stock"? Maybe someone out there knows of a way to look or download the internal error logs on the Android platform so we can at least get some stack trace info? Thanks!
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
danaff37 said:
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This is the exact fix I installed. So far no problems, will report back in a day or two.
Also, for the earlier question, when I said nearly stock, I should have said I am using nfinitefx45's Stock Sprint Deoxed ROM.
Before taking the plunge I am looking for success/problem comments from those who have failed with OTA and then tried the JH7_OTA.zip approach.
I have searched and I don't see many comments yet.
It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.
Worked great for me. GPS is working like a champ too.
Thanks to all who worked so hard on the flash.
I updated with the JH7_OTA.zip and it went well, but my phone is worse than before... laggier, bottom buttons seem less responsive (could be due to the increased lag) and the GPS will not see any satellites and much less, lock. I'm sure it's not the file... just another defective unit. This is my fourth Captivate. First two simply lost the ability to connect to 3G and WIFI, the third had a great GPS but the search function would randomly self activate and the body creaked like an old rocking chair, and my current one.
bigdoug2005 said:
It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.
Click to expand...
Click to collapse
This happened to me. You don't need to pull the battery. Just hold the up volume button and power button for about 10 seconds and the phone will shut off.
Edit Disregard my post.
It's working great for me. I usually stream radio during the day and it usually will drop out once or twice an hour. Today, it has been streaming just perfectly with no dropouts. Thanks to all of those that got this working!!!!
No problems here, either. I did remove my previously installed LagFix first, and I flashed over JH3. GPS seems to track me a little better than before, and it does seem that perhaps the radio is working a bit better and battery life is slightly better as well.
I have the same commute on the train each morning, and pretty much do the same routine each time, so that's a good way for me to compare things after a change. This morning I noticed that my streaming radio barely cut out at all in areas where the signal is low, much less than before, and when I got into work my remaining battery PCT was a little better than usual. I applied the RyanZ lag fix from the market this afternoon and overall am pretty happy so far!
My GPS is still jacked up.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Worked great for me. everything working including the 3 button, usb, and better gps/compass. Things other people were complaining about not working. I flashed odin and rooted with update.zip before i applied this rom.
luck? Sure... but...
I went with the Cognition ROM as JH7_OTA didn't do the trick for me.. All in all I like the Cog experience (install went smoothly, seems fast, no weird errors), but the GPS is definitely not fixed. Accuracy is better in that my phone can locate me on the neighborhood level, but it is still not locking and is locating me blocks away from where I'm actually at.
Worked great for me.
No problems flashing for me. That is the answer to your question, now to issues I had.
HSUPA was not working for me. So I did the revert HSUPA to get 3G back and it killed all data for me. So I did a nandroid back to my previous ROM and then I got FC so I had to Odin and then reinstall my nandroid. That is why I don't like his zip, it works fine but if you want to change ROM's you have to basically flash odin to make sure you have no issues. That is how it was for me, others might be different and then you have the nut swingers who are only for Cognition.
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Last edit: Just went back to his Cognition thread and see that he pulled the HSUPA zip, so it wasn't just me having issues. Unfortunately stuff like that lets me know that all in one package zips like that need to be worked on more.
flashman2002 said:
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Click to expand...
Click to collapse
you probably should have removed the voodoo lagfix to try to flash other roms since clockwork DOES NOT work with voodoo
alternatively you can install cognition, and install a different kernel if you dont want voodoo lagfix...
flashed it and it's great! except the gps is kind of on and off.
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
Your search method must be flawed, as this is a known & frequently discussed issue.
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
It's defective. Get a new one.
Thanks for the reply.
Now to unroot...
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
When you get your hands on the new one, before you leave the store do this. After power on & such, try the audio (V0l + -). Works? Put to sleep for >10sec. Wake & test audio. No-work? Reboot, (Long power press) Try sleep/wake sequence again. If it works you are golden, now check a few other things & go home & root it! If it fails the test, don't let the Nook Genius tell you that you should let it charge for at least 4 hrs. before testing. The three that I have received had between 50% & 90% charge OOB. That's plenty for it to work properly, assuming the battery level meter is accurate. Put together your own checklist based on info on this forum. Crossword to test edges of screen, kbd. when charging from wall adapter etc.
Good luck, when you get a good one they are solid!
kev
trumpet444 said:
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Interesting! That would support the thinking that this issue is related to timing & initializing the audio codec or something related. Hardware specs may be skewed just enough for it to not work when waking up. That's actually encouraging! Means that all those with this problem may see a F/W fix if they don't want to re-clock it.
Cheers,
kev
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
timmyjoe42 said:
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
Click to expand...
Click to collapse
That's interesting. I had the audio/sleep problem with 1.0.0 & exchanged it for another 1.0.0 that worked fine. ?????
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
GaVLaR123 said:
Hi all im having to post here because i dont have permission to post in development thread.
I have been using cm9 for few days went from build 5 to 7 yesterday and i have an issue with both builds, after a while my sound just goes i cant hear phone calls youtube videos or games sounds. As far as i know all sound has gone even woth volumes turned right up. I have searched the forums and cant find anything on this issue, anybody else have it/know how to fix it. The only way i can get sound back is rebooting. Any helo much appreciated
Click to expand...
Click to collapse
was it working fine on Sammy's ROM?
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
GaVLaR123 said:
yes i have never had an issue until using cm9. i think the microphone stops working too. i think it maybe when i try using the spirit fm app would this make sense? im not going to try the app now and see if it happens again. i thought that app should work?
Click to expand...
Click to collapse
Well, i think that's not a hardware issue to be worried about & don't mess with unknown and bugged up apps .
Why not try a re-flash (wipe cache & factory reset ) of BUILD8 ? If that doesn't also solve the issue then try Odin re-flash back to 2.2/2.3 and then again CM7.1 [with a Modem flash] to CM9 ?
It happens a couple seconds after sound stops being emitted. I think it's the sound of the speakers being turned off. I had the same exact issue with my gnex but I'm pretty sure that it happened to most if not all gnex users.
Nothing like this happened until I updated my firmware to install a GPE 4.3 rom. I guess it could be the rom itself and not the firmware, but I've tried a couple different gpe roms.
I've ran both sense and aosp-based roms before this without said problem.
I've read that some people have had this issue since they bought their phones and it's a hardware defect. Since mine happened recently I feel like it's a different problem.
Any suggestions?
Sent from my HTC One using xda app-developers app
Are you sure you hadn't this problem since the first day? My speakers (and I asked three different people and they confirmed it) are popping from the beginning at the end of a sound, though the quality itself is very good. My HTC Desire and the HTC One X+ from my boyfriend are making the same noises, although they're not as loud as the One, because there's only one speaker on the back of the phone.
If it occurs now and never before there is hope that it'll be a software issue
Sent from my HTC One
I've actually noticed the exact same thing and it certainly started after updating my firmware to the latest Base 3.09. I had never noticed it before that. The weird thing is that it'll happen when my phone is on vibrate. And I think (not 100% sure) that it happened more than once when I navigated away from the text messaging app.
It's something I can live with but at least I'm not alone. I thought it may have been from installing the Noozxoide EIZO-rewire E application. I have since uninstalled it but who knows if it left any kind of remnants. I really won't know until I re-flash my Viper ROM and start from scratch.