Hello Recently got my shield and after rooting it (properly, Followed the xdadevelopers YouTube video) My wifi just goes in and out of use. And if I try to reconnect it just sticks at "Connecting..." It also says I have a Bar of wifi, when i'm literally next to it. I've tried two routers and no hope. Before the root it did work like a charm. Anyone else having this issue and/or have any idea how to fix it? - Edit: I believe it's my modem, but i'm not positive. (It's been causing issues all month...)
SayreSkaggs said:
Hello Recently got my shield and after rooting it (properly, Followed the xdadevelopers YouTube video) My wifi just goes in and out of use. And if I try to reconnect it just sticks at "Connecting..." It also says I have a Bar of wifi, when i'm literally next to it. I've tried two routers and no hope. Before the root it did work like a charm. Anyone else having this issue and/or have any idea how to fix it? - Edit: I believe it's my modem, but i'm not positive. (It's been causing issues all month...)
Click to expand...
Click to collapse
Root did not affect my wifi.
My concern now is to keep rooted after the big update of 28th october. I want to use my PS3 Dual Shock controller wirelessly with the new "console mode"!!!
king conan said:
Root did not affect my wifi.
My concern now is to keep rooted after the big update of 28th october. I want to use my PS3 Dual Shock controller wirelessly with the new "console mode"!!!
Click to expand...
Click to collapse
I forgot Nvidia is releasing that update! Well I did figure out what was my problem anyways... It's my POS modem. (tried at friends house and it did work fine)
Asking for help from Shield controller owners.
Have you updated the software for the controller? Is the controller still working after the update?
I updated my controller when prompted last two weeks, and it went wonky. RMA'd it and got a new replacement today, and afraid to update it again.
The notification is killing me, really.
No problem when mine did the update.
RaySorian said:
No problem when mine did the update.
Click to expand...
Click to collapse
thank you for your reply.
may I please know when did you update it? i contacted nvidia and they are aware of this issue since they have seen a few reports on it. they recommend to skip this update and wait until the update for the tablet is released. the update for the controller should follow closely afterwards.
Within the last week - week and a half. Did the update right after getting Android 5.0 installed.
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
https://forums.geforce.com/default/...-35-min-40-sec-consistently/?offset=4#4777262
Streaming stops randomly at a certain time, I've resetted it but that didn't help.
Yes I am having this problem too. I have raised the issue with nvidia and twitch but not heard back from either.
This is a big problem for me as I stream nightly but now fed up of having to restart it every 35:42. Not sure who is to blame but I know the update has caused the problem as it was fine on 5.1.1. I hope who ever has to fix it does it quick.
ArcaneDroid said:
https://forums.geforce.com/default/...-35-min-40-sec-consistently/?offset=4#4777262
Streaming stops randomly at a certain time, I've resetted it but that didn't help.
Click to expand...
Click to collapse
I have this problem too!
I have upgraded my SHIELD Tablet K1 to Marshmallow once opened from its box, so I can't tell if it's an another bug of the Marshmallow update, but I think that this bug is because of this update....
Elpatii said:
I have this problem too!
I have upgraded my SHIELD Tablet K1 to Marshmallow once opened from its box, so I can't tell if it's an another bug of the Marshmallow update, but I think that this bug is because of this update....
Click to expand...
Click to collapse
It is, I downgraded to 5.1.1 and I'm now able to stream forever lol
ArcaneDroid said:
It is, I downgraded to 5.1.1 and I'm now able to stream forever lol
Click to expand...
Click to collapse
Ok... happy to see your feedback, thanks
I wonder if I stay with Marshmallow and wait a fix from NVIDIA or if I downgrade to Lollipop..
In case anyone still has this problem, Ive talked to someone and it will be fixed in the next OTA
https://twitter.com/ManuelGuzman/status/692552921226027008
Hello.
I have come across an error on my brand new Mate 9, where the wifi simply wont turn on.
Firstly, Yesterday i received the phone and the WIFI was seemingly working ok. Which would suggest it may now have arrived faulty.
But last night, i completed the setup process. Installed my apps as you do. Updated all existing apps and updated to the most recent android version in the update section.
After a while i noticed i was on Mobile Data and not WiFI was odd as i sit 2 meters from my Router.
I attempted to connect to wifi but the option wont even turn on. I have contacted my provided who are willing to have it looked at but i will be without a phone for up to 2 weeks. So im trying to trouble shoot myself.
Below are 2 videos of me trying to turn WiFI on. First one is trying through settings. 2nd one is after a factory reset indicating it may not be a settings issue.
https://youtu.be/Q-VfQrMA-4s
https://youtu.be/g8cpAHd3nBU
Any help would be appreciated.
Regards
Update messed up?
Can you apply update again?
Could be the update. Device says its up to date.
Unsure if you can to roll back.
Hi guys, I have the same problem with my mate 9, also I have this problem from 3 months ago, and I not found any solution, it's exist that?
Anyway I have problems also with overheating, battery fast drain, touchscreen.... I really I feel like I pay for a **** my money... Cheers
I have a same trouble, when I got update via OTA on my L29C636. Updated to B181, wifi and bluetooth doesn't work.
I have try to flash the same firmware with dload method, and it can roll back with dload method (I've try to flash B156 firmware)
So I think that we can do is waiting for the next update (maybe on Oreo firmware)
I saw your video. The same happen to me. Please, If you find the way to solve the problem, sahre it!!!!! Good luck.