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

[natemcnutty]

Originally Posted by [ACL]

hey nate.. i didnt test this at all but i did implement the sdcard loop wait for the recovery. pain in the ass to restore and lose the modules .. so im still trying to master mind a way around that.

By the way, tested the sdcard loop just now. Works perfectly. I have some more cleanup that I'd like to do in init, so can you look through this patch and let me know what you think?

Edit: I changed the sdcard partition thing to be more efficient, removed some unnecessary stuff like the install-seq.sh portion, moved /tmp to /cache instead of /data/tmpcache, and removed the auto-mount sections for the mtdparts since we specify them in Tinboot.

[[ACL]]

Originally Posted by natemcnutty

By the way, tested the sdcard loop just now. Works perfectly. I have some more cleanup that I'd like to do in init, so can you look through this patch and let me know what you think?

Edit: I changed the sdcard partition thing to be more efficient, removed some unnecessary stuff like the install-seq.sh portion, moved /tmp to /cache instead of /data/tmpcache, and removed the auto-mount sections for the mtdparts since we specify them in Tinboot.

This part is confusing

-mkdir -p -m 0777 /data/tmpcache
-mkdir -p -m 0771 /data/shared_prefs
+if [ ! -d /data/shared_prefs ] ; then
+	mkdir -p -m 0771 /data/shared_prefs
+fi
 chmod 0771 /data/shared_prefs
 chown 1000:1000 /data/shared_prefs
 ln -s /data/shared_prefs /shared_prefs
-ln -s /data/tmpcache /tmp
+mount /cache /tmp

Does the link /shared_prefs need to exisit?

Also what is stored on /tmp? ifs its true tmp i wonder if we can scrap it

Keep in mind that recovery needs some of this so we need to make sure we arent getting in the way. recovery uses cache lot for its logs and stuff.

I see this on the rc mkdir /data/local/tmp 0771 shell shell . so how many tempts do we really need ..lol

edit: all the other changes are really good. good house keeping . Lets figure this part out "+mount /cache /tmp" before commiting. Everything else will be fine. Did you test it yet?

[natemcnutty]

Originally Posted by [ACL]

This part is confusing

-mkdir -p -m 0777 /data/tmpcache
-mkdir -p -m 0771 /data/shared_prefs
+if [ ! -d /data/shared_prefs ] ; then
+    mkdir -p -m 0771 /data/shared_prefs
+fi
 chmod 0771 /data/shared_prefs
 chown 1000:1000 /data/shared_prefs
 ln -s /data/shared_prefs /shared_prefs
-ln -s /data/tmpcache /tmp
+mount /cache /tmp

Does the link /shared_prefs need to exisit?

Also what is stored on /tmp? ifs its true tmp i wonder if we can scrap it

Keep in mind that recovery needs some of this so we need to make sure we arent getting in the way. recovery uses cache lot for its logs and stuff.

I see this on the rc mkdir /data/local/tmp 0771 shell shell . so how many tempts do we really need ..lol

Yeah, so here's how I understand some of this.

shared_prefs is for sharing preferences between standard user and root user in some applications. Not sure if this is some legacy backwards compatibility thing or what.

The ln -s will create a link at /shared_prefs and it doesn't have to exist like a mount does.

The /tmp was already being stored on /data, and I just moved it over to /cache. I have a feeling that /tmp is used by programs that don't support or may not be aware of /cache. In any case, I figured we could leave that one alone but move it to /cache to clean up our /data partition. No point in backing that up when we backup the data partition.

Edit: Well, I just read that /data/local/tmp is what things like the market use to download APK's to. I'm beginning to think maybe /tmp is something we did on XDAndroid...

[MassStash]

Originally Posted by natemcnutty

GPS works flawlessly on my phone. Takes about 2 minutes to get the initial lock, but after that, it's great.

oh sh*t, I have to try that now.... nah no lock, ocean

[natemcnutty]

ACL, you able to cat your recovery to a file that you can upload? I'm going to see if I can simply cat it onto the end of our existing payload before it creates the NB. I'm going to have to pad it to the right offset which could be a real pita to figure out, but this is the only method I can think of that might get this to work.

Figured out I can't use nbtools in any way because the OS.nb ends with the fatfs that we made 8 MB. If we wanted to include it in the NB, we would need to make it part of the imgfs or fatfs, but putting it in either might prevent us from being able to mount and update it. The fatfs was what was overwriting our partitions previously until we fixed that with the new payload.

[[ACL]]

Originally Posted by natemcnutty

Yeah, so here's how I understand some of this.

shared_prefs is for sharing preferences between standard user and root user in some applications. Not sure if this is some legacy backwards compatibility thing or what.

The ln -s will create a link at /shared_prefs and it doesn't have to exist like a mount does.

The /tmp was already being stored on /data, and I just moved it over to /cache. I have a feeling that /tmp is used by programs that don't support or may not be aware of /cache. In any case, I figured we could leave that one alone but move it to /cache to clean up our /data partition. No point in backing that up when we backup the data partition.

Edit: Well, I just read that /data/local/tmp is what things like the market use to download APK's to. I'm beginning to think maybe /tmp is something we did on XDAndroid...

time for a pig build ? leave it out for now, and if this is needed by android we can add it to the rc. This wya we dont have to rebuild the initrd to get this to work.

[natemcnutty]

Originally Posted by [ACL]

time for a pig build ? leave it out for now, and if this is needed by android we can add it to the rc. This wya we dont have to rebuild the initrd to get this to work.

Then should we do the same with shared_prefs? Also, in the latest build, did anyone else lose root? I see su there, but it isn't working.

Edit: Weird, I had to download busybox to get Titanium Backup working, but then ES File Explorer won't let me root explore... Guess I need to start fresh again.

[natemcnutty]

Originally Posted by [ACL]

time for a pig build ? leave it out for now, and if this is needed by android we can add it to the rc. This wya we dont have to rebuild the initrd to get this to work.

I just did a build without /tmp and noticed recovery tries to save a log there. Still waiting on the install at this point, so I'll let you know what else blows up

[MassStash]

Ooook, tried in moving car n gps is workin for me as well

Off the slightly tweaked FRX05 Nandroid ROM, fu(k winmo...

[m4f1050]

Originally Posted by T_D_H

what confuses me exactly, is that wifi is the only thing not working, and no one else seems to have the same issue, also seem to not be able to connect to the device with the usb drivers provided either, oh well, poke prod and beat untill ready, bake @ 350 and hope it doesnt taste bad :P

You're not the only one, 2 of us also got error scanning using Wifi... I reverted back to 3.11.11 files which Wifi worked... Haven't tested new files... My device is a Sprint Touch Pro2 without a Sim card (but Sim unlocked, with WU radio for Sim use)