Related
I wanted an app to play audio through a phone earpiece, so that if I didn't take my headphones somewhere, I could still listen to an audio book as if I was on the phone. So I made a very simple app that toggles whether sound comes from the earpiece or the speaker: Earpiece.
Currently alpha, or maybe early beta, quality. Works on my Epic 4G Touch. Don't know how many other phones it'll work for. (Interestingly, I also noticed that if I have earphones plugged in and I select earpiece mode, then the volume goes up a little. I am curious if this happens for other users)
I also wanted an app that would let me boost the audio volume, so I added that functionality to Earpiece while I was at it (Android 2.3+ only, should work even on devices like tablets that don't have an earpiece). I know there are such apps (Volume+ seems to be the most popular one), but why have a separate app for this?
You can set Earpiece to show up when you long-press the search key. (I don't use this feature myself. Instead, I have another simple app that pops up a menu of my favorite apps when I long-press the search key, and I use that to launch Earpiece.)
Free and open source (BSD license).
Works on SGM l. But DSp manager FCs
Sent from my GT-S5570 using Tapatalk 2
ensoy said:
Works on SGM l. But DSp manager FCs
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
With what settings in Earpiece?
I would expect the Boost setting to interfere with DSP Manager, since both apps would be trying to do the same thing.
Not working on Motorola Defy with MIUI GB ROM.
5pace said:
Not working on Motorola Defy with MIUI GB ROM.
Click to expand...
Click to collapse
Thanks! Tell me more. How did you test it?
Here's how I test. I start an audio book playing in Mortplayer, and then go to Earpiece, and toggle the Earpiece checkmark.
Clever idea, thanks!
Works perfectly on my HTC EVO 3D ICS 4.0.3 leak, boost as well - even the feeble speaker becomes louder
Cheers
Christoph
Works perfectly on ZTE Blade.
Looks pretty weird when "talking" to phone without saying anything
mikpel said:
Looks pretty weird when "talking" to phone without saying anything
Click to expand...
Click to collapse
It looks like the person on the other end of the line is just talking your ear off and not letting you get a word in.
Question: Should I activate the proximity sensor in Earpiece mode, and turn the device screen off and on based on closeness to the face?
arpruss said:
It looks like the person on the other end of the line is just talking your ear off and not letting you get a word in.
Question: Should I activate the proximity sensor in Earpiece mode, and turn the device screen off and on based on closeness to the face?
Click to expand...
Click to collapse
Thats great idea. Im using this in sgs2 running aokp.
Sent from my GT-I9100 using XDA Premium HD app
I just posted 0.02 with proximity sensor support.
Screen off while close to face is default for phone calls on my htc, saves lots! of battery during long talks.
So, yes, please
Workaround so far: With screen off manually (power button), sound plays nicely in the background.
Thanks and Cheers!
EDIT: Too fast for me Thanks again!
Edit: Getting FC after "boosting"... all options set
chw9999 said:
Edit: Getting FC after "boosting"... all options set
Click to expand...
Click to collapse
Did this happen with the previous version?
Can you send me a log after the crash? Install Log Collector, then do the crash again, and then go to Log Collector to email the log to arpruss at gmail dot com.
My ICS has a not stable beats installed, deactivated it, now works flawless
Noticed that the "Volume up/down" beeps don't get routed through earpeace, which is fine with me. Probably, because it's not a media volume sound?
Cheers!
Work on zte blade, but is it possible to use earpiece + speaker in same time?
Envoyé depuis mon Blade
Works for mytouch 4g miui gb
Sent from my HTC MyTouch4G using Tapatalk 2
Gokh said:
Work on zte blade, but is it possible to use earpiece + speaker in same time?
Click to expand...
Click to collapse
You mean, for greater volume?
I doubt it, but I can experiment and see. Might actually be hard to tell if it's working, because the earpiece speaker will be drowned out by the main speaker.
I just posted 0.03.
It switches to the earpiece using a slightly different method. I'd appreciate reports whether it works for people.
By the way, no luck routing audio to BOTH the speaker and the earpiece at the same time.
I posted a release in the Market.
The release version carries one text ad on the screen, for my paid products. If the ad annoys you, just buy any of my paid products and the ad will disappear. Or just use a pre-release version.
Cool thing I found. If you turn on Earpiece while in Camera, the camera sound gets routed to the earpiece, and hence is very quiet, at least in my Epic 4G Touch.
(I know there are root-based solutions to the camera sound issue, but I haven't rooted my phone yet--I haven't found a way to do it that's both safe and doesn't involve copyright problems, like downloading unauthorized copies of parts of ROMs.)
I posted 1.01 in the Market and on the google code page. If you press MENU, you can go to Settings and select whether you want the status bar notification always, only when the background service is running, or never. The "never" is attractive if you don't like clutter, but unfortunately it allows the OS to kill Earpiece's proximity sensor and boost features (they need the background service) when the OS runs out of memory. Still, it's up to the user.
I am kind of excited by my discovery that earpiece mode makes the camera sound come out of the earpiece and hence be very quiet. I've experimented some more, and when I combine this with a negative volume boost, I can make the camera sound almost inaudible--probably inaudible to anybody more than two feet away except in an almost perfectly silent environment. Of course, for rooted devices there are ways of turning it off entirely, but I don't have root, and I want to be able to take pictures without disturbing people.
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
self bumb
How did you do it with tasker? If I can get that working I could help you out an see if I experience the same thing.
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
How did you do it with tasker? If I can get that working I could help you out an see if I experience the same thing.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I use tasker and Autovoice (a plugin for tasker). I have autovoice assigned to my bluetooth button. So when I press it, Autovoice comes up waiting for a command.
Then I have this tasker profile:
Profile: Google
State: AutoVoice Recognized [Configuration:Command: "hey google" ]
Task: Load App: Voice Search Data
A tip for AutoVoice when you set up the command make sure to check 'Event Behavior' or it'll keep the tasker profile active.
So when I say "hey google", Google now (or voice search) launches. But as I stated, with the headset the mic never turns red. It works great without the headset though (I have a shortcut to launch autovoice recognize). The other interesting thing is Autovoice uses the same voice engine that GN uses, and it works fine with the headset.
Just downloaded Tasker. I added a profile an selected voice search as my app. I now have to select a task. What should I choose?
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
Just downloaded Tasker. I added a profile an selected voice search as my app. I now have to select a task. What should I choose?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm assuming you've never used Tasker before.
You'll need both Tasker and AutoVoice from the market. I'll post a step-by-step really fast, even though it's a bit off topic.
Go into tasker --> Click '+' --> Name it whatever --> State --> Plugin --> AutoVoice Recognized --> Edit --> Check 'Event behavior', click Command Filter and enter 'hey google' (make sure no space after google) --> click check on top --> click icon on top left --> new task --> name it whatever --> click '+' --> App --> Load App --> Voice Search --> click icon on top left --> click icon on top left.
Now the bluetooh button should launch AutoVoice to wait for your command.
Well I got it running. Great instructions. I got this though now when I press the button. I select autovoice but nothing happens an I just go back to my home screen.
I understand you had another question so no worries. You can pm if you want. Hopefully someone can chime in for your question.
Sent from my SCH-I535 using xda app-developers app
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
Try this.........
http://www.youtube.com/watch?v=c9lElGDIOGM
Bump.
Any new news here? I have the same problem as the OP. It seems that some devices don't play well with Google now bluetooth still. I have a Motorola H700 headset that the mic will not work with Google now. S-voice hears my commands thru the bt mic fine (but has its own problems). It's just GN. I have the box checked, and I hear the beep in my headset but it can't hear any instructions. HELP!
havetolovemusic said:
I'm assuming you've never used Tasker before.
You'll need both Tasker and AutoVoice from the market. I'll post a step-by-step really fast, even though it's a bit off topic.
Go into tasker --> Click '+' --> Name it whatever --> State --> Plugin --> AutoVoice Recognized --> Edit --> Check 'Event behavior', click Command Filter and enter 'hey google' (make sure no space after google) --> click check on top --> click icon on top left --> new task --> name it whatever --> click '+' --> App --> Load App --> Voice Search --> click icon on top left --> click icon on top left.
Now the bluetooh button should launch AutoVoice to wait for your command.
Click to expand...
Click to collapse
Thank you, these instructions were very helpful.
Headset difference
Hi All,
I am facing a peculiar problem. I have 2 BT headsets. A Samsung WEP one and a Nokia 110 one. When I press the BT button on my Samsung headset, I am able to invoke the google now option. However, the same thing does not work with the Nokia. I do not get any option/default command when I press the button for Nokia BT headset. It works properly otherwise(recieve/reject call)
I have tried clearing the BT data in all apps and few other suggestions as well but the Nokia one just doesn't invoke Google now.
What might be missing in my Nokia headset?
Please suggest.
Thanks
Vishal
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
At least for me, the only thing I had to do to get audio from the BT headset was:
Open Google Now
Press Menu --> Settings
Select "Voice"
Check "Bluetooth Headset - Records audio through Bluetooth headset if available" box
EDIT:
Be warned that Google Now's audio prompt and voice playback appears to use the system volume (opposed to media or notifications), uses the Bluetooth media volume settings, so make sure it's not turned all the way down.
Hope this helps!
Has anyone had any success with this recently? I heard that usb audio is finally working on CM 10.2. Last I tried I still couldn't get usb audio + bluetooth mic for voice commands/Google Now.
havetolovemusic said:
First off, this is not a question of how to launch Google Now via headset (already got that using Takser)
Rather, I can't seem to get Google Now to recognize the mic. When I start GN, I can hear the chime over the headset to start talking, but when I talk GN doesn't recognized anything. I've been looking all over, and this forum and others to find an answer. I tried the 'touch sounds' workaround with no luck either. Anyone have any suggestions?
Click to expand...
Click to collapse
I finally figured it out. You can use SoundAbout to force the mic through bluetooth.
VoiceCommand 1.1.1
Delete
Did anyone try a wired headset with mic and buttons on Nexus 5 or other LG phones?
Can I use these buttons to skip tracks forward and reverse?
It seems they only act as volume control and play/resume on Nexus 5.
I couldn't figure out it's Android, phone or headset problem.
kevintemp said:
Did anyone try a wired headset with mic and buttons on Nexus 5 or other LG phones?
Can I use these buttons to skip tracks forward and reverse?
It seems they only act as volume control and play/resume on Nexus 5.
I couldn't figure out it's Android, phone or headset problem.
Click to expand...
Click to collapse
i think it's a patent that apple hold for 3 button headsets
Sent from my Nexus 5 using XDA Premium 4 mobile app
JoshuaFCB said:
i think it's a patent that apple hold for 3 button headsets
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same headset works properly on my Nexus 7 and HTC Inspire 4G.
Did you try holding the buttons?
MegaR said:
Did you try holding the buttons?
Click to expand...
Click to collapse
Yes, I did. I have tried double-press too.
check out the jays headset app in the play store, lets you set options for the one button on some android phones
Anyone know how to adjust the volume using apple earbuds?
Android app for controlling your 1 or 3 button headset
Do you also want to control function of your headset buttons? If you want full control and also the possibility to control online music services via your headset (play/pause etc one of the things that HAS been working better on the iPhone because of their way of integrating functions with their app makers) like Spotify, Pandora, Rdio and more you would need the free app from the guys at Degauss Labs.
The app is found on google play by the searchwords "degauss labs"
They just added suppor for Android 6.0 Marshmallow
http://play.google.com/store/apps/details?id=com.shengande.degausslabs
Its brilliant, ad free and no catch. Use it and love it :laugh:
nixter99 said:
Do you also want to control function of your headset buttons? If you want full control and also the possibility to control online music services likr Spotify, Rdio and more you would need the Free! app from the guys at Degauss Labs
The app is found on google play by the searchwords "degauss labs"
play.google.com/store/apps/details?id=com.shengande.degausslabs
Its brilliant, ad free and no catch. Use it and love it. Like me
Click to expand...
Click to collapse
I tried Headset Button Controller and Jays's and neither managed to change the up and down buttons' settings, only the center one. I have the Samsung Galaxy S3 default 3 button earphones on Nexus 5.
I'm gonna pretend this guy is not a marketer and give this app a shot. tired of going through all these settings
EDIT: Same issue... I can set the button for Next Track and Previous Track but it doesn't react, it just changes the volume as usual.
I got no luck either. It seems system intercepts the buttons first. No matter where I am, the system volume slide pop up when I press the buttons.
I got a hunch it might be LG's design issues. I was thinking it could be my haedset wasn't compatible to LG's phone. So I browsed Amazon looking for a headset specifically stated it worked on LG's phones. It turned out all of them were one button headsets. This result made me wondered somehow LG doesn't support 3 buttons headset control intentionally.
No Luck Either
nadram said:
I tried Headset Button Controller and Jays's and neither managed to change the up and down buttons' settings, only the center one. I have the Samsung Galaxy S3 default 3 button earphones on Nexus 5.
I'm gonna pretend this guy is not a marketer and give this app a shot. tired of going through all these settings
EDIT: Same issue... I can set the button for Next Track and Previous Track but it doesn't react, it just changes the volume as usual.
Click to expand...
Click to collapse
I got no luck either. It seems system intercepts the buttons first. No matter where I am, the system volume slide pop up when I press the buttons.
I got a hunch it might be LG's design issues. I was thinking it could be my haedset wasn't compatible to LG's phone. So I browsed Amazon looking for a headset specifically stated it worked on LG's phones. It turned out all of them were one button headsets. This result made me wondered somehow LG doesn't support 3 buttons headset control intentionally.
kevintemp said:
I got no luck either. It seems system intercepts the buttons first. No matter where I am, the system volume slide pop up when I press the buttons.
I got a hunch it might be LG's design issues. I was thinking it could be my haedset wasn't compatible to LG's phone. So I browsed Amazon looking for a headset specifically stated it worked on LG's phones. It turned out all of them were one button headsets. This result made me wondered somehow LG doesn't support 3 buttons headset control intentionally.
Click to expand...
Click to collapse
Hi
I never said the up and down button was programmable on the Nexus 5. These are hard coded by LG and will not do anything but +/- volume. It i snot the app´s fault but LG´s idea of making "Life Good" Only the center button is programmable on the Nexus 5.
But if you try the same app with the Nexus 3 by Samsung you will see the app makes all buttons programmable. As Samsung left the buttons possible to program.
But if you find this a drag, just think if you had the Nexus 4 from LG where there is only a one button support.
Bye
This thread really helped me out. I've been using Samsung phones up till a month ago when i bought my nexus. The first thing i noticed when i tried listening to music via poweramp and google play music was that the double and triple click to change tracks did not really work as well as they did on my S2. However, the deguass app really works well. Thank you.
Sent from my Nexus 5 using Tapatalk
does this mean that nexus 5 has no built in support for buttons from the headset?
Hi, please check this app, it can skip track using volume buttons single or double clicks.
http://forum.xda-developers.com/and...ick-double-t3265607/post64189497#post64189497
kevintemp said:
I got no luck either. It seems system intercepts the buttons first. No matter where I am, the system volume slide pop up when I press the buttons.
I got a hunch it might be LG's design issues. I was thinking it could be my haedset wasn't compatible to LG's phone. So I browsed Amazon looking for a headset specifically stated it worked on LG's phones. It turned out all of them were one button headsets. This result made me wondered somehow LG doesn't support 3 buttons headset control intentionally.
Click to expand...
Click to collapse
1 or 3 buttons
Yes, some phones only have support for one button headsets example Motorola Droid Maxx. But most have 3-button support today.
ALL LG´s (2015+2016) support 3-button headsets, ALL Samsungs support 3-button headsets as well, ALL Nexus phones after Nexus 4 supports 3-buttons, ALL Xperia Sonys.. you just need a real Android headset. As a user of the Degauss Headset Control Center which I think is faboulus in function and totally free app, I suggest to support the guys who made that at Degauss Labs. They have a truckload of Android eadsets that might fit your thinking, you´ll find them on www.degausslabs.com I myself use the Noir´s which are superb.
In my previous comment youll find the Headset App now also supporting Android 6.0 Marshmallow, Nexus 5x, Nexus 6P and many others are coming... Youll need that App to tailor the button clicks and set them to actiavte your musicplayer and "control" it.
Cheerio!
Just wrote a very simple app called BT GNow, which activates Google Now rather than the default Android Voice Dialer when you hit the hands-free button on your Bluetooth headset. Surprisingly, I can't seem to find another app that accomplishes this simple function. Bluetooth Launch does this to an extent, but the UI is difficult, it requires some configuration, it seems to me to cause wakelock problems, and the instance of Google Now that it starts takes off where Google Now left off (so you are often brought to an old search rather than an opportunity to speak a new voice command).
BT GNow keeps only a limited wakelock, requires no configuration (other than configuring Google Now to accept input from your Bluetooth device and possibly disabling the native Voice Dialer), and starts a fresh instance of Google Now each time.
Here's the Play Store link: https://play.google.com/store/apps/details?id=com.vibaroo.btnow
And the (minimal) website that describes the setup: https://sites.google.com/site/btgoognow/home
Great will try tomorrow
I will try now, great APP man:good:
Fail, my bluetooth now is not working, i tried, factory reset, re-flash system but not working more
Wow, great app. Makes my bluetooth headset and Google Now work as I always expected it would have to begin with.
I noticed that there was a problem with the screen locking and not responding to touches if lockscreen security is enabled and Google Now is interrupted. Solved this problem with the latest version and also improved wakelock control by sticking an icon in the corner of the screen. The icon disappears when the screen is turned off, and the phone is kept awake only as long as the icon is present.
Got rid of the icon that people seemed to dislike (made it invisible).
Donations?
New Feature
Some have reported problems with BT GNow not effectively bypassing the lockscreen. To address this, I've added an option that requires you to say "OK Google" after pressing your handsfree button; this in effect lets Google Now handle the lockscreen itself. You can activate this option by clicking on the app in the launcher and choosing the "OK Google" option.
Note that if you choose this option, you have to make sure that "OK Google" detection is set to work "From any screen": Google Now > Settings > Voice > 'OK Google' Detection > From any screen (checked or set to "on").
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Dzinic said:
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Click to expand...
Click to collapse
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
NYZack said:
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
Click to expand...
Click to collapse
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Dzinic said:
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Click to expand...
Click to collapse
Did you try disabling the voice dialer (as in the instructions)?
NYZack said:
Did you try disabling the voice dialer (as in the instructions)?
Click to expand...
Click to collapse
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Dzinic said:
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Click to expand...
Click to collapse
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
NYZack said:
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
Click to expand...
Click to collapse
Don't go out and get one just to fix my problem! I just don't use my phone for music enough to justify investing in a bluetooth, haha. Thanks for looking into it.
:thumbup:
Thanks!
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
patientzero said:
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
Click to expand...
Click to collapse
I've noticed that problem if you have more than one bluetooth device connected at once - for instance, if your phone is connected to your car's bluetooth or a stereo headset while connected to your Moto Hint. I'm considering options to try to fix this. In the meantime, perhaps it's better not to use the "OK Google" option and just launch directly from the bluetooth button?
My friend has same thing on his iPhone. I can now use google now with handsfree, when i driving my car. Thanks! The Coolest app on my week!
Wishlist ....
Given the code you have already written here is a little wish from me ... could you implement that the HFP bluetooth headsets just do not launch any application - just volume up and down.
xperia Z, TWIINS bluetooth headset for motorcylce, mono Bluetooth to route Navi output to headset - whenever I press volume down I get the stupid voicedialer or -if disabled- a black screen. I do not want to make any phoncalls on a fast bike!
Thanks in advance.
DrT_Music
So I got a new car (2016 "facelift" Kia Ceed 4 Tech)... and whilst OK Google Hotword detection over bluetooth sort of works, the
state of the dialler appears quite broken... and I was hoping if anyone could help.
Nexus 5 running Marshmallow paired to the car with Phone & Media Audio selected.. Google Voice Typing settings set to record audio through headset if available.
1) With screen on, say "Ok Google" wait for phone to respond with the first and then second beeps (I guess the second beep is to
signify the phone is then listening over bluetooth)
2) Say "Call xxxxxx mobile/home" etc.
3) Phone responds and starts dialling. Call is answered and the car Infotainment screen gives a prompt to change to "hands free mode", requiring a manual button press..
Not exactly "hands free behaviour".. Not compared to when I pair my wife's Galaxy Note 4, do exactly the same steps and everything goes through seamlessly with
the car automatically going to bluetooth handsfree without requiring me to press the button on the infotainment screen.
Now if you look at the dialler screen on the Nexus 5 whilst the call is going through, you can see the dropdown to manually choose between "Headset" "Speakerphone" "Bluetooth"
and the "Bluetooth" one is indeed selected but clearly the phone and car aren't handshaking to tell the car to automatically default to handsfree. At this point, you can re-select the bluetooth
option but it doesn't do anything, and the car is still waiting for manual confirmation.
More weirdness is, if you start a voice call with OK Google but actually press the phone button to action the call, then it all works fine...
Both Marshmallow and the car are new, so I'm not hopeful that anyone has an answer but given the Note 4 works perfectly, I'm keeping my fingers crossed..
Looks like a known problem since lollipop for nexus and some other phones.. not fixed in marshmallow either.. not sure what to do..LLC.. wait and see I guess
here