A reddit thread brought to my attention that there is a bandwidth limit on the steam link. I've finally figured out where the stream settings are saved and how to read / write them.You will also have to make one file called streaming_args.txt, I'll explain below. streaming_settings.bin  This config file has its maximum_bitrate_kbps set to 0. Which signifies no limit. streaming_settings_100000.bin  This config file has its maximum_bitrate_kbps set to 100,000 for 100mbps. To use these you can either scp them into your /mnt/config/system/ folder as streaming_settings.bin or you can put the file on a USB pendrive as /steamlink/config/system/streaming_settings.bin and reboot with the pendrive inserted. (Note: You need to hard 'reboot' un-plug and re-plug the power, you should see the steamlink on a blue background icon thing.) To see if it worked goto your Streaming settings and press Y to go into Advanced Settings. If it worked your Bandwidth Limit row wil...

Notice for anyone that hasn't found the dev_build.txt and the two indev builds 'available' to the public right now. I've been neglecting to post the dev_builds.txt just to avoid anyone from grabbing the 337 and 341 and flashing them to their links. The 337 build works fine but I see no notable changes, the 341 build actually fails to run on the steam link. On startup the 341 build gives you an error telling you to contact a internal valve employee. The message is a little more specific but I'm trying to avoid names.  But if you're feeling technical and comfortable in your ability to fix your steam link should something mess up then you can flash the 337 and 341 builds manually with a USB drive, see the S01config script in /etc/init.d/startup in there you can see how to change your update branch to dev and flash the dev images. Once again I'm being ambiguous just to avoid hand-holding anyone into messing something up. All in all though the two dev builds d...

Alright this was a lot easier than I expected. Thanks Valve! After digging through the full 332 update zip I found that Valve left their developer init scripts in /etc/init.d/startup. Not sure if they did this intentionally or not but I like it. So first and foremost I was wrong about the Android AOSP thing, it looks like its just a custom linux and the android stuff I was seeing earlier was just from them using the android signing utility for their updates. Basically they use signapk on their zip files which leaves some android stuff in META-INF. So sorry about the false alarm there. As for enabling ssh on your Steam Link its very easy. All you need to do is get a pendrive and make this file in these folders: /steamlink/config/system/enable_ssh.txt (Note: the file must have some data in it, if enable_ssh.txt is empty it will not work) Then reboot the Steam Link with the pendrive inserted, after its done connecting to the network you can ssh into the Steam Link as root with the p...

Currently looking into the updater system for the Steam Link. As for the update system its fairly simple, the first thing the Link does is send a request to. http://media.steampowered.com/steamlink/06_2015/public_builds.txt That returns a newline delimited list of the 'public' Steam Link builds. If there is a higher version in that list somewhere then it will send a request to http://media.steampowered.com/steamlink/06_2015/SystemUpdate_delta_[current_version]_[latest_version].zip That will download the delta update and the system will reboot. Its actually pretty well thought out how they designed the update system, it uses bsdiff to keep the updates small.  Also after some trial and error I found that http://media.steampowered.com/steamlink/06_2015/SystemUpdate_full_[version].zip is also available for full updates, these zips even contain the recovery/bootloader files.

Wow I haven't used this site in forever. Might have some updates about the Steam Link here soon.

I've recently moved my Linode VPS from Ubuntu to Arch to try and save some disk space (which it actually does). The VPS is just a simple one to conserve my bandwidth at home to host some garrysmod or various source servers. Problem tho, the latest glibc that installs with pacman on arch fucks up with the hldsupdate tool. Well this is problematic, simple solution tho. Two options what I did was reinstall arch on the VPS and didn't run a -Syu, luckly enough the older version of glibc that comes with the base install is compatible with hldsupdatetool. But if you're reading this you probably don't want to reinstall arch just for srcds, so here is the steam i686 binary that comes out of the hldsupdatetool (see bottom). Just run ./steam (might have to chmod +x it) and it should create your clientregistry.blob in ~/Steam then run it a second time and you should get the help menu. Have fun installing dedicated server stuff :D By downloading this you accept to the valve/steam...

I need to post on this blog more. I recently moved off of ubuntu linux and switched to arch (great os by the way) and still kept my gnome desktop like ubuntu, issue is i was on a older version of ubuntu that was still using gnome 2 so when i switched to arch it put me on gnome 3 which looks unfortunatly WAY different. That is unless you use  fallback mode like I am, then it looks alot more like gnome 2. Altho this isn't the solution you are looking for, you're here because your wallpapoz/drapes/generic wallpaper changer no longer works for gnome 3. Sadly they moved away from gconf and the likes and now they use some xml kinda thing with gsettings and that is why most other desktop changers don't work with it yet (that i know of) so I got pissed and made a very simple and short python script to shuffle my wallpapers from a directory where all my wallpapers are stored. I'll shut up now and just give you the script. I told you it was really short http://pastie.org/212...