Quote:
Originally Posted by natemcnutty
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?
|
The only part that changes on tinboot is the cmd line. Here is what i use and it works for me
"gsensor_axis=2,1,3 msmvkeyb_toggle=off htc_hw.force_cdma=1 hw3d.force=1 physkeyboard=rhod400 panic=0 pm.sleep_mode=2"
I pushed some other changes today so you may need to try those out. In anycase ive never heard of bootanimation crashing anything on our builds. So im really baffled by your issue