The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.
Here’s an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 10,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 4 sold-out performances for that many people to see it.
This post will help you to install the required Google Play Store, Superuser and Busybox binary in your Emulator.
Download the required files from the following URL
GOOGLE SERVICES– http://www.mediafire.com/download/7cps3k7qgyjcpsp/Google%20Services.zip
SUPERUSER BINARY– http://www.mediafire.com/download/bgy1et6e3vytge7/Superuser%2520binaries.zip
BUSYBOX BINARY– http://www.mediafire.com/download/mye5qcejxk54e6v/Busybox%2520binary.zip
The following urls contains a zip file which after extracting would find “install.bat” file. This bat file contains the necessary scripts for installing the corresponding apps and binaries.
The commands present in script file are given below.
1:Installing Google Play Store
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
adb shell chmod 777 /system/app
adb push GoogleLoginService.apk /system/app/
adb push GoogleServicesFramework.apk /system/app/
adb push Vending.apk /system/app/
adb shell rm /system/app/SdkSetup*
2:Installing Superuser binary
adb shell mount -o rw, remount -t yaffs2 /dev/block/mtdblock0 /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb shell chmod 06755 /system/bin/su
3:Installing Busybox Binary
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
adb push busybox /system/xbin/
adb shell chmod 06755 /system/xbin/busybox
Please note that once the emulator has been closed the the above files will be deleted. So again the process should be repeated when the emulator is started once again.
Recently Android KitKat (4.4) has been released and now available in Google’s flagship device NEXUS 5. On every Android update there comes the introduction of CyanogenMod custom ROM or simply CM. The latest release of CM is v11. But CM11 has been released only for few devices. For my luck I could find CM11 or Android KitKat ported on my device (SGS I9003) that too an unofficial version in XDA forum. Let me personally thank the person behind porting CM11 on SGS I9003 (http://forum.xda-developers.com/showthread.php?t=2534312) . So as usual I installed the ROM using the steps specified in the forum and I could successfully boot into the new OS. The very first moment I entered the home screen after some registration procedures I could find few random changes compared to Jelly Bean starting right from the dock menu to settings page. Anyways the new OS is looking too cool and thought of keeping the device for testing overnight before using the new OS for regular use.
After 24hrs of use I could find that the phone doesn’t connect to network provider. So I started to figure out the cause. From my observation I found that the device is having data connectivity but no telephony services. Later I replaced the SIM with another one but still the problem persists. Suddenly something caught in my eyes that the IMEI number has been changed when the new OS has been installed. The following is the new IMEI generated in my device when the OS (CM 11) has been installed.
” 004999010640000 “
Here is the issue, I will give a brief explanation which I found in XDA forum ( http://forum.xda-developers.com/showthread.php?t=859914) . This could be really useful for those who really prefer to install custom ROM rather than stock OS. (THIS IS ONLY FOR SAMSUNG DEVICES)
Samsung uses RFS as their default file system. The IMEI number is stored in /efs folder found in the root directory. This is a very sensitive system folder that contains Phone-specific information such as the IMEI , wireless devices MAC addresses, product code, and much more.The file system used by custom ROMs are YAFFS (Yet Another Flash File System). When custom ROMs are installed the filesystem will be changed to YAFFS and hence the RFS file system cannot be accessed since it is proprietary of Samsung. So for as result the default device sensitive information are not available. To overcome this issue please use the following steps to recover back your lost IMEI number once custom ROM has been installed.
Step 1: Creating backup of the IMEI before flashing the stock ROM
- While in stock ROM create a backup of the efs folder using the following command either in ADB or terminal emulator
ADB command prompt: su tar zcvf /sdcard/efs-backup.tar.gz /efs Terminal Emulator: busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
- The above command will create a backup of “efs” folder in your internal memory. Please copy the backup file to your sdcard.
Step 2: After installing custom ROM and restoring back the IMEI
- Now extract the contents of the backup to your sdcard and perform the following commands using Terminal Emulator App
cp /sdcard/nv_data.bin /efs/nv_data.bin rm -rf /efs/nv_data.bin.md5
- The first commands will copy the backup file “nv_data.bin” to your efs folder. And the second command will delete the existing “nv_data.bin.md5” since we have replaced the another file for “nv_data.bin” and the hash signature has been changed. Reboot the device and the system will generate a new “nv_data.bin.md5” file. Make sure you have rebooted the device after executing the above commands.
- Now after rebooting the device use the following command in Terminal Emulator app to change the ownership of the file
chown 1001:1001 /efs/nv_data.bin
- Cheers!! You have successfully replaced your default IMEI number.
Well smart phones have became an integral part of our life. Its quite common nowadays to see people with smart phones. In fact users prefer to choose devices which are simple to use and yet reliable. That’s the main reason why there is a tough competition between Android, iPhone and Windows Mobile. To make it simple the applications should really have unsophisticated UI rather than making it more complex and hard to understand.
Here comes a new era UI design – FLAT UI DESIGN. Flat designs uses plain 2D icons and more vibrant colors with minimal design and emphasizes usability. For example
Another great example of flat design is Google Now app, which uses a card-like system to display information . Recently released iOS7 have got really a cool , “flat” and colorful design.
Since flat UI design has really became a new trend. So I thought of changing my new apps to flat design. The recently developed bus tracker app is my first step into FLAT design.
Finally after a long wait I received the order for OBD2 Bluetooth scanner. It looks quite bulky as I thought but it quite fits perfectly into my cars OBD port.
Once successfully connected to OBD port I paired my phone with the OBD scanner using Bluetooth connection. I installed a couple of most popular OBD2 scanner apps for Android and the output which I found was far more amazing. I could really communicate with my car and read the data from car ECU.
My question is whether Android has anything to do with an automobile????
OK folks lets dive into something interesting topic..This time I have got something fishy stuff which I found in the web few days back… As usual I was searching for new updates and new apps published in Android Play Store but suddenly something got stuck to my attention regarding OBD Bluetooth, OBD Console etc etc. But then I just had a look on those apps and could find something similar to speedometer apps found in the market. Later doing small research I could understand that those are diagnostic tools for cars. Once again Android has proved that its not a mere OS built for making calls, sending sms etc it has capabilities beyond a standalone mobile OS.
OK I was taking abt OBD OBD!! Any idea?? Well I am not an automobile mechanic but I would explain what I found on the web.. OBD stands for On Board Diagnostics. It is in fact used for self diagnostics and trouble shooting in automobiles. For more info http://en.wikipedia.org/wiki/On-board_diagnostics On Board Diagnostics are done via OBD port found in cars. Say for example the one found after a long search inside my car
ODB port usually contains 16pins. From the above figure you could find that only six pins are enabled. Here is the complete pin out diagram
OBD ports are usually present in most of the modern cars. You could have a small search beneath the steering column or under the hood.
Ok lets return back to our topic..we were discussing what Android can do with these ports. In fact we could create an interface with our Android device using OBDII Bluetooth connector. The Bluetooth connector looks something similar to this
The one featured above is ELM327 Bluetooth OBDII OBD2 Diagnostic Scanner readily available in amazon. If we are able to create an interface between our car and Android device then there opens a whole new world of apps that could convert an Android device into something a different tool for vehicle diagnostics and monitoring such as speed monitoring, fuel statistics, engine temperature etc etc. I think geeks have already started rolling out apps for On Board Diagnostics. Here are few
and lots more……..
In fact I couldn’t really believe that Android 4.2.2 runs seamlessly on my low end legacy device Samsung Galaxy Fit . Thanks to Cyanogenmod 10 (CM10) team for creating after market custom ROM’s. The CM ROM performs much better than the stock ROM and operates without any glitch. I would recommend everyone who uses Android to root and install custom ROM’s which opens up a new world of Android OS which you cant experience in stock ROM’s. Trust me rooting doesn’t cause any harm to your device!
The best garage for Android Modd: http://forum.xda-developers.com
Link to Cyanogenmod: http://www.cyanogenmod.org/
Clockwork Mod Tool (must have app for every rooted device): http://www.clockworkmod.com/
Tech spec of SGS Fit
- 600Mhz ARM CPU
- 160MB internal memory
- 250MB RAM!!