<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Attila Molnár on Medium]]></title>
        <description><![CDATA[Stories by Attila Molnár on Medium]]></description>
        <link>https://medium.com/@shovelend?source=rss-28a7d0598bf7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_fjbarNQ96TnoJiW.</url>
            <title>Stories by Attila Molnár on Medium</title>
            <link>https://medium.com/@shovelend?source=rss-28a7d0598bf7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:05:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shovelend/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I achieved great 4K streaming performance with Philips The One 58PUS7304/12 Ambilight]]></title>
            <link>https://medium.com/@shovelend/how-i-achieved-great-4k-streaming-performance-with-philips-the-one-58pus7304-12-ambilight-2f10dc871103?source=rss-28a7d0598bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f10dc871103</guid>
            <category><![CDATA[philips]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[movies]]></category>
            <category><![CDATA[tv]]></category>
            <dc:creator><![CDATA[Attila Molnár]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 20:36:43 GMT</pubDate>
            <atom:updated>2026-08-07T20:36:43.481Z</atom:updated>
            <content:encoded><![CDATA[<p>When we bought our Philips The One in 2019, we were immediately impressed by its Ambilight feature — the one that shines the background wall with fluid colors, according to the displayed content.</p><p>Our first child was born that year, and in the long run, I wanted to set up home content streaming so that we could re-watch childhood movies unavailable on popular streaming sites. That’s when, a couple of years later, I came across <a href="https://www.plex.tv/media-server-downloads/">Plex Media Server </a>and set up an older laptop in a Linux environment, with separate drives for Films/TV Shows and Music. After the initial setup, there was room for improvement. I learned quickly, that I shouldn’t transcode unless it’s really necessary and if I do need to transcode, I should <a href="https://www.reddit.com/r/PleX/comments/yrne7c/transcoding_to_ram/">use the RAM for transcoder temporary directory</a>, instead of a disk (it’s slower and erodes the disk fast, I had to throw out one due to that).</p><p>However, another issue arose. When kids got a little bit older and I got hold of higher bitrate movie material (e.g. 4k DoVi LoTR extended edition with Dolby Atmos, or Star Wars 1,2,3 with bitrate more than 25/30 Mbps), my TV/Plex started to stutter every 5/10/20 seconds which originally I thought was buffering. <br>Looking at <a href="https://play.google.com/store/apps/details?id=tv.plex.labs.dash">Plex Dash</a>, I’d see consistent plummets during the spikes, meaning my Plex server wasn’t sending data over to the TV. Could this be because of the server or the TV? I didn’t see anything wrong on the server side, Plex logs looked pretty quiet.</p><p>I read up on possible issues and came across the lack of network speed. I was connecting via Ethernet cable and when running speedtest.net I could only get 50Mb/s (I have Gigabit internet at home). On the wifi, I got around 100 Mb/s and when using Netflix’s built-in speed tester, I ended up with 180 Mb/s over Wi-Fi. I tried a USB-Ethernet adapter, but it turns out, the TV cannot recognise it, since a kernel module is missing.</p><p>Other sites out there suggest to <br>- Clear out your TV’s cache. You’ll free up some space, but even if it speeds things up in the short term, eventually, you’ll end up in the same situation.<br>- Check for updates: Tongels also uploads all Philips firmware to <a href="https://toengel.net/philipsblog/?s=Tpm191">his site</a>, make sure you’re running the latest firmware for your TV.<br>- Restart your TV — this could be a short term solution, but your mileage may vary<br>- Factory reset your TV — eeeeeh, no thanks.</p><p>The problem with these suggestions is that they’re very generic, and you’ll never understand what is actually wrong with your TV’s performance.</p><p>Since I was getting reasonable internet speeds when on the Wi-Fi, I knew the connections should be able to handle 30–40 Mbs bitrate movies, so I dug even deeper, and that’s when I came across <a href="https://browser.geekbench.com/v4/cpu/11428609">the CPU performance of this TV</a>. It’s not great, but it shouldn’t be struggling either. <a href="https://www.reddit.com/r/AndroidTV/comments/ryx53k/android_tv_performance_boost_on_philips_android_tv/">Others have been complaining </a>about <a href="https://www.baesystems.com/en-us/definition/what-is-a-system-on-a-chip">TV SoC</a>s, there’s also a <a href="https://www.reddit.com/r/AndroidTV/comments/1qigqq3/4k_movie_lag_on_philips_android_tv/">recent Reddit post</a> that’s more than suspicious. Can we confirm this ourselves?</p><p>After this long, but somewhat relevant build-up, let’s get to the real meat. Meet <a href="https://developer.android.com/tools/adb">Android Debug Bridge</a>! For this to work, you’ll need:</p><ul><li>An Android-based TV and a laptop/PC on the same Wi-Fi network</li><li>Enable Developer Options in your Android settings on your TV</li><li>Enable USB Debugging on your TV</li><li>adbinstalled on your laptop. Windows: `winget install — id Google.PlatformTools` , Linux: `apt-get -y install android-tools-adb` , Mac: `brew install — cask android-platform-tools`</li><li>Your TV’s IP address on your local network. This is usually found in the TV’s network settings.</li></ul><p>Once you have all that, start streaming a higher bitrate movie on Plex that stutters and we can issue the following commands from a laptop/PC:</p><pre>adb connect &lt;TV_IP_ADDRESS&gt;:5555 # Sets up the connection between the debugger and the TV. Be sure to approve the connection request on your TV!<br>adb devices # Confirm that your TV&#39;s IP address is present in this list<br>adb -s &lt;TV_IP_ADDRESS&gt;:5555 shell # If the IP is present in the previous list, let&#39;s grab a shell to the TV<br>top # Display currently running processes, ordered by CPU usage</pre><p>This is when things get interesting, since this opens up a whole new world for us! You’ll see something similar to this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WrgkiDGarOyYmqziNh6_Hg.png" /></figure><p>In my case, when the system stuttered, alongside Plex, an interesting app peaked CPU in top ‘s list:</p><p><a href="https://play.google.com/store/apps/details?id=com.google.android.tvrecommendations"><strong>com.google.android.tvrecommendations</strong></a></p><p>This app handles recommendations on your TV and hogs CPU constantly.</p><p>Let’s disable it with `pm disable-user — user 0 com.google.android.tvrecommendations` . Find other packages that might be hogging, and disable them too.</p><p>There’s also the <a href="https://github.com/0x192/universal-android-debloater">Universal Android Debloater</a> that can be installed on your laptop or <a href="https://adbappcontrol.com/en/tv/">ADB TV</a> on the TV to remove apps that look odd. ADB TV is especially useful and you can disable/remove apps that are bloating your TV currently.<br> <br><a href="https://www.reddit.com/r/AndroidTV/comments/1bhumwj/anyone_knows_how_to_get_rid_of_the/">https://www.reddit.com/r/AndroidTV/comments/1bhumwj/anyone_knows_how_to_get_rid_of_the/</a></p><p>My “old” TV can handle 30–40Mbps movies without any issues after identifying and removing CPU hogging tasks. Good luck with the hunt!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f10dc871103" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unravelling the Web: Firebase Web Environments]]></title>
            <link>https://medium.com/@shovelend/unravelling-the-web-firebase-web-environments-44def127420a?source=rss-28a7d0598bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/44def127420a</guid>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Attila Molnár]]></dc:creator>
            <pubDate>Mon, 11 Jun 2018 12:55:54 GMT</pubDate>
            <atom:updated>2018-06-11T13:09:51.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SQGaH3dA9rpE1vLHGO6yfA.png" /></figure><p>Using Firebase is a great way to develop, deploy and host applications. However, when you are to create a production-ready app, you want local and testing environments next to the live one, probably an automated CI pipeline to roll out your changes.</p><p>There are some resources on the web where they create several projects to simulate environments and they do work pretty well if you don’t mind changing the necessary firebase config file to use your actual project’s <em>apiKey</em> , <em>projectId</em>, etc… when initializing your app.</p><p>Unfortunately, none of them has the answer for multiple environments in a CI pipeline where you don’t really have the opportunity to tweak around manually.</p><p>Surprisingly, Google has been hiding the solution to this problem under the rug and the answer is <em>firebase setup:web</em>. This command returns the required configuration keys for your current project after logging in or passing in the CI token (more about it in a bit).</p><p>So how does it all hang together?</p><h3>Create them projects</h3><p>Let’s go to the <a href="https://console.firebase.google.com/">Firebase Console</a> and create our application’s environments (2–3 or as many as you’d like). I’ll call them <em>myproject-dev</em>, <em>myproject-staging</em> and <em>myproject-prod</em> respectively.</p><h3>Generate tokenz</h3><p>We’ll need to log into the Firebase CLI tool generate the CI token for our deployments. On our local machines let’s install <a href="https://github.com/firebase/firebase-tools">Firebase Tools</a> with <em>npm install -g firebase-tools</em>.</p><p>Once the installation is completed, we type <em>firebase login:ci</em> in our project’s folder which generates a url where we can authenticate ourselves with the Google account we used to create the projects. Let’s log in there and in the command line we’ll see our CI token.</p><h3>Prepare your application</h3><p>If we’d like to see our special command work in action, we’ll need to log in properly as well. <em>firebase login</em> will let us do that. After selecting our project to use with <em>firebase use &lt;YOUR PROJECT ID&gt;</em> we can generate our config with the magic command:</p><pre>firebase setup:web --json &gt; src/firebase-config.json</pre><p>This will create the file <em>firebase-config.json</em> under the folder src and will look like this:</p><pre>{<br> &quot;status&quot;: &quot;success&quot;,<br> &quot;result&quot;: {<br> &quot;apiKey&quot;: &quot;&lt;YOUR API KEY&gt;&quot;,<br> &quot;databaseURL&quot;: &quot;&lt;YOUR DATABASE URL&gt;&quot;,<br> &quot;storageBucket&quot;: &quot;&lt;YOUR STORAGE BUCKET&gt;&quot;,<br> &quot;authDomain&quot;: &quot;&lt;YOUR AUTH DOMAIN&gt;&quot;,<br> &quot;messagingSenderId&quot;: &quot;&lt;SHOULD I TELL?&gt;&quot;,<br> &quot;projectId&quot;: &quot;&lt;myproject-dev&gt;&quot;<br> }<br>}</pre><p>For your own convenience you can keep this file locally, but don’t put it into any VCS.</p><p>The only change we need to make in our application now is to import this file and use its result where we initialize our app like so:</p><pre>// Your awesome imports</pre><pre>import firebase from &#39;firebase’;</pre><pre>import { result } from &#39;./config-firebase.json&#39;;</pre><pre>firebase.initializeApp(result);</pre><pre>// Your awesome code</pre><h3>Deploy to (Bitbucket) Pipelines</h3><p>The last thing to work with is our CI pipeline. Remember the CI token we generated earlier? Add its value to your pipelines’ environment variables as <em>FIREBASE_TOKEN</em>.</p><p>I’ll use bitbucket pipelines to deploy to my app’s environments and my bitbucket-pipelines.yml looks like this (adjust to your CI tool of preference):</p><pre>image: node:8.11.2</pre><pre>pipelines:</pre><pre>  default:</pre><pre>    - step:</pre><pre>        name: Deploy to staging</pre><pre>        deployment: staging</pre><pre>        caches:</pre><pre>          - node</pre><pre>        script:</pre><pre>          - npm i</pre><pre>          - npm i -g firebase-tools</pre><pre>          - firebase use --token $FIREBASE_TOKEN myproject-staging</pre><pre>          - firebase setup:web --json --token $FIREBASE_TOKEN &gt; src/firebase-config.json</pre><pre>          - npm run build</pre><pre>          - firebase deploy -m &quot;Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID&quot; --non-interactive --token $FIREBASE_TOKEN</pre><pre>    - step:</pre><pre>        name: Deploy to production</pre><pre>        deployment: production</pre><pre>        caches:</pre><pre>          - node</pre><pre>        script:</pre><pre>          - npm i</pre><pre>          - npm i -g firebase-tools</pre><pre>          - firebase use --token $FIREBASE_TOKEN myproject-prod</pre><pre>          - firebase setup:web --json --token $FIREBASE_TOKEN &gt; src/firebase-config.json</pre><pre>          - npm run build</pre><pre>          - firebase deploy -m &quot;Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID&quot; --non-interactive --token $FIREBASE_TOKEN</pre><p>Where I install firebase-tools globally, then</p><ul><li>Specify which project to use with <em>firebase use --token $FIREBASE_TOKEN myproject-ENV</em></li><li>Generate the necessary configuration with <em>firebase setup:web --json --token $FIREBASE_TOKEN &gt; src/firebase-config.json</em></li><li>And deploy the app with <em>firebase deploy -m &quot;Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID&quot; --non-interactive --token $FIREBASE_TOKEN</em></li></ul><p>Let me know of your thoughts and questions in the comments section! If you’re having difficulties with the setup, just reach out to me, I’m happy to help you out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44def127420a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tedious Test Driven Development (TTDD) with Firebase, React and Jest]]></title>
            <link>https://medium.com/@shovelend/tedious-tdd-with-firebase-react-and-jest-7054877a9c51?source=rss-28a7d0598bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7054877a9c51</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[jest]]></category>
            <dc:creator><![CDATA[Attila Molnár]]></dc:creator>
            <pubDate>Fri, 27 Oct 2017 13:12:29 GMT</pubDate>
            <atom:updated>2017-10-31T00:07:33.741Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W1FC3OAIqN5TuQZvGn-KNQ.png" /></figure><p>Ok. You’re planning to bring your project to life using</p><ul><li>Firebase for hosting, auth, db, Cloud Functions and all that kind of good stuff</li><li>React to show all the fancy pages using states, props, centralizing your UI and logic</li><li>A testing framework like Jest to make sure everything works as intended</li></ul><p>So how do you introduce unit tests?</p><p>I’ve just started to learn React and I find it pretty good so far. I am reimplementing one of my personal projects in React and wanted to do TDD.</p><p>Let’s say that you want to unit test a function in your app where something happens when the user logs out from your site. I’ll call it handleSignOut for now.</p><pre>handleSignOut() {<br>       if (firebase.auth().currentUser) {<br>           firebase.auth().signOut();<br>           return true;<br>       }<br>     }</pre><p>You’d like to test that this function returns true when the user was logged in previously. In order to do that, you’ll need to mock the firebase object so it can return the currentUser successfully using Jest.</p><blockquote>import Main from &#39;./index.js&#39;;<br>import React from &#39;react&#39;;<br>import Enzyme from &#39;enzyme&#39;;<br>import Adapter from &#39;enzyme-adapter-react-16&#39;;<br>import * as firebase from &#39;../../firebase&#39;;</blockquote><blockquote>Enzyme.configure({ adapter: new Adapter() });</blockquote><blockquote>describe(&#39;handleSignout&#39;, () =&gt; {</blockquote><blockquote>beforeAll(function() {<br> firebase.firebase.auth = jest.fn().mockReturnValue({<br> currentUser: true,<br> signOut: function() { return true; }<br> });<br> });</blockquote><blockquote>it(’should return true’, () =&gt; {<br> const wrapper = Enzyme.shallow( &lt; Main / &gt; );<br> let result = wrapper.instance().handleSignOut();<br> expect(result).toBe(true);<br> });<br>});</blockquote><p>Thanks to Richard Kotze we’ve now managed to mock the firebase object successfully, he has launched this rocket to the moon (and back). Find more interesting javascript insights and techniques on his blog: <a href="https://www.richardkotze.com/">www.richardkotze.com</a></p><p>That’s it for now, have a great day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7054877a9c51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide on how to install Node.js and NPM on a Chromebook]]></title>
            <link>https://medium.com/@shovelend/guide-on-how-to-install-node-js-and-npm-on-a-chromebook-8d89a35b791a?source=rss-28a7d0598bf7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d89a35b791a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[chromebook]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Attila Molnár]]></dc:creator>
            <pubDate>Fri, 27 Oct 2017 13:03:14 GMT</pubDate>
            <atom:updated>2018-09-16T16:42:19.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EKmPts2DQk1NIpVXdTitHg.png" /></figure><p>When I bought my Acer R13 Chromebook in June 2017 I had a firebase project in my pipeline. I wanted to use firebase cli commands to manage and develop the project on my new machine.<br>In order to do that, I needed Node.js and npm and after lots of struggle and browsing guides, I managed to install both of them in a clean way.</p><p>First, you need to switch your Chromebook to developer mode. Follow this video in order to do that: <a href="https://www.youtube.com/watch?v=UWXO61_v_xo">https://www.youtube.com/watch?v=UWXO61_v_xo</a></p><p>You should be able to access the browser terminal by pressing Ctrl+Alt+T in a Chrome window. Type shell to use the terminal we need.<br>You can check your processor architecture by typing `lscpu` in the terminal.</p><p>Download the appropriate Node package for your processor architecture from here: <a href="https://nodejs.org/en/download/">https://nodejs.org/en/download/</a></p><p>Navigate to the Downloads folder from the command line:<br>$ cd ~/Downloads</p><p>Extract the downloaded node package:</p><pre>$ tar xf node*.tar.xz</pre><p>Navigate to the extracted bin file:</p><pre>$ cd node*<br>$ cd bin</pre><p>Copy the node file under/usr/local/bin/ (create the bin folder if it doesn’t exist):</p><pre>$ sudo cp node /usr/local/bin/</pre><p>You should be able to see node version now:</p><pre>$ node -v<br>eg.: v8.11.2</pre><p>Now navigate to the npm folder:</p><pre>$ cd ..<br>$ cd lib/node_modules/npm/scripts</pre><p>And install npm:</p><pre>$ sudo sh install.sh</pre><p>You might get a read-only file-system error, in order to fix that, you’ll need to run (as found on the official chromium website: <a href="https://www.chromium.org/chromium-os/poking-around-your-chrome-os-device">https://www.chromium.org/chromium-os/poking-around-your-chrome-os-device</a>)</p><p>sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification</p><p>This will give you another command to execute. Run it and reboot the device.</p><p>Verify that you have npm installed:</p><pre>$ npm -v<br>eg.: 6.0.1</pre><p>Useful resources:<br>– Old way of doing it (didn’t work for me): <a href="https://coderwall.com/p/lonlyq/node-and-npm-on-chromebook-chrome-os">https://coderwall.com/p/lonlyq/node-and-npm-on-chromebook-chrome-os</a><br>– Chromebrew package manager. It didn’t work for me, but you get GIT out of the box: <a href="https://github.com/skycocker/chromebrew">https://github.com/skycocker/chromebrew</a><br>– Miniconda (if you need python27 for some reason). Make sure you download the right package for you processor arch: <a href="https://conda.io/miniconda.html">https://conda.io/miniconda.html</a> and <a href="https://repo.continuum.io/miniconda/">https://repo.continuum.io/miniconda/</a><br>– You might have to set a pw for chronos if you need to do some task with sudo: Ctrl+Alt+=&gt; (where =&gt; key is the right-arrow key just above the number 3 on your keyboard) and follow the instructions to set the password (login as root)<br>– Different approaches for installing node and npm (they didn’t work for me): <a href="https://gist.github.com/isaacs/579814">https://gist.github.com/isaacs/579814</a><br>– If your node file is not executable, do `chmod +x node` in /usr/local/bin</p><p>Let me know if it works for you in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d89a35b791a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>