Scene slider for media device volume control? - Tasker Tips & Tricks

Hi,
i need help to create a slider in a scene to control some things on my Sony Android TV or Onkyo AV Receiver.
Onkyo: Master Volume Control
I can send an eISCP command via shell > echo > nc to the Onkyo in hex format like:
For absolute master volume of 25 > MVL19 (in hex format):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVL19\x0D' | nc 192.168.10.6 60128
For up & down master volume (if a command has more then 5 letters then x08 needs changed to x0A):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVLUP\x0D' | nc 192.168.10.6 60128
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x0A\x01\x00\x00\x00!1MVLDOWN\x0D' | nc 192.168.10.6 60128
It is also possible to stack commands with an " , ".
I can send a status question for the master volume to the Onkyo (but didn't know yet how to get this into Tasker ):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x0A\x01\x00\x00\x00!1MVLQSTN\x0D' | nc 192.168.10.6 60128
Maybe anyone can help here a bit to polish my Tasker Media Remote Scene.
Hoping also for a Tasker update to set a scene as a widget!

Related

ULV on milestone, how to?

hey you guys (and girls if there are any)
I'm using The froyo mod 2.9, and android 2.2.2
I'm having a little heat and battery problem,
but, I don't want to change the mod to something else.
I saw that there is a option to flash a ULV setting for the proccessor,
then, the phone can achive extra battery life and lower heat,
without leaving the froyomod.
because I'm a newbie, I wanted to ask, how it can be done?
It will affect the froyo mod?
are there any other problems that I need to be aware of?
thanks alot :]
*edit : found the ULV packs, how should I install them? as an Update (OR/updates) ? do I need to make any cache clear or not? and if I need to make a clear cache, wich one and what are the affect of the cleaning? (or wipe :/ )
thanks!
Why don't you just change your OC-settings in the OR overclocking menu?
if you have to go, don't say goodbye..
TBH I found that even running ULV didn't help battery usage much on FroyoMod, nor heat.
Anyway just put the ULV.zip from the FroyoMod thread into your OpenRecovery/Updates/ folder and update from AOR. Nothing will happen as it only updates the 10overclock file.
As already told the ULV just replaces the 10overclock file in system/etc/init.d
You have to adjust the settings yourself.
#!/system/bin/sh
insmod /system/lib/modules/overclock_milestone_21.ko
echo 0xc0295704 > /proc/overclock/cpufreq_stats_update_addr
echo 0xc004e4b0 > /proc/overclock/omap2_clk_init_cpufreq_table_addr
echo YOUR VALUE > /proc/overclock/max_vsel
echo YOUR VALUE> /proc/overclock/max_rate
#echo "5 800000000 48" > /proc/overclock/mpu_opps
echo "4 700000000 46" > /proc/overclock/mpu_opps
echo "3 500000000 35" > /proc/overclock/mpu_opps
echo "2 250000000 27" > /proc/overclock/mpu_opps
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 800000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table
echo "2 500000" > /proc/overclock/freq_table
echo "3 250000" > /proc/overclock/freq_table
insmod /system/lib/modules/cpufreq_interactive.ko
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
insmod /system/lib/modules/cpufreq_conservative.ko
#echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo 125000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
#echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step
Click to expand...
Click to collapse
I think [email protected] is the best, but [email protected] will work too, but your battery will drain quite fast.

[Root][Guide][MT6795] Improve the responsiveness and battery life on your X9

Update : Aug 8th 2017
These settings should benefit any helio X10 device maybe even other mediatek octa core devices.
The idea behind these settings is to keep the CPU in the lower frequency states and prevent unnecessary power drain when performing simple tasks.
to apply these settings I used Kernel Aduitor.
First Up Interactive Governor Settings
Code:
[SIZE="3"]Above hispeed delay - 20000 1326000:30000 1469000:40000 1781000:10000
Bootpulse duration - 0
hispeed freq - 1183000
boost - 0
go hispeed load - 70
io is busy - 0
min sample time - 20000
target loads - 60 1183000:80 1326000:90 1469000:97 1625000:99
timer rate - 25000
timer slack - 35000[/SIZE]
Limit you CPU to 1781MHz To save some battery all 1.9GHz does is produce heat and the performance isn't worth it.
Also you must disable touch-boost by editing the build prop line; ro.mtk_perfservice_support=1 to ro.mtk_perfservice_support=0
This will save a lot of battery life as the CPU won't jump to high frequencies when you touch the screen.
Also in Virtual Memory settings set the folowing
dirty ratio - 90
dirty background ratio - 80
dirty expire centisecs - 1000
dirty writeback centisecs - 2000
swappiness - 40
vfs cache pressure - 10
Z-RAM disksize - 300MB
Next up....... RAM management so the HTC X9 RAM management is good but it can be made better by going into the low memory killer tab in Kernel Auditor and tapping on the light option.
and that is it. we can't do much without a custom Kernel......... Also you can increase entropy by changing it's read value to 1664 and write value to 2048. I don't know if this is needed on marshmallow but I did it anyway.
Even more battery Savings
You will need Tasker for the following.............
Note: This Will limit your CPU to 5 cores and reduce unecessary CPU Scaling also will disable some bug checks
Make a new 'device boot' profile and add the following as tasks
1. Wait 30s
2.Run Shell:
Code:
[SIZE="3"]
su
echo "0" > /sys/module/alarm_dev/parameters/debug_mask
echo "0" > /sys/module/alarmtimer/parameters/debug_mask
echo "0" > /sys/module/binder/parameters/debug_mask
echo "0" > /sys/module/earlysuspend/parameters/debug_mask
echo "0" > /sys/module/sbsuspend/parameters/sbsuspend_debug_mask
echo "0" > /sys/module/pvrsrvkm/parameters/gPVRDebugLevel
echo "0" > /sys/module/musb_hdrc/parameters/debug_level
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level
echo "5" > /proc/hps/num_limit_low_battery
echo "5" > /proc/hps/num_limit_power_serv
echo "5" > /proc/hps/num_limit_thermal
echo "5" > /proc/hps/num_limit_ultra_power_saving
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
echo "1781000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1781000" > /proc/cpufreq/cpufreq_limited_max_freq_by_user
echo "0" > /proc/gpufreq/gpufreq_input_boost
echo "0-4" > /dev/cpuset/foreground/cpus
[/SIZE]
Make Another tasker Profile 'on device unlock'
1.Run Shell;
Code:
[SIZE="3"]
su
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
[/SIZE]
Credits;
jajk - Learned a lot from his Skinny Custom Boot thread.
I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.
m3johan said:
I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.
Click to expand...
Click to collapse
nope
thx.methods u said work on my htc x9.but like the 'Even more battery Savings' i not done yet
Htc one x9
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.
Lord Dre said:
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.
Click to expand...
Click to collapse
It's battery problem, Chagne it

With Tasker brightness not adjustable

Hi,
I have an issue with Tasker on my Oreo car stereo.
With Tasker I am not able to adjust the screen brightness:
Code:
Profile: Night (7)
State: Twilight [ Configuration:From CIVIL DUSK to CIVIL DAWN at Device location. ]
Enter: Dimmer ON (5)
Stay Awake
A1: Display Brightness [ Level:0 Disable Safeguard:eek:n Ignore Current Level:eek:ff Immediate Effect:eek:ff ]
A2: Set Tasker Icon [ Icon:mw_action_bookmark_border ]
Exit: Dimmer OFF (6)
A1: Display Brightness [ Level:255 Disable Safeguard:eek:n Ignore Current Level:eek:ff Immediate Effect:eek:ff ]
A2: Set Tasker Icon [ Icon:mw_action_bookmark ]
Even the manual executing of the task it doesn´t change the brightness.
Any hints how to get this working?
I used exactly this task on earlier radio with Android 7 and it is still working fine on my Phone with Android 7.
I think the behavior is related to Andoid 8, could that be possible?
Is adaptive brightness turned off?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Is adaptive brightness turned off?
Click to expand...
Click to collapse
Yes it is turned off in the Android settings, to not use the head lights.
Even if I switch off adaptive brightness in the task it doesn´t do anything.
The unit itself has no light sensor, so I need something which dims the screen brightness independant of the head lights.
rigattoni said:
Hi,
I have an issue with Tasker on my Oreo car stereo.
With Tasker I am not able to adjust the screen brightness:
Code:
Profile: Night (7)
State: Twilight [ Configuration:From CIVIL DUSK to CIVIL DAWN at Device location. ]
Enter: Dimmer ON (5)
Stay Awake
A1: Display Brightness [ Level:0 Disable Safeguard:eek:n Ignore Current Level:eek:ff Immediate Effect:eek:ff ]
A2: Set Tasker Icon [ Icon:mw_action_bookmark_border ]
Exit: Dimmer OFF (6)
A1: Display Brightness [ Level:255 Disable Safeguard:eek:n Ignore Current Level:eek:ff Immediate Effect:eek:ff ]
A2: Set Tasker Icon [ Icon:mw_action_bookmark ]
Even the manual executing of the task it doesn´t change the brightness.
Any hints how to get this working?
I used exactly this task on earlier radio with Android 7 and it is still working fine on my Phone with Android 7.
I think the behavior is related to Andoid 8, could that be possible?
Click to expand...
Click to collapse
Hi Mate.
I have exactly the same problem. Did you get a solution?
I have a Xtrons Android 8 unit and brightness does not work , exactly like you explained.
Did you get a solution?
Hi,
there will be no solution until they use the Adroid_API as it should be.
Tasker uses the API, but the dev of our version seems to use different folder structures.
If I have a look at the traces I find the following entry:
Code:
05-07 13:45:54.415 292 292 E Lights Hal: write_int failed to open /sys/class/backlight/rk28_bl/brightness
/sys/class/backlight/rk28_bl/brightness would be the correct folder used by the API.
The reason for this issue is, that the folder rk28_bl does not exist. The file "brightness" is stored in folder:
/sys/class/backlight/backlight/brightness
I´m thinking about a method to get a workaround for this issue, but I don´t have the needed time to do it in the moment.
Hello,
I have the same issue. Did you find how to fix this?
alek_05 said:
Hello,
I have the same issue. Did you find how to fix this?
Click to expand...
Click to collapse
I got a new firmware for my Pumpkin and use FCC car launcher, which is able to do it.
rigattoni said:
Hi,
there will be no solution until they use the Adroid_API as it should be.
Tasker uses the API, but the dev of our version seems to use different folder structures.
If I have a look at the traces I find the following entry:
/sys/class/backlight/rk28_bl/brightness would be the correct folder used by the API.
The reason for this issue is, that the folder rk28_bl does not exist. The file "brightness" is stored in folder:
/sys/class/backlight/backlight/brightness
I´m thinking about a method to get a workaround for this issue, but I don´t have the needed time to do it in the moment.
Click to expand...
Click to collapse
Try this, run shell with tasker :
settings put system screen_brightness=216
value : 0 to 216
philippe734 said:
Try this, run shell with tasker :
settings put system screen_brightness=216
value : 0 to 216
Click to expand...
Click to collapse
No that can not work... and it does not work with OREO head units... at least not with mine.

URGENT: Raspberry Pi 3B Fails to Connect to HDMI Monitor

Hi all, urgently need help with displaying output form Raspberry Pi to my HDMI monitor! I'm trying to boot Pi 3B with USB and display onto an HDMI monitor, but all the output I see is a black screen.
Tools:
- 1x USB (flashed via Etcher with Debian Stretch with Raspberry Pi Desktop)
- 1x monitor (connected via HDMI-HDMI 1.5m cable): 1024x768
- 1x Raspberry Pi 3B model (connected to 5V supply)
I've referenced many relevant threads, changed my "config.txt" file accordingly, but it doesn't seem to fix the problem.
Here's my config.txt file:
program_usb_boot_mode=1
# For more options and information see
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=16
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=11
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
Any assistance is greatly appreciated!!

Any Way To Control Charging

Has anyone figured a way to control the charge limit via Input Power Control module or the app Battery Charge Limit? I've stuck out with both unfortunately.
Set a custom control file for Battery Charge Limit...
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
The phone will still say that it is charging, but the battery level will have stopped where you set it to.
Anyone found a solution for Android 11? I used the above settings fine on 10 with battery charge limit app, but on 11 it will intermittently charge to 100% overnight.
Edit-Advanced Charging Controller magisk module seems to be working so far.
The app battery charge limit was working with the post no 2 settings until i updated to android 11.
Will try the magical.module and report back. A bit difficult to setup. Hard to read via terminal.
Sent from my Nexus 5 using Tapatalk
Battery Charge Limit still works for me with Sept/Oct updates.
On android 11?
Care to share your settings?
Sent from my Nexus 5 using Tapatalk
Sorry, but it never stopped working for me... so I'm using the same settings I posted above.
On android 11?
Sent from my Nexus 5 using Tapatalk
What else would September and October updates be?
I am using same setting with Tasker to limit my charging to 80% on overnight charging.. It still works now on Android 11.
jljtgr said:
Set a custom control file for Battery Charge Limit...
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
The phone will still say that it is charging, but the battery level will have stopped where you set it to.
Click to expand...
Click to collapse
This is working for me on a Pixel 4 XL with the latest Android 11.
EDIT: Got it working perfectly with these additional settings:
Enforce charge limit: disabled
Always Write CFTRL File: enabled
------------------------------------------
so to put it all together, for the Pixel 4 XL:
Manually enter Configure Control Data ->
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
Advanced settings ->
Enforce charge limit: disabled
Always Write CFTRL File: enabled
Since Battery Charge Limit is somewhat abandoned and might get disrupted more by successive Android versions... I started looking into replacing this functionality with Tasker... since Tasker is supported, it should keep running despite new battery optimizations.
I've attached the full Tasker project at the end. Download it to your phone, open Tasker, long-press the Home icon at the lower-left, select Import Project and select the XML file attached. Lastly, manually run the "Charge Limited" task. This will set up the QuickTile and %BATTLIMIT variable.
Here are some description exports of what the project does.
Code:
Profile: Check Battery To Enable (92)
Restore: no
State: Battery Level [ From:0 To:55 ]
State: Power [ Source:Any ]
Enter: Enable Charger (88)
A1: Read Line [ File:/sys/class/power_supply/charger/charge_disable Line:1 To Var:%bdisable Structure Output (JSON, etc):Off ]
A2: If [ %bdisable ~ 1 ]
A3: Flash [ Text:Enable: %BATT% Long:Off ]
A4: Run Shell [ Command:echo '0' > /sys/class/power_supply/charger/charge_disable Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: ]
A5: End If
Code:
Profile: Check Battery To Disable (93)
Restore: no
State: Battery Level [ From:60 To:100 ]
State: Power [ Source:Any ]
Time: Every 2m
Enter: Disable Charger (87)
A1: Read Line [ File:/sys/class/power_supply/charger/charge_disable Line:1 To Var:%bdisable Structure Output (JSON, etc):Off ]
A2: If [ %bdisable ~ 0 & %BATTLIMIT ~ 1 ]
A3: Flash [ Text:Disable: %BATT% Long:Off ]
A4: Run Shell [ Command:echo '1' > /sys/class/power_supply/charger/charge_disable Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: ]
A5: End If
There are two other tasks that configure the AutoNotifications tile and a task that accepts commands from the tile.
This obviously requires root. I will not answer any questions about not requiring root.
For QuickTile functionality, you will need AutoNotifications. If you don't have AutoNotifications, you will have to go into Tasker to toggle the functionality manually. For me, this uses AutoNotifications tile #2, you may need to configure the AutoNotifications task config to use other tile #'s. This was made for a Pixel 4 XL. It probably works for the Pixel 4. It might work for other Pixel phones, but I have no idea.
Edit: I redid my phone and noticed that Tasker can no longer ReadLine on rooted paths... so I had to replace it with a root shell command. (unfortunately this means a toast will appear for root usage every couple minutes, which I personally disabled in Magisk)

Categories

Resources