Related
Ok. My first post, so hello everyone, I'm the new noob on this forum If you don't know what I'm talking about - see the damn movie, noob
To the gist:
1) I noticed a couple of similar topics on phone-specific forums, went through them (unbelievable how much flaming and bs is there on this forum, by the way), but it seemed like most of them were purely guessing as to what may be the cause of drainage. If I missed something I'll be grateful for links
2) I'm using a Samsung Galaxy S2, but I post it here since I noticed other phones with Android (including those with new Gingerbread) have the same issue - the battery is being drained enormously when the phone signal is poor, so I think it might be an OS issue rather than a particular device
I had SGS2 for almost 2 month now and only today did I notice a huge drop in battery life. From 5 to 6 days (this is not the thread for battery life tips. Send me a PM if you want to know how and what I did to get it last so long or I can post another topic on the SGS2 forum and explain everything I've done to my phone, just don't spam this thread) to around 1 day (it's been 22,5 hours and the battery level is 27%)
The only thing that changed is my phone signal - I live in the centre of a town so usually the signal strength is good, but I had a really windy weather and I guess something got destroyed, as I had to try around 5 times even to send a text message. Anyways, this is where the guessing part comes in - with usually 5, 6 days on a battery I can pretty much rule out everything else than phone signal since I don't use anything else (hubs social, music, etc. uninstalled, voice search and voice command uninstalled, StreetView uninstalled, etc. All via TitaniumBackup)
Spec (not sure what might me useful, posted what think may be the basics):
- Android 2.3.5
- Baseband: I9100XXKI4
- Kernel: [email protected] #20
- VillainRom 3.0
- Free version of LauncherPro
- I have wifi, gps, bluetooth off, I turn them on only when I need them; same with data network mode, but I hardly ever use it and I didn't turn it on today anyway
- no fancy widgets, no fancy processes in the background
- I used my phone as I usually do - some calls, messages, some music, bit of market and web browsing on wifi
The question is not about battery life itself or battery saving tips but about how the Android system handles signal searching and what does it do when the signal is weak. I assume similar battery drainage would occur in every-day situations, f.e. while using the tube, tunnels or living in some mobile-network ****-hole
Any ideas on a specific cause? Any on how it may be improved? I'm not thinking about software-side, like turning on "Flight mode" or some apps (though I'll be grateful for any ideas). I mean more of an OS solution, maybe something will help to improve Android further
My first post and end
Hi guys,
I am the owner of an Ascend P1 Huawei and I am running a stock firmware not officially released from the constructor but a stable version.
It never goes in deepsleep except when it is on plane mode so I started to search some solution and I started analysing my phone with Wakelock Detector.
It gives me a result of about x1200 wake call from AlarmManager and Android OS with the most percentual of battery drain.
After that I've tryed to access the AlarmManager.txt o AlarmDump.txt but probably the indications that I found on the differents threads on this forum doesn't work or probably this file has a different name on my phone.
So anybody can help me to access this file? I need it to understand which application of the system is keeping awake my phone.
P.S.: When I got these results I had a factory resetted phone so I had no app and I didn't make calls or data connection.
Thank you so much for the help!
EDIT: I've got the files I was looking for, someone can help me to understand where is the problem
Q&A for [ROM][4.4.4r2]p6800/p6810/i815(12Sep2014)CarbonROM Kitkat Unofficial
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth (BlueZ) issues on Samsung Tab7.7 CarbonRom (latest by Daniel_hk)
Hi!
Having flashed this http://forum.xda-developers.com/showthread.php?t=2723126 pretty one, I've experiencing unstable bluetooth connection with almost everything. Philips bluetooth music station connects after 10 seconds only for half a minute then drops (i can see a slight screen flash-redraw on the phablet), car multimedia does not discover the phablet as a 'phone' device (only audio), which means no convenient hands-free for me. And I'm not alone to these problems: http://forum.xda-developers.com/showpost.php?p=55861531&postcount=103, 'alnon' describes same issue.
Can someone check out this ROM and/or confirm this bug? Also, if anyone knows of a solution/fix, please advise!
A Big Thank-You to Daniel
I've used some of Daniel's roms before, but I have to say that the Carbon rom is by far the best -- fast, with low battery usage, and a chance to use KitKat.
Thanks.
Samsung Tab 6800 CarbonRom
Hi,
I just installed the unofficial CarbonRom(4.4.4) release on my Samsung Galaxy Tab P6800. I upgraded from official rooted ICS using TWRP. The tab boots up fine but hangs within a minute of operation. Please help and let me know if you guys have any ideas on what is causing this.
Regards
Here I installed last build (december one) and bluetooth cant receive files from another android, neither can turned off. I have a p6800.
Bluetooth bug... cant turn off
I really like this carbon Rom. It runs like a Mercedes SL. But i have one big problem,. Once i turn on Bluetooth, i am not able to dissable it. Every time i try to switch it of, it turns on itself short time after again. I think it is the so called "cant't turn oft issue". But i cant find a solution to fix this. Actually Bluetooth is always in in my Device. But i dont need it.
Any help would be great
Best regards
Litreb
problem accessing internal memory
guys, i have some problem after intall this ROM. first step before install this room , i do wipe data and cache from boot recovery and install via CWM. but after finish installing, when i try access data in the internal memory, i got empty data, i think all data in teh internal memory has been formatted. But.. when i try to installing once again, when using option select zip from internal memory, all folder in the internall memory has appear. so i canceling to install and try to open data again, but the internall memory was empty, different when i looking from recovery mode before.
so. is it normal? how i can access again data that doesn't appear when open in normal mode? thanks a lot
Bluetooth problem
Hi there,
I was reading for years until I yesterday decidet to flash (from stock) to this rom.
All went fine (besides a corrupt backup, sh. happens)
All seems to work besides: bluetooth.
I thougt there should be no Bluetooth issue with this rom?
I can turn BT on or off, but the Tab doesn't find any bluetooth device.
I canNOT turn on its visibility for other devices. Its not found by eg. my pc.
Anyone who had the same problem?
With stockrom it worked all fine, no hardware change.
THANK YOU - to anybody who finds some minutes to care about a newbie
dvorak104
This Build work well except Bt
I installed the 12 december version with opengapps nano GAPPS package. But I get a horrible wakelock on google play services, no matter what I try. I can't seem to track it down or solve it.. (tracked it down with Wakelock Detector, GSAM Battery Monitor). It's preventing deep sleep. Any tips?
Tab 7.7 CarbonRom KitKat starts automatically when charging
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
memunnik said:
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
Click to expand...
Click to collapse
The automatic reboot when charging was a bug in the old Kitkat Rom's that Daniel fixed with Android Lollipop rom's, its a feature of those builds.
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
I thought im the only one having this bluetooth issues..
If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk
abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.
I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!
vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.
I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.
vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF
Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Maybe found the culprit? How to remove it? :/
Just in case anyone actually cares, I may have found some useful info...
Facebook Messenger has been very resource hungry and unstable... In my culling of apps I'm noticing it is the most resistant to being uninstalled. No matter how I find the app (in Rom Toolbox, App manager etc) - it won't let me kill it fully.
Attempting an uninstall of Messenger triggers an immediate crash/reboot.
How can I completely obliterate it?
Loopster said:
Hi there-
My Galaxy S2 just last night started with some new weird behaviour. I had tried to use it for navigation earlier in the evening and left WiFi and GPS on accidentally... an hour or so later the phone was running hot and started rebooting (has never been super-stable, so I wasn't too concerned) - charging overnight and now the phone insists on rebooting after about 1-2 minutes.
Have rebooted into SAFE MODE, and things are relatively ok, until I open the SETTINGS> APPLICATION MANAGER... which triggers a crash/reboot almost immediately.
I've not installed any new apps for some time (nor bothered with any regular virus scanning) - and am not sure what's up with my phone.
I'd really like to avoid having to re-flash/factory reset... as getting one's phone back to "normal" can take months!
Any helpful input would be most appreciated.
Thanks in advance!!! =)
Running Android 4.3.3 JellySNAP ROm, Kernel version: 3.0.101-Apolo_4.13_Regular-gf40153f
[email protected] #603
Build number: JSRA K47|=|v7.0
Click to expand...
Click to collapse
I managed to "freeze" messenger with a lot of luck... though I can't remove it. Phone is kind-of ok... unless I open the Application Manager.
Seems Messenger doesn't want me even looking at it! (Instant reboot)
Any ideas how to remove this awful program?
Hi there,
You'd be best served asking for help from the experts who own your device here:
[Q&A][SGS2][Newbies][Experienced Users][RCs] New members friendly Q&A thread
Good luck