FORUMS

What Features Do You Look for in a Gallery App?

With so many different options to choose from, finding the right Gallery app may be a … more

Google Photos ‘Unlimited’ Storage Reportedly Being Capped

When Google Photos was announced, many of us thought very highly … more

Sprint Moves to Lift Video Streaming Limit for All-In

Yesterday, Sprint announced a new unlimited scheme that offered customers an … more

Xiaomi Releases Kernel Source Code For Mi4i

If you’ve been following the XDA News Portal lately, you might have noticed an … more

[MOD] CyanogenMod 11 on Verizon S4 in GSM mode (AT&T/T-Mobile)

140 posts
Thanks Meter: 68
 
By linuxthinker, Senior Member on 4th February 2014, 06:36 AM
Post Reply Subscribe to Thread Email Thread
CM11 is great, but the libraries it's got appears to be heavily targeted toward CDMA mode and less so GSM. If you're a traveler or want to use your device with AT&T/T-Mobile, you'll want to install this patch which loads the AT&T ril onto your device. Without it, I couldn't receive any incoming calls and calls I placed couldn't be hung up (I would be stuck at the "hanging up" screen).

This patch is just two files (libril-qc-qmi-1.so and libril.so) pulled from the AT&T version (jflteatt) of CM11 (specifically, this version: https://download.cyanogenmod.org/get...2-jflteatt.zip).

I'm overseas right now, so I'm only able to test GSM mode, but it's working just fine for me now. If it's not enough for you, you might want to try the two other changes suggested here: https://jira.cyanogenmod.org/browse/CYAN-2362

To summarize, they are:
  • Set telephony.lteOnCdmaDevice=0 in /system/build.prop
  • loki_flash the jflteatt CWM with jfltevzw aboot - see here. Note that this is specific to MDK, so don't do this if you're on any other bootloader. Let me know if you want me to create a flashable version of this possible fix.

I didn't need to do either of these things to get it working for me, but you may need to do the first item if you want LTE (I'm currently in a country without LTE, so I can't test).

Flash this for GSM-optimized rils: jfltevzw-gsm-0.2.zip
Flash this to revert to CDMA-optimized rils: jfltevzw-cdma-0.2.zip
Last edited by linuxthinker; 4th February 2014 at 08:29 PM.
The Following 7 Users Say Thank You to linuxthinker For This Useful Post: [ View ]
 
 
4th February 2014, 03:45 PM |#2  
Junior Member
Flag Dallas, TX
Thanks Meter: 6
 
More
Are these the updated files?
Quote:
Originally Posted by linuxthinker

CM11 is great, but the libraries it's got appears to be heavily targeted toward CDMA mode and less so GSM. If you're a traveler or want to use your device with AT&T/T-Mobile, you'll want to install this patch which loads the AT&T ril onto your device. Without it, I couldn't receive any incoming calls and calls I placed couldn't be hung up (I would be stuck at the "hanging up" screen).

This patch is just two files (libril-qc-qmi-1.so and libril.so) pulled from the AT&T version (jflteatt) of CM11 (specifically, this version: https://download.cyanogenmod.org/get...2-jflteatt.zip).

I'm overseas right now, so I'm only able to test GSM mode, but it's working just fine for me now. If it's not enough for you, you might want to try the two other changes suggested here: https://jira.cyanogenmod.org/browse/CYAN-2362

To summarize, they are:

  • Set telephony.lteOnCdmaDevice=0 in /system/build.prop
  • loki_flash the jflteatt CWM with jfltevzw aboot - see here. Note that this is specific to MDK, so don't do this if you're on any other bootloader. Let me know if you want me to create a flashable version of this possible fix.

I didn't need to do either of these things to get it working for me, but you may need to do the first item if you want LTE (I'm currently in a country without LTE, so I can't test).

Flash this for GSM-optimized rils: (removed - broken)
Flash this to revert to CDMA-optimized rils: (removed - broken)

I see above that the flashable zip files were removed due to being broken. Are the ones attached good now? Also, these are AT&T files so will they work the same way with T-Mobile service since its fixing the issue with GSM and is not carrier specific?

If so, I'll give it a shot tonight. Thanks!
4th February 2014, 07:30 PM |#3  
OP Senior Member
Thanks Meter: 68
 
More
Quote:
Originally Posted by mbastats

I see above that the flashable zip files were removed due to being broken. Are the ones attached good now? Also, these are AT&T files so will they work the same way with T-Mobile service since its fixing the issue with GSM and is not carrier specific?

If so, I'll give it a shot tonight. Thanks!

No. Attached files are no-good; I've now removed them. I made a mistake in building the packages that'll likely brick your phone. I quickly removed the links while trying to fix my own device but forgot to remove the attachments. I'll repost when it's working properly.
4th February 2014, 07:50 PM |#4  
Junior Member
Flag Dallas, TX
Thanks Meter: 6
 
More
Quote:
Originally Posted by linuxthinker

No. Attached files are no-good; I've now removed them. I made a mistake in building the packages that'll likely brick your phone. I quickly removed the links while trying to fix my own device but forgot to remove the attachments. I'll repost when it's working properly.

Glad I didn't trust the files! I noticed that someone else in the same cyanogenmod ticket thread recommended an update to a line as a fix. On my mobile, or I would post a link. Thanks for trying to find a fix though!
4th February 2014, 08:32 PM |#5  
OP Senior Member
Thanks Meter: 68
 
More
Quote:
Originally Posted by mbastats

Glad I didn't trust the files! I noticed that someone else in the same cyanogenmod ticket thread recommended an update to a line as a fix. On my mobile, or I would post a link. Thanks for trying to find a fix though!

I just tried the fix in the CM thread - stuck in a segfault loop

Now that I've unbricked myself, I've updated the zip packages and they should be usable now.

Lesson learned: mount partitions by name whenever possible! I'm lucky I didn't blow away anything that I couldn't recover from. I was just unlucky that it was a partition not normally included in odin reset tars.
4th February 2014, 09:03 PM |#6  
Junior Member
Flag Dallas, TX
Thanks Meter: 6
 
More
Recap of how to
Quote:
Originally Posted by linuxthinker

I just tried the fix in the CM thread - stuck in a segfault loop

Now that I've unbricked myself, I've updated the zip packages and they should be usable now.

Lesson learned: mount partitions by name whenever possible! I'm lucky I didn't blow away anything that I couldn't recover from. I was just unlucky that it was a partition not normally included in odin reset tars.

So to recap how this is done, please correct me or agree.

If someone was installing CM 11 for the first time, they would:

1) Download the CM rom.
2) Download the GAPPS they prefer.
3) Download your 2 zip files for GSM ril provided in this thread.
4) Flash into recovery (assuming they had a custom recovery in place already)
5) Wipe data/cache/dalvik
6) Flash ROM, Gapps, and the 2 GSM ril zips you provided. (I prefer to flash Gapps after the first boot)
7) Reboot and watch it boot up.
8) Calls should work (assuming the correct apn settings are in place)

Agree?
4th February 2014, 10:53 PM |#7  
OP Senior Member
Thanks Meter: 68
 
More
Quote:
Originally Posted by mbastats

So to recap how this is done, please correct me or agree.

If someone was installing CM 11 for the first time, they would:

1) Download the CM rom.
2) Download the GAPPS they prefer.
3) Download your 2 zip files for GSM ril provided in this thread.
4) Flash into recovery (assuming they had a custom recovery in place already)
5) Wipe data/cache/dalvik
6) Flash ROM, Gapps, and the 2 GSM ril zips you provided. (I prefer to flash Gapps after the first boot)
7) Reboot and watch it boot up.
8) Calls should work (assuming the correct apn settings are in place)

Agree?

Almost!

(2) is optional and can be done later. There's no dependency here.
For (3), you only need the GSM flash package. The cdma package is provided if you want to revert.
For (4), a custom recovery is a given, since CM can't be flashed on the vzw s4 without it
For (6), flash only the GSM package.
For (8), calls should work even if APN settings are broken.

The two things to test for is:
1. After you've placed a call and are connected to the other party (i.e. the call timer starts ticking), you can successfully hang up.
2. You can receive an incoming call.

And to answer the carrier specificity question -- I'm testing this with Taiwan Mobile, so it's most definitely not carrier specific.
Last edited by linuxthinker; 4th February 2014 at 11:20 PM.
5th February 2014, 09:35 PM |#8  
Member
Thanks Meter: 1
 
More
I guess this would have to be re-flashed after each nightly update that is applied?
5th February 2014, 09:38 PM |#9  
OP Senior Member
Thanks Meter: 68
 
More
Quote:
Originally Posted by canaanp

I guess this would have to be re-flashed after each nightly update that is applied?

I haven't worked with nightlies, but I suspect the answer is yes since nightlies are full images and not deltas.

Sent from my Nexus 7
5th February 2014, 10:05 PM |#10  
Member
Thanks Meter: 1
 
More
I just tested with a fresh install of the 2/5 nightly. I wanna have your baby. Works perfectly, thank you!
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes