No incoming calls on recent CM12/other 5.x ROMs

[opalelement]

Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.

I have been updating official CM12 nightlies every week or two, so sometime around 3/15 I would have installed a nightly and could still receiving calls, just as I had been before. Then I installed the 3/29 nightly (based on files in my Downloads folder) and since then I have not received a single incoming call (evidenced by call logs showing last incoming call on 3/27). I can make outbound calls fine, but incoming calls don't even show up on my phone; it is like the call never happened, but I get the voicemail notification if they choose to leave one. The callers say the call rings 4-6 times then goes to voicemail as if I just didn't answer, and it happens with every caller, not just certain ones.

I tried wiping data with no luck, also tried clean-flashing a few other nightlies from the last two weeks including 4/14 and it still doesn't work. Swapped SIMs with my wife (we both have i605's being used on T-Mobile) and incoming calls to my SIM worked on her phone, calls to her did not ring on my phone so it is something phone-related, not network related. Nightlies from before 3/29 seem to be deleted from the CM Downloads page so I can't go back and test CM12 nightlies that I know worked, but I installed the CM11 M10 (KK) snapshot and can receive calls, so I know it has to do with recent Lollipop builds - the problem is that nobody else has issues (other than a few issues with certain OPO nightlies a while back) so I can't find a fix.

I thought maybe it was just CM12 but other ROMS (PAC-MAN 4/8 and CyanideL 4/14) still have problems, presumably because they pull code from CM. I checked logcats and the phone doesn't give any indication that the call is even coming through the network, but the SIM swap shows that it isn't a network issue.

Is anyone else experiencing any of these problems? I don't want to go back to KK if I can get this working, but it seems to be leaving me no choice.

 

[goofwear]

Yes I have a Verizon Note 2 unlocked using a net 10 At&t service sim card and after cm12 build 3/26
all calls go straight to voice mail with out notification or ringing. Other people are having this same problem on other phones too. I believe its in the telephone stack with the changes that were made. I believe we can revert the changes that were made and or flash the few files affected over the new builds. I cant get the rom to extract fully under windows the exe is giving my a python error and I have not had time to try it on my Linux machine.

Any one interested in helping figure this out, message me. I let you know How you can help and then we can post back in here

 

[wiitwd]

Wondering if anyone else is having problems with incoming calls not arriving on Lollipop nightlies over the last few weeks.

I have the same problem on my i605. I've done factory reset, wiped everything, flashed the latest nightly (cm-12.1-20150511-NIGHTLY-flo.zip) and pa_gapps-stock-5.1-20150418-signed.zip to no avail.

Incoming calls still ring several times and then go to voicejail. Another anomaly is that outgoing calls don't want to hang up. Calling my bank's voice menu system or leaving a voice mail requires me to power-off or reboot the phone to terminate the call. Calls will end if the other end hangs up.

I've reverted to cm-12-20150130-NIGHTLY-i605.zip via a ROM copy found on AndroidHost at which does have a working phone section. I can't post a link as yet, but searching for "cm-12-20150130-NIGHTLY-i605.zip" will lead you to it.

 

[jobren]

Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||

Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.

 

[wiitwd]

Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||

Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.

Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.

 

[jobren]

Thank you ever so much! It worked to get my i605 back on the air as a CM 12.1 phone. There are some oddities such as the Settings->Security page missing Screen lock and the Owner info bits. Hopefully the developers will find and fix the phone issues in the i605 nightlies. For now my plan is to try the latest nightly every two weeks and revert back if there's no joy.

Any good news? I noticed lots of updates going on in the nughtlies. I myself didn't get much luck with the nightly one week before.

 

[wiitwd]

Any good news? I noticed lots of updates going on in the nightlies. I myself didn't get much luck with the nightly one week before.

As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.

 

[harjotsandhu]

I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9

 

[harjotsandhu]

I am in the same boat. Any way other than described to get back to calling abilities? Like downgrading to KK maybe? I am in baseband MJ9

As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.

I tried the given method with 13 July 2015 nightly and it works. Saved my life. I upgraded my MJ9 baseband to ND7 with no effect. Only the given around is working.

 

[RJ803]

Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||

Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.

I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated

RJ

 

[wiitwd]

As of last night telephony is still broken in the i605 nightlies. I've gotten used to modifying the t0lte nightly to work on the i605.

I have some new information. When using the i605 nightlies, telephony fails to hang up calls or to receive incoming calls while in a GSM service area, e.g., Guam. Now that I'm back stateside in CDMA/LTE land, the i605 nightlies work great. I offer as a working hypothesis, therefore, that GSM telephony is broken in the i605 nightlies. When I go back in October I'll bring the latest modified t0lte nightly as well as my GTA SIM card.

 

[jobren]

I must be doing something Wrong, I copy the lines above and paste them into the appropriate file updater-script. just add the line in with the other very similar ones. Save the file and rezip it and flash using latest TWRP but It always fails. I tried blisspop and Cyanide L. from note 2 ATT forum. Does this only work with CM nightly s? any information would be appreciated

RJ

I have not tried with other ROMs. It definitly works.
Might worth it to have a look at the file in I605 and check the difference.

Sorry I couldnt upload my file. It seems that I do not have the rights to upload files yet. :silly:

 

[dmcgregor]

Temporary solution
According to beddess in the official cm12.1 thread
http://forum.xda-developers.com/showpost.php?p=60829301&postcount=513
t0lte ROM might be the solution to that. One have to go in to the zip pack and find the updater-script. Follow the syntax of the script and add two entries for the t0ltevzw into the long device list
Like this
getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" ||

Then this zip file would be flashable for I605. I am currently typing this reply on my Verizon galaxy note 2 with the latest t0lte nightly in Netzclub's network. Phone call hanging up and receiving issues are gone.

I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.

I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.

 

[dmcgregor]

I've tried this a couple of times and the flash always fails quickly at "updating partition details." I've downloaded the cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte.zip, found the updater-script (in \cm-12.1-20150901-SNAPSHOT-YOG4PAO23C-t0lte\META-INF\com\google\android) edited the file by adding in the getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || (added it right after the getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || entry. Saved the file and zipped the folder. Transfered back to the phone and tried to flash from recovery (TWRP v2.8.1.0), which is where things failed.

I'm pretty much a complete noob at this. I've only flashed my phone one time previously, and that was after a lot of false starts. So it is very likely I'm making a very basic error, but I'd appreciate any guidance given.

Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.

 

[jobren]

Any chance that someone who has successfully done this could upload their updater-script file? I've tried a few different variations without any luck getting it to flash. Right now I'm stuck between going back to a known insecure version of Android, or not being able to receive calls, hoping for a 3rd option.

OK. Let's try this.

The following is the content of my script file. Copy it into a empty txt file and rename it as 'updater-script'.....Here we go.
assert(getprop("ro.product.device") == "t0lte" || getprop("ro.build.product") == "t0lte" || getprop("ro.product.device") == "t0ltexx" || getprop("ro.build.product") == "t0ltexx" || getprop("ro.product.device") == "GT-N7105" || getprop("ro.build.product") == "GT-N7105" || getprop("ro.product.device") == "t0ltedv" || getprop("ro.build.product") == "t0ltedv" || getprop("ro.product.device") == "GT-N7105T" || getprop("ro.build.product") == "GT-N7105T" || getprop("ro.product.device") == "t0lteatt" || getprop("ro.build.product") == "t0lteatt" || getprop("ro.product.device") == "SGH-I317" || getprop("ro.build.product") == "SGH-I317" || getprop("ro.product.device") == "t0ltetmo" || getprop("ro.build.product") == "t0ltetmo" || getprop("ro.product.device") == "SGH-T889" || getprop("ro.build.product") == "SGH-T889" || getprop("ro.product.device") == "t0ltecan" || getprop("ro.build.product") == "t0ltecan" || getprop("ro.product.device") == "t0ltevl" || getprop("ro.build.product") == "t0ltevl" || getprop("ro.product.device") == "SGH-I317M" || getprop("ro.build.product") == "SGH-I317M" ||getprop("ro.product.device") == "t0ltevzw" || getprop("ro.build.product") == "t0ltevzw" || abort("This package is for device: t0lte,t0ltexx,GT-N7105,t0ltedv,GT-N7105T,t0lteatt,SGH-I317,t0ltetmo,SGH-T889,t0ltecan,t0ltevl,SGH-I317M; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/USERDATA", "/data", "");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/dw_mmc/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/dw_mmc/by-name/SYSTEM", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/dw_mmc/by-name/BOOT");
show_progress(0.200000, 10);

 

[dmcgregor]

A belated thanks as I'm just now seeing this. After struggling to get this to work for a few weeks I ended up rolling back to CM 11. But I'll give another try with CM 12.1 today and let you know how it goes. Either way I greatly appreciate you taking the time to post this.

 

[dmcgregor]

No dice. Copied the text above into notepad. Saved it over the original updater script. Zipped everything back up and tried to flash, but it failed right away on "updating partition details." No clue what I'm doing wrong. Could it be my recovery? I'm using TWRP 2.8.1.0, which seems to work fine for flashing the i605 version.

 

[jobren]

Emmm…i really don't know now. I have been using this file for several months without any issue. I dont think it is the recovery, either…Could be some details in the formating of the script…or our phones are actually different…

BTW…how many posts it needs to unlock the attachments feature?

 

[goofwear]

With the rom zip on your phone download and use ES file explorer. Locate your zip long press it then click the more button. then click extract and press ok. Navigate to the the META-INF\com\google\android\ folder and then long press on the file updater-script and then click rename and then ad .txt to the end so the file is now called updater-script.txt then click ok.
then click on updater-script.txt and open with es file editor. click the pencil in the top right corner to edit text. Then select the text I have shown here

assert(getprop("ro.product.device") == "epic4gtouch" ||
       getprop("ro.build.product") == "epic4gtouch" || 
       getprop("ro.product.device") == "SPH-D710" ||
       getprop("ro.build.product") == "SPH-D710" || 
       getprop("ro.product.device") == "d710" ||
       getprop("ro.build.product") == "d710" || 
       getprop("ro.product.device") == "smdk4210" ||
       getprop("ro.build.product") == "smdk4210" || 
       getprop("ro.product.device") == "SPH-D710VMUB" ||
       getprop("ro.build.product") == "SPH-D710VMUB" || 
       getprop("ro.product.device") == "SPH-D710BST" ||
       getprop("ro.build.product") == "SPH-D710BST" ||
       abort("This package is for device: epic4gtouch,SPH-D710,d710,smdk4210,SPH-D710VMUB,SPH-D710BST; this device is " + getprop("ro.product.device") + "."););

you want to sop at the ) + ".");
and right before the ifelse mount statement. delete the code above.
then press your back button once and then click save. Then RENAME updater-script.txt back to updater-script. press your back button a couple of time till you get back to the folder that has all the extracted files and then LONG PRESS and select all the files once they are highlighted then pres the bottom that says more and then click compress. then you can a -modded to the end of the file so you can tell them apart.
after it is done compressing you can delete the other files and keep your new zip.

after you get the hang of this you can do it in under 30 seconds, not including the time to extract and compress the rom.

WARNING THE ASSERT CHECK IS THERE SO YOU CAN NOT ACCIDENTALLY FLASH THIS TO THE WRONG PHONE AND PERMA BRICK YOUR DEVICE.
DELETING THE ASSERT TEXT WILL ALLOW YOU TO FLASH THE NEWLY MODDED ZIP

---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------

Stay off TWRP and philz cutom recovery I have never had a successfully boot, zips would fail halfway through flashing other phone would boot loop. this is back when i was flasinh I605 custom roms of 4.x.x and even cm 11.

I'm on cm 12.1 t0lte Nightly's now and I am using the actual Version I605 Clockword mode recovery with no problems. https://download.cyanogenmod.org/get/jenkins/139629/cm-12.1-20151217-NIGHTLY-i605-recovery.img

 

[Droid_Nut]

I just installed the latest nightly 12-22-15 and made a couple of calls and it rang every time, I am using VZW, so is this not a problem with this carrier, or will it eventually stop working?