yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] eik:
Same here travelled by train today. Normally this is an almost guarantee for lockups. Today it was all ok.

Edit: one day later: the phone kept on running without freezing (normally I had like 3 freezes a day). I travelled to and from my work, normally a guarantee for at elast one and most of the time 2 or 3 lockups.

After running for 26 hours on Wistilt2 kernel and the latest ril I decided to charge the phone again (still 38% battery left!). So far everything functions perfectly. Thanks guys. Very well done!
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Using the latest RIL 391df1f, can't dial into my voice-mail again, CDMA Rhod400 Sprint.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Ah, that's too bad. You're going to need to use gdbserver to get a decoded stack trace if anyone is going to have a chance of debugging this. google "android gdbserver" if you're not familiar with it. If you've never used gdb before, this may be more difficult than you can deal with.

Apparently you either can't read or just suck at following instructions. Sucks to be you.
[Touch Pro2, Tilt 2 Android Development] xUmaRix:
yeah i know gdb.need to swtich to ubuntu.however i saw that my phone was mistakenly configure as CDMA instead of GSM.Thats's why the library keep crashing.After reboot i can see in logcat -b radio my phone is configured properly as GSM.So far after 3 hours on 3G data everything seems fine.
[Touch Pro2, Tilt 2 Android Development] muziling:
function killConn()

Sometimes when system("killall pppd"); phone reboot.

The code is killall pppd,then send ATH to disconnect?

Can send ATH to disconnect,then killall pppd?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
"Sometimes" means when?

Doing the ATH first will cause pppd to hang. That is in fact one of the main causes of hangs in the past.
[Touch Pro2, Tilt 2 Android Development] muziling:
I add some LOGD to debug:

Here is my sometimes log,

1. When 3g icon appear at the top banner, disable data connection, when 3g icon disapper ,enable data connection, repeat several times

2. When 3g icon appear, wait 5 seconds, disable,enable, when 3g icon appear, wait 10 seconds, disable, then phone reboot.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Nah, doesn't suck to be me, my lifes great, and I can read and follow instructions just fine but thanks for checking. And didn't think you'd need logs to see something that was previously happening and already fixed and now reappears... no biggee, I'm not the first or the last that you'll snap at on here... must suck to be so miserable day in and day out, just saying... ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Alright alright guys settle down.

The reason he snapped at you is you posted a comment that something is broken... with no logs. He needs logs if he's going to fix anything.

With that said, DTMF works perfectly fine for me on the newest RIL. Just tested voicemail - fish, are you set to CDMA or are you still in fake GSM? See the second post of this thread - if you didn't do this step, you're in fake GSM. You might need to be in CDMA mode for DTMF to work properly, I'm not exactly clear on how that all works.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Thanks arrrghhh, and I understand needing logs, but honestly didn't think they were needed at that point since it was something already reported, but I understand now that they are. Just don't see a need for the comments, but meh, it's Monday, it's not a biggee. I'm going to have to check in the phone how this one is set up, I've got it set using the test RIL and wistilts kernel without Jonpry's battery meter, and one set with jonpry's battery meter, and I do believe when this happened it was in fake GSM when it happened. I'll try it again later as it's set up right now and grab some logs and post them up.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Lots of testing stuff flying around the forums nowadays lol. I would definitely confirm that you're actually in CDMA mode (see if netloc works :p) because DTMF might be hosed in fake GSM now - I guess I should test it, but I'd rather leave my phone in real CDMA mode rather than a fake anything if at all possible ;).
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Just checked, it is still in fake GSM that I'm running. I'll just go back to running the stock build with wistilts test kernel and play around with different radios and the airave. I tried looking into the thread about setting the APN but I'm clearly not advanced enough at this point so I won't bother any more on that.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
If fake GSM mode is hosed now that also means that running a worldphone in GSM mode is also hosed, since they use the same RIL commands. But apparently that doesn't matter, since no one has mentioned it here.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not many use the CDMA devices as GSM, and those that do seem to mostly be those who are not so tech-savvy. I've been trying to get those guys to help out more, as there is a pretty serious show-stopping bug related to the radio turning off when the screen turns off in the newest kernels... but I haven't had much help from their end.

I'm thinking more and more I need to swipe a SIM from a friend and try to resolve this myself... Or at least pinpoint the problem, as I don't think anyone knows the exact issue is. If I do, I'll let you know - I should be able to help address this DTMF issue as well.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You should always use "-v time" to get your logs, like it says in the directions in the 1st and 2nd posts of this thread.

Search through your log for the "Call End" messages. Notice that they occur every time your data call ends. At the end of your log, notice that it occurs twice - once before your killall command executed. This tells me that your network connection is poor and the data connection was in the process of disconnecting already, before you Disabled it. It's hard to tell though.

To know for sure, you should obtain the regular logcat at the same time. (Again, just like it says in the directions.) Also, make sure your logs start from the actual bootup of the phone. Don't trim off the beginning, there's important information about the network state there that is missing from the file you attached here.

I state very clearly what is needed. Don't "try to be helpful" and trim it down to just the part you think is relevant. You will usually be wrong and some important detail will be missing. Get the whole thing.
[Touch Pro2, Tilt 2 Android Development] mizofizo:
Hey, saw my name pop up on the IRC logs. You need another rilspy log testing call waiting?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Maybe. Have a test going with arrrghhh right now, if it fails then we'll probably need the log. Don't know yet. Thanks!
[Touch Pro2, Tilt 2 Android Development] muziling:
Sorry , I attach new log:

This GENERIC_FAILURE maybe at_send_command("ATH", &p_response) return fail.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The GENERIC_FAILURE can be ignored. It is interpreting the NO CARRIER (numeric code 3) response from the hangup command as an error code, but obviously it is a success in this case since that is the expected result for a hangup command.

Again, your crash cannot be diagnosed without both the radio log and the regular log, obtained simultaneously. Your zip file only contained a radio log.
[Touch Pro2, Tilt 2 Android Development] muziling:
I did this to obtain logs, wrong?

adb logcat -v time -b radio > x:\111.log

Catch an adb logcat >x:\222.log soon later.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
adb logcat -v time

adb logcat -v time -b radio

This is already stated in the first post. And repeated over and over in the rest of this thread.

Without timestamps in both log files it is impossible to correlate the events from one file to the other.
[Touch Pro2, Tilt 2 Android Development] muziling:
My fault.....new logs with time
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Hm. The pattern that was in your previous logs didn't occur in these logs, so I don't have any other ideas. But since you're using gingerbread, and there are many other instabilities in that still, it could be something completely unrelated to the ril.

My only other suggestion is to try the files in post#6, since they no longer use killall to stop the pppd, and the /system/bin/pppd that they use is actually native to gingerbread. (Nobody I talked to remembers where the /bin/pppd in the rootfs came from originally. It is rather old.)
[Touch Pro2, Tilt 2 Android Development] muziling:
Do with post #6, problem still happend.

new logs:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Still not seeing anything obviously wrong. Updated anyway to check for the NO CARRIER result code in killConn, so at least that should be cleaner now. (Try either post#6 or #1, both are updated.)

I also noticed that your carrier supports TCP/IP header compression. Mine didn't, so I left "novj novjccomp" in the pppd options, but it would probably be better for you to enable them. Delete these keywords from your init.(froyo|gingerbread).rc ...
[Touch Pro2, Tilt 2 Android Development] toadlife:
Phone hung, but I'm not sure if it was a ril related or just a system freeze. Light was stuck on solid green and the freeze happened as I slid the keyboard out. I'll continue to take logs as I've gotten a few sods in the past week.

http://db.tt/g5m5Uwr
[Touch Pro2, Tilt 2 Android Development] muziling:
Replace ril, test again. Still cause reboot

12.zip is when I enter android, disable data connection, reboot.

34.zip is when I enter android, enable->disable->enable->disable...,reboot.

Maybe somewhere do an null point operation cause phone reboot.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Looks like the music player crashed on you. Nothing ril-related that I could see.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No obvious errors in these logs. A null pointer exception in the ril would only cause the rild to crash, we've had those in the past. To make the phone reboot to Windows would usually require a hardware error or kernel bug. Perhaps you need to look at dmesg / klogd output.
[Touch Pro2, Tilt 2 Android Development] muziling:
Oops...some one told me back to previous kernel, no reboot again.

Do some feedback to arrrghhh :)

I try old kernel... still...

ril back to version 5297d81(April ,5) seems much better than newest.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
If I switch wifi off, I have no 3G or G data connection until I switch airplane mode on and off.

Maybe this log can help.

(ril-391df1f)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The log only shows that you enabled and disabled data several times. Each time you enabled data, it connected successfully. A minute later you disabled it, also successfully.

If there's any problem with the data connection, it is not in the ril.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have not seen G E or 3G Symbol, when I have switched off the wlan.

Now with the new ril-3cdf593, i have directy a GSM-Data-symbol and it is working. Don´t know why.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Tried to search thread but found nothing...is it a known issue to have static coming from external speaker when doing "non-speakerphone" calls? I am using CDMA mode on Rhod400...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
It's a known issue that in-call audio is screwed up, in general, and the external speaker tends to come on by itself at all sorts of odd times.
[Touch Pro2, Tilt 2 Android Development] kastg1:
A quick question about the recent updates to the RIL -- for CDMA phones, do these updates (such as the one above) only apply when you are in CDMA mode (as opposed to the fake GSM mode)?
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Have you tried waiting? It does take a little bit of time for data to come up.

I have had occasional times where data didn't come up unless I disabled/reenabled it, unfortunately I didn't have logs running and it's fairly rare. (And usually, wifi was hosed at the point I disabled it, which is why I disabled it.) I avoided mentioning it because I didn't yet have logs.

Also, the data connection may not come up until something causes it to come up - try opening Maps.

Edit: Regarding static and in-call audio, audio routing is known to be non-perfect, and is more of a kernel thing than a RIL thing as far as I can tell.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Phone totally borked itself in the last hour or two. Noticed at first that data would not come up after disabling wifi. Tried making a call....nothing. tried switching to airplane mode...nothing.

Logs....

http://db.tt/1NZ77df
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed. jb is supposed to be cleaning this up, not sure if he's pushed any commits yet in this space (AFAIK not yet...)
[Touch Pro2, Tilt 2 Android Development] rcgators:
The fixes here for both. The ones late last week and into the weekend helped GSM cosiderably. :D
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Your pppd hung while you were in an area with a weak signal. I think you need to patch your ppp options file, as outlined in this thread. (Note that the corresponding changes are already present in my patched rootfs files.)
[Touch Pro2, Tilt 2 Android Development] toadlife:
Yeah, my office is a metal building with no Windows and a signal repeater that doesn't work very well. A good testing ground.

Thanks, I'll look into that thread.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I'm currently using the RIL posted yesterday morning. On some previous versions, I've been very happy with the stability of the connection - seeing a green signal status makes me smile!

On the last couple I've tried it doesn't seem to have been as good. In particular, they don't seem to be able to get a data connection after going through an area with no signal at all (the London Underground).

The symptoms are a G or 3G icon appears (and changes according to area), and OS monitor shows me that the ppp0 has an IP address. But the signal and 3G are white (I'm on gingerbread), and I don't have data. If I turn off data or go through airplane mode, the signal indicator behaves appropriately, but the ppp0 is never dropped according to OS Monitor. And when it comes back, I can't access data.

I've attached my logs, but I'm not sure they seem to go back far enough - I ran the command as root in a connectbot shell and left it a for a minute before using ctrl-c, but looking at them they don't both start at the same point.

Apologies if I have not done this correctly!

rhod100_uk with AUO panel. Gingerbread GBX0A.
[Touch Pro2, Tilt 2 Android Development] toadlife:
My data hung a few minutes ago. Tried for 10 minutes to connect. Toggling airplane mode solved the problem. On the bright side, I've had no complete failures since switching to the custom rootfs you suggested.

Logs....

http://db.tt/2hX5xEz
[Touch Pro2, Tilt 2 Android Development] highlandsun:
My p7zip extractor couldn't do anything with your file.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Not sure if I'm doing it the "right" way either but how I log is with gscript light. I create a new script with the following lines....

nohup logcat -v time -b radio>/sdcard/logcat_time_radio.txt &
nohup logcat -v time >/sdcard/logcat_time.txt &

....and just execute the script right after I boot my phone. Right after the script launches, I close it and gscript and the two instances of logcat continue to run in the background until I kill it or the phone gets reset.

Not sure if the 'nohup' is needed but it works.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Hang

Had a hang (actually 3 but this time I had the logging running).

Log shows:

RIL implementation has returned an error where it must succeedcom.android.internal.telephony.CommandException: GENERIC_FAILURE

Both logs attached. Hope this helps!!

edit: Running RIL 3cdf593 2011-04-12
[Touch Pro2, Tilt 2 Android Development] rcgators:
nohup is not necessary, only the &.

That's essentially what I've been running. Except I added code at the start to delete the processes if already running and to archive off one copy of the log file. This way I can reset the log if it starts getting too big.

kill -9 $(pgrep logcat)
rm /sdcard/logr.1
rm /sdcard/logcat.1
cp /sdcard/logr.txt /sdcard/logr.1
cp /sdcard/logcat.txt /sdcard/logcat.1
rm /sdcard/logr.txt
rm /sdcard/logcat.txt
logcat -v time -b radio > /sdcard/logr.txt &
logcat -v time > /sdcard/logcat.txt &
ps
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I don't see any misbehaviors in the ril. I see several lines like this

04-13 14:36:15.840 D/GSM ( 1406): [GsmDataConnectionTracker] no DATAIN in a while; polling PDP

04-13 14:36:15.840 D/RILJ ( 1406): [3020]> DATA_CALL_LIST

which just tells me that the network wasn't talking.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You actually had a crashed ril. Fixed now.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Sweeeet!!:cool: You've helped make XDAndroid on TP2 reliable enough for every day use!!

Thank You!
[Touch Pro2, Tilt 2 Android Development] toadlife:
This has only happened at my office and today my coworker who has a G2 also had a few connection issues today, so perhaps it's a local tower issue.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Sorry for taking so long to reply to this one, been away for a bit.

I'm still getting static while the call is active on true CDMA mode on the most recent ril (7001de9). Static is present as soon as phone starts ringing, no need to dial any keys. I assume everyone else on CDMA is experiencing this as well?

On GBX, CDMA rhod400.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Yes - although I've been told here it is not a RIL problem...does it happen with the "stock" RIL?
[Touch Pro2, Tilt 2 Android Development] manekineko:
Nope, but stock RIL is running fake GSM. I don't believe this problem occurs with the latest RIL in fake GSM mode either.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I just got my invite for the Sprint/GV thing. Attempted to set up GV again (still dislikes using my Apps domain cred, long story), had it autoconfigure. Tried dialing VM, was told it isn't supported. Not sure where it pulled *86 from, but Sprint wants you to dial your own # when calling VM.

http://db.tt/vR3krZy

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, this is an audio routing problem with the kernel. I know jb is working on cleaning it up, in addition to fixing BT. Hopefully something from that madman arises soon, he's always got good things in store :D.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Would this not be more elegant as a gscript light script?

DATE=`date +%Y%m%d%H%M`

logcat -v time -b radio > /sdcard/logs/radio$DATE.txt &

logcat -v time > /sdcard/logs/logcat$DATE.txt &

You may still want to add the kill line in, and the logs folder would need to be there.

Note those are backticks (`)on the first line, not single quotes ('). I have them on the FN SYM key on GBX0A/F22 rootfs. And the hour is GMT for some reason.

I'm currently running some new logs as per above and I'm about to go underground. Will post later assuming I don't get data back when I come out!
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Hopefully this time the zip file will work better than the 7z one did!

Booted phone, used it for a few minutes with data, indicators green, train went underground. Came up from underground, signal returned, but indicator is white and data doesn't work.

Turned off data, checked OS Monitor, ppp0 still listed with IP address.

Turned on data, 3G returns (white), no data.

Went to airplane mode, checked OS Monitor, ppp0 still listed with IP address.

Came out of airplane mode, 3G returns (white), not data.

As a side issue, recently my phone has been crashing (freeze with screen on generally) when I plug it into power (mains or PC). Not always, and I haven't isolated what triggers it. But that is probably kernel related so off topic in this thread! Oops!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
This is a stock ril. Nothing to see here, it's obviously hosed.

Please, sanity check your logs before wasting my time. The version is printed plainly at the beginning.
[Touch Pro2, Tilt 2 Android Development] Starfox:
This is what I put into my froyo.user.conf to support CDMA Dialing. The /tmp/build.prop is necessary because init firsts copies /system/build.prop to /tmp, fiddles with it, then binds /tmp/build.prop to /system, so it's not possible to edit build.prop from within Android. sed dislikes working on bound files, so that's the other reason I cat /tmp/build.prop. I added jit because my other Android system has no issues with it.

<snip - don't use>

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Last time I tried jit it caused Very Bad Things to happen. (as in crash crash bootloop crash crash...)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Thanks. That'll explain why all the good things I had come to expect from you RIL weren't working any more!

I did look at that for exactly the reason you suggest, but I didn't know what the stock ril reports and what your one reports. I could have looked at one someone else posted I suppose.

I'll go and work out why I'm no longer using your RIL.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
In addition, you seem to be on GB. The mountpoint for the RIL is different in GB IIRC, plus... there's the issue of data flakiness in general on GB - I don't think data flakiness is a RIL issue in GB's case. I don't see the same behavior on FRX06, and it would probably be best to test with that if you can. It's not a big deal if you don't want to, just might mean your testing is invalid because GB isn't stable :p.

Agreed... why are you enabling JIT Starfox?
[Touch Pro2, Tilt 2 Android Development] Starfox:
I do like to test stuff out, my data.img needed to be blown away anyway (too many crashes), worst case was for me to comment out the sed and waste a bit of time re-installing.

That being said, I think the phone is acting fine, and perhaps even faster with JIT. I know there is an issue with certain multimedia with it enabled, but I don't use this for that and I haven't come across any showstoppers so far.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] snalbansed:
I had been having a very good experience with data on GB with highlandsun's RIL, so I will persevere. Just need to get it working again!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fair enough :p. Perhaps I need to test this new RIL on GB... been a while since I've played with GB. I know, shame on me haha.
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
Really long logs

So...running the "worldphone" ril updates my phone decided it didn't like being a CDMA phone and switched to GSM then proceeded to dump a CRAPTON of loglines. Since it wouldn't pastebin here it is!
[Touch Pro2, Tilt 2 Android Development] mizofizo:
I went to update today and noticed all of the CDMA changes which have caused my brain to fail. :confused:

I understand how to edit the build.prop and how to add the files from the rootnew.zip archive. However, I haven't done anything with git and patching so I'm stuck. I want to keep using F22's rootfs but doing the patching of the init myself is beyond my skills. Anyone care to help me out?

I know that technically if I can't do it myself, I probably shouldn't be messing around with this new ril but I've been fine up until now and I want to keep up with the latest stuff to help out with testing.

Thanks!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I may look at this later. F22 said he'll be pulling in my changes also, so it may not be an issue for very long.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That edit to /system/build.prop can't be done within Android anyway; the default_network setting only takes effect on a fresh data.img. Pretty sure I already said that.

I'll add the note about /etc/default.prop.