Related
my defy is just 2 weeks old and i have started experiencing trememdous lags....
its 2.2.2 running , kernel is 2.6.32.9-g0671d13 , just in case it could help in finding a solution...
1. the screen goes off on its own half of the time (even though the time out is of 1 minute) and even when i unlock it , it again goes off.. ITS REALLY FRUSTRATING
2. i have just 1 game installed, but even then the phone lags a lot, the game lags and so does the entire phone..!
3. the internet isnt getting activated (i guess thats a network problem though), anyone with a similar problem!?
please post replies as soon as possible..
well i too experience the same, mine is 30 days old...
I have disabled gps/data/wifi/auto brightness to get max battery yet it fails to go beyond 1 day even if i use max an hour of wifi.
screen going blank on it own is frustrating
moto widget for time and date does not keep current time
lag in touch even after running ATK on auto aggressive mode
defy is running indian 2.2.2
p.s. any idea if i can get data on first date of use for battery? I somehow feel a new one should give more standby life.
my phone does last around 1 1/2 days with an hours gaming....and it does keep the current date and time (as of now)...
mine too lags inspite of the ATK being on autokill.... even the homescreen takes time to load after pressing the home button ...
Might want to try getting rid of ATK.
Tasks/services run for a reason on android. When something kills them, they'll start back up, causing more cpu and memory usage than if you'd just leave the service running.
Run for a reason, but not necessarily a good one. Stock motorola/vodafone firmware that I had on my defy would run many completely irrelevant processes - VF360, newsandweather, amazon mp3, etc. Task killing isn't the solution because they just start up again.
The best way to get best performance from the phone is to install CM7.
You could try to wipe in stock recovery. Check http://forum.xda-developers.com/showthread.php?t=1216982, point witch says Froyo laggy. You will lose all data.
If you find it laggy afterwards, you will never be happy with the preferments on stock froyo. Then try CM7. You will be able to downgrade to send it to warranty as I also did this. It is quite a difference.
shreymehta said:
1. the screen goes off on its own half of the time (even though the time out is of 1 minute) and even when i unlock it , it again goes off.. ITS REALLY FRUSTRATING
Click to expand...
Click to collapse
Is it going off while you are holding it by the top, with a finger on the left of the speaker hole?
If it is the case, it is because you are masking the proximity sensor. And if you have the "Pocket detection" feature activated, it will cause this annoying stuff...
Well not to worry even mine was laggy before, i had just installed 2-3 apps. I had to restart my phone at least once then i installed cm7 rc1.5 Now its very fast and i dont remember the last time when my phone was lagging and freezing.
I guess it has something to do with the froyo and motoblur on defy that makes it laggy.
You have to have get rid of stock froyo after owning a defy.. thats the truth..
I did a readup on the ATK stuff and the excerpt from the and dev documents... well since the read i have uninstalled all task killers... (kept one just in case with all auto actions disabled)
I do hope the lag issue is resolved after moving to CM7/Jboogie3 etc
however the battery issue is a major hurdle for now as one day is too less, i probably have to take it to the service center for a checkup and/or claim warranty on battery. till them no flashing for me...
att: patriiice - even when the proximity sensor is not covered, i do experience screen blanks, almost immediately asa the power button is pressed to wake the device.
The lag presented on the Defys running Froyo is a "super nice feature" by Motorola it has an easy fix tho.
Its caused by the VM consuming all memory, all its needed is adjusting the amount of MB the VM should leave free.
There are a few ways to it:
1) Run a terminal emulator, or use GScript Lite to run this:
su
vm.min_free_kbytes=8192
(Not permanent, need to be ran every time you reboot)
2) Get Sysctl from market and do it from there.
3) Get SetVSel and do it from there.
Lag
I have that problem to. The bad thing is that i can`t answer call during the lag, it says i have my phone is closed or i don`t have signal. I`ve installed Temp+CPU and during lag it shows that the proc is running at 100%. Memory has all the time, around 130 min and 230 max. Closed all programs one by one, no change. I restart the phone and everything is running smooth and it lasts max 1 day. i have stock rom 2.2.2. (please excuse my spelling)
mmariann2001 said:
I have that problem to. The bad thing is that i can`t answer call during the lag, it says i have my phone is closed or i don`t have signal. I`ve installed Temp+CPU and during lag it shows that the proc is running at 100%. Memory has all the time, around 130 min and 230 max. Closed all programs one by one, no change. I restart the phone and everything is running smooth and it lasts max 1 day. i have stock rom 2.2.2. (please excuse my spelling)
Click to expand...
Click to collapse
I also use 2.2.2 stock and my defy runs without lag... you should consider to root the phone and freeze some unnecessary stock-preinstalled apps like Kindle, Voice command, etc... the ones you will never use. I freezed about 20 apps and there is no lag at all. (I even froze Maps, Streets, SIM toolkit, and some others)
Zephyrot said:
The lag presented on the Defys running Froyo is a "super nice feature" by Motorola it has an easy fix tho.
Its caused by the VM consuming all memory, all its needed is adjusting the amount of MB the VM should leave free.
There are a few ways to it:
1) Run a terminal emulator, or use GScript Lite to run this:
su
vm.min_free_kbytes=8192
(Not permanent, need to be ran every time you reboot)
2) Get Sysctl from market and do it from there.
3) Get SetVSel and do it from there.
Click to expand...
Click to collapse
My Defy was lagging until I rooted and installed SetVSel. Now its running as breeze with Stock Indian Froyo.
stock froyo is not good but it shouldn't be that bad. there were some faulty battery issue that i have heard of before too. but in your case your defy might even be faulty. so i would suggest you get it replaced or fixed under warranty first before flashing any custom rom.
lag on defy
with rootunistaller i`ve frozen skype and yahoo and i haven`t had any lag since. If i want 2 use them "defrost" and when i`m finished i just "freeze" back the app
mmariann2001 said:
with rootunistaller i`ve frozen skype and yahoo and i haven`t had any lag since. If i want 2 use them "defrost" and when i`m finished i just "freeze" back the app
Click to expand...
Click to collapse
Easy as that...
Lag on defy
Nope. I was wrong after 3 days of normal proc usage it started again. I`ve installed OS Monitor (free on market) and there was a process the ate all my resources: "DRM Protected Content Storage". Selected watch log and there was something like "enter,delete update, uri: content://media/external/audio/media/1 ../44.... /254..."
This process is searching ur phone for media, video audio and looked like it was stucked at this folder. I`ve searched the phone for that folder but couldn't find it so i just killed the app in OS Monitor. After the process restarted at log was showing "media search finished:182 audio files found and 1 video found". Looks like that's my problem and maybe yours to. Cheers mates
so I might visit the service center this weekend to have my battery life checked.. one day life with all wifi/data/gps disabled and below average voice calls is not acceptable at all.
what is stock recovery?? and will it void my warranty???
thanks a lot guys for ur replies!!
but the thing is my phone has become even slower!!
when i first switch on the phone i have around 240MB free RAM but just after an hour everything becomes too slow, even opening of the menu! and after 2-3 hours of usage it keeps on reducing and finally reaches as low as 40MB .....
what could be causing this??
i have android assistant by which i clear cache, ram still it doesnt help....
So today I've installed latest MaximusHD rom for HTC One X, and everything is super fine, except for one thing - when I'm trying to connect to my Skydrive (using official app) while on Wi-Fi I just can't do it. After awhile it just says that I should check if I have a connection. The problem does not occur when I switch to Data Transmission. Other apps usually are able to connect but it seems slower than when using Data Transmision.
I have installed the WiFi update, and when using Google Play, or browsing the internet it seems to work just fine... I also switched from Superuser to SuperSU, but the problem occured before that so I don't think it had anything to do with that (noob question - which should I use? Superuser was there by default, but is ist actually better, or there is no big difference?)
Have you tried uninstalling and then reinstalling the app?
Sent from my HTC One X using xda app-developers app
Yep.
seedubya said:
Have you tried uninstalling and then reinstalling the app?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I tried, it's still very slow.
Other odd thing is that when I turn on Data Transmission it's always showing the "H" symbol, even in the places where it previously showed "3G" or "3.5G", now it never switches. What does it mean? The speed seems fine though.
This happened to me too. And it's happening to YouTube and google play.
Could it be because I didn't do the OTA update?
In that case i have a little question: if I update the OTA do I/will it wipe all data?
mortix02 said:
This happened to me too. And it's happening to YouTube and google play.
Could it be because I didn't do the OTA update?
In that case i have a little question: if I update the OTA do I/will it wipe all data?
Click to expand...
Click to collapse
Well I did the OTA update almost right away (after intalling few apps), and I saw the problem after that, so I don't think it has anything to do with that although it's suppose to fix WiFi. Oh and it didn't wipe my data.
EDIT:
Well I can't post in MaximusHD thread yet so I'll ask here, does everyone using this rom experience such a tremendous drop in battery life when using Data Transmission? On WiFi it's normal, but when using cellular it drains 5-10% in 10 minutes... That seems absurd.
bump. Seriously? Anyone knows if this problem with power drain when using cellular data transmission is also present in other clean Sense 5 Roms? Or is there a way to fix that, or maybe there is an update underway?
I just switched ROMs but was getting a full days use out of a charge. WiFi at work and home all day. So I never really used hspda.
Sent from my Avatar ROM that kicks buttski!!!
kolas310 said:
Well I did the OTA update almost right away (after intalling few apps), and I saw the problem after that, so I don't think it has anything to do with that although it's suppose to fix WiFi. Oh and it didn't wipe my data.
EDIT:
Well I can't post in MaximusHD thread yet so I'll ask here, does everyone using this rom experience such a tremendous drop in battery life when using Data Transmission? On WiFi it's normal, but when using cellular it drains 5-10% in 10 minutes... That seems absurd.
Click to expand...
Click to collapse
Yes! It does this for me too. It seems to drain at something like 1% per minute for me when I have mobile data on. Wifi also drains it quickly, but not as fast. I posted about this in the Maximus thread (some other issues too) but nobody has replied. Good to know it's not just me.
Nasalhair said:
Yes! It does this for me too. It seems to drain at something like 1% per minute for me when I have mobile data on. Wifi also drains it quickly, but not as fast. I posted about this in the Maximus thread (some other issues too) but nobody has replied. Good to know it's not just me.
Click to expand...
Click to collapse
Yep, hopefully there is going to be some kind of fix, I really wouldn't like to go through the whole configuration, app instalation, etc. process again.
Ok, so another thing is - some icons in one of the folders on my home screen disapear. It's always in the same folder, and only in this one, others seem to be unaffected.
kolas310 said:
Yep, hopefully there is going to be some kind of fix, I really wouldn't like to go through the whole configuration, app instalation, etc. process again.
Ok, so another thing is - some icons in one of the folders on my home screen disapear. It's always in the same folder, and only in this one, others seem to be unaffected.
Click to expand...
Click to collapse
Issues I'm having:
1. Crazy battery drain when I enable wifi, but particularly bad when I enable mobile data. I have a Tasker profile where if I enable wifi and connect to my home network, autosync and GPS are enabled for 2 minutes then disable themselves. Last night my phone was on 61%, I enabled wifi, and immediately it dropped to 56%.
2. When I go to bed at night I turn my phone off. If I put it on charge at night it gets to a certain point and the phone switches itself on! One night last week it switched itself on at about 89%, so I switched it off again, and about ten minutes later it switched itself on again!
3. I use Google Calendar, not the HTC one. I seem to be unable to disable the HTC calendar - the only option is to "freeze" it in my backup app.
Aside from these things, I really like the rom, but these three issues are making me wonder if I should try something like ARHD and see if the same things are present there.
Nasalhair said:
Issues I'm having:
1. Crazy battery drain when I enable wifi, but particularly bad when I enable mobile data. I have a Tasker profile where if I enable wifi and connect to my home network, autosync and GPS are enabled for 2 minutes then disable themselves. Last night my phone was on 61%, I enabled wifi, and immediately it dropped to 56%.
2. When I go to bed at night I turn my phone off. If I put it on charge at night it gets to a certain point and the phone switches itself on! One night last week it switched itself on at about 89%, so I switched it off again, and about ten minutes later it switched itself on again!
3. I use Google Calendar, not the HTC one. I seem to be unable to disable the HTC calendar - the only option is to "freeze" it in my backup app.
Aside from these things, I really like the rom, but these three issues are making me wonder if I should try something like ARHD and see if the same things are present there.
Click to expand...
Click to collapse
Well I don't know how it is with the phone turning itself on, because I'm not turning it off to begin with.
The thing with calendar - it seems to me it was also like that when using official Sense 4+, so I don't know if it's fixable.
I think I'm going to switch to ViperX Sense 5 Rom, people seem to say good things about battery life in this one.
kolas310 said:
Well I don't know how it is with the phone turning itself on, because I'm not turning it off to begin with.
The thing with calendar - it seems to me it was also like that when using official Sense 4+, so I don't know if it's fixable.
I think I'm going to switch to ViperX Sense 5 Rom, people seem to say good things about battery life in this one.
Click to expand...
Click to collapse
Yes, I know some people think the idea of switching a phone off is somehow weird, but I turn mine off at night. As an experiment I just switched my phone off here in work, plugged it in to charge it (it was on about 93% - charged overnight and it has lost 7% since I switched it on when I got up for work at 5.30) and lo and behold it powered itself on when it reached 100%. I don't want this to happen.
The calendar on Sense 4 could be disabled - I know this as I had it disabled! I prefer the Google calendar, so I disabled the HTC one. On this ROM you can only hide it, or backup apps allow it to be frozen, which is what I've had to resort to.
Nasalhair said:
Yes, I know some people think the idea of switching a phone off is somehow weird, but I turn mine off at night. As an experiment I just switched my phone off here in work, plugged it in to charge it (it was on about 93% - charged overnight and it has lost 7% since I switched it on when I got up for work at 5.30) and lo and behold it powered itself on when it reached 100%. I don't want this to happen.
The calendar on Sense 4 could be disabled - I know this as I had it disabled! I prefer the Google calendar, so I disabled the HTC one. On this ROM you can only hide it, or backup apps allow it to be frozen, which is what I've had to resort to.
Click to expand...
Click to collapse
Well then since nobody seems to know what to do in our instance, and I have no idea if there is some kind of update for MaximusHD underway, we propably will have to switch the Roms. I usually had the mobile Data Transmission turned on all the time when outside my apartment and while it did drain the battery more than WiFi it still was enough for 8+ hours of being on with medium usage (sometimes with battery saver option ticked when I needed to be outside for a longer period of time). Now the phone would be dead after few hours.
EDIT:
Today I switched for ViperX Rom, and all of the issues I wrote about seem to be gone, Skydrive app no longer has any issues with connecting. Although I'll say something more about batery life in 2-3 days when I'll actually have a chance to see how it works. In general I can say that this ROM is a lot more customizable, and has lots of tweaks (greeat ones) I haven't seen in Maximus, but still I'll wait for a few days with my final opinion.
Ok so after using it for a few days I can tell that the ROM itself is just better in sheer terms of funcionality. First thing I noticed is that I can now put more than 16 shortcuts into Folders, the icon grid in app panel is 5x6 so now I have 3 pages to scroll instead of 7. WiFi seems work more stable but I can't say that it worked bad in MaximusHD. When it comes to battery drain while using Data Transmission - it's still there, but after a few cycles of charging it seems to get better bit by bit, if it still changes I'll let You know. ROM comes with lots of additional tools, and allows heavy customization, and reclocking the processor for better battery life. And that's just the tip of the iceberg. I don't know what about the phone turning itself on, because I don't switch it off. In terms of the callendar I also use gogle one and I just turned of sync options in the one provided by htc. Also I'm not sure if while installing the rom You are able to choose not to install the HTC callendar.
kolas310 said:
Ok so after using it for a few days I can tell that the ROM itself is just better in sheer terms of funcionality. First thing I noticed is that I can now put more than 16 shortcuts into Folders, the icon grid in app panel is 5x6 so now I have 3 pages to scroll instead of 7. WiFi seems work more stable but I can't say that it worked bad in MaximusHD. When it comes to battery drain while using Data Transmission - it's still there, but after a few cycles of charging it seems to get better bit by bit, if it still changes I'll let You know. ROM comes with lots of additional tools, and allows heavy customization, and reclocking the processor for better battery life. And that's just the tip of the iceberg. I don't know what about the phone turning itself on, because I don't switch it off. In terms of the callendar I also use gogle one and I just turned of sync options in the one provided by htc. Also I'm not sure if while installing the rom You are able to choose not to install the HTC callendar.
Click to expand...
Click to collapse
I've gone back to my old Orange-branded 4.1.1 / Sense 4+ build. Battery life has gone through the roof, HTC calendar is disabled, everything works, no problems. As for the phone powering itself on, well, something odd happened there...
When I decided to go back to the old build I restored my Nandroid backup and reflashed my old boot.img, taking the phone back to its old setup, and all seemed well, but that night I switched it off at bedtime (still find it weird that so many people think I'm freakishly odd for daring to switch my phone off from time to time) and lo and behold, some time later, it switched itself on again! The next morning I did some searching about removing the Clockworkmod recovery, followed the instructions, and also relocked my bootloader for good measure, and guess what? Since then it hasn't powered itself on while charging. So all I can gather from this is it was either Clockworkmod or having an unlocked bootloader that caused my phone to power itself on, because as soon as these two things were changed it has behaved normally.
So anyway, I'm going to stay on this build until Orange get around to releasing 4.2, or my contract expires in April, whichever comes first. Probably the latter, as according to a post I've seen from Orange themselves they reckon the update will appear 3-6 MONTHS after the manufacturer releases it.
Nasalhair said:
I've gone back to my old Orange-branded 4.1.1 / Sense 4+ build. Battery life has gone through the roof, HTC calendar is disabled, everything works, no problems. As for the phone powering itself on, well, something odd happened there...
When I decided to go back to the old build I restored my Nandroid backup and reflashed my old boot.img, taking the phone back to its old setup, and all seemed well, but that night I switched it off at bedtime (still find it weird that so many people think I'm freakishly odd for daring to switch my phone off from time to time) and lo and behold, some time later, it switched itself on again! The next morning I did some searching about removing the Clockworkmod recovery, followed the instructions, and also relocked my bootloader for good measure, and guess what? Since then it hasn't powered itself on while charging. So all I can gather from this is it was either Clockworkmod or having an unlocked bootloader that caused my phone to power itself on, because as soon as these two things were changed it has behaved normally.
So anyway, I'm going to stay on this build until Orange get around to releasing 4.2, or my contract expires in April, whichever comes first. Probably the latter, as according to a post I've seen from Orange themselves they reckon the update will appear 3-6 MONTHS after the manufacturer releases it.
Click to expand...
Click to collapse
Heh I'm alson in Orange (poland), and we got info that the update will show up sometime mid-december. I just got tired of waiting for them to update that's why I ended up with custom roms.
Maybe it was CM fault? I'm using TWRP, tonight I'll turn it off and see if it powers back itself during the night and let you know.
Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....
These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).
After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!
Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.
zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.
Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain
My battery suddenly started draining rapidly earlier today. I normally get through a full day after charging overnight, but today the battery was down to 15% after 8 hours with the same amount of use as I do normally.
I let it die out completely since I didn't have my charger with me, then did a full charge once I got home. I took it off the charger and within 3 hours it is back down to 15% again. I have barely even turned the screen on except to check a few incoming messages.
I have just done a cache wipe in the hopes that it will fix itself. Is there anything else I could try? I'm completely baffled.
Well, i was facing same thing untill i did few tweaking like-
1. Go in auto start manager and ****ing close every useless social app(FB) they will suck it up
2. Choose power saver mode u like or use customized one
3. Do not use live wallpapers, well i use to change my wallpaper randomly every 30 minutes
4. Delete useless apps and pray to god that ur battery works like it used to
5. If you wont mind using any custom rom, then install echoe rom its based on stock rom nothings changed much except better battery and performance , i have used it and its awesome i totally recommend it
IGN-10/10
M facing this issue after updating to .165 official update
NiTesh said:
M facing this issue after updating to .165 official update
Click to expand...
Click to collapse
I'm on the .165 update also, since 3 days ago. It was fine until yesterday.
android lover 2000 said:
Well, i was facing same thing untill i did few tweaking like-
1. Go in auto start manager and ****ing close every useless social app(FB) they will suck it up
2. Choose power saver mode u like or use customized one
3. Do not use live wallpapers, well i use to change my wallpaper randomly every 30 minutes
4. Delete useless apps and pray to god that ur battery works like it used to
5. If you wont mind using any custom rom, then install echoe rom its based on stock rom nothings changed much except better battery and performance , i have used it and its awesome i totally recommend it
IGN-10/10
Click to expand...
Click to collapse
Thanks for those tips. I have all of that set up already. Custom power saver profile, all unnecessary apps removed or disabled, including auto start manager.
I have not rooted my device, only had it a month so I want to preserve warranty status.
I waited a couple of days to see if the battery would sort itself out, and it did.
Battery life has actually now improved slightly from what it was before the random drain happened.
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
i have samne problem on 8.8.16
Just uninstall CPU Z and accu battery problem solve
iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Problem will back soon on stock kernel
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Actually bad solution, you know
Zanr Zij said:
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
Click to expand...
Click to collapse
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
iFreeMan said:
Actually bad solution, you know
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
Click to expand...
Click to collapse
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly.
Try to boot to safe mode for several hours to check if it really caused by user app. Turn off your phone > Hold power to turn on > As soon as mi logo appear, quickly hold volume down until the phone finish booting (can be up to 30 seconds). You should see "safe mode" watermark at the bottom left corner, indicating all user app has been temporary disabled. Leave it for several hours to see if the battery still drain or the phone stay awake all the time (high cpu usage). To exit from safe mode, simply reboot.
I always found it is kind of a habit to blame MIUI for everything. I am not defending MIUI here, they bloat a lot. I also hate it and I am using RR now. But on several occassions when we troubleshoot, we found out it is one of the user app that cause the trouble, ads, or slow charging; not anything related to MIUI. Blaming MIUI won't solve the problem, only troubleshooting will lead us to the real culprit. In your case, it still can be caused by the MIUI itself. But until you troubleshoot it out, you won't know who is the real culprit.
For comparison, when still using MIUI 9.5.17.0 I can easily achieve 10+ hours SOT within 1,5 days (max is 14 hours). When switched to RR, affected by the wifi deep sleep drain, I rarely get 10 hours SOT anymore. Still in the process of troubleshooting the problem.
Zanr Zij said:
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Click to expand...
Click to collapse
I don't mind to have additional applications.. But I don't like when my CPU works incorrect O_O
Desmanto said:
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly..
Click to expand...
Click to collapse
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
iFreeMan said:
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
Click to expand...
Click to collapse
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Desmanto said:
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Click to expand...
Click to collapse
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
iFreeMan said:
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
Click to expand...
Click to collapse
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Desmanto said:
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Click to expand...
Click to collapse
Yes, I understand that and understand why it would occurs and tried to investigate in this way, but...
I have equals application list which I had on previous device except...CPU-Z and AccuBattery (the AccuBattery for now is removed) because of I faced with this frequencies issues.
This morning it happened again. But I just.. woke up, saw on frequencies - everything OK. Then I just.. Instagram, Telegram, Facebook Messenger and Google Chrome and no more. Then I realized that the phone became a bit warm.. I saw on frequencies - it was locked again
As it happened, I've came to office, connected via ADB to laptop and made several screenshots from `top` utility and looked a bit into `adb logcat`. But nothing... IDLE ~798%. And then I've tried to go to all apps and do force stop for ALL apps. But nothing.
I just rebooted device again...
Please look on it.. https://drive.google.com/open?id=1yXjQQ4rsF3MURh1PF0DZ1Z_Gtgc4-m4_
Just concerning about.. there are a lot errors in logcat. But I understand that.. that's ok.
But 90% of logs flowing from system processes, not from apps. But there is nothing critical.. Nothing something what could flow unstoppable text and caused over-loading CPU.
I'm afraid that it could be manufacturing defects
I event tried to re-flash firmware with fastboot (I thought that byte-by-byte flasing into ROM memory could fix some random small issues). But after flashing with fastboot this CPU locking happening again.
Actually.. dunno what to do with that. The last thought to try any custom ROM (may be Lineage OS) with custom kernel and make sure that it is just bug in Xiaomi's ROM..
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
iFreeMan said:
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
Click to expand...
Click to collapse
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Desmanto said:
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Click to expand...
Click to collapse
I just used custom firmware just for check is that factory defect. But seems that's issue only with xiaomi's firmware.
Yes, I thought that could be governor likewise. But.. Don't think so, because this low-level things, I think, debugged and enhanced successfully by default. Seems some conflicts between system applications.
On custom ROM I haven't faced with this issue, so...
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
iFreeMan said:
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
Click to expand...
Click to collapse
Yes, I've got first lock on maximum frequencies.
So, after researches.. I could say that it's a bug in xiaomi firmware. Definitely.
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
marc_alv said:
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
Click to expand...
Click to collapse
I have no problem with Miui based custom Rom + custom kernel
Zanr Zij said:
I have no problem with Miui based custom Rom + custom kernel
Click to expand...
Click to collapse
Could you specify the rom and kernel, please?