Apparently someone is trying to make money with an Android application that I wrote a month ago. At first I was really mad about people ripping off others by making money of other people’s work. But today I actually feel it is a bit of a compliment. At least this guy thinks, my little app is worth some money. 
But seriously, of course I complained about it to Google with their DMCA form.
Regarding the GPL and selling software: this is actually possible, as long as you respect the terms of the license. Paragraph 4 of the GPL says:
You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
Update: Google removed the App. And it seems to me that they removed the vendor’s account all together.
Update 2: After Google removed it the first time, the guy created a new merchant account and uploaded my app again. I filed a DMCA complain again and Google took down the app and his account a second time. But this guy is really persistent: On August 16th he uploaded the app AGAIN. Remember: He has to pay 25 US$ everytime he creates a new account. And he does this to try selling an app (of about 50 LoC) for 2$, that I give away for free. How stupid can one single person be? I would have thought you’d need at least ten *really* stupid people to gather that amount of idiocy.
Because I couldn’t find any info on how to use sub-projects (that is sub folders in a project) as libraries within the ADT in Eclipse, here’s a short how-to:
Use submodules as you normally would, e.g. when cloning a project with sub-projects use this:
git submodule init
git submodule update
Then in Eclipse you can create a new Android project with the wizard from the existing source (and pointing the location to the sub directory).
When you reference the sub-project as a library for the main project, it will magically point to the correct directory inside the main project.
The yaxim Jabber client for Android for example uses this to depend on the MemorizingTrustManager (see the screenshot).
OMG! Ubuntu! zeigt, wie man die neue Ubuntu-Schrift auf seinem Android-Telefon nutzen kann. Ich finde die Anleitung unnötig kompliziert, aber da man auf deren Site nicht kommentieren kann, ohne irgendwo Accounts anzulegen, beschreibe ich mal hier, wie es einfacher geht–nämlich mit adb. (adb in $PATH vorausgesetzt)
adb remount
adb pull /system/fonts/ # holt alle Schriftdateien vom Telefon; optional
adb push /usr/share/fonts/TTF/Ubuntu-R.ttf /system/fonts/DroidSans.ttf
adb push /usr/share/fonts/TTF/Ubuntu-B.ttf /system/fonts/DroidSans-Bold.ttf
Update: Auf Ubuntu ist der korrekte Pfad, wenn man die Schriften über den Paketmanager installiert hat, /usr/share/fonts/truetype/ubuntu-font family.
Mit diesem Befehl sollte man sicherstellen, dass die Schriften root:root gehören:
adb shell ls -l /system/fonts
Die Rechte sollten etwa so aussehen (nicht etwa 777, wie im original behauptet):
-rw-r--r--
Gegebenenfalls anpassen (war bei mir nicht nötig):
adb shell chown root:root /system/fonts/DroidSans.ttf /system/fonts/DroidSans-Bold.ttf
adb shell chmod 644 /system/fonts/DroidSans.ttf /system/fonts/DroidSans-Bold.ttf
Dann noch neustarten und bewundern. Ich persönlich finde es schick, aber mit den Droid-Schriften geht mehr auf’s Display, da sie schmaler sind.
PS: Bei skweez.net kann man ohne Account und anonym kommentieren!
