Related
Sony xperia Z3 Dual D6633 Android 5.0.2 Build 23.1.1.E.0.1
Hi there,
Upgraded my Z3 to lollipop last week and, despite the fact that the upgrade itself was flawless, I think I went from a device that used to work like a charm to one full of annoyances.
On day #1, noticed the batt drain skyrocket. 3h after disconnecting it, it was at 68%, half way through the morning. WTF? was my first thought. On a typical day on kitkat, I was able to end the day at 40% at least.
The second thing I´ve noticed was the phone app. It starts giving me errors, saying that the "network could not be reached" when I try to dial a number. If I insist for 4, 5 more times, it crashes. Dialing is only possible again if I reset the phone.
The third thing is the lock screen. It seems that lollipop has a drop down menu that makes it possible to enable/disable lots of things, like communications and even setting the phone in airplane mode. Imho that´s a huge liability / security risk and it appears that there is no way around that.
Still about the lock screen, it seems to have a bug: if you have any activesync account setup, not notifications will show up, no matter how you configure it (to show all or hide sensitive content).
So, I had only one thing to do, after reading forums etc... factory reseting it.
Surprise! All problems are still there.
Does any1 have any tips on those?
Thanks in advance.
There will be a widget on one of the screens which keeps refreshing itself and I found that to be the battery killer on my 6603.
Did you use any specific app to pinpoint the culprit?
1. It is possible that the battery levels are calibrating and will be imprecise for a while after the update, using the device normally for a couple of days will fix it, or at least this is what I observed in many phones I owned.
2. This is very weird and I can't help you with. If not even factory reset did help you may have some corrupted data on one of your contacts maybe? Try to make a thread about this issue on the Sony forum.
3. I noticed that as well, but even on pervious versions you could turn off the phone so I don't think it changes anything. Make sure to disable the multi user options that would allowanyone to add a new user from the lock screen.
4. Another weird thing, I use exchange accounts on my phone and I don't have any problem on mine. See point 2.
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
ozzy lion said:
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
Click to expand...
Click to collapse
That's not a smartphone anymore, with all functions shut down and brightness low.
This phone has the best screen, use it at least 50% brightness.
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
ozzy lion said:
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
Click to expand...
Click to collapse
You said stamina.
Stamina means already some functions off.
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Hi, if problems are persistant you can always downgrad software at KitKat by using FlashTool and wait Lollipop 5.1 (5.1 will probably solve many problems).
StealthNet said:
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Click to expand...
Click to collapse
A new firmware version has dropped for the Z3 which I think fixes your issues with notifications.
I received it OTA yesterday, I'm running the Balkans customisation.
Thank you for the tip! I hope it does! Will keep it posted here just for the reference. I am starting to feel other "symptoms" as well, like bluetooth instability (you pair a device and it stops working, have to pair again).
.
Just hit another weird thing.
I am not being able to create a new vpn connection. I am trying to use the PureVPN and IPVanish client software, but when I try to setup the conection, I receive a disclaimer, saying that my traffic might be monitored, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
My device is encrypted and I have also noticed that I am not able to decrypt it.
Also, If I go to Accessibility and try to enable a service, the same thing happens: a disclaimer appears, saying that the service might observe my actions, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
Any ideas?
Ok, just a quick fup: the ability to create VPNs from apps is disabled if you encrypt the phone. It seems that if you create if before encrypting, it won´t be disabled; but you wont be able to create a new vpn from an app downloaded, after encryption.
Regarding the Accessibility > Services, after a *lot* of research, I have found that Twilight was the culprit. For the reference:
https://code.google.com/p/android/issues/detail?id=79637
Hello guys. This topic is pretty long and it is hard to read all of it but try to read all of it till end.
Well, let me begin. The main problem of the nougat update is the dramatic increase of battery consumption (for me at least) But why this is happening?
Actually this is a matter of battery managers. Huawei had created a great phone but obviously they messed things up in the software side. Google announced "Doze" feature with Marshmallow. If we could have a brief explanation of "what doze is" is it is basically a battery protection policy created by google. In Android, apps have the ability to use what’s called a “wakelock” to prevent your phone from going into a power-saving deep sleep mode. This deep sleep mode usually kicks in when your phone’s screen is off, but that can get in the way of how some apps work. For example, if you’re using a fitness tracker, you don’t want your phone turning off GPS or your accelerometer just because your phone is in your pocket with the screen turned off.
In principle, this is a good concept. Apps keep your phone awake and working when they need to, and let it sleep when they don’t. This is a problem, though, when every developer thinks their app is important enough to keep your phone on all the time. That’s why apps like Facebook kill your battery, even when you’re not using them.
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device). Here is a graphical explanation of how doze works versus time:
http://itresan.com/wp-content/uploads/2016/05/doze-header.jpg
Doze helps solve this problem by periodically blocking wakelocks and shutting off network access if your phone goes unused for a while. It will then periodically allow apps to check in during “maintenance windows” every so often (these windows occur less frequently the longer you don’t use your device)
If we turn back to the main topic, as I mentioned before, Huawei has some difficulties combining it's own features with google's. Huawei has its own battery manager. That's why you are not receiving some notifications from facebook or whatsapp. That is because that freaking battery manager shuts everything off but still, since it has a very poor approach, the system drains battery. It is basically a matter of doze does not kicking in. As you can see, the battery usage when the screen is turned on is about the same. However, the same thing cannot be seem when the screen is off.
So what to do in order to save some juice?
-There is some workarounds for doze kicking in like these ones:
https://play.google.com/store/apps/details?id=com.yirgalab.dzzz
https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze
These two apps have different approaches. I prefer ForceDoze as it seems the google's intended way.
I want to highlight this item because this might be the most important thing in this topic. If you don’t do anything with your phone, Doze will still do its job. It runs almost invisibly in the background. Occasionally you’ll get a few messages at once, rather than spread over a few minutes, but for the most part there’s no noticeable change. In other words this is a bit different from the conventional full deep sleep and you do not have to afraid from doze as you do with the full deep sleep.
-DO NOT CLEAN YOUR RAM TOO OFTEN. This will cause closed apps re-open and hence, more cpu usage.
-No! Cleaners, Task managers and other stuff does not work! As I mention before, they even lead more battery consumptions.
-Huawei has poor google service implementations. Even one or two implementation has some bugs that causing battery drain(for example: google backup). Try to turn them off.
-Know when to reboot your phone. Too frequent reboots may do the same thing as you cleaning your ram. However, rebooting cleans app caches so the system will work smoother. Once a week or two weeks is fine I suppose.
Please hit the "Thanks" button if you like and please point out the missing things and if you see a mistake please warn me for correcting it. I hope you liked the topic.
Have a nice day!
Doze is problem for me. I don't have push notification by the night.
darrr1 said:
Doze is problem for me. I don't have push notification by the night.
Click to expand...
Click to collapse
It's probably not because of the doze but the huawei's power manager itself.
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
darrr1 said:
Problem starts when phone is not active longer than 2-3 hours. In root I removed phone manager and it did not help fix the push notification problem
Click to expand...
Click to collapse
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
I did everything what I can without succes.
furkey said:
Assuming that you are on huawei release (not los releases), untick your app from close apps after screen lock. Then go to apps, settings, special access, and make the system ignore battery optimizations for the spesific app you want to get notification from.
Click to expand...
Click to collapse
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
xtcislove said:
first thanks for this tip. i hate it that i dont receive whatsapp messenges all the time, i hope it will work now.
BTP:
I assume huawei did not remove "doze" from our firmware, but maybe they replaced it with theire own battery manager?
Is there a complete source for doze, so we can check if everything is there? If yes it should not be that hard to activate doze and deactivate the huawei one.
But i guess we need at least the kernel sources to clear things up?
Click to expand...
Click to collapse
Doze is not on kernel level but it is on software level. Programmatically we can activate what is left from doze or at least simulate it. However, if there is a certain need for doze we should cook a whole new rom and yes, it requires open source too.
But, let's clear a thing here: Huawei did not completely removed doze. Actually, I think they can't do that if they wish to use Android. Just some settings of Huawei conflicts with doze and prevent its functioning.
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
antimatter.web said:
I'm using the honor 9 with emui 5.1 (android 7.0) and screebl (app used to control how and when screen locks/times out) is constantly getting killed. I have added it to ignore(=allow to run) in battery optimization and it's activated as a device administrator. It is not selected to close (power intensive app prompt) or instructed to close when screen goes off. Yet it repeatedly is getting killed - is there something else I need to do? I can't seem to find anything else I can do to stop it from being killed and it's a major nuisance.
Click to expand...
Click to collapse
Could you finally solve this?
I also have and Honor 9, and have the same problem with aplicacition radardroid. Is getting killed, and also have all configured to prevent this...
Try by having both in the Settings
-Battery/Close apps after lock screen (uncheck in the list)
-Apps/Settings gear/Special access/Ignore battery optimization (make it allowed)
Thank szgfg,
Both are already well configured, but still closing the app.
mikicl said:
Thank szgfg,
Both are already well configured, but still closing the app.
Click to expand...
Click to collapse
Check also is not being closed by the automatic cleanup (so add it to clean whitelisted apps) and that is not being closed due to high consumption...disable that on battery settings... Let the advertisement but do not let phone administrator close that apps automatically
Enviado desde mi EVA-L09 mediante Tapatalk
Hi jcalderonv74,
Thanks for your answer. I didn't know about the clean whitelisted apps, was a surprise to find it. But unfortunetly, everything was well configured.
Option to avoid being closed due to high consumption was already OK.
So nothing to change, everything was as it has to be. Seems more a software problem in EMUI 5.0
After some days without touching anything in the phone's configuration, finally observed that everything is working fine. All aplications configured keep opened, and it's only Radardroid aplication that sometimes closes alone (only sporadically after a recent update)
Seems more an error in Radardroid aplication that in telephone's software. So I'm not worring more about that.
Hello,
I'm doing a simple Android background service that implements the raise to wake up feature. Thus, when the phone is in sleep mode (i.e. screen off) and the user raises the phone from the table, it will be waked up by the service.
When I attach the phone to the computer using the debug USB to test the application, in particular looking at the message of logcat, everything work well. Even if the screen is turned off, I can see from android studio that the service is alive and when I try to raise the phone from the table it will wake up.
However, when I detach the phone from the computer, the service won't work. In details, sometimes it works, but if I leave the phone asleep it doesn't work anymore. Checking the running services on my phone I can see that my service is alive, however it is not responsive.
What could be the problem?
I tried both making the service as background service and foreground service. The result is the same.
I'm testing the service on Android 7.0.
You can see the source code (with a precompiled binary) and/or contribute on github (look for the project called raison, I don't have the permission to put the link). The service is started after the boot of the phone or when the user opens the activity.
It doesn't seem a bug of the application (e.g. in the logic), because it works during the debug phase.
Furthermore, I don't have any power saving option and I see the service running (using the developer options).
Another note is that my phone has the double tap to wake up, however the double tap often doesn't work or is really slow (it wakes up after >10 seconds), thus seems that my system is slowing down so much during the sleep. However, applications like whatsapp work well.
There is a way to force my phone to keep the service running (without slowing it down) even in the sleep mode?
Thank you! It could be helpful also to have a feedback of the application on your phones, to see if it is just a problem of my phone or it is some behaviour of Android that prevents the correct execution of the service.
EDIT:
I've also tried to use a wake lock to keep the CPU awake (preventing the deep sleep) without success.
Hello. I'm sure this has been asked bunch of times, but whenever I google it, I get opposite results.
So.. I want my phone not to save battery. Like.. I want my notifications to come through instantly. Now only few apps are capable of doing that (calls, messages, alarm clock). But all other apps - like gmail, skype or FB Messenger are not. I only receive notifications when I wake up my device (or when someone starts spamming me messages, after like 5th message they come through, so I guess phone is receiving those messages, just not putting them through). Whenever I google solutions for this, I only get tips on how to make it worse (because for some reason everyone just want to save their batteries) or nothing that actually worked.
What I have done so far:
Battery optimization - off for every single application (even system).
Background activity manager - looks off (there is no toggle, only the 'blacklist', which is off).
Background activity cleaner - off.
Every app has 'Urgent' notification importance.
Phone is not rooted (nor it can be.. stupid Nokia policy). Android 8.1. Nokia 5.
Battery power saver - off (obviously).
Looks like I have data saving modes turned off (I might have missed some, but I only do not get notifications while device is sleeping).
Factory reset (multiple times (for various reasons)). I never received real-time notifications on this phone while it's sleeping.
I contacted Nokia support team, but they took 30 minutes to tell me to reboot the phone, so decided not to wait another half an hour to tell me to clear apps' cache.
I saw that with ADB I could turn off doze, but as I understood, it's temporary as restarting the phone brings this 'feature' back, but I have to restart this phone every day or two due to not a huge amount of RAM (2GB) as it fills up with trash and restarting the phone brings me the best performance, so it's really not a great option. Edit: also, it didn't help
I guess it's a manufacturer specific problem then? ;s
* Often when I work the mobile is at my desk but I still comunicate by sending SMS and using Whatsapp in my webbrowser. Works fine with Samsung and Huawei but with my new Mi10 Ultra id does not work. Connection is lost and I have to tuch some key on the phone to light up the screen and then it syncronizes.
I have set permissions for the apps to allow both autostart and not affected by the battery saver in the system.
I have also set the "data usage" for the apps to allow background data.
...but still, background data for SMS and whatsapp IS deactivated until I light up the screen.
Has anyone run into this problem? Is there any general (mayor) switch for this that I have missed?
This happens to me with Gmail. Sometimes they come in on the lockscreen and sometimes I have to turn the phone on for them to appear. I still have this problem on my Samsung S20 Ultra but I learned to live with it since I never figured out what the problem was. I have no such problems with my SMS or WhatsApp though. Everything else for me seems to be coming through.
tusenkonstnar said:
* Often when I work the mobile is at my desk but I still comunicate by sending SMS and using Whatsapp in my webbrowser. Works fine with Samsung and Huawei but with my new Mi10 Ultra id does not work. Connection is lost and I have to tuch some key on the phone to light up the screen and then it syncronizes.
I have set permissions for the apps to allow both autostart and not affected by the battery saver in the system.
I have also set the "data usage" for the apps to allow background data.
...but still, background data for SMS and whatsapp IS deactivated until I light up the screen.
Has anyone run into this problem? Is there any general (mayor) switch for this that I have missed?
Click to expand...
Click to collapse
Hi there. I pretty much have the same problem with this phone. If it's not permissions nor background data, it's the power saving feature, which is the most aggressive I've seen yet.
I was talking with someone about this in another thread, but I was instructed to turn off battery saver. It got better for a day, but it kind of returned back the way it was. I think you could try and play around with the power saving settings for the apps you want immediate notifications from, which I haven't had time to do. Please let me know how it goes for you and I'll find time to play with it this weekend.