This problem just started for me and I have experienced nothing like it. I'm running the LG p930 with CM10.1.3 RC2. Yesterday, the phone began restarting whenever it tries playing a sound. This happens in Netflix/ Youtube once a video starts, Pandora when it attempts to start playing a song, even the sound panel when I use the volume rocker to try changing my volume and it attempts to play the little beep. It also happens no matter what speaker it tries using - headphones, speakerphone or earpiece, meaning I can't actually use the telephone functionality of the device either..
As far as fixing- I've tried clearing the cache and dalvik, fixing permissions, and even flashed several other ROMs. Everything seemed to have the same problem. Does anyone know what could be going on?
This exact thing happened to me. I couldn't find any information on it.
I had to completely format and un-brick the phone. I'm not even sure that it worked the first time. But after completely wiping and un-bricking a couple of times, it was back to normal. I think this is the guide that I have always used for that.
http://forum.xda-developers.com/showthread.php?t=1597488
Hope this works for you. I know that problem can really suck.
Thank you so much! I'll try this. I can't believe someone else had this issue, it seems incredibly rare. Can you tell me more about it? What ROM were you running? could you play any sounds at all?
Thanks again
I know what you mean. I was surprised to stumble across this post about it. I feel like I have had a few issues that just seemed very strange with this phone.
Mine was just like you described. I couldn't even change the volume without it crashing. If my phone was on vibrate, I could see the call come through. When I answered the call, the phone crashed.
I was probably on a PAC-ROM or CM10 Nightly. But like you, I probably went through every available ROM, stables and nightlies at that time. I think I even tried to flash a stock ROM.
Thank you so much. Actually, you don't have to follow the whole guide. All you need to do is download the image files, and skip to step 4 in the section "Restoring the original Nitro HD images:" Then get cwm working, and move on from there with whatever ROM you want. I would never have thought to try this. Thanks again.
Related
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
jedijackie said:
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
Click to expand...
Click to collapse
Well, you've tried everything I would've suggested...tried different kernels, flashed backed to sense, performed a full wipe, etc. I would think that flashing back to stock would've alleviated the issue if it was software related. Perhaps your speaker is starting to fail? I've seen many people reporting needing to replace the speaker. However, it is indeed odd that its intermittent, you'd think that if the speaker was failing, it'd be consistent, and a reboot wouldn't clear it up. Odd, but I don't know what else to suggest. Have you tried tweaking the settings using DSP manager at all? If all fails, and being on stock sense doesn't fix it, I'd unroot and have it looked at by Sprint probably.
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You definitely seemed to try just about everything but did you flash a Stock RUU? I'd nandroid backup and flash it to see if the problem still exists, if you've tried that then you would only have one option left, take it to BB. Best of luck either way.
Huh... haven't tried a Stock RUU. Good call! I'll try now and report back. Thanks Blake.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You're welcome, sorry there isn't more I can suggest. As Blake said, run RUU to unroot, which I would do before you take it in anyways. (What I meant when I said "unroot and take it in). If its still out of wack then, take it in.
Sent from my PC36100 using XDA App
I attached the Stock rooted RUU but visiting HERE should return you to unrooted stock evo.
Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App
i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?
This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App
moved to general
I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Had a similar experience
Headset being detected even when not connected seems to be a common bug on Gnex, have seen several posts and I myself had to go through this. It usually gets fixed by itself in a day or two.. but till then use the "toggleheadset2" from the play store, which would allow you to manually say when the headphone is connected or not.
--Vj
PhreeqQitsikk said:
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Click to expand...
Click to collapse
---------- Post added at 10:27 AM ---------- Previous post was at 10:17 AM ----------
Only permanent solution is to change the socket. Its the switch inside which usually gets jammed.
Same exact problem
I am having this same exact problem. Its fine on stock, once I flash CM10 calls say connected and the time starts ticking but I can't hear a thing and no one on the other end can hear me.
Sometimes when I do connect, the person will hear me for a couple seconds and then it'll drop then connect again then drop...over and over again.
Google now doesn't pick up any voice searches either.
HELP, this is a relatively new issue. (2-3 months old) I've had the nexus since January and had it rooted and rom'd shortly after. Only recently has this issue cropped up.
toggleheadset2 seems to work but it sucks that I even have to use it. Any devs out there have suggestions/input? I've looked all over for a resolution.
Please don't make me go back to stock....Please!
So this happens before but has always been able to resolve by restarting or reflashing the newest nightlies. However, this time no matter how many times i restart and reflash, it doesn't work.
Essentially my phone doesn't have sound, and all sound-related apps are acting strangely. I have found a similar case with same issues as mine but is a s4. link :http://android.stackexchange.com/questions/124501/no-audio-samsung-galaxy-s4
The poster mentioned he solved the issue by flashing a pack but I couldn't find the equivalent for g3. Can anyone help?
This should help :good: http://forum.xda-developers.com/lg-g3/help/lg-g3s-sound-cm13-whats-wrong-t3300246