Related
Evo 4G bad.
{
"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 haven't ever had FANTASTIC battery life like I'm seeing from some folks around here... when I first started on Starburst (I didn't keep stock for more than about four hours), I was at around 70% at the same time. I'm currently on Calkulin's 2.0.0; about to revert to Starburst and see if it's ROM-related, now that I've given Calkulin's about a week with a calibration to no effect.
I'm currently undervolted by -75 on all steps, and this seems to have made it WORSE if anything, which I didn't think was possible for undervolting to do. I've been monitoring things fairly closely with Watchdog, and nothing jumps out at me. The phone signal in the pic doesn't look good, but I've been in all the same places as I was when I was getting much better life.
What interests me is that I'm seeing absolutely no usage-based change in battery life. Until that sudden dip you see up there, it was going down at the exact same rate whether I was using it or it was sitting on my desk doing absolutely nothing.
That dip started after I played Fieldrunners HD for about ten minutes during a break at work. After I stopped playing, battery life went into a continuous plummet.
I use Tasker (extensively) to keep things in check; generally speaking, nothing is active unless it needs to be, except for Wi-Fi which is always active as it's my primary method of detecting my locations.
Am I missing something simple-stupid here? If not, anyone got any ideas, assuming going back to Starburst doesn't magically fix it?
Not sure if this will help, but improved my battery.
(1) go to your email setting for each account and change sync update, I believe by default it's set up to check every 15 minutes. With 10 email accounts, it took a toll on my my battery. I changed all my accounts to 4 hours.
(2) best way to kill a task is by holding down home button, going to task manager and kill from there. Market task killers were making things worse for me.
Hope this helps.
Thanks for the thoughts! Sadly, neither of those really apply in my case. I stick with with the default Gmail app, which is all push, and I don't use task killers at all.
I'm running the stock rom with a custom kernel. I did notice that as soon as I went from stock to a different kernel I started to lose battery life. Maybe its something Samsung did? I am still a novice with Roms and what not, but nothing like this happened on my original Epic or my Hero. Maybe the yellow triangle isn't the only thing Samsung put in there.
Maybe the aggressive undervolt is causing your phone to ramp up to a higher state to perform the tasks? That drop is steep with how little screen on time you have
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Maybe the aggressive undervolt is causing your phone to ramp up to a higher state to perform the tasks? That drop is steep with how little screen on time you have
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
For as little as I know, that certainly sounds logical. I still wasn't getting as good as I would've expected even the UV, though.
I just flashed the EK02 modem with today's wonderful developments; I'm going to wait and see if that gets me better reception and thus better life. If not... now I'm not sure whether to try the new ROM first, or scale back the UVs. I want to try one thing at a time, since it's not urgent that I have good battery life ASAP. This gets me through my day, currently, more or less; I'd like to try and find my root cause so that I'm not just trying things wildly in the future.
wolfkstaag said:
For as little as I know, that certainly sounds logical. I still wasn't getting as good as I would've expected even the UV, though.
I just flashed the EK02 modem with today's wonderful developments; I'm going to wait and see if that gets me better reception and thus better life. If not... now I'm not sure whether to try the new ROM first, or scale back the UVs. I want to try one thing at a time, since it's not urgent that I have good battery life ASAP. This gets me through my day, currently, more or less; I'd like to try and find my root cause so that I'm not just trying things wildly in the future.
Click to expand...
Click to collapse
Well, the good thing is that as of today, its possible to return back to bone stock and start again so you can mess with a few setups and see what works best for you. I have found that this is the first phone that uses the frequencies well. I haven't undervolted at all yet and I have had great battery life. I did the standard delete Sprint bloat, Social Hub and associated apps, Maps, etc. Also, get BetterBatteryStats. It may give you some insight into what's happening.
Sent from my SPH-D710 using xda premium
How you return to bone stock? By applying the update?
Odin this
Przekret posted what appears to be a full EG30 RAR archive
Przekret - EG30 full - [post] [direct dl]
- RAR Pass: sampro.pl
- extract HOME.tar from rar file and flash in ODIN using PDA button
- does NOT include data.img so your userdata is preserved
- qbking77 installation video
http://forum.xda-developers.com/showthread.php?t=1381494
Then update to EK02
Got very slightly better today after flashing the EK02 kernel. 23% at the same time instead of 18%... anything could account for that 5%, though, so I don't really think EK02 had any effect on this. Zedomax kernel with stock voltages is next.
CPU boots pro
(From the market & assuming your rooted)
Settings
~Screen off profile max800 min200
~GPU to Conservative max1000 min800
~Nitrous Widget GPU to on demand max1400 min1000
What this should do is downclock your device when on standby by alot. Second for phone calls and daily stuff a clock of 1k will be silky smooth and be a small downclock. Third when you set up the nitrous widget and activate it you will overclock to 1.4k which is stoopid fast my quad score is at 1.4k I get 4500 scores at 1.6k oc but forget batt when I'm using the nitrous. I like too personally keep my phone at a clock of 800 for daily phone calls and web surfing... if I play a graphic intense game ill oc it with nitrous and not worry about burning up my phone because if I set the phone down it downclocks as soon as it stands by and will pick right back up when I'm ready.
Hope it helps here's pics.
Sent from my SPH-D710 using xda premium
Batt life on my day off doing nothing but trolling forums at 800 clock.... I was on my phone like six hours straight while waiting for jury duty selection to be done.
Sent from my SPH-D710 using xda premium
Wolf we need to see your app and process details page. I bet your Android OS and cell standby are much higher than they should be.
Sent from my SPH-D710 using Tapatalk
Dchibro said:
Wolf we need to see your app and process details page. I bet your Android OS and cell standby are much higher than they should be.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
If you're talking about the page I think you are, it'll have to wait until at least morning. I just did a full charge.
To wit... I spent 43 minutes on a phone call, and lost almost the same as what I normally lose in that same time period. 6% for a 43 minute call; I'm averaging 5%/hr loss doing NOTHING.
@Dchibro, assuming that's true, what would it mean for me? Does it give me a solution?
So, doing a bit of my own detective work... I've had Watchdog installed for about three days, with aggressive monitoring. I was almost immediately getting a bunch of alerts for two processes:
I initially whitelisted them through Watchdog, dismissing them as system processes that unavoidably needed to run. However, the comment from Dchibro got me thinking and sent me back to those, and I started Googling around. Here's what I've turned up so far:
http://goo.gl/Hsvej (HUGE thread on the issue in SGS2 forums. Haven't had a chance to go through all this yet.)
http://goo.gl/kUcqx (SGS2 forums.)
http://goo.gl/mlWW4 (Nook Color forums.)
http://goo.gl/mNiId (My Google search results.)
Gonna try some of the suggestions on here and see what I turn up. For now, I'm returning to stock voltages, implementing a bunch of those changes and keeping everything else as it is now to see where I end up. Phone will be charged to 100% before bed tonight, and I'll post sometime tomorrow with my findings.
Wish me luck!
So, in stead of waking up to 50% this morning, I woke up to 86%! Which is the same I went to bed at. Six hours of sleep, not a single percent lost. If nothing else, I learned from all this that I can reboot the phone when this bug hits me and and get away from it.
As I suspected. Your Watchdog shot clearly shows that you are/were (sounds like a reboot solved your issue at least temporarily) suffering from the Android OS bug. This bug presents itself most prominently in the suspend and events/0 processes. Unfortunately, a conclusive solution has not been found, but there are some things you can do to hunt the problem down.
This is the best post/thread I've found regarding the AOS bug on Galaxy SII phones ...
http://forum.xda-developers.com/showthread.php?t=1290020
Im one week into my new sgs2 running full stock. What should normal battery use be? I feel my battery drains too fast. Here is my usage summary since full charge couple hours ago.
I charged too 100%, shutdown, then charged to 100%, powered up and used the phone very sparingly since. Battery is at 91%
Sent from my SPH-D710 using XDA App
Dchibro said:
As I suspected. Your Watchdog shot clearly shows that you are/were (sounds like a reboot solved your issue at least temporarily) suffering from the Android OS bug. This bug presents itself most prominently in the suspend and events/0 processes. Unfortunately, a conclusive solution has not been found, but there are some things you can do to hunt the problem down.
This is the best post/thread I've found regarding the AOS bug on Galaxy SII phones ...
http://forum.xda-developers.com/showthread.php?t=1290020
Click to expand...
Click to collapse
That bug gave me nightmares on my OG Epic.
Sent from my SPH-D710 using xda premium
Definitely seeing a bit of an improvement, here.
Watchdog alerted me to the suspend and event/0 stuff again about an hour ago, but I quickly rebooted and nothing seems to have come of it. I'm going to try to make a Tasker profile to do this automatically, kinda like Viper's LoS script.
All in all, I'm considering this a mostly satisfactory alternative to draining 80% of my battery with almost no use in eight hours.
This doesn't represent real-world use. This is an extreme example of how long you can make the battery last by severely throttling the CPU!
I posted another thread about the method used to apply this mod (you can find it here) but I made this thread to concentrate purely on the side effect of it, which is insanely good battery life. Firstly, I'd just like to make this point clear: I would not recommend doing this mod. It makes your device get pretty screwy and renders it fairly unusable. It needs further development before it can be useful.
Yes, this mod gives you absolutely incredible battery life but it only does so by severely limiting the CPU speed and limiting the CPU to a single core (It might even just run off the companion core and nothing else. I've had conflicting results) which makes the phone insanely laggy. I believe, however, that this throttling could be made less aggressive and then toggled on and off at will. From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life (which is already pretty amazing). This isn't definite though and needs more tests
Anyway, less chit-chat, here are my results:
{
"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"
}
That's right, 12 hours and 35 minutes screen-on time!
It would probably last about 4 or 5 days if the screen was off!
ROM: Android Revolution HD
Kernel: stock ARHD kernel
Screen on lowest brightness
No other modifications (apart from the throttling mod)
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
SartoriXX said:
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
Click to expand...
Click to collapse
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Might aswell do that!
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Meltus said:
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Click to expand...
Click to collapse
I think it sounds awesome and happy to see people like you try to developing the power consumption!
Sent from my HTC One X using Tapatalk 2
sure beats my battery life with only 30 minutes screen on time
ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
Comments like that are a complete waste, if they are on to something you should be more encouraging.
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
lamenramen said:
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
Click to expand...
Click to collapse
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Meltus said:
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
Click to expand...
Click to collapse
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
punyategar said:
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
Click to expand...
Click to collapse
The hox has 5 cores, 4 main cores and 1 super low power core.
What this does is turn off the main cores and run on the super low power core which is great for battery life but it only goes to 500 MHz and in respect to CPUs is slower at processing stuff then almost all CPUs price you pay for power saving.
Sent from my HTC One X using xda premium
Applaud your investigations, so many Haters on this forum!
This phone has masses of potential for some awesome custom Roms (and even a decent official Rom if HTC ever sort themselves out!). Battery life pretty much whole day for me but improvements always welcome.
xchasa said:
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
He is probably talking screen-on time. 4-5 Hours screentime is great, unfortunately you do not fall under the average hours of screen-on time. The average time would be anywhere between 2 and a half to 3 and a half hours.
Which in my opinion is nothing special, admittedly, it does get me through a day but hey! I wouldn't mind having more screen-on time. If 4-5 hours screen on time was the average than you wouldn't see many if anyone complaining at all.
Good day!
treebill said:
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Click to expand...
Click to collapse
Ah, that makes more sense
So, were you able to get the 'throttle' file to stick to anything but '1'?
I noticed the throttle_table and tried to use a few of them but they all just defaulted to 1.
It's a shame the 'throttle_table' file isn't editable too, that would make modifying it so much easier!
My first test failed miserably I'm afraid, I forgot to turn off an alarm and it rang out for about 3 hours and then ran out of battery! I'll remember to turn off the alarm next time
Bloody good effort. Despite the idiotic comments from those who clearly haven't grasped the idea behind this, it's impressive homework.
Research like this can only help improve custom-ROM's, which is kinda the point of XDA Dev's, no?
I think some people should focus on the comments section of sites like Engadget, where their funny pictures will be much better suited.
Well folks, I took time to study our G2 battery to really see what is killing it. After testing it on different roms i have come out with something that can save your battery for a while before you think of replacing it.
On a general scope these are the main factors that really drain your battery:
1.3G data connection
2.Screen brightness
3.Rom type(mostly sense roms)
On 3g, if the user has a wireless network nearby i suggest you connect to that for your browsing and all that, there is no need using hspa when you have a WI-fi network working great, 3g networks drains the battery faster than you think i tried it and i saw that the WI-fi use was very slow in draining the battery up to the point i switch to 3g. IF your thing is voice calls i still don't see how good and different 3g is from 2g "it's not like you are recording an album over the phone to need such voice clarity" remember a good battery life affects your phones performance in a great way. these photos tell the whole story..
{
"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 used the wi-fi for about 12 hours and when i switched to 3g it drained in 2 hours
For screen brightness you will notice that every time you check battery usage your screen always has the biggest share of the consumption. You have to reduce your screen brightness to 30% or lower or put it on auto-brightness that's about all you can do about it.
Also your rom and the kernel it comes with are a huge factor in battery consumption. On a general scale i have noticed that sense roms are the big killers of all just see
in 51 mins of no use at all just screen off the battery drops to 81% i have never had above 9 hours of use with any sense rom
Other things like gps also drain your battery, so if you are not on "MAPS" just switch it off to save your battery. Also keeping your cpu clock speed at high points drain the battery a lot try to use apps like setcpu to control the clock speed and set profile like screen off to keep your cpu down when you are not using it, and use cpu governors like smatass, ondemand, conservative etc
Also the trick of draining your battery completely and then recharging it in intervals of 3 months or more help enhance battery life,
do not leave lots of apps running in the back ground they also drain you battery alot :good:
Any body who knows something that can help pls add cos there are a lot of guys who still don't know these stuff....
and a lot of guys like me who still want to enjoy their G2 for a looooong time....so big boys...yes it's needed......
photos missing.......................................................................................................
About the sense roms, even though i agree it consumes more battery than AOSP, they are not as bad as u say (at least not all of them). I use a sense 3.5 rom and with regular use i get about a day and a half before it hits 20% (80% consumed) (This is on 2g, with wifi on... when with data on, i still get at least 22 hours). I know it comes down to settings and usage, but just saying, its possible to get a lot of battery endurance with sense.
If anyone is interested in more detalied information on my settings and usage, feel free to ask me (through pm if possible)
Nice review though, thanks for sharing!
Coldsun15
strip419 said:
Also your rom and the kernel it comes with are a huge factor in battery consumption. On a general scale i have noticed that sense roms are the big killers of all just see
in 51 mins of no use at all just screen off the battery drops to 81% i have never had above 9 hours of use with any sense rom
Click to expand...
Click to collapse
This is impossible if you havent got a problem with the rom. I have been using all kinds of roms with my Desire Z. The battery life is not that much different on sense and aosp roms.
I am using GenY Beta5 right now for example. On standby mode (only gps is disabled) it can go more than 2 days! A stock optimized 2.1 Sense rom can go even more than that.
For battery life problems I suggest using an app like Better Battery Stats and see what is causing your phone to stay awake. It is easy to see what eats your battery.
Other than that as you said, whatever rom you use Screen will eat your battery the most. Overclocking will obviously eat more battery too. Using 3G instead of 2G will use more battery. COnstant Wi-fi activity and gps are battery killers too as you may guess.
The rest is how the user uses his/her phone.
strip419 said:
Well folks, I took time to study our G2 battery to really see what is killing it. After testing it on different roms i have come out with something that can save your battery for a while before you think of replacing it.
On a general scope these are the main factors that really drain your battery:
1.3G data connection
2.Screen brightness
3.Rom type(mostly sense roms)
On 3g, if the user has a wireless network nearby i suggest you connect to that for your browsing and all that, there is no need using hspa when you have a WI-fi network working great, 3g networks drains the battery faster than you think i tried it and i saw that the WI-fi use was very slow in draining the battery up to the point i switch to 3g. IF your thing is voice calls i still don't see how good and different 3g is from 2g "it's not like you are recording an album over the phone to need such voice clarity" remember a good battery life affects your phones performance in a great way. these photos tell the whole story..
i used the wi-fi for about 12 hours and when i switched to 3g it drained in 2 hours
For screen brightness you will notice that every time you check battery usage your screen always has the biggest share of the consumption. You have to reduce your screen brightness to 30% or lower or put it on auto-brightness that's about all you can do about it.
Also your rom and the kernel it comes with are a huge factor in battery consumption. On a general scale i have noticed that sense roms are the big killers of all just see
in 51 mins of no use at all just screen off the battery drops to 81% i have never had above 9 hours of use with any sense rom
Other things like gps also drain your battery, so if you are not on "MAPS" just switch it off to save your battery. Also keeping your cpu clock speed at high points drain the battery a lot try to use apps like setcpu to control the clock speed and set profile like screen off to keep your cpu down when you are not using it, and use cpu governors like smatass, ondemand, conservative etc
Also the trick of draining your battery completely and then recharging it in intervals of 3 months or more help enhance battery life,
do not leave lots of apps running in the back ground they also drain you battery alot :good:
Any body who knows something that can help pls add cos there are a lot of guys who still don't know these stuff....
and a lot of guys like me who still want to enjoy their G2 for a looooong time....so big boys...yes it's needed......
Click to expand...
Click to collapse
All you are saying are basic stuff everyone knows about power consumption, and all that you have been testing are YOUR results, what you are saying now are absolutely no facts, and some are wrong. You're saying sense takes more juice? Well since IceCreamSandwich it doesn't really matter. Are you sure your battery is properly calibrated?
After installing a rom you shouldn't put the phone on a charger, but just use/leave it till the battery has 10% left. then charge till its full. By prefer you should do it another time and then it should be calibrated.
Also you forgot to add the radio. The radio is also important, if you got a proper radio for your provider/rom, you can easily get more power out of your phone. If you have the wrong one, drains can be high. The extremest example I can take is my old HD2. Which had a radio not compatible with the version of android and the battery drained from 100 - 10 in 3 hours.
Now look at my stats of my DesireZ, running Gen.Y RC1(Which seems to be using more battery then the B5). I attached a screenshot. The battery is totally stock and not an extended one. I used it yesterday at home when I was busy with my car(whatsapp, mail, google), at the evening I played some games. Before I went to bed my battery stats was 60%, when I got out of bed this morning it was 59%.
Also I think the topic should be in "general" since its talking about everything, and I can't see how this is rom development.
Thanks for adding up guys,but I am sure your batteries are quite fresh that's why you have very good batteries,people like me with aging ones who still want to use it for a while. I had to wipe my battery stats a few times to calibrate it. And if your read things very well this was meant for guys who really don't know the does and donts about battery usage yes it's basic but people still ask these questions in dev sections. I did not add radio because that thing does not work well for everyone and it's still an easy way to brick your phone most of these radios were made with USA service providers in mind ,people have complained about having serious issues with battery and connectivity when they Change their radio and if any one is even reading this then I don't think that person even knows what the radio is so why not do the basics than brick your phone in an attempt to go high .....to the big boys who know all.... you have to know that there are still guys out there without rooted phones facing these problems so radio is the last option......
Sent from my HTC Vision using xda app-developers app
strip419 said:
Thanks for adding up guys,but I am sure your batteries are quite fresh that's why you have very good batteries,people like me with aging ones who still want to use it for a while. I had to wipe my battery stats a few times to calibrate it. And if your read things very well this was meant for guys who really don't know the does and donts about battery usage yes it's basic but people still ask these questions in dev sections. I did not add radio because that thing does not work well for everyone and it's still an easy way to brick your phone most of these radios were made with USA service providers in mind ,people have complained about having serious issues with battery and connectivity when they Change their radio and if any one is even reading this then I don't think that person even knows what the radio is so why not do the basics than brick your phone in an attempt to go high .....to the big boys who know all.... you have to know that there are still guys out there without rooted phones facing these problems so radio is the last option......
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
If their phone is not rooted, how can they have a custom rom then lol. I think if you want to use a custom rom on your phone you should read everything and not blindly start everything. Also flashing a radio has risks, but not really something to worry about if you do it right. Its quite easy and as long as you stay on the right path you are fine. If you want to make a proper thread about battery consumption you should include the radio thing. And also post it in a place where it belongs. You are right that newbies don't know everything, but if we should do everything for them, you get even more newbie questions. They need to put some effort in it like we do.
also you have not added the tricks like changing the advanced wifi to always wifi when screen off....
Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?
U can try to run it in performance mode.
Sent from my P6-U06 using Tapatalk 2
{
"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"
}
The performance mode just reduces the resolution...
try
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:
savio_mascarenhas said:
try rooting and installing clockworkmod and then flash a rom or install cynogen mod or install game booster on playstore
good luck
hit the thanks button:cyclops:
Click to expand...
Click to collapse
there is no clockworkmod until now ...
But which firmware does your phne have?
B104 is not very smoothy, try the official B107 if it is ... good luck
i dont
i dont have a ascend p6 so try to flash a new rom but becareful if you need further help i can help you
hit the thanks button please
good luck tell me if you need help
i have a huawei idoes x5:highfive:
i am an android developer
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.
zhenaguo said:
:laugh:I come from china.now i am in ShenZhen.I have already competly made the customer recovery for Huawei P6.I will upload it soon .Hope you gays enjoy it.
Click to expand...
Click to collapse
solve your problem
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit
zhenaguo said:
The cpu and GPU locked in a certain frequency power can be achieved not so serious and fluent game approach.
The first machine to ROOT then RE Manager to set inside the file!
1. Open sys-devices-system-cpu-cpu0-cpufreq-cpuinfo_block_freq, use a text editor to open, modify the value of 600,000 or 800,000 or 700,000 are cpu frequency is locked, save and exit after completion of editing,
2. Locate scaling_cpu_lock_nun, a method using phase inside the 0 modified to 4. It is locked cpu cores. Save and exit editing can! In power management policy settings in a super-power standby.
GPU in accordance with slim post to unlock! But I set 480000 360000.
Heat is also not so great to play the game is very smooth! Power consumption is not serious enough for everyday use heat is also better!
I charge 100% after setting the screen brightness is not open to the minimum WIFI playing whitewater boats two effects 30 minutes of high power consumption 23% is power! But look at the beep beep miles 720 miles to see 24 minutes of animation power at about 7%! Several times hovering at about 7%.
After rebooting modify things will revert to re-edit
Click to expand...
Click to collapse
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks
JackHanAnLG said:
Hi there, im not very code technical, From what I can see, have you made the phone not get as hot and gave it better proformance, the only thing thats putting me off buying this phone is that even though it has a snapdragon S4 pro it isnt as good as the Nexus 4 which is cheaper and that it gets way to hot ( someone had a screen shot of the phone getting so hot that asked to close apps )
Many thanks
Click to expand...
Click to collapse
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.
beodenls said:
Yesterday I bought a Huawei ascend p6 for my wife. Even when holding it in hand, I feel like its design. After a day of use, I feel quite disappointed in its performance. When running the game like candy crush, subway surf, ... I find it does not run smoothly, or say exactly shocked. I wondered if I run the game require higher configuration will how?
According to you, is caused by the configuration of the machine or the rom? Is there any way to solve this problem?
Click to expand...
Click to collapse
Yes the solution is go to settings>power manager>select normal
Then go to manage apps>subway surfers>enable the perfomance mode
Hope this helps and tell the results
Sent from my HUAWEI P6-U06 using xda premium
yfnew said:
well... Based on what I know about this phone, the CPU is not a Snapdragon S4 pro but a K3V2E developed by Huawei itself. That might explains the performance issue. Huawei locked the CPU frequency and GPU frequency for power saving reasons, but it locked it too much.
Click to expand...
Click to collapse
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?
JackHanAnLG said:
No way! How could they lie? Do you think its a Cortex A7? I only ask because the battery life seems pretty good and as far as i know 1.5ghz is the max an A7 can go, also if the performance isnt great, that would be why?
Click to expand...
Click to collapse
Yes, you are right ! The cpu's are cortex A7.
any idea what GPU it has? any info about it?
Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app
S34Qu4K3 said:
Immersion. 16, and we got Cortex A9, not 7
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
never heart of that gpu....
no one has any specs list about it?
yeah A9, gsmarena sayed it.
loooks like a cute phone
Hi
Im satisfied with my new P6, but honestly the battery life is very bad. My phone 's been 5 hours on battery, and has 50%. I have disabled Google services, wifi, gps and cleaned background apps. I dont even keep my screen brightness high !
I also get sometimes mobile data lost, i've 3g/h on statusbar, but data is not moving. Going to airplane mode and back makes it work again. This happens few times a day.
I have B106, the build which came with the phone. Should i update to B107 or something else? Im in Finland with Elisa / Saunalahti network and i've heard about connection issues on B107. Is it still better than 106, or is there some other build that i should try?
And have you any info about coming versions from Huawei? Thanks alot
We have in Germany by default B104 and the B107 is much better ... at the moment I have a beta B111 on my phone and that is still better than B107 ... I think there will be better roms soon.
Hope that there will be custom rom possible soon, the test possibility is much better then ...
Find out whats causing the drain. Go to settings-battery(asetukset-akku) and see if there is a program misbehaving. Stopwatch prevents the phone from going to deep sleep and therefore drains lots of power even when the screens off, other programs might do it aswell.
If you get 4-7 hours of screen on time id say that its pretty normal, although i do not play any games that consume loads of power. And i think browsing with wifi consumes less power than mobile data.
Ill try to take some battery stats with syncs, gps and google now on. So youll have something to compare with.
I have had my OP3 for 2 years. I have noticed the battery life is much shorter, overall burn-in on the screen (screen is getting dim even on max brightness), and the overall performance is much slower than it was even a year ago. Am I the only one experiencing this? Is OnePlus doing similar to Apple where the CPU is throttling as the battery degrades?
Edit:
Using latest beta build, but the same issues persist regardless of using stock, beta, or custom roms. I am also rooted, but notice the slow speeds even with a fresh ROM reinstall with everything stock.
No OnePlus can't do what Apple did, we would notice in a second. You should try new kernels or go with stock if you aren't using stock already. Try different ROMs if you want to confirm your hardware condition. Other than that the decreasing speed is normal, the device is getting older and it is getting tired.
I've tried multiple different roms and kernels. The issue is close to the same across all ROMs. Just now opened a twitter notification and it took several seconds to open rather than instantly like you'd expect.
Was just wondering if it is worth a try with one of the $25 batteries on Amazon. Will likely just start looking to upgrade.
Highly doubt you have burn-in. Almost doesn't happen these days anymore unless you abuse your phone. Regarding that your phone is slow. Did you try a full reset yet? Have you done any tweaks or something? My phone is hitting the 2 year mark with only a new battery and camera (common focus problem). And it is still like it was at day 1.
It definitely has image burn in. If I put a full screen white image on the phone, it is all off-white except the middle part of the notification bar, I can even see burn in for the static icons like wifi, battery, LTE, etc...
I have done a full reset just a month ago, but didn't help. Even when completely stock including recovery then tried with a few different kernels. still very slow compared to new.
You did say you have a new battery, considering my battery life is crap right now, I may just give that a try. OEM parts are pretty cheap on witrigs.
I would definitely recommend using bluspark kernel on oxygen os. If you enable the fastlane feature and set both of the cores to 35 it will be blazing fast and no lag what so ever. Try that and let us know how your phone reacts.
Puddi_Puddin said:
Highly doubt you have burn-in. Almost doesn't happen these days anymore unless you abuse your phone. Regarding that your phone is slow. Did you try a full reset yet? Have you done any tweaks or something? My phone is hitting the 2 year mark with only a new battery and camera (common focus problem). And it is still like it was at day 1.
Click to expand...
Click to collapse
{
"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"
}
mrmcshagbag said:
I would definitely recommend using bluspark kernel on oxygen os. If you enable the fastlane feature and set both of the cores to 35 it will be blazing fast and no lag what so ever. Try that and let us know how your phone reacts.
Click to expand...
Click to collapse
I reset and reflashed OOS and installed bluspark. Also limited the apps I installed too. It seems to be a bit faster. Will report back if I get any slowing.
Still no issues. I was thinking and realized my issue. I had two separate profiles on my phone, a home profile and work profile. I assumed that the inactive profile automatically shutdown whenever switching like on a PC when you sign out of one account and into another. I am guessing this isn't the case with android. The inactive profile continued to run in the background causing my slowdown and battery drain issues.
Moving forward, multirom is probably the way to go for me if I decide to go back to having separate work and home work spaces.
daggorlad said:
It definitely has image burn in. If I put a full screen white image on the phone, it is all off-white except the middle part of the notification bar, I can even see burn in for the static icons like wifi, battery, LTE, etc... .
Click to expand...
Click to collapse
I have the same . In addition, I have a burn in screen at the bottom (strip about 1 cm ) . I've noticed keyboard image burn in as well . Never amoled again .
daggorlad said:
Still no issues. I was thinking and realized my issue. I had two separate profiles on my phone, a home profile and work profile. I assumed that the inactive profile automatically shutdown whenever switching like on a PC when you sign out of one account and into another. I am guessing this isn't the case with android. The inactive profile continued to run in the background causing my slowdown and battery drain issues.
Moving forward, multirom is probably the way to go for me if I decide to go back to having separate work and home work spaces.
Click to expand...
Click to collapse
Did you get fastlane enabled on both cpu clustors and set to 35?
mrmcshagbag said:
Did you get fastlane enabled on both cpu clustors and set to 35?
Click to expand...
Click to collapse
I didn't see a fastlane using Kernel Auditor. It has been so long since I have adjusted kernel level settings, I don't really remember a lot of it.
Edit: I just did some more searching and found the settings. I enabled and set to 35 on big and little governers. Thanks for the advice.
daggorlad said:
I didn't see a fastlane using Kernel Auditor. It has been so long since I have adjusted kernel level settings, I don't really remember a lot of it.
Edit: I just did some more searching and found the settings. I enabled and set to 35 on big and little governers. Thanks for the advice.
Click to expand...
Click to collapse
No problem let me know how your phones running with that enabled ?
daggorlad said:
I reset and reflashed OOS and installed bluspark. Also limited the apps I installed too. It seems to be a bit faster. Will report back if I get any slowing.
Click to expand...
Click to collapse
Do you life in a area with alot of sun? Still don't have burn in, sad to see that you do tho.
Also keep in mind that once android gets above 50% storage performance starts to degrade.
I have same issues. My op3 overheating and lagging alot while playing pubg. Any solution?
Noob02 said:
I have same issues. My op3 overheating and lagging alot while playing pubg. Any solution?
Click to expand...
Click to collapse
There really is nothing you will be able to do about that. Those kind of games are really just pushing mobile hardware in directions that it just wasnt designed to go. Until we get a real cooling system (20 years or so before they shrink the liquid cooling small enough maybe) Gaming like that will always cause the device to heat up alot and lag. Its the nature of the beast.
zelendel said:
There really is nothing you will be able to do about that. Those kind of games are really just pushing mobile hardware in directions that it just wasnt designed to go. Until we get a real cooling system (20 years or so before they shrink the liquid cooling small enough maybe) Gaming like that will always cause the device to heat up alot and lag. Its the nature of the beast.
Click to expand...
Click to collapse
So buying new phone is the best solution? I can't effort new phone now. So is there any kernel configuration or tweaks?
Noob02 said:
So buying new phone is the best solution? I can't effort new phone now. So is there any kernel configuration or tweaks?
Click to expand...
Click to collapse
No, Not even a new phone will really help. Besides the hardware in the 3 and 3t will still be able to handle anything Google tosses at it for a few more years yet. You hear it all over the place on every device. No device has a proper cooling setup for gaming of that nature. Even the S9 with Fortnite is getting hot after playing for a while.
This is a side effect of trying to game on something that was not made to game like that. Ill be honest. If you want to game like that save it for the PC until the hardware can support it. Other wise you will just have to deal with the heat and the lag.
zelendel said:
No, Not even a new phone will really help. Besides the hardware in the 3 and 3t will still be able to handle anything Google tosses at it for a few more years yet. You hear it all over the place on every device. No device has a proper cooling setup for gaming of that nature. Even the S9 with Fortnite is getting hot after playing for a while.
This is a side effect of trying to game on something that was not made to game like that. Ill be honest. If you want to game like that save it for the PC until the hardware can support it. Other wise you will just have to deal with the heat and the lag.
Click to expand...
Click to collapse
I see. Thanks bro