Hello, I would like to ask other users of LG Optimus One about compass. I don't know, if it's defect, or it's normal, neverthless on my Wildfire, there were no problems with Compass like that.
When I launch Compass app (or in Geocaching app I will choose to navigate via compass), it lasts about few minute until compass begin to work! Until that it's stucked and north arrow points everywhere I turn myself - it doesn't rotate in way of magnetic field. It moves around few degrees, but randomly. Until few minutes it starts working and north arrow points to north correctly. But when I turn off Compass app or Geocaching and launch it again, I have to wait again few minutes until it starts working
I tried Google SkyMap and the problem is the same. I tried to calibrate it via moving phone in way of figure 8, it restarts the sensors, but it doesn't help.
Sometimes compass starts working correctly immidiately after Compass app launches, but it's really rare.
I have original ROM version 10a (no root).
Thanks for any help or advice!
Just received my phone today, and I was very susprised first that it didn't embed any gyro sensor (as it is very common in todays' phones) but only accelerometer and magnetic sensors. You can see that notably trying to play with google cardboard VR program which doesn't let you navigate in it..
But even more worrying, I noticed that the geomagnetic field sensor which can determine phone orientation (even without gyro) wasn't working properly..
Indeed, whyle trying to use google sky map app I noticed after 1 or 2 min that orientation started to completely mess up...
It seems sensor is loosing calibration anytime (usually in a few minutes).... I tryed many sensors app to be sure it wasn't software issue but they all fail the same way..
For instance if you try "Phone Tester" and go to sensors status, you can see in compass that there are 3 orientations:
- rotation which points directions (North -Est-West-South)
- pitch which is a rotation on 2nd axe (range going from -90° to +90°; 0° when phone laying on flat surface)
- roll rotation on 3rd axe (range going from -180° to + 180°; 0° when phone laying on flat surface)
As soon as you play with these rotations, you can see they are all okay for some minutes, but after a whyle, one of them remains stucked (for instance compass pointing South all the time) no matter how you rotate the phone...
This is really annoying as all apps relying on 3d orientation (Virtual Reality for instance) aren't able to work for decent time without going crazy. What is strange is that sometimes you just need to restart the app without calibrating sensor again to have it work again but only for 1 minute or so..
It is like if sensor needed to be reset all the time.
I don't know if this is firmware or faulty hardware?
Does anyone has encountered the same issue? I don't know if I need to send it back to store...
If anyone is willing to test using google sky map to see if he has the same issue as me, I'd be glad
I have the same issue using Google Sky Map. In my case, the effect is like the sky in the app vibrate. It happens to me from the beggining, when I start the app.
ok thanks for trying,
well maybe if it does this right at the begining is because you need calibration first? it would be interesting to see if you loose calibration then as I do..
But vibration is normal, it does this also with my galaxy note 8. What is abnormal is that at some point you don't see the sky moving as it should, e.g. there is one direction which is stuck. For instance, you look at south, and then you move your phone to the north, but it stays on the south.. we
but this might be a hint that this phone has an issue with magnetic sensors... maybe firmware issue...
Finally, I have observed that Sky Maps doesnt work as smooth as expected. I tried it in several phones (Xperia S, S4 mini) and i can check that it doesn't work as well as in the other devices. Also, it appears that sometimes one direction is stuck (as you say) but it isn't very noticeable and after move some times the device finally works. I think that is a firmware issue (I have the vodafone spain firmware 26.1.A.1.112).
I hope that my experience can help you
Indeed, your feedback seems quite similar.
I'm still thinking about returning it to shop and take z3 compact instead even if i would loose dual sim... Because im also bothered by the usb OTG issue reported.
Will see...
False alert?
To correct what i reported before. After further successful attempts seems like device isn't faulty and is behaving as expected when used properly . I think mistake was trying to use Google's Cardboard VR kit which simply doesn't work with this device because it doesn't have gyro. I think cardboard's magnet prevent compass from working as expected and might uncalibrate device as well. I don't know why cardboard exclusively use gyro and doesn't support compass as a way of moving head because it should works too...
Just in case someone would have the same issue.
The last time I had Amazfit app register elevation data was the 13th of July. Since 15th every single run has no altitude data. I believe I got the last firmware update on the 13th or 14th.
Currently running 2.8.0.5
Has anyone else noticed this issue ? I have messaged them by means of app's contact us. Not sure if they address issues and how quickly.
Last Saturday I did a 102Km MTB route with 2200 elevation. After 25Km, elevation started to malfunction, not changing values more than 10 or 15 meters till the end of the route. On the next trip the day after, elevation was recorded correct. I'm also on 2.8.0.5 and never ocurred before updating.
Monsterlicks said:
Last Saturday I did a 102Km MTB route with 2200 elevation. After 25Km, elevation started to malfunction, not changing values more than 10 or 15 meters till the end of the route. On the next trip the day after, elevation was recorded correct. I'm also on 2.8.0.5 and never ocurred before updating.
Click to expand...
Click to collapse
there are many amazfit pace smartwatchs having battery isues because of the barometric sensor, probably the Xiaomi to avoid complaints turned off this sensor in this rom, it's just a theory[emoji16]
hermitd said:
The last time I had Amazfit app register elevation data was the 13th of July. Since 15th every single run has no altitude data. I believe I got the last firmware update on the 13th or 14th.
Currently running 2.8.0.5
Has anyone else noticed this issue ? I have messaged them by means of app's contact us. Not sure if they address issues and how quickly.
Click to expand...
Click to collapse
I have the same problem...
Altitude does't work anymore!
Same here... I get a flat altitude. It seems that get the altitude at the beginning and it never changes during the race. Hope Xiaomi cand fix this fast. :crying:
1. Restart watch;
2. Go to Compass widget, calibrate it if it tells you to do so, then tap on it to display GPS + barometer data: it will show four numeric fields, air pressure is in the bottom right;
3. If it doesn't display any value for air pressure or compass refuses to work at all, probably it's damaged and high chances it was due to water damage;
4. Blow some air in the hole (Pace has only one hole for mic+barometer, Stratos has two holes, so water drys faster), and see if pressure increases a bit;
5. If it doesn't change, probably the hole is blocked, clean it with a small needle (but don't push it too further), you can use a small amount of isopropyl if it looks very dirty;
6. Restart the watch before you start an activity, and check barometer as explained above then start recording, it should work fine.
lfom said:
1. Restart watch;
2. Go to Compass widget, calibrate it if it tells you to do so, then tap on it to display GPS + barometer data: it will show four numeric fields, air pressure is in the bottom right;
3. If it doesn't display any value for air pressure or compass refuses to work at all, probably it's damaged and high chances it was due to water damage;
4. Blow some air in the hole (Pace has only one hole for mic+barometer, Stratos has two holes, so water drys faster), and see if pressure increases a bit;
5. If it doesn't change, probably the hole is blocked, clean it with a small needle (but don't push it too further), you can use a small amount of isopropyl if it looks very dirty;
6. Restart the watch before you start an activity, and check barometer as explained above then start recording, it should work fine.
Click to expand...
Click to collapse
The barometric pressure was static so I rebooted the watch and it began to work again. I will have to test it on the run to see if it works, but it looks promising. Thank you
Altitude still doesn't work
lfom said:
1. Restart watch;
2. Go to Compass widget, calibrate it if it tells you to do so, then tap on it to display GPS + barometer data: it will show four numeric fields, air pressure is in the bottom right;
3. If it doesn't display any value for air pressure or compass refuses to work at all, probably it's damaged and high chances it was due to water damage;
4. Blow some air in the hole (Pace has only one hole for mic+barometer, Stratos has two holes, so water drys faster), and see if pressure increases a bit;
5. If it doesn't change, probably the hole is blocked, clean it with a small needle (but don't push it too further), you can use a small amount of isopropyl if it looks very dirty;
6. Restart the watch before you start an activity, and check barometer as explained above then start recording, it should work fine.
Click to expand...
Click to collapse
I restarted the watch before the activity, I calibrated the compass, I tapped on the compass and I could see the four numeric fields, latitude, longitude, altitude and air pressure, everything seemed to be fine. To be sure, I also blew air into the hole of the watch.
I chose the climb activity, the altitude was correct at the beginning, but during the activity the altitude value has always remained the same :crying:
Does anyone have the same problem as me?
cripi said:
I restarted the watch before the activity, I calibrated the compass, I tapped on the compass and I could see the four numeric fields, latitude, longitude, altitude and air pressure, everything seemed to be fine. To be sure, I also blew air into the hole of the watch.
I chose the climb activity, the altitude was correct at the beginning, but during the activity the altitude value has always remained the same :crying:
Does anyone have the same problem as me?
Click to expand...
Click to collapse
Disable alerts in activity Settings, some may cause problems on WOS2...
Disabling alerts in the activity settings was the cause of the problem
lfom said:
Disable alerts in activity Settings, some may cause problems on WOS2...
Click to expand...
Click to collapse
Disabling alerts in the activity settings was the cause of the problem. In the climb activity settings, I disabled "HR alert" and "Auto lap alert" and the altitude value has changed during the activity. :good:
Thanks
will try all of this trick thanks
still did all of this fixes but not working , takes the right alltitude at the start of the activity but doesnt change during
Same issue here. Air pressuer, gps location and altitud are measured well but remains without any modification during the activity.
Had the same in the mountains during a trail with stratos2.... correct altitude at the beginning then frozen’...
Amazefit support : clean the hole..
Ok man but barometer was functioning so its not dust in the hole that cause the problem.. it s a firmware problem... barometers does not supply the GPS when signal lost...
wait next year for fenix6
This watch is not reliable as a fenix or suunto .. sometimes it works sometimes not..
pbxl said:
Had the same in the mountains during a trail with stratos2.... correct altitude at the beginning then frozen’...
Amazefit support : clean the hole..
Ok man but barometer was functioning so its not dust in the hole that cause the problem.. it s a firmware problem... barometers does not supply the GPS when signal lost...
wait next year for fenix6
This watch is not reliable as a fenix or suunto .. sometimes it works sometimes not..
Click to expand...
Click to collapse
i think i am going for fenix and keep this one for audiobooks on running )
cripi said:
Disabling alerts in the activity settings was the cause of the problem. In the climb activity settings, I disabled "HR alert" and "Auto lap alert" and the altitude value has changed during the activity. :good:
Thanks
Click to expand...
Click to collapse
Hi, I have this same problem where my amazfit pace doesn't record altitude. This started happening a few months ago after an update and I thought it was just my phone. I want to try your method but I can't seem to find this HR alert or Auto lap alert in my settings. Please advise! Much appreciated!!
herb0322 said:
Hi, I have this same problem where my amazfit pace doesn't record altitude. This started happening a few months ago after an update and I thought it was just my phone. I want to try your method but I can't seem to find this HR alert or Auto lap alert in my settings. Please advise! Much appreciated!!
Click to expand...
Click to collapse
those setting are available only if you are on 2.8.0.5 rom
Since update to 2.8.0.5, doesn't work for me either. Have tried fixes suggested here but no change. Still doesn't work.
It doen't work in my case
cripi said:
Disabling alerts in the activity settings was the cause of the problem. In the climb activity settings, I disabled "HR alert" and "Auto lap alert" and the altitude value has changed during the activity. :good:
Thanks
Click to expand...
Click to collapse
It doen't work in my case. The altitude during activity is fixed to its initial value.
still struggling with this issue (