Related
Hi,
I noticed that after I charged my XZ using the docking station especially the launcher gets laggy until I reboot.
It's definitely not the launchers fault. Stamina mode is enabled and many user plus system apps greenified.
I'm running stock .253 unlocked with DooMKernel v7.
Did anyone experience the same issue and knows how to solve it?
Gesendet von meinem C6603 mit Tapatalk 2
Am I really the only one with that problem? Maybe it's an issue with the apps greenified:
Account Manager
Airdroid
Amazon
Aptoide
Backup-Restore
Chrome Beta
Dropbox
Demo
eBay
Facebook
Google Keep
Lucky Patcher
Maps
MirrorLink
Office Suite
Package Buddy
Photo Analyzer
Picasa Uploader
Pico TTS
SenseMe
SmartcardService
Smart Connect
Titanium Backup
TV App Start
Update Center
Xperia Proxy
Xperia Social..
Xperia Home
Xperia extension for Throw
Youtube
Zedge
is it hot? if so its probably thermal throttling.
I will wait for the next time and see if it's hot. But the CPU goes up to 1,5ghz, so it shouldn't be thermal throttling.
It also stays laggy for hours, the device sleeps well without any battery drain.
Gesendet von meinem C6603 mit Tapatalk 2
ccab said:
Hi,
I noticed that after I charged my XZ using the docking station especially the launcher gets laggy until I reboot.
It's definitely not the launchers fault. Stamina mode is enabled and many user plus system apps greenified.
I'm running stock .253 unlocked with DooMKernel v7.
Did anyone experience the same issue and knows how to solve it?
Gesendet von meinem C6603 mit Tapatalk 2
Click to expand...
Click to collapse
might be some problems with smart connect app? it starts every time u connect ur phone to docking station
damned91 said:
might be some problems with smart connect app? it starts every time u connect ur phone to docking station
Click to expand...
Click to collapse
Could be. There issue seems to be solved for now. What I did:
- degreenify smart connect and smartcard services
- delete trickster mod and replace it with faux123 kernel enhancement
Damn, looks like it has nothing to do with charging or trickster mod. Homescreen and notification bar got laggy again..
Device is not hot. With mpdecision turned off it gets a little bit smoother again, but still not perfect.
I've got this problem sometimes after I take the phone out of the dock ( not oem ). I'm on locked bootloader, root .253 version no stamina mode, only Greenify
Do you think it could be caused by Greenify?
I flashed CM10.1 and after a day that fu*king phone got laggy again..
Gesendet von meinem C6603 mit Tapatalk 2
No, not Greenfiy, I think, in my case, it has to do with the charger, charging, docking mode something like that.
vibecatalin said:
No, not Greenfiy, I think, in my case, it has to do with the charger, charging, docking mode something like that.
Click to expand...
Click to collapse
Finally.. I thought I was the only one having issues!..
Yes, after docking I occasionally have this problem. The phone just becomes laggy until I restart.
I don't use greenify since I don't root my phone. Tried killing all tasks, apps, to no avail
I have no problems on my XZ after docking it.
Sent from my Xperia Z
I'm not having this ``problem`` but very rarely, only 3-4 times in 3 months.
I had spanish generic 569, and since they didn't update yet to 10.4.1.B.101 I decided to switch to a CE one that I found here:
http://xperiafirmware.com/8-firmware/33-sony-xperia-z-c6603
The issues are:
-When I call someone I can not hear anything unless I activate the loudspeaker. This is not always happening and seems to be temporally fixed after a reboot.
-If anyone calls me, the loudspeaker is activated automatically when I pick the call (some says this is due to Google Chrome update)
-The proximity sensor that turns off the screen while talking is misbehaving
Of course I have tried again wiping everything in the flashtool, but didn't help.
Solution? I went back to the safe spanish generic 10.4.B.0.569 which they didn't updated yet to 101, maybe because they found this serious bug? I find it weird that they didn't adopted it yet
http://forum.xda-developers.com/xperia-z/general/info-firmware-version-customization-t2315914
The bug has also been posted in other forums http://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/10-1-1-b-0-101-update-problem/td-p/568927
Anyone else here can reproduce or solve it?
The loudspeaker activates randomly when I answer calls, but only from one specific contact. My earpiece works fine, however.
I'm on 10.4.B.0.569 Generic ES and I've found no solution to it. I just remember to deactivate the speaker phone when I answer calls from them.
Sent from my C6603 using Tapatalk
I read somewhere that its been caused by google chrome,delete every thing related to it and reboot and wait
Verstuurd vanaf mijn C6603 met Tapatalk
demon2112 said:
I read somewhere that its been caused by google chrome,delete every thing related to it and reboot and wait
Verstuurd vanaf mijn C6603 met Tapatalk
Click to expand...
Click to collapse
that's right, i had this same problem, and disabling google chrome solved the problem.
sorry for my bad english.
Well, I like Chrome, so I will live with it.
Thanks for the advice though.
Sent from my C6603 using Tapatalk
Yeah i like chrome aswel butt aosp browser i fond it suits me a little better ill try to search. And link that thread in here
Verstuurd vanaf mijn C6603 met Tapatalk
I have done more research and yes, indeed it seems that google chrome is resposible of the auto loudspeaker mode and it can also happen in other firmwares or even phones.
http://forums.androidcentral.com/lg...e-automatically-when-calling-answering-2.html
NEVERTHELESS for me the issue of not being able to hear anything when you call if it is not in loudspeaker mode is a different issue that I can only reproduce in 101
kingvortex said:
Well, I like Chrome, so I will live with it.
Thanks for the advice though.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Disable chrome and install chrome beta the issue doesn't seem to be there
Sent from my C6603 using Tapatalk
This is not problem with this 101 rom. I'm back to 4.2.2 A.2.67 and there is the same problem. Probably Chrome make this problem
fatis said:
This is not problem with this 101 rom. I'm back to 4.2.2 A.2.67 and there is the same problem. Probably Chrome make this problem
Click to expand...
Click to collapse
Yes, that's why I posted that I have the same problem on 569 and there has already been a link posted saying it affects other devices.
Sent from my C6603 using Tapatalk
so which browser you prefer instead chrome..?
What about the internal speaker mute when receiving a call? For me this is a different issue that I only have in 101, and it doesn't help disabling Chrome
I got the same problem on 101. I'm back to A.2.67 (4.2.2) and waiting for solution or for 4.4.
I I threw out chrome so I can't test it is issue. But I think some program make this because this problem start few days ago.
Uninstall updates from Chrome (back to stock version). It helped for me.
​Chrome is becoming a bug fest, always strange things, man google is really screwing things up recently.
fernando823 said:
I had spanish generic 569, and since they didn't update yet to 10.4.1.B.101 I decided to switch to a CE one that I found here:
http://xperiafirmware.com/8-firmware/33-sony-xperia-z-c6603
The issues are:
-When I call someone I can not hear anything unless I activate the loudspeaker. This is not always happening and seems to be temporally fixed after a reboot.
-If anyone calls me, the loudspeaker is activated automatically when I pick the call (some says this is due to Google Chrome update)
-The proximity sensor that turns off the screen while talking is misbehaving
Of course I have tried again wiping everything in the flashtool, but didn't help.
Solution? I went back to the safe spanish generic 10.4.B.0.569 which they didn't updated yet to 101, maybe because they found this serious bug? I find it weird that they didn't adopted it yet
http://forum.xda-developers.com/xperia-z/general/info-firmware-version-customization-t2315914
The bug has also been posted in other forums http://talk.sonymobile.com/t5/Xperia-Z-ZL-ZR/10-1-1-b-0-101-update-problem/td-p/568927
Anyone else here can reproduce or solve it?
Click to expand...
Click to collapse
Sometimes in call, my phone activate the loudspeaker, but earpiece works well.
kingvortex said:
The loudspeaker activates randomly when I answer calls, but only from one specific contact. My earpiece works fine, however.
I'm on 10.4.B.0.569 Generic ES and I've found no solution to it. I just remember to deactivate the speaker phone when I answer calls from them.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Same here.
And, now the phone can wake when I press power button, even I close the proximity sensors.
Before, the screen won't wake up when the proximity sensor closed. So, the phone not wake up randomly in pocket.
Chrome related audio bug should be fixed today with update pushed out
Sent from my C6603 using Tapatalk
so someone find solution for internal speaker mute during a call? Is this problem with chrome too? Its working now? I
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Aruarian said:
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Click to expand...
Click to collapse
Sounds like a different issue.
Mine was a complete one of, switch made me suspect software asop issue.
Monitoring.....
Sent from my Nexus 6
Happened again, dead power button, woke by volume buttons, reboot, works fine again.
So this isn't intermittent, in that when it fails it won't work again until restart, which says to me software.
I'm now using this thread as log. To see if RMA necessary.
Chroma 5.1 22/03/2015
Sent from my Nexus 6
Happened again later in the day.
Sent from my Nexus 6
ben_pyett said:
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Click to expand...
Click to collapse
Do you have a screen protector covering the sensor? If so that's probably the issue, disable ambient display and see if you can reproduce the problem.
Sent from my Nexus 6 using XDA Free mobile app
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
ben_pyett said:
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
Click to expand...
Click to collapse
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Feature is disabled. ?
Sent from my Nexus 6
ben_pyett said:
Feature is disabled. ?
Sent from my Nexus 6
Click to expand...
Click to collapse
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
ben_pyett said:
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
Click to expand...
Click to collapse
Then short of backing up and doing a clean install I am out of ideas, sorry.
Sent from my Nexus 6 using XDA Free mobile app
Cheers. Literally only just did that for stable Chroma 22/03 version... Will wait until further versions come out and will consider doing that. Cheers anyway
Sent from my Nexus 6
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
happened to me today, like it was in a deep sleep and took ages for the power button to work.
Im on stock 5.1
Happened once 31/01 soft reboot resolved it
Still believe this is software.
ben_pyett said:
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
Click to expand...
Click to collapse
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I would get this issue on Chroma if I had enabled the option Display--Ambient Display--Overwrite Value.
See if thats enabled, and if so, try with it disabled for awhile.
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I was clean install on 5.1 but not since, although did import apps and data from TB not that it should impact it at all. Only ever run Chroma, jumped straight to it after initial unlock.
Fortunately volume keys always wake - so far.
Let me know how you get on - in this thread.
If I find it continues to happen then I'll consider clean install and then maybe even a replacement device.
Everything was fine after last reboot.
Immediately after plug in into charger, the power button stop working. First time experiencing this. Able to try this to guys?
Edit: I toggled 2 things.. Enabled / disabled ambient display overwrite defaults and screen on when plug / unplug charger..
Power button is working again without any restart.. @githyanki @ben_pyett
Hi, I get on my non-rooted phone the message in the status bar that tasker uses the battery. How can I get rid of this message?
Go to Settings>Battery, select the Settings icon in the upper right corner, then disable Power Intensive Prompt
No, that's wrong unfortunately. This will only disable the notification for power intensive apps, but not for apps that are constantly using the battery without being power intensive, like tasker. This notification is from the Android system itself. You need to disable all Android System notifications to remove it. If you don't want to do this, you need to live with the constant notification.
No, you're wrong. Since disabling the power intensive prompt I've gotten zero notifications about Tasker using battery. I've disabled none of the system notifications. I haven't had a single battery use notification since.
djparent said:
No, you're wrong. Since disabling the power intensive prompt I've gotten zero notifications about Tasker using battery. I've disabled none of the system notifications. I haven't had a single battery use notification since.
Click to expand...
Click to collapse
Does this mean you are using tasker and don't get this message?
Gesendet von meinem CLT-L29 mit Tapatalk
topcaser said:
Does this mean you are using tasker and don't get this message?
Gesendet von meinem CLT-L29 mit Tapatalk
Click to expand...
Click to collapse
100% correct. I only saw it briefly when I first got the phone, was as annoyed as you were, did some reading and found the power intensive prompt switch. I turned it off and haven't received a notification about battery use since. I've even double checked my notification settings after the other fellow claimed I'm wrong but I can assure that I've not turned any notifications off in the system. It's possible we're on different EMUI versions that are behaving differently but turning off that switch should keep the system from alerting you of further battery use.
I have a Samsung Galaxy Watch and a Samsung S10 phone. Several times over the past week or so, my watch battery has completely drained in about an hour. I only notice when it vibrates at 15%. There doesn't seem to be anyway to get a notification either from the watch or through the Samsung Wearable app when it reaches 30% instead of 15%. Is there a way to create a task on the phone to notify me when the watch's battery level reaches 30%?
Thanks.
Sorry I have no answer to your question but as a user of the gw myself, what are you doing to drain the battery that fast? Do you have the 42 or 46mm version?
Gesendet von meinem HD1903 mit Tapatalk
xe0r said:
Sorry I have no answer to your question but as a user of the gw myself, what are you doing to drain the battery that fast? Do you have the 42 or 46mm version?
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
I have the 42mm. Unfortunately, I'm not doing anything. It is a bug with the watch (or phone). It happens to my husband's 46mm as well. It will suddenly just become unresponsive and burn through the battery. It can drain a full battery in about an hour. Several times, I've charged it completely before bedtime, put it on to sleep, and then sometime during the night it'll drain and turn off. Happens randomly during the day, too.
That for sure makes the watch unusable. I am using the 46mm variant and use it heavily for tracking sports and / or use the navigation while sport (eg riding bike). Even with this heavy usage I never had less than ~40% in the evening. For everyday use I get 3 days with 30 percent left with my medium usage setup, if I switch off some sensors I would even get more I guess. That's what you can take as a comparison for the 46mm watch.
Now how to get there? Don't try to spend time into tracking this drain with tasker or whatever, instead pull it by the root. Sounds like some app is misbehaving (in the background?). I would try to start looking for apps on the watch. What 3rd party apps do you AND your husband have both installed? Remove them, one by one, and watch the result. I have only 3 3rd party apps (GPS navigation, wrist camera and watchevents). If it doesn't get better after you only have the stock apps installed, you unfortunately have to make a reset to the settings. If the behaviour comes back after the reset with only the stock apps, send it back if you still have warranty.
Btw, you know that you can see the apps that are running in the background on the watch? I put this overview on the double tap action on the home button. You can also use this for further investigation, like close all apps instead of one, like the suspicious one and so on...
Keep me updated on the results!
Gesendet von meinem HD1903 mit Tapatalk
*Edit*: just some typos.. =)
xe0r said:
Btw, you know that you can see the apps that are running in the background on the watch? I put this overview on the double tap action on the home button. You can also use this for further investigation, like close all apps instead of one, like the suspicious one and so on...
Click to expand...
Click to collapse
How do you see which apps are running? I know through the Samsung Wearables app that I can see what apps have used the most battery since last charged, but unfortunately that is no help in this situation. I just removed a couple of apps that were on the watch that I don't use (Samsung Flow, and one or two others). Now the only uninstallable apps are Timer and Stopwatch. Everything else is a stock app (most of which I never use).
Thanks.
I don't know how it is called in English, so I roughly translate it on the fly:
- Settings
- Expanded settings (4th entry with the orange gear and plus sign)
- Double tab home button
- tick recent apps --> [x]
Now you get an overview of the open apps when you do a double click on the home button.
Why does it not help to see which app is using the most battery in the wearable app? Whas it a 3rd party app? System app?
Gesendet von meinem HD1903 mit Tapatalk