[Q] GT540 G-sensor problem - GT540 Optimus General

Hello everyone
I have noticed a slight problem with my GT540, it is basically very similar to this one with HTC Hero:
http://forum.xda-developers.com/showthread.php?t=545311
Im running my Optimus on Android 2.2.1 FroYo CyanoGenMod OpenSwift4.4 but it shouldnt matter, because this issue is with this phone from the start (1.6 and 2.1 had the same issue).
I also noticed it uses the same G-sensor (i hope it is g-sensor) AK8973, the same that Hero or Nexus is using.
I should mention that i tried to fix it with the instructions there with some differences: the file in /data/misc was called akmd_set.txt but changing values or even removing it did nothing to the Pitch and Roll values.
If the GT540 has the same AK8973 and BMA150 sensors, it should have these values stored elsewhere...
Is anyone having this problem? On leveled surface the Pitch and Roll are about 6 with Sensor Test and also Need For Speed Shift is not leveled. If i want my car to go straight, i have to tilt my phone to the right.
It would be great if this could be fixed. Thanks for every advice!
eXistenZko

Related

seem to have killed autofocus

well, i'm not really sure what i did but i seem to have managed to stop autofocus from working. this is a real problem because it means the barcode scanners can't focus.
i haven't been monkeying around in root or anything (obviously) just installing and uninstalling random apps, but i'm at the bottom of the android learning curve and don't really know how to begin trouble shooting this.
any advice on where to begin would be appreciated.
thanks
I actually think I may have a very similar issue (as it ONLY happens when using a bar code scanning app) but I thought it was just me. Is this what is happening to you...
When I am using a bar code scanning app, the camera starts focusing on the image and just as it gets in focus, it goes out of focus again and then repeats this cycle endlessly. Sometimes it is able to get a lock before it focuses again but not always. I thought it might be a low light issue. I tried turning up the light and it wasn't much different though.
I have this problem, too. I can't focus the camera, it makes the sound, but there is no change at all in the focus when I tap to focus. Also, barcode reader / shop savvy is useless, as the focus on the barcode never occurs.
It seems like this happened when I went to 2.2 via one of many ROMs I've tried.
I suppose it could just be a hardware issue?
What rom and radio are you guys using?
Sent from my Incredible using XDA App
Virtuous 2.7 with the default adrynalyne Kernel
Radio is 2.15.00.07.28
in virtuous 2.7 the focus on my camera sux, especially for night pics w/ flash.
radio 2.05.00.06.11
Just sharing my two cents. I'm running virtuous 2.7 with king's kernal #4, rooted with s-off and 2.15 radio, also on 2.2. Just checked camera after reading this thread and not experiencing any probs thus far. Auto focus working, using touchscreen to take photos.
Im a newb, so I didn't do any modifications other than following directions on this site for rooting, adding roms, etc.. Not any help to you guys, sorry.
I tried downgrading back to stock 2.1, then applied the OTA Update.zip to 2.2, still no luck with the camera focus.
I have a new DInc coming to me under a warranty claim with Verizon.
Hold 'er steady...
Same story for me - won't 'lock on' to the image in order to scan the barcode ~ stock camera. Also tried the EVO camera available in the one of the ROM Manager d/l sections - not much different - for me.
Anecdotally, oddly, I let someone else try w/ my handset, and it worked for them.
SO...... either they have a more steady hand, or.....

EB13 Magnetometer / Accelerometer issues

Hey Everybody I have experienced and corrected the compass / magnetometer issue in the epic by calibrating the unit upside down.
I am curious of a few things.
Does your Magnetometer work correctly without calibration in EB13?
If you calibrate with your screen facing up does it cause the Magnetometer to display erratic results EB13?
If you calibrate the unit while the screen is facing down does it solve the issues?
What Hardware revision are you on?
_____________________________________
::My Results::
Used exe from Samsung to update
Compass didn't work right after the flash.
Calibrated display upside down.
Used compass calibration tool.
Now it works great.
GPS is great.
EB13 is better than DK28 but still has issues....
Hardware Revision
D700.0.5
My old man updated OTA. his compass was fine. Never rooted or flashed.
Mine was messed up by flashing dk28. horribly.
Rooting and running "/system/bin/sensorcalibutil_yamaha" face-up fixed the erratic behavior.
"Settings>display>calibrate" face-down fixed the backwards reading.
Works great now.
EB13 has a calibrate option where I don't recall seeing it in 18?
Hey all,
I am just curious if there is a corrilation between hardware revision and sensor issues. What hardware version are you guys?
Thank you!!!
I noticed issues with the accelerometer mainly when playing Words With Friends. It was damn near impossible for me to not have the words constantly shuffling. This was after having calibrated with the phone face up. I just recalibrated with the phone held upside-down on a door frame and now have no letter shuffling issues in Words With Friends...
gremlyn1 said:
I noticed issues with the accelerometer mainly when playing Words With Friends. It was damn near impossible for me to not have the words constantly shuffling. This was after having calibrated with the phone face up. I just recalibrated with the phone held upside-down on a door frame and now have no letter shuffling issues in Words With Friends...
Click to expand...
Click to collapse
Did it how you did it and.now I have no more rotation lag. Thanks
mindinfiltrator said:
Hey Everybody I have experienced and corrected the compass / magnetometer issue in the epic by calibrating the unit upside down.
I am curious of a few things.
Does your Magnetometer work correctly without calibration in EB13?
If you calibrate with your screen facing up does it cause the Magnetometer to display erratic results EB13?
If you calibrate the unit while the screen is facing down does it solve the issues?
What Hardware revision are you on?
_____________________________________
::My Results::
Used exe from Samsung to update
Compass didn't work right after the flash.
Calibrated display upside down.
Used compass calibration tool.
Now it works great.
GPS is great.
EB13 is better than DK28 but still has issues....
Hardware Revision
D700.0.5
Click to expand...
Click to collapse
Thank you so much! I was on the verge of returning my handset due to the compass not working, I figured the unit was broken. I could not find any info anywhere, and this fixed everything. Now CDompass works, as does Google Sky Chart. Yeah! Thank you!
using bonsai 3.0.0 rom and kernel
both sensors working great no need to calibrate.
i could be wrong but i think everyone has the same hardware version unless somehow you were part of a beta test and have the beta hardware.
i have the same hardware as you.
Unfortunately for me, none of the tips provided here or elsewhere worked. My hardware revision is same as the others here: D700.0.5
I have calibrated the phone facing up, facing down, facing sideways. Ran the sensorcalibutil_yamaha util. Nothing. On a flat surface, the phone points North where West should be. If I rotate the phone a little, it changes its mind completely and thinks East is where West should be.
It has done this with all the various official and unofficial ROMS I have installed on this thing. Is there anybody else in the same boat as I? Is my phone broken and would Samsung fix this under warranty?
Thanks.

[Q] G Sensor not working properly

Hi,
I recently flashed my HTC HD2 with the nand Android 2.2 (HSPL is 2.08.000)
I'm experiencing problems with the G sensor. Sometimes the screen won't flipp within the Browser market place mail client ect. The only app where everythng works fine is Teeter.
Do I have to instell a bug fix? Or is it a known problem with no fix available?
Thanks
Cuerly
It's hard to say without knowing which build you flashed. depending upon which kernel you are using, you might be able to calibrate the sensor.
I suggest that you ask this question in the relevant development thread... once you have 9 more posts under your belt.

[Q] G-Sensor and Compass calibration

Hi I have some Problems with my Magic 32B (rooted, but no custom Rom)
I dont know how to calibrate the G-Sensor and the Compass. I tried to delete the akmd files and the rild_ril files but nothing happened.
There are some akmd-files on the board and on the web, but they didnt fixed my Problem.
Does anyone know what parameter I have to change.
Btw the y-value is about 20, and i think it should be around 10.
Thx
same problem
I think there is the wrong type of sensor defined in /sys/qsensor/vendor
in mine there is written AK89761_0X1 which is wrong for my device, but i do not know the right entrance. I tried AK8973 but this did also not work.
Hours of searching on the web did not give me any results.

How to fix magnetometer

I just fixed the magnetometer on my Vibrant, using advice found on another site. It took me a long time to find it, so I thought I should post it here to help other Vibrant users find it more easily. There is similar advice in forums for other Galaxy S variants, but nothing here.
About a week ago, I noticed that my phone was no longer sensing its position. The screen would not rotate, and the compass was not working. I ran the sensor test using the *#0*# code, and both the accelerometer and magnetic sensor were stuck on one reading regardless of phone position. Rebooting had no effect.
I found the following procedure on a different site. I would post the link to give proper credit, but I don't have sufficient forum privileges because this is my first post. It was on the dp.nonoo.hu blog.
Your Samsung Galaxy S phone’s compass is not working? Auto rotation is faulty? Check your hardware by dialing *#0*# – this is a factory test app for the phone.
If the compass is broken there too, here’s how you can fix it: delete /data/system/ms3c_yamaha.cfg, and if there’s a backup file, delete it too, then reboot.
If it won’t help, make sure the files are deleted and then run /system/bin/sensorcalibutil_yamaha from a root shell, follow the instructions and then reboot your phone.​
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.
Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.
Cheers Blue,
This fixed it for me.
I cannot find neither the .cfg fila and or the configuration app.
+1
These files do not exist in ICS AOKP on my Vibrant and my magnetometer still points in the wrong direction lol.
Trying everything I can find on the Internet.
Edit: Removing the battery does not work even after 15 minutes. However, flipping the phone end over end worked immediately. Seems strange that this is not mentioned by any of the Compass apps yet they tell you to draw figure 8's in the air which does nothing on my Vibrant. lol
Thanks to the individual who shared that tip.
same here, a few vertical and horizontal flips did the trick for me. (on ics passion)
Didn't find the "/data/system/ms3c_yamaha.cfg" on my GalaxyS running Slim ICS 3.2. Seems like ICS doesn't have this file. And some vertical/horizontal flips almost did the trick. Now the compass is moving, before it wasn't moving at all. It not showing very good direction like it used to when I first purchased the device almost 15 months ago.
And one more question, does anyone know, what is the testing code for ICS? Because *#0*# isn't working on ICS. I used this code while on gingerbread and it worked before. I thought this code is universal, but now it seems like, its not.
blueguitarbob said:
I deleted the file using RootExplorer and rebooted. The accelerometer and magnetic sensor were working perfectly.
Click to expand...
Click to collapse
1. Doest it still work when the phone is:
- touched with a little magnet like in a standard vertical flip-case (with little magnet) or
- travelling by car/bus/train or
- plugged in headphones
In the one I had (I don't have it any more) while plugging in headphones, or travelling by car/bus/train, or putting it in an flip-case with a little magnet the arrow In Google Maps pointing the direction which a device is currently facing simply freezes. Compass app also freezes at the same time. The app called Android Sensor Box in the scale for magnetometer reaches its maximum level. While moving the little magnet, from mentioned before filp-case, around a phone the arrow travels with it. Move it away and it freezes. It simply won't move. While sticking S4 to the metal part of laptop table the arrow immediately points opposite direction. Only making 8s in the air helps but only for a bit. Neither S3 9305 nor S5 have this problem. Even when stuck with a magnet their arrows in GM works just fine.
2. Does deleting the file fixes the GM's arrow issue also?
Danstek said:
Lol I fixed mine by simply flipping the phone a few times. Basically I first downloaded and installed the compass app from the market. Then in the app, I calibrate it normally (wave in a figure 8 pattern) a few times. It will still be pointing incorrectly so next all I do it flip the phone on it's vertical axis a few times then repeat with the horizontal axis. Then it will be correct. This always works for my phone, I do it every time after a factory reset since it uncalibrates the magnetometer every time. I've never had problems with the accelerometer though, only the magnetometer. It would always be out of whack no matter what until I figured out what to do.
Click to expand...
Click to collapse
**** this worked

Resources