Related
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
Seen lots of threads all over xda (and other forums) about having no sound during calls so decided to create a new thread which can hopefully sort this out.
My facts
* currently running Omega v27
* If I flash stock ROM or Omega v27, sound during call is fine.
* If I flash a different modem, sound is normally lost, despite clearing caches and fixing permissions.
* flashing a theme can lose call sound
* I can restore a known working nandroid backup and have no sound when it boots
* best way to get sound back is to flash siyah kernel then dli4 modem, then clear caches and fix permissions (although this doesn't always work)
* sometimes the only way to get audio during a call isto reflash
* changing a kernel often means sound is lost
* I never had this problem with ics or earlier versions
This is driving me nuts, anyone got any ideas about what is causing this or how to debug/fix
Sent via TCP/IP
Try a different Rom?
Cheers dude, will try that, question is, so sick of flashing, can't be arsed trying loads of roms, now which one....
Sent via TCP/IP
it's easy.
never reboot phone in silent/vibrate mode and have a boot animation sound (or at least lock screen soundo on).
after reboot be sure some sound is played before a call (as mentioned above).
your problem is gone (at least it should be).
just out off interest, does your provider do HD voice, just wondering if there might be a link?
tumult said:
it's easy.
never reboot phone in silent/vibrate mode and have a boot animation sound (or at least lock screen soundo on).
after reboot be sure some sound is played before a call (as mentioned above).
your problem is gone (at least it should be).
Click to expand...
Click to collapse
Whoaaa, I'll try that and re-enable boot sound, really hope it works..... Thanks for suggestion
Sent via TCP/IP
slaphead20 said:
just out off interest, does your provider do HD voice, just wondering if there might be a link?
Click to expand...
Click to collapse
Yeah, I use 3 UK who use hd voice...
Sent via TCP/IP
Hmmmm, enabled boot sound, applied themes, changed kernel, did 2xwipes and fix permissions and still got call sound
Sent via TCP/IP
I have a crackling sound when making calls....and have something to do with enabling disable the sound, like the other guy mention here...
but the crackling persist and I cant make any call
see my post here
http://forum.xda-developers.com/showpost.php?p=32351893&postcount=9189
gsw5700 said:
* currently running Omega v27
* If I flash stock ROM or Omega v27, sound during call is fine.
* If I flash a different modem, sound is normally lost, despite clearing caches and fixing permissions.
* flashing a theme can lose call sound
* I can restore a known working nandroid backup and have no sound when it boots
* best way to get sound back is to flash siyah kernel then dli4 modem, then clear caches and fix permissions (although this doesn't always work)
* sometimes the only way to get audio during a call isto reflash
* changing a kernel often means sound is lost
* I never had this problem with ics or earlier versions
Click to expand...
Click to collapse
Been dealing with this since JB leaked. Exact symptoms... Took me almost 4 hours 1 day to finally get all my mods/themes/kernel right and have sound. Looks like we found the fix though, will try next time I run into this issue. Likely when an official official JB is released, not the poland soak test.
yes!!!
best way to get sound back is to flash siyah kernel then dli4 modem
just did that, only left combination that I had to test...sound is back I think...
Scared to touch again at the phone kkkkkk
let's see...
Dude, i think tumult has maybe sorted it out, enabled boot sound and not one issue since, hoping it continues.
Sent via TCP/IP
Tumult is a star xda dude looks like problem is fixed, many many thanks
Sent via TCP/IP
I've started getting a situation when I install a MIUI based ROM in my I9300T, and any call to or from a mobile has extremely distorted audio (sounds like an amplifier trying to run at 150%) in both directions.
The audio is fine to landlines, so it sounds like it might be CODEC based.
I've done factory resets, Dalvik, Cache, reflash, new modem, reduced volume, and everything else I can think of. Flashing back to a non-MIUI resolves the problem, and re-flashing MIUI brings it back every time.
I've found a couple of threads asking about this problem, but nobody has every given a suggested solution (other than reset, reflash, modem).
Has anyone here experienced this or found a solutions?
Cheers,
Jason
AW: [Q] Badly clipped voice audio running MIUI based roms
Had exactlythe same problem, tried different MIUI versions, different modems etc. Call audio on ALL Samsung based MIUI was terrible, it worked only well on MIUI polimorph (which is AOSP/CM based). But on this MIUI I had issues with Bluetooth...
I read somewhere that this problem may occur when you come from stock Samsung Jellybean ROM and then flash a Jeallybean MIUI. So I tried following:
1. Download a ICS Stock Samsung ROM (for example 4.0.4) - important: complete ROM with PDA, Modem & CSC)
2. Flash ICS ROM with ODIN -- warning: all your data on internal SD will be erased!
3. Boot into your ICS Stock Samsung ROM (just to check call audio, should be fine...)
4. Flash CWM
5. Restart phone into CWM and flash your MIUI
6. Wipe data/factory reset
7. Restart & boot your MIUI. In case you got stuck while booting into MIUI do another full wipe data/cache in CWM. Then booting into MIUI should work fine.
!!! Attention: ALL YOUR DATA ON INTERNAL SD ARE ERASED WITH THIS METHOD !!! Be sure to copy your data, backups etc. to external SD or to your PC/laptop !!!
This was the solution I found after 1,5 weeks trying and reading and trying etc... Hope this works for you also!
Btw: be very careful doing this - there is always a risk of bricking your phone! Read carefully all about flashing with ODIN! Good luck...
Brilliant, thanks for the lengthy response!
The main thing I was wanting was an acknowledgement that someone had experienced and been able to overcome the problem, and you've included a description of exactly how you did it too.
Thank you very much for the help, and I'll post back in here if this works for me too in case others have the same problem.
I'd love to know which part of this process actually resolves the issue. I wonder what aspect of the JB ROM is not erased or overwritten by the MIUI installer.
AW: [Q] Badly clipped voice audio running MIUI based roms
You're welcome mate!
I'm also wondering WHY this helped, but it did... I only read somewhere in the forums that all the Bluetooth and WiFi issues on CM 10.1 only happen when flashing from a JB Samsung ROM, and everything is ok when coming from an ICS ROM. So I thought it is worth the try...
And I'm really happy now that I can use my beloved MIUI (Sammy-based MIUI-India) on my SGS3
Wow, what a grind this was to implement.
OK, so I...
1. Odin installed 4.0.4 and reset
2. Flashed MIUI m0, same problem
3. Odin installed 4.0.4 again, reset
4. Made a call, no audio at all
5. Factory reset again
6. Made a call, receive audio only, no send
7. Factory reset again
8. Reflashed MIUI m0
9. Made a call, no audio
10. Flashed modem DUELL2
11. Audio works!
12. FlashedMIUI India
Finally, MIUI and working audio!
You'd think from this list that flashing the new modem would have fixed the original issue, but I'd already tried this several times with no luck.
I'm guessing there is something in the 4.0.4 roms that is set in the flash related to a hardware codec. It may be that in JB the values are modified, and once it's been changed MIUI doesn't have any means of resetting it, during installation or subsequent booting.
Now I've wasted many hours on this, but at least I can go home happy
AW: [Q] Badly clipped voice audio running MIUI based roms
Really much work, but finally you got it working! Congrats!
Yes, I know, only flashing different modems without flashing ICS before won't help with this weird MIUI audio issue... Can't remember all the modems I tried, but tried many...
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
This issue was mentioned before, but there isn't any recent or working solution. So...
My lower microphone doesn't work, neither in calls nor in recording applications It's very very quiet. Changing ROM, kernel, nuking the rom doesn't fix this, however sometimes the microphone works fine. Upper microphone also works fine (could be checked by switching to loadspeaker).
Does changing the charging board will fix this or the issue is elsewhere (on MB ie)? What board should I buy (new china one, used original)? What revision is best (2.2, 2.3 (this one I currently have). Or maybe the problem lays somewhere deep in the software (audio menu is ofcourse blocked)?
Is this problem even exist on the official rom?
Zile995 said:
Is this problem even exist on the official rom?
Click to expand...
Click to collapse
Actually I didn't try one. But I tried:
- CM 10.1
- AOSP Neatrom 5.0
- Neatrom from 5.9 to 6.3 (problem first occured sometime after updating to 6.0, but I could have nothing in common)
Also tested serval Dorimanx kernel, Apolo 4.13 and 4.14, latest Philz and nothing...
Try to flash stock firmware over odin. First do the full wipe in recovery and then boot phone to download mode.