• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ICS/CM9-JB/CM10 Development Thread

Just tried a crude hack to RIL.java that snarfs the net parameters from system properties instead of the SETUP_DATA_CALL response. It seems to be working. :D

Currently says 1x service but I don't know if that's real or not, and if it is real, whether it is due to poor service -- I am inside a building that has crappy cell service. But hey, at least we have bits flowing! :D
 
Craptorman said:
Awesome find!
Click to expand...

Thanks. But it's a hack to be sure. One visible consequence is that you get two default routes, presumably because pppd or rild adds it, and then the framework adds it again.

I need to investigate and ask around to see if there's a better and/or more standard way to handle PPP based data connections, because I don't see anything obvious in the CM9 RIL code. In the meantime, this should work.

I don't have time to build a fresh LS855 ROM today but I'll get one out in the morning with all these changes. The following are changes since last release:

* fixed BOOTCLASSPATH for gtalk
* ril/ppp fixes/hacks for 3G
* eri.xml fixed (Sprint version, not VM)
* qtaguid for network stats (just checked, it's working)
* init binary built from source
 
Oh, and if someone can get me the Boost configs, I'll make a Boost version too.

I will need:

* Model name (I think it's LG-LG855?)
* /system/build.prop (for operator.alpha and operator.numeric)
* apns-conf.xml
* eri.xml
* Framework overlay parameters for MMS (packages/apps/Mms/res/xml/mms_config.xml)
 
tdm said:
Oh, and if someone can get me the Boost configs, I'll make a Boost version too.

I will need:

* Model name (I think it's LG-LG855?)
* /system/build.prop (for operator.alpha and operator.numeric)
* apns-conf.xml
* eri.xml
* Framework overlay parameters for MMS (packages/apps/Mms/res/xml/mms_config.xml)
Click to expand...

Code: 
ro.product.model=LG-LG855

Code: 
ro.cdma.home.operator.alpha=Boost Mobile
ro.cdma.home.operator.subscriber=31000
ro.cdma.home.operator.numeric=311870
gsm.operator.alpha=Boost Mobile
gsm.operator.numeric=311870
gsm.sim.state=READY
gsm.operator.iso-country=us

this is the apns for the prevail's cm9:

Code: 
<apns version="7">
  <apn carrier="Boost_Mobile" mcc="310" mnc="00" apn="Boost_Mobile" user="Boost_Mobile" password="*" mmsc="http://mm.myboostmobile.com" mmsproxy="68.28.31.7" mmsport="80" type="" />
  <apn carrier="Boost_Mobile" mcc="311" mnc="870" apn="Boost_Mobile2" user="Boost_Mobile" password="*" mmsc="http://mm.myboostmobile.com" mmsproxy="68.28.31.7" mmsport="80" type="" />
</apns>

eri.xml should be the same for both sprint and boost but here it is: https://dl.dropbox.com/u/37768988/eri.xml

Code: 
<mms_config version="4">
    <bool name="enabledMMS">true</bool>
    <int name="maxMessageSize">1048576</int>
    <int name="maxImageHeight">960</int>
    <int name="maxImageWidth">1280</int>
    <int name="defaultSMSMessagesPerThread">200</int>
    <int name="defaultMMSMessagesPerThread">20</int>
    <int name="minMessageCountPerThread">2</int>
    <int name="maxMessageCountPerThread">5000</int>
    <bool name="enabledTransID">true</bool>
    <int name="recipientLimit">40</int>
    <int name="smsToMmsTextThreshold">4</int>
    <string name="uaProfTagName">Profile</string>
    <int name="countOfHighPriorityMessage">0</int>
</mms_config>

all this stuff can be changed after the roms already built tho, if you wanna just do a sprint one I can change it to boost for you if you want.
 
Played with 3g on the way home. It seems to reconnect after switching to wifi but won't receive data. Probably a dns or route error. I'll need to look into that of course.
 
tdm said:
Played with 3g on the way home. It seems to reconnect after switching to wifi but won't receive data. Probably a dns or route error. I'll need to look into that of course.
Click to expand...

that's the same issues thekraven had with cm9 earlier alpha builds for the optimus s. we would toggle airplane then toggle data to resolve issue. maybe kraven can provide some insight?
 
  • Like
Reactions: tdm
mkfryan said:
that's the same issues thekraven had with cm9 earlier alpha builds for the optimus s. we would toggle airplane then toggle data to resolve issue. maybe kraven can provide some insight?
Click to expand...

All they did to fix that was a simple build.prop edit. that would be awesome if it was a build.prop edit.. Great job though tdm, amazing progress
 
  • Like
Reactions: tdm
The LG pppd startup script needs to be executable but it's not by default. The stock LG init.rc does this with a chmod line, but I think that's ugly.

Anyone know how to hook into the edify generator to add set_perm() calls? There are many of them already, for things like ppp and bluetooth.

That seems to be the only remaining issue preventing 3G from working in a full build. I should have a release before 11am PDT.
 
@ tdm The rom your working on now is it cm9 or aosp? I know your gonna release both as you did with the ov. Just curious.
 
k28king1 said:
@ tdm The rom your working on now is it cm9 or aosp? I know your gonna release both as you did with the ov. Just curious.
Click to expand...

CM9 is the first -- the CM team generally leads in device functionality.

I'll work on AOKP next. Don't expect that to be too difficult (famous last words, right?)

Then I'll do AOSP last. Maybe after some other fixups and kernel work though. It's hard to justify much work on AOSP when there's broken stuff in the other builds.
 
Okay here we go. This is the LS855 version. I'll be posting LG855 and AS855 shortly.

This is intended to be released as alpha1.

Please verify the following works: phone, sms, wifi, bluetooth, etc.

Please verify 3G comes up at boot with wifi disabled. It is expected that switching from wifi to 3G will turn on 3G but no data will flow.

It is also expected that the camera app loads but the camera views are screwy (front camera is upside down, back camera is sideways(!) and colors are inverted/wonky).

Goo.im Downloads - Downloading quattrimus-LS855-cm9-alpha1.zip
 
Just verified the issue with 3G is routing. After 3G goes down and comes back up, there is no default route. Manually adding the default route shown in the radio log lets it work.
 
Poking around some more. Looks like Samsung implemented a similar thing to the Marquee, in that the 3G connection is driven by pppd instead of internally by rild (see SamsungRIL.java in the source). Unfortunately, the semantics are a bit different and Samsung has other vendor specific stuff that we probably don't want/need, so I will probably end up making a new RIL class.
 
You must log in or register to reply here.
Back
Top Bottom