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
Related
I received the ota jelly bean update 4.2.x build 10.6.1.8. All seems well except for one issue, which for me is a major issue.
The micro hdmi out port always displays at 420p, i've tried everything I can think off to get it to change. There is nothing in settings to change resolution or any hdmi settings.
Prior to the update it worked great connect the micro hdmi cable and I could play videos with dice player or bsplayer. I would get highest possible resolution, I am using the same display device that I've used for the past year, projector with hdmi. Projector is ok as I hooked another hdmi device and works fine.
So any ideas on how to fix hdmi issue ? If no fix how can I drop the back to the previous build ?
Would the new 10.1 cm rom use hdmi out ok, or anyone have suggestion of another rom that hdmi out works ok ?
I've tried rooting but have run into another problem I'll post as separate issue.
Asus says factory reset, did not work.
I can confirm the problem, I hope it's a bug and not a "feature" because the update makes hdmi output useless.
tonyjsan said:
I received the ota jelly bean update 4.2.x build 10.6.1.8. All seems well except for one issue, which for me is a major issue.
The micro hdmi out port always displays at 420p, i've tried everything I can think off to get it to change. There is nothing in settings to change resolution or any hdmi settings.
Prior to the update it worked great connect the micro hdmi cable and I could play videos with dice player or bsplayer. I would get highest possible resolution, I am using the same display device that I've used for the past year, projector with hdmi. Projector is ok as I hooked another hdmi device and works fine.
So any ideas on how to fix hdmi issue ? If no fix how can I drop the back to the previous build ?
Would the new 10.1 cm rom use hdmi out ok, or anyone have suggestion of another rom that hdmi out works ok ?
I've tried rooting but have run into another problem I'll post as separate issue.
Asus says factory reset, did not work.
Click to expand...
Click to collapse
I can't give you a fix as I don't have 4.2 yet.
I don't know your previous built so I'll give you instructions and you use the build you wish.
I'll use 10.4.2.18 as an example. Unzip Asus firmware once and put the new zip file on your internal sdcard wait if no response power down. Repower you should get the update triangle as with an ota. Accept and wait for results. I have used this to update and downgrade as well with success.
Good Luck!
no crop /scale
hi there!
so let's try my school-english....
since the last update a few days ago to android 4.2.1 i have almost the same problems with hdmi -out!
bevore the update, for example videos from the youtube-app in 1080p came to the tv in full-screen and 1080p - AND the tab-display became black - until i tapped on it for re-activating. In the status-bar there was the hdmi-button with two options: scale or crop. in one of this two cases i only saw the video on the tv in full screen, in the other option i could see the status-bar additional on the tv. I liked to use the full-screen without status-bar.
so thats history now!
since the glourious update, nothing of this works: no more hdmi-option in the status bar, only the information. no fullscreen, but the same picture like on the display-including BOTH status-bars (on the top and -hmmm- on the "floor"), and the whole picture does not fill the tv-screen. and the display of the tab doesn't get black anymore.
that's bad. very, very bad, 'cause using the tab via hdmi in 1080p to tv is one of my main use.
can anybody help, plz?!?! i hope there is a solution without "down-date" to 4.1.x!
sry 4 my bad english
After the 4.2.1 update the tf300t has the same problem of the nexus 10:
http://code.google.com/p/android/issues/detail?id=40225
Yeah, this really sucks, can't even get the audio now! I regret that i updated to 4.2.1. Hopefully the developers will notice this and update the current version.
Well mine doesn't even work so mehh..
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
Only: 72 people starred this issue and may be notified of changes. And it's listed as enhancement because the Nexus 10 never had what the TF300 has lost.
Surely it's a bug and not a new feature request for TF300 users, and should be put to Asus not Google? Doers more people "starring" an issue increase its urgency?
And does it work with cm 10.1 ?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
It's a known issue on 4.2.1 that afflicts more than just the TF300T. It's why I'm still on 4.1.1 and the original JB bootloader.
So three months and no fix ? Does 4.2.2 offer anything worth updating or is it mostly fluff plus this bug?
Searched around google, xda, similiar threads, couldn't find any help, so i finally decided to make an account and look for some help.
I recently updated from my stock GS3 to CM10.1 RC5, and paired with NovaLauncher, i love it. But i ran into my first real problem today, and havent been able to find a solution. I have a logitech wireless headset (Model: H800) that i use sometimes for making calls where i need to use both hands while on the phone. Ive always used bluetooth to connect my headset and phone and it worked splendidly. This is my first time trying to pair the devices since upgrading to CM10.1, and my phone now will not recognize the headset. I cant connect them through normal wireless, so im not sure what to do. Will updating to the new 10.1.0 fix this? Is there a patch somewhere i havent found? Any help would be appreciated.
Relevant info:
Verizon Galaxy S3
CM10.1 RC5
Nova Launcher Prime
Logitech H800
Bluetooth not connecting for the 2 devices.
I have to go to the store, so i wont be able to respond right away, but ill be back in a little while if anyone needs any more info/has questions. Thanks for looking!
Bluetooth hasn't worked quite properly for a while in AOSP. I went back to TW for that reason.
If you want AOSP and want fully working Bluetooth I suggest SLIM version 4.2.2. Also don't update the kernel from stock on SLIM.
Sent from my SCH-I535 using Tapatalk 2
cuban11182 said:
Bluetooth hasn't worked quite properly for a while in AOSP. I went back to TW for that reason.
If you want AOSP and want fully working Bluetooth I suggest SLIM version 4.2.2. Also don't update the kernel from stock on SLIM.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks!
there is a major bug on jellybean with this tablet where the otg will stop working and you have to reboot to fix the problem, can a app like USB OTG Helper get around this problem?
and please don't reply and say your otg works fine, you are not helping me by saying that, i want a solution & help with this problem, not a "works fine for me, not sure what you are talking about herpy derp" its really annoying and doesn't help my cause, just don't reply if you are going to say that.
so anyways, anyone installed this app on jellybean and have no lockups with the otg? please post on this topic, or if you know any other solutions or apps that can help that would be nice, just that i want to update to jellybean to get the feature to turn of notifications for apps, i get spammed to death by it and its really annoying. if nothing comes from this topic then i will just have to stay on ics till 4.3 or 4.2 comes (if that ever happens that is)
HUYI said:
there is a major bug on jellybean with this tablet where the otg will stop working and you have to reboot to fix the problem, can a app like USB OTG Helper get around this problem?
and please don't reply and say your otg works fine, you are not helping me by saying that, i want a solution & help with this problem, not a "works fine for me, not sure what you are talking about herpy derp" its really annoying and doesn't help my cause, just don't reply if you are going to say that.
so anyways, anyone installed this app on jellybean and have no lockups with the otg? please post on this topic, or if you know any other solutions or apps that can help that would be nice, just that i want to update to jellybean to get the feature to turn of notifications for apps, i get spammed to death by it and its really annoying. if nothing comes from this topic then i will just have to stay on ics till 4.3 or 4.2 comes (if that ever happens that is)
Click to expand...
Click to collapse
What is otg
Could you tell us what the model number of the tablet is, root status, and software version?
I am having the same problem. However, the issue is not universal, i.e.: not all notes suffer from this problem. Sofar, it is not even clear to me whether the problem is hardware or software related. E.g.: my Note has Android 4.1.2 installed and USB only works once after a reboot (that is with the official Samsung adapters). I did try my adapters with a different Note, where they worked perfectly, but that tablet was running 4.1.1.
I have not tried OTG Helper, as I do not want to root my tablet (too risky with possible curious little fingers around), but I have just received a return ticket from Amazon Germany for a repair and/or replacement. If the replacement works, while running 4.1.2, I am much more inclined to call this a hardware failure, in which case no helper app can save you. I shall keep the forum informed...
CMNDR said:
Could you tell us what the model number of the tablet is, root status, and software version?
Click to expand...
Click to collapse
wifi model ice cream sandwich.
karel jansens said:
I am having the same problem. However, the issue is not universal, i.e.: not all notes suffer from this problem. Sofar, it is not even clear to me whether the problem is hardware or software related. E.g.: my Note has Android 4.1.2 installed and USB only works once after a reboot (that is with the official Samsung adapters). I did try my adapters with a different Note, where they worked perfectly, but that tablet was running 4.1.1.
I have not tried OTG Helper, as I do not want to root my tablet (too risky with possible curious little fingers around), but I have just received a return ticket from Amazon Germany for a repair and/or replacement. If the replacement works, while running 4.1.2, I am much more inclined to call this a hardware failure, in which case no helper app can save you. I shall keep the forum informed...
Click to expand...
Click to collapse
if it was a hardware problem then my otg adaptor wouldn't work on ics would it? it's a software problem on jellybean, hence the reason i created this topic.
i've found solution to the problem and will leave this for anyone who needs it, basically sixaxis app and a dual shock 3 controller and root, you only need to connect the usb otg once and it registers the mac code from the controller with your tablet, after that you can play wirelessly without cables so the otg problem is completely bypassed, i'm happy because i can finally leave ice cream sandwich behind and enjoy jellybean on my tablet finally, i just wish someone told me this ages ago and i wouldn't have been stuck on ice cream sandwich for so long, yay! time to celebrate lol
started a bug report with android. Please help get this fixed
I started a bug report for this with android. Please go and star it for importance so that it gets fixed. If you got it working please go and say what you have/did to have usb otg working with 4.1.2.
"https://code.google.com/p/android/issues/detail?id=61264&thanks=61264&ts=1382289634"
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
Hi everyone,
I've been using a bluetooth keyboard (iClever BK03) with my Samsung J5 on Android 7.0 without any problems, but when I switched to the Samsung S7 on Oreo, it doesn't work. It either says it connected and doesn't do anything, or it says it can't connect. I've tried everything in the system itself. Is there a way I can make the phone recognize it?
Nikolakv said:
Hi everyone,
I've been using a bluetooth keyboard (iClever BK03) with my Samsung J5 on Android 7.0 without any problems, but when I switched to the Samsung S7 on Oreo, it doesn't work. It either says it connected and doesn't do anything, or it says it can't connect. I've tried everything in the system itself. Is there a way I can make the phone recognize it?
Click to expand...
Click to collapse
The keyboard Bluetooth connection standard is 3.0 and the S7 is 4.2. Its often the case that devices are not backward compatible. Check iclever website for a Bluetooth firmware upgrade.
Also worth noting that devices will be moving away from Bluetooth when the new short range WiFi standard is rolled out.
cooltt said:
The keyboard Bluetooth connection standard is 3.0 and the S7 is 4.2. Its often the case that devices are not backward compatible. Check iclever website for a Bluetooth firmware upgrade.
Also worth noting that devices will be moving away from Bluetooth when the new short range WiFi standard is rolled out.
Click to expand...
Click to collapse
Makes perfect sense, thank you!