I've installed both the 3d Compass app and the CompassX app, both great apps, the 3d Compass is awesome - however, after restarting the watch every day, the Compass reads zero, I try moving it in all 3 axes with rotation and figure of eight motions, but nothing happens, then eventually it kicks in and works, but there is no rhyme or reason to what I'm doing to suddenly start working. After that it continues to work until I restart the watch. Can anybody shed light on this, what is the most effective way to calibrate this thing, or what is triggering it to start working? It's driving me nuts!
Related
Hello, I had this problem on my phone that is the Samsung Galaxy Ace 2 GT-I8160. Initially I tried to use the Auto-Rotation feature back. Once could be in a state of Landscape, when I play back in an upright position at the same instant Portrait indirect screen returns to normal.
Then I tried to play the game Moto Racing, consequently always turn right and crashing. After my rather tilt the phone slightly to the left (left oblique) turns back to normal straight. I concluded my phone, there are problems with the G-sensor is slightly deviated to the left oblique.
I have tried to use the manual calibration sorts of apps Bubble, bubble and so on but the power has absolutely no effect.
Is there really a problem in Hardware G-sensor my phone. What had to be taken to the Samsung Service Centre? But I tried to fix this on their own and the help of friends here.
If there is a solution please help and let me know.
Hello.
It seems my phone need compass calibration (rotating phone in 3 axles) pretty much every time I open any application that uses compass.
In google maps for example the arrow never points to the correct direction, no matter how much I rotate the phone. In fact the compass doesn't work for a while in any app, it takes quiet a few seconds or even minutes before it shows some life, usually it starts working after gps lock, but even then it can be off by 180 degree...
In GPS Status app it's very noticeable. I can place the phone on a table and start rotating it, the compass stays still or jumps all over the screen, depends on the phones angle. Then when left alone the compass arrow constantly moves.
Anyone else have this issue?
Yes, I have the same problem. Very unreliable in TW ROMs, and isn't working at all in CM11.
Mine works fine, it does need calibration once in a while, but once I do that it stays good. Can't say how it works with maps since I always use North up, I get too confused if the map rotates according to my movement. Do you use s-view or any type of magnetic mount etc? That could affect compass and require frequent calibration, I think.
So Just got the 360 as a birthday present to myself. However I am having buyers remorse right now. I want to keep the screen on in ambient mode however it does not work. I have tried with it on and off to no avail. Screen just turns off after 5 seconds. Why is this not working? Am I missing something? I have searched Google for hours and found nothing. This is driving me mad. Also my wrist gesture do not work i was under he impression that when you bring the watch up to your face the screen will come on. Is it possible mine is just a dud?
Any thoughts on how to fix this, as well as any apps that may force screen to stay on?
Turning the wrist with the watch towards me in a single quick move is sufficient.
So the issue was a broken gyroscope or accelerometer. Returned to store for a new one and ambient works fine as does the raise to view time. If any noobies have this issue I would suggest returning for a new one.
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
RetroTech07 said:
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
Click to expand...
Click to collapse
it just closes? or shows a blank screen? (you checked camera access is enabled in QS).
Go to play store and hit uninstall on the camera (it'll revert the camera back to the default version the phone came with).
Also try the camera in another app (it doesn't use gcam but the camera api). Also try gcam in safe mode..
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
Tasker/Automate script to detect when you're connected to your car's particular Bluetooth (assuming it has that), and when so, turn sensors off, and when not connected to your car's Bluetooth, then turn sensors on.
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
there is an adb command to do this
Code:
adb shell settings put secure doze_quick_pickup_gesture 0
Sometimes it just happens, rarely and randomly. Makes a gyro aimed game useless. The figure 8 recal doesn't resolve it. Solution?
Simply invert the display. It will then work normally and will continue to work in the normal position in the next game. Stupid simple easy