So i've done the six axis process with my s3, it was successful several times. Currently i'm running stock 4.2 rooted on my nexus 7. I've downloaded the pairing tool for my pc, changed the bluetooth adress of my controller to match my tablet. HOWEVER whenever i go to "start" in the app on my tablet it does the "attempting connection type 1 and then 2" Sits there for a while and never pairs to my device. I'm also seeing similar people having this exact issue
"This app is the greatest thing to happen to Android. It does it all. The touch emulation is fantastic. I really can't say enough good things about it. Buy it! You'll definitely be glad you did."
same thing happens to me and it messes my wifi up. Is this a bug we have to deal with until app dev fixes it or has anyeone heard of a work around?
I'm always able to find an answer in a different site shortly after i post. someone posted this...
I emailed the dev, and he sent me an email yesterday, and he said "I'm aware of this issue and hope to have a fix soon. Android 4.2 has introduced a new Bluetooth stack, so it will take some time to rewrite the sixaxis driver. I hope to have a fix within a week."
I'm in the same shape. This is the only reason I rooted my Nexus 7. I'm not going to roll back to an earlier image. If this isn't fixed in a week or so, Im going to restore my N7 to factory.
I paired my N7 with my mac and got the BT address. I used the mac sixpair app and wrote that address to my PS3 controller. Then I tried the Sixpair Controller test, but no joy via BT or USB. Hopefully this is fixed soon.
I heard that bluetooth was broken with 4.2 :[
Locklear308 said:
I heard that bluetooth was broken with 4.2 :[
Click to expand...
Click to collapse
What do you mean?
Other Question: What means the Connection Type? What is the difference between 1,2,3?
Greetings
OT: Why can´t I edit my signature in profiles?
Hi, everybody.
I recently got an LG G Pad 8.3 as a present and, instead of retiring or giving away my Nexus 10 I decided to give it a second life as an emulator machine.
I bought an iCade Core, downloaded Mame4Droid and... nothing. I can't pair the iCade with any of my Android devices (LG G Pad, LG G2 or Nexus 10). It asks for the pairing code but it's not recognised (every button in the iCade is supposed to be a number while you are pairing).
When I try to pair with my wife's iPad Air or my son's iPad 2 it works flawlessly (it doesn't ask for any code, 'though).
I'm currently on 4.3. I read somewhere that 4.2.2 broke Bluetooth for certain devices, and was ready to try a downgrade to 4.1.2, but then I remembered that the N10 shipped after that
Has anybody had any luck trying to make the iCade work? I don't mind having to flash whatever firmware, since I've everything up and running in the new tablet. I'm willing to go to 4.4, 4.4.2, back to 4.2.2... But I'd prefer to know in advance if there is any solution.
I've read people having success with an app called Bluez IME, but I keep getting a "bt connet socket error" or something like that.
Any help would be greatly appreciated. Thanks in advance!
Edit: Nevermind. After days of trying without success, I followed the instructions in this thread for the Nth time and it worked!
Has anyone tried and succeeded at pairing the nexus remote with another device? Just out of curiosity.
I'd love to have one paired to my phone.
Yeah, it works on the Forge TV. It probably works on any Android device as well.
Amazon's Fire TV remote used to work on other devices... but with their OS updates, they released remote firmware updates that seem to have disabled it working with anything but Amazon products.
Unless there's a pairing trick I don't know about, it didn't work with my moto x. I'll try some other devices later
I paired it with my LG G2 device running Android 5 and it worked.
I got it to work once I totally unpaired it from my NP. I don't know why I didn't think to do that first.
Thanks all!
I can't cast from Ipad, android phone or google chrome anymore. Device is not showing up as a casting device anymore. :crying:
Anyone else with this issue?
The same for me. The Chromecast is still working, but the NP is not. I've also did a factory reset but the result is the same! The Nexus Player is not found in the device list in any of my devices.
I can only repeat what was said before me. Cast shows 'no devices available'. Also tried a factory reset since that is mentioned for earlier versions of android. But that did not work for me also.
Both of mine updated to 6.0. I was able to cast yesterday evening.. There was an update to the cast app about 2 or 3 days ago. Is your app up to date?
Only the Google Play Music sees the Nexus Player, but an atemp to connect to it fails. I've tried reinstalling the Google Cast Receiver, but there is no change.
The same for me. The Chromecast is still working, but the NP is not. I've did a factory reset but it did not help. Only the Google Play Music sees the Nexus Player, but the connection fails.
Same problem for me
The latest google cast receiver app update broke casting for me on 6.0 and 5.1.1... the only app i had which found the nexus player was hulu. YouTube, netflix, bein sports were not finding the nexus player. Try uninstalling the update
Anyone have casting working since the 6.0 update? If so, what version of the Google Cast Receiver do you have?
No casting for me since yesterday. I'll check to see if I am on 6 later.
Casting from ios without a problem. make sure you guys have the updated casting app in the playstore.
EldarH said:
The same for me. The Chromecast is still working, but the NP is not. I've did a factory reset but it did not help. Only the Google Play Music sees the Nexus Player, but the connection fails.
Click to expand...
Click to collapse
Yea, same here, GP Music is the only app that sees the NP. Can't actually get a cast attempt to work though. But not even YouTube is able to see it. Netflix can't either. GP Music just got a recent update. Maybe that helped it to at least see the NP?
When I try and cast things using YouTube and such, nothing running 6.0 is seen.
Time for 6.0.1.
This is shameful for Google. You can't miss a bug like this, unless you totally failed to test.
And I have the latest Chromecast app, always have since it was released.
Sent from my Nexus 10 using Tapatalk
Casting worked for me for a week after updating to 6.0.
My devices no longer see the Nexus Player as a cast device after installing the most recent Oct 13 update of the Google Cast Receiver app, version 1.16.43955.
I've tried clearing the app data and uninstalling the update (reverting to 1.15) and there's been no change.
The same goes for me, when can we expect Google to solve this, within a reasonable time?
I have got the same issue here on my sony android tv. I was able to cast few days ago, but not now.
Please report back to this thread if someone finds a solution.
In the same boat. Purchased the NP yesterday and was able to cast last night while it was on 5.1.1. This morning I find that the NP updated to 6.0 and now it does not show up as a casting option. Didn't have much time to troubleshoot this morning, but did a factory reset and that had no effect.
Probably not related to marshmallow, my android tv is still in 5.1.1
Same problem. I will attempt to flash 5.1.1 back tonight to see if all is good. Isn't Google testing it's OS? This is some major issue they introduced with 6.0 on the Nexus Player (and possibly all of the Google TV devices running 6.0).
cescman said:
Probably not related to marshmallow, my android tv is still in 5.1.1
Click to expand...
Click to collapse
Interesting. When did yours stop working?
ETA: Your case is the only one that I have seen that had the trouble at 5.1.1. Everyone else (including me) had the issue in conjunction with the update to 6.0
No Casting for me after upgrade
No Casting after upgrading to 6.0.. Tried Factory reset, Uninstalling updates to Google Cast Receiver, Clearing Cache & Data
I am trying to turn my shield tablet into basically an android TV box. I am trying to get Prime, Netflix, and Cinema apk to play on tablet and cast to Roku box. I used to be able to do it no problem. I do not know what changed. I am running Triodexe 15.1 Lineage. I am trying to cast to my Roku Ultra. I know your devices have to be on the same wireless network which they are. If it isn't the tablet doing it the only thing I can think of that possibly changed is ROM and now my wireless network just has one network name for both 2.4 and 5. This new router just sets up one network and prioritizes devices automatically for which network the device will use. As far as ROM I cannot remember which one I had it working on. Is anyone else able to confirm casting is working on this app?
Update - When using Lineage I could not get my PS4 to connect via Bluetooth. This was in addition to not being able to use the cast button. I ended up finding a solution to the casting problem. I downloaded Cast to TV-Xcast from the Google play store once it was setup I was able to detect my wifi connection and get it setup. I decided to experiment trying get the PS4 controller working. I seen Magisk actually has a module to add support for the PS4. I installed it and it did not work. Therefore, I decided to try another custom ROM. I am now running ASOP 6.7 with Pie Android 9. I still have the cast problem on it but my controller now pairs. So, it took some monkeying around but I solved those issues.
It seams like we have a couple good ROMs for this device which are close to working perfectly and then the people building them stop. I know Lineage had official builds of 14.1 and 15.1. Somewhere there has to be on o hei builds floated around that is stable. Then, the proper patches can be applied to it. I have tried looking into building images myself but that is over my head. I have a PC I just built that is more than fast enough. I have a Ryzen 7 3600, 32gb of RAM, and more than enough SSD space. I wish someone could connect to my PC and remotely build images, or they could remotely help setup my PC and show me how to do it. Then, I would keep the forum updated with new builds. If I could figure it out I would help out building images for other devices as well.