Database Users

[Q] How to launch Voice Search using headset while screen locked?

Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.

Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m

Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?

I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.

rhoadster91 said:
Jelly Bean introduced headset controls which allowed Play/Pause and Next for single and double presses respectively on headsets. I can confirm both these work just fine.
However, the long-press option to launch Voice Search only works while screen is unlocked. When screen is locked, long-press has no effect (it does not even register as a single press)
I tried the following:
1. Disabling Pattern lock (which I mostly use)
2. Turning on screen (but still locked) and then long pressing.
3. Keeping Google Search on in the background and then locking screen.
No luck.
Cannot seem to get any useful info regarding this on the Internet.
There is no point in the voice search shortcut on headsets if the phone has to be dug out from my pocket and unlocked. There has to be a way to bypass that.
Can somebody help??
EDIT: I am also unsure if this is an Android-specific problem or a ROM specific problem, so it would be kind of you if you could test it yourself. You can see my ROM details in the signature. I use Samsung headset in combination with my Nexus 4.
UPDATE: I tried turning off the "Power button immediately locks phone" option and set "Automatically lock phone after sleep" time to 30 minutes. Still the long press doesn't work. It works only after screen is turned on again. Whaaaaa...?!
ANOTHER UPDATE: This issue is present on Google Code but it has been closed without further comments. Please star this issue so that it is noticed by the development team.
Click to expand...
Click to collapse
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.

HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.

I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app

WilliamWynter said:
Been really frustrated about this as well. Any help would be greatly appreciated.
I'm running Jellybeer 4.0 on SGH i717m
Click to expand...
Click to collapse
Solutions Etcetera said:
Astounding. I even have to use a third party app to dial by voice reliably. What good is Google's extensive voice technology if you can't use it?
Click to expand...
Click to collapse
bryantee said:
I'm equally as confused. One advantage of owning an iPhone is that you've got an excellent bike companion that could read and reply to texts, make calls, check the time, etc all while keeping my eyes on the road and hands on my handlebars. I always figured my Nexus S didn't do that because I was running a different ROM - but 4.2 on a brand new Nexus.....come on.
Click to expand...
Click to collapse
HB66 said:
the closest thing that i know of is using touch control to swipe to unlock (like pressing the power button) the using NAV RING to swipe the nav ring to google search, or what ever app you like. not sure if this is what you want but it may get you closer.
Click to expand...
Click to collapse
thedarkharlequin said:
Here is what appears to be the correct place to file this complaint.
https://productforums.google.com/d/msg/websearch/ZbaIyhTIje4/GAKOqRrNjnAJ
Someone else started the report, I added as well, maybe someone at google will see and fix this oversight.
Click to expand...
Click to collapse
Lord_alias said:
I have to admit I have wanted to be able to do this for a long time on my motorcycle, being able to press one button and use voice controls would be a god send, although when riding I use an E-Dash app that keeps the screen awake so voice is available.
Still.......would be nice to be able to leave the phone alone, say in a bag or on my hip and use my Bluetooth headset to do all the work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Please check this link

My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search to desired one. Now you should be able to use Google Now in your preferred language.

stunner2002 said:
My solution:
1. Download Bluetooth Launch from Play Store
2. Launch, scroll to Google Search and expand it
3. Enable option “com.google.android.googlequicksearchbox.VoiceSearchActivity”
4. close
5. launch Google Now go to Settings -> Voice and enable Bluetooth Headset option
6. connect not working Bluetooth or wired headset and long press button. Dialog should appear and select Bluetooth Launcher always!
7. test if this is the complete solution for you. If it doesnt work properly when screen is locked try following:
- Install Xposed Framework
- go to Downloads and Install "AppSettings"
- open AppSettings and go to Google Search
- Turn On Settings and check "Show when locked"
- save
- restart Phone
If you are having issues with your selected language in Google Now. Also use AppSettings and change Location for Google Search Now you should be able to use Google Now in your preferred language.
Click to expand...
Click to collapse
But Exposed Framework requires your phone to be rooted, which I'm done doing... to much of a pain when it comes time to update

How do you reassign hardware buttons?

Hi all,
I have an Erisin 6046B HU with android 6.01 - I think this is a MTCB unit?! Anyway, I thought I could assign the hardware buttons on the unit to any app.. Eg NAV to Google maps, BAND to the DAB app. But I can't find the bit in the menus to do this - does anyone know how you do it?
Cheers

Oh my headunit (s190) I can go to Settings - Factory Settings (enter pass code) and then have a menus , Audio, Radio, Power, Icon Logo etc, and one menu is for hardware button settings
also I have Settings - Navigation Settings, where I can choose which app loads via the NAVI button

Jstyants said:
Oh my headunit (s190) I can go to Settings - Factory Settings (enter pass code) and then have a menus , Audio, Radio, Power, Icon Logo etc, and one menu is for hardware button settings
also I have Settings - Navigation Settings, where I can choose which app loads via the NAVI button
Click to expand...
Click to collapse
Perfect, thank you! I wonder how I find out what the passcode is? What is yours, just in case it's the same?

I saw a video of a similar unit and they typed in 126. Another was 1234.

Mine is 126

mikeroq said:
I saw a video of a similar unit and they typed in 126. Another was 1234.
Click to expand...
Click to collapse
Thanks guys, it was 126

[Solution] Start Tasker after head unit sleep

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.

How do I UNHIDE an app????

I was having trouble with an app (Android Auto) so I disabled it, which I shouldn't have, because it hid the app on my screen. As a result, the app no longer functions with my car.
Can somebody please tell me how to UNHIDE the app? I have watched 20 YouTube videos on how to unhide apps, unfortunately, they all show things that I do not have on my version of Android 10.
Thank you!

cameraz said:
I was having trouble with an app (Android Auto) so I disabled it, which I shouldn't have, because it hid the app on my screen. As a result, the app no longer functions with my car.
Can somebody please tell me how to UNHIDE the app? I have watched 20 YouTube videos on how to unhide apps, unfortunately, they all show things that I do not have on my version of Android 10.
Thank you!
Click to expand...
Click to collapse
Should be pretty simple and standard... I am assuming you are running stock A10 - if not, the names of the options in Settings may be a bit different, but the idea is still the same. Go to Settings -> Apps & notifications -> App Info. Above the app list there is a dropdown - make sure "ALL APPS" is selected, so both enabled and disabled apps are listed. You should see the Android Auto on the list below, marked as "Disabled". Tap on it - it will open the app details, then hit "Enable". That's all.

kt-Froggy said:
Should be pretty simple and standard... I am assuming you are running stock A10 - if not, the names of the options in Settings may be a bit different, but the idea is still the same. Go to Settings -> Apps & notifications -> App Info. Above the app list there is a dropdown - make sure "ALL APPS" is selected, so both enabled and disabled apps are listed. You should see the Android Auto on the list below, marked as "Disabled". Tap on it - it will open the app details, then hit "Enable". That's all.
Click to expand...
Click to collapse
Thanks, but I did all of that! I see Android Auto on the list, but it is not marked as "Disabled." When I click on it, it appears as Enabled in the app details.
However, that's not the problem. The problem is that the app is hidden from my Home Screen. So, in order for me to access it, I have to go into the Settings, etc., etc.
Is there a way to UNHIDE the app so it appears on my Home Screen? Thanks.
PS: I am running stock Android 10.

cameraz said:
Thanks, but I did all of that! I see Android Auto on the list, but it is not marked as "Disabled." When I click on it, it appears as Enabled in the app details.
However, that's not the problem. The problem is that the app is hidden from my Home Screen. So, in order for me to access it, I have to go into the Settings, etc., etc.
Is there a way to UNHIDE the app so it appears on my Home Screen? Thanks.
PS: I am running stock Android 10.
Click to expand...
Click to collapse
This is now normal behavior for android auto, the app is hidden and will only show in your car when you connect to your car (as far as I know there is no way to use it on your phone like the older versions), even if you add a shortcut to homescreen it will only allow access to the settings screen (I assume).
If it's not working with your car, go to settings>apps>android auto>storage> and then clear storage to reset everything. While there check it has all permissions granted.
If you want to use AA on your phone maybe consider sideloading an old version (from a reputable store like F-Droid) which still worked from the handset.

[Solved] Fake navigation app to use in Tasker for Chinese head unit

I have a generic Chinese head unit that allows me to define a Navigation app that can open when I press a specific button on my steering wheel.
However all the available apps for selection from my installed applications are the navigation ones (Google Maps, Sygic, Waze).
The thing is that I don't need to open a navigation app and want to make the button do something else, like starting Google Assostant for example which will be more useful.
So I would like to ask if someone knows a way or fake application that is viewed as an Navigation app from Android, which I will be able to assign to the button. And then link it to Tasker / Macrodroid / Autome whatever can handle it.
If the app can be configured to send intents or call something from Tasker it will be great.
There are triggers for app opening also but I guess for it to work the fake app shouldn't open anything and auto close, because killing apps requires root.
Another options is to make the Tasker secondary launch or Automate alternative start be recognized as an navigation app, so I could select it as my navigation app, but I don't think that would be possible really.
If anyone has any ideas it will be greatly appreciated.
P.S. Technically I can develop the app myself, but I'd like to know if there is a faster way
P.S.2. Solved.

You could do the following trick:
- trigger for Tasker: Google Maps (or similar) started
- then run a task which waits 2 seconds and then opens your app
Second possibility is to rename the package name of your app to the same as a navigation app like Sygic. You could use an app like Lucky Patcher. I don't know if this will work. Give it a try.

The first approach will leave an open Navigation app which is not desired, and I'm trying to avoid.
The second option is an interesting suggestion, I could try that (although the app will be better to auto close again). Who knows, maybe the chinese software is **** and only checks for specific text in the app package name

AppSwitcher - smart SWC launcher (for Junsun, Xtrons and similar devices) incl. autostart
AppSwitcher SWC (Steering Wheel Control) app launcher Stay focused on the street and don't touch the head units display to switch between apps. Support the development of this free app via ko-fi.com/appswitcher Please note: This app is...
forum.xda-developers.com
You could check if 'AppSwitcher Starter' appears in your list after installation.
If your goal is not to have an app switcher you could try 'FlowStarter' which can trigger an Automate Task and start the Automate Service:
Use SWC to switch between Navi and Radio
Attached app FlowStarter.apk allows to start an Automate flow (https://llamalab.com/automate/) which has to be defined in file flowstarter.cfg Required steps: 1. Install the apk. 2. Extract the file flowstarter.cfg to the internal storage (root...
forum.xda-developers.com
It works with every Flow and the attached Flow is just a sample.

Ok, so I had some time to tinker with the head unit and found out that it had a dumb check for the navigation app based on the package name containing certain words.
So I changed the package name of the FlowStarter app to include the word 'navi' and then I was able to select it in the menu as my navigation app.
So now I can technically do anything with the flow in Automate.
Thanks for the app recommendation very useful

alexdo said:
Ok, so I had some time to tinker with the head unit and found out that it had a dumb check for the navigation app based on the package name containing certain words.
So I changed the package name of the FlowStarter app to include the word 'navi' and then I was able to select it in the menu as my navigation app.
So now I can technically do anything with the flow in Automate.
Thanks for the app recommendation very useful
Click to expand...
Click to collapse
Great. Have fun with FlowStarter but leave a like for my app. ;-)

TorstenH said:
Great. Have fun with FlowStarter but leave a like for my app. ;-)
Click to expand...
Click to collapse
Liked it np. Very useful, was able to do a flow that detects how many times I started it in the span of some time (a second), so now I can assign multiple actions for the button, just have to think what they will be

alexdo said:
Ok, so I had some time to tinker with the head unit and found out that it had a dumb check for the navigation app based on the package name containing certain words.
So I changed the package name of the FlowStarter app to include the word 'navi' and then I was able to select it in the menu as my navigation app.
So now I can technically do anything with the flow in Automate.
Thanks for the app recommendation very useful
Click to expand...
Click to collapse
Great. Have fun with FlowStarter but leave a like for my app.
alexdo said:
Liked it np. Very useful, was able to do a flow that detects how many times I started it in the span of some time (a second), so now I can assign multiple actions for the button, just have to think what they will be
Click to expand...
Click to collapse
You could have a look on the sample flow which allows to switch between last used media app and navigation app with a single button press.