hello all, I have a strange problem with my hero.
Everytime I unlock, the time is an hour behind, it then flips to the corect time within a second, so I get the right time but its very annoying.
I hoped that with the clocks going back this weekend, it would be ok as I assumed the "first" time it shows was GMT and it flicks to show the daylight saving time.
not a huge issue I know, but annoying
It's a feature, same is in Sense or Manila for WM
It's meant to be that way.
Nothing wrong with it really, as long as it tells me correct time when I look at it, that's all that matters.
i guess they want to show off the clock so like to have a bit of movement, but it means that it takes more than a quick glance to see the time.
Related
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..
Hey guys,
thank god I use two alarm clocks every morning, if not I would be screwed today...
Im using G-Alarm now for some years and it never disappointed me before, but today I was a bit angry.
I have a returning alert on monday-friday @ 7:40AM which I never change. Today my alert clock at my bed woke me up at 7:30AM... just as always.
10 Minutes later my HD2 should wake me up the second time but today it didnt.
I had to press a hardware button to wake it up. As soon as the screen turned on I saw in a millisecond that the time changed to the actual time 7:42AM and THEN G-Alarm started....
So what the hell has happened? Was it in a deep sleep or something like that? Its really bad that I cant rely on my Leo... Evil, very evil I think this was the second time this happened in 2 months...
Anyone got an idea what I can do?
Hi everyone!, I'm having this really odd issue with my S2. I've only had it about a week now and this could have been happening all along though I didn't notice it.
Basically If the screen is off and I hit the power button is has this really slight flicker as the screen comes on. It's almost like a single line down the screen right before the wallpaper appears. It's also right-justified on the screen and always in the same spot.
Has anyone else had this issue? It can be reproduced by simply hitting the power button to shut the screen off then hitting it again to turn it on.
Thanks!
Edit: Also the screen doesn't always fade on. 3/5 times it will just "instant-on" where I'll hit the power button and it will instantly show the lock screen tile instead of "fading" into it. Does this happen to anyone else or does it ALWAYS fade in?
I'm probably just being paranoid but I'd rather replace the phone quickly to avoid actually sending it to manufacturer.
Thanks again!
You should take a video of it so we can see if it is normal. I don't see what you describe, and not sure the phone is supposed to "fade in" to the lock screen. Mine is always instant on.
I once flashed to Litening ROM and it had that flicker (lightning style) as a feature I guess, is it the same problem OP stated?
Regards.
Saw it once two days ago, vertically on the extreme left of the screen. Haven't seen it since, but it was very rapid - blink-and-you'll-miss-it job. Can't say it worries me. On Revolution FWIW.
B3311 said:
Saw it once two days ago, vertically on the extreme left of the screen. Haven't seen it since, but it was very rapid - blink-and-you'll-miss-it job. Can't say it worries me. On Revolution FWIW.
Click to expand...
Click to collapse
sorry I can't take a video since this is the only device that I own that is capable of taking video.
anyway, yeah - it's really quick. And it's vertically down the screen. I kind of assumed that it was the backlight turning on but I'm pretty certain that happens on the sides right?
Right now it's 10:00 and this issue happens right where the "1" is on the clock at the top of the screen. So starting from that 1 all the way to the bottom.
Again it's REALLY fast - but it's noticeable, I'd have no problem showing it to someone in front of me. It just looks like a single line about the same width as the "1" as well. It almost seems like the one tiny line is showing before the rest of the screen, like if the screen were a "loading process" that line would be the first thing to appear before the rest gets backlit.
Not sure if it matters but it's the model I9100M from Virgin, just incase they are made differently somehow.
This phone has no backlight. The LED's are all individually lit.
Ryne said:
sorry I can't take a video since this is the only device that I own that is capable of taking video.
anyway, yeah - it's really quick. And it's vertically down the screen. I kind of assumed that it was the backlight turning on but I'm pretty certain that happens on the sides right?
Right now it's 10:00 and this issue happens right where the "1" is on the clock at the top of the screen. So starting from that 1 all the way to the bottom.
Again it's REALLY fast - but it's noticeable, I'd have no problem showing it to someone in front of me. It just looks like a single line about the same width as the "1" as well. It almost seems like the one tiny line is showing before the rest of the screen, like if the screen were a "loading process" that line would be the first thing to appear before the rest gets backlit.
Not sure if it matters but it's the model I9100M from Virgin, just incase they are made differently somehow.
Click to expand...
Click to collapse
Hmm, not the same problem as me - certainly nothing to do with the time here - it was in the afternoon when it happened with me, and my lockscreen clock's in 12 hour format. Clock's also at the bottom of my screen.
Been trying to reproduce it, and can't.
B3311 said:
Hmm, not the same problem as me - certainly nothing to do with the time here - it was in the afternoon when it happened with me, and my lockscreen clock's in 12 hour format. Clock's also at the bottom of my screen.
Been trying to reproduce it, and can't.
Click to expand...
Click to collapse
No no, I wasn't saying that the clock had anything to do with it, I was just trying to describe where the line appears on screen. I was also talking about the clock that appears at the very top, not the one on the lock screen. If I just continually tap the power button on and off I can see the "line" appear every time exactly in that spot.
It's pretty noticeable, unless you have the phone away from you - so if you don't see it then it probably isn't happening.
Does anyone think I should return this and get another? I don't really want to run into issues later and have to send to manufacturer. Is this problem big enough that I could get it replaced without issue?
Thank's for the replies!
Sorry, misunderstood. Definitely not my problem, I have no clock in the status bar.
If it happens every time, I'd probably return it if I was you - could be the precursor of something more serious.
Hi again, Thanks for the replies. I realized today that the issue is really only noticeable if you're in a dark room. Even in a semi-lit room it's almost unnoticeable which is probably why I hadnt seen it thus far.
If anyone wouldn't mind flicking the lights off and taking a look I'd appreciate it. If not I'll just return it.
thanks again forum!
I experience it too (at least I think we are talking about the same thing)..it's like it's stuttering and lagging after being in standby. So the first time it renders the lockscreen, the first few frames seem to be rendered at a different pace. If you turn the screen on after a good break, it'll likely do it, but after a few times in a row it instantly shows the screen.
Perhaps it relates to how big the wallpaper for the lockscreen is. I'm not sure, but I've had some huge 2mb pictures set as wallpapers for the lockscreen, and afterwards I think I decided to select a smaller image. I don't know if it was just a placebo effect, but anyways..it still does it with my current picture. I don't really care. You could try a different lockscreen from android market and see if it helps, but I think every SII suffers from this.
I have this exact issue too and it really annoys me! I also bought the phone from Virgin if that is relevant. It's a white streak on the left of the screen for me and only happens every so often. So what's the prognosis? A software fault? Hopefully fixed in a subsequent firmware update? Or a hardware fault worth repairing?
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.
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?