[DEV] GSM phone calls on Nexus 7 3G

[Shinj1EVA]

This won't boot after flashing here - I'm stuck at the CM circling...

Strange. I flashed it yesterday before sending you the link, and it boot up fine. I did use the Grouper CWM and removed the assert line from the updater-script, but I doubt that would keep it from booting...

 

[TinTin]

Strange. I flashed it yesterday before sending you the link, and it boot up fine. I did use the Grouper CWM and removed the assert line from the updater-script, but I doubt that would keep it from booting...

I had to remove the assert line too, it was still in the version you sent me (else it wouldn't flash). I used grouper CWM 6.0.19

[Edit]
Reflashed with TWRP 2.3.1.2 but still not booting :\

 

[Shinj1EVA]

I had to remove the assert line too, it was still in the version you sent me (else it wouldn't flash). I used grouper CWM 6.0.19

[Edit]
Reflashed with TWRP 2.3.1.2 but still not booting :\

No point.. I grabbed a SIM card. Mobile data does work, and Phone.apk and Mms.apk are built. Messaging does send/receive text messages, but that's already been confirmed. However, I have been unable to dial a phone number

Well at the very least, MMS isn't crashing the Texting app.. That's an improvement.

 

[kRt_uK]

No point.. I grabbed a SIM card. Mobile data does work, and Phone.apk and Mms.apk are built. Messaging does send/receive text messages, but that's already been confirmed. However, I have been unable to dial a phone number

Well at the very least, MMS isn't crashing the Texting app.. That's an improvement.

MMS doesn't crash the app, but actually doesn't send MMS too, does it?
When you say, unable to dial a phone number, do you mean "unable to complete the call" or literally dial on the dial pad?

 

[Shinj1EVA]

MMS doesn't crash the app, but actually doesn't send MMS too, does it?
When you say, unable to dial a phone number, do you mean "unable to complete the call" or literally dial on the dial pad?

Can't complete a call.. well still same choices as earlier with Mobile Data and Skype.
It seems to receive MMS okay, but doesn't want to send. Maybe I'm just being impatient. I'll write back if it does successfully send.

On another note, I noticed my build doesn't actually include android.hardware.telephony.gsm.xml. Any idea on where to look to enable it?

[Edit]
Correction, the MMS does send

 

[kRt_uK]

Did you setup the mms proxy and mms port for your carrier at settings - mobile network - apns? Or it isn't needed?
-------------
Cool!!!

 

[kRt_uK]

Can't complete a call.. well still same choices as earlier with Mobile Data and Skype.
It seems to receive MMS okay, but doesn't want to send. Maybe I'm just being impatient. I'll write back if it does successfully send.

On another note, I noticed my build doesn't actually include android.hardware.telephony.gsm.xml. Any idea on where to look to enable it?

[Edit]
Correction, the MMS does send

Is this file you requested?
http://forum.xda-developers.com/showthread.php?p=34233312

 

[Shinj1EVA]

Is this file you requested?
http://forum.xda-developers.com/showthread.php?p=34233312

Yes, I found it in the cm source. I added it to be copied in the device.mk file, one of the developers actually removed the line.

As for the MMS, I didn't have to do anything special, just popped in the cellcom SIM and it worked. Same with the orange SIM.

 

[Shinj1EVA]

One more thing to try, change the PRODUCT_CHARACTERISTICS in build.prop to not indicate tablet. It seems that Phone.apk and TelephonyProvider.apk depend on this, at least for labeling.

PRODUCT_CHARACTERISTICS := tablet, nosdcard

PRODUCT_CHARACTERISTICS := nosdcard

This is from packages/providers/TelephonyProvider/res/values/strings.xml

    <!-- Official label of the TelephonyProvider, as seen in the "Manage
         Applications" UI.  This is the version of the label for tablet
         devices, where the TelephonyProvider stores configuration info
         about the mobile data network. [CHAR LIMIT=40] -->
    <string name="app_label" product="tablet">Mobile Network Configuration</string>

    <!-- Official label of the TelephonyProvider, as seen in the "Manage
         Applications" UI.  The TelephonyProvider stores configuration
         info about the carrier and cell network, and also provides
         storage for SMS and MMS messages. [CHAR LIMIT=25] -->
    <string name="app_label" product="default">Phone/Messaging Storage</string>

So I think it builds differently based on the product characteristics. Can someone confirm this? Either way, I'm going to try a clean build with this in a bit.

 

[Synman]

Hate to state the obvious but we should be focusing on a base build first, as is, with the grouper drivers.

Flash and verify.

Add maguro (or other gsm driver)

Rebuild

Flash and verify.

Add build tweak

Flash and Verify.

That's the mode I'm in.

I know tilapia can take a grouper build as I've done it myself... You just lose gsm.

So at this rate I'll likely have something in a week

Sent from my Galaxy Nexus using Tapatalk 2

 

[Shinj1EVA]

Hate to state the obvious but we should be focusing on a base build first, as is, with the grouper drivers.

The grouper drivers will be the same as the tilapia drivers, only one we're missing is the GSM driver. The hardware is identical otherwise. Did you try extracting the radio driver from the 4.2.1 system image? I have libxgold-ril.so in my CM directory and the GSM network is working fine. I just can't get Phone.apk to make any calls successfully at this point... but at least it says Phone instead of Mobile Data now.. small, pointless, cosmetic step.... I only replaced Phone.apk and TelephonyProvider.apk instead of flashing the whole build. Downloading and going to try to flash the whole system in a bit.. or tomorrow. The internet at this hotel is ridiculously slow.

To be honest, I have no working knowledge of AOSP. I just stated poking around with this a few days ago.

 

[Synman]

I'm done with framework hacks for a framework intentionally gimped.

We are close!

Sent from my Galaxy Nexus using Tapatalk 2

 

[Synman]

tilapia w/ grouper drivers builds but immediately segfaults on boot.

grouper /w grouper drivers builds and boots fine.

rebuilding grouper now with rild, base-telephony and tilapia init.rc

Will sideload libxgold-ril.so once I get a clean boot. Are there any other shared and/or static libraries, resources, etc anyone can think of I might need to get radio to light up?

 

[Synman]

got a clean build and deploy with telephony-full ... now to get the radio turned on

 

[Synman]

time to make the donuts (real job)... will pick this back up tonight.

Have full telephony and mms ... boots like a dream up until the point ConnectivityStatus changes. Looks like a kernel panic and reboot. put grouper in airplane mode and it stays up. looks like i'm missing something with ril

Made some build.prop changes, etc... doing another full build now

12-05 12:11:05.263: E/AndroidRuntime(23090): *** FATAL EXCEPTION IN SYSTEM PROCESS: NetworkPolicy
12-05 12:11:05.263: E/AndroidRuntime(23090): java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE_IMMEDIATE flg=0x8000010 (has extras) } in [email protected]
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:768)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.os.Handler.handleCallback(Handler.java:725)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.os.Handler.dispatchMessage(Handler.java:92)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.os.Looper.loop(Looper.java:137)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.os.HandlerThread.run(HandlerThread.java:60)
12-05 12:11:05.263: E/AndroidRuntime(23090): Caused by: java.lang.ArrayIndexOutOfBoundsException: length=12; index=-1
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.text.format.Time.getActualMaximum(Time.java:239)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.net.NetworkPolicyManager.snapToCycleDay(NetworkPolicyManager.java:222)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.net.NetworkPolicyManager.computeLastCycleBoundary(NetworkPolicyManager.java:179)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at com.android.server.net.NetworkPolicyManagerService.updateNetworkRulesLocked(NetworkPolicyManagerService.java:1031)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at com.android.server.net.NetworkPolicyManagerService.addNetworkPolicyLocked(NetworkPolicyManagerService.java:1461)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at com.android.server.net.NetworkPolicyManagerService.ensureActiveMobilePolicyLocked(NetworkPolicyManagerService.java:1139)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at com.android.server.net.NetworkPolicyManagerService.access$1500(NetworkPolicyManagerService.java:170)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at com.android.server.net.NetworkPolicyManagerService$12.onReceive(NetworkPolicyManagerService.java:901)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:758)
12-05 12:11:05.263: E/AndroidRuntime(23090): 	... 4 more

 

[Synman]

Also, need some discussion on:

Are there any other shared and/or static libraries, resources, etc anyone can think of I might need to get radio to light up?

 

[TinTin]

Synman,

concerning the networkpolicy have a look at AndroidManifest.xml, check if the proper permissions for telephony, sms etc. are in there, maybe compare with Maguro or Mako.

 

[Synman]

I'm sourcing the tilapia overlay with the gsm permission and voice_enabled options set. I did have a blank apns file and have corrected that.

 

[Synman]

should add that immediately before the NetworkPolicy crash I got an NTP update and it looks like that's what caused the panic.

 

[Synman]

shutdown data and am able to maintain a gsm only connection.

outbound voice call still fails:

12-05 16:13:06.177: D/CallNotifier(19800): onDisconnect: cause = ERROR_UNSPECIFIED, incoming = false, date = 1354741985803

Will have to look into NetworkPolicy a bit deeper. The error above is being thrown because the N73G is passing in a null date to the whole data metering service for setting its time window.

Also need to look at network capabilities a bit as I'm getting some "back door" info that indicates I may be missing some carrier specific data.