Hi. I'm unsure if this is covered elsewhere. If so, please disregard.
After getting the OTA 3.2 upgrade (unrooted; obviously), I noticed a bug. If I had any applications that weren't set as the default app for a specific piece of functionality, then the option to choose which app to use no longer appears.
For example, prior to 3.2, if I clicked on a bookmark, I was prompted whether to use the default browser or Opera. I didn't set either to use as a default because I may use one or the other depending on the situation at the time since both treat pages differently.
Another example of this shows up when clicking on either the ASUS weather widget or the weather info on Beautiful Widgets. Again, clicking on the forecast for either of these will call up a browser page but since I didn't have a default one selected, the screen dims, but no option to choose a browser appears.
This isn't limited to the browser. I'm getting the same "dim screen, no option to choose" with other programs that had no default option set, such as movies. Prior to 3.2, clicking on an MP4 movie asked me if I wanted to view in the gallery or PowerAMP. Now.. ..nothing. Dim screen. Clicking anywhere or hitting 'back' returns to the screen without the file being played.
It seems any attempt to launch any file or in-app link that points to a link or file that is unassigned results with the same "dim screen" road block.
Anyone else experiencing this? or am I the only lucky one getting this frustrating bug?
Edit: Possible temporary fix...
Quick afterthought. It may be possible with some apps to set "use as default" for a specific file type in the app settings and this may fix this issue for myself and any others. Personally, I don't want to do this. I like being able to choose on the fly and would like this bug fixed. Still, if it's going to be weeks until a fix arrives, I may need to use this workaround (if it is even possible for all my affected associations) so I'm not standing still till a patch comes.
UPDATE:
While I can't be sure this fixed the problem, I undocked the tablet and removed both a 16GB MicroSD (from the unit) and a 16 GB SD (from the dock) and then re-inserted both memory cards and the tablet into the dock. After that, my links called up the association window again. I 'believe' it was reseating the tablet into the dock that corrected the issue, but ejecting and putting the memory cards may have been the answer. Note to self: check results after 'each' step.
Just tested this on mine and no I do not have this issue, I still get all the prompts for what to open stuff in be in links or videos from file managers etc
I just noticed this problem too. Very annoying, reverting to previous firmware...
I got this bug too. I tried the above solution as suggested but no luck. Then i tried another one from one of the threads here. It works!
http://forum.xda-developers.com/showpost.php?p=16100385&postcount=4
Hell, my bookmarks don't even open at all.
There is no pinch-to-zoom either.
Edit: tried the above & it did work how strange. I have auto rotate turned off.
Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.
Removing the dock and putting it back on seem to have solved the problem. Thanks for the tip!
OK I did some more tests: upon a reboot with the dock on, the problem was back. With the tablet in the "stuck" state, I removed the dock and the selection screen magically appeared.
I had this very same problem. No dock or SD here... Did the portrait - landscape rotation cycle and everything is solved now.
Regards.
This makes for a workaround, and I'm thankful for that, but I think the underlying problem is that while in Landscape mode, the OS won't go through the process of asking for a choice of browser, and you can't make the rotation with the keyboard attached. I went through the removal and rotation, and that was fine until I reattached the keyboard and was back where I started.
I had to remove it a second time, and this time assigned a default browser, then subsequently was able to operate properly with the keyboard back on. This problem is going to confuse the heck out of casual users, and ASUS will need to fix it pronto.
JoTeC said:
Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.
Click to expand...
Click to collapse
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.
nego_0 said:
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.
Click to expand...
Click to collapse
Unfortunally this was the first problem I noticed. It happens all over again when you shut the unit off and restart with the dock plugged it. I guess with this official thread maybe someone from Asus will notice it? Not holding my breath. Wonder if full factory datat reset will help. I've found when updating android on my phone tht helps wierd problems but don't want to have to go through all the re-setting up and downloading of my programs.
What a hassel. I guess when they officially begin supporting 3.2 over the phone line I can get them to resolve? Not holding my breath for that either.
I've been thinking about this further and think I might at least be able to point to the culprit (granted, in a 'shoot an arrow into the air' and you're bound to hit something manner).
Recently, ASUS made a change to the way the tablet behaves when docked. Specifically, in the way the auto-rotate functions while docked. Prior to this change, you could view your screen in portrait mode (even if docked) by turning the entire tablet + keyboard 90° or more. After the change, the screen locks at landscape oriented with the tablet in place. Flip it around now and it stays oriented (even upside-down).
With some applications, display boxes are written to start in a specific orientation which will then flip based on the current viewing angle. Since Android was (first and foremost) a phone OS (that uses portrait as it's main orientation), it may start most pieces of functionality such as display of the "choose desired app" dialog box in portrait mode but rotates it based on a call to the current device orientation status. However, I'm wondering if the OS can't reconcile that it is in landscape mode because auto-rotate has been turned off with the change ASUS made when the tablet is docked (making it specifically an auto-rotate issue), or if this change is blocking the dialog in another fashion due to the way ASUS programmed this functionality to communicate with the OS (making this a 'ASUS isn't playing well with Google' issue).
In short, this may be a bug relating to either a "auto-rotate / forced orientation" toggle, or a bug with the ASUS "lock orientation while docked" functionality.
It could also be related to the new "default size / zoom to view" 3.2 functionality mixed with a locked viewing angle.
Thoughts?
Edit: Just did a test. Rebooted the tablet (while docked) and the bug occurred; as expected. I lifted the tablet out of the dock but didn't change the orientation. I just simply lifted it up, then set it back into the dock. When I launched an html link, it now works. I know that some users (without docks) are able to fix this by simply changing orientation after booting. The process of unseating, then reseating may be providing a similar function as changing the orientation does with a dock-less tablet.
Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.
CalvinH said:
Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.
Click to expand...
Click to collapse
It is bit ridculous that the bug comes back aftrer a reboot. I guess with 3.2 we are supposed to reboot?
I'm not 100% sure about this but don't Android apps actually shut down and restart instantly when the orientation is changed?... so doing this restarts the Launcher?
And the same happens when removing and inserting into the dock? launcher restarts...
Try this... reboot in one orientation and test and try the other.. i.e. Boot in Portrait and see if the bug is there then change to landscape to see if that fixed it... then boot in landscape and test..
Related
Are there any tweaks/apps that allow you to tailor the backlight's behaviour depending on what app you are using and set it up to suit each one?
I can't find anything like that but the reason I'm asking is as follows.
I want the backlight to stay on indefinitely when I have adobe reader open, but I don't want it to stay on indefinitely for anything else.
I read ebooks in adobe reader and it has no setting for this, so you either have to change the overall backlight settings to stay on then change them afterwards or just put up with constantly having to touch the screen to get the backlight on again.
What I'd like ideally is something almost like the Changescreen app (for rotation) where you can choose the apps you want and set how the backlight behaves when each app is in use.
Is there anything that does this? Or have I overlooked some really basic way of doing it?
Cheers
You can try Lumos: http://forum.xda-developers.com/showthread.php?t=450318
Thanks mate - that could be just the ticket.
Bah - tried to install it and as soon as I click it I get a "Installation Unsuccessful" error.
I'm on a custom rom but I forget which...
Bugger - looks like it could have been perfect.
Hmmm, I've installed Glight now to try that out but I can't get it to work for some reason.
It's enabled.
The phone's own auto backlight control is disabled.
I've added adobereaderle.exe as an exception and set it so it keeps the backlight on permanently.
I've done soft reset.
But it still switches off after a minute or two. I am talking about the backlight also, not the phone's standby. Ie with an acrobat doc open the light turns off after a minute or two then the phone goes into standby shortly afterwards. I guess ideally an app that deals with this would also be able to prevent standby for specific apps too.
Have I got the correct filename for Adobe reader or is there something else I've messed up? That's what I saw it as on the phone somewhere (I forget where but that's definitely what was written).
It will be nice obviously if I can make this work but I have to be honest and say that using Glight is a horrible user experience. It's a case of tapping the screen and waiting a few seconds for every single response. When you're trying to position the cursor in the exact right spot (ie to edit text or a typo etc) on the capacitive touchscreen with your finger this can take many screen taps, and it's pretty frustrating! But better that than nothing obviously!
I'm interested in this too. I tried Lumos and it works as for setting the backlight for certain apps (like max. brightness for Adobe Reader etc.), however it still doesn't prevent the phone going into standby, which is the main problem when trying to read something.
check this out:
http://forum.xda-developers.com/showthread.php?t=661472
When applications that are GPU accelerated are switched to full screen, the screen orientation always switches back to default (with the Asus on the Transformer logo on top). This is regardless of the orientation you have set.
For example:
A)
1.) You have rotated your screen upside down
2.) you run Angry Birds
3.) the screen switches back to standard default orientation
B)
1.) You have rotated your screen upside down
2.) launch youtube
3.) play a video
4.) switch to full screen
5.) the screen automatically switches back to standard default orientation
I have upgraded to 3.1 recently and don't seem to remember this being an issue before with 3.0.1 before.
Is anyone else also having this issue?
ok, is anyone with 3.1 NOT having this issue?
I get the same thing happening, and I think I would go as far as to say that it's actually intentional behavior on the part of Asus and Google to make the orientation revert like that. It makes more sense for fullscreen video to default to that orientation so as to ensure that it's consistent with the proper docking position, which is with the docking port on the bottom. Most people who watch fullscreen video for any extended period of time are probably going to dock the device.
Why do you turn the tablet upside down in the first place? I understand that having the ability to rotate 270 degrees is sometimes helpful for games and multi-user applications, I just don't see how using the tablet in its default orientation would pose a problem.
I'm typing on phone so briefly, the reason I need the transformer to be upside is due to the design of the variable angle stand of the official asus transformer skin case.
The case stands by folding in a scalene triangular fashion.
20 degrees above horizontal requires upside down.
75 degrees above horizontal requires right side up.
So most of the time when you use it in your lap, you want only 20 degrees
Applications are allowed to overide the orientation. This is true for most media players. It'll force the screen into the default landscape mode. App controlled so not honeycomb issue
Sent from my Transformer TF101
Sounds like a bit of a design oversight on the part of Asus.
Now as far as fixing it, you only have a few options. While you do have the ability to disable auto rotation on the screen, that's going to cause the tablet to simply default to the 0 degrees landscape orientation. What you need on top of that is a way to manually set your orientation, and so far I've never seen an app or ROM that does that. That's not to say it's impossible, just that I've never seen it done. The other option is to buy the keyboard dock, but that's a little excessive unless you really think you need it.
This is due to the fact that the dev of the app has forced it to lock in that orientation (landscape right side up, there's an app called androsensor that will give you more info). There was another thread concerning the same topic in themes and apps section. Your best bet is to email the app developer when you run into this.
One example is airport mania, if you were holding the device upside down and launched the game, it would force it to run right side up. I sent them am email with a description of what is happening and that the official sleeve (although I don't have one but felt it was with mentioning) is designed so the device is upside down with camera at bottom and charge port at top. Got a reply within the day and an update in the market within 3.
Sent from my Transformer TF101 using XDA Premium App
klau1 said:
Uncontrollable Orientation Behaviour
Click to expand...
Click to collapse
To much beer, not enough sex
There is an option to lock the orientation in the settings. So once it is upsied down you can lock the orientation and it shouldn't change.
I am not with my TF right now to test this though.
no, that doesn't work.
I don't recall this being a problem prior to the 3.1 update. Having to purposely ask each developer to change the orientation when none was necessary before is simply unacceptable.
Having bought something as simple as a case with it's multi-angle feature, one expects it to work out of the box.
As far as I knew, apps like Moboplayer always stayed in the default landscape orientation during video playback
I don't use Moboplayer much, but as far as I can recall, the Youtube app worked upside down in full screen before.
Can someone with 3.0 confirm?
While generally being quite happy with the Gingerbread update for my Desire Z, clearly there are a few glitches.
First of all, my DZ is a Nordic version with the characters Æ, Ø, Å, Ä and Ö on the hardware keyboard.
On 2.2 before the OTA there was a bug which consistently caused capitalization of Æ, Ø and Å (æøå) when using the hardware keyboard. I don't know about Ä and Ö which are only used in Swedish and not in Danish and Norwegian.
This bug is now fixed using the native keyboard but still present using Scandinavian Keyboard which I have installed from Market. I must admit that I have not contacted the developer to ask if this could be a bug in the app.
Sadly, I have now experienced another bug related to the hardware keyboard after updating to 2.3 - today it happened for the second time.
When typing in Whatsapp and the SMS app (and possibly other apps) using the hardware keyboard pressing "S" will open the SMS app, pressing "G" will open Gmail and pressing "B" will open the built-in browser (not Dolphin HD which is set to default). This is fixed by a reboot (temporarily, it seems). Incidentally, the bug disappeared just now without a reboot while checking if it was also present in Gmail.
The missing pictures bug in HTC's gallery app is still there - still using QuickPic.
Anything that is not listed here - please add to the thread.
EDIT:
As many others I also get the constant Sense restarting thing which is driving me insane!
Also the brightness setting itself to maximum many times.
A handful random reboots. A couple happened with no apps open and doing nothing on the phone - I just happened to notice when it rebooted.
Since monomer888's advise I haven't had another shortcut typing bug happen (as of yet). Thanks!
I'm running software version 2.42.405.2 CL84109
whpsnp said:
[..]Sadly, I have now experienced another bug related to the hardware keyboard after updating to 2.3 - today it happened for the second time.
When typing in Whatsapp and the SMS app (and possibly other apps) using the hardware keyboard pressing "S" will open the SMS app, pressing "G" will open Gmail and pressing "B" will open the built-in browser (not Dolphin HD which is set to default). This is fixed by a reboot (temporarily, it seems). Incidentally, the bug disappeared just now without a reboot while checking if it was also present in Gmail.[..]
Click to expand...
Click to collapse
You can try this:
Originally Posted by Snotmann
If i type a "S" in a SMS, on the hardware keyboard, i get the message that the SMS will be saved and the screen went back to the SMS Overview.
Did someone have the same issue ?
Click to expand...
Click to collapse
Have had this happen to me before. Fix it by doing this:
Settings -> Applications -> Quick Launch -> Delete all shortcuts
Also [..] restart just to be on the safe side.
Click to expand...
Click to collapse
No guarantees but it might work.
My phone doesn't show album art in the music player, and it still doesn't work after several restarts, and dismounting and mounting sd card. Hope it gets fixed soon
Sent from my HTC Vision using XDA App
- when exit from a fullscrren app, sometimes the status bar doesnt fit all screen, leting a space (about 10% of the screen space). Expanding the status bar fix it
- Portuguese translation erros remains from the first rom 1.34!!!!!:
Call volume is "Volume de ligação recebida" - shuold be "Volume da ligação"
The tips widget is "Dicar", should be "Dicas"
And a few others, that I don't remember now.
I've only seen some minor UI bugs and most recently, the capital letters typing a text message. That only happens when I try to type too quickly after opening the thread.
I must admit that I havent seen the gallery bug yet but then I don't really use the camera.
Might be worth posting your version number to track regional bugs.
Mine is 2.42.405.2
Brightness will be stuck at max waking from sleep sometimes. Brightness slider has no effect. Fixes itself if you sleep then wake again.
Playback of videos not taken with the camera is very stuttery. THis wasn't the case in 2.2.
I had the missing gallery pictures problem and the brightness problem as well-I have it normally on auto-bright, but sometimes when I wake it or reboot it, it automatically changes to full brightness and I have to select auto-bright again.
Also, Sense restarts after almost anything.
After installing, deleting or moving an app, returning to the home makes sense crash and restart.
I have a gallery bug aswell, can click on some line with pic and wording not shown.
I had once a bug in the unlock pin screen, tapping 7 was actually hitting 4, same if I hold on 7, i see the pressed status of the 4 button onscreen. It happened when i had no charge at all and plugged the phone to the usb port of my running pc. It was also impossible to switch on the phone, i had to plug it out.
Can't remember more right now.
Sent from my HTC Vision using XDA App
Sense crashing sometimes when leaving app
Newsreader crashing when returning from browser
The shortcut bug (pressing Searchkey once on hardware keyboar solve this)
The 10% status bar bug
Coming up some more soon
Sent from my HTC Vision using XDA App
I was wondering if anyone had noticed if there is still this bug or if you could test to check for me:
Start an app in portrait mode, slide out the keyboard for landscape mode, hit the home key. Do your apps/widgets load right away or within a couple seconds? For me it has always been that it will take 15-20 seconds for the screen to load, all I will see is the status bar and my background, no loading screen, no errors, nothing but that. Let me know if you had this prior to updating and also if you have it after, thanks!
ME TOO!
nicolaibaun said:
My phone doesn't show album art in the music player, and it still doesn't work after several restarts, and dismounting and mounting sd card. Hope it gets fixed soon
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I also don't have album artwork shown in my music app :| Do you guys think HTC will bring out a software update for these bugs?
noneabove said:
I was wondering if anyone had noticed if there is still this bug or if you could test to check for me:
Start an app in portrait mode, slide out the keyboard for landscape mode, hit the home key. Do your apps/widgets load right away or within a couple seconds? For me it has always been that it will take 15-20 seconds for the screen to load, all I will see is the status bar and my background, no loading screen, no errors, nothing but that. Let me know if you had this prior to updating and also if you have it after, thanks!
Click to expand...
Click to collapse
Happens to me sometimes as well. Also, waking up by opening the keyboard may cause the widgets on the home screen to show after a few seconds.
Sense crashing sometimes when leaving app
The 10% status bar bug
Click to expand...
Click to collapse
I've experienced these as well. Funny thing is, I only experience the 10% bug in Facebook app.
Besides that "desktop loader" and sense-crash problem I got some strange issue with my mobile data connection - searched the forum for a while, haven't found anything, so I'll report it as a gingerbread bug.
Sense displays an activated connection all the time (3g/H - with those two little arrows flashing, thus indicating some traffic) but, unfortunately totally random, it decides to stop working.
Only way to check the data connection is browsing google. Turning off/on fixes the problem temporarily.
In addition, the speed of my mobile connection seem to be capped at some point - typically, depending on my location, it'll stick with 3G instead of H until I reboot. (noticed a remarkable speed difference by browsing the web before and after reboot)
Anyone similar problems?
Desire Z - 2.3.3 Stock
@Kueber;
While i've only seen the sense reload when my phone is uunder a lot of CPU load, I have seen it.
Regarding the data issue, i've only seen it with a certain app, "London Journey" This would retrieve some downloads, but not others. Maybe its a change in the data API relating to the new Download API. Using any other app was fine.
In maybe a slightly related issue, I've noticed that when in GPRS or EDGE, its much more reluctant to go to HSPA, especially when the H signal is low. However, this would normally just drop straight back to G / E anyway so is an improvement in my mind. It also seems quicker to see the HSPA connection has been lost and goes to G / E.
In your case, if location determins 3G rather than H, it could indicate you mobile provider may not have upgraded all their sites yet. If it passes data, then its stuck at 3G.
Craig
craiglay said:
@Kueber;
While i've only seen the sense reload when my phone is uunder a lot of CPU load, I have seen it.
Regarding the data issue, i've only seen it with a certain app, "London Journey" This would retrieve some downloads, but not others. Maybe its a change in the data API relating to the new Download API. Using any other app was fine.
In maybe a slightly related issue, I've noticed that when in GPRS or EDGE, its much more reluctant to go to HSPA, especially when the H signal is low. However, this would normally just drop straight back to G / E anyway so is an improvement in my mind. It also seems quicker to see the HSPA connection has been lost and goes to G / E.
In your case, if location determins 3G rather than H, it could indicate you mobile provider may not have upgraded all their sites yet. If it passes data, then its stuck at 3G.
Craig
Click to expand...
Click to collapse
Hey there, thanks for your answer.
The strange thing is that my previous phone (HTC Legend) always displays a HSDPA connection (speaking of my hometown as testing area). My Desire Z also states a H connection until it get capped somehow. Then I reboot and the little H is back. It is definitely not a display bug, since the speed difference, as already mentioned earlier, is noticeable after rebooting.
Is there some kind of a "user control" in areas that aren't fully covered by a mobile provider, so that my connection may drop due to non using the phone? (It happens normally while phone is sleeping) And is it possible that my Legend, 2.2 stock btw, just isn't very accurate when it comes down to displaying the current connection speed? - to mention your point of a quicker HSDPA loss on gingerbread.
greetings
I also have the Sense constantly restarting. It is really, really, REALLY annoying!
It happens about 50% of the times when I return to the home screen from any app, even the browser.
Has any of you tried uninstalling the Gingerbread update? Don't even know if it is possible, though.
beside the above bugs. the missing pictures bugs also affects my sound files. i can't change my ringtone or alarm tone. it will change back to the default ringtone every few hrs as the sound files went missing on my sd card. has to do a sdrescan to get it back. but few hrs later it will go missing again & ringtone either be empty or back to default.
marlar said:
I also have the Sense constantly restarting. It is really, really, REALLY annoying!
It happens about 50% of the times when I return to the home screen from any app, even the browser.
Has any of you tried uninstalling the Gingerbread update? Don't even know if it is possible, though.
Click to expand...
Click to collapse
yeah it drives me crazy too. Any chance to downgrade easily before update?
I've had the exact same bugs as described above, it drove me insane.
after 3 days or so i was fed up with it and downgraded and installed Virtuous 2.0. the bugs are gone and i've got a stable, rooted phone.
has anyone tried to contact HTC about these bugs? I myself was too lazy to write an email..
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
mrhomiec said:
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
My Advice, try the re-calibration thing, lay it flat on a desk and calibrate it.
Ensure the lock is enabled, and then try again.
If this doesn't help, I read somewhere a while back that this works, but I don't get how:
lay the phone flat on a table, spin it 3 times. Put it on it's side, spin it 3 times. Hold it up on one end, spin it 3 times.
Weird but works (APPARANTLY)!
cool, thank you for the info, but i think i'm missing something. how do i calibrate it?
i have screen rotate locked/disabled on a flat surface. then i tried to unlock/enable it (while still on a flat surface), and it still doesn't rotate.
mrhomiec said:
cool, thank you for the info, but i think i'm missing something. how do i calibrate it?
i have screen rotate locked/disabled on a flat surface. then i tried to unlock/enable it (while still on a flat surface), and it still doesn't rotate.
Click to expand...
Click to collapse
No you need to re-calibrate the gyro sensor, Im not with my tab so I can't quite remember where it is. Go to settings, and just have a look round, untill you can find the calibration of the gyro sensor.
No worries btw, glad to help
i still think i'm totally missing something. i can't find anything in the settings to re-calibrate it.
however, i did setup Z - Device Test and within the accelerometer and gyroscope testing shows that movement is being detected.
ok, something is totally messed up.
i just flashed Cyanogenmod monthly-2, did a full wipe cache and dalvik, and factory reset from CWM.
and my screen is still not rotating.
i'm totally clueless now.
I am on CM10 grouper latest build my home screen wont rotate, the apps and settings rotate only the home screen and apps drawer wont rotate.
Any ideas anyone?
Edit: Got it to work, I was using Nova launcher and by default its not enabled. Nova Launcher- Look and Feel - enable auto rotate. You need to enable both in system settings and nova settings. Silly of me :-\
mrhomiec said:
ok, something is totally messed up.
i just flashed Cyanogenmod monthly-2, did a full wipe cache and dalvik, and factory reset from CWM.
and my screen is still not rotating.
i'm totally clueless now.
Click to expand...
Click to collapse
Read here: http://forum.xda-developers.com/showthread.php?t=1929790 it seems you need to extract some stock files to get it to work.
Guhrasoh said:
Read here: http://forum.xda-developers.com/showthread.php?t=1929790 it seems you need to extract some stock files to get it to work.
Click to expand...
Click to collapse
thank you for the link. i download a binary file from here..
https://developers.google.com/android/nexus/drivers#grouper
but i have no idea what to do with it.
on a side note, i'm wondering why this all of a sudden stopped working tho? AOKP's build 4 was doing it before the release of 4.1.2, but then just stopped. i don't understand why i need to manually do something that was working from the beginning. especially within apps. i can't get the screen to rotate in Chrome, GMail, Reader, Twitter, etc. i can care less about the home screen rotation.
[UPDATE]
so i was downloading different apps- mainly games trying to test out the rotation to see if that is buggy too, and i came across this app...
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsInphdXNhbi56ZGV2aWNldGVzdCJd
with this, i was able to test the Gyroscope and Accelerometer sensors and i noticed the blue axis (z-axis?) was not moving at all.
i then gave a few door knocks on the back plate, and all of a sudden the z-axis jumps to the correct view.
somehow it got stuck in place, but it seems to be working now. very odd. i've never dropped it. don't know how this could have happened.
mrhomiec said:
<edited>....somehow it got stuck in place, but it seems to be working now. very odd. i've never dropped it. don't know how this could have happened.
Click to expand...
Click to collapse
Well first of all stop banging on it, it has nothing to do with that. I've noticed there was something either added or removed from AOSP that causes this after the 4.1.2 update last week. Most people who are compiling locally probably noticed this... any others that have it working are just proof of the excessive kanging nowadays... since they're all probably a kang of AOKP or CM (who of which I'm sure identified it and corrected it in their git).
I haven't had time to look into it yet but I'd assume its related to Launcher2.apk. Look in Launcher2 in the AndroidManifest.xml and see if there's a line with something like:
android:screenOrientation="nosensor"
Click to expand...
Click to collapse
...you want that to be set to either "sensor" or "user"... I cant recall right now.
Did you try editing the build.prop file yet? If it is in fact related to the sensors then I dont think this will correct it anyway, but it's worth a shot. Go to your /system dir and mount is r/w, edit build.prop by adding this to the very end, on its own line:
launcher.force_enable_rotation=true
Click to expand...
Click to collapse
...save that, close it, then reboot and see what ya got. If it doesn't work then you know its Launcher2 not enabling the sensors. I'll post again once I look at it and fix it.
mrhomiec said:
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
Do you have "auto rotate" in 'settings/accessability' , checked?
Posted via my Amiga 3000, EVO 3D , or Nexus 7
oOo B0XeR oOo said:
Well first of all stop banging on it, it has nothing to do with that. I've noticed there was something either added or removed from AOSP that causes this after the 4.1.2 update last week. Most people who are compiling locally probably noticed this... any others that have it working are just proof of the excessive kanging nowadays... since they're all probably a kang of AOKP or CM (who of which I'm sure identified it and corrected it in their git).
I haven't had time to look into it yet but I'd assume its related to Launcher2.apk. Look in Launcher2 in the AndroidManifest.xml and see if there's a line with something like:
...you want that to be set to either "sensor" or "user"... I cant recall right now.
Did you try editing the build.prop file yet? If it is in fact related to the sensors then I dont think this will correct it anyway, but it's worth a shot. Go to your /system dir and mount is r/w, edit build.prop by adding this to the very end, on its own line:
...save that, close it, then reboot and see what ya got. If it doesn't work then you know its Launcher2 not enabling the sensors. I'll post again once I look at it and fix it.
Click to expand...
Click to collapse
thanks for all the info.
i'm not the type to mess with the files. but as i mentioned, i wasn't on 4.1.2 yet when this started happening. AOKP build 4 was based on 4.1 or 4.1.1. and would it be possible for a file to make the z-axis jarred in one direction? then when placing some force to the back of the device jump it back in place?
i haven't had any issues since then. i am now able to rotate the screen at will.
Originally Posted by mrhomiec
i've had AOKP build 4 flashed on my Nexus 7 since it was released on Sept.30.
all of a sudden yesterday, i noticed that nothing would allow me to change the screen orientation. i checked and double checked, i have that setting enabled.
for example, if i'm in portrait mode on the home screen, open up Chrome, i can not change the orientation to landscape.
but, if i launch a game, where it forces the orientation to landscape, i am now stuck in landscape mode. if i open up Chrome, i can't change it to portrait.
i've tried clearing data and cache of Nova Launcher. tried to lock down orientation then enable it. but nothing is working.
has anyone come across something like this before?
Click to expand...
Click to collapse
Do you have "auto rotate" in 'settings/accessability' , checked?
Posted via my Amiga 3000, EVO 3D , or Nexus 7
Click to expand...
Click to collapse
I'm having this problem now too. Just in the last 2 days.
I have a completely stock 2013 N7. It gets stuck in an orientation, and locked there. I have checked all the settings, and auto rotate is on.
I downloaded the Android Sensor Box, and something is fishy with the orientation hardware. One axis of the sensor is locked to one side and won't move.
Hi Everyone,
Recently my phone was updated to Android v7 and since then I noticed that the icons for the cursor in text boxes and system dialog boxes have got messed up.
I read on Android central, one user posted that uninstalling Kaspersky fixed the issue, although in my case I don't have Kaspersky, so I can't go about uninstalling all apps, got a hell lot of them!
1drv.ms/i/s!AigR1NGUKZ2stFWGsf_bkkIg_WEa
1drv.ms/i/s!AigR1NGUKZ2stFa4-NP8jEiQCuMs
1drv.ms/i/s!AigR1NGUKZ2stFRZcp6bHn6VE_JE
It's frustrating everytime i see this... Please help me...
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
jivenene said:
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
Click to expand...
Click to collapse
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
jivenene said:
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
Click to expand...
Click to collapse
I have those glitches as well apart from what i posted.
I read online its because of some app messing things up. I seriously don't want to reset and start testing this out one app at a time. It will take at least a few days to get back up to speed.
Thanks :crying: