NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[[ACL]]

Originally Posted by steveholtam

Here is my ifconfig capture:

export PATH=/data/local/bin
:$PATH
$ $ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1376 (1.3 KiB) TX bytes:1376 (1.3 KiB)
$

This means nothing dood.. i need real logs. The logcat you posted before had nothing. Do a "logcat -b radio". you need to adb into the phone to do this. But the radio is smart, it tries less and less as you lose service so to get the logs pumping stuff again just put to airplane mode then back to normal.

[steveholtam]

Sorry.... I am so out of my league. I was stuck with the terminal with this error -
"Unable to open log device /dev.log/main': Permission Denied" when running "logcat -b radio". But I figured out how to capture the same data using alogcat app. So here is the detailed RADIO only info.

There seems to be a bunch of errors. Some are GSM related. Take a look.

[vistazifta]

from my console it looks like u put in a gsm ril ima plug in my att sim card and run it again ill let ya knowwhat happens and ill send my log when done

[[ACL]]

Originally Posted by steveholtam

Sorry.... I am so out of my league. I was stuck with the terminal with this error -
"Unable to open log device /dev.log/main': Permission Denied" when running "logcat -b radio". But I figured out how to capture the same data using alogcat app. So here is the detailed RADIO only info.

There seems to be a bunch of errors. Some are GSM related. Take a look.

When did you download your adnroid install and nhb ? you are getting an old error

fopen /etc/ppp/pap-secrets failed = 30
[ 03-06 17:46:41.980 125:0x8b E/RIL ] Some bullshit error

failed = 30 meains you are still using the ppp from system instead of data. Now there is a chance the script failed and its looking in the old location. You really need to use adb to troubleshoot this further.

Edit : try the new androidupdate. this was a mistake on my end

[[ACL]]

Originally Posted by vistazifta

from my console it looks like u put in a gsm ril ima plug in my att sim card and run it again ill let ya knowwhat happens and ill send my log when done

dont bother. we dont support gsm.

[vistazifta]

Originally Posted by [ACL]

dont bother. we dont support gsm.

yea i noticed ur android itself doesnt support it although im hoping u will one day but it goes further than it used to i actually get it booted up into android its when it starts lookin for service that makes it reboot now so it aint that bad

Edit: and acl if i dont have service do u still want my logs because i doubt it would make a difference if all u want is ril info?

[[ACL]]

Originally Posted by vistazifta

yea i noticed ur android itself doesnt support it although im hoping u will one day but it goes further than it used to i actually get it booted up into android its when it starts lookin for service that makes it reboot now so it aint that bad

Edit: and acl if i dont have service do u still want my logs because i doubt it would make a difference if all u want is ril info?

i think i see the issue.. the android update on the autobuild already had a ppp directory in system which is preventing it from making a link. so give me 10 mins and redownload the android upate.tgz.

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

[arrrghhh]

Originally Posted by [ACL]

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

I see CM NAND in our future!

[natemcnutty]

Originally Posted by [ACL]

i think i see the issue.. the android update on the autobuild already had a ppp directory in system which is preventing it from making a link. so give me 10 mins and redownload the android upate.tgz.

Ok done: redownload the android update and install. sorry bout that fellas. Maybe the picture below will get you to forgive me

That looks awesome ACL. Any chance you can push all of your changes to bootenv (feel free to overwrite my commits)? I pulled down your changes and a few things were missing. I was initially not getting the cache partition to format and mount because it was not created yet. Once I did that, it got me further to where Android started initializing, but then it keeps rebooting.

Your files from the autobuild seem to boot up just fine, so I'm thinking there is something not committed in initrd or something like that. Also, no data for me either, but not real way to show anything without ADB. I'm sure it still has to do with pppd, but I'm just not quite sure where to begin on that.

Edit: Also, your androidinstall does not have a /system/bin/su

[[ACL]]

Originally Posted by natemcnutty

That looks awesome ACL. Any chance you can push all of your changes to bootenv (feel free to overwrite my commits)? I pulled down your changes and a few things were missing. I was initially not getting the cache partition to format and mount because it was not created yet. Once I did that, it got me further to where Android started initializing, but then it keeps rebooting.

Your files from the autobuild seem to boot up just fine, so I'm thinking there is something not committed in initrd or something like that. Also, no data for me either, but not real way to show anything without ADB. I'm sure it still has to do with pppd, but I'm just not quite sure where to begin on that.

wow i didnt realize git didnt have my cache directory. Thats some buggy shit. I made a directory and addeded but git does not have it. So when you check the gz. its there .. odd. Thanks for the fixes bro.. I guess its smarter to have the script create it. So these are good commits.

I have a BIG todo for you..

when we install new modules we just put em in data/modules. Thing is they should really be in data/modules/<uname of kernel>. Then link it back to data modules. This is so we can have different versions of modules for more than one kernel. This is a must since if you upgrade a kernel and wipe your old modules you wont be able to go back incase its a bad kernel. Also we cant use mount bind like we do now. Sometimes it locks the partition busy so we need to implement this and use links for the final product. You can do it

hmm.. maybe we need lmiller to adb and verify. Can you ssh into your phone once wifi is enabled? should give u full shell.


Edit: thanks to this im going to re-push out a new autobuild. shortly. Cache is important for cyanogen. they use it for alot.. so good call on that partition.