Hi all, I really hope you can help me with this...
I can't stand TouchWiz, so I very quickly replaced it with CM 10.1, which sort of works. However, I find it very annoying that it lacks stuff like PIE (yes I know I have hardware buttons, but I still would like a proper menu, and LTM is just not quite there). I therefore tried Paranoid Android (had no phone, camera worked very badly) and then I discovered ReVolt! I must say ReVolt is a marvellous rom - but with one, massive caveat: I loose sound in the phone app, and indeed the phone seems to go rather bonkers (fails to actually call etc). I did see this somewhat on CM too (failed to place calls - timed out and hung up), but with ReVolt it's consistent.
This is what I did: I reloaded my nandroid backup of stock, checked that the phone worked (it did). I then flashed June 15th (or 14th - it doesn't quite agree) nightly of ReVolt. No sound in phone (but it could call). No ringer sound (on outgoing), no sound either way during the calls. Call in does ring, and it can be answered, but there is just no sound. No errors shown, no nothing. Putting it on speaker, adding headphones - nothing works.
I reloaded the stock rom, then installed latest CM10.1 nightly, and phone works as expected.
Both run on the same baseband (I9505XXUAME2), and they are both based on CM. Any ideas (I'm not allowed to post in the ReVolt thread - I don't have enough posts yet it seems).
Any help is greatly appreciated.
/R
Related
I have been searching for an answer to this for two weeks with no success. I apologize in advance if the question has already been answered… I couldn't find it.
On Sprint's Hero, when setting up a headset (in my case the car radio BT adapter) one can enable both Phone and Media. Supposedly, this should allow a user to listen to tunes/podcasts/Sprint Nav and be able to use the phone when needed through the BT. Unfortunately, it doesn't work this way.
If I'm listening to something on the phone and wish to place a call, I will enter the contact and start the call. The phone responds by pausing the audio program I'm listening to as it should, but I get NO AUDIO from the phone! Nothing! The call is placed and the recipient hears nothing also!
Now; If I'm listening to something and a call comes in, again, as would be expected, the audio program gets paused and the phone rings through the BT. Unfortunately, there is no auto-answer in Android 1.5 (grrr!), so I reach over and press the Answer button. Lo and behold, it answers! but over the phone's speaker and mike instead of the BT!
They refused to accept that it was a problem with the phone at Sprint. Is this fixable? Can I look forward to it working in Android 2.1? Is there anyone else experiencing this problem?
As far as I have read/heard its a known issue that I think one of the roms here may have corrected. I will look around and see if I can find the thread, its been more than a month since I read it. Maybe MoDaCo but again, I will have to track it down.
EDIT:
Personally I wouldn't look towards anything in android 2.1, sprints release could be as far as 6 months away.
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Las_Vegas said:
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Click to expand...
Click to collapse
So maybe no one fixed lol
I recently installed CM 10.1 on a Defy+.
For some reason - if I call someone (or they call me) - they cannot hear me, and I cannot hear them. Even if I put on the loudspeaker I still cannot hear them.
Phone is working normal apart from that, speaker seems to work fine so not convinced it is a hardware issue.
Only happened after flashing the ROM. It *was* working for some time. Any ideas what could have caused this? From reading about CM on other phones, people recommend flashing different kernels. Any ideas which kernel to flash?
Thanks.
Ok looks like this is an issue with BlueTooth being on. I turned it off and it worked fine.
Seems to be an issue with all CM 10.x that I was unaware of. I flashed this ROM on my wifes Defy+ to improve the speed and reliabilty of her phone. Needless to say she is not happy.
Maybe I should have flashed 7.2??
sterankin said:
Ok looks like this is an issue with BlueTooth being on. I turned it off and it worked fine.
Seems to be an issue with all CM 10.x that I was unaware of. I flashed this ROM on my wifes Defy+ to improve the speed and reliabilty of her phone. Needless to say she is not happy.
Maybe I should have flashed 7.2??
Click to expand...
Click to collapse
I guess 7.2 is good and stable enough for a non power user. That bug is known and it's not yet fixed.
Like @hotdog125 said, it's a known bug, and happens sometimes even when bluetooth is not used at all. I never use bluetooth and it happens to me quite often; rebooting your phone fixes the problem.
Ok I'm not a complete newb but I can't figure this out and its been driving me nuts for over a week now...
SGH-1337M (Rogers)
Up until last week I'd been running the nightly builds of CyanogenMod and loving it, the phone was fast had lots of functionality then I did a nightly upgrade and my phone stopped working. Incoming calls would ring but when I picked up the call I couldn't hear the caller and they couldn't hear me. After much frustration I ended up flashing back to stock. This fixed the problem but the phone was useless as far as I was concerned for everything but making phone calls. It was laggy, I couldn't listen to music (it was staticy) and just generally full of all of the extraneous crud that Rogers seemed to think I should have on my phone. (I honestly couldn't suggest the phone to anyone who was going to run it as a stock device if this was how it came out of the box!)
Now On Sunday I decided to try again and after setting everything back to defaults I reloaded Cyanogen and at first it seemed that things were working properly... until last night. Again I got a call and when I answered it there was no audio.
I can't figure it out, I'm running the correct radio now after flashing to stock (I337MVLUAMG1) but I just can't seem to get it to work and stay working. Besides Cyanogen I'm only running two other "root" apps Fantastic audio installer and AdAway.
Any suggestions would be great, I just can't go back to stock on this phone...
Any ideas?
I think I have the problem figured out...
Seems like it was a combination of a bad build of CM and the "Fantastic Audio Installer"
Beware of compatibility issues with apps like this...
Boys suddenly I had this problem, there is no precedent and no operations strange that I made...
In practice, the audio system of my Nexus 4 (OS: Cyanogenmod 11 last nightly 14sept14) will not start: first when the screen was stuck giving audio feedback, now nothing. I do not feel even the incoming calls.
It is not a problem of speaker, if I play a song I can feel it ... the problem is only for the channel "audio system".
Identical problem as regards the vibration (problems manifested simultaneously apparently), only that in this case do not receive the vibration anywhere, even installing app apposite to vibrate.
I tryed to reboot the phone, I reinstalled (reflash) the latest nightly, I checked the settings, I changed the kernel (at the time of mixup was AK Kernel with Synapse, now that the CyanogenMod Kernel)...
What to do?!?!
Thank you all
dix93 said:
Boys suddenly I had this problem, there is no precedent and no operations strange that I made...
In practice, the audio system of my Nexus 4 (OS: Cyanogenmod 11 last nightly 14sept14) will not start: first when the screen was stuck giving audio feedback, now nothing. I do not feel even the incoming calls.
It is not a problem of speaker, if I play a song I can feel it ... the problem is only for the channel "audio system".
Identical problem as regards the vibration (problems manifested simultaneously apparently), only that in this case do not receive the vibration anywhere, even installing app apposite to vibrate.
I tryed to reboot the phone, I reinstalled (reflash) the latest nightly, I checked the settings, I changed the kernel (at the time of mixup was AK Kernel with Synapse, now that the CyanogenMod Kernel)...
What to do?!?!
Thank you all
Click to expand...
Click to collapse
Try changing the ROM completely, with a full wipe (after you backup of course). Does it still do it?
I was looking for a solution without dat loss...
If by tomorrow I don't find other solution, I will do as you say
dix93 said:
I was looking for a solution without dat loss...
If by tomorrow I don't find other solution, I will do as you say
Click to expand...
Click to collapse
There's no loss if you do a backup from recovery.
You just backup, then wipe and install a ROM.
And then, you just restore, and you would have lost nothing
Hello,
i've found some threads here with similar problems but they all were a result of wrong baseband used after a custom rom installation.
BUT i bought a i9505 with stock 4.4.2 TW rom UGNG8 (not rooted). At some point i noticed that the phone loses sound and mic completly. Sometimes can take a call but with no sound, neather can the caller hear me, no sound from music/video player and no system sounds eather(not even with headphones plugged in). Everything goes back to normal after a reboot.
I figured it was an outdated baseband so i rooted the device, updated the baseband to the latest (UGNK4) and installed CM12. But the problem is still here. At random times the device loses all sound and only a reboot fixes it
Haven't been able to reproduce the exact moment when it happen as it seem to be completly random (gets really anoying when i need to take an important call and there is no sound )
I could really use some help with this
Cheers,
H.
Rule of thumb: If it happens across multiple roms then it is most probably a hardware issue.
I'd suggest flashing the stock rom back and see if it helps.
Make sure it's the stock rom for the country where the phone was initially bought.
For instance: If the phone was bought from Germany but you're using it in England, it is still a German version of the S4 and therefor needs the German version.
GDReaper said:
snip
Click to expand...
Click to collapse
thanks for the reply, i will try the stock firmware, maybe i missed something in the process earlier, and post back the results.
cheers,
H.
Fixed!
ok, after a lot of trial and error i narrowed it down to a hardware issue. The headphone jack was the thing making all the problems. i tried cleaning it but it didnt help, so i removed it. Device works flawless now. Already ordered a new jack. :good:
So to anyone having a similar issue -replacing (or just removing) the headphone jack does the trick.
Cheers,
H.