Fairphone Bluetooth status - Fairphone

Hi,
In the coming weeks we will be looking into the current bluetooth issues to try and figure out what we can do about them. If you have problems/questions feel free to talk about them here.

The only little problem is that everytime I enable Bluetooth on my device (since my update to 1.6), I get a "Unfortunately, Bluetooth has stopped" dialogue. Afterwards, Bluetooth works just fine (at least for file transfers and audio). Here is some log output captured while enabling bluetooth:
Code:
E/AndroidRuntime( 1437): FATAL EXCEPTION: main
E/AndroidRuntime( 1437): java.lang.RuntimeException: Unable to start service [email protected] with Intent { cmp=com.mediatek.bluetooth/.ftp.BluetoothFtpService }: java.lang.StringIndexOutOfBoundsException: length=16; regionStart=0; regionLength=-1
E/AndroidRuntime( 1437): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2822)
E/AndroidRuntime( 1437): at android.app.ActivityThread.access$1900(ActivityThread.java:156)
E/AndroidRuntime( 1437): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1437)
E/AndroidRuntime( 1437): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1437): at android.os.Looper.loop(Looper.java:153)
E/AndroidRuntime( 1437): at android.app.ActivityThread.main(ActivityThread.java:5299)
E/AndroidRuntime( 1437): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1437): at java.lang.reflect.Method.invoke(Method.java:511)
[...]
E/AndroidRuntime( 1437): Caused by: java.lang.StringIndexOutOfBoundsException: length=16; regionStart=0; regionLength=-1
E/AndroidRuntime( 1437): at java.lang.String.startEndAndLength(String.java:583)
E/AndroidRuntime( 1437): at java.lang.String.substring(String.java:1464)
E/AndroidRuntime( 1437): at com.mediatek.bluetooth.util.SystemUtils.getMountPointPath(SystemUtils.java:120)
E/AndroidRuntime( 1437): at com.mediatek.bluetooth.ftp.BluetoothFtpService.onStartCommand(BluetoothFtpService.java:962)
E/AndroidRuntime( 1437): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2805)
E/AndroidRuntime( 1437): ... 11 more
I have no idea why my phone tries to start a so called "BluetoothFtpService", let alone why this fails and why this didn't occur with earlier software versions.

I have BT Problems with my ALpine INE-W920R Car Radio.
Handsfree is connecting automatically most of the time, but not everytime, but A2DP is not connecting , or connects and disconnects immediatley.
with other Android Phones Bluetooth-connection works without Problems.
i am not really shure if it worked with 1.3 because i got this naviceiver 1 or 2 days before my upgrade to 1.6. But AFAR it worked better before.

Bluetooth Share Gateway Activity Bugs
_keesj said:
Hi,
In the coming weeks we will be looking into the current bluetooth issues to try and figure out what we can do about them. If you have problems/questions feel free to talk about them here.
Click to expand...
Click to collapse
Hi Kees,
we've encountered a bug which seems to be in the (Fairphone) Bluetooth share activity ( com.mediatek.bluetooth.BluetoothShareGatewayActivity.onCreate(BluetoothShareGatewayActivity.java) ). You can find a detailed description in the Simpletask bug report (issue #118) on github -> mpcjanssen -> simpletask-android.
A brief explanation:
Sharing one(!) simple text file by Bluetooth (chosen with Intent.createChooser) results in different errors, depending on what will be sent as EXTRA_STREAM:
Uri (like mentioned in Android documentation): "STREAM expected ArrayList" because Intent.getParcelableArrayListExtra() was called.
Using ArrayList instead: "STREAM expected Parcelable" because Intent.getParcelableExtra() was called.
Using Bundle instead: "Bundle cannot be cast to android.net.Uri" (cause unclear)
ACTION_SEND_MULTIPLE failed as well, but this action is not intended in this case.
Unfortunately, there is no code in your Fairphone repository.
Regards,
Dominik

haffenloher said:
I have no idea why my phone tries to start a so called "BluetoothFtpService", let alone why this fails and why this didn't occur with earlier software versions.
Click to expand...
Click to collapse
This was caused by the changes to FUSE storage and the default location to store data and should be fixed for the next release.

haffenloher said:
The only little problem is that everytime I enable Bluetooth on my device (since my update to 1.6), I get a "Unfortunately, Bluetooth has stopped" dialogue. Afterwards, Bluetooth works just fine (at least for file transfers and audio). Here is some log output captured while enabling bluetooth:
Click to expand...
Click to collapse
if you change the default storage from SD card to Internal, this should go away

rsommerv said:
if you change the default storage from SD card to Internal, this should go away
Click to expand...
Click to collapse
Yes, you're right, I can confirm that!
However, I prefer to keep the SD card as my default storage, a small error message from time to time won't hurt Good to hear that a fix is on the way!

If had issues with stuttering sound when streaming (Stereo) music from my fairphone to a bluetooth speaker by "PEAQ" (cheap brand of german MediaMarkt/Saturn).

fredflegel said:
If had issues with stuttering sound when streaming (Stereo) music from my fairphone to a bluetooth speaker by "PEAQ" (cheap brand of german MediaMarkt/Saturn).
Click to expand...
Click to collapse
Streaming to this cheap bluetooth speaker works for me, so it doesn't seem to be a general issue.

Hi,
Dominik K said:
Hi Kees,
we've encountered a bug which seems to be in the (Fairphone) Bluetooth share activity ( com.mediatek.bluetooth.BluetoothShareGatewayActivity.onCreate(BluetoothShareGatewayActivity.java) ). You can find a detailed description in the Simpletask bug report (issue #118) on github -> mpcjanssen -> simpletask-android.
Click to expand...
Click to collapse
Can you please google BluetoothShareGatewayActivity.java and have a look arround to try and determine what need doing? I have no access to the sources so best would be to get a patch I we can send forwards.

Once switched off, bluetooth refuse to be switched on again, until reboot
I don't know whether this problem is already known, but I have the strange issue that once bluetooth has been turned off, it's not possible to turn it on again, until a restart. That's also happening when in flight mode.

PLEASE make mediatek remove the need to "allow" every Bluetooth tethering connection via a notification and a modal dialog that needs the phone to be unlocked.
As far as I know mediatek added this unremovable feature for the sole reason of being a nuisance for their users to their Bluetooth driver/app. No other android hardware does that.
With the fairphone philosophy of being "open" this shouldn't be an issue, but the Bluetooth driver/app fairphone distributes is not and so users are stuck with whatever antifeatures mediatek imposes on them...

Bluetooth 4.0 LE
Hello and sorry for hijacking this thread but it seams to be the best existing topic for this,
i just read the discussion on the official forum regarding the BT 4.0 LE situation ( forum.fairphone.com/t/future-android-version-for-the-fairphone/67/33 ). After reading it i stumbled about a question/answer on stackoverflow ( stackoverflow.com/a/25974364 ) where an independent company was supposedly able to add a better Bluetooth stack.
Maybe @_keesj can forward this option to the team and maybe we can get a better Bluetooth stack this way?

Related

[Q] visual c# GPS application using OGL library

Hi!
I am triing to make a Windows Mobile gps application that is able to determine the current position and writes it on a form. Iam using the OGL open source GPS library.
My device is a trimble geo xh 2005. When i deploy my project on it, and try to connect to the receiver it keeps throwing an error: "An error has occured connecting to the receiver(error code5)" .
I've attached my project.
Maybe my gps setting are incorrect, i dont know. Just in case: GPS software port: 3; GPS hardware port:8 Baud rate: 9600 and Manage GPS automatically checkbox is set.
The above error appears giving port 3 in the application. If i choose port 8 it tells me that the port is already in use.
I cant figure out what am i doing wrong:-(
The GPS settings or something in the code?
Any help would be appreciated!
Never mind!
I have solved it, I was using the wrong port as i suspected

Who else is having bluetooth w/ car headunit issues?

Been having this issue ever since moving to official UVLE1 derived ROMs. I have tried everything except going to the Mr X rom. I would other ROM types( i have actually) but need wi-fi calling as tmobile does not dare enter my house. The issue is that bluetooth conencts to my Kenwood headunit immediately but then disconnects anywhere between 2 minutes and ten minutes later. It will then reconnect 30-60 seconds later but not have any audio unless i hit the play button on the headunit itself. I tried "bluetooth keep alive" app but did not work for me- yes i tried all the options. I actually got it working one night but flashed another rom and cant remember what i did. I've spent hours searching this issue. Anyone else have any luck?
oh some additional information: Problem is not present on any other rom bases including CM9, AOKP, Gingerbread, and skyrocket based ROMS. I have also turned off phone audio to strictly keep it to media with no difference. My Nexus 7 does not have this problem with the head unit.
this might or might not relate to your ROM but it helps my connection with AOKP anyways browse to /system/etc/bluetooth/ open up file audio.conf
look for the "autoconnect=" should be halfway through the page make sure there's no "#" in front and that it says AutoConnect=true
I'm on AOKP and it helps me, sometimes only phone audio connects for mine but ^^ that helped it.
Always seems to connect quickly- just disconnects just as efficiently lol. I will however give this a try and look around the rest of the config file.
yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.
configuration
Teo032 said:
yeah i looked around at the config file too and there doesn't seem to be anything else that might trigger a random disconnection. But for me, it always connected quickly, but for some reason with AOKP the media wasn't connecting all the time, and then someone mentioned the "#" in front of the AutoConnect. Hope it helps.[/QUO
Itookyour advic and then wentonefurther. ItookthewhileBluetooth folder from cm9and copied it. been good for about ten minutes so far. if I continue to have problems I'll copy over the Bluetooth apk. thanksagain.
Click to expand...
Click to collapse
Software Engineer with Bluetooth Car Disconnect Issue
Hi, this is my first post. Think I am in the right place.
I have a Samsung Galaxy S2 (hercules) and a 2010 VW Tiguan. The phone is running ICS, but problem happened on Gingerbread too. The problem happens at random times, but normally seems to happen while on the phone. I have tried a number of things including turning off the PAB service when running Gingerbread (didn't work). I also modified the config files from a tip from another post, but this didn't work either.
Below is a a portion of a log of when this appeared recently. I have not looked into much further just yet, but maybe this will help or maybe someone can explain what they think is happening at the disconnect. Thanks.
Note - The disconnect happened at 12:05:
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.267 E/BluetoothPbapVcardManager(20687): write outputstrem failedjava.io.IOException: Abort Received
08-06 11:58:28.287 E/BluetoothPbapObexServer(20687): operation close failedjava.io.IOException: Abort Received
08-06 11:58:29.318 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 11:58:29.428 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 11:58:29.468 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 12 PrevState: 11
08-06 12:02:05.559 I/HeadsetService(24033): Headset=false; Bluetooth=false
08-06 12:05:21.790 I/AudioHardwareMSM8660( 175): Routing audio to Bluetooth PCM
08-06 12:05:22.060 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 12
08-06 12:07:25.884 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 11 PrevState: 10
08-06 12:08:05.953 E/Bluetooth HS/HF( 592): BluetoothSocket could not connect
08-06 12:08:07.955 D/Bluetooth HSHFP( 592): AudioStateIntent: 00:0E:9F:7B:96:BA State: 10 PrevState: 11
08-06 12:20:16.896 D/BluetoothAdapterStateMachine( 332): BluetoothOn process message: 2
08-06 12:20:16.926 D/BluetoothAdapterStateMachine( 332): Bluetooth state 12 -> 13
replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly
TeamHackura said:
replacing the Bluetooth folder with the one from cm9 fixed my problem completely. you can try bluetoothkeepalive app as it works for some. i have since ditched tmo based roms in lieu of JB and haven't had issues yet. limited use so far since i been pairing my nexus 7 with stereo mostly
Click to expand...
Click to collapse
Oh, forgot to mention that the log file is with cm9. It seems to happen less with cm9, but not fixed for me. Will take a look at that app, and continue my mission to fix this.
Thanks for the reply!
I know this is dead but upgraded to note two on T-Mobile and issue is there.
Sent from my Nexus 7 using Tapatalk HD

Distorted sound via bluetooth headset with nAOSP ROM 5.1 for Xperia S

Hello,
I've installed nAOSP ROM 5.1 on my Xperia S. The ROM is working fine except an really annoying issue with my bluetooth headset. The voice of the person I call is really heavy distorted and impossible to understand. Also my recorded voice is not understandable. It sounds like after inhaling helium. Pairing my headset worked fine and it doesn't loose connection. I already did some research and tried to disable NuPlayer but without any effect on my issue.
The used headset model is "plantronics explorer 50" and it was working fine with stock ROM and it still works fine with other phones.
Are there any known issues or fixes/workarounds for this problem? Or other things I can do to solve the problem?
Best regards,
wewa00
UPDATE: I connected my Win7 laptop as a music player to my Xperia S via Bluetooth. This works fine. Sound from e.g. a youtube video i play on my Xperia S is transferred clearly to the laptop's speakers.
Does this Bluetooth sound issue only affect a special set of Bluetooth devices?
Best regards,
wewa00
PS: I use an "Intel Wireless Bluetooth" driver with version "17.1.1407.474" on my laptop.
UPDATE: I was in a shop recently and tried several headphones of various brands. Each shows the same issue like mentioned in my initial post.
Does no one have any idea what could cause this Bluetooth issues?
wewa00 said:
Does no one have any idea what could cause this Bluetooth issues?
Click to expand...
Click to collapse
For now it seems to be a ROM issue. You could try getting a logcat and posting it here. That might help the developer.
Mirhawk said:
For now it seems to be a ROM issue. You could try getting a logcat and posting it here. That might help the developer.
Click to expand...
Click to collapse
Thank you very much for your answer. I already thought that this might be a ROM issue. Others are also suffering under these issues (see following quotes).
yoda16211 said:
Hi! I have two (2) bluetooth issues. I am using the latest version (b22).
1) bluetooth headset only receives static/noise, and its bluetooth control (e.g. volume, next/prev) doesn't work
2) bluetooth keeps disconnecting when trying to pair with my car's head unit
Are there others who have experienced this or have a suggested fix?
Thanks in advance!
Click to expand...
Click to collapse
wxl104 said:
Same here
Sent from my Xperia S using XDA Free mobile app
Click to expand...
Click to collapse
I was already able to logcat via adb. But could you please tell me with which arguments I should call logcat to contain only necessary Bluetooth data and no confidential personal data?
Best regards
wewa00
wewa00 said:
Thank you very much for your answer. I already thought that this might be a ROM issue. Others are also suffering under these issues (see following quotes).
I was already able to logcat via adb. But could you please tell me with which arguments I should call logcat to contain only necessary Bluetooth data and no confidential personal data?
Best regards
wewa00
Click to expand...
Click to collapse
Unfortunately, I don't know what arguments are to be used to target it specifically,but what You could do is start logcat just before switching on bluetooth and end it after You try a few songs via bluetooth headsets. Logcats rarely contain personal data which are unique to Your device except Your problems.
I've uploaded a logcat to gist: https://gist.github.com/anonymous/7b8fc5a68feb5be3e1e9
I captured this logcat with Android Studio and this filter:
Code:
Log Tag (regex): BT|luetooth|bt|Bt
Log Level: Debug
I did following actions while logging:
Bluetooth on
headset connected
dialed a number
answered on 2nd phone
distorted sound on in headset and on 2nd phone
changed volume via headset buttons
quit call with headset button
started youtube video (no sound in headset)
turned headset off (phone did not notice that)
turned Bluetooth off and on again
tried to pair with laptop (didn work)
tried again, pairing worked, BUT: phone rebooted
tried several things, but could not play sound via Bluetooth on my laptop speakers
In another post I wrote that I could transmit sound to my laptop via Bluetooth. That was on another laptop, I'll try this again tomorrow.
I noticed an interesting line in the log.
Code:
E/bt_osi_config﹕ config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory
. The file does not exist on my phone. And i found out that also other android users have this line in their logs. But none of them offered a solution.
Now I have two questions:
Can you get some info out of the log or do I need to modify my filter settings?
Could the missing ble_stack.conf file be the problem?
Best regards
wewa00
EDIT: @mickybart: I've some debug info about the Bluetooth issues. Maybe you could take a look at it.
wewa00 said:
I've uploaded a logcat to gist: https://gist.github.com/anonymous/7b8fc5a68feb5be3e1e9
I captured this logcat with Android Studio and this filter:
Code:
Log Tag (regex): BT|luetooth|bt|Bt
Log Level: Debug
I did following actions while logging:
Bluetooth on
headset connected
dialed a number
answered on 2nd phone
distorted sound on in headset and on 2nd phone
changed volume via headset buttons
quit call with headset button
started youtube video (no sound in headset)
turned headset off (phone did not notice that)
turned Bluetooth off and on again
tried to pair with laptop (didn work)
tried again, pairing worked, BUT: phone rebooted
tried several things, but could not play sound via Bluetooth on my laptop speakers
In another post I wrote that I could transmit sound to my laptop via Bluetooth. That was on another laptop, I'll try this again tomorrow.
I noticed an interesting line in the log.
Code:
E/bt_osi_config﹕ config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory
. The file does not exist on my phone. And i found out that also other android users have this line in their logs. But none of them offered a solution.
Now I have two questions:
Can you get some info out of the log or do I need to modify my filter settings?
Could the missing ble_stack.conf file be the problem?
Best regards
wewa00
Click to expand...
Click to collapse
Yup, I noticed the missing file in log of other users too. Probably the developer is working on it too.
This log seems to be enough, given that You have done most the the stuff needed and it has been logged.
Do tag mickybart in Your post though, so it will come to his attention too.
Mirhawk said:
Yup, I noticed the missing file in log of other users too. Probably the developer is working on it too.
This log seems to be enough, given that You have done most the the stuff needed and it has been logged.
Do tag mickybart in Your post though, so it will come to his attention too.
Click to expand...
Click to collapse
I now also tried to connect the laptop where I once successfully played sound from my Xperia S via Bluetooth. Today I had no luck. When the Windows Bluetooth application searches for services running on my Xperia S, it says that it couldn't find any services or maybe an error occurred. I also tried repairing, without success.
https://gist.github.com/anonymous/0c03b6ca342dbff0f0ef
@Mirhawk: I think that unfortunately mickybart nor any other developer shows attention to these Bluetooth issues. Should I post to the developer thread, or what can I do to get their attention?
wewa00 said:
@Mirhawk: I think that unfortunately mickybart nor any other developer shows attention to these Bluetooth issues. Should I post to the developer thread, or what can I do to get their attention?
Click to expand...
Click to collapse
I don't think that will help much, but worth a shot, given that it is a development related issue.
Apologies, even I don't seem to understand as to what is causing the issue.
I've got the same problem with Plantronics M55, M75, M90, Jawbone Era (they're BT 2.1 or greater). But my old Plantronics ML12 (BT 2.0) works OK. As to the bt_stack.conf file, it seems to be a bt logger configuration file. See http://forum.xda-developers.com/mot...official-cyanogenmod-12-4-4-4-t2951070/page52 . They had such bt file missing with Moto G and ripped it from stock fw. I can't check if it helps placing that file into our filesystem. But you can. ))
PS: I wrote mickybart a pm about our issues, but there's no reply...
azteched said:
I've got the same problem with Plantronics M55, M75, M90, Jawbone Era (they're BT 2.1 or greater). But my old Plantronics ML12 (BT 2.0) works OK. As to the bt_stack.conf file, it seems to be a bt logger configuration file. See http://forum.xda-developers.com/mot...official-cyanogenmod-12-4-4-4-t2951070/page52 . They had such bt file missing with Moto G and ripped it from stock fw. I can't check if it helps placing that file into our filesystem. But you can. ))
PS: I wrote mickybart a pm about our issues, but there's no reply...
Click to expand...
Click to collapse
@azteched: Good to see that also others are struggling for a solution. I also found the thread mentioned by you. But I am missing the ble_stack.conf file. They are missing it in the mentioned thread too, but only bt_stack.conf is provided there. And I tried to reach mickybart too, but I never got any answer.
Hi, I will redo some tests with an headset that I know it was working. I will check if this is not an introduced bug. If I have the issue that will help me but if I haven't it will not be easy to fix it without an headset. In fact doesn't have the hardware is the main problem to be able to solve this kind of bug but I will try.
mickybart said:
Hi, I will redo some tests with an headset that I know it was working. I will check if this is not an introduced bug. If I have the issue that will help me but if I haven't it will not be easy to fix it without an headset. In fact doesn't have the hardware is the main problem to be able to solve this kind of bug but I will try.
Click to expand...
Click to collapse
@mickybart: Thank you for replying. Tell me if you need some additional debug info or testing on my hardware. I think that I could provide this data.
wewa00 said:
@azteched: Good to see that also others are struggling for a solution. I also found the thread mentioned by you. But I am missing the ble_stack.conf file. They are missing it in the mentioned thread too, but only bt_stack.conf is provided there. And I tried to reach mickybart too, but I never got any answer.
Click to expand...
Click to collapse
My fault. )) But AFAIK BLE stands for Bluetooth Low Energy, that is not supported by LT26i in hardware, so it doesn't seem to be the source of problem.
My girlfriend's headset is still working (Motorola H730). I will try to have an headset with the issue reported.
wewa00 said:
I've uploaded a logcat to gist: https://gist.github.com/anonymous/7b8fc5a68feb5be3e1e9
I captured this logcat with Android Studio and this filter:
Code:
Log Tag (regex): BT|luetooth|bt|Bt
Log Level: Debug
I did following actions while logging:
Bluetooth on
headset connected
dialed a number
answered on 2nd phone
distorted sound on in headset and on 2nd phone
changed volume via headset buttons
quit call with headset button
started youtube video (no sound in headset)
turned headset off (phone did not notice that)
turned Bluetooth off and on again
tried to pair with laptop (didn work)
tried again, pairing worked, BUT: phone rebooted
tried several things, but could not play sound via Bluetooth on my laptop speakers
In another post I wrote that I could transmit sound to my laptop via Bluetooth. That was on another laptop, I'll try this again tomorrow.
I noticed an interesting line in the log.
Code:
E/bt_osi_config﹕ config_new unable to open file '/etc/bluetooth/ble_stack.conf': No such file or directory
. The file does not exist on my phone. And i found out that also other android users have this line in their logs. But none of them offered a solution.
Now I have two questions:
Can you get some info out of the log or do I need to modify my filter settings?
Could the missing ble_stack.conf file be the problem?
Best regards
wewa00
EDIT: @mickybart: I've some debug info about the Bluetooth issues. Maybe you could take a look at it.
Click to expand...
Click to collapse
Hi wewa00, can you redo the same test but with a grep on "Audio|snd" and post the logcat report. If you prefer you can post a complete logcat and I will extract what I need.
Thanks
mickybart said:
Hi wewa00, can you redo the same test but with a grep on "Audio|snd" and post the logcat report. If you prefer you can post a complete logcat and I will extract what I need.
Thanks
Click to expand...
Click to collapse
Here is the logcat: https://gist.githubusercontent.com/anonymous/857bd9914999d69a7ed6/raw/gistfile1.txt
I hope it helps. If not, please let me know.

Bluetooth audio hiccups in Bliss Pop Rom and Reserection Remix

Well since I can't post in the actual rom thread I'll go here.
Tried searching for a fix for Bluetooth audio hiccups i'm getting from either of these roms. Both won't stream to my car stereo and just glitch bits of audio to the stereo. I have a 2015 Santa Fe.
Any ideas as the search is not working for me
An error occurred while performing a Searchlight query:
connection to 10.0.100.17:9312 failed (errno=111, msg=Connection refused)
If you followed a valid link, please notify the administrator.
Thanks
Ryan

Continuing issues with MirrorLink

Ever sine the upgrade from Android 6 to 7 I have been unable to get MirrorLink working the way it did before. I used to simply connect my phone to my Pioneer AVH-X7700BT and it would start mirroring the screen. I mostly used this for navigating to customers homes when I needed to perform on-site repairs. Now when I try to do the same thing on any Android 7 Rom the stereo rejects that the phone is connected, already updated the firmware on the stereo to the latest and I can connect my M8 without issue. The latest update to the MirrorLink app did not fix the problem, I've even installed much older versions of the app pulled from my M8. I've attached a log I pulled and from what I can tell the issue involves these lines ( I could be wrong and that's why I've attached the log.)
D/[MirrorLinkServer] RfbProtocol(9794): Server's RFB Version (3, 8)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.e.c.b(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.h.E(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.j.D(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.j.run(Unknown Source)
I don't want to use the Pioneer AppRadio stuff because it is slow to load, drains battery, often won't find addresses, has no voice assistance, and doesn't give you a very good user experience when it actually works. I've tried multiple versions of Viper, LeeDroid, NuSense, and a 100% stock 10 from a friend.
lightweaponx said:
Ever sine the upgrade from Android 6 to 7 I have been unable to get MirrorLink working the way it did before. I used to simply connect my phone to my Pioneer AVH-X7700BT and it would start mirroring the screen. I mostly used this for navigating to customers homes when I needed to perform on-site repairs. Now when I try to do the same thing on any Android 7 Rom the stereo rejects that the phone is connected, already updated the firmware on the stereo to the latest and I can connect my M8 without issue. The latest update to the MirrorLink app did not fix the problem, I've even installed much older versions of the app pulled from my M8. I've attached a log I pulled and from what I can tell the issue involves these lines ( I could be wrong and that's why I've attached the log.)
D/[MirrorLinkServer] RfbProtocol(9794): Server's RFB Version (3, 8)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.e.c.b(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.h.E(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.j.D(Unknown Source)
07-23 15:09:02.222 W/System.err(9794): at com.htc.mirrorlinkserver.vncserver.j.run(Unknown Source)
I don't want to use the Pioneer AppRadio stuff because it is slow to load, drains battery, often won't find addresses, has no voice assistance, and doesn't give you a very good user experience when it actually works. I've tried multiple versions of Viper, LeeDroid, NuSense, and a 100% stock 10 from a friend.
Click to expand...
Click to collapse
can you tell me which version of mirrorlink is working?
Inviato dal mio HTC 10 utilizzando Tapatalk
I don't have one that works with that stereo on the HTC
10 right now if that's what you're asking. The latest version available on the M8 works for that phone and stereo combo though.
Same problem with the new Oreo update. I plan to try it on my friends new Subaru this week.

Categories

Resources