Has anyone been able to do this since the update. it seems to try then reverts back to off. using att version
Related
I got nexus S in December 2011 in anticipation of ICS(still waiting for official update. that's a whole other issue). Out the box I was on version 2.3.3 and my wireless tether work perfectly fine. I saw that I could do a manual update to 2.3.6. I did notice at that time that the initial 2.3.6 had tethering issues. A new build was put out 2.3.6 build GRK39F that was supposed to fix this issue. That was the one I downloaded. Now when I turn on my hotspot my tablet sees it, connects to it. When I go to open a browser or try to check email, I get connection error due to no connection. Can anyone help with this issue?
I got nexus S in December 2011 in anticipation of ICS(still waiting for official update. that's a whole other issue). Out the box I was on version 2.3.3 and my wireless tether work perfectly fine. I saw that I could do a manual update to 2.3.6. I did notice at that time that the initial 2.3.6 had tethering issues. A new build was put out 2.3.6 build GRK39F that was supposed to fix this issue. That was the one I downloaded. Now when I turn on my hotspot my tablet sees it, connects to it. When I go to open a browser or try to check email, I get connection error due to no connection. Can anyone help with this issue?
Is wifi direct disabled by Samsung for the Skyrocket? Coworker and I are on ICS 4.0.3 (ICSMOD5) and can connect but when we try to send a file,pic or anything it doesn't display his device as an available option.
Really tired of having to pull out my SD card to send files.
same problem on my end except it won't fully connect either. just detect other devices. probably just an early version bug.
Maybe. I don't remember if this was available back on 2.3.6 or not.
We do have wifi direct cert but is samsung disabling this?
http://certifications.wi-fi.org/pdf_certificate.php?cid=WFA12015
i believe it was.
at least 2.3.5 it was.
Switched to a few different roms with the same results. Even tried to mix and match ICS roms with coworkers and we still can't get it to do jack.
Hand to face moment..
SOLVED: Disable the data and reconnect. It wasn't allowing the send I think because the LTE was still on. Works fine now.
Doing a Quick Poll to see if anyone on Straight Talk Wireless has Pandora working over LTE/3G. About a month or so ago I noticed that Pandora has become basically useless on my phone over LTE/3G. It will not load and play any songs unless I put the phone in airplane mode then take it off airplane mode for every song. I have had this problem on both of my N5's that are completely stock running Android 5.0.1.
nexus 5 on 5.0.1 + Pandora + straight talk = headache
Having same problem with the same setup. I did not notice the problem until the factory update. Not sure if it is a Straight Talk issue or an issue with the way the new os handles pandora's requests for data via cellular. I've thought about downgrading the is to see if that helps. Seemed to work fine on 5.0 before the ota update
rturkin1 said:
Having same problem with the same setup. I did not notice the problem until the factory update. Not sure if it is a Straight Talk issue or an issue with the way the new os handles pandora's requests for data via cellular. I've thought about downgrading the is to see if that helps. Seemed to work fine on 5.0 before the ota update
Click to expand...
Click to collapse
If you downgrade please let me know if it works.
Pandora updated their app today and it is now working just fine
Anyone have a link for the "modified" Pandora 5.7 thanks
Has anyone else noticed the NFC refuses to switch off, since Android 6 already.
Never mind what option in settings related to NFC I tried, always stays a dull / softer blue of other active options like sync or gps ...etc ...
In NFC settings menu, the on off switch is grey and locked to only on, so either my phone hates Tmo firmware or they have a bug they refuse to fix.
I flashed old, new, emergency restored with smart switch, tried G930U Tmobile versions and today just snapped. Talked to Tmobile and they refuse to accept they have firmware issues.
I tried other firmware and the NFC works perfectly in those firmwares.
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
truwrxtacy said:
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
Click to expand...
Click to collapse
Bluetooth is an intermittent issue with Pixel and Oreo. Google is aware and apparently added a fix in most recent update (November).
Fortunately, I have had no issue with Bluetooth and Oreo on my Pixel.
Concerning downgrade, you can always flash any factory image.
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
truwrxtacy said:
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
Click to expand...
Click to collapse
Wasn't aware you had Verizon's version. You may want to check with Google Forums concerning the Bluetooth issue. Best wishes!