CM11-nightly Dialer FC - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Flashed 140101 and then updated to 140103 and still having the same issue on both versions. FC anytime the dialer is used. Sometimes it just ends the call, other times it says com.android.phone process has stopped. Every 20th or so time, however the call does go through. I can text and data is working, but I'm not getting LTE on EDGE. I did have 4G prior to flashing. This is strange.
Additionally, when I go to settings>wireless&networks>mobilenetworks and press carrier settings, I get the same com.android.phone process has stopped error message.
using TWRP 2.6.3.1
CM11 140101 nightly
pa-gapps-4.4.2-20131215
Service Provider is Family Mobile
When straight from stock 4.1.2 to CM11-140101. Used the factory reset wipe in TWRP prior to flashing (not the advanced wipe).
Sorry if this is posted in the wrong place but I cant seem to find a CM11 d2att thread in the Development forum.

seqops2013 said:
Flashed 140101 and then updated to 140103 and still having the same issue on both versions. FC anytime the dialer is used. Sometimes it just ends the call, other times it says com.android.phone process has stopped. Every 20th or so time, however the call does go through. I can text and data is working, but I'm not getting LTE on EDGE. I did have 4G prior to flashing. This is strange.
Additionally, when I go to settings>wireless&networks>mobilenetworks and press carrier settings, I get the same com.android.phone process has stopped error message.
using TWRP 2.6.3.1
CM11 140101 nightly
pa-gapps-4.4.2-20131215
Service Provider is Family Mobile
When straight from stock 4.1.2 to CM11-140101. Used the factory reset wipe in TWRP prior to flashing (not the advanced wipe).
Sorry if this is posted in the wrong place but I cant seem to find a CM11 d2att thread in the Development forum.
Click to expand...
Click to collapse
Im also experiencing this, flash back to 12/31 build and you should be fine.

Epikarus said:
Im also experiencing this, flash back to 12/31 build and you should be fine.
Click to expand...
Click to collapse
I'm on 12/31 after this problem, and phone is fine. Has this been fixed? I have not tried a new nightly since 12/31 because of this. It seemed to be in all the 2014 nightlies. I believe the last I tried was around 01/04.

mrsubway said:
I'm on 12/31 after this problem, and phone is fine. Has this been fixed? I have not tried a new nightly since 12/31 because of this.
Click to expand...
Click to collapse
Yes it has. A fix was applied on the 5th. Everything is fine and dandy now.
Sent from my Nexus 7 using Tapatalk

Related

Can't connect to Sprint service

I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?
hvuong said:
I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?
Click to expand...
Click to collapse
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Please make sure to update us...
billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2
billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas
hvuong said:
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas
Click to expand...
Click to collapse
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
fergie716 said:
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Don't think so I do it often too. Don't think it hurts anything tho
billard412 said:
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
Don't think so I do it often too. Don't think it hurts anything tho
Click to expand...
Click to collapse
Thanks.. I've been Googling it and found some stuff on the Sprint forums the other day. I'll enter it when my 3G seems to lag a bit lol. Always provides a boost
Sent from my SPH-L710 using Tapatalk 2
I got it repaired at the Sprint store. They replaced the board after flashing didnt work for them either. It was probably the radio he said
ya cuz he dont no u ****ed wit it. i bet he didnt no wat he was doing and the sprint store wasnt necessary. my $.02

[Q] Phone deactivated?

I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules

[Solved] Urgent, LTE issue.

Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.
Solved. ODIN'd back to stock =) Thanks hednik!
RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app

[Q] Have CM 10.2 - Phone Randomly Reboots

I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
cbellk said:
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
Click to expand...
Click to collapse
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Jessooca said:
Does your phone get to the Samsung logo and reboot?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nope, it's the CM logo.
joeyhdownsouth said:
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Click to expand...
Click to collapse
Thanks. I tried this, and it didn't seem to work. Phone's still randomly rebooting. I'm on 10.2, btw. Haven't moved to 11 yet.
Jessooca said:
The best way to truly fix your issue is to start back over at square 1... Odin it back to stock with the tar or MD5 file. The last thing you want to do is make things worse trying too many things.
If you can get back into recovery wipe everything, (but not your Sd card ) as long as you've got a Rom on your Sd card to flash. Don't flash the same rom again, your issue could be a number of things.
- If you made a backup before flashing then revert back to it. Then try to download the rom again, or if you can download the latest slimkat on another pc and copy it to your sd card it's small a quick download and it will get you back up and running.
That is, if you don't feel like using Odin.
Click to expand...
Click to collapse
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
cbellk said:
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
Click to expand...
Click to collapse
Data restore could very well be the culprit.
sent from my GS3
joeyhdownsouth said:
Data restore could very well be the culprit.
sent from my GS3
Click to expand...
Click to collapse
So I'd have to start from scratch? Is there any way I could keep my data?

[Q] Unfortunately, themes provider has stopped

Hello, T mobile GS4 owner here. I think I first posted this question in the wrong forum. Hopefully this is the right place. I wanted to post in the Liquidsmooth thread, but was unable to.
I just signed up because I'm having trouble flashing the latest Liquidsmooth rom. I've been happily running Liquidsmooth for many months now, and my current version is from 6/21/14. I haven't had any problems flashing until now.
I've tried flashing the last 2 builds and keep getting the message "unfortunately themes provider has stopped".
It appears as soon as the phone boots up after flashing. It's right in the middle of the screen and won't allow me to do anything. Every time I click on OK, it comes back immediately. I have searched high and low for a way to fix this. So far I've tried reloading, rebooting, re-downloading starting again from scratch. I always clear the data and cache and do a factory reset. I have attempted flashing at least half a dozen times and always get the same annoying message.
Any help would be very much appreciated.
BTW, I'm also flashing the latest full version of GAPPS at the same time.

Categories

Resources