Turning the hero from portrait to landscape (or back), takes several seconds to work. Is there a setting somewhere to speed this up? It's unusable the way it is, life is just too short to wait for that!
iwillgetoutmore said:
Turning the hero from portrait to landscape (or back), takes several seconds to work. Is there a setting somewhere to speed this up? It's unusable the way it is, life is just too short to wait for that!
Click to expand...
Click to collapse
Unusable is rather strong! Takes about 2 seconds to happen, quickest rotation I have ever seen.
Anyway, I dont know of a way of tweaking this, though I support the intent
After watching my girlfriends iPhone switching instantly for the last year or so, it 'is' unusable to me. She laughed at it when she turned the phone. However, having said that, I've switched it back to standard andriod and now it works properly, certainly less than a second.
WIll have to play with perfmon and work out what's happening, maybe grabbing top while trying it in both UI's would be enlightening...
Seems to work fine for me, soooo much faster than Opera on WM.
You can calibrate it by going to Settings -> Sound and Display -> Calibrate G-Sensor.
Calibration only set up angle sensitivity, so is not relevant..
Related
Am I the only one experiencing an overly sensitive Sense UI? Perhaps I'm missing a setting. I have looked all through /etc and can't find any way to adjust the sensitivity.
Anyone have a solution?
Touchscreen Spaz-out
I will say: occasionally my touch screen will just go bat-**** crazy, registering even the slightest movements as "clicks". The phone is completely unusable; god help you should you be in the lock screen.
Now, after observing this for a couple of days I have a hare-brained theory: it's related to how hot the device is. I've noticed that it happens after extended periods of use, or when it's plugged into the wall charger. Just unplugging it grants a short reprieve, and a refractory "cool down" period generally fixes it. Also it'll work sorta if you press down on the screen like you're trying to kill your phone.
Can anyone else confirm this?
I was getting a lot of the jitteryness and screen lockups before I loaded MR2, everything seems pretty fine now. I had more problems with my wife's myTouch than the eris for once last week.
I do not have any issues like this (I do have all the updates though)
-Chr1831
been trying out this rom the past few days even though using sense roms is against my religion (i'll confess later and everything will be fine).
anyway, whenever i take it off of automatic brightness... like say, at night, i turn the brightness all the way down... once the screen goes off and i turn it back on, it's bright as hell again.
oddly, the brightness setting will still show that it's all the way down(even though it's bright as hell), so then i have to slide it up & then back down again.
and then it does the same thing all over again!
am i the only one experiencing this issue? is there a fix for it?
have you given up your booty to jesus?
voxigenboy said:
been trying out this rom the past few days even though using sense roms is against my religion (i'll confess later and everything will be fine).
anyway, whenever i take it off of automatic brightness... like say, at night, i turn the brightness all the way down... once the screen goes off and i turn it back on, it's bright as hell again.
oddly, the brightness setting will still show that it's all the way down(even though it's bright as hell), so then i have to slide it up & then back down again.
and then it does the same thing all over again!
am i the only one experiencing this issue? is there a fix for it?
have you given up your booty to jesus?
Click to expand...
Click to collapse
...nope. Ain't given up my booty to Jesus yet.
Never had that problem, but I haven't messed with screen brightness manually on beta8. Last time was Beta7 and it worked just fine. It does seem REAL slow on the brightness level uptake though. Like when you use the camera and it ramps up brightness all the way... it takes it about 30 seconds or so to readjust it.
In a completely dark room, auto-brightness will sometimes randomly bump up the brightness level of the screen to, say, 25% (way too bright). In a dimly lit room, it generally stays pinned to minimum unless i move it up manually before turning auto-brightness on (way too dark).
Changes take a long time and are inconsistent. Anyone else experience this?
Never been a fan of auto-brightness. It depends on the light sensor in the device, but I turn this off on most android devices as it just ends up soaking up power anyway.
JazzMac251 said:
In a completely dark room, auto-brightness will sometimes randomly bump up the brightness level of the screen to, say, 25% (way too bright). In a dimly lit room, it generally stays pinned to minimum unless i move it up manually before turning auto-brightness on (way too dark).
Changes take a long time and are inconsistent. Anyone else experience this?
Click to expand...
Click to collapse
I have noticed that as well. Specifically the in a almost completely dark room its not set at minimum brightness, and when in a dimly lit room it will be at minimum brightness.
Oddly enough when in the completely dark room if I turn off auto brightness then put it back on it will usually go down to minimum brightness. This lasts for awhile then it seems to bump back up.
mine does this also..
I do recall nearly every reviewer of the Prime saying that the auto-brightness was pretty wonky.
But with that being said, auto brightness seems rather unnecessary on pretty much any Android device. Even Froyo had native brightness widgets.
UmbraeSoulsbane said:
Never been a fan of auto-brightness. It depends on the light sensor in the device, but I turn this off on most android devices as it just ends up soaking up power anyway.
Click to expand...
Click to collapse
Ditto here, you will find auto turned off on all my devices. Never seems to work for me correctly.
Same here on my 64gb model on .33 version. Also posted here ...
http://forum.xda-developers.com/showthread.php?p=21024017#post21024017
Can heavily be noticed in mobilephonetalk forums while scrolling the page with auto bright turned off. Even on max or min brightness....
It sucks. Plain & Simple
I do wonder why they have such a hard time making Auto Brightness / Sensors that work correctly. Or at least consistantly. I used to play with it, setting the brightness level, then going to auto on several HTC devices, and while it was a LOT better than the Primes setup, it wasn't consistent which always caused me to give up on it. Seems a waste to even put the sensor in there when no one seems to be able to control it properly.
Maybe it IS an Android thing, for I remember no such issue with Windows Mobile devices. Hmm. Hold out any hope of ICS? Perhaps it will address it, but for now, I am still skeptical that ICS is the Holy Grail everyone claims it to be. It would have to address a LOT to be anywhere near that perfect. Who knows. Maybe it IS that good, in which case, My Prime is really gonna shine!
I don't like it on my HTC Sensation either. Too much dimmed when outside and in bright rooms.
Does anyone have a device with ICS that can confirm if auto brightness still acts the same? Every Android device I have had has the same issue. I have just learned to deal with it although I do not like it.
keitht said:
Does anyone have a device with ICS that can confirm if auto brightness still acts the same? Every Android device I have had has the same issue. I have just learned to deal with it although I do not like it.
Click to expand...
Click to collapse
Yep HTC sensation is the same..
I find it very good on my Sensation, suits me well. But in the Prime its well too low.
Sent throught the wormhole from my CoinInserted Sensation OG.
it's ok. not perfect
I also never use auto backlight, but on the TFP it seems ok.
It's not perfect but it almost always reacts pretty fast to changes in light.
When I'm in a dark room it always goes to the lowest setting.
Sometimes it seems to 'forget' to work and then I need to turn the auto setting off and then back on again and that seems to remind it to go back to work.
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
ImmanuelCunt said:
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
Click to expand...
Click to collapse
I can't help myself, 3 thanks virgins in 2 days!!!! Owned!!!! last time I held something up to the sun it melted. Its kinda hot!!!!........
Ok in all seriousness I have not had this issue....did you try rebooting your prime? I have noticed some hicups from time to time, like touch tones stop working....but if I reboot it will work again. I am sure its just the newness of ICS, these things will get ironed out in time.
I leave it off anyways. Its a known automatic brightness is a battery drainer. You'll get better battery life with it off.
slayer69 said:
I can't help myself, 3 thanks virgins in 2 days!!!! Owned!!!! last time I held something up to the sun it melted. Its kinda hot!!!!........
Ok in all seriousness I have not had this issue....did you try rebooting your prime? I have noticed some hicups from time to time, like touch tones stop working....but if I reboot it will work again. I am sure its just the newness of ICS, these things will get ironed out in time.
Click to expand...
Click to collapse
I wish you took my thanks virginity LOL but yeah i've not come across this issue but who holds their tablet up at the sun... lol
ImmanuelCunt said:
Hello,
theres a bug in automatic brightness: if you turn it on and hold it against the sun the brightness will go to maximum but it won't get back (darker).
Click to expand...
Click to collapse
I think this is more of a feature than a bug, although I keep mine at one certain level anyway.
It's to give you a more seamless experience, as soon as the screen goes off and back on it adjusts. It's so when you're reading an article and move from one area to another, you don't get a surprise mid-sentence. I always hated reading things off my phone with auto brightness on, couldn't just focus on the words had to keep tripping up on a constantly changing screen.
With sun i meant that you can hold it against a bright light
Sry for my bad english...
I've actually noticed some differences in the sensitivity of the light sensor on various units. Some do seem to get "stuck," where others maintain an accurate measurement of ambient light. This seems to be correlated to newer units (e.g., C1 units).
The one I'm using right now does switch lighting both more quickly and, it would seem, more accurately. The ones I had previously would get stuck either on high or low brightness (with very little adjustment in between), and I needed to toggle the auto brightness button to get them to adjust to new conditions.
I found auto brightness on the device to be an annoying burden if anything. I just keep it pretty low all the time. Better that way anyways.
Same problem here - The brightness goes up under bright light, and won't readjust until the next screen off/on or reboot.
Does anyone have a Prime that adjusts back down without turning the screen off?
I swear it's intentional and not a bug, although they should offer you the option of controlling its parameters. Just have to wait for the unlocker and some custom ROMage.
But seriously, I think it's to keep a continuity in your current session, so that if you're gaming or working (the two things this tablet's for) you're not plagued by an ever-changing screen that distracts you...
buxtahuda said:
Does anyone have a Prime that adjusts back down without turning the screen off?
I swear it's intentional and not a bug, although they should offer you the option of controlling its parameters. Just have to wait for the unlocker and some custom ROMage.
But seriously, I think it's to keep a continuity in your current session, so that if you're gaming or working (the two things this tablet's for) you're not plagued by an ever-changing screen that distracts you...
Click to expand...
Click to collapse
I can see how the concept of continuity can be good. But in my case for example, switching the bedroom light on - followed by a certain increase of brightness on ATP - then switch the bedroom light off to go to bed - the persistent brightness (tested for >15mins) can be a little straining on the eyes. Although readjusting the brightness is as simple as 'clicking' the 'auto' icon on/off again so that the brightness comes down to appropriate level (it only takes 2seconds to do it) - I think this is defeating the purpose of having the auto-brightness setting in the first place.
maxfac1234 said:
I can see how the concept of continuity can be good. But in my case for example, switching the bedroom light on - followed by a certain increase of brightness on ATP - then switch the bedroom light off to go to bed - the persistent brightness (tested for >15mins) can be a little straining on the eyes. Although readjusting the brightness is as simple as 'clicking' the 'auto' icon on/off again so that the brightness comes down to appropriate level (it only takes 2seconds to do it) - I think this is defeating the purpose of having the auto-brightness setting in the first place.
Click to expand...
Click to collapse
Oh I whole-heartedly agree. Going from my living room anywhere else in the house causes blindness with auto brightness on. And it acts completely opposite on this device than all others I've touched that use the feature. And like you say, if it's "automatic brightness" then why would it not be totally automated?
I'm just saying there's definite reasoning and programming behind it, it's not just some bug per se.
Therefore, don't expect ASUS to do anything about it, it'll all be up to our wonderful dev's here; they'll say it's properly functioning even though it's bass ackwards from everything else in existence.
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?