Quote:
Originally Posted by [ACL]
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
|
I did compile with the new changes, and still the same problem. About 20 flashes in now, and so far, I've tried with hw3d.force=0, hw3d.force=1, and removing it entirely (and every combination I can think of). I've even tried your exact startup and no dice (moved files to root of card for that). Any chance you can post your froyo.user.conf? To add to the fun, every once in a while, I actually get the animation going forever (let it run for 30 minutes). I even pulled my data off the card and formatted it while I was doing all of this to make sure the card wasn't corrupt.
On the rootfs part, I'm still messing with this. I'm re-working their script a bit so I can keep my changes
dmesg doesn't help me catch whatever is causing this because it stops logging before it crashes out, but it crashes before I get to a point I could turn it again. I think the only option is ADB that I still haven't been able to get working
