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

[liveordie56]

hmm, i have been trying this and i feel like i have everything right

tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, the nbh in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 100 percent when i flash back to windows

I have tried multiple module/nbh files and i have formatted my sdcard to fat32, no matter what i'm getting the same problem

anybody know what could be going wrong?

[coolsilver]

Originally Posted by Lmiller1708

What I did was keep hitting the end button, slowly... then go to settings, display and check auto backlight control. It works fine for me know.

I agree it is more consistent with autobacklight setting on.

I think my backlight may soon burn out because it still from time to time have a red washed out look like a fluorescent bulb not getting enough power to turn the gas to plasma.

[tpdjr]

hey nate did you ever make the custom rootfs like f22 rootfs where the end key bring up recent apps and the helicoper veiw

[MassStash]

Originally Posted by tpdjr

hey nate did you ever make the custom rootfs like f22 rootfs where the end key bring up recent apps and the helicoper veiw

i agree, i cant get it working....

[natemcnutty]

Originally Posted by tpdjr

hey nate did you ever make the custom rootfs like f22 rootfs where the end key bring up recent apps and the helicoper veiw

Nope, because I haven't had a chance to look at the button codes. F22 didn't post any of the changes he made (that I know of).

In the next rootfs, I am making this change for the 3d testing:

if [ -f /sdcard/gralloc.msm7k.so ];then
mount --bind /sdcard/gralloc.msm7k.so /lib/froyo/hw/gralloc.msm7k.so
mount --bind /sdcard/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so
elif [ "$WVGA" = "1" ] && [ "$RCSCRIPT" = "froyo" ];then
mount --bind /lib/froyo/hw/gralloc.msm7k_wvga.so /lib/froyo/hw/gralloc.msm7k.so
mount --bind /lib/froyo/hw/gralloc.msm7k_wvga.so /system/lib/hw/gralloc.msm7k.so
fi
if [ -f /sdcard/libGLES_qcom.so ];then
mount --bind /sdcard/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
fi
if [ -f /sdcard/build.prop];then
mount --bind /sdcard/build.prop /system/build.prop
fi

And, I have added support for all of the rhod100 vairants in the new rootfs. I'm waiting on feedback from those users so I can automate that one as well

[tpdjr]

alright i have a few questions did you ever make the roots that enabled the screen to stay on while android is starting up and do use the libgles_qcom.so, build.pro and gralloc is it the same as haret?

[natemcnutty]

Originally Posted by tpdjr

alright i have a few questions did you ever make the roots that enabled the screen to stay on while android is starting up and do use the libgles_qcom.so, build.pro and gralloc is it the same as haret?

I did echo 50 >/sys/class/leds/lcd-backlight/brightness right when rootfs is mounted.

Then I did the code I posted previously for optionally loading the libgles, build.prop, and gralloc from the sdcard. If you do not have the files on the sdcard, it will default to the original ones.

I think some of the issues people are having with graphical issues might be because I replaced the original files with the 3d testing ones in the last builds. The method I am doing now will be much better. Just waiting on the files to download right now

[MassStash]

sweetness. you don't think it's faster/better to be running android from a "natively" partitioned ext2 partion on sdcard as upposed to just the fat32 andboot partitioned sdcard? and i'm dumb with the finding of how the hell i get a .kb file, all i see is .kl in the keymapping folder.... trying to get end=home/recent apps|power=power/turn off with the accesibility option to end call with power button....

edit: also, i can test some shtuff on the rhod400 if needed

[natemcnutty]

Originally Posted by MassStash

sweetness. you don't think it's faster/better to be running android from a "natively" partitioned ext2 partion on sdcard as upposed to just the fat32 andboot partitioned sdcard? and i'm dumb with the finding of how the hell i get a .kb file, all i see is .kl in the keymapping folder.... trying to get end=home/recent apps|power=power/turn off with the accesibility option to end call with power button....

edit: also, i can test some shtuff on the rhod400 if needed

I don't see a whole lot of performance coming from a file system change at this point. I'd just leave it as FAT32 so you can interface it easier with Windows for copying files back and forth (unless you run Linux).

For the .kb file, you shouldn't need it unless you want to override the automatic keyboard detection. To create one, just open notepad, click File-Save As, change the File Type to All, and save as rhod400.kb.

Also, the new RootFS is uploading to here: http://dl.dropbox.com/u/11790134/roo...14-42b44e2.img

[MassStash]

heck yea i'm running ubuntu 10.10. super nasty at that. but yea, trying to get the end buttong to home instead, didnt know i could just make up the file lol werd to the new rootfs dropping dlin now... get back to you on it asap

edit: gettin 404 at the file site brudda....

edit to edit: ahhhhh ha ha ha, "IS uploading"...... damn i'm a jumpy ass nerd haha