Hello,
I have a simple case:
- I have PX5 radio in car
- and Huawei Mate 20 Lite as a phone
Both devices are paired with bluetooth.
Since PX5 radio is full Android device that can run Google Play apps itself.
I would like to use bluetooth only for calling and as trigger for Tasker(start WiFi hotspot).
But since it is possible my phone sends also multimedia sound(but it won't be played on radio, since specific app for A2DP is not working - and I'm fine with that), I would like my phone to simply play multimedia itself, not via bluetooth.
I know it is possible in vanilla Android(https://fscl01.fonpit.de/userfiles/6983662/image/androidpit-lollipop-bluetooth-forget-w628.jpg) but since Huawei has it's "awesome" custom settings menu it is not there, do You guys have any idea how to change that settings?
ADB or any application would be great.
I'm not interested about any solution with root.
Apparently there is small "i" button on the right of paired device in bluetooth settings - not that easy to click(because when I tried to hit it for a first time I couldn't hit it correctly - that why I created that topic) - where You can change what sound is passed via bluetooth.
Related
Hi all,
I am trying to use the factory bluetooth integration in my car, and from everything I've read, it requires SAP (or rSAP?) to work properly. I've never had trouble pairing to the bluetooth module, but the car still insists there is no phone.
After messing with it yesterday and installing SAPSettings, I can hear the speaker of the phone in the car's audio, but no microphone, and it still says "insert phone" in the car's phone menu as apposed to downloading the phone book and letting me dial on the screen.
The phone lists the SAP profile among many others, but if I go into the settings of the car's bluetooth connection, it only lets me choose "Hands Free", with an on/off checkbox. It seems like thats what it sensed was available from the car, and offers nothing else, but I'd like to force SAP instead.
Car: MB E-Class
Phone: Sprint HTC Touch
OS: WM 6.5
Thanks!
I'm going to put the official windows mobile 6.1 on it to see if it makes a difference.
bluetooth is a long list of various profiles
problem is that devices only need to implement 1 or 2 to call themselves
bluetooth devices and no if the maker of the bluetooth stack in both ends
didn't implement a profile you can't force it
I have this problem trying to get my HD to connect to my landrover freelander 2 hse. I can get it to connect to the phone, but cant get the call to play thru cars speakers.
Dont bother with winmo 6.1 or official rom, just doesnt work at then (cant connect).
Only way i can get it to work is with winmo 6.5 (manila 2.5) (profiles must have newer or more stable settings). Only thing i have to do then is to make a call (normally voicemail) turn privacy on, then off again and voila it plays thru speakers.
Downside is i have to do this everytime i start the engine.........
Now that probably doesnt help you much but you will probably find from your car manufacturer that you device is not supported with you cars handsfree bluetooth kit.
the only one fully compatible with the freelander 2 is................. an phone
An amazing One click - Connect 2 Specific Bluetooth device for A2DP and Phone app:
Bluetooth Pair
https://play.google.com/store/apps/details?id=com.gnssoftworks.bluetoothpair
found it very useful for swapping bluetooth headphones between devices WITHOUT turning off Bluetooth entirely or going into the settings menu.
Example Use Case:
I have one Stereo Bluetooth headset with mic (two profiles - phone and A2DP audio)
I have one Android Phone and one Android Tablet.
Phone Profile is always connected to the Android Phone, but the A2DP audio changes depending on which device you want to listen to music from.
Normally, if you want to listen to audio from the Tablet when your headset's A2DP profile is connected to the phone, you'd have to first go to the settings menu of the phone, and disconnect the A2DP, leaving Phone Profile connected. Then go to the settings menu on your tablet and connect the A2DP only.
Then you'd have to do the opposite if you want to listen to audio from the Phone again.
Takes a long time.
With Bluetooth Pair, you can specifically connect or disconnect to a specific device and specific profile (phone / a2dp) by widgets.
So you won't have to turn off the bluetooth completely on one device just to allow your headset to connect another device. Nor do you need to go into settings anymore.
1.) Just tap on the A2DP device specific widget on the phone to disconnect, the A2DP Profile from the phone
2.) go to the Tablet, and tap on the A2DP device specific widget to connect the A2DP profile of the headset to the Tablet
Two taps!
Would you mind sharing a code snippet on how you achieve this? I've been working on a little program that I intend to use around the house and this is the missing piece that I can't figure out. Basically, I have some NFC tags spread around the house and a receiver app that triggers various actions. One of them enables bluetooth on my device (if off), turns on my home audio receiver (over telnet), connects to the receiver's A2DP device (this is the missing piece), and launches a music app.
I've seen examples where this works using an AIDL method, but from what I've gathered this no longer works under Android 4.2. Does your app work on 4.2? Any hints you can provide?
Thanks!
Brian
I'm not the writer of this app.
You could try contacting them via the email listed on Google Play.
BTW, while you're making your app, please dedicate a thread to it on XDA so we can all beta test and buy it later!
klau1 said:
I'm not the writer of this app.
You could try contacting them via the email listed on Google Play.
BTW, while you're making your app, please dedicate a thread to it on XDA so we can all beta test and buy it later!
Click to expand...
Click to collapse
Oh, OK. I just assumed this was your app.
After reading the Play Store description more carefully, I don't think this app actually does what I'm trying to do (programmatically establish an A2DP connection). It appears this app enables / disables certain profiles but the actual connection is still handled by the OS.
As far as the app I'm making, I was intending it to just be something for personal use. I'm planning on keeping it very lightweight and tailored specifically to my needs. For it to be used by anyone else they would have to have the same brand of A/V receiver as me (Pioneer) that supports the same telnet commands. Most of the rest of the functionality of the app can be duplicated by using some of the existing NFC apps like NFC Task Launcher. If I ever develop it into something interesting that could be used by a wider audience I probably will post it on XDA for feedback though.
I'm pretty sure I remember this setting being available in the preview versions just like in kitkat, but on the recently released images I cannot find the setting to change the bluetooth visibility setting to never time-out. The pioneer bluetooth stereo in my car absolutely will not recognize the presence of my phone unless it is discoverable.
Am I missing something, or has this option simply been removed.
If it has been removed I'm hoping maybe there is something I can modify to get this option back.
Thank you
xxrzdxx said:
I'm pretty sure I remember this setting being available in the preview versions just like in kitkat, but on the recently released images I cannot find the setting to change the bluetooth visibility setting to never time-out. The pioneer bluetooth stereo in my car absolutely will not recognize the presence of my phone unless it is discoverable.
Am I missing something, or has this option simply been removed.
If it has been removed I'm hoping maybe there is something I can modify to get this option back.
Thank you
Click to expand...
Click to collapse
If you open the bluetooth settings it says, that your device is visible to all devices as long bluetooth is enabled. Only in this screen your bluetooth device is visible to other devices.
I hope google fixes this, because its too confusing.
Yes, unfortunately that's the only reference to bluetooth visibility I have found.
My understanding in 5.0 is that your device's Bluetooth is only visible to paired devices, except when the Bluetooth Settings page is open. When the Bluetooth Settings page is open on your device it will be visible to all nearby Bluetooth devices (which is what you need when pairing). Have you paired the Pioneer Bluetooth stereo with your device?
There no longer appears to be an option as there was on 4.4 to permanently set 'Visible to all nearby Bluetooth devices'. However, why would you want that, other than when setting up pairing? It's a security risk.
xxrzdxx said:
I'm pretty sure I remember this setting being available in the preview versions just like in kitkat, but on the recently released images I cannot find the setting to change the bluetooth visibility setting to never time-out. The pioneer bluetooth stereo in my car absolutely will not recognize the presence of my phone unless it is discoverable.
Am I missing something, or has this option simply been removed.
If it has been removed I'm hoping maybe there is something I can modify to get this option back.
Thank you
Click to expand...
Click to collapse
I'm in your same situation, I was googling around and I found this... I'm on CM12 and wish that we can find a solution for make the bluetooth always discoverable on AOSP roms. I own a Lg G3 and on the stock Android 5.0 rom the option (like in KitKat) it still there!
The only reason I was really looking for this features is that my older Pioneer head-unit in my car (DEH-P9800BT) won't connect automatically to my phone unless the phone is discoverable. I've managed to adapt my other bluetooth connections that were set this way to work without the option, but I've tried for years (since my Palm Treo 650p) to get the head unit to connect automatically with no luck.
I am also wondering why they have hid this feature...
Looks like they are trying to go like (cr)Apple, whereas your iPhone is only discoverable within the Bluetooth menu.
Hi
I am using a PX5 system and have an OBD2 elm227 (tried 2 different brands, 1x icarly and a white label product) and a iphone 7 paired.
The iphone BT works, i can call etc and in my BT settings menu all the devices are listed as paired etc..
Problem:
When i start Torque Pro and i want to choose the BT adaptor there is nothing shown...
According to Torque there is NO BT adaptor paired at all which i can choose from.
I use the latest offcial (paid) PRO version of Torque!
I rebooted the device already but this had no effect.
Is there a fix for this?
I am using malaysk rom on my PX5 device, so it is rooted and has xposed installed.
Who can help/advise
[update]
It worked after a reboot but it seems BT does not work after ACC off/on, only on a reboot or cold start.
Hi there, i also use OBD2 with torque and works like a charm!
Try to delete all the BT paired connections first and after that, pair first the OBD2 adapter and test it!
Regards.
1. Press reset button
2. Unpair
3. Start the phone app and pair from there
Go to torque app and select the obd
it seems when my system goes standby (acc off) the BT connection is lost after power on.
All paired devices are simply not working anymore...
Sometimes they aren's even visable anymore in BT menu after ACC off/on, on a cold start or system reboot they work again.
Is there a way that when the system goes to sleep (acc) these apps keep running in background or are restarted when ACC is turned on again (not cold start/boot).
Also other apps are killed and not started anymore on resume.
Also i cannot find any option too change the ACC time, in an other rom i could set this time for example to 10 seconds and if then returned on it would cold start.
On PX5 Malaysk rom i cannot find any menu for changing ACC sleep/shutdown time
it seems when my system goes standby (acc off) the BT connection is lost after power on.
All paired devices are simply not working anymore...
Sometimes they aren's even visable anymore in BT menu after ACC off/on, on a cold start or system reboot they work again.
Is there a way that when the system goes to sleep (acc) these apps keep running in background or are restarted when ACC is turned on again (not cold start/boot).
Also other apps are killed and not started anymore on resume.
Also i cannot find any option too change the ACC time, in an other rom i could set this time for example to 10 seconds and if then returned on it would cold start.
On PX5 Malaysk rom i cannot find any menu for changing ACC sleep/shutdown time
Search the thread for the no-kill mtcmanager.apk
This will keep all apps on resume
To be able to see they menu for shut down delay you have to be on an mcu higher than 2.48 I think.
I'm having a similar problem. Iphone via bluetooth and torque worked perfect until yesterday.
Now, Iphone is not on the paired devices, nor I can pair with it again. And torque sees the obd adapter, but can´t talk to ecu and I dont see the obd under bluetooth devices .
What shoud I do?
Audiofanx said:
I'm having a similar problem. Iphone via bluetooth and torque worked perfect until yesterday.
Now, Iphone is not on the paired devices, nor I can pair with it again. And torque sees the obd adapter, but can´t talk to ecu and I dont see the obd under bluetooth devices .
What shoud I do?
Click to expand...
Click to collapse
I have the exact problem. was able to pair iphone before, now can't pair anything
B3rt said:
Hi
I am using a PX5 system and have an OBD2 elm227 (tried 2 different brands, 1x icarly and a white label product) and a iphone 7 paired.
The iphone BT works, i can call etc and in my BT settings menu all the devices are listed as paired etc..
Problem:
When i start Torque Pro and i want to choose the BT adaptor there is nothing shown...
According to Torque there is NO BT adaptor paired at all which i can choose from.
I use the latest offcial (paid) PRO version of Torque!
I rebooted the device already but this had no effect.
Is there a fix for this?
I am using malaysk rom on my PX5 device, so it is rooted and has xposed installed.
Who can help/advise
[update]
It worked after a reboot but it seems BT does not work after ACC off/on, only on a reboot or cold start.
Click to expand...
Click to collapse
unfortunately I have the same issue - BT works till next power on of the radio...then only after reboot but I can not connect the paired devices...
I think, it wasn't so in original ROM...
I am using malaysk rom on my PX5 device too.
Ok I was able to get Bluetooth back full time by reinstalling maylaysk rom. Does anyone have a copy of the original torque that came with the factory rom? I have the paid version but I'm having issues with it
Same here hoping for original version of torque that came with px3 device.
Sent from my SM-G892A using Tapatalk
The torque app that came with the unit and torque pro did the same thing for me as soon as I went from MCU 2.75 to 2.8 for my HA MTCD unit.
See this thread for the torque app you need... It's at the bottom of post 1.
https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155
I just posted in Dasaita and Hal9k_ threads regarding my BT OBD.
1. Connecting but not recognized by apps
2. Not connecting to MCU anymore.
Both have been resolved with...
1. Update to latest MCU (my HA is 2.83).
2. Install/update rom to latest Dasaita or Hal9k_ rom.
3. Do a Factory Reset
4. Connect to BT OBD
5. EVERYTHING WORKS FLAWLESSLY NOW FOR ME.
OBD2 Bluetooth Issues with Oreo 8.0
demetry14 said:
I just posted in Dasaita and Hal9k_ threads regarding my BT OBD.
1. Connecting but not recognized by apps
2. Not connecting to MCU anymore.
Both have been resolved with...
1. Update to latest MCU (my HA is 2.83).
2. Install/update rom to latest Dasaita or Hal9k_ rom.
3. Do a Factory Reset
4. Connect to BT OBD
5. EVERYTHING WORKS FLAWLESSLY NOW FOR ME.
Click to expand...
Click to collapse
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Pineapple5809 said:
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Click to expand...
Click to collapse
That worked for me for a week... Now my OBD still connects, but my phone no longer auto connects.
pavllo1980 said:
unfortunately I have the same issue - BT works till next power on of the radio...then only after reboot but I can not connect the paired devices...
I think, it wasn't so in original ROM...
I am using malaysk rom on my PX5 device too.
Click to expand...
Click to collapse
good evening I have the same problem with bluetooth that does not work after a reboot, I want to know if you have find the solution? thank you
ps: i'm french sorry for spelling
Pineapple5809 said:
For all those wondering about the connection problems - I have spent the last week trying everything - then randomly saw a video on connecting one of these devices. Stock setting for the bluetooth is password 0000 - it showed changing the password under bluetooth settings to 1234 which is the stock setting for all OBD2 devices. I went into settings - deleted all bluetooth devices - changed the password to 1234 - searched - found the OBD2 sensor (BLUEDRIVER) and it instantly connected and showed in paired devices. Fired up BlueDriver App and BAM! shes working without a hitch - fired up Torque Pro Lite and bam - connected without a hitch - for others with ELM you need to download the App for ELM because it only works with certain devices. After all the work I did trying to get it to work it was really just one little issue with the handshake *being the password* since you cant enter the password from the Bluetooth device like you would from your phone. Setting them both to the same solved the issue.
Click to expand...
Click to collapse
After quoting a a large post with meaningless correlations, I found postive shockra!
If your car has an older head unit with Bluetooth compatibility, you may have seen that with Android O, some of the metadata won't show up when playing audio from the phone. I found a tweak in the Android developer options that fixes it:
http://www.androidpolice.com/2017/0...ight-developer-preview-2-adds-avrcp-selector/
On my Honda Accord 2014, I set it to AVRCP 1.4 or 1.5, and Bluetooth shows the artist/track/etc again. Pandora runs more reliably as well.
There's no way I can get the audio system in my 2017 Subaru Forester to show remaining time on individual playing audio tracks. I have tried the various different developer options settings and it doesn't seem to make any difference.
I can confirm that setting version to 1.4, do fix this issue for pioneer radios. (Tested on DEH-X8500DAB).
After changing this, I can now switch tracks over bluetooth in my Honda Fit. Thanks!
In my case, after upgrading to Android 8.1 (Xiaomi Mi 5 @ AOSPExtended.mod by DennySPB) track infos won't work.
It doesn't matter if I choose AVRCP 1.3, 1.4, 1.5 or 1.6. It's just "no time, no title" etc.
Any other suggestions to fix that - apart from downgrading to 7.0?
(post removed by author, as it was not directly applicable to thread)
In my case, this solution worked, but I only post it "as is", without any warranty, that it will work for you.
1. Unpair audio device.
2. Go to Applications > show systems apps
3. Find "Bluetooth" and "Bluetooth MIDI", clear data for both of them
4. Go to developer settings, change AVRCP to 1.5 or 1.6
5. Restart phone.
6. Pair audio again.
Hi, thanks for the information, just reporting that this didn't work for me.
Android V9
Peugeot 508 JBL 2013