Database Develop

[krn.modules] overclocking for Arc (ICS) without custom kernels [now released!]

Update:
Use at your own risk, nothing is guaranteed!! Overclocking is dangerous and could brick your phone so be aware of what you are about to do!
If you want to take the risk, the files are below:
overclock_arc_ics_v1.zip
Install procedure:
1. The zip contains two files, overclock_12.ko and overclock_14.ko.
2. Unpack the two files onto your /sdcard folder
3. Insert one or the other using:
Code:
insmod /sdcard/overclock_1X.ko
where X is 2 or 4 depending on what frequency you want, 2 for 1200MHz or 4 for 1400MHz.
You can create a small script with the same contents and have Script Manager run it at boot time.
IMPORTANT: About frequency managers:
The CPU Managers are not perfect (I've tried SetCPU and No Frills).
They do not read the frequency tables from kernel - but as far as I can tell, they rely on the time_in_state file to see what frequencies are available. But if a frequency is changed, they remain disorientated.
THUS.
a) When booting the phone with any of the overclocking module there should be no problems, as long as SetCPU / NoFrills did not start and did not read the time_in_state file. Then no changes needed.
b) But if you start them and THEN you insert / remove the modules, etc - please go back to them and select again minimum frequency and maximum frequency EVEN IF they appear as already selected.
Just drag the first slider to the max and the second one to the min.
Also IMPORTANT:
Do not set the module at boottime unless you are absolutely sure the phone is stable with the frequencies. Otherwise you might end up in a boot loop.
PS: To other members trying to help: PLEASE DO NOT REPACK the archive and to offer it as update.zip or init.d scripts, etc.
I will do it in the next few days. The reason is that people get confused what to choose and then they ask questions about those .zips and so on. Better keep things simpler with minimal changes to the system (even these modules, they are very small, ~30kb ).
Enjoy guys - and thank you very much for your support!
Do not forget: for anyone interested, I posted a lengthly tutorial on my blog on how overclocking is achieved (disassembly and so on): http://hex.ro/wp/blog/overclocking-an-android-phone-running-with-an-msm-core/
--
I've managed to overclock my Arc (running Arc S latest ICS ROM) to run at 1200Mhz - all this WITHOUT a custom kernel and without the bootloader unlocked and so on.
I've read oppinions like this one: http://talk.sonymobile.com/message/184828#184828:
To Overclock you need to use a custom Kernel[ DoomKernel]. with Stock kernel overclocking not possible. To use a custom kernel you need to unlock the bootloader. [which is little bit sensitive]
Click to expand...
Click to collapse
This is plain wrong.
I will offer the module, but now is still in development, since the time_in_state table is still wrong (but that doesn't mean CPU doesn't go to 1200Mhz with any governor installed). Also, I don't know if I will ever fix the time_in_state since it is boring to disassemble - but it can be done.
Here are some screenshots:
1) Running at 1200MHz, but SetCPU insists the maximum frequency is 1024MHz - it probably uses some other values instead of the one on the /sys/devices/system/cpu ..
{
"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"
}
2) SetCPU Native Benchmark (at 1200Mhz it is around 600, and at 1024MHz it is arround 800 - lower is better)
Although things could have been easier if the kernel would export some symbols - nonetheless it can be done by using the /proc/kmem dump in a similar process described here http://code.google.com/p/milestone-overclock/wiki/Disassembly (but adapted to msm instead of omap2).
I will post a full article too - but I have to write it first - on how to do this...
If you guys are interested or having any questions, just post below ..

Great project man. o:
Btw how's the work coming along on those flashable modules ? Cause module loader loads the module randomly in the middle of a game and it gets stuck. :/

WOW.
please work on these..
i am on locked bootloader and dying to overclock.
do it. go go vulian
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
i want my arc to have cpu values that of an arc s.
oc to 1.4g with same cpu states as that of arc s.
my device is ready for testing. waiting for guide.
---------- Post added at 10:40 AM ---------- Previous post was at 10:36 AM ----------
+1000
please do it.
---------- Post added at 10:56 AM ---------- Previous post was at 10:40 AM ----------
i read the article. most of it went above my head. i understood few things though.

Nice try mate!
But why 1200 and not 1400Mhz like by default in Arc S?

thanks for the support guys
I did not try to go to 1.4 Ghz since I believe I need to up a bit the voltage and I did not yet identified kernel memory spaces where this has to happen.
I'm still looking to see if time_in_state can be adjusted - the table seems dynamically allocated and it makes its detection a bit more tedious since it doesn't have a fixed address in memory upon each reboot.
I'm wondering if it is needed to know what time in state is, seems more useful for battery saving but since the goal is to overclock ..

Good news - time in state table is fixed.
Noticed a few glitches with the time_in_state programs (mostly SetCPU).
Since the phone starts with 1024MHz but then is changed by the module to 1200MHz, some programs have small bugs because they remember the initial frequency. For example, after module is inserted, SetCPU somehow considers the minimum frequency to be 245MHz but a touch of the slider makes it go back to 122MHz.
This is now the only small inconvenience ..
Also, the smartassV2 module I've built has the max frequency set to 1024MHz, but I will recompile and offer them as a bundle to have 1200MHz hard coded. It is actually faster to have the speeds hardcoded instead of detected on the fly, since it makes the transitions quicker ..
Below few screenshots:
a) SetCPU showing correct Max frequency.
b) CPU Spy showing time in state ... it uses also deep sleep.
c) SetCPU bogomips:
One last thing...
I cannot add all Arc's S frequencies. It is easier to 'patch' the kmem and have the phone go to 1200MHz instead of 1024MHz instead of adding new values - because time_in_state table is allocated dynamically when phone boots to have 6 states. There's no space allocated for additional frequencies. If I add another value at the end (and patch the indexes) - some other variable put there by the kernel could be overwritten.
I could allocate the table in the module and update the global pointer to the new space - but it means more code which now doesn't seem necessary.
I will do some tests with 1400 instead of 1200 ..

keep going...
waiting for your release.
finally oc.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
not a worry for not implementing all Arc s frequencies.
in first hand, get this working..
thanks for hard work

VICTORY!!!
First, for happy side, here are the benchmarks:
a) AnTuTu 3373 vs 3069 (about 10% increase according to it).
b) Linpack 38.05 vs 33.5
Second, for drama side:
SetCPU native results from the initial posts above ended up to be fake. Don't know what SetCPU was doing but were incorrect. I'll explain.
Wanting to put some screenshots of OC improvements, I tried out Antutu and linkpack. To my surprise / shock, they were both offering the same values for the two speeds, 1200MHz and 1024MHz. I could not believe, how come the speed was now 1200 but results the same ???? Also, SetCPU did report an massive improvement, right ? From 800 down to 600 ...
Unconvinced, I found a PI Calculator, and tried it out with 10000 digits, it also reported same results 10.3 seconds .....
So ... going back to the source code I found out that frequency was actually controlled by the PLL rates and I was not modifying those, the CPU was actually phisically running at 1024Mhz. I lost trust in SetCPU with it's native tests (which now return about 500 when I finally fixed the code).
I thus dug more and found the correct PLL rates - and changed them to the real 1200MHz. Indeed the phone switched to the correct frequency and all performance tests above show the increase.
Tests were done with Performance governor on (max speed).
PS: PI Calculator now reports 9.3 seconds for 10.000 digits, and improvement of 10%.
I will release the module very soon now.

Hurray!
waiting for module and guide on how to implement it...
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
btw, this time I understood some of drama part.
improvement.

It will be very simple - just:
Code:
insmod overclock.ko
To run it at boot time, it can be done from GUI using apps as Module Loader or Script Manager (SManager).

viulian said:
It will be very simple - just:
Code:
insmod overclock.ko
To run it at boot time, it can be done from GUI using apps as Module Loader or Script Manager (SManager).
Click to expand...
Click to collapse
or use install-recovery.sh which works like init.d folder

viulian said:
VICTORY!!!
First, for happy side, here are the benchmarks:
a) AnTuTu 3373 vs 3069 (about 10% increase according to it).
b) Linpack 38.05 vs 33.5
Second, for drama side:
SetCPU native results from the initial posts above ended up to be fake. Don't know what SetCPU was doing but were incorrect. I'll explain.
Wanting to put some screenshots of OC improvements, I tried out Antutu and linkpack. To my surprise / shock, they were both offering the same values for the two speeds, 1200MHz and 1024MHz. I could not believe, how come the speed was now 1200 but results the same ???? Also, SetCPU did report an massive improvement, right ? From 800 down to 600 ...
Unconvinced, I found a PI Calculator, and tried it out with 10000 digits, it also reported same results 10.3 seconds .....
So ... going back to the source code I found out that frequency was actually controlled by the PLL rates and I was not modifying those, the CPU was actually phisically running at 1024Mhz. I lost trust in SetCPU with it's native tests (which now return about 500 when I finally fixed the code).
I thus dug more and found the correct PLL rates - and changed them to the real 1200MHz. Indeed the phone switched to the correct frequency and all performance tests above show the increase.
Tests were done with Performance governor on (max speed).
PS: PI Calculator now reports 9.3 seconds for 10.000 digits, and improvement of 10%.
I will release the module very soon now.
Click to expand...
Click to collapse
speak ENGLISH. lol. i can't understand, but, where is the overclock.ko? hehehe

The overclock.ko will come in two flavours
One for 1200000Hz another one for 1401600Hz.
I have posted an article on my blog on the procedure followed to create the module: http://hex.ro/wp/blog/overclocking-an-android-phone-running-with-an-msm-core/
I've tested the 1.4Ghz frequency with 1200mV voltage and it resets in Antutu towards the end of the 3D test. However, I've upped the voltage to 1250mV and I've ran 3 Antutus with no problems! But boy it gets hot.
Here are some benchmark results from 1024000Hz up to 1401600Hz
a) 37% in CPU Integer operations
b) 41% in CPU Floating Point operations.
This generates almost 20% increase in total performance!

viulian said:
I've managed to overclock my Arc (running Arc S latest ICS ROM) to run at 1200Mhz - all this WITHOUT a custom kernel and without the bootloader unlocked and so on.
I've read oppinions like this one: http://talk.sonymobile.com/message/184828#184828:
This is plain wrong.
I will offer the module, but now is still in development, since the time_in_state table is still wrong (but that doesn't mean CPU doesn't go to 1200Mhz with any governor installed). Also, I don't know if I will ever fix the time_in_state since it is boring to disassemble - but it can be done.
Click to expand...
Click to collapse
its very much possible...
if u have the time to get it working, here is MSM7x30 specific module for this type of overclock:
https://github.com/coolbho3k/vision_oc
viulian said:
The overclock.ko will come in two flavours
One for 1200000Hz another one for 1401600Hz.
I have posted an article on my blog on the procedure followed to create the module: http://hex.ro/wp/blog/overclocking-an-android-phone-running-with-an-msm-core/
I've tested the 1.4Ghz frequency with 1200mV voltage and it resets in Antutu towards the end of the 3D test. However, I've upped the voltage to 1250mV and I've ran 3 Antutus with no problems! But boy it gets hot.
Here are some benchmark results from 1024000Hz up to 1401600Hz
a) 37% in CPU Integer operations
b) 41% in CPU Floating Point operations.
This generates almost 20% increase in total performance!
Click to expand...
Click to collapse
just saw this
nice work with the how-to on the blog...

Thanks for the link.
I've checked it but is incomplete - it doesn't handle the time_in_state file ( cpufreq_stats_table kernel variable).
Mine goes on a similar route but :
a) handles the time_in_state
b) is unloadable (which the vision_hc doesn't do - it doesn't go back to stock if you want rmmod it). Mine switches back to stock.
But a good effort on that one also!
Will put them up tonight.

very nice, really looking forward the release to try it

Is it possible on the ARC S too ? Maybe 1.6 Ghz ?

@Dark Fable - About the Arc S - I could but I need remote access to a phone to be able to dump specific addresses into memory and adjust the constants from the code.

tRippinthehead said:
or use install-recovery.sh which works like init.d folder
Click to expand...
Click to collapse
How do you use install-recovery.sh to boot modules?
Sent from my SO-01C using xda premium

Thanks Vuilian.
i want to implement this.
what is to be done?
i find no modules in here.

[APP]LGP880 Booster v1.5.1 (ROOT)

This application was tested on JB (Android 4.1.2) and requires "root" permissions.
None of the settings are permanent. Default values will be restored when you restart your phone.
Download link: http://www.tazetaze.com/?dl_id=8 (53 KB)
LG Optimus 4X decreases CPU frequency after battery temperature reaches 43 °C to cool the device.
If you play a game for a long time, battery temperature reaches 43 °C rapidly and the game starts to lag because of frequency decrease.
This application sets the Tegra3 "temp_throttle_skin", CPU governor and GPU frequency values according to your preferences when you switch "Boost" on.
So you can play games with higher frequencies and more CPU cores without being effected by the heat increase.
Boost Preferences
Temperature threshold (temp_throttle_skin) value can be set to 46, 48 or 50 °C.
CPU governor value can be set to interactive (default), ondemand or performance.
GPU frequency (3D and 2D) value can be set to 200 MHz (default value), 330 MHz, 380 MHz or 416 MHz.
Your device may feel hotter than before after you set "Boost" on and play a game for a long time.
Other Functions
It's possible to see the CPU usage and frequency by setting the "Show CPU Usage" switch on. This has the same effect as enabling "Show CPU Usage" setting from the hidden menu.
If you enable "Unlimited Temp. Charging", you can continue to fast charge even if slow charge is activated because of high temperature.
New function: If you set "Keep Brightness" switch to "On", LCD brightness will be kept at the level you specify at the "LCD Brightness" preference. Temperature rise will not lower the brightness.
"Keep Brightness" function does not work properly for high temperature conditions.
Although brightness seems to stay at the level you specify in the notification tray, it is actually decreased when temperature rises.
This side effect occurs only when you play games for a long time with high temperature levels.
Please follow the new versions of "Tegra Overclock" application for a proper way of avoiding LCD brightness cutter.
Click to expand...
Click to collapse
WARNING
Use at your own risk.
Turn "Boost" off after you play your game.
Battery will drain faster when CPU governor is set to "performance".
Overheating may damage your phone hardware.
The code to change CPU governor was taken from the "No-frills CPU" project. Thanks to Luca Santarelli for making his project open source.
Shell commands to change GPU frequencies was taken from the "Tegra Overclock" application.
{
"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"
}
Release Notes
v1.5.1
If the kernel supports GPU frequency higher than 416 MHz, this maximum frequency can be selected in the GPU Frequency preference.
v1.5.0
"Keep Brightness" switch was added. Now you can keep brightness at the level you want regardless of phone temperature.
Note: This function requires that "Brightness Service" keeps running. If you kill the service with a task killer application, brightness will not be kept.
v1.4.0
"ondemand" CPU governor option was added to preferences.
Current CPU temperature is displayed under "Temperatures" section.
Minor user interface changes.
v1.3.0
"Unlimited Temp. Charging" functionality was added.
v1.2.3
Minor bug fixes
416 MHz was added to GPU frequencies list
v1.2.1
"echo 'Y' > /sys/module/tegra3_clocks/parameters/detach_shared_bus" command was added to program startup to prevent crashes that happened when GPU frequency was set.
v1.2.0
GPU frequencies for Boost can be set from "Boost Preferences" section.
v1.1.0
Temperature threshold and CPU governor values for Boost can be set from "Boost Preferences" section.
v1.0.0
First release

FC on kholk's CM10.1, ups!

I think this is for stock kernel only.

just a small tip from me, use more than 48°C for skin temp. i'd suggest at least 50.
'cause the throttle will kick in even before the temp_throttle_skin value is reached.
also performance gov is not the very best choice IMO. it produces too much heat, 'cause it would be enough to run @ 800MHz (or another freq, just as an example)
But nice work anyways

laufersteppenwolf said:
just a small tip from me, use more than 48°C for skin temp. i'd suggest at least 50.
'cause the throttle will kick in even before the temp_throttle_skin value is reached.
also performance gov is not the very best choice IMO. it produces too much heat, 'cause it would be enough to run @ 800MHz (or another freq, just as an example)
But nice work anyways
Click to expand...
Click to collapse
Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?

postacik said:
Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?
Click to expand...
Click to collapse
He was more suggesting another governor - interactive is fine, in my opinion.

someth1ng said:
He was more suggesting another governor - interactive is fine, in my opinion.
Click to expand...
Click to collapse
Interactive is the default CPU governor and is fine on JB but it really helped to boost games on ICS.
Maybe I can make CPU governor change optional.

New version (v1.1.0) was released.
CPU governor and threshold temperature settings can be adjusted under the "Boost Preferences" section.

Thanks for your precious comments.
So you recommend to set 50 °C for temp_throttle_skin, no change for CPU governor and 800 MHz for maximum CPU frequency.
Is that right?
Click to expand...
Click to collapse
partly yes
- I'd use at least 50°C for temp_throttle_skin.
- CPU gov, maybe ondemand, it "likes" higher frequencies --> good for gaming
- and no, please do not cap the freq it was an example of what is bad at performance governor. (800MHz actually needed, but it is forced to keep @1.7/1.5GHz)
but you could increase the min freq during gaming to 500MHz or something. that way the quad core stays online and doesn't change to LP mode. this can slightly improve the performance a bit

Can you suggest if i should add gpu frequency change option for boosting as in the Tegra Overclock application?
I would be glad if you have an optimum gpu frequency to play notoriously lagging games without any problems.
Some of my friends suggest setting gpu frequency to 416 mhz to play need for speed and real racing. Is that the right frequency?
Sent from my LG-P880

Nice idea..
Great idea for our 4X! :good:
will test it soon..
But, i think this should be moved to themes and apps..

New version (v1.2.0) was released.
Now you can set GPU frequencies to use for Boost mode.

Can a moderator move this thread to "themes and apps" section if that's the right place for an application?

postacik said:
Can you suggest if i should add gpu frequency change option for boosting as in the Tegra Overclock application?
I would be glad if you have an optimum gpu frequency to play notoriously lagging games without any problems.
Some of my friends suggest setting gpu frequency to 416 mhz to play need for speed and real racing. Is that the right frequency?
Sent from my LG-P880
Click to expand...
Click to collapse
well, the N7 uses 416 by default. this should be a pretty good value, regarding performance AND battery.
if you want more battery life, i'd suggest 330 MHz.
for really, really hardcore gaming 520 (564/600) MHz. but this will cause heat, too...
postacik said:
Can a moderator move this thread to "themes and apps" section if that's the right place for an application?
Click to expand...
Click to collapse
i'm on it

New version (v1.2.1) was released.
A missing setting caused the phone to freeze in version 1.2.0.
This problem was solved in v1.2.1.
Please uninstall v1.2.0 and install v1.2.1 to avoid crashes.

force close on rooted ICS when opening.

Emmanuel2000 said:
force close on rooted ICS when opening.
Click to expand...
Click to collapse
Which version? Since I have stock JB installed I don't have a chance to test it on ICS.

postacik said:
Which version? Since I have stock JB installed I don't have a chance to test it on ICS.
Click to expand...
Click to collapse
United Emirates
ICS 4.0.3 V10E Open AME
rooted with stock rom.

Emmanuel2000 said:
United Emirates
ICS 4.0.3 V10E Open AME
rooted with stock rom.
Click to expand...
Click to collapse
Can you try again with the attached apk?

where can i get latest version??
---------- Post added at 06:39 PM ---------- Previous post was at 06:25 PM ----------
postacik said:
Please do not use version 1.2.0. It makes the phone freeze when Boost switch is clicked. Install v1.2.1 instead.
Release Notes
v1.2.1
"echo 'Y' > /sys/module/tegra3_clocks/parameters/detach_shared_bus" command was added to program startup to prevent crashes that happened when GPU frequency was set.
v1.2.0
GPU frequencies for Boost can be set from "Boost Preferences" section.
v1.1.0
Temperature threshold and CPU governor values for Boost can be set from "Boost Preferences" section.
v1.0.0
First release
Click to expand...
Click to collapse
Where can i get latest downloads??
the link given is downloading old ver......

Chaos Kernel users' thread—tips, experiences, and NXTweaks settings

Hello everyone.
A few people in the Chaos Kernel development thread suggested that there should be a thread in the general section devoted to the use as opposed to the development of this great kernel.
For those who don't know, Chaos is a CAF kernel developed by @neobuddy89 for use with Cyanogenmod. Rather than being a place for discussing Chaos's pros and cons with respect to all the other great custom kernels available, this thread is for sharing the NXTweaks settings that we have found work well for us, whether this is with a view to achieving great performance, great battery life, or some balance of the two.
My own settings are based roughly on @neobuddy89's own settings that he posted several pages back on the dev thread. I'm looking for a solid balance between performance and battery, and I find that these settings deliver both (at least vs stock CM kernel).
Every setting not mentioned is left at the default setting for the built-in 'balanced' profile.
CPU:
PE WQ: enabled
OC: 2.496GHz
Gov: Intelliactive
Sleep gov: Conservative
IO: FIOPS
Sleep IO: ROW
Hotplug: Intelli HotPlug (eco mode disabled)
Colour Profile: Piereligio TrueRGB V7
Fast Charge: Auto
Cron zipalign task enabled.
What do you guys and gals think? (As an aside, I used to be able to oc to 2.576GHz on Chaos 10.2 with earlier CM11 M builds, but since Chaos 11 with M4, 5 and 6, I get an instant kernel panic as soon as I enable this. I'm going to post on the dev thread with my last kmsg when I hit ten posts. I don't talk much!) Specifically, what's your experiences with FIOPS vs ROW?
I find that this gives me an utterly smooth UX across every app, combined with enough battery to get me from 0700 to late in the evening. Sorry I don't have screenshots or SO states (or benchmarks) but I prefer to use the entirely subjective criterion of whether my phone *feels* fast and long-lived.
Hope people like this thread. Also, I'm new here, so sorry if I've got any etiquette wrong.
Edit: I should've said, I'm running a D821 N5 with CM11 M6, and the latest Chaos 12 nightly. I was on CM nightlies but I got sick of it.

Kernel: 12.0 5/12
Rom: SOKP MS-1
Profile based: Balanced
CPU:
PE WQ: enabled
UC: 1.728 GHz
UV: -20 MHz
Sleep Freq: 1.497 GHz
Boost Freq: 1.267 GHz
Sync Freq: 1.574 GHz
Gov: Intelliactive
Sleep gov: Intelliactive
IO: FIOPS
Sleep IO: Row
GPU: 320 Mhz
Polling: 14 ms
Hotplug: Cyanogen
DT2W: Enabled
Power key toggle: Enabled
Sound: Custom
Headphone: 260
Speaker: 262
Attenuation: 39
Mic: 260
Camera: 258
Colour Profile: Piereligio TrueRGB V7 / Vivid
Gentle Fair Sleepers: Disabled
Dynamic Fsync: Enabled
Fast Charge: Auto
Cron: All enabled
GPS: North America
Thanks for creating the thread =]

Kernel: Always latest.
Rom: AICP RC-4.0
PE WQ: Enable
CPU Freq: All Default.
UV: -25mV (from Kernel Tweaker)
Gov: Intelliactive.
Sleep gov: Conservative
IO: FIOPS
Sleep IO: ROW
Hotplug: Intelli-Hotplug (Eco Mode Disable)
GPU: Default
KSM: All Disable
Sound: Quality
Color Profile: Piereligio TrueRGB V7
Color Tweak: Stock
Dynamic Fsync: Enable
Cron Jobs: All Enable except Update Ad-Block.
This is my favourite settings and it's running great

fluther said:
My own settings are based roughly on @neobuddy89's own settings that he posted several pages back on the dev thread. I'm looking for a solid balance between performance and battery, and I find that these settings deliver both (at least vs stock CM kernel).
Click to expand...
Click to collapse
I have changed back to default settings of default profile with KSM, ZRam (for testing), Quality Sound, TrueRGB Color profile. :fingers-crossed:

Trying to change color profile display with nxtweaks but I'm not able to apply it
Used Franco display control and seems to apply correction Piereligio_v7
CM 11 build 05/12 and chaos latest nightly
Anyone?
Inviato dal mio Nexus 5 utilizzando Tapatalk

NXtweaks:
max CPU freq: 1.574
max CPU susp freq: 1.190
min CPU susp freq: 300
boost duration: 0ms
input event boost duration: 0ms
input event boost freq: 1.190
sync threshold: 1.190
cpu governor: interactive
cpu sleep governor: conservative
io sched: fiops
io sleep sched: fiops
hotplug: MSM
boosted cpus: 1
max cpus online: 2
max gpu freq: 200
polling interval: 30ms
gpu governor: MSM
dirty ratio: 20
dirty background 5
set ZRAM to 200MB
swappiness: 80
freq throttle: 65
freq throttle suspend: 60
core throttle: 70
core throttle suspend: 70
TRICKSTER MOD (beta tester app version):
tcp congestion: westwood
read ahead buffer size: 384
GOVERNOR (interactive):
above: 20000
go_hispeed_load: 99
hispeed_freq: 652800
min_sample_time: 20000
sync_freq: 300000
target_loads: 90
timer_rate: 20000
timer_slack: 40000
up_threshold_any_cpu_freq: 960000
up_threshold_any_cpu_load: 90
multicore power saving: 2
gpu max freq: 200
UNDERVOLTS:
300: -65
422: -65
652: -65
729: -65
960: -65
1574: -65
all the other: -50

giajp said:
dirty ratio: 20
dirty background 5
set ZRAM to 200MB
swappiness: 80
Click to expand...
Click to collapse
80 swappiness?? Any diff?

neobuddy89 said:
80 swappiness?? Any diff?
Click to expand...
Click to collapse
I don't know, try it. I always use this recommended settings by Faux
Sent with my Google Nexus 5

It seems that some of you are underclocking and undervolting quite aggressively. How does this work out for you in terms of battery? And how much does performance suffer?
@neobuddy89 is there any particular reason why you use KSM and ZRAM, given that the N5 has 2gb of ram already? Also, what's your take on the various governors and schedulers?

With the chaos is the only one situation when the performance doesn't suffer so much (try and give me your opinions). Battery incredible
{
"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"
}
Half WiFi, half data
Edit: @fluther i think the ZRAM, on CM11 is indispensable. The memory leak is still too strong, unlike stock/aosp
Sent with my Google Nexus 5

giajp said:
With the chaos is the only one situation when the performance doesn't suffer so much (try and give me your opinions). Battery incredible
View attachment 2744321
Half WiFi, half data
Edit: @fluther i think the ZRAM, on CM11 is indispensable. The memory leak is still too strong, unlike stock/aosp
Sent with my Google Nexus 5
Click to expand...
Click to collapse
Not to offend.....seriously.....but that is OK battery life..... And with all that under clocking and volting..... You've basically shown it is unnecessary. You've gained little, if anything doing it....and I imagine your performance must be suffering.
I think realistically.... You can under volt or under clock the phone into the ground and at best gain only minutes of screen time....and an hour or 2 overall total life.
Just my experience with it. Never touch clock and volts now.....there's no significant change to battery, yet performance degrades the lower you go.
My 2 cents. ?

lezzi said:
Trying to change color profile display with nxtweaks but I'm not able to apply it
Used Franco display control and seems to apply correction Piereligio_v7
CM 11 build 05/12 and chaos latest nightly
Anyone?
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Yeah, I have the same problem. Not sure why. It used to work just fine when I first flashed the kernel. Let me know if you figure it out.

Hi everyone. I said in the OP that I'm not terribly interested in benchmarks, and while this holds true, I though I'd share this great antutu result. However, I've a question: why the poor integer performance? @neobuddy89 ?
Sent from my Nexus 5 using XDA Premium 4 mobile app

fluther said:
Hi everyone. I said in the OP that I'm not terribly interested in benchmarks, and while this holds true, I though I'd share this great antutu result. However, I've a question: why the poor integer performance? @neobuddy89 ?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe because we use our own hotplug engine? Someone with more Antutu test knowledge might able to help.

Sorry, I should've said this was using intelliactive and intellihotplug.
Sent from my Nexus 5 using XDA Premium 4 mobile app

guys, got really frustrated with DT2WAKE issue, it could work flawlessly all day long, and all of a sudden it fails to wake the device up.
if i wait about one minute without using the power button, dt2wake works again and keep working for some time - then it happens again.
it happens on freshly installed and wiped system with all the latest nightlies of Chaos kernel + pacman rom.
from DEFAULT SETTINGS i only lower CPU freqs to 1.7
PE WQ on
GPU 320, polling 30ms
MSMhotplug with 2 cores
DT2W enable
color profile TrueRGB
vibrator strength 0
what can POSSIBLY relate to WAKE issue, any apps/settings? maybe nxtweaks are being killed in background? really annoying, especially while driving.
suppose to wake and get to dialer without looking and with one simple action, look at the phone once to find contact and dial.
and its like: look at the phone to check if DT2wake worked, if not try again, then slide the phone in palm to use the power button etc. etc.
i rely on this function and really need it working all the time.

oo0 said:
guys, got really frustrated with DT2WAKE issue, it could work flawlessly all day long, and all of a sudden it fails to wake the device up.
if i wait about one minute without using the power button, dt2wake works again and keep working for some time - then it happens again.
it happens on freshly installed and wiped system with all the latest nightlies of Chaos kernel + pacman rom.
from DEFAULT SETTINGS i only lower CPU freqs to 1.7
PE WQ on
GPU 320, polling 30ms
MSMhotplug with 2 cores
DT2W enable
color profile TrueRGB
vibrator strength 0
what can POSSIBLY relate to WAKE issue, any apps/settings? maybe nxtweaks are being killed in background? really annoying, especially while driving.
suppose to wake and get to dialer without looking and with one simple action, look at the phone once to find contact and dial.
and its like: look at the phone to check if DT2wake worked, if not try again, then slide the phone in palm to use the power button etc. etc.
i rely on this function and really need it working all the time.
Click to expand...
Click to collapse
As I told over PM, will clean up that code next week which may help..
Sent from my Nexus 5 using XDA Free mobile app

@neobuddy89, thanks! it's an old post. also, i guess, no one else has that issue. good thing - i have no SODs like many people reported with any of your builds. tested Furnace kernel for a while, dt2wake works perfectly, but having better battery with Chaos.

Anyone have a high performance set up that can be used for daily use that they want to share?
Sent from my Nexus 5 using XDA Premium 4 mobile app

JLO155 said:
Anyone have a high performance set up that can be used for daily use that they want to share?
Click to expand...
Click to collapse
Interactive governer,
sleep governor conservative
CPU 300-2500mhz
Hotplug see picture
After 2 load circles the battery consumption and performance is amazing (latest AICP nightly) with a sot time of ~5 hours with auto brightness. Regards, Matt

Changing CM11S Performance profiles with Tasker - Can it be done?

Note: I'm not referring to the CM Profiles such as Home, Work, etc.
I haven't purchased Tasker, nor have I used the program before. Is it possible to get Tasker to change CM11S kernel profile to Performance when screen comes on, and Power-saving profile during night hours? I am preferring Performance instead of Balanced at the moment because it makes quite a difference in responsiveness and smoothing out scrolling, but it's probably eating away at battery during non-use.
Or am I just better off waiting for a non-mpdecision custom kernel to be more stable and just use that instead? Franco for e.g.
{
"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"
}

U can modify the highest and lowest CPU frequency with tasker which is sort of what you're looking for

Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html

So I just updated my OPO to 30O and now Tasker says the CPU option is not available one my device.
Anyone know what is going on? Is there another option to use?
[UPDATE] Oops, I lost root.

Bump! I want this too...

I've used this but i noticed battery drain.

128
hmm i consider if it's needed to use Tasker on Lollipop

butro said:
Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html
Click to expand...
Click to collapse
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.

Frankyg said:
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.
Click to expand...
Click to collapse
That's how I have it set up but my profile is screen off. powersave when off, exit task (screen on) is back to balanced. I do like your wait a minute after screen off idea. I just implemented that. Thanks!

Thanks, this is what I was looking for. But why only CPU 0, do we not have to repeat the same for CPU 1,2,3. I guess CPU number refers to respective cores.
And how much is tasker effecting the battery discharge being in background.

I had up and downs using Tasker to set CPU Governor, so ended up using Boeffla kernel which supports this kind of management natively as described in the FAQ page: http://www.boeffla-kernel.de/index.php/faq.
Boeffla kernel has both CM 11s and CM 12 versions, so you are covered whichever ROM you are running.

it is possible, but not with tasker!
i will write an app therefore
it's just a hour task or so, will upload it to the playstore later this week.
i don't know exactly but i think you need to be rooted, but maybe i'm wrong, will look into it later

butro said:
Yes, you can modify the performance profile using Tasker but I you need to be rooted to change it. This is how I am using Tasker to change my CPU profile when my screen is on and off. Obviously you can change CPU settings on your own accord.
Screen off (powersave mode):
(leave CPU at 0)
CPU governor to powersave
max frequency to 1036800
(everything else leave alone)
Screen on (balanced mode):
(leave CPU at 0)
CPU governor to interactive
max frequency to 2457600
(everything else leave alone)
You don't have to limit the CPU frequency, but I figured it would be the best way to maximize the benefits of powersave mode, not to mention restricting any apps to crank up the CPU while phone is sleeping.
I would not recommend using powersave mode normally. The phone will become very unresponsive. However, I am setting my phone to screen off setting if battery is between 0-15%. That may change to 10% if if ever becomes troublesome.
Here are all the different governor settings: http://tasker.dinglisch.net/userguide/en/cpu.html
Click to expand...
Click to collapse
i have set cpu , i have set governor to ondemand but don't know what to do with scheduler. Also is there screen off and on setting in it ?

AAA118 said:
i have set cpu , i have set governor to ondemand but don't know what to do with scheduler. Also is there screen off and on setting in it ?
Click to expand...
Click to collapse
Not sure what you mean about the scheduler. But the screen off and on is controlled by a new profile. Add a profile and select event, then display off. When display off is active, you select your powersave task. The exit action of display off profile, or screen on, should be activating the ondemand task, returning the device to full speed.
I did it like this to have one profile to control that one action. More efficient than two profiles, one for screen on and off.

k.harish.r said:
Thanks, this is what I was looking for. But why only CPU 0, do we not have to repeat the same for CPU 1,2,3. I guess CPU number refers to respective cores.
And how much is tasker effecting the battery discharge being in background.
Click to expand...
Click to collapse
I'd like to know that, too.

Time delay for task... how?
Frankyg said:
What about having one profile to set the CPU to Balanced mode when the screen is on, and having an exit task to set it to powersave?
I think I'll try that, but maybe with a delay of a minute or two before running the exit task.
Click to expand...
Click to collapse
Hi there! How do you set the 1 minute delay to start task?? Thanks
For example, i have it set to display off, governor battery saving and 1036800 max freq and min 300000 freq, but i want it to start the task about 1 min later, becouse sometimes rigth away we go tether again, for some reason...

Anyone knows more about this nowadays?

aussieglis said:
Anyone knows more about this nowadays?
Click to expand...
Click to collapse
user boeffla kernel + tasker. just follow the guide from boeffla site.

Pure Nexus/Elementalx : CPU Throttling (Low Battery)

I am running the latest version of Pure Nexus, with the latesst version of the Elementalx Kernel. I have also installed the EX Kernel Manager. This is my first attempt at a custom kernel and it is working very well.
The only 'issue' I am having or the last hurtle I am trying to get over is the CPU throttling at low battery power. I haven't done extensive testing but in the small amount of testing I have done it seems that when the phone gets around 40%, the Max CPU speed reported in the EX Kernel Manager drops to 1958MHz, with all the cores still enabled. It will remain that way until I charge up the phone above approx 40%, and at that point it will go back to 28800MHz (max value).
I have tried this https://forum.xda-developers.com/nexus-6/development/mod-disable-throttling-battery-low-t3440814 but it doesn't seem to work for me.
Is there a way to achieve this through Elementalx itself. I believe if I change the CPU Gov. to Performance the CPU returns to its maximum value of 28800 MHz even under 40% but using the Elementalx Gov. yields such a good mix of performance and battery life I would rather keep it.
Any thoughts or suggestions welcome.
Thanks.

Just looking at it again...... I'm hitting a max CPU frequency of 1985 MHz earlier than expected. It has happened at 50% battery usage. I can also confirm that changing the Gov. to Performance will up the CPU to the expected, max, value of 2880MHz.

I have discovered a couple things..... First, throttling, from the posts I have read means ' Throttling is turning cores off at lower percentages and keeping frequencies down, not at regular.' So the issue that I am experiencing is not throttling entirely as I have all 4 cores working throughout the battery range. What I do have happening and want to resolve is the Max CPU value, in Ex Kernel Manager changing from 28800 MHz, which is the maximum CPU frequency I have set, to 1958 MHz when the device battery drops below approximately 45%. Second... Changing the CPU Gov., while the battery is under 40% (1958MHz), will increase the CPU frequency back to 28800MHz until the phone drops another battery percentage, which will trigger the underclock (1958Mhz).

EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Phone was at 43% and running at an underclocked speed of 1958 MHz. Made the changes in EXKM to the Mode file and enabled the 'Apply on Reboot'. Rebooted the phone. Once booted took a look at EXKM and the CPU speed was still underclocked at 1958 MHz. Check the Temp and it was at 45. Checked EXKM and the CPU temp threshold is set for 60. Didn't change the ofc value. I don't want to disable the thermal as I don't want to damage the hardware accidentally. I also couldn't find the value. It isn't in the Mode file. Where could I find that? Is the ofc file required as well to allow this method to work?
I will continue to tinker.
Thanks for the reply and your help.

ofc= of course. [emoji12]
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Sent from my Nexus 6 using Tapatalk

nemanja066 said:
ofc= of course. [emoji12]
Click to expand...
Click to collapse
Lol! Oops.....
For me, work ok, only edited thermal conf file (cpufreq, hotplug, gpu threshold 100 threshold clear 99). Please wait some time to.phone cooling down (sleep phone 10-15 minutes) and open EX Manager and see again. Sometimes does not change max freq value at the begining. At least, i had this situation.
Click to expand...
Click to collapse
Thanks for the reply. I'm getting closer. I am able to run at 28800 Mhz until 20% battery life and then it underclocks to 1958 MHz on all cores. This is definitely a step forward. Below are the three sections you referred to, CPUFreq, HotPlug, and GPU. This is the modified file. My understanding of what this configuration accomplishes is that at 5% battery power the CPU will throttle back (underclock) to conserve battery power. Unfortunately this isn't happening.... yet.
Any other ideas on why this isn't working as expected? Is there another part of the file that needs to be changed?
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 95
thresholds_clr 94
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 90 92
thresholds_clr 89 91
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 88 90 95
thresholds_clr 89 89 94
actions gpu gpu gpu
action_info 600000000 389000000 300000000

@monteie2016
I find your shamu thermal conf file a bit strange. I have a pure nexus and elementalx and it's not like that. All you need to edit in this file (with text editor) is set the thresholds to 100 a thresholds_clr at 99.
Thresholds is the battery percentage at which the throttling occurs (at 0% (100-thresholds))
Thresholds_clr is the battery percentage at which the throttling clear (at 1% (100-threshold_clr)).
In practice, this will never happen because in that time your device is already dead.
I will upload a screenhoot of EXKM dashboard to see max freq in my case when battery was bellow 20%. It's stay on 2.6 Ghz.

Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:

monteie2016 said:
Can you also post the CPU, GPU, and hotplug values. I would like to see how yours is configured.
Thanks
:good:
Click to expand...
Click to collapse
Also, I have an older version of the elementalX 4.23 as you can see on screenshot (with july security patches) , because the PureNexus rom does not have august and september kernel patches.
Here is SS thermal conf:
[emoji106] [emoji482]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk

Couple of things...... Above you are showing me a status from EXKM at 62% battery. I don't have and underclock issue anywhere between 100% and 20%. When the battery life drops below 20% is where I get the issue (Underclocks to 1958Mhz from 2880Mhz).
Here is what my file looks like
sampling 5000
[BAT-SOC-CPUFREQ]
algo_type monitor
sensor soc
sampling 5000
thresholds 100
thresholds_clr 99
actions cpu
action_info 2649000
[BAT-SOC-HOTPLUG]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100
thresholds_clr 99 99
actions hotplug_3 hotplug_2
action_info 1 1
[BAT-SOC-GPU]
algo_type monitor
sensor soc
sampling 5000
thresholds 100 100 100
thresholds_clr 99 99 99
actions gpu gpu gpu
action_info 600000000 389000000 300000000
I should also mention that I have disabled BCL, /sys/devicds/qcom,bcl.39/mode and changed the value to disabled.
I have attached two images. One is the battery at less than 20% and what I am seeing for CPspeed (underclock) and the other is above 20%.

Off topic thoughts @monteie2016
What you had asked for was posted in the previous post. The additional information was provided additionally. But you jumped on the extra info. And not one time in this thread have you "thanked" (thumbs up) the only person who had been trying to help you.

I did thank nemanja066 for his post on 20th September 2017, 04:51 PM (thanks button in thread) and my reply on September 23rd had a thanks and a thumbs up.
Also is there a resource that explains what each line in these files do? I couldn't locate one.
Thanks!
:good:
Click to expand...
Click to collapse

[emoji106] No throttling yet.
I will post SS for battery bellow 15%, too.
Sent from my Nexus 6 using Tapatalk

@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.

nemanja066 said:
@monteie2016
Looks like a bug with the aroma installer. Try again with flashing kernel in recovery and then in aroma set max freq cpu to 3033MHz. After flashing, reduce the frequency to the desired one in EXKM. After that, it might be fine, and the freq can be reduced only due to the increase in temperature, which is quite OK. When the phone cools down, freq will go back to the old value. If all this fails, then I do not know what to do next.
Click to expand...
Click to collapse
Thanks for the information. I will take a look at it later. Got busy doing other things
:good:

nemanja066 said:
EXKM - Tools- User Settings Navigate to file sys/devices/qcom,bcl.39/mode and set "disabled".
And, ofc, edit threshold (99) in thermal conf file.
Click to expand...
Click to collapse
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.

ozzmanj1 said:
Hello, just curious if you can specify the file location of the thermal config file? Thank you for your help.
Click to expand...
Click to collapse
/system/etc/thermal-engine-shamu.conf
Sent from my Nexus 6 using Tapatalk