[Q] mic issue - Captivate Q&A, Help & Troubleshooting

I'll just get down to the brass tacks here,
I have a cappy (love it) running Helly Bean 4.2.1, and I followed the instructions as per the thread. Everything worked fine until I tried to use the Config Manager, which told me I had not installed the Devil Kernel. I got the latest kernel from hellybean's site, and after installing it (flashing .zip through CWM), I would get back-to-back popups that com.android.phone had stopped working. I tried every version for Jelly Bean, from 1.6.x to 1.9.5, and all did the same thing.
It might be worth noting that, the same day I flashed 4.2.1, I also replaced the touchscreen assembly, touch button assembly, and the touch button ribbon cable thanks to the cruel mistress Gravity. I'm pretty sure everything was done right, and I'm not aware of any calls I had made to test it. When starting on a fresh rom, I tested the mic with Z-Device Tester, and the mic registered sound input. When I would call someone, the mic wouldn't work, and testing it again with Z-Device, the mic picks up nothing.
To add to the confusion, I reinstalled a backed-up rom I had made back in November (Helly Bean 4.1.2), when everything was in working order. Again, Z-Device picked up on my voice, test call failed, Z-Device no longer shows mic input. Using an external mic (headphones with a mic) works, but the built in mic fails on calls.
Should I try Odin back to Gingerbread and start totally fresh, do you think it's a hardware fault on my end, and has anyone else had the com.android.phone FC like i have on Helly Bean 4.2.1?
Thanks for reading.

guitaraddict4791 said:
I'll just get down to the brass tacks here,
I have a cappy (love it) running Helly Bean 4.2.1, and I followed the instructions as per the thread. Everything worked fine until I tried to use the Config Manager, which told me I had not installed the Devil Kernel. I got the latest kernel from hellybean's site, and after installing it (flashing .zip through CWM), I would get back-to-back popups that com.android.phone had stopped working. I tried every version for Jelly Bean, from 1.6.x to 1.9.5, and all did the same thing.
It might be worth noting that, the same day I flashed 4.2.1, I also replaced the touchscreen assembly, touch button assembly, and the touch button ribbon cable thanks to the cruel mistress Gravity. I'm pretty sure everything was done right, and I'm not aware of any calls I had made to test it. When starting on a fresh rom, I tested the mic with Z-Device Tester, and the mic registered sound input. When I would call someone, the mic wouldn't work, and testing it again with Z-Device, the mic picks up nothing.
To add to the confusion, I reinstalled a backed-up rom I had made back in November (Helly Bean 4.1.2), when everything was in working order. Again, Z-Device picked up on my voice, test call failed, Z-Device no longer shows mic input. Using an external mic (headphones with a mic) works, but the built in mic fails on calls.
Should I try Odin back to Gingerbread and start totally fresh, do you think it's a hardware fault on my end, and has anyone else had the com.android.phone FC like i have on Helly Bean 4.2.1?
Thanks for reading.
Click to expand...
Click to collapse
I would flash back to stock gb (kk4) as a first step. Let us know how that goes.
Sent from my SGH-I897 using xda app-developers app

BWolf56 said:
I would flash back to stock gb (kk4) as a first step. Let us know how that goes.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I did, and again, same result. Mic testing worked right up to the call, and once in-call, the mic no longer worked.

guitaraddict4791 said:
I did, and again, same result. Mic testing worked right up to the call, and once in-call, the mic no longer worked.
Click to expand...
Click to collapse
Did you try it on stock KK4?
Also, did you restore your apps?

BWolf56 said:
Did you try it on stock KK4?
Also, did you restore your apps?
Click to expand...
Click to collapse
Yeah, all the way back to stock KK4, and no, I didn't restore apps. I just downloaded z-device from the market and tested again.

guitaraddict4791 said:
Yeah, all the way back to stock KK4, and no, I didn't restore apps. I just downloaded z-device from the market and tested again.
Click to expand...
Click to collapse
I would try without z-device and if that doesn't work, it could be a hardware issue. I've never heard of a mic that stops working on call but I'll keep looking.
Sent from my SGH-I897 using xda app-developers app

BWolf56 said:
I would try without z-device and if that doesn't work, it could be a hardware issue. I've never heard of a mic that stops working on call but I'll keep looking.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I went back to KK4 again, no z-device, and it still didn't work. I'll crack it open and see what's what. I didn't beforehand because I didn't have the money to replace anything that I could potentially break (thank you, tuition and flimsy ribbon cables)

mic not working
i had a stock captivate and i got to messing with the setting when u hold the volume buttons and power at the same time. and i deleted something that i couldnt get back and after that my mic stopped working. i rooted my phone and flashed the collective 4.1 rom and mic still didnt work

I have no idea what's going on with your mic as it could be a hardware issue since you've had it open recently. However I can tell you about your other issues.
On 4.2.1 hellybean the devil kernel config app does not function correctly whereas the devil kernel manager app does. As far as the issues you encountered after flashing the other devil kernels, that is because those kernels are built for 4.1.2 so they aren't fully compatible.
Sent from my SGH-I897 using xda app-developers app

salgomez14 said:
i had a stock captivate and i got to messing with the setting when u hold the volume buttons and power at the same time. and i deleted something that i couldnt get back and after that my mic stopped working. i rooted my phone and flashed the collective 4.1 rom and mic still didnt work
Click to expand...
Click to collapse
The only thing I could think is to factory reset and flash from stock KK4 for your mic issue. I'm not sure what you deleted but if you could remember (or at least where it was), that would help.

Related

[Q][i9000] Rear Speaker Problem after Flash

Hi Everyone,
I've searched through the i9000 section and have not found a solution to my problem.
I have a problem with my rear speaker on my i9000 after flashing to the stock XXJVU 2.3.6 rom using Odin. I have sound through the headphones, and the front speaker but no sound through the rear speaker (i.e. I cannot hear the phone ring).
Prior to the flash I was running a cooked rom (from Rom Kitchen) JS8 (2.2.1) with the speedmod k13c kernel with the lagfix enabled. This was working fine and the speaker was working correctly prior to the flash.
Before I flashed I attempted to disable the lagfix through CWM, however, towards the end of the lagfix the phone got stuck during the testing proportion after converting everything back to RFS. When disabling the lagfix I had forgotten if the /system was converted to ext4, and I did not convert that back to RFS (to my mistake the /system was most likely still ext4), but converted the rest back to RFS.
After a long time I took out the battery and restarted the phone. The phone booted into the rom fine, however, all the settings had been reset (just like when you factory reset the phone). I assume the reason was that it did not restore the backup of my settings when it got stuck during the disabling of the lagfix. I do not remember if I had sound when I booted back into the rom.
I then turned off my phone and flashed the XXJVU stock rom via Odin (pda/modem/csc/pit with re-partition selected), and then cleared all the caches and factory reset before and after installing the Semaphore 2.5.0 kernel. Both of the flashing processes completed without any error. When I did boot into the new rom I realised that I no longer had any sound, however everything else seems to be operating fine.
List of things I have tried to fix this issue:
Factory reset (both through the menus and *2767*3855#)
Wiped and factory reset, wipe cache, wipe dalvik cache many times
Tested the speaker through *#0673# (Audio Test Mode) and get no sound
Tested the speaker through *#0283# (Audio Loopback Control) and get no sound
Taking the back cover off the phone and pressing the speaker module whilst playing music to see if it was a loose connection
Flashed the firmware back to two stock roms from my carrier (2.2 and 2.3.3 version from Optus) still no sound (everything else worked fine)
Flashed the XWJW1 stock firmware and still no sound
Tried inserting and removing headphone plug into the jack multiple times. In case there was an issue with the phone thinking there were headphones still plugged in.
Turned on "logger" in Semaphore kernel and using alogcat to see if there were any errors related to the rear speaker (nothing I could see)
I am now thinking it could be a hardware issue, however, it just seems too coincidental that the rear speaker breaks whilst I am flashing a new rom on the phone. Might have to open it up and have a look at the speaker module more closely.
Any ideas anyone?
For those who find it tldr
Summary:
Disabled lagfix on 2.2 rom process got stuck and battery had to be removed
Flashed new rom as phone still booted to XXJVU and noticed there was no sound in rear speaker
Tried many things to try to get phone sound working again but have run out of ideas
Thanks everyone!
Outcome:
I have bought a new speaker module and installed it and it WORKS!
Buy a new phone, bro
That is a best ideas ever)
Sent from my GT-I9000 using xda premium
kettont said:
Buy a new phone, bro
That is a best ideas ever)
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
haha I wish I could. Gotta wait for the SGS III to be released
Anyone have any ideas?
same problem
Up, Up
Sounds very intresting.
I got the same problem after flashing Slim ICS 2.8 to 2.9.
Revert back with my Nandroid Backup to 2.8, that i done before flashing ,but still the same, Before everythings worked fine.
I also suspect Free Spirit Fm and the options in audio --> Method --> Galaxy S ALSA/ICS (DANGER) , but this option always wored fine since some month.
pimux said:
Up, Up
Sounds very intresting.
I got the same problem after flashing Slim ICS 2.8 to 2.9.
Revert back with my Nandroid Backup to 2.8, that i done before flashing ,but still the same, Before everythings worked fine.
I also suspect Free Spirit Fm and the options in audio --> Method --> Galaxy S ALSA/ICS (DANGER) , but this option always wored fine since some month.
Click to expand...
Click to collapse
Yes it is a very odd problem.
I have yet to open up the phone and check the connection of the rear speaker module. Everything is working fine except the rear speaker.
At least I now know I'm not the only person with this issue. What else have you tried to fix your problem? Tried some of the fixes that I have tried?
this is actually what I've done
revert back to Nandroid backup
Delete cache of some apps like Dsp manager and Spirit FM as i suspect it to broke my Rear Speakers (but maybe nothings releated)
Factory Reset and Wipe Everythings
Change Kernel to Glich V14
Now i also open up the phone and check the connection, everythings seem to be good
I'm now going to buy a new Rear Speaker and try to change it, maybe it's just a coincidence , But very strange .....
Yes, I find it hard to believe that my rear speaker stops working at the exact time that I'm flashing a new rom. I was going to buy a new speaker, but decided that I'll wait until I open it up and have a proper look. Just trying to find some motivation to go and do this, it has been about two weeks of trying and I've almost given up.
pimux said:
this is actually what I've done
revert back to Nandroid backup
Delete cache of some apps like Dsp manager and Spirit FM as i suspect it to broke my Rear Speakers (but maybe nothings releated)
Factory Reset and Wipe Everythings
Change Kernel to Glich V14
Now i also open up the phone and check the connection, everythings seem to be good
I'm now going to buy a new Rear Speaker and try to change it, maybe it's just a coincidence , But very strange .....
Click to expand...
Click to collapse
Did you end up buying a new speaker and installing it? How did it go?
m1n1on said:
Did you end up buying a new speaker and installing it? How did it go?
Click to expand...
Click to collapse
Hi m1n1on,
That seems to be very crazy , but i got the speakers today, i place it on my phone and it Works
I start to thinks that it was a pure coincidence !!!
It cost me 7,50 $ shipping include with this seller on ebay -----> easyworldwidetrading and i got also the screwdriver with it. I bought it on 19th and receive it today so it takes 9 days.
Try it and let me know......
pimux said:
Hi m1n1on,
That seems to be very crazy , but i got the speakers today, i place it on my phone and it Works
I start to thinks that it was a pure coincidence !!!
It cost me 7,50 $ shipping include with this seller on ebay -----> easyworldwidetrading and i got also the screwdriver with it. I bought it on 19th and receive it today so it takes 9 days.
Try it and let me know......
Click to expand...
Click to collapse
Wow awesome!
How is the quality of the speaker compared to the original? I'm debating if I pay more to buy a genuine rear speaker or just get a generic one.
How difficult was it to open up the phone and replace the speaker?
same issue but slightly different
Hey guys, I have the same issue with my i9000 after a fresh wipe and flashing the latest CM9 nightly build as of april 2nd ( update-cm-9-20120402-NIGHTLY-galaxysmtd-signed.zip ) and the rear speaker doesn't work for ringing or music playback, but I noticed it works for putting calls on speakerphone -- is this just me? Should I replace the speaker?
dariusr said:
Hey guys, I have the same issue with my i9000 after a fresh wipe and flashing the latest CM9 nightly build as of april 2nd ( update-cm-9-20120402-NIGHTLY-galaxysmtd-signed.zip ) and the rear speaker doesn't work for ringing or music playback, but I noticed it works for putting calls on speakerphone -- is this just me? Should I replace the speaker?
Click to expand...
Click to collapse
If the speaker is working in some cases then you won't be in the same situation as us. Ours didn't work at all, no matter what situation.
Have you tried flashing it back to a stock rom?
edit: stupid question but you have checked the "Sound" settings > "Volume" > "Media volume" and "Incoming call volume"?
Same problem I got today when woke up in the morning, I wonder why didn't alarm ring today. Then I tried flashing ROMs etc etc. watching videos on the youtube, did google and find this post.
I think I will have to buy new speaker.
Any idea?
buddyforever said:
Same problem I got today when woke up in the morning, I wonder why didn't alarm ring today. Then I tried flashing ROMs etc etc. watching videos on the youtube, did google and find this post.
I think I will have to buy new speaker.
Any idea?
Click to expand...
Click to collapse
G'day,
Have you tried the methods I tried in my first post?
Factory reset (both through the menus and *2767*3855#)
Wiped and factory reset, wipe cache, wipe dalvik cache many times
Tested the speaker through *#0673# (Audio Test Mode) and get no sound
Tested the speaker through *#0283# (Audio Loopback Control) and get no sound
Taking the back cover off the phone and pressing the speaker module whilst playing music to see if it was a loose connection
Flashed the stock firmware.
Tried inserting and removing headphone plug into the jack multiple times. In case there was an issue with the phone thinking there were headphones still plugged in.
I'm still waiting for my replacement speaker in the post. I will update if this fixes the issue.
Good luck!
Do you get ANY sound from the rear-speaker? I have a similar issue (loss of audio after flashing new ROM) but it is the handset speaker. After some troubleshooting, I found that there it was still working but was ULTRA low volume. With a number of tweaks, you can just hear calls if the other person is yelling. With headphones/rear-speaker, very thing is fine.
My next troubleshooting step is to find a way to repartition the phone and reflash a stock ROM. That's about all I have left as I have tried all other options.
Zimzum
Just an update people.
Just installed the replacement speaker module... and it..... WORKS!!
flash an official ROM using Odin
I need some help here. My i9000 seems to work through the rear speaker ONLY??? During hands free calls the thing is MUCH louder when turned around and listening from the rear. All ringing, alarms, etc. seem to emanate from the rear speaker. Is it difficult to replace the front speaker? I have cm9 Nightlies flashed (up to date). It's been like this for a few months already.

Odd Touchscreen issues

Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
CrazyPhil said:
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
Click to expand...
Click to collapse
Which ROM are you on, stock or a custom one?
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Phibernaut said:
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Haha ya I have odd touchscreen issues when I get to 100% battery and am still plugged in :cyclops:
adamskub said:
Which ROM are you on, stock or a custom one?
Click to expand...
Click to collapse
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
CrazyPhil said:
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
Click to expand...
Click to collapse
Oh ok, then I'm not really sure. I would, if you want, try and flash right back to complete stock and see if your having the same troubles. If you are then it's almost guaranteed to be a hardware problem. However, if the problem doesn't persist then it could have just been some weird bug or glitch that happened. I've had some weird things happen a week or so after a flash and it was software related.
But all this would be having you do a reflash either through CWM/Safestrap or sbf and then you lose everything you have (Though you can backup & restore apps via Titanium Backup). So if you don't end up reflashing I understand
Also does this happen only at certain times/intervals say when your charging? Hope this helps!
Edit: I looked at the orig post at work and forgot to look at it again. A hard reset should be able to fix it, but you never know. I would recommend a reflash and see what happens. Sorry I can't be more help
I hate you. I read your post yesterday and thought "huh, that's really weird and unfortunate." I woke up today and the same thing is happening to me. I haven't flashed anything since April. It was totally out of the blue.
Mine only works when the screen is slid open bout half a centimeter, not even enough to force the screen to rotate.
Sent from my DROID3 using xda premium
That's exactly what's happening....It's been like this for a week. However, it sometimes works when I left it for the night to charge...or randomly, but full functionality lasts only a few minutes.
has there been any update on this status? im trying to fix a friends with the same problem.
Chaunton said:
has there been any update on this status? im trying to fix a friends with the same problem.
Click to expand...
Click to collapse
I think that is bad luck and your digitizer is stopped working.
ugynok said:
I think that is bad luck and your digitizer is stopped working.
Click to expand...
Click to collapse
I'm in the same train
It's strange.
Yesterday my touchscreen it was completely unresponsive the whole day.
stock rom, everything untouched
i rebooted it a million times. closed or open make no difference.
today, it is working amazingly
what was the difference? nothing at all! it layed on my desk all night
i don't understand how the digitizer can go between perfect condition and not working as it wish.

[Q] No Sound from Speakerphone

Received a few months old Note as a gift. Installed stock ICS through Kies and flashed a safe kernel + CWM (PhilZ kernel + CWM 6.0). Been using it for 2 days, and tonight when I played a MP3 through speakerphone, the sound completely disappeared midway through the song. I've tried changing the sound settings and rebooting the phone to no avail. Is the speakerphone dead?
whats happens when u call someone?
Normal calling is fine, but if I put it on speaker there's no sound.
Hey i think you should try a factory reset or get back to original rom
Sent from my MB865 using xda premium
Mucchan said:
Normal calling is fine, but if I put it on speaker there's no sound.
Click to expand...
Click to collapse
so that means the earpiece works fine and the speaker is dead.. could be a hardware issue as well.
yea as said above try doing a factory reset with CWM and check if that works.. if not. go back to stock rom (but dont wipe anything on that)
last resort : take to a phone shop and take advice.
Did a factory reset and still nothing. I suppose I'll call Samsung tomorrow to see how much they charge for a speakerphone replacement. This phone was my dad's and he lives overseas so I won't be able to repair it under warranty here
If I were to send it to Samsung for repair, I'll need to flash the stock ICS kernel back right?
any ways if its not under warranty so if i were samsung i wouldnt care but not sure how real samsung ppl will react.
its ur decision if u want stock kernel or not.. there is a thread from Dr ketan and has all the stock kernels on it
I switched the phone off and left it to charge overnight. When I switched it back on this morning the sound came back. Pretty confused now.
how did that happen... is that symptoms of a loose assembly
Sent from my GT-N7000 using xda premium

[Q][SOLVED]Weird camera problem (image but unresponsive buttons), any ideas?

Hello to you all,
I've looked and couldn't find a similar thing happen to anyone else!
So, I have a X8 with locked bootloader and stock Ginger DX 29, and although it used to work fine, I now am experiencing this problem with my camera.
Basically, the camera button isn't recognized to launch the app from the homescreen for a start, and then if I do open it from the app drawer, I can see the image fine, but nothing works (accessing the settings, changing from camera to video, taking a picture, etc) and after a few second I get a Close app/Wait kind of dialogue and I'm back to square one.
this is annoying because I tried pushing older camera.apks that I knew worked with no problem, no change. I tried doing a factory reset, no luck, flashing gdx again from scratch (didn't try the SEUS reset because it's a pain to root again and all that, and gdx used to work fine) I've also checked that it wasn't a hardware problem by mapping the camera button to an action in snesoid and it worked fine.
I don't really know what to do from that point! I was thinking maybe it's got to do with my image folder on the sd card, or something like that since it's the only thing that stays there throughout the wipes? Anyone knows what could be at fault? It's annoying not able to use the camera!
Thank you in advance.
Re: [Q] Weird camera problem, any ideas?
Settings ,applications,manage applications,find camera.apk and wipe cache and data.
If it doesnt help,try to download a camera app from play store and see if it works.
so, wiping the data didn't work, however I did two things : download a third party app and renamed my DCIM folder to another name, and one of them worked!
I'm suspecting the second one because as I tried my original app again, everything worked as well...
It must have been write protected for some reason, and that's why my camera app would be stuck at the begining I guess...
I'll try to copy my files back in the new folder that was created and see if it happens again.
Thank you!
Re: [Q] Weird camera problem, any ideas?
nice to hear you solved it. :thumbup: please do indicate in the thread title that it's solved. it may help other users with a similar issue.
Sent from my rooted tomato using tapatalk
All done!
I'm still not able to use the camera button when on my home screen but I'm guessing it's a rom issue, as I don't remember how it behaved before...
awkXda said:
All done!
I'm still not able to use the camera button when on my home screen but I'm guessing it's a rom issue, as I don't remember how it behaved before...
Click to expand...
Click to collapse
i'vw never really experienced that before... so i can't help. just a suggestion though, have you tried using a different sdcard? if it still persists, maybe you're right and it's a rom issue.
Sent from my rooted tomato using tapatalk

[Q] Mic cuts out but with a twist.

The mic on my son's D4 was cutting out during calls, he could press any button to get it to stop for a second but it would keep doing it. He could hear the caller but they could not hear him. He did numerous factory resets (always being sure not to have stuff backed up to Google) and got a new SIM, tried safe mode. No change, still had trouble. For what it's worth, calls on Skype worked with no trouble so it's not the phone.
I got a new phone so sent him my old D4, it had never done this to me so again, nothing wrong with the phone. He fired it up and it started muting right away. It's not the phone, it's not the SIM...it has to be Google somehow. He's done more numerous factory resets and safe modes and making sure it's not backing up to Google but the new-to-him phone is still muting calls. He says that stuff IS being backed up because it pulls his wallpaper over every time he resets.
Any ideas on what he can try or why it may be happening?
Clementine_3 said:
The mic on my son's D4 was cutting out during calls, he could press any button to get it to stop for a second but it would keep doing it. He could hear the caller but they could not hear him. He did numerous factory resets (always being sure not to have stuff backed up to Google) and got a new SIM, tried safe mode. No change, still had trouble. For what it's worth, calls on Skype worked with no trouble so it's not the phone.
I got a new phone so sent him my old D4, it had never done this to me so again, nothing wrong with the phone. He fired it up and it started muting right away. It's not the phone, it's not the SIM...it has to be Google somehow. He's done more numerous factory resets and safe modes and making sure it's not backing up to Google but the new-to-him phone is still muting calls. He says that stuff IS being backed up because it pulls his wallpaper over every time he resets.
Any ideas on what he can try or why it may be happening?
Click to expand...
Click to collapse
Root safestrap and install cm10.2 on stock romslot? Or fastboot stock image. If neither works its gonna be a h/w issue
Sent from my XT894 using xda app-developers app
It's not rooted and he won't root. It's not a hardware issue, the phone he's using now was mine and never had any issues. It's the same problem on two different phones with different/new SIMs. As I said, Skype works without cutting out.
Something very strange is going on.
Clementine_3 said:
It's not rooted and he won't root. It's not a hardware issue, the phone he's using now was mine and never had any issues. It's the same problem on two different phones with different/new SIMs. As I said, Skype works without cutting out.
Something very strange is going on.
Click to expand...
Click to collapse
I'd say to fastboot or rsd to latest image and try then. Could also be a signal problem also
Sent from my XT894 using xda app-developers app

Categories

Resources