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.
Related
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!
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
I've found a similar problem, and explanations on why it's happening, but it says that it appeared in Gingerbread but has been corrected in Honeycomb and ICS.
It does seem like the exact same problem with the same symptoms though, so I wonder if it really is gone...
Here is the page where I found the info :
http://fivasim.pcriot.com/androsensor.html
And here is a quote from that page :
Update: After many months of testing and debugging I haven't found a way to fix the battery issue for good. Perhaps I shouldn't... It's not really my issue but a general android problem (just google for "gingerbread battery drain"). And it happens with EVERY app that makes use of the sensors that are the root of the problem.
The battery leakage comes from android sensors that are not well supported by the kernel or the android OS. Most usually the accelerometer sensor causes the issue but sometimes the light sensor and the proximity sensor can cause this issue as well. Other sensors seem to have nothing to do with battery drain.
However I have found what's causing it and ways to `patch` over it (unfortunately, no way to permanently fix it).
Trying to invoke a sensor with such a problem, will cause the sensor to stay open even after the app is stoped and disposed of memory.
Another common issue is a conflict. Two apps register the same sensor, then one app unregisters but fails because the sensor is in use by the other app. The sensor stays in use by one of the two apps and this will remain even after both apps are killed.
In most cases there is a way to fix this:
- In the first case, you may just find which sensor is misbehaving (strange readings, very slow response or 'Failed to start' error etc.). Go to AndroSensor's settings and disable that sensor. Then reboot, run AndroSensor once and wait to see if the problem persists. Most usually the light and the proximity sensors are to blame for this issue. Sometimes the issue is caused only if both light and proximity are enabled, but disappears after disabling any of the two.
- If you don't have a misbehaving sensor then there is probably some conflict. Conflicts can be caused (usually in Gingerbread) when having auto-rotate (accelerometer use) or auto-brightness on.
Solution: Go to your device's display settings and disable auto-brightness and auto-rotation. Then reboot, run AndroSensor once and wait to see if the battery drain continues. If the problem persists then there is probably a conflict with some hidden/system service. Most usual is the conflict with SGS and SGS2 secret menu ( by dialling "*#0*#" on the dialer ). I have found no way to bypass this and it can only be solved by disabling the accelerometer and orientation sensors in AndroSensor, then reboot (orientation sensor makes seemless use of the accelerometer).
The only good thing about this, is that in HoneyComb and ICS the issue seems to have disappeared for good!
Am I really the only one with the problem?
Mithrandir007 said:
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
Click to expand...
Click to collapse
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
chamonix said:
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
Click to expand...
Click to collapse
It does seem to go to deep sleep, but I still see a big difference in battery life between when it happens (around 7-10%/hour), and after I reboot (~ 1%/hour).
Before I start applications using those sensors, the battery life is normal as well, so I don't think it's something else.
I've just made a few screenshots to show what's happening.
Last night, before going to bed, I've rebooted the phone, then started Sygic and AndroSensor, exited the apps, then manually force closed them to make sure.
Then I left the phone charging for the night.
This morning, I remove the phone from the charger, and Badass Battery Monitor starts from that point to calculate the battery drain from everything (so I'm sure neither Sygic nor AndroSensor have been running at all since I unplugged the phone).
Since then, a bit less than 2 hours have passed (I've barely used my phone during that period since I was getting ready then driving to work).
There was a 5% discharge (which is strangely not as much as I had yesterday, but still more than the usual 1%/hour when in standby) and we can clearly see what's eating the battery the most in Badass Battery Monitor.
The "Orientation", "Pressure", "Magnetic Field" and "Accelerometer" sensors have been running the whole time since it was unplugged.
What do you think, is this normal behavior?
I've now installed another custom ROM (Omega 8, with the new samsung firmware update), and the problem seems to remain..
If I'm the only one with the problem, I'm starting to think it might be something hardware (or an app I've installed every time maybe), since I've had the problem with every ROM I've installed...
Switching to another kernel didn't seem to help either.. I'm really starting to wonder if this is something I can fix.
Does no one else have the problem?
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
Click to expand...
Click to collapse
Yes I care. Thanks very much for posting this. I've noticed exactly the same thing and it's been driving me crazy. Good to know it's just a false alarm. With ICS 4.0.4 coming to the Galaxy S2 soon, maybe it will be fix there.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
If this is really the problem that would be an deep in Android or between the hardware and android as it is the 'batteryinfo' service reporting sensors data.
Indeed, I don't think there is an easy fix for this one, unless someone has already worked on that part ((un)registration of sensors from the battery measurement service).
Hopefully it'll be fixed in a future version of the firmware, or in Jelly Bean.
XDA-Usr : maybe it'll be fixed in that version, indeed..
It is just a false alarm, although it still leads to inaccuracy of the battery level.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
luzok said:
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
Click to expand...
Click to collapse
On my Galaxy S4, the problem seems to be gone, so hopefully it'll be gone on your device as well once Samsung releases the 4.2.2 update.
Sent from my GT-I9500 using xda app-developers app
Whatever happen to this OwatchON wake up watch app? I've sen it demoed all over the place early but I don't see it in the Ostore?
It was pulled from the ostore.ppl have tryed many shake to wake apps from the PS. Some with success but most without.
Yeah - I tried "Shake" but it's either too sensitive or not enough. Plus I'm not sure how to just "wake" to lockscreen without triggering an app.
Tony
There's a few issues with the shake apps. Either they keep your processor awake and burn your battery. Or the sensors in the ts seem to sleep once the screen goes dark.
The OwatchOn was pulled due to the 1/8 firmware being broken. This broken firmware is also the reason why many other similar apps have issues as well. The only x201 they do work on correctly is the 512/4 running the "working sensors" firmware.
As many of you may know, for newer version of TS (at least for 4th List, May version devices), it's NOT possible to flick your wrist to show watch face since the Accelerator is DISABLED whenever screen is OFF!!!
What an oversight! A smart watch needs you to push a button to see time? What if when you are driving or have both hand full and cannot spare even a finger!?
(My Pebble, on the contrast, works great here!)
I tried to force the screen always on with watch face, it's great, except it kills my battery in around 6 hrs (airplane mode!) Not acceptable!
Thus, Here comes "Tasface". With this, you could achieve:
1. Let TS shows you time WHENEVER you LOOK at the watch! (well, actually when the watch is face up) or when you flick your wrist (You can modify this!)
2. Reduce using your button (if you have an Shortcut supported launcher like Smart Launcher 2)
Details here: http://forum.xda-developers.com/showthread.php?t=2764787
maybe I'm seeing it right but how do you import the Taskface into Tasker?
When I tried I got told it cannot do such?
Cannot Import
dj898 said:
maybe I'm seeing it right but how do you import the Taskface into Tasker?
When I tried I got told it cannot do such?
Click to expand...
Click to collapse
Same with me, I can't see the xml when trying to import on my TS.
I did something else,I installed the app' shake' and it does almost the same thing without root..
The only minnus is that when you make sudden moves it opens and the battery drains a bit faster...
At this point I am happy Though
I use Awesome on/off with my late model TS, with generally good results, although sometimes it stops working for no obvious reason. It can happen when the watch has been awake very recently. And other times, when it has not been on my wrist for an hour or so, it still works and the clock appears as soon as I pick it up. I've not yet been able to pin down why it behaves the way it does.
Ozpeter said:
I use Awesome on/off with my late model TS, with generally good results, although sometimes it stops working for no obvious reason. It can happen when the watch has been awake very recently. And other times, when it has not been on my wrist for an hour or so, it still works and the clock appears as soon as I pick it up. I've not yet been able to pin down why it behaves the way it does.
Click to expand...
Click to collapse
I can't get this to work at all, did you change the default settings?
death_entry said:
I can't get this to work at all, did you change the default settings?
Click to expand...
Click to collapse
No (as I recall it) just tinkered with the degree setting for personal preference. But I get the impression that on some TS models the sensors work better than on others.
Does anyone else have issues with their unit (I have the T-Mobile version) mistakenly showing their location as someplace they were HOURS earlier? My maps shows the location where I currently am, but then will occasionally report my location incorrectly as where I was earlier that day, which affects my weather and traffic reporting. Any thoughts?
Do you have high accuracy enabled?
I do have high accuracy enabled. Which the phone doesn't seem to understand the definition of.
If it is showing properly when you open maps but not in other apps, then it isn't the GPS that's the issue. Those apps aren't updating properly.
Mine is off by about 20 ft or so ... no biggie.
One thought though ... do you have background data blocked for the map app?
Background data enabled. I'll use the phone to navigate from work to school. The map shows me at school. Weather and traffic based around campus. Then, maybe an hour later, I look at my phone and it gives me the weather for my office, not school. I open google maps, it looks like I'm back at work, but I'm not.
I have had this happen several times. I open a gps Waze and Google maps, for a little while at work then minmize. A few hours later I will use the gps again at a different location and the gps will flip back an forth from the previous location, this will occur 30 min away or in another state.
I have tried to just shutdown the app and restart but still occurs. My only way to clear this has been to reboot the phone. This happen on both Waze and Google maps.
I found turning location off and back on works for me, but this shouldn't happen
Joe Smithereens said:
Does anyone else have issues with their unit (I have the T-Mobile version) mistakenly showing their location as someplace they were HOURS earlier? My maps shows the location where I currently am, but then will occasionally report my location incorrectly as where I was earlier that day, which affects my weather and traffic reporting. Any thoughts?
Click to expand...
Click to collapse
I've had this issue several times. With my G6 and V30. It happens when I'm using a GPS heavy app and then go inside where a good GPS signal cannot be found or where I'm on WiFi. Oddly. I feel like it happens more if that iZat crap is active. Happens a lot with PoGo.
Also get heavy GPS drifting when in High Accuracy Mode. GPS on LG devices seems to work best in Device Only Mode.
Sent from my LG-H872 using XDA Labs
This is driving me mad. I had to switch phone due to this issue on Galaxy S7 and now it happens on V30.
Took a factory reset for mine to work again. Was fine for the entire time I've had the phone, then out of the blue, just stopped working.
Sent from my LG-H932 using Tapatalk
zsunsun said:
This is driving me mad. I had to switch phone due to this issue on Galaxy S7 and now it happens on V30.
Click to expand...
Click to collapse
Chiming in with "other phones have wonky GPS too": My Moto X Pure has had a couple instances where position appeared to be randomly jumping around, up to several hundred feet away with varying azimuth. Made for " fun" navigation in heavy traffic in unfamiliar cities.
But don't worry, autonomous vehicles will work without a problem. (Yeahhhhh....right....)
...
Autonomous vehicles are using a wide array of sensors to work, combine with deep learning, big data, etc. The GPS used in phones is not the same chip as the one used in a dedicated GPS device, even something as a sports watch as a much more precise GPS, optimised antenna, dedicated processor and optimised OS. I’ve been trying to use phones to track my runs for years and it always jumped around a bit. In a car, depending on the placement (direct view of the sky, for instance vs. blocked by the ceiling), on the weather, on the insulation of the car even, you can have issue with jumping signal. You can try to place the phone in a spot where the antenna has a view of the sky and it might be less of a problem.
I have noticed that the issue is with both Pokemon Go and Google maps. It is really frustrating, and sometimes nothing seems to help. On another site, they recommended installing GPs Status and Toolbox from Google play store. I will try that. If that does not help, the site said that the issue is with the GPS antenna.