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

[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

[[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

[steveholtam]

No data with the last update. I'm working on installing the Android SDK now for full adb.

[vistazifta]

Originally Posted by steveholtam

No data with the last update. I'm working on installing the Android SDK now for full adb.

the latest build just went up so if u didnt just try it then its already the old one. they pump out new builds avery few hours these days its amazing how much proress there is, but either way go pull it from here

[[ACL]]

Nate/Lmiller : weird thing just happened.. i got some file corruption on /cache.

cyangen has two dalvik-caches and one had a bunch of nonsense and i would get oob errors on the dmesg log. Im thinking since cache is at the end of nand, you think we have the same issue as hd2 where they cant write to the last 24mb of nand ? So far this happened once and i guess im glad it was just the cache. Had it been the data it would be difficult to troubleshoot.

/data/dalvik-cache <= Used by market apps (stored in /data/app)
/cache/dalvik-cache <= Used by System apps (stored in /system/app).

[natemcnutty]

Originally Posted by [ACL]

Nate/Lmiller : weird thing just happened.. i got some file corruption on /cache.

cyangen has two dalvik-caches and one had a bunch of nonsense and i would get oob errors on the dmesg log. Im thinking since cache is at the end of nand, you think we have the same issue as hd2 where they cant write to the last 24mb of nand ? So far this happened once and i guess im glad it was just the cache. Had it been the data it would be difficult to troubleshoot.

/data/dalvik-cache <= Used by market apps (stored in /data/app)
/cache/dalvik-cache <= Used by System apps (stored in /system/app).

I doubt we have the same problem as the HD2 because they can't even format that section, but I guess we could test it pretty easily by taking some space away from the data partition and see if the issue goes away. Could it be running out of space on the cache? What if we upped it to 64 MB instead?

[Lmiller1708]

So you guys still can't write to the cache partition?
If so try changing this line on the MAKEDEV's

mknod -m 0666 /dev/mtd/mtd4 c 90 6
to
mknod -m 0666 /dev/mtd/mtd4 c 90 8

I stated this before but never looked at the push, but I was also uncertain about it... Sorry about that.

But maybe the cache getting corrupt is something different... Kinda like the losing of some widgets on the Android home screen?

As for not being able to write to the recovery partition are you still using the same starting place as before. 0x4000000?

I won't be able to test for a while today for I forgot my phone at home.

[[ACL]]

Originally Posted by natemcnutty

I doubt we have the same problem as the HD2 because they can't even format that section, but I guess we could test it pretty easily by taking some space away from the data partition and see if the issue goes away. Could it be running out of space on the cache? What if we upped it to 64 MB instead?

nahh the cachent isnt running out of space. That was the first thing i checked, but then i noticed errors on dmesg.

Since cache partition begins at 1E000000, the errors start showing up at 1ff31000 which is really close to the end. We will need to try a few things to see whats up.

A good test to see is if you or lmiller can move your dalvik cache over to this partition. And recreate my issue. Simple link should do the job. Right away android gets angry since a corrupt dalvik cache is trouble for any app in the bad area.

I'll try to reduce the mtd parts and see if the problem keeps happening. I'll reduce the mtd from to end at 1FE00000 which is about 510mb (skipping the last 2mb).

Now a separate issue is the recovery. which is marked as protected. we can read it but writing to it does not work. So i get the feeling this needs to be extended as well.

[steveholtam]

Still no data using the 213238 nbh and update files. I've got the adb shell logcat stuff all figured out as well. Just took all day! Here is the latest logcat -b radio log attached.