Related
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
zllovesuki said:
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
Click to expand...
Click to collapse
I dont get it.....???????
Sent From Droid Ultra
caseyk621 said:
i dont get it.....???????
Sent from droid ultra
Click to expand...
Click to collapse
battery sucks for some reasons, solutions please?
zllovesuki said:
battery sucks for some reasons, solutions please?
Click to expand...
Click to collapse
Assuming you started from %100?
I found after some app updates that my play services cache was rather high and I had some unnusual battery drain. So I went to manage apps and cleared the cache on play services. Seemed to correct itself after that.
If you just got it then cycle it a couple times, it gets better after a week or so.
If you've had it awhile then a rogue app is causing it. BetterBatteryStats or gsam from play store will do better at helping figure it out.
5hrs 36mins SOT
Sent from my XT1080
KitKat and Jelly Bean have both had battery drains related to location services. I'm keeping location turned off until the next release. I'm not happy about it, but it does seem to make a difference.
cpurick said:
KitKat and Jelly Bean have both had battery drains related to location services. I'm keeping location turned off until the next release. I'm not happy about it, but it does seem to make a difference.
Click to expand...
Click to collapse
I don't have an issue with location services unless I have google now enabled then it is a battery hog.
I had a massive battery drain because of WiFi even when off. Go to WiFi settings advanced turn off scanning always on.
you need to use better battery stats. just research xda for it. and follow the posts directions. you will find out what exactly is eating your battery.
zllovesuki said:
Well, this is not why I bought this phone for. SOT is only 25 minutes, and it is worse than my Xperia Z Ultra.
Click to expand...
Click to collapse
Battery drain has been a relatively common experience after the KitKat 4.4 update. I have a Droid Mini, not a Maxx, but I've been seeing a lot of reports for all three of last years Droid line (Mini, Ultra and Maxx). Troubleshooting battery life is typically done through looking at events called wakelocks. Wakelocks are created by apps on your phone to prevent it from going into "deep sleep"--basically, they allow the CPU to stay on when the screen on your phone seems off. BetterBatteryStats or WakelockDetector are two apps that can be used to gain a little more insight into what wakelocks you are experiencing and what might be causing them.
However, wakelocks are broken down into two categories--those run by the Android kernel itself (kernal wakelocks) and those created by apps running in the background (partial wakelocks). Unfortunately, the 4.4 update made it impossible to view the partial wakelocks directly without root permissions. If you did as I did and naively updated to 4.4 without root, you won't be able to root your phone (as of now) to see the partial wakelocks. Instead, the wakelocks will show up under the kernal wakelocks that can be viewed--but instead of an app by app breakdown, they are visible only in the aggregate, so figuring out which app in particular is causing your problem can be a real trick.
One way to do so is to look at the apps running in the background of under the "Apps">"Running" in settings and see which apps you have actually been using and are supposed to appear and which apps are not. Then select the apps that you didn't start and force close them in sequence, checking Wakelock Detector or BetterBatteryStats after each to see if they have fixed your issue at all. The best way IMHO to see if they had an immediate effect is to look for increases in the "Deep Sleep" stat--if the app had been keeping your phone awake, and you force closed it, the Deep Sleep time should go up after you shut off your phone.
All that being said, troubleshooting is a real *****. There is an abundance of non-app-related issues with 4.4, or so it would appear. I have seen posts attributing fixes to turning location services to "GPS only". Others recommend clearing the Google Play Services cache in the Apps menu, clearing the cache in phone more generally, and using every other more conventional battery conservation trick in the book. Still others reported the only fix as a factor reset. These things had little to no benefit to me--although I never had to resort to a factory reset since I found a fix this morning. For me, all it took was going into Wifi>Advanced>Wi-Fi frequency band and changing from "Auto" to the 2.4GHz setting. This seems to have nailed the persistent wakelock issue that had been showing up as "Android OS" under the stock battery life in the settings, which showed up as a kernel wakelock under "suspend_backoff" in BetterBatteryStats. Hope that something out of all of this can help you--I'm immensely frustrated with how poorly my phone performed for the last month after the KitKat upgrade. It appears, however, that the fix I just found has restored my battery life from the 3-6 hours I have been getting lately to 12-14 hours. I'll update in a couple days after I see how things go. Best of luck!
Update, after a real short period of time:
Somehow doing this appears to have broken my Touchless Control. I can't get Google to recognize the "Ok, Google Now" bit, which it had done in the past nearly flawlessly, nor will Google Search transcribe voice searches, period. Going into the Settings>Touchless Control shows Touchless Control to be unchecked, but tapping the button to enable Touchless Control doesn't do anything. The button dims slightly, as if the press is registered, but the box doesn't check and the Voice Search and continues not to work. Interestingly, putting the Wifi back on "Auto" as opposed to 2.4GHz doesn't seem to fix this; rebooting into Safe Mode makes it work fine though. I've tried uninstalling and reinstalling my Touchless Control app, but I'm hoping this isn't a persistent issue for me. Ugh. In any case, I'll take battery life over Touchless Control for the time being.
EDIT: Voice input doesn't work anywhere on my phone--I can't press the microphone button on the keyboard and speak, for example, to dictate a text message. Potentially this is unrelated to the battery life issue, but I'm going to do some more digging and see what I can find.
Jumnhy said:
Update, after a real short period of time:
Somehow doing this appears to have broken my Touchless Control. I can't get Google to recognize the "Ok, Google Now" bit, which it had done in the past nearly flawlessly, nor will Google Search transcribe voice searches, period. Going into the Settings>Touchless Control shows Touchless Control to be unchecked, but tapping the button to enable Touchless Control doesn't do anything. The button dims slightly, as if the press is registered, but the box doesn't check and the Voice Search and continues not to work. Interestingly, putting the Wifi back on "Auto" as opposed to 2.4GHz doesn't seem to fix this; rebooting into Safe Mode makes it work fine though. I've tried uninstalling and reinstalling my Touchless Control app, but I'm hoping this isn't a persistent issue for me. Ugh. In any case, I'll take battery life over Touchless Control for the time being.
EDIT: Voice input doesn't work anywhere on my phone--I can't press the microphone button on the keyboard and speak, for example, to dictate a text message. Potentially this is unrelated to the battery life issue, but I'm going to do some more digging and see what I can find.
Click to expand...
Click to collapse
What do you have checked under settings, language and input?
Do you have any third party keyboards installed?
Have you done or considered doing a factory data reset?
Sent from my Nexus 7 using Tapatalk
jfriend33 said:
What do you have checked under settings, language and input?
Do you have any third party keyboards installed?
Have you done or considered doing a factory data reset?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No third party keyboards whatsoever. Up until now I had been really happy with Google's stock keyboard. Under Settings>Language and Input I have Google (English) checked, as well as Google Pinyin Input, and Google voice typing, which is set to English (US).
Been thinking about doing a factory data reset but would like to avoid it if possible because I've been horribly disorganized about curating my contacts across a variety of Google accounts--I know that if I had to, I have all my information backed up, but it'd be a big pain getting it sorted again afterward. I've heard others say that an FDR has fixed the battery all on its own. I don't know if I mentioned, but booting into safe mode restores the voice input functionality.
Got a Droid Mini now myself for a few days, it's at 4.4 and obviously unrooted and there apparently is no hope for the Chinese unlock nowadays either, sadly, so that means doing whatever possible to ensure the best battery life on mine as well. I hadn't considered forcing the 2.4 GHz Wi-Fi operation so I set it that way just now and then immediately attempted to use touchless control and it's working fine for mine with only that one change from Auto to 2.4 made.
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
On complete idle it does lose about 1.2% per hour (with Wi-Fi off) but I might redo that test now with the 2.4 GHz manual setting and see if anything is changed.
It's not anywhere near the battery life of the Droid MAXX I had and sold, obviously, but so far it's doing ok. I ordered an Incipio Ghost 100 Qi-charging base a few days ago, hopefully it'll be here by the weekend so I can stop wearing and tearing the microUSB port.
Will see what happens...
br0adband said:
Got a Droid Mini now myself for a few days, it's at 4.4 and obviously unrooted and there apparently is no hope for the Chinese unlock nowadays either, sadly, so that means doing whatever possible to ensure the best battery life on mine as well. I hadn't considered forcing the 2.4 GHz Wi-Fi operation so I set it that way just now and then immediately attempted to use touchless control and it's working fine for mine with only that one change from Auto to 2.4 made.
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
On complete idle it does lose about 1.2% per hour (with Wi-Fi off) but I might redo that test now with the 2.4 GHz manual setting and see if anything is changed.
It's not anywhere near the battery life of the Droid MAXX I had and sold, obviously, but so far it's doing ok. I ordered an Incipio Ghost 100 Qi-charging base a few days ago, hopefully it'll be here by the weekend so I can stop wearing and tearing the microUSB port.
Will see what happens...
Click to expand...
Click to collapse
Glad to know that the Wi-Fi settings aren't the likely culprit of my ****ed voice input. I tried the Snapdragon BatteryGuru for a while--for me the effect was negligible over a period of about two weeks. What was the wakelock keeping your phone up?
Jumnhy said:
Glad to know that the Wi-Fi settings aren't the likely culprit of my ****ed voice input. I tried the Snapdragon BatteryGuru for a while--for me the effect was negligible over a period of about two weeks. What was the wakelock keeping your phone up?
Click to expand...
Click to collapse
I have no idea, haven't bothered to look at the wakelocks presently. I got used to using TricksterMod to monitor everything but of course I can't do anything with it because of no root access.
Really wish a miracle would come along at some point, we could use a working root definitely.
Hell, we could use 4.4.2 AND a working root to be honest, hopefully whenever 4.4.2 comes along it'll fix a lot of crap in 4.4 that Motorola and Verizon just broke for whatever reason. Bleh.
Come on, Motorola, make it happen.
<and offer the option for us end users to purchase an unlock code direct from you, too...>
br0adband said:
I have no idea, haven't bothered to look at the wakelocks presently. I got used to using TricksterMod to monitor everything but of course I can't do anything with it because of no root access.
Really wish a miracle would come along at some point, we could use a working root definitely.
Hell, we could use 4.4.2 AND a working root to be honest, hopefully whenever 4.4.2 comes along it'll fix a lot of crap in 4.4 that Motorola and Verizon just broke for whatever reason. Bleh.
Come on, Motorola, make it happen.
<and offer the option for us end users to purchase an unlock code direct from you, too...>
Click to expand...
Click to collapse
Yeah, I'm with you there. I'm hoping we get 4.4.2 by mid/end of the summer, and in the meantime sitting here kicking myself for not jumping on top of buying an unlock code while they were available. $40 would have been cheap compared to putting up with this broken ****. I've been hugely disappointed in Motorola for failing to address the bugs in 4.4 in any sort of official capacity for the Droid lineup. It's funny--I didn't really care about having root so long as my phone was working. But trying to fix everything that has gone wrong has gotten my just drooling for root. Hopefully we get it eventually, and I know that the next phone I buy will DEFINITELY have an unlocked bootloader. Ugh.
I swore I'd never purchase another Motorola product and I suppose technically I haven't meaning I will never directly buy one from Motorola or from a carrier with their products (not even Google) - I got this Droid Mini for a decent price from someone off craigslist after selling the Droid MAXX for a very nice profit indeed so, in the long run I got the Droid MAXX free of charge to begin with, made profit from that then bought the Mini which is basically the same device in a smaller package more or less and still no money has gone directly to Motorola (or Verizon for that matter since I use T-Mobile just fine).
Gave up on Motorola when they pooched all of us Atrix and Photon owners so to hell with Motorola for that fiasco. Now it seems like they're doing it again by being slow and stupid for whatever reason.
I cannot for the life of me understand why it takes these companies so damned long to release a fix or update for a device - consider that the Moto X, the Droid Ultra, the Droid MAXX, and the Droid Mini all have the same X8 custom chipset and are basically the same devices in almost every respect and yet it still just doesn't get done like it should.
It's pathetic but I'm ranting now... my intolerance for stupid people (and companies) is well known so, Motorola, I can see not much has changed and so neither will my opinion.
I like the Droid Mini, it's a nice device, works fine given the limitations (no root yet, no 4.4.2) and the rather meager 2000 mAh battery. I could sell this I suppose, get me another Atrix HD (and still be mostly locked down I guess) but then slap that RAZR MAXX battery in it and get near-Droid MAXX battery life once again.
Nah, I think I'll keep the Mini unless someone makes me another offer I can't refuse. I see them listed on craigslist for rather low prices - exactly why I got this one a few days ago - and I honestly think there are a lot of people that just don't realize this is basically a "Moto X Jr" model that does effectively the same things including Active Display and "OK Google Now" touchless control.
You'd think most consumers were stupid or something for not noticing just what a fine device this Mini actually is. </sarcasm>
br0adband said:
I was using GSam Battery Monitor to get some idea of what's going on with this device but recently decided to just give the Snapdragon BatteryGuru a shot and see what happens (got another 1.5 days of monitoring before it does whatever it's supposed to do).
Click to expand...
Click to collapse
I tried that a week or so ago. I didn't let it control WiFi for me, but otherwise let it do its thing. (I also wouldn't let it turn off GMail syncing unless the phone was on - having GMail come to me close to push is one of the reasons I carry the thing with me.) It didn't make a damned bit of difference for me; it's off the phone now.
I've done the 2.4 GHz only thing. We'll see if it helps.
My ultra was doing the same thing. I back up my phone and factory reset it. For the first couple days I was killing the battery quickly from setting up my phone again and with in a week or so my battery life seemed to come back as it was in 4.2.
Sent from my XT1080 using Tapatalk
I was very excited to see this:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
So, I pushed ahead thinking that Lollipop has already been in the wild long enough, surely the initial kinks like WiFi drops and battery hogging have been resolved. No such luck, and after doing it, it looks like I'm going to have to do this:
http://forum.xda-developers.com/showthread.php?t=2784880
Lollipop is horrible. My phone no longer does one of the most basic things that's been around since the G1: Go (the F) to sleep! Seriously?!?!
Here are my other problems:
-Phone doesn't sleep on its own if timeout set for longer than 30 seconds (and even then, it's not reliable)
-WiFi doesn't reconnect after sleep (when sleep even happens, which is only when I push the button to force it). I have to toggle WiFi off/on to reconnect.
-Battery drain is pretty bad. My first month with the S5 had me barely even thinking about charging. Now, with Lollipop, I feel like I'm back on my old HTC MyTouch!
-The silly way they implemented the lockscreen. Here's my problem: I can ONLY use Settings > Sound and Notification > While locked with the option "Do not show notifications". Why? Any other setting blocks the Owner Information (Settings > Lock screen > Owner Information). If I don't, and if I'm unfortunate enough to have lost my phone, yet fortunate enough to have it found by a good samaritan, I better hope I haven't miss any calls or received any messages in the meantime. This one REALLY GRINDS MY GEARS because it's a horribly-implemented Feature ... at least the others are unintended bugs, but somebody had to give this one the green light.
-I can't adjust the icon sizes anymore. There used to be a choice of large or small icons.
-Oh, and for some bonehead reason, Samsung decided their stock ROM wouldn't have the Lollipop built-in flashlight icon.
-Another intentional feature that I can't disable: the phone keeps a history of recent activity that persists through reboots. YUCK! Why can I not disable this?!?! Again, another bonehead call that somebody had to green-light, without even considering the possibility that I might want to turn it off!
-All the UI "polishing" and improvements don't mean a thing to me, I want it to work.
I found all of the above in less than 24 hours on Lollipop! I might lose my s**t entirely if I keep it for much longer.
Here is my take on why:
Google and Apple are in a heated race to the top. They wrongly assume that what will set each apart from one another is almost entirely dependent on what a few bloggers say about some hot new feature. The paradigm appears to be something like: "Who cares if millions of loyal subscribers lose functionality when we want 100 people to have this one obscure and half-baked feature?"
Latest != Greatest
-----
EDIT:
I've had a change of heart on this. It's not too bad, I just needed to adjust a few settings and live with the other issues.
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Tldnr
Don't start a thread just to complain
Lmfao when I saw that link and clicked it, I actually had that same thread opened moments before opening this thread because I, too, am having to go back to KitKat. I laughed for a good 20 seconds. Lollipop is freaking terrible at the moment. Zero customization and Google + Samsung are forcing too much garbage on us without giving any bit of customization.
mygraine said:
I too do not like the lolli. Bad battery life, and for some reason the Heart rate monitor led turns on whenever anything is within a half inch of it. I just can't figure that out, but it sucks the battery like a red led vampire!
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Heart rate monitor thing was fixed in OC4 I think, but if it still goes off a factory reset will fix it.
Agree
OP, I agree with you. It probably is the first version without the definitely improvement overall for users. It is risky to upgrade and troublesome if it didn't work out well on your devices. Wish Android 5.1 could be better than Kitkat overall.
I have absolutely no problems with the lollipop. I always had it stock from the start and just let the OTAs take over on their own. Have you tried even rebooting into recovery and wipe cache? Even though it's not a custom recovery you can still do that, also even when you dirty flash nightlies that's something that's good practice. My wife's phone had similar issues that I wasn't experiencing, until I did that to her phone and now she's having no problems. Now the general annoyances of how Samsung implemented ****, I understand, it's stupid with not having native flashlight, tethering is annoying having to use foxfi, and the lockscreen.. bleh. But other than that, everything is actually working like it is supposed to
Chiming in, Yes it's bad.
I have two lines with Verizon, both with S5 phones on them. Great device, its actually the first Android phone I've had that I did not do anything with beyond the out of the box experience. That changed when Lollipop was pushed via OTA, the most prominent issue I experienced on both of my S5s is general responsiveness issues, simple things like switching apps or launching apps sometimes would leave me with a white screen for between 5-10 seconds, an eternity especially when the device was lighting fast on 4.4.4 Kitkat. I followed every suggestion from wiping the device in Android, Wiping in recovery, wiping cache, all of these with only marginal improvements. It really is a shame that Google / Samsung did not do a bit better quality assurance on this build before it was pushed out to carriers and ultimately peoples devices. It says something that other carriers skipped 5.0 and that very rapidly 5.1 surfaced on Newer devices / Nexus devices.
As of last night both of my phones are Odin'd back to 4.4.4 and its like having a brand new phone. Sure, there might not be as much polish, but there are no features I will die without having. The only one that I can say I do miss is the feature where the device will disable the lock screen when your smart watch or home WiFi is connected.
Here's to hoping that Google eventually gets Android 5 right in the optimization department and that Samsung picks it up for the S5, and that Verizon gets it ready for OTA before I am ready to move on to a new device. Not interested in the S6 at all for its sealed nature for storage and battery, but that's for another thread on a different day.
-Nate
I Have to agree. I've given it several chances to perform to expectations but it just fails.... ( insert sad puppy face here ) no matter what I have tried it just under-performs and the biggest thing is the horrible battery life. Sooooo yeah like most of the other commentators in this thread, I'm moving back to 4.4.4......
Unfortunately/fortunately, I have found most of my battery issues were solved with a factory reset. I'm more frustrated that Samsung seems to having issues with Android Auto.
ldeveraux said:
Tldnr
Don't start a thread just to complain
Click to expand...
Click to collapse
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
CaptainRewind said:
Observations, not complaints. Getting these points out in the open is an essential stepping stone to getting them fixed. Maybe, just maybe, a Producteer or architect at Google has read this by now so they know what to improve next time. Problems cannot be solved until they are defined.
---
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
ldeveraux said:
Yeah, go start a petition, just like the bootloader guys, see how far it got them? No one from google reads your complaint threads and regrets their work...
Click to expand...
Click to collapse
Yeah, I guess that was wishful thinking.
In any case, it seems this thread was a complete waste of time. It made me feel better at the time, but looking back on it and the purpose of this site, it doesn't add any value or help anyone modify their phone. Not only that, one of my primary reasons for the OP was the screen lock issues which turned out to be an app, not the Android version.
So, I stand corrected. Live and learn. Enough said.
My wife would never let me root her phone ever. After this update either I find a way to go back a few with root or it goes against the wall. Looks like I have to start reading and figure out how to do this.
Lol I love how you described it. Sometimes you have to vent. Lol
CaptainRewind said:
UPDATE:
The issue with the screen not sleeping was actually related to the "Show CPU Usage" setting in the app "OS Monitor". I've used that for years on previous Android version with no problems. In Lollipop, it must be disabled.
Click to expand...
Click to collapse
Care to share where this app is?
Sent from my SM-G900V using XDA Free mobile app
dk-v1 said:
Care to share where this app is?
Click to expand...
Click to collapse
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
CaptainRewind said:
This is the one:
https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en
It's a great app, but something about it staying active in the Notification Bar keeps the screen awake. I still use the app, just can't keep the notification active in Lollipop.
And in case it isn't obvious, even though I still have my concerns about Lollipop, I never did go about the procedure of downgrading. It looks like a risky procedure, and I don't want to trip Knox, or worse, have a brick.
Click to expand...
Click to collapse
Ok, so it's not a stock app. I am still having poor battery life and overheating issues.
Sent from my SM-G900V using XDA Free mobile app
Hi,
Coming from a Moto Z and before that a 6P.
Ok... I didn't intend to hate this phone but... Why are notifications broken? Why dont PocketCasts playback controls work?
I know this is "1 aspect" but to me notifications are vital and i simply don't understand this phone.
- i receive a notification and screen lights up (i set that per app)
- but then I unlock phone
- notifications still in notification shade. I lock device.
- they are no longer on lock screen
Why?
That's not how any other device i have owned worked?
And lock screen music playback is... A disaster?
I consider this phone basically unusable... Yet reviews never mentioned this. Am I alone?
I agree with you, mostly. I'm coming from a Nexus 6P (and many Nexi before that since the One), so I'm used to the plain Vanilla and love it. I was able to rectify some of the notification issues by enabling banner and lockscreen notifications from the Settings >> Notification & Status Bar >> Notification Management area. It doesn't fix everything, and at times (especially the beginning) it was very frustrating. I have it for 5 days now and am at a point where I think it's usable and am waiting for LineageOS to come out with a vanilla-ish version.
http://lineagerom.com/huawei-mate-9-lineage-nougat-update/
The battery is what drew me to the phone and it doesn't disappoint. I can get about 24 hours and that impresses me.
Thanks, have that set for important apps. Feels like a massive part of Android (notifications) are basically missing. Rest is good/ok/great but.... Just feels like madness that this is acceptable in 2017.
yup, hw software sux. end of. waiting for stock-ed customs
Just you
Sent from my MHA-L29 using Tapatalk
Yea, that's what ended up being the deal breaker for me. I absolutely loved everything else with the phone, but notifications are the baseline of what a phone should be (at least to me), and this phone failed at that miserably. Not being able to reply to a text without unlocking the phone is a no go for 2017. I also kept hearing how battery life was amazing...I never really saw that either considering the size of the battery and a 1080p screen. I've got a Moto Z Play and I can tell you that this is truly amazing battery life. I'm now sitting at 53% with 4:39 sot and been off charger since 9:45a...It's now 1a the following morning. Not putting down Mate 9, as I really did like the rest of the phone...So much so that I'm on here looking to see if they have come out with an update for the glaring problem you guys are discussing. It looks as they Huawei doesn't even acknowledge the issue, so not counting on a fix. Oh well
Sent from my XT1635-02 using Tapatalk
I'm really surprised Huawei get a free pass on this. I read about 10 reviews, saw lots of YouTube videos and I had no idea how this phone handles notifications. I simply don't believe that someone coming from "normal" Android versions wouldn't find this different enough to warrant a huge rant?
Very frustrating. I like so many aspects of this device but the basic things are terrible. Madness.
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Spot on! I'm 700 USD in on this phone. Only thing going for it on my side is the battery (so far) and dual sim as I travel a lot.
The rest is just unacceptable... At the very best. Likely the first and the last Huawei I'll own.
It's not just software that is bad for notifications. The hardware is poor too. The LED is tiny and almost invisible. The vibration is very weak so you can't feel it in your pocket.
This is a great phone underneath, but the little things really spoil it.
Huawei had a great opportunity to take business off Samsung, but they have blown it.
This has put me off Huawei. I'll be trading in the Mate for a Note 8. Or perhaps I won't wait for that. The S8+ is looking good.
Coming from a Nexus 6, the software has it's issues, but overall I like my Mate 9 so much more. Thought I would be missing the stock Android in a daily basis, but I seem to be very happy with my new phone.
-ErrorFile- said:
Coming from a Nexus 6, the software has it's issues, but overall I like my Mate 9 so much more. Thought I would be missing the stock Android in a daily basis, but I seem to be very happy with my new phone.
Click to expand...
Click to collapse
Coming from the disastrous year of Samsungs (s7 Active, s7 Edge, Note 7) Im loving the mate 9. Getting 10 hours of screen on time, notifications havent been an issue at all (Ive had to unlock the phone to reply to a text on every single phone Ive used including iPhone). I prefer the lockscreen stay clean and the led flash when I have something unread. Out of all the phones Ive used this past year, this is the only one Ive kept. Ive got a Moto Z Force sitting on my table thats for sale and once its gone all Ill have left is my iPhone 6s plus and the Mate 9.
wingzfan said:
Coming from the disastrous year of Samsungs (s7 Active, s7 Edge, Note 7) Im loving the mate 9. Getting 10 hours fo screen on time, notifications havent been an issue at all (Ive had to unlock the phone to reply to a text on very single phone Ive used including iPhone). I prefer the lockscreen stay clean and the led flash when I have something unread. Out of all the phones Ive used this past year, this is the only one Ive kept. Ive got a Moto Z Force sitting on my table thats for sale and once its gone all Ill have left is my iPhone 6s plus and the Mate 9.
Click to expand...
Click to collapse
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
RR-99 said:
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
Click to expand...
Click to collapse
I have no issues with the brightness of the led at all, in fact I prefer it to the absurd brightness of the s7 series. My phone is primarily on a desk or table and I havent missied any notifications at all. Also my volume is always on so I hear my phone go off and never really pay attention to the vibration of it but I would say its right on par with my iPhone. Another thing is I use Textra and always have so Ive got the vibration set to "multiple short" and if the phone is for some reason on silent I still hear the vibration when a notification comes in. Honestly I have no complaints about anything with this phone especially now that Ive been able to change out the emojis without root (hate android emojis).
coming from a pixel
i really like the mate 9, the software could do with abit more though.
if it was pure vanilla, this phone would be the end all.
RR-99 said:
Do you find the LED bright enough and the vibration strong enough? If so I have a different phone to yours
Click to expand...
Click to collapse
I use an app called Flash notificationn 2. basically on any missed notifications it keeps flashing the camera and lights up the screen( set every min or so). it works very well. coming from a note 4 i was also tossed. I do love this phone and at 599.00 seems a steal. does it have shortcomings , ya it does. but so does every phone. price to price with the s8+ or note 8 rumored at close to a grand makes this phone a steal. especially considering the list of shortcomings the galaxys 8 will have.
https://play.google.com/store/apps/details?id=com.manzy.flashnotification2&hl=en
admorris said:
Not being able to reply to a text without unlocking the phone is a no go for 2017.
Click to expand...
Click to collapse
That seems like an odd issue to me. All it takes to unlock the phone is touching a sensor. Unless the complaint is about doing it while sitting flat on a surface, then I agree the sensor placement isn't optimal. But if replying to a text without unlocking the phone is important, that's easily solved with a 3rd party text app, like Textra.
I also haven't noticed the issues with notifications in my usage that others have had. But I do agree the notification LED could be brighter, and the vibration stronger.
tommy281 said:
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Click to expand...
Click to collapse
This just doesn't work reliably. Spotify works 60% of the time maybe but PocketCasts about 5%. Totally rubbish.
Really mixed bag of opinions here.
I'm almost wondering if there are multiple software versions showing different behaviour?
The 2 notifications issues i have are :
1. Music playback controls. Dreadful. Seems like some apps whitelisted but even those don't work 100% of the time. PocketCasts (even latest version from 2 days ago) works basically never, meaning i need to unlock phone to pause. A total joke.
2. Notifications. Lock screen shows them once and once only. As soon as i unlock, all notifications are not shown again on lock screen, unlike normal Android.
For those that "don't have issue with the notifications"... Do you see what i see?
tommy281 said:
for lock screen music playback -
settings> then uptop type in notifications> notifications panal> notification managment. then find the app you want to allow on the lockscreen. hope that helps.
Click to expand...
Click to collapse
That doesn't fix the issue...It's a known problem.
Sent from my XT1635-02 using Tapatalk
---------- Post added at 05:41 PM ---------- Previous post was at 05:36 PM ----------
RealEvil said:
Really mixed bag of opinions here.
I'm almost wondering if there are multiple software versions showing different behaviour?
The 2 notifications issues i have are :
1. Music playback controls. Dreadful. Seems like some apps whitelisted but even those don't work 100% of the time. PocketCasts (even latest version from 2 days ago) works basically never, meaning i need to unlock phone to pause. A total joke.
2. Notifications. Lock screen shows them once and once only. As soon as i unlock, all notifications are not shown again on lock screen, unlike normal Android.
For those that "don't have issue with the notifications"... Do you see what i see?
Click to expand...
Click to collapse
I think what you have are two types of people on here...Not two software versions. You have people that have given up on the phone and people who are justifying their purchase...lol
Sent from my XT1635-02 using Tapatalk
https://twitter.com/sarvikas/status/955753890770665472
Get it here :
https://www.nokia.com/en_int/phones/betalabs
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
I have been battering it since installing and i cant make it cough, splutter or hiccup, seems all but finished to me rather than a beta.
Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.
amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .
xterminater07 said:
Do you mind doing a system dump for me? If you need help look up how to do a system dump, but I think you need root and do adb /pull system .
Click to expand...
Click to collapse
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.
aoleg said:
Not quite. I discovered and reported a rather annoying kernel wakelock that doesn't allow CPU deep sleep for hours, causing battery drain.
Click to expand...
Click to collapse
Thats weird, everyone else is reporting better battery life.
amunarjoh said:
Cool. Bought the phone today, and it's already on 8.1. Hoping Nokia will keep up the pace
Click to expand...
Click to collapse
amunarjoh said:
Hi, and thanks for asking. At the moment I am so happy with the barbone Android, that I don't see a reason to root. Maybe at some other point in time...
By the way, it took just a few seconds to enter Nokia beta and download the 8.1.
Click to expand...
Click to collapse
I do not have the phone, I have another phone that uses the same sensors as the Nokia 8, that's why I would like to have the system dump so I can see some information regarding cameras. Or if you can link me to the beta download that would be great. I can try to pull files and info from it.
I haven't noticed any crashes on this beta, but the battery life is definitely worse for me.
This device has no root, so pulling the system will be difficult I think.
MrBelter said:
Thats weird, everyone else is reporting better battery life.
Click to expand...
Click to collapse
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.
If you set animations to 0.5x you can notice the speed improvement more. Though could be placebo. Before 0.5x was more choppy and 8.1 feels smoother.
8.1 is definitely smoother!
The double tap on recent apps (for fast change) are waaay faster and without a single hiccup for me.
Battery have better stand-by with wifi and auto sync on.
Less than 1% per hour! (almost two hours to drain 1%)
Sent from my Nokia 8!
aoleg said:
That's what beta testing is for. "Works on my computer", you know, is not an acceptable excuse for programmers doing paid work. In some circumstances, on some models, in some regions, with some mobile service providers, etc, etc, you get intermittent weird problems that are impossible to catch during the "closed" beta testing phase. On my phone, there is almost no CPU deep sleep due to some kernel wakelock (I cannot get more details than this without root access, and there's no root for this model). After 3 days on 8.1 beta, I rolled back to 8.0 stable; no wakelock issues whatsoever. Of course, I submitted a comprehensive bug report before rolling back, so hopefully HMD catches and squashes this bug.
Click to expand...
Click to collapse
Wow chill your beans, i am fully aware what beta testing is and i certainly do not need preaching to about it by the likes of you.
I was about to report that the standby times on my phone are also reduced but i don't think i'll bother now, you seem to have it all covered with your comprehensive report.
I observe that when i take my phone out of my pocket it automatically unlocks the screen lock( i put my finger on fp sensor when i take my phone out of my pocket). After that i checked if there is a problem with the light sensor, so i covered it so it couldn't get any light but still unlocked the phone when i used my fp to unlock it. Do you guys have that problem? Also to note that when i am making phone calls light sensor works like normal.
Sent from my TA-1012 using XDA Labs
USB tethering also doesn't seem to be working correctly and causes reboots.
still no ambient display......
Also the pop up when i want to disable the mobile data is frustrating. Is there a way to disable this?
Sent from my TA-1012 using XDA Labs
bluetooht not working
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit
hennieh said:
bluetooht also doesn't seem to be working correctly and causes reboots. when i make calls over carkit
Click to expand...
Click to collapse
I'm using Bluetooth with two different car kits, speaker and headphones. No issues at all. Actually it seems to be using less power than on 8.0.
On 8.0 sometimes I couldn't connect to car kit. On 8.1 this issue seems to be gone.
This is the kind of battery life i am getting now after a few days running the beta, i still think standby times are worse but not shockingly so.
I'm tired of this. It's been 8 days since I got this phone and It's still absolutely unusable in conditions like dimmed room with any source of light (i.e tv or bedside lamp), or mounted in a car used as a satnav, or with lights off in the dark.
Aactually, it can play up at anytime, any day, any night.
It's unbelievable that in 2019 I can't get normally behaving display under controlled conditions. It goes up and down like crazy. Tried to teach this thing by adjusting manually every time hoping for the best but no improvement. It's just totally unreliable and I hope Amazon will accept my return. My first and only journey with this company has ended. I knew I shouldn't go with chinese brand, I knew it. Never ever again.
It's 10pm here, I'm sitting only with a small bed side lamp and whilst writing this post the brightness went up to 1/3 of the scale 3 times for no reason and never went back down where it should be. This makes my eyes bleed. What a joke.
The phone is awesome besides that 1 hiccup I do agree that brightness issue sucks but not to the point you have said.
I hope they fix it.
discodestroyer10 said:
I'm tired of this. It's been 8 days since I got this phone and It's still absolutely unusable in conditions like dimmed room with any source of light (i.e tv or bedside lamp), or mounted in a car used as a satnav, or with lights off in the dark.
Aactually, it can play up at anytime, any day, any night.
It's unbelievable that in 2019 I can't get normally behaving display under controlled conditions. It goes up and down like crazy. Tried to teach this thing by adjusting manually every time hoping for the best but no improvement. It's just totally unreliable and I hope Amazon will accept my return. My first and only journey with this company has ended. I knew I shouldn't go with chinese brand, I knew it. Never ever again.
It's 10pm here, I'm sitting only with a small bed side lamp and whilst writing this post the brightness went up to 1/3 of the scale 3 times for no reason and never went back down where it should be. This makes my eyes bleed. What a joke.
Click to expand...
Click to collapse
It's nowhere near as big of a problem as you're making it out to be.
I really think you are exaggerating. All phones have issues and on average this phone is very good.
The problem is they keep saying they've fixed it when they clearly haven't. I can get complete dimness in daylight all of a sudden. This is the first phone I've ever experienced auto brightness problems.
tropical cactus said:
The problem is they keep saying they've fixed it when they clearly haven't. I can get complete dimness in daylight all of a sudden. This is the first phone I've ever experienced auto brightness problems.
Click to expand...
Click to collapse
Yes it gets dim all of a sudden that too in Bright Light
do you have the 9.5.11 update? i think that it has been improved with the latest update.
zniper89 said:
do you have the 9.5.11 update? i think that it has been improved with the latest update.
Click to expand...
Click to collapse
Already updated and still the same for me. I have to manually untick and retick the auto brightness icon for it to correct at least once a day.
i feel that it was better with the latest update, maybe try to Wipe Cache? to see if it helps
That's one of the reasons i will switch to a custom rom when they are full functional. But that's been the issue with all oneplus phones at oos, in my experience. I had the 5t and 6, i thought it was the same.
It's not that hard to download an autobrightness app like lux
Arden144 said:
It's not that hard to download an autobrightness app like lux
Click to expand...
Click to collapse
I think it should work out of the box... Like in any other os. And these app you're referring to - it's been updated the last time 2016?
zniper89 said:
i feel that it was better with the latest update, maybe try to Wipe Cache? to see if it helps
Click to expand...
Click to collapse
I always wipe cache after every update to make sure all the improvements come through.
Trinaaa said:
That's one of the reasons i will switch to a custom rom when they are full functional. But that's been the issue with all oneplus phones at oos, in my experience. I had the 5t and 6, i thought it was the same.
Click to expand...
Click to collapse
Are you saying that custom ROMs can help with that? I may try it.
I used to use Lux app on my Nexus 6p and it worked well. But this app has never been updated to work with current versions of android. Probably because all the manufacturers can get it done right out of the box
zniper89 said:
do you have the 9.5.11 update? i think that it has been improved with the latest update.
Click to expand...
Click to collapse
Nothing changed in this update, infact this update is broken, i lose connection all the time and some calls cant get through, i have been forced to go back to 9.5.10
I have no problem with adaptive brightness. Since Android Pie, AI from google handle the adaptive brightness. See more https://venturebeat.com/2018/08/28/how-android-pies-adaptive-battery-and-adaptive-brightness-work/
My adaptive brightness is not that bad. I only really need to adjust at night in bed with lights off. Other than that i think it works well.
borijess said:
My adaptive brightness is not that bad. I only really need to adjust at night in bed with lights off. Other than that i think it works well.
Click to expand...
Click to collapse
Before Adaptive brightness was supposedly improved I used a product called Lux (no longer works on Android Pie) and compared to that apps options and ease of use the OP7 pro implementation of Adaptive Brightness sucks. You simply need to spend too much time teaching it to "adapt" while missing profiling options for particular circumstances to override the adapt option and just have the brightness level you desire for what your using the phone for at that particular time. Older android versions beat the current situation hands down at least on this phone. On the whole I love OOS and the OP7 Pro but this is a fail in my books. One that I've actively looked for a way to correct.
I rarely find it a problem
Not a issue for me and seems to get better each update...