There are some users that have been reporting, using apps such as CPU Spy, that the phone does NOT enter a deep sleep state in standby. Some resourceful users over on the S10+ have found the cause of the issue, which is a bug with the proximity sensor. The bug is triggered AFTER entering a VoiP call such as WhatsApp call or Skype, at which point the phone will continue to fail to deep sleep until the next restart.
Thus, in order to fix the issue, in the meantime I recommend restarting after VoiP calls, and report the issue to Samsung through the Members app in hopes of getting it fixed.
I can confirm that... After finding why I have massive standby drain and blame few apps for that, now I know this is an issue with Voip calls. Reported trough Members app already.
+1
can confirm it too.
Can confirm that this happens too. Will report it through via samsung members
I experienced this as well. On the first day when i didn't have anything installed was able to see the phone going to deep sleep. But after I installed did a few whatsapp calls and bam no more deep sleep. After seeing this post, rebooted phone, unplugged from charger about an hour ago and lo and behold, 50 mins of deep sleep.
Asked my SO to not to do whatsapp calls today. Lets see how the battery life stands.
Interesting, I am guessing this bug is limited to Exynos models? Haven't tried whatsapp or voip calls on my Exynos S10+ yet.
VICosPhi said:
Interesting, I am guessing this bug is limited to Exynos models? Haven't tried whatsapp or voip calls on my Exynos S10+ yet.
Click to expand...
Click to collapse
Apparently.
So far 1hr 32min in deep sleep after reboot. A few calls, SMSes, YouTube, whatsapp messages and web whatsapp used. On battery power for 1hr 45mins so far and 93% left according to AccuBattery.
I can confirm having the same bug, exynos model here. One whatsapp call is sufficient to stop the phone from going into deep sleep.
I already reported the issue on samsung member too.
Is this happening after normal calls also?
gunemalli said:
Apparently.
So far 1hr 32min in deep sleep after reboot. A few calls, SMSes, YouTube, whatsapp messages and web whatsapp used. On battery power for 1hr 45mins so far and 93% left according to AccuBattery.
Click to expand...
Click to collapse
Thanks, does it also happen after calls placed using Google Duo? I am installing Feb 1 security patch which supposedly improves fingerprint recognition and camera performance.
Battery life on my Exynos seems slightly worse than Note-9 so far.
VICosPhi said:
Thanks, does it also happen after calls placed using Google Duo? I am installing Feb 1 security patch which supposedly improves fingerprint recognition and camera performance.
Battery life on my Exynos seems slightly worse than Note-9 so far.
Click to expand...
Click to collapse
I can confirm, that it happen after Whatsapp and FB Messenger call, or even when You play voice messages via this apps. Not sure about Google Duo.
---------- Post added at 08:32 AM ---------- Previous post was at 08:31 AM ----------
AayushN4 said:
Is this happening after normal calls also?
Click to expand...
Click to collapse
Nope.
Any snapdragon users having this issue?
sruel3216 said:
Any snapdragon users having this issue?
Click to expand...
Click to collapse
I'm interested to know
Add Viber to the list as well.
If you have a SnapDragon variant you can try this. If you have AccuBattery installed, check if you have at least 1hr of deep sleep recorded after unplugging the phone from the charger. Next make a whatsapp/viber/skype call. After about an hour or so check again the deep sleep time. If it has increased from the previous recording that means you're not affected.
I can confirm I have this bug on my exynos s10, only tested whatsapp though. The bug is triggered by whatsapp calls but not by whatsapp voice messages for me.
Inviato dal mio SM-G973F utilizzando Tapatalk
I was also kinda facing this deep sleep bug where in the phone was at 442 mhz continuously but don't know why it stopped and I'm getting such a good idle drain.... Just the fact that I deleted facebook app and 2-3 other apps which I wasn't using at all.
More importantly I was facing this issue of no deep sleep without the proximity sensor bug
I can confirm this bug is also triggered by google duo's voice and video calls
Can confirm regular s10 exynos model affected by the bug
Is it possible to get rid of it without reboot?
Say if you clear cache and force stop WhatsApp/viber and then start them over again?
tiho5 said:
Is it possible to get rid of it without reboot?
Say if you clear cache and force stop WhatsApp/viber and then start them over again?
Click to expand...
Click to collapse
Unfortunately not... Only restart can do the trick. And this is very annoying! And more annoying is, We will wait for Samsung update for ages...
Related
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
I've found a similar problem, and explanations on why it's happening, but it says that it appeared in Gingerbread but has been corrected in Honeycomb and ICS.
It does seem like the exact same problem with the same symptoms though, so I wonder if it really is gone...
Here is the page where I found the info :
http://fivasim.pcriot.com/androsensor.html
And here is a quote from that page :
Update: After many months of testing and debugging I haven't found a way to fix the battery issue for good. Perhaps I shouldn't... It's not really my issue but a general android problem (just google for "gingerbread battery drain"). And it happens with EVERY app that makes use of the sensors that are the root of the problem.
The battery leakage comes from android sensors that are not well supported by the kernel or the android OS. Most usually the accelerometer sensor causes the issue but sometimes the light sensor and the proximity sensor can cause this issue as well. Other sensors seem to have nothing to do with battery drain.
However I have found what's causing it and ways to `patch` over it (unfortunately, no way to permanently fix it).
Trying to invoke a sensor with such a problem, will cause the sensor to stay open even after the app is stoped and disposed of memory.
Another common issue is a conflict. Two apps register the same sensor, then one app unregisters but fails because the sensor is in use by the other app. The sensor stays in use by one of the two apps and this will remain even after both apps are killed.
In most cases there is a way to fix this:
- In the first case, you may just find which sensor is misbehaving (strange readings, very slow response or 'Failed to start' error etc.). Go to AndroSensor's settings and disable that sensor. Then reboot, run AndroSensor once and wait to see if the problem persists. Most usually the light and the proximity sensors are to blame for this issue. Sometimes the issue is caused only if both light and proximity are enabled, but disappears after disabling any of the two.
- If you don't have a misbehaving sensor then there is probably some conflict. Conflicts can be caused (usually in Gingerbread) when having auto-rotate (accelerometer use) or auto-brightness on.
Solution: Go to your device's display settings and disable auto-brightness and auto-rotation. Then reboot, run AndroSensor once and wait to see if the battery drain continues. If the problem persists then there is probably a conflict with some hidden/system service. Most usual is the conflict with SGS and SGS2 secret menu ( by dialling "*#0*#" on the dialer ). I have found no way to bypass this and it can only be solved by disabling the accelerometer and orientation sensors in AndroSensor, then reboot (orientation sensor makes seemless use of the accelerometer).
The only good thing about this, is that in HoneyComb and ICS the issue seems to have disappeared for good!
Am I really the only one with the problem?
Mithrandir007 said:
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
Click to expand...
Click to collapse
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
chamonix said:
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
Click to expand...
Click to collapse
It does seem to go to deep sleep, but I still see a big difference in battery life between when it happens (around 7-10%/hour), and after I reboot (~ 1%/hour).
Before I start applications using those sensors, the battery life is normal as well, so I don't think it's something else.
I've just made a few screenshots to show what's happening.
Last night, before going to bed, I've rebooted the phone, then started Sygic and AndroSensor, exited the apps, then manually force closed them to make sure.
Then I left the phone charging for the night.
This morning, I remove the phone from the charger, and Badass Battery Monitor starts from that point to calculate the battery drain from everything (so I'm sure neither Sygic nor AndroSensor have been running at all since I unplugged the phone).
Since then, a bit less than 2 hours have passed (I've barely used my phone during that period since I was getting ready then driving to work).
There was a 5% discharge (which is strangely not as much as I had yesterday, but still more than the usual 1%/hour when in standby) and we can clearly see what's eating the battery the most in Badass Battery Monitor.
The "Orientation", "Pressure", "Magnetic Field" and "Accelerometer" sensors have been running the whole time since it was unplugged.
What do you think, is this normal behavior?
I've now installed another custom ROM (Omega 8, with the new samsung firmware update), and the problem seems to remain..
If I'm the only one with the problem, I'm starting to think it might be something hardware (or an app I've installed every time maybe), since I've had the problem with every ROM I've installed...
Switching to another kernel didn't seem to help either.. I'm really starting to wonder if this is something I can fix.
Does no one else have the problem?
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
Click to expand...
Click to collapse
Yes I care. Thanks very much for posting this. I've noticed exactly the same thing and it's been driving me crazy. Good to know it's just a false alarm. With ICS 4.0.4 coming to the Galaxy S2 soon, maybe it will be fix there.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
If this is really the problem that would be an deep in Android or between the hardware and android as it is the 'batteryinfo' service reporting sensors data.
Indeed, I don't think there is an easy fix for this one, unless someone has already worked on that part ((un)registration of sensors from the battery measurement service).
Hopefully it'll be fixed in a future version of the firmware, or in Jelly Bean.
XDA-Usr : maybe it'll be fixed in that version, indeed..
It is just a false alarm, although it still leads to inaccuracy of the battery level.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
luzok said:
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
Click to expand...
Click to collapse
On my Galaxy S4, the problem seems to be gone, so hopefully it'll be gone on your device as well once Samsung releases the 4.2.2 update.
Sent from my GT-I9500 using xda app-developers app
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
graffixnyc said:
Do you have touch sounds enabled? I noticed when I have them enabled I get more of an audioout wake lock. I also get it while I play music on my phone.
Click to expand...
Click to collapse
Yes i have it enabled. in fact all the sound settings i have under settings-sound-system are all enabled. il try disabling them all. its just so weird why its having sound wakelocks even if the phone is not being used or the screen off. thanks for your reply.
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Same problem here, and I don't have the sound enabled.
Sent from my GT-I9300 using xda premium
Ausboy 2011 said:
have same problem too...
Sent from my checkrom jellybean powered sgs 3
Click to expand...
Click to collapse
Im aware your using checkrom from your signature but its on jb..i am running omega 27.1 JB..on the nexus 7 forums some guys are having the same problem too..is it because we are all running JB?
Sent from my GT-I9300 using Tapatalk 2
same problem here using omega 27 with all system sounds off
Anyone track down a solution to this yet?
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
slaphead20 said:
seems to be a jb thing and I spent a bit of time trying to pin down what caused it, but each time I drew a blank, but I got rid of it.....and I have kept my eyes open but I remember GM starting in his kernel thread that even he couldn't pin down what it was.
Apologies for not having a solution, but you can get rid of it
Click to expand...
Click to collapse
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
NewAussiefromCanada said:
Might I inquire as to how you ended up getting rid of it in the end? :fingers-crossed:
Click to expand...
Click to collapse
that's the thing.....I'm really not sure at all, something in my set up, something I froze with titanium, some sound setting, I really don't know,, I don't use haptic or touch sounds, so that might be linked, but beating in mind if I had tried one thing at a time, then used bbs and let it idle for two hours each time I tried something,I would be at it forever,
I'm dual booting slim and wanamlite, so even more complicated
Sorry to be so vague but I really can't pin it down!
skylinerr34j said:
as the title says im having trouble with battery drain due to AudioOut_2 wakelocks but im not sure if this is really whats causing my drain. il upload my logs from betterbatterystats since im not an expert on really understanding the logs it generates. hope somebody can give me a clear explanation on my problem. because im getting paranoid over this. lol
Click to expand...
Click to collapse
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
puredesire said:
As a test, I suggest you to disable this feature of the phone (go to Settings - Manage Applications and disavle apps Google Text to Speech and Samsung TTS).
Click to expand...
Click to collapse
Did this work for anyone?
themadproducer said:
From my testing with my stock rom and communicating with the Dev from Better Battery Stats a month ago or so, I don't believe the statistic AudioOut_1 or AudioOut_2 is the cause for any battery drain. (at least not for me) You see them listed under Partial Wakelocks but the "count" increases every time certain UI sounds are triggered even with the screen ON! So it's a bit misleading...because the OS implies that the counts are increasing during standby.....hence the term Partial Wakelock.
And YES...by disabling Keytones and Touch Sounds etc., the statistic is eliminated and BBS will not show an increase. So basically...I IGNORE THIS STATISTIC...and keep my sounds turned ON!
Click to expand...
Click to collapse
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Metalshadowx2 said:
See I would agree with you but when you turn and disable everything you have to your phone should be allowed to enter deep sleep. under the partial wakelock the audioOut_2 is the only thing not allowing it to enter thus if you look at all the all the apps you have running and some apps run like the sound is on even with the screen off. My problem was puzzle and dragons would run the sound and drain my battery and when i exit it the audio problem stops. So to answer your question tony just empty your running apps when you get ready to turn your screen off and see if that helps.
Click to expand...
Click to collapse
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
michalurban said:
Same for me. Normally my tablet eats 1 percent of battery max for a screen off hour. Today, I restarted, done a backup, booted the system and then I turned the screen off and went about my bussiness. Now, according to BBS, I have 3,5 percent down per hour. And the only "huge" wakelock is Audioout_2.
Click to expand...
Click to collapse
Same problem here on my note 2... last night before sleep time i killed all apps by holding down the home button.BBS clearly showed audio_out2 as the one which has the partial wakelocks... sigh... no solution yet?
on a side note in sound settings im not using sound and vibration. just keyones. screen lock sound and haptic fb.
Same problem here
All touchsounds disabled and AudioOut_2 did not stop to drain my battery. Maybe it's time to switch to BlackBerry Z10.
for those who are having problems with phone not going to sleep, just go to settings - manage apps - and disable the Samsung TTS app (or freeze it with Titanium Backup). At least this fixed the problem here.
cya
Has anyone encountered this problem? After a few minutes of my screen being off, i do not receive ANY notifications for incoming messages (e.g. Hangouts, Whats App,...etc). As soon as I wake up the phone again, I am flooded with pending notifications (some of which are hours late)
The problem is not limited to my phone; as 2 of my other friends are facing the exact same issue on their units.
I am referring to the Galaxy S6 Edge.
Does anyone know how to resolve this issue ?
[[Update]] seems this problem is with all lollipop phones. At least where I'm at. I can confirm that the M9, Nexus 5, and Nexus 6 all demonstrate the same behavior.
Bump! Problem still exists. Hoping for someone to shed some light
Crimso said:
Has anyone encountered this problem? After a few minutes of my screen being off, i do not receive ANY notifications for incoming messages (e.g. Hangouts, Whats App,...etc). As soon as I wake up the phone again, I am flooded with pending notifications (some of which are hours late)
The problem is not limited to my phone; as 2 of my other friends are facing the exact same issue on their units.
I am referring to the Galaxy S6 Edge.
Does anyone know how to resolve this issue ?
Click to expand...
Click to collapse
Anything installed? Like Greenify, or battery saving apps?
Nothing. Stock and straight of the box.
Do you have any battery saving options on?
None. Its has no power saving nor blocking mode activated.
yep. Just got my AT&T 64g edge. with screen off I get no notifications for Gmail, Hangouts, Text or mms. turn screen on and everything suddenly shows up. fresh out of the box, no powersavings or anything on..
I'm seeing the issue on my regular at&t s6. any solutions ?
You do not get the blinking LED notification? Or are you guys expecting an Ambient notification?
In some cases the notification arrives late or in some cases not at all. no LED notification, no sound notification .. nothing!
I'm not sure why this hasn't bubbled up yet .. its quite a serious problem. My old s4 on 4.4.2 handles push notifications like a champ.
Sadly it this issue did bubble up earlyier as this thread was started on the 2nd... about half the time if my screen has been off for a bit I get nothing, and then when I wake it up I get multiple email, text and google hangouts notifications...
[[Update]] seems this problem is with all lollipop phones. At least where I'm at. I can confirm that the M9, Nexus 5, and Nexus 6 all demonstrate the same behavior.
Same problem for me -push notifications work intermittently under lollipop - had same problem with my moto x 2014 and now has started with the edge.
I didn't have this issue with my M8, I have it with the S6E though..
Have same problem here. Sometimes works with no issues, sometimes get 4 notifications once the screen is turned on.
Started noticing this as well. Turn my screen on and I will get notifications from email, whatsapp, groupme and a few other apps.
turn off wi-fi
this happens to me on my s6 edge (t-mobile variant) when I have wifi on and am connected to a wifi network.
turn off wifi --> perfect notification behavior
I assume this is a software issue and not a hardware one. I guess Sammy needs to push a fix for this.
I have the same problem, i have been pulling my hair looking for a fix. Brand new s6 edge att model here doing the same thing.
The only solution is to use other email apps other than gmail and it works fine. I'm certain it is a software bug however my wife has an S4 with lolipop and no issues so I'm concerned a bit but now that I have seen this thread it is clear I'm not the only one.
The issue on my phone resolved itself. No firmware updates or anything. Go figure
Hello while I really love this phone it's got a few annoyances. I created this thread to see if I'm the only one and if anyone else reports any more.
Frequent FC of the Google and Google photos app
Random things happening if phone is not restarted frequently (eg all sound went quiet until restart)
Keyboard skin doesn't change for lock screen
Let me know if your having these issues or if you have any not listed.
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
My xperience
I only had the phone for four days, because I found a dead pixel on my screen. I am currently expecting a replacement or a refund. During that time I noticed that changing the theme does not change anything else besides the home and lock screens. There were some random drops in wi-fi connection. I also noticed a couple of stutters here and there. Two or three apps crashed on exit. I also miss the picture album widget with the swiping pictures on screen. That is not present here.
So no one seems to be getting any issues like me ?
Sent from my Sony Xperia XZ1 using XDA Labs
kistigun said:
Bugs I've had so far:
- one reboot while using snapchat
- sometimes it takes a lot of time for the device to wake up
- autobrightness is terrible in low light conditions(stuttering and inconsistence)
- while streaming audio with bluetooth in my car the radio somtimes shows audio paused while it's still playing. In this case remote controls also stop working
Click to expand...
Click to collapse
Agree about the autobrightness, it's inconsistent and keeps changing in low light conditions. Makes reading an absolute chore.
I'd also love a way to quick enable glove mode, my previous Samsung had that in the drawer menu.
for those of you who have owned sony phones, has there been timely updates to fix bugs like the ones being reported in this thread? some companies like to release updates with new features but without fixing bugs so im just making sure before i pull the trigger on an XZ1
thank you all!
I've had this issue after the recent update to build 47.1.A.2.324 . Google assistant doesnt work with Music ( default sony music app) . it used to work before this update, and it doesnt work anymore and asks me to set google music as the default music service.
WiFi signal drops when I hold my hand on the backside.
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
I've aso had problem 2 & 3. I also overslept myself 3 times over this, very anoying!!!
Edit: found this on the sony forum on how to get smart lock menu back:
https://talk.sonymobile.com/t5/Xperia-XZ1/47-1-A-2-374-new-update-13-10/m-p/1268608#M467
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
NockIt said:
1. The phone seems to reboot itself frequently.
Click to expand...
Click to collapse
Oh god, i was going to change to the XZ1 this week after returning my Compact due to the rebooting, I thought they'd be different enough internals to not have the same issue. I guess its a Sony/Oreo issue then.
a freeze occourred waking up the phone from camera button. The camera button was set to "open and shot"
I had to reboot via vol+ and power...
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
kistigun said:
Updated to 47.1.A.2.374 yesterday, sadly all bugs remain the same. And I can add one; the smart lock menu is empty and all smart lock function dont work anymore
Click to expand...
Click to collapse
Its a android 8 bug
Solution:
Disable trusted agents on security settings.
Restart phone
Enable security settings. Thats it.
I can add another issue. That is bluetooth delayed when I watch video on youtube and play some games.
NockIt said:
1. The phone seems to reboot itself frequently.
2. Sometimes no sound when alarm is going off. I overslept once because of this
3. Quite often no sound when phone is ringing. Need to reboot the phone for it to act normal again.
4. Crashing when picking up phone. Call goes to call waiting and phone rings again. When picking up there is a very loud biping sound throughout the conversation. This goes away when rebooting.
Click to expand...
Click to collapse
Similar problems here even on the latest build 47.1.A.2.374. Also Google assistant frequently stops responding and then the phone becomes unresponsive and eventually restarts without prompting. Never had problems like this on the XZ when that was released. Seems to be some issues with Google services on this Sony hardware. Suggest everyone having issues pound the send feedback option and hope that someone in Google or Sony are listening!
My notification tones keep going off at random intervals and nothing's in the status bar that could've set it off.
Can confirm random reboots.
Bought the phone from clove and Amazon.
Amazon was horrendous reboots during setting the phone up - returned.
The clove one had no reboots until today, several times.
Some fkd up kernal CPU bogusness going on here.
Sony need to sort this.
I'll check with matlog tomorrow if anything stands out
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
roytam1 said:
Phone Idle is always 1st entry of battery drain list, does anyone have similar situation?
Click to expand...
Click to collapse
same here.... battery life is suffering. Stock firmware was better
Why goes my pocophone not going in deep sleep. I'm using the last update 10.2.20 Stable. I use battery saver, use adaptive battery is on, non interactive-mode is on. Anyone who can help me? ,
Sidddy said:
Why goes my pocophone not going in deep sleep. I'm using the last update 10.2.20 Stable. I use battery saver, use adaptive battery is on, non interactive-mode is on. Anyone who can help me? ,
Click to expand...
Click to collapse
Your phone is always awake whereas mine isn't (see screenshot, awake is "éveillé"). Maybe you need to disable mobile network like me ?
Blendman974 said:
Your phone is always awake whereas mine isn't (see screenshot, awake is "éveillé"). Maybe you need to disable mobile network like me ?
Click to expand...
Click to collapse
Yes, but before the Pie update, my pocophone was going in deep sleep and uses 2% standby at night, now 10%
Sidddy said:
Yes, but before the Pie update, my pocophone was going in deep sleep and uses 2% standby at night, now 10%
Click to expand...
Click to collapse
That's why I thinks it's a bug. May be usefull to make a bug report.
I have the same increased stand-by battery usage (1-2% per hour). After monitoring battery usage with a Gsam Battery Monitor app, I noticed that 'sms_snd wakeup' activity was active for several hours.
After googling, I found out that sms_snd is a proximity sensor's process.
Try to disable 'Pocket mode' in Settings -> Lock screen & password -> Advanced section.
I am testing it at the moment, will share my results after a day of usage.
Please try and share yours.
Blendman974 said:
Your phone is always awake whereas mine isn't (see screenshot, awake is "éveillé"). Maybe you need to disable mobile network like me ?
Click to expand...
Click to collapse
You can as well switch off the phone.
You have a severe mobile signal issue. The place where the phone was (while sleeping) has a very bad mobile signal. So for you it might be a solution to switch off the network. If you can't do that (as most of us can't afford to do that), another option is to switch to 3G or 2G where the signal might be better.
JamilG said:
I have the same increased stand-by battery usage (1-2% per hour). After monitoring battery usage with a Gsam Battery Monitor app, I noticed that 'sms_snd wakeup' activity was active for several hours.
After googling, I found out that sms_snd is a proximity sensor's process.
Try to disable 'Pocket mode' in Settings -> Lock screen & password -> Advanced section.
I am testing it at the moment, will share my results after a day of usage.
Please try and share yours.
Click to expand...
Click to collapse
Actually I don't think it will disable this process. A lot of users are reporting that there proximity sensor is always on (small IR led in proximity always on). This activity could be the source :/
EveryThing is linked xD
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
tnsmani said:
You can as well switch off the phone.
You have a severe mobile signal issue. The place where the phone was (while sleeping) has a very bad mobile signal. So for you it might be a solution to switch off the network. If you can't do that (as most of us can't afford to do that), another option is to switch to 3G or 2G where the signal might be better.
Click to expand...
Click to collapse
Yes I could switch it off at this point xD. But it's faster to wake up when it's on airplane mode. Anyway I don't personally need network when I'm sleeping.
I have not noticed any progress with Pocket mode turned off. Also double tap and change orientation wake up switchers are turned off. 10.2.2.0 is in use.
Still awaking, still battery draining...
Are there any news to resolve the problem?
Turn off adaptive battery. It has improved battery life for me noticably.
Murareelalm said:
Turn off adaptive battery. It has improved battery life for me noticably.
Click to expand...
Click to collapse
It is already turned off.
Same issue with mine...
Googled a lot but no progress .. nothing works..
If anyone find solution.. please do inform me..
I did not have any issue when moving to MIUI 10 (androi Pie) myself on my pocophone, but I recently installed a nokia 5.1 plus for a friend.
New, out of the box, new install, immediate upgrade to android 9 (it's an android one phone), no additional apps installed.
It barely survived more than 10-12h, phone never went to sleep.
I found this was a quite common problem when upgrading to android pie, and most users suggest to clear system cache from recovery menu.
However, that is not possible anymore as in most cases android pie doesn't show you that option anymore.
I solved the issue by doing a factory reset from within the OS, then did not configure it when it started up. Instead, I turned it off again, booted to recovery menu and again wiped all data. After that, the phone was configured and the battery was fine. From 10-12h it now holds for 40+ hours.
For reference: that phone lost 30-40% during nighttime!
I'm having issues with my battery too, does anyone know how to fix this?
logawa said:
I'm having issues with my battery too, does anyone know how to fix this?
Click to expand...
Click to collapse
There can be hundreds of reasons. If you are merely going to ask a question without furnishing any details, this is the best I can do.