Has anyone done this? The whites seem a bit muddy/yellowy to my eyes.
I used a kernel app (Fauxclock, but Trickster might work too) and reduced "Red" to 255, to 235
I left everything else as it was
The screen looks infinitely better!
243,220,255 is all I've gotta say! with fauxclock its 255
I suppose this could vary from device to device, ROM to ROM, etc, but on AOKP 4.3 I've done some comparisons with some test images and my calibrated monitor and at about 70% brightness the colours are close enough for me. I'm a photographer, so I tend to notice such things. I haven't put a Spyder on it or anything, nor will I.
martindar said:
243,220,255 is all I've gotta say!
Click to expand...
Click to collapse
It's out of 100?
Sent from my LG-G2 using XDA Premium 4 mobile app
xblackvalorx said:
It's out of 100?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you have CM11?
It's out of 100 for me too...
3473 said:
Has anyone done this? The whites seem a bit muddy/yellowy to my eyes.
I used a kernel app (Fauxclock, but Trickster might work too) and reduced "Red" to 255, to 235
I left everything else as it was
The screen looks infinitely better!
Click to expand...
Click to collapse
I tried change these values with both Fauxclock and Trickster, but I can't go below 250 250 255, even when I put lower values like 200, 200, 200 and apply, both Fauxclock and Trickster set the values to 250 250 255.
What is wrong?
So I've decided that at normal brightness the screen looks fine, but last night when I was driving around using Waze with the brightness at almost zero the screen is VERY BLUE. Annoyingly blue.
I don't think there's any way to adjust it in any granular way, although I might look into it.. Perhaps Tasker can use some app to adjust the screen values only while in GPS mode or something... What's interesting is I didn't notice it around the house, even in the dark. Ah well.
Related
So I love Set CPU and it was working for a bit, but now for some reason my profiles refuse to work. I have them enabled, but it always has "Main Profile" activated, which kills my batter. Below are my set profiles:
Screen Off 245/245
Priority: 100 Ondemand
Charging/Full 806/806
Priority: 85 Ondemand
Battery < 50 748/710
Priority: 75 Ondemand
Battery < 1 710/604
Priority: 65 Ondemand
I'm using KaosFroyo v23, but I haven't seen anything about bugs with SetCPU in it.. so anyone have any other ideas? It seems the problem is the 'Main Profile' over riding my profiles.
those are some pretty high profiles......... what are you OC to?
copestag said:
those are some pretty high profiles......... what are you OC to?
Click to expand...
Click to collapse
You mean how high can I OC to? Umm, 824 is the highest I've gone too.
Holy **** 824, lucky bastard.
Anyway, I have the same exact problem. If you want it to work you have to go into set cpu and tap the "enable" button under profiles and disable and re-enable and then hit the back button to exit. This'll keep it working on your profiles until you reboot, so just do this once as soon as you reboot.
Hungry Man said:
Holy **** 824, lucky bastard.
Anyway, I have the same exact problem. If you want it to work you have to go into set cpu and tap the "enable" button under profiles and disable and re-enable and then hit the back button to exit. This'll keep it working on your profiles until you reboot, so just do this once as soon as you reboot.
Click to expand...
Click to collapse
Yeah, guess I lucked out on my phone. It's kind of a beast lol. Anyway, I tried that but it still doesn't seem to work. In the notification in the status bar, it always says "Main Profile" rather than "Charging/Full" or whatever. My "screen off" one out does work, though. The widget will show my screen off settings for a sec when I unlock the phone.
It may just be an issue with the notification bar updating.
Oh and does that say battery < 1% ? or is it supposed to be 100%?
Just so you know here's an example of how profile priority should be done
When under 50% battery, 90 priority
when under 100% battery, 80 priority
You see how lower battery needs a higher priority? This is because when you're under 50, you're also under 100. This may be your problem. Make sure that lower battery gets HIGHER priority.
I also suggest you set a temperature priority, especially with your killer speeds.
*dies of jealousy*
Hungry Man said:
It may just be an issue with the notification bar updating.
Oh and does that say battery < 1% ? or is it supposed to be 100%?
Just so you know here's an example of how profile priority should be done
When under 50% battery, 90 priority
when under 100% battery, 80 priority
You see how lower battery needs a higher priority? This is because when you're under 50, you're also under 100. This may be your problem. Make sure that lower battery gets HIGHER priority.
I also suggest you set a temperature priority, especially with your killer speeds.
*dies of jealousy*
Click to expand...
Click to collapse
I think this was the problem. I messed up the priorities, it's a tad confusing.. oh well, this should fix it. When I did the fix in your last post, I realized that both my screen off AND my charging one did. Just not my battery.
Thanks for the help man. And for the tip about the temperature, I didn't take that into account, being that I wasn't aware my OCing was that crazy!
EDIT: Yep, that fixed it! One more question, I'm assuming that my screen off/charging/temperature profile should be set at 100% Priority? Or should it go temp profile > screen off > charging > lower battery > higher battery?
EDIT AGAIN: Okay, I think the proper set up is: temp profile > charging/full > screen off > 25% battery > 50% battery. Correct? The temp should be the highest priority so it can override the others, then charging should be able screen off, since it's pointless to lower the overclock while charging, then screen off since it is important to battery life, then lower battery, followed by higher battery for the reason you explained.
Wewf. It's worth the set up, I suppose.. and btw I CAN overclock to 844, but it's not stable in the slightest.
824? nice....... thats why I was mentioning the high profiles......... most people cap out at about 768 on this phone......I just initially set mine there and havent really tried for more
as for the profile priority goes...... IMO the temp needs highest priority.... this is the one that does the damage if not obeyed ........
I personally have all my profiles (other than main of course) set to 480/245 so priority doesnt really matter
in your last post you mentioned it being pointless to lower OC while charging..... depending on your temp profile and charging method, this theory doesnt much matter..... since on wall charger I always exceed my temp profile anyhow (which I have set to the specs in the manual 40°C/104°F)
copestag said:
824? nice....... thats why I was mentioning the high profiles......... most people cap out at about 768 on this phone......I just initially set mine there and havent really tried for more
as for the profile priority goes...... IMO the temp needs highest priority.... this is the one that does the damage if not obeyed ........
I personally have all my profiles (other than main of course) set to 480/245 so priority doesnt really matter
in your last post you mentioned it being pointless to lower OC while charging..... depending on your temp profile and charging method, this theory doesnt much matter..... since on wall charger I always exceed my temp profile anyhow (which I have set to the specs in the manual 40°C/104°F)
Click to expand...
Click to collapse
Yeah, I just realized something pretty bad when I charged it over night.. being that charging (the 824 one) was set to a high priority that the screen off, it was literally on 824 ALL night long.. I woke up and the battery tempt was 145 D: It was fine, my temp profile saved it from going too high, thank God.
Any ideas for a good temp to set that profile at, though? It's at like 130 now, but I think that's a bit too high as well.
specs list an upper limit of 40C/104F....
specs are usually conservative (my profile is set to spec).....but I wouldnt go too far over if I were you
Sent from my Eris using XDA App
copestag said:
specs list an upper limit of 40C/104F....
specs are usually conservative (my profile is set to spec).....but I wouldnt go too far over if I were you
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Alright, I kicked it down a notch to 40C.
Thanks for the help guys.
I have mine at 41.7 degrees since I can hit 40 easy.
Quick Question -
Running Kaos v23 now - since upgrading from v21, I have lost the icon at the top of the menu home screen. Also, when I go into task killer, it is not shown as an active application. Any ideas???
Thanks
bl4scott said:
Running Kaos v23 now - since upgrading from v21, I have lost the icon at the top of the menu home screen. Also, when I go into task killer, it is not shown as an active application. Any ideas???
Thanks
Click to expand...
Click to collapse
Um, have you tried OPENING the app? Go to your app drawer, click on it, then check mark "Notifications" under "Profiles."
And yeah I changed the temp profile, cause it overheated during a phonecall..
Make sure it's installed. If none of your superuser permissions are working reflash an old superuser.
Does anybody have ANY good info on the Advanced settings for setcpu
sampling rate
power save bias and what not for our phones
or where we can find them ?
Ok - someone help me understand how this thing works. Can I only have three steps? What is the VSel1/2/3? Can I change the governor?
it's here :
http://forum.xda-developers.com/showthread.php?t=898036
That is the app thread but I don't see instructions.
Yes, there are three steps and for each one you can choose the CPU voltage (vsel) and frequency.
You can choose between two governors: performance (always at max freq and voltage) and on demand (freq and voltage scaling).
Sent from my MB525
Ok but how do I know what voltage is best? What frequency is best? I read the item about phone ringing:
________________
update7:
when i set my defy to 300mhz while screen is off then when a phonecall is incoming the defy is so slow that it takes ages for the screen to go on....
sometime it takes 2-3 ring befor i can answer the call
so setvsel set it to maximum speed on phoneringing befor the screen is on!!
________________
Is he saying he did that in code or an action is needed by the user to handle this? Mine still takes 3 seconds for the screen to turn on.
its preety much the same as overclocking cpu on pc ..but easier
just try ...each chip is different ..and it depends on the rom aswell
phone will reboot if ull set it 2low ...or ull get some app closing errors or stuff like that
safe voltages to start would be 300/20 600/40 1000/56 ...then go lower
So if I set it too low then phone will reboot?
What is the safest settings if I am still using stock rom?
Sent from my MB525 using Tapatalk
e-prast said:
So if I set it too low then phone will reboot?
What is the safest settings if I am still using stock rom?
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Yes if you go too low on the vsel for that frequency then the phone will reboot - just make sure at first you don't have setvsel configured to "apply at boot" until you have discovered your stable settings.
As for stable settings then maybe start with the first vsel & lower it until it reboots then you know it's too low & you need to go up higher by 2 vsel or so.
It would be easier to do each vsel at different times so you know which one causes the reboot.
Just for info my settings are:
300/18
700/32
1100/56
Up_threshold 75%.
I could possibly go lower on the 300 & 700 but I'm happy as they are. The 1100 on mine is set at the lowest stable vsel I could get.
As mentioned all cpu are different & what settings that work for one person may not be any good for another.
Ok thanks
I am still using the default clock but i'm lowering the vsel a bit. I'll start tweaking untill get the best result. I hope I can reach 1000 max. BTW what is the threshold for? Mine still in default.
Sent from my MB525 using Tapatalk
Threshold is the % load that the cpu reaches before it switches to the next higher frequency.
Just for example sake here are my settings. Actually the only one I changed was #3. [email protected] All the rest is left at default. I just wanted a bit of a quicker device, and changing just this one setting gave me what I wanted. Very stable and snappy now. My Quadrant scores are in the low 1700s. (oh and I'm on the official 2.2.1, but nothing else is changed)
How is your battery? Do you use the stability test to determine your lowest values?
sp8y said:
Yes if you go too low on the vsel for that frequency then the phone will reboot - just make sure at first you don't have setvsel configured to "apply at boot" until you have discovered your stable settings.
As for stable settings then maybe start with the first vsel & lower it until it reboots then you know it's too low & you need to go up higher by 2 vsel or so.
It would be easier to do each vsel at different times so you know which one causes the reboot.
Just for info my settings are:
300/18
700/32
1100/56
Up_threshold 75%.
I could possibly go lower on the 300 & 700 but I'm happy as they are. The 1100 on mine is set at the lowest stable vsel I could get.
As mentioned all cpu are different & what settings that work for one person may not be any good for another.
Click to expand...
Click to collapse
Battery lasts a long time for me could get between 2-3 days on a full charge but i normally top up the battery every day and don't let it run out.
As for the stability test i did use it when there was a one built into the setvsel app but not for long. I just adjusted my settings then used the phone for a while to make sure it was ok.
How do I know how high I can go on over clock?
Sent from my MB525 using Tapatalk
Bump
Sent from my MB525 using Tapatalk
Just try it; but generally top frequency is 1200 otherwise you have to set too high vsel with consequences on temperature and stability.
Sent from my MB525
Just working fine, thanks
Hello guys, i have overclocked the cpu at 1100Mhz with 58v and is perfect but i want understand what is the maximum v for stay secure.
I have 1200 at 62
Sent from my MB525 using XDA App
I use
19/300
38/600
50/800
only for the reason - to to keep my Defy, without charging as lons as it possible. now my record is 4,5 day for normal everyday using (30 minuts of wi-fi, 45 minutes of conversations, a little bit games some times, 1-2 hour of reading e-books)
I was wondering what some SetCPU profile suggestions are for the Atrix? Right now all I have is a screen off profile. It has like 608 max and 216 min.
Ideally I would want to set the min a little lower, but it doesn't seem that I can?? It's also kind of annoying that each value can only be set to certain increments, like it jumps from 608 to 450 something or 760 something the other way.
Any thoughts on some other profiles I would maybe want to set?
thebeardedchild said:
I was wondering what some SetCPU profile suggestions are for the Atrix? Right now all I have is a screen off profile. It has like 608 max and 216 min.
Ideally I would want to set the min a little lower, but it doesn't seem that I can?? It's also kind of annoying that each value can only be set to certain increments, like it jumps from 608 to 450 something or 760 something the other way.
Any thoughts on some other profiles I would maybe want to set?
Click to expand...
Click to collapse
screen on 1000/216
screen off 216/216
stevendeb25 said:
screen on 1000/216
screen off 216/216
Click to expand...
Click to collapse
That screen off max seems sorta low. You haven't experienced any wake up lag or anything while using that?
out of all honesty i used setCPU for a while and didnt notice any difference other than wake lag on my LWP. The phone is already excellent at managing the processor loads on its own. To me it was Just another app using up my battery. I will def use it once OCing is possible. It didnt really seem to have any benefits IMO. I have great battery life without it and thats with chainfire, sdspeed increase, Titanium, and a few others running unrestricted by my task manager. Once again just my opinion.
thebeardedchild said:
That screen off max seems sorta low. You haven't experienced any wake up lag or anything while using that?
Click to expand...
Click to collapse
nope no lag here
I see, I could probably get away with setting it even lower.
Dirtburgler, yeah that's mostly why I've only set one profile so far because I haven't really noticed a super high need for anything else lol. I did notice that, in spare parts, my runtime greatly exceeded screen on time on average, so I wanted to make sure to limit the CPU while it was off and it actually has worked very well. I'm only about 1-3% higher with runtime now, even with heavy usage!
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
syrenz said:
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
Click to expand...
Click to collapse
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
SetCPU is used for setting CPU parameters. Like the range of mhz your CPU works at. Also setting profiles (CPU mhz when the phone is charging, reach temperature, battery lower than... etc.). But it cannot be used for overcharging, that's why we use Milestone overclock...
Sent from my XT720 using XDA App
jackfrost3821 said:
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
Click to expand...
Click to collapse
Setcpu is free for XDA members bud, find it here
how should i adjust my advanced settings? im overclocked at 850mhz
LibertyMonger said:
Setcpu is free for XDA members bud, find it here
Click to expand...
Click to collapse
Thank you I wasn't knowing it is free for xda members!
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Thanks for the answers
jackfrost3821 said:
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Click to expand...
Click to collapse
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
LibertyMonger said:
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
Click to expand...
Click to collapse
Exactly that is what I've tried, uninstalled SetCPU to see the battery performance. It was really unnoticeable the battery drain with and without Setcpu. I use Autokill Memory Optimizer which seems to be providing good results as well as performance enhancement.
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
exist2resist said:
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
jackfrost3821 said:
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
Click to expand...
Click to collapse
I guess you are correct.
But currently I removed the SetCPU. And I see much better performance now. I was min at 250MHz. Even the quadrant score is much better now.
Thanks for your insight
I remove setcpu and do a comparison too. I'm using CM 7.1.0 of fjfalcon and it lasts 1.5-2 days with minimal usage on setcpu. Now let's see if it's barely unnoticable.
but I think set cpu to 250mhz during the night when you don't use your phone may prolong battery life.
Woodrube said:
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
Click to expand...
Click to collapse
Dude! with those settings what is your battery life like?
my minimum is at 125mhz and max at 250mhz (when screen off) and I lose 30% over night! and it barely lasts 8hours D:
what ROM are you on?
Do you guys know how the smartass governor works?
around?
You post in the wrong spot and also u need to find that out on your own because all ROMs have deferent stuff inside them also all phones not all work the same
Sent from my LG-E970 using XDA Free mobile app
Posting in the right forum is my favorite way to save battery.
this is the rom sub-forum isnt it? if isnt can someone please move it to the right place
Don't listen to what anybody says: battery life isn't too ROM-dependent for our LG OG. I get the same battery life no matter what ROM I use. It all depends on your kernel settings. I get at least 4 hours of screen on time with the following settings in the Official CM11 rom with the LGE Gproj Kernel:
162 min, 1026 max, Wheatley with a powersave bias of 1, MPDecision ON (from what I've seen, it's better at turning off cores than the in-kernel implementation), max GPU at 128 if you don't plan on playing too many games with the interactive governor, Multicore Power-Saving set to 1, and -150 UV across the board (voltage for 162MHz starts at 650; I have a fast-binned E970). Also, I use auto-brightness but I've edited the brightness table heavily so it's JUST bright enough for most situations. I also keep GPS, Bluetooth, NFC, LTE, notification light, and cap keys off. My data is off whenever possible too. And every time before I turn off my device, I press Greenify's "hibernate now" widget to prevent any wakelocks. Lastly, I use ART instead of Dalvik but I don't think that it makes that much of a difference in battery life (that should change by the time Android 4.5 comes out though).
Hope all this helps lol. But seriously, you posted in the wrong forum noob
i apologize for the mistake but in other forums i havent really been meet with such issues then again i suppose this phone is more popular then my previous ones. In any case i got around 4:30 hours right now, i was just hoping to get more out of it. I would expect a phone with such a huge battery to do 8 or 9 hours but maybe thats just too much
topdawg7793 said:
Don't listen to what anybody says: battery life isn't too ROM-dependent for our LG OG. I get the same battery life no matter what ROM I use. It all depends on your kernel settings. I get at least 4 hours of screen on time with the following settings in the Official CM11 rom with the LGE Gproj Kernel:
162 min, 1026 max, Wheatley with a powersave bias of 1, MPDecision ON (from what I've seen, it's better at turning off cores than the in-kernel implementation), max GPU at 128 if you don't plan on playing too many games with the interactive governor, Multicore Power-Saving set to 1, and -150 UV across the board (voltage for 162MHz starts at 650; I have a fast-binned E970). Also, I use auto-brightness but I've edited the brightness table heavily so it's JUST bright enough for most situations. I also keep GPS, Bluetooth, NFC, LTE, notification light, and cap keys off. My data is off whenever possible too. And every time before I turn off my device, I press Greenify's "hibernate now" widget to prevent any wakelocks. Lastly, I use ART instead of Dalvik but I don't think that it makes that much of a difference in battery life (that should change by the time Android 4.5 comes out though).
Hope all this helps lol. But seriously, you posted in the wrong forum noob
Click to expand...
Click to collapse
I consistantly get ~4 hours screen on with 384 min/1512max ONDEMAND. Everything else (undervolting, alternate governors, disabling radios) just hurts it for my OG.
Like honestly, Mine has gotten a lot better since I quite trying to do so much to it and just let it do its thing.
droidkeyboardfan12 said:
i apologize for the mistake but in other forums i havent really been meet with such issues then again i suppose this phone is more popular then my previous ones. In any case i got around 4:30 hours right now, i was just hoping to get more out of it. I would expect a phone with such a huge battery to do 8 or 9 hours but maybe thats just too much
Click to expand...
Click to collapse
You're never gonna see 8 to 9 hours on any phone for on screen time. I had a huge extended battery on my SGS3 and still got only 7 at best (4200mah battery)
Sent from my LG-E970 using XDA Premium 4 mobile app
well is there at least a rom that is more stable then others for this phone?
droidkeyboardfan12 said:
well is there at least a rom that is more stable then others for this phone?
Click to expand...
Click to collapse
From my personal experience. CM nightlys are very stable. I've read good things about mokee but haven't tried it out yet. I think CM with xposed framework and AC display from the play store is perfect.
I get about 3 to 3.5 hours screen time with about 12 hours off charger (this is with location turned off... Until Google fixes all the nlp wakelocks it's not worth having it turned on).
Sent from my LG-E970 using XDA Premium 4 mobile app
I still use the 4.4 beanstalk rom with the adreno kernel.. from my personal experience it's the best.. power saving wise..