yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] muziling:
libhtc_rilspy.c has one code:

h_lib=dlopen("/system/lib/libhtc_ril.so", 0);

but my rhod400 have not this file, so I think, it will fail to spy.

How to use:?

1. copy two file to /system/lib

2. edit /system/build.prop

#rild.libpath=/system/lib/libhtc_ril.so

rild.libpath=/system/lib/libhtc_rilspy.so

how to use this edit build.prop when I in android, seems value will be restore back when I reboot the android system.

Seems I can do this

mv /lib/froyo/libhtcgeneric-ril.so to /system/lib/libhtc_ril.so

mv build.prop to SD card and edit gingerbread.user.conf to bind build.prop
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The rilspy is only for use with the original HTC ril, which comes on native Android phones. If you don't have a native Android phone, then ignore this, it is not for you.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
OK, the git rev is now in the zip filename and also in the ril Version string.
[Touch Pro2, Tilt 2 Android Development] Raa_1:
Okay, I got it installed and modified my froyo config file. Booted and locked up again at the Home screen.

Is there a way I can tell it's actually using the new RIL driver?

Edit : It's definately loaded. But with the USB cable in it hasn't locked up. So i'm not sure what the problem is. :/
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Will do on my tb, can you pm me with instructions on how to implement?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Strange. Can you send me a logcat? With the USB cable in you can use "adb logcat -b radio" from your PC.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
highlandsun IS THE MAN! Just got a fix with CDMA network location on my Sprint Rhod400!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Gotta love it. I don't think GSM netloc is working well yet :P
[Touch Pro2, Tilt 2 Android Development] Raa_1:
I'll do it again tonight and do a log for you. I had another go last night and it didn't lock up. So maybe it's fixed itself. Either way, i'll zap you a log or two and you can let me know what you think.

It didn't go into full deep sleep though (green LED) at any stage. Not so worried about that yet.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
By the way, with this RIL and CDMA mode enabled, NITZ works like magic, say goodbye to ClockSync!
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Haven't been around much, but with the f904331 RIL, I had the following behavior:

One blinkengreen hang (no logs from that, sorry) at desk at work

Not long after, left work. Turned screen on in car, waited a bit and sig strength went to two bars, UI hung.

I held down power for a bit to try and turn the phone off (expecting failure), but:

The phone returned to the xdandroid bootanim

Once it got back to the launcher, it was stuck in "no service"

An interesting thing - at some point after the weird reset, I got a completely wacked NITZ that was about 10-15 minutes behind the actual time.

Logcat attached (phone num scrubbed out)
[Touch Pro2, Tilt 2 Android Development] muziling:
I set network = 4, adding "-h <sid>" to the rild, follow is my log.

signal strength icon is 0 level, may a call, has noise sound.

It's strange,I had added "-h <sid>"

# cat /init.cfg/init.froyo.rc|grep rild

cat /init.cfg/init.froyo.rc|grep rild

service ril-daemon /system/bin/rild -h 14136 -l /lib/froyo/libhtcgeneric-ril.so -- -d /dev/smd0

socket rild stream 660 root radio

socket rild-debug stream 660 radio system

but ps command result has no -h parameter

# ps

ps

PID USER VSZ STAT COMMAND

1399 1001 5472 S /system/bin/rild -l /lib/froyo/libhtcgeneric-ril.so -

Right top of lock sceen show "Enable Roaming Indicator"
[Touch Pro2, Tilt 2 Android Development] Starfox:
What is the correct NetID for Sprint? And as for the -h parm, you need to pass it to the .so, since rild woul have no idea what to do with it. I believe you need to put it after the "--" which tells it to pass any arguments after to the module.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Starfox:
I had problems with writing to /init.cfg, so I did a sed replacement via froyo.conf.

sed -i -e 's:-d /dev/smd0:-h 14136 -d /dev/smd0:' /etc/init.cfg

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice! Thanks for the tip!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
GSM network location now works, post updated.
[Touch Pro2, Tilt 2 Android Development] wmg316:
I may be "posting in the wind" here since I have no logs! :D

But, I went into a building today where I lost reception.

The good: No freeze; no SOD!

The bad: I lost connection to my provider.

After leaving...and back on the road where I always (100% of the time) have great reception and no problems, I thought that my connection would come back...but it did not. I went to Settings, Wireless & networks, Mobile networks, Network operators to try to refresh my connection...without any luck.

I finally had to reboot and everything was fine.

I guess my question is...when I go into an area of bad reception (where I actually lose my network connection), and I go back into an area where I should have perfect reception, what do I do to get my connection back?
[Touch Pro2, Tilt 2 Android Development] toadlife:
By connection, do you mean "data" or "phone", or both? I had an issue where if I lose signal my data stops working and the only way to solve it was to either turn off the radio (airplane mode). ANother time it happened the data started working on it's own but it took awhile (several minutes) after the signal was restored.
[Touch Pro2, Tilt 2 Android Development] wmg316:
The first thing I noticed was phone...but yes, both!

I tried going into Airplane mode...and turning off Airplane mode...without luck.

Maybe I just didn't give it "enough time"??
[Touch Pro2, Tilt 2 Android Development] muziling:
See post#2

You can modify source code, replace "dummy" to your data connection account.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Notice you have Radio .57 and we are both from LA. Is that the best radio for you if so I will be switching?
[Touch Pro2, Tilt 2 Android Development] toadlife:
He's not CDMA. That doesn't apply to him.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Your issue is different than mine. You would need to be taking logs for highlandsun to be able to help you.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That's just the radio this thing came with when I bought it on eBay. I haven't unlocked it so I haven't tried any other radio ROMs yet. In fact, I don't even know how to flash a new radio. I don't have any Windows machines here so I can't use e.g. the HardSPL unlocker. I've been told that I can just flash from the SD card but I haven't looked for the instructions...
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Thanks, Are you getting good battery life?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
A couple days of pure standby time. About 15 hours of use - 3G, maps, browsing, etc...
[Touch Pro2, Tilt 2 Android Development] Starfox:
If it's a official update you can flash from SD by extracting and naming it RHODIMG.nbh. If it's just a radio file then you have to SPL unlock it.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] toadlife:
data failing again

I've been having my data fail again.

I was taking logs. When the failure to connect starts, this pops up in the logs. Before rebooting, I tried to toggle airplane mode and it failed. I'm running F22's latest rootfs.

04-25 16:06:14.640 D/RILJ ( 1411): [1527]< SETUP_DATA_CALL error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
04-25 16:06:14.640 D/GSM ( 1411): [GsmDataConnection-1] DcActivatingState msg.what=EVENT_SETUP_DATA_CONNECTION_DONE
04-25 16:06:14.640 D/GSM ( 1411): [GsmDataConnection-1] DataConnection Init failed com.android.internal.telephony.CommandException: GENERIC_FAILURE
04-25 16:06:14.640 D/GSM ( 1411): [GsmDataConnection-1] DataConnection setup result='Other error' on cid=1
04-25 16:06:14.640 D/RILJ ( 1411): [1534]> LAST_DATA_CALL_FAIL_CAUSE
04-25 16:06:14.650 D/AT ( 1294): AT< +CME ERROR: 30

Logs...

http://dl.dropbox.com/u/25754012/debuglogs_20110425171335.tar.gz
[Touch Pro2, Tilt 2 Android Development] Jandyman:
You know the alternate ril version in post 6? Now that the number cwm compatible roms are growing and eventually all roms will be compatible. . . .have you taught of making it a flashable zip? To be installed via cwm? :) would simplify things for every1 making it faster to install/test.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can make an update.zip too. I don't think hyc should be wasting his time on it tho (no offense) but not many people here on xda-devs are using cwm. That's pretty much a neopeek thing.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Yes but I'm sure cwm will catch on here too :)

Okay your rit, I'll make an update.zip when I'm on the computer next and post it for anyone interested, its basically just the files in the folders they need to be pushed to, in a zip with the path/appropriate folders intact rit? :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I haven't made any update zip's for cwm, but yes that's my understanding. The META-INF syntax and how to use it is where I get confused.

As for cwm catching on here, I doubt it. It's a pain to format your card, and the trade off is a lot of work for very little reward. I'm not a big fan of the partition builds, for that reason. I don't really see the gain, other than partial USB mass storage support - which seems pretty useless, as you can't remount the SD in Android, so you must reboot after doing so.

Just seems to add a ton of complexity to something that's already pretty complicated. If the added complexity added great benefits, then I would probably feel differently about it - but I honestly don't see any great benefits from using cwm on SD card builds. It's depressing, you install your build on cwm, and reboot to WinMo. Sad.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Well said and I agree 100%.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I partially agree, what you said is all true but there are benefits for both the dev and end user. (Which I'm sure uv allready heard but I'll summarize) Devs only have to worry about /system, and also instead of having to upload a huge file everytime they update they only need to upload patches. Also the partitions/cwm bring our builds much closer to how nand builds work meaning we now update like people with native android devices too and can use flashable font packs themes etc. (Which isn't a great advantage for those of us with knowledge on editing our system but great for people with very little knowledge on the android filesystem)

Cwm let's us backup and restore partition by partition which means when your build fails there is no longer always a need to reinstall completly just restore a backup from when it was working or just wipe /data. You can also easily wipe cache and fix permissions. So basically cwm is great for progress, to use a metaphor I used before: the domino which will speed up the rate of progress . . .which is good :P the having to reboot to launch haret is a pain though . . . I'm hoping soon for an update will let us launch into android straight from cwm.

Also the partition is a bit complicated but is a once off and I feel its worth it. Just follow tutorial vid and your good to go. For people currectly running partition builds its not much of a change but for people using data/system.img builds they should also see a noticable general speed increase :)

EDIT: A user at neopeek has just reported that he believes that cwm (4partitions) run better then normal 2partition builds! I can't garentee this is true but its a good observation.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
off topic post for today

Problem is, XDAndroid is already pretty much complicated enough with all the additional files that it requires. What makes one think that adding partitions to the microSD will help? Point being, we only require one partition (no user intervention here) Just a matter of perspective, I suppose? I agree that the partitions make it easier, for people that know how to do this but for others that don't have a f'ing clue... VERRRY PROBLEMATIC at best but it isn't a bad idea, in theory; kind of like the d-pad for the TP :p ;) (hint hint Arrrghhh)

I apologize to the OP for this off topic post :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I snipped your post, and even tho your points are valid - there's not many users that are going to be needing to run fix perms, or do any of that other stuff. Backup data.img... done. Yea... looped builds are a ton easier to manage.

However, your commend about a 'general speed increase' could not be more false. It's been proven time and time again, there is no speed benefit to running dedicated partitions.

In theory it's best with 4 partitions because if there's some corruption in a particular part of the data.img, you can localize that corruption instead of blasting out the entire data.img. Plus, we are more native in a sense... but who really cares if there's no NAND - if we're still dependent on WinMo, CWM seems relatively pointless. Sorry...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Hhhhmm well iv always found partition builds handier because its awesome to be able to go with astaro or rootexplorer to the root and change things on the fly, But I suppose like everything its what your used to, iv a much greater understanding of partition builds and so that's what iv becom accostomed to. Also the speed thing has also been a bit controversial most people who go from xda builds to partition builds claim a speed increase . . .. .wether this is the placebo effect or not noone knows for sure. But try cherrypie and then try and say that's not super fast! ;)

Anyway BOT--

Iv done a quick dirty update.zip, its late so I havnt time to test right now but feel free to test or open it up to see if iv messed anything up. But I think iv got it relativly ok :D

http://db.tt/mZDBNZM

Update: Updated to remove rootfs changes and switch to first post ril which works well for most.

-thanks to midnight/helicopter88 for the tip about meta-inf

EDIT: apologizes to highlandsun for slightly derailing the the thread, I didn't intend on starting a partitionVSnon-partition debate when I mentioned about cwm support :) back on topic from here on out.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Jandyman: enough! This thread is not about partition builds vs non-partition builds.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm at fault too, sorry mang ;).

Jandyman, I PM'd you why that build is faster. It has absolutely nothing to do with dedicated partitions.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
CME ERROR: 30 means "no network service" - looks like you've just lost your signal.
[Touch Pro2, Tilt 2 Android Development] toadlife:
When this happens I have multiple bars and in the past I've been able to make calls when this happened. I'll make a call tomorrow when this happens to make sure I'm not mis-remembering.

Should losing your signal cause Android to be unable to turn airplane mode on?
[Touch Pro2, Tilt 2 Android Development] AkumaX:
How about non-partition builds vs partition builds? :P
[Touch Pro2, Tilt 2 Android Development] Starfox:
Something weird happened that freaked the RIL out. Apparently something that should never failed did, and it made the RIL no longer respond. After cycling airplane mode, it works properly.

http://db.tt/3arRgN6

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Weird. The "AT+HTC_BSINFO?" request got a response that was just an empty line. That should never happen if the radio is actually registered to a network. I guess I could patch the code to return a response full of NULLs instead of an error code, but I don't think that Android will like that any better. And it's going to be a pain to duplicate the occurrence to test this, unless we just fake it and return a series of NULL responses to see what happens.
[Touch Pro2, Tilt 2 Android Development] nickleby:
I've been using this RIL for several weeks, and is working extremely fine...The only thing that should be "debugged" is the signal meter to become perfect :D
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Using XDAndroid FRX06+Fixes, other things work great, only the problem for ringtones and vibrate.

It seems that i can't never have the phone to vibrate when having phone or msg with setting properly. Also, the ringtones in phone setting is only silent, not other rings.

How can this be fixed?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is unrelated to the RIL - For ringtones, format the SD card using the HP Tool. Full format, FAT32 - don't use any built-in Windows/WinMo utilities.

Feel free to backup your data and restore, or start fresh doesn't matter.

As for the vibe, make sure all settings for vibrate are enabled. There's a global one, and per-app ones.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
I'll try it now.

Besides, f22's option to make call key become home with setting "physkeyboard=rhod100_uk--b1HOME" didn't work in frx06+fixes..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You have two hyphens in that command... it's not only case-sensitive but you have to put the command in exactly as it's listed...
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Besides, HP Tool never recognize my card. I can only use a tool call SDFormatter..
[Touch Pro2, Tilt 2 Android Development] xi.lin:
I type wrong in the post..

Actually my startup.txt is:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=240 acpuclock.oc_freq_khz=720000 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk-b1HOME"

boot
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
HP Tool works great for me, you're doing something wrong.

What does any of this have to do with the testing RIL...?
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Since i'm using FRX06+Fixes and the post refer in its release note point to here..

And he says that build merge f22's key function.
[Touch Pro2, Tilt 2 Android Development] mbellot:
arrrghhh - It may not be something he's doing (intentionally). I found out that the SD card reader in my laptop doesn't play nice with a lot of these format utilities.

I had to go out and buy a USB to SD reader to get them working.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, but the thread doesn't point to FRX06+Fixes. So please, quit cluttering this thread with non-RIL discussion.

Why not just use the phone? USB Mass Storage mode is almost as good as a SD reader.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Should i open a new thread for questions in FRX06+Fixes? I have no idea where to discuss...

Formatted and using existing data.img, still no ringtones to choose.. Try a new one.

And for me, the usb port has some problem so it can only be charged in both android and wm.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Can probably discuss the ringtone issue here:

http://xdaforums.com/showthread.php?t=1047347

The fixed media scanner only scans in specific directories on the SD card, instead of slowing down the system scanning everywhere.

Ringtones go in sdcard/Ringtones, Notifications go in sdcard/Notifications. Full list of directories is linked from that thread to here:

http://developer.android.com/guide/topics/data/data-storage.html#filesExternal
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think hyc is going to be providing support for his build like 'normal' builds. He only released it for those who didn't want to wait for the code to hit XDAndroid builds. If you're not going to wait, then you're on your own for support.

manekineko provided some good links, thanks.
[Touch Pro2, Tilt 2 Android Development] toadlife:
scbs

I don't know if causal link exists, but it seems the problems I have been having with the radio lately have all happened while I was running scbs. After my last indecent of not being able to connect to data and not being able to toggle airplane mode, I decided to disable scbs and the phone has been 101% stable since then.
[Touch Pro2, Tilt 2 Android Development] yelped:
On Sprint

I have a Rhodium 400 on Sprint (CDMA), and I can't seem to get 3G Data working.

Here is my Conf file to see if I mounted the required files right, and my build.prop, to see if I added the lines for Sprint correctly. They are both renamed to text files, because that's what the forum accepts.

Many thanks to everyone!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea... Pretty sure each command needs its own line. You have all the commands jumbled into one line. On each file.
[Touch Pro2, Tilt 2 Android Development] yelped:
Thanks! Is that because I use notepad? Should I use a different program, or is there a setting that changes this behavior?

Thanks again!
[Touch Pro2, Tilt 2 Android Development] BoominSVX:
Use wordpad to open, edit and save.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, if you use Windows you certainly need to use a piece of software that can handle Linux carriage returns/enter keys. Did you see all these commands on one line or on separate lines? I would think if anything Windows format would just put in an extra "enter key" for each time you hit enter.

I prefer Notepad++ - great software.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Thanks for the links~

I put ringtones and notifications directories in sdcard's root and now i can select them!
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Got it. Now my problem is solved and i'm looking forward to next frx release~

Thanks again for manekineko.
[Touch Pro2, Tilt 2 Android Development] muziling:
Seems you used the patch from http://xdaforums.com/showthread.php?t=1047347
[Touch Pro2, Tilt 2 Android Development] yelped:
Thanks! I actually used Wordpad, like the poster above you suggested. Now, I have the roaming indicator issue to resarch, and restoring all my apps.

Thanks again everyone!
[Touch Pro2, Tilt 2 Android Development] webxplore:
Not to hijack the thread but....based on my experience.....

Did you blow away your data.img if you are updating build.prop? I had the same problem until I followed post number 2 from this thread where we have to update the preferred network mode to 4 within the settings db using sqlite. Try the sql portion to update the network. You will probably end up connecting to the network with roaming indicator on. For this you might need to update eri.xml.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Yeah, highlandsun say tha in his fix builds~

I check the system/media/audio and it did has files in. I didn't know i should keep directories in sdcard's root.
[Touch Pro2, Tilt 2 Android Development] yelped:
I did, without the SQL portion since I don't know how to do it.
[Touch Pro2, Tilt 2 Android Development] manekineko:
I've noticed that using the post 6 RIL, under Settings => About Phone => Status, no matter where I am (even in the middle of major cities), the Mobile network type is never EvDo rev. A on my Sprint Rhod400.

Sometimes I get 1x, and sometimes I get CDMA - EvDo rev. 0, but it never shows EvDo rev. A.

Is there a way to determine whether this is a display issue, or a connection issue?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No. The files in /system/media will always be scanned as well, my patch only affects what gets scanned on the sdcard. It doesn't change what gets scanned on /system/media.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That seems to be true for everyone. Same for the post 1 RIL. No ideas at the moment. It's of course possible that the RIL is interpreting the result from the modem incorrectly. The only way to check that would be to compare against a known-good RIL for these phones. I would compare against WinMo ril logs, but unfortunately WinMo doesn't seem to even report the EVDO type. If you can find out how to make WinMo tell you, then this would be the way to go to verify.