So basically, I installed Foxhound ROM 1.4.1 (XXALE8) with Siyah kernel and from then I have had no sound on outgoing calls (from my mic) and no sound either way on incoming calls.
After reflashing, wiping, restoring Nandroids, flashing different ROMs and everything else I could think of. There was no fix apart from going back to Stock.
If i go back to the Stock ROM then sound works 100%. I can root and install a custom recovery (via gs3 tools) with no problem and audio works perfect. But as soon as i install a custom ROM it no longer works (even ROMs which i could previously install fine).
I would really really appreciate any help at all that people can give or if anyone else has this issue if they can post so we can try to find the cause of the problem. I have found a few mentions of this here and there on different ROM threads but by posting here someone more knowledgeable may see it and be able to post a resolution.
Any help would be massively appreciated!!
boarder.2k9 said:
So basically, I installed Foxhound ROM 1.4.1 (XXALE8) with Siyah kernel and from then I have had no sound on outgoing calls (from my mic) and no sound either way on incoming calls.
After reflashing, wiping, restoring Nandroids, flashing different ROMs and everything else I could think of. There was no fix apart from going back to Stock.
If i go back to the Stock ROM then sound works 100%. I can root and install a custom recovery (via gs3 tools) with no problem and audio works perfect. But as soon as i install a custom ROM it no longer works (even ROMs which i could previously install fine).
I would really really appreciate any help at all that people can give or if anyone else has this issue if they can post so we can try to find the cause of the problem. I have found a few mentions of this here and there on different ROM threads but by posting here someone more knowledgeable may see it and be able to post a resolution.
Any help would be massively appreciated!!
Click to expand...
Click to collapse
I have the same problem, however I was on stock when it happened. And it JUST happened for no reason after a call. Nothing helps. Really nothing. I've flashed custom, different stock roms, reset etc etc. The modem must be damaged some how as KIES says there is a software update available, I download and install it and then upon reboot it says the same again. The phone looks as if it's connecting but after 10-30 seconds it says out or range or similar and disconnects from the network for about 10 seconds and then reconnects.
Sometimes I can hear a crack sound for a second before it fails to connect a call.
Everything else works perfectly.
Are you on 3 UK by any chance? Apparently an ota with new modem was released yesterday that fixes it. Look in the foxhound thread (I'm just relaying what I've read, I know no more than that)
Good luck guys
Sent from my GT-I9300 using xda app-developers app
bump.
someone managed to fix this?
anyone figure is one out yet?
Hi guys
i have galaxy S3 with the same problem when you try or make a call there is no sound even if you will used the speaker headset there is no sound and when i end the call the signal bar becomes circle void but it will came back again the signal. i try to make a software and reheat the audio ic and it is the same still no sound on call
iam live in ksa
i send it back to samsung to solve the problem and iam waitting for them
Same problem here, had no problems flashing different modems on Omega 27 until I moved from siyah kernel to Franco kernel. Now got no sound problem during call. Can get call sound back sometimes by playing wth clearing caches, fixing permissions etc. I do always get sound back by restoring nandroid. Drives me nuts! Wish I knew what causes it
Sent via TCP/IP
i am also having same problem
stock rom no modification
any solution ?
this video well describes : youtube.com/watch?v=fo46OXWEcX0
Problem with audio
MonsterMMORPG said:
i am also having same problem
stock rom no modification
any solution ?
this video well describes : youtube.com/watch?v=fo46OXWEcX0
Click to expand...
Click to collapse
Hi guys, i'm from Portugal, and i have installed omni rom 4.4.2 into my Samsung Galaxy S3 LTE ( GT-I9305). I installed properly using full wipe and cleaning the cache but, after a week using this rom, the sound into my device was death. Don't have sound into notifications, calls, even using headphones, don't have sound. Already reinstall the room making all the process again, but i have the same problem all the time. Someone can help me please?
Info:
Model : GT-I9305
Android Version: 4.4.2
Omni Version: 4.4.2-20140220-i9305-NIGHTLY
BaseBand Version: I9305XXBLL5
Kernel Version : 3.0.64-CM-g659c99f
[email protected] #1
Thu Feb 20 02:07:18 CET 2014
Compilation number: omni_i9305-userbug 4.4.2 KVT49L 149 test-keys
Thnks for the assist
Related
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
citronbitare said:
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
Click to expand...
Click to collapse
Really nobody who could help???
Can you record sound with other apps?
That should see if its a problem with just the phone apk or a more native problem.
Sent from my GT-I9300 using xda premium
Well, others can hear me but I can't hear them in phone calls. There is no problem with the phone speaker, because I can use viber without problems.
*** via Tapatalk ***
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Well, it shouldn't be hardware related, because there is no problem on unmodified stock firmware.
*** via Tapatalk ***
Zabalba said:
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Click to expand...
Click to collapse
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
JJEgan said:
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
marcinrek21 said:
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Click to expand...
Click to collapse
Yes, it all started after flashing syiah 1.2.6. So maybe it's not a coincidence after all.
*** via Tapatalk ***
Zabalba said:
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
Click to expand...
Click to collapse
For me it has also been an intermittent problem. Kernel changes, modem changes, wipes, etc often temporarily helped - but only for one boot cycle. A reboot always brought the problem back. Only on stock firmware I can always hear.
*** via Tapatalk ***
marcinrek21 said:
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
Click to expand...
Click to collapse
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
citronbitare said:
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
Click to expand...
Click to collapse
And may you have an earlier backup? Stock with cfroot or similar?
marcinrek21 said:
And may you have an earlier backup? Stock with cfroot or similar?
Click to expand...
Click to collapse
The sound problem is there even when I restore earlier backups. Now I am on stock firmware and everything is okay.
But I would like to use custom ROMs again with working phone call function, which is not possible for now.
*** via Tapatalk ***
This is the weirdest problem that I have seen here.
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
citronbitare said:
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
Click to expand...
Click to collapse
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Zabalba said:
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Click to expand...
Click to collapse
I'll keep my fingers crossed and hope that you have finally gotten rid of this problem. And thanks btw for asking Chainfire and Indie too look at this thread!
*** via Tapatalk ***
I got that problem myself, the only thing that really helped for me is to
flash my Stock Rom that where on the Phone out of the Box... since 2 Days
the Bug is gone. But havent tried any other Stock Rom.
I want to try Omega 6.0 Rom...(now)
I was thinking about flashing CF-Root and do those steps before custom:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
3. In Advanced ---> Format System/Cache/Data (someone tried this before?)
4. Flash the Rom.
My Question is for those guys like me where the only solution is to stay on
non rooted stock rom, have you tried flashing a custom rom with step 3. from above and still encounter the call issue?
I read somewhere that with step 3. the Phone is really FULL WIPE.
Sorry for my bad english :silly:
Good morning, I did the update my phone to android 4.3, everything worked, but when I call someone, the person does not hear me or hear and not what they say, that only the calls, if I use Recorder application voice recording correctly, just does not work during calls the phone and microphone, already tested several roms, I'm back to official through Odin, and all gave the same problem like your help, thank you!
Did you do a factory reset after the update and ROM flashes?
Sent from CM 10.2 optimized sph-l710
I've done it and it did not, I do not know what else to do, is there a sound driver or some fix? I'm out of options, I've tried everything: (
Did you flash a 9100 4.3 rom, or one from our development thread? Regardless, sounds like a simple mic swap issue; flash AJK 4.9 AOSP and it should fix your problem.
Sent from the i777
SOLVED
I managed to fix, I downloaded a rom (I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5) installed by Odin and the sound of the calls started again, then installed the recovery and put the rom 4.3 downloaded right here, thank you so, if someone is having the same problem, I do upload the rom and post here, thanks!
wendelldjmixer said:
I've done it and it did not, I do not know what else to do, is there a sound driver or some fix? I'm out of options, I've tried everything: (
Click to expand...
Click to collapse
Sorry typing is wrong, it's because I'm from Brazil and I'm using the google translator, here is the link of the rom in my worked, install by Odin, after installation, test call, if it works, just install the recovery, and put the rom you want, post your answer here if it worked or not, below is the link rom, extract the file and install by Odin, thanks
http : // www . hotfile . com / dl / 160521955 / 8de1076 / I777UCLE5_I777ATTLE5_ATT .zip. html
(Remove the spaces from the link)
im helping my wife. and i got the problem described below.
When making or receiving phone calls from my
s3 some strange noise starts happening and
won’t stop, resulting in me or the person I am
talking to having to hang up an make the call
again. I have tried new modem. resetting back to stock. flashed new build. reinstalling the
operating system from the built in function and am still experiencing the problem.
If you've already factory reset and flashed a fresh stock 4.1.2 rom for your country then it can only be a hardware fault.
Maybe worth trying a mega wipe script first?
boomboomer said:
If you've already factory reset and flashed a fresh stock 4.1.2 rom for your country then it can only be a hardware fault.
Maybe worth trying a mega wipe script first?
Click to expand...
Click to collapse
already done that. viber and skype works perfect. and also the built in internet call service.
so i think it must be something else like operator(3 sweden) or something as i didnt have this issue a year ago. it started with the lastest update.
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Noypi14 said:
Hi. I've got a challenge for the experts
I have a galaxy s4 (i9505) and currently on cyanogenmod 11-20140414-nightly so its running on 4.4.2
The minute i got my phone, i put foxhound rom and was on4.2.2 that time and everything was fine. It was about june last year. A couple of weeks ago, i decided to have a go at other roms or update to 4.4.2 so i tried foxhound rom that ran on4.4.2. This is when the problems started. The first problem was the signal was greatly affected that i could not get any signal indoors. So i tried several other roms like omega rom, cyanogenmod, wanamlite, wicked, virgin rom and several others but none of them perfectly worked. I always cleared cache and restore factory settings but still there were problems. On some roms the camera wont work as if there is another app using it. On others, i cant get any signal even though im in an area where i used to get strong signals. Another big problem is that i cant make a call! The screen goes black and can't do anything until the call gets disconnected. I can't use voice services like skype, ym, everything that uses the mic as if there is an app or service using it. When i put the jack to use the headset, i dont get the notification that im on headset unlike before.
So i decided to use stock rom on 4.3. Now i have even bigger problems. In addition to the previous problems stated, the wifi won't turn on but i can get a signal outside. Even though i have already removed the microsd card and wiped cache and restore to factory settings, the phone still says that the device was modified so i can't really return it even though it is still under warranty.
So now i decided to root it again and temporarily use cyanogenmod since the wifi works, texts and the internet works.
Btw, youtube doesnt work also. It doesnt play.
Sorry for the vrry long post but i just want to give much info as possible..
Thanks so much
Click to expand...
Click to collapse
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
es0tericcha0s said:
So, which type of rom do you want to be on, assuming most of the things work properly? I don't want to try to address all those issues because there are different ones for the different setups and would take forever. Most likely signal issues are from not using a matched modem with the firmware / rom you are running. Do you know the original carrier / region the phone is from so we can make sure you get the right stuff installed?
Please provide details on the the currently installed baseband version. Also, what is the last official version of Samsung's software that you installed via Odin or OTA (not via custom rom)?
Click to expand...
Click to collapse
Thanks for your reply.
The current cyanogenmod is fine although i prefer the virgin rom. but i can go back to virgin once the problems have been rectified.
I agree that the signal issue has something to do with the modem so i tried different modems using odin but the XXUBMEA wouldnt change despite trying several modems and several times.
The phone is on three network (uk) with its current baseband 19505XXUBMEA.
The official rom i tried was on 4.3 and kies said it was the latest
Thanks again
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
es0tericcha0s said:
Alright, I'm with ya so far. I'll look into the rom situation when I get back in front of the PC, but the trick with updating the modem is you gotta flash it twice in a row before you reboot unless you flash official firmware.
Click to expand...
Click to collapse
Thanks again for replying.
What i havent actually tried (which i'm reading at the moment) is the formatting of data under the advanced options on twrp. I dunno if it will make a difference say i try a new rom. I don't mind trying and starting from scratch. Like format data then install a new rom. Do u think this will make a difference? (will this be similar to formatting a dard drive on a pc before installing windows?)
What i suspect is there is nothing wrong with the roms i've tried but something in the installation got messed up and remains there even after wiping the data.
I think i have tried doing it twice only to find out that it didnt change the modem despite odin saying pass.
Should i format data then install a fresh rom?
Hard
but challeng refused
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
es0tericcha0s said:
Ok, so there is something odd here. If you had flashed the official 4.3 via Odin, your modem would have changed to a newer one. The one you have is still a 4.2.2 one. Or were you referring to the last stock rom that you loaded with a custom recovery? Also, which recovery are you using?
Try this modem via Odin:
http://d-h.st/Kwv
Install Guide:
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Reference thread: http://forum.xda-developers.com/showthread.php?t=2192025
Let's see if that doesn't help anything and go from there.
If you have issues with wifi, there is a wifi fix to be had in the reference thread. Remember to flash that through the Phone slot if needed.
Click to expand...
Click to collapse
Noypi14 said:
thanks again.
i can't exactly remember what modem i had when i flashed it with the official 4.3 using odin. but my guess would be the XXUBMEA. most of the custom roms i've tried had this modem anyway. some had no problems with 3g signal.
i am using twrp.
i don't want to play around with the modem yet as the 3g and wifi signals are working fine on cyanogenmod. its the call and video that's not working that i want to sort out.
do u think if i reflash by formatting data would clear out the problems i specified earlier? i don't mind trying this if u think it will make a difference.. tthanks.
Click to expand...
Click to collapse
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
es0tericcha0s said:
The custom roms you've been using don't install a modem with them, so that would be why you've been on the same one for a bit. Often times the stock rom is a little more picky about which modem it likes best, though this varies by phone and update. What call issues are you having? There were so many issues listed for various things on the first post that I had trouble sorting which problem for which rom (not criticizing, just making sure we're on the same page). And as far as videos go, is it just YouTube that isn't working right or any type of video playback? If it is just YouTube - is it force closing, not loading searches or videos, or some other problem?
Click to expand...
Click to collapse
thanks again for your interest.
the issue about the modem is somehow clear. thanks for clearing that up.
i think it is better to tackle the problems i have in my current setup rather than the previous problems. so, as previously mentioned, i am on cyanogenmod 11 (on 4.4.2). here are some of the problems i am aware of or rather, those that i have experienced:
1. calls - whenever i dial a number, the screen goes black as if the phone is next to my ear (could there be something wrong with the proximity sensor? i haven't done anything to rectify this yet though. when this happens, i can't do anything as the seems to hang although i could see the call timer working. during that call however, i can't hear a sound nor the person i just rang. same thing happens when someone calls me. my phone vibrates (because there is another problem with the sound which i will discuss next) and when i answer it, i hear no sound and the screen goes black and i couldn't do anything with the phone. i have to wait till the caller disconnects before the phone becomes useable again.
i tried calling using viber and the same thing happens.
2. sound - phone is muted even though all the volume controls are midway or almost 100%. i tried changing the ringing tone but i don't hear any sound at all. normally, when i switch to a different ringtone, it should give me a preview of what the chosen sound is like.
3. videos - it doesn't work. when i go to youtube, it opens up the site, opens the selected youtube clip, tries to play it but pauses then tries to play again then pauses until i get a message saying "there was a problem while playing. touch to retry."
so far these are the problems i have faced.
sorry for the long post again.
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
es0tericcha0s said:
Hmm. Seems weird that you are having so many issues that most others aren't having, at least not since some of the earlier builds. During the install of CM, did you wipe /system? If not, I definitely would just start fresh. Install the most up to date modem. Wipe everything (system, data, cache, dalvik). Use the most up to date CWM (I like TWRP most of the time, but since CM says you should try CWM before reporting issues, it's one of those things...) Some Samsung proximity sensors aren't that accurate and really don't work well with CM. Other users reported that issue i the main CM thread for your phone, but was definitely not prevalent. I had a Samsung phone that I couldn't use a tempered glass screen protector with as they had an app to install to test to see how sensitive it was and mine didn't pass the test, though it worked for everything else.
As far as the video bug. It affected some earlier builds and other roms based off of CM but I hadn't seen anyone commenting about it for a bit so can't imagine it still being a common issue as that's a deal breaker for most. It might just be easier at this stage to either go back to stable CM 10.2 or try another rom altogether, such as Slim.
Click to expand...
Click to collapse
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Noypi14 said:
i know. i don't really want to blame these issues i've mentioned to the rom i am using or have tried. perhaps there was something i did not do or overdid that messed it all up. the cynagenmod 10 (the stable version for my s4 model) had similar issues as the cm11. so i suspect the problem i've created still lingers within my phone that messes up a lot of things.
during installation, i did wipe the system, data, cache and dalvik which i found in the advanced menu.
the thing is, everything else worked fine when i was on 4.2.2 (like the proximity sensors, videos, sounds, etc) so as i said earlier, i don't want to blame it on the roms.
i might have another go on the slim rom tonight but use CWM instead of TWRP.
thanks again for your interest and help
Click to expand...
Click to collapse
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
es0tericcha0s said:
Do you have a screen protector or anything like that? Sometimes if it isn't laying on the screen right or dirt gets around it, it can cause issues. There's also a way to pop out the actual proximity sensor and clean between the part and the little piece of clear glass on the back of the front piece of glass that can help too if it ends up being hardware related.
Click to expand...
Click to collapse
I put the screen protector when i got the phone and i don't see any visible dirt so i wouldn't want to blame it either. Although i did read about the screen protectors causing problems. But the thing is, even youtube or any videos do not play. Even any sound.
I've tried the slimkat rom by following the developers' instructions and still no youtube, no sound, can't make a call as i can't hear the person i'm calling nor can that person hear me.
Any other suggestions on what to do? I don't mind going back to stock as long as i get all the features back. I went to official 4.3 before but had more severe issues. Or perhaps i did it wrong?
Thanks..
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
es0tericcha0s said:
Videos are another issue, but I still think the call problems and such are modem related. What I would do would be to wipe everything, then use Odin to install official Kit Kat, then test this stuff out and see if it works. If so, then you can do a nandroid and redo recovery and try the roms again, then if they still have that issue then your phone just doesn't cooperate with CM roms or something weird like that. If it doesn't work even after official 4.4.2, then there's probably something else going on, possibly hardware related.
Click to expand...
Click to collapse
Thanks.
Got hold of the official 4.4.2 and flashed it via odin. Failed. But tried again and now working fine. Sound is back, video is back as well as calls. Just the annoying google search failing all the time.
The baseband it has is I9505XXUFNC9. i didn't install any modem in odin though. Just flashed in the pda section the tar file
Now i don't know whether to root this again and try custom roms or leave it as it is. I saw knox by the way but haven't installed it. Or is it pre installed? I have little knowledge about knox
I've searched and can't find anything similar with this phone.
Problem started randomly and occurs randomly. Sometimes, when I make or receive a call, I will get no sound whatsoever. Not through the earpiece, speakerphone won't do it, never have connected a bluetooth etc. Also, when it happens, I can't get the phone to "hang up" either. It's like the phone call is stuck. It happened when the phone was on Gingerbread, but I upgraded to 4.0.4 and it still does the same thing. No custom roms or anything, but I wouldn't be opposed to it as a fix. Is it a hardware thing? Help!
check the modem ICS is UCLF6 its correct ?
ddrface said:
check the modem ICS is UCLF6 its correct ?
Click to expand...
Click to collapse
Correct. I got bored last night and tried Beanstalk 4.3 and it has the same issue, but it also says the modem is the same... It currently reports i717uclf6
you made a full wipes before install some rom ? wipes everything x2 or x3 and install i´m using the hybrid RCVII is ICS very stable and smoothess !!