[HD2 Android Q&A, Help & Troubleshooting and Genera] letama:
History

2010/11/24 Hastarin root package (ppp_tweaks_root.zip) added, it includes wrapper, ppp options and kernel tweaks.

2010/11/18 new kernel and wrapper v0.7

new test kernel with smd_tty trimmed to 2K.

wrapper fake data call list has now active=1

v0.6 - 2010/11/17

same as 0.5 without the stupid bug that trashed the code.

2010/11/16

Test kernel to diagnose the "tty_prepare_flip_string fail" error with high cpu usage, please check post here for detail

v0.5: delay changed for deactivate and fake data call list added.

v 0.4 - 2010/11/14

Changed tag to RIL_WRAP to improve log reading

Improved log messages

Signal tracking to try to find who kills wrapper monitor

Lower delay between AT commands

Sleep delays and sequence reworked

Tentative improvement to re-establish ppp

Tentative fix for wrapper monitor death with extra debug messages

Memory leak on deactivate fixed

v 0.3 - 2010/11/02

added network state detection to avoid doing ATD too early resulting in getting stuck.

changed nand handling, proper initialization for nand is now done by adding "nand_init" to wrapper command line in init.rc.

(Ex: service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init)

added a wrapper command line switch "rmnet_mode" for rmnet, "active" file in /etc/ppp is no longer used nor required for ppp.

v 0.2 - 2010/10/31, first release

restarts pppd when it dies

Troubleshooting

How to verify if wrapper is running:

In radio log (logcat -b radio -d), my wrapper write this at startup (do it quickly after boot, it disappears quite quickly over time):

----------- HTC Ril Wrapper v0.7 starting ------------

and you should have debug messages there starting with RIL_WRAP, not RILW.

Crash on boot (v0.2):

Check if your kernel command line in startup.txt has "nand_boot=0". If it still doesn't boot, try to remove any other option and only keep "nand_boot=0"

Troubleshooting crash on boot

Even if it crashes very early, it should be possible to grab early logs. To do that, start adb *before* starting android with this command:

adb logcat -b radio -v time

adb should say *waiting for device*, you can then start Android. Adb will show some logs before the device crashes. Please send me the logs if you are able to do so.

If you see AT@BRIC=0 in the log, it means that the wrapper thinks you are on nand, and that's why you device crashes.

pppd-fix

I saw in some logs that some are using Cass pppd-fix script with the wrapper. Cass script and wrapper are doing the same thing and are conflicting. So, if you have installed the pppd-fix, please remove it, it won't play nice with the wrapper.

Known issues

2010/11/14: pppd first launch fails after boot. wrapper catch it, however it would be nice to have it working the first time. It adds few seconds to re-establish data, so be patient!

2010/11/14: high cpu consumption. The issue comes from memory management in kernel, we still have to figure out what's happening.

2010/11/04: pppd monitor process seems to die from time to time. I don't know why yet, looking at the code it doesn't seem possible. I'll look into it and maybe release a new version with more debug traces. You can see it in terminal by doing a 'ps', it will show one of the rild as zombie ( Z instead of S just before process name). The easiest way to restart it is to do a data off/on.