• 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

Yea that's what I was think I just turn things off when I'm done. The rom is pretty stable just some apps crash but great progress has been made ^_^ awesome work man.
 
  • Like
Reactions: tdm
Question for TDM: Maybe I missed it but what carrier are you building this for? It says Virgin all over it and error on baseband.
 
Question for TDM: Maybe I missed it but what carrier are you building this for? It says Virgin all over it and error on baseband.

I build a version for myself that is for virgin, but the one I release should be for sprint. Anything you see that says virgin is an oversight.

And of course I'll do a boost version soon.
 
I build a version for myself that is for virgin, but the one I release should be for sprint. Anything you see that says virgin is an oversight.

And of course I'll do a boost version soon.

Sweet. I'm on Boost myself. This thing is a smooth running rom. Good work so far. I can't wait for a stable version to use as a daily driver.
 
If you take the eri.xml file from tdm's tree and edit it with your carrier, save it and then put it in your /data folder on your phone. Worked for me to change carrier from virgin to mine.
 
Just sent them to your email. One thing some people don't know is that you can rename a jar file extension to .apk and use apk manager to decompile/recompile them.

Okay got the file. Thanks!

This is decompiled to smali, which I gather is basically Java VM assembler or something similar.

Is there a way to convert smali to Java source code?
 
I build a version for myself that is for virgin, but the one I release should be for sprint. Anything you see that says virgin is an oversight.

And of course I'll do a boost version soon.

Sweet. I'm on Boost myself. This thing is a smooth running rom. Good work so far. I can't wait for a stable version to use as a daily driver.

I pretty sure that the majority of Marquee users in this section are on Boost. Matter of fact, I only know a couple of people in here that are on Sprint.:idea:

Hmmmm, now I'm wondering. I wonder what percentage of Sprint and Boost users are in this section. Hmmm, I might just start a thread to see.:D
 
Do it biker I'm on sprint curious to see how many on sprint also have terrible service with this phone or if its just my area in general. On 3g I'm LUCKY to get over 120k on sprints 3g
 
So I'm finding out more about RIL than I ever wanted.... sigh.

The SETUP_DATA_CALL request is failing for some reason. I noted that the command has 6 args with the stock rom and 7 args with ics, so I fixed that. The new code seems to be sending the exact same request as stock now, but still the same result. :mad: There must be some other message that is missing or incorrect, probably prior to SETUP_DATA_CALL.

Currently writing a Perl script to tear through strace data from rild and decode the messages passed back and forth. What fun! :rolleyes:
 
I pretty sure that the majority of Marquee users in this section are on Boost. Matter of fact, I only know a couple of people in here that are on Sprint.:idea:

Hmmmm, now I'm wondering. I wonder what percentage of Sprint and Boost users are in this section. Hmmm, I might just start a thread to see.:D

I second that. The sprint marquee community is very small. Most users here are on boost mobile. It would be better to build for boost before sprint than to port to sprint. I don't mean to knock on the sprint users just saying the boost user community is much much larger.
 
I pretty sure that the majority of Marquee users in this section are on Boost. Matter of fact, I only know a couple of people in here that are on Sprint.:idea:
Hey, don't go tryin to trump Boost's support over Sprint! :mad:;)

Really though, I've noticed a problem with the bottom buttons lighting up missed texts(calls?). When I receive a text the bottom lights up to notify, but when I unlock the phone to read the message the bottom lights go black and you can't see them.
 
I pretty sure that the majority of Marquee users in this section are on Boost. Matter of fact, I only know a couple of people in here that are on Sprint.:idea:

Hmmmm, now I'm wondering. I wonder what percentage of Sprint and Boost users are in this section. Hmmm, I might just start a thread to see.:D



LOL. That'd be interesting to see.
 
boost or sprint i don't care, it will work for both eventually and i am so glad i chose this phone as my first droid. all of you helping to develop this are amazing, even this test rom kicks some ass already. wish i could do more to help but you guys are light years ahead of me. one of these days though lol. keep up the good work men, we're all counting on you!
 
So there's nothing glaringly obvious in the RIL commands, except that the Sprint RIL.java is sending lots of proprietary messages. I'm hoping those aren't necessary.

I'm switching focus to the ppp setup, to see if maybe that is failing to init properly.
 
So there's nothing glaringly obvious in the RIL commands, except that the Sprint RIL.java is sending lots of proprietary messages. I'm hoping those aren't necessary.

I'm switching focus to the ppp setup, to see if maybe that is failing to init properly.

I work for my carrier, one of our engineer/tech guys is going to see what the phone is trying to authenticate with or not with etc. His guess was the rom is not getting the AAA keys from the phone that the tower needs. He's been busy but hopefully he'll get to it this week
 
  • Like
Reactions: tdm
Changing sprint to boost takes like 5 minutes anyway. It really doesn't matter which comes first

Yeah, I was just curious since I don't see that many people in here talking about them using Sprint. The thread I started confirmed my suspicions. This section is predominantly Boost. :D
 
Making some progress today.

I found a message in the kernel log that indicated rild was trying to start service pppd_gprs1 but didn't have permission. The service start permissions are hardcoded in the init source, and I don't see how to change that.

Additionally, I was mistaken when I said that my init binary worked before. So I was feeling pretty screwed.

Finally I tracked down the issue with my init. It was my own stupid mistake that caused it not to work. Protip: make sure your debugging code doesn't crash the program! ;)

Anyway, so I added permission for rild to start pppd_gprs1 and now pppd is launching. But it won't stay up, because there is some miscommunication and/or missing data in the SETUP_DATA_CALL response. The result is this in the radio log:

D/RILJ ( 1670): [0038]< SETUP_DATA_CALL DataCallState: {version=3 status=0 retry=-1 cid=0 active=0 type='' ifname='ppp0' addresses=[] dnses=[] gateways=[]}
D/CDMA ( 1670): [CdmaDC-1] DcActivatingState msg.what=EVENT_SETUP_DATA_CONNECTION_DONE
D/CDMA ( 1670): [CdmaDC-1] onSetupConnectionCompleted received DataCallState: DataCallState: {version=3 status=0 retry=-1 cid=0 active=0 type='' ifname='ppp0' addresses=[] dnses=[] gateways=[]}
D/GSM ( 1670): setLinkProperties: UnknownHostException java.net.UnknownHostException: no address for ifname=ppp0
D/RILC ( 1367): RIL onRequestComplete: free
D/CDMA ( 1670): [CdmaDCT] notifyOffApnsOfAvailability - reason= null
D/RILB ( 1670): getLteOnCdmaMode=0 curVal=-1 product_type='' lteOnCdmaProductType=''
D/CDMA ( 1670): [CdmaSST] getOtasp: state=3
D/GSM ( 1670): setLinkProperties: error clearing LinkProperties status=0 result=ERR_UnacceptableParameter SetupResult.mFailCause=NONE
D/CDMA ( 1670): [CdmaDC-1] updateLinkProperty failed : ERR_UnacceptableParameter SetupResult.mFailCause=NONE
D/CDMA ( 1670): [CdmaDC-1] DcActivatingState onSetupConnectionCompleted result=ERR_UnacceptableParameter SetupResult.mFailCause=NONE
D/CDMA ( 1670): [CdmaDC-1] tearDownData radio is on, call deactivateDataCall

But the main log clearly shows that pppd is firing up properly:

I/pppd ( 2686): Starting pppd for cid=1
I/pppd ( 2688): pppd options in effect:
I/pppd ( 2688): debug # (from command line)
I/pppd ( 2688): nodetach # (from command line)
I/pppd ( 2688): connect-delay 10000 # (from command line)
I/pppd ( 2688): dump # (from command line)
I/pppd ( 2688): /dev/pts4 # (from command line)
I/pppd ( 2688): 115200 # (from command line)
I/pppd ( 2688): mru 1472 # (from command line)
I/pppd ( 2688): mtu 1472 # (from command line)
I/pppd ( 2688): ipcp-accept-local # (from command line)
I/pppd ( 2688): ipcp-accept-remote # (from command line)
I/pppd ( 2688): ipparam 1 # (from command line)
I/pppd ( 2688): usepeerdns # (from command line)
D/pppd ( 2688): using channel 1
I/pppd ( 2688): Using interface ppp0
I/pppd ( 2688): Connect: ppp0 <--> /dev/pts4
D/pppd ( 2688): sent [LCP ConfReq id=0x1 <mru 1472> <asyncmap 0x0> <magic 0xe33e81f1> <pcomp> <accomp>]
D/pppd ( 2688): rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <magic 0x59b3685a> <pcomp> <accomp>]
D/pppd ( 2688): sent [LCP ConfAck id=0x0 <asyncmap 0x0> <magic 0x59b3685a> <pcomp> <accomp>]
D/pppd ( 2688): rcvd [LCP ConfRej id=0x1 <mru 1472>]
D/pppd ( 2688): sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0xe33e81f1> <pcomp> <accomp>]
D/pppd ( 2688): rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0xe33e81f1> <pcomp> <accomp>]
D/pppd ( 2688): sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
D/pppd ( 2688): sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
D/pppd ( 2688): rcvd [LCP DiscReq id=0x2 magic=0x59b3685a]
D/pppd ( 2688): rcvd [IPCP ConfReq id=0x0 <addr 66.1.0.193>]
D/pppd ( 2688): sent [IPCP ConfAck id=0x0 <addr 66.1.0.193>]
D/pppd ( 2688): rcvd [LCP ProtRej id=0x3 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
D/pppd ( 2688): rcvd [IPCP ConfNak id=0x1 <addr 28.205.92.91> <ms-dns1 66.1.0.133> <ms-dns3 66.1.0.132>]
D/pppd ( 2688): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 28.205.92.91> <ms-dns1 66.1.0.133> <ms-dns3 66.1.0.132>]
D/pppd ( 2688): rcvd [IPCP ConfAck id=0x2 <compress VJ 0f 01> <addr 28.205.92.91> <ms-dns1 66.1.0.133> <ms-dns3 66.1.0.132>]
I/pppd ( 2688): local IP address 28.205.92.91
I/pppd ( 2688): remote IP address 66.1.0.193
I/pppd ( 2688): primary DNS address 66.1.0.133
I/pppd ( 2688): secondary DNS address 66.1.0.132
D/pppd ( 2688): Script /etc/ppp/ip-up started (pid 2697)
I/pppd ( 2713): ip_up: cid=1 iface=ppp0 ip=28.205.92.91 remote=66.1.0.193 dns1=66.1.0.133 dns2=66.1.0.132
D/pppd ( 2688): Script /etc/ppp/ip-up finished (pid 2697), status = 0x0
 
Back
Top Bottom