Develop Bugs

[Q] Installing Hulu in other ROMs

I'm trying to nail down the exact procedure for installing Hulu into Roms other than SkyRaider. Specifically I am currently using HeyItsLouFroyo which after trying all the ROMs I could find worked the best.
So far I have downloaded the Hulupack.zip from the OP of this thread http://forum.xda-developers.com/showthread.php?t=764787&highlight=hulu
and the Hulu.apk.zip file from an update to the same thread http://forum.xda-developers.com/showthread.php?p=7903587&highlight=hulu#post7903587
I tried installing the "install_huluflash_player.apk" but it gave me an error during the install something to the effect of "Application was not installed". From there I installed the "Hulu.apk" which installed successfully. Next I tried "flash_fixed_final.apk" which gave me the same error as the original flash install. Just for grins I launched the Hulu app and to my surprise it seemed to be working until I got a message that said "Unfortunately Hulu is not supported on your platform" I have not installed the updated hulu.apk that I found later in the thread yet. I wanted to first start a thread and see if you guys can save me some time and frustration by telling me what the proper process is for getting this working.
Any help is appreciated. Thanks.

It looks like I may have posted this in the wrong spot. Can someone please move this to the correct spot or tell me how I can move it and where to?

Bump bump
Sent from my ADR6300 using Tapatalk

subscribed, i've actually been trying to figure this one one since 9am tried everything found in every 2.2 thread

Did you uninstall old files first?

daftlush said:
Did you uninstall old files first?
Click to expand...
Click to collapse
I did not. I just removed the flash app via Titanium and tried to install the flash_fixed_final.apk but received the same error as before.
Now I have no flash at all and still can't install flash. HMMM, now what?

Wait, alright I rebooted and after the reboot I was able to install the new version of flash. I opened hulu and it seems to be working now except it has this issue where the voices are super slow. I remember reading something about this in another forum but I think it was fixed by an update to the ROM. Anyone know how to fix the demon voices?

I have a 100% working Hulu now.
The fix for the demon audio was found in another forum. Here is what I did.
1. Opened Rom Manager
2. Selected "Download ROM"
3. Selected "Ihtfp69"
4. Selected "Goodies for 2.2+"
5. Clicked on the "Download" button
6. Checked the checkbox next to "Revert Audio Fix" and clicked OK.

Netflix Error 13007

I updated to the new netflix today and I am getting this error when attempting playback of any show. Anyone experience this?

Same here. Tried both my Samsung Galaxy S (T-Mobile Vibrant) with Android 2.2 (Bionix-v 1.3.1) and my wife's Vibrant (stock 2.2).
The error that appears when attempting to start a program is:
We are unable to start playback. Please try to restart it (13007)
After this, it appears to hang and then crash. Help!

It works fine on my samsung captivate.
still no solution.

I tried it with one item, got the same error 13007, and restored the previous version from backup. I am afraid that eventually they may turn off the old version and force an upgrade, but for now it works.

arpruss said:
I tried it with one item, got the same error 13007, and restored the previous version from backup. I am afraid that eventually they may turn off the old version and force an upgrade, but for now it works.
Click to expand...
Click to collapse
I did the same,with titanium,and it's working again.

could someone post the .apk of the older version, or tell me where to get it?

orlandoxpolice said:
could someone post the .apk of the older version, or tell me where to get it?
Click to expand...
Click to collapse
if no one can post the .apk of the prior version, can you tell me which version it was so i can search for it?

downgraded to 1.4.1 and it works fine.

orlandoxpolice said:
could someone post the .apk of the older version, or tell me where to get it?
Click to expand...
Click to collapse
It wouldn't be legal to post without permission from Netflix.

I did see on ArchosFans, that after two reboots, the new version starts to work.

Didn't seem to do the trick
Sent from my SAMSUNG-SGH-I897 using xda premium

Yes it is working
Yes 2 reboots on my Archos 101 and is working, thanks a lot

Two reboots on my Archos 70 seems to do nothing -- worse when I uninstalled it, and installed the 1.4xx version from Titanium Backup, the old version insists I upgrade!

jerryasher said:
Two reboots on my Archos 70 seems to do nothing -- worse when I uninstalled it, and installed the 1.4xx version from Titanium Backup, the old version insists I upgrade!
Click to expand...
Click to collapse
I know: I hate that they force "upgrades" like that.
However, the new version seems to work now.

Has anyone found a fix for this? The two reboots thing did not work on my 101.

Any ideas on this guys? a buddy of mine is having this issue with his Vibrant.... thoughts?

Not working on my Archos Internet 70
The last version forced me to upgrade now all I get is 13007 errors. Anyone know what that means? I tried uninstalling, resinstalling, killing all running apps, uninstalling other apps. nothing works.

Has anyone got this working, I'm really pissed I can't get it going.

OK, guys. I found a work around for Netflix app. I got it working on two different 101s. Hopefully this wasn't posted already. If it was disregard this.
First you need to have Arctools installed to get the android market. If you don't already have it on your device, here is a step by step video.
http://www.youtube.com/watch?v=LWyjeMXQMOU
Make sure you follow step by step. I didn't do the format the first time, and it wouldn't install the market right.
Once you have the market on there, you need to download the old version of netflix (1.4.1). APK is in post. Download and install the app. When you first launch the app it will tell you you need to upgrade, click the OK box. The next box that shows up will be the "Complete action using" box. It should show you the two options "Market" or "search". When the box comes up, press the back arrow. This should take you to the Netflix home page, and there you go, you can stream! The reason you need the Android market is because without it the "You must upgrade" won't give you an option on how to upgrade. (see attached pics)
A couple of side notes.
1) If the "Complete actions using" box doesn't come, you need to clear the market as the default app. To do this go to Settings>Applications>Manage applications>Find the Market in the list and click "Clear Default". That should force the box to pop up.
2) The issue I had on mine was once I start streaming something the back button freezes the video. The only way out is the home button or wait till force close pops up. The one I did for my friend didn't do that. When the back arrow was pushed on that one the "need to upgrade box" pops up. If it does, follow the same steps from above. (Press OK, then when the select option box pops up just click the back arrow). I know the Force close is an inconvience, but hey, at least you have streaming video.
I don't know how long this will work, or if they plan on patching so you can't do this (or fix their stupid app). Hopefully this helps the people that couldn't get the app working with the multi-reboot method.
If it works for you, please make sure you hit the thanks button.

As of today 12/15/11, Netflix released an update for their app, and it fixed (at least for me) the 13007 error. So upgrade to the newest version and test it out!

New Netflix app not working (worked before updating to 51.1.4.1_514013920 fixed)

The old Netflix app worked fine. I am in Australia, and use UnoTelly DNS service.
I just updated to pre-rooted 51.1.4.1_514013920 fixed and tried the new netflix app. It loads fine, but when I select a title to play, it gets to about 6% buffering and says: We're having trouble playing this title right now. Please try again later or select a different title.
I tried clearing the Netflix data and cache as was mentioned in another post, but no luck.
Anyone else managed to get past this, or have any ideas? Otherwise I guess I will have to downgrade again, which sucks, I like the screen mirroring

modstore said:
The old Netflix app worked fine. I am in Australia, and use UnoTelly DNS service.
I just updated to pre-rooted 51.1.4.1_514013920 fixed and tried the new netflix app. It loads fine, but when I select a title to play, it gets to about 6% buffering and says: We're having trouble playing this title right now. Please try again later or select a different title.
I tried clearing the Netflix data and cache as was mentioned in another post, but no luck.
Anyone else managed to get past this, or have any ideas? Otherwise I guess I will have to downgrade again, which sucks, I like the screen mirroring
Click to expand...
Click to collapse
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?

rbox said:
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?
Click to expand...
Click to collapse
Yes, I updated to 51.1.4.0 first, boot menu is installed fine, and everything else works as it should.

rbox said:
Were you sure you followed the instruction that tell you to update to 51.1.4.0 before going to 51.1.4.1?
Click to expand...
Click to collapse
Just in case it's relevant, I updated to 51.1.4.0 by doing a restore from backup through clockworkmod recovery, not an install from zip.

modstore said:
Just in case it's relevant, I updated to 51.1.4.0 by doing a restore from backup through clockworkmod recovery, not an install from zip.
Click to expand...
Click to collapse
You need to install with the full zip. Backups don't include firmware.

rbox said:
You need to install with the full zip. Backups don't include firmware.
Click to expand...
Click to collapse
Ahh right. Thanks, I'll install 51.1.4.0 then do boot menu, then the latest zip and hopefully that fixes the problem. Cheers.

rbox said:
You need to install with the full zip. Backups don't include firmware.
Click to expand...
Click to collapse
I installed 51.1.4.0 and tried Netflix once it completed. Netflix loads, but when I try to watch something, it gets to 15% buffering or so and then the app just exits, no message or anything.
I installed boot menu and updated to 51.1.4.1, but still the same issue. I tried clearing Netflix data/cache and re-installing, but no progress.

modstore said:
I installed 51.1.4.0 and tried Netflix once it completed. Netflix loads, but when I try to watch something, it gets to 15% buffering or so and then the app just exits, no message or anything.
I installed boot menu and updated to 51.1.4.1, but still the same issue. I tried clearing Netflix data/cache and re-installing, but no progress.
Click to expand...
Click to collapse
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.

rbox said:
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.
Click to expand...
Click to collapse
Yep, this is the file I used: bueller-51.1.4.0_514006420-rooted+updated.zip

rbox said:
And you're sure you used the updated zip? Getting to 15% is something different though. Usually it stops before it reaches double digits. I do know a few international people were reporting issues with the latest Netflix.
Click to expand...
Click to collapse
In case it's relevant, I have a rule in my router to redirect 8.8.8.8 to my router's IP so it is forced to use my DNS overrides, as I believe the new app hardcodes Google's DNS.

modstore said:
In case it's relevant, I have a rule in my router to redirect 8.8.8.8 to my router's IP so it is forced to use my DNS overrides, as I believe the new app hardcodes Google's DNS.
Click to expand...
Click to collapse
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.

rbox said:
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.
Click to expand...
Click to collapse
Yeah, I used to have a Roku before the Fire TV and it required the redirect to be setup and worked fine once it was. The app would do the check on startup and exit if it failed.
It works fine on my computer too.

rbox said:
Hrm. Strange. It might be a temporary thing, not sure. Maybe try again tomorrow? You sure the redirect is working? I think google's dns has 2 ips... maybe you need to redirect both.
Click to expand...
Click to collapse
I grabbed the log of when it happens, in case it gives any insight.

modstore said:
I grabbed the log of when it happens, in case it gives any insight.
Click to expand...
Click to collapse
Something is crashing... weird.

rbox said:
Something is crashing... weird.
Click to expand...
Click to collapse
I don't know if it's just a coincidence, but I de-registered and re-registered the Fire TV to my account and it's working now Thanks for your help rbox.

[Q] Just want Xfinity app to work via Ethernet

Last summer I had my Fire TV rooted and set up with Xposed to fake Wifi access so that I could use my Xfinity app via ethernet. Previous to that I was using FOX-FI and my phone as a Wifi hotspot but Metropcs blocked the ability to do so.
All was well until the unit started turning itself off a few months ago. I was sent a replacement that I believe was a refurbishment and it NEVER updates (i.e. never updated to the Prime option on the left side of the menu) -- which would be great except I haven't been able to root it (most likely it's unrootable). Now I have a 3rd one and I just need to know how I can run my Xfinity TV GO app on it (after it's sideloaded) without having to use WIFI. Also, where is the list of serial numbers or whatever it is that allows one to know if the box can be rooted?
Thanks in advance.

The newest version of Xfinity Go does work over ethernet. I do have a lot of buffering issues when trying to watch on demand video though.

Aobeta said:
The newest version of Xfinity Go does work over ethernet. I do have a lot of buffering issues when trying to watch on demand video though.
Click to expand...
Click to collapse
Really? I'll download the new app then sideload it to see if I'm still being told to connect via Wifi. I'll update later.

I'm getting the errror message "Sorry ,we are experiencing some difficulties. You can continue using the app, but not all areas may be working." What do you think the problem might be? I searched for this particular error but only viewed unanswered questions.

And when I went to 'Bookmarked' This popped up:
"An unknown error occurred during this request. Please try again.
Instantiation of [simple type, class com.xfinity.playerlib.model.tags.Network] value failed: Invalid int: """

Are you sure you have the newest version? Its at version 2.4.2. When I tried an older version, I would get that error about experiencing difficulties. But the new one works fine. And you should get a popup about it working with mobile data the first time you open it.

Aobeta said:
Are you sure you have the newest version? Its at version 2.4.2. When I tried an older version, I would get that error about experiencing difficulties. But the new one works fine. And you should get a popup about it working with mobile data the first time you open it.
Click to expand...
Click to collapse
Yep. I went and downloaded the lastest from Google Play after typing my response. This one:
https://play.google.com/store/apps/details?id=com.xfinity.playnow

Hmm, did you get the popup about mobile data now working at least? I have no clue why it wouldnt work for you unless you are on an old version.

Aobeta said:
Hmm, did you get the popup about mobile data now working at least? I have no clue why it wouldnt work for you unless you are on an old version.
Click to expand...
Click to collapse
It's still not working. I included the link to the version I installed today. So, I'm not sure what the problem could be. There's a version of Xfinity for X1? users with cloud that I don't believe applies to my account. I've retried it a few times now and it shows the same message

ihadtoregister said:
It's still not working. I included the link to the version I installed today. So, I'm not sure what the problem could be. There's a version of Xfinity for X1? users with cloud that I don't believe applies to my account. I've retried it a few times now and it shows the same message
Click to expand...
Click to collapse
If you don't see that mobile data popup then you likely do not have the newest version. Downloading from play store may not always get you the newest version because the version it lets you download is based on what device you download it from. Google "xfinity go apk 2.4.2" and find it that way and make sure you are downloading version 2.4.2.002. If that doesn't work, I have no more advice for you because I have no clue what the issue is.

Aobeta said:
If you don't see that mobile data popup then you likely do not have the newest version. Downloading from play store may not always get you the newest version because the version it lets you download is based on what device you download it from. Google "xfinity go apk 2.4.2" and find it that way and make sure you are downloading version 2.4.2.002. If that doesn't work, I have no more advice for you because I have no clue what the issue is.
Click to expand...
Click to collapse
I tried installing that same file on the older rootable device that won't update and the new non-rootable one and it's the same "experiencing difficulties" error. I was able to navigate to the 'Live' streaming area and when clicked to view a channel I got the "No Wi-Fi Connection. You must be on Wif-Fi to stream video content." pop-up. So, that's the true issue --- this version isn't ethernet compatible. I also tried to google for that apk and there were only a few sites that didn't seem to be safe. Would you be able to upload the apk that you have working via Ethernet?

https://www.dropbox.com/s/7arau0nbu67vbud/XFINITY_TV_Go.apk?dl=0

Aobeta said:
https://www.dropbox.com/s/7arau0nbu67vbud/XFINITY_TV_Go.apk?dl=0
Click to expand...
Click to collapse
Thanks.

ihadtoregister said:
Thanks.
Click to expand...
Click to collapse
Could either one of you please send me that file? The dropbox link is dead.
Thanks In Advance

jhawk757 said:
Could either one of you please send me that file? The dropbox link is dead.
Thanks In Advance
Click to expand...
Click to collapse
Here you go

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom menu issues

Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18

For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.

New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.

Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.

Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.

drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.

Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.

drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.

Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!

drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...

Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!

I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.

drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.

Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.

Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.