My GN which is rooted (only so I could remove takjuxw and put takju on it) and on 4.1.1 has this strange problem with the gyro.
After using a phone for a day or so, the gyro stops working. This manifests itself as the phone not autorotating when put into landscope mode, apps quick respond to shaking stop working and a game that rely on the phone being tilted side to side to move a character not responding.
The problem is always fixed by a reboot. But, and this is the puzzling aspect, the problem can also be corrected by doing the following.
- put the phone into standby mode
- orient the phone in landscape
- unlock the phone (I only use the slide lock) by moving the lock icon up to the top edge of the screen, holding it for a second or so and then releasing. The screen will freeze momentarily and then unlock to a landscape orientation. From then the auto rotation will work for a while.
From that it's hard to know if the problem is hardware or software but it occured with ICS, JB 4.1 and then JB 4.1.1 and on the first JB installation I did a complete wipe and installation.
Anybody seen this behaviour before and provide some ideas of what the problem could be?
Thanks
After using a phone for a day or so, the gyro stops working. This manifests itself as the phone not autorotating when put into landscope mode, apps quick respond to shaking stop working and a game that rely on the phone being tilted side to side to move a character not responding.
The problem is always fixed by a reboot. But, and this is the puzzling aspect, the problem can also be corrected by doing the following.
- put the phone into standby mode
- orient the phone in landscape
- unlock the phone (I only use the slide lock) by moving the lock icon up to the top edge of the screen, holding it for a second or so and then releasing. The screen will freeze momentarily and then unlock to a landscape orientation. From then the auto rotation will work for a while.
From that it's hard to know if the problem is hardware or software but it occured with ICS, JB 4.1 and then JB 4.1.1 and on the first JB installation I did a complete wipe and installation.
Anybody seen this behaviour before and provide some ideas of what the problem could be?
Thanks
