Related
I have found that my One X often kills apps I have running when I press the power button and put it away for more than a few minutes. I know Android will try to reclaim resources starting with background apps but this is killing the app I am currently looking at.
I have almost nothing else running and my system normally has 200-300 mb of available memory so it is a very unexpected behaviour. A typical example is I have something like firefox displaying a page. I read a bit then press off. I come back 10 minutes later and it needs to restart and reload the page. With previous phones the app would still be in the foreground the next time I turn it on and unless I navigate away it would stay that way.
I have a nexus s running ICS and that does not happen.
I have a desire running GB and is doesn't hapen.
I have a desire running Froyo and it does not happen.
Is there any way to force a less aggressive memory management on HOX?
There is an option for this, in settings > developer options, furthest down under apps section, first one; "Don't keep activities" check if it is enabled.
Sent from my HTC One X using xda premium
.. also beneath it, there is a restriction "Background process limit", it may also cause immediate kills if "no background process" is set
Sent from my HTC One X using xda premium
Thanks for the suggestions but those were set normally.
Tried using the built in browser instead of firefox and the problem was significantly reduced. It seems the system has a bias against non google apps. Even so - this HOX is behaving different in this respect to my other phones. It is my expectation as a user that if I am doing one thing, that thing should still be there the next time I look at my phone.
Something on the device may be leaking and the result is this need to stop stuff. My money is on sense ( mainly because of the observed ripple/flicker on the home screen ).
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Seeing the same issue on my One S.
This happens with Dark Meadow. If the screen times out, or you hit the lock button, the game kind of "crashes". Not sure if this is the One X killing it or whether it's how the app is coded.
It's irritating anyway ><
Applications with a notification icon have not this behavior. Is there a possibility to set a higher priority to applications without root?
I'm having the same problem.
With cm9 @ Desire Z, I could, say, restore my 3000 sms within GoSMS (which takes a while) and meanwhile do whatever I wanted with the phone, eg. browsing, texting and so on.
With the H1X, after a certain time, the apps gets killed/suspended and therefore anything that happened within the app - which is pretty annoying. Any solution in sight?
H1X @ ARHD
I get this too. Annoying.
ViaraiX said:
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Click to expand...
Click to collapse
Sense launcher closing is not cos of the over-aggressive app killing. It's cos the system needs more RAM, so closes Sense since it's not directly in use right now. I do notice that some apps are getting closed after a period of inactivity, probably a default ICS setting that we can tweak when kernels and ROMs get more mature releases
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
harryshepard said:
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
Click to expand...
Click to collapse
If your battery is that bad you have a bad app running rampant or your battery is faulty.
For everyone else, even in settings if "Don't keep activities" is unchecked, try checking it and unchecking it. I read that sometimes it is still set to "Don't keep activities" even if it is unchecked and checking and unchecking it could solve the problem if this is the case. Doesn't hurt to try.
Hopefully one of the devs will make a Rom/kernel with better oom adjustments... I'm hoping.
the multitask implementation on this phone is terrible. I was using runkeeper, stopped to check something in my settings during the ride, phone closed the runkeeper application deleting my ride. It is getting annoying ...
I've been having issues with the GN2's performance while scrolling menus and playing games. Jetpack Joyride is the most noticeable, with it stuttering all throughout. This even happens with simple games like Scramble with Friends, making it more unresponsive than it should be. Plugging the phone into the wall seems to lessen the stuttering. It also appears that the longer the app is used it slightly lessens the stuttering.
Strangely, frame rates seem better while playing 3D intensive apps like Death Dome.
My Galaxy S2 did not have any of these problems throughout its entire life span, ever. It did everything buttery smooth, which is strange considering this phone is supposed to be more powerful. The stuttering isn't terrible, but it's definitely there, and I'm not exactly happy with it.
This occurs no matter how many idle programs are closed or what Launcher that is used. I've used TouchWiz, Launcher Pro, and Go Launcher.
Is anyone else having this problem? Is this something that can be fixed or should I return the phone for another?
make sure power save is not enable.go to setting and check
mintu123 said:
make sure power save is not enable.go to setting and check
Click to expand...
Click to collapse
Wow, hahaaa! Thanks a lot! That's silly to think that works. I felt like it was some sort of power related issue and was sooner going to overclock the CPU than suspect that option.
It didn't work immediately after disabling it, but once I restarted the phone everything was fine. THANKS AGAIN!!
In the interest of making things easy for those who are holding off on the KitKat OTA, I thought it might be a good idea to consolidate all of our experiences into one thread. This is intended to cover mainly the changes specific to this OTA over Razr M-flavored Jellybean.
I'll start with my experience/thoughts and edit in additional findings. (Note: I'm bootloader locked, and now unrooted.)
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
My opinion, overall:
It's a nice upgrade, but all of little problems I've encountered (bugs, Verizon blockades, the works) make this feel like a bit of a letdown after the 6-month wait. In the end, after just three days, I find myself wishing I could take the phone back to Jellybean.
Here's hoping for either some exploitable holes or maintenance updates.
My opinion
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
Worth noting that I am using an unlocked bootloader, with CWM and SuperSU (only really did this to remove VZW bloat and install Xposed)
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to show more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
ATTACK said:
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to so more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
Click to expand...
Click to collapse
Gonna be doing some more testing in that regard. Even my M7 with its garbage radios gets LTE just about everywhere in the Metro Detroit area.
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
I have had the KitKat OTA now for 2 days and haven't found anything major wrong. The changes to the keyboard bugged me but I use swiftkey so that was moot. I also have an issue I haven't seen listed yet. The new sound for screen taps....it seems to give that "popping" feedback (that ive seen listed as an issue on driver start-up) ALL the time. I maybe get 1 clear sound out of every 5-6 screen taps. That is the only real "problem" I can find as of this point though. Does anyone have any insight on that?
Also activated Dev Mode and changed to ART runtime. Might be placebo but app response seems to be noticeably better! Not groundbreaking by any means but better than 4.1.2 for sure. Overall I am happy with the upgrade. Rather, will be happy once a root exploit comes up (I miss my debloating! On that note though, disabling apps never seemed to work right with 4.1.2....after hitting disable the app would show back up in active processes after a short time. Now I've gone 24 hours and 3 phone reboots and that damn NFL app is STILL disabled and NOT running as a background process. Might just have been an issue with my phone in particular before, but its fixed now!)
I am generally happy.
It fixed all the issues I had with Dhackers KitKat.
and feels about the same once you have rid of all the Bloat.
I like and I am happy that we still surprisingly got the update unlike the Galaxy S3
Happy =)
Just wanted to comment on the heat issue mentioned above:
I have only had KitKat for 2 days but I have definitely noticed a difference in heat after extended use compared to JB. One of the things I really liked about my Razr M was lack of heat so hopefully this is a fluke and I wont notice it too much in the future.
---
With that said, no big issues.
I don't like the keyboard -seems smaller, or something, The heptic feedback seems to be different too (for the worse IMO).
The lockscreen number pad seems smaller - definitely liked the number pad from JB.
I had to change the messaging app (hated the all white/lack of contrast). Using "8sms" if anyone is curious.
I also changed launchers to use the google-now launcher so the "okay google" thing would work on the homescreen and also get the transparency notification bar. But, in doing that I did lose the circle widgets which I liked. Can't win for losing sometimes...
---
On a positive note, Chrome/google searches seem to be much faster. The UI seems about the same (no complaints with JB).
If battery life can increase then I'll be satisfied with update (so far, no difference).
My experience has been very positive. My phone was bootloader locked and not rooted before (and, of course, after) the OTA. I cleared the cache partition from the recovery menu post-install but have not done a FDR. General impressions:
-- UI is overall much snappier/quicker. Extremely noticeable.
-- Love the new quick settings panel that you can get to after pulling down the notifications shade.
-- KK's changes to how the SDcard works have not been a big deal at all for me. The native "Files" app seems to have complete read/write access, as does ES File Explorer.
-- Like the new clock feature to automatically add a "home" display when traveling outside a pre-defined timezone.
-- Hate the new way you set the alarm on the clock. (Really, whoever came up with that input method should be transferred to a department where s/he can never affect design decisions again.)
-- I miss the audio silencer/mute on the lockscreen.
-- Battery life has been interesting. When I first installed the update (morning of 05/15), battery life was definitely worse, probably by about 50%. It has gradually been getting better, however, and now is probably only about 20%-25% worse than JB. Why it would change I have no idea, but it definitely is (I've been keeping notes, and am sure it is actually happening). I have noticed, using the Battery History details screen, that there are a LOT less wakelocks in KK than JB. In JB, I used to see tons of "Awake" indicators on that screen that did not pair with "Screen On" indicators. In KK, there are very few incidences of "Awake" that are not paired with "Screen On." Someone smarter than me will have to explain how that translates into worse battery life.
-- It may be my imagination, but it seems like the battery charges faster w/ KK. If it's not my imagination, I wonder if that means that the apparent decrease in battery life is really an issue of improper calibration/accuracy.
I have not experienced some of the things others have reported:
-- No random reboots.
-- No changes to WiFi or 4G signals. I don't use Bluetooth so can't comment on that.
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
4039995825
GPlX said:
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
Click to expand...
Click to collapse
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Nidstang said:
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
Click to expand...
Click to collapse
Attempted a FDR on my phone, unfortunately it did not work for me. I will attempt to clear the cache partition to see if that may help the issue if
possible. So far i can only get the boot menu for a couple seconds and im lucky to get a selection in time.
EDIT: I cleared the cache partition, no effect. (NOTE: it seems to get into the recovery menu after selecting it at boot menu, you have to hold power & vol UP for a couple seconds)
crazy4android said:
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Click to expand...
Click to collapse
That is an excellent point. I'll shut off the optimization and will edit my results in after tinkering with it for a while.
EDIT2: Without doing speedtests etc. It is very noticable that the wifi has improved. Youtube & other apps load as fast as they did on 4.1.2
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
kashif87 said:
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you can uninstall updates to the cam in apps
bwer1233 said:
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
Click to expand...
Click to collapse
Lockscreen widgets were introduced in Android 4.2.2.
Just want to let people know that the Google Now Launcher is working great on 4.4.2 including the "ok Google" functionality.
You can't download it from the play store. I just grabbed the apk from this thread.
http://www.xda-developers.com/andro...-and-gpe-devices-apk-mirrored-for-all-others/
Sent from my XT907 using Tapatalk
rooted + cwm
can't use "memory" feature under settings, while calculating settings app would crash
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
tieuvienson2005 said:
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
Click to expand...
Click to collapse
There are many "phone info" apps in the Market. Or create the short cut with Activity Launcher.
Also the Cam sucks on my Wife's m so get the Lenovo from my Moto x signature link.
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.
I already tried disabling touch sounds and similar things.i know its not any of my music players cause it shows as a seperate lock.i dont have music playing the whole day and the battery drops like crazy for no reason. Any way to pinpoint this wakelock or a fix?
Are you rooted? Have you tried Amplify? I don't usually limit that wake lock but it's safe to limit per Amplify.
I found that wake kick and tried limiting and didn't seem to have an issue until the first time I used the S Pen. After the tone to initiate screen write, Amplify unexpectedly went back a step and became unresponsive; had to kill the Amplify and try again. I noticed the blocked wake count had increased by one when I came back in to make the scroll capture.
For some reason, I can't keep the stats reset but momentarily. I can see that the wake locks were reduced by nearly two thirds and wake time seems limited more than expected. It was very high unlimited but I can see a difference since limited.
If you're rooted, try it. Reply back if it seems buggy with limitation. I use a sound mod that includes V4A and Dolby Atmos. I didn't have audio problems; I get notifications in sleep mode. But the initial S Pen issue was unexpected. Hopefully just a one time thing.
Sent from my SM-N910P using Tapatalk