Database Develop

[Android 2.1+] SIP HorsePower Dyno - measure your performance

Playstore Link:
https://play.google.com/store/apps/...siphorsepowerdyno&feature=more_from_developer
Updates in second post: http://forum.xda-developers.com/showpost.php?p=29938013&postcount=2
{
"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"
}
This is a dyno app, for scooters, motorcycles or cars.
I have only tested it on my vespa, but people told me it works good on other vehicles, aslong the engines sound can be recorded and IT IS NOT AN AUTOMATIC SCOOTER !
Unlike all other dyno apps, I don't use the GPS signal or the accelerometer to measure your speed, but i use the sound.
Ok, I know what you are thinking:
"Dude this wont work or do you really think: The louder the faster ?"
Here is how it works:
Each sound has its specific frequency, consider someone whistling low or high.
The frequency is always the same, let's say you run your engine at 2000 RPM or 2100 RPM, i can measure 2 different frequencies there and i can exactly say at which RPM the engine runs.
From the RPM i can calculate the EXACT speed (GPS or accelerometer just isn't exact, it's a mess).
From the speed difference at 2 points of time i can calculate the power that is needed to get from speed1 to speed2.
Done, thats it.​
There are a couple of important things you should be aware of, before you download the app:
1. Not all devices support the recording quality, therefore i uploaded a test app. Please download it, record sound (speak or something else, doesn't matter). Then replay the sound. If it doesn't force close, you are good to go. Link: https://play.google.com/store/apps/...29tLnBsZWRsc3RlZmFuLmhvcnNlcG93ZXJ0ZXN0ZXIiXQ..
2. In order to get the measurement right you need to know these values (it is a very technical app):
Overall Weight (vehicle + you + gas + backpack + helmet + trousers + shoes ...)
Gear Ratio (this needs to be as exact as possible as well, i use the overall gear ratio, which is your gear ratio divided by your tire-circumference in meter, i have an option to calculate the gear ratio by using the GPS speed, but as said before the GPS isn't exact enough)
Cw-Value (if you dont know what this is, please google it. I could fill a whole thread with information on this. If you don't enter the exact value here, you will still get comparable results for different dyno runs and engine setups aslong you leave this value the same)
Frontarea in squaremeter: (either measure it, or just leave the value, like the Cw-Value to get comparable results)
Temperature + air pressure: (can be get online, within the app)
One thing i didn't consider yet is how the tire changes during the run, the faster it spins the higher the tire circumference gets.
I compared my measurements to real dyno runs and its usually only about 0.5 horsepower off.
The displayed horsepower is "power on the ground". I know americans have some other fancy methods to measure this, but to be honest, "power on the ground" is the only measurement that is worth measuring.
Unlike power on the crank it is the real value which your engine has on the street.
Maybe you might have noticed that i am not native english speaking, so here are a couple of copy/pastes from other users, which i think help to explain what is going on:​
I tried a couple of more runs with this app. I'm really fascinated by your app. This time I tested mypinasco 225cc Vespa GL.
I still can't find a big enough road for that 3rd gear run, but I did ride on and off the motorway a couple of times in 2nd gear. Both runs gave me the same result within 0.5hp
Click to expand...
Click to collapse
it would be power at the ground. The sound frequency gives you the RPM of the engine, knowing the gear ratio and tire size gives you speed. The rate of change gives you acceleration.
Power = Force * Velocity
The forces that we care about are due to acceleration (f=ma) and drag (f=1/2*roh*A*C*V^2).
We know the mass, acceleration we got above, roh is constant and known for air at a given temp and pressure, frontal area*drag coefficient can be estimated, and velocity is known from above as well.
So, as long as you are not doing a burnout, it can measure the power at the ground.
Click to expand...
Click to collapse
Text Tutorial which i wrote here:
http://modernvespa.com/forum/topic101980?page=1
1. Go to “Settings”
Here are 2 options:
a) Calculation by Overall Gear Ratio
From the RPM/min the Speed is calculated by the overall gear ratio which you can enter below.
Overall Gear Ratio: “Primary Gear Ratio” times “Secondary Gear Ratio” devided by “Tire Circumference in meter”
E.g.rimary : 60/20=3
Secondary: 50/20 = 2.5
Tire Circumference in meter: 1.3
Overall Gear Ratio: 3 * 2.5 / 1.3 = 5.769
b) Calculation by Maxspeed
If the GPS was on during the run I record the speed and look for the max speed. Then after editing the frequency spectrum I look for the max RPM and calculate the Overall Gear Ratio. The GPS signal is sometimes unreliable so I recommend using option a.
If you have a digital Speedometer you can also check the max speed and enter it at “GPS TOP Speed in km/h” with option “b” checked.
All other settings are pretty obvious, just enter them as precise as possible.
If you don’t know the Cw-Value just leave the predefined value in there,
In order to compare different scooter setups, please keep in mind that these values should not change (unless they really changed, e.g. you lost 20kg or dismounted a windshield or whatever) and that you should keep the same position on the scooter for all dyno runs
Save the settings.
2. Go to “New Record”
Find a place where no other vehicles are. Best is a street which has a minimal gradient upwards.
If you want to record the GPS Speed hit the checkbox in the bottom right, enable the device’s GPS if it is not already (a popup will show up if it is not enabled) and wait for a GPS Lock.
Hit the Microfon-Button. The record is now started and the Buttons are locked. Locking the Menu Button is not possible, so don’t touch it. Power Button will shut the screen off, but the record will keep going.
NOW PUT YOUR DEVICE IN A BACKPACK!
In your pant’s pocket the airstream will be too loud, thus making it harder to find the right frequency.
Get on your scooter and start driving slowly. Shift to 2nd ord 3rd gear and from lowest RPM possible full throttle to max speed and hold max speed for a bit.
Stop your vehicle, get your phone and slide the ring from right to left to unlock the buttons.
Hit the microfone button again.
3. Find the run
Here you can see (easy put) the volume of your record. By pressing the Menu Button (^) you can replay the record, where the white area shows the replayed part. Move the red bars until the record of the run (from low rpm to high rpm) is in-between the red bars. Hit menu(^)-> Trim. The red areas will be cutoff, the green part will stay. Replay the record and see if all went fine or continue editing the now zoomed in part.
When done hit > to go to the next screen.
4. Find the right RPM curve
Usually our scooters have their max RPM at around 8000-9000 rpm. So your first look goes to the left side to find these rpm. Then look at the right side which curve has its max rpm at 8000-9000.
You should now know which curve is the correct one. Unfortunatly its not that easy to find the right curve programmatically, so what you first do now is:
Menu(^) -> Snap
Snap: This function starts looking on the very left side of the spectrum to find the signal with maximum strength. Then it looks in a small range heading right for the next max strength signal. Please keep this in mind !
Start removing the false signals from the very left and eventually “Snap” will snap to the right curve.
If snap wont find the right curve, because on the very left side it finds a curve under the real one, then you should either go back and cut the record a little earlier, so there is a signal of your run with lower rpm
Or
Disable snap ad completely edit the spectrum by hand, removing all false signals.
The white line shows the signals which will be used for calculation.
The green line is the smoothed signal, smoothing the signal is necessary. You can play around with the filterlength on the “Edit Spectrum” screen and on the “Result” screen. The larger the filterlength, the smoother the signal will be. But unfortunately too long filterlengths will lead to a wrong result. Play around with the filter on the spectrum screen and the result screen to see what it actually does.
5. Result
Well this is your result. You can save it and compare it to other results or you can share it with your friends.
Will this text tutorial work without pictures for you guys ?
If something isnt clear, just let me know, maybe suggest a better wording
I was asked what some permissions do or why the app needs them, so:
This application has access to the following:
Hardware controls
record audio
->well, no need to explain this i guess
Your location
fine (GPS) location
-> ... GPS
Phone calls
read phone status and identity
-> if a call is incoming i have to handle the current app state, for example stop the record, or stop the "data transforming" and so on
modify/delete USB storage contents or modify/delete SD card contents
-> save record to sd card/delete the record
Network communication
full Internet access
-> just needed to get the weather online
System tools
modify global system settings
->i am kinda confused why google makes this sound so bad, this is the permission to save private app settings (i use this to save weight,gear ratio, temperature...)
in code all permissions look like this, with the bold being this permission
uses-permission android:name="android.permission.PREVENT_POWER_KEY"
uses-permission android:name="android.permission.RECORD_AUDIO"
uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"
uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"
uses-permission android:name="android.permission.READ_PHONE_STATE"
uses-permission android:name="android.permission.INTERNET"
uses-permission android:name="android.permission.WRITE_SETTINGS"
uses-permission android:name="com.android.vending.CHECK_LICENSE"
Click to expand...
Click to collapse
Either watch this thread or follow me on Google+ for updates:
https://plus.google.com/105280101829289526269/posts
or:
https://plus.google.com/109720416927515295704/posts
If there are apple fanboys around here:
I am working on an iphone version.

Changelog:
06.09.2012:
Added "SHARE" at compare results
03.09.2012:
Jelly Bean related fixes
16.08.2012:
Mean of results can be build
13.08.2012:
Files go into different folders now
fixed a couple of typos and missing translation
The only problem right now is the filterlength, which i use to smooth the curve.
The automatic detected length is usually too short, so please change the value on the result screen.
I saw at least one word in the english version which was german, this is because the new eclipse version somehow doesn't handle files with the same filename right.
To come:
An option to rename the record straight after recording.
An option to build the mean of different results.
A better filter, without the need of chossing the filterlength.
I am pretty busy with my tests at University, so please dont expect any update before the 16th of August.

Wow! Very cool app! How goes the progress on it? I always wanted to make a measurement of actual power of my Vespa but the costs of diagnosis on the dyno seem to me to be too expensive. I hope that in two days there's an update to the application.

Version 1.5 is out, with the long awaited option to build the mean of different runs!

Version 1.6: jelly bean related fixes

1.61: Added "share" button to compare results.
Gesendet von meinem Nexus 7 mit Tapatalk 2

Very cool, and I want to get distance. As you say, f =ma,time can be recorded, the distance between two positions could be culculated.
Sent from my SHW-M250S using xda app-developers app

Sure, i will add that later.
I released a Free Version:
https://play.google.com/store/apps/...sZWRsc3RlZmFuLnNpcGhvcnNlcG93ZXJkeW5vZnJlZSJd

Updates in 2.03:
- The spectrum is visible at the "Trim Screen". This means it is lot easier to find the right positions to trim the record.
- Edit Spectrum: it is no possible - by turning "change snap area" on to tell the algorithm where it should look for the right signals. So instead of wiping the wrong signals you chose where the curve should be. This makes the editing much easier.
- Added the option to chose between DIN and SAE climate correction factors.
- Added the option to display the torque in NM or ft-lbs.
- Added a reminder to update the weather when a new record is done.
- The last two locations are saved at the Update Weather screen.
- lots of bugfixes
- details are attached to the email message and are inserted into the jpg when a result is shared
- UI changes: the navigation bar at the bottom is gone and was replaced by an ActionBar,

Some people still seem to think that this is something like a burp app.
->
http://www.scootering.com/Current-Issue/
94 Tech Tips – A Dyno in Your Pocket?
Yes it’s true, and Sticky checks it out.

[GUIDE][Difficulty: Beginner] Shake your Phone to Increase Brightness

If you dislike Android's auto-brightness implementation or have turned it off entirely, then this guide will help you set-up Tasker to toggle the brightness whenever you shake your phone. This is helpful for when you're outside and would rather not reach for the brightness slider (which can be difficult for larger phones while one-handed).
Instructions
Create a new Profile and name it "Toggle Brightness."
Create an Event context and go to Sensor. Pick the Shake event. For Axis, I recommend Left-Right as this is a pretty natural way to shake the device. For Sensitivity, I recommend Very Low so you don't accidentally toggle the brightness. You can also leave it at Low in case you think you're having to shake it to hard to get it to work, however. For the Duration, I would pick Medium. You can experiment with these settings until you're comfortable.
Exit and create a task. No need to name it since it's unlikely you'll use this task elsewhere.
{
"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"
}
Task --> If. Set it to %BRIGHT ~ 255. This will check if the device brightness is already at maximum.
Display --> Display Brightness. Set the Level to %Bright. This will be the saved brightness that will be restored when you shake the device again.
OPTIONAL: Display --> Display Timeout. Set the display timeout to restore to what you normally use.
Task --> Else.
Variables --> Variable Set. Set %Bright to %BRIGHT. You're storing the current brightness level to a variable to restore on next shake.
Display --> Display Brightness. Level 255. You're setting the brightness to maximum.
OPTIONAL: Display --> Display Timeout. Set this to a higher display timeout in case that's what you want.
Task --> End If.
That's it! Now when you shake your phone, your brightness will toggle between maximum and whatever it is you had before you switched to the maximum.

Thanks for the tutorial. I got it to work but it won't revert back to the original state it was in. It keeps going back to like 15% or so. Any idea why? Double checked and have everything the same that's in your screenshot

I can't pass through point 2 how to set brightness level to %Bright ? I can only set it from 0 to 255 with slider there is no text input field

Very nice guide, works perfectly. Only thing is, the new version of tasker doesn't have some of the same settings. Take for example, step 2 where you put "Level %Bright", I only have a slider to set brightness. Got it figured out none the less.
Domino5 said:
I can't pass through point 2 how to set brightness level to %Bright ? I can only set it from 0 to 255 with slider there is no text input field
Click to expand...
Click to collapse
I just set the slider to 15%

Domino5 said:
I can't pass through point 2 how to set brightness level to %Bright ? I can only set it from 0 to 255 with slider there is no text input field
Click to expand...
Click to collapse
kenboyles72 said:
Very nice guide, works perfectly. Only thing is, the new version of tasker doesn't have some of the same settings. Take for example, step 2 where you put "Level %Bright", I only have a slider to set brightness. Got it figured out none the less.
I just set the slider to 15%
Click to expand...
Click to collapse
Sorry, there is some confusion here (it's a problem with Tasker's UI being so clunky!) By default, certain actions such as changing the brightness show a pre-defined slider that you can move up and down, however you CAN use a variable to set the brightness like I mentioned.
When you enter the Display --> Display Brightness screen, click on the little double arrow criss-cross icon near the top right and it will switch the slider view to a text input view. Here, you can simply write in %Bright and tasker will interpret the variable as a number that will set the brightness. Keep in mind that %Bright must be between 0 and 255 because those are the only acceptable values for the brightness, however this should not cause any problems because you are simply setting brightness to whatever it was previously.

MishaalRahman said:
Sorry, there is some confusion here (it's a problem with Tasker's UI being so clunky!) By default, certain actions such as changing the brightness show a pre-defined slider that you can move up and down, however you CAN use a variable to set the brightness like I mentioned.
When you enter the Display --> Display Brightness screen, click on the little double arrow criss-cross icon near the top right and it will switch the slider view to a text input view. Here, you can simply write in %Bright and tasker will interpret the variable as a number that will set the brightness. Keep in mind that %Bright must be between 0 and 255 because those are the only acceptable values for the brightness, however this should not cause any problems because you are simply setting brightness to whatever it was previously.
Click to expand...
Click to collapse
I do not see any criss-scross icon in the top right as you mentioned!

Where to add if I am to tell Tasker to turn brightness to 30% after a certain period of time ?
By the way , Thanks to the tips and it works perfectly !
Just want to add an additional task the let tasker return to a lower brigntness automatically say in about 5 minutes or so.....
Where I should put this in ? ( i.e. after ' End if ' ? )

MishaalRahman said:
If you dislike Android's auto-brightness implementation or have turned it off entirely, then this guide will help you set-up Tasker to toggle the brightness whenever you shake your phone. This is helpful for when you're outside and would rather not reach for the brightness slider (which can be difficult for larger phones while one-handed).
Instructions
Create a new Profile and name it "Toggle Brightness."
Create an Event context and go to Sensor. Pick the Shake event. For Axis, I recommend Left-Right as this is a pretty natural way to shake the device. For Sensitivity, I recommend Very Low so you don't accidentally toggle the brightness. You can also leave it at Low in case you think you're having to shake it to hard to get it to work, however. For the Duration, I would pick Medium. You can experiment with these settings until you're comfortable.
Exit and create a task. No need to name it since it's unlikely you'll use this task elsewhere.
Task --> If. Set it to %BRIGHT ~ 255. This will check if the device brightness is already at maximum.
Display --> Display Brightness. Set the Level to %Bright. This will be the saved brightness that will be restored when you shake the device again.
OPTIONAL: Display --> Display Timeout. Set the display timeout to restore to what you normally use.
Task --> Else.
Variables --> Variable Set. Set %Bright to %BRIGHT. You're storing the current brightness level to a variable to restore on next shake.
Display --> Display Brightness. Level 255. You're setting the brightness to maximum.
OPTIONAL: Display --> Display Timeout. Set this to a higher display timeout in case that's what you want.
Task --> End If.
That's it! Now when you shake your phone, your brightness will toggle between maximum and whatever it is you had before you switched to the maximum.
Click to expand...
Click to collapse
Can you make a video tutorial as i'm not into these stuff. Few step by step pics would work.. If you want to....?

i did these all steps
But when i turn this profile on my screen brightness continously changes without any action
It becomes max nd min regularly infinite times withou shacking

R3XER said:
Can you make a video tutorial as i'm not into these stuff. Few step by step pics would work.. If you want to....?
Click to expand...
Click to collapse
The text guide I wrote shows you how to add everything step by step. Try it out first.
lalitkhokhar said:
i did these all steps
But when i turn this profile on my screen brightness continously changes without any action
It becomes max nd min regularly infinite times withou shacking
Click to expand...
Click to collapse
That is because you're running the task, and haven't linked it to a profile. You need to create a profile and just leave it be. Don't click on the run button.

tmkinger said:
I do not see any criss-scross icon in the top right as you mentioned!
Click to expand...
Click to collapse
Go in to your UI preferences and uncheck Beginner Mode. It should pop out then.

MishaalRahman said:
The text guide I wrote shows you how to add everything step by step. Try it out first.
That is because you're running the task, and haven't linked it to a profile. You need to create a profile and just leave it be. Don't click on the run button.
Click to expand...
Click to collapse
No I am not doing so
I am creating a profile and tasks as said
But when I exit tasker brightness start fluctuating itself

lalitkhokhar said:
No I am not doing so
I am creating a profile and tasks as said
But when I exit tasker brightness start fluctuating itself
Click to expand...
Click to collapse
you have to disable auto brightness to make it work, or add auto brightness on and off respectively at the begin of the 2 steps in the task.
i modified the task so i can left auto mode turned on and shake the phone when i need full brightness.

Is't working great for me, Thanks!

Sorry for second time my question..............
How I can modify this profile ( or task ) if I am to tell tasker turn back Brightness to 30% ? ( say in 2 minutes to turn back to 30% brightness )
Also is it possible to have an icon on top of my phone so I know whether or not the profile is on ( or the icon no show when profile off )
Thank you very much.
edmond.

eeeemc said:
Also is it possible to have an icon on top of my phone so I know whether or not the profile is on ( or the icon no show when profile off )
Click to expand...
Click to collapse
Add a Notification to the task, it's pretty straightforward.

Thanks, this is my first time using tasker and it worked well. Easy to follow instructions.
I was just wondering though, yours has gree bars down the side of all the info, one of mine is red. Its doing what its supposed to anyway, but just wondering why this is? It works anyway.
Also in my notification bar it still says theres no active profiles, even though i've now created this one.
Edit:
Never mind, I understand how the active profiles thing works now i've made a few more

Works great, and the guide is easy to follow. Thanks!

Thanks...........
However, I still unable to figure out where & How to add a notification ---> on to same line of battery level icon when this profile is activated.
I play around & found I could add a notifiction from " Notification drop down ". ( but how about a steady icon on top line of screen as above said ? )
Thank you very much.
FenrirMX said:
Add a Notification to the task, it's pretty straightforward.
Click to expand...
Click to collapse

beren said:
you have to disable auto brightness to make it work, or add auto brightness on and off respectively at the begin of the 2 steps in the task.
i modified the task so i can left auto mode turned on and shake the phone when i need full brightness.
Click to expand...
Click to collapse
Thank you very much, this helped me

Phone number Search

Hey Ara! Thanks for tackling this series. I know that AC ranges from 101 articles, to device rumor mill articles, to tasker tutorial type articles, and based on comparing the comments of the full spectrum of articles, it looks like the tasker crowd might not be as large as some of the other crowds that read and are interested in ACs other stories, so... props to ya for taking on the giant.
I've been using tasker since I had the OG Droid and have loved its functionality. Lately though, I've been stumped on one thing in some of my tasker profiles that I just can't seem to nail down. It's a function that you may or may not be familiar with unless you've done other types of programming, specifically logic programming like ladder logic (PLC). I'm looking for an ON DELAY TIMER, not just a timer that begins and continues counting when a series of contexts (permissives) is activated, but a timer that will ONLY count while the contexts are true, and will stop counting AND RESET when at least one of the contexts isn't true. This way, if you want something to happen 5 minutes after your screen is on and your screen hasn't shut off into sleep mode, it will execute a task, but if for some reason the screen does shut off before 5 minutes, it will not execute the task and will begin counting from 0 sec the next time the screen turns on. I've tried to make custom ON DELAY TIMERS with variables and other methods, but my profiles just don't work the same as if there were just a simple ON DELAY TIMER task built in (Currently with variables, I can only start a timer based on contexts, and then check in an amount of time to see if the contexts are still true at the end of the timer, but nothing to stop the profile if a context goes false during the timing... so with my screen example, tasker can't tell the difference between the screen turning on for a minute, off for 3 minutes and on for 2 minutes and the screen being on for 6 minutes straight.). Anyway, if you, or anyone reading this stupid long comment, knows where to find this ON DELAY TIMER, or how to create one in tasker, please spread the wealth! Thanks!
Phone number Search

You can accomplish this but it will eat some RAM.
Have contexts trigger delay timer task.
In delay timer :
1 add variable, say %timer and add 1.
2 wait 1 second
3 stop task if criteria are not met.
4 goto step 1 (variable add) if %timer < set number.
5 whatever action you want triggered when counter reaches end
You can add some steps before the #1 listed for a dialog, spinner, etc if you want user to set new time each use.
Hope this helps.
Zac

[APP][Automate] Eye comfort mode between sunset and sunrise

I got annoyed that the eye-comfort mode could only be scheduled on fixed times and I had to constantly change them during spring and autumn.
So I made this simple flow for the Automate app - it is probably something like Tasker but it is free for a task with a few blocks - ideal for cheapskates like me.
I used this flow by Sándor Illés to calculate sunset and sunrise times.
The flow
It gets current location, calculates the times and then sets them up as schedule times (eye_comfort_starttime and eye_comfort_endtime system variables).
Then it waits for 1:00 (am) and starts over again.
I just tested it for 3 days and it runs ok on my View 10 with EMUI 9.1. No idea whether it works on older and newer versions or not. //edit: Works okay after EMUI 10 update too.
How to?
Basically, you install Automate, go to the settings and enable resuming flows after system startup.
Extract and install this flow, start it and it should daily update the schedule times.
You obviously also have to have eye-comfort schedule enabled.
On a related note: Stronger eye-comfort filter
I always felt that the blue light filter using eye-comfort is quite weak. During my search for correct variables to modify, I discovered that the highest value for filter you can select using the slider in the eye-comfort settings is 20, but you can dial the filter up to 50 and it gets slightly stronger then!
It is user_set_warm system variable.
Funnily enough, there are also eye_comfort_lesswarm and eye_comfort_morewarm variables which change the range of the slider in the settings.
You can set the eye_comfort_morewarm to 50 and then the slider in the settings will let you set the filter stronger. Higher values than 50 turn the filter off though.
The system variables can be modified using the "system settings set" block in the Automate or simply using SetEdit app. They can probably be changed using ADB too, but I didn't try that. Sadly these settings reset after reboot.
No root required for any of that.

Great stuff! Looking for the same feature on my Huawei phone but unfortunately, the file that you have attached has been removed. Could you upload it again? Thanks

Samuel Grande said:
Great stuff! Looking for the same feature on my Huawei phone but unfortunately, the file that you have attached has been removed. Could you upload it again? Thanks
Click to expand...
Click to collapse
What, they just deleted all the user uploaded stuff when changing the boards? Now that's a shame.
Anyway, I reuploaded the file.

Tasker Scene WebView JavaScript Interaction

Is it possible to call a Javascript function that exists within a WebView from Tasker? I tried calling a URL on the WebView of "javascript:FUNCTION_NAME()", but that did not seem to work.
This is a completely random example. Lets say, from Tasker, that I want to be able to change the background color of the body of the WebView.
In the webview, I have the code
JavaScript:
function ChangeBGColor(NewColor)
{
document.body.style.backgroundColor=NewColor;
}
I want to be able to call ChangeBGColor() from Tasker with a color.

I remember having this same question a while back and was unable to find a solution that didn't involve sending HTTP requests, so I came up with a really weird hacky solution. I'm not sure its going to work for your situation, but maybe it can give you some ideas.
On the web side- have a transparent div element that occupies a single pixel. Put it in a corner or somewhere you won't accidently touch it. Now, add an event listener to it like this:
element.addEventListener('touchend', (e)=> {
let x = e.changedTouches[0].clientX;
let y = e.changedTouches[0].clientY;
renderColor(x, y);
});
On the Tasker side- If you don't already have it, download AutoInput, which is plugin that was created by Joao Diaz before he took over development of Tasker, and its incredibly cheap for what it does. You can use it to simulate a swipe gesture that starts at that exact spot on the screen, and ends at the coordinates you specify. You now have a way to send two values from tasker to you Javascript with a possible range of your screen resolution.
This might be challenging if you want the full spectrum of colors, because ideally you would want 3 parameters with 256 possibe values (0 for 00 and 256 for FF), so you'll have to figure out a way to encode and decode your color. You could either dumb down the resolution of colors and then use some math involving the modulus operator, but a better way would be to send the data via two swipe gestures, which would give you 4 parameters to work with- so to send white with full opacity (FFFFFFFF), simulate a swipe starting at 0,0 and ending at 256, 256 (FF or 256 for your alpha value, and the same for red), have your Javascript function store that in a variable. Then, send the second swipe which in this case will be the same as the first, and you now have 4 values to give you your color. Keep in mind you'll want to offset everything by 1 or you wouldn't be able to send black, since swiping from 0,0 to 0,0 won't trigger anything.