Related
So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
_MetalHead_ said:
So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
Click to expand...
Click to collapse
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
username4this said:
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
Click to expand...
Click to collapse
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
_MetalHead_ said:
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
Click to expand...
Click to collapse
Obvious question here but have you tried a factory reset?
username4this said:
Obvious question here but have you tried a factory reset?
Click to expand...
Click to collapse
I'm going to tomorrow if it does it again tonight. But the tablet is only a few days old and I already did a factory reset before I set it up initially.
Ok it just did it again right in front of my face. It didn't just go black in the middle of use, I picked it up to use it and before I could do anything it powered down, but did so as if I had deliberately done it. Meaning, the Power Off pop up was on the screen and it said "shutting off" the same way it does when you turn it off manually. That would lead me to believe it would be a software bug as opposed to a hardware one... am I correct in that assumption? Or can some hardware defect actually trigger the normal power down sequence?
I'm currently still running 4.4 but I've read horror stories of 5.0 and above being really buggy and not pushing notifications anymore and random disconnects. Has that been fixed or should I stay with 4.4?
It's a good update. No issues that I have had except that sometimes I set my notifications to none on accident. No performance or reliability issues.
I may consider it then. Did you notice any increase in battery life?
flamestang977 said:
I may consider it then. Did you notice any increase in battery life?
Click to expand...
Click to collapse
Yes, it's pretty massively better. I didn't have mine for very long prior to the 5 update (we're on 5.0.2 on the watch now), but I would definitely go ahead and update it.
I have no problem/issue after updating.
I did the update and am very pleased. The overall experience is better plus better battery life.
Same as everyone else
I highly recommend the update to 5:good:
We updated my wife's watch to Lollipop shortly after we took it out of the box. I like the Lollipop interface better and she has had no problems with it.
You can update to Lollipop. It is advance version and you will feel the power of this updated version.
Here is a video on how to update your Zen Watch.
https://www.youtube.com/watch?v=3Evc60gx8ng
Update 5.1.1 dont work command voice
Hello, the thing is that I buyed this smartswatch; the watch did the update for OTA 5.1.1 , and the command voice doesnt work.
Do you know what can I do?
Thanks in advance
The first thing I would do is a factory reset of the watch.
Willber G said:
The first thing I would do is a factory reset of the watch.
Click to expand...
Click to collapse
Yes I did it several times , but still doesnt work.
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Anyone?
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
frellingfrakker said:
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Did that 3-4 times. Today though it seems more stable.
Looks like Android Wear keeps crashing. That's the cause of all this, even after several resets.
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
Others on 12.1 have not had these issues.
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I haven't gotten Wear 5.1.1 yet unfortunately. Hopefully soon. 5.0.2 is BUGGY! Especially with battery drain during app sync.
i'm having the same issue here running android wear 5 . and cm12.
6 reset so far today . it keep disconnecting and then after on the phone it says connecting... which does not goes away until you reset the watch .
It seems to be a software issue . Android wear is still buggy
karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
karcher01 said:
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
Click to expand...
Click to collapse
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Moto 360 5.0.2
agentfazexx said:
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Click to expand...
Click to collapse
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
dvrose said:
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
Click to expand...
Click to collapse
It should eventually stop. It did it for me after posting this for hours after resetting.
agentfazexx said:
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Click to expand...
Click to collapse
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way that CM12 and CM12.1 handles low energy bluetooth devices. Try another rom.
TheSt33v said:
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way the CM12 and CM12.1 handle low energy bluetooth devices. Try another rom.
Click to expand...
Click to collapse
I got flamed in the thread for blaming the ROM.
agentfazexx said:
I got flamed in the thread for blaming the ROM.
Click to expand...
Click to collapse
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
TheSt33v said:
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
Click to expand...
Click to collapse
Whenever I blame anything on CM that worked fine on stock, they all flame me.
Those that had this issue.. Were you on CM or not?
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
This happens to me on my stock Nexus 5, so I doubt it's a ROM issue. Most likely it's an issue with the firmware on the 360, or maybe the hardware. Hopefully 5.1.1 comes before my 30 days is up so I can decide whether or not to keep the 360, kind of sick of resetting the watch.
I upgraded to Nougat yesterday, currently facing many stability issues. Any help would be appreciated on the below problems.
* Sound is unstable, screen lock does not produce any sound
* Incoming calls are often silent, no sound comes out for some reason
* HTC Live Wallpapers disappeared, I cannot locate them
* Double tap to wake problem persists, I had this problem on 6 and still cannot fix it despite many attempts including sensors, wipe clean and 3 hard reset attempts // I had this issue when I purchased my phone back in September. After many trial and errors it somehow worked on its own. Then I got a problem on my screen and took it to the HTC Service. They told me they replaced the screen and did a software update and my DT2W no longer worked
Also missing the live wallpapers over here.
NFc is working for you? Reading any NFC tag?
sloaxleak said:
NFc is working for you? Reading any NFC tag?
Click to expand...
Click to collapse
Nfc is not working either
No live wallpapers either from UK Nougat update but not encountered stability issues yet.
My Xperia keyboard was playing up but reinstalled and seems to be OK now.
Are you guys on the latest 2.41.xxx update?
comstockload said:
Are you guys on the latest 2.41.xxx update?
Click to expand...
Click to collapse
Yes, the update has brought many challenges though
cengizbey said:
Yes, the update has brought many challenges though
Click to expand...
Click to collapse
I guess that's why there's a new firmware 2.41.401.4 leaked. Would explain why they halted the Roll-Out of 2.41.401.3, and seems they already working on a fix.
Sent from my htc_pmeuhl using XDA Labs
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
cengizbey said:
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
Click to expand...
Click to collapse
My HTC 10 is an unlocked US version and it seems pretty stable. After initial roll out of Android 7 on Nov 25th, we then got 2 updates(Dec and Jan) which contained bug fixes and security patches.
I guess my #htc10 has hardware issues out of the box
After the UK Nougat update my Sandisk SD card is not being recognised as external storage. Was ok before the update. I've removed & reinserted a couple of times, still no joy. Anyone experienced this?
Sent from my HTC 10 using Tapatalk
I had the same problem. I had to remove it and reinsert into the phone.
Hey guys,
None of the issues above I ran into....Has OP tried a factory reset? Always recommended to Android devices after a big version upgrade.
Speaking of factory reset, well, I did it, and I have some other issues :
1. Camera in Pro mode, under long exposure duration, the image quality drops significantly...I am an photography amateur, so I know what I am talking about.
2. Sometimes the phone app does not recognize saved contacts. (It seems that this would be solved with 2.41.401.4)
3. Battery drains...much quicker than 1.95...before I can get 5h or + screen on time, now barely passes 4h.
I've also noticed a batterydrain. Although I've done a fresh install. Yesterday I did a complete wipe again without backup recovery. Battery seems stable now.
Since the OTA Nougat update i've had issues with instagram videos not playing whilst pictures work fine (on both 4g and wifi).
Also gmail no longer syncs automatically and i have to manually refresh to get mail.
Wiping cache partition and wiping app cache/ reinstalling the apps didn't work. I do feel like the update has somehow caused this as it was fine before.
Anyone else having these issues?
To comment on issues others have been having, my battery drain feels normal. And I have always has issues with gestures and double tap to wake not working
Unlocked USA 2.41.617.3 is stable here
Unlocked USA 2.41.617.3 is stable here. It brought the January security patch and also fixed all of my battery drain issues I had since the September, 2016 Android 6.1 update. I lost 2-day battery life in September, 2016.
I am finally back to 2-day battery with doze acting normally since January, 2017 update.
No extra updates or fixes yet for us in the UK. Also noticing apps will won't auto update correctly now. Getting a google play is not responding message. HTC need to sort this out asap
cengizbey said:
Nfc is not working either
Click to expand...
Click to collapse
Got it... is it a known issue?
Same, no nfc either
Hello, I just received MIUI 11.0.2.0 based on Android 10 Stable, so I'm wondering if it is safe to update, I'm afraid that after updating the battery will drain faster as it usually happens, do you have any info about this?
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
Update just showed up, is it worth? any audio improvement?
Update and don't be afraid ...?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
Click to expand...
Click to collapse
Well I have worse battery live on Android 10.
Something keeps phone awake and drain battery.
I have about 1 or 2 hours less SOT.
Looking for solution. ?
I ended up upgrading, at first, my phone was lagging when scrolling in any app, and the battery was somehow draining a bit faster but I managed to fix it.
Try this if you have a related problem.
-Go into developer settings
-Scroll almost to the button
-Disable MIUI optimization
-Reboot
-Enable MIUI optimization
-Reboot
Also, the permission of most of my apps got lost, like access to the microphone, storage, phone... so I had to re-enable them manually because they were "blocked".
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Kev23 said:
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Click to expand...
Click to collapse
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
littleleaf said:
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
Click to expand...
Click to collapse
Today I discovered that settings changed in the developer menu are not persistent and don't survive to a phone reboot. So every time I get in the car I've to repeat settings.
This is quite annoying, any solutions other than waiting for another software update?
Another alternative would be changing the car, but it's more expensive than buying another mobile phone.
Danchibald said:
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
Click to expand...
Click to collapse
Tried this, still seeing high Android OS drain
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
Think you are right on the battery. Mine has settled down and not as good as before
I think after few cycles of charging it will be better...
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
ScanaX said:
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
Click to expand...
Click to collapse
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Ever since I updated to 11.0.3.0PGGEUXM I've been unable to use one of my wallet apps (bbva wallet), and am afraid something else breaks if I update; has anyone from Mexico updated and been able to use it again, along with citibanamex pay?
littleleaf said:
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Click to expand...
Click to collapse
I'm opening a ticket reporting this issue with my phone...
I hope It will work
After 20 days I decided to downgrade back to MIUI V11.0.3.0PGGEUXM based on android 9, the only thing I liked about android 10 was the dynamic MAC address but it didn't compensate the high battery drain from the Android System, with up to 9-10 hours of CPU usage and about 6-6:30 hours of Screen-on time. I will test how many hours of SOT I have now.