Wtf. This never happened to me on my hero. Does anyone know why its so high.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think its ridiculous.
In spare parts it says my sensor is high for android sysyrem so I wiped it and recalirabate it and nothing.
Sent from my PC36100 using XDA App
Yeah I had a similar post right after it came out. Unfortunately, its still unknown and still happens even after patches. We'll see if the next MR fixes it, but I won't hold my breath. There's a lot of processes running under it, so figuring out which one is the cause would be pretty painful. Tap on it sometime and there's like 20 something services under Android System that are shown as having contributed. I can still manage great battery life with it doing that, just annoying that the Android system uses more of the battery than anything. Sometimes it even uses more than Cell Standby.
I feel flashing another cdma snapdragon rom like the incredible and see if it would boot and if it would have this problem. Its pissing me off.
Sent from my PC36100 using XDA App
get alogcat and see if there are any obvious error messages
here's the thing, atleast from what i've noticed, if you do alot of flashing, wether it be theme, boot anim, splash, rom's kernels, then yes you will see the android system running a high percentage, that is normal, but if you not doing any of that then chance's are it's a app that is preventing the phone from sleep, or many apps keeping the phone from sleeping, such as the Facebook bug not long ago that did that when they made the updated facebook app the first time around, till they pulled it and fixed that issue.
If you have recently been doing some flashing if your rooted, just put the phone down and leave it alone for awhile and you'll start to see the percentage drop.
Related
Um...is this normal?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hadn't really noticed a huge drain though.
Edit: I'm running DCv1.
Just checked mine. I'm at 88% display and 12% cell standby. Running Darchtrev v2.
Using DC v1
Cell Standby 70%
Phone Idle 20%
Display 8%
Android System 2%
im right there with you ajones. anybody have ideas as to why this is? i havent really seen a difference in battery life though. could just be a glitch.
Did you guys open the camera before you checked?
no. its been like that for a while. last time i used the camera was last night.
Not right before... I did use my camera today though.
I don't like telling people this because you can get in trouble by closing the wrong thing but... try a task killer and make sure the camera is completely closed.
Many Roms come with Astro of ES File Manager and those have a task viewer/killer built in.
i tried that. didnt see the camera as one of the running processes.
Maybe its an app running like goggles or barcode.
just checked. only thing that i could think of to have a hold on the camera is handcent and the messaging app. closed those. ill see what happens
*update*
so that didnt do anything. still reading at 93%. anybody have any ideas or are we just out of luck?
I check battery usage now and again and since I moved to gb you have the handy dandy graph. However as seen in the attached graph there is very strange drop I can't explain maybe some might help shed some light?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sent from "The Other Woman"
I've seen this once, after turning the phone off and putting in a diff. Battery... Could also be something else.
Would have made more sense if it corresponded to hooking up to wifi. I get over 2 days on wifi on weekends at home.
You have data corruption that's not giving you an accurate read on the battery.
Sent from my SPH-D700 using xda premium
I would get drops in my graph when my phone randomly rebooted or when the modem crashes. Check your uptime when you see those dips, it will probably correspond with those dips. At least it did for me.
Thx for the responses guys. Yea I have noticed both 4g and wifi seem to get a lot better battery life than 3g which was not the case with froyo. I figured that is what samsprint are working on. It might have been a reboot but I can't get data corruption from a reboot when I'm on rfs right? All in all I chalk it up to an unfinished build but I thought I would ask around anyways.
sent from "The Other Woman"
I've had some ridiculous graphs. Open Gaps, 90% battery loss, you name it. It happens lol.
Sent from my Nexus S 4G using Tapatalk
Turn off yur phone then back on again you'll see the exact same thing happen, and obviously since your on gingerbread, it was a reboot, which is common with the leaks.
Sent from my SPH-D700
You all sammy fans are know about our famous super villian Android Os high battery usage bug
I was so tired of that because i love sgs2 madly
So here is my words. JUST DONT TAKE TENSION OF ANDROID OS AND DONT LOOK AGAIN AND AGAIN FOR BETRERY STATUS YOU BUY YOUR PHONE FOR USING IT NOT FOR MAKING IT A ANOTHER TENSION IN YOUR LIFE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am using now samsung galaxy s2 which i bought used and it is from O2 mobile Uk
So first of all when i install 2.3.5 official in my phone its work good android system goes to near 14% and android OS goes to Like 5-9 percent
But when i try to pull something like 2.3.6 with odin it cause me problem of high battery usage again
So i do some research and what i did is flash 4.04 in ny phone
But thats not a full story i root it and install root exploler
And i unistall all ****ty apps like samsung hub,even gmail email
Yeah i am saying it correctly i didnt freeze them i just delete or uninstall them
And yeah problem solved
One more thing to new problem facers
Dude dont worry about that problem i check many peoples they all are facing that thing
Our Galaxy S2 is still best if you compare them will all other present smartphones
My advice is to just check if you are getting same battery timing in real which you were getting before all that
If your answer is yes then dont bother yourself with seeing battery status again and again and enjoy your phone
I hope this process will be usefull to you
I post all ****ty apps list later so you can delete them
When I got my Nexus 7 a few weeks ago I always intended to root it as soon as possible. I thought it best to leave it a while in case it died after a few days, since it would be simpler if I had to send it back.
I knew I would lose all my stuff when I unlocked it, so I just played around with different apps. I had it working with a graphic display showing battery charge details on the Pull-Down Notification Shade. The graph showed the charge state and history leading up to that time, and also prediction as to how long it would take to charge to 100% if on charge, and discharge time otherwise. I was unsure which app had created it or whether it was just a part of JellyBean itself.
This week I rooted (and backed out the 4.2 upgrade) with no problem. Trouble is though, that I have lost the Notification Screen Battery display and I can't find which app I need to get it back. I have a backup of the apps created with AppMonster Pro but none of them gets it back.
Can anyone advise me which app it may have been please.
Battery Widget Reborn:
https://play.google.com/store/apps/details?id=net.hubalek.android.reborn.beta
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exactly right.
Thanks ever so much. - It's been driving me mad for days!
For future references, couldn't you go into Play Store -> My Apps -> All Apps and look for it there? Using the same account of course, that should work?
Yes, It was in there.
Together with the dozens of other apps I downloaded whilst I was playing with the Nexus.
On the App store, it doesn't always mention sufficient detail. Certainly not Notification shade displays.
I know it's not the fastest and most efficient way, but it helped me find the app in the past, and thought it may help you.
Usually you remember the app as soon as you see it (it does stay in your subconsciousness)
Hi everyone,
I'm a bit new to this but bear with me. I got an S5 SM-G900A this week with OA1 loaded on monday night. After spending tuesday marveling at how much bloatware was on it and how horrible the battery life was I rooted and began freezing and uninstalling some apps. Day 2 with the phone was also very bad, it nearly died in 8 hours with less than 1 hour screen time. Today, Day 3, I began tweaking a lot of the settings to see if I could get it do better at idle, but again it barely lasted through the day. It took me a while to figure out the "WiFi always scanning" setting, but even once I got my phone to sleep, it didnt seem to make that much difference (no blue bar in usage manager). I've attached some screenshots from usage manager and wakelock detector, does this all look normal to the experts out there?
Should I just flash back to stock to see if I can get the phone at least making it to 15+ hours with light usage on the completely stock setup? I feel inclined to do this, because it SHOULD work bone stock, right? Or is it a waste of time and the stock rom is so bad I should just load something else?
Finally, if I did want to try going back to completely stock I could just follow the troubleshooting section of this post, is that correct? can I flash the OTA updates in the same manner using ODIN instead of sideloading from an sdcard? http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flashed to stock
Just wanted to update for anyone having similar issues. I flashed back to stock using the "downgrade to NCE" file found on this site, then sideloaded NCE to NG3 and NG3 to OA1. That solved my problem and the phone now runs like a dream.