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
I really like having LTE on my nexus 7. It eats power though - over 2% per hour. It does this even when connected to wifi with mobile data off. It seems that disabling mobile data does not turn off the cell radio...
When in 2G only mode only about 0.5% per hour is consumed. You can switch this manually via settings but eventually you will forget and pay the price. With a bit of hacking you can make things better.
Here is a script manager script that can be called with llama or tasker to toggle the 2G only state.
#!/system/bin/sh
/system/bin/am start -W -a android.intent.action.MAIN -n com.android.phone/.MobileNetworkSettings
/system/bin/input tap 990 1070
/system/bin/input keyevent 4
/system/bin/sleep 2
exit 0
This is built to be run by script manager. To use it effectively you also need root (supersu) and the 'pro' version of script manager. You also need to install SMWidgets which lets llama/tasker easily start scripts. To use this on other devices you will have to figure out the coordinates for input as they will be different.
First add the script to script manager and set the 'su' flag.
Then in llama add events that do the following:
event
Toggle 2G
delay for 30 seconds and if still true
condition
screen rotated 0
screen off
llama variable 4g has a value of 1
connects to any WiFi network
actions
disable rotation
disable screen lock immediately
turn on screen at low brightness
run app shortcut called 'toggle 2g'
. select SMShortcuts, select 'add one script shortcut' and set the background flag when prompted
toggle llama variable 4g betwen 0 and 1
queue an event named '2g'
. wait 5 seconds
. condition
. llama variable 4g has a value of 0
. action
. enable screen lock (force)
. enable rotation
event
Toggle 4G
delay for 30 seconds and if still true
condition
screen rotated 0
screen off
llama variable 4g has a value of 0
dissconnects from any WiFi network
actions
disable rotation
disable screen lock immediately
turn on screen at low brightness
run app shortcut called 'toggle 2g'
. select SMShortcuts, select 'add one script shortcut' and set the background flag when prompted
toggle llama variable 4g betwen 0 and 1
queue an event named '2g'
. wait 5 seconds
. condition
. llama variable 4g has a value of 1
. action
. enable screen lock (force)
. enable rotation
make a test event to set the llama variable '4g' to 1
What the events do the following: verify that your screen is not in landscape mode, disable rotation, turn off lock screen, turn on the screen, run the script, (re)enable the lock screen & lock, (re)enable rotation.
And when wifi disconnects 4g quickly gets enabled, when you reconnect '2g only' is selected.
Have fun.
switching to Airplane mode then activating wifi will switch off NEXUS 's 7 LTE mobile data completely
xslavic said:
switching to Airplane mode then activating wifi will switch off NEXUS 's 7 LTE mobile data completely
Click to expand...
Click to collapse
Yes I realize that. I've had problems with wifi after using airplane mode.
Try this: switch to airplane mode, turn on wifi (it works), turn off airplane mode. Does your wifi work?
Some combo of turning on airplane mode, switching wifi on and off, and ending airplane mode with wifi off usually restores wifi.
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
Hi,
I tried the Advanced Settings app on my rooted Huawei Watch without success.
I managed to completely disable vibrations on my watch by doing "chmod 000 /sys/class/timed_output/vibrator/enable" in shell. But I would rather change the vibration intesity to be very low, and the vibration time to be very short.
However I cannot find where to change the values for this.
Looking at the vibrator folder in the watch (/sys/class/timed_output/vibrator), it contains the following folders:
enable,
power,
subsystem,
uevent
And enable is a file which I talked about, that would disable the vibration completely.
If I do "cat" on the files inside the folder "power" I get these results:
cat: autosuspend_delay_ms: I/O error
cat control auto
cat runtime_active_time 0
cat runtime_status unsupported
cat runtime_suspended_time 0
As the active time is already set to zero I don't know how to set the vibration length or the strength.
Anyone got an idea?
So apparently the 1 III suffers from the same issues as its Sony Predecessors... The Flashlight is very bright when you use it as camera flash, but when you turn on the flashlight, its artifically throttled to idk, prevent overheating?
So for the older Xperias there were ways to modify flashlight configs and librarys. However, I havent found a way to edit the current parameter for the flashlight on the 1 III. For the 5 II the GodlyTorch App seemed to work, according to a report in https://forum.xda-developers.com/t/...ness-fix-torch-light-not-photo-flash.4203293/, but that doesnt want to work on my 1 III (I have Root)
Now the question: Can someone find the parameters to increase Flashlight LED Current via Magisk Module, XPosed/LSPosed Module or manual edit? I'd be even willing to donate to a kind developer who builds a usable flashlight mod for the 1 III.
Thanks in advance.
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
MK73DS said:
When flashlight is on and your device is rooted, you can change the value of
Code:
/sys/class/leds/led:torch_0/brightness
/sys/class/leds/led:torch_3/brightness
(There are two flash LEDs)
The max value you can set is given by the max_brightness file in the same directory.
I didn't find a way (yet) to apply this by default, you have to have the flashlight running in order to change its brightness that way.
However, I do warn you that I am not responsible in any way if using your LED at full power causes damage to your device.
Click to expand...
Click to collapse
Thanks for this info, working fine for me!
I played a bit around with this and tested the brightness values with 150; working fine in terms of short term heat development.
Edit 2: After a few days I start to notice a very slight discoloration of the diffusor with a value of 150. Its not affecting anything and barely visible, but I'd recommend to go lower than 150, because I suspect the LED may get too warm for the diffusor. I changed the guide to use 30 for now (which equals double the brightness compared to stock), please test your values for yourself, its probably better to not exaggerate it.
Make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible for side effects resulting from the mod.
With Terminal Shortcut Pro and assigned Root Priviliges I made myself a Home Screen Icon that will boost the values for me in the current "Torch session" once the LED is turned on before. Other terminal emulator apps will work too.
In the Shortcut I set Run with Root and used the following command
Code:
echo 30 >> /sys/class/leds/led:torch_0/brightness && echo 30 >> /sys/class/leds/led:torch_3/brightness
Basically just a command that writes the 30 brightness value to the 2 files.
If someone can find a terminal command that turns on the flash in the first place, we could combine the commands to potentially make a simple but working replacement quick settings for the torch.
Edit: Thanks to the XDA Community and a Tool I was able to recreate the Torch experience with a Quick setting
You need https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings
You have to buy the premium in app purchase for 1,29€ to unlock Root Command Running. Then you configure your quick setting (choose the Advanced -> Root Command under Preset) and paste the following script (credits to https://forum.xda-developers.com/t/increasing-torch-power-with-root.3637773/post-73098701, modified by me for 1 III)
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 30 > /sys/class/leds/led:torch_0/brightness
echo 30 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Once again, make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible side effects resulting from the mod.
Then you get rename the toggle, give it a nice Torch Icon and set the color to grey. It will function like the normal quick setting: Tap once, it turns on, Tap again, turns off. Even works locked.
Good luck and best regards.
If you want to use the Google Assistant Button as a torch toggle and also have Quick Settings Toggle (sadly its always toggled on) i found an app that can do both.
You need:
LSposed/Xposed
Root Shell access (adb shell)
Xposed Edge pro
Busybox for Android NDK (Magisk Module)
XperiaGAButtonRemap (Magisk Module)
Open a cmd or powershell
execute adb shell
execute su
accept root permissions on your phone
execute vi /bin/torch
press the key i
paste the script:
einhuman197 said:
Code:
#!/system/bin/sh
toggle=$(cat /sys/class/leds/led:switch_0/brightness)
if [ "$toggle" = "0" ];then
echo 150 > /sys/class/leds/led:torch_0/brightness
echo 150 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi
Click to expand...
Click to collapse
press ESC
type :wq and press ENTER
execute chmod +x /bin/torch
Now you can execute /bin/torch as root and it will toggle the torch with higher brightness values.
In Xposed Edge enable "Keys" toggle and open it. Tap on "+ Add" at the bottom, press the Google Assistant Button, it should be recognized as "KEYCODE_PROG_BLUE", then set the action of either click/double click/long press (whatever you prefer as the torch toggle) to execute a Shell command, enter /bin/torch in the input field and enable the "Root access" toggle.
If you want, you can also set other custom things to the Google Assistant button for the other 2 states.
For the quicksettings menu tap on "Quick settings tiles" in the main menu of Xposed Edge and enable the first tile and open the settings for that tile. Set the action, again, to a shell command, input /bin/torch and enable Root Access. You can set the label to "Torch" and choose the Torch icon found in "Built-in icons". As i already said, the toggle will always be turned on for some reason. It just executes a shell command after all.
Good luck
Amazing, thank you everyone.
However, please let me insist that this may damage your phone if you put values too high... trust me. I accidentally put a brightness of 350 instead of 150 while trying the script in a terminal, and a few seconds were enough for the plastic underneath the glass to melt... Thankfully, it is still transparent so I can still use my flashlight, but no doubt it could have done a lot more damage if I let it run for longer. So please, use this with a lot of care (and double check what you write).
That's why in lots of countries, rooting voids your (hardware) warranty, you can do physical damage to your device so again, please be careful. Thankfully, this plastic bit and even the LED underneath are easily replaceable (the plastic bit is separated from the rear glass and the LED is on a separate ribbon cable). However, there don't seem to be a lot of OEM replacement parts for this phone yet.
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
jaseman said:
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
Click to expand...
Click to collapse
Sony could definitely improve it. But it seems like they had a history for compareably dim Flashlights.
I edited my explanation post to adapt lower brightness, because 150 as value starts to slightly discolor my diffusor, so I suspect we should run it lower.
MK73DS said:
太棒了，谢谢大家。
但是，请让我坚持，如果您将值设置为高，这可能会损坏您的。......我相信在终端中尝试手机时，我不小心将恢复设置为 350 而不是 150 ，几秒钟就可以让玻璃下面的恢复正常……幸好还是可以的，所以我可以使用我的手电筒，但有疑问，如果我能运行更长时间，它会请小心使用它（并仔细检查你写的内容）。
这就是为什么在国家/地区，root 导致您的许多（硬件）故障，您可能会再次对您的设备造成物理损坏，请小心。值得庆幸的是，塑料钻头甚至下面的 LED 都可以轻松更换（塑料钻头与后玻璃分离，LED 还位于单独的带状电缆上）。
Click to expand...
Click to collapse
darken5404 said:
Click to expand...
Click to collapse
You can't say I didn't warn you!
Indeed flashlight in mark 3 and older xperias is very bad.
I compared it to an iPhone and it's like day and night. Many aspects xperia brand is suffering like front camera, flashlight, no 21:9 pics, missing 4k 60fps recording in main app with stabilization, poor screen brightness, insufficient battery capacity, no any cooling system (especially at this price there should be vapor chamber or any other advanced cooling and not throttling cpu as a solution...), Not to mention regular software apps like Album, email and others :/
MK73DS said:
You can't say I didn't warn you!
Click to expand...
Click to collapse
I got it fixed through sony aftermarket and has ip68,fixed the screen for me by the way
On android 12 after rebooting the function stops working.
So I got to the area of the phone you guys specified, but as of today, the default values are WAY different that what yall found. Let me take a few screen shots
Here is the systems default peramitors. Any idea why they are so different?
Edit- Okay, so extra piece to the puzzle. When torch is off, the brightness file is 0, but when it is on the file is set to 15.
editing the file while the torch is on does nothing.
Edit 2 - Just wanted to note that for those who just want a demonstration of the changes possible, the fallowing app will do just that
Release v1.4.6 · BRoy98/GodlyTorch
Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...
github.com
this app needs root. Run it as a HTC 10 and it works just fine. However, I would like to recommend NOT going over the half way point. its VERY bright and will probably kill your LED if you do. You have manual control over the brightness. You can add it as a shortcut in the drop down menu of your phone. simply use the standard torch button, and then click the godly torch button to activate whatever preset you gave it.
Edit 3 - setting the brightness in Godly Torch to 50% Intensity sets the brightness to 135. Given that we know damage starts to happen at 150, I set the brightness in Godly to 15% (under the "toggle Intensity" shown in the screen shot), which brings the brightness to a value of 45. Its easily double as bright. I would not recommend going past this point.
I would say by using godly torch as a HTC 10 worked...mind you I double checked the brightness by just hitting the quick toggle and then messing with godly torch. The lower setting is matching just turning on the quick toggle the higher setting is what I'm comfortable with, but idk how long I'm comfortable running it at that brightness.
BlazingKahn35 said:
On android 12 after rebooting the function stops working.
Click to expand...
Click to collapse
For those on stock who use the assistant button :
If it stops working after reboot, copy the binary file to somewhere safe on your sd card, then using XPosed edge just add a long press gesture to your assistant button that recopys the file from your sd card, then sets the permissions again (make sure to check run as root)
cp /sdcard/torch /bin/ | chmod +x /bin/torch