Related
Hey,
I'm trying to use NFC with URL task launcher on my n4, but whenever I tap a tag that i've written to, a pop up comes up that says "new tag collected" and it shows the url i've written and I can click it and it will run the task, but it doesnt just open up the task right away...If i write a normal url to the tag, such as youtube.com, it automatically goes to the browser and opens the page. I am looking to be able to tap a tag and have tasker run the task without me having to click the pop up on the screen. anyone else having the same issue?
N4 running PA 3.
post in wrong topic. Sorry guys
bummppp?
On the Galaxy S3, that issue was resolved by by going into the Application Manager and "disabling" an app called "Tags" which seems to be an Android system app of some kind. It didn't have any negative results on being able to read/write tags with other apps.
Not sure if it'll be the same on the Nexus 4, but worth a shot...
hollywoodfrodo said:
On the Galaxy S3, that issue was resolved by by going into the Application Manager and "disabling" an app called "Tags" which seems to be an Android system app of some kind. It didn't have any negative results on being able to read/write tags with other apps.
Not sure if it'll be the same on the Nexus 4, but worth a shot...
Click to expand...
Click to collapse
I've tried this on my N4, and it isn't working. Normal URLs will launch, but the tasker://task URLs just make the NFC tag read sound, and nothing happens.
I'm in the same boat. And now a strange thing: I tried the official Samsung TecTiles app and according to NFC TagReader it also writes a stupid URI to the NFC tag in the form: tectiles://www.samsung.com/tectiles - and THAT one works! It directly calls the defined task without showing the "New tag collected" screen or prompting for an app to use the NFC data with. Why is that?
Took me a long time to solve but this is what needed to be done in order for the app to work with Tasker on my Nexus 4.
Go into tasker, open the setting menu by tapping the icon in the upper right of the main screen. Select “preferences”. Select the “MISC” tab and turn on “Allow External Access”. Exit this window by tapping the icon in the upper left and exit Tasker.
I set up the WatchOn app to control my devices. I can control them individually just fine. However, what I'd like is to hit a button for an activity, say watching a movie, and it automatically turns on the TV, sets its input to DVD, turns on my receiver, sets its input to DVD, and turns on the Blu Ray player.
Is this something this app does? If so, where do you access this? If not, why does it ask you for all the inputs on your TV and receiver?
DLarva said:
I set up the WatchOn app to control my devices. I can control them individually just fine. However, what I'd like is to hit a button for an activity, say watching a movie, and it automatically turns on the TV, sets its input to DVD, turns on my receiver, sets its input to DVD, and turns on the Blu Ray player.
Is this something this app does? If so, where do you access this? If not, why does it ask you for all the inputs on your TV and receiver?
Click to expand...
Click to collapse
Do you actually have a remote control that does all that with the press of one button? Cause I never seen one. I don't think that's possible with the phones WatchOn.
Reinaldo33897 said:
Do you actually have a remote control that does all that with the press of one button? Cause I never seen one. I don't think that's possible with the phones WatchOn.
Click to expand...
Click to collapse
Yes, I do. It is a logitech harmony.
The reason why I thought it might is because WatchOn has you set the input types on your TV and receiver. If you have to turn each component on manually, then it has no idea what input you want the TV on, so you have to set that manually as well, so why ask for the input.
If it can't do this, it doesn't seem like much of a stretch of the imagination to add a "Watch TV" button which just runs through a step of button presses for you.
I dont know I think watchon is a joke. Samsungs way of saying hey I can turn your components on and off lol. But see if you can hit play on the blueray and it should put tv in blueray input. But then I think yoy manually have to get it back to tv mode.
I think its a nice app if you want to search for tv shows but really worthless to operate the whole system.
Sent from my SAMSUNG-SGH-I337 using xda premium
Well 1 somewhat long way to do it is using the "Tasker" app. It can emulate virtual screen taps and bunch of other stuff.
Create a task from tasks tab.
Add Action -> App -> Load App -> WatchOn
Add Action -> Task -> Wait and set it to wait a few seconds for the app to load.
Add Action -> Script -> Run Shell and for command enter in "sleep 0.1; input tap 564 1856" where numbers are X,Y of your screen you want tapped.
- sleep X seconds is same as adding wait action. so you can change to whatever duration you want
- To determine X,Y values go in Settings->More ->Developer Options -> check Show Pointer Location.
- If its not there, to unlock the Dev Options menu, go to Settings -> About Device and scroll down to the "Build Number." Tap on your "Build Number" 7 times.
Keep adding actions for tapping all the WatchOn buttons you need (switch to remote view, load the correct room/tv etc).
Then just throw a tasker widget on ur screen and you have ur 1 button that auto does everything you want; after like 10 secs of running lol, sadly not instant.
PM me if you want to try this and need help
Hi I just got a Nexus 6p and its been great but I have low vision and if I keep the option turned on the phone, it becomes very laggy so I would like to only use it when I need to.
Help would be greatly appreciated!
Thank you .
This isn't exactly what you wanted, but it's kind of close...
I use ADW as my launcher, which allows me to set custom shortcuts on my home screen. Other launchers might offer the same functionality.
I long pressed on my home screen and selected the Add tab on the popup. I then tapped Custom Shortcut, and tapped "Pick your activity." Next, I tapped Activities, scrolled down to Settings and expanded the list. It's rather long, but in that list there is one called "Accessibility(.Settings$AccessibilitySettingsActivity)". I selected that one, gave it a name (what it displays under the icon), and pressed OK. This created a settings gear icon on my home screen that when tapped goes straight to the accessibility options in the settings menu, and then you can tap the toggle for Magnification.
Alternatively, you should be able to do the same thing with Tasker if you have it installed and it's a bit easier. Make a new Task, give it a title (anything) and press the plus to add a step. Select Settings, then Accessibility settings (first option). There is some "if" options, but you can just tap your back button to go back to the step list. Create a widget for Tasker (1x1 task) and select the name of the task you just created. You then need to select an icon for the "widget" by tapping the icon in the lower right that looks like 9 squares in a grid. There are a bunch of built in icons you can choose from, or use your own. The result will be an icon on your desktop that goes to the accessibility options screen, allowing you to quickly toggle the magnification gesture.
Again, sorry this isn't exactly what you asked for, but it would save some taps. Luckily the mag gesture toggle is high enough in the list of options that it should always be on the screen when you open the accessibility settings, so you won't need to scroll.
Lastly, if you are rooted, you could use Tasker to also hit the toggle for you. If you want instructions for that, please do let me know and I'd be happy to share how to do that. It would allow you to tap the "widget" and it would then launch the accessibility settings, wait a second and then tap the toggle, and go back to the home screen. That way you wouldn't need to toggle it yourself.
fury683 said:
This isn't exactly what you wanted, but it's kind of close...
I use ADW as my launcher, which allows me to set custom shortcuts on my home screen. Other launchers might offer the same functionality.
I long pressed on my home screen and selected the Add tab on the popup. I then tapped Custom Shortcut, and tapped "Pick your activity." Next, I tapped Activities, scrolled down to Settings and expanded the list. It's rather long, but in that list there is one called "Accessibility(.Settings$AccessibilitySettingsActivity)". I selected that one, gave it a name (what it displays under the icon), and pressed OK. This created a settings gear icon on my home screen that when tapped goes straight to the accessibility options in the settings menu, and then you can tap the toggle for Magnification.
Alternatively, you should be able to do the same thing with Tasker if you have it installed and it's a bit easier. Make a new Task, give it a title (anything) and press the plus to add a step. Select Settings, then Accessibility settings (first option). There is some "if" options, but you can just tap your back button to go back to the step list. Create a widget for Tasker (1x1 task) and select the name of the task you just created. You then need to select an icon for the "widget" by tapping the icon in the lower right that looks like 9 squares in a grid. There are a bunch of built in icons you can choose from, or use your own. The result will be an icon on your desktop that goes to the accessibility options screen, allowing you to quickly toggle the magnification gesture.
Again, sorry this isn't exactly what you asked for, but it would save some taps. Luckily the mag gesture toggle is high enough in the list of options that it should always be on the screen when you open the accessibility settings, so you won't need to scroll.
Lastly, if you are rooted, you could use Tasker to also hit the toggle for you. If you want instructions for that, please do let me know and I'd be happy to share how to do that. It would allow you to tap the "widget" and it would then launch the accessibility settings, wait a second and then tap the toggle, and go back to the home screen. That way you wouldn't need to toggle it yourself.
Click to expand...
Click to collapse
Thanks a lot!
So it sounds like theres no way to make a widget the will toggle it specifically, without rooting my device.
And if I do root it and use Tasker it will take almost the same time as if I didn't.
If thats no other way then I guess I should root it even though Id prefer not too.
Unless theres another way, Instructions would be great! Thanks again!
Are you familiar with Tasker? It's a paid app, but it's absolutely worth it and you'll find lots of uses for it. I use it to auto reply to text messages while I'm driving, mute my phone when I'm at work (calendar based) turn on wifi when I'm at home (location based), etc.
First thing you need to do is find the location of the toggle on the screen. Go to Developer Settings and turn on "Show Pointer Location". This will make a gray bar at the top of your screen that lists your X and Y coordinates at the top when you are touching the screen. Go to the accessibility settings and touch the toggle, taking note of what the X and Y coordinates are for that touch input.
To simulate touch input, can make a task that opens the accessibility settings as I described above, then add a "wait" command (Task > Wait), enter a value of 1 second. Next enter a command for Code and select Run Shell. Under the command, type "input tap x y" where x and y are the x and y coordinates that you found for the toggle. Make sure the "use root" box is checked. Lastly, add a Tasker command to go to the home screen (back to where you started with the "widget").
Back all the way out of Tasker to save that task, then go back in and press the play button at the bottom left side to test your setup. You should see it launch the accessibility settings, wait a second, toggle, and go home. The first time you run it you will need to grant Tasker root permissions, so be ready for that. If you're not quick to approve it, the task may proceed and go to your home screen before you press approve, so you might need to run it again a second time after you approve it.
If you need more help with, or have any questions, please do let me know. Happy to help.
fury683 said:
Are you familiar with Tasker? It's a paid app, but it's absolutely worth it and you'll find lots of uses for it. I use it to auto reply to text messages while I'm driving, mute my phone when I'm at work (calendar based) turn on wifi when I'm at home (location based), etc.
First thing you need to do is find the location of the toggle on the screen. Go to Developer Settings and turn on "Show Pointer Location". This will make a gray bar at the top of your screen that lists your X and Y coordinates at the top when you are touching the screen. Go to the accessibility settings and touch the toggle, taking note of what the X and Y coordinates are for that touch input.
To simulate touch input, can make a task that opens the accessibility settings as I described above, then add a "wait" command (Task > Wait), enter a value of 1 second. Next enter a command for Code and select Run Shell. Under the command, type "input tap x y" where x and y are the x and y coordinates that you found for the toggle. Make sure the "use root" box is checked. Lastly, add a Tasker command to go to the home screen (back to where you started with the "widget").
Back all the way out of Tasker to save that task, then go back in and press the play button at the bottom left side to test your setup. You should see it launch the accessibility settings, wait a second, toggle, and go home. The first time you run it you will need to grant Tasker root permissions, so be ready for that. If you're not quick to approve it, the task may proceed and go to your home screen before you press approve, so you might need to run it again a second time after you approve it.
If you need more help with, or have any questions, please do let me know. Happy to help.
Click to expand...
Click to collapse
I just realized I need to buy an adapter for that USB C lol.
Before I go ahead with all of this work, your completely sure there is no other way to toggle magnification without rooting?
Thanks!
drewtass said:
I just realized I need to buy an adapter for that USB C lol.
Before I go ahead with all of this work, your completely sure there is no other way to toggle magnification without rooting?
Thanks!
Click to expand...
Click to collapse
Sorry for the delay. I am not aware of any widgets. I couldn't find a widget on the Play Store or light Google searching.
Regarding the adapter, the 6p should have come with a short USB A to USB C cable specifically for connecting to a PC.
drewtass said:
Hi I just got a Nexus 6p and its been great but I have low vision and if I keep the option turned on the phone, it becomes very laggy so I would like to only use it when I need to.
Help would be greatly appreciated!
Thank you .
Click to expand...
Click to collapse
Have you used the built in magnification gesture? You turn it on in accessibility settings, then when you need something to be bigger, just tap the screen 3 times rapidly. You can use pinch to zoom to adjust the text size. When you're finished with it, tap the screen 3 times again. I use it when an app's text is just too small.
EMcTx said:
Have you used the built in magnification gesture? You turn it on in accessibility settings, then when you need something to be bigger, just tap the screen 3 times rapidly. You can use pinch to zoom to adjust the text size. When you're finished with it, tap the screen 3 times again. I use it when an app's text is just too small.
Click to expand...
Click to collapse
Haha Yes I have tried it you have to tap your finger 3 times to magnify which means every time you tap something once it waits to see if you will tap more times and cause slight lag.
Niceeee idea bro, i will try it
moqueet said:
Niceeee idea bro, i will try it
Click to expand...
Click to collapse
Are you saying you will try to make a widget like this?
fury683 said:
Sorry for the delay. I am not aware of any widgets. I couldn't find a widget on the Play Store or light Google searching.
Regarding the adapter, the 6p should have come with a short USB A to USB C cable specifically for connecting to a PC.
Click to expand...
Click to collapse
No problem!
Lol I was so excited for my new phone I never checked but I found it !
Thanks I will root it when I get the chance.
i have the same exact problem,i absolutely love the feature as i wouldn't be able to use any phone with out it but it also gets frustrating sometimes (the touch delay) for example in the dialer app or Instagram.
a toggle in the notification panel would be great or an app through which you specifically enable/disable the gestures for each individual app.
any other alternative would be appreciated, somebody posted the same issue here with a possible fix (which i am not exactly sure how to implement) https://code.google.com/p/android/issues/detail?id=39685
hassanabid94 said:
i have the same exact problem,i absolutely love the feature as i wouldn't be able to use any phone with out it but it also gets frustrating sometimes (the touch delay) for example in the dialer app or Instagram.
a toggle in the notification panel would be great or an app through which you specifically enable/disable the gestures for each individual app.
any other alternative would be appreciated, somebody posted the same issue here with a possible fix (which i am not exactly sure how to implement) https://code.google.com/p/android/issues/detail?id=39685
Click to expand...
Click to collapse
Nice to know I'm not the only one.
Sorry for the late reply been busy with school. It would be nice to have this option maybe like a button shortcut .
Hey guys so that way of using tasker is very slow and not feasible.
Is there any other way of making a quick toggle magnification gestures. It would be nice if I could hold the menu button to enable it. (IPhone tripple tap home button to toggle)
Thanks again.
I have low vision as well and have also found that leaving the magnification gesture turned on causes the phone to be laggy even when I don't actually have the magnification turned on. Instead of using that, I rooted my phone, changed the global DPI and I use App Settings (an Xposed module) to increase the font size in some apps or force the standard DPI in apps that have issues with the custom one.
There's a gestural workaround I've employed: if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears. Doing this helps a lot but obviously its a bit of an awkward gesture.
Al--g said:
There's a gestural workaround I've employed: if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears. Doing this helps a lot but obviously its a bit of an awkward gesture.
Click to expand...
Click to collapse
How did you set it up?
There's no set up. I just do that gesture to get the scrolling to stop when I have magnification enabled.
GuinnessX said:
How did you set it up?
Click to expand...
Click to collapse
Hey Guys,
i have a general question. Is there a mod or. APK where i can define a point/dot on my Touchscreen and map it to a Hardware Button of the car (e.g. Steering wheel Buttons)?
What i want to Do is, to control the Touchscreen without touching. Seems funny but would be perfect, cause id like the steering wheel buttons.
I am using Android Auto with HeadUnit Reloaded, and switching through music with my Buttons works perfectly. Now it would be awesome to launch Google Assistant through a Button. Inside HUR isnt the Option to map the Assistant. And in my Hal9K mood i tried several Things.
So i thought, i am. 90% Inside Android Auto and the G Assistant Touch Icon is in bottom right corner. So i need a App that points on that Display location and simulate a Touch press, when i press the steering wheel. Is that possible?
Thanks for your time and help
Best wishes
R. Schulz
Waffel57 said:
Hey Guys,
i have a general question. Is there a mod or. APK where i can define a point/dot on my Touchscreen and map it to a Hardware Button of the car (e.g. Steering wheel Buttons)?
What i want to Do is, to control the Touchscreen without touching. Seems funny but would be perfect, cause id like the steering wheel buttons.
I am using Android Auto with HeadUnit Reloaded, and switching through music with my Buttons works perfectly. Now it would be awesome to launch Google Assistant through a Button. Inside HUR isnt the Option to map the Assistant. And in my Hal9K mood i tried several Things.
So i thought, i am. 90% Inside Android Auto and the G Assistant Touch Icon is in bottom right corner. So i need a App that points on that Display location and simulate a Touch press, when i press the steering wheel. Is that possible?
Thanks for your time and help
Best wishes
R. Schulz
Click to expand...
Click to collapse
That is a great idea! There is a way to send touches on the screen. You can do it via command line, e.g. :
input tap 560 960
You can also send key events the same way:
input keyevent KEYCODE_WAKEUP
You can browse in internet for the whole list. To determine the coordinates you can enable debug mode, and there is an option that is called INPUT -> pointer location.
This will display the coordinates on the screen whether you put your finger on.
Now, to map hardware buttons I think there are a couple of applications that let you do that. You can also map the hardware button to the key M to start the assistant. If I remember properly that is the hot key from HUR to start the microphone.
Let me know how it goes, I am also interested!
EDIT: Yet another way is to trigger an intent from the HUR app:
am start -a gb.xxy.hr.mic
There are several apps that let you start intents like tasker.
Am application to map the buttons without requiring root is Button Mapper.
Sent from my ONEPLUS A3003 using Tapatalk
Fgarcor said:
That is a great idea! There is a way to send touches on the screen. You can do it via command line, e.g. :
input tap 560 960
You can also send key events the same way:
input keyevent KEYCODE_WAKEUP
You can browse in internet for the whole list. To determine the coordinates you can enable debug mode, and there is an option that is called INPUT -> pointer location.
This will display the coordinates on the screen whether you put your finger on.
Now, to map hardware buttons I think there are a couple of applications that let you do that. You can also map the hardware button to the key M to start the assistant. If I remember properly that is the hot key from HUR to start the microphone.
Let me know how it goes, I am also interested!
EDIT: Yet another way is to trigger an intent from the HUR app:
am start -a gb.xxy.hr.mic
There are several apps that let you start intents like tasker.
Am application to map the buttons without requiring root is Button Mapper.
Click to expand...
Click to collapse
Thanks for that informative and interesting answer. Thats a lot of input for me. I will try some of this stuff in the next days and let you know if it works and whats the best solution for me
Waffel57 said:
Thanks for that informative and interesting answer. Thats a lot of input for me. I will try some of this stuff in the next days and let you know if it works and whats the best solution for me
Click to expand...
Click to collapse
The other day while driving I suddenly had a question. Why cannot you use the voice activated trigger! Ok Google, to start the voice commands? That way you don't need to press the voice button.
Sent from my ONEPLUS A3003 using Tapatalk
Toggeling with voice is Okey but often i have to scream or turn volume down. Or say it multiple Times. So a key is much more comfortable to me. My Touchscreen is Not perfectly reachable during driving so steering wheel buttons would be the perfect solution for me ?
Hey Fgarcor,
I had some time so investigate the problem. What i have done so far:
Mapping all my Hardware Keys to specific keycodes:
-Google Assisstant - - > 289
-Start Route - - > 288
-Switch Spotify - - > 291
-See Notifications - - > 292
-Route Option A - - > 283
-Route Option B - - > 284
-Route Option C - - > 285
So thats all "Events" i need for android auto. Then i went into debug Mode an locate the coordinates for each section:
-Google Assisstant - - > 925 x 556 y
-Start Route - - > 224 x 450 y
- Switch Spotify - - > 215 x 550 y
- See Notifications - - > 791 x 562 y
- Route Option A - - > 260 x 175 y
- Route Option B - - > 260 x 275 y
- Route Option C - - > 260 x 375 y
So i have all Information that i needed an just have to merged them but i dont know where can i define specific commands. I tried "Button Remapper Pro" but the APK does Not detect my keycodes.
Where can i Set up some command lines? Do i have to install a specific Module in Magisk Manager? Or is there Kind of a console on my rooted Android Radio?
Sorry, i dont understand it for 100% and need your help, Thanks
Best wishes
René
Waffel57 said:
Hey Fgarcor,
I had some time so investigate the problem. What i have done so far:
Mapping all my Hardware Keys to specific keycodes:
-Google Assisstant - - > 289
-Start Route - - > 288
-Switch Spotify - - > 291
-See Notifications - - > 292
-Route Option A - - > 283
-Route Option B - - > 284
-Route Option C - - > 285
So thats all "Events" i need for android auto. Then i went into debug Mode an locate the coordinates for each section:
-Google Assisstant - - > 925 x 556 y
-Start Route - - > 224 x 450 y
- Switch Spotify - - > 215 x 550 y
- See Notifications - - > 791 x 562 y
- Route Option A - - > 260 x 175 y
- Route Option B - - > 260 x 275 y
- Route Option C - - > 260 x 375 y
So i have all Information that i needed an just have to merged them but i dont know where can i define specific commands. I tried "Button Remapper Pro" but the APK does Not detect my keycodes.
Where can i Set up some command lines? Do i have to install a specific Module in Magisk Manager? Or is there Kind of a console on my rooted Android Radio?
Sorry, i dont understand it for 100% and need your help, Thanks
Best wishes
René
Click to expand...
Click to collapse
Hi Rene,
I don't have the pro version, I just tested on my phone to associate a long press on the volume down button to start the Google assistant and it worked. So I guess for your case you can do the following to associate a key with the Google assistant, I see several options:
- On the main screen select "add buttons". Now that the hardware button is not any of the standard buttons like home, recents, volume, etc that you would find on a phone.
- then press the hardware button you want to add so the application automatically reads the code, on this case one of the keycodes that you sent before.
- associate the action with the button you just pressed, you can associate to:
--- actions: like sending keycodes (only for pro it seems), or intents (actions inside an application that can be started from outside of the application), other typical actions like volume control, home, etc
--- applications: launching one of the installed applications
--- shortcuts: available for some applications to start an action quickly.
- here you can select as action send keyevent and there you can choose to send KEYCODE_M. That is specified by HUR as the key to launch the mic, in your case assistant, that way you are independent of a change in the interface and coordinates.
- you can select also to send a shell command, and there you can write what we discussed before "input tap x y". And replace X and Y with your coordinates.
- you could also select directly the assistant under actions, veggie the last one, but I think that would trigger the assistant on your head unit Android and but in HUR.
I hope it helps, if questions, feel free to ask.
Sent from my ONEPLUS A3003 using Tapatalk
---------- Post added at 02:50 PM ---------- Previous post was at 02:46 PM ----------
Waffel57 said:
I tried "Button Remapper Pro" but the APK does Not detect my keycodes.
Click to expand...
Click to collapse
Sorry I missed this part, how did you get your keycodes in the first place?
Sent from my ONEPLUS A3003 using Tapatalk
Thanks for your reply Basically i opened Hal9K MOD Settings. There is a Option called "remap Buttons". There i can enable "keycodes" so whenever i press a key, the Code will displayed for a few seconds. I also can Change the Button functions from a define keycode list (i am Not able to enter a specific keycode). So i put all the Buttons i want to use to a defined keycode which has no function on my Radio yet.
I downloaded tasker and tried to Set up shell commands. I Used "Input tap x y" whenever the specific keycode Was Red. But it seems, tasker cant read the keycodes? I tried to put in the if statement:
getKeyCode() == 289
Keyevent.getKeyCode() ==289
Input keyevent == 289
And some combimations of that but Google assisstant wont start.
Maybe i have to implement a whole Script for that? Never die amything like that, could be funny ?
Thanks for your help so far
Shell command from tasker
Waffel57 said:
Mapping all my Hardware Keys to specific keycodes:
-Google Assisstant - - > 289
-Start Route - - > 288
-Switch Spotify - - > 291
-See Notifications - - > 292
-Route Option A - - > 283
-Route Option B - - > 284
-Route Option C - - > 285
Click to expand...
Click to collapse
Did I understand you correctly? These numbers from above were assigned by you? Or did you read them via tasker?
Sent from my ONEPLUS A3003 using Tapatalk
Correct, i assigend them in Hal9K, they were inside the list. I think i cant read them with tasker or i just have the wrong command.
Waffel57 said:
Correct, i assigend them in Hal9K, they were inside the list. I think i cant read them with tasker or i just have the wrong command.
Click to expand...
Click to collapse
Can you try with the following app? This is the one I use to know what are the values of the key pressed.
https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay
You can check whether the keys are pressed, if they are detected by Android and in that case which value are they bound with.
I am not sure whether the mapping you made was to give a keycode to a hardware button or to remap existing keycodes. In the second case I would skip the remapping and just use the original values.
You can check with this app before and after assigning the keycodes to the hardware buttons, and maybe I can understand better how does it work for you. Sorry.
Sent from my ONEPLUS A3003 using Tapatalk
Fgarcor you are absolutly right, thank you!! But this confuses me much more ? find attached a Screenshot from your apk.
It seems that the keycodes i "mapped" in Hal9K, werent really mapped. Cause in the output of "keyeventdisplay" there are different keycodes. As you mentioned, this have to be the right Codes.
Nevertheless there are just a couple of Buttons recognized but this would be Okey first of All.
A big Mysterium for me is still Tasker ? I dont know how to Set up a Profile that makes a Input tap whenever a Button was Pressed? Which variable/function Do i have to Check for the keyevent?
Im sorry for annoying you, but there is no comprehensibly thread to find on Google. Do you have some experience with tasker and Set up something like this?
I am really thankful for your help so far
Waffel57 said:
Fgarcor you are absolutly right, thank you!! But this confuses me much more [emoji85] find attached a Screenshot from your apk.
It seems that the keycodes i "mapped" in Hal9K, werent really mapped. Cause in the output of "keyeventdisplay" there are different keycodes. As you mentioned, this have to be the right Codes.
Nevertheless there are just a couple of Buttons recognized but this would be Okey first of All.
A big Mysterium for me is still Tasker [emoji85] I dont know how to Set up a Profile that makes a Input tap whenever a Button was Pressed? Which variable/function Do i have to Check for the keyevent?
Im sorry for annoying you, but there is no comprehensibly thread to find on Google. Do you have some experience with tasker and Set up something like this?
I am really thankful for your help so far
Click to expand...
Click to collapse
It looks like the 19,20,21,22 area corresponding to the arrows (up, down, left right, not necessarily in that order) and the 87, 88 could be select and back?
I think I have something similar in my head unit.
Coming back to the mapping to actions. You said that Button Mapper is not detecting your key presses when you try to add a button? Even after unmapping them from your keycodes in your head unit? Because that is the easiest way to move forward.
Regarding tasker I haven't used it much. Once I tried to set a routine but it turned out macrodroid did the job better than tasker and I sticked to it.
Let me check if I can find it how to do it in tasker.
EDIT: it seems that tasker needs a plugin called auto input where you can either select the key presses to react to, as a trigger, or they can be detected by the app. This is a paid plugin with a trial period of 7 days.
And then I read in some forums that to run a shell command you may need to have root on the device what I guess it is not the case in your display. That also made me think if button mapper or similar could run a shell command.
I need to check a bit further.
Sent from my ONEPLUS A3003 using Tapatalk
So, once again, i tried Button mapper to recognize my Button Keys but nothing will be found. I deleted all keycodes and Pressed any Button, but they wont be displayed in Button mapper.
I also have to mention that i am rooted through Hal9K, i have Magisk Manager and can give superuser for Apps (did that for Button mapper).
Thanks for searching the Internet, i tried Auto Input, but didnt had that much time So far. Seems like i have to read/watch Videos about that plugin and tasker Routines. I hope i have time for that at the weekend. But it would be awesome if it would work, cause i See a lot of opportunity in that.
Thanks for your time, maybe that will help some other Guys
I was asked by @rigattoni if I could write an app that allows to trigger Tasker after head unit wakes up from sleep (aka fast boot).
Why? Android has no reliable way for apps to be triggered when the device resumes from suspend-to-RAM state (aka fast boot).
Therefore a lot of Tasker users are missing a way to achieve that any Tasker jobs are started in fast boot.
My small little app tries to solve this.
This topic was first mentioned here: https://forum.xda-developers.com/showpost.php?p=82596933&postcount=6133
How it works:
When a USB mass storage device is attached, the app will be triggered by Android, both in cold boot, and also in "fast boot".
Then the app waits for 10 seconds and then fires a Tasker specific intent to Tasker and the app will finish itself.
This allows that any Tasker tasks will be triggered.
In the attachment you find both a ready APK and the source code of it.
Note: I will not maintain this app.
If the APK does not fit your needs, adapt the source code yourself.
If you want to send other intents additionally, adapt the source code yourself.
If you want to change the timeout of 10 seconds, adapt the source code yourself.
If you don't know how to do so, take an online Android App Development training.
Thanks for your effort and this post ?
I've simply used tasker with "Display on" event for starting the app I need, turning wifi on, etc.
Working flawlessly for cold boot or resume... why not this method?
themissionimpossible said:
I've simply used tasker with "Display on" event for starting the app I need, turning wifi on, etc.
Working flawlessly for cold boot or resume... why not this method?
Click to expand...
Click to collapse
For me and others, the Tasker background process is killed on resume so it's not "active" to know that the screen is on or otherwise.
In my case tasker always runs on start.
But if for somebody tasker is killed on resume, how another app instead should be able not to be killed as well?
This app here is started by Android itself if a USB stick is present and so resistent against the 'kill all running apps' issue.
Missing Accessibility activation
On CSN2, CSN2-D, RL7Ac units another issue is visible, according to the Android restrictions starting with Android 8, that accessibility settings are not stored. That means that Tasker is not allowed to work in background... This is a no go for us...
This can be "fixed" if the unit is rooted!
What is needed:
Preparation:
Unit is rooted
Tasker installed
Secure Settings installed and activated
Workflow:
Secure Settings:
Switch to tab "SYSTEM+"
Press the button "DISABLED" and wait until the system is set to "ENABLED"
Close the app
Tasker:
Open "Preferences" in Tasker, switch to tab "MISC", activate "Allow External Access" and deactivate "Reduce Resource Usage". There might be some popups afterwards when closing Tasker about battery usage... As we don´t care about that, please accept these changes.
Task:
Create a profile, Example:
"Screen on" with higher priority (otherwise the task may be scheduled)
Create new task
Press the "+" button to add a command
Choose "Plugin and there "Secure Settings"
Press the stylo and open "System + Action"
Choose "Accessibility Settings" and search for Tasker in the list (on some units, the field is really small to find any app)
Press the "DISABLED" button to get it changed to "ENABLED" and safe the setting.
You can add other accessibility changes too. In this case you need to add a wait of 100ms between the commands.
(FCC needs it, because otherwise some functionality of FCC does not work (automatic light, volume....))
Example added to import in Tasker.
not working for me on android 10 (( (825X_pro)
magicm3n said:
not working for me on android 10 (( (825X_pro)
Click to expand...
Click to collapse
Would you please precise what is not working?
What happens if you start the app manually?
...some information as given would really be useful, right?
rigattoni said:
Would you please precise what is not working?
Click to expand...
Click to collapse
Tasker does not start after waking up.
rigattoni said:
Would you please precise what is not working?
What happens if you start the app manually?
Click to expand...
Click to collapse
If I start app manualy its OK, tasker starts
You need a USB stick being attached to the head unit. Have you done this?
realzoulou said:
You need a USB stick being attached to the head unit. Have you done this?
Click to expand...
Click to collapse
Yes, of course, USB stick attached
magicm3n said:
Yes, of course, USB stick attached
Click to expand...
Click to collapse
If you pull out the stick and put it back in again. Do you get the popup to start the StartTasker automatically?
rigattoni said:
If you pull out the stick and put it back in again. Do you get the popup to start the StartTasker automatically?
Click to expand...
Click to collapse
So, here's what news.
After a long sleep (the car sleep for about 2 hours), I turned on the ACC and received a notification asking whether to launch the StartTasker when the UDisk device was connected. I checked the "allow" box.
But now if I turn off the car for just a couple of minutes, then nothing happens: the unit wakes up, all applications are killed and the StartTasker does not start.
When I take out the stick and insert it again, then OK, the StartTasker starts - I see the correspond popup notice below.
But now there is another problem: the StartTasker itself does not start the Tasker ((. Even if I manually start StartTasker , I can see the startup notification at the bottom, but the Tasker won't start. Hm...
magicm3n said:
So, here's what news.
After a long sleep (the car sleep for about 2 hours), I turned on the ACC and received a notification asking whether to launch the StartTasker when the UDisk device was connected. I checked the "allow" box.
But now if I turn off the car for just a couple of minutes, then nothing happens: the unit wakes up, all applications are killed and the StartTasker does not start.
When I take out the stick and insert it again, then OK, the StartTasker starts - I see the correspond popup notice below.
But now there is another problem: the StartTasker itself does not start the Tasker ((. Even if I manually start StartTasker , I can see the startup notification at the bottom, but the Tasker won't start. Hm...
Click to expand...
Click to collapse
StartTasker is NOT for starting Tasker, it´s to activate Tasker working in background. It just send an Intent, nothing else.
Check if in Accessibility settings Tasker is activated and in Tasker settings if "Allow External Access" is activated and "Reduce Resource Usage" deactivated.
Add a new profile with Display Orientation Landscape, write a short task with a Wait for 10 sec and add a Flash with some text and retest.
This should automatically activated after boot. and should show this flash on your unit.
Yes of course, a profile is written in the Tasker to launch another application. It works. When I rebooted the device, the StartTasker saw the connected USB and launched the Tasker, which completed the task.
But all this does not happen for some reason after exiting sleep mode.
I'll check settings tomorrow. Tnx!
rigattoni said:
StartTasker is NOT for starting Tasker, it´s to activate Tasker working in background. It just send an Intent, nothing else.
Check if in Accessibility settings Tasker is activated and in Tasker settings if "Allow External Access" is activated and "Reduce Resource Usage" deactivated.
Add a new profile with Display Orientation Landscape, write a short task with a Wait for 10 sec and add a Flash with some text and retest.
This should automatically activated after boot. and should show this flash on your unit.
Click to expand...
Click to collapse
My Head unit have not Accessibility settings (
All other is on.
Did not start after sleep.
If I reattach USB stick manually then Starter had starts, I see pop up message, but Tasker is not.
magicm3n said:
My Head unit have not Accessibility settings (
All other is on.
Did not start after sleep.
If I reattach USB stick manually then Starter had starts, I see pop up message, but Tasker is not.
Click to expand...
Click to collapse
I assumed that....
See my posting here: https://forum.xda-developers.com/showpost.php?p=82627859&postcount=7
You can import the task and then export as app afterwards.
In this case you just need a launcher which supports this app on start up. I use Fcc Car Launcher for that.
rigattoni said:
I assumed that....
See my posting here: https://forum.xda-developers.com/showpost.php?p=82627859&postcount=7
You can import the task and then export as app afterwards.
In this case you just need a launcher which supports this app on start up. I use Fcc Car Launcher for that.
Click to expand...
Click to collapse
FCC Car Launcher does not work on my Unit. No widgets support.
magicm3n said:
FCC Car Launcher does not work on my Unit. No widgets support.
Click to expand...
Click to collapse
Which unit?
Please don´t let us tear all information in small parts out of you.
which Unit, MCU version, Android version... please.
Use this app to configure the Accessibility settings and check if this is still activated after deep sleep.
Just now I don´t know any unit which does not work with Fcc... not completely may be with some missing features, but the standard things are working.
...and please read at least the first thread of the Fcc Car Launcher thread...
This thread gives a solution to rework the Tasker issue... and is a real Tasker fault.
I added a solution for getting it working if any Android unit forgets the accessibility setting in deep sleep.
Your problem now is a complete different thing, which needs to be discussed in the related thread.... and this is for fact the Fcc thread.