yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
New ril in post #6 no longer needs the network mode setting.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
So i faced weird problem that it didn't scan /system/media since no file to select before i put files in sdcard's root.. Maybe i can try to clean the media cache or sth. to see whether it can work..
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Most of the changes we've been playing with recently have now been merged into the XDAndroid repos. There's still a lot left to merge, but we're much closer now. And a lot has changed as well. Corresponding patches for Gingerbread have been written and tested, and new bugs in Gingerbread have been found and squashed. (I keep saying, to everyone who's rushing into running Gingerbread - it's not even half-baked yet. Unless you enjoy testing code that crashes all the time, I believe installing GBX would be a mistake at this point in time.)

All of the patches I list above have been written and tested. Everything but the rootfs changes have been merged.

The ril, telephony framework, and Phone app have been updated again. You no longer need to set the ro.telephony.world_phone or ro.telephony.default_network properties. The ril detects both of these cases dynamically now. You still need to set the operator ID though.

Also the default eri.xml is being changed, it will simply say "XDAndroid" by default. You can still copy your own into /data if you want to customize it, but as always, it's just a cosmetic detail. My updated init script will copy local.prop, eri.xml, (and serialno) from your boot directory automatically so setting this up should be fairly painless.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
Can we use it in some eclair's build? Thanks~
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't see why not, but there's no supported Eclair builds around... So you'd be on your own.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Another crash and burn while at the office...

Restarting the phone was the only way to get phone/data to connect again...

http://dl.dropbox.com/u/25754012/debuglogs_20110429232201.tar.gz
[Touch Pro2, Tilt 2 Android Development] highlandsun:
04-29 15:34:51.580 D/AT ( 1295): AT> AT+CGACT=0,1
04-29 15:34:51.590 D/AT ( 1295): AT< 0
04-29 15:34:51.590 D/AT ( 1295): AT< +CME ERROR: 0
04-29 15:34:51.600 D/RILJ ( 1402): [7099]< SETUP_DATA_CALL error: com.android.internal.telephony.CommandException: GENERIC_FAILURE

CME ERROR 0 is "Phone failure".

Sorry dude, can't help you.

Looking at your general logcat, you have a lot of Wifi disconnects starting around 06:42. It looks like Wifi connects for a couple minutes, which triggers a disconnect of the Mobile Data connection. Then Wifi fails, and Mobile Data is restarted. Over and over and over. Your Wifi is a problem - fix your access point, or leave Wifi turned off, and your Mobile Data won't have to bounce up and down so often.
[Touch Pro2, Tilt 2 Android Development] toadlife:
The wireless network at work is a mess and I'm not the guy in charge of it, so I think I'll just try turning my wifi off when I work at that particular office.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
I try tiad's newest SENSE X(OK, tiad's...) and it's based on eclair.

I use this command in conf:

"mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /lib/eclair/libhtcgeneric-ril.so"

after that i have no signal at all when i didn't use it, i just have no apn to save..
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Ask Tiad to fix it.
[Touch Pro2, Tilt 2 Android Development] recnamoruen:
So I have a rhod500 on the Verizon Network. After installing and setting up Highlands ril and my Apn for verizon, I am now able to send and recieve picture messages on my device.

These are my apn settings

apn name=Verizon

apn=internet

mmsc=http://mms.vtext.com/servlets/mms

If you have any questions just let me know and I'll try to answer them.
[Touch Pro2, Tilt 2 Android Development] ravip_27:
Need one clarification

Hyc post6 mentions that the updated ril does not need the network setup but needs operator id set. he also talks about using local.prop file for this. other people have mentioned using build.prop file to do this. Which file should we cretae? Also how does one go about creating a new build.prop file with all the entries (not just the operator entry) if they are starting from scratch?
[Touch Pro2, Tilt 2 Android Development] recnamoruen:
I used local prop, for some reason changes to the build.prop were not working for me
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The old directions used build.prop. That turns out to be too much hassle. Use /data/local.prop, it's much easier.

The original build.prop is created when the system is compiled. Unless you're compiling your own Android source tree, you would not be creating a new build.prop from scratch. (And even then, it would be built automatically.)
[Touch Pro2, Tilt 2 Android Development] ravip_27:
Thanks recnamoruen and hyc. Will use the local.prop to set the values.
[Touch Pro2, Tilt 2 Android Development] tjrhine:
If /data/local.prop does't exist should I create a new one and just put the statements in that I need for my carrier (Sprint)? Or should it contain additional information?

Thanks
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Just create it with those two statements.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Probably a smart move.

I've added some code to parse the CME ERRORs in the latest version. It might give Android a better idea of what's going on, dunno. See if it makes any difference for you.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Thanks. Running e374d98 now. I work in the steel cage from hell all this week (the office where the ril always blows up), so we'll see how it goes.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
For the record: I've been running a partitioned build for the past couple months. IMO it's worth the additional setup effort because there's a noticeable increase in stability. Also with my latest rootfs and kernel patches, USB mounts are fully functional.

I like the idea of having a native-style recovery; I use Amon-RA on my G1 all the time for updates and such and always missed that here. But I'm disappointed at neopeek's implementation, he should be using kexec() to get from the recovery boot to the main system instead of booting into winmo again. I'd fix it myself but as far as I know he hasn't made his source code available.

So yes, I believe that's the right direction, but neopeek's implementation is lacking and his coding method precludes others from helping. I can't tolerate that. All of my coding is fully open. IMO that's the only way to work because it makes it possible for others to contribute and guarantees the fastest progress. And ultimately that's all that matters to me - making progress, as quickly as possible.
[Touch Pro2, Tilt 2 Android Development] xUmaRix:
@highlandsun

could you please update your files for patitioned build.I had modified xdandroid rootfs to include neopeek CWM and it works.I saw that in init file for xdandroid rootfs have different set of paritition from neopeek rootfsf.Xdandroid use mmcblk0p3 and mmcblk0p4 while neopeek use mmcblk0p2 and mmcblk0p3 for system and data respectivly.You are right about kexec().neopeek dosen't use it in his init.recovery.I think we can merge both development to make it solid.I had try neopeek fix for neocore texture and it works.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I'm not making any further changes to anything until my last round of merge requests is resolved. As arrrghhh keeps pointing out, there've been a ton of changes flying around recently and I'd like to let the dust settle and see where we are.

If you're capable of setting up a partitioned build I think you're able to set your rootfs up the way you want it without me doing anything, anyway.

I was chatting with stinebd about the recovery shell earlier tonight, he pointed out that we don't even need to use kexec. All that's needed is to make init.android restart itself, and he already has some patches to do that. Not sure if he plans to publish those, it sounds like he's had that stuff in his private tree for a long time already.
[Touch Pro2, Tilt 2 Android Development] manekineko:
That said, the fact that we use p3 and p4 is pretty mysterious, and without any apparent advantages. Net result is that you can't even use gparted to setup the partitions, unless you create a dummy empty p2, it's command-line only to setup the partitions.

While you have so many patches to init already, maybe the small change to use p2 and p3 would make sense.
[Touch Pro2, Tilt 2 Android Development] ndno:
Hi hyc,

I'm using the system.ext2 and rootfs.img you have on your link at http://highlandsun.com/hyc/FRX06+/. In your changelog, you said you updated the mediascanner to only scan a particular directory tree and not the whole SD card; where is this directory tree? I'm been pulling my hair trying to figure out where it is because I can't set my ringtone/notification tones (I don't see any ogg tone files in the system.ext2/rootfs.img you provided; actually, the sound settings doesn't see anything other than "silent"). Thanks!

Is it easy to port the RIL patch(es) you did to other Android builds besides the FRX06 that you used as the baseline? For example, I'm running a couple other Android builds (Cherry Pie v3 and Froyo B V6 available at neopeek.com) and I like to put your RIL patch(es) in those build for use; Cherry Pie v3 is a CWM build and Froyo B V6 is a ext2 partition build. The rootfs.img those builds use are drastically different than the rootfs.img (FRX06-based) you provided. I guess I can look at your GIT repository and figure out the delta and apply the delta to those builds rootfs.img; what is your suggestion? Thanks!
[Touch Pro2, Tilt 2 Android Development] manekineko:
See highlandsun's post here:

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

Full list of directories is linked from that thread to here:

The scanner will scan:

Music/ - Media scanner classifies all media found here as user music.

Podcasts/ - Media scanner classifies all media found here as a podcast.

Ringtones/ - Media scanner classifies all media found here as a ringtone.

Alarms/ - Media scanner classifies all media found here as an alarm sound.

Notifications/ - Media scanner classifies all media found here as a notification sound.

Pictures/ - All photos (excluding those taken with the camera).

Movies/ - All movies (excluding those taken with the camcorder).

Download/ - Miscellaneous downloads.
[Touch Pro2, Tilt 2 Android Development] xi.lin:
You can put your alarms\notifications directories in sdcard's root, and you will get them~
[Touch Pro2, Tilt 2 Android Development] helicopter88:
It could be pretty hard to edit rootfs,if you aren't experienced in that,i'm searching a way to do it within cwm,and i haven't got anything successful,at least in replacing init.android(it deletes old init.android without putting the new one)..

The best thing to do it's wait for all the patches to be merged in official rootfs,and then neopeek will port it on cwm's rootfs..
[Touch Pro2, Tilt 2 Android Development] ndno:
You're right, it's pretty difficult as you said. I've been trying for the last couple days and comparing the init file between the different rootfs.img is a nightmare. It's hard to figure out what to pull in from hyc's rootfs.img/system.ext2 since his rootfs.img/system.ext2 not only have RIL patches but other system-wide improvements. I guess I'll play some more while I wait; it's a good learning experience of what's actually going on during Android boots up.
[Touch Pro2, Tilt 2 Android Development] ndno:
Just some status: I used hyc's rootfs.img and system.ext2 he posted at highlandsun.com in his signature and it's the bomb! Very solid and stable. I have not got any reboots/SODs; data seems to work very reliably; I didn't even add an APN as I don't use MMS at all. IMO, with hyc's other improvements in his rootfs.img and system.ext2 besides the RIL patch, it's faster than the FRX06 stock build. Overclocking at 614Mhz, I'm consistently getting a score of 570-600 on Quadrant.

I took jonpry's battery meter patch and incorporated it into the hyc's rootfs.img and used wiltist2's 4/15/11 kernel and it's working like a champ.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That stuff is already a week or so out of date. I haven't updated it because I thought we'd have the official release out soon.
[Touch Pro2, Tilt 2 Android Development] ndno:
I noticed XDandroid has a new 5/1 rootfs.img build; is that "update" you were talking about? So if I want to use your latest updates, where can I find them? Thanks.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
CDMA Roaming Indicator

OK, been rummaging around trying to make sense of this eri.xml stuff.

Found this useful post http://www.howardforums.com/printthread.php?t=1443675 which explains more of what's going on. The modified eri.xml that I've used in my builds sets the string for id=128, which seems to be what Sprint is using these days (that thread is from 2008 and apparently out of date). Meanwhile Verizon seems to default to id=64. I hadn't modified the string for id=64 up till now. I can't even imagine what other networks out there are using, but I'll stick with setting 64 and 128 for now.

The main conclusion is if you want the roaming indicator to look *exactly* right, you probably need to install an eri.xml that corresponds to your network operator. If you're ever roaming off your home network, the roaming indicators will probably look all screwy again.
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
So do we need to extract an eri.xml from a working device on whatever network we want to use? I take it that it doesn't matter what phone it's from?

I don't know if this has been posted anywhere or not, but are there any instructions or tips on how to extract/inject an eri.xml? I could get a sprint one from my Wife's Samsung Transform if that will help.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
You don't need a device from the carrier, when you're running a radio log (logcat -b radio) in the text is a line that looks like this:

[CdmaServiceStateTracker] Set CDMA Roaming Indicator to: 128

Whatever the number at the end is, that is what you need in your eri.xml, once you've edited the provided eri.xml to that number you just adb push it into /data/ on the phone and you're set.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Well, there's no real mystery. p2 is reserved for the rootfs itself. But that's set up in the initrd, so you don't see any commands to set it up in the rootfs init script because it's already done by then.

The XDAndroid partition layout makes perfect sense, if you want to go that route. In talking with some other XDAndroid folks, their position is that it's too complicated for newbies so they don't want to support it. I understand their perspective all too well. If you want to run with partitions, you need to know what you're doing.

With that said, we're now at the point where if you know what you're doing, you can put together a Froyo install that is totally solid and hassle-free.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Is there a possibility to get older rils? I'v changed to new one and it's not as good as one I used before.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
How so? That certainly should not be the case.

There's no point in going backwards, let's look forwards with testing - outline your issues, provide logs, and either there's something you're doing wrong, or there is a regression - in which case don't you think it'd be better to help fix it rather than ask for an old RIL...?
[Touch Pro2, Tilt 2 Android Development] Raul^:
Ok, you are right. I will try to make logs and post them here.
[Touch Pro2, Tilt 2 Android Development] wmg316:
@ Hyc

I ran your 'rootfs-hyc-20110424-495424d.img' and 'system-hyc-20110425.ext2' (downloaded, extracted, READ YOUR PAGE and followed directions :), created new data.img). It ran very well!

I just tried your 'rootfs-hyc-20110506-a13049d.img' and 'system-hyc-20110506.ext2' (downloaded, extracted, READ YOUR PAGE and followed directions :), created new data.img) and was having a couple of problems:

Wi-fi is "unable to scan for networks"

There were a couple of apps that I download from Market that are not installing (they show that they downloaded, but "installation unsuccessful"). Apps are 'Angry Birds' and 'Bible KJV'

I noticed that there is an inoperable "Quake" shortcut in the app drawer

I tried the 20110506 with the kernel and modules I always use (WisTilt2) and with the kernel and modules that you posted at your site, creating a fresh data.img with both and encountered the same results above. Everything else appeared to be working good.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Something weird happened, Android soft-booted and it showed a blinking roaming triangle. Toggled airport and it seems back to normal.

http://db.tt/tQ4fgor

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Logs would be necessary to troubleshoot this issue. Doesn't sound like a modules/kernel mismatch off hand tho....

I assume these were able to be downloaded/installed previously? Again, logs would really be needed to determine what's going on... Might want to try clearing the Market cache to see if it helps out.

This is expected, you need your own PAK file as it states when you run it...
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
Ok, sorry, I must have missed it, but where do we get an eri.xml file to start with? I don't have one currently in /data/
[Touch Pro2, Tilt 2 Android Development] NeoMatrixJR:
nevermind, found it in /system/framework/framework-res.apk.

Had to decompile with apk manager to edit the file.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I guess that is one way, the other being:

http://xdaforums.com/showpost.php?p=12565116&postcount=83
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The files on my site are provided as-is. I am not supporting them, I'm just posting what I am currently running.

With that said, I already know about the issues you mention.

For wifi, a fix is to edit /data/misc/wifi/wpa_supplicant.conf and change "tiwlan0" to "wlan0".

The apps you're having trouble with are "secure" and with my current setup in the /init script secure app storage is broken for loopmounted builds.

already answered by arrrghhh.

I will not post bug fixes to those files. Like I said, they're simply what I'm now running and they work for me. If they don't work for you, not my problem.

[I lied. Both 1 & 2 are now fixed in the new rootfs. Also I've posted a new kernel to fix the battery charging issues that were caused by the USB tethering fix. And just a reminder, on my kernels solid green means a wakelock, blinking green means full sleep.]
[Touch Pro2, Tilt 2 Android Development] manny05:
i had the same problem with the wifi ^ however i noticed that when i install the kernel and everything else from highland, i did a restore of all apps and system data using titanium backup. so i figured it must of corrupted a file or a setting..so i did a new data.img, replace all the files in my andboot (kernel, zimage etc) and only did app restore (not system settings) and it seemed to have fix the problem..although for some reason it wont pick up my music..says no sd card found. so i use gtunes (app from market store) to play my music..however i cant set a ringtone, or notification since apparently its not picking up any audio files from my sd card. any fix or suggestions for this?
[Touch Pro2, Tilt 2 Android Development] großa:
Tried the files too and i've the same problem.

No ringtones, notifications etc.

Will try a full format with the HP tool tomorrow.

It solved the problem, see here:

no storage card

EDIT:

Did a full format with the HP tool. Installed Android again (new data.img), root of the sd card.

No ringtones at all.
[Touch Pro2, Tilt 2 Android Development] Starfox:
hyc, is Voice Privacy correctly working? I always see VoicePrivacy is disabled in the logs, even when the checkbox is enabled. Never seen it say VP is enabled.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Dunno. Watch your logs when you toggle the checkbox.

On a completely separate note - the Gallery3D that I included in my build corrupts the screen when you rotate the screen. The Gallery3Dr.apk from here http://xdaforums.com/showthread.php?t=752007 works a lot better.
[Touch Pro2, Tilt 2 Android Development] killerz298:
Mine isn't blinking but it is on the entire time my phone is on. I don't think I am actually roaming though as my roaming data usage didn't go up that much. I didn't try turning on and off airplane mode yet though.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you do the eri trick? Although it should no longer be necessary. I think this thread may not be getting more updates, the updates now are probably just going to the tree so they can be integrated immediately.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yeah, the original purpose of this thread has been met, as far as I'm concerned. The new ril is feature complete and is no longer the main cause of any hangs/crashes. Testing is over.
[Touch Pro2, Tilt 2 Android Development] muziling:
Attach error logs, password I pm you:

When goto error, does need to free p_response_bs?

at_response_free(p_response_bs);
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes, you're right.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
New version uploaded with that memleak fixed.

The official xdandroid repo is also sync'd with all of my ril patches now.
[Touch Pro2, Tilt 2 Android Development] muziling:
Thanks, RoamingIndicator now set to 64 for my carrier, not 128. :)

another problem still
[Touch Pro2, Tilt 2 Android Development] killerz298:
No I haven't tried that yet. I will give it a shot this afternoon. So I shouldn't be downloading the file from this thread in post 6? Where should I be downloading it from then?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The binary in post#6 is still the most up to date.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks dude, wasn't sure if you were keeping it updated ;).
[Touch Pro2, Tilt 2 Android Development] wmg316:
Do you know if anything in this Gallery3D would cause SOD's. I have not had a SOD in a very long time. But I have had two since installing this apk yesterday (using your rootfs, system.ext, kernel, modules btw). Just wondering if you may have experienced this?
[Touch Pro2, Tilt 2 Android Development] toadlife:
Hyc's (highlandsun's) latest kernels seem to be causing the occasional SOD. I've had one and I believe Hyc has been having them too. Has nothing to do with Gallery3D.
[Touch Pro2, Tilt 2 Android Development] wmg316:
After posting what I did, I remembered that 2 days ago I also changed from WisTilt2's kernel to Hyc's posted kernel. I have changed back to WisTilt2's kernel thinking that it was kernel related instead of the gallery...I just forgot that I had also changed my kernel in the last two days.
[Touch Pro2, Tilt 2 Android Development] Serren:
Do I have to use a partition setup to use the hyc files?

I ask because during the boot effort, I'm getting a bunch of path does not exist, , cannot create symlink, no such file or directory, etc. errors.

I had a working install last night, and just today changed to the hyc Kernel and modules. (while also using the hyc system.ext2 file and I think the proper F22 root files.)

So is a partioned SD card needed or not?

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Partitioned card is not required. I run this on looped a build every day.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No, partitions are not required, but my system only works with my rootfs.

My previous kernel had a bunch of merges in it, one may have gotten mucked up. My current kernel (1321) has been more stable and is only 3 patches different from autobuild.