**IMPORTANT** Please Test. G-Sensor = Cause of 'Random' freezes + Bad Screen response - HD2 Android Q&A, Help & Troubleshooting and Genera

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.

Related

[Q] SoD Confirmed Workaround+Question

Guide:
If you get SoDs as often as I do, you might be getting mad. in fact, you might even go back to WinMo! But, try this tip out.
[0] Disable automatic phone lock / screen time out. (I'm not sure if Aldiko does this)
[1] Download the Aldiko app from the Android marketplace (before you ask, yes, the eBook reader one.)
[2] Start the app and click one of the included books.
[3] Slide your finger from the top left corner of your screen to the bottom left corner of your screen. This is your new "locked" screen.
[4] To unlock your screen, hit the home button and go to your home screen, or phone button and go straight to your phone.
[5] Next time you want to lock your screen, just start the Aldiko app, it should already be a blank screen but if not just slide your finger down again.
Question: Is there any way to make the power/hang up hardware button on your phone start Aldiko?
While I appreciate your creative work around, I've not experienced a hard freeze or touch screen freeze in almost a month.
If your juggling android builds, this can cause corruption in some cases, and can result in said-per SOD.
If your working with an older build, the g-sensor can cause a freeze, but its not quite a hard freeze unless you fiddle with it to the point of it not recovering.
If your using Set CPU and its clocked on the lowest settings, this can cause hard freezes via it being clocked too low to wake up.
These are the main reasons that I've found for my own SOD. My suggestion? Use a WM Rom built specifically for android. Use a RECENT build that specifies that most everything is working. There are some new chefs out there working on builds that aren't quite as polished as some of the more experienced chefs.
Good luck, and may you never experience an SOD again!
M&ate said:
While I appreciate your creative work around, I've not experienced a hard freeze or touch screen freeze in almost a month.
If your juggling android builds, this can cause corruption in some cases, and can result in said-per SOD.
If your working with an older build, the g-sensor can cause a freeze, but its not quite a hard freeze unless you fiddle with it to the point of it not recovering.
If your using Set CPU and its clocked on the lowest settings, this can cause hard freezes upon wake up.
These are the main reasons that I've found for my own SOD. My suggestion? Use a WM Rom built specifically for android. Use a RECENT build that specifies that most everything is working. There are some new chefs out there working on builds that aren't quite as polished as some of the more experienced chefs.
Good luck, and may you never experience an SOD again!
Click to expand...
Click to collapse
The thing about the Windows ROM is bringing up this question. What is the best WM ROM to use? I'm using Miri's V17 but it sucks so much it can't even get the flipping time right... I really hate it, what should I change to?
I'm using ChuckyDroidRom, and its working out pretty well for me. But I cant say its the BEST.
M&ate said:
I'm using ChuckyDroidRom, and its working out pretty well for me. But I cant say its the BEST.
Click to expand...
Click to collapse
I'll give it a try. Anything is better than a POS that can't even get time right... should probably try Elegancia too, hearing good things about that.
Im using an old energy rom from back in june i believe and i will get a random screen freeze. Maybe one every 3 days. thats it. and my radio is still on 2.10 and i can get through a day of normal use with just one battery. Someone had referred to that aldiko app but thats too much trouble. If your getting that many SOD's then reformat your memory card, add a fresh android build. And try not messing with setcpu. Im using the froyo build by tytung and its running great.
+1 for not having anymore freezes. I have not had 1 freeze in the last 7 days using latest darkstone froyo build. Im also using a old full energy rom from july. Also a class 6 8gb memory card.
I think with all this work that has been done on these kernals and builds have REALLY reduced the SOD's.

100% CPU usage and touchscreen glitching?

I've got a rooted EVO and often run into a problem of CPU usage as reported by system monitor spiking to 100% while idle. CPU clock speed stays low however, around 400-500 Mhz but continues to run at 100% until I force close all apps.
This sometimes happens around the time I use 4g in conjunction with wireless tethering to my laptop, but has happened out of the middle of nowhere too.
I use Swype keyboard and it gets messed up when this happens. When dragging between letters the trace goes way off the screen and inserts random characters.
I've tried several different ROMs, Fresh and AVA-Froyo but I get the same problem.
Hm, that's is odd. Another user was talking about 100% CPU usage with 4G on too..so without 4G on how does your phone act?
if it goes away when you force close all apps. go through and close each app separately and wait a minute or 2 in between to see if it clears up. you should be able to find the exact app that is causing the problem then because anything anyone can tell you right now would be a guess in the dark as it is obviously some app you have on your phone causing it.
mistersquirrle said:
When I press on the very bottom of the screen (edge of the glass), it acts as a click to about 1/3 the way up the screen. This is annoying by its self (and doesn't seem ROM related) but also my screen sometimes locks up, with a point at about 1/3 the way up the screen, and horizontally in the middle, and I can't do anything until I lock the screen and leave it off for a second. More recently, but related to this issue, the keyboard when typing hasn't been accurate. I've tried to type 'a' but got caps or 'q' instead, and I get letters I didn't press.
This is not ROM related, as it started happening on CM6 about a week ago, and I've flashed Ava V9, Myn's 2.2, FrEaKy Evo, and CM6, and I have tried stock kernels, and Kings. It seems to lock up more when plugged in also. I've been watching the forums and I haven't seen anyone else post about this, is it just me? It seems very hardware related, but if there is a fix for it that someone knows about, please let me know.
If I get around to it I might take a video of what I'm talking about, but probably only if it's requested.
I'm currently running Myn's Two-Point-Two with King's CFS #11 and am still getting the issues. I've rebooted, and wiped cache/dalvik, flashed new roms, reflashed, nothing.
Click to expand...
Click to collapse
bhughes3 said:
I am having the exact problem, except that the spot that keeps getting phantom clicks is at the very top of the screen, so the drop down bar starts freaking out. I downloaded the program 'dotty' and it is showing that a touch is being registered in the expect spot, so I'm pretty sure it is just an issue with the screen hardware. I want to take it to a sprint store and see if they can replace just the screen instead of getting a brand new phone because I have so much stuff downloaded on it and I don't want to lose data/settings.
It happens a lot, but then I will have days at a time that it stops happening...its just very strange.
Its good to hear that I'm not the only one with this problem. Currently running rooted stock froyo. unrevoked forever. Original June 7th release device.
Click to expand...
Click to collapse
mrjeancw said:
same here...was happening witht he W/q as well...but when your viewing a white page you can see a light on the screen brighter than the rest...
Click to expand...
Click to collapse
mistersquirrle said:
W/q? what are you talking about there?
also the light bright spot is completely unrelated: evo developing a light spot in middle of screen
Screen burn possibly due to overclock
Bright spot in the lower right of screen
I downloaded dotty, and it's saying my spot is at:
X: 159.6
Y: 363.5
and P which I'm assuming is the size of the area being touched at .937.
I tested P and it does seem to be how big of an area you're touching but the biggest that I could get using my thumb was only .235, so it's a huge area and constantly in the same spot. Some times it gives me two points or one a bit up and to the left.
Click to expand...
Click to collapse
Hopefully this helps.
it hink you posted in the wrong thread as this has nothing to do with the op

[Q] Erratic Touch Behavior?

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

Anyone else Got Touch Lag?

Firstly hello to all my fellow Vega UK users!
For the price I think this device is great, but it does have it's issues.
Do any of you have the problem where the touch screen just seems to stop working? It'll kick in again soon enough, but it's frustrating as hell.
Also sometimes the task manager seems to appear by itself, but I can;t get it to appear when I need it?
I'm using Pauls Add-on ROM. (thanks Paul )
Logicalstep
I havn't had any major lag at all.
What do you mean by task manager? do you mean the one when you hold "home"?
I have found after a lot of use, with a lot of apps open that the system can lag. I guess this is due to system resources. Recommend installing ES Task Manager from the market to manage running tasks.
You mentioned the task manager appears by its self, do you mean the home screen selector? I found hitting the home button to many times makes this display.
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
adfrad said:
Some users have reported issues with the touch system when the tablet is charging. Do these issues only appear when plugged in?
Click to expand...
Click to collapse
Yes believe so. due to non regulated power supply causes the screen to become over sensitive.
I get this issue too occasionally, vastly increased when plugged in, now and then when not.
I dont use the machine when its charging.
No real rhyme or reason to it occouring in my experience, id love to know of a cause, other than dirty screen.
Rgds
Lok
Yeah It's a bit of a strange one tbh.
Can;t say I have noticed the lag more when plugged in. I though the PSU was regulated, isn't it just a standard Switch mode PSU?
On the task manager, well obviously there is a task manager with Foryo and oon my Galaxy s I hold the hold button down and it appears, however there doesn;t appear to be a reliable way to do this on the Vega....or am I wrong?
Logicalstep
I never get any touch lag, but I'm not convinced "lag" is the word you want.
"lag" would indicate that the response is somewhat behind the touch action. Android versions below Gingerbread do suffer from that when the CPU is loaded but the Vega is better then most in that regard.
What it does suffer from a _lot_ it erroneous and missing touch events (especially when using a poorly smoothed PSU like the one provided) symptoms include:
1. Swipe gestures being terminated before you lift your finger.
2. Long press actions acting like multiple-presses.
3. (The most common for me) Finger up events failing to register (resulting is erroneous long-presses)
But none of these are "lag". I believe there are grounding problems in the Vega and thus how you hold the tablet and the humidity and static of the environment can change the reliability of the touch screen. It's been reported that having the Vega plugged into a desktop via USB increases the reliability of the display (at least when also charging) which lends credence to the idea that it's grounding related.
What I have noticed ín particular is that holding the tablet in landscape mode makes the keyboard ultra inaccurate. You must press much below the level you want. E.g., if you want to write a Q you hit the A key. It's a bit bothersome while writing...
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
CalumD said:
I haven't experienced any lag, just a slight deadzone at the bottom of the screen and inaccurate keyboard typing. Nothing major. I also haven't really noticed the messed up screen sensitivity when charging that people have been going on about.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
HunteronX said:
Try this out:
http://android.modaco.com/content/advent-vega-vega-modaco-com/327198/screen-calibration-app/
Click to expand...
Click to collapse
I gave if a try, seems to have made typing on the Vega a whole lot better!
Sent from my HTC Desire using Tapatalk
Confirmed over at modaco and by myself also.
Not 100pc improvement but a 90pc. Another essential app.
Goodstuff.
Rgds
Lok
Iv seen lag when I first turn it on but it goes away in couple of minutes, if its on standby it never lags.... cmon honeycomb!!!!
Sent from my HTC Desire using XDA App
The performance pack really reduces start up lag issues btw.
I've seen the device lag sometimes but since i installed pauls peformance pack the lag has gone away making the device so much better.
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
dopeh said:
Well for me the keyboard is still a major issue. Not lag really, but it appears to register my touches multiple times. Right now Im typing this reply on my tablet and I have to go back so many times to correct multiple characters, spaces etc. Its just taking so long and requires so much effort to write a simple message.. for browsing and apps I love it but for email its horrible..
Click to expand...
Click to collapse
Have you tried cleaning your screen and then using the calibration program posted on modaco?
zzleezz said:
Have you tried cleaning your screen and then using the calibration program posted on modaco?
Click to expand...
Click to collapse
Just tried it but doesn't seem to make any difference..
dopeh said:
Just tried it but doesn't seem to make any difference..
Click to expand...
Click to collapse
OK just to be sure...
Is the power supply plugged in? (Screws up the calibration in my experience)
Are you touching the screen while it calibrates?

Gyroscope issue on nexus 7

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.

Categories

Resources