Netflix instability

[tr3w]

Hi All,

I'm using Finless 1.4 (4.2) on my CX-919 and the stick is rock solid, except under Netflix.

Sometimes it works, once I could watch it for a couple of hours without problem, but usually it just stops playing after a minute or so. Sometimes the video stops, sometimes the audio.
I checked the logs, and looks like it gets SIGSEGV in the surfaceflinger or in the audioflinger.


Does anybody have the same issue? Is it a known Netflix bug?
Can it be just some instability problem with my stick? (I use the original powers supply, and the case of the stick is just warm.)

[spifey]

Hi All,

I'm using Finless 1.4 (4.2) on my CX-919 and the stick is rock solid, except under Netflix.

Sometimes it works, once I could watch it for a couple of hours without problem, but usually it just stops playing after a minute or so. Sometimes the video stops, sometimes the audio.
I checked the logs, and looks like it gets SIGSEGV in the surfaceflinger or in the audioflinger.


Does anybody have the same issue? Is it a known Netflix bug?
Can it be just some instability problem with my stick? (I use the original powers supply, and the case of the stick is just warm.)

I have the same issue as this. And it's present in almost everything I have ever tried.
Is there any way you can post the whole log for me? I would love to see it.

[tr3w]

I have the same issue as this. And it's present in almost everything I have ever tried.
Is there any way you can post the whole log for me? I would love to see it.

I will do... Obviously since I connected with adb to get the logs it works...
But it will crash sooner than later, so I'm not worried...

[tr3w]

Finally it died again:
Logcat: http://pastebin.com/aZCZtGzz

Interestingly, based on the log, the audiofinger died, but in the netflix app the video stopped and the audio played forward... Probably the app tried to recover and failed.

[tr3w]

I think it's much more complicated than this simple SIGSEGV...
I watched the logcat while played a movie, and I saw at least 3 different types of errors, and once it died without any thing in the logs...
But it looks like it's always audio related.

[spifey]

I think it's much more complicated than this simple SIGSEGV...
I watched the logcat while played a movie, and I saw at least 3 different types of errors, and once it died without any thing in the logs...
But it looks like it's always audio related.

Sorry I haven't replied any sooner. But I never received any emails about thread reply's. But the build prop samsung/GT-I9100. I think is only a 2.3 JellyBean phone. If I remember netflix uses this to decide it's libs. Maybe change this to a officially supported 4.2.2 phone model. Samsung Galaxy S4 model?

Also I have seen netflix back track on 1 or 2 video frames. Which seem random and sometimes does or doesn't lock up from this.

Could also be why if you move the video bar fast forward or rewind it locks up due to a touch screen issue.

But surly it can't be this simple. I was reading a thread from finless a few months ago. He pointed it out to be DRM and the reason why it's not the build prop.

But I think it can't hurt at this point. And may be worth a try.
Change the build prop to a Samsung Galaxy 4 and cross your fingers.
Don't forget to uninstall netflix first before you change it. Then reinstall after.

[tr3w]

Sorry I haven't replied any sooner. But I never received any emails about thread reply's. But the build prop samsung/GT-I9100. I think is only a 2.3 JellyBean phone. If I remember netflix uses this to decide it's libs. Maybe change this to a officially supported 4.2.2 phone model. Samsung Galaxy S4 model?

Also I have seen netflix back track on 1 or 2 video frames. Which seem random and sometimes does or doesn't lock up from this.

Could also be why if you move the video bar fast forward or rewind it locks up due to a touch screen issue.

But surly it can't be this simple. I was reading a thread from finless a few months ago. He pointed it out to be DRM and the reason why it's not the build prop.

But I think it can't hurt at this point. And may be worth a try.
Change the build prop to a Samsung Galaxy 4 and cross your fingers.
Don't forget to uninstall netflix first before you change it. Then reinstall after.

I don't think it's a DRM issue since sometimes it works flawlessly.
For this reason I also don't think it's a build prop issue.
After a week of trying I would say it mostly works. Sometimes I can watch a movie or one or two episodes of some series without any issue.
When a problem occurs it just stops playing the video, and if I try to seek it does the buffering forever.
If I go to Home and kill the netflix app in the task manager, I can restart the app, and play the video again, and sometimes its works for another 10 minutes, sometimes it dies sooner. But after the first error, the probability of flawless video playing falls rapidly.
Interestingly rebooting the stick doesn't really helps.

Thats why I thought it's maybe some general instability of the stick, although it doesn't feel particularly hot, and I can't see any other problems with any other apps...
(Except it umounts the "internal sdcard" once a week, but pushing the only button on the stick helps. )

[Tabber2013]

I'm using Finless 1.4 (4.2) on my CX-919 and the stick is rock solid, except under Netflix.

Is there actually a reason why you are using such an old rom? A lot of different roms and kernels have been released since, fixing a lot of problems.

[tr3w]

Is there actually a reason why you are using such an old rom? A lot of different roms and kernels have been released since, fixing a lot of problems.

Others reported wifi issues with Finless 1.5, so I thought I will wait for 1.6.

[Javinator]

Not sure if you figured out your issue, but I used the xposed framework fix found here: http://forum.xda-developers.com/show....php?t=2185130 to make Netflix work on my stick (the fix is related to Android 4.2+, not the finless build you're on so it should work regardless of whether you're on 1.4 or 1.6.

Sent from my Nexus 7 using Tapatalk

[tr3w]

Not sure if you figured out your issue, but I used the xposed framework fix found here: http://forum.xda-developers.com/show....php?t=2185130 to make Netflix work on my stick (the fix is related to Android 4.2+, not the finless build you're on so it should work regardless of whether you're on 1.4 or 1.6.

Sent from my Nexus 7 using Tapatalk

Looks really promising based on the discussion on that thread (and the original one), sadly I just canceled my Netflix subscription a week ago, so I can't test it...

But thanks anyway!

[spifey]

Not sure if you figured out your issue, but I used the xposed framework fix found here: http://forum.xda-developers.com/show....php?t=2185130 to make Netflix work on my stick (the fix is related to Android 4.2+, not the finless build you're on so it should work regardless of whether you're on 1.4 or 1.6.

Sent from my Nexus 7 using Tapatalk

I've tried this out. But for some reason my videos just kept wanting to buffer. Had to stop using it and switch it back. Video sometimes distorts and sometimes locks up the unit. I will have to try Finless 1.6a.

[ulises1954]

I am using the latest Neomode 1.7 with my CX-919 and also have the same Netflix lockup problems, Please see my post #85 and #99 at:

http://www.freaktab.com/showthread.php?7489-NEOMODE-HYBRID-ROM-1-7-MK802IV-UG007B-CX-919-MK809III-and-others-with-AP6210&p=104660&viewfull=1#post104660

http://www.freaktab.com/showthread.php?7489-NEOMODE-HYBRID-ROM-1-7-MK802IV-UG007B-CX-919-MK809III-and-others-with-AP6210&p=105166&viewfull=1#post105166

I am waiting and hope that Neomode could help us with this matter!

[Javinator]

I was having similar issues before on other ROMs. I just watched some Netflix successfully last night on Finless 1.6 (had to use the xposed workaround to get it to stop freezing). Worth a try with 1.6!

Sent from my Nexus 7 using Tapatalk

[Javinator]

Upgraded to Finless 1.6b last night and wiped my stick. Not sure if it has to do with the recent netflix app update, but I'm watching netflix right now with no xposed framework fix and it's working great. It might work since the app was updated (running netflix app version 3.0.1).

Give it a try!