I had realized that the pointer in Google Maps doesn't point to the correct direction. Exactly like this video :
In Google Sky Map, its impossible to rotate 360 degrees, gets stuck in a certain area.
However, the compass works completely fine in pure compass apps, such as GPS Status, or the "Compass" app from Catch.com.
Could someone who have a Razr do a test and let us know if its working for you?
Your help would be much appreciated!
I can report the same issue!
brkelley said:
I can report the same issue!
Click to expand...
Click to collapse
Google Sky only works in horz., must be a Google API to the compass problem See if it works with the razr held flat.
Anybody else?
I can confirm having this issue in Google Sky Maps. No issue in the Compass app (Catch.com one), haven't checked GMaps, yet.
same problems here
chiehkai said:
I had realized that the pointer in Google Maps doesn't point to the correct direction. Exactly like this video :
In Google Sky Map, its impossible to rotate 360 degrees, gets stuck in a certain area.
However, the compass works completely fine in pure compass apps, such as GPS Status, or the "Compass" app from Catch.com.
Could someone who have a Razr do a test and let us know if its working for you?
Your help would be much appreciated!
Click to expand...
Click to collapse
Maybe a noob solution, but might wanna give the compass calibration tool in the GPS-status app a try, it fixed an orientation problem in Maps on my wife's charge...it was only reading accurate directions while moving...GPS vectoring worked, but when the phone relied on the magnetic orientation it pointed in the wrong direction... after compass calibration it worked fine
Related
Seems the accelerometer works in some apps but not in others.
Examples:
aTilt 3D - Yes
TurboFly 3D - No
(some free 'bubble level' app I tried) - No
Anyone know why that would be?
Anyone care to list the apps they have tried and what the outcome was?
I've had a similar experience, the tricorder app recognized the accelerometer but a plumb bob/ protractor app did not. My rookie guess would be a driver problem.
Don't have an answer, but I noticed this as well: Screebl doesn't recognize the accelerometer either...
Don't some of those apps need a g-sensor (which as I understand it is different than an accelerometer...)
??
Xhorder said:
Don't some of those apps need a g-sensor (which as I understand it is different than an accelerometer...)
??
Click to expand...
Click to collapse
For kicks I installed Torque (OBDII reader; fairly useless for me on the nook without Bluetooth, although it does support WiFi OBD dongles), which also measures acceleration/G-force, and at first glance, that measurement appears to be working well.
I expect many things will probably start working properly once we are able to rid ourselves of this castrated 2.1; looking forward to CM7 very very much.
Hi, anyone figured this out? I am desperate to get Screebl working. all Screebl needs is the X and Y axis, which works in some other apps/games.
Reviving an old topic as I'm having the same issue: accelerometer works for Labyrinth Lite and Grow, but not Furdiburb.
Anyone with the same issue? I'm on CM7 by the way.
Any ideas about this?
I never really tested this out, but I remember trying one game a while back, and only seemed to register full 90 degree turns. Anything in between it would not pick up correctly. Maybe it has something to do with the way sensor data is read?
Did anyone update Google Map 6.1.0 and experienced Navigation turning-off GPS when it turn-on and asking to enable GPS (it's already enable) and when you enable GPS, go back to click on your address/destination ... Navigation turn-off GPS again?
I have to downgrade Google Map back to 6.0.3 and the problem is gone.
Running BulletProof with Faux' 0.0.8 beta 7 - themed
antiquezip said:
Did anyone update Google Map 6.1.0 and experienced Navigation turning-off GPS when it turn-on and asking to enable GPS (it's already enable) and when you enable GPS, go back to click on your address/destination ... Navigation turn-off GPS again?
I have to downgrade Google Map back to 6.0.3 and the problem is gone.
Running BulletProof with Faux' 0.0.8 beta 7 - themed
Click to expand...
Click to collapse
no man works fine here, just updated...
Thanks my man. I think it may conflict with my tasker app.
There's still the issue of compass being 180 degress off, I think for everyone...my dad has a stock nonrooted locked amaze and he anything after google maps 6.0, the compass is 180 degress off...I've contacted google and reported the problem. reverting back to pre 6.0 map fixes the problem.
seansk said:
There's still the issue of compass being 180 degress off, I think for everyone...my dad has a stock nonrooted unlocked amaze and he anything after google maps 6.0, the compass is 180 degress off...I've contacted google and reported the problem. reverting back to pre 6.0 map fixes the problem.
Click to expand...
Click to collapse
I have the same issue on my stock amaze.
I'm completely stock with Maps 6.1.0, Compass 2.1.1, and mine points correctly north. It's done so both in Michigan and Arizona (don't see why that would make a difference, but I thought I'd add that note).
gregb882 said:
I'm completely stock with Maps 6.1.0, Compass 2.1.1, and mine points correctly north. It's done so both in Michigan and Arizona (don't see why that would make a difference, but I thought I'd add that note).
Click to expand...
Click to collapse
a 3rd party compass works correctly, but the compass in google maps itself points 180 degrees off... This is getting on my nerves, It confuses the navigation and starts giving wrong directions when you're stopped. Anyone find a solution yet? I have reported this to google twice and the past two updates haven't addressed this issue, and it seems to affect some other phones as well.
seansk said:
a 3rd party compass works correctly, but the compass in google maps itself points 180 degrees off... This is getting on my nerves, It confuses the navigation and starts giving wrong directions when you're stopped. Anyone find a solution yet? I have reported this to google twice and the past two updates haven't addressed this issue, and it seems to affect some other phones as well.
Click to expand...
Click to collapse
Crap! You're right. I just checked and my Maps is off 180 degrees, too. Interestingly, as I was walking back into my office from trying it out, I received an update to Maps 6.2. It didn't help, though; still off 180 degrees.
problem has been fixed with google maps 6.3, came out today!
6.3 has me off by 90 degrees which is better than 180 I guess. It's also really shaky/glitchy in certain places. Oh well... They will get it fixed I'm sure.
Sent from my Energized HTC Amaze 4G using xda-premium
Hi there
Well, i´m using Jokersax´s CM9 based ROM, latest version, and still seeing an issue i also observed with other ICS ROMs released the for Motorola Atrix: the compass is off by 180 degrees...so north shows south.
Right now i have the "Compass" app, from developer Catch, openened and a standard table compass side-by-side and they´re showing this 180 degrees offset. This doesn´t happen with gingerbread based roms..
Anyone can confirm that? I can train my mind to adjust, but i would like to have a working and reliable compass as i have with gingerbread
Thanks!!
I´ll answer myself
Further testing revealed that it´s a software issue with the app i mentioned above and ICS roms. Sad. I´ve tried a few other compass apps and some worked, some not.
Sundroid is an example of an app that didn´t work (not a compass app but uses the sesor input for a few features). GPS status is also off by 180 degrees.
Apps that worked:
Compass PRO
Accurate Compass
Hope that helps someone out there!!
Dorregaray has just posted this on Rootzwiki
gyroscope patch: http://goo.im/devs/Dorregaray/testing
Somehow your link's formatting got screwed up. This folder has the downloads for both CM9 and CM10:
http://goo.im/devs/Dorregaray/testing
spunker88 said:
Somehow your link's formatting got screwed up. This folder has the downloads for both CM9 and CM10:
http://goo.im/devs/Dorregaray/testing
Click to expand...
Click to collapse
Thanks I've now edited my posts .
sstar said:
Dorregaray has just posted this on Rootzwiki
gyroscope patch: http://goo.im/devs/Dorregaray/testing
Click to expand...
Click to collapse
I'm running the 01/06/13 official cm9 nightly. Whenever I open a compass app (I tried 2), the TP crashes (instant reboot).
Here's the link from rootzwiki, where someone else is experiencing the same thing :
http://rootzwiki.com/topic/38033-touchpad-gyroscope/page__st__30
I've installed on Oat's CM10 and am using Compass by Catch. Com and haven't had any problems . It appears the problems reported so far relate to CM9. I'm sure it will get sorted .
Change log?
Is there one?
I have patched to 12/16/12 jcsullins for testing only. Compass sort of works. Can't see anything else.
I'm sorry, I understand gyroscope was the last bug to get fixed on tp but what use is it to us?
Sent from my HTC One S using xda app-developers app
I'd think it would let us play games like Riptide, NFSMW or Asphalt by tilting the TP like a steering wheel as opposed to touching the screen. Could also help with maps and navigation I'd think (among other things)...
Daistaar said:
I'd think it would let us play games like Riptide, NFSMW or Asphalt by tilting the TP like a steering wheel as opposed to touching the screen. Could also help with maps and navigation I'd think (among other things)...
Click to expand...
Click to collapse
I was already able to tilt steer. That's the accelerometer.
Sent from my HTC One S using xda app-developers app
Isn't the Gyroscope just a 6-axis accelerometer? I'm probably missing the concept. What is the Gyroscope patch for? I just tried the 3b patch and feel like I just got the tilt steering working the first time, albeit inverted. Beautiful progress IMO. i didn't even realize it was an issue until the patch since I don't really use it for anything and i use my phone for maps. Would be interesting to see if this affects Google Sky Maps.
A gyroscope would be more accurate than an accelerometer for a steering control. An accelerometer is going to read zero if you are moving the device at a constant velocity for example. A gyroscope measures angular velocity, which should make for a much better response on steering controls.
Great work on the patch, I never knew the touchpad actually had a Gyroscope. As others have said, roll & pitch seem to be swapped with each other (v2 and v3).
If any of you guys need the APK for Gyrospace, grab it here.
Gyrospace 3D Free
Hi,
I got a Kingzone K1 MTK6592 phone last Friday.
Would be almost perfect to me if I didn't have this problem: (Firmware is deodexed and Xposed 4.2.2, some sort of AOSP-like Aliyun OS unfotunately)
The compass and the Gyroscope work perfectly well in the App "Z-DeviceTest" but not e.g. in GMaps (the arrow always points straight north) or other Gyroscope testing apps?? Even in MobileUncle no Gyroscope Data are available.
Anyone has an idea to fix this? The device has a magnetic compass for sure and other K1 owners report exactly the same behavior. So it must be something in the Software.
Please help!
iErp
bump
Noone got an idea? Am I posting in the wrong category for this?
Interesting thing I discovered, at least the compass is working in some apps but in others it doesn't.
The gyro doesn't show any sign of life although it is listed in the specs of the phone (like the compass) and appears in Z-DeviceTest.
All Kingzone K1 devices seem to have that problem.
Are there different methods to read the compass? Or is the gyro just mismapped as compass or something?
Apps working:
"Compass 360 Pro" https://play.google.com/store/apps/details?id=com.proapp.pro.app.compass&hl=de
Brothers "Compass" https://play.google.com/store/apps/details?id=com.brothers.compass
Google SkyMaps
Apps not working:
google Maps
c:geo (Geocaching app)
Gabenative "Compass" App https://play.google.com/store/apps/details?id=com.gn.android.compass
I also have the same issue which is really annoying. Sent an email to Kingzone but I've heard their support isn't too great. Anyone else with a K1 also able to confirm the gyro on their phone?
I am active in the German Forum chinamobiles.org. ANYONE with a K1 confirmed this.
I have the same here, works fine in the test app, but with other apps it doesn't
Noticed it the first time in gmaps and with camera app when taking a picture with multiple angels, normally when taken you can rotate the phone to rotate the picture.
Will be a fix for it soon, we just need to make sure they know about the problem.
I have the same issue. Did anyone resolve it yet? I don't think it actually works in the compass apps either. Its more orientation sensor than gyro....