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

[edwill]

Originally Posted by arrrghhh

If this is your first time with Android, you're going to want to start with the haret builds. They run entirely off of the SD, and there's a lot less chance of damage occurring. Best to learn how Android works on our phones, and then graduate to NAND testing.

Oh, I meant it was my 1st post on PPCG. Ive been using both XDAndroid (on XDA edwill44) and Neopeek. I am ready to move to the next level. I just want to make sure I do it correctly. But thanks for the concern, I dont want to brick my phn either.

[damage_them]

Originally Posted by Lmiller1708

Shoot. Yeah give mine a try. Change the extension from .txt to .conf.

thanks will do and report back...this is for the the build today right? 28th

[natemcnutty]

Originally Posted by [ACL]

Up to you guys.. yall are pretty much the NAND team. If nate is happy supporting the rootfs in the mean time, then go that method. My setup is obviously custom for many reasons so i dont have a standard for myself.

I don't mind hacking my way through the rootfs. Been a fun learning experience, and I really don't like the idea of moving things back out of NAND when the goal is to move everything onto it, lol.

Removed test rootfs. Didn't work again

[natemcnutty]

WOOT. Got the modded rootfs to autoconfigure keyboard! Now I just need some testers Remove any .kb file from your andboot folder and see if it works for you.

http://dl.dropbox.com/u/11790134/roo...28-36b2308.img

[coolsilver]

Works ok on my Rhod500.

Then again you been building for RHOD500, so maybe someone else can confirm.

[damage_them]

new roots is a go on rhod400 it detected it

[natemcnutty]

Originally Posted by coolsilver

Works ok on my Rhod500.

Then again you been building for RHOD500, so maybe someone else can confirm.

Originally Posted by damage_them

new roots is a go on rhod400 it detected it

Excellent. I took a little different approach. I had been trying to use cat /sys/class/htc_hw/machine_variant | grep -q RHOD50000 to return true, and it kept telling me file does not exist. Instead I created a variable in init called LAYOUT:

LAYOUT=`/bin/grep ".*0*" /sys/class/htc_hw/machine_variant`
and then did a if $LAYOUT="RHOD50000" elseif $LAYOUT="RHOD40000", etc.

[natemcnutty]

Originally Posted by edwill

1st post....

Ok, I have read each and every post in this thread. I have to say that what youre doing is to be commended. I want to add my TP2 on the list of testers. I will read the noob post VERY carefully and report all my findings. Off hand, is there anything I need to look out for during the process? Keep pushin guys and again, Thanks....

Some builds are more stable than others. I try to put a comment next to builds when they are not working properly or have known issues. If want to get a baseline for what nand should feel like, I recommend the2010-10-21 build under Archives

The two most recent ones have issues with the panel initializing because it has the new panel code for turning it on and off and handling ambient light control.

On the latest build, I have done echo 50 > to the brightness file which keeps the backlight on through boot, but it still seems to be having issues re-initializing the panel. Everyone else experiencing this?

[coolsilver]

Nice Job!

I can't wait for the Auto Dim stuff to work. I haven't tested any of it after the initial NBH was uploaded. I fought for 5 minutes to get the screen on the first time. On, off, on, off, on for 3 seconds, off.... etc.

I'll probably get around to setting up a dev environment and taking a look at things. I know nothing of writing code other than basic scripting. I can usually read through it ok.

[natemcnutty]

I also wanted to remind everyone that a new ext2 is available from the main XDAndroid site in case you haven't updated (like me...). Here's a direct link: http://files.xdandroid.com/system-FRX02.ext2.zip