ive got the android flame boot logo on it as well. maybe that has something to do with it? idk for sure though. im no developer or anything, couldnt tell you how to change files or even look at them like yall are. i just mess with a lot of things that look interesting and sometimes dig into bin files i shouldnt be. idk whats making it work, its not plugged in though and so far sync is whats locking it down. ill update if anything new occurs.
Believe me man, I'm no dev either, I just finagled around until I got it to work...tested it internally, had a few other's test it and released it.
If you don't mind, what steps did you take to flash the rom...ie wipe/no wipe, what order, did you boot then go back into recovery to enable sensors, what Romer version...etc, anything that might be helpful (or even what you think maybe wont be helpful.)
Thanks, and as far as I know, your the only GSM user, so data is working right?
This is probably a long shot guess, but what ROM did you have on the phone before you flashed liberty?
I am wondering if you started off from a stock blur rom or Fission in particular.
I'm no dev but, The thinking goes that maybe Liberty does not overwrite everything on the device when it installs and results might vary depending on what Rom was previously installed.
I'm new to Android but in WM it was sometimes better to flash to stock before flashing a new rom and I'm thinking maybe it would be a factor here as well.
I actually need the phone this week so I can't try this until the weekend.
I can't see any reason why the boot animation should have anything to do with the sensors. Especially considering it doesn't play the boot anim when it goes to sleep. It is possible however that by changing the anim it re-writes something in the boot script that is the real cause of the problem.
Perhaps if someone tried installing a real D2G boot animation it would shed some light on the situation.
