Moto G XT1039 - Suunto Movescount [bluetooth issues] - LineageOS Questions & Answers

Hi!
I face a problem with LineageOS and connecting my sports watch (Suunto Ambit3) to the smartphone in order to receive push notifications on the watch. The watch has to be paired via the Suunto Movescount app. Afterwards, when being in bluetooth range pushed notifications should be transferred to the watch, automatically. In addition, trainings I logged with the watch can be transferred to the app, too. With my stock ROM (Motorola G LTE XT1039 "peregrine", Android 5.1.2) this worked.
However, with LineageOS I can pair the watch with the Movescount App initially but it cannot reconnect after being disconnected once. Lineage smart lock shows that the watch is connected (trusted devices) but no data is transferred between the phone and my watch.
Has anyone a clue which settings to modify in order to make the connection work? What else could I do? Is there an alternative app that could Transfer the push notifications to the watch (Botifiy doesn't work) Thanks in advance

default_user0815 said:
Hi!
I face a problem with LineageOS and connecting my sports watch (Suunto Ambit3) to the smartphone in order to receive push notifications on the watch...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3469103
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Already did that.
Thank you.

Sorry, me again.
I didn't get an answer to my question in the corresponding sub-forum. Anyway, my next question is more or less a general question.
I still have no real clue why the connection with my watch works under the stock ROM and doesn't work under lineage OS. But I identified some differences in the build.prop files of the two ROMs:
In lineage the building.prop files shows
Code:
[...]# Bluetooth
qcom.bluetooth.soc=smd
qcom.bt.le_dev_pwr_class=1
ro.qualcomm.bluetooth.opp=true
ro.qualcomm.bluetooth.hfp=true
ro.qualcomm.bluetooth.hsp=true
ro.qualcomm.bluetooth.pbap=true
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.nap=true
ro.qualcomm.bluetooth.map=true
ro.bluetooth.sap=true
ro.bluetooth.dun=true
ro.bluetooth.hfp.ver=1.6
ro.qualcomm.bt.hci_transport=smd[...]
whereas the building.prop of the stock ROM looks like this:
Code:
[...]# system property for Bluetooth hci transport
#
ro.qualcomm.bt.hci_transport=smd
#
# system property for Bluetooth HFP version
#
ro.bluetooth.hfp.ver=1.6
#
# system property for Bluetooth SAP support
# Motorola disabled SAP
#
ro.qualcomm.bluetooth.sap=false
# Bluetooth LE power class
qcom.bt.le_dev_pwr_class=1[...]
Would it be possible that my issues are related to the differences within these files? Could I play around with the Bluetooth settings there without risking to brick my phone (of course I know it is a delicate thing to modify the building.prop file, but maybe there is a chance that....)?

Related

TP2 / Kenwood BT Contacts Download Issue

I have a Kenwood KDC-MP642U car audio system with Bluetooth capabilities and I have my HTC Touch Pro 2 [t-mobile] successfully paired and working great with 1 annoying exception.
As soon as the units connect to each other the contacts / phone book start downloading from the phone to the Kenwood system which is fine, however..... after EVERY call the contacts download fully again making the phone barely usable [slow] until the full phone book is downloaded. [90 secs for 150 contacts]
There is no setting on the Kenwood unit to not allow automatic download... if the phone supports it.... it will download. I was told by sales rep that his Kenwood did that as well and just to live with it ? ? ? ? ? ?
I have tried to find the appropriate registry setting on TP2 to deny auto PBAP access and download and cant find any help on this...... any help would be greatly appreciated.
I have the same setup, and noticed it on my prior phone as well (Motorola KRZR K1). I believe that the phone is updating the "recent calls" list on the headunit. I know for me the second download is MUCH faster than the first.
I haven't seen any information about preventing the update download.
this should do the trick:
http://forum.xda-developers.com/showthread.php?p=3848325
Question: does it show up as one of the profiles under the bluetooth paired devices list?

[REF] Fix bluetooth A2DP failing to connect (root required)

Tried connecting my Galaxy S to some A2DP speakers, found it would pair then fail to connect, constantly reporting "Paired but not connected".
After a bit of poking around, I found in /system/etc/bluez/audio.conf:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Switch to master role for incoming connections (defaults to true)
#Master=true
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
Changed to:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control,Headset,Gateway,Source
#Disable=
# Switch to master role for incoming connections (defaults to true)
#Master=true
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
Rebooted, and everything works like a charm. Probably only need to enable the additional profiles.
Here's the diff for those so inclined:
Code:
--- audio.conf.dist
+++ audio.conf
@@ -5,8 +5,8 @@
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
-Enable=Sink,Control
-Disable=Headset,Gateway,Source
+Enable=Sink,Control,Headset,Gateway,Source
+#Disable=
# Switch to master role for incoming connections (defaults to true)
#Master=true
@@ -19,7 +19,7 @@
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
-#AutoConnect=true
+AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
@@ -27,7 +27,7 @@
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
-#HFP=true
+HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
wiimote support
interesting to know that, thanx for sharing buddy
is it possible to get the sgs connected to a Wiimote? i think i had a similer problem when i tried to pair it with the wiimote, it seems to pair fine but it just wont connect, i appreciate your support
Will it work with car based handsfree?
kloodee said:
interesting to know that, thanx for sharing buddy
is it possible to get the sgs connected to a Wiimote? i think i had a similer problem when i tried to pair it with the wiimote, it seems to pair fine but it just wont connect, i appreciate your support
Click to expand...
Click to collapse
The Wiimote is a different beast - it's a HID device, and I don't know that the hidp module is included in the Galaxy kernel, or whether the proprietary bluetooth interface supports it.
ondoteam said:
Will it work with car based handsfree?
Click to expand...
Click to collapse
Yep, should do.
sorry, but how do i pull this file? i tried copying it with linda file manager to my sd but is doesn't copy.
aridoasis said:
sorry, but how do i pull this file? i tried copying it with linda file manager to my sd but is doesn't copy.
Click to expand...
Click to collapse
You'll need root - I just edited the file in place, but if you have a copy on your SD card, you could use Root Explorer to paste it over the existing one after making /system R/W.
hmm.. i'm getting 'error opening file'
Tell me what steps you're performing exactly, and I may be able to point you in the right direction.
i'm pretty sure i'm missing something...
i'm using linda explorer
i got to /system/etc/bluez/
click on audio.conf
so, i'm made to select what to open the file with
the only logical thing for me to use was dropbox text editor
is there a special file editor i need to use?
Your device needs to be rooted, and you need to use Root Explorer - you won't have permission to modify the file without root privileges.
lol. ok. my device is already rooted. thought i could do it without having to buy root explorer.
Any tool that will let you remount /system read-write, and write files as root will do - there may be others, but Root Explorer works particularly well, so that's the only one I'm aware of. I just did it from the command line, but you need a level of comfort with linux for that.
thanks spoidar. i was finally able to do it. just got super manager. not as great as root explorer, but it did the job.
Glad to hear you got it sorted
spoidar said:
The Wiimote is a different beast - it's a HID device, and I don't know that the hidp module is included in the Galaxy kernel, or whether the proprietary bluetooth interface supports it.
Yep, should do.
Click to expand...
Click to collapse
Thank you!! Working
Method works using root explorer for my e-blue airhifi bluetooth stereo receiver. Previously can only pair but cannot connect.
kaikee said:
Method works using root explorer for my e-blue airhifi bluetooth stereo receiver. Previously can only pair but cannot connect.
Click to expand...
Click to collapse
Good to hear - it astounds me that Samsung wouldn't get something so simple right.
BT Handsfree - not working
spoidar said:
Good to hear - it astounds me that Samsung wouldn't get something so simple right.
Click to expand...
Click to collapse
I edited and saved audio.conf on SMASUNG GALAXY S in root mode.
Then I rebooted - but no change.
I still get the same message "Paired but not connected"
ANy help ?
It works like a charm. Thank you very much man.
I am a android noob but i have figured out from rooting to editing the audio.conf
And now it connects to all my headset, helmet a2dp headset and to my car's bt system.
I have to say that ia had big prtoblems in the past with bt. Sometimes when a headset was connected an tried to call it frozed my phone to the point that i had to took out the battery to reset it. Right now, after the process, i used my phone for 3 days with intensive BT activitiy (from calls to music and to all headsets) and no freeze.
vrajitoru said:
It works like a charm. Thank you very much man.
I am a android noob but i have figured out from rooting to editing the audio.conf
And now it connects to all my headset, helmet a2dp headset and to my car's bt system.
I have to say that ia had big prtoblems in the past with bt. Sometimes when a headset was connected an tried to call it frozed my phone to the point that i had to took out the battery to reset it. Right now, after the process, i used my phone for 3 days with intensive BT activitiy (from calls to music and to all headsets) and no freeze.
Click to expand...
Click to collapse
Can I know after editing and saving audio.conf file - what are other steps to be performed in order to solve this problem?
Though I rebooted - the same problem continues.
Pl help?

Force bluetooth "phone audio" from nexus 7?

Nexus 7 2013 WiFi
Stock 6.0.1 rooted with Timur's Kernel v4
For some reason when I BT connect my tablet to ANY pioneer head unit (tried 3 so far) I don't get the check box in bluetooth options for "phone audio" . I am using the Verizon messages+ app to make calls and receive texts over wifi Hotspot from my phone. This works amazingly but for some reason I can't get it to route through to the pioneer bluetooth connection. I tried a set of bluetooth headphones and the phone audio checkbox is there and it works flawlessly.
I did some Google searching and searched this sub but don't see anything relating to this problem.
edit: see below for update
Is there a way to force a bluetooth profile to use "phone audio"? Is there a Config file anywhere I can manually edit?
I've tried Bluetooth Auto Connect and choosing the phone audio option for the head unit but it did not change anything.
I assume your nexus is lte ?
deadgiveaway said:
I assume your nexus is lte ?
Click to expand...
Click to collapse
Sorry should have put that info in the initial post. No, it is the WiFi model.
I would be wifi tethering my phone to get network connectivity. This is a Nexus 7 carputer type build.
Bit of an update though:
Per a website that I cant post a link to until i make 10 posts.... It looks like the nexus 7 2013 lacks the HFP (Hands Free Profile) by default. Now I'm not entirely sure why the bluetooth headset works if this profile is not present other than its possible the headset uses the HSP (Head Set Profile) but I can't seem to find any documentation on if the N7 actually has the HSP.
Through extensive googling, I ended up at posts talking about Bluez bluetooth stack implementation. This is a bit over my head though and cant really find any solid documentation on implementing it on Stock 6.0.1
I also ended up getting directed to the source.android page that mentions at the bottom:
Custom Bluetooth profiles - If you want to add Bluetooth profiles that do not have HAL interfaces provided by Android, you must supply an SDK add-on download to make the profile available to app developers, make the APIs available in the Bluetooth system process app (packages/apps/Bluetooth), and add them to the default stack (system/bt).
Click to expand...
Click to collapse
But like I said, this is over my head.
Anyone with any sort of experience give me some insight?

Mirrorlink with A3 2017

Hi all,
just a simple question - had anybody succeeded with MirrorLink? And with full phone mirroring (not just with the limited number of apps allowed)? If so, how? My A320FL is updated to the latest available Android 6.0.1, then rooted.
I tried several apps and guides together with two cars (Toyota & Skoda) with no success:
1) Samsung CarMode - the latest available from the market is not the latest, as I found somewhere here, but anyway: it doesn't do anything with Skoda and does show "Your phone is connected through MirrorLink" when connected with Toyota Touch 2, but shows nothing on the display. No option to start it is displayed on Toyota display, Skoda Amundsen says "no compatible app found".
2) LG MirrorDrive - does not even start, but it's shown as compatible app in Skoda. And once, I got the display in portrait mode shown on Skoda display for few seconds.
3) Android Auto - even though it's not accessible in my country (don't know why), I installed the latest version, but it is possible to start this app only on the phone, no car sees it.
check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t
shaggyxda said:
check this
https://www.youtube.com/watch?v=F-TNAXxFqDw&t
Click to expand...
Click to collapse
Thanks for idea, but it's unfortunately not the right thing - this deals with app flickering when the phone is already connected via MirrorLink. In my case, I don't see anything related to phone display on the car's display. In the meantime, I found out, that the possible problem could be system incompatibility - Samsung supports only MirrorLink 1.1 and Toyota is MirrorLink 1.0 (that's why all the videos online with Toyota are shown with the old S3). I also found out, that Samsung dropped the backward compatibility on Bluetooth, so i.e. old integrated handsfree in 2007 Yaris is now unusable. Shame on Samsung, did those people ever see a car?
Finally, got it working. But not thanks only to myself
The first is thanks to Toyota - there has to be at least HE3934 firmware version loaded (that I found out only when trying to make the mirrorlink running in a new Yaris).
The second is, that in phone, only one mirrorlink app is allowed and it shall be LG MirrorDrive for make it running in Toyota (Samsung CarMode app supports only VW group vehicles - possibly because they provide VW with the whole infotainment and related electronics).
The third and most important is the cable - it has to be a cable that "somehow" supports mirrorlink - Samsung original cable is ok, but I firstly tested it with another "noname" cable, which works only sometimes. Only during longer continuous driving period I found out, that the "impossible to connect" periods happen when the phone and cable shake - maybe some contact is doubled in the original cable.
As last I need to say, that LG MirrorDrive mirrors any running app, but after you run an app, mirroring quits with message, that the function is not available during driving. But it starts the app in background anyway, so when you run LG MirrorDrive on the infotainment again (without disconnecting or anyhow touching the phone), the system opens directly in the app you started before. It's also good to turn off the notifications for LG MirrorDrive, as it shows a message about incompatibility every time it's started.
So I hope that the lines above help also somebody else.
Can a samsung a3 2017 screen mirror? If yes then how please??
... but only working with nougat. Android 8 not working any more. ?
Please send me

Android Pie (and Oreo) Bluetooth Pbap

I have a 2017 Honda Accord Sport SE, with only the single display system that handles bluetooth and streaming etc.
Ever since somewhere around the May or June Oreo update and including the new Pie first production release, the car has been unable to transfer contacts from the Pixel XL to the car system.
I've played around with the AVCP setting, but that does not help. Briefly on the last version of Oreo, I was able to use the app "Bluetooth PhoneBook" to alter the phones PBAP so that my contacts were appearing in the car, but the first Pie version is now incompatible with "Bluetooth PhoneBook", so I cannot get contacts into the car system, and therefore cannot use voice dial with the phone. So I disable the bluetooth in the car and have to use my Plantronics bluetooth earpiece to make calls via bluetooth. The author of the app at http://www.android-rsap.com/bluetooth-phonebook/38-aktuelle-nachrichten/143-phonebook-app-and-android-8-oreo.html, mentions:
Google once again changed the internals of the Android Bluetooth stack, and guess what: it breaks my phonebook app. It is no longer able to properly stop the built-in phonebook service.
Today I found out that the latest Android source contains a change which once again enables my app. I don't have an idea when that change will be published in an official release or if there may be new Android 8 firmwares in the future which don't contain that fix. Simply check if your car connects to my app, if not you'll probably have to wait for the next firmware update.
And these problems all happen only because Google refuses to add a proper Bluetooth SDP API to the Android SDK. So they work their way from hack to hack. Sad...
Click to expand...
Click to collapse
Can anyone explain to me how the Bluetooth PBAP works an if this is an issue with the car manufacturer's implementation or Google's fault.
Unfortunately, Honda being a car manufacturer is not very interested in keeping firmware in its cars up to date, at least as far as phone functionality.
The 2018 Honda's allow firmware updates easily, so I imagine this is going to be less of a problem for 2018 and newer models.

Categories

Resources