Originally Posted by TinTin

Oh, nevermind. The Mako (Nexus 4) has the same values
0,0,0,-1,truefor "item" mobile in it's 4.2.1 config.xml, so this is not it I guess.

I found a thread elsewhere that could contain (parts) of the solution. Looking at the config.xml of the Mako (Nexus 4) and comparing it to the one of tilapia I see these parameters missing (line 40 ff.)

    <item>"mobile_mms,2,0,2,60000,true"</item>       
    <item>"mobile_fota,10,0,2,60000,true"</item>
    <item>"mobile_ims,11,0,2,60000,true"</item>
    <item>"mobile_cbs,12,0,2,60000,true"</item

Please someone try adding them to the string-array of network-attributes (I don't have the decompiler yet). They definitely should be there. This might not be all yet though.

Those values might be connected with Verizon APN settings.

System Infrastructure

APN Manager by 81 Square -- Has a list of APNs for USA, Canadian and European mobile operators, plus you can type in your own. I enabled Verizon Internet (choices are CBS, FOTA, IMS, Internet). No visible effect. Power cycled the phone. Didn't help.

http://www.math.ucla.edu/~jimc/moto-droid3/apps.shtml

They appear here, too.

http://pastebin.com/NFGMVi2a

Here are the relevant Galaxy Nexus maguro values:

    <string-array name="networkAttributes">
        <item>wifi,1,1,1,-1,true</item>
        <item>mobile,0,0,0,-1,true</item>
        <item>mobile_mms,2,0,2,60000,true</item>
        <item>mobile_supl,3,0,2,60000,true</item>
        <item>mobile_dun,4,0,3,60000,true</item>
        <item>mobile_hipri,5,0,3,60000,true</item>
        <item>mobile_bluetooth,7,7,1,-1,true</item>
        <item>ethernet,9,9,1,-1,true</item>
        <item>wifi_p2p,13,1,0,-1,true</item>
    </string-array>
    <integer-array name="config_protectedNetworks">
        <item>10</item>
        <item>11</item>
        <item>12</item>
    </integer-array>
    <string-array name="radioAttributes">
        <item>1,1</item>
        <item>0,1</item>
        <item>7,1</item>
        <item>9,1</item>
    </string-array>
    <integer-array name="config_data_usage_network_types">
        <item>0</item>
        <item>2</item>
        <item>3</item>
        <item>4</item>
        <item>5</item>
        <item>10</item>
        <item>11</item>
        <item>12</item>
    </integer-array>

I found out that neither device.mk nor full_tilapia.mk inherit from a telephony package (while the Mako (Nexus4) does through the following line in full_mako.mk:

$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)

This describes a similiar situation under ICS and the steps someone took to solve the problem,
this sounds like a promising way to me (The same things are missing in the Tilapia build):

http://groups.google.com/group/andro...28bb754b9ba18a

now all we need are the device binaries... c'mon google

Originally Posted by Synman

now all we need are the device binaries... c'mon google

i know, i shouldn't post here so feel free to delete my post, but are the device binaries something we just have to wait a little for google to release or are they closed source and we have to urge google to release them?
https://developers.google.com/android/nexus/drivers
only has the binaries for the grouper...
Someone wrote that the radio chipset is the same as for the galaxy nexus so shouldn't it be possible to use the gsm binaries from the galaxy nexus?

Originally Posted by punshkin

i know, i shouldn't post here so feel free to delete my post, but are the device binaries something we just have to wait a little for google to release or are they closed source and we have to urge google to release them?
https://developers.google.com/android/nexus/drivers
only has the binaries for the grouper...
Someone wrote that the radio chipset is the same as for the galaxy nexus so shouldn't it be possible to use the gsm binaries from the galaxy nexus?

we gotta learn somehow, right?

This is the page to watch: https://developers.google.com/android/nexus/drivers

just as soon as it hits we will be able to do our own full builds and device deploys right from the master source branch.

In the meantime I've made the change inheriting telelphony to my .mk file and am in the process of making to see what all changes. I lost a ton of time today doing a maguro build hoping to salvage something from it and ultimately coming up empty.

That same line is in the maguro build. Something that I noticed is that tliapia refers to $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk) unlike the phones.

Have also found this at the bottom of full_base.mk

# Get everything else from the parent package
$(call inherit-product, $(SRC_TARGET_DIR)/product/generic_no_telephony.mk)

full_base_telelphony.mk includes full_base + telephony and brings along some extra stuff for the ride such as carrier apns and voicedialer.

telelphony.mk includes Mms.apk

----

looks like that's just about everything. It's probably redundant to have both full_base_telelphony and full_base in tilapia's mk file. Probably better to just use full_base_telephony. At the very least have full_base_telephony referenced first -- comments indicate the earlier entries take precedence.

Originally Posted by Synman

looks like that's just about everything. It's probably redundant to have both full_base_telelphony and full_base in tilapia's mk file. Probably better to just use full_base_telephony. At the very least have full_base_telephony referenced first -- comments indicate the earlier entries take precedence.

Sounds good so far. Did you go the extra bit and try what else was mentioned in the post I linked to? Adding the extra parameters (see above) to the networkAttributes string-array and checking if telephony contains:

          PRODUCT_PACKAGES := \ 
 
             Contacts \ 
              ContactsProvider \ 
              Phone \ 
              TelephonyProvider \ 
              UserDictionaryProvider \ 
              Mms 
 
      PRODUCT_COPY_FILES := \ 
             development/data/etc/apns-conf.xml:system/etc/apns-conf.xml 
 
          PRODUCT_PROPERTY_OVERRIDES := \ 
             keyguard.no_require_sim=true \ 
             ro.com.android.dataroaming=true

-> Clean build and build freshly

Originally Posted by Synman

That same line is in the maguro build. Something that I noticed is that tliapia refers to $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base.mk) unlike the phones.

Right, that's because most of Tilapia derives from Grouper. You'll find the same there.