HLCM->System->GDI->GLYPHCACHE
click values
highlight and chose limit
change value
default is 16384
change this to 32768 or 65536
Also what does omaping do and what is safe level to change it to on tornado? I have kavanna 6.1 and my dash is made in china i believe.
stats555 said:
HLCM->System->GDI->GLYPHCACHE
click values
highlight and chose limit
change value
default is 16384
change this to 32768 or 65536
Also what does omaping do and what is safe level to change it to on tornado? I have kavanna 6.1 and my dash is made in china i believe.
Click to expand...
Click to collapse
I know that changing those values will speed up the performance of the Dash in some capacity. I don't know exactly what speeds up, but there's a noticeable difference.
OMAPing (or overclocking) speeds up your phone's processor speed. The processor is set to 200mhz by default. Overclocking pushes the phone to perform at speeds higher than the suggested mhz of the processor. There's a BIG difference in the phone's performance, but there's also a RISK that your phone will lock up if set too high. I have mine set to 240mhz--and it runs beautifully. For a couple of days, I had it set to 252mhz--but it began to freeze at random times. Thus, I set it back to 240mhz. Just be careful going above 240mhz. I own a Dash/Excalibur, so I don't know what a safe clock speed will be on your Tornado.
Does increasing glyphcache maintain an application's normal running speed? i.e. does a video run faster, or normal?
Regarding overclocking, it would be nice if there was some level of dynamic switching. There was a tutorial for setting a different clock speed for when the screen's backlight is on or off. That would maximize battery usage and performance transparently. Anyone still running this scheme?
I have performed the Gyphcache tweak, but not sure how to re-set the processor speed. My system info says 201 Mhz, but tcpmp says it's running at 180. How can I raise it? I have T-mob 6.0 Standard (...I know...)
Thanks!
runningerin said:
I have performed the Gyphcache tweak, but not sure how to re-set the processor speed. My system info says 201 Mhz, but tcpmp says it's running at 180. How can I raise it? I have T-mob 6.0 Standard (...I know...)
Thanks!
Click to expand...
Click to collapse
Not quite sure how to overclock the 6.0 ROM. I'm running Kavana's 080408 6.1 ROM, and it has a pre-installed OMAPClock program which allows you to overclock. Just look for the standalone OMAPClock program on Google or some other search engine.
Download Rickys Extras
Go to the page for Ricky's remade ROM and download his extras. The OMAP clock should be in there. Once installed open it and it will set you processor to whatever speed you want, but make sure to not go over 240 like stated earlier. Don't trust the TCMP's info. Just listen to the OMAP clock. It works perfectly. Later.
runningerin said:
I have performed the Gyphcache tweak, but not sure how to re-set the processor speed. My system info says 201 Mhz, but tcpmp says it's running at 180. How can I raise it? I have T-mob 6.0 Standard (...I know...)
Thanks!
Click to expand...
Click to collapse
I have just used z4 root + milestone overclock to tinker with battery etc,
and i forgot to ask
what are the default Clock/Vsel settings?!?!
(i have been searching around)
thanks
800 Mhz 57 vsel
aikidoka90 said:
800 Mhz 57 vsel
Click to expand...
Click to collapse
really？ I even run 1.2Ghz @ 56 vsel, and it's stable.
the default cpu is 550mhz & the vsel is 56 for the milestone
Why not use SetVsel app? Its specially for the Defy and has a defaults button to restore back to defaults.
I think he means, because the stock speed is 800mhz, on which vsel is it running on? 57 is too much i believe because battery drains quite fast.
Is there a guide to using VSEL? I've downloaded and installed it but don't have much clue as to what settings I should try.
Although the settings seem to be quite high, but here are the standard settings for clock and voltage:
[email protected]; [email protected]; [email protected]
my settings (working like charm and not unstable):
[email protected]; [email protected]; [email protected]
PS: you might be able to go lower with the voltage, but use "apply at startup" only, when you're 100% sure that each setting is rockstable.
Hi,
My "defy" always had freezing and lag problems when I try to run heavy applications, such as 3D games, or Gmaps, etc.. in every ROM I've tried (CM7, MIUI, stock froyo, stock gb, etc.)
I read that a solution could be setting the minimum values of memory with an application called SYSCTL CONFIG (it's in the Market)
Anyone also has this problem? What values do you use? Increasing this value, can cause problems?
Code:
Mine are:
Min Free Kbytes: 8192
Dirty Ratio: 95
Dirty Background Ratio: 60
Pressure VFS Cache: 20
PD: This is the post I found: http://forum.xda-developers.com/archive/index.php/t-1047153.html
Same here ... : )
I had to use Sysctl config to set the min free Kbytes to 8192.
But all remaining parameters are left in default values.
Dirty Ratio = 20
Dirty Backgr. = 5
VFS Cache Pressure = 100
Can we get a thread together for battery values. I am looking to maximize my battery life and wanted to know what governor values to set for cm9 particularly
Format of the thread should be
battery uptime: 22 hours per charge
main usage: wifi/music/email vs heavy data useage
vsel values
1. 33 300
2. 48 600
3. 58 800
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?
zetsui said:
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?
Click to expand...
Click to collapse
This doesn't need to be in the development forum. But to answer your question, utilizing CLK 4/VSEL 4 requires the GB kernel.
zetsui said:
Can we get a thread together for battery values. I am looking to maximize my battery life and wanted to know what governor values to set for cm9 particularly
Format of the thread should be
battery uptime: 22 hours per charge
main usage: wifi/music/email vs heavy data useage
vsel values
1. 33 300
2. 48 600
3. 58 800
Why is it even in the bootloader when I set VSEL 4 that the max CPU in the CM10 menu is set to VSEL3? How can I enable VSEL 4?
Click to expand...
Click to collapse
My settings for all roms. I get usually get 24 hours plus no matter what rom I use, and that's with using live wallpapers as well. The only time I get less is when I'm using a ton of bandwidth online or playing games. I get better battery with the values in parentheses since 700mhz handles mid lever activity much better than stock 600mhz and doesn't need to jump up to vsel3 near as much.
1. [email protected] (or 18)
2. [email protected] (or [email protected])
3. [email protected] (or [email protected])
Governor is Boosted (You can also mirror these settings with Smartass or SmartassV2 -preferred- for similar results)
Settings Are:
bst_awake_ideal_freq 600000 or 700000 (whatever vsel2 is set at)
bst_debug_mask 0
bst_down_rate_us 60000
bst_max_cpu_load 88
bst_min_cpu_load 40
bst_ramp_down_step 300000
bst_ramp_up_step 150000
bst_sample_rate_jiffies 2
bst_sleep_ideal_freq 300000 (whatever vsel1 is)
bst_sleep_wakeup_freq 300000 (whatever vsel1 is)
bst_up_rate_us 80000
You can also get good battery with conservative with these values. If you get lag, either deal with it or lower con_up_threshold. If you don't mind slight lag, the set con_up_threshold to 100.
con_up_threshold 95
con_down_threshold 40
con_freq_step 8
con_sampling_rate 160000
You can't use vsel4 since that requires a gingerbread kernel, which requires you to be on a Defy; preferably a red lens so you can use the camera. Motorola never updated the Bravo past Froyo, so were stuck with the Froyo kernel and all the limitations because of that.
syllogyking said:
This doesn't need to be in the development forum. But to answer your question, utilizing CLK 4/VSEL 4 requires the GB kernel.
Click to expand...
Click to collapse
Completely missed that post yesterday....There already is a vsel\cpu governor thread for the Bravo here. You'll notice my settings have changed quite a bit from that post\thread, but the roms have gotten better so they work better with lower vsels now. I was in a hurry and didn't even think of linking to the other thread
Check this out http://androidunderground.blogspot.com.ar/2011/05/setvsel-overclock-and-undervolt-your.html
BravoMotorola said:
Check this out http://androidunderground.blogspot.com.ar/2011/05/setvsel-overclock-and-undervolt-your.html
Click to expand...
Click to collapse
Good link for the newbs. My only issue with it is I've never had good vsel2 time with ondemand's stock 86 threshold value. That may be due to the page being written for Eclair and Froyo Defy while I've done most of my tests on CM7, a few on CM9, and a few on GB MIUI.
With minor\no tweaking, anything is better than ondemand 86 to save battery life. IMHO it goes boosted\smartassV2 > conservative > interactive > everything else. Those 4 governors are the only one's I'd bother with since they work (no bugs; smartass), have noticeable changes in behavior when tweaked, and can be tuned to use vsel2 more than 3. Also, boosted/smartassV2 are based on both conservative and interactive and take features from both.
LG H440N 4G LTE kernel performance tweaks
FINAL VERSION
any other tweaks I find useful will be posted in the "init.d" section
{
"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"
}
Changelog:
27. December 2015 - added FINAL values. Everyone should use these. "They are nice!" - says Borat.
28. December 2015 - added a changelog. Heh!
29. December 2015 - added a super secret, secret testing zone. I dare you to find it. Note that it's well hidden!
30. December 2015 - new tcp tweaks in init.d section, screenshot how it should look like, Recently tweaks.
31. December 2015 - added a link to a web site with an excellent article on battery care. Added Kernel Adiutor tips by jonathansmith.
1. January 2016 - Added 7+ hours SOT settings in the testing zone. Happy New Year!
3. January 2016 - Since I achieved what I aimed for, I am taking a break from this thread. It will stay open, so feel free to keep on discussing.
18. January 2016 - Testing settings became default settings, with a few changes.
29. January 2016 - Low Memory Killer & swappiness value updated.
BATTERY CARE - a must read for everyone!
Disclaimer:
I am not to be held responsible if anything goes wrong. Simple as that. You do these mods of your own free will.
Warning:
Please, do not report issues or complain about lousy battery times/performance, if you've used any of those pre-made scripts that promise godly battery or performance - they often cause more trouble than they're worth, and are mostly snake oil. And often, you cannot easily undo those changes. If you run a lot of background apps ( for example, five different messengers that cause wakelocks or increased battery usage ), then this guide is not for you. Do not report issues if you've modded your phone with any audio scripts ( like v4a ), xposed, or anything like that! Do not report if you did any permanent system mods, period! These kernel are for CLEAN & STOCK phones, that are rooted ONLY. To summarize, I will not bother replying if you did anything to your phone besides the tweaks I recommend.
Nothing done here is permanent. Everything can be returned to stock in a matter of minutes, if you prefer so, just by uninstalling Kernel Adiutor, unfreezing the bloatware and power cycling the phone.
And hugs to all that pushed the "Thanks!" button. Hell, hugs for everyone!!!
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
BEFORE WE START...
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
Must be done before modifying CPU values:
Open your hidden system menu by dialing 277634#*#, go down to Power, find items "High temperature property" and "Thermal mitigation daemon", and set them like this:
High Temp Prop OFF
Disabled
Thermal Mitigation
Disabled
After that, turn phone off, wait 15-20 seconds and turn back on.. The screen will not dim in hot conditions anymore. Benchmarks are higher, games run smoother. And we can tweak our CPUs.
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
KERNEL ADIUTOR SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
Apply on boot time is to be decided by the user. Although Kernel Adiutor waits for boot complete, I noticed ( on few occasions ) that it takes more time to apply the settings properly. Why? Who knows. Depends on the number of apps you have running on boot, version of the firmware or how lazy it is on boot... Safest setting is 40 seconds, but 20 should cause no issues and is preferred. 10 can be a problem.
CPU:
CPU Maximum Frequency: 1209
CPU Minimum Frequency: 800
CPU Governor: interactive
*note: Minimum frequency is set to default 800, since Snapdragon 410 draws the same voltage on 200, 400, 533 and 800. That's the reason I set the frequency back to 800 idle. No need to go lower for absolutely no gain in battery life or performance.
CPU Governor Tunables subsection:
above_hispeed_delay: 20000 1094400:40000
go_hispeed_load: 80
hispeed_freq: 998400
min_sample_time: 40000
timer_slack: -1
DEFAULT ( 7+h SOT ) - target_loads: 1 800000:75 998400:80 1094400:85
PERFORMANCE ( smoother, few hours less SOT ) - target_loads: 1 800000:75 998400:80 1094400:80 1152000:85
timer_rate: 20000
max_freq_hysteresis: 40000
*note: Reason for system lags is found in the cheaper and slower memory LG has used for H440N ( my guess is, to cut cost ). You can test that yourself by running various I/O benchmark tools and noting speeds of random and sequential reads/writes. I did not manage to make that better in any way by tweaking the I/O schedulers, be it deadline, cfq or row - even testing some examples from Franco's Dev Team. Seems that it's best to leave it on cfq and cut overhead with the flashtweaks init.d script found later mentioned in this post.
Frequency changes happen VERY fast. So fast that CPU widgets or passive frequency readers have a lousy time keeping up. Only values you can trust are found in Kernel Adiutor's Frequency Table.
Those values found above are the best possible values for H440N's CPU for performance & battery saving, and I stand by them. If anyone else cares to try and do some tweaking to improve on those, by all means, please do so. If in the future I decide to add new CPU values, they will be strictly performance based, hence no battery saving.
Reason for the CPU frequency sticking to 1209600 is caused by the LG Home launcher. It contains a system call where, if you open up your apps drawer, it immediately ramps up the frequency to the max for almost 8 seconds or until you close the app drawer! That sucks, and is a lazy way for LG to provide smooth app drawer opening/swiping/closing! Bad LG, bad!!!
Two ways to solve that:
1. Spend less time listing through your apps drawer, since the frequency drops as soon as you stop swiping through it, or...
2. Freeze LG Home and use another launcher ( like Nova or Apex ), if you don't mind losing Double Tap to Wake, or work around that problem with launchers that support double tap gesture and link that gesture with a screen off app like this. Do not freeze any LG Home system apps, besides Easy Home. No need. System will automatically kill the unneeded launcher. Just follow my frozen bloatware list. Nothing more, nothing less.
Low Memory Killer values ( top to bottom ):
48
60
72
84
96
120
Virtual Memory:
vfs cache pressure: 100
swappiness: 80
Build prop Editor
dalvik.vm.heapsize: 174m
dalvik.vm.heapminfree: 512k
dalvik.vm.heapstartsize: 8m
dalvik.vm.heapgrowthlimit: 128m
dalvik.vm.heaptargetutilization: 0.75
dalvik.vm.heapmaxfree: 8m
*note: Dalvik tweaks are based upon Intel's recommended Dalvik tweaks for Lollipop phones with 1 GB RAM and xhdpi displays.
Init.d
1. Turn on "Emulate Init.d" and click that big "+" to create a new script.
2. Name the new script: flashtweaks
Contents of the "flashtweaks" script are:
Code:
#!/system/bin/sh
echo 0 > /sys/block/mmcblk0/queue/nomerges;
echo 2 > /sys/block/mmcblk0/queue/rq_affinity;
echo 512 > /sys/block/mmcblk0/queue/nr_requests;
echo 0 > /sys/block/mmcblk0/queue/iostats;
echo 0 > /sys/block/mmcblk0/queue/add_random;
echo 0 > /sys/block/mmcblk1/queue/nomerges;
echo 2 > /sys/block/mmcblk1/queue/rq_affinity;
echo 512 > /sys/block/mmcblk1/queue/nr_requests;
echo 0 > /sys/block/mmcblk1/queue/iostats;
echo 0 > /sys/block/mmcblk1/queue/add_random;
2. Name the new script: tcptweaks
Contents of the "tcptweaks" script are:
Code:
#!/system/bin/sh
#more reasonable tcp tweaks
echo 1 > /proc/sys/net/ipv4/tcp_low_latency;
echo 0 > /proc/sys/net/ipv4/tcp_timestamps;
echo 900 > /proc/sys/net/ipv4/tcp_keepalive_time;
echo 5 > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo 156 > /proc/sys/net/ipv4/tcp_keepalive_intvl;
Example of properly added scripts. I just named them differently:
Ignore the "99SuperSUDaemon" script unless you know what it is. It's not needed for our tweaks, and if you don't have it, it's perfectly fine.
Here are some screenshots on clearing / checking Kernel Adiutor's Frequency Table, by our fellow XDA member jonathansmith:
How to clear timers?
Check correct frequency usage.
Now, since you've finished with Kernel Adiutor, power cycle the phone. You're almost done. All that's left are:
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
OTHER SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
In Developer options, set animation scale values to OFF.
In Settings / Display / Brightness enable Night Brightness. Who needs anything over 0% brightness from midnight to six in the morning?
Visit Play Store and install these apps:
Recently by Chainfire
Trimmer (fstrim)
Recently! settings ( preferred ):
Age limit: No limit
Entry limit: 12
Apply on boot: Yes
Freeload: Checked ( yeah, we're cheapskates )
EVERYTHING ELSE DISABLED / UNCHECKED.
Recently! settings ( much faster version ):
Age limit: Running apps only
Entry limit: Running apps only
Apply on boot: Yes
Freeload: Checked ( yeah, we're cheapskates )
EVERYTHING ELSE DISABLED / UNCHECKED.
Do a "Clear all" in recent apps list after a reboot. It will make things faster. Believe me.
As for Trimmer (fstrim), run that every week or so, on "/data", "/cache" and "/system". No need to run it daily.
Apps frozen with Titanium Backup ( freeze bloatware, do not delete it - you'll thank me later ):
Chrome
Drive
E-mail
EasyHome
Gmail ( I am using Aqua Mail. )
Google Play Books
Google Play Games
Google Play Movies
Google Play Music
Google Play Newsstand
Google Search
Google+
Hangouts
HTML viewer ( do not disable if using stock browser or Chrome )
Internet ( I am using this version of Opera. It's the best one.
LG Keyboard ( disable only if already using another keyboard. I am using Smart Keyboard. )
LG Keyboard Black Theme ( disable only if already using another keyboard. I am using Smart Keyboard. )
LG MLT ( disable LG MLT in the hidden service menu before freezing it! Menu code is 277634#*# )
Live Wallpaper
Music ( both widget and app - I am using PlayerPro. )
Trusted Face
Weather
Weather Theme
WeatherPlatform
Do not touch anything else! Don't say I did not warn you.
If you prefer blocking ads on web sites, like I do... then download AdAway from XDA forum, and enjoy ad-free surfing.
That's it. Have fun, and enjoy your buttery smooth phone. One of this year's best-buy smartphones. Too bad it doesn't get the attention it deserves. Really, an unsung hero if there ever was one.
Although there are a lot of other CPU tweaking values throughout the thread, these values are the standard ones you should use. Other ones are experiments, or just plain testing values.
H440N is compatible with DriveDroid - in case you want to boot an operating system or a Linux distro off of it.
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
SUPER SECRET, SECRET TESTING ZONE
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
by WellHidden™
THESE SETTINGS BECAME THE DEFAULT SETINGS. SEE ABOVE.
With the latest test settings I achieved 7+ hours SOT. And yes, it can be done! You got the proof below.
Everything else besides these TESTING values below stays the same as in FINAL values ( dalvik, init.d, etc. ).
CPU:
CPU Maximum Frequency: 1209
CPU Minimum Frequency: 400
CPU Governor: interactive
CPU Governor Tunables subsection:
above_hispeed_delay: 20000 1094400:40000 1152000:20000
go_hispeed_load: 82
hispeed_freq: 998400
min_sample_time: 40000
timer_slack: -1
target_loads: 72 998400:82 1094400:85 1152000:86 1209600:90
timer_rate: 20000
max_freq_hysteresis: 40000
Virtual Memory:
Swappiness: 60 ( I recommend 100, but go back to 60 if you feel the memory gain is not worth a slight performance drop. )
Vellamo 3.2 scores:
My phone was originally set at frequency max 1200 and min 1200. After all the changes you suggest, do you set the min cpu frequency at 200 or leave it on 1200?
polfrank said:
My phone was originally set at frequency max 1200 and min 1200. After all the changes you suggest, do you set the min cpu frequency at 200 or leave it on 1200?
Click to expand...
Click to collapse
Min 200 Max 1200
Interactive / Noop
Other values as suggested.
But, damn. Those original settings must've drained the battery like hell... Are people at LG crazy?
EDIT: Sometimes, SetCPU will show the lowest frequency as 1200, but don't worry. Set it to 200, and verify it's at 200 in Times in state on the last SetCPU tab. It seems to be a bug in the app. That's why I used Kernel Adiutor.
ondemand + noop + lmk set to agressive and the phone flies like never before! looks like constant 60 fps. Thanks op!
Always glad to help out. Like I mentioned before, this phone has good hardware and is capable of stellar performance. Only problem is LG did not pay much attention on the tweaking side of things.
It's easy for them to tweak flagships
EDIT: Just found out about another gem! The app is called Recently by chainfire.
Installed, tried and it's marvelous even on default settings. I encourage everyone to try it. It's what Recent cards were supposed to be, in my opinion.
So I installed Busybox and Kernel Adiutor, set CPU min frequency to 200 Mhz, cpu governor to interactive and and I/O scheduler to noop. I've set both to apply on boot. Is that everything I need to do?
Fobos531 said:
So I installed Busybox and Kernel Adiutor, set CPU min frequency to 200 Mhz, cpu governor to interactive and and I/O scheduler to noop. I've set both to apply on boot. Is that everything I need to do?
Click to expand...
Click to collapse
It is, if you don't mind the default Interactive values. Otherwise, go a bit lower to "CPU Governor Tunables". Click that and set values as mentioned in first post. Those give a much better battery life.
After that, my recommendation is to visit the Low Memory Killer section and set that to Aggressive and apply on boot.
I can say that, after a bit of tweaking, this phone rocks! Glad to have bought it. Still hoping for a unlocked bootloader and maybe a CM port
Can you please take a screenshot of your CPU Governor Tunables section? I'm not completely sure that I did it right.
No problem, my good man. Here they are:
http://imgur.com/yDbXHE3
http://imgur.com/3uDi04u
holy ..! this really does make a difference. is it ok if i set cpu to "performance" and dont mess anything else with it? i dont care about battery life that much. cuz it seems that with agressive setting for ram, and changing to "noop" made wonders for me performance wise
Performance governor forces 1200, so that's not desirable.
For the best performance with lowest idle, set it to Ondemand / Noop. You will lose a bit more battery with those, but the phone will fly.
Otherwise, set as I've set it. Tweaked interactive.
userspace,powerspace hotplug and performance is what i have in karnel auditor.. which one should i choose then? tyvm!
p.s. thanks again for these tips man
That's strange. Are you using the LG Spirit H440N or some other variation?
See here ( list of governors ):
http://imgur.com/hxZOoDz
ah right. that could be a reason.. i use 3g version, with mediatek cpu
* moved to first post *
Tomo123 said:
Performance governor forces 1200, so that's not desirable.
For the best performance with lowest idle, set it to Ondemand / Noop. You will lose a bit more battery with those, but the phone will fly.
Otherwise, set as I've set it. Tweaked interactive.
Click to expand...
Click to collapse
amazing speed and multitasking (with Recently), thank you for this
Can you help me with target loads? Is this ok?
Sent from my LG-H440n using Tapatalk
String seems to be written ok, but my guess is it will clash with go_hispeed_load value.
If go_hispeed_load has a value of 85, then your initial value in target loads can't be "1". It must be higher than 85.
We're using our hispeed frequency ( 400000 ) as idle. It often drops to 200, so I see no reason of adding 200 to target loads.
Did you check out my post above?
Also, take a look at my KA frequency table:
http://imgur.com/BikoQk2
It seems that ive messed up something. Now my phone wont go deepsleep. This is the result over night.
Sent from my LG-H440n using Tapatalk
Can you make a screenshot of your target loads. Im having a hard time making it work. Performance is on point but i get a lot of battery drain.
Sent from my LG-H440n using Tapatalk