Last Update: 11-9-20 | Updated ventz-media-pi for new Chromium version (v.84+) and new WideVine setup: v.4.10.1679.0+ NOTE: You MUST re-download and re-run it from this date to fix – lots of changes!
Last Update: 11-2-20 | Updated libwidevinecdm.so_.zip to v.4.10.1679.0 within ventz-media-pi
Last Update: 7-22-20 | Updated .desktop with Chrome User Agent string for CrOS Chrome/77.0.3865.120
Last Update: 7-20-20 | ~redacted~ company reached out about creating an official package, also there are conversations happening with ~redacted~ company about official support of the Pi
Last Update: 5-6-20 | Specify that “Raspbian with desktop” is assumed and tested
Last Update: 4-7-20 | Fixed screen tearing

If you just want to take a Raspberry Pi 4 (as of today!) and turn it into a fully functional “Media” center by just pasting one line, here it is:

SSH to your Pi (don’t run from the Pi console if you want pretty graphics :)) and run:

This will produce the following (click to see larger image):

Reboot, and then from the Application Menu (top left) -> go to “Internet” -> open “Chromium (Media Edition)

You are now ready to use your Raspberry Pi on Netflix, Hulu, Amazon Prime, Disney Plus, HBO, Spotify, Pandora, and many others.

If you need to change any browser Settings, do so via the “Chromium” browser and not the “Chromium (Media Edition) – both are the same browser, so the settings are the same. The “Media Edition” (just a custom launcher with the user-agent) cannot load the settings since Chromium thinks you are launching it on “Chrome OS”, and when it checks for the Chrome OS language settings it crashes since they don’t exist.

At last, all this assumes the latest version of Raspbian with desktop (not Debian/Ubuntu! –
https://downloads.raspberrypi.org/raspbian_latest), and you can re-run the curl and sh as many times as you want without any harm.

If you are curious about some of the background and details on why you can’t easily run Netflix (and others) on your Pi and how to solve it, you are welcome to go look at my “development” blog post article: http://blog.vpetkov.net/2019/07/12/netflix-and-spotify-on-a-raspberry-pi-4-with-latest-default-chromium/

Enjoy!

424 Thoughts on “Raspberry Pi Netflix One Line Easy Install – along with Hulu, Amazon Prime, Disney Plus, HBO, Spotify, Pandora, and many others

  1. origna_traveler on November 17, 2020 at 5:55 am said:

    Chromium has audio problems with some web video streams. Medium Edition does not resolve this issue.

    • Can you list which streams so that it helps others?

      I believe you need what Mark posted below in the comments for that scenario:

      • Today’s upgrade of chromium-browser to 84.0.4147.105-rpt3 (reported by sudo apt upgrade) seems to now detect that BlueALSA is running (on my system) and disable the audio sandbox automatically, so there’s no need to add –disable-features=AudioServiceSandbox to the command line for launch. I’ve also found that after re-curling and re-running ventz-media-pi and rebooting, Spotify runs happily in the ‘normal’ Chromium browser (i.e. without the user agent switching on Chromium (Media Edition) – would that make sense? I haven’t tested this fully though, YMMV…

  2. Ventz,
    Thank you for the one liner. Works great!
    I have a Raspberry Pi 400 and by default there is no audio in Chromium (HDMI or BT). A lot of searching and trying things did not resolve. Lots of dead ends.

    This person posted in a Raspberry forum how to run chromium with something disabled and the audio works through Bluetooth.
    https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=291066#p1760404
    Command that worked

    I’ve been trying to get this command to launch chromium (web edition) so that possibly the audio will work. Last hurdle to having a streaming machine.

    Thanks for any help! Newish to Linux…

    • Mark – what you want is to open the

      file, locate in

      , and change lines that have the “Exec=” (lines #6, #19, #23, #27)

      After that selecting the “Chromium (Media Edition)” should do what you need.

  3. I am running Pi 4B 8GB version overclocked to 2GHz with cooling and I’m getting some tearing in Netflix. Is there a way to fix this?

    Best regards

  4. Alec Devlin on November 13, 2020 at 3:38 pm said:

    If the version of the Raspbian OS installed was the one dated 20-08-2020
    for the 32bit version of Raspbian OS from the following image,
    2020-08-20-raspios-buster-armhf-full.img then updated with the following
    commands:-
    sudo apt-get update
    sudo apt-get upgrade

    after that then a reboot.

    Then I would expect the version of Chromium to be 84.0.4147.141, then
    execute the easy one line script, start up the Media Edition of Chromium
    it should tehn work well with the Netflix and Prime Video stuff etc.

    Hope you get it working, it seems to work good on my Pi 400 4GB version.

    All The Best.

    Alec.

  5. Hi,

    Just installed the latest scripts on Raspberry Pi 4B 8GB. When trying to play Netflix I get an error C7701-1003. Chromium is Version 78.0.3904.108 (Official Build) Built on Raspbian , running on Raspbian 10 (32-bit).

    Any ideas?

    Best regards.

    • All is good now. Just updated Raspbian with the latest packages and rerun the scripts.

      Thanks for this feature. Works great.

      Best regards

  6. Alec Devlin on November 10, 2020 at 2:00 pm said:

    WideVine setup on Raspberry Pi 400, Latest Raspbian OS (32 bit version.)

    Ventz,

    Recently I have tried to install the WideVine software on my new Pi 400,
    latest model of the Pi, Faster Processor, 4GB, and all built into a nice small
    keyboard.

    I have the latest Pi software (32 bit) installed from Raspberry Pi website, runs fine.
    But until today I couldn’t get the Chromium Browser to work on either Netflix
    or Prime Video, or Spotify, however I can report that having used the latest
    software ventz-media-pi

    All of the above 3 sites work great.

    I also tried HBO and BritBox they worked without any problems as far as I could
    see.

    So, Many Thanks for the work you have done on this, it certainly works now for sure.

    Cheers,

    Alec.

  7. Ted Torres on November 8, 2020 at 1:35 pm said:

    Just tried your 11-09 mod to chromium (netflix, etc) to fix Chromium ver 84.

    WORKS GREAT !

    Thanks so much for your effort on this!

  8. @UPDATE TO EVERYONE SUBSCRIBED TO EMAILS – FIX for Chromium v84+@

    Updated ventz-media-pi for new Chromium version (v.84+) and new WideVine setup: v.4.10.1679.0+
    NOTE: You MUST re-download and re-run it from this date to fix – lots of changes!

    • Hi~ Ventz!

      Could I receive the fixed solution of widevine for Chromimum84???

      I took update the Pi4 include chromium….. oh my Netflix……

      I’m look forward your reply…

    • Thanks a lot Ventz!

      I solved the problem via your fixed solution.

    • Grim Static on November 8, 2020 at 7:02 am said:

      You are awesome! Thank you for maintaining this one-liner fix and sparing us from the recovery image download annoyances!

    • Maximillan on November 8, 2020 at 8:37 am said:

      Thank you for the fix

    • Thank you!!!!!

    • Thanks Ventz!

      Works like a charm

    • DAVIKING on November 9, 2020 at 8:41 pm said:

      Ventz, firstly, thanks for you kind work to this community. Nextly, I love what you’ve done to make netflix work.

      Now, as of today, 11-09-2020 @1936cst, Nexflix throws the error:
      Error Code M7701-1003
      This references Widevine Content Decryption Module.

      All other entertainment stream I us, works fine.

      • Daviking – check what version of the media script you last used. Between the Chromium changes, and the WideVine changes, it makes sense to re-run the ‘ventz-media-pi’

        With Netflix specifically, every once in a while they+Chromium over-cache some stuff. After you re-run the install, if you can – clear the cache/etc, quit the browser, reboot. If it’s the cache, that always fixes it.

    • Hi Ventz,
      I did this update but found that I was not getting any audio using Chromium v84 for Spotify or Youtube (or anything else played in the browser). My audio setup uses Jack on top of ALSA to a USB sound card (i.e. not HDMI or 3.5mm socket). I have found a workaround which is to launch the browser with the following option in the command line:

      –disable-features=AudioServiceOutOfProcess

      I just added this to the launch command for Chromium (Media Edition) using the Pi ‘Main Menu Editor’.

      Chromium v84 now successfully launches Jack clients for Spotify, Youtube, etc. This may work for other users who continue to have sound problems after updating to v84 and the latest WideVine.

      Needing this workaround seems to me to point to a bug in Chromium v84 – I actually found it in a bug report that said it was fixed in v79….

      -Paul

  9. Hey I think the browser is giving me a dns issue? For some reason certain sites like Facebook and Spotify will come back “could not resolve” the only work around I’ve found is a reflash. Can I give you more details on the problem? Or do you know of anyone else who had a similar problem with a possible fix? Thanks for all the help always.

  10. @EVERYONE – UPDATE@

    Looks like the latest push of Chromium itself was the issue.
    (Nice catch Aaron!!)

    Please check that you are NOT running: 84.0.4147.105-rpt1
    And instead, that you ARE running: 84.0.4147.105-rpt2

    • fivenote on November 7, 2020 at 10:56 am said:

      Hi Ventz! I am running 84.0.4147.105-rpt2 but it still doesn’t work. I ran your latest script above, cleared cache, and rebooted. What else should I check?

    • Hi Ventz,
      Before I mess up my setup, can you please explain how to ensure I get the 84.0.4147.105-rpt2 version?

      (currently I’ve reverted to my old Chromium 78 set up and put an apt-hold mark on the three main Chromium packages to stop them getting upgraded….)

      • I also noticed that the Chromium 84 upgrade has stopped audio routing from the browser to Jack (Qjackctl) – such that I no longer get audio on youtube videos. Chromium used to open a soft Jack connection whenever a video played and now it does not launch anything in the Qjackctl connection dialog. Think I’m going to stick with 78 for a while…..

    • I’m on 84.0.4147.141, and it is not working (Error code C7701-1003) on a fresh Raspbian install with running your oneliner after upgrading everything. Any suggestions?

    • fivenote on November 7, 2020 at 3:45 pm said:

      Here’s how I finally go WIDEVINE to work again…

      (1) As mentioned to do, I did an apt-get upgrade to get chromium to 84.0.4147.105-rpt2.

      (2) Ran the widevine-flash_armhf.sh script (easy to find with a web search). It puts libwidevinecdm.so under /opt/WidevineCdm. That seems to be where the updated chromium wants to find it, and maybe why re-running ventz-media-pi isn’t working right now.

      So for the ventz-media-pi script to work again, it may just need to change where it puts libwidevinecdm.so.

      Thanks to Ventz for all his good work here!

      • fivenote – I am guessing you installed Vidali, because that config is customized for Vidali 🙂

        I actually pushed out an updated version which configures for the new widevine config structure within the latest Raspberry Pi OS Chromium, but I am assuming the old version is cached on the CDN. Just did a manual redirect to the server until the CDN updates.

        Here are the big updates that are needed:

        1.) /opt/WidevineCdm (as you mention, a new dir – although this can be arbitrary – see bellow)
        2.) manifest.json
        The one Vidali has is actually incomplete.
        Here is the full one per docs:

        As new versions of WideVine come up — it will have to be updated.
        This has prompted me to stop using .zips, and just start using files directly, since everything is behind the ventz-media-pi script anyway.
        3.) The new arm dir: /opt/WidevineCdm/_platform_specific/linux_arm
        This needs to contain “libwidevinecdm.so”, and everything after /opt/WidevineCdm (used in pointer – see bellow) is actually required as is.
        4.) A pointer for Chromium (under the pi user) to the new hook for libwidevine under: ~/.config/chromium-browser/WidevineCdm/latest-component-updated-widevine-cdm

        This (Path) can technically be any arbitrary location. But the “pointer” file has to be *exactly* that.

        • fivenote on November 8, 2020 at 9:53 am said:

          Thanks for the fix Ventz!

          Re Vivaldi… I never installed that. I just let apt-get upgrade chromium and ran widevine-flash_armhf.sh. It put libwidevinecdm.so and a manifest under /opt/WidevineCdm and that worked.

          I’m glad ventz-media-pi is working again. It’s a simpler solution.

    • Hi, when I check my chromium version it’s 84.0.4147.141 how do I install 84.0.4147.105-rpt2 please?

      I’m very new to Linux just got my pi4 only bought it because I saw this fix.

      And it’s just my luck that it broke.

      Thanks for all your hard work.

      • Vaz – open a terminal and type:

        When prompted at each step, “y” to continue/confirm.

    • Larry Harris on November 7, 2020 at 10:15 pm said:

      I am running 84.0.4147.105-rpt2 and it is not working. I cleared browser cache reran scripts and rebooted no success. how deo you go back to Chromium 78 until this is working?

  11. Not working. This is frustrating…….

  12. Not working. This is frustrating. Even when I do the curl command and sh command when I go to my Chromium settings it errors out. Error code: RESULT_CODE_KILLED_BAD_MESSAGE. WTF….. What is going on with this error 83 BS? I mean what is the problem? What needs to be done to get this working?

  13. HIMANSHU on November 6, 2020 at 2:50 am said:

    Hi,
    Somehow Netflix stopped working as of now. Hope you will look into it and fix it.

    • Christian on November 6, 2020 at 3:26 pm said:

      Hello together,

      also the same problem. Updated chromium to 84 nothing is working. Also tried the hints posted below nothing helped. When I take a closer look at the components widevine version shows 0.0.0.
      Any ides how to fix the problem and make it work again?
      Thanks for your work up to now.
      Christian

  14. Ted Torres on November 5, 2020 at 4:09 pm said:

    Today my RPI4 updated, and downloaded a new version of Chromium….
    that broke your “media edition”

    i Tried your updated “media edition” (page said updated 11/2/2020.)

    Does not work on Chromium Version 84.0.4147.141 (Official Build) Built on Raspbian , running on Raspbian 10 (32-bit)
    today is 11/05/2020

    any thoughts?

  15. fivenote on November 5, 2020 at 11:37 am said:

    Same problem… no sites that need WIDEVINE work after update to Chromium 84.0.4147.141 on rpm 4. I re-ran ventz-media-pi to get the latest version and update them Chromium desktop file, but still nothing works.

    Love this solution and hope it can get working again!! Thanks for your help.

  16. Netflix on Pi on November 4, 2020 at 10:30 pm said:

    Error message for my earlier post just now: We’re having trouble playing Netflix. Please visit chrome://plugins, and make sure both “Netflix” and “Widevine content Description Module” are turned on, and the “Always Allowed” setting is checked.

    Error Code: C7701-1003

  17. Netflix on Pi on November 4, 2020 at 10:10 pm said:

    Doesn’t work anymore after today’s update of chromium (84) from raspberry pi “apt update”.

    Please help

  18. @UPDATED LIBWIDEVINE@

    Updated libwidevine (libwidevinecdm.so_.zip) to v.4.10.1679.0

    If you have already installed, you can either re-run ‘ventz-media-pi’

    or, if you prefer to do this manually/inspect it:

    Pull the updated:

    Extract it:

    Move the copy to Chromium:

    • Aaron Guidazzi on November 5, 2020 at 6:15 am said:

      Hello…i already had updated libwidevine to that version….i tried to update again, but after the chromium update of today in raspberry os netflix is not working anymore…
      Any suggestions or a newer libwidevine? The error code is c7701-1003 which seems to be related to libwidevine and drm

      Thank you very much
      Aaron

      • Aaron – can you check the md5/sha1 of what you had and the latest libwidevine.so files? If the version is the same, they should be identical.

        Here is the older version too (confirmed last working), just in case: https://pi.vpetkov.net/libwidevinecdm.so-OLD.zip

        • Doesn’t work for me too, after the latest update of the Chromium for Raspberry Pi OS.

          Hi, how do I check the md5/sha1? Please advise.

          Thank you in advance.

        • I checked and it is the same…i downloaded it from your post this summer…
          But the problem is not the libwidevine…
          I updated chromium in raspbian and went from version 7x to 8x and also chromium ffmpeg plugin got updated and after that netflix stopped working…then i tried to update libwidevine but your python script was showing same version even before…
          The funny thing is that I have also vivaldi installed in my raspberry…and it was not working….it got some updates in the time..and it is also based on chromium 8x and now it works very well ( with chromebook user agent)….i was able to enable gpu acceleration in vivaldi also and it runs smoother than chromium in my opinion both for Netflix and amazon prime video…

          • Exactly. The latest apt update upgraded the Chromium from v76 to v84.

            Btw, how did you configure Vivaldi to play Netflix? Could you help me to do it? Thank you in advance.

          • Today raspbian is got another update of chromium and everything went back to normal…so I guess there was a problem with yesterday’s build…
            No need to do anything except updating to latest version…

          • Aaron — this is great to hear, because I was going crazy trying to figure out why it was breaking…everything from my side looked good.
            Looks like Chromium itself was broken and Rasbperry Pi pushed the fixed version 🙂

          • fivenote on November 6, 2020 at 9:34 am said:

            Still not working for me. I got the second chromium update to 84.0.4147.105-rpt2 and the 11/2/2020 libwidevinecdm.so_.zip v.4.10.1679.0 from Ventz. I cleared browser cache and rebooted. Still, no DRM sites work.

            Anyone still having problems? What’s missing? Thanks.

          • I am actually curious if it’s just the user-agent that needs to be upped, since the new version of libwidevine has a “minimum” agent requirement. However the current upgrade is a minor version release, which means the previous should have had the same issue — so this breaks my theory. I need to look into this, simply have not had free time yet. (I think the update came out less than 2 days ago :)). I wish PiOS had upgraded to a higher version of Chromium.

          • SixWasNine on November 6, 2020 at 11:28 am said:

            @fivenote

            Still facing the same problem even after the latest chromium update.

    • Paul-E on November 5, 2020 at 8:31 am said:

      Hi Ventz,
      I really appreciate your work on this – having spotify on my pi is great!
      I did an ‘update and upgrade’ on my pi this morning and it upgraded Chromium to this version:
      Version 84.0.4147.141 (Official Build) Built on Raspbian , running on Raspbian 10 (32-bit)

      This has unfortunately stopped the Spotify web player working in the Chromium (Media Edition). (I’ve tried running your curl and sh ventz-media-pi and rebooting but the spotify web player now asks for me to change Chromium settings to enable playing of protected content. When I go into Chromium settings, this setting is already enabled so I’m guessing something else has changed?

      Is this problem something you are aware of?

      Thanks! Paul

      • Paul – I’ve noticed that something happens with Chrome and caching. Can you first try an incognito window, and and if you can, clearing history/cookies/etc. There is definitely a “drm cache” if you will, that happens via the data store and html5 store. It’s the same reason why Netflix will start throwing errors randomly when people upgrade the browser (or sometimes libwidevine).

        • Paul-E on November 5, 2020 at 2:45 pm said:

          Hi Ventz,
          I cleared history etc. in normal Chromium, then launched in Chromium (Media Edition) an incognito tab and went to the spotify web player. The player initially comes up as expected but when I try and log in I just get the ‘Enable secure playback in your browser’ screen come up. Can’t seem to get past this…. Any other ideas of what I can try?
          Thanks, Paul

          • Paul-E on November 5, 2020 at 3:36 pm said:

            I’ve also tried using a ‘Guest’ account on Chromium (Media Edition) and get the same behaviour – webplayer initially comes up but when I try to play something it asks for log in, I log in, get the ‘Enable secure playback in your browser’ screen.

    • Maximillan on November 5, 2020 at 10:39 am said:

      getting error on chrome://plugins it says it cant be reached
      i tried going to chrome://settings/content/ there is nothing that can be set to allow always
      also getting error in widevine in chrome://components

    • Do you have a fix from the newly update Chromium 84?

  19. Neat! Thanks for the excellent work!

  20. This is brilliant work. i would like to run the media edition on startup automatically. Is the right way to do this adding

    /usr/bin/chromium –kiosk –ignore-certificate-errors –disable-restore-session-state “http://www.domain.com”
    to:
    /etc/xdg/lxsession/LXDE-pi/autostart

    I want to make sure I am runnng the media edition launcher on start up so there is no tearing.
    Thanks in advance 🙂

    • Eugene on November 5, 2020 at 8:29 am said:

      I was trying this too and i found out that i had to use the Chromium Media icon command, i right clicked the icon and exposed the icon command when its clicked something like: $ chromium-browser %U –user-agent …

  21. Really easy setup script! Thanks!

    Does anyone have any debugging suggestions for skippy audio running netflix on a Raspberry Pi 4? It’s not too bothersome, but a little choppy

  22. This worked first time for me excellent article finally got britbox working

  23. Alexandre Leite on October 13, 2020 at 10:28 pm said:

    hi! amazing job! very nice!
    So, is it work with raspiberry pi 3? Ive tried but some error has occurried.
    Thanks!

  24. Architects on October 12, 2020 at 6:36 pm said:

    Sorry to be ‘that’ guy but is there a way to make this work with the 64 bit version of Raspbian Buster? It worked just fine for me on the 32 bit variant but recently reinstalled the OS using the 64 bit variant and cannot get this to work correctly. I apologize in advance, I’m a total novice when it comes to Linux and am trying my damndest to learn.

    • Not at all – unfortunately there isn’t currently a 64bit libwidevine (or Chrome lib to libwidevine) hook available. I would have to imagine at some point Google will make this happen for their own chromebooks as they become 64bit.

  25. robin33 on October 8, 2020 at 2:08 am said:

    Hello Ventz,

    J’ai tout installé sur un raspberry PI4 8G° de ram avec os raspbian

    ca marche mais le son est saccadé ca saute de morceau en morceau

    Merci pour votre aide
    Robin

  26. David Davidson on October 7, 2020 at 8:50 am said:

    Hi,

    I just installed your your one-liner workaround and seems to work like a charm in my RPi 3B+, but there seems to be one problem. Netflix works fine, but Spotify doesn’t. As soon as you load one song, it plays for one second and then jumps into the next.

    Did anyone find thyself in a similar situation?

  27. AleXSR700 on October 6, 2020 at 1:37 pm said:

    Hello,

    I was wondering how to uninstall this mod. Is there a way to undo all changes?

    • To un-install, it’s just reversing the order, open a terminal and:

  28. rreddy78 on October 6, 2020 at 8:37 am said:

    As i use a jetson nano (ARM 64) i have to run chromium 32 version in a docker container

    https://github.com/teacupx/docker-chromium-armhf

    I have followed the steps given here and still DRM is not working.

    Do you think i need the latest widevnecdm in order for it to work ?

    The chromium 32 in the docker is v85.0.4183.121

  29. Hi,

    unfortunately when I want to use the Spotify Web-Player I get the message that this browser is not supported. :/
    Is there any way to fix that?

    Thanks for your help, keep up the great work!

  30. Hi,
    thank you very much for your work, I’ve been enjoying the fruits for quite some time now.

    As of yesterday, on 2 separate raspberry pi’s, both Pi 4, with latest Raspbian update I can’t get to enter Netflix.com.
    It gives a “This site isn’t available” error while ANY other URL and video play works fine.

    Did anyone ever encounter that and found a fix?

    Thx a lot

    • That happened to me once too. I cleared my cache and cookies and then just ran the script again, reset the pi and it was working just fine. Hope that helps!

  31. Nice work. This worked first time on my RP3 that I imaged just this week. Super happy now that Netflix and spotify are working. Also soundcloud and mixcloud.

    Chromium settings does crash with a “Aw, snap!” window. Has anyone seen this?

  32. This is very interesting. I haven’t read all the technical details about the solution but have a general understanding on how it works and why it’s needed on the RPi.

    However, the caveat in the end does apply to me: I am running Ubuntu. So my first question, if anyone would have the time and knowledge to enlighten me: Why is this solution not applicable on Ubuntu?

    Second question would be: Is there any realistic solution for Ubuntu on RPi?

    Awesome job anyway. It’s rather annoying that a potent little computer like the RPi has to suffer from limitations like this.

  33. I had the same problem..Did all what you adviced, but no result.
    Same as first reply above:
    Invalid desktop entry file:“ /usr/share/applications/chromium-media-browser.desktop”my raspberrypi vision is raspberrypi4,4GB 64bit ,
    how to solve this problem?thank you!

    nb Your advice worked for me with the 32 bits version!

    • Hi John,

      i had the same problem.

      Check in Preferences -> Add / Remove Software if “web browser” is installed.

      I have changed it to “Chromium web browser, open-source version Chrome”, rebooted the system and the problem was fixed. Now i can use “Chromium Media Edition” without any problem.

      Regards
      Steve

  34. Matthew Jones on September 14, 2020 at 11:58 am said:

    This really worked. I am so amazed. Worried a bit cause I do not know anything about most of this stuff but for the most part works as advertised. Use it!!

  35. I used your code and everything works fine, except for HBO Max. Every time I load a movie or show, I get an error of ”
    Can’t Play Title”. Do you have any type of fix for this issue?

  36. hola , ahora tengo la raspberrypi4 ,pero funcionaria bien utilizarlo en la 3 a+? utilizando la misma tarjetasd con raspbian ya con chromium media edition

  37. Hello Ventz,

    i did the installation of Chromium-Media as mentioned above, but i get the following message:

    Wrong .desktop-file: ‘/usr/share/applications/chromium-media-browser.desktop’

    Can you help?

    • Hi Steve,

      run “sudo nano /usr/share/applications/chromium-media-browser.desktop”
      in the editor, you search for “chromium-browser”.
      Change that to “chromium”
      press CTRL+X to save the changes

      from the applications-menu open Chromium-media-browser again.

      • John_NS on October 1, 2020 at 12:47 am said:

        Looks like this might be raspberry pi 64 bit thing. From what I can see/figure out the 32bit Raspberry OS uses chromium-browser for a directory while 64bit uses chromium.

        You can change that to chromium but it doesn’t install the wildvine files properly, so nothing works – it just creates a file called “chromium-browser”.

        Above my skills to figure out how to fix it. 🙂

        • LibWideVine is not supported on 64 bit ARM systems currently to my knowledge.

          If that changes, applying this to the Pi should be relatively easy. Google is really driving this effort unfortunately, and it seems they (again, currently) have no interest in changing it.

  38. colporteur on August 23, 2020 at 8:13 pm said:

    I have just discovered the installation I did a few months back on my Pi4B 4G, not only supports BritBox but also Bell Satellite TV. The following link https://www.bell.ca/Fibe-TV/Fibe-TV-App provides a login under Watch on Screen of Your Choice. Using Bell account credentials and the Chromium install allowed me to watch the Sportnet hockey game.

    Ventz, add Bell Satellite TV to your repertoire of streaming services the installation supports. Great job man. Thank you for sharing.

    Question:
    What ever became of Raspberry Pi’s O/S interest in looking at making this part of an install?

  39. Hello! On the 64 bits version of Raspberry Pi OS, instead of launching normally, I get:
    Invalid desktop entry file: ‘/usr/share/applications/chromium-media-browser.desktop’
    However, on the regular 32 bit branches as well as twister OS, it works perfectly fine. Any hint on how to fix that? Thank you!

    • Francisco on September 8, 2020 at 2:20 pm said:

      Hello! I get the same problem and I am also using a 64bit version of Raspberry Pi OS. I hope there is a workaround. Thank you!

  40. Thx a lot, now able to watch hulu and netflix on raspberry because of your help. But I still cannot get HBO max to work. Tried multiple user agents for latest chrome version but nothing works. Can you please help? Using Latest Raspberry pi 4, 4 GB. Latest software installed.

  41. TungstenX on August 12, 2020 at 3:05 pm said:

    Good day,
    Two days ago this solution stopped working for me. Netflix opens all good until the show starts playing in the back ground, then the screen goes black (with black font) saying Page not found. But the audio of the trailer is still playing. F5 shows the pages again for a few seconds before going back to black. It happens after log in on the main page and the My list page.

    • I have the same issue. Screen goes totally black except for the cursor, but the video’s sound keeps playing. Has anyone found a fix?

  42. Bartosh on August 11, 2020 at 10:17 am said:

    Hi! Nice work. Im running your solution on one of my 2 sd cards. runs perfect. today i installed raspbian buster via noobs in the lite version with desktop. then i copied your code from above into the terminal an executed it. when im trying to watch for example youtube i don’t get it to run in fullscreen.

    is the mistake responsible that i copied it into the terminal and didnt do it via ssh?

    greetings
    pascal

    • Hi,

      I have the same problem. Display Netflix in full screen does not work correctly, as it looks like it is “encoded”, horizontal lines are visible.

      This problem also occurs on youtube, both from chromium-media and from normal chromium.

      Is there a solution for this problem?

      Thanks.

  43. nairod on August 8, 2020 at 12:52 pm said:

    Bonjours
    Pour ma part j’ai fait tout comme vous avez dit mais quand je clique sur l’icône “Chromium(Media Edition)” rien ne se passe. Avez vous une solution a se problème ? Je suis sur le nouveau rapberry pi os.

    • Essayez d’ouvrir un terminal et d’exécuter:

      Si cela ne fonctionne pas, c’est quelque chose d’autre sur votre système avant le script.

  44. Sean Collar on August 6, 2020 at 9:33 am said:

    Big fan of your your work, I was able to get Chromium widvine DRM functional using Docker image on RPI4b however I get a sound “stutter” I guess I would call it on Ubuntu Mate 20.04 when using local tv provider app viewing certain channels. You got any input on how I may be able to resolve?

    • Sean – that’s an interesting deployment method 🙂
      I would assume you have to mount the sound device from the Pi to the container, something like this for your “docker run …”:

Comment navigation

 

Leave a Reply to David Davidson Cancel reply

Your email address will not be published. Required fields are marked *

>> NOTE: Please use <code>...</code> to post code/configs in your comment.

Post Navigation