Hi
Can't pair my PS3 controler with my brand new 32Gb 3G
Tab Already rooted, can't get bluetooth address at the bottom of Sixaxis app, so i can't pair them together...
Don't know what's wrong...
I'm sorry, it seems, "sixaxis controller" isn't compatible with Android 4.2. On 4.1.2 it worked like a charm on my N7.
Since there are alot of issues with 4.2 (especially with Multiuser) for me, I downgraded to 4.1.2 today and I'm absolutely happy again.
Regards!
Related
Hi all
Well I know this is a bit of an odd one but thought would be very cool if anyone had any idea how to do this
I've got an old fully functional k-jam in the cupboard and was thinking of buying a Logitech Dinovo mini Bluetooth keyboard for my Playstation 3, when I thought to myself hey the K-jam has a mini keyboard and bluetooth couldnt these somehow be reprogrammed so that the keyboard output could be output via bluetooth to be used by the PS3.
Would be brilliant if anyone has any ideas
This would be pretty damn cool
so anyone have any ideas how this could be done
Got this working upgrade my ROM to the CR86 Touch HD2.1 ROM installed Mobile remote and it works perfectly as a bluetooth keyboard on my PC, Netbook, and PS3. £99 save on the Logitech Dinovo.
It's good to hear that man
Hello everyone,
Just got my A7, so far I'm pretty happy with it. However, I do have one issue and wanted to see if it's just me. I've already searched the forums to no avail so I apologize if I just missed this. Are there any Wiimote pairing apps that work on this device? I've tried four of them but they either disconnect right away or force close upon pairing. I have the same apps working fine on my droid 2 global.
I'm running Dexter's mod 1.3 along with more recent update patch. BT seems to be wotking fine in general and I've enabled the proper input methods.
Any ideas?
Bump. Specifically, has anyone tried pairing a Wii remote with the official Elocity update from a few days ago which is supposed to include better bluetooth compatability?
I bought a wii remote to use but returned it. It seems the elocity will not support it.
I have the Nexus 7 with 3G running the latest Android 4.2 stock/rooted. I've been trying to connect my Motorola Bluetooth Android Keyboard and it pairs fine, shows it's connected but nothing works...no typing, home button...nothing. I tried it on my VZN Galaxy Nexus running Jellybelly 10.2 (also Android 4.2) and it also isn't working. I did some research and saw that 4.2 might have broken bluetooth connections? Is this true? Is there a work-a-round or do we just have to wait for Google to send the update?
Thanks
Should work fine. I've got a Nexus 7, Jelly Bean 4.2, rooted, Motorola Android Bluetooth keyboard and mouse.
All paired and working no problems. Try switching off the keyboard and then reconnecting again.
kilowatt.xda said:
Should work fine. I've got a Nexus 7, Jelly Bean 4.2, rooted, Motorola Android Bluetooth keyboard and mouse.
All paired and working no problems. Try switching off the keyboard and then reconnecting again.
Click to expand...
Click to collapse
I did that about 20 times...still nothing...I tried changing batteries but they were from my tv remote...I'll try again tomorrow with brand new batteries...I just can't figure it out...frustrating...unless the keyboard itself is faulty? It used to work on my iPad about 4 months ago...
Well I tried new batteries and no go...it wouldn't work on my iPad either so it's not 4.2. Plus my Bluetooth mouse worked just fine. I just ordered a new keyboard from eBay so we'll see how that goes
Sent by an Android Guy using an iPad...
The Bluetooth stack was replaced in 4.2 to a new, standard conforming one from Broadcom. This is a good thing - long term.
Devices that were dependent on the BlueZ stack will have problems.
rmm200 said:
The Bluetooth stack was replaced in 4.2 to a new, standard conforming one from Broadcom. This is a good thing - long term.
Devices that were dependent on the BlueZ stack will have problems.
Click to expand...
Click to collapse
Thank you! I hope my new keyboard will work now! Lol
Sent by an Android Guy using an iPad...
Howdy all!
I'm running CM10.1-nightly and I've been trying to connect my inPulse SmartWatch to my N4, without success. It appears to pair successfully, but the client app never connects and I can't send any commands to it. Has anyone successfully paired their device with an inPulse watch? I wonder if it has anything to do with the changes in the bluetooth stack in 4.2.2?
jsylvia007 said:
Howdy all!
I'm running CM10.1-nightly and I've been trying to connect my inPulse SmartWatch to my N4, without success. It appears to pair successfully, but the client app never connects and I can't send any commands to it. Has anyone successfully paired their device with an inPulse watch? I wonder if it has anything to do with the changes in the bluetooth stack in 4.2.2?
Click to expand...
Click to collapse
I have the same problem too. I upgraded my Motorola Atrix 2 to 4.2.2 and also cannot connect. My Ubuntu netbook however has no problems. I'll reply back here here if I find anything, but I'm not too optimistic.
Hi guys. I emailed Alerta a while back about the compatibility issues with newer versions of Android. I emailed in February of this year...
"Good afternoon. I wonder if you plan to update the inpulse Android app to
run correctly on 4.2 Jellybean? I have tried several times after updating
my Nexus S to 4.2 but the app simply will not connect to my watch. I would
really like to be able to use the watch. I used it all the time before the
Android system update and I truly miss it.
As an added note, if it helps, I am running Cyanogenmod ROM's and have been
for years. Never had an issue with my watch connecting until 4.2.1. I would
try the forums but those have been taken over by bots and have become
pointless.
I will appreciate your reply, should I receive one.
Your paying customer,"
On March 01, 2013 I received this reply...
"Thank you for reaching out to us. We are not supporting further development on the inPulse Android app.
Best regards,
Asad"
Guess we can chalk it up to another wasted $100. Jerks.
Since i upgraded to Android 4.3 from 4.2.2 my ipega bluetooth controller has a big input lag. Its not usable anymore. Ipega work great with my NVIDIA shield and Samsung tab2. No input lag at All. Should i downgrade to 4.2.2. My nexus 4 is not rooted. Thanks for help.
renejr902 said:
Since i upgraded to Android 4.3 from 4.2.2 my ipega bluetooth controller has a big input lag. Its not usable anymore. Ipega work great with my NVIDIA shield and Samsung tab2. No input lag at All. Should i downgrade to 4.2.2. My nexus 4 is not rooted. Thanks for help.
Click to expand...
Click to collapse
It's a problem with your ipega bluetooth and 4.3 you can try a full reset and test again. There have been a lot of reports regarding the bluetooth and the wifi not working together, but I never had this issue. I use a LG bluetooth (the one I use for my PS3) and have no lag. My Jambox also works well. I have used the jambox via bluetooth while web browsing using wifi and had no problems also.
zcucurullo said:
It's a problem with your ipega bluetooth and 4.3 you can try a full reset and test again. There have been a lot of reports regarding the bluetooth and the wifi not working together, but I never had this issue. I use a LG bluetooth (the one I use for my PS3) and have no lag. My Jambox also works well. I have used the jambox via bluetooth while web browsing using wifi and had no problems also.
Click to expand...
Click to collapse
Finally it seem a problem with nes.emu only. Even erasing data and cache and reinstalling dont help. I use retroarch instead no lag at all