So, I have a Daydream Controller I'm trying to pair with my Nexus 5X. On Android Nougat, it was as easy as launching the Daydream app, and hold the home button to pair the controller. However, with Android Oreo, it does not work! I went to Bluetooth settings to check whether the device detects the Daydream Controller, but it doesn't. However, on my laptop, the controller shows up as "Daydream Controller"... Furthermore, I tried with some more devices (bluetooth headset is detected, my laptop is detected). What do you think the issue is? Am I missing out something?
Edit: I want to add that I have Magisk installed (I am rooted).
Related
I tried to pair Ouya Controller with the phone , it hasn't worked.
Is there any way to get the Ouya Controller working on the phone to play games?
I mean , it is a bluetooth controller and the Ouya is based on Android ; it should not be so different :silly:
Thanks for help!
kevinrus123 said:
I tried to pair Ouya Controller with the phone , it hasn't worked.
Is there any way to get the Ouya Controller working on the phone to play games?
I mean , it is a bluetooth controller and the Ouya is based on Android ; it should not be so different :silly:
Thanks for help!
Click to expand...
Click to collapse
I paired it to my Samsung Discover - Android 4.0.4 today as a test. I bought the phone yesterday as a replacement for a broken phone. Upon pairing everything seems to work fine. However, the buttons are mapped differently than the Ouya. The mouse pad works perfectly although the click isn't very sensitive.
U: Back
A: Ok
L2: Menu
DPAD: Random? long press menu function (Brings up current running apps list in an unpredictable manor)
LS: Up, Down, Left, Right
The mapping suggest that when paired with normal android the keys are not putting out the same values as when the controller is paired with an Ouya.
nexuslite said:
I paired it to my Samsung Discover - Android 4.0.4 today as a test. I bought the phone yesterday as a replacement for a broken phone. Upon pairing everything seems to work fine. However, the buttons are mapped differently than the Ouya. The mouse pad works perfectly although the click isn't very sensitive.
U: Back
A: Ok
L2: Menu
DPAD: Random? long press menu function (Brings up current running apps list in an unpredictable manor)
LS: Up, Down, Left, Right
The mapping suggest that when paired with normal android the keys are not putting out the same values as when the controller is paired with an Ouya.
Click to expand...
Click to collapse
How did you paired the controller with your device? Is your device running a stock rom?
kevinrus123 said:
How did you paired the controller with your device? Is your device running a stock rom?
Click to expand...
Click to collapse
I went to bluetooth settings turned bluetooth on. While it was scanning I held down the Ouya button on the controller until the middle two lights were blinking and it paired. The phone is 100% stock, not rooted, no special controller drivers.
I believe I tried the same thing with my Samsung Stratosphere - Android 2.3.5 and it wouldn't work. Could be a combination of bluetooth protocols and android versions preventing it from pairing.
nexuslite said:
I went to bluetooth settings turned bluetooth on. While it was scanning I held down the Ouya button on the controller until the middle two lights were blinking and it paired. The phone is 100% stock, not rooted, no special controller drivers.
I believe I tried the same thing with my Samsung Stratosphere - Android 2.3.5 and it wouldn't work. Could be a combination of bluetooth protocols and android versions preventing it from pairing.
Click to expand...
Click to collapse
Thanks , will try it again to pair ASAP
This worked great for me. Thanks for the info on the holding down. I wasn't doing it long enough.
I recently rooted my nexus to connect my control using Bluetooth. I had everything set up but then it wouldn't read L1 or L3. I know it works because when I have the control connected directly through cable without the sixaxis app, all buttons work. I tried looking for others with this problem but nothing. I even changed the room to Cyanogenmod and still same issue. What am I missing here?
Has anyone been able to get the USB/Bluetooth version (that is, non HDMI) of MirrorLink to work?
I have a Pioneer AVH-X2700BS head unit. With the HU in MirrorLink mode, I connect the phone via Bluetooth, then connect the USB. The phone gives a notification that it is in MirrorLink mode with a "press to configure" button. When pressed, it goes to the setting menu with the MirrorLink mode enable checkbox. There are no compatible apps listed there.
The HU makes no indication that it is working with MirrorLink, other than it shuts down access to the other Bluetooth features like Bluetooth Audio and Pandora. However, the HU also doesn't present the application screen. I keep wondering if there should be some type of MirrorLink application, other than the OS support, on the phone.
By comparison, Pioneer has their AppRadio One mode that functions in a similar fashion, but makes a different set of applications available to use on-screen. That mode seems to work, but is severely limited by the low number of apps that support it.
This is exactly what I'm seeing with an AVIC-8000NEX and the N910A. I just recently switched from an iPhone 5S, so I hadn't really done any research on MirrorLink. Thinking it might only work with specific apps, I searched for "MirrorLink" in the Play Store and downloaded an app that appeared to be some kind of launcher application for MirrorLink (?). Didn't work either, promptly uninstalled.
If it makes you feel any better, the Apple CarPlay functionality on these higher end head units turned out to be a turd. It was the main reason I went to iPhone for a while.
I am trying to use a bluetooth Media Remote. When I search for bluetooth devices the device will appear and when I select it asks if I want to connect. However when I click yes it does not actually connect. I have tried to run XMTC and changed the name from ODB to the name of the device. This changes the icon of the device on the unit however it still does not connect. This appears to be OS\driver issue not a hardware issue since the device is being found.
I have tried two different bluetooth remotes with the same results(from amazon)
Satechi® Bluetooth Button Series (Media Button)
iSimple Portable Wireless Remote Control
I can however connect these to my phone and change the volume on the phone while I am streaming music to the head unit. And this is nice, but I would really like to be able to control the head units volume instead.
Does someone have a custom ROM that could fix my issue?
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
I am glad you were able to resolve your issue. Hoping someone smarter than me can fix mine
Anyone have any ideas how to get other bluetooth devices to work with this system? I expect someone that can build a custom ROM could fix this.
Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
Cool. What BT module did you use?
Zeneffect said:
Edit - was able to resolve my issue. Used xposed framework and bt module to remove the name limitation.
Click to expand...
Click to collapse
Did anyone ever find out which xposed module this is?
Hey there, I've got the Satechi® Bluetooth Button Series (Media Button) thing too, and surprise surprise, it won't talk to my Pumpkin HU (rk3066, android 4.4.1, mcu KLD2).
I've rooted the stock using the #hct#root# trick and installed SuperSU. I would love to get the button working!
I've got my head unit installed in my right-hand drive car (am in UK) - and where it's mounted, it is just out of reach unless I lean forward - so I can't really use it without looking, apart from using the tiny buttons down the side.
Happy to try the xposed framework but like OP I don't know which modules to use to get a USB BT dongle working. Any help greatly appreciated!
I definitely may be wrong but I assumed he was referring to the Xposedmtc module (http://forum.xda-developers.com/showpost.php?p=54334741) in the OBD settings where you specify the string. Though I assumed this only worked for OBD devices. I tried using it to pair an iRadar device with mine but was unsuccessful.
Oh, poop. Thanks all the same. Will keep an eye on this thread and report back if I ever get anywhere! Could it be that these HU's are only Bluetooth 2.0 compatible? Every device I've seen seems to be 3.0...
Hmmm. I'm thinking of getting a cheap wired USB numberpad (they're like £3) and using it with a keyboard mapper like this one:
https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
and this list:
http://developer.android.com/reference/android/view/KeyEvent.html
Oh and this is as much a note to self as anything!
http://www.barbatricks.com/en/android-en/remap-ab-shutter-3-selfie-remote/
It's going to be ugly...but that's never stopped me
Bumping as I have interest too.
You guys are making this way too difficult. Check this out. It works great on my joying.
http://m.ebay.com/itm/Car-Steering-...ayer-Bluetooth-Phone-/151832759268?nav=SEARCH
Anyone has found which xposed bt module the op was talking about ? I have already bought the bluetooth remote but I can't connect to it. (Works on my phone)
Also bought a Satechi® Bluetooth Button Series (Media Button) for use with my Joying unit but alas no success, so bumping this thread to see if there is any progression.
@dcmtnbkr are you able to show a quick video of your unit in action?
For the people that have gotten their bluetooth "remotes" to work, can you simultaneously also pair your phone and perform calls?
dcmtnbkr said:
You guys are making this way too difficult. Check this out. It works great on my joying.
http://m.ebay.com/itm/Car-Steering-...ayer-Bluetooth-Phone-/151832759268?nav=SEARCH
Click to expand...
Click to collapse
I bought much the same device but it won't directly connect to my HU. The HU will connect to my phone and my phone connect to media controller so I know all the devices work. Do I need a Droid program to allow access directly to the HU which is playing music from a USB flash drive.
Main problem is HU has panel controls for volume but cannot skip a song with going into player program. I use the display for my engine management gauges and don't want to keep getting out of program just to skip a song I don't like.
jim
I'm familiar with the one you're talking about, it's not the same thing.
I found another one that would work and is less intrusive.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/222631804601
Trying to pair a PS4 controller through Bluetooth and it's not working on my note 10 plus. It pairs fine but the phone seems to receive no input from it. Trying to unpair the controller hangs and never finished disconnecting. If I turn off the controller, the phone still thinks it's connected. Turning off Bluetooth takes a minute or so as well.
It works perfectly fine on my wife's s10 plus, and after it failed to work on my note 10 I tried pairing it with my note 8 for the first time and it also worked perfectly. I was really looking forward to using Samsung Dex with my living room TV and the PS4 controller to play emulated games.
Hoping this is a software issue that can be fixed and not a bug with the Bluetooth radio on my phone. My gear fit 2 paired fine and works great as far as I can tell. My headphones work fine through bluetooth and so does the bluetooth/aux adapter in my car. So it leads me to believe it could be software issues. The controller works fine on everything else.
I checked for updates and there was an Android update from Verizon but it did not fix the issue.
Also the controller works if I hook it up to USB via the USB C adapter included with the phone but the input is all wonky. Shoulder buttons are start and select, up is triangle, etc. I know there's ways to alter the input to fix that but it works perfectly by default on bluetooth on my other two Samsung phones.