I saw on a screenshot from a Galaxy S2 a dotted line predicting data usage based on current usage which I’d not seen on my Galaxy Nexus.
I had a look and it was true, it wasn’t there, I checked then menu to see if there was a way to turn it on, and stumbled across what seems to be a bug.
Here is how to repeat it, this is on my UK Galaxy Nexus running stock Android 4.0.4.
Go to settings and choose Data Usage
As you see, no prediction line.
Select Show Wi-Fi usage from the menu.
Press the Wi-Fi tab and then go back to Mobile
There you go, the dotted prediction line is visible.
A quick post just to put the installer script I’ve done for Fedora to get Spotify installed from the latest Debian packages available from their servers:
Tested on Fedora 16 32bit, Fedora 16 64bit, Fedora 17 64bit. All fine so far.
No uninstall script just yet though, I’ll likely incorporate it into this script anyway and have it as an option. -i install -u uninstall maybe.
# This script will download the .deb packages, unpack them and put the bits where they need to go.
# This does not have an uninstall element to it, nor does it keep it up to date. Sorry.
# Updated to just work and grab everything required rather then searching out a specific
# This needs to be ran as root, because it extracts files into /usr/bin and /usr/share which is root only. sudo should work.
echo "Grabbing dependancies, say yes to this or Ctrl+C to cancel the script."
yum install binutils qt-x11 openssl nss nss-util nspr qtwebkit libpng-compat libXScrnSaver
mkdir -p packages/client/gnome
lftp -e 'mget spotify-client-gnome-support;exit' http://repository.spotify.com/pool/non-free/s/spotify/
ar xv spotify-client-gnome-support_*.deb data.tar.gz
tar -C / -xf data.tar.gz
if [ "$HOSTTYPE" == "x86_64" ]; then
lftp -e 'mget amd64;exit' http://repository.spotify.com/pool/non-free/s/spotify/
ar vx spotify-client_*_amd64.deb data.tar.gz
tar -C / -xf data.tar.gz
ln -s /lib64/libssl.so.10 /lib64/libssl.so.0.9.8
ln -s /lib64/libcrypto.so.10 //lib64/libcrypto.so.0.9.8
ln -s /lib64/libnss3.so /lib64/libnss3.so.1d
ln -s /lib64/libnssutil3.so /lib64/libnssutil3.so.1d
ln -s /lib64/libsmime3.so /lib64/libsmime3.so.1d
ln -s /lib64/libplc4.so /lib64/libplc4.so.0d
ln -s /lib64/libnspr4.so /lib64/libnspr4.so.0d
elif [ "$HOSTTYPE" == "i386" ]; then
lftp -e 'mget i386;exit' http://repository.spotify.com/pool/non-free/s/spotify/
ar vx spotify-client_*_i386.deb data.tar.gz data.tar.gz
tar -C / -xf data.tar.gz
ln -s /lib/libssl.so.10 /lib/libssl.so.0.9.8
ln -s /lib/libcrypto.so.10 /lib/libcrypto.so.0.9.8
ln -s /lib/libnss3.so /lib/libnss3.so.1d
ln -s /lib/libnssutil3.so /lib/libnssutil3.so.1d
ln -s /lib/libsmime3.so /lib/libsmime3.so.1d
ln -s /lib/libplc4.so /lib/libplc4.so.0d
ln -s /lib/libnspr4.so /lib/libnspr4.so.0d
# for some reason Spotify is linked against specific libraries, but we can fake it with symlinks.
echo "Done, you should now be able to excute the spotify command succesfully. If not, something went wrong. Sorry"
I’ll put up another download at some point, but for now, that should work if you put it in a script and execute it as root.
I spent a good while debugging this not wanting to change too much incase it was something bizarre.
Turned out to be something simple.
So, we use OSTicket at work, and for the most part it works well. However, there are parts which are a little buggy.
One of these appears to be that, when we were trying to create a New Ticket using the New Ticket option when you’re signed in, it would highlight the Source field and give the error “Invalid Source”.
This happened no matter what option from the drop down you would choose.
I had a look at the code, and made a guess at the problem, at it appears to work:
In the file: scp/tickets.php
if($_POST['source'] && !in_array($_POST['source'],array('web','email','phone','other')))
if($_POST['source'] && !in_array($_POST['source'],array('Web','Email','Phone','Other')))
This appeared to resolve my problem and the ticket was logged successfully without error.
I’ve been playing around with my Hannspree Hannspad that I bought a few months back, and sure, its a budget tablet, but I think Ice Cream Sandwich will make it much better.
I don’t know what I’m holding out for, something between Honeycomb and Gingerbread. I’ve used a Honeycomb ROM on my Hannspad, and I’ve also tried Froyo and Gingerbread ROMs, and I’ve come back to Gingerbread since trying all.
I suspect that with very few Honeycomb specific apps around and ICS (Ice Cream Sandwich) just around the corner, development on Android Honeycomb will halt and ICS will be its successor.
What do you think?
I had the requirement for some tests to turn a big plain text file into a “more or less” formatted correctly ttx file.
Now, this is by no means something that you would want to open in Trados to start editing with etc, but it does surround the lines with Trados TTX tags in sufficient detail for me tests.
Get the script here: http://www.leenukes.co.uk/downloads/TXTtoTTX.py
Now I know, its messy, but I don’t care at the moment as it worked for me and saved me copying and pasting over 1400 tags to lines of text.
I also didn’t find anything online that would do this for me, hence me writing this. I’m not a programmer, and I know actually outputting XML using elementTree would be better, but it was more work to do that then I was willing to spend at the time.
This small piece of code would benefit from reading in language options from the user, and then slotting them into the tags and it would also benefit from a re-write to allow it to output XML correctly as at the moment it reads in the file stated, and outputs it wrapped.
Characters that are not valid XML still go through, for example if there is an & in the file, it will wrap that too, it doesn’t care. & isn’t valid XML amongst other characters and is commonly substituted with &
Call this script whatever you want, but I was calling it TXTtoTTX.py
So, what does it do?
Lets say you have a file with 3000 lines of text in it called mytesttext.txt, you would use this python script as follows:
python TXTtoTTX.py mytesttext.txt
this will then output it to screen for you to quickly check, then you can redirect the output to file like this to save it:
python TXTtoTTX.py mytesttext.txt > mytesttext.ttx
Not long until Fedora and Ubuntu release their distress with Wayland instead of X.
I’m looking forward to it but my worry is with drivers. I like to use the proprietary drivers for the performance gains as I sometimes play 3D games and use 3D effects on the desktop.
Anyone else interested in Wayland and what it will bring?
I recently installed Fedora 14 Beta Release 2 on my desktop PC at home and I’m going to go so far as to say its the best Fedora release I’ve used.
It was an upgrade of the existing Fedora 13 installation which in my opinion seemed pretty buggy, no specifics, it just didn’t feel very polished.
Totally the opposite for this release, just a couple of issues at present which are no problem really. The flash player is having some issue with creating crackling electronic noises when playing videos online such as YouTube etc but I’m hoping this resolves itself. I’ve tried reinstalling the plugin from Adobe but had the same issue. Same issue in Chrome as well as Firefox also.
It’s due out in a few days now. I also updated my netbook to Ubuntu 10.10, I’m not that impressed with this release though. Not a fan of the new Unity interface. Never really been a fan of sidebars. There is probably a way of getting the windows to overlap it, but for now I’m not impressed. They’re always breaking things those Ubuntu people. Grrr.
I’ve read lots of release information about the upcoming Android 2.2 release Froyo which has now started to roll out to the Google Nexus One and I’m wondering if it will bring 802.11n to the HTC Desire.
People have managed to hack a kernel together for the HTC Desire and get 802.11n already, I just hope it comes officially with Froyo. And soon…