Anyone figured out how to get the S6 to work with Android Auto? I have a Pioneer 4100 NEX and keep getting the same error message that several have reported. Phil over at Android Central has the same setup and to my knowledge hasn't found a workaround either. The head unit has the most recent firmware update which is supposed to address compatibility issues. I have tried using USB debugging and also using different launchers all with no effect.
Any ideas on things to try would be appreciated greatly.
Thanks!
Antagonistt said:
Anyone figured out how to get the S6 to work with Android Auto? I have a Pioneer 4100 NEX and keep getting the same error message that several have reported. Phil over at Android Central has the same setup and to my knowledge hasn't found a workaround either. The head unit has the most recent firmware update which is supposed to address compatibility issues. I have tried using USB debugging and also using different launchers all with no effect.
Any ideas on things to try would be appreciated greatly.
Thanks!
Click to expand...
Click to collapse
Waiting for an answer on this as well. Same setup. I hate that it worked so well on my M8 and is unusable on the GS6.
It's somewhat OT but have you tried it with MirrorLink? The Note 4 was supposed to support ML but seems to be completely incompatible with any available head unit and I was wondering if the S6 is any better.
Related
So, I updated to 4.3 and now my focus is having problems with bluetooth. It used to work perfectly before the update but now the metadata of the song doesn't update on the radio and some other things like texts don't come through like they used to.
Simply put, is there a way to get the old bluetooth "stuff" into 4.3 or is that baked in?
I was just studying the BT issues and I found out all phones with 4.2 or greater has BT problems across the board.
Can you just copy-paste BT files? I don't know.
But its a common issue.
rangercaptain said:
I was just studying the BT issues and I found out all phones with 4.2 or greater has BT problems across the board.
Can you just copy-paste BT files? I don't know.
But its a common issue.
Click to expand...
Click to collapse
That's what I aim to find out... I'm tempted to just go back to a 4.1.2 ROM but meh...
No, I agree about staying with 4.3. I'm sure Google will release a fix or a clever xda member will get it.
Bump, still looking for info :laugh:
k4zyn said:
Bump, still looking for info :laugh:
Click to expand...
Click to collapse
Can you explain what are the exact problems you experiencing with BT.
Because I'm not getting any atm! Just curious is to what's not working and what is...
Thanx
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Sounds like he isn't getting song info and text messages on his car's head unit when connected to the phone through BT on a 4.3 ROM.
Me, I just get choppy playback.
rangercaptain said:
Sounds like he isn't getting song info and text messages on his car's head unit when connected to the phone through BT on a 4.3 ROM.
Me, I just get choppy playback.
Click to expand...
Click to collapse
Pretty much. I used to be able to see what was playing. I used to be able to control pandora (pause/skip) but that no longer works either. I also do not get notifications like texts anymore.
Bajanman said:
Can you explain what are the exact problems you experiencing with BT.
Because I'm not getting any atm! Just curious is to what's not working and what is...
Thanx
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Quoting you too so you get a notification,
Edit: quote from a verizon thread:
Just so everyone is aware, this is due to the whole Motorola/Google ownership change. In previous versions of Android, Motorola sourced their own protocols for their products, and included MAP in their bluetooth profiles. Since the Jelly Bean update, they've used Google's own Bluetooth protocols, in which MAP was omitted.
is this true? Surely not, how would it have worked on 4.1.2?
Edit again:
http://www.androidheadlines.com/201...ocus-feature-bluetooth-map-now-supported.html
Says kitkat supports MAP again............. may just get a kitkat rom even though I'd rather stick to stock TW.....
Well, I updated to 4.4 ........... still no go
Hi guys. Just wondered if anyone can help. I am having a problem with an app that connects a cycle computer (mio/magellan cyclo 505) and nexus 5x that provides texts and phone call notifications to the Cyclo 505 through a bluetooth connection. This seem to be occurring with other marshmallow nexus phones.
The developer has not as yet updated the companion app (cyclosmart) so that it is compatible with the marshamallow and as such it won't work at the moment. The phone app states when trying to pair with the 505 using the app that it 'Cannot detect your cyclo device' so it won't pair. I can pair using general BT settings outside of the app but the notifications don't work.
Previously I used the app with a sony xperia z3 running lollipop and it worked fine. The app and its purpose is relatively specialised but I wondered if there is anyway to get the notification back on the bike computer again. If you take a look at the following theread on the CycloGPS forum you will see that this issue has been going on for a while and it some have got it working with a htc m8 and nexus 7 running marshmallow.
I have contacted the developer and mio/magellan) and it not looking like it will get updated at the moment so wanted to try and find a fix myself I've tried many things but all without success.
Any help will be much appreciated.
Not an answer for you, but Garmin's fitness devices also have various BT and Wifi issues that are difficult to get working.
Sent from my SM-T700 using Tapatalk
Does anyone here have a chromebook they use with their Oneplus 3?
I got a chromebook recently and can't pair the OP3 to the chromebook, and as a result can't use Smart Lock to unlock the chromebook by unlocking the phone. Am I doing something wrong or is the chromebook or the phone the issue?
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Anova's Origin said:
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Click to expand...
Click to collapse
Are you on stock OOS?
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
peterk-1 said:
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
Click to expand...
Click to collapse
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
2x4 said:
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
Click to expand...
Click to collapse
Sorry - I missed the point in my explanation. I should have made clear the "trusting" doesn't work in either direction. In the case of attempting to set up any device to unlock a Pixel C, the Pixel C menu Smart Lock > Trusted devices doesn't open to BT / NFC options but instead gives an "error" message " Trusted devices feature is not available to use". This has been the case with Android M and N so it has been suggested that this is a hardware restriction. The relevance? - Pixel C started life designed as a Chrome device. Another suggestion is that there is a coding error and GPS has been included as a requirement - I doubt this since trusted locations works.
2x4 said:
Are you on stock OOS?
Click to expand...
Click to collapse
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Anova's Origin said:
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Click to expand...
Click to collapse
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
2x4 said:
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
Click to expand...
Click to collapse
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
yes it is up to date
2x4 said:
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Click to expand...
Click to collapse
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
MrWilsonxD said:
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
Click to expand...
Click to collapse
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
2x4 said:
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
Click to expand...
Click to collapse
My pleasure. I doubt it's a problem with the CBP. Probably something to do with oxygen OS unfortunately.
added a new user to the chromebook today, and enabled smartlock with her phone (Nexus 6P) with zero issues - it's definitely the Oneplus 3.
i'm current on freedomOS community beta version. not sure what the issue is...
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
F4uzan said:
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
Click to expand...
Click to collapse
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
2x4 said:
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
Click to expand...
Click to collapse
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
F4uzan said:
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
Click to expand...
Click to collapse
tried a clean flash of the ROM I'm currently on (FreedomOS based on OOS beta), and the issue still persists.
I'd be open to using another ROM but haven't ever had a reason to switch and I like the optimal camera performance with OOS
just tried a clean flash of lineage OS (https://forum.xda-developers.com/oneplus-3/development/rom-t3532088) - smart lock STILL didn't work (I keep getting the "can't find your phone" error message)
what specific ROM(s) did you see it work on @F4uzan ?
Hello everyone, I'm Jade.
I have a Samsung Galaxy Note 3 SM-N900T. I am currently facing an issue with the front camera not responding when i try to start it from any app.
I have tried factory resetting, clearing the cache, installing a custom rom, rooting, trying a different stock apk for it. I have even replaced the front facing camera module. Nothing has worked and has led me to the conclusion that this is a software issue.
Here's what I would like help doing, I need to know what I can do to modify the camera and fix the firmware for it. I want to see what is causing it not to start and what I need to do in the core of the phones firmware, how to do it.
I'm familiar with adb, command lines, mostly linux environments but also windows, so it's not hard to find my way around. That being said, I am not imagining, n'or am I looking for an easy way to do this. If there is already a solution for this someone please let me know. ANY HELP is greatly appreciated!
I can't post a link to the file because xda won't let me. so email me for it: [email protected]
If using Odin and a stock ROM doesn't fix it, it might be a hardware problem.
Sent from my Sprint Note 3 running Lineage 7.1.1 on T-Mobile. using XDA-Developers Legacy app
rbeavers said:
If using Odin and a stock ROM doesn't fix it, it might be a hardware problem.
Click to expand...
Click to collapse
I haven't used Odin since my S3. But this was an issue before I even bothered rooting it. It can't be a hardware issue because I had already gotten a replacement. I'm assuming it's the fact that it's Android 5.0 that I'm facing the software issue. This is why I want to get right under the hood and find out how to write and modify firmware for it.
I've tried searching around but I'm getting nothing but bull's tail. I'm going to keep searching but honestly, this is ridiculous. (Talking about the searches, not you. Thanks for pointing that out anyway) :good:
Ogichidaa said:
I haven't used Odin since my S3. But this was an issue before I even bothered rooting it. It can't be a hardware issue because I had already gotten a replacement. I'm assuming it's the fact that it's Android 5.0 that I'm facing the software issue. This is why I want to get right under the hood and find out how to write and modify firmware for it.
I've tried searching around but I'm getting nothing but bull's tail. I'm going to keep searching but honestly, this is ridiculous. (Talking about the searches, not you. Thanks for pointing that out anyway) :good:
Click to expand...
Click to collapse
Nothing to do with that. If a firmware flash doesn't fix it, it's a hardware issue. Could be a number of factors...dirt and dust by camera or the camera is loose somehow.
Hey guys and gals,
I have tried multiple ROMs now, and am having the same problem with all of them. Whenever I connect my Note 3 to my car, I get a "This device does not support media function" error that I do not get with a stock ROM.
After a weeks worth of trial and error, the only thing I can come up with are USB incompatibility, or DRM? I have tried all the rom provided usb modes, with and without debugging enabled, still no luck. Anyone know a fix?
Using my wifes phone, I was able to confirm that the stock head unit works perfectly, so the issue is definitely with my phone/roms.
Currently running Phoresis v7 (which I love).
Here is a pic of said error
I fixed this the hard way :crying:
digimancer said:
I fixed this the hard way :crying:
Click to expand...
Click to collapse
how did you fix it?
I returned my Note 3 to stock via Odin... It is just barely worth it...
I almost want to buy another phone to keep in the car and just network it to my hacked one...
digimancer said:
I returned my Note 3 to stock via Odin... It is just barely worth it...
I almost want to buy another phone to keep in the car and just network it to my hacked one...
Click to expand...
Click to collapse
I'm not exactly sure what my problem was but I updated my phone via ODIN since I was on a beta software, reinstalled the AA app, removed my car from the settings in the app (reinstalling didn't delete it) and also toggle the setting for AA on my car's headunit and then it finally worked