Related
EDIT: According to garyd9, this is an Exynos issue and cannot be fixed. I believe him that this is an Exynos issue because it supports what I've seen, and he's a smart guy. I'm still holding out hope that there is some possible resolution in the future. Why else are we here if not to find ways to make our phones better, right? However, because of the nature of this issue, it's not going to be resolved by app settings, disabling apps, etc. If you don't see the lag yourself, it's because your phone isn't in deep sleep when you try to wake it.
Original Post:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem
More info from Entropy512:
Entropy512 said:
To be more detailed: It seems to be specific to how Samsung wires up the modem interfaces of Exynos devices. On Exynos4 devices, they're always hung off of HSIC (a variant of USB) buses. Since HSIC is based on USB, it has the same slow suspend/resume of USB. Almost all Exynos3 devices hung the modem off of a serial port if I recall correctly, and these devices could suspend/resume much faster. If you look at a resume sequence, there are huge time gaps, and after the first 200-300 msec, almost all resume activity is modem stuff.
The only solution, unless someone figures out a way to make the HSIC resume faster (I'm not messing with it, I have enough trouble getting it not to drop the bus randomly!!!!!!!), is to inhibit deep sleep with a wakelock - but this will be bad for battery life.
Click to expand...
Click to collapse
Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
Click to expand...
Click to collapse
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
u921333 said:
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
sling said:
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Click to expand...
Click to collapse
I'm getting about 2 second lag on both mine and my wife's AT&T N2s. Mine is rooted, hers is not.
Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem.
Click to expand...
Click to collapse
I have everything that you have listed except Turn off screen popup mode & I have no lag at all.
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
800ms???? No way can I wait that long lol jk
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
Bummer.
Jrockttu said:
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
Click to expand...
Click to collapse
I have used it on my galaxy s2 and my international galaxy s3 without seeing any negative battery issues. Now granted it has to have some effect but even with the not so great life on s2 wasnt noticeable. Try it out and see if it works for you. I was skeptical at first.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
I dont but I do know my galaxy s3 had it even when I was on aokp.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Like the poster above this says, my wife's Galaxy S2 has the lag on AOKP and AOSP based roms that do not have S-Voice. As much as I don't want to believe it, Gary is likely right that it's an exynos issue. I was just hoping that it could be solved through a kernel.
Tested it for ****s and giggles, definitely not S-Voice. I disabled it and restarted phone. Let it settle about a minute from start up, opened BetterBatteryStats to CPU state screen and looked at the "deep sleep" state. Turned screen off for a few seconds, lagged, checked deep sleep state to make sure it had increased (ensuring it was recovering from deep sleep). This is the simple method to test any of these supposed fixes that people say will solve the laggy wake.
Anybody that says their phone doesn't lag when they wake up the screen is likely because they're looking at it while they're charging it, they're playing music, they have an active notification, or they're turning it off and back on really quick. All of these prevent the phone from deep sleeping. Deep sleep is what causes the issue.
I had lag on my Note I whenever it would deep sleep on any Rom. This only happened when I had Wi-Fi off when sleeping. When I turned Wi-Fi on all the time lag was gone. Not a clean battery friendly fix but the lag was driving me crazier than charging the battery a little sooner.
Sent from my GT-N7000 using Tapatalk 2
I have the att version and I was just wondering...the same thing...I am willing..to try anything...I mean it sucks just waiting a little bit. I was just waiting for a new rom
daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
truth77 said:
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
Click to expand...
Click to collapse
The only thing disabling S-Voice does is make your Home key work faster once the phone is already on because it's not waiting to see if you're double tapping it. S-Voice has no impact on the wake issue.
Mj23foreva said:
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
Click to expand...
Click to collapse
That's the first thing I watched this morning when investigating this issue. If you notice, his "fix" doesn't seem to work that well for him. Try it yourself, it won't work. That's why I put it in the OP that these don't work.
No lag here and the phone's been in use/running for 24 hours now.
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Bliznade said:
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Click to expand...
Click to collapse
Ive noticed it as well. Got used to it and it don't bother me anymore but a solution would be nice
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=33492447
Sent from my SAMSUNG-SGH-I317 using xda premium
have you tried to increase your minimum deep sleep cpu frequency from 200mhz to maybe 350mhz or so?
a shot in the dark would be reducing the animation scale in developer settings but this is only if it's considered an animation when you turn on the phone
battery life is amazing on this phone and if you agree and want to try it. There is a app called soft locker on the market that will fix the delay. I dont notice that much of a drain on the battery even though I know it has to have some. Basically the CPU in samsung phones go into a very deep sleep and that helps battery but if you use the above app it creates wakelocks that keep it from deep sleep and fixes the issue.
This can make battery life less but like I said I have used it for over a month and still get over a day out of my phone and I usually have 4 hours or more screen on time and still end day with 25%-50% battery left.
http://forum.xda-developers.com/showpost.php?p=35617276&postcount=2096
Apen83 in the Jedi ROM thread says to do this:
"Settings > developer options > window animations off / transition off / animator duration off"
Looks like its working for them.
If it works for you, hit the link and thank his post.
This doesn't help as it's not an animation.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
It's a characteristic of Exynos processors. It sucks, but what can ya do?
I'm using asylum rom and kernel and see nowhere near the delay that stock had. It's almost instant on for me
Its probably the pegasusq governor, but that's what you have to go with to be able to hotplug CPU cores. This is the price you pay for battery life.
You did not search well enough. There is no solution, and nothing you can do about it other than the aforementioned Soft Locker, which will negatively impact your battery life.
More info here: http://forum.xda-developers.com/showthread.php?t=1983697&highlight=wake+lag
It sucks, but I guess it's a sacrifice I have to live with on an otherwise awesome device.
I've a serious problem in my phone that appears after upgrading to ICS, frequently when someone calls me it gives him ring and my phone do nothing and it doesn't even shows it in the missed calls, when i tested this from my other phone the phone didn't respond until i press the standby button it starts to ring!!!, this issue always happens when the phone is on standby and when i press the standby button i noticed the signal fluctuating from 0 to full like crazy and stabilizes after a second. I'd like to say that it happens frequently not every time (once or twice daily).
i had to activate the call forwarding when not answered option to my another phone until i found any fix for this issue, i was using stock ICS then used custom and rooted rom then lite kernel and nothing changes, i used CPU tuner app to set the min CPU seed at least 750 and nothing changes, changed the sim and no changes, I didn't have this issue before when using GB.
I'm currently using this phone in Egypt with Vodafone as it is unlocked
Can any one help.
Thanks in advance
Update
i had found a new app on Google play prevent the phone from going to deep sleep called (wake my android pro), it is a free app as it allow the phone to sleep and not to deep sleep so it is not consuming battery like (wake lock) app which keeps the phone running in background and reduce battery cycle for about 40%.
i had tested it for 10 days i didn't loss calls so far
still waiting for a real fix.
How about some search?
here (some workaround avail)
or
here
braintweaker said:
How about some search?
here (some workaround avail)
or
here
Click to expand...
Click to collapse
thank you for your reply, actually i'm searching in this issue for 2 months and i see the above links before,i was looking for a real solution not workaround as the device is already draining battery and the solution will make it worse.
i was looking for a mod or a even a rom that solves this issue because GB was working fine but its too old now.
anyway thanks again
Well, I think if there were a solution, it would be posted shortly. I am not satisfied with the wake lock too, so still at GB
I have this annoying ''bug'' on the 2 custom roms I tried as well as the stock unrooted rom, sometimes I got up to 2 seconds of lag between the double tap thingy and the screen to wake up.
I don't remember having such lags with the M8 though I was using the Dot View cover double tap.
Why is the M9 doing this? Could it be too much apps working in the background? The infamous M9 wakelocks? Could it be the LP 5.0.2 memory leak?
It occurs once over 3 times perhaps, I always mocked old sammy phones to have this lag with the home button/screen wake and now we have this lag on the 2015 M9 :crying:
vegetaleb said:
I have this annoying ''bug'' on the 2 custom roms I tried as well as the stock unrooted rom, sometimes I got up to 2 seconds of lag between the double tap thingy and the screen to wake up.
I don't remember having such lags with the M8 though I was using the Dot View cover double tap.
Why is the M9 doing this? Could it be too much apps working in the background? The infamous M9 wakelocks? Could it be the LP 5.0.2 memory leak?
It occurs once over 3 times perhaps, I always mocked old sammy phones to have this lag with the home button/screen wake and now we have this lag on the 2015 M9 :crying:
Click to expand...
Click to collapse
hello.
I have the same exect problem. Every time my phone is not used for a while i get massive lag on wake up guestures.
Did you find out what is cosing this lag?
Same here as well. It didn't happen on the M8.
If I kill all the recent apps it's a temporary fix, but it's not cool to do this before everytime we want to close the screen, it looks like a bad RAM management.
I hope someone can post this bug into Elevate so HTC fix ir
vegetaleb said:
If I kill all the recent apps it's a temporary fix, but it's not cool to do this before everytime we want to close the screen, it looks like a bad RAM management.
I hope someone can post this bug into Elevate so HTC fix ir
Click to expand...
Click to collapse
Hopefully 5.1 fixes it and is released soon.
same here. my M9 doubletap does not awake sometimes and I need to try few times, or even use my power button. someone suggested to me to wipe cache and Dalvik in twrp. seemed to improve (but i dont know if its just psychosematic.)
Disabling Zoe help alot reducing the lag
Sent from my HTC One M9 using XDA Free mobile app
vegetaleb said:
Disabling Zoe help alot reducing the lag
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Already disabled it (and the other htc *rubbish bloatware) when I got my M9 new.
Wondering, Could it be Greenify then?
simonbigwave said:
Already disabled it (and the other htc *rubbish bloatware) when I got my M9 new.
Wondering, Could it be Greenify then?
Click to expand...
Click to collapse
I think it has to do with RAM in general, I have the absolute bare bones on the ROM I use and I have issues with double tap to wake and even sometimes with the power button. I've noticed that the apps running option in settings doesn't accurately display how much RAM is actually being used. Just restarting the phone clears it up, but I have to do it once or twice a day.
Mine too peeps and I'm glad someone aired that one out ..personally it's annoying but not a deal breaker .I strongly feel it's a lollipop issue since google released multiple builds helping memory leaks and what nots
I dont believe it's a ram problem. The phone goes in deep sleep when you don't use it for a longer time. This you can see in the graph of your battery usage. This is normal behavior and saves alot of battery.
You'll see that standby time is way better when you don't check your phone every couple of minutes.
You don't have the lag if you try to double tap every or so minutes.
So ram problem is out the window. Or else you would be having it all the time?
And more importantly...you'll be having serious lag opening all of your apps.... Just check the s6 thread. ?
O.T.:Be careful crying ram problems or within no time there will be ram problem hysteria... (like camera hysteria,heat problem hysteria and so on...?)
Sent from my HTC One M9 using XDA Free mobile app
Auto-kill Google Playstore with a Task killer help too but it will drain your battery, looks like a Google 5.0.2 app bug
BUBBA DUB'S said:
I think it has to do with RAM in general, I have the absolute bare bones on the ROM I use and I have issues with double tap to wake and even sometimes with the power button. I've noticed that the apps running option in settings doesn't accurately display how much RAM is actually being used. Just restarting the phone clears it up, but I have to do it once or twice a day.
Click to expand...
Click to collapse
If it was a ram problem don't you think you'll be having huge lags opening other apps? If ram runs out you will be seeing apps being closed when you open new big apps.... The only lag you notice is when waking the device when coming from deepsleep.
When it's running and you start opening apps you never run in to lag.
At least not on my phone.
Sent from my HTC One M9 using XDA Free mobile app
I get this mate, usually when I'm trying to show someone it..in all fairness tapping just below the center of the screen seems to do the job, don't tap too quickly.
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
vegetaleb said:
Auto-kill Google Playstore with a Task killer help too but it will drain your battery, looks like a Google 5.0.2 app bug
Click to expand...
Click to collapse
Avoid them mate, the criteria for apps doesn't change with app killers, the start stop process actually uses more battery than it saves. Use auto starts mate.
I think the up threshold for screen off could be raised a bit to help with the lag, I can live with it tbh, haven't tried it yet.
dannylow79 said:
If it was a ram problem don't you think you'll be having huge lags opening other apps? If ram runs out you will be seeing apps being closed when you open new big apps.... The only lag you notice is when waking the device when coming from deepsleep.
When it's running and you start opening apps you never run in to lag.
At least not on my phone.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Just my opinion sir, with no apps open and coming from a deep sleep I've only had a few issue. It comes more (for me) from multi tasking with multiple apps open for a prolonged period of time, turning screen off and then trying double tap or press power button on a minute or two later. I just wanted to know why the device thinks it has so much memory free. I should I have re worded my first post, I get what you are saying
I never experience this lag, but I did happen to recently have an occurrence. It happened when, by coincidence, I picked up my phone and double tapped right at the time my phone was receiving an email. Apparently being busy with a data process delayed the the screen waking. I'm just wondering if you all that are experiencing this issue have the phone set to turn of data during sleep mode and upon double tapping to wake an app waiting on data is beating the screen to the punch. Or maybe the act of data becoming active again is delaying the screen on. Just grasping at straws here, but it definitely sounds like something is interfering with the screen on process.
I didn't have any issue before the latest update but now it wakes too slow, even up to 4-5 seconds.
dannylow79 said:
If it was a ram problem don't you think you'll be having huge lags opening other apps? If ram runs out you will be seeing apps being closed when you open new big apps.... The only lag you notice is when waking the device when coming from deepsleep.
When it's running and you start opening apps you never run in to lag.
At least not on my phone.
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
BUBBA DUB'S said:
Just my opinion sir, with no apps open and coming from a deep sleep I've only had a few issue. It comes more (for me) from multi tasking with multiple apps open for a prolonged period of time, turning screen off and then trying double tap or press power button on a minute or two later. I just wanted to know why the device thinks it has so much memory free. I should I have re worded my first post, I get what you are saying
Click to expand...
Click to collapse
My experience is more similar to Bubba Dub's here. There is almost always a slight delay in awaking with MLG or double tap, but every so often there is a multi-second delay and it almost always occurs after only a few minutes of inactivity and NOT after a deep sleep. It seems I'm most likely to experience the issue when I turn the screen off, then shortly thereafter go to wake with an MLG. I get the normal haptic feedback with my gesture, but the screen stays black for a second or two...long enough to make me wonder if I imagined the haptic...
I've found that turning off Auto Rotate seems to sort it out, though as soon as its re-enabled it happens again.
It's really annoying with a dotview case as sometimes there are massive delays when opening the flip, other times its instant and free RAM is always round 2.5-2gb due to custom rom and bloat removal. It happens on Stock, Stock Rooted, Custom Rom's
hlhmark said:
I've found that turning off Auto Rotate seems to sort it out, though as soon as its re-enabled it happens again.
Click to expand...
Click to collapse
I turned auto-rotate off and just got the "big" delay (as opposed to the normal lag).
I found it very hard to find information from people who actually have the update in other threads because it is mixed with information on how to actually obtain and install the update.
So what are your impressions of tge 5.1.1 update ? Please only post if you have the update installed and running for at least few hours.
My impressions:
- Battery life is worse, like 30% worse with Wi-Fi detection on, even if mostly using Bluetooth.
- Still can't edit the canned response list Emoji drawing is a bad joke.
- I can't dismiss notifications with flick gestures (only hide them)
- Very smooth and responsive UI overall
- No annoying "Ok Google" text on watch face until you say "ok Google" 5 times
Battery life for me for 5 times better.... One thing, this enables 'always on' apps... I would check some of your apps and see what battery consumption is. I've been in my watch since about 10am and I have 53% left right now. Way better than anything I have ever gotten. This is with wifi on.
It's pretty fantastic for me. I have no complaints. The processor is old, but I'm very impressed with how optimized they've made it. The lag just doesn't interrupt my work flow, unlike with the Apple Watch at least. There's no major delay. Will likely be buying V2 or V3 depending on how I feel the life cycle for these devices will be.
Updated yesterday. I feel like the battery lasts less, but you have to give it 2-3 days to settle down. Liking the new features, but I don't think I'm gonna use Wi-Fi too much since it drains battery.
For now, I'm keeping WiFi, gestures, and ambient mode off. This way within a week I'll have a true comparison of battery life. Then I'm going to test each function and how it effects battery. I'll let everyone know how it goes.
Have the update one day now,
Good points:
-Smootness
-less buggy
-wifi when out of range
-wrist flick(great idea)
-Google maps maps
Bad points:
-Wrist flick is hard to perform correct (think it is a learning curve)
-When wifi is active on whatch and is connected but phone isn't connected to internet it still says it is connected.
-Laggier in first minutes after boot
-Lock screen sometimes activates when on wrist.
Overall i'am happy. Batterylife is to early to judge
I got the update yesterday after resetting my device. The first thing that I have noticed is that I can no longer dismiss notifications that only take up the bottom part of the screen. I have to pull the notification up and can then dismiss it. If this is what the developers intended, then that it is a major step backwards.
Also where do I setup which apps should stay "always on"?
Battery life after the update is disasterous, about 6% per hour but I need to give it a few days to sort itself out.
The dismissing of notifications is very much hit and miss and is impracticable.
At the moment I am not impressed with the update. Hopefully things will sort themselves out over the next few days.
For me, the update has been surprisingly good.
Good:
- Battery life (which I must admit, was my primary concern) is as good as it was prior to the update, even with the watch connected to WiFi.
- I love the flicking gestures, they work exactly as I imagined they would, although they're not as smart as they should (you can swipe available cards up and down, but when a card has multiple sub-cards, you can't scroll between them).
- Performance is great, specially considering it's a device with 512MB RAM, UI is still responsive enough and with very little lag.
- I love the new contact screen, it saves me a lot of time for quick calls when I can't remember the contact name (I normally use Google Now to call someone).
Bad:
- For the life of me, I haven't figured out how to enable always-on apps. It's one of the features I've been waiting for so eagerly, specially for Google Keep's checked notes (which I use A LOT).
- The WiFi connection is USELESS if you leave your phone home and find a protected WiFi network, because you NEED the phone to input the password. It kinda defeats the whole purpose.
One thing I noticed after the update is all of my hangouts threads became unmerged. Now each person has SMS/Hangouts as seperate threads. My one buddy experienced the same issue when his watch updated. Not sure why the software update would cause that, but it's upsetting.
Overall, I'm really liking the update. The only thing that's really bugging me is that you can't seem to dismiss notifications unless they're open. I'm used to being able to dismiss them immediately if I can get all the information I need from their title. Now, I actually have to swipe up first to open them, and only then can I dismiss them. It's not so bad that I can't live with it, but it is annoying.
The update has exceeded my expectations so far. I have only had it installed for about 12 hours. Battery life seems better. Worst case I don't think it has gotten any worse which was a huge concern because it hasn't been so wonderful. It seems to give more feedback and explanations so I'm not guessing as much. For example when I added a playlist it informed me that the battery needed more charge to download to the watch. Prior to the update I would have been scratching my head all day and then it would magically download when I charged up at night.
I really hope the WiFi works as advertised. I can think of many ways it could be useful to me. It seems like there are lots of times when I want notifications in case of an emergency because I'm a single dad but I also don't want to carry the phone with me.
My biggest annoyance with update is that now I have to open cards before they can be swiped away. Most times I can tell what a card is telling me and used to swipe them away without opening them.
Seems more responsive.
As others have said, removal of swiping / dismissing the previews was not a good call.
Not entirely sure, but looks like I won't be able to connect to my work WiFi which uses certificate based EAP-TLS authentication ? Will see when I'm back in the office next week.
Sent from my Lollipop TF700T
Do the other watches have the same issue (yeah, I'm calling it an issue instead of a feature) with the notification swiping? Or maybe this is something Motorola did thinking they were compensating somehow for the flat tire? Regardless, I hope there's an update to fix it, it just annoys the piss out of me every time.
My first day battery report.
Off charger at 9am, end of the day (11pm) 67%. This is with WiFi and ambient mode off so I can have a direct comparison to prior then update. But to me that is a huge improvement.
Has anybody figured out how to enable the App Always On feature?
I've updated my watch yesterday and wanted to let my watch get to 0% to calibrate the battery because of the new update. so I didn't put my watch off at night, and the next morging (today) my watch was 10% and the screen was totally black and it wasn't responding to the side button so I tried to hold it for 30 seconds to let it restart I saw the normal bootupscren but as soon it was staring the app it became black again. I now have let it charge to 100% and it it's responding perfectly again. Does anyone know what was wrong?
Thanks for your time!
user of android said:
I've updated my watch yesterday and wanted to let my watch get to 0% to calibrate the battery because of the new update. so I didn't put my watch off at night, and the next morging (today) my watch was 10% and the screen was totally black and it wasn't responding to the side button so I tried to hold it for 30 seconds to let it restart I saw the normal bootupscren but as soon it was staring the app it became black again. I now have let it charge to 100% and it it's responding perfectly again. Does anyone know what was wrong?
Thanks for your time!
Click to expand...
Click to collapse
I noticed the same behavior when mine was at 2%. It did not respond to screen touches and only switched on for about half a second after clicking the side button several (5 or more) times. It still took about 30 minutes for the watch to finally shut down. Maybe this is because of a very aggressive battery saving mode?
I must add that I did reset the watch after the 5.1.1 update was fully installed and wanted the battery to drain completely for the same reason you did: to recalibrate it.
Sent from my One S using XDA Free mobile app
Mister-B said:
Has anybody figured out how to enable the App Always On feature?
Click to expand...
Click to collapse
I'm thinking it may only be an AMOLED feature.
Mine had the same issue at 10%. I wonder if this is related to the performance issue Motorola was talking about.
I don't know if I am happy or sad that this is widespread. Hopefully they patch this up.