Settings, launcher, opera not working (orientation) at the same time paper airplane is working flawlessly. Opened it twice and it worked perfect both times. Opera which I'm using right now to type this, broken.
[All CM7 Roms] Accelerometer Wonky - For months now...
- Thread starter Schlidel
- Start date
Ok, it's been running fine now as long as I don't open Google Sky.
I googled google sky orientation freeze or something similar and read about people experiencing similar issues.
Someone said it can be caused by other apps that use the compass like earth.
Anyway sky is a cool app, but at least on iho it causes screen lock. That's my theory and my phone is fine now.
I googled google sky orientation freeze or something similar and read about people experiencing similar issues.
Someone said it can be caused by other apps that use the compass like earth.
Anyway sky is a cool app, but at least on iho it causes screen lock. That's my theory and my phone is fine now.
Well, sorry to say, I have to say I have similar symptoms to Schlidel. I have an LG Optimus V (LG-VM670), baseband VM670ZV5. I purchased it in October 2011, so it is a fairly recent edition. I used the stock rom up until a month ago, and google sky map worked reliably with the phone for 6 months with the stock rom (I used it more than once a week). Also, the accelerometer would reliably change the screen orientation properly.
Recently I flashed with CyanogenMod-7.2.0-RC1-BACKside-IHO eng.jerryscript.20120502.032319. I installed it because I wanted to work with a bluetooth keyboard. Mostly trouble free, and definitely an upgrade over the stock rom (which is surprising, I thought the stock rom was pretty good, all things considered). Thanks, JerryScript et al!
Anyways, since I flashed it, the accelerometer is flaky. I have two apps now that use it: PicaSim (which is awesome, btw), and Sky Map, and of course the system screen rotation. If I load either of those apps, then it seems to select at random 2 possibilities: (1) works perfectly, (2) locks one of the axes of the accelerometer (and mangles the other axis?). Once the accelerometer is messed up, it is generally unavailable for all purposes (i.e., often my screen will even be stuck in a funny orientation). But once I have had it spontaneously start working again, too. Force killing google sky map & picasim doesn't change anything.
It seems to happen at random whether the phone has been on for a long time or not. I do not reboot very often, but I rebooted yesterday because of exactly this issue, and it is already not working again.
Killing ami304d (which automatically respawns) also doesn't fix it. So I suspect it is a kernel problem, but maybe ami304d keeps some calibration data somewhere else? Anyways, when I get a chance I will try to prove whether it is a kernel problem or not.
Sorry for the newbie question, but: is there kernel source for the specific kernel (with config and patches) that was used for this backside release? Like a git repository somewhere or directions for patching a stock 2.6.32.9 kernel? I'm probably too lazy, but I might even make a patch...since the trouble isn't reproducing for the developers, as they say: if it is to be, it is up to me.
Thanks!
- Greg
Recently I flashed with CyanogenMod-7.2.0-RC1-BACKside-IHO eng.jerryscript.20120502.032319. I installed it because I wanted to work with a bluetooth keyboard. Mostly trouble free, and definitely an upgrade over the stock rom (which is surprising, I thought the stock rom was pretty good, all things considered). Thanks, JerryScript et al!
Anyways, since I flashed it, the accelerometer is flaky. I have two apps now that use it: PicaSim (which is awesome, btw), and Sky Map, and of course the system screen rotation. If I load either of those apps, then it seems to select at random 2 possibilities: (1) works perfectly, (2) locks one of the axes of the accelerometer (and mangles the other axis?). Once the accelerometer is messed up, it is generally unavailable for all purposes (i.e., often my screen will even be stuck in a funny orientation). But once I have had it spontaneously start working again, too. Force killing google sky map & picasim doesn't change anything.
It seems to happen at random whether the phone has been on for a long time or not. I do not reboot very often, but I rebooted yesterday because of exactly this issue, and it is already not working again.
Killing ami304d (which automatically respawns) also doesn't fix it. So I suspect it is a kernel problem, but maybe ami304d keeps some calibration data somewhere else? Anyways, when I get a chance I will try to prove whether it is a kernel problem or not.
Sorry for the newbie question, but: is there kernel source for the specific kernel (with config and patches) that was used for this backside release? Like a git repository somewhere or directions for patching a stock 2.6.32.9 kernel? I'm probably too lazy, but I might even make a patch...since the trouble isn't reproducing for the developers, as they say: if it is to be, it is up to me.
Thanks!
- Greg
Sorry to keep talking to myself, but I'm just going to post stuff as I discover it.
It is definitely not a purely kernel problem. Killing system_server "fixes" it without rebooting the kernel.
When it fails, this is in logcat:
D/Stardroid.LocationController(12750): LocationController stop
D/Stardroid.LocationController(12750): LocationController -stop
D/Stardroid.SensorOrientationController(12750): Unregistering sensor listeners
and then a series of:
E/AmitSensor(12176): Sensor is closed. Can't set delay
When it is working /sys/devices/platform/i2c-gpio.5/i2c-5/5-0019/x (y and z too) always have new values in them. But once "Sensor is closed" happens, they always contain the same stale data.
So my theory is that this is a power management fail. When sky map (Stardroid) releases its handle on the orientation sensors, the KR3DH gets powered down (or something), and stops updating. Then when the sensor is needed again, it doesn't get properly "opened" again. Sky map pretends that one axis is still working wonkily because it is still getting enough information from the magnetometer to know that the phone is changing orientation, even though the accelerometer is AWOL.
I'm going to put this down for the moment, I swear. Maybe this will ring a bell for someone and I won't get a chance to use baksmali and grep tomorrow?
It is definitely not a purely kernel problem. Killing system_server "fixes" it without rebooting the kernel.
When it fails, this is in logcat:
D/Stardroid.LocationController(12750): LocationController stop
D/Stardroid.LocationController(12750): LocationController -stop
D/Stardroid.SensorOrientationController(12750): Unregistering sensor listeners
and then a series of:
E/AmitSensor(12176): Sensor is closed. Can't set delay
When it is working /sys/devices/platform/i2c-gpio.5/i2c-5/5-0019/x (y and z too) always have new values in them. But once "Sensor is closed" happens, they always contain the same stale data.
So my theory is that this is a power management fail. When sky map (Stardroid) releases its handle on the orientation sensors, the KR3DH gets powered down (or something), and stops updating. Then when the sensor is needed again, it doesn't get properly "opened" again. Sky map pretends that one axis is still working wonkily because it is still getting enough information from the magnetometer to know that the phone is changing orientation, even though the accelerometer is AWOL.
I'm going to put this down for the moment, I swear. Maybe this will ring a bell for someone and I won't get a chance to use baksmali and grep tomorrow?
Similar threads
Trending Posts
-
Back from a 10 year hiatus!
- Started by 8livesleft
- Replies: 2
-
-
-
OneUI 8 beta coming week of August 11, 2025- Started by Laura Knotek
- Replies: 2
Facebook
Twitter
Instagram