OK so my gf n5 had issues on the ROM which was a lolipop ROM so we flashed stock image of 4.4.4 because it was the only one I knew would unpack correctly to flash... She has taken all the ota's and is now on 6.0.1 thru all the versions the issue is this: on regular call she cannot hear me, but if its placed with speakerphone or Bluetooth it works... Without nothing... I have even done a factory reset after all updates... No dice.... Any advice other than returning it(not possible) are welcome.... Thanks
Related
Hello I have a strange problem on my nexus s.
When I make a call all work fine but when I make a new call the microphone and the speaker didn't working.
And then when I reboot the phone all fix and after a one call all back.
I try to do full wipe and install CM rom and still the problem is here.
Maybe someone can help me with that?
Thanks!
UNiQQ said:
Hello I have a strange problem on my nexus s.
When I make a call all work fine but when I make a new call the microphone and the speaker didn't working.
And then when I reboot the phone all fix and after a one call all back.
I try to do full wipe and install CM rom and still the problem is here.
Maybe someone can help me with that?
Thanks!
Click to expand...
Click to collapse
I have the same problem. Did you fix that? I used CM10.2, CM11, and 4.4 AOSP not official rom. But nothing helps.
Try booting into safe mode and see if what happens.
Try this thread as reference: http://forum.xda-developers.com/showthread.php?t=1319871
Still nothing(
monahxxx said:
Still nothing(
Click to expand...
Click to collapse
Clueless like you now ;(
Same problem with me
I have the same Problem with my phone .
Reboot fixes everything but then after one or two calls i cant hear anything at all .
I tried flashing many roms even the official rom
Did u find any solution ??
even with safe mode i have the same issue
It is a OS issue since the mic is working fine in Skype or other similar apps.
Google couldn't find a solution for it yet... https://productforums.google.com/forum/#!topic/nexus/2eVRjUXPS-A
UNiQQ said:
Hello I have a strange problem on my nexus s.
When I make a call all work fine but when I make a new call the microphone and the speaker didn't working.
And then when I reboot the phone all fix and after a one call all back.
I try to do full wipe and install CM rom and still the problem is here.
Maybe someone can help me with that?
Thanks!
Click to expand...
Click to collapse
In my case Nexus S (from AT&T - 9020A) KitKat (4.1.2) I had to overwrite radio driver with Radio KD1 version
I have tried multiple versions from here:
http://forum.xda-developers.com/nexus-s/development/radio-guide-tweak-radio-jk1-jk8-kb1-kb2-t1116884
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
blkhrt13 said:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
Click to expand...
Click to collapse
Did you flash any audio mods or new firmware?
loonatik78 said:
Did you flash any audio mods or new firmware?
Click to expand...
Click to collapse
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
blkhrt13 said:
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
Click to expand...
Click to collapse
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
loonatik78 said:
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
Click to expand...
Click to collapse
Actually every single time I flash a new rom, I go into advanced wipe and wipe system, data, cache and dalvik cache 3 times. Every Time. But I flagged that new firmware and was rubbing digital high rom from the Verizon thread and did not have the music issue. I'm running fluent rom sense 7 from the Verizon thread now but have not tested the music yet But will update you guys in the morning. Thanks for all your replies
Hello everyone,
I was on Lollipop 5.1.1 Stock and not rooted then i decided to give rooting a shot. I downloaded Cataclysm and flashed successfully. everything was fine then i discovered that there is no Cellular Data connection. Rebooted and tried all possible things but didn't work. Finally gave up and flash Cyanogenmod 12. worked perfectly, nothing was wrong and cellular data was fine. After a while i wanted to come back to the clean stock lollipop so i downloaded and flashed Factory Image of Lollipop 5.1.1. Weirdly the Cellular Data doesn't work, i have no idea why or what may cause the problem. Please note that my Nexus 5 is from Amazon Germany. I doubt that there might be something wrong with the radio image ( meant for US models ?!! ) but i don't know really or have no clue what might be causing this !!!!
Any help is appreciated. Thanks in advance
FIXED
After spending 7 hours moving between different ROMs, i found out what was causing the problem of cellular data. The problem also exists after flashing stock image and Cataclysm. I noticed that on CM12 there was one option in the APN settings that was different from stock and Cataclysm. The MVNO type was set to None however in stock and Cataclysm it was IMSI. I don't know how or why would android change or decide that on its own and i also have no idea what does this option do. I guess that this may help many people who are suffering from the same issue ( also people who updated stock ran into same problem )
Don't know where you are but, every time that has happened to me a hands free activation fixed it.
Sent from my Nexus 5 using Tapatalk
I recently flashed the stock firmware in order to get the MM update but noticed that I didn't have any sound once inside a call. I tried reverting back to cm13 and even cm12 but I still have the same issue. This has never happened before, I'm thinking that it could have been caused by the stock firmware but I don't know. XT1540 1GB.