Hi!
When I try to pair my Rii GP-500 gamepad to my Lenovo P2, this restarts automatically. This doesnt happen in my Amazon Fire TV.
Im on stock S233 rom. No rooted, no bootloder unlocked. All stock.
Thx in advance!
Edit: Finally I managed to get working. Rii GP-500 has 3 or 4 modes to work with it. I changed the mode, then I paired and now it works like a charm! Thx!
I am having the same issues can you go into detail how you got it to pair thanks
Sorry, I tried to pair again but I had no luck, it doesn't work.
Related
Hi guys, has anyone had any luck getting the 360 wireless controller receiver to work with the N5? I've tried the various methods posted around xda for other devices but non of them work, has anyone any ideas? The Receiver is detected correctly as It's listed as a usb device but nothing happens when the pad is connected.
Edit: I've just tried it with my Galaxy Nexus and it's working fine, that's also running a kitkat ROM so could it be a kernel issue?
Interesting... I always thought it needed to be a wired controller. I'll have to try this out when i get home and report back.
I can't get it to work either. Tried following the guide by sleeplessninja.
Hello, I had a tab2 7" more than a year ago. I remember using mouse and other usb otg devices on it.
Then I sold it. I can't remember what rom was on it.
I remember usb otg notifications worked, telling something like "mouse is connected" etc
Now I got another one, it has custom rom installed but usb otg isn't working and was trying to figure out the new ROMs.
I tried lots of latest roms with no luck.
Kitkat ones are great, run smooth, but when I try to connect a mouse it doesn't work.
Then I read that on CM based roms native usb otg isn't working. One can browse usb pens with apps, but no luck with other devices.
I don't care about storage, I need mouse/keyb and other input devices working.
Do someone use USB mouse or keyboard? What rom/kernel?
I'm starting to think it could be ICS since it was soo much time ago?
Thanks,
Robert
rc87 said:
Hello, I had a tab2 7" more than a year ago. I remember using mouse and other usb otg devices on it.
Then I sold it. I can't remember what rom was on it.
I remember usb otg notifications worked, telling something like "mouse is connected" etc
Now I got another one, it has custom rom installed but usb otg isn't working and was trying to figure out the new ROMs.
I tried lots of latest roms with no luck.
Kitkat ones are great, run smooth, but when I try to connect a mouse it doesn't work.
Then I read that on CM based roms native usb otg isn't working. One can browse usb pens with apps, but no luck with other devices.
I don't care about storage, I need mouse/keyb and other input devices working.
Do someone use USB mouse or keyboard? What rom/kernel?
I'm starting to think it could be ICS since it was soo much time ago?
Thanks,
Robert
Click to expand...
Click to collapse
Mine is working perfectly smooth with Sungsonic ROM and Next Kernel.:good::good:
bbugger said:
Mine is working perfectly smooth with Sungsonic ROM and Next Kernel.:good::good:
Click to expand...
Click to collapse
WIRED ONES?
I know bluetooth ones work. I need to know about wired.
thx
bbugger said:
Mine is working perfectly smooth with Sungsonic ROM and Next Kernel.:good::good:
Click to expand...
Click to collapse
Thank you. With that combo I was able to diagnose a fault in the otg cable.
Repaired it and it works, now I'll try the other roms.
Both usb wired mouse and storage works perfectly with Sungsonic ROM v7 and Next Kernel 2.1.6
:good:
everything works fine on 4.4.x too. The fault was the damn usb otg cable.
Hello All,
In need of urgent help i am about to travel to Portsmouth today SUN 20th Apr 14,
and i am still not able to get my Note 3 SM-N9005 Android 4.4.2 rooted busy box, triangle away adaway super Su, to work on my APPRADIO 3 DA110.
the headunit has the handbreak bypass in.
i have the samsung MHL adapter inplace and charges the phone via the pionner external power pack.
i am getting 2 errors up on ARL which are Virtual device permissions (permissions set as readable,unwriteable)
and the other is Virtual device creation,
i have tried ARU and that doesnt do anything??
Bluetooth connects and i can make calls no problem...but this seems the only thing i can do.
PLease help a noob
im very new to rooting etc but so far have bricked the phone...touch wood
Bump
Sent from my SM-N9005 using xda app-developers app
laurenceroke said:
Hello All,
In need of urgent help i am about to travel to Portsmouth today SUN 20th Apr 14,
and i am still not able to get my Note 3 SM-N9005 Android 4.4.2 rooted busy box, triangle away adaway super Su, to work on my APPRADIO 3 DA110.
the headunit has the handbreak bypass in.
i have the samsung MHL adapter inplace and charges the phone via the pionner external power pack.
i am getting 2 errors up on ARL which are Virtual device permissions (permissions set as readable,unwriteable)
and the other is Virtual device creation,
i have tried ARU and that doesnt do anything??
Bluetooth connects and i can make calls no problem...but this seems the only thing i can do.
PLease help a noob
im very new to rooting etc but so far have bricked the phone...touch wood
Click to expand...
Click to collapse
It is an issue with stock kitkat.. Will not work. I have tried many of times.. I have ATT Note3.. I had to return the thing after the kitkat update for a 4.3 works like a champ. Something in the video driver causes flashing on the damn screen. Yes I never have any issues on 4.3. I really wish someone would figure this out. Could it be a firmware issue permission issue? Almost like the MHL driver doesn't want to play nice, yet it will work on my tv just fine with samsung OEM MHL2 adapter. Just not in the car with my Appradio 3.
mastamind said:
It is an issue with stock kitkat.. Will not work. I have tried many of times.. I have ATT Note3.. I had to return the thing after the kitkat update for a 4.3 works like a champ. Something in the video driver causes flashing on the damn screen. Yes I never have any issues on 4.3. I really wish someone would figure this out. Could it be a firmware issue permission issue? Almost like the MHL driver doesn't want to play nice, yet it will work on my tv just fine with samsung OEM MHL2 adapter. Just not in the car with my Appradio 3.
Click to expand...
Click to collapse
The flashing can be stopped by going into developer options and disabling hardware overlays, also seems to work by foring GPU rendering.
U need flash a permisive kernel and disable knox or flash a rom without knox if u are on kitkat .I have a s5 running moars rom I couldnt get the appradio 3 to work till I flashed kt kernel. I have the same issue with the screen flashing .ill have try dimlow_uk methods thanks
Did that end up working for you. Disabling the hardware overlays and GPU rendering. I still have not updated to kit Kat Kat since all is working still on jelly bean.
Omg i love you... Thanks haha i knew it was something in the dev options. Just didnt know what. My att note 3 working like a charm now thanks
I upgraded to the Lollipop 5.0.2 Stock firmware yesterday from KitKat - everything seemed to go smoothly but I am experiencing a problem with my Logitech Pro Keyboard.
I can scan and discover the keyboard, connect and enter the PIN and the keyboard shows up as being present, connected and an input device. However, no key presses are registered by the tablet at all from the keyboard. I have tested the keyboard with another tablet - a 2011 Nexus 7 running 5.1.1
Has anyone got this keyboard working with the stock firmware?
danburycollins said:
I upgraded to the Lollipop 5.0.2 Stock firmware yesterday from KitKat - everything seemed to go smoothly but I am experiencing a problem with my Logitech Pro Keyboard.
I can scan and discover the keyboard, connect and enter the PIN and the keyboard shows up as being present, connected and an input device. However, no key presses are registered by the tablet at all from the keyboard. I have tested the keyboard with another tablet - a 2011 Nexus 7 running 5.1.1
Has anyone got this keyboard working with the stock firmware?
Click to expand...
Click to collapse
Nope.... this seems to be a major bug with this initial release of 5.0.2 for the P900. I have the same with my Logitech Pro and also a Logitech K810.
From what I've seen so far no BT keyboards work except for Samsung (model unknown) where I've seen one report of it working.
Well, the issues with 5.0 and Bluetooth are universal, so I'm not at all surprised....
ShadowLea said:
Well, the issues with 5.0 and Bluetooth are universal, so I'm not at all surprised....
Click to expand...
Click to collapse
Bummer... Should we expect Samsung to address this issue in a future release, or are we stuck with an expensive cover with keys? (I'm just wondering if Samsung actually tracks those issues and if they are willing to fix it...)
Really too bad it works for the 'original' Samsung keyboard cover, if that were broken too it may have been a bigger incentive for Samsung to fix this BT problem
And I haven't seen keyboard issues with CM12 on the Note 12.2, so that makes me wonder if this is a Lollipop issue, I would guess it is more a Samsung problem. I remember the BT stack on my SIII being 'different', it didn't work too well with my car kit...
"....... or are we stuck with an expensive cover with keys?" It seems we are
COF4 for Canada and Cellular South with a different build date is now available so it'll be interesting to see if it has the same problems.
BOF2 is also now available for Switzerland but it has the same build date/time as the Netherlands build.... so much for country variations :silly:
Cheap Polaroid bluetooth keyboard working fine with 5.02 on a P900 here. Maybe this is Logitech specific?
netizensmith said:
Cheap Polaroid bluetooth keyboard working fine with 5.02 on a P900 here. Maybe this is Logitech specific?
Click to expand...
Click to collapse
what fw build have you flashed/updated to.... BOF2 or COF4 ?
BOF2. Just checked again and all is working well. Note that I did a full reset after flashing because clicking "Toolbox" in the settings->Device caused settings to crash. That might be something to try (I know it's a common suggestion and one that's a real pain to do but if that's the only difference between our devices then maybe try it).
netizensmith said:
BOF2. Just checked again and all is working well. Note that I did a full reset after flashing because clicking "Toolbox" in the settings->Device caused settings to crash. That might be something to try (I know it's a common suggestion and one that's a real pain to do but if that's the only difference between our devices then maybe try it).
Click to expand...
Click to collapse
Ok, thanks for the info.
I did a full reset after flashing as I wanted a clean build.
Same issue here
Installed 5.02 .. Logitech keyboard no longer working.
As I never use my tablet without a keyboard and supplies of the original Samsung keyboard are not exactly great ( at least in the UK and NL ) I have ordered a US keyboard from Ebay - Not ideal, as I will be using 3 different keyboard layouts each day, but I wanted to make sure that I got one before they all disappear.
Maybe something logitech should fix then given that Polaroid and Samsung keyboards work.
Sent from my D6603 using Tapatalk
JimMNH said:
Installed 5.02 .. Logitech keyboard no longer working.
Click to expand...
Click to collapse
Which 5.0.2 did you install? BOF2 (Dutch) too or the Canadian COF4?
Tonv said:
Which 5.0.2 did you install? BOF2 (Dutch) too or the Canadian COF4?
Click to expand...
Click to collapse
I installed the BOF2 - Dutch version.
Where can I download the COF2 version ?
EDIT: found it - downloading now - will try and report results.
My tablet originally came from the US - I wonder if North American versions have something different at the hardware or OS level that is different from European models ?
Tonv said:
Bummer... Should we expect Samsung to address this issue in a future release, or are we stuck with an expensive cover with keys? (I'm just wondering if Samsung actually tracks those issues and if they are willing to fix it...)
Really too bad it works for the 'original' Samsung keyboard cover, if that were broken too it may have been a bigger incentive for Samsung to fix this BT problem
And I haven't seen keyboard issues with CM12 on the Note 12.2, so that makes me wonder if this is a Lollipop issue, I would guess it is more a Samsung problem. I remember the BT stack on my SIII being 'different', it didn't work too well with my car kit...
Click to expand...
Click to collapse
It's Google's fault, actually. They messed up the Bluetooth protocols.
How come my.Bluetooth keyboard works on my note pro and my z3, both on lolipop? Also my Bluetooth speaker and my car both work fine with both devices. Can't be a.general lolipop bug surely?
Sent from my D6603 using Tapatalk
Just updated my P900 to 5.0.2 and my logitech keyboard does not work. I updated my US purchased tablet OTA if that helps.
Same on us version
Just updated to 5.0.2 on us bought tablet with us ota and yes logitech bluetooth keyboard will pair but no keys do anything. This is pathetic, why break things?
Anyone have a fix? If not can I go back to a version of android that actually works? If so, how?
---------- Post added at 01:09 AM ---------- Previous post was at 12:20 AM ----------
The logitech blutooth kbd does not work with the galaxy note pro 12.2 OTA (US) 5.0.2 update however it works fine with my nexus 4 running android 5.1.1. Point is that I can use the phone to act as a keyboard using a number of apps (for example im typing this through an2an remote 3.2.4)
You guessed it, the logitech keyboard is paird to the phone and the phone is running as a remote control keyboard and its working. There is some light lag (only some of the time) and at least I can get on with writing my document now. Wierd to be bouncing the keyboard off the phone to the tablet but thats better than not being able to use the keyboard at all.
The spesfic app im using on the phone has to be open in order to work so I couldnt use the phone for anything else (or have any other screen open on the phone) so this is not a long term solution however it will allows people to do some typing on the galaxy note pro with 5.0.2 and the logitech keyboard in the short term.
Absurd
Really, this has to be a joke. I have the same issue here. Did a factory reset fix it for anyone?
Tarps.nj said:
Really, this has to be a joke. I have the same issue here. Did a factory reset fix it for anyone?
Click to expand...
Click to collapse
I havent tried that yet but i agree its very disapointing. The logitech keyboard works fine on my nexus 4 running android 5.2.2 so its not an android thing, its a "we couldnt be bothered to test it" thing and unfortunatly samsung dont release updates very often so it could easily be 6 months before this is fixed (if its ever fixed). There are only a couple of keyboard cases designed to fit the 12.2 inch device so this will affect a LOT of people - I would have prefered to not update (and in future may hold of on updating) as everything was working fine before and now the keyboard I use every day no longer works, great work samsung.
This is the second or third time an android update has given me nothing I wanted and broken something I actualy relied on
Friends,
I have been trying desperately to get my Genius Bluetooth Mouse Navigator 900 to work on my Micromax P480 tablet which is powered by Android Kitkat.
There is no problem whilst detecting. The mouse is correctly identified as "Genius Bluetooth Mouse". The problem begins when trying to pair this device. The proffered options of "1234", or "0000" do not help at all. The communication is not established. And, an error message is displayed stating that the PIN provided is incorrect. I have also tried using "1111", "12345", "123", "000", and "111" as possible options. But these have been to no avail.
Pressing on the connect button provided underneath the mouse is also of no help. The communication is instantly disconnected on using this button with an identical error message.
The mouse, however, connects to Android Jelly Bean powered Samsung Galaxy DUOS 2 (GT-S7582) without any issues.
Any help would be much appreciated.
Thanks.
Sorry for bumping such an old topic, but did you try pairing after upgrading to Lollipop?
Ibbi786 said:
Sorry for bumping such an old topic, but did you try pairing after upgrading to Lollipop?
Click to expand...
Click to collapse
Would you believe it if I told you that Micromax does not seem to offer relevant updates to Lollipop for this model?
I am sorry, too, for responding late.
somnambulistic said:
Would you believe it if I told you that Micromax does not seem to offer relevant updates to Lollipop for this model?
I am sorry, too, for responding late.
Click to expand...
Click to collapse
I have lollipop currently installed, I've made a thread about it too. Let me send the link, wait.
EDIT: http://forum.xda-developers.com/showthread.php?t=3398406
Sent from my SM-T311 using Tapatalk
Seems interesting. However, upgrading to Lollipop at this point has taken a backseat for me insofar as this device is concerned. What I am more concerned is with the battery. In its stock mode, the tab does not offer much by way of battery backup. Thank you for sharing that guide. Will check it out as soon as I possibly can.