I have this issue on cyanogen mod 7.1 maybe.
some apps for example for ar.drone 2.0 i use this app https://play.google.com/store/apps/...1bGwsMSwxLDEsImNvbS5wYXJyb3QuZnJlZWZsaWdodCJd (maybe someone know this?) when i move in front this accelerometer go left instead front, and if go on right instead back.
Possible axes are wrong direction on some apps. But the things more strange not all apps have same problems...if play a game race car is correct direction so what wrong?
Sometime others apps is correct but not all apps have same direction correct. Dunno if this issue have something to do on mod 7 or issue for only apps? Wasnt first time happened me...is kinda a bit annoyng.
Someone have same problem experience about it?
I hope can solve problems with cmd 9 but im waiting when is all stable next months.
This is a known issue at least in CM9, I believe
http://teamhacksung.org/wiki/index.php/CyanogenMod9:GT-I9100:Nightly:Known_issues
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?
I dont if anyone else encounter a same problem but for me after installing CM 7 i cant find G-sensor. I have SGS2 and i cant play any racing game which require calibration (asphalt 5, raging thunder). When i start game car just moves either in wrong direction or in circle. No matter what i do it is still do the same thing.
I am not sure but i think it is something that has to do with G-sensor which is not available in latest stable CM.
Any help would be appreciated.
sha587 said:
I dont if anyone else encounter a same problem but for me after installing CM 7 i cant find G-sensor. I have SGS2 and i cant play any racing game which require calibration (asphalt 5, raging thunder). When i start game car just moves either in wrong direction or in circle. No matter what i do it is still do the same thing.
I am not sure but i think it is something that has to do with G-sensor which is not available in latest stable CM.
Any help would be appreciated.
Click to expand...
Click to collapse
sensors works fine for me.
Try a full wipe (data/cache/dalvik cache) and reflash
Sent from my GT-I9100 using Tapatalk
Posting this in the CM thread might have helped...
Please use the Q&A Forum for questions Thanks
Moving to Q&A
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
I have kernel Fusion 5.4 and 5.5 tried.
I have a new problem: Google Maps is very laggy. The "direction-Arrow" of the current location point rotates ongoing. It doesn't get fixed to the direction i'm driving. And the point does not move slightly but it jumps from one point to the next.
Can anyone confirm this?
In other gps apps like oruxmaps i have the problem that the point jumps from one location to the next and does not move slightly too.
Has anyone an idea?
gps has problem in cm10 roms ... compass dances like fully drunken monkey ... use cm10.1 better than cm10 stable fully featured
Hello. Few days ago I've got Huawei M5 10
And I've found strange behavior of the touch screen.
Long story short :
If you slowly move finger in one direction, and then change the direction, touch screen doesnt detect changing of direction and doesn't follow the finger. It waits for 10-15 (or more) pixels and only after that it places touch point into correct position.
I wanted to add video but XDA prohibits me
Its not a problem in regular work, but its annoying in games because you can't take aim in any shooters.
Do you have the same?
I haven't gamed much on my 8.4", but when new I initially experienced some buggy scrolling, possibly similar to what you describe, inside web browsers and what not.
If you are experiencing the same, I recommend:
Upgrading to the latest available OTA. (I actually hate upgrading software, but this was forced o me after a boot loop)
Disable/Delete Chrome (so it doesn't take over for Android System Webview)
Uninstall any updates to Android System Webview (after a reset, some buggy behavior returned for me immediately after updating Webview)
There are other things you can do if rooted. But those were the big things that seemed to fix touchscreen behavior for me. fwiw I can't discount that my upgrade to B153 may have helped, but I suspect that Chrome/Webview was the issue all along.
Thanks for answering
I've already updated Android and even tried to play with screen resolution (thought that because of huge resolutions touchscreens have this problem)
I can't paste link to YouTube but you can find the video named 'huawei medipad m5 10 screen lagging?'
I show there a bug.
Notice that in the name of video Mediapad replaced with Medipad. It's okay.
I'm having the same problem as you but i am pretty sure this is a software issue... But it doesn't bother me much as I use my tablet more for work than games
Hi, did anyone find a fix for this problem?
I don't have this problem on my 8.4. I play alot of first person shooters.