Update to WidescapeWeather Screenlet

I was looking for desktop widgets for Ubuntu and I came across screenlets.

I didn’t realize it was 8 years old and not maintained at all but I ended up spending some time fiddling around with it and fixing the WidescapeWeather widget.

The reason it wasn’t working was because weather.com changed the URLs for getting the most recent data and so a manually modified the Python script.

Original widget download location: https://www.gnome-look.org/content/show.php/Wide+weather?content=77168

After installing this with Screenlets Manager, edit the script

gedit ~/.screenlets/WidescapeWeather/WidescapeWeatherScreenlet.py

And modify:

data = urlopen('http://xoap.weather.com/weather/local/'+self.ZIP+'?cc=*&dayf=10&prod=xoap&par=1003666583&key=4128909340a9b2fc&unit='+unit + '&link=xoap').read()


data = urlopen('http://wxdata.weather.com/wxdata/weather/local/' + self.ZIP + '?cc=*&dayf=10&unit=' + unit).read()

The only tricky thing here is to make 100% sure that you keep the tabs on the modified line.  Python will be upset if the formatting is not correct.


Screenshot from 2016-07-16 17:22:47

And then after more Googling, I think I should have used Conky.  Oh well.

RIP LinkStation :(

My 250GB Buffalo LinkStation has died.  And I’m kinda sad.  I don’t remember exactly when I purchased this, but the earliest review I can find was from 2006 (http://www.smallnetbuilder.com/nas/nas-reviews/28111), which makes it about 9 years old.


It first started with the dreaded 6 red blink hard drive error.  I took the device apart, placed the hard drive into my Ubuntu box, and used xfs_repair to fix the drive.  It looked like there were some journal and read errors that were fixed.

I was able to browse the file system while the drive was connected to the Ubuntu box so I thought I was in the clear.  But when I reassembled the LinkStation, there was another problem; this time, it was a 4 red blink error.

(Decoding error flashes: http://buffalo.nas-central.org/wiki/Information/LSProLED)

When I looked at the fan, it was not spinning.  I tried a few other PC fans I had lying around, but none of them spun up.  I then dusted off the multimeter and found that there was no more 12v supply going into the fan from the 3-pin header.  I first suspected a blown fuse (http://forum.buffalo.nas-central.org/viewtopic.php?f=39&t=6561) but the multimeter indicated that the fuse was intact and there was 12v coming from the power supply.

At this point, I gave up.  I didn’t search for a schematic to try and isolate where the 12v could be cut off.  Even if I was able to find the faulty component (or maybe a broken trace), I don’t have the tools to rework the board.

It was a nice run.  I’m thinking about keeping the 250GB drive, but if the root cause of all this was in fact some side effect of overheating due to the fan not spinning, I probably shouldn’t trust the integrity of the drive.

Thanks for the 9 year uptime, Mr. Buffalo LinkStation LS-GL.



I have a really old Nexus 7 (https://en.wikipedia.org/wiki/Nexus_7_%282012_version%29) and upgrading that to Lollipop basically made it unusable.  It was terribly slow.

I unlocked the bootloader and reflashed with 4.4.4 (https://dl.google.com/dl/android/aosp/nakasi-ktu84p-factory-2c6e4d6f.tgz) and that was much better.

But that’s really no fun so I decided to give CyanogenMode a shot (http://download.cyanogenmod.org/?device=grouper&type=).  It was a bit overwhelming at first to work out that:

  • nakasi is the codename for that tablet at Google while grouper is the codename for the CM team
  • CM 11.0 is based on Android 4.4.4
  • M vs N vs stable vs snapshot … (http://wiki.cyanogenmod.org/w/Release_Versioning)

I finally settled on this http://download.cyanogenmod.org/get/jenkins/90453/cm-11-20141112-SNAPSHOT-M12-grouper.zip but that’s no fun either so I built it from scratch.  https://wiki.cyanogenmod.org/w/Build_for_grouper

Everything is all documented and there are even steps to make sure the GMS apps are installed so the resultant build is very much usable.

That was fun.

SPP server for Windows

I have posted a simple protocol server for Windows on GitHub: https://github.com/kaytat/SimpleProtocolServer

There is more technical info in the README of that project.

The server will probably require a little configuration from the user.   The reason is the WSAPI loopback used for capture does not allow for programmatically changing the sampling rate.  Since the SPP player requires a certain format, the user will  have to set the properties of the playback device to match.

Here are the steps to do so for a Win7 machine.  First open up the “Playback devices” from the system tray.



Choose the “Properties” button of the sound card being used:



Choose the format the best fits SPP.  SPP defaults to 16bit 44.1kHz, but it will also support 16bit 48kHz.



A corresponding update to SPP has been posted on the Play Store that adds an option to choose either 44.1kHz or 48kHz for the sampling rate.