First noticed a problem using Google Sky Maps. I couldn't tilt phone to view above the horizon. I was on a 2.2 ROM, but I never tried it on a stock ROM. This position sensor error would effect any app that uses the phones position (pitch, roll, azimuth) as an input, for instance game control. It would manifest as not being able to turn or climb. It also effects horizontal/vertical screen switching.
What I know from testing:
A. Download Sensor Debug from market. The simple program lists the sensor values that are reported to programs: Azimuth, Pitch, Roll, as well as force sensed along X,Y and Z axis. If the system is working properly, values with the phone sitting still would read: Pitch 0, Roll 0, X and Y Forces = almost zero, Z (gravity)= -9.xx. Tilting the phone to the left or right, Roll goes +/- 90. When tilted toward the sky, pitch would smoothly increment from 0 to -90 when vertical, and -180 when upside down. My phone when sitting on the table will read (depending on calibration method): Pitch= 0 or -180, Roll =0, Z axis= either +9 or -9. Rolling the phone is sometimes limited to +/-30 degrees. Pitch increments in the proper direction, but is capped. If I start at 0 when flat, it stops at 90 degrees when vertical. If it starts at -180, it stops at -150.
B. Calibration settings appear to be stored in /data/system/ms3c_yamaha.cfg. Changes are real time. If deleted, it is recreated. Values vary greatly. Settings/display/horizontal calibrate effects the values. There is also a calibration utility available from terminal: su system/bin/sensorcalibutil_yamaha. The terminal method has been reported as more accurate.
C. The problem has persisted with full data wipes, factory resets and ODIN return to stock.
So, is anyone else seeing these kind of problems. Questions:
1. What kind of pitch/roll values do you see in Sensor Debug:
2. What are the values in your /data/system/ms3c_yamaha.cfg? and what kind of calibration did you do if any?
3. I want try going back to stock 18 again, but think my method is not complete. What is the most thorough method?
I used the method described in the "my gps fix for 2.2" thread: [guide] my gps fix for 2.2 - xda-developers
. It uses Odin 1.3 and SPH-D700-DI18-8Gb-REL.tar.md5.
There's another "Return to Stock" thread [How To] Return to Stock / Fix Bricked Epic - xda-developers
. It uses the same version of Odin and SPH-D700-DG27-8Gb-REL.tar, and maybe a different PIT. Not sure what a PIT file is.
It appears that the threads re ODIN for DK28 use a different version of ODIN and or PIT, or no PIT.
4. Is it possible that ODIN isn't writing part of the firmware? If I can verify the problem after a thorough return to stock, well maybe it is a hardware issue and I'll just go down to Sprint and get a new one!
Hey thanks for listening! So looking forward to fixing this issue and appreciate any and all help/comments. Thanks!