Has anyone had any issues with the gyroscope? Is there anyway to recalibrate it?
When playing games I notice it veers to the left, for example temple run on a flat surface, character is running along left wall. I guess this could be an app issue.
Anyone else experience this?
Thanks
Does it use the accelerometer at all? If so, completely close the app, hold the tablet in the perfect "Centered" position, and re-launch. This will re-calibrate the app to the accelerometer.
I get an issue in Modern Combat 3 were within about a minute of play the character ends up looking at the ceiling very annoying. Tried recalibrating in app etc. but to no avail. Anybody else experiencing this?
Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .
flexwong said:
Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .
Click to expand...
Click to collapse
I'm having the same issue!
Everything works fine except the screen rotation, which I have to hold the device completely vertical (or toward me) to make it rotates.
In games, it seems to work fine though.
I have no other issues, and would hate to return it back too.
Is there anything we can do to calibrate this?
satanicsurferz said:
I'm having the same issue!
Everything works fine except the screen rotation, which I have to hold the device completely vertical (or toward me) to make it rotates.
In games, it seems to work fine though.
I have no other issues, and would hate to return it back too.
Is there anything we can do to calibrate this?
Click to expand...
Click to collapse
Ditto here.
My case with stand sits at angle of 15-20 and when a new app is launched it fails to detect that it should be in Landscape mode?
Here's a demo of the issue:
http://www.youtube.com/watch?v=IIYzn54uN9Y
I had to recalibrate my compass to make it work right. There are instructions on youtube -- open an app that uses compass, etc. and spin it three times around on three different axes.
Don't know why, but some apps seem to have compass issues when others do not.
BaronInkjet said:
I had to recalibrate my compass to make it work right. There are instructions on youtube -- open an app that uses compass, etc. and spin it three times around on three different axes.
Don't know why, but some apps seem to have compass issues when others do not.
Click to expand...
Click to collapse
But it's not a compass issue. I downloaded a compass app for my N7, it works perfectly. Just can't get the screen to rotate unless it's held at a perfectly vertical angle.
I don't know if this is just me, but I'm so used to just kinda giving the device a little shake to point the gyro in the right direction (for landscape or portrait), so I haven't noticed anything weird.
flexwong said:
Similar issue, I have to hold my device completely straight up before the screen rotates. Problem with the gyroscope maybe? But when I play games like Rip Tide GP, it works perfectly, senses every single movement, no matter how slight. I'd hate to have to return it, since this unit has no other issues .
Click to expand...
Click to collapse
I also have this. I've gotten used to the fact that I need to just quickly hold ot vertical. On a positive, I find my phone is too sensitive, and when I lay it flat on the table it sometimes switches orientation when I don't want it to, but obviously my Nexus 7 does not have this 'issue'.
I'd say mine rotates automatically at anything beyond say 30-40' from horizontal and while very slowly tilting it to that angle. I definitely do not have to bring it to anything near 90' for this to happen. I am not sure that I'd call it not rotating at 15-20' an issue other than one of sensitivity, and if it becomes overly sensitive it has a tendency to flip at the smallest movement/vibration, which occurs in a number of phones on different roms.
if anyone else is still having this problem I figured out how to fix it. Close the app/ game, then restart with tablet flat on a table or surface. That should reset it at center.
I have been having this problem since day 1. In temple run if i hold my nexus straight he runs down the right wall, i have to hold it about 25-30 degrees to the left to center it. Other games and apps exhibit the same problem. I have yet to find a solution. I have tried all the tips suggested here and even flashed back to stock. No luck yet.
I had an issue where the gyroscope endlessly turns towards one direction. Going to erase the tablet and see if that fixes the issue. Will report soon.
--update
erase and reset resolved the issue for me
I got my new one today (already have one with bad screen) and it has this problem.
Have to hold the tab directly facing me to rotate, games veering off to the right etc.
Calibrating with compass makes everything work until I remove it, then all screwed up again.
Been on to Google for a replacement
i'm developing a 3d augmented reality app and i tried it on my nexus 7 and after a few other apps that i tried that use the gyro it looks like google swapped the x and y axis or something. so it's not really a hardware error, but more on the software side...
edit: or maybe not. but there's definitely something going on with the gyro.
edit2: on further research it seems that the timestamp of the gyroscope sensor is broken, somehow i end up always getting the same timestamp. on my other android devices (galaxy nexus and galaxy s 2) this is not the case. if this is true (and my findings are correct) then this is definitely a bug that needs to be filed to google. can some other developer confirm this?
Hi,
I just started having this problem :crying: :crying: very sad with it.
It worked perfect since I received it a few days ago, then I locked (on the top bar) to use in an app and after I unlocked it it stopped working.
The behavior/test goes as follows:
- on the home screen, click on Chrome (or any other app that is supposed to rotate freely)
- turn landscape CCW, the app turns
- turn it back to portrait, the app does not turn
- back to home screen, open the app again
- opens in portrait
- turn landscape CW, the app goes landscape but upside-down (to be viewed as if it was turned CCW)
- tries rotating the app, it doesn't ever rotate again.
I would hate having to return it, but if it stays like that, I don't have other option.
------
edit:
I've just checked for games that uses the gyro:
Temple Run: the character is always on the right-hand side of the screen.
Highway Rider: although it's possible to turn the moto left, if I center the screen it will go to the right hand side
that's it,
just gave back to Carphone Warehouse (UK) and now I have to patiently wait for them to receive a new one so I can go pick it up.
I installed this https://play.google.com/store/apps/details?id=imoblife.androidsensorbox app that left me without any questions that the accelerometer was not working horizontally on the screen (if you holding in portrait) :crying:
let's just hope that the replacement doesn't have any of the faults that we've been reading around the forum.
I found a "workaround". I installed the "Compass" application from Google Play and use the "Calibrate" option... and it solved the problem.
However, I need to re-do the same steps when I shut down and start my tablet again.
That's the best I found so far...
There is an app called GPS Status & Toolbox https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&feature=search_result
It has a calibration tool and I had to run it a few times but once it got things working, it did stay that way even after shutting down the Nexus 7.
It even stayed that way after removing the app altogether but after altering the DPI to try tablet mode, it knocked the gyro off again so had to reinstall the app.
Such things really are just workarounds though and I certainly wouldn't consider keeping the device and having to keep messing like that.
Fortunately, my replacement has a perfectly working gyro.
Related
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape,
SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZING AND LAGGING BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then Physically turned the HD2 around and Back to Portrait orientation, AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG OR FREEZE.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 back around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
thesweeney said:
I Think I May have found the cause of the otherwise apparently 'random' freezes/hangs and total lack of touch sensitivity.
Basically, In my case at least, It Is the G-sensor/accelerometer.
I have been noticing increasing numbers of these freezes on Mattc 1.5 Froyo, Mainly in Landscape, Mainly in games.
TEST:
I installed 'Iron Sight' Game. (If theory is right then you should be able to use any landscape game, but please try Iron sight if possible.)
I Ran the game and it switched to landscape, SO I PHYSICALLY TURNED MY HD2 TO LANDSCAPE.
THIS IS WHERE THE FREEZES BEGAN!
On the Main menu found it difficult to press any options.
When I did manage to start a Game The control buttons were hard to press and the game was unplayable because screen sensitivity was just not there most of the game.
I Then turned the HD2 Back to Portrait mode AND ALTHOUGH THE SCREEN ORIENTATION STAYED IN LANDSCAPE I DID NOT EXPERIENCE ONE SINGLE LAG.
BUTTON PRESSES WERE RESPONSIVE TO TOUCH AT ALL TIMES FOR AT LEAST 15 MINUTES!
HERES WHERE IT GETS MORE INTERESTING....
I Then Turned the HD2 around to landscape again and the Problems IMMEDIATELY RETURNED.
I THEN HELD THE PHONE VERY STILL IN LANDSCAPE AND AFTER A FEW SECONDS THE PROBLEMS/LAG/FREEZES DISSAPEARED AGAIN!!!
TESTED REPEATEDLY!
IN LANDSCAPE AS SOON AS THERE IS ANY PHYSICAL MOVEMENT, THE GAME FREEZES, BUT IF I KEEP IT STILL THE GAME RESPONDS PERFECTLY WITHOUT HESITATION.
Can some of you please test this theory?
A cradle/Dock would be handy for testing but it is possible to keep the phone still enough in-hand in my tests.
Use the game "Iron Sight" where possible, but use other games/apps too if you have time or inclination
Post the results below ( with logs where possible ?) Please.
Note:
After discovering the above, I did a search on XDA and found that a member called 'Hinky' and touched on this but I think I have narrowed it down.... I think
Please test and confirm (or debunk lol).
Thanks.
Click to expand...
Click to collapse
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
ala380 said:
Yes this is something that the devs have been discussing. It does seem that the freeze issue is in fact related to the g sensor. I don't know if anyone is working on it at this time but I believe Cotulla will try to sort it out for his September release
Click to expand...
Click to collapse
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol keep with the testing though I didn't figure that much out
Hmmm this is def the prob for my touch screen issues. I tested a bit using the latest mattc Leo + Froyo w/Sense 1.5 version, with latest FULLRAM. I found that while on the sense home screen if I hold the phone out in front of me either landscape and portrait it's ok, and I can do whatever I want at full speed no lag at all. THEN if I lay the phone flat, It freezes. I did this like 20+ times and every time It would freeze whether I was playing a game or reading an email.
This also happen to me. Using Mattc 1.5 Froyo, it happens when using internet browser. The screen will freeze or not response right after i turn from Portrait to Landscape or sometimes have to wait for few seconds. I have to turn my device from Landscape to Portrait, and back to Landscape again, then the screen responses back to normal. This also happens in Copilot app when using in Landscape mode.
I turned off the screen rotation
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
robrob777 said:
What I did since i installed my ROM with 380mb ram is to turn off all screen rotation settings, so far so good, I haven't notice any freeze or lag so far in any application or while waking the device up, I used to have it and I hate it, I almost went back to Winmo!!.
Click to expand...
Click to collapse
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
thesweeney said:
This was the first thing i tried but strangely it made no difference.
anyone know how to totally disable the g-sensor?
Click to expand...
Click to collapse
I want to know too! disabling auto rotation doesnt mean completely stop the g-sensor running.
Bimme said:
doesnt have any of the mentioned problems...
iron sight lite runs the same for me when i hold the phone portrait or LS...
have no bad screen sens while holding LS...
running mattc 1.5 with the default zimage...
Click to expand...
Click to collapse
Please tell me....
Did you fresh install 1.5 or upgrade 1.4>1.5?
I had quite a few freezes on 1.4.
Then I upgraded to 1.5 and kept my apps etc from 1.4.
I HARDLY HAD ANY FREEZES AT ALL
Then I did a fresh install of 1.5 and started getting LOTS of freezes.
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
thesweeney said:
DOH! Didnt know it was already a known issue LMAO
I'll get my coat....
Click to expand...
Click to collapse
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
I have the occasional screen freeze on landscape, but not very often using froyostone.
Bimme said:
i did a fresh install.
i deleted all android files on my sd card and extracted the new build to a new made "Android" folder...
i use xanny roms, and i still have the robovoice problem, so i can´t use android daily...
i noticed on all android builds ive tried sofar, that the polling interval of the gsensor is very bad/small. U can see it when u go to calibrate the gsensor, the bubbles move very slowly...
this is not a big thing when u only use the gsenor to turn screen to LS, but it is essential to play games using the sensor...
Click to expand...
Click to collapse
Cheers for that ^
+1 for the Gsensor polling intervals seeming very slow.
THIS CAN BE SEEN VERY CLEARLY USING THE 'VR TUNNEL' LIVE WALLPAPER.
Here the cubes move smoothly at a good fps while the tunnel moves around at what appears to be 4/5 fps.
ala380 said:
Lol, no worries I'm glad that you pointed it out. This was actually one of those really useful threads and the kind of thing that the developers are looking for. I am not a dev but I speak with them pretty regularly when the same issue are pointed out time and time again by those who do not read the threads. This was something that has not been talk about here so I appreciate your well thought post and the information that you provided
Click to expand...
Click to collapse
Hehe, Thanks for that ^.
I dont feel quite so stupid now
For a moment there, before I found out it was a known issue... I thought I had discovered the Androids very own penicilin or something equally as important... but as usual I was behind the times lol.
Jealousy said:
I was just a step before creating a new thread about it when I saw this one.
This is definitely one of the things that are really pissing me off using Android.
Furthermore, I did tests on this issue for quite long to doubt that it's an autorotation related issue. Maybe it has something to do with the g-sensor, but it still would happen randomly even trying not to move the phone at all. I noticed that the problem wouldnt appear that often when decreasing the polling interval of set cpu and same time increasing the min. freq. to 380, but still, it DOES happen.
I'd really appreciate any statement on this, developer side of course.
Click to expand...
Click to collapse
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Do the G-sensor and the Dgital compass 'interlink' or communicate in any way? Is it possible that the screwed up compass output is screwing with the g-sensor output?
I ask this because the game 'hungry shark' thought that my phone was flat whent the usb port was pointed down towards the floor.
Dont know if that makes sense but for me it seems like the g-sensor is fubar as well as the digital compass.
trilbyfish said:
I then used even bigger and bolder letters to emphasize my points!
Click to expand...
Click to collapse
[SARCASM]Very helpful buddy[/SARCASM]
I did the font size thing for people who just wanted to skim through the long post.
thesweeney said:
Possibly not related to autorotation per-se, but...
With Autorotation disabled... If I turn my phone on its side (with volume buttons pointing towards floor) I still experience freezes on my home screen or anywhere else for that matter.
Plus I have found that holding the phone VERY still in any position seems to eliminate 'ALL' freezing and lagging problems.
Click to expand...
Click to collapse
Well ofc, it wouldn't freeze when it's COMPLETELY hold still, but I guess that shouldn't be the point of daily usage.
Now when it comes to spontaneous outside actions, you are trying to pick up a call using touchscreen cuz ur used to it or trying to shoot out a text in hurry, and your device will just go sleep for some time. I mean, how'd you hold still if you're moving (fast)?
If you ask me thats pretty much a major bug, not to forget the 3g data thing. I'm not moaning around, just want to attain more focus on this. I notice people losing themselves in some benchmark trolling - just time waste.
There is already a thread for that (walking dead)
Just found a possible solution, please repport if it is better for you too :
- boot windows mobile, calibrate the g-sensor in settings (i did it 2 or 3 times, but i don't think its important)
- do a proper shutdown of wm
- restart wm + android
Sent from my HTC HD2 using XDA App
After disabling "Auto-rotate screen" I haven't had a freeze yet, so good so far.
First noticed a problem using Google Sky Maps. I couldn't tilt phone to view above the horizon. I was on a 2.2 ROM, but I never tried it on a stock ROM. This position sensor error would effect any app that uses the phones position (pitch, roll, azimuth) as an input, for instance game control. It would manifest as not being able to turn or climb. It also effects horizontal/vertical screen switching.
What I know from testing:
A. Download Sensor Debug from market. The simple program lists the sensor values that are reported to programs: Azimuth, Pitch, Roll, as well as force sensed along X,Y and Z axis. If the system is working properly, values with the phone sitting still would read: Pitch 0, Roll 0, X and Y Forces = almost zero, Z (gravity)= -9.xx. Tilting the phone to the left or right, Roll goes +/- 90. When tilted toward the sky, pitch would smoothly increment from 0 to -90 when vertical, and -180 when upside down. My phone when sitting on the table will read (depending on calibration method): Pitch= 0 or -180, Roll =0, Z axis= either +9 or -9. Rolling the phone is sometimes limited to +/-30 degrees. Pitch increments in the proper direction, but is capped. If I start at 0 when flat, it stops at 90 degrees when vertical. If it starts at -180, it stops at -150.
B. Calibration settings appear to be stored in /data/system/ms3c_yamaha.cfg. Changes are real time. If deleted, it is recreated. Values vary greatly. Settings/display/horizontal calibrate effects the values. There is also a calibration utility available from terminal: su system/bin/sensorcalibutil_yamaha. The terminal method has been reported as more accurate.
C. The problem has persisted with full data wipes, factory resets and ODIN return to stock.
So, is anyone else seeing these kind of problems. Questions:
1. What kind of pitch/roll values do you see in Sensor Debug:
2. What are the values in your /data/system/ms3c_yamaha.cfg? and what kind of calibration did you do if any?
3. I want try going back to stock 18 again, but think my method is not complete. What is the most thorough method?
I used the method described in the "my gps fix for 2.2" thread: http://forum.xda-developers.com/showthread.php?t=869806. It uses Odin 1.3 and SPH-D700-DI18-8Gb-REL.tar.md5.
There's another "Return to Stock" thread http://forum.xda-developers.com/showthread.php?t=773032. It uses the same version of Odin and SPH-D700-DG27-8Gb-REL.tar, and maybe a different PIT. Not sure what a PIT file is.
It appears that the threads re ODIN for DK28 use a different version of ODIN and or PIT, or no PIT.
4. Is it possible that ODIN isn't writing part of the firmware? If I can verify the problem after a thorough return to stock, well maybe it is a hardware issue and I'll just go down to Sprint and get a new one!
Hey thanks for listening! So looking forward to fixing this issue and appreciate any and all help/comments. Thanks!
I've had the same exact problems that you're having. I've done the same things you've done to try and fix the problem but nothing works. I've really only noticed the problem in sky maps because I haven't played any games that required going above the horizon. Hopefully someone can figure out a fix for this because I'd really like to use sky maps again.
I used the link above, return to stock, last page of that thred. Odin3 ver 1.67, and DI 18 stock with no PIT. Sensor debug values are the same....
What are your sensor debug values? Maybe try the su calibrate if u can.
Went to Sprint store. Nominal debug values on an Epic and an Intrepid...
Not a tech store so walking 1 mi to the other one. I am resolveed that I have hardware issues, or at least issues that ODIN can't fix.
I don't have insurance, but it's only 3 months old...should be covered?
Make a big scene, ask for manager... they may try to refer you to sammy warranty... don't put up with it. But the 7 bux a month is def worth it...
I don't think that the problem is the hardware. Sky maps was working for me before flashing over to the froyo roms. I'm just hoping that once the official froyo is released, it'll be fixed with that.
Update of my journeys....
2 mi walk to the tech store. 45 min later, they say yes the accelerometers are faulty, you need a new phone. Don't know what they did, but the only two things not stock on the phone where Google Sky and Sensor Debug.
So great, I get a new phone! But wait.... "it'll be here in a week." But I don't live in San Francisco, so that does me no good. They say to talk to go to my local store in SC, or call CS to get it mailed. Evidently they won't swap with a retail phone.
CS is no help. Won't authorize a retail swap. Won't have replacement sent to residence or my local store. I'll try calling them tomorrow.
In the meantime, I'm going to ODIN 1.6.1 straight to SPH-D700-DK28-8g-rel.tar.md5 OFFICIAL with no PIT, one click root, and restore my Bonsai system and data. My previous 2.2 upgrades have all been via update zip from DI 18.
So I guess the question remains, does the phone have hardware issues, or did my 2.2 upgrade dork something up that ODIN can't fix. Seems like it will be a while till I can Google Sky....
You cannot use another person's accelerometer values. Each and every accelerometer is different and calibrating will give everyone different values.
To fix the accelerometer you can run the following command in a terminal emulator :
Code:
su
/system/bin/sensorcalibutil_yamaha
The problem is that something has changed from Eclair to Froyo that Samsung hasn't taken into consideration. The update from a DI18 stock to the OTA Froyo should work without a hitch.
Hopefully w/ the official Froyo update we will get a fix. Otherwise, we should confer w/ noobnl or the CMSGS team to figure out how they were able to resolve the issue.
I've used the utility numerous times. Agreed that individual accelerometers would be somewhat different, but I think the differences wouldn't be very large in the .cfg file. The utility is "fine" calibration.
My device has gross errors.... Z axis prior to running the utility is +9.xx instead of -9.xx, and lay flat pitch is -179. The utility helps a little, but pitch values are referenced wrong, and don't increment properly even after running it.
Obviously there are areas of the phone that don't get reset with ODIN return to stock (Phone remembers the time, account info, etc). Sprint Tech couldn't get the g-sensors working right either with what ever reset procedure they use. Either data is stored on a level ODIN can't reach, or it's hardware failure.
Im a complete noob so correct me if I am imagining this... I had the same problem and fllashed back from froyo. Did the su/system/bin/sensorcalibutil_yamaha fix and it worked. Started restoring all my stuff and the orientation started to dog again.
I messed around and tried changing my launchers. I was using ADW and switched back to TW and the response was much better. I changed to Launcherpro and it is a little slower but not as bad as ADW. Am I high? Please forgive my noobiness.
I have noticed the same problem. The D18 rom was fine and all the games worked good. I checked the horizontal calibration and the sensors seem fine but the games and sky map don't seem to register properly with 2.2. I'm waiting for the OTA to come out b4 I take the phone back for a swap.
I'm actually having the exact problems you all are having with the pitch sensor, ever since I moved to DK28. Right now it is annoying, but I am hoping it will be resolved when DL11 is released. If not, it looks like I'll have to call Sprint and have them get me a new phone, because some programs don't work correctly right now.
Sent from my SPH-D700 using XDA App
I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App
styles420 said:
I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Wow...that seemed to help a ton. The games are off, but I don't really play them anymore so no issue. Sky map actually works now. The auto rotation is much better also. Thanks.
Edit: This fix works. I also started my game prior to doing the fix paused it and did the calibration. The game works great now.
styles420 said:
I noticed this problem while using maps, my compass seemed to have East and West swapped (but North and South were fine). I used the calibration tool in the Settings menu under "Display" (horizontal calibration), but I put the phone on the table upside down (hanging off the edge enough for the "calibrate" button to be in reach).
Not ony did this fix my compass, it seems to have improved the auto rotation response time dramatically
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks! This seems to have fixed problem. I'm not exactly sure which part fixed it for me so I'll just go through what I did. I placed my phone face down and did the calibration in display settings, but then my phone wasn't switching to the correct orientation, so I rebooted my phone to see if that would help. It didn't. So I then did the terminal emulator calibration and now it's fixed. So, that makes me wonder if it has something to do with the calibration utility in display settings having some settings that are flipped around.
Woah... that worked. For whatever reason, it actually worked. Hmm...
Sent from my SPH-D700 using XDA App
Wow!
I actually tried the upside down trick once before with out success. Thought I had some results this time... then added another step. Voilla!
1. Working on a rooted froyo ROM. Upside down horizontal calibration from system/display/settings/display.
2. Reboot. (Not sure if that step is needed)
3. Connectbot su system/bin/sensorcalibutil_yamaha
At this point, sensor debug showed no success. Pitch and roll both limited to 30 deg.
4. Settings/display/autorotate. Uncheck.
Back in sensor debug, every thing checked out.
Anyone think it's still fixed if you enable autorotate?
Sent from my SPH-D700 using XDA App
I agree that the calibration in display settings seems to be the problem, sensorcalibutil works fine right-side-up. But sensorcalibutil didn't seem to fix the orientation lag, so it's possible that the display settings' calibration is correct, the internal compass I installed upside down, and sensorcalibutil has been modified to compensate... but I doubt it, the hardware should work no matter what the orientation, so a software problem in the settings' calibration is more likely the cause
Sent from my SPH-D700 using XDA App
I've tried everything in this thread and I still can't get google sky maps to tilt up, above the horizon. Anyone word on EB13 resolving this particular issue?
no matter what i do, pitch is never a positive value in sensordebug..
same with sky maps. only other problem i'm having after calibration with the exception of an occasional compass jitter
I also have a problem with Sky Maps.. Pointing up will not register.
Has anyone run into issues w/touch on this device periodically?
I've been having problems with mine from time to time where a touch is registered in the wrong location... like very wrong, I notice this most often when looking through menus in the system settings.
I fight with scrolling properly in a few diff apps. One in particular is pocket informant. Some times I also have trouble switching home screens and the transition starts to twitch when it hits about half screen then ultimately returns to the screen I'm trying to move away from.
If you would like a video I can try to capture it
Is this common or should I start an RMA and get a fresh new A7 on the way?
I've had this problem sometimes. I think it's because the screen is probably low quality or something is.
Ive also noticed that if I bring it too close to my face to see the side buttons in the dark, my breath on the screen makes things jump around spastically.
eskaryo said:
Has anyone run into issues w/touch on this device periodically?
I've been having problems with mine from time to time where a touch is registered in the wrong location... like very wrong, I notice this most often when looking through menus in the system settings.
I fight with scrolling properly in a few diff apps. One in particular is pocket informant. Some times I also have trouble switching home screens and the transition starts to twitch when it hits about half screen then ultimately returns to the screen I'm trying to move away from.
If you would like a video I can try to capture it
Is this common or should I start an RMA and get a fresh new A7 on the way?
Click to expand...
Click to collapse
My screen has been touchy as well
My Acer works just fine for orientation sensor games, like asphalt, need for speed, etc. However, when I use things like ilighter, ibeer, etc the orientation is very off. The application is supposed to be help in portrait mode to be considered upright. However, when I want to use the program, I actually have to hold it in landscape (a 90 degree turn counter clockwise ) to actually have the program register that it is "upright". I originally thought that this was a problem with the program, but there are a number of programs that act this way. It acts this way regardless of orientation lock on/off or any settings, and only impacts on some applications.
Is this a common issue on the tablet device due to honeycomb issues, or is it something wrong with the sensor?
Anyone having similar issues?
Thanks in advance.
This is probably due to the different Android versions we use.
I have noticed the same issue on some apps that were made for my phone running Froyo (2.2). The app works fine on my phone and it reverses every sensor on my tablet so it becomes useless. The app you're trying to use is probably not made to support the tablet hence the sensor problems.
Ive been testing this out with other things. like bubble level, flight games, labrynth, etc. ever application is off. It seems to be seeing the x and y axises as being different. x=y y=x etc.
Anyone able to try downloading ilightr or ibeer or bubble or some other setup and seeing if they have the same issue or not, please?
phoenixbennu said:
It seems to be seeing the x and y axises as being different. x=y y=x etc.
Click to expand...
Click to collapse
exactly the same here...tested with ibeer, bubble, turbofly 3d.
i don't know if it's the same problem with a 3.1 version. i've tested all the apps with 3.2
Been using the 2nd gen Moto G for a week and I've noticed the touch screen isn't as sensitive/accurate as my previous phone (NEXUS 4). For example, when I scroll (in Facebook, Chrome etc.), the app opens links and images if my thumb is over either one. It's the same with gallery. If I were to scroll then halt, it'll open the image under my thumb. It's doesn't happen often, but enough to take notice. I have to press slightly harder (compared the NEXUS 4) for the Moto's touch screen to register accurately. Can't use light touches reliably at all. Has anyone experienced similar/same issue?
Not an issue with me like this
Works fine
It is by no means bad, but it takes a little bit of getting used to. I'm guessing they'll fix it via OTA if it needs fixing.
I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.
anshumandash said:
I have noticed the same thing. I am also coming from nexus 4. I find these touch issues very irritating. Overall scrolling isn't as smooth as the n4 as well. I think scrolling could be related to the kernel configuration.
Click to expand...
Click to collapse
Glad I ain't the only one. Hopefully it is software related and can be addressed via update
I have this only when I charge my phone with a specific wall adapter, everything else is fine
Gabboplano said:
I have this only when I charge my phone with a specific wall adapter, everything else is fine
Click to expand...
Click to collapse
Strange, I didn't notice this issue before yesterday's OTA.
Will try other another wall adapter.
I'm currently using the Sony/Ericsson LwW adapter (5V/800mA).
My Moto G 2nd Gen had this issue too, but it also had problems where occasionally the touch screen would interpret scrolling as tapping and vice versa, in the end, I had to RMA it.
I had mentioned earlier that sometime scrolling would consider as tapping and would open apps/links etc. Some time tapping needed multiple taps. I just removed the screen guard and this problem is mostly not noticeable any more. Just thought this information might help some one.
My phone came with the official charger of 550 MA and I don't get any screen freezing while the phone is charging with it.
Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5
sahil kaul said:
Okay, i had this problem too. However i got the phone replaced so now i'm using a different handset and the issue is resolved for me. At first even i thought that this is the problem related to the software but i started to notice this over and over again. So i spoke to flipkart and they agreed to replace the handset. So i suggest to all the people who are having this problem to get your phone replaced.
Sent from my Nexus 5
Click to expand...
Click to collapse
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.
anshumandash said:
Did you have the problem even without a screen guard? After I removed the screen guard, I get this tap while scrolling may be only once a day. Normal sensitivity is far better without a screen guard.
Click to expand...
Click to collapse
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5
sahil kaul said:
As soon as i got the phone, i booted it up with the screen guard on that's when i first realise that there is a problem with the scrolling and tapping on the touch screen. I removed the screen guard immediately and even after that the scrolling was mistaken for tapping. Used it for a few days and still had the issue. It did not happen very often if I compare it with the screen on time, but it was enough for me to be pissed at. I would rate it at about 30 % of the time when im scrolling, sometimes in a music playlist or when i am browsing or scrolling just about anything.
Sent from my Nexus 5
Click to expand...
Click to collapse
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.
delete please
anshumandash said:
I have another question. In the new phone do you see any stuttering or jitter while scrolling through apps. It harkens to me in many apps even on g+, scrolling through contacts, Facebook, Tapatalk etc. I know this could be software related. But just wanted to check with you. Now the tapping during scrolling issue happens really less, but it happens if the scrolling is jittery.
Click to expand...
Click to collapse
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.
touch sensitivity
this problem appeared once, after an update from motorola.
Factory resetting it solved the problem xd
Nielo TM said:
I have a feeling that is also to blame. I've noticed it when using FB, Chrome etc.
The surface of the glass may also be one of the culprits. My thumb and fingers don't glide as well on the Moto compared to my NEXUS 4. Sometimes I have to apply bit more pressure to keep my thumb firmly on the screen. Otherwise I can feel it loosing contact. It's very obvious after cleaning the screen with soft cloth. Maybe it is to do with the coating? I've ran touch screen tests and the screen detects inputs just fine. I don't see the point of returning mine, cos they won't find anything wrong with it.
PS: Android L should drastically reduce or eliminate stutters (and lag) thanks to Android Run Time (ART). People are already seeing major improvements, but I don't recommend enabling it in KitKat. It's can screw up your phone and apps. But if you wanna take the risk, click on ART Under "Select Runtime" option in developer options.
Click to expand...
Click to collapse
I completely agree with you. This phone has got two coatings. One called splash resistant and the the other is finger print resistant coating. I think those are another cause the finger doesn't glide well on the screen. I am also coming from Nexus 4 and I can feel this problem every time as I still carry the N4 with me. I too ran touch screen tests and everything looks fine. I am not sure if I RMA how will the 2nd device behave. It might be same. I can actually replace it from Flipkart.com from where I bought, but I am not sure if that will help.
I read some review comparison between the new moto g and new moto x and the reviewer has commented that Moto x 2014 screen is far more responsive than the moto g 2014. I know the problem was real bad with the stock screen guard on the screen. If I need to manage with the phone, I know I will have to use the phone without a screen guard.
I tried using ART as I have been using that on my N4 since Jan 2014. But in Moto g the app optimization starts at every boot with ART taking more than 10 mins for every boot. I wrote a mail to Moto support and they said there is a technical problem with the builds and they suggested me to use Dalvik. I think they won't fix it till Android L drops in.