Whenever I am somewhere with a new network, my Tab is slow to recognize it. Sometimes the network will show up in the list of available networks for a brief moment, and then disappear before I can establish a connection. Other times I can connect by manually adding the SSID. Sent Sometimes turning the wifi off and then back on, or rebooting the Tab, works, but not always.
Most recently, I was in a place for almost an hour before it recognized the local network, even manually adding the SSID didn't help. The weird thing is, once it saw this network, it also saw several others in the neighborhood that previously were not shown on the list of available networks.
Once you I finally establish a connection, reconnecting to that network usually works without a problem.
Any thoughts?
Sent from my GT-P7510 using xda app-developers app
Try a factory reset or if you are in any custom rom, try reflashing other rom.
Factoryreset willerase all your data so watch out.
Tried a factory reset... Didn't fix it. Here's the strangest thing: if I bring another network into the picture, all of a sudden it recognizes all the nearby networks. For example, right now I am in a place with 5 or 6 networks. Couldn't see any of them, until I fired up my cell phone's teather app, at which point it recognized not only the cell phone teather network but all of the others as well. It's almost as if it needs a new network to come along and wake it up. Other times though, it is my cell phone teather network that it won't see!
Sent from my GT-P7510 using xda app-developers app
you need to mention if you have stock or non-stock, rooted or not, etc.
my best guess is that you are rooted and running a non-stock ROM. in this case, you should try another kernel. the wifi modules are the ones causing most of the problem, whatever the device. make sure you flash the proper wifi modules after the kernel!
otherwise... I would suggest to root. I heard all kind of crazy stories about our beloved Tab, so... don't fear trying different solutions until you get the one working for you.
okty2k said:
you need to mention if you have stock or non-stock, rooted or not, etc.
Click to expand...
Click to collapse
Stock, not rooted. That's what makes this so frustrating - I haven't messed with anything, and it still doesn't work right! I'm running the most current Samsung android distribution for the Tab 10.1.
I've been avoiding rooting the Tab because one of the apps I use does a root check and won't run on a rooted device, but I think there is a workaround to that so rooting is definitely a possibility.
Rooting the device won't be sufficient in itself to solve this problem - I'd need to root and then install a different kernel, right? Or are there wifi modules I can install on top of the stock kernel (once I root the device)?
Any ideas on why this is happening and how I might fix it, short of rooting and installing a non-stock version of Android? My temporary fix is that I fire up FoxFi on my cell phone, and once the Tab sees the FoxFi network, it all of a sudden "sees" the other networks as well. But I've had several situations where I have my tablet but not my cell phone, and in those instances I can't get the Tab to recognize the new networks, even if I reboot the Tab or try messing around with the various networking settings. Note that a factory reset didn't fix this either.
Never mind - broke down and installed CM10.1.
I was having a similar issue on stock. I rooted and have since installed a few roms. I am a Much bigger fan of my tab now. I used infamous for a while and am now on the paranoid android 3.50 build which is awesome!
CM10.1 solved the shy network problem for me... And my tab is much more reliable now too.
Sent from my HTCONE using xda app-developers app
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
NCSUZoSo said:
I am running Netflix version 3.9.1 build 4105 and Android 4.4.2.
When I open Netflix the program just sits and spins and spins then gives me a "Sorry we could not reach Netflix Service. Please try again later (-9)". Then I clear app data and after I do that and relaunch then I get the extremely common 15001 error (that is impossible to actually troubleshoot..).
I have read multiple people having issues with Netflix, but that was when they released a patch that broke it and I am pretty sure that isn't a common problem anymore. I have one of the apps that show network activity and all I get is random hits of like 20-30 KB/s max while trying to launch Netflix. I have tried this on two completely different networks, so I don't think it has anything to do with my network.
My device is rooted with TWRP installed, but I don't see how this could have any affect on Netflix (it never did on my old rooted Nexus 7 running Cyanogen Mod).
Is there something I can try that maybe I haven't heard yet? I even tried clearing the Google Services Framework cache/data (as this helped people in the past) and that changed nothing above. Not being able to use Netflix is a huge problem for me and I am hoping someone has run into this on our devices. I imagine Netflix is one of the most common Apps used.
Thanks for any help or ideas anyone can provide. If I need to I'll restore the tablet with Fastboot, but there is no guarantee that will work and an obvious pain if it doesn't.
Edit: Read the latest comments on Netflix and it seems there are still plenty of people having problems just like mine. I guess I may be waiting for a new version to release??
Click to expand...
Click to collapse
I have the exact same problem! No matter what it's the same error, restoring the tablet doesn't work either.
Screw Netflix, use TV portal! https://drive.google.com/file/d/0BzI_9bXSPgLUX0kwVV8wd3lsTGM/view
When you grab a movie with TV portal, then use Tubemate to download mp4 quality movies of your choice. (touch the green arrow above to get the download interface)
http://www.androidfreeware.net/download-youtube-tubemate.html
I don't think anyone has problems these days ripping off movies, however streaming thousands of movies and TV shows is more convenient by a mile (especially on a tablet).
That is indeed one reason Google & apple push to get rid of the power of personal storage and force the cloud.
When Netflix won't work when you finally settle for a movie, it's nice to have options.
The measly amount Netflix charges is worth it, they have a good service....
But as you know, traveling you are forced to use sporadic data on the road that cost. Until they fix that, I want my storage.
Thank you for starting this thread driving me nuts today! Thought I was alone. It's my son's tablet and Netflix is one of his major uses for it. Tried so many fixes and none are working. Guess we'll keep an eye out for an update.
Also, anyone have trouble with Netflix in general? I had to install an xposed mod just to get it to run!?!
Edit: I tried a much older version of Netflix and it's working perfectly: http://www.apkmirror.com/apk/netflix-inc/netflix/netflix-3-2-0-build-1340-apk/
I then updated the app again and it refused to load at all. Rolled back and turned off auto updates.
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
NCSUZoSo said:
How do you turn off auto updates for a single program? I know how to turn it off completely, but is there a way to do it just for Netflix? It's not like we can deny it network connection..
Also does anyone know the last Netflix version that did work? I think it was around December 2014.
I can also confirm that Netflix 3.2.0 build 1340 does work.
Click to expand...
Click to collapse
Go to Netflix in the play store then hit the three buttons in the top right and the option to disable auto updates should be there.
Never got around to testing other builds as that on works fine for my kid.
I believe the reason behind new versions beyond 3.7.1 not working is because of below;
"As of version 3.7.2, Netflix has begun using Forced Google DNS lookup for their Android app. This means that the Netflix app bypasses any DNS servers you setup on the Android device or on the router and uses Google DNS instead.
Traditionally we were able to block Google DNS lookups on the router and force Netflix to use alternative DNS. However, the Android app seems to not work at all if Google DNS is blocked."
In any case I can confirm that version 3.7.1 build 1711 does work as it should.
Also as recommended earlier you have to stop the app prom auto updating.
Hope that helps.
My hd fire 10 is showing the following message, every time I try to enter the Netflix app: 'Sorry We Cannot Reach The Netflix Service (-9)'.
My device does not have root and the netflix was working normal in the last weeks ...
I tried to clear the cache, reinstall the app, connect to other wifi networks ...
Someone is also having this problem or knows how to solve it?
Responded in another thread on the same topic. Basically, what I did was to uninstall the Google APKs (Framework/Play store ... etc) in order for Netflix to work again. I haven't re-installed those files back yet, so not sure if Netflix will continue to work afterwards.
I also use LauncherHijack, and that continues to work, even though there is a 4,5 seconds delay after touching the Home button.
MatFGo! said:
My hd fire 10 is showing the following message, every time I try to enter the Netflix app: 'Sorry We Cannot Reach The Netflix Service (-9)'.
My device does not have root and the netflix was working normal in the last weeks ...
I tried to clear the cache, reinstall the app, connect to other wifi networks ...
Someone is also having this problem or knows how to solve it?
Click to expand...
Click to collapse
I had started a thread on this issue at https://forum.xda-developers.com/hd8-hd10/help/hd10-netflix-app-stopped-t4038683.
MatFGo! said:
My hd fire 10 is showing the following message, every time I try to enter the Netflix app: 'Sorry We Cannot Reach The Netflix Service (-9)'.
My device does not have root and the netflix was working normal in the last weeks ...
I tried to clear the cache, reinstall the app, connect to other wifi networks ...
Someone is also having this problem or knows how to solve it?
Click to expand...
Click to collapse
You can install Netflix using Fire toolbox: https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
FWIW -- I just updated to version 7.48.0 dated 03/16/20 via Amazon App store -- the updated version seems to work fine.
As stated, for all who are interested/looking. The CURRENT Firestick 4k , direct from Amazon is still 100% Unlock/Rootable. I have had the first release, for a while and it finally burned out. So i took the plunge and ordered a brand new one. Obviously it goes without saying that there is only 1 generation of Firestick 4k, but there have been many reports of ppl not being able to run the script on them. Well i am here to confirm that straight OOB direct from Amazon you will get a stick that has no newer than 6.2.8.1 on it, and if you immediately crash the update from installing via the initial setup, you can enable dev options, usb debug, and run the OTA disable app to erase the downloaded update, and block the update channels that are normally contacted. (search forum for the TDUK Firestick Update Blocker). Then it is completely safe to connect back to your network to quickly log into your amazon account, and then disconnect again IMMEDIATELY once completed. (Failure to disconnect immediately will allow built in scripts to start the update download again in the background and then either once you let the device go to sleep, or if you accidentally reboot, it will auto install on the next load!) But if you completed the 1st part, then you're good to go on using the Kamakiri 2.0.1 scripts to Unlock/Twrp/Root without having to open your stick up. EZ - Peezy. 5 min and my stick is ready to re-customize like i want, but i get the new remote, and it seems a bit snappier... might be just me.
*Also, for those who dont have an OTG, or dont want to use one: simple process is to unplug the usb cable from the OEM adapter that comes with the stick, and plug that straight into your computer. 1st get your linux / fireiso environment ready, and have Kamakiri already on the "Waiting for Device" prompt... Then unplug from your adapter block, and plug right into your PC's USB port. Script should immediately take action, and you're still connected to your TV, so after running the 'fastboot-step.sh' , you will see TWRP on your TV. Now just run "adb shell" , in your same terminal window you have open. Then use TWRP cli to install Magisk, or flash your Rom /whatever you plan on doing. No need to swipe to allow modifications, cuz running "twrp install <whatever you want.zip>, it will automatically bypass that for you.*
hope this info helps somebody!
(PS. DO NOT choose to have Amazon link your device, in the ordering screen. It will offer this before checkout, and I'm almost positive that if you do this, then they open the package and setup your stick for you, thus almost guaranteed they will install the current updated firmware, which is said to block the pre-loader setup ... you want a virgin Firestick, untouched by their grubby little update installing hands! lol)
beatbreakee said:
But if you completed the 1st part, then you're good to go on using the Kamakiri 2.0.1 scripts to Unlock/Twrp/Root without having to open your stick up. EZ - Peezy.
Click to expand...
Click to collapse
We are good to go on using kamakiri 2.x just out of the box...
Thats the safest way, no need to do anything infront of the unlock.
Sus_i said:
We are good to go on using kamakiri 2.x just out of the box...
Thats the safest way, no need to do anything infront of the unlock.
Click to expand...
Click to collapse
true, thats what i was confirming, because several threads in this and the other android development forum had replies from ppl who claimed that the currently sold Firestick 4k was being shipped with a version of FireOS that was not exploitable via the Kamakiri method... basically claiming that the 2018 firestick 4k (as marketed by Amazon) and the CURRENT released 4k are somehow different, which in fact they are absolutely NOT. Theres not a single difference in the board layout or chipset.
Then theres ppl claiming that the updated builds after 6.2.8.1 have patched the access to the pre-loader. Well even if that was true, there would have to be some form of hardware modification that would have had to take place, or at the bare minimum Amazon would have had to trigger an E-fuse to be blown during your initial setup, that would make it unable to downgrade via the short method. BUT they did do exactly that with the Firestick 2nd Gens, that were re-released as some other model, i forget. But i know for a fact that this did happen because i have 3 of those which do not recognize the short, and will not advance past the very 1st file when connected using the NO SHORT method. They freeze immediately and lock up the process. So i was simply doing both a CONFIRMATION to those who stated that there were no UNLOCKABLE versions being sold by Amazon right now, because that is an outright lie... The ONLY firestick 4k being sold by Amazon IS the Unlockable version.... AFAIK the only BLOCKED version being sold is the 4k Max... There is not a "NOT UNLOCKABLE" Firestick 4k being sold anywhere. BUT i also was warning everyone that if you DO purchase a new 4k with the intent of unlocking it, that they need to be aware that Amazon is sneaking an option into the order where you can just check YES and it will come pre-connected to your prime account.
(Some lesser knowing individual might see this as a GOOD OPTION, because they think they wont have to worry about connecting it to the internet to set it up, and risk updating the firmware... but this is EXACTLY Amazon's intent; They WANT ppl to have them link the device before they ship it because that insures that the newest FW is installed onto it, before it leaves the warehouse, thus rendering any mitigations useless if indeed they have patched out the pre-loader exploit!)
I have a few friends in the Software dev team in Cali, and they have told me it is COMPLETELY an ongoing process to disable or nullify all possible methods to Unlock/Alter the bootloader of some current, and ALL future FireOS devices, because they have gotten some pretty nasty legal issues directed at them for allowing system mods that are enabling these 3rd party apps which provide access to Unreleased and In theatre Movies, as well as FREE access to many of the paid streaming platforms! Paramount, Peacock, Hulu, and HBO to name a few have all blamed Amazon for not doing something to prevent the installation of these apps and services which are cutting into their profit margin. Mainly because companies like ROKU disabled all access to their Custom channel lineup, and the ability to use secret codes to install 3rd party apps, on ALL their devices, new and old!.
So just was warning any "Novelty" unlockers, that they need to make sure to not allow Amazon to pre-configure their devices. Hell several features have been removed already in just a few builds... namely the Permissions manager. I hsve one 4k stick here now that is UNLOCKED but the owner has installed several OTA updates to keep it current, and there is literally NO PERMISSIONS manager AT ALL, so several 3rd party apps wont even load. It also has no way to install the Settings V2, so theres, 1. No permission mgr, AND 2. No Accessibility options to grant access for some apps which request it.
Just as a FYI, I also unlocked my new sheldonp (I ordered it on Prime Day) without any problem. Just make sure to run the unlock exploit before powering on the device.
sooo if I got my 4k max today, I should not power it on, and wait for unlock release, right?
ForbEx said:
sooo if I got my 4k max today, I should not power it on, and wait for unlock release, right?
Click to expand...
Click to collapse
Yes
Hmm let me get straight. Tomorrow I will get my 4k (non max) and I'm from Europe. Can't I power it on to see the firmware version? I bought it to escape from sony tv bloatware. Can't be still in the matrix please I'm looking into removing bloatware, root or no root as required to get the job done. I will use it only with kodi for local content. That's it.
ycodryn said:
Hmm let me get straight. Tomorrow I will get my 4k (non max) and I'm from Europe. Can't I power it on to see the firmware version?
Click to expand...
Click to collapse
No
ycodryn said:
I bought it to escape from sony tv bloatware. Can't be still in the matrix please I'm looking into removing bloatware, root or no root as required to get the job done. I will use it only with kodi for local content. That's it.
Click to expand...
Click to collapse
The best is if you try the unlock first, kamakiri 2.1 from this thread:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
Note: The 'shorting' isn't necessary anymore... and it's very easy to do it now, you can see the updated procedere (or lets say guide) in this threads OP:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p)
Read this whole guide before starting. This is for the 3rd gen Fire TV Stick (sheldonp) and Fire TV Stick Lite (sheldon). NOTE: FireOS < 7.2.7.3 required NOTE: This process does not require you to open your device. What you need: A Linux...
forum.xda-developers.com
Thank you for your time. I will read the threads and comeback with some info.
Ok stick arrived, is with VM10137. Now is rooted and working. Thanks again.
I've got mine from Blackfriday sales in Europe. Germany to be exact.
Never turned it on once. Did not connect to internet.
I always get "RuntimeError: ERROR: Serial protocol mismatch, expected 0000 got 2001"
on executing bootrom-step.sh
Boot-Fastboot.sh ran just fine saying "preloader ready, sending FACTACT"
I'm not sure if that means patched.
yes i can also confirm. i bought one a month ago and unlocked it out of the box no prob. I got excited so ordered a second and that one (same process) is giving me the 0000 got 2001 error also.
beatbreakee said:
and if you immediately crash the update from installing via the initial setup
Click to expand...
Click to collapse
Can anyone please point me to instructions on how to do this?
beatbreakee said:
because they have gotten some pretty nasty legal issues directed at them for allowing system mods that are enabling these 3rd party apps
Click to expand...
Click to collapse
IMHO, these Amazon claims do not hold water. I can buy a Dell computer that can do all those "nasty" things with apps, and Dell will not get into legal issues.
ahsad said:
Can anyone please point me to instructions on how to do this?
Click to expand...
Click to collapse
As soon as you connect to WiFi during setup you will see checking for updates. Hold 'back'+'menu' on the remote for 5sec as soon as you see this screen. It will open an accessibility screen, just tap 'back' on the remote, and the update step is skipped.
You can either throttle your internet connection to give you more time on the checking for updates screen, or just unplug your router when you see that screen.
===========
Alternatively, when you are setting up WiFi (entering your password), tap on Advanced on the onscreen keyboard, enter Ighor's DNS address for DNS1 + DNS2, and the stick will be blocked from downloading updates right away. Then use back+menu to skip the check for updates screen.
Is "Ighors DNS address for DNS1 + DNS2" the exact command, or should I put in the actual IPs for the DNS servers? If I am to enter IPs is the + necessary?
Did you mean to type "ignore" or is "lghors" what I really should type?
ahsad said:
Is "Ighors DNS address for DNS1 + DNS2" the exact command, or should I put in the actual IPs for the DNS servers? If I am to enter IPs is the + necessary?
Did you mean to type "ignore" or is "lghors" what I really should type?
Click to expand...
Click to collapse
Yes Ighor, not ignore . Click on that link, and it has step by step information how how to fill out the advanced WiFi settings.
When you get to the option to enter the DNS, you need to enter the DNS IP address corresponding to one of Ighor's DNS servers (choose the one that corresponds to your geographical region).
Ighor's DNS servers block the addresses that serve Amazon's OTA updates. By using them in your advanced WiFi settings, you are blocking your FireTV from connecting to them.
Thank you. I am new to the forum and did not catch that the blue writing was a link. I clicked it this time.
do i need to solder or anything to root this? tired in the past but failed. would love to root the 4k i have. its sitting on an OLD 6.x.x.x update. the custom launcher still boots by default without issue
this.guy.lol said:
do i need to solder or anything to root this?
Click to expand...
Click to collapse
I am new here. That being said, what I have read here, and in another thread, indicated the disassembly and shorting are no longer needed. See message #2 of this thread.