Related
I'm really sensitive to the button backlight screen bleed on these phones. Here are two things which have helped me so far:
1. mVideoPlayer https://market.android.com/details?id=afzkl.development.mVideoPlayer&feature=search_result
This is the only video player I have found which disables the button backlight when playing in the dark.
2. Screen Filter https://market.android.com/details?id=com.haxor&feature=search_result
Allows you to disable the button backlight all together!!! Set the filter to 100% if you don't want it to dim your screen and the de-select the check box for soft-key backlight.
Ideally I would prefer to find an app which will timeout the capacitive back lighting but I have not been able to find one.
Dude... you just fixed my phone!
I used the screen filter app and it works perfect!
I mean those buttons are in the same place all the time why do they even need to be lit?
Thanks for sharing~
Turboboxer said:
Dude... you just fixed my phone!
I used the screen filter app and it works perfect!
I mean those buttons are in the same place all the time why do they even need to be lit?
Thanks for sharing~
Click to expand...
Click to collapse
I felt the same way
Thanks a lot that screen bleed is gone. Doesn't bother at all now. Never need the keys at the bottom to light anyways.
Sent from my HTC_Amaze_4G using xda premium
Tasker + Locale Execute Plug-in
OR
Tasker + Secure Settings (Recommended)
Secure Settings -> Market Link
Local Execute Plug-in -> Market Link
Tasker -> Market Link
There is a difference between the Market Version and Off market version -> http://tasker.dinglisch.net/faq-ov.html
Command to turn off softkeys backlight -> echo 0 > /sys/class/leds/button-backlight/brightness
For Locale Execute Plug-in, "@! echo 0 > /sys/class/leds/button-backlight/brightness" without the quotes
heyodee said:
Tasker + Locale Execute Plug-in
OR
Tasker + Secure Settings (Recommended)
Secure Settings -> Market Link
Local Execute Plug-in -> Market Link
Tasker -> Market Link
There is a difference between the Market Version and Off market version -> http://tasker.dinglisch.net/faq-ov.html
Command to turn off softkeys backlight -> echo 0 > /sys/class/leds/button-backlight/brightness
For Locale Execute Plug-in, "@! echo 0 > /sys/class/leds/button-backlight/brightness" without the quotes
Click to expand...
Click to collapse
Nice, but why spend the money if you only using it for that feature??? Couldn't you just run the echo from a Terminal?
vw671 said:
Nice, but why spend the money if you only using it for that feature??? Couldn't you just run the echo from a Terminal?
Click to expand...
Click to collapse
Tasker is arguably one of the best apps ever developed on android. Its feature extensive. A must have app for all android devices. Then again, that's my setup, tot i share
vw671 said:
Nice, but why spend the money if you only using it for that feature??? Couldn't you just run the echo from a Terminal?
Click to expand...
Click to collapse
Yes it can be tun straight from terminal emulator.
Code:
su
echo 0 > /sys/class/leds/button-backlight/brightness
chmod 0333 /sys/class/leds/button-backlight/brightness
The second line makes the changes permanent until reboot. Otherwise locking the screen and unlocking again, as well as some other things, will turn the backlights back on again.
To undo the permanence, type this:
Code:
su
chmod 0647 /sys/class/leds/button-backlight/brightness
vw671 said:
I felt the same way
Click to expand...
Click to collapse
+1,000,000 and thanks OPoster for this!!!
the screen filter darkens it a lot..
Felinos11 said:
the screen filter darkens it a lot..
Click to expand...
Click to collapse
Set it to 100% to disable the filter.
Thank you!!! Great find! Now there's not a single flaw with my phone .
For some weird reason, after installing Screen Filter, I was unable to install a third-party application downloaded from the Internet, the Install button froze. Then after uninstalling Screen Filter everything went back to normal...
Just in case someone else bumps into the same problem
lgtsanev said:
For some weird reason, after installing Screen Filter, I was unable to install a third-party application downloaded from the Internet, the Install button froze. Then after uninstalling Screen Filter everything went back to normal...
Just in case someone else bumps into the same problem
Click to expand...
Click to collapse
have had trouble sideloading apps too
I just reboot when it happens
fixed the last 3 times. Seems to happen every couple of days for whatever reason
Awesome thanks a lot .. works great
lgtsanev said:
For some weird reason, after installing Screen Filter, I was unable to install a third-party application downloaded from the Internet, the Install button froze. Then after uninstalling Screen Filter everything went back to normal...
Just in case someone else bumps into the same problem
Click to expand...
Click to collapse
Just pull down the taskbar and click on the screen filter icon to disable it , and your apps should install like normal .
I have tasker and I just downloaded secure settings. However I am confused by your instructions. How do I set this up? Do I create a profile if so what profile? What type of task do I assign that profile? Sorry to sound like a tasker newbie but I am. I saw your post purchased tasker and tried to set it up but there is no clear cut way.
Sent from my HTC_Amaze_4G using XDA App
cirrob said:
I have tasker and I just downloaded secure settings. However I am confused by your instructions. How do I set this up? Do I create a profile if so what profile? What type of task do I assign that profile? Sorry to sound like a tasker newbie but I am. I saw your post purchased tasker and tried to set it up but there is no clear cut way.
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
Create New Profile -> Softkeys Light
First Context -> Event -> Display -> Display ON
**The Task should pop up**
Add New -> Plugin -> Secure Setting -> Run Command ( from dropdown)
Use Root (Checked)
Command Name (backlight) or whateva
Command is
chmod 644 /sys/class/leds/button-backlight/brightness (make file writable for chanages
echo 1 > /sys/class/leds/button-backlight/brightness (turn softkeys backlight on)
sleep 10 (wait 10 seconds)
echo 0 > /sys/class/leds/button-backlight/brightness (turn softkeys backlight off)
chmod 444 /sys/class/leds/button-backlight/brightness (make readonly to prevent changes by system)
Thats it, you can tweak however you like, or tell it to stay off when a particular app is running in Fore Ground stuff like that
***You could add a second context to the first So when you are in a bright environment, it doesn't come on
Second Context -> State -> Sensor -> Light Level --- Range (0-15)
Thanks! I will try this when I get home today. I appreciate your detailed and patient response.
Sent from my HTC_Amaze_4G using XDA App
OK I think I did something wrong. I created the profile just fine and then created the task by cutting and pasting the text of your command in the run command field of secure settings. Hit apply and nothing has changed.
Am I missing a step?
Sent from my HTC_Amaze_4G using XDA App
The backstory first:
I have a Nexus 10. I like to plug it into my TV via HDMI and watch videos or play games, or what have you. Since the aspect ratio doesn't match the TV I get black bars on the sides. In a command line, one can type
Code:
am display-size 2560x1440
to change the resolution of the screen and get rid of the black bars on the TV completely (at the cost of adding black bars on the top and bottom of the tablet.)
Code:
am display-size reset
Sets it back to normal.
Rather than typing this into a terminal /every time/ I want to do this, is there a simple widget or app that will let me set up a shortcut on the homescreen that I can just click on to toggle instead?
There isn't a utility that does that, but i made one in dos for you. too lazy to upload, will give you the code.
Make a batch file by making a new file in notepad and saving it as a .bat extension for eg. filename.bat
inside the file, copy-paste this code :
Code:
@echo off
ECHO Please enter x for screen resolution of 2560x1440 and enter y to get back to default resolution
SET /P res=Please enter x or y:
IF "%res%"=="x" (
adb shell am display-size 2560x1440 ) ELSE (
adb shell am display-size reset )
ECHO Done!
Hit save!
if you want to set your resolution to 2560x1440 , type x and hit enter. if you want it set to normal hit y.
save this file and adb in the same folder.
I haven't tested it, so test it and tell me if it worked :good:
Lazz said:
The backstory first:
I have a Nexus 10. I like to plug it into my TV via HDMI and watch videos or play games, or what have you. Since the aspect ratio doesn't match the TV I get black bars on the sides. In a command line, one can type
Code:
am display-size 2560x1440
to change the resolution of the screen and get rid of the black bars on the TV completely (at the cost of adding black bars on the top and bottom of the tablet.)
Code:
am display-size reset
Sets it back to normal.
Rather than typing this into a terminal /every time/ I want to do this, is there a simple widget or app that will let me set up a shortcut on the homescreen that I can just click on to toggle instead?
Click to expand...
Click to collapse
For these kind of things:
Script Manager can create widgets from scripts.
TechMasta said:
There isn't a utility that does that, but i made one in dos for you. too lazy to upload, will give you the code.
Make a batch file by making a new file in notepad and saving it as a .bat extension for eg. filename.bat
I haven't tested it, so test it and tell me if it worked :good:
Click to expand...
Click to collapse
I never thought of using a batch file on a computer to do this. I have one hooked up near my TV, I could just plug the tablet in and set the batch file to a hotkey and it would be just as good as running from the tablet itself.
It seems "am" needs root permissions for some reason
It throws:
Code:
java.lang.SecurityException: Neither user 2000 nor current process has android.permission.WAKE_LOCK.
I tried to modify the code to get root access but then it gets stuck in adb shell. perhaps there is a way to run more than one shell command per line?
"am" does work from adb shell when it has root permission. This is strange since I don't need root permission from the terminal emulator on the tablet itself. Maybe there is something corny going on with my tablet.
Zatta said:
For these kind of things:
<URL> can create widgets from scripts.
Click to expand...
Click to collapse
This looks like it would work as well, except for some reason the Play Store says it isn't compatible. Perhaps I can download it on my phone, and then copy it to the Nexus 10.
Thank you both for your assistance!
We'll get this going somehow!
Hello,
This is my first post on the forum and I am relatively new to programming on Android so please forgive my ignorance.
I own a Samsung Galaxy S3 and am trying to write a shell script that will simulate screen presses in a very rapid fashion. To do so, I stumbled across the "input tap" function from /system/bin/input and my script looks like this:
Code:
x=1
while [ $x -lt 10 ]
do
input tap 640 110
(( x++ ))
done
Anyway, the code works great in that it will tap the screen at location 640,100. However, each call to "input tap" takes almost a second to return. My script takes around 10 seconds to complete. However, I was hoping to find a way to speed up the call to "input tap". I am not sure if this is a limitation of my phone. Any suggestions would be greatly appreciated.
Thanks!
You can speed it up by changing:
Code:
input tap 640 110
Into:
Code:
input tap 640 110 &
And if you must wait until all touch events have been sent before proceeding you can add this at the end of the loop:
Code:
wait
So the final result would be this:
Code:
x=1
while [ $x -lt 10 ]
do
input tap 640 110 &
(( x++ ))
done
wait
But I honestly don't understand why it takes so long for a touch event to be sent. This limitation makes it impossible to automate testing of applications that require low latency of user-based input.
Edit: I probably should have explained. When you add
Code:
&
at the end of a command, you are telling the shell to run it "in the background" so your script continues even though the tap command has not returned yet. When you type
Code:
wait
at the end, you are asking the shell to pause until all the commands that you spawned in another thread have returned.
It's time to post some of recipes I find useful. I drive for a living so operating my mobile gadgets HandsFree+EyesFree is how I have to do it.
[Rooted Watch + Rooted Phone Required ]
Most of these recipes incorporate the Autovoice App that uses Google App to grab spoken commands, HOWEVER, just switching out a variable in these recipes/tasks for your specific input will get the job done ... if you're interested in Autovoice off your watch the final pages of this thread are informative http://forum.xda-developers.com/xposed/modules/mod-google-search-api-t2554173 ... sadly though, it looks like no-one who has Marshmallow ON THEIR PHONE has a working flow at this time.
ANNOUNCEMENT: This new 5.0 version of wearshell comes included with some better versions of some recipes so far posted here by me, especially tts. here is the thread: http://forum.xda-developers.com/android-wear/development/app-wearshell-t2902242
FROM THAT THREAD:
WearShell version 0.6.0 has just been released.
I also put together some BeanShell commands for download:
https://goo.gl/2mA1uU
These commands are included:
Wearshell Command Collection 1
brightness
filepull
filepush
killws
mediaplayer
openuri
tts
unzip
vibrate
volume
WearShell Command Collection 2:
https://goo.gl/2mA1uU
battery
md5
notify
record
showimage
startapp
sysload
toast
uptime
zip
Wearshell Commands Collection 3
WearShell 0.6.0 has just been released. It includes support for Result Intents, sensors support and bug fixes.
alarm
charging
freestorage
heartrate*
light*
stepcount
stt
timer
wifioff*
wifion*
Commands marked with * I could not test because my G Watch is lacking the sensors and WiFi support. If you find any errors please let me know, I'll try to fix them.
Hope it's useful
...................
I'll leave this thread up and adding recipes, because these recipes usually don't require a file to be loaded onto the watch, they just run from an intent. so I can add things to the list and others too.
All I know is these work on my Huawei Watch with 1.4 update and Galaxy Note 3 on KK4.4.2. Please post recipes you find useful (and earn my undying gratitude) and I'll repost what I find and post ones I've made.
[Quick Summary on How These Work: Wearshell installs on phone and watch. the Wearshell app ON PHONE doesn't even need to be running to function because it sleeps until a tasker intent sent to it wakes it up, then Wearshell connects to it's companion app ON WATCH (companion app is tiny and uses like zero battery) and passes code to the companion app that it then executes the code. Wearshell is an awesome bridge to pass shell commands and java code via tasker]
Thanks and hopefully enjoy.
Reboot Watch By Voice
"Ok Google Reboot"
PROFILE: "i named it watch reboot"
Event> Plugin>Autovoice>Recognized> Command: "reboot"
TASK: "i named it watch reboot"
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c reboot");
LEAVE ALL OTHER FIELDS AS IS
Set Watch Brightness by Voice
"Ok Google Brightness xxx"
(xxx's are a number between 0 - 254 to set brightness level)
PROFILE: "i named it watch brightness"
Event> Plugin>Autovoice>Recognized> Command: "brightness" (then I speak a number between 0-254)
Advanced> Replacements:to =2,+=, =,:=,-=,one=1,two=2,three=3,four=4,five=5,six=6,seven=7, eight=8,nine=9,ten=10,eleven=11,twelve=12,thirteen =13,fourteen=14,fifteen=15,sixteen=16,seventeen=17 ,eighteen=18,nineteen=19,twenty=20
TASK: "i named it watch brightness"
Add Action> Variables> Variable Set
NAME
%spokenbrightness
TO
%avcommnofilter
Add Action>Task> If
CONDITION
%avcommnofilter > 254
Add Action> Variable> Variable Set
NAME
%spokenbrightness
TO
254
Add Action>Task>Endif
Add Action>Task> If
CONDITION
%avcommnofilter < 20
Add Action> Variable> Variable Set
NAME
%spokenbrightness
TO
20
Add Action>Task>Endif
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA:
bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness %spokenbrightness; su -c input keyevent 26");
LEAVE ALL OTHER FIELDS AS IS
Notes: you might have noticed that the second if condition prevents the watch from going below brightness level 20. also that "input keyevent 26" that you see there just simulate a power button click on my phone which clears the Google search results from the screen of my watch so that I have my watch face back when the task completes
Voice Search Results in UC Mini Browser on Watch (VERY fast+smooth over Bluetooth)
"Ok Google search lions tigers and bears"
[Instructions on easy installing UC Mini Browser after the recipe]
PROFILE: "i named it watch uc mini"
Event> Plugin>Autovoice>Recognized> Command: "search"
TASK: "i named it watch uc mini"
Add Action>Variable>Variable Set
NAME
%url2wearshell
TO
"https://www.google.com/search?site=&source=hp&q=%avcommnofilter"
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: import android.content.Intent; import android.net.Uri; uri = %url2wearshell; intent = new Intent(Intent.ACTION_VIEW, Uri.parse(uri)); intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK); context.startActivity(intent);
LEAVE ALL OTHER FIELDS AS IS
Install
grab "UC Mini Browser" from the playstore on your phone and use an app like "Apk Share" to get the apk, then on the watch go to developer options enable "adb debugging" and "adb over bluetooth," then use the app "Apps2Wear" from playstore to sideload it (it'll take a few tries, and make sure on the watch you clicked ok to allow connections over adb) ... then grab " /system/app mover root" from the play store and sideload it with "Apps2Wear" (it'll take a few tries) then run "/system/app mover root" on the watch to install "UC Mini Browser" as a system app (so that it gets permission to use the internet)...you might get a weird error saying it couldn't move UC Mini, but it moved 'enough of it' (the base apk) to get this working. So reboot for good measure and it'll be ready. (btw: because 'enough' of UC Mini got moved to system folder it won't survive a factory reset like a fully installed system app and will need a reinstall.)
Usage:
on my Huawei Watch there is no back button, so I recommend you open some links from the Google results 'in the background' (long press the links), then use the tabs button on the bottom bar to switch between pages (this speeds up browsing too). also I recommend you go to settings in UC Mini (bottom right corner on my watch and hard to click) and go to Customize and check "Hide Bottom Bar" = this gives you full screen without losing the bottom bar, it's great.
Text Messages Automatically Spoken On Your Watch (Watch TTS)
[ ** This recipe needs work to be good, but it's 'good enough' to allow me to keep my eyes on the road, and much better solutions are on the way I'm sure. Also, It requires a tiny tasker app to be made and sideloaded (it's only 5 easy actions to input)..]
The tasker app we'll make in this recipe is named "Watch Speak"
THE APP FACTORY APP::
TASK: "I named it watch Speak"
Add Action>File>Read File
FILE
/sdcard/speak.txt
TO
%watchspeak
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
€ (<--- don't type this, but see that weird symbol?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
' (<--- see that apostrophe?)
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
¥ (<--- don't type this, but see that weird symbol?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
" (<--- see that quote mark?)
Add Action> Alert>Say
TEXT
%watchspeak
LEAVE ALL OTHER FIELDS AS IS, UNLESS YOU WANT TO
CHANGE SPEED AND PITCH
Add Action>Task>Stop
IN TASKER:
PROFILE: "I named it Watch Speak"
Event> Phone>Received Text
TASK: "I named it Send Watch Speak"
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
text from, %SMSRN. it says, %SMSRB
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
' (<---don't route this, but see that apostrophe?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
€ (<--- don't type this, but see that weird symbol?)
Add Action>Variables>Variable Search and Replace
VARIABLE
%watchspeak
SEARCH
" (<---don't type this, but see that quote mark?)
STORE RESULTS IN
%watchspeak
REPLACE MATCHES
...check the box
REPLACE WITH
¥ (<--- don't type this, but see that weird symbol?)
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c echo '%watchspeak' >| /sdcard/speak.txt"); Runtime.getRuntime().exec("su -c monkey -p com.gmail.paulporter1.watchspeak -c android.intent.category.LAUNCHER 1");
LEAVE ALL OTHER FIELDS AS IS
Add Action>Task>Stop
NOTES:
(a) the weird symbols ¥ and € in search and replace are because I do not know how to transfer the symbols ' and " from a variable into linux commands that are embedded in java code, because ' and " will break a command that is supposed to put text into a file, that file being the /sdcard/speak.txt file that our tasker app on the watch reads from, but without those symbols tts can't speak words correctly, so we switch them then switch them back.
(b) on my Huawei Watch the texts won't read out loud if you are actively using the watch (which I like actually) but you might get a duplicate reading once the watch goes idle.
Voice Command Your Watch To Read Last Text Message
PROFILE: "i named it repeat message"
Event> Plugin>Autovoice>Recognized> Command: "repeat message"
TASK:
(just use/reuse the task from the previous post, the task that resides on the phone)
Automate theater mode
This is a repost originally posted by ShadowEO.
In the task, add a Send Intent action with these parameters:
On:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
Off:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");
Off will turn off theater mode, however still leave the watch screen off, however the screen will come back on with the next tap and theater mode will be off.
Notifications Automatically Spoken On Your Watch (Watch TTS
Use/Reuse the same recipe from a few posts back for speaking text messages, but just change these lines:
From this:
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
text from, %SMSRN. it says, %SMSRB
to this:
Add Action>Variables>Variable Set
NAME
%watchSpeak
TO
notification, %NTITLE
Change LCD Density By Voice
"Ok Google density xxx"
(where. xxx is a number I speak between 180-340)
PROFILE: "i named it watch density"
Event> Plugin>Autovoice>Recognized> Command: "density" (then I speak a number between 180-340)
Advanced> Replacements: to =2,+=, =,:=,-=,one=1,two=2,three=3,four=4,five=5,six=6,seven=7,eight=8,nine=9,ten=10,eleven=11,twelve=12,thirteen=13,fourteen=14,fifteen=15,sixteen=16,seventeen=17,eighteen=18,nineteen=19,twenty=20
TASK: "i named it watch density"
Add Action> Variables> Variable Set
NAME
%spokendensity
TO
%avcommnofilter
Add Action>Task> If
CONDITION
%avcommnofilter > 340
Add Action> Variable> Variable Set
NAME
%spokendensity
TO
340
Add Action>Task>Endif
Add Action>Task> If
CONDITION
%avcommnofilter < 180
Add Action> Variable> Variable Set
NAME
%spokendensity
TO
180
Add Action>Task>Endif
Add Action> System>Send Intent
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA:
bsh: Runtime.getRuntime().exec("su -c wm density %spokendensity; su -c input keyevent 26");
LEAVE ALL OTHER FIELDS AS IS
Pablo, tonight i want test all. Its wonderful.
I m curious how work speaker tts! Are there delay with this method?
Inviato dal mio SM-N9005 utilizzando Tapatalk
vingar said:
Pablo, tonight i want test all. Its wonderful.
I m curious how work speaker tts! Are there delay with this method?
Click to expand...
Click to collapse
you rock man, good luck. the watch will vibrate then 7-10 seconds later it talks. (the watch reads out emojis too, like ??? makes it say 'smiley face ring penguin) ... android is cool
pablo71 said:
you rock man, good luck. the watch will vibrate then 7-10 seconds later it talks. (the watch reads out emojis too, like ??? makes it say 'smiley face ring penguin) ... android is cool
Click to expand...
Click to collapse
Pablo you have a PM!
Any alternative for nonrooted phones? Don't want to root my new s7 edge yet... I miss the simple root and warranty from the nexus :/
Sent from my SM-G935F using XDA-Developers mobile app
[email protected] said:
Any alternative for nonrooted phones? Don't want to root my new s7 edge yet... I miss the simple root and warranty from the nexus :/
Click to expand...
Click to collapse
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.
pablo71 said:
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.
Click to expand...
Click to collapse
Thanks! I would simply use Adb reboot bootloader as usual on my nexus 4 and 7.
But saw the root needed disclaimer in your first post.
Sent from my SM-G935F using XDA-Developers mobile app
pablo71 said:
most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine, and I don't think root is needed for any of that. just use your watches button combination to reboot into bootloader, then select recover mode, connect cable to your computer and use adb commands to sideload apps. there are some good threads in Android Wear section that I've been using to do stuff.
Click to expand...
Click to collapse
So this part of your statement: "most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine"
I've been adding profiles in Tasker on my phone with WearShell installed and they are not working on my watch, I really wanted the brightness changes to be triggered by connect and disconnect from my home wifi network. I guess now I understand why the tasks don't work, since I have not sideloaded them into my watch. I also tried the automate theater mode that fails as well,
I totally missed the fact that they need to be exported as apps and sideloaded into the watch via adb. I missed that in this thread and the WearShell thread. Gah!
Pkt_Lnt said:
So this part of your statement: "most of the tasker tasks I've exported as apps/apks and sideloaded onto my watch work just fine"
I've been adding profiles in Tasker on my phone with WearShell installed and they are not working on my watch, I really wanted the brightness changes to be triggered by connect and disconnect from my home wifi network. I guess now I understand why the tasks don't work, since I have not sideloaded them into my watch. I also tried the automate theater mode that fails as well,
I totally missed the fact that they need to be exported as apps and sideloaded into the watch via adb. I missed that in this thread and the WearShell thread. Gah!
Click to expand...
Click to collapse
no no, I didn't explain myself very well in the previous post ... these recipes I've posted are not apks to sideload ... what I was referring to in the previous post is a few little Tasker apks I've side-loaded onto my watch, but I did not include those in this thread because this thread was for recipes that included wearshell ... pardon me for not communicating clearly in the previous post. If you wouldn't mind copying and pasting the intents in Tasker that are being sent to wearshell I would like to see them
this would set brightness to full, the number 254 does that in this intent
SEND INTENT
ACTION
de.fun2code.android.wear.shell.EXEC
EXTRA
bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254");
LEAVE ALL OTHER FIELDS AS IS
pablo71 said:
no no, I didn't explain myself very well in the previous post ... these recipes I've posted are not apks to sideload ... what I was referring to in the previous post is a few little Tasker apks I've side-loaded onto my watch, but I did not include those in this thread because this thread was for recipes that included wearshell ... pardon me for not communicating clearly in the previous post. If you wouldn't mind copying and pasting the intents in Tasker that are being sent to wearshell I would like to see them
Click to expand...
Click to collapse
Brightness:
Wifi disconnect (this actually has about 15 steps for various changes to the phone for sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254 ");
Wifi connect (same, changes to sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106 ");
I have also tried removing the space after the number and before the quote, since other bsh: entries I have seen don't show the space.
Code:
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106");
Theater:
Start sleep tracking (Sleep as Android works as a plugin with Tasker, I set silent mode and try to start theater)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
End sleep tracking when alarm sounds (again, Sleep as Android as a plugin for Tasker allows the sleep tracking to terminate on alarm and run an intent)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");
Pkt_Lnt said:
Brightness:
Wifi disconnect (this actually has about 15 steps for various changes to the phone for sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 254 ");
Wifi connect (same, changes to sound and security)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106 ");
I have also tried removing the space after the number and before the quote, since other bsh: entries I have seen don't show the space.
Code:
Extra: bsh: Runtime.getRuntime().exec("su -c settings put system screen_brightness 106");
Theater:
Start sleep tracking (Sleep as Android works as a plugin with Tasker, I set silent mode and try to start theater)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 1");
End sleep tracking when alarm sounds (again, Sleep as Android as a plugin for Tasker allows the sleep tracking to terminate on alarm and run an intent)
Code:
Action: de.fun2code.android.wear.shell.EXEC
Extra: bsh: Runtime.getRuntime().exec("su -c settings put global theater_mode_on 0");
Click to expand...
Click to collapse
I assume that all the other fields in this Send Intent action are left as is, so these intents are written perfectly. Now, the things that I'm about to say next are probably things you already know, but Tasker is extremely finicky with profiles, especially cloned profiles, and you have to back out of Tasker completely using the back button to activate profiles. Sometimes I have to delete profiles that should be working, and then recreate them. Once I do that they work flawlessly forever. Sometimes I have to turn the profiles on and off as well. Also I am pretty sure you are using the latest version of wearshell, because I read in that Forum that the previous version of wearshell did not work with the screen off on the phone. Hopefully the wearshell companion app is in memory on the watch so that it can receive communication from the app on the phone. You could try opening the app on the phone and starting and stopping at the server just to wake the it up and testing to see if they are running.. That server, by the way, is not part of any of this, you probably already know that the server is just to run test code through a web server interface that is on the watch. But running that server would be a great way to check that the companion app and the phone app are both operating and talking to each other.
EDIT: In tasker, is 'allow external access' granted in the settings? I'm not that great at tasker, but I think something like that in settings could be it maybe
pablo71 said:
I assume that all the other fields in this Send Intent action are left as is, so these intents are written perfectly. Now, the things that I'm about to say next are probably things you already know, but Tasker is extremely finicky with profiles, especially cloned profiles, and you have to back out of Tasker completely using the back button to activate profiles. Sometimes I have to delete profiles that should be working, and then recreate them. Once I do that they work flawlessly forever. Sometimes I have to turn the profiles on and off as well. Also I am pretty sure you are using the latest version of wearshell, because I read in that Forum that the previous version of wearshell did not work with the screen off on the phone. Hopefully the wearshell companion app is in memory on the watch so that it can receive communication from the app on the phone. You could try opening the app on the phone and starting and stopping at the server just to wake the it up and testing to see if they are running.. That server, by the way, is not part of any of this, you probably already know that the server is just to run test code through a web server interface that is on the watch. But running that server would be a great way to check that the companion app and the phone app are both operating and talking to each other
Click to expand...
Click to collapse
Yes, I know the idiosyncrasies of Tasker, I've been beta testing for a couple years, and if you saw the complexity of my myriad tasks.....
When I have the WearShell running, I get a screen wakelock that keeps the display on. I don't have it running because joschi70 in the WearShell thread stated (in response to you) it does not have to run for broadcasts .I have tried running it and still nothing changes on the watch.
Actually the server is only needed if you use the web API or the web interface itself.
If you use broadcasts to send commands it should work without having to start the WearShell server on the phone.
Click to expand...
Click to collapse
I did see the message on the watch that WearShell was installed. Of course, it does not show in the apps menu.
Hi everyone,
I recently noticed the green indicator lighting up when I use my phone, indicating that the microphone or camera is being accessed.
How can I disable that function, it is a bit irriating as it keeps popping on when I use the phone?
Many thanks
Andy
and_novice said:
Hi everyone,
I recently noticed the green indicator lighting up when I use my phone, indicating that the microphone or camera is being accessed.
How can I disable that function, it is a bit irriating as it keeps popping on when I use the phone?
Many thanks
Andy
Click to expand...
Click to collapse
It's an integral privacy feature of Android 12. It may be possible to disable it using a Magisk module, but I don't know of a specific module that might do it, nor would I ever want to in the interests of privacy.
I have the solution!
Activate the developer option on the phone. Enable USB debugging.
Install platform tools on the PC.
Connect cell phone to PC.
Start command prompt with platform-tools. E.g. C:\platform-tools>
then type in ADB DEVICES and confirm on the phone.
The phone should now appear in the list.
Now copy and paste the following line
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled false default
and confirm with Enter.
From now on there is no longer a green dot when using the camera and microphone.
Restore the green dot with
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled true default
Dennis9 said:
I have the solution!
Activate the developer option on the phone. Enable USB debugging.
Install platform tools on the PC.
Connect cell phone to PC.
Start command prompt with platform-tools. E.g. C:\platform-tools>
then type in ADB DEVICES and confirm on the phone.
The phone should now appear in the list.
Now copy and paste the following line
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled false default
and confirm with Enter.
From now on there is no longer a green dot when using the camera and microphone.
Restore the green dot with
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled true default
Click to expand...
Click to collapse
This works great. However, if you reboot the device, the annoying icon is back. Do you know of a more permanent solution? Thanks!
+1 want/search a permanent solution for the location icon
I would like to know how to make those changes persistent, too.
I tried the method, worked once, but next time when I tried to use the front camera to record a video, although it showed no green dot, the video wasnt catched! only voices.... anyone knows how to resolve it? thx
Hummm... doesn't work for me.
adb shell
cmd device_config put privacy camera_mic_icons_enabled false default
I still see annoying green dot when opening camera (not horrible, but prefer not to have it).
I still see annoying green dot flashing on and off randomly all the time due to some background location (ie: sharing my GMaps location with my wife).
That drives me frickin insane to be trying to use my phone and have that damn green thing keep showing a location bubble, then a green dot, then nothing, then the location bubble again and so on all the frickin time. Who wants that? You can't even click it to see what is getting your location and disable it. It is totally useless.
Has anyone found a fix (that both works and survives reboots)?
rpmccormick said:
Hummm... doesn't work for me.
adb shell
cmd device_config put privacy camera_mic_icons_enabled false default
I still see annoying green dot when opening camera (not horrible, but prefer not to have it).
I still see annoying green dot flashing on and off randomly all the time due to some background location (ie: sharing my GMaps location with my wife).
That drives me frickin insane to be trying to use my phone and have that damn green thing keep showing a location bubble, then a green dot, then nothing, then the location bubble again and so on all the frickin time. Who wants that? You can't even click it to see what is getting your location and disable it. It is totally useless.
Has anyone found a fix (that both works and survives reboots)?
Click to expand...
Click to collapse
I found a solution. But it needs Tasker and root. If interested let me know. I'm using it on custom rom
I found that I have a slider in Developer Options to turn on/off the location one which is the one that is truly annoying. The issue is that even if I turn it off, it comes back on by itself (always after a reboot, but randomly when I have not rebooted in a few days as well).
I have root and Tasker, though I never use Tasker and find it a bit annoying in my notifications area. I would be interested in your solution though. I wish the dev-opts switch just held so I didn't get the location one all the time. The camera/mic is not so bad (though completely unnecessary useless feature that has never helped anyone identify a bad-actor app and never will)
Task: Disable Green Dot
A1: Run Shell [
Command: cmd device_config put privacy location_indicators_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
This is the task.
Create a profile with Event - Device Boot and assign this task. I only use it since a few days, but it works so far.
After a reboot the green indicator will appear for s few seconds until Tasker sets in.
Using Tasker as XtraWater suggested and the following command:
cmd device_config put privacy camera_mic_icons_enabled false default
I was able to create a task to disable the camera's green dot. But, it only works 1/2 the time after a reboot. And when it does not work after boot up then running the task manually also does not get rid of the green dot. I'm using a rooted Pixel 6 on Android 13. I copied the other settings as well: timeout: 0, root: on, global namespace: on.
This is the first time I've ever used Tasker and I'm fairly new to rooting phones but what gets me is that it works about 1/2 of the time. Maybe a timing issue during boot up?
Any ideas??? This is driving me crazy.
It appears the Tasker job isn't doing anything actually. I disabled it and rebooted the phone a few times and it seems sometimes it shows the dot and sometimes it doesn't.
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Thank you, the module just worked fine...
Jackson Karloff said:
Thank you, the module just worked fine...
Click to expand...
Click to collapse
Not working for me on
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Not working for me on S20 with latest magisk on Android 13. Is there an updated version for this?
Hi.
Please help me.
I didn't understand how to make the command final. I tried to enter the command "cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default"
but it gives me error. how can I do? thank you
Hey, really thanks man. It worked for me fine.
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Hello.
This work but after some times again show green dot can you please check this ?
Redmi 10 note ver 12
Hello, I found an XPosed module called Location Indicator Whitelist. Despite the name, it can disable indicator for microphone and camera in addition to location. Instead of totally disabling indicator, it disables indicator for selected application.