So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
Related
Hi everyone.
I'm having a little problem with my Xperia S, it's kind of new (2 weeks of use).
When I'm using normally the cellphone, everything works great, but if don't use it for a long time and I grab it faster and unlocked it, sometimes the cellphone freezes! Well, not exactly freezing, it still works but VERY slowly, almost like freezing. I can't turn it off with power button, I had to user Power + Volume button to turn it off/restart it.
That happened in first week, so I unlocked bootloader and flash it another kernel (advanced stock kernel), and the problem was there.
Later I made a backup of the firmware (I updated to its last version with PC Companion, ICS btw) and flashed a custom ROM (XTXperience 4), and the problem was still there.
Yesterday I flashed a Generic ICS ROM downloaded from XDA Server using Flashtool, everything went normal until today, when the problem happened again.
I've been searching here in XDA and Google and still nothing seems clear of what is causing the problem, if it's the sim card or maybe a hardware problem. I'm going to relock the bootloader today, and I will try to repair the phone using SUS.
What is causing the cellphone to freeze? Hope someone help me with this. Thanks in advance!
btw, sorry about my english, hope you understand most of what I wrote
Well in my experience,
The phone freezes because it is too hot,
Or the RAM memory suddenly drops.
I mean sudden ur phone's RAM memory is 0.
I'm not sure too.
But I think reflashing the kernel, or flash other kernel will fix the problem
Try it
Sent from my LT26i using xda premium
What ics firmware did you flash? And did you do a complete wipe when flashing?
Sent from my Jellybean Xperia S
I've flashed other kernel and yes, I do a complete wipe when I flash another ROM, via Flashtool or CWM.
I've been thinking of rolling back to GB to see what happens.
Yesterday my phone freezes like 2 or 3 times in less than 15 minutes. First time I reboot the phone and it was ok like 5 minutes, then it freezes. I reboot again the phone and happened again.
Its not even hot or using a lot of RAM, it always has like 250 or 200mb free
Did u play with CPU settings?
w3nZ said:
Did u play with CPU settings?
Click to expand...
Click to collapse
No, this is happening since the first boot of the phone. When I turned it on the first time it happened, and I had to search how to force a reboot because I didn't know how to do it LOL
It doesn't happen very often, but when it does is very frustrating!
Try flashing a new rom, but wipe the system partition too? I always do that to ensure a fully clean install.
l.Urker said:
Try flashing a new rom, but wipe the system partition too? I always do that to ensure a fully clean install.
Click to expand...
Click to collapse
I'm thinking in flashing a non based stock rom, like CM or MIUI, because I flashed XTXperience before and the freezing happened.
Oh, and the problem still exists. I believe Wi-Fi connection maybe it's the problem, I'm testing some things right now.
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Well, I was on 6.1.A.2.45, I relocked the bootloader and an update changed the firmware to 6.1.A.2.55 using SUS without wiping data and the problem was still there, so I repaired the phone with SUS, it erased everything and the problem was gone for like 2 days. Today it happened again.
babylonbwoy said:
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Click to expand...
Click to collapse
Advanced Stock Kernel supports 6.1.A.2.55 firmware?
babylonbwoy said:
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Click to expand...
Click to collapse
Well, I Supercharged my ROM now, which setting do you use to fix the problem? I'm still having it.
I even flashed a CM10 based ROM and its still happening! I think it's a hardware problem
Nek0x90 said:
Well, I Supercharged my ROM now, which setting do you use to fix the problem? I'm still having it.
I even flashed a CM10 based ROM and its still happening! I think it's a hardware problem
Click to expand...
Click to collapse
Hi, did you manage to solve the problem? I'm having similar issues like you
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.
I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?
icewolf293 said:
I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?
Click to expand...
Click to collapse
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.
And that's why I only root my phone, and run it stock. Roms always do this, no matter what anyone says. And I said this in my other thread, but ppl try to day otherwise. I told you guys lollipop roms are buggy for our phones. 4.4.4 for the win. Just uninstall bloatware and ur good to go.
Sent from my SGH-M919 using XDA Free mobile app
epicboy said:
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.
Click to expand...
Click to collapse
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.
j21098 said:
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.
Click to expand...
Click to collapse
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.
epicboy said:
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.
Click to expand...
Click to collapse
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.
j21098 said:
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.
Click to expand...
Click to collapse
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?
epicboy said:
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?
Click to expand...
Click to collapse
No, I tried MD 1.3 and the stock T-Mobile ROM. Also forgot to mention I had a really bad problem with the Play Store. I couldn't install anything at all. I'd always get error 905 and this other number I forgot. No matter what I tried I couldn't get a fix, clearing cache, data, dalvik, uninstalling updates, reboots after each one and nothing fixed. Stock Firmware seemed to fix all the problems I had
Long story short, I started having this issue 2 days later the flashing of CyanogenMod 13 ROM, almost a month ago, maybe a little more. Searching on Google it appeared as a problem of the Cyano ROM, watching the amount of complains found on the web but, after flashing a stock-based ROM, the problem persisted. So I thought that maybe the earpiece speaker got damaged and orderer a new part on eBay. While waiting for the new part to replace, I decided to try to flash the latest stock firmware, trying to solve any kind of kernel related problems. Of course it didn't work. Finally the new part arrived and, after installing it, with a bit of disappointment on my face I realized it wasn't the earpiece speaker the problem: still no sound in calls.
Now, could the problem be the motherboard itself? The 3.5" jack, which belongs to the same module, works just fine. Any idea?
PurPLe SKy said:
Long story short, I started having this issue 2 days later the flashing of CyanogenMod 13 ROM, almost a month ago, maybe a little more. Searching on Google it appeared as a problem of the Cyano ROM, watching the amount of complains found on the web but, after flashing a stock-based ROM, the problem persisted. So I thought that maybe the earpiece speaker got damaged and orderer a new part on eBay. While waiting for the new part to replace, I decided to try to flash the latest stock firmware, trying to solve any kind of kernel related problems. Of course it didn't work. Finally the new part arrived and, after installing it, with a bit of disappointment on my face I realized it wasn't the earpiece speaker the problem: still no sound in calls.
Now, could the problem be the motherboard itself? The 3.5" jack, which belongs to the same module, works just fine. Any idea?
Click to expand...
Click to collapse
Flash the newest modem and bootloader, see if anything change
yaro666 said:
Flash the newest modem and bootloader, see if anything change
Click to expand...
Click to collapse
They have been installed on the phone automatically by flashing the latest stock rom available in my country.
Hello bro i have same problem but now no problem
Flas stock firmware n7100xxufnd3 with odin then root phone install cmw recovery 6.0.43 dont install phils or twrp ans flash rom eclips or rubaband 4.4.4 dont install any rom based cm or aosp with phils or twrp recovery .
For me when i flash phils or twrp recovery then i flash any rom i have this issue no sound in call but with cwm 6.0.43 no issue at all 3 month without any problem
zortadot said:
Hello bro i have same problem but now no problem
Flas stock firmware n7100xxufnd3 with odin then root phone install cmw recovery 6.0.43 dont install phils or twrp ans flash rom eclips or rubaband 4.4.4 dont install any rom based cm or aosp with phils or twrp recovery .
For me when i flash phils or twrp recovery then i flash any rom i have this issue no sound in call but with cwm 6.0.43 no issue at all 3 month without any problem
Click to expand...
Click to collapse
First of all thank you very much for the answer, mate, unfortunately even by following the steps you listed the problem isn't gone. Any other tip?
I'm having the same prob 2. No sound on either sides of the call. The strange part is the sound returns intermittently
vishal1286 said:
I'm having the same prob 2. No sound on either sides of the call. The strange part is the sound returns intermittently
Click to expand...
Click to collapse
What do you exactly mean? Would you verify if the problem occurs only during calls? You can test the earpiece by downloading a specific app from the Play Store (e. g. Speaker Tester).
I've been playing around with the phone flashing modems, bootloaders, stock ROMs et cetera but nothing seems to solve the issue.
PurPLe SKy said:
What do you exactly mean? Would you verify if the problem occurs only during calls? You can test the earpiece by downloading a specific app from the Play Store (e. g. Speaker Tester).
I've been playing around with the phone flashing modems, bootloaders, stock ROMs et cetera but nothing seems to solve the issue.
Click to expand...
Click to collapse
the earpiece n mic r gud n working. Tested. They work well with skype n whatsapp call. I hv been using custom ROMs n kernel in this phone since its release bt this prob started 6 mnths bk.
Sent from my GT-N7100 using Tapatalk