Quote:
Originally Posted by [ACL]
you got it.. those changes for the rootfs should work just fine. I dont think i can get those committed, the best i can do is convince them to be more nand friendly but its not worth it since Rhod is the only nand device. We may need to just do it ourselves like the hd2 guys.
as for the changes on 9/30. You mean the kernel changes here ?
Commit in linux-msm-rhod-nand in Linux on Qualcomm's MSM - Gitorious
Those changes actually enable 3d. The latest rootfs has the gralloc lib needed for 3d to work, so make sure you have that. Also we decided to have 3d always enabled on all builds (including haret) unless the force_3d=0. So if you think 3d is breaking the startup, mod your cmd line on tinboot for no 3d and it will default back to the old settings.
If that does not work, then i need some dmesgs / logcats. Give it a try. |
Excellent. I'm heading over to a friends for the game, and I'll make changes to rootfs over there. I did notice that init uses $notnand=0 to qualify if we are nand booting, so maybe we could utilize that unless it is actually looking for data stored on nand as well.
Also, is it possible to write a provisioning program that would store values that can be used on next boot? We could have it present the user with options on phone model, GSM vs CMDA, and anything else we want on first boot, and then use those values for subsequent boots.
As far as the changes on 9-30, it must require me to make changes to tinboot, but apparently I'm not making the right changes. I am on the absolute latest rootfs direct from XDAndroid like you recommended. So far, I have tried leaving force_hw3d=1 in tinboot, setting force_hw3d=0, and leaving it out entirely, but the phone still cannot get past the animation. dmesg isn't helpful at all for this one, but I'll try to get a logcat for you. Adding a custom startup command of "su logcat >> /sdcard/logcat.txt" should work right?