Database Users

Apps Hang and dont donwload from Market

I am having this problem recently. I try to download any app or an update to any app. It will just sit at starting download and never download.
I am on Fresh ROM 1.0
I did update some apps after installing the ROM so that's not the problem.
I also have a problem that if I clear the cache, when I reboot Everything force and keeps force closing forever. Whats up with that? isn't the cache supposed to recompile on reboot?
I tried clearing the cache to fix the market issue to no avail (beacuse of all the force closes never got to see what happened after clearing cache). I tried clearing the cache from recovery and using Fresh's app installer,and both times tons of force closes.
Someone please HELP!

U probably need to login to gtalk. I had the same problem from using autostarts. Jus open the gtalk app, it will/should sign u in automatically.

this is not a gtalk issue. gtalk is not even related to what problem he has. i had it happen to me on my eris when i was playing around in the bootloader. when i started back up everything force closed and would not start. only sugetion i can give you on the force close it is a factory reset or ruu reset both will work. as far as downloads not starting are you rooted?

Yes, to install a custom ROM you need to be rooted. Tried the gtalk sing in to fix the Market issue and no dice. Still hanguing...
Anything else??

rigamrts said:
this is not a gtalk issue. gtalk is not even related to what problem he has. i had it happen to me on my eris when i was playing around in the bootloader. when i started back up everything force closed and would not start. only sugetion i can give you on the force close it is a factory reset or ruu reset both will work. as far as downloads not starting are you rooted?
Click to expand...
Click to collapse
So I'm not going to call you out or something, but please read before you speak. Gtalk is MAJORLY tied in to the market and it is a documented fix from google themselves to try signing in to gtalk to fix stalled downloads.
Even though it doesn't work for everyone (depending on the reason it's stalled) it IS related.
daveli said:
Yes, to install a custom ROM you need to be rooted. Tried the gtalk sing in to fix the Market issue and no dice. Still hanguing...
Anything else??
Click to expand...
Click to collapse
http://www.google.com/support/forum/p/Android+Market/thread?tid=57b5e3efa7477b50&hl=en
Hundreds (maybe thousands?) of posts. Starting back in March and dating all the way until today. Google hasn't been able to resolve the issue. I can tell you that what has always worked for me is a combination of cancel download > disable wifi > disable mobile data > enable mobile data > try download again.
Didn't work? Reboot and repeat. Eventually it will go......

Thanks a lot flipz. I'll try that

flipzmode said:
So I'm not going to call you out or something, but please read before you speak. Gtalk is MAJORLY tied in to the market and it is a documented fix from google themselves to try signing in to gtalk to fix stalled downloads.
Even though it doesn't work for everyone (depending on the reason it's stalled) it IS related.
http://www.google.com/support/forum/p/Android+Market/thread?tid=57b5e3efa7477b50&hl=en
Hundreds (maybe thousands?) of posts. Starting back in March and dating all the way until today. Google hasn't been able to resolve the issue. I can tell you that what has always worked for me is a combination of cancel download > disable wifi > disable mobile data > enable mobile data > try download again.
Didn't work? Reboot and repeat. Eventually it will go......
Click to expand...
Click to collapse
95% of the time your second sugestion works. it may be that gtalk has major issues with stalled downloads but ussually i have this issue when i start my download over wifi for some reason it just never connect to the google server but when i kill the download and connect over 3G or Edge it works everytime on my G1. that's been a documented fix too. this issue only happens more frequently on custom roms than stock android roms. so it's more of a rom issue that googe issue. we're all here to help each other not trash talk each other. from my point of veiw gtalk may have some type of issue but it's more with the rom cooks than the app itself and it's not their fault either gtalk was desighned to work on googles cookie cutter os not on the home brew roms so errors happen you just have to know how to sweat talk your andoid to doing things when issues happen. the problem i had with your post was you only stated the gtalk issue when the wifi issue is more prevelent. i wasn't sure if he was on stock os or custom os so i asked about it. then i would have given him the instructions on turning off the the wifi, killing the downloads, and restarting the phone. like you told him to in the second post cause that seem to work better than the gtalk method.

rigamrts said:
i wasn't sure if he was on stock os or custom os so i asked about it.
Click to expand...
Click to collapse
I stated clearly on my first post I am on Fresh 1.0 ROM, so everyone would know I was on a custom ROM.

daveli said:
I stated clearly on my first post I am on Fresh 1.0 ROM, so everyone would know I was on a custom ROM.
Click to expand...
Click to collapse
sorry. i did not read your post clearly thought when you said fresh you ment fresh install. haven't really been keeping up with the hero roms to much and thier names still waiting for my eris to get it's turn at root. when i saw your post it just reminded me of how my rooted G1 would not start downloads over wifi. so i asked rooted or not just to be on the safe side.
the thing that got me a little heated was when he said "not to call you out" then he goes into a trist about how wifi seems to be the better fix.
by the way did you get your problem fixxed?

rigamrts said:
sorry. i did not read your post clearly thought when you said fresh you ment fresh install. haven't really been keeping up with the hero roms to much and thier names still waiting for my eris to get it's turn at root. when i saw your post it just reminded me of how my rooted G1 would not start downloads over wifi. so i asked rooted or not just to be on the safe side.
the thing that got me a little heated was when he said "not to call you out" then he goes into a trist about how wifi seems to be the better fix.
by the way did you get your problem fixxed?
Click to expand...
Click to collapse
(Ok,fair enough it can be confusing when i wrote fresh; no worries).
About my problem: Not at all man, I tried every single one of the fixes and no luck. I am thinking about going back to stock and reflashing the custom ROM. I'll report back if/when/how it gets fixed

Nevermind Disregard

daveli said:
(Ok,fair enough it can be confusing when i wrote fresh; no worries).
About my problem: Not at all man, I tried every single one of the fixes and no luck. I am thinking about going back to stock and reflashing the custom ROM. I'll report back if/when/how it gets fixed
Click to expand...
Click to collapse
I ended up factory resetting and now everything downloads normally

So... apps were downloading perfect from market UNTIL I restored a nandroid backup. Afterwards, Apps hang again. I mean exactly after restoring, went to the market and the problem is there again. Can the problem be tied to restoring backups? Or just coincidence?
Update:
Got the downloads working after clearing the cache of every single google application on the phone as well as IM.
After this, started downloading the app and it still hung. Opened gtalk and exactly as it signed in it started downloading fine.
I tried the afore mentioned fixes and had no luck, so for anyone who has this issue and has not been able to resolve it, this is another workaround.

Just FYI to anyone still with problems, I had problems again today EXACTLY after restoring a backup again.
This post I quoted by Zippy-man did the trick today Great Help..
http://forum.xda-developers.com/showpost.php?p=5374641&postcount=43

Warning new supersu update lock the tablet

I just upgraded supersu from google play. After a reboot, the tablet locks after about 20 seconds or so. After that it is impossible to access anything. The tablet then reboot. The only pudate I did was supersu
It took me few tries to be able to access the settings and remove the update before the tablet locks.
Now it seems to work again without problem.
Don't update until the problem is solved
Mod if this should be placed in another forum feel free to move it
Sent from my GT-N8013 using Tapatalk HD

jmlmrk said:
I just upgraded supersu from google play. After a reboot, the tablet locks after about 20 second or so. It took me few tries to be able to access the seting and remove the update before the tablet locks.
Now it seems to work again without problem.
Don't update until the problem is solved
Mod if this should be placed in another forum feel free to move it
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
Odd. Ive already had the update and have rebooted and havent had any problems

conan1600 said:
Odd. Ive already had the update and have rebooted and havent had any problems
Click to expand...
Click to collapse
Well the only thing I did was removing the update to supersu.
I also connected the tablet to my laptop thinking I will have to odin back to stock. But didn't need too. I hope it was nothing... I just wanting to let people know it may be a problem
Sent from my GT-N8013 using Tapatalk HD

No problem for me with the update.Rebooted fine.
Sent from my GT-N8010 using xda premium

Same here, updated and did a few reboots due to enabling multiwindow in some apps and everything is working fine..

No problems here on note 10.1 and Note 2.

Just updated.. rebooted and no problems here..
Sent from my GT-N8013 using XDA Premium HD app

Be worth reading Google Play comments before drawing any conclusions .
jje

FWIW, I had the same issue, too. I'll also keep looking into it.
Also getting that request for "dumpstate", too.

kcrudup said:
FWIW, I had the same issue, too. I'll also keep looking into it.
Also getting that request for "dumpstate", too.
Click to expand...
Click to collapse
I have looked further into the problem, it seems that the new supersu may not play well with some apps that request root access. I had avast anti theft software which required root. I uninstalled it reapplied supersu update and it is working. Also avast keep on giving me error even after the downgrade of supersu.
Like you I had the request for dumstate.
Finally I have avast on my galaxy nexus and the new supersu and no problem at all.
So as of now on the tablet I cannot have both (avast and new supersu) together
Sent from my GT-N8013 using Tapatalk HD

A friend of mine having the same issue with N7000.
How did you manage to uninstall update before getting stucked.

Same Issue here. Stucked after reboot after SU Binary update.
Managed to run "top" in adb shell which shows me that /system/xbin/su runs to many times......

no problem here on 5 devices

dionysos77 said:
A friend of mine having the same issue with N7000.
How did you manage to uninstall update before getting stucked.
Click to expand...
Click to collapse
Restart the tablet as soon as you are on the lock screen tap status bar , tap settings, tap applications scroll to supersu and uninstall upday tap ok. You have to do it as fast as possible before 5he tablet locks... I had to do it a dozen times before succeeding
Good luck
Sent from my GT-N8013 using Tapatalk HD

This happened to me as well...had to race to SuperSU/settings and changed Default Access from Prompt to Grant and it stopped locking up...couple of reboots then and reset access on your apps after it completely reboots and settles down.....

I had this issue yesterday after installing ROM Android Revolution HD. I thought it was a problem with rom and returned to stock. But on stock I updated it and have no problems.

There's a new update with some bug fixes out. I don't know if it fixes your problem since I did not have it.

[Q] [HELP] Unfortunately, Direct pen input has stopped

Hello Guys,
At first i just flashed a N900 Pre-Root Deodex file using Odin, but after reboot a window popped out displaying," Unfortunately, Direct pen input has stopped." And it happened all the time as it keeps freezing my note 3 with all these windows & notice over & over again.
I really don't know how did i go wrong. So I tried to do factory reset, wipe cache & dalvik cache using CWM Recovery 6.0.3.8 but to no avail. The problems worsened as now multiple windows starts to freeze the screen with different notice such as now:
1. Unfortunately, Direct pen input has stopped
2. Unfortunately, Samsung keyboard has stopped
3. Unfortunately, Internet has stopped
4. Process system isn't responding
Do you want to close it
I checked into my download mode, it displayed CURRENT BINARY CUSTOM and SYSTEM STATUS CUSTOM ???
Please kindly advise, thanks in advance

[Sharing Info]
Problem is solved by flashing Stock ROM from same Asian Region here (WAN) because my original country's Stock ROM (XSE) isn't available yet.

Denim Guy said:
[Sharing Info]
Problem is solved by flashing Stock ROM from same Asian Region here (WAN) because my original country's Stock ROM (XSE) isn't available yet.
Click to expand...
Click to collapse
Hello, Can you elaborate further what exactly did you do? I got the same problem now on my Note 3
Thanks in advance!

Check logcat for crashes!
I disabled / uninstalled as many system apps that appeared in my drawer as I could. One too many it seems and Messaging would crash each time I got a text.
Re-installed the app from backup and just hid it in my app draw (ADW Launcher EX)

The remedy is simply flash your original firmware using odin, then for rooting process i just flashed using CF-Auto Root File with same method
b0ybitzzz said:
Hello, Can you elaborate further what exactly did you do? I got the same problem now on my Note 3
Thanks in advance!
Click to expand...
Click to collapse
At my point of trouble that time, it was totally chaotic as the phone kept freezing with multiple error windows, and i could neither use the keyboard nor using the phone normally at all. It was quite relieving to know that i could still reboot into download mode that time, otherwise i would be stressful in vain till now.
@Class said:
Check logcat for crashes!
I disabled / uninstalled as many system apps that appeared in my drawer as I could. One too many it seems and Messaging would crash each time I got a text.
Re-installed the app from backup and just hid it in my app draw (ADW Launcher EX)
Click to expand...
Click to collapse

Denim Guy said:
The remedy is simply flash your original firmware using odin, then for rooting process i just flashed using CF-Auto Root File with same method
At my point of trouble that time, it was totally chaotic as the phone kept freezing with multiple error windows, and i could neither use the keyboard nor using the phone normally at all. It was quite relieving to know that i could still reboot into download mode that time, otherwise i would be stressful in vain till now.
Click to expand...
Click to collapse
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!

right
hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
above is absolutely right and I have fixed the issue .

hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
I cant believe I had to read 15 posts about gibberish before you fixed it for me. TY sir.

Thanks
hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
Thank you very much I had turned this process off a few days ago but today it caught up with me..

FIXED IT!!!!!
hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
This was my solution! Thank you!!! :good:

same problem on note 3 SM-N900A (att)
how do fix this on att note 3 please help, the pop out is really anoying and making me frustrated

odan360 said:
how do fix this on att note 3 please help, the pop out is really anoying and making me frustrated
Click to expand...
Click to collapse
Haing any luck with your issue mines the same BE4 i soft bricked mines and AFTER i unbricked it.....

Same
champgee said:
Haing any luck with your issue mines the same BE4 i soft bricked mines and AFTER i unbricked it.....
Click to expand...
Click to collapse
Not sure what you mean by this. I'm having the same issue now. I tried to root using this tutorial https://www.youtube.com/watch?v=hg82AWA_lmI having no luck and failing on the first part. After that the phone wanted to be fixed via kies firmware; tried that with no success. I then tried these steps http://forum.xda-developers.com/showthread.php?t=2525279 to recover. While in Odin, I was given a success message ONLY with the PIT. Everything else during, before and after fails. This results in me having to re-PIT every time.
So now the phone, even after a factory reset, is still showing the message
Unfortunately, Direct pen input has stopped.
Click to expand...
Click to collapse
Any help would be appreciated
SM-N900A AT&T US
Kies reset: SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
Odin 3: PIT and PDA: SECURE CHECK FAIL : system
When using this guys method: http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/ When I get to the Heimdall Frontend section I get this message: Initialising protocol...
ERROR: Failed to send data!Releasing device interface...

How?
hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
How do I get this process back on the phone?

allnamesaretaken said:
How do I get this process back on the phone?
Click to expand...
Click to collapse
Reflash stock
No data loss, but will loose root
If u rooted via urdlv, flash the file u used to root your device.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

Flash -
Killberty said:
Reflash stock
Click to expand...
Click to collapse
No data loss, but will loose root
If u rooted via urdlv, flash the file u used to root your device.
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
I've been trying to do this, is there something I'm missing? Please refer to this link or scroll up a bit.
http://forum.xda-developers.com/showpost.php?p=49473243&postcount=13

allnamesaretaken said:
Not sure what you mean by this. I'm having the same issue now. I tried to root using this tutorial https://www.youtube.com/watch?v=hg82AWA_lmI having no luck and failing on the first part. After that the phone wanted to be fixed via kies firmware; tried that with no success. I then tried these steps http://forum.xda-developers.com/showthread.php?t=2525279 to recover. While in Odin, I was given a success message ONLY with the PIT. Everything else during, before and after fails. This results in me having to re-PIT every time.
So now the phone, even after a factory reset, is still showing the message
Any help would be appreciated
SM-N900A AT&T US
Kies reset: SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1
Odin 3: PIT and PDA: SECURE CHECK FAIL : system
When using this guys method: http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/ When I get to the Heimdall Frontend section I get this message: Initialising protocol...
ERROR: Failed to send data!Releasing device interface...
Click to expand...
Click to collapse
allnamesaretaken said:
I've been trying to do this, is there something I'm missing? Please refer to this link or scroll up a bit.
http://forum.xda-developers.com/showpost.php?p=49473243&postcount=13
Click to expand...
Click to collapse
Took it to AT&T they replaced the phone.:good:

hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
Your solution is the usual error/solution for most. I just found out that if you are using xposed - xprivacy module to limit permissions that when I recently installed samsung's "Watchon" TV and its helper app Media that I recieved a popup from xposed XPrivacy to set my policy on something of a long winded name like "1000 ANT HAL Service, Android System, Application installer, Assistant menu, BluetoothTest, Camera Test, Color adjustment, DgitalPenSdK, Direct pen input, EasyOneHand, Enterprise Sim Pin Service...." and it goes on and on. Apparently it's one of those deep shared system identifiers that the new apps added themselves to so when I took my usually cautious approach to limit some of the permissions I didn't have any errors immediately but upon reboot it all began. I naturally did a search and found your solution is the most common but seeing as it wasn't a solution for myself I had to dig deeper. Anyhow, if anybody else is in my position with that particular error and it relates to xprivacy just know that you can begin releasing permissions rather than unrestricted for that mass identifier, or just use "clear" so that it is totally unchecked and the FC of Direct Pen Input will go away immediately.

Not working
hockeyfan said:
I ran into this issue as well, when I started carelessly turning off all the services on my GN3 to free up memory. I narrowed down the issue to the process/service called "MyScript ResourceManager." If this is disabled/removed, you will get the Direct Pen input error. Make sure you don't disable/remove this process!!
Click to expand...
Click to collapse
I tried this solution but with no luck. I have just reimaged my phone and it starts popping up as I try to set up the phone for the first time. I went to the app manager and the MyScript ResourceManager was on and never turned off. Please help. I have the sprint version SM-N900P

killjoy666 said:
I tried this solution but with no luck. I have just reimaged my phone and it starts popping up as I try to set up the phone for the first time. I went to the app manager and the MyScript ResourceManager was on and never turned off. Please help. I have the sprint version SM-N900P
Click to expand...
Click to collapse
reflash stock, or do a factory reset. that worked for me.

WiFi connected but not working

A couple days ago my WiFi(on my note 3 only) has started randomly disconnecting. It still says connected though. When I try to go to the play store or browser it won't connect. I tried to see if it was my WiFi connection, but its not the problem. All other devices work fine. It's just my note 3. I dropped it a couple days ago. Could that have messed up WiFi antenna? Also I'm only using the note 3 as a WiFi only device. It has no data plan.
Sent from my SM-N900V

Try deleting updates to and re installing google play services again. You can get it at apk mirror. Check the parenthesis matches your device before you install it.
If you are rooted and have used luckypatcher to patch an ingame purchase you need to get rid of the record of the patch within luckypatcher.
Otherwise you are looking at a reset with odin. If this doesn't solve it then the device is faulty.
Sent from my GT-I9300

shivadow said:
Try deleting updates to and re installing google play services again. You can get it at apk mirror. Check the parenthesis matches your device before you install it.
If you are rooted and have used luckypatcher to patch an ingame purchase you need to get rid of the record of the patch within luckypatcher.
Otherwise you are looking at a reset with odin. If this doesn't solve it then the device is faulty.
Sent from my GT-I9300
Click to expand...
Click to collapse
I know this is way late but I ended up wiping data and going back to the rooted stock rom. The problem was still there. I didn't bother uprooting or doing it through odin. Didn't bother with the hassle. Pretty sure it was a hardware problem.

jmindset said:
I know this is way late but I ended up wiping data and going back to the rooted stock rom. The problem was still there. I didn't bother uprooting or doing it through odin. Didn't bother with the hassle. Pretty sure it was a hardware problem.
Click to expand...
Click to collapse
Do you installed any root wifi app?
It happened to my after restoring the passwords (binary files)
Get a new official ROM and flash it, you don't have anything to lose.
I hope it helps.

Paradox13 said:
Do you installed any root wifi app?
It happened to my after restoring the passwords (binary files)
Get a new official ROM and flash it, you don't have anything to lose.
I hope it helps.
Click to expand...
Click to collapse
Yeah I did that. Tried 3 different roms. It's random but it happened often. Wifi stayed connected but wasn't working. I think it was my antenna

Also checked stock rom??

Nachtwesen2 said:
Also checked stock rom??
Click to expand...
Click to collapse
Yeah I went back to stock. Via twrp backup. Stock apps and everything. Same problem. Still think it was a hardware problem.

Netflix Error 5.2 after updating to Android 8.0- UNROOTED, STOCK

Hi all,
Just updated my stock, unrooted Verizon Galaxy S8 this morning to Android 8.0. Now, whenever I try to watch a show on Netflix, I get an error message saying "This video could not be played. (5.2)". I have already uninstalled and reinstalled, restarted my phone, and called Netflix (who said to just contact Samsung- and we all know how useful that will be). Any ideas here for how to fix?
Thanks!

I fixed that using root.
In a nutshell:
Rename the following file:
/system/lib/liboemcrypto.so to /liboemcrypto.so.bak
Not sure if you can root a Verizon S8, try your luck at this thread for a discussion on the issue.

Ahmer Jamil Khan said:
I fixed that using root.
In a nutshell:
Rename the following file:
/system/lib/liboemcrypto.so to /liboemcrypto.so.bak
Not sure if you can root a Verizon S8, try your luck at this thread for a discussion on the issue.
Click to expand...
Click to collapse
I can't, and don't want to root- I feel like Netflix and/or Samsung really screwed up here

This is an issue with Android's DRM implementation, I guess. Can you check if your device passes SafetyNet?

That's ... Odd. Netflix works fine for me

ryanpm40 said:
That's ... Odd. Netflix works fine for me
Click to expand...
Click to collapse
Never mind- It randomly started working again!

mancoh51 said:
Never mind- It randomly started working again!
Click to expand...
Click to collapse
Haha well I'm glad it's working for you! After it working all night for me, I'm now getting the same exact error you were getting. It's really annoying me, going to try rebooting next I guess.
Edit
So, rebooting was enough to let me watch one episode of a show, but then I got that error when I autoplayed to the next. I cleared the app's data and that fixed it, too. We'll see if that's a permanent fix.

I have this exact same problem. Don't want to root or unlock. I've tried uninstalling and installing the app. I've tried clearing data and cache. Is the next step a factory reset? Anything else I can do before that?

Buffpandabear said:
I have this exact same problem. Don't want to root or unlock. I've tried uninstalling and installing the app. I've tried clearing data and cache. Is the next step a factory reset? Anything else I can do before that?
Click to expand...
Click to collapse
Same thing happened to me. Just uninstalling and reinstalling the app didn't work. Had to reboot the phone after reinstalling and after logging back into Netflix, went to settings and ran check network. Everything came back OK. Was able to watch without any issues since. Hoping it stays that way.