How to set CDMA APNs with new more stable ril - Touch Pro2, Tilt 2 Android General

See post #20 , highlandsun resolved this.
I decide to create an new thread for APNs setting, just search for many help.
Thanks to highlandsun, the ril is great.
RIL link : http://forum.xda-developers.com/showthread.php?t=1009112
Android I run: **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Put apns-conf.xml in /system/etc, go to mobile network -> APN, menu key, reset to default, system will load the APNs from apns-conf.xml and add APNs which match your carrier's operator ID.
After enable data connection, android seems not pass selected APN's info to ril (such as APN name,user,password)
D/RIL ( 1422): requesting data connection to APN '(null)'
Click to expand...
Click to collapse
APN got null value from system, then use default user/password to connect(default is dummy/dummy). So if user/password is not dummy/dummy, data connection will not work.
The new ril handled MMS, we can set the correct APNs for MMS receive.

---

muziling said:
I decide to create an new thread for APNs setting, just search for many help.
Thanks to highlandsun, the ril is great.
RIL link : http://forum.xda-developers.com/showthread.php?t=1009112
Android I run: **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Put apns-conf.xml in /system/etc, go to mobile network -> APN, menu key, reset to default, system will load the APNs from apns-conf.xml and add APNs which match your carrier's operator ID.
After enable data connection, android seems not pass selected APN's info to ril (such as APN name,user,password)
APN got null value from system, then use default user/password to connect(default is dummy/dummy). So if user/password is not dummy/dummy, data connection will not work.
The new ril handled MMS, we can set the correct APNs for MMS receive.
Click to expand...
Click to collapse
I appreciate the info. I'm not sure how to merge it into the system file, hopefully somebody will come out with a build with the new RIL. (preferrable GB) or I'll just wait until it's committed.

---

I believe a simpler approach will be just to re-enable the APN Settings option in Phone Settings menu for CDMA phones. I don't have a CDMA phone to test this with, but something like this patch ought to do the trick:
Code:
diff --git a/res/xml/cdma_options.xml b/res/xml/cdma_options.xml
index 346674c..dfc9223 100644
--- a/res/xml/cdma_options.xml
+++ b/res/xml/cdma_options.xml
@@ -17,6 +17,17 @@
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:settings="http://schemas.android.com/apk/res/com.android.phone">
+ <PreferenceScreen
+ android:key="button_apn_key"
+ android:title="@string/apn_settings"
+ android:persistent="false">
+
+ <intent android:action="android.intent.action.MAIN"
+ android:targetPackage="com.android.settings"
+ android:targetClass="com.android.settings.ApnSettings" />
+
+ </PreferenceScreen>
+
<com.android.phone.CdmaRoamingListPreference
android:key="cdma_roaming_mode_key"
android:title="@string/cdma_system_select_title"
violino:/home/software/xdandroid/packages/apps/Phone>
(I literally just copied and pasted that out of the gsm_umts_options.xml file.)
Enabling this setting should make life easier for packaging, because then we don't need to worry about shipping with correct APN info pre-loaded for every carrier... But someone who can recompile the Phone app and run on CDMA will have to try this out and report back.

---

I must leave home now, I will try tonight, thanks .

---

I gave it a try with apk manager, but might have done it a little wrong. All I ended up with was a fatal error in MAIN when I clicked the wireless and networks button. Force Close. I'm not sure I should be jumping in this deep yet.

---

BoominSVX said:
I gave it a try with apk manager, but might have done it a little wrong. All I ended up with was a fatal error in MAIN when I clicked the wireless and networks button. Force Close. I'm not sure I should be jumping in this deep yet.
Click to expand...
Click to collapse
Yeah, looks like there's more to it than just that first patch. I'm still looking...
OK, since Phone.apk is a system app, it's not straightforward to just build a new one and drop it into place. The apps are cryptographically signed, and you need to have the same key on your build machine as was used to create it originally. I was running FRX06 and I don't have their release keys, so I replaced all of my /system with my own build of the Froyo tree. But even that wasn't enough, because /data/system still had records of the original keys. I found out about that here
http://forum.cyanogenmod.com/topic/3550-restoring-google-account-synchronization-after-upgrade/
After I did these edits on /data/system/packages.xml I was able to boot with my new system image (without first deleting all of my /data).
So here's the changes I made to the Phone.apk:
First, instead of leaving the APN setting in the GSM-specific options, I moved up to the generic Network Settings instead, so it can be used by both GSM and CDMA:
Code:
diff --git a/res/xml/gsm_umts_options.xml b/res/xml/gsm_umts_options.xml
index afdd0d3..25bc031 100644
--- a/res/xml/gsm_umts_options.xml
+++ b/res/xml/gsm_umts_options.xml
@@ -17,17 +17,6 @@
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:settings="http://schemas.android.com/apk/res/com.android.phone">
- <PreferenceScreen
- android:key="button_apn_key"
- android:title="@string/apn_settings"
- android:persistent="false">
-
- <intent android:action="android.intent.action.MAIN"
- android:targetPackage="com.android.settings"
- android:targetClass="com.android.settings.ApnSettings" />
-
- </PreferenceScreen>
-
<com.android.phone.Use2GOnlyCheckBoxPreference
android:key="button_prefer_2g_key"
android:title="@string/prefer_2g"
diff --git a/res/xml/network_setting.xml b/res/xml/network_setting.xml
index 5d70e67..f296d67 100644
--- a/res/xml/network_setting.xml
+++ b/res/xml/network_setting.xml
@@ -49,6 +49,17 @@
android:dialogTitle="@string/preferred_network_mode_dialogtitle" />
<PreferenceScreen
+ android:key="button_apn_key"
+ android:title="@string/apn_settings"
+ android:persistent="false">
+
+ <intent android:action="android.intent.action.MAIN"
+ android:targetPackage="com.android.settings"
+ android:targetClass="com.android.settings.ApnSettings" />
+
+ </PreferenceScreen>
+
+ <PreferenceScreen
android:key="gsm_umts_options_key"
android:title="@string/gsm_umts_options"
android:persistent="false">
Then I deleted the GSM-specific code that disables this menubutton when the phone is not GSM:
Code:
diff --git a/src/com/android/phone/GsmUmtsOptions.java b/src/com/android/phone/GsmUmtsOptions.java
index 48411f6..9fcf6f4 100644
--- a/src/com/android/phone/GsmUmtsOptions.java
+++ b/src/com/android/phone/GsmUmtsOptions.java
@@ -30,11 +30,9 @@ import com.android.internal.telephony.PhoneFactory;
*/
public class GsmUmtsOptions extends PreferenceActivity {
- private PreferenceScreen mButtonAPNExpand;
private PreferenceScreen mButtonOperatorSelectionExpand;
private CheckBoxPreference mButtonPrefer2g;
- private static final String BUTTON_APN_EXPAND_KEY = "button_apn_key";
private static final String BUTTON_OPERATOR_SELECTION_EXPAND_KEY = "button_carrier_sel_key";
private static final String BUTTON_PREFER_2G_KEY = "button_prefer_2g_key";
@@ -45,12 +43,10 @@ public class GsmUmtsOptions extends PreferenceActivity {
addPreferencesFromResource(R.xml.gsm_umts_options);
PreferenceScreen prefSet = getPreferenceScreen();
- mButtonAPNExpand = (PreferenceScreen) prefSet.findPreference(BUTTON_APN_EXPAND_KEY);
mButtonOperatorSelectionExpand =
(PreferenceScreen) prefSet.findPreference(BUTTON_OPERATOR_SELECTION_EXPAND_KEY);
mButtonPrefer2g = (CheckBoxPreference) prefSet.findPreference(BUTTON_PREFER_2G_KEY);
if (PhoneFactory.getDefaultPhone().getPhoneType() != Phone.PHONE_TYPE_GSM) {
- mButtonAPNExpand.setEnabled(false);
mButtonOperatorSelectionExpand.setEnabled(false);
mButtonPrefer2g.setEnabled(false);
}
The resulting phone.apk still works for me. I'm pretty sure it will work for CDMA too, but you either need to build it yourself, or one of the xdandroid dev team will have to give us a patched Phone.apk signed with their release key.

---

Specifically, you'll need to build the whole release yourself using the info at:
http://xdandroid.com/wiki/Getting_the_Source
I don't run CDMA so I can't test this even though I run self-build source builds.

---

Entropy512 said:
Specifically, you'll need to build the whole release yourself using the info at:
http://xdandroid.com/wiki/Getting_the_Source
I don't run CDMA so I can't test this even though I run self-build source builds.
Click to expand...
Click to collapse
That link is very outdated and I am having problems getting it to work, so far it has been about a month since I started trying to get it working. GingerBread will not compile doing what they say, I am about to try Froyo. Oh and I will be covering GSM only.

---

ryannathans said:
That link is very outdated and I am having problems getting it to work, so far it has been about a month since I started trying to get it working. GingerBread will not compile doing what they say, I am about to try Froyo. Oh and I will be covering GSM only.
Click to expand...
Click to collapse
I didn't realize there was a more up-to-date one...?
Those directions worked great for me on Froyo, I haven't tried since gb was released TBH...

---

ryannathans said:
That link is very outdated and I am having problems getting it to work, so far it has been about a month since I started trying to get it working. GingerBread will not compile doing what they say, I am about to try Froyo. Oh and I will be covering GSM only.
Click to expand...
Click to collapse
As far as I know the only differences for GB is it requires a 64bit OS and a different version of Java IIRC.

---

rpierce99 said:
As far as I know the only differences for GB is it requires a 64bit OS and a different version of Java IIRC.
Click to expand...
Click to collapse
Interestingly enough, the docs say java 1.5 is required to build froyo, but it looks like FRX was built with 1.6 anyway. So it should say "at least 1.5" (I thought it meant *only* 1.5...)
Sent from my MSM using Tapatalk

---

highlandsun said:
Interestingly enough, the docs say java 1.5 is required to build froyo, but it looks like FRX was built with 1.6 anyway. So it should say "at least 1.5" (I thought it meant *only* 1.5...)
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
I had sun-java6-jdk installed and it wouldn't compile, it said i needed java5 so i removed java6 jdk and installed sun-java5-jdk and it compiled sweet as.
Turns out parts of the page were outdated but I fixed them a while back and changes got approved, its all good now

---

what list?
muziling said:
Put apns-conf.xml in /system/etc
Click to expand...
Click to collapse
What apns-conf.xml? There's already one in there, but it doesn't have any CDMA stuff to match up?

---

NeoMatrixJR said:
What apns-conf.xml? There's already one in there, but it doesn't have any CDMA stuff to match up?
Click to expand...
Click to collapse
You don't need to do this at all...

---

Looking over the CDMA code in the android framework, this seems to have been a red herring. Currently the CDMA code doesn't ever send the username or password from the APN, it always sends NULL. It seems to assume that some CDMA provider's profile will be used to fill in the rest of the details. I don't know how to get hold of the CDMA profile though. It doesn't appear to be programmed into the radio firmware. Anyone know? On Winmo and Sense builds you'd use epst or somesuch.
Hmmm. I think the right way to solve this for XDAndroid is going to be to hack the CDMA code to use real APNs.

---

highlandsun said:
Looking over the CDMA code in the android framework, this seems to have been a red herring. Currently the CDMA code doesn't ever send the username or password from the APN, it always sends NULL. It seems to assume that some CDMA provider's profile will be used to fill in the rest of the details. I don't know how to get hold of the CDMA profile though. It doesn't appear to be programmed into the radio firmware. Anyone know? On Winmo and Sense builds you'd use epst or somesuch.
Hmmm. I think the right way to solve this for XDAndroid is going to be to hack the CDMA code to use real APNs.
Click to expand...
Click to collapse
I know BlackBerry phone not have APN, instead of set user/pass with QUALCOMM QPST or other similar.
So, there maybe some AT COMMAND can obtain user/pass which store at phone.

---

muziling said:
I know BlackBerry phone not have APN, instead of set user/pass with QUALCOMM QPST or other similar.
So, there maybe some AT COMMAND can obtain user/pass which store at phone.
Click to expand...
Click to collapse
I've been searching for those things but I don't believe it's worth the trouble. The fact is that for any data connection, you need the ability to set username, password, and MMS settings. All of these fields are already present in the APN database, so it's stupid to introduce a new tool to manage these somewhere else.
If you're using my modified Phone.apk and you've set your operator IDs correctly in your properties, the APN menu will work for you. So again, the tools are already built in to Android; no reason to use some other mechanism.
I've updated the framework to use the APN info for CDMA data connections now.
https://gitorious.org/xdandroid/frameworks_base/commit/e0fa513741f513476a0d17d1fd6236b23d7dec02
It's optional; if you don't setup an explicit APN everything will continue to work as before. But if you set one, it will get used.

---

Nice! More changes to figure out how to pull .

---

highlandsun said:
I've updated the framework to use the APN info for CDMA data connections now.
https://gitorious.org/xdandroid/frameworks_base/commit/e0fa513741f513476a0d17d1fd6236b23d7dec02
It's optional; if you don't setup an explicit APN everything will continue to work as before. But if you set one, it will get used.
Click to expand...
Click to collapse
Great, hope next release, both froyo and gingerbread have this function.

---

Patched binaries
Here's the updated framework.jar and Phone.apk with my patches to enable APNs in CDMA. (The attachment is named "framework.zip" because the forum doesn't allow attaching .jar files. Just rename it to framework.jar.)
I guess the easiest way to install this is adding a couple bind mounts in your user.conf. Personally I just mount the filesystem image read/write and replace the files directly, I don't like having so many bind mounted files.
The framework.jar file should be mounted over /system/framework/framework.jar. The Phone.apk gets mounted over /system/app/Phone.apk.
Remember to set your operator properties otherwise none of this will make any difference.
http://cleanimport.xda/index.php?posts/12401915/