yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.

manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".

This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6 4).
[Touch Pro2, Tilt 2 Android Development] highlandsun:
OK, here's the current status before I leave for the weekend:

Currently the ril code sets a radio status of "SIM not ready" when the radio power is first turned on. The CDMA phone sees this and says "wtf, it's trying to use a GSM SIM card" so it kills itself to start the GSM phone code again.

So we need to be able to obtain the current operating mode in the ril so we can see, if we're trying to startup with network mode 6, it should use some other radio status code instead of the SIM-related codes.

Anyone who wants to dig into it and think about how to do that, please do...
[Touch Pro2, Tilt 2 Android Development] pdawg17:
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
It's only working well for GSM. Sounds like you should pass it by for now.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Request - for those of us following your source tree, when you upload a binary can you post which git revision that binary was built from? :)
[Touch Pro2, Tilt 2 Android Development] toadlife:
Thanks

Started running this last night when you posted it in the other thread. I'm GSM only (Rhod210) so I can't help with CDMA, but I've been the victim of what are probably RIL related bugs. In areas with bad signal and when switching between EDGE/GPRS/UMTS networks I've experienced a bug where the "phone" part of the phone starts going haywire. The first symptom is that the phone no longer responds to incoming calls. From that point on, I can receive one text message after which point I can no longer send or receive text messages nor can I make or receive calls. Switchiung to airplane mode doesn't fix the issue and a reboot is required.

I'm hoping you've accidentally fixed this bug too.
[Touch Pro2, Tilt 2 Android Development] blutruck:
Confirmed. Works well on my Tilt2. It seems that data speeds are better as well. Can't say for sure but will keep testing. Great work!!
[Touch Pro2, Tilt 2 Android Development] Raa_1:
For the less educated amongst everyone, what chance is there of making a quick kernel zImage for us to try out?

I can't use anything after Feb 28th or I get a home screen lock. :(
[Touch Pro2, Tilt 2 Android Development] Starfox:
The RIL is not a kernel module (.ko), but a loadable library (.so). This is why you need to use the mount command in froyo.conf.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Raa_1:
Ahhh okay, gotcha.

I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen? :)

The FAQ's don't seem to cover loading new modules! lol

Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.

If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/

Okay, found the conf file. Making the changes now! Must've been a late night. lol
[Touch Pro2, Tilt 2 Android Development] muziling:
problem still, logs below

6d5b27e_6.zip is network mode 6 's log, com.android.phone keep FC.

6d5b27e_0.zip is network mode 0 's log, when 3G enable, phone in, who call me will listen hang up audio ,and I can not accept and reject this call in my phone.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
That's odd - what build are you running, and how was it installed?

I know the conf file was included with the FRX05 full ZIP bundle (or was it the FRX04 bundle?)
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Thanks for that~

Can my log in pre post tell sth?
[Touch Pro2, Tilt 2 Android Development] nickleby:
Hi

I made 2 logs today, hope you (highlandsun) or arrrghhh can help me to solve my evdo issue...

The phone have the 3G icon, but I don't have internet :confused:

I've sent the password by mp

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I see the arrows are highlighted in both directions as well - as I stated previously, Metro is a horrible carrier that requires a proxy to access the internet. Have you set that up? If not, you won't be able to access the net at all, thanks to your sub-par carrier :p.
[Touch Pro2, Tilt 2 Android Development] nickleby:
My carrier is Movilnet (Venezuela) and it doesn't need a proxy to connect to the internet...As i said before, i just use #777, my user and password in windows mobile to connect. :confused::confused:

btw, i'm using the stock ril
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, I must've mixed you up for someone else, sorry 'bout that.

If you're using the stock RIL, why are you posting in this thread?

Someone else had an issue with that carrier, something about not being able to pass on the username/pass. I don't have a username/pass for my carrier - both are blank. Perhaps that's your problem as well.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Your logs shows that your username and password are fine, the authentication was successful. Whatever problem you're having seems to be specific to their network.

Since you're using the stock RIL, which has nothing to do with this thread, please ask your question somewhere else. This thread is for very specific testing of my code, not answers to random questions.

I googled around and found this thread which has relevant information

http://foros.cantv.net/forum_posts.asp?TID=72333
[Touch Pro2, Tilt 2 Android Development] nickleby:
I decided to try this new ril, but i can't set the apn!

Wireless& Networks-->Mobile networks:

-Data enabled

-Data roaming

-System select

I can't set a new apn because i don't have the option :confused::confused:

Edit: My phone shows "Roaming Indicator On" instead of my Carrier name...I have set ro.telephony.default_network = 4
[Touch Pro2, Tilt 2 Android Development] ryannathans:
regarding the issue that we discussed today, should those changes be applied to everyone? Would they benefit everyone? What is the deal there?
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I psuhed the new RIL straight into system/libs today replacing the old RIL. And I seem to be getting wayyyyyy better results, maybe this is because I also changed my build.

But I have a feeling its showing better coverage it used to in winmo :) which doesn't make sense . . . Maybe its a false reading or maybe I'm imagining it but eithar way its working awesome. (The reading may also be because of some framework editing . . .are there any xml files that need to be edited when changing status bar icons?) But I didn't get the usual SOD today so its working great here (gsm)

I also noticed there is no tutorial for directly replaces old ril with the new one in first post? Is there a reason for this? It seems to be working better if anything for me . . . Even though technically I don't see how there should be much difference between this method and the froyo.user.conf method :) (except I personally find it easier)
[Touch Pro2, Tilt 2 Android Development] Starfox:
The RSSI for CDMA was changed, so it's possible that you are just seeing the readjusted strength. I highly doubt you are actually getting better signal, except for the placebo effect of using something new.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The old signal strength stuff was off by miles. The new stuff is dead-on accurate, and has been confirmed by WisTilt2 using dedicated signal strength measurement gear.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
New ril posted now. It should never hang for this particular reason ever again. And the fix is helpful in general (for CDMA and GSM) for any other situations where pppd may be unable to establish a data connection.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
He's on GSM, and AFAIK there are frameworks issues with the signal strength on GSM - I could be wrong tho, lots of theories bouncing around lately lol..

hyc already responded, ignore me :p.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
That's awesome to hear! :D that more than likely is what I'm seeing, I noted signal switching in and out of android around my house and it seems to be about the same now. Much better than before :)

Also I was going to report a hang I just had. . . .but nvm, new ril ;) will push it right away. Also managed to get through the coverage 'danger zone' that is my old school today without a SOD, and even received a call and text so I'm 100% sure its working great in that sense. Its also switching from non-coverage back into coverage without getting stuck! Which used to be an issue I had with the first RILs.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I'm still not so sure about this - It seems like some signal strength reports are accurate, and others are not. I'm seeing WAY too many situations in which case the SS pegs and it never did in WinMo.

I haven't had a chance to look at this in detail though - but I often see five bars in places I know I don't in WinMo, and where HTCCSQ (the old method on GSM) is reporting three bars. Of course, "bars" i somewhat arbitrary, but it seems like HTCCSQ was more conservative in terms of not over-reporting signal strength to the user.

Note: The signal strength reporting in Settings-> About Phone may be fine, but the signal strength reporting on the status bar seems to still have issues. I think it might only happen when a location update (+Q3GNCELL) response comes in on 3G. I need to poke at it tonight.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The current code is using HTCCSQ. The signal strength returned by Q3GNCELL is ignored, since there's no simple formula to map it into CSQ.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Oh, so you changed that back. Yeah, looking at it now, I think it looks like it is no longer pegging like it did before.
[Touch Pro2, Tilt 2 Android Development] muziling:
Follow problem I encount today:

If file /etc/ppp/ppp-gprs.pid exists(maybe last boot abnormal shutdown) and pid file can be read, data connection will keep "goto error", so change to ?

killConn()

follow AT command seems always fail.

logs

something not supported
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I already know about this, there is an alternate version in my git repo that uses /system/bin/pppd instead of /bin/pppd and doesn't have this problem. I haven't posted it here because it requires patches to other parts of rootfs before you can use it.

No actually the ATH succeeded.

That's in the Phone.apk, not the RIL. Totally irrelevant.
[Touch Pro2, Tilt 2 Android Development] muziling:
No, not /bin/pppd, /system/bin/pppd problem, if file /etc/ppp/ppp-gprs.pid can be fopen and pppd process not exists, the while loop will always "goto error", and data connection will not establish ,until manual delete file /etc/ppp/ppp-gprs.pid
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You don't understand.

The current code uses /bin/pppd. The patch that I'm talking about uses /system/bin/pppd which does not create a ppp-gprs.pid file, so this bug does not occur there.

Trust me, I've been through all of this. If I tell you "this is so" it is *exactly* so.
[Touch Pro2, Tilt 2 Android Development] muziling:
Is the next version ,we will use /system/bin/pppd instead of /bin/pppd

So, next version, we can pass pppd user/pass by cmdline
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes.

Depending on when my patches get integrated in the xdandroid repo. I sent the merge requests a couple days ago.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Ironically, the problem that originally got me started in investigating the ril, the SoD with orange LED, has returned for me in the past couple days. I'm trying to get some logs to catch it in the act. It happened a couple times while I was driving around town with the phone on me. (Which is a first; up till now I have only used my TP2 at home.)
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Is this ril strictly rhod? If not what devices does this apply to?
[Touch Pro2, Tilt 2 Android Development] Starfox:
This should work with any MSM72xx 528mhz processor, incl. Diamond, Touch Pro, and Diamond2s.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] rcgators:
Same here but when I'm running logcat to capture something useful it hasn't failed. Don't know what changed that made it suddenly reappear.:confused:
[Touch Pro2, Tilt 2 Android Development] Entropy512:
I've had a few orange light hangs too.

Go figure, as usual - it only happens when I'm not running logcat!

I need to figure out a way to set up auto-logcatting on boot.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I live in a marginal service area and was someone who got 1-2 orange LED SoDs per day but since using your RIL 2 weeks ago (CDMA) I have had ZERO SoDs (even on newest a70 from yesterday)...I have had a couple of reboots to WinMo when wireless was on but I'm assuming that is due to something else...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Same here, it worked fine with the older ril, but I tried the latest at school today and also experienced SOD and another later. And a reboot. Sry no logs though,
[Touch Pro2, Tilt 2 Android Development] rcgators:
Did the next best thing...

downloaded gscript_lite from the market and added a script to kill any process named logcat, archive the log, and then start the logcat again.

2 presses and it's running.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Same here, just got my first SOD with orange LED couple of minutes ago. :(
[Touch Pro2, Tilt 2 Android Development] highlandsun:
And now I've just woken up and found everything working perfectly after 7 hours of standby. Just read thru 7 hours of utterly normal, boring logs. :p Oh well.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
well heading to the BLACK WHOLE, level B of my office. we will see if I get the Orange LED DEATH. crossing fingers.

will report back
[Touch Pro2, Tilt 2 Android Development] webxplore:
highlandsun, tried your RIL on sprint cdma tp2. Have a problem with tones. Tried accessing my voicemail and when prompted for password, used the dialpad to enter number and it did not work. Works fine with the ril removed. Any ideas for cdma?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I think you're running an old version, that bug was squashed a few days ago, download again from the first post and see if it works better.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Darn...same thing happened to me...had been running logs all day with everything running great...rebooted after making some changes and 10 minutes later had an orange LED SoD...this is on latest RIL...
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
feedback on the above, I did get the Orange LED non responsive phone. it went from blinking orange and green and stayed in orange and couldn't make it respond. :(

but other then that, the phone is sleeping well, I guess the device get's stuck when it looses signal or connection.
[Touch Pro2, Tilt 2 Android Development] webxplore:
I did download the latest one from the first post. Anything else that I can try. If it matters, I downloaded the latest FRX06, new data img and using the test kernel from 4/4. Works fine when I comment out the ril shared lib mount from froyo conf.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You can try exactly what it said in the 2nd post of this thread. Don't ask questions that already have answers posted; doing that gets you onto my Ignore list.

Doesn't matter, the ril behaves the same on FRX05 and FRX06.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I think I found the problem; the ril wasn't waiting for pppd to fully shutdown before returning from a DeactivateData request. So it was possible to request a new pppd session while the old one was still being torn down. Pretty sure this is fixed now.

If you've been following my git repos, you're probably seeing a large mess of commits just pushed out. I seem to have screwed up some rebases here and there. The actual changes from the last revision aren't nearly as big a deal as the number of commits would imply.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Without using this ril when you check the battery stats it tell you the ril is using loads of battery and is outta coverage aroung 50% of the time.

This was fixed with this ril.

But in the last 2 rils I tink it was its come back, installed latest and checked battery stats and ril has used 70% of battery used and was outta coverage 50% of the time (which it wasnt)
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Got a SoD today.

And i think it's RIL related, cuz in WinMo(after reset) i couldn't get a signal.

Is there something i can do after reset, logs or something?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No, there's no useful information after a reset.

By the way, please tell what version of the RIL you're talking about when you mention these problems, since it has changed quite rapidly in the past weeks.
[Touch Pro2, Tilt 2 Android Development] slobba:
Orange light SOD for me overnight. This occurred using ril d0e5a70. I wasn't able to get a dmesg but I was runnng a logcat on my Rhod110 GSM.

Thanks for all of your efforts highlandsun.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Locked up today while driving around. :( Using RIL from this morning bcbbc4f (4/9) and Test Kernel 4/4 on FRX06.

Both logs attached. Hope this helps!!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've gotten logs like this on my phone before as well. Pretty sure this was already fixed in the current ril.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've run into some lockups while driving around too. I believe the ril I just posted will take care of these, but I haven't gone out driving again yet to check.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Finally, another user with a rhod110! :p
[Touch Pro2, Tilt 2 Android Development] nickleby:
I think the latest ril is not detecting correctly my mnc and mcc :confused:

D/RILJ ( 1423): [0004]> OPERATOR

D/RILJ ( 1423): [0005]> REGISTRATION_STATE

D/RIL ( 1319): onRequest: OPERATOR (22)

D/RILJ ( 1423): [0004]< OPERATOR error: com.android.internal.telephony.CommandException: OP_NOT_ALLOWED_BEFORE_REG_NW

D/AT ( 1319): AT< $HTC_CSQ: 5,0

D/AT ( 1319): AT< $HTC_ERIIND: 0,0,1,0,0,0,0, Movilnet,1

D/AT ( 1319): AT< +CREG: 1

D/AT ( 1319): AT< +HTCCTZV: "11/04/10,02:30:55-18,0"

D/AT ( 1319): AT< $HTC_SYSTYPE: 2,2,1,0,3

D/AT ( 1319): AT> AT+HTC_BSINFO?

D/AT ( 1319): AT< +HTC_BSINFO: 31488,0,269,+151364,+963604,-61,"11/04/10,02:30:56-18,0"

D/AT ( 1319): AT< 0

D/RILJ ( 1423): [0005]< REGISTRATION_STATE {1, null, null, 6, 269, 151364, 963604, 1, 31488, 0, 128, 1, 0, -1}

D/RILJ ( 1423): [0007]> OPERATOR

D/AT ( 1319): AT< 0

I/RIL ( 1319): Calls=0,Valid=0

D/RIL ( 1319): onRequest: OPERATOR (22)

D/AT ( 1319): AT> AT+HTC_SRV_STATUS?

D/AT ( 1319): AT< +HTC_SRV_STATUS: 0,2,"1023127"

D/AT ( 1319): AT< $HTC_ERIIND: 0,0,1,0,0,0,0, Movilnet,1

D/RILJ ( 1423): [0007]< OPERATOR {Movilnet, Movilnet, 1023127, null}

D/RILJ ( 1423): [0009]> RIL_REQUEST_CDMA_SUBSCRIPTION

D/RIL ( 1319): onRequest: REGISTRATION_STATE (20)

D/AT ( 1319): AT> AT+HTC_GETSYSTYPE=0

My carrier (Movilnet) should be 73406, not 1023127

Btw, what should i need to edit on "eri.xml" to have the correct carrier name on the screen instead "roaming indicator on" ?

E/CDMA ( 1423): ERI defRoamInd 0 not found in ERI file ...on

E/CDMA ( 1423): ERI defRoamInd 0 not found in ERI file ...on

D/CDMA ( 1423): [CdmaServiceStateTracker] Set CDMA Roaming Indicator to: 128. mCdmaRoaming = false, isPrlLoaded = true. namMatch = true , mIsInPrl = true, mRoamingIndicator = 128, mDefaultRoamingIndicator= 0

D/CDMA ( 1423): [CdmaServiceStateTracker] Poll ServiceState done: oldSS=[3 home null null null Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[0 home null Movilnet 1023127 EvDo rev. 0 CSS supported 0 31488RoamInd: 128DefRoamInd: 0EmergOnly: false]

E/CDMA ( 1423): ERI defRoamInd 0 not found in ERI file ...on
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The ril only reports what the radio reports. The radio reports what it received from the network. I can't explain this for you, you're going to have to find out what's going on by yourself. Your best bet is comparing the debug output from a native Android CDMA phone connected to your network. You can use the rilspy to help with that.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Worldphone support

I'm kinda curious to get started on dual-mode GSM/CDMA support, but this kind of work is awfully slow going without an actual phone to test with. Anyone got a rhod400 or rhod500 they'd be willing to loan to me for a week or two? I've already spent $110 on a CDMA Hero that I have no other use for aside from this testing. I don't want to sell it again right away, in case there's other details I need to debug later. And I don't feel like buying yet another phone right now. (My work table already has 4 phones lying on it most of the time...)

PM me if you can help, thanks.
[Touch Pro2, Tilt 2 Android Development] nickleby:
My carrier doesn't have a CDMA Android device, so I can't test "rilspy"

If the number "1023127" is reported by the radio/network, should I get the same number on WM right?

How can I see my MCC/MNC under Windows Mobile?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Why don't you ask that in one of the Windows-oriented forums? I don't use Windows - it boots up as far as Gen.Y and then I never see it again. You're really starting to piss me off with your off-topic questions.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Yeah! I forgot the Windows Mobile thread, my bad! ¬¬ And since I'm using "your" ril, I think I must post in this thread, because that issues could be related to "your" ril...I've verified and WM gives me the correct MCC/MNC

Btw, I managed to get working the internet on Android for my carrier...I've found the correct settings (you must modify something in the EPST). It must work with any carrier that uses and specific username and password for the internet and you don't even need to change the APN. PM me if someone is interested to know this conf, since I can't see the reason to post that in public!
[Touch Pro2, Tilt 2 Android Development] xi.lin:
http://code.google.com/p/cyanogenmod/wiki/APNlist

<apn carrier="Movilnet" mcc="734" mnc="06" apn="int.movilnet.com.ve" type="default,supl" />

<apn carrier="Movilnet MMS" mcc="734" mnc="06" apn="mm.movilnet.com.ve" mmsc="http://mms2.movilnet.com.ve/servlets/mms" mmsproxy="192.168.16.12" mmsport="8080" type="mms" />

I think sth like the apn setting numbers should no bother highlandsun any more.. Other things should be cared more.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I drove back again thru the area that I lost signal earlier today - no lockups. I think this one is finally resolved.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
i was using ril-d0e5a70
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I have a incoming call problem,when someone calls me,he gets busy..

using my custom build with latest ril from here,rild and other pieces from xdandroid..

attached there's logcat,the call has been done at 16:26-27

I'm on a diam100 gsm,carrier is wind...