Related
I know this thread is repeated everywhere, but I thought I'd start it up for our GNote forums
What are your Tasker profiles? I just found out how to use Tasker yesterday and I find myself loving it.
Mine are as follows:
1) Incoming Calls - Decrease volume to second lowest setting (I have loud friends)
2) Turn wifi on at home automatically
3) Open PowerAmp when headphones are plugged in
4) Send a "Happy Birthday!" text to various people on their birthdays.
5) Alert me when battery is full to 100%. Really useful if you don't want to overcharge your battery.
What about you guys?
Mute at work locations
Pandora + Bluetooth in car
Wifi at home
100% Battery alert
Auto-off unpaired Bluetooth
Regulated auto-sync based on battery
Long-press search changed to notification drawer open
Screen timeout change for various apps
Data off and screen timeout change for ad-supported games
I posted a couple just recently in this thread...
http://forum.xda-developers.com/showpost.php?p=23151996&postcount=25
Here's a C&P for the lazy....
______________________________________________
Car Profile
Enter Task
1) Disable PIN Security so I don't need to unlock my phone while in the car (one less distraction)
2) Set Media Volume to 15
3) Turn Wifi off
4) Change Display timeout to 30 minutes (nice for google maps and viewing the album art of the streaming music)
5) Turn on GPS IF power is connected to phone
6) Start recording video with DailyRoads Voyager ( A car DVR program in case of an accident so you then have Objective evidence)
7) Play the THX sound after a couple seconds to make sure the Bluetooth audio streaming is working right
Car EXIT task
1) Stop Recording Video for DailyRoads Voyager (DRV)
2) Wait 5 seconds
3) Kill App - DRV
4) Perform Task - PIN ON
5) Secure Settings - Disable GPS
6) Display Timeout - 2 min
7) WiFi - Turn ON
8) Bluetooth - Off
9) Display Brightness - Set to 150 out of 255
Other fun stuff
Home VAR %STATUS_HOME
Set VAR for when I am near my home micro-cell as the signal radius is small and specific to my house. I use this since the phone part is always on and I don't need to use GPS to determine location which uses more juice. That VAR is then used to turn on wifi when I arrive at home, disable PIN again, Flash "Welcome home", set WiFi sleep to Never. The Exit task for when I leave home turns PIN ON and sets the WiFi sleep policy to Never While Plugged"
Power VAR %STATUS_POWER
I have 2 seperate profiles for when I am connected to AC or USB power. The AC one sets the power VAR to 2 while the USB one sets it to 1. Both are used for other tasks and profiles, like the car one above requires AC connection so my GPS doesn't drain my battery even while connected. I have it flash "AC connected" or "USB connected" to let me know if the phone is receiving the correct amount of juice. When both of them exit they set the Power VAR to 0 and flash "Power Disconnected"
Sleepy Time
Profile conditions
1) Time - From 00:01 to 06:30
2) State - Home VAR = 1 (so this doesn't happen when I am out and about somewhere at night)
Enter Task - In case I'm tinkering with the phone in bed and don't want to keep the wifey up with a blazing screen and vibrations when clicking buttons. Also prevents annoying sounds at night by disabling data sync and muting all but the Alarm audio.
1) AutoSync -OFF
2) Flash "Good night"
3) Display brightness at 0
4) Screen Filter set to 25%
5) Perform Task - Alarm Audio only
Alarm Audio only task above
1) Alarm Volume - 4
2) Flash "Alarm Audio Only"
3) Haptic Feedback - Off
4) Notification Volume - 0
5) Ringer volume - 0
6) System volume - 0
7) Media volume - 0
Exit Task
1) AutoSync - On
2) Display Brightness - 255
3) Screen Filter - 100%
Quick Stats - This has two parts. One is the Notification that tells me a bunch of info I like to know like Battery level, Screen timeout, screen brightness and CPU govenor. The second part is launching a menu whe nI click on the the notification that has the commonly used Screen brightness & timeouts I use. I need to add some audio options in there too. I re-discovered that menu was there the entire time and didn't see the + button add more items to the menu. Iwas over complicating it by trying to use Scenes as a pop-up menu. Still need to learn more about Scenes.
Part 1 - Quick Stats Notification
State - Orientation Face Up (I use this state so if I want to refresh the stats all I do put the phone face up. There is automatically a time stamp so I can know when the stats were last updated)
Task - Notify Quick Stats
1) Notify - with Battery level, Screen timeout, screen brightness and CPU govenor variables as the text.
Part 2 - Notification Bar Tool
Event - Notification Click
Task - Quick Stats Menu
1) Menu with options for display brightness at 0, 100 or 255. Display timeout options for 30 secs, 2 min, 10 min and 30 min
Remote PIN Disable - This is for in case I forget my pin this will disable the PIN likew used in the Car and Home profiles. It is triggered by receiving a text from certain people with a specific phrase.
Event - Text with specific phrase under Content
Task - PIN OFF
Where Are You - Here's a 3 part setup. If I can't find my phone I again send a text with a specific phrase that then cranks up all volume settings to MAX and repeat "The Most Annoying Sound in the world" by Jim Carrey from Dumb & Dumber. The text sets a VAR called %SHUTUP to 1. When %SHUTUP = 1 it triggers Part 2. Once I find the phone to set the VAR back to 0 I shake the phone.
Part 1 - Where Are You Status
Event - Received Text with specific phrase
Task - Variable Set - %SHUTUP = 1
Part 2 - Where Are You Status
State - Variable Value = 1
Task - Where Are You Audio
1) Perform Task - Crank It Up (sets all volumes to MAX)
2) Flash - "I'm over here!"
3) Music Play - Annoy.wav
4) Wait - 15 sec
5) Goto - Top of Loop IF %SHUTUP = 1
Part 3 -Shutup Shake
Event - Shake
Task
1) Variable Set - %SHUTUP = 0
2) Flash "SHUT UP!!!"
A couple more but they are straight from the Tasker Wiki
I'm definitely going to have to do those. Right now, all I understand is the basics of Tasker (no where near Variables) but I'll follow your instructions.
Thanks especially for "Where are you"
A few I use....
1). Pocket Lock - Detects when phone is upside down in my pocket and activates WidgetLocker.
2). Read Caller Aloud - Incoming caller name said aloud so I can decide whether I want to answer without looking at my phone.
3). Night Mode - From 00:00 to 06:00 Puts phone into silent mode, plus checks whether Wifi, Data, GPS, or Blutooth are on, and turns them off if they are.
4). Battery Low - When battery gets to 15%, and it's not connected to a charger, Says "Battery low, connect charger" and turns off Wifi, BT, Data, GPS.
5). Music Player - When headset is plugged in, loads music app.
6). Home - Gets general location from cell tower, activates Wifi, disables Data & GPS. Exit Task disables Wifi, and enables Data.
7). Work - Gets general location from cell tower, disables Wifi, Data, GPS, BT, and Auto Replies to sms that im working and will reply when i can.
I'm pretty new to tasker, but have been pretty bored lately and have been working on an addition to my Work profile.
This profile will, use variables to save up to 5 peoples numbers and how many times each has txted me, and txt each of them back, using their names from my contact list in the body of each txt.
So lets say BOB txts me once, his number will be added as a variable, and it will begin counting the txts from him. On the first txt he is send a txt saying, something like. "Sorry BOB, im at work, will reply when i can".
Then DAVE txts, he will be assigned to Sender2, and have a txt sent to him like above, with the second Counter and Number (%CNTR2 and %SNDR2).
BOB, realizing it's an auto-reply, decides to be funny and spam txt me, thinking he will get a reply every time. However, tasker counts his incoming txts, (%CNTR1) and when it reaches a value of 10, send just one more txt saying something like (Thats 10 txts you've sent, seems Im still unavailable).
Profile: Auto Reply
Variables:
%SNDR1 <---- BOBs cell number
%SNDR2 <---- DAVEs cell number
%SNDR3
%SNDR4
%SNDR5
%CNTR1 <---- BOBs txt counter
%CNTR2
%CNTR3
%CNTR4
%CNTR5
%TXTVAR <---- Counter determining whether a txt received is from someone new or a number already saved.
Enter Task:
Code:
1). GoTo label Sender1 if %SMSRF ~ %SNDR1
2). GoTo label Sender2 if %SMSRF ~ %SNDR2
3). " " etc.
4).......
5).....
6). If (%SNDR1 ~ 0) then SetVariable %SNDR1 to %SMSRF
7). If (%SNDR2 ~ 0) and (%TXTVAR = 1) then SetVariable %SNDR2 to %SMSRF
8). If (%SNDR3 ~ 0) and (%TXTVAR = 2) then SetVariable %SNDR3 to %SMSRF
9)........etc.
10).
11). If (%SMSRF ~ %SNDR1) <-------- Label Sender1
Variable Add (%CNTR1 + 1)
If (%CNTR1 = 1)
Send SMS (Tells this person eg. BOB I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR1 = 10)
Send SMS to %SNDR1 (Thats 10 txts you've sent me)
Endif x2
12). If (%SMSRF ~ %SNDR2) <-------- Label Sender2
Variable Add (%CNTR2 + 1)
If (%CNTR2 = 1)
Send SMS (Tells this person eg. DAVE I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR2 = 10)
Send SMS to %SNDR2 (Thats 10 txts you've sent me)
Endif x2
13). If (%SMSRF ~ %SNDR3) <-------- Label Sender3
Variable Add (%CNTR3 + 1)
If (%CNTR3 = 1)
Send SMS (Tells this person eg. EMILY I'm at work)
Variable Add (%TXTVAR + 1)
Else If (%CNTR3 = 10)
Send SMS to %SNDR3 (Thats 10 txts you've sent me)
Endif x2
14). ......Etc.
15). ......
I'm still working on it, deciding whether to have the variables reset as they are all filled, 1 at a time, or to make them reset every hour or so. Also whether to make another profile purely for resetting those variables, or add them to this task. Bearing in mind that on my phone it gets rather annoying to manage/edit the task since its currently at 78 lines long.
As I said I was bored.
If anyone is interested in this I can post a backup xml of this somewhere.
TriggerSpasm said:
BOB, realizing it's an auto-reply, decides to be funny and spam txt me, thinking he will get a reply every time. However, tasker counts his incoming txts, (%CNTR1) and when it reaches a value of 10, send just one more txt saying something like (Thats 10 txts you've sent, seems Im still unavailable).
[...]
As I said I was bored.
Click to expand...
Click to collapse
Bored indeed. Anywho, look into arrays in Tasker, that'll make this tracking stuff much easier. Track all of that stuff in one array vs a bunch of different ones. Might clean up the code a little, make it easier to erm.. relieve more boredom?
khaytsus said:
Bored indeed. Anywho, look into arrays in Tasker, that'll make this tracking stuff much easier. Track all of that stuff in one array vs a bunch of different ones. Might clean up the code a little, make it easier to erm.. relieve more boredom?
Click to expand...
Click to collapse
Thanks, I certainly will.
Using Tasker http://www.pocketables.com/forum//showthread.php?t=9680
Scripted Backups using Tasker and TWRP http://www.pocketables.com/forum//showthread.php?t=11435
Beginner’s guide to Tasker http://www.pocketables.com/tag/beginners-guide-to-tasker
Tasks to:
(1) Take photos and email them when a specific text message is received
(2) Lock and password protect the phone when a specific text message is received
(2) Use different keyboards depending on the open app or screen orientation
Ktoonsez presents:
{
"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"
}
KT-SGS5 kernel features
•Must have a S5 model G900T or G900P or G900V (Dev Edition ONLY!!!) or G900F or G900M or G900W8 or G900I
•Must have a Touchwiz Rooted ROM
•Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•KTweaker app for kernel control
•KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz and AOSP
•F2FS compatible with AOSP 4.4, 5.0 and 5.1
Click to expand...
Click to collapse
Touchwiz Lollipop 5.0 VERSION:
05.02.2015: http://bit.ly/1EN5UtG
Click to expand...
Click to collapse
AOSP Lollipop 5.0 VERSION:
05.02.2015: http://bit.ly/1JJhnxv
Click to expand...
Click to collapse
AOSP Lollipop 5.1 VERSION:
05.02.2015: http://bit.ly/1DTVhBf
Click to expand...
Click to collapse
TWRP Recovery by Ktoonsez:
04.06.2015: http://goo.gl/LgBsuk
Click to expand...
Click to collapse
AOSP /system F2FS converter:
03.31.2015: http://bit.ly/1IOdXpX
Click to expand...
Click to collapse
What you can expect to get benchmark wise:
******* END OF LIFE *******
Touchwiz Kitkat 4.4 VERSION:
02.26.2015: http://ktoonsez.jonathanjsimon.com/sgs5/TW/KT-SGS5-KK4.4-TW-G900-02.26.2015.zip
Click to expand...
Click to collapse
AOSP Kitkat 4.4 VERSION:
11.06.2014: http://goo.gl/t3H5oK
Click to expand...
Click to collapse
KTweaker Shop and previous versions can be seen here (thanks to LuigiBull23):
http://forum.xda-developers.com/showthread.php?t=2784319
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
Post #2 will be reserved for change logs
Post #3 will be reserved for MY Settings, Extras and FAQ's
Sources can be found here:
https://github.com/ktoonsez/KTSGS5
Change Log 05.02.2015
1. KTweaker 9.3
2. Cleaned up some FC issues
3. "Get Phone Information" screen was pretty'd up and added CPU "Time in State" grid including Deep Sleep and Total up Time items.
4. ktoonservativeq: Adjust alloc_workqueue(). Remove WQ_UNBOUND to assure it always runs on CPU0 and add WQ_CPU_INTENSIVE to assure these work items will not prevent other work itemsin the same worker-pool from starting execution. This is useful for bound work items which are expected to hog CPU cycles so that their execution is regulated by the system scheduler.
5. CM ramdisk updates.
Change Log 04.06.2015
1. Removed the RED text when booting that warns about NOT SEANDROID ENFORCING for TW 5.0 and AOSP 5.0
Change Log 04.05.2015
1. Merge in ramdisk update for CM call lag problem
2. Removed the RED text when booting that warns about NOT SEANDROID ENFORCING
Change Log 03.27.2015
1. fastcharge: Add some blocking code for functions reducing chargin current and setting some variables for 3rd party apps
2. cpufreq: Add some protection when setting policy changes. Add some disabled debug messages in case I need them later. Remove usleep call after calling cpu_up()
3. cpufreq: Add main_cpufreq_control global var to make other modules aware that the main cpufreq code is bringing a core up so they will not take the core down.
4. ktoonservativeq: Modify some code to make sure hotplug cores obey touch_boost_cpu_all_cores during boostpulse while sync cores is off
5. cpufreq: Disable some extra booster code on wake for testing
Change Log 03.25.2015
1. ktoonservativeq: Totally revamped
2. NEW tunable lockout_changes_when_boosting used to lockout changes to frequency and hotplugging activities during touch/button boost (this basically makes touch boost behave the old way before all the new code)
3. NEW tunable cpu_load_adder_at_max_gpu_ignore_tb used to ignore gpu cpu load adder during a touch/button boost
4. Modified all global vars placement so governor can run on all 4 cores instead of controlling them thru proxy
5. Optimized code adding more sub functions to reduce code
6. Moved global counters into cpu_dbs_info_s struct so each core keeps there own version
7. sing new debug_enabled tunable from previous commit added a few more debug lines for keeping track of load and hotplugging activities
8. All hotplugging activities are mutex protected
9. Added some more effective boost code upon wakeup
10. KTweaker version 9.1
11. KTweaker: Fix up previous screen tracking for Governor Adjustments screen
12. KTweaker: Will now set the selected governor to ALL 4 CORES!
13. Ramdisk update for AOSP version from CM latest
14. New ktoonsified v4 in Shop for new kernel, works great on TW or AOSP, currently running TW and I can not believe how much faster it is on this new version!!!!!!!!!!!!!!!!!!!!!!!!!
Change Log 03.22.2015
1. ktoonservativeq: Optimized ktoonservatieq governor during boost sequence (more from the previous test) and a bunch more cleanup and fixes for hotplugging and mulit-threaded flags.
2. ktoonservativeq: Added new tweak item called "debug_enabled", this will enable some cpu info that can be viewed using the "dmesg" command in adb shell.
3. Added ktoonsified v3 profile to Shop
4. ktoonservativeq: Optimize the boost sequence to allow upscaling during a boost
5. Merge OB1 from TMO source drop
6. video: mdss: Color temperature interface using PCC
Change Log 03.18.2015
1. CM ramdisk sync.
Change Log 03.10.2015
1. CM ramdisk sync.
Change Log 02.25.2015
1. Changed KTweaker to remember to go back to Profile/Script type list when pressing back button from the List of profiles in that type.
2. Changed KTweaker to remember to go back to the 3 choices of ktoonservativeq when pressing back button from Governor Adjustments
3. Fixed touchscreen issue with certain games like Snes9x EX+ thanks to @DevVorteX!!!!!!!!!!!!!!!!!!!!!!
4. Updated ramdisk for TW 5.0 to OB1.
5. FINAL build for TW 4.4
Change Log 02.25.2015
1. Set TW 5.0 SELinux to permissive.
2. Updated ramdisk for AOSP version.
3. KTweaker version 9.0!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
4. Added slider drawer for easy navigation
5. Profiles and set on boot options can be easily loaded from the drawer
6. Menu button still retained the easy navigation items like CPU, GPU, Scheduler Settings....
7. Old "Tools" screen is now called "Utilities"
8. New "Utilities" item: SELinux changer
9. New "Utilities" item: Get Phone Information
10. New "UI Settings" item: Startup Drawer Status is used to set whether the drawer is open or closed when starting the app
11. New "UI Settings" item: Startup Screen is used to set which screen starts up when opening the app. You can pick from the list of screen available for startup or specify "Remembeer last screen" to make it go back to the last screen you were on.
12. New "UI Settings" item: Main Background is used to set the color or an image to be used as the background in the main part of the screen. I have predefined ones and you can also pick from a image that you place in the /KTweaker/ThemeManager/Backgrounds folder
13. New "UI Settings" item: Main Fore Color is used to set the color to be used as the fore color in the main part of the screen.
14. New "UI Settings" item: Drawer Background is used to set the color or an image to be used in the Drawer part of the screen. I have predefined ones and you can also pick from a image that you place in the /KTweaker/ThemeManager/Backgrounds folder
15. New "UI Settings" item: Drawer Fore Color is used to set the color to be used as the fore color in the Drawer part of the screen.
16. New "UI Settings" item: Main Screen: Show Icons is used to specify if you want the icons to show in the main part of the screen.
17. New "UI Settings" item: Drawer: Show Icons is used to specify if you want the icons to show in the Drawer part of the screen.
18. New Menu item: "Reset Color Scheme" is used to reset everything back to stock if you mess up a setting for back/fore color items.
19. All icons are now customizable too!!!! So if you dont like my icons all you have to do is download http://ktoonsez.jonathanjsimon.com/sgs5/StockKTweakerIcons.zip, extract them onto your PC so you can see the names of the icons for the different items, replace the ones you want with yours, then place them in the KTweaker/ThemeManager/Icons/ folder on your phone, DONE !!!!
20. As a result of all these options in UI Settings this give you the aility to share your Theme if you want by zipping up the KTweaker/ThemeManager/Settings/, KTweaker/ThemeManager/Backgrounds/, KTweaker/ThemeManager/Icons/ folders
21. Thats all I can think of right now, ENJOY THE AWESOME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Change Log 02.16.2015
1. Remove all OA6 source to see if that clears up reboot for some people.
2. Re-added GPU 266 Mhz step.
3. KTweaker 8.1, general fixes for GPU items.
Change Log 02.11.2015
1. Update ramdisk for CM version
2. Update ramdisk for TW version for OA6 knox screwage
Change Log 02.09.2015
1. Update ramdisk for CM version
2. Merged in OA6 code for AOSP and TW versions
3. Many CM patches for call lag/hang issues
4. AOSP guys, this is the same as the test from earlier
Change Log 01.25.2015
1. Update ramdisk for CM-12 changes
2. Merged in albinoman's commits
Change Log 12.21.2014
1. Update ramdisk for CM-12 changes
2. msm8974_sec: Enable IDLETIMER
3. SELinux: Fix possible NULL pointer dereference in selinux_inode_permission()
4. Enable setting security contexts on rootfs inodes.
Change Log 12.04.2014
1. Update ramdisk for CM-12 changes for LP 5.0.1
Change Log 11.27.2014
1. AOSP 5.0 Version is born!!!!!!!!!!!!!
Change Log 11.06.2014
1. Ramdisk sync with CM
Change Log 10.30.2014
1. msm: vidc: Send resolution along with output buffer
Change Log 10.20.2014
1. Linux 3.4.104
2. Ramdisk tweaks for universal compatibility
Change Log 10.15.2014
1. Added key disabler that allows user to disable the Recents and Back buttons (you can change it by setting /sys/class/sec/sec_touchkey/keypad_enable to a 1 or 0 until I have time to add to KTweaker).
2. Updated ramdisk on TW so MTP works on 900F variant
3. Updated ramdisk to sync with CM for AOSP version
Change Log 10.07.2014
1. Merged in NI2 from 900V source drop
2. MAJOR update for 4.4.4 platform: 1,104 changed files with 23,268 additions and 8,923 deletions.
3. Firmware updates for almost all devices
4. GPU updates
5. media/video updates
6. exFat upgraded to 1.2.9
7. Many updates to sound driver and various codecs
8. Touch screen updates
9. Too many more to list, you guys get the point...
Change Log 09.21.2014
1. Sound Control: add line gain to cached and register lock
2. i2c_qup: Massive rewrite to improve pm_runtime handling
3. WLAN subsystem: Sysctl support for key TCP/IP parameters It has been observed that default values for some of key tcp/ip
parameters are affecting the tput/performance of the system.
4. Trying different flags in KTweaker widget to try and stop it from getting killed by the ROM
Change Log 09.11.2014
1. Sync with latest stuff for CM
2. Add in my NFC selective code from my TW version
3. Ramdisk sync
Change Log 09.03.2014
1. Sync with latest stuff for CM
2. Added F2FS support
3. Added vibration strength control.
Change Log 08.25.2014
1. Added in kernel commits from elelinux
2. Sync ramdisk
3. Tweaked defconfigs
Change Log 08.21.2014
1. Added faux sound to AOSP version
2. Added SmartAss gov to AOSP
Change Log 08.10.2013
1. The first 2 are the stuff from the OTA only release from 08.03
2. Merged in Faux sound
3. Linux 3.4.100
4. Linux 3.4.101
5. Linux 3.4.102
6. On AOSP, merged in all the latest stuff from "intervigilium" which will be the standard stock kernel for official CM.
7. Adjusted ramdisk so Sprint can run the newest kernel
Change Log 08.04.2013
1. Merged in Faux sound
2. Linux 3.4.100
Change Log 07.26.2013
1. cpufreq_limit: stop overriding user's max freq
2. Bump up max allowable voltage since we are OCing higher
3. vibe: Remove the moronic amount of dmesg spam from vibration motor
4. synaptic: Remove dmesg spam
5. cpu: Try some bandwidth tweaks on the upper steps
6. msm: kgsl: Fix nice level for higher priority GPU start thread
7. PM: devfreq: Use high priority workqueue
8. mm: slub: Default slub_max_order to 0
9. block: Reserve only one queue tag for sync I/O if only 3 tags are available
10. mmc: disable CRC check for speed
11. deadline: Allow 0ms deadline latency, increase the read speed
12. fs: Add sysfs module to allow enabling/disabling of fsync
13. KTweaker: Add toggle to enable/disable fsync under "Main Settings->Scheduler/SD Settings". This function will increase your write speeds by up to 3x, but reads do suffer by going down by about 20%!! Disabling this can cause corruption or loss of data if you have a random reboot so be careful!!!!!!
14. SELinux: Fix memory leak upon loading policy
15. Linux 3.4.1 thru 3.4.99 for the TW version from albinoman!!!!!!!
16. Merged in NG2 code from source drop which include the items below!!!!!!!!!!!!!!!!!!!!!!
17. GPU fixes optimizations
18. Display patches
19. Wifi driver update
20. Camera updates
21. Various sensor fixes/updates
22. GPU governor fixes/updates
23. Video codec updates
24. Encryption updates
25. ext4 updates
Change Log 07.18.2013
1. OC CPU to 3072, thanks to albinoman for finding the field that was limiting CPU to 2900!!!!!!!!!!!
2. 2899 CPU step is no replaced with 2918 to keep steps uniform
3. Tweaks to the bandwidth output for the new upper steps
4. Lots more demsg spam removed
5. Major over-haul to AOSP version along with merging in garwynn's latest code that is used for the stock CM kernel
6. Add touch screen patches to stop touch driver while screen is off. The ROM is not shutting down the touch screen or the 2 haptic buttons as many of you have probably noticed. I will work on getting the button shutdown when I get more time.
7. Some ramdisk tweaks
8. Update KTweaker to accomidate the new OC steps
9. AOSP kernel is now getting crazy stupid battery life at idle, I am currently at 21 hours 5 minutes on battery and still have 78% left with about 45 minutes screen time.
10. Fix ups for screen 2 wake functions for AOSP.
Change Log 07.14.2013
1. Add 657500 step to possible gpu boost values
2. More booster tweaks
3. DRIVERS: SLIMBUS initial overclock
4. readahead: make context readahead more conservative
5. net: loopback: set default mtu to 64K
6. cpufreq: Memory leak with sysfs when stats table are freed
7. Input: Send events one packet at a time
8. softirq: reduce latencies
9. sched: remove redundant update_runtime notifier
10. devfreq: Re-enable simple_ondemand. Also fix simple_ondemand crashing from GuneetAtwal
11. Merge in code from NF6 source drop
12. auto_hotplug: make enable_load configurable
13. ktoonservativeq: Add cpu_load_adder_at_max_gpu parameter so user can bump up CPU perceived load when GPU is at max Mhz
14. Screen wake and sleep functions, (I.E. doubletap2wake, sweep2wake)!!!!!!!!!!!!!!! In KTweaker the wake lock options are still disabled since it was not needed to make these function work. Same rules apply as the test kernels, if you get in a situation where the screen doesnt respond to touch, using the power button to turn it on and letting it timeout on its own then turning it on again has always restored touch.
15. Added ktoonsified v2 profile to KTweaker Shop with updated settings including the new ktoonservativeq parameter.
Change Log 06.27.2013
1. AOSP version is born
2. All caught up with all the features that are in TW.
Change Log 06.22.2014
1. OC CPU to 2899!!!!!!!!!!!
2. OC GPU to 657!!!!!!!!!!!!
3. GPU: Add "kt-simple" governor that is based on fauxs simple_gpu_algorithm function, made it configurable thru sysfs and made it a stand-alone module
4. Made GPU default Mhz speed 200 Mhz instead of Samsung standard 320 Mhz
5. ******* IF YOU THINK THAT THE UI DRAWS SLOWER WITH NEW 200 Mhz DEFAULT, CHANGE GPU Min Mhz TO 320 TO MAKE IT ACT LIKE STOCK!!!!!!!
6. ******* WITH CHANGE ITEMS 1 AND 2, THIS MAY REQUIRE YOU TO DELETE THE KTWEAKER FOLDER ON YOUR INTERNAL SD CARD AND START OVER IF YOU HAVE PROBLEMS!!!!!!!!!!!!!!
7. Add TCP congestion flag for TCP_CONG_BIC
8. Add TCP congestion flag for TCP_CONG_HSTCP
9. Add TCP congestion flag for TCP_CONG_HYBLA
10. Add TCP congestion flag for TCP_CONG_HTCP
11. Add TCP congestion flag for TCP_CONG_VEGAS
12. Add TCP congestion flag for TCP_CONG_RENO
13. Add TCP congestion flag for TCP_CONG_SCALABLE
14. Add TCP congestion flag for TCP_CONG_LP
15. Add TCP congestion flag for TCP_CONG_YEAH
16. Add TCP congestion flag for TCP_CONG_ILLINOIS
17. NE5 source merged in from Sprint's source drop (only about 30 lines of code have changed from TMobile's source)
18. Added Screen OFF Governor and Scheduler. This allows user to set a seperate governor and scheduler while screen is OFF.
19. Added GPS scheduler and governor selection. This allows user to set a seperate governor and scheduler when GPS is in use.
20. Add GPU Max mhz while screen is OFF
21. Updated ramdisk to support NE5 changes on Sprint variant.
22. Update ktoonsified v1 in the KT Shop.
Change Log 06.19.2014
1. Improve Max Mhz limit code for people that OC and use mpdecision or thermald.
2. More booster code to improve in coming call lag when using super_conservative for screen off. If you still get lag, turn super_conservative_screen_off to a 0 to get rid of it completely.
3. Made G900I compatible with main stream kernel!!!!!!!!!!!!!!!!!!!!!!!
4. Enable code for the Music/Media min/max Mhz and hotplugging settings in KTweaker
5. Couple of other minor miscellaneous patches.
6. Updated KTweaker with a couple of fixes.
7. Finally remembered to upload the OTA file so the checker will report a new kernel when available
Change Log 06.16.2014
1. Re-order cpug/gpu boost calls.
2. vfp: Some tweaks from around the net.
3. Add some build flags from some of the other variants.
4. Remove optimize for size flag.
5. KTweaker: Changed "Charging Settings" to "Charging Mhz Control" under the "Main Settings->CPU Settings" screen.
5. NEW! Add code for "Battery Mhz control" which lets you set a Max Mhz based on battery level. (found under "Main Settings->CPU Settings->Battery Mhz Control").
6. NEW! Add code for "Charging Settings" (found under "Main Settings->CPU Settings->Charging Mhz Control").
7. NEW! Trinity Colors goes live!!!!!!
8. sched: set mc_power_savings=2 this feature packs tasks together and try to bind them to cpu0, which in theory will let cpu1 idle longer, thus improving battery life.
9. smp: patches from mainline 3.5 to hopefully help with hotplug efficiency
10. kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
11. cpufreq: Break out early if freq equals to target_freq
12. NEW! KThermal: Add option to disable/enable kthermal so user has a choice between this and Samsung thermald (3 options listed below)
13. NEW! KThermal: Option to use KThermal (this disables thermald and is what stops Smart Stay from working.)
14. NEW! KThermal: Option to use KThermal+thermald in the background (this will use my thermal throttling engine and still let you use Smart Stay).
13. NEW! KThermal: Option to use thermald (Use stock Samsung thermald for thermal throttling)
14. CHROMIUM: mm: Fix calculation of dirtyable memory
15. mm: Adjust dirty writeback for IO boost
16. mm: optimize Kernel Samepage Merging(KSM)
17. Async I/O latency to a ssd greatly increased, 34% gain (Creds: kleikamp)
18. mm: Increase VM_MAX_READAHEAD to 512
19. NEW! sched: Make GENTLE_FAIR_SLEEPERS configurable thru sysfs
20. video: re-order booster hooks for more speed
21. FIX NFC for Sprint variant!!!!!!!!!!!!
22. Lots of new profiles uploaded to the KTweaker Shop by me and LuigiBull23!!!!!
23. Updated to latest June Linaro from @Christopher83
24. bfq: Upgrade to BFQ-v7r4
Change Log 06.12.2014
1. OC to 2841600!!!!!!!!!!!!!!!!!!!!!!!
2. Increase bandwidth table for new OC step
3. Add LTE support for Sprint users
4. Added conditional code for mpdecision to interact with for people that like the stock full bore all cores mode for smoothness
5. Fix interactive permissions so it can be tweaked
6. Updates from latest Samsung source
7. Adjustments to kthermal settings
8. Miscellaneous KTweaker fixes.
9. Adding missing flag to allow more than 1200 mA when screen is on and charging on A/C charger.
Change Log 06.09.2014
1. Initial Release
2. There are many configuration items in KTweaker, so here is what is working so far since this is just initial release:
3. ktoonservativeq governor
4. Voltage Control
5. CPU Min/Max Mhz control
6. GPU Min/Max Mhz control
7. Screen Off Max Mhz
8. Lots of governors and schedulers
9. 3 choices of hotplugging (stock mpdecision, KT Hot plug, and disabled)
10. FAST Charge
11. LED Settings are active
12. OTA
ktoonservativeq explained:
***** NOTES *****
Any item with the word cycle in it refers to how many sampling_rate's have occurred.
Examples:
A "boost_hold_cycles" of 28 and a sampling_rate of 35000 equates to 1 second of holding your Mhz at the boost level.
A block_cycles_offline_screen_on of 14 and a sampling_rate of 35000 equates to a half of a second block before it takes cores offline.
***** NOTES *****
block_cycles_offline_screen_off =1
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is OFF.
block_cycles_offline_screen_on = 11
How many sampling_rate cycles need to occur before a core is allowed to go OFFLINE while the screen is ON.
block_cycles_online_screen_off = 11
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is OFF.
block_cycles_online_screen_on = 3
How many sampling_rate cycles need to occur before a core is allowed to go ONLINE while the screen is ON.
block_cycles_raise_screen_off = 11
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is OFF.
block_cycles_raise_screen_on = 3
How many sampling_rate cycles need to occur before the current Mhz is allowed to be raised while the screen is ON.
boost_2nd_core_on_button_screen_off = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_2nd_core_on_button_screen_on = 1
When this item is a 1, it will turn on the 2nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_3rd_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 3nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_off = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is OFF. 0 leaves the core in its current state.
boost_4th_core_on_button_screen_on = 0
When this item is a 1, it will turn on the 4nd core when a button any hard button is pressed while the screen is ON. 0 leaves the core in its current state.
boost_hold_cycles = 22
How many sampling_rate cycles need to occur before going out of CPU/GPU boost mode
cpu_load_adder_at_max_gpu = 0
When set to higher than zero, this will add to the actual CPU load to create a perceived higher load when an app is using alot of GPU but not CPU.
cpu_load_adder_at_max_gpu_ignore_tb = 0
When set to 1, this will ignore cpu_load_adder_at_max_gpu during touch/button boost. When set to 0 cpu_load_adder_at_max_gpu will be used all the time.
debug_enabled = 0
When set to 1 this will output the current cpu load and whats online using dmesg so you can follow what is going on.
disable_hotplug = 0
When this item is a 1, it disables hotplugging so all cores stay on full time. 0 lets all cores turn on and off when needed.
disable_hotplug_bt = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while paired to a bluetooth device and doing bluetooth activities like playing music, transfering files.... 0 doesn't do anything extra to the cores when doing bluetooth functions.
disable_hotplug_chrg = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while charging the device. 0 doesn't do anything extra to the cores while charging.
disable_hotplug_media = 0
When this item is a 1, it disables hotplugging so all cores stay on full time while playing music or movies. 0 doesn't do anything extra to the cores while music or movies are playing.
down_threshold_screen_off = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is OFF.
down_threshold_screen_off_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is OFF.
down_threshold_screen_off_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is OFF.
down_threshold_screen_on = 52
A percentage of CPU utilization that needs to occur before the current Mhz begins to lower while screen is ON.
down_threshold_screen_on_hotplug_1 = 35
A percentage of CPU utilization that needs to occur before the 2nd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_2 = 45
A percentage of CPU utilization that needs to occur before the 3rd core is taken offline while screen is ON.
down_threshold_screen_on_hotplug_3 = 55
A percentage of CPU utilization that needs to occur before the 4th core is taken offline while screen is ON.
freq_step_lower_screen_off = 8
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is OFF.
freq_step_lower_screen_on = 2
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when lowering the current Mhz while the screen is ON.
freq_step_raise_screen_off = 1
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is OFF.
freq_step_raise_screen_on = 5
How many steps from the Mhz table (the entire Mhz table can bee seen in the CPU Voltage screen) it skips when raising the current Mhz while the screen is ON.
ignore_nice_load = 0
If this value is 1, the system will ignore "Nice" processes when deciding to scale up or down. Nice processes are used by the IO scheduler to designate a low-priority process. Ignore nice load basically tells a governor to disregard processes with higher nice values.
lockout_2nd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_2nd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_3rd_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_off = 0
This is a 3 way option. While the screen is OFF, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_4th_core_hotplug_screen_on = 0
This is a 3 way option. While the screen is ON, 0 = Hotplug Normal so the core will go on and off as needed, 1 = Lock this core always ON, 2 = Lock this core always OFF.
lockout_changes_when_boosting = 0
If this value is 1, all CPU changes to all cores will be ignored while executing a touch/button boost. If 0 all cores will be allowed to scale and hotplug.
no_extra_cores_screen_off = 1
When set to a 1, this option keeps all extra CPU cores offline while the screen is OFF. 0 lets it hotplug them on and off as needed
sampling_down_factor = 1
NOT USED!
sampling_rate = 35000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is ON.
sampling_rate_min = 10000
READ-ONLY value that specifies the lower value that "sampling_rate" and "sampling_rate_screen_off" will accept.
sampling_rate_screen_off = 40000
The amount of milliseconds that the governor will analyze the CPU usage and adjust for changes in load while the screen is OFF.
super_conservative_screen_off = 0
With the screen OFF: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items.
super_conservative_screen_on = 0
With the screen ON: When set to a 1, this option will explicitly obey your block cycles settings to be a super battery saver (Setting a 1 will slow down the UI a little bit). When set to a 0 it uses fuzzy logic on the "block cycle" items to create a smooooooth UI experience.
sync_extra_cores_screen_off = 0
With the screen OFF: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
sync_extra_cores_screen_on = 0
With the screen ON: When set to a 1, all online cores will be sync'd to the same speed as core 0. When set to a 0, all cores will operate at speeds independant of each other.
touch_boost_2nd_core = 1
When set to a 1, this option turns on the 2nd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_3rd_core = 0
When set to a 1, this option turns on the 3rd core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_4th_core = 0
When set to a 1, this option turns on the 4th core when the screen is touched. When set to a 0 it doesn't do anything extra to the cores.
touch_boost_cpu = 1804800
The Mhz that you want the online CPU's to jump to when the screen is touched.
touch_boost_cpu_all_cores = 0
When set to a 1, this option sets the current Mhz on all online cores to the selected touch_boost_cpu value.
touch_boost_gpu = 462400
This value specifies what Mhz the GPU should jump to when the screen is touched.
up_threshold_screen_off = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is OFF.
up_threshold_screen_off_hotplug_1 = 58
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_2 = 68
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is OFF.
up_threshold_screen_off_hotplug_3 = 78
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is OFF.
up_threshold_screen_on = 57
A percentage of CPU utilization that needs to occur before the current Mhz begins to raise while screen is ON.
up_threshold_screen_on_hotplug_1 = 52
A percentage of CPU utilization that needs to occur before the 2nd core is put online while screen is ON.
up_threshold_screen_on_hotplug_2 = 65
A percentage of CPU utilization that needs to occur before the 3rd core is put online while screen is ON.
up_threshold_screen_on_hotplug_3 = 68
A percentage of CPU utilization that needs to occur before the 4th core is put online while screen is ON.
Other Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Now it's time for the REAL party to begin!! Great to see you back boss!!!!
Good stuff! Glad to see ya!!!
Loved your work on the lg g2. Great to have you aboard the s5
Sent from my SM-G900T using XDA Free mobile app
pluginre said:
Loved your work on the lg g2. Great to have you aboard the s5
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Lol. You must be thinking of someone else I don't own an LG.
Sent from my SM-G900V using XDA Premium 4 mobile app
ktoonsez said:
Governors and schedulers explained:
http://forum.xda-developers.com/showthread.php?t=1687578
http://forum.xda-developers.com/showthread.php?t=1369817
http://tinzdroid.blogspot.com/2012/07/android-kernel-governors-modules-io.html
http://forum.xda-developers.com/showpost.php?p=21638852&postcount=56
Enable ZRAM: Flashable zip
http://db.tt/8vssawIO
Click to expand...
Click to collapse
What does the zram flashable zip do?
Sent from my SM-G900T using Tapatalk
raw2000j said:
What does the zram flashable zip do?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Oooops. Ill remove that, thats for old school TJ ROMs on the S4.
ktoonsez said:
Oooops. Ill remove that, thats for old school TJ ROMs on the S4.
Click to expand...
Click to collapse
Lol thank godd i didnt flash it lol
Sent from my SM-G900T using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------
Can we use faux123 or just ktweaker?
Sent from my SM-G900T using Tapatalk
raw2000j said:
Lol thank godd i didnt flash it lol
Sent from my SM-G900T using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:13 PM ----------
Can we use faux123 or just ktweaker?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Either or, doesnt matter. But once I get all my features merged in you will miss out on a lot of settings that are only in mine.
ktoonsez said:
Either or, doesnt matter. But once I get all my features merged in you will miss out on a lot of settings that are only in mine.
Click to expand...
Click to collapse
Cool one other thing wifi calling isnt working stuck on enabling
Sent from my SM-G900T using Tapatalk
Updated the Change Log post. I forgot that FAST Charge is also working. Also Fading LEDs is active.
Kernel is working great so far, only issue is wifi calling not working, stuck on enabling
woo hoo! Time to get Ktoonsified!
Was go-to for my S4
Thank you @ktoonsez.
Where is the ktweaker app?
Sent from my SM-G900F using Tapatalk
raw2000j said:
Cool one other thing wifi calling isnt working stuck on enabling
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Not really sure what that is, mush be a Tmobile thing. I would guess that it doesnt want to work when a custom kernel is loaded maybe.
Brava27 said:
Where is the ktweaker app?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
In your app drawer.
ktoonsez said:
Not really sure what that is, mush be a Tmobile thing. I would guess that it doesnt want to work when a custom kernel is loaded maybe.
Click to expand...
Click to collapse
I used blaze kernel wifi calling works must be something else
Sent from my SM-G900T using Tapatalk
raw2000j said:
I used blaze kernel wifi calling works must be something else
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
I made some ramdisk updates, redownload with same link as earlier (also has the same file name) and give it a try:
http://goo.gl/WGCntg
Code:
Disclaimer: I am not responsible for any damage caused by or done with this kernel.
.
About
Welcome! Plasma kernel is a unique and specially tailored custom kernel for the Snapdragon variant of the Note 4. It is the product of my strange brain and the monkeys that reside within it. Plasma kernel is designed to be very flexible, able to cater to those who wish to miser every bit of power, as well as those who demand performance, speed, and fluidity. It combines some common features from brilliant developers around the world, along with a great deal of my own work. One thing worth mentioning is that unlike most other kernels, this one does not offer many CPU governors, as much work was put into its flagship governor, ZZMoove. Currently Plasma kernel is only for TouchWiz ROMs, but an AOSP version is already in the works. Thank you for your interest!.
Screenshots
.
{
"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"
}
..........
.
..........
.
.
General Features
Compiled with Linaro 4.9, tuned and optimized for Cortex A15
Initially based on Starkissed's (twistedumbrella) repo
All settings fully configurable with andreilux's free Synapse app
Mpdecision and thermald disabled
Additional I/O schedulers (noop, deadline, row, cfq, bfq, sio, fifo, zen, vr, fiops)
CPU under/overclocked to 268 MHz - 3,072 MHz
CPU voltage control
GPU under/overclocked to 166 MHz - 800 MHz
Simple GPU Algorithm
Charging control
mDNIe Hijack color control for KitKat
KCAL color control for Lollipop
Kernel Samepage Merging (KSM)
CRC control
TCP control
SELinux always permissive
Frandom
Rngd control
Stereo call recording
Fauxsound
Plasma Features
Extended LED control
Touchkey multipress lockout
Touchkey remapping at the driver level
Touchkey Flicks
Touchkey Slides
Turbo Home button
Plasma Simple Scaling Lock instead of Hardlimit
Optional kernel-level universal wakelock
Optional always-on voice detection tweaks
Optional always-on touchscreen (can wake from deep sleep)
Touchscreen reduced scanrate while sleeping to save power
TouchWake (my implementation)
Slide2Wake (my implementation)
Pull2Wake (my implementation)
Arc2Wake (my implementation)
PlasmaUnlock 2.0
MultiButton
Stem Gestures
Tactile controls (vibrate when touched with finger or S-Pen)
S-Pen adjustable minimum pressure (aka sensitivity)
S-Pen adjustable fixed pressure
S-Pen WorryFree mode
Detailed Plasma Features
ZZMoove: Plasma Edition
Heavily modified version of ZZMoove
Supports various low-level boosts that hook into all other Plasma features
Music detection to help avoid skips
Native Input Booster
Applies a different up_threshold and various other parameters when input events are detected
Dynamically restarts governor timer to instantly apply the requested boost
Can detect, restart, and change frequency within 1ms (according to Wikipedia, 1ms = the time for a neuron in human brain to fire one impulse and return to rest, 100-400ms = time for the human eye to blink).
Many, many other features to be documented later
Extended LED control
Full sub-LED control (RGB) allows you to calibrate to a beautiful white, since not all LEDs are the same and may exhibit ugly tints with factory settings
Adjustable global high and low power sub-LED brightness
Optional pulse (fade) style blinking
Adjustable blink timing
Customizable driver-level TouchWiz LED colors
High/low missed notification sub-LEDs color, defaults to white
High/low charging sub-LEDs color, defaults to white with a red tint
High/low charged sub-LEDs color, defaults to white with a green tint
Touchkey multipress lockout
If you find yourself accidentally pressing a touchkey, this feature can require a double or triple press. Useful for handing someone your phone and not having them accidentally press the Back button.
Touchkey remapping at the driver level
Touchkey Flicks
Quickly pressing and flicking up from either touchkey can perform 2 unique actions
No residual pass-through - meaning only your action gets performed, the touchkey press and any touchscreen input are blocked at the driver level
Supported by Automatic Media Mode
Optional crossed mode to offer an additional 2 unique actions
Touchkey Slides
Quickly slide across the touchkeys from either left or right for 2 unique actions
No residual pass-through - meaning only your action gets performed, the touchkey presses are blocked at the driver level
Only works while the screen is off
Can wake from deep sleep, but may be unreliable for now
Turbo Home button
By default the home activity is executed after the home button has been pressed AND released, which can introduce as much as 100ms of wasted time. This feature will immediately send an up-event as soon as a down-event is detected. Unfortunately this breaks the ability to press and hold the home button - however there is one workaround - another optional mode that will send the up-event, then immediately send another down-event, and whenever you lift your finger, that will provide the mating up-event. This will allow long-pressing the home button, but the downside is that it always must send a complete press before starting to hold.
Plasma Simple Scaling Lock
A very simple replacement for hardlimit
Locks governor name and min/max for anything but Synapse
Kernel-level control of back (flash) LED
Optional kernel-level universal wakelock
Optional always-on voice detection tweaks
Force screen on when activated - If you use a 3rd-party lock screen, you may have noticed "ok, Google" is acknowledged, but doesn't wake anymore. This will send a power-on event to mimic the normal behavior.
Turn power off on second activation (from screen-off) - This was a silly idea I had, but it sorta works. I was frustrated because after saying "ok, Google" and asking my question, the screen would stay on. When this is enabled, it will turn the screen off when you say "ok, Google" a second time. Example: Ok Google...what time is it in NYC?...[The time is 12:21 AM]...ok, Google...[screen turns off]. This obviously only works for things that don't require more input, in which case touching the screen will restore normal behavior. It's sorta cool though because in a quiet car you can ask a question to your pocket and then tell it to turn itself off.
TouchWake (my implementation)
When the screen times out you can wake it with a tap or button press. Functionality is like the existing, well-known TouchWake.
DoubleTap2Wake (see PlasmaUnlock)
Slide2Wake
Pull2Wake
Pull2Wake will wake your device when swiping from the top of the screen, to the bottom. If done slowly, you can use your fingertip to
Arc2Wake
Now part of Stem Gestures
Turn your phone on while grasping it - left/right arc with your thumb from above Home to the side
Touchscreen
Support for waking from deep sleep
Adjustable width for valid Slide2Wake/Pull2Wake to filter out false positives
Reduced scanrate while sleeping to save power
Support for detecting finger hovering (very buggy at the moment)
PlasmaUnlock (previously called PatternUnlock)
A kernel-based screen/input locking mechanism. It is designed to be as flexible as possible, from serving as a simple way (eg. DoubleTap2Wake) to augment your existing power-on methods, to a robust means of protecting your phone from prying-eyes. It features up to a 20-step lock pattern, verified against not only x/y coordinates, but also time between taps, and tap peak-width. Because it resides within the kernel, low-level access provides some unique features not found elsewhere, such as power key blocking, screen blanking, and locking that takes effect so early, it even blocks the boot-animation.
Can be on at all times, doesn't need a wakelock
No complex coordinates to set, the pattern recording feature accessible via Synapse makes creating your pattern easy
Up to 20 taps can be recorded
Mode for taps only, or swipes only (like connect-the-dots), or both
Taps are validated against x/y coordinates, optionally milliseconds between taps, and optionally width
Relative coordinate mode allows for abstract patterns to be input anywhere on the screen, as long as the display is in a portrait orientation
All detection methods can be independently disabled, achieving a variety of results such as:
Unlock with a sequence of wide-thin-wide presses anywhere on the screen, by turning off x/y coordinate and time validation
Unlock with one wide press at a specific spot on the screen, by turning off time validation and using absolute x/y mode
Unlocking with a simple double or triple tap anywhere on the screen, by turning off width validation and using relative x/y mode
Unlocking with a rhythm, by turning off x/y coordinate and width validation and using time only
Adjustable pattern entry timeout (so you don't have to wait for the normal Android screen timeout delay, which is usually at least 30 seconds)
Lockout mode
Can take effect at the boot animation
Locks the touchscreen, S-Pen, and disables USB data connections until the correct pattern is entered
Can also black the screen out. Besides obvious privacy reasons, it also has the potential to confuse/delay thieves.
Optionally disables the power and/or home button (three very fast power presses will always turn on)
When screen is on, power long-pressing is prevented
Option to automatically disable/restore lockout
When connected to USB
When connected to a defined safe WiFi SSID
Adjustable delay before relocking after the screen goes off
Tamper evident mode will flash the front LED when any attempt has been made to turn the screen on
Optionally block all LED activity while locked (to help give the appearance of a dead phone)
Optionally disables itself while on a call, then immediately relocks when hung up
Optional automatic home button press (so you always unlock to your home screen)
Optional delayed blackout restoration (when used with the automatic home button feature, this is so no one will see what app is in the foreground the instant your screen turns on)
Can automatically unlock for Touchwake
Option to coexist with Slide2Wake, Arc2Wake, Pull2Wake
Stem Gestures
A series of versatile touch gestures that are specially designed to be unintrusive. By existing within the kernel, the Stem engine is capable of blocking and restoring input events, allowing the gestures to be triggered and used without interfering with normal device usage. This iteration is a hybrid of previous Plasma kernel features "Arc2Wake" and "HomeUp".
Supported by Automatic Media Mode
Works in deep sleep
20+ customizable payloads delivered via VirtualKey engine
Tap2Repeat repeats last action when finger is lifted then put back down in the same place
Equal for right or left handed people
Gestures (some can have different screen-off and screen-on payloads)
High Left
High Right
Low Left
Low Right
Side Up Left
Side Up Right
Arc Spike Left
Arc Spike Right
Center Spike High
Center Spike Low
Center Spike Bottom
MultiButton
When enabled, pressing different combinations of buttons will yield up to 6 different payloads. This iteration is a version of the previous Plasma kernel feature the "Volume MultiKey."
16 customizable payloads delivered via VirtualKey engine
Combinations (each can have different screen-off and screen-on payloads)
Volume Up + Volume Down
Volume Down + Volume Up
Volume Up + Power
Volume Down + Power
Volume Up + Home
Volume Down + Home
Long-Press Mode
Supported by Automatic Media Mode
Combinations (each can have different screen-off and screen-on payloads)
Long-press Volume Up
Long-press Volume Down
Automatic Media Mode
Detects when music is playing, and overrides certain payloads with music-oriented ones instead (volume, track control, play/pause)
Allows for altered parameters in ZZMoove to prevent skipping, include when recording audio
Userspace Booster
Provides small boosts for common things, like the keyboard opening, files being transferred, incoming calls, packages being installed or updated, etc.
Adjustable frequency and core count boosts for:
New app starting
Scrolling in a list
Activity changes
Progress bar being shown (KitKat only)
S-Pen
Adjustable minimum pressure to help prevent errant input, especially when doing things like crossing t's or dotting i's.
Adjustable fixed pressure to effectively disable actual pressure input, to make writing easier for some people.
WorryFree mode that always disables the touchscreen and touchkeys while the S-Pen is out.
GPU
Adjustable minimum frequency while interacting
Adjustable minimum frequency while plugged-in
Nightmode
A very fast home button double-press will toggle nightmode (red screen)
Synapse
Set DPI to 640/480/320
Built-in support to apply the surround sound hack at 3 volume levels: stock, medium and loud
Changelog
v.1.00
Initial release
Installation
Download
Flash via recovery
Reboot
Optional: Install Synapse
Download
Plasma kernel 1.00 for Sprint Note 4 - KitKat (4.4.4)
Plasma kernel 1.00 for Sprint Note 4 - Lollipop (5.0.1)
Until I update this post, please see my replies in this thread for the latest versions (1.21 for CM-13, 1.20 for CM-12.1, and 1.17 for TouchWiz)
Known Issues
Lollipop (5.1.x)
Surround Sound mod untested
Donations
Developing Plasma kernel takes an enormous amount of time and effort. Features like MultiButton, PlasmaUnlock, and the Stem Gestures represent hundreds upon hundreds of hours of planning, testing, development, more testing, squashing bugs, and even more testing. If the functionality they offered were apps, each would be worth a few dollars in the store. But alas, they are merely free. If you find my work useful, consider helping your starving developer out and make a donation - it would be GREATLY appreciated! However, if you do, please understand that donations are reciprocation for all this existing work, and are not guarantees of support. It's not because I'm mean, it's because like all the other developers here, I do this in my free time, and sadly that is a very finite resource
Donate!.
Credits
LoungeKatt (TwistedUmbrella), ZaneZam, AndreiLux, Faux123, Franciscofranco, Friedrich420, savoca, Yank555.lu, and many others.
A special thank you to bjrmd and everyone else who has helped test and support Plasma kernel on the Note 4
.
Source
Source code can be found on my github.
XDA:DevDB Information
Plasma kernel, Kernel for the Sprint Samsung Galaxy Note 4
Contributors
ffolkes
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2015-11-25
Great to see you back, looking forward to trying it out!
Awsome great to see that you got this working with lp cant wait...
Sent from my SM-N910P using Tapatalk
Oe1 or ob7 fingers crosses
pbedard said:
Oe1 or ob7 fingers crosses
Click to expand...
Click to collapse
Works on my oe1!
Perfect for me- ob7--thanks.
Looking forward to the AOSP one for sure
Working well here on LP. Only issue I'm having, and I had it on the KK version as well and forgot to mention, is with smart stay. Proximity sensor isn't keeping the screen on like it should when looking at screen. Working on stock kernel, and another kernel I tried. Anyone else? Thanks for the update! I sure missed all the features of this kernel.
Sent from my SM-N910P using Tapatalk
Whats the securty thing always going off
See here
egodriver07 said:
Working well here on LP. Only issue I'm having, and I had it on the KK version as well and forgot to mention, is with smart stay. Proximity sensor isn't keeping the screen on like it should when looking at screen. Working on stock kernel, and another kernel I tried. Anyone else? Thanks for the update! I sure missed all the features of this kernel.
Click to expand...
Click to collapse
I've never used smart stay, but I will give it a try and see what's going on.
pbedard said:
See here
Click to expand...
Click to collapse
That is really weird. What ROM are you using? I've been using HybridX for KK and Notarized for LP and I have never seen a dialog like that before. When does it happen? When using Synapse?
Synapse never installed and im using the 0e1 stock rom
I am loving this kernel great job.
The settings inside synapse for this kernel is amazing. I had an antutu score around 40 but I'm sure that can be fixed once I get the hang of setting this up
OK, I love this kernal. The amount of options and tweaks are unbelievable. I loved this kernal on my note II and was disappointed when it fizzled out at 4.1.2
I have an issue with this build though. For some reason zzmove has never given me good results. It is good for battery life, but performance is bad. I could not find a good balance for this govenor on my Note II (AT&T) and my Note 4 doesn't like it either. I have tried many different variations of zzmove to no avail. It's a deal breaker on my phone.
Would you be absolutely opposed to using other govenors? Intelliactive and Alucard have worked the best for my phone (trltespr). Blueactive and Interactive Pro have also been popular on this device. Your choice of schedulers is great
Your work is much appriciated :thumbup:
Zzmove is giving me music skips while the screen is off. Anyone know what setup u should use to stop it
thatdudeaaron said:
Zzmove is giving me music skips while the screen is off. Anyone know what setup u should use to stop it
Click to expand...
Click to collapse
zmove scaling page---freq limit while screen off-- set to 2649
max freq while screen off and music plays--2649
min freq while screen off and music on--576
zmove hotplug page--max core while screen off--change to 2
my problem is that the music detection algorithm is not very accurate, so the "freq limit while screen off" is the setting that saves me.
TY
Kernel breaks proximity sensor for me. Running stick oe1 ROM. Any fix to this?
Oh well music still skips on zmoove governor
V12 turbo charged - Good Job ffolkes
Buckle Up Folks long post coming through.
For those that just want to get strait to the point Skip down to the Bold “Tweaking the governor” section.
This kernel has changed my opinion on what is possible with the note 4 from a fluidity stand point. I always thought that androids weakest points was scrolling performance, general fluidity, and speed, but this kernel along with the Noterized Rom with the Next Launcher 3d shell on top, makes my brothers iphone 6 plus seem sluggish.
I’ve been playing around with the lollipop version of this kernel before ffolkes officially released it (since version 18 and 18a). From my experiences with it, I have discovered the same thing that some of you have probably noticed: if left un-configured, it is painfully sluggish in some aspects but battery life is fantastic.
Unlike a lot of other kernels out there, I don’t believe that this kernel was meant to be left alone (ffolkes, please fee free to correct me if I am wrong on anything written in this post. This is your baby afterall, I am not the artist here). Honestly, there are so many options to tinker with, that it would be shame to simply leave it alone. This baby is a v12, turbo charged monster with a hidden Nitrous boost button just waiting to be pushed.
Some have asked for settings, So I am going to do my best share with you my experiences with tweaking this kernel thus far. Hopefully it will help someone.
A quick disclaimer with reference to my usage habits: I like to Glide. For me, my phone has to feel like the content on the screen is like a puck on an air hockey table or a hovercraft on water. I want no hard stops, as little friction as possible. I am obsessed with flicking things around on my screen and watching it glide to a slow, almost un-inhibited stop. The longer the glide the happier I am. My finger does not stay on the screen for more than half a second but If I do a full flick the content does not stop until 3 to 4 seconds later and it always a slow, gradual descent with no stutter or lag.
To achieve the above effect , 2 things need to happen. The application you are using has to be properly coded and configured, and the kernels governor needs to be tweaked.
Tweaking the applications:
Through my testing, I have found what I feel is a direct relationship between the applications dpi setting and scrolling/panning smoothness. How long it takes items to come to a stop after being panned or scrolled with a flick, seems to be directly related to the dpi. The lower the dpi, the longer the glide. I have narrowed my preference to three specific dpi settings:
345 – My personal favorite – you could set the entire rom dpi to this and get tablet mode for most apps and the text is still legible(to me), I could use this without exposed though you will have to user a different dialer and camera app due scaling issues.
380 – Text is much more legible (most will prefer this mode) and apps also tend to behave with much less stutter.
430 – Good Performance, Text is super legible but not to big but the air hockey glide effect only last about half a second.
Tweaking the governor:
Lets start with the touch-bootster
Sampling rate = 60000
Input Boost Punch Minimum Cores = 4
Input Boost Punch Frequency = 2649
Input boost Punch Cycles = 50
Input boost Up Threshold = 20%
Punch on Every Initial touch = enabled
Punch on All Touch Movements = enabled,
Punch on all S-Pen Movement = enabled,
Level 1 Batter Threshold & Master Switch = Disabled
For most, the above settings alone will remove almost all lag if you are using Noterized Rom or a Variant that uses it as a base ie Hybrid X (heck of a job also tx_dbs_tx). Just to let you know, with these settings, I can get 5 hours of web browsing along with and additional 40 to 60 minutes of web video streaming. If your video content is from the youtube or Netflix app, I can almost double the video streaming time when using Netflix, and almost triple it for google Youtube. I've gotten close to 8 hours of total onscreen time, even when pushing the touch-booster really hard with the above changes only.
To further squash out any lag related to general application load, change the following:
Down threshold While Screen On = 11%
Up Threshold while Screen On = 12%
Smooth Up threshold while screen on = 15%
Fast Scaling Up While Screen On = 4 Steps
Scale Blocking Cycles = Disabled
Scale Up Blocking = Disabled
By now if you still have lag then issue is either application specific, ROM specific, incorrect user settings or failed hardware. But if you still need more power and you don’t want an application to even think about stuttering, then go over to the zzmove hotplug page and change the following
*****Delays*****
Block Up Logic Cycles = Disabled
Stagger Up = unchecked
Block Down cycles = 5 cycles
Stagger Down = checked
*****CPU Core 2****
Up Block Multiplier = 0x(No delay)
Down Block Multiplier = 10x
Up Threshold = 10%
Down Threshold = 9%
Up Frequency Threshold = 422 MHz
Down Frequency Threshold = 345 MHz
*****CPU Core 3****
Up Block Multiplier = 0x(No delay)
Down Block Multiplier = 5x
Up Threshold = 15%
Down Threshold = 14%
Up Frequency Threshold = 652 MHz
Down Frequency Threshold = 576 MHz
*****CPU Core 4****
Up Block Multiplier = 0x(No delay)
Down Block Multiplier = 10x
Up Threshold = 20%
Down Threshold = 19%
Up Frequency Threshold = 806 MHz
Down Frequency Threshold = 729 MHz
God I hope by this point your still not lagging but if you are there the usual kernel lever tweaks that
1. include things like are things like:
2. enabling Dynamic Fsync,
3. disabling Error Correction,
4. Upping the GPU touch boost to 500, (very important for Noterized Rom or other variants that are fully Hardware accelerated(gpu rending forced + hardware acceleration) This is one reason I believe this rom can sometimes eat into batter life pretty quickly.
5. Increasing GPU Laziness to 8
6. Reducting the GPU ramp Up Threshold down to 300
7. Zram, Low Memory Killer, Frandom and all the other settings have pretty good guides out there to tweak accordingly.
Battery Life:
Tweaking battery life has to be done methodically. It should be based on each individually usage habits and should take into account the apps running in the background and available memory (low memory killer and Swapness should help out with this also)
Choose and Good Test Application - To start with I would find and use a good Application validate if there is lag and or stutter. This app should not be one the pushes the note4 to its max limit all the time, unless it is the primary app you use on the phone. Testing with such in app will have you tweaking your system to maximum performance all the time. At that point you could simply leave the settings that I gave you earlier as is and skip the rest this these sections. Those setting will get you maximum performance out of your phone when you need to running your hard-line application and still provide 4 to 5 hours of no screen time when you don't. when tweaked ffolkes version of zzmove can get you on-demand performance governor performance without the wasted power. You could just also switch to the standard performance or on-demand governor.
For the rest of us, when it comes to scrolling I would highly Recommend UC Browser(Can’t Sing it’s praises enough). Don’t just download the latest version. Not all versions are equall when it comes to scrolling performance and lag. I will include an APK in the post or link to their historical archives. There are three that I would recommend:
build dated 01/27/2015 - It is a web page eater. It is quick light and is stutter free if you are using a lollipop rom Based on Noterized. If on Kit-Kat it is not as smooth as the version listed below but still better than chrome, firefox or the Samsung browser, the new versions of dolphin might come close but still a distant second in scrolling performance.
build dated 06/04/2015 - about 5 to 10% slower on than the one above for java script performance but man is scrolling smooth on Noterized. If you guys remember the Old webkit browser on android 4.2.2, This one out does it and makes my brother want know how to get his iphone 6 to work like my Note 4 when it comes to website loading and smoothness. This version also has UC excellent Night mode with transparent background that makes things look even smoother when using dark themed wallpaper and has the added bonus of extending the notes battery life significantly. Keep in mind to achieve this performance, for me takes 345 dpi. 380 and 420 aren't bad either.
build dated 05/15/2015 - honorable mention goes to this build for its superb memory management. No crashes, hangs or forecloses with a variety of content for 2 weeks straight. remains snappy even though phone was never rebooted and memory never cleared. Was my go to until I started us plasma on lollipop and saw that I could have the best of both worlds and went back to the 01/27/build. the bruit force of the input booster will make anything that has a remote chance of being smooth, glide like butter.
The uc browser archives:
http://wap.ucweb.com/verlist/english_354/ucbrowser/145?uc_param_str=vepffrbiupla&from=U3-help&plang=
If using a web browser to determine lag and smoothness Desktop Mode mandatory for UC and the following Web Pages:
Yahoo.com – Stutter city because of the continuous loading of content ( you have to scroll for a good while, but once enough content has loaded you will see the limits of your browsers memory handling and allocation. This could also be a good benchmark for your io scheduler , and tcp congestion algorithm of choice.
Youtube.com – Same as above but content is heavier. Good test due to the fact that it will show you when you are not properly optimized, but reward you greatly if you are. You are either in the gutter or you’ve hit a strike.
Espn.com-Highly optimized well written code and template, should be smooth even though the content containers may load slowly. Again good test for tcp congestion. This site will also expose the performance delta between the 01/27 build of UC and the other builds mentioned.
Touch-Booster Battery Life - You need to tweak the touch booster settings to match how you interact with you screen. Some people flick there content always letting it glide and some people keep their fingers on the screen until they get to where they want to go. This alone will change how you optimize the setting for the touch booster to maximize battery life.
Using me for example, the settings listed in the touch-booster tweaks was custom tailored to me. Most of the time, I use my phone for web browsing, reading pdf files, and emails. As stated earlier, to interact with content on my screen, I flick on my screen and expect content to glide for as long as possible. On average, in UC browser (my browser of choice and the smoothest out there for scrolling performance) , even a light flick will last 1 to 2 seconds and if I flick content quickly enough, the content could glide along the screen for as long as 3 full seconds. Therefore I need my Input Punch boost to last 3 seconds just in case.
If My sampling rate is 60ms for the above stated situation, I need 50 cycles(Input boost Punch Cycles ) of the 60ms sampling rate to give me a total cycle time of 3,000ms, which of course we all know equals my 3 seconds. If I am someone who keeps my fingers the screen and rarely flicks then that’s a lot of wasted power for absolutely no reason at all.
To tweak touch-booster for , start with the settings I gave in the first section and reduce “Input Boost Punch Frequency ” until you begin to notice your first hint of lag on the above pages. One you experience lag increase the frequency by 2 steps from that point. Now reduce the number of active cores until you get lag again. Once you get lag, increase the core count by 1. Finally, decrease the power usage caused by the sampling rate by increasing the time between intervals by 5ms at a time. So from 60 to 65, then to 70. Once things start to lag, decrease the interval by 10ms
GPU Battery Life - In addition to the cpu touch-booster tweaks, flokes was even nice enough to include input based boosters for the gpu(freaking awesome by the way dude). He gave us the ability to under-clock the gpu to 166 when not in use (fingers off the screen) but giving us power for 1.5 seconds(hope this duration is tweakable in the future) of up to 800mhz. This is important for a Rom Like Notarized where gpu is doing most of the work all of time. The gpu is in use even for traditionally lite loads such as 2d work. I would recommend lowering the min frequency all the way down to 166 and capping the gpu somewhere between 266 to 300 if you are like and don't game much. if you get lag or stutter/jitter then increase the frequency one step at a time until the lag disappears from your application. You will get so much more mileage from steaming video like Netflix. The Adreno 420 is powerful enough to handle light loads without flexing its muscle, but will flex it anyways if not kept in check.
General Applications Performance and Battery Life - First you need to tweak the main up and down thresh hold for cpu load:
1. Increase the “Up Threshold while Screen On” by 10 until you notice your hint of lag in your application. 2. Once you noticed the lag or stutter decrease the “Up Threshold while Screen On” by units of 2% points until lag goes away.
3. Once you found you optimal number, increase the “Down Threshold while Screen On” number to a number 10 less than the “Up Threshold while Screen On”.
You can follow the same procedure listed above for the hot plug algorithm, Tweaking each individual cores up and down thresholds starting with core number 4. Once optimal threshold is set for core 4, test core 3 in the same manner then core 2. Once thresholds have been optimized, starting with the 4th increase the “Up Frequency Threshold” until you notice lag in your application. One you hit the lag frequency decrease your frequency step by 2 levels and then move on to the next core doing the same thing.
After achieving the optimal hot-plug and frequency thresholds for each core. You can then begin to explore power saving by adjusting the up and Down delays. Starting with Core 4 and working your way down, decrease “Down Block Multiplier ” in increments of 1 until lag is achieved. If no lag is achieved after getting to zero. Then your usage pattern is not effected by this and you can simply disable this feature for that core.
Normally I would not recommend introducing lag but from a power saving standpoint it also might be to your advantage to increase the “Up Block Multiplier ”. Starting with core 4 increase the number slowly until you begin to notice lag with you usage pattern. Do this for each core until you fine the optimal multiplier.
Other Power Tweaks – In my opinion remaining power tweaks can be done without effecting usage by much:
1. Sampling Rate Idle = 500ms – Decrease the number if you notice lag when try to interact with an application after having you finger off the screen for a while. I am not sure but I believe the input booster engine relies on this setting since it does not have a setting listed for poling in the governor(ffolkes correct me if I am wrong). If you notice that applications work great when you touch the screen and poorly when you don’t, you need to decrease the “Sampling Rate Idle Threshold(Frequency)” and/or “Sampling Rate Idle Threshold(load)” until its gone.
2. Sampling Rate Multiplier While Screen Off = 8x – The higher this number, the bigger the sampling interval when the screen is off. I love this feature. It’s given be great talk and music playback time when the screen is off. I don’t do it very much, but if I remember correctly I was getting less then 1 percent battery loss for an hours call with my sister(yeah she’s a talker).
Lastly, In my opinion, a good experience on the phone comes down to three pillars. The Rom it’s running on, the kernel, the Launcher, and then the Web browser. You already know about The Rom (Notarized), The Kernel(Plasma), and the browser Being UC browser. What I have not told you about is the Launcher. If you guys have not Tried Next Launcher 3D. Take it for a spin. If is not only full accelerated but it is full optimized for battery life. Even before I was using Plasma and the touch-booster. It was the only part of my note 4 I had never seen lag. The screen shot look Gimicky but when tweaked to your taste it can do a flat design like the other launchers with all the widgets and icon packs. The only difference is it does not slow down and does not eat your battery. Also no FC's. I am a stickler for smooth and this Launcher with Plasma and Notarized just plane burns.
Told you this was going to belong, but I am done. I would like to finish by Thanking Ffolkes for his hard work. This is not copy and past code folks. I have not even gotten talk about the rest of the settings in this thing like the gestures, multi-button and so on. This guy toils to bring a lot of these things to us. He's not just waiting for linux versions to do his releases. Considering the open source nature of android, I can’t state for sure that this is all his engineering but it sure looks like it. You tell me if you’ve seen this type of attention to detail and code command, in any other kernel. It’s not just him though I think SaintZ93 deserves more than a round of applause for fundamentally changing the base for all or our roms for the better. If Norterized is now base for our custom roms and I will accept no Less than Plasma for the kernel(People will, emulate, wait and see), Then the future looks Golden. Donate people. Think of it as taking the guy out to McDonald’s or for a pint of Beer and some fry’s. We all know he deserves at least that. Hope I am not breaking some type XDA rule with the length of this post.
Hi everyone,
when trying to replace a damaged digitizer for this tablet, I only received a similar one that is wired inverse to the original, so that recognition of touch gestures is now flipped vertically (in landscape mode).
Got a refund from the Chinese seller, meanwhile ordered from another seller - got the same screen, a compatible replacement seems to no longer exist for this tablet, now it can only be used with an external mouse.
The device is Archos 97 Neon, running Android 4.2.2 on some Rockchip 31.., I also have root access by now.
After reading through source.android.com/devices/input/touch-devices.html#touch-device-configuration
there was only two .idc files I could find, but they do not (yet?) seem to contain much configuration for the touch screen:
qwerty.idc
Code:
#
# Emulator keyboard configuration file #1.
#
touch.deviceType = touchScreen
touch.orientationAware = 1
keyboard.layout = qwerty
keyboard.characterMap = qwerty
keyboard.orientationAware = 1
keyboard.builtIn = 1
cursor.mode = navigation
cursor.orientationAware = 1
and qwerty2.idc
Code:
#
# Emulator keyboard configuration file #2.
#
touch.deviceType = touchScreen
touch.orientationAware = 1
keyboard.layout = qwerty
keyboard.characterMap = qwerty2
keyboard.orientationAware = 1
keyboard.builtIn = 1
cursor.mode = navigation
cursor.orientationAware = 1
The calculations shown for reference in the Android docs seemed quite straightforward, so I guessed I could just add a few magic lines to those .idc files to have the digitizer input fixed?
But it seems to be more complicated, will I really need the touch driver and / or kernel source code to build a new driver / kernel when all I want to do is mapping the touchpoints to a different location on the screen?
Is there maybe some universal app for rooted devices that kind of sits in between the manufacturers driver and the Android input system? Only found commercial fake "calibration" tools on the Play Store that do not really do anything.
I will be pleased about any suggestions
(the bad thing is, I actually offered to repair the crackled but otherwise still working screen for someone... now that the original screen fell into even more pieces when ripping it out, and there is no more chance to get an exact replacement, I basically destroyed their tablet... feels quite bad )
have a Firefly AIO-3399j board that I am attempting to run a BOE NV140XTM-N52 display directly from it's eDP interface. I'm a novice when it comes to compiling kernels so I'm having some issues getting this to work properly. I have verified that the physical pinout between the board and the display is correct, and I do get an image on the screen some.
First information about the display from the data sheet. The timing that I see from the display says a 269.5 MHz Clock and the EDID table gives the following information. The clock max is 275.6MHz and minimum is 220.5MHz. Hor Active = 3840, Hor Blanking =160, Ver Active = 1100, Ver Blanking = 48, Hor Sync offset = 48, H sync pulse width = 32, v sync offset = 3, and v sync pulse width = 5. That's where I would assume the following timing would be correct.
hactive = 3840
vactive = 1080
hsync-len = 32
hback-porch = 80
hfront-porch = 48
vsync-len = 5
vback-porch = 40
vfront-porch = 3
Now if I do a cvt modeline calculation I get Modeline "3840x1100_60.00" 353.18 3840 4088 4504 5168 1100 1101 1104 1139 -HSync +Vsync which is completely different on the porches and sync lengths.
Now, onto the board. According to the SDK, the display timing isn't set in the device tree files, it's set in the drivers at /kernel/drivers/gpu/drm/panel/panel-simple.c which I've tried the timing above that I assumed is correct from the datasheet and I've tried the timing from the modeline calculation. I've also put the display timing in the device tree file to see if that would work.
So far, I have gotten to where I get an image on the display and it will flicker from time to time sitting at the home screen of android, but then if I open the app menu, it will flicker even more until I exit it. I've tried adjusting the clock up and down with no resolution, and eventually I will either get a brief image on the screen and then it fades out, or the display will start looking like the porches are completely wrong. The display appears to have EDID information, but doesn't appear to get passed onto the kernel properly.
I've spent several hours recompiling and flashing firmwares to where I'm at a point I have no clue what to do anymore. Can someone help?