Perhaps this is a known issue, but a quick forum search didn't turn anything up.
I'm running a pre-rooted image. I haven't been a Netflix subscriber for many months, but recently resubscribed. Unfortunately, I can't get anything to play back. I just get "We're having trouble playing this title right now. Please try again later or select a different title". In the bottom right corner, it says "aip-701".
Thinking perhaps I needed to be on the latest image, I upgraded to the pre-rooted ROM of 51.1.5.3_515040320. Same issue. I read other posts saying to clear your Amazon app setting, and to clear your Netflix app and cache. Tried both, had to add my account info back into Netflix, but it still fails.
These same titles play fine on my wife's iPad. And my wife isn't streaming anything down while I am doing these tests, so it's not a concurrent stream issue.
Is this a known problem with the pre-rooted ROMs? An issue with FireTV's on Netflix tonight? Something else?
Taige said:
Perhaps this is a known issue, but a quick forum search didn't turn anything up.
I'm running a pre-rooted image. I haven't been a Netflix subscriber for many months, but recently resubscribed. Unfortunately, I can't get anything to play back. I just get "We're having trouble playing this title right now. Please try again later or select a different title". In the bottom right corner, it says "aip-701".
Thinking perhaps I needed to be on the latest image, I upgraded to the pre-rooted ROM of 51.1.5.3_515040320. Same issue. I read other posts saying to clear your Amazon app setting, and to clear your Netflix app and cache. Tried both, had to add my account info back into Netflix, but it still fails.
These same titles play fine on my wife's iPad. And my wife isn't streaming anything down while I am doing these tests, so it's not a concurrent stream issue.
Is this a known problem with the pre-rooted ROMs? An issue with FireTV's on Netflix tonight? Something else?
Click to expand...
Click to collapse
I did something like this and I rarely get that message anymore but Netflix is just not without bugs on aftv apparently.
1. Clear data and uninstall Netflix.
2. Reboot to recovery and wipe cache partition and dalvik. Then reboot system.
3. Install Netflix.
***some people add a step between 1-2 and clear data 3 times in amazon video then unplug aftv 10 seconds but I don't find lasting results there.
KLit75 said:
I did something like this and I rarely get that message anymore but Netflix is just not without bugs on aftv apparently.
1. Clear data and uninstall Netflix.
2. Reboot to recovery and wipe cache partition and dalvik. Then reboot system.
3. Install Netflix.
***some people add a step between 1-2 and clear data 3 times in amazon video then unplug aftv 10 seconds but I don't find lasting results there.
Click to expand...
Click to collapse
Thanks for the steps.. I did the clear data, uninstalled Netflix, booted to recovery and wiped cache and dalvik cache (something I don't think I've heard of before today), rebooted and installed Netflix.
Signed back in to Netflix and tried playing a video. Shows come up, including the show my wife was just watching on her iPad. Try to continue that episode, and got the same error message...
So, this didn't fix mine, but thanks for trying to help. Any other suggestions?
Taige said:
Thanks for the steps.. I did the clear data, uninstalled Netflix, booted to recovery and wiped cache and dalvik cache (something I don't think I've heard of before today), rebooted and installed Netflix.
Signed back in to Netflix and tried playing a video. Shows come up, including the show my wife was just watching on her iPad. Try to continue that episode, and got the same error message...
So, this didn't fix mine, but thanks for trying to help. Any other suggestions?
Click to expand...
Click to collapse
Sorry it didn't work for you. I forgot to ask, which firmware were you on before the update? Seems to me like a crap shoot who gets netflix issues and who doesn't, but awhile back some users swore by the fact you needed to do some updates incrementally. So if you were on say 51.1.3.0 you would first update to 51.1.4.0 before installing 51.1.4.1. The problem is I can't remember precisely which updates could be skipped without running into issues like the netflix one.
What I can say with at least a bit of confidence is if you were on 51.1.3.0 then you should update to 51.1.4.0 before jumping to the latest firmware (maybe even update again after that before making the jump.) But try to do a search and see if you can find that thread. It was a few months back but it was pretty lengthy and some users had useful info. If I find it I'll let you know.
KLit75 said:
Sorry it didn't work for you. I forgot to ask, which firmware were you on before the update? Seems to me like a crap shoot who gets netflix issues and who doesn't, but awhile back some users swore by the fact you needed to do some updates incrementally. So if you were on say 51.1.3.0 you would first update to 51.1.4.0 before installing 51.1.4.1. The problem is I can't remember precisely which updates could be skipped without running into issues like the netflix one.
What I can say with at least a bit of confidence is if you were on 51.1.3.0 then you should update to 51.1.4.0 before jumping to the latest firmware (maybe even update again after that before making the jump.) But try to do a search and see if you can find that thread. It was a few months back but it was pretty lengthy and some users had useful info. If I find it I'll let you know.
Click to expand...
Click to collapse
I believe I was on 51.1.5.0_515020820 before I updated to the latest. There's no telling relative to the order I've updated in prior to that. I know I've skipped some versions.
It's not a big deal. My wife actually seems to prefer watching her shows on the iPad. If it's something for the entire family, it will just require a bit more planning on my part to run PlayOn and record the Netflix episodes I want to watch later on the FireTV.
My suggestion is to follow the rooting guide found at aftvnews.com to see where you might of gone wrong....Good luck.
Related
I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.
Everything was working fine until today. My market refuses to download apps or updates, even after a factory reset. Not sure if anyone else has noticed. Can't seem to fix it. Not sure if its server side or some update to the market, but I can't get my apps back until its fixed. Please post here if you know what's going on or have the issue. I'll try WiFi later and see if that helps.
Update: It started working randomly shortly after I wrote this post. Unfortunately, another problem has come up. Now I get unknown error -18 when downloading and installings Google Sky Map, MiniSquadron!, Bubble Breaker, and Bubble Breaker Editor. So essentially all is well, but I'm getting weird errors on one of my favorite apps and one that I just bought and haven't been able to use. I'm going to try a different rom and see if that helps. This is really starting to annoy me...
Update: I did an RUU last night and as of right now, I still cannot access those four apps. Same error -18. Someone else here on the forums is having market issues similar to those I was having at first, so it might just be a server side or recent market update issue.
i have the same problem market gets stuck at downloading
It sucks, but repartition your sd card. Worked for me after getting the same errors. Something about it trying to overwrite an existing file and then failing.
Yeah, I was just googling for information on the error and found out you have to move any existing apps from the SD card to the phone and then delete the .android_secure folder from your card. Guess all of these apps were meant to install to the SD card by default and that's what was causing the error. Fixed my phone now.
superlinkx said:
Everything was working fine until today. My market refuses to download apps or updates, even after a factory reset. Not sure if anyone else has noticed. Can't seem to fix it. Not sure if its server side or some update to the market, but I can't get my apps back until its fixed. Please post here if you know what's going on or have the issue. I'll try WiFi later and see if that helps.
Update: It started working randomly shortly after I wrote this post. Unfortunately, another problem has come up. Now I get unknown error -18 when downloading and installings Google Sky Map, MiniSquadron!, Bubble Breaker, and Bubble Breaker Editor. So essentially all is well, but I'm getting weird errors on one of my favorite apps and one that I just bought and haven't been able to use. I'm going to try a different rom and see if that helps. This is really starting to annoy me...
Click to expand...
Click to collapse
i have a similar issue.....except it will only download when im on wifi
techdude54 said:
i have a similar issue.....except it will only download when im on wifi
Click to expand...
Click to collapse
Yeah, I've had that problem for a while. Usually if I rebooted or used wifi tether it would start working. They've pushed out a couple of updates to the market in the last couple of days, and I haven't been having problems today at least. We'll see how long that lasts.
Settings, Applications, All Apps, Market, Uninstall updates, clear data, clear cache, force stop. Open market. Fixed.
Has anyone else experience their WIFI connection almost completely stop working? For the last few days either I get no connectivity at all or very slow, but every now and then for a few minutes it will run at normal speeds.
I'm stock, rooted, no custom recovery or 2nd bootloader. I've rebooted the kindle and my router multiple times. I've done a full factory reset on the Kindle. None of that helped. There's 3 laptops, 2 other tablets, and 2 phone all running fine on the WIFI so I don't think it's the router.
If anyone has any suggestions. I'd appreciate it.
Have you done any other modifications other than rooting?
soupmagnet said:
Have you done any other modifications other than rooting?
Click to expand...
Click to collapse
I've got the google services installed to get the Play Store working, and installed NOVA launcher. I think that's all.
Well, I thought it may be something with the drivers gone funny, so I finally got around to getting 2nd bootloader and recovery going. I tried CM10, I tried Hashcode's stock ROM, and I tried the full restore from the KFHD First Aide tool. All the same results. I'll get intermittent bursts of full speed, but for the most part every web page, market request or attempt to stream something times out.
When I look at the WIFI settings in the kindle, it pretty consistently says 39Mb link speed. My phone is connecting at 26Mps, but everything works no problem as do all the other devices.
I know I'm heading into O/T territory, but does anyone know what Router Settings to check for that may be limiting just one device? Failing that I'm going to have to return to stock and see if I can get some help from Amazon.
Thanks in advance!
I'm also having some wifi issues like you. Mine's 8.4.3, rooted, with google play store and a few other things. Like you, all my wireless settings seem to be ok, several other devices use the wifi without any problems. And like you, I've had CM 10.1 installed in the past and I'm back on the stock Amazon rom.
One hunch that I had yesterday was the following: I bought a cover for my Kindle that can cover the back and front of the kindle. When I use it normally, I fold the front cover around to the back of the device, meaning there's a double cover on the back when in use. I thought to myself, maybe the cover is blocking the wifi signal or something... I then tried changing the cover to "kickstand" mode, so that it wasn't against the back of the device. It seemed to help, but I still need to do more testing.
If you have a cover then maybe try taking it off and testing the wifi. If not then I'm out of ideas, but I'm not sure how it could be a software problem, since you've tried different ROMs with the same results.
Apparently, after a quick google search, it looks like a lot of people are having wifi problems with the kindle fire HD. Perhaps the following thread will help: http://www.mobileread.com/forums/showthread.php?t=210002. It mentions changing some router settings. I'll try it on mine when I get home.
Make sure that QoS is disabled on your router.
Greek2me said:
Make sure that QoS is disabled on your router.
Click to expand...
Click to collapse
Thanks for the suggestions. No help unfortunately.
I need to get somewhere I can try connecting to a different router. If that's still unusable, I think it's time for the service call.
Hello everyone! I'm not exactly new to rooting, roms, or XDA, but I am a new member, so as such, the forums system forced me to post here...
What I am having trouble with:
twa_priv's CM11.0/SGT7 For kindle fire.
Issue description:
I flashed this rom today to my 1st gen kindle fire. (I used KFU 0.9.9 a few days ago to get root, and everything's good there.)
I'm using TWRP 2.3.6.0 and the ROM mentioned above. After flashing, I tried to connect to my home wifi. But the tablet said "Could not connect". So I thought, "well I'll try setting my router to 'insecure' and see if it works." and it worked fine. Then I tried switching the router back to secure. Nope. Rebooting the kindle? Nope. Wiping and re-flashing? Nope. Clearing Dalvik and Cache? Nope.
So I played around with everything else that ROM had for a little while and couldn't find any other problems...
But not having secure wifi was a dealbreaker for me. I'm still upset, as I very much like KitKat, and that ROM in general...
So, instead of sitting there with a [unusable - to me at least] device, I decided to flash the previous version of the ROM. That would be CM10.1/SGT7 For the Fire, by the same author.
Unfortunately, this ROM also has some issues, although I have mostly been able to ignore them so far (they are not as destructive as the wifi issue). Those issues would be: 1) For whatever reason the microphone no longer works, and 2) Trebuchet force closes from time to time.
Okay, so you may be thinking, well the KF doesn't have a mic. Yes, I know. I'm using an ifrogz headset w/inline mic. How do I know that headset works? I was able to use it with google voice search on the rooted stock ROM, as well as a free voice recording app. I happen to be slightly paranoid though, and tested the headset in a android phone I have. I was able to successfully make recordings there.
So, I tried a favorite app of mine called Soundabout, which allows me to force the system to use the speaker or headset, the bluetooth (if equipped), etc.
Still nothing.
Allow me to describe what happens when I try to record using the built in voice recorder app: kkkkssssshhhhhhhhhhhhh.....
(Something like a very noisy PC fan.)
This sound was generated regardless of the headset being plugged in or not.
I forgot to test this recording issue on the CM 11 ROM, and I don't have time (or patience) to do that tonight
So, please, please help!
PS:
I apologize for having such a lengthy post, but I've read complaints of not "describ[ing] in detail your problem" so I figured I would err on the sive of being too descriptive
FYI, just updated my FTV to the latest CMW and pre-rooted firmware. Updated Netflix and gives me error NW-4-8. I go to Netflix and they have put up a banner (after you log in) that some devices are having issues currently. I was wondering if someone running the latest firmware (the updated version) can confirm if they are having issues (after they had the latest version working)? I am wondering if I did something wrong on my install....
Thanks.
Hi im on latest pre-rooted ROM by rbox and im watching the Netflix right now no problem.
*UPDATED* I exit Netflix and re run the Netflix. Bingo they are down this time. So you aren't only one so count us in.
PS. I tested run my Verizon note 3 able run Netflix and working fine.
PSS. Now my Amazon fire tv Netflix is back online. Very ODD!
Update
Netflix was working fine for me yesterday with pre rooted rom new update. I tried this evening and it's not working at the moment. I tried checking network says all good, tried signing out and errors. Tried reinstalling Netflix still no go. Weird how it worked now it is not. Error I get is code ui-113.
Update: got to login screen seems to be working now.. very weird.
Works now... Took couple of tries.. Thanks.
Using an AFTV from Canada and using a DNS service to view other regions. It was working yesterday but now having issues (got error aip-701)
anyone else?
Most of the times these issues are from ISP throttling Netflix traffic. The banner about problems streaming to "some devices" is up more than it is down I think.
Just to chime in on this topic, the latest update/new netflix app seems to have more connectivity issues that the old one, the old one was not perfect either, but I can tell you the newest firmware/netflix gives me errors on playback or startup/logging in quite frequently, I have 3 FTV's all rooted in my house. 1 is on latest update/netflix other two are on firmware just before that one, Netflix will stop working or give errors on new firmware way way more frequently than old ones. But it always works/plays if I switch to the other one. Hopefully they fix that
I haven't had any Netflix issues since the updated latest firmware. Been watching it every day.
For me, after I entered the login details, netflix app is crashing(basically it goes back to the page where it is launched from). I have created a thread for this issue http://forum.xda-developers.com/fire-tv/help/netflix-app-crashes-login-details-t2934865