This is the third of 4 postings related to my first Android phone I did buy 4 months ago:
myAndroid -- hardware
myAndroid -- software
myAndroid -- why rooting / programming
myAndroid -- DataPower WebGUI
According Wikipedia Android rooting is no problem outside US.
And if I read it correctly, it is no problem in the US for cell phones
that are not bound to a provider like my prepaid free of contract cell phone.
I do have two prepaid SIMs from http://www.pennymobil.de, partner+surfer.
While ZTE Blade does not allow for dual SIMs, I just change the SIMs as needed,
the other just fits below the rechargable battery inside the device.
So the 2nd question to answer after the legal one above is, why rooting?
For me rooting of the device makes the difference between an Android phone and
a Linux phone. After rooting I can access anything, including system applications.
There are many instruction on how to root a device, and most differe wrt to the device type.
I did successfully follow this android Wiki instructions without problems (google for English ones):
Before rooting I did indentify the exact Blade version of my cell phone by Blade Checker app:
After rooting I did not change the Android 2.2 firmware on the device.
Many people root their devices to just do that, and I could install an Android 4.x OS.
But currently I do not see the need for that.
The device has only a single core 600MHz ARM 11 processor which is fine for 2.2 firmware.
The first app I installed then was Android Terminal Emulator of course.
Immediately followed by BusyBox providing all my favorite command line utilities.
Unfortunately the available editor "vi" does not provide syntax highlighting, anyway I use it.
This is "top" output for the device ...
Then I did disable the only really bad preinstalled feature of the device, the boot animation.
While I could live with the animation itself on device startup the sound is played
at maximum volume. And the volume cannot(!) be changed.
Everytime I had to start the device I got full attention of all people around ;-)
I did not want to remove the bootanimation, just do not start it.
"service bootanim /system/bin/bootanimation" in /init.rc starts the animation.
First I tried to comment out that line, but had to learn that the firmware wrote
that file newly on each bootup, overwriting my changes :-(
Then I tried to remove "run" access rights for "bootanimation" and that worked.
After starting the Terminal Emulator first switching to root user by "su" is needed.
Then "chmod 644 ..." does the rest:
The same could not be done easily from the "outside" by Android Debug Bridge (adb):
I created my first "Hello world" application following these instructions.
No big development environment, just learn each step needed.
While the above was a Java program, I created an Android version of "tidy"
command line utility with free CodeSourcery C/C++ cross compiler for ARM.
Based on "tidy4aug00.tgz" I just had to change two Makefile lines:
Important is the "-static" change -- by that no libraries have to be installed on Android.
Here is "Android tidy" in action:
Just found interesting (free) Terminal IDE app
"with a full Java / C / C++ / HTML / Android development kit, that runs on your Android device."
Unfortunately (for me) that requires Android OS 2.3.3 or higher -- this might be a reason to
Also Eclipse Android SDK seems to be worth to try.
What I really want is some XLST 1.0 or XSLT 2.0 or XQuery 1.0 processing on the device.
By open source XSLT 2.0 processor Saxon CE that is already possible today.
And with kws - Android Web Server app you can do XSLT 2.0 in the Android browser
locally on the Android device -- even without any internet connectivity!
As example see screenshot of Saxon CE port of my peg-solitaire XSLT game:
Find more information on my experiments with Saxon CE here:
Hermann<myXsltBlog/> <myXsltTweets/> <myCE/>