Originally Posted by [ACL] (Post 1963422)

As much as id love to do this on the kernel i think the quick and dirty way to get it done right now is just to modify the rootfs for nand.

What we can do is create a blank file on your sdcard that has the name of your physkeyboard value that would originally go to the startup/cmd line. So for example if you normally use physkeyboard=rhod400 on your cmdline, we can just create an empty file called rhod400.

This modded rootfs can detect that and load the correct kb settings. Thats all the difference really between the rhods.. rest of the crap we alreayd handle in the kernel. I can help someone do this or you would like i can upload one modified already. The downsides are that we would need to keep up with changes on the real community rootfs, but then again that doesnt change much.

Also, i checked tinboot and it really doesnt need any modification. So natemcnutty, not sure why its not working for you. But i can help you mod the scripts if needed.

Originally Posted by damage_them (Post 1963436)

ok on this one start animation up is back..but it freezes right @ the animation screen..lol..doesnt go any further

Originally Posted by natemcnutty (Post 1963437)

Yup, so same issue as I'm having. I've tried this with several different options. I've tried with force hw3d set to 1 (which is how Wozz had it set). I tried it set to 0 and having it not set at all. None of them worked for me and all froze up at the animation screen.

I have a custom command of "dmesg >> /sdcard/dmesg.txt" in my froyo.conf file, and the last thing it shows is ramzswap size setting which is why I was trying to tweak with that option.

Originally Posted by damage_them (Post 1963439)

ive already switched back to the 9-25 one..no animation(which i really dont care for)..with out it phone comes one one shot! about 5-10 seconds..kinda like it that way :)

Originally Posted by natemcnutty (Post 1963441)

Excellent. Thanks for the feedback. As far as the animation goes, I did compile the 9-25 one with force_hw3d=0 since we didn't have 3d enabled yet. I can generate a new one with it set to 1 for you to play with tomorrow and see if that makes any difference.

As far as the new build is concerned, I'm just hoping ACL might have an idea of what is going on there. I'll have some free time tomorrow to really take a look at the changes between the 9-25 build and the 9-29 commit and see if anything sticks out, but I'm pretty sure ACL's code is perfect since it seems to be working for him. I'm kind of hoping there's something that just didn't get committed that is needed to get it working :)

Originally Posted by natemcnutty (Post 1963410)

Well, since your device performed a little differently than mine did with the 0925 build, maybe you can see if the latest build works for you. I just updated the first post with a newly compiled NBH (included the zImage for reference) and module files. On my device, it seems like it freezes on the loading screen, but it is doing something because I'll see it flicker every so often. Unfortunately, nothing gets logged to dmesg, so I have no way to figure out exactly what it is doing.

Also, you may want to edit your froyo.conf file on the SD card to reduce the size of compcache to something smaller than 90 as that seemed to help me get a little further into the boot before it froze :)

Originally Posted by [ACL] (Post 1963422)

As much as id love to do this on the kernel i think the quick and dirty way to get it done right now is just to modify the rootfs for nand.

What we can do is create a blank file on your sdcard that has the name of your physkeyboard value that would originally go to the startup/cmd line. So for example if you normally use physkeyboard=rhod400 on your cmdline, we can just create an empty file called rhod400.

This modded rootfs can detect that and load the correct kb settings. Thats all the difference really between the rhods.. rest of the crap we alreayd handle in the kernel. I can help someone do this or you would like i can upload one modified already. The downsides are that we would need to keep up with changes on the real community rootfs, but then again that doesnt change much.

Also, i checked tinboot and it really doesnt need any modification. So natemcnutty, not sure why its not working for you. But i can help you mod the scripts if needed.