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.
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
Hi guys, I'm on the latest Vegacomb, I can play Need For Speed or SpeedX using the accelerometer, however, if I try Turbofly 3D (Wipeout clone) or something like Satellites AR then the accelermoter doesn't work at all
UPDATE:
Krazy Karting - the cars just turn right
Riptide GP - even with graphics on lowest setting it takes nearly a second to respond to turning, this makes the game near impossible to play (works perfectly on highest setting on my Galaxy Nexus)
any ideas?
did turbofly work on any other rom , i have always played it with screen controls because even with a perfectly working accelerometer on all my other games it never worked on this game, and i have used all the available roms
Don't know mate, only got my vega about a day after this rom was released
i think Turbofly 3D is also having problem on dropad a8 tablet, guess the game got bug.
Krazy Karting - the cars just turn right
Riptide GP - even with graphics on lowest setting it takes nearly a second to respond to turning, this makes the game near impossible to play (works perfectly on highest setting on my Galaxy Nexus)
Sorry for late reply.
You can try how precise the accelerometer is with this app.
If you can't access it thru the market (like me) I've extracted the apk from my phone and put it on megaupload.
Sorry I can't tell you how precise it is on my unit, because the accelerometer is broken and I will send my unit back for repair in few days/weeks.
This app is monitoring only z-position (green) and it's not moving, but it should go up/down if I move my tablet around.
On my phone all positions are jumping up/down when I move my phone.
I hope that this app works for you and you can see the latency, or how good your accelerometer works on your tablet.
yani2000 said:
Sorry for late reply.
You can try how precise the accelerometer is with this app.
If you can't access it thru the market (like me) I've extracted the apk from my phone and put it on megaupload.
Sorry I can't tell you how precise it is on my unit, because the accelerometer is broken and I will send my unit back for repair in few days/weeks.
This app is monitoring only z-position (green) and it's not moving, but it should go up/down if I move my tablet around.
On my phone all positions are jumping up/down when I move my phone.
I hope that this app works for you and you can see the latency, or how good your accelerometer works on your tablet.
Click to expand...
Click to collapse
Cheers, it force closes on mine
OK, I'm back with some news.
After 1 month my tablet's accelerometer just started working on it's own again.
And here are the results of my findings:
Riptide GP v1.0.1 and v1.3:
- With G-Sensor: it just turns right
- Without G-Sensor: it just turns left
That is all in normal tablet position (landscape).
But if I turn the tablet in portrait (90-degrees left), then I can steer left/right with 1 second delays but the game is not playable anyway because the picture is turned 90-degres.
Krazy Kart Racing v1.2.7:
- With G-Sensor: reverse steering
- Without G-Sensor: perfectly normal steering, no lag whatsoever
Only the graphics was a little bit low, but it's OK.
And the "Accelerometer" app I gave you worked flawlessly!
All three positions were jumping up and down and there we no delay, everything worked snappy (with or without G-Sensor enabled).
I tried all these on stock Android v2.2!
Hope that helps, but I know you have other problems with your tablet right now.
i have the exact same problem you described in riptide with the stock 2.2 rom. how did you manage to fix it? whats this accelerometer app that you mention?
slybunda said:
i have the exact same problem you described in riptide with the stock 2.2 rom. how did you manage to fix it?
Click to expand...
Click to collapse
Sorry, but there is no fix for Riptide GP.
slybunda said:
whats this accelerometer app that you mention?
Click to expand...
Click to collapse
I mention this accelerometer app.
And the megaupload link to apk is here (because you can't install it from market).
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.
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Agreed. I'm in the same boat. I have searched for hours and have come up with nothing.
i never really messed around with cm9 but in aokp(would assume they have some of the same things) u can change the nav bar stuff around have u guys tried any of that?
I'm using CM10 on my OG Galaxy Tab 7, on screen navigation enabled, and LEFT Navigation enabled (240 DPI of course).
Works great.
I bought a Galaxy Tab 2 to do the same setup with, but couldn't get the CM10 Developers to help me get the left navigation going, but it DID work just fine at 240 DPI.
I've been using this setup in my car for a year and a half.
Tablet mode is cute and all, but the bigger navigation in phone mode is better in my opinion. Also, the quick widgets in phone mode are much easier to use while driving in my opinion.
I tried CM10 a week ago or so and had the same problem as CM9 and the buttons messing up. Even when the bar shows to the right, the buttons go from left to right, instead of top and bottom. It is very strange. AOKP did nothing better either.
Since I have the thread open, I've had a few other minor issues that you guys may know something about: I set up Tasker to script wifi/bt/gps/sync on and off with power as well as screen timeout and wake lock on charge. This is to shut down everything with ignition off and wake it all back up with the ignition. For some reason this only works about 80% of the time. It almost seems like a deep sleep or an embeded task killer is destroying the scripts that Tasker is trying to run. There is really no rhyme or reason to it. Tasker just fails sometimes and either I go out to a dead tablet or a tablet that wont stay on.
zavien3 said:
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Click to expand...
Click to collapse
I'm looking to get this SGT2 7" to put in my car dash. I'm not clear exactly what the issue is not having one yet, can anyone post screenshots of the issue or how the keys look? Or let me know if this is no longer an issue? I have not looked into various custom ROMs yet, just figuring out if this is going to work for my car at this point.
If your nav buttons are whats giving you trouble, get rid of them and use lmt launcher.