CM13.0 Problem - AT&T Samsung Galaxy S II Skyrocket SGH-I727

After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!

M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A

M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.

spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk

Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/

Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here

Related

[Q] CM10 Phone App Issue

Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
clcrawl said:
Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
Click to expand...
Click to collapse
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Thank you very much, I am going to give this a try shortly.
scarroll825 said:
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Click to expand...
Click to collapse
The 8/26 nightly fixes this issue and was just posted to get.cm.

[Q] Problem with making and receiving calls

Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..

SMS/ Phone call Issues

Hello everyone!
I installed TKHD ROM and love it except i'm having 2 very big issues!
1. Text messages. I don't get messages friends send me even when they're right next to me.
I've tried AirPlane Mode, rebooted, cleared Data and Cache of the app itself and nothing :'(
2.. Phone calls. When placing a phone call it sometimes lags before making that little chime (the one that notifies you that you're now making a call before the ringer sounds) It could sometimes take a good 5 seconds before making the call. Or, sometimes i make a call and it goes straight to VM even tho the person im trying to call is right next to me. This is also the same when people sometimes try to call me. Tho i'm not even using the phone, when thye dial it goes straight to VM sometimes.
Once again i've tried rebooting, flashing the ROM clean all over again etc but the same thing persists.
How did i install this ROM? By following the exact guide provided on the OP.
ROM: Latest version of TKHD
Kernel: Whatever comes with this ROM tho i also use SkyHigh
Recovery: Latest TWRP
Bootloader/ Modem: The latest version (OKC?)
I know some may say its my device but we'll idk about that. It only happens on this ROM.
I really like this ROM and would love to stay with it but idk how i can do that if i can't get the basics to work
Please help XDA !
Have you tried Odin to stock rom. Factory reset then fresh install? Also, I would download another copy of the rom. Could be a bad download.
edward6790 said:
Hello everyone!
I installed TKHD ROM and love it except i'm having 2 very big issues!
1. Text messages. I don't get messages friends send me even when they're right next to me.
I've tried AirPlane Mode, rebooted, cleared Data and Cache of the app itself and nothing :'(
2.. Phone calls. When placing a phone call it sometimes lags before making that little chime (the one that notifies you that you're now making a call before the ringer sounds) It could sometimes take a good 5 seconds before making the call. Or, sometimes i make a call and it goes straight to VM even tho the person im trying to call is right next to me. This is also the same when people sometimes try to call me. Tho i'm not even using the phone, when thye dial it goes straight to VM sometimes.
Once again i've tried rebooting, flashing the ROM clean all over again etc but the same thing persists.
How did i install this ROM? By following the exact guide provided on the OP.
ROM: Latest version of TKHD
Kernel: Whatever comes with this ROM tho i also use SkyHigh
Recovery: Latest TWRP
Bootloader/ Modem: The latest version (OKC?)
I know some may say its my device but we'll idk about that. It only happens on this ROM.
I really like this ROM and would love to stay with it but idk how i can do that if i can't get the basics to work
Please help XDA !
Click to expand...
Click to collapse
What app are you using for messaging? I'm having an issue with MMS sending right now, but I think it's related to WiFi Calling and EvolveSMS. However my cousin did send me a text yesterday which I did not receive, and I wasn't on WiFi Calling at the time.
I am actually using stock SMS and MMS.
And I heard something about WiFi calling or wifi in general
And I do have them off and still run into this issue

Stable ROMs?

I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
I'm using cm and lineage and they are alright, cm from November has less bugs right now
What bugs are you seeing on Lineage?
jdinkel said:
What bugs are you seeing on Lineage?
Click to expand...
Click to collapse
Sprint variant, normal cm complaints early: SMS issues, some calling issues, can't cheat at pokemon go, 5ghz WiFi crashes for me 900p on lollipop bootloader...ok4 firmware
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
jdinkel said:
I went ahead and installed it this weekend. I'm not having any problem with 5ghz wifi, but I am having calling issues - when making or receiving a call the call screen just doesn't show up. The phone looks like I'm not even in a call but I'm certainly talking to someone on it. So I can't send any number presses (was impossible to navigate a businesses caller menu) and I can't hang up - either they have to hang up first, or I have to reboot my phone to know for sure it is hung up.
Other than that it is working great. Performance seems better and I'm loving the Pixel launcher. I don't see any sms issue, but I do all sms through Google Voice/Hangouts. The phone issue is going to force me back to CM13 though.
Click to expand...
Click to collapse
Is it a bug in the. .looking at the screen thing? My cm flashes sometimes because it thinks Im looking at it or not
i7vSa7vi7y said:
I'm on stock rooted MM and want a stable ROM since I've been having problems like sudden short freezes and now my internal storage says 96% full when it's not even close to that. I'm thinking of going back to Lollipop with MOAR v7. Is there any other stable ROMs you guys suggest?
Click to expand...
Click to collapse
the internal storage issue youre having isnt ROM specific, its basically an issue with the ROM basically ghosting your internal storage and ignoring whats there by not looking at the table of contents. Ive been looking for a solution for this myself and not finding much. If i find a solution, ill post something up

Microphone not working...

My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??

Categories

Resources