Related
For those with Droid 3s that love to randomly reboot. and crash/lag
and also crash on camera, here is a fix
1) FACTORY RESET PHONE (Erase all data)
2) When its back up and your signing back in, DO NOT CHECK 'Restore Data' or 'Keep Device Backed up'
3) Open settings later, and ensure they're both unchecked under Privacy
NEVER enable them
4) For safety incase wifi settings were restored:
Go to Wireless and Networks, Wifi Settings, Manage Network Settings, tap first option and itll say 'forget or erase wifi settings' , choose Yes
5) Reboot Phone
*If camera is still not up to your standards, use Camera360 from market.
Should be all fixed up, no more reboots or crashes, and fast.
I guess its a temporary fix until Moto serves an update.
Sucks if you rely on backup to get your apps back, but Titanium Backup is a nice app to backup settings/apps
I have random reboots also, but the strangest thing is that when I shut the phone off I can put it in my pocket or on a table and it will turn itself back on. Was wondering if this would help this as well?
Is it being charged when it turns back on?
Nothing is pressing the power button right
Not sure of your issue would be fixed by this you can try
Sent from my MB860 using XDA Premium App
not being charged when it turns back on,
nothing pressing power button. will try and let u now what happens.
Hey Guys,
I know this thread is ancient, but I couldn't find anything newer on that topic.
I'm having the random reboot issue since a while now and wondered if you could help me piece together what I've got.
I managed to find a way to provoke the reboots and that is by flooding the RAM. I opened up some random apps (doesn't seem to matter which ones, as long as they consume a lot of RAM) and it crashed rather quickly. I also managed to get a Logcat of that, but it seems pretty normal.
I attached the Logcat-Log of the last 15 sec before the crash.
But sometimes there are reboots that happen when I don't have anything intense running.
Also sometimes (often when I am using rather intense apps) the phone gets stuck with the screen turned off and it essentially acts like dead until I do a battery pull. Sometimes when it does that, it just reboots on its own after a minute or two. That could be what Cglocke might have been experiencing.
I am running an XT860 with System version 5.2.476.XT860.BellMobility.en.CA and Android Version 2.3.6
Does anybody have any ideas on that topic?
Try using rom toolbox to increase the memory management to aggressive
Sent from my DROID3 using xda premium
Hey guys,
I am using my Moto X (XT1052) for almost 2 years now. It is/was the best android phone I've had so far. It was smooth, had no hangs and just did what it was supposed to do. Since I received the Update to 5.1 I keep on having real strange issues and it really bothers me because it really renders the phone useless at times. And since I couldnt find another thread with all bugs collected in one place, I am going to start my own thread.
So which bugs did I find so far?
1.Youtube and other video services don't work all the time
(They work sometimes, but the the video stops, tries to resume and ends up in a loop trying to load the video. Often only a reboot helps.)
2. Battery consumption in general has become way worse (cell-standby)
3. Random "Optimizing apps" after a reboot
4. No Active Display with handsover (I know this isn't a feature anymore, but to me this is a bug as well)
5. Missing energy widget
6. Wifi range has reduced significantly and seems to be buggy at times (can't always tell if it's my router or the phone, but mostly it's the phone)
7. Sometimes the phone uses mobile data instead of wifi, even if connected
8. Vibration mode (important notifications only) doesnt always end properly and the phone doesn't start vibrating again after the set time or alarm
I think that's it for now. But this clearly is enough for me.
So please Moto guys do something! If you need logcats or anything else, let me know and I ll help out as good as I can. I was one of those who patiently waited for an update instead of crying for one, because I wanted a stable one rather than a fast and unstable one. So either fix it, or I ll have to return my Moto X. The phone in its' current state is useless for me. Especially as I can't even downgrade without having to risk a full brick. So please do something and push an update to either allow downgrading, or fix the existing bugs!
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
Hey guys,
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I miss this very badly
"No Active Display with handsover"
Now I have to tap or take my phone to see notifications... :crying:
I switched over to CM and all is going great of course at a small cost of losing Moto voice feature but I can most certainly live without it. I've got very decent battery life of 5-6hours of screen time over a span of 13hours. No over heating issues and usually cell standby sits at 2% usage which is absolutely fine for me.. Even the hand wave gesture works with active display. I'm so happy with how stable it is with CM. Living with a bug free phone for now.
Sent from my Moto X
Random Crashes followed by optimization boot
I have been getting random crashes that lead to the phone shutting off. When I turn it back on, it takes FOREVER to optimize 92 apps. I don't have even 30 apps on the phone!
I did a factory reset and still have this problem. It's happening every couple of days. It's making my experience with this phone very frustrating!
Some more issues I've found:
Soundproblem, sometimes when I switch e.g. from twitch to spotify and then try to increase or decrease the volume, I get a crackling sound every time I push the button. Sometimes it disappears after a certain time of not playing anything, but mostly again only a reboot helps.
The phone unlocks itself more often in my pockets for no obvious reason.
The unlock on the ActiveDisplay unlockscreen often only leads to the normal unlocking screen instead of the homescreen. Same thing when I try to open notifications. Mostly those apps run, but I get to see the normal lockscreen, instead of the app with the notification.
Sent from my XT1052 using XDA Free mobile app
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
adity said:
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
Well that's not exactly what I would call a fix it appears to work sometimes though. I also noticed that simply changing the video quality from let's say 720p to 480p often resolves the issues. I mostly get the video bug, when I am trying to watch things in 720p or above. Maybe it is a codec problem? A broken lib?
Sent from my XT1052 using XDA Free mobile app
For YouTube, you could get another app. I stopped the cell standby issue by turning off carrier internet when not needed. Install greenify, servicely, battery saver, and power nap. 1 I too have random optimizing of apps. 2 pocket dials have increased, 3 if I tap on the phone icon from messaging app to make call to that person, I have to exit out of the SMS app before I see the call screen. 4 sometimes when I'm multi tasking I go back to another app but the app reloads and doesn't take me to where I was. 5 Google now voice only responds 30% of the time when i say hello google. Some other problems I have noticed but can't think of right now
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
Good thing I waited for a version that I could go back to kit kat because it didn't update the bootloader to lollipop. This is the thread if anyone is interested. I flashed this rom for xt1053 on my Rogers xt 1058, with only speaker phone not working away from WiFi for some reason, but that's if you flash on another moto x besides xt1053. http://forum.xda-developers.com/showthread.php?t=3155843
1. Battery drain (cell standby) makes the phone unusable.
2. WiFi does not connect or only works rarely now.
- download two times on whatsapp
- dialler doesnt dial a call
Sent from my XT1052
Cell Standby Battery drain is the worst..
Randomly restarting and optimizing apps has been a huge problem as well.
I miss the wave to wake for active notifications...
But what I really hate about 5.1, is that when using wifi my mobile radio keeps active all the time...
This drains the battery while being on wifi...
Funny enough, when I'm on mobile data, everything is ok and mobile radio is active only when needed by the apps...
On wifi on the other hand, oh man... it's active all the time...
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Does anyone experience any problems with this setting on 4.1.3? On my phone if i switch it off it sometimes switches itself back on. It also seems to close down apps without notifying me. They are just greyed out and cannot be cleared or removed. (Podcast republic and swipe). Those two apps are also the reason i want it switched off as they stop functioning properly if on.
It seems to be linked to the power saving auto rotate switch-off bug as it tends to happen most of the time when the auto rotate isn't switched on again when i charge the phone. Anyone else experiencing this?
Phone is not rooted and run on stock rom
Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Sent from my ONEPLUS A3000 using Tapatalk
i snort flour said:
Lol everybody learning how to set up the new power savers that the development community has been using since the days of ics.
1st problem sounds like you ambient display enabled which will turn on your phone every time you receive some sort of notification. To fix this simply go into your settings, display and turn off ambient display and don't get it confused with adaptive brightness.
2nd problem to me sounds like you have aggressive doze mode active on all your apps or auto close high power apps. To fix this just go to settings, battery, click the 3 dots next to the refresh symbol near the top right corner, click aggressive doze..., if it's turned on make sure the slider is not enabled next to the apps you desire, hit the back button, click on the 3 dots top right corner again, click on high power usage apps, turn it off if it's on.
These battery savers in the Android os are basically hacked and slashed from development on xda. Greenify did most of these functions alone then if you were to mash greenify with power nap you basically got yourself aggressive doze with closing of high usage apps.
Sadly Google is still behind the curve as the power saver app on my Asus Zenfone 2 does a better job at saving power on lollipop because in addition to hibernating and closing apps it allowed you to turn off networks allowing only phone, sms, and alarm to work after the device is asleep and enabled upon waking or you could do super saving which did the same thing except the network stays disabled the whole time boosting standby time from 92 hrs to 105 hrs
Seriously though the best course of action here if this does not help you is to contact the developer of the app and tell them the issues your having, your device and a detailed log report and you will see better results faster because it's probably just an incompatibility due to the new os as apps always have issues with fresh out of the gate os systems and your might not be the only person with this issue but you just might be the only person to point it out for a long time.
Click to expand...
Click to collapse
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
Grab a catlog off of the play store they are fairly simple to figure out and they are free. I can't remember for sure but I believe I liked logcat the best as it provided a better ui with a more detailed and easier to read log.
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 01:46 AM ---------- Previous post was at 01:35 AM ----------
Eggstones said:
Thanks
A) ambient screen is off already
B) already done that but the apps work better if battery optimisation is on for them than off. They really misbehave if not optimised.
How do I produce the logs? Checking under the specific app under apps doesn't seem to have an app log option.
Click to expand...
Click to collapse
That's weird that it keeps turning back on hopefully it's not a hardware issue. Most likely due to a rogue incompatible app. Also if you haven't already done so check for an update and make sure you have the latest version and if that don't work the last thing I could think of to try would be to download the latest update and put it on your phone somewhere you can remember, reboot into recovery and erase your cache and perform a factory reset followed by another cache wipe just to be sure. Then select install update from zip file, navigate to it's directory and open it, allow it install the update and after it completely has finished booting don't use it but keep the screen from turning off for about 2 minutes
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 02:07 AM ---------- Previous post was at 01:46 AM ----------
Sorry I can't be of more help to you but I just got my phone today and I'm on the oos 4.1.3 and mine is doing just fine so far but I don't sync mail, push notifications, or use any social media which drain your battery like a hooker with your bank account. So far I'm at 10+ hrs uptime with 4 hrs of sot sitting at 66% battery life with an estimated 20 hrs left.
hope you find your problem or at least know where you got take your issue to which will be discovered in your cat log so you will know if it's the apps, kernels, os or hardware that is to blame and be able to address it to the proper source.
Sent from my ONEPLUS A3000 using Tapatalk
EDIT: Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
Bugs I noticed so far, please check if you can reproduce these yourself and let us know yours so we make a list. This is a thread I started on Asus forums and it might help ppl here to to iron some of these out.
1- After a call (accepted or not) the blue MIC image stays on the watch even after the call has ended (this happened on AW 1.5 already) - Multiple reports
2 - Watch vibrates non-stop during a call, even if you picked the call allready on the phone, the watch will start vibrating with no reason. - Multiple reports - SUPER ANNOYING!!!
3 - Battery drains much faster, with same usage I end a day with 30% on AW 2.0 instead of 65 to 70% on AW 1.5 - Multiple reports
4 - When not trough Wifi the "ok Google" command gives an error saying Google is out of reach, restarting phone fixes it, but if connection of phone and watch is broken, the "OK Google" voice command (or long-pressing the main button) won't work again, nor will other apps like the App store - Multiple reports
5 - if I pick one phone number with the "text message' icon, the watch does not go into listening mode to get the text content. Instead it keep on loading with the loading icon and no message can be sent out. However if I use "OK Google" command instead of go thru the Contact app I can send text messages - One report
6 - Turning theater mode on seems to break the alarm. Thankfully the alarm will still go off, but the screen becomes unresponsive. Clicking dismiss or snooze won't work. Restart of watch is needed. Only happens when the watch is in theater mode. - One report
7 - Huge delay when phone receives a call to when watch shoes that call. - Multiple reports.
8 - Dowload speed on watch is most of the times terrible slow - Multiple reports
9 - "Ok Google" actions takes much longer to activate than on previous version - Multiple reports
10 - WhatsApp-ing someone is impossible it keeps asking "to whom?" indefinitely. - One report
11 - Pairing seems to be having problems - One report
12 - UI losing frames - One report
13 - Keyboard missing some symbols - Multiple reports
1. This occurred to me on 1.5 but hasn't reproduced it for me on 2.0
3. Battery draining around 4% per hour. Seems very similar to 1.5
9. Seems about the same to me.
Clean cache!
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
1. Works good, no issue
2. Works good, no issue
3. Battery almost same as 1.5
The rest i do not use or no problems with.
Annoying : swipe left change to change watchface. I do not like it this way
I received my watch off of Amazon two days ago, let it go through it's initial updates and then took the 2.0 update. It seemed to be working okay, but I did an FDR as I often do after major updates and it completely screwed the watch up. It reboots every five minutes now.
I unlocked the bootloader, downgraded back to 1.5 and tried the process over again to no avail. Not sure if it was the upgrade or just a dud watch, but I'm glad I'm still within my return policy deadline.
mkengel said:
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
Click to expand...
Click to collapse
I did this now, if it fixes the bugs listed, well, fantastic.
mkengel said:
None of them, except for keyboard symbols.
All the same issues until I clean the cache.
1. Turn off the watch
2. Press the main and bottom button about 15 seconds "asus logo and reboot bootloader message apears" then a green android with a "!" symbol appears.
3. swipe on the screen
4. a bootloader menu appears, then swipe up or down until "Clear cache" is selected, then swipe right.
5. after is done swipe to select "reboot to sytem" swipe right and you're done.
Many problems fixed even the google assistant lag.
Click to expand...
Click to collapse
I did this too. Helped with a lot of the lag issues
I've tried this and still having terrible battery after wear 2.0 upgrade. I can barely make it through a day.
c_86 said:
I did this too. Helped with a lot of the lag issues
Click to expand...
Click to collapse
I recommend doing what @artur777 explains bellow, it fixed some of the issues for me, to the point where I'll no longer go back to AW1.5, even so, some bugs persist and won't be solved by the factory reset.
Hi Everyone,
I highly recommend doing a factory reset (see my post from 2017/07/24). It solved many problems for me and the watch OS works now like brand new! Give it a try and maybe it will do the trick for some of you too. It will definitely not make things worse, I think.
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
Good luck to everyone!
When i press the do not disturb option the phone does not turn silent where in 1.5 it used to make it silent...any suggestion?
One more Bug
Reminders notification, marked as complet, causing not to be seen in watch or phone. In some exceptions when there is a bad comunication with phone the reminder stay a few seconds.
Google is aware of this bug, and they are working on it with a promise to fix it soon with an update to their google app. (Working right in wear 1.5).
By the way many bugs listed, happen to me, but were fixed with a factory reset in watch, unpair and erase (forget any bluetooth reference) and clear dalvik cache in phone.
Some things doesnt improve immediately like google now or battery.
But I have to say that I own a zenwatch 2 too. Recently updated to wear 2.0 and it works better maybe in every task by example google now, speed downloading apps and battery so far (today from 8:15 to 22:05 65 % available, screen always on brightness level 3, 21 notifications and 1 hour monitoring google fit activities, 3 apps updated (13 MB))
So I think Asus need to put attention on whats going on.
I will make a comparison video in 2 days. Zenwatch 2 vs. Zenwatch 3 both android wear 2.0
Have a good time
My watch is not updating the day and date on the watchface unless I change watchfaces or reset the watch. I.E: It's saturday and it shows Friday. It will keep showing Friday for days unless I change watchfaces or reset.
Does anyone else have this problem as well?
battery drain formost!
my battery drains very fast. Faster than aw 1.5
---------- Post added at 02:52 PM ---------- Previous post was at 02:49 PM ----------
battery drain totally unacceptable in AW 2.0
MK24ever said:
Bugs I noticed so far, please check if you can reproduce these yourself and let us know yours so we make a list. This is a thread I started on Asus forums and it might help ppl here to to iron some of these out.
1- After a call (accepted or not) the blue MIC image stays on the watch even after the call has ended (this happened on AW 1.5 already) - Multiple reports
2 - Watch vibrates non-stop during a call, even if you picked the call allready on the phone, the watch will start vibrating with no reason. - Multiple reports - SUPER ANNOYING!!!
3 - Battery drains much faster, with same usage I end a day with 30% on AW 2.0 instead of 65 to 70% on AW 1.5 - Multiple reports
4 - When not trough Wifi the "ok Google" command gives an error saying Google is out of reach, restarting phone fixes it, but if connection of phone and watch is broken, the "OK Google" voice command (or long-pressing the main button) won't work again, nor will other apps like the App store - Multiple reports
5 - if I pick one phone number with the "text message' icon, the watch does not go into listening mode to get the text content. Instead it keep on loading with the loading icon and no message can be sent out. However if I use "OK Google" command instead of go thru the Contact app I can send text messages - One report
6 - Turning theater mode on seems to break the alarm. Thankfully the alarm will still go off, but the screen becomes unresponsive. Clicking dismiss or snooze won't work. Restart of watch is needed. Only happens when the watch is in theater mode. - One report
7 - Huge delay when phone receives a call to when watch shoes that call. - Multiple reports.
8 - Dowload speed on watch is most of the times terrible slow - Multiple reports
9 - "Ok Google" actions takes much longer to activate than on previous version - Multiple reports
10 - WhatsApp-ing someone is impossible it keeps asking "to whom?" indefinitely. - One report
11 - Pairing seems to be having problems - One report
12 - UI losing frames - One report
13 - Keyboard missing some symbols - Multiple reports
Click to expand...
Click to collapse
Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
I have seen some of these issues on my watch running AW 2.0.
The delay with the calls is the most annoying one. Also if u have wrist gestures on and u turn your wrist when the Call Ui is up, the gestures removes the notifcation and u have to answer call on phone.
I experience another bug. I have a pattern password set on my watch and I placed watch in Eco mode. After the watch is locked in Eco mode, the screen is unresponsive to enter the pattern and none of the buttons work. A restart is neccesary.
Also. I have disabled Smart replies, yet whenever i go in whatsapp chats there are atleast 5 smart reply otions.
hi all, just got this watch, so far so good. only problem is that my watch does NOT notify me when I have an incoming call - except if I set the watch to play voice on incoming call. I'd rather not do this, just the straight up notification. does anyone know how I can adjust this? thanks!
---------- Post added at 08:57 PM ---------- Previous post was at 08:38 PM ----------
jco23 said:
hi all, just got this watch, so far so good. only problem is that my watch does NOT notify me when I have an incoming call - except if I set the watch to play voice on incoming call. I'd rather not do this, just the straight up notification. does anyone know how I can adjust this? thanks!
Click to expand...
Click to collapse
Disregard, it works now.
I had to give full permission to Android Wear.
Sent from my DROID Turbo using XDA-Developers Legacy app
Hello friends!!
Someone has been able to resolve incoming call delay
MK24ever said:
Doing a factory reset will solve many of the issues mentioned, specially the battery drain, I suggest you to do a factory reset and do the initial setup, then leave the watch on charge overnight, the next day restart both your phone and your watch (don't take the watch of the charger yet), wait 20 minutes and then unplug the watch from the wall and just use it as usual, you should see a huge battery improvement. I did.
Click to expand...
Click to collapse
What do you recommend to do factory restoration ?; only "clear data" or "Factory reset", help me pls
Davis26 said:
What do you recommend to do factory restoration ?; only "clear data" or "Factory reset", help me pls
Click to expand...
Click to collapse
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
MK24ever said:
You can restore your watch OS to the factory settings either on your watch or on your phone through the Android Wear app:
On the watch:
Settings -> System -> Disconnect & reset
On the Android Wear app (phone):
Settings -> tap ASUS ZenWatch 3 under Device settings -> UNPAIR WATCH (at the bottom of the screen)
The process of resetting your watch will take a while until your watch is ready to be paired with your phone again. In my case it took about 15 minutes, so don't panic if it takes too long.
Mind that unpairing your watch from your phone will reset it to the factory settings and delete all the apps and settings you had configured on your watch. The fatory reset will NOT roll your watch OS back to AW1.5 though, but it will flash the AW2.0 to it's original state as if it were freshly installed on a brand new device.
Once the watch OS has been successfully restored (you should see this on the screen) you will need to pair your watch with your phone again through the Android Wear app and re-install all the apps and set the settings up to your liking and preference.
Click to expand...
Click to collapse
I appreciate your help, do not recommend doing it from the boot loader?
Again thank you