Tablet Technology Trend

How Install apk from sdcard using internet browser

2012-06-13T11:12:00.003-07:00

What if you need to install an apk from sdcard but you don't have a file manager installed yet.
And to make things worse you don't have internet access to download it from the market!

Well, there's a solution to that. Provided by every internet browser available.
(I suppose you have one installed :-)

Here's what you need to do:

1. Put the apk file in the main directory of your sdcard. Rename it to something very short for easy typing. In this example, I will use "fm.apk".

2. Boot your device. Goto Security Settings and check "Unknown Sources".

3. Open your internet browser. In the address bar type "file:///sdcard/<filename>.apk". (Without the double quotes of course)

In our example above it should look like this: file:///sdcard/fm.apk

4. Press "Go". That's it! Installation started!

How to root Alcatel OT 990

2012-05-01T08:38:00.004-07:00

This is for those people who not have much experience about rooting n those who got tired of HSUSB drivers for Alcatel OT 990, here is simple solution.

Step 1: install PDANet to pc here is link http://junefabrics.com/android/

Step 2: While installing PDANet u ll get windows prompt...... click on Install Anyway
"
Step 3: During installation further u ll get a pop up saying..... Insure USB Debugging is On.... etc connect ur Phone n click on Yes (You must have turn on usb debugging in your phone for that go to settings > applications > development > Usb debugging)

Stup 4: Install SuperOneClick to your pc, Download SuperOneClick 1.9.5 (Later versions May NOT WORK!) Here is link http://www.4shared.com/zip/A-qwLIMw/..._22OT-990.html

Step 5: Go to the Downloaded SuperOneClick folder,there will be a folder called "ADB" open it. There you will find 2 adb.exe files,one for Win 7,and one for Win XP.
Open your required file, it will show a command prompt window, Type "adb devices" and you should get something like 1234567890ABCDEF
If you get that,just close it.

Step 6: Now right click on Superoneclick icon and run as administrator.

Stup 7: Hit the Root button in superoneclick window and it will start rooting ur fone.

Step 8: while rooting it will ask u to.... Chek it by test Run.....press ok n ur phone is rooted ( To ensure u can c superuser app in your phones apps after rooting)

Now driver problem is already solved with this updated version of Alcatel Androidmanager download and install it from here http://www.alcatelonetouch.com/globa...es/ot-990.html

How to create and Ice Cream Sandwich VM on a PC

2012-05-01T08:35:00.001-07:00

Easiest Step-By-Step Tutorial for Creating an Ice Cream Sandwich Virtual Machine on a PC

INSTRUCTIONS (Build Revision: 2012-03-07):

Install VirtualBox (version 4.1.14-77440 or higher)
1. Download Here: https://www.virtualbox.org/
Run VirtualBox, click File, select Import Appliance
Download THIS archive and extract the files locally. In VirtualBox, choose the "Android-x86 (ICS).ova" file to complete the Import process
Start the Android-x86 machine (Let the default selection boot)
Once the Android OS boots, click "Machine" on the VirtualBox menu bar, and select "Disable Mouse Integration". (This will give you a blue mouse that you can now use inside the Android OS)
Unlock the screen by dragging the lock to the side, and enjoy Ice Cream Sandwich!

===
TIPS:

Press Right-CTRL on your keyboard to release your mouse from the virtual machine.
To turn off the virtual machine, select "Machine" from the menu bar and click "ACPI Shutdown".

NOT WORKING:

Camera

NOTE:

When a new Android-x86 release comes out, I will try to keep this thread updated with a new download package that contained an update OVA file. The instructional steps should never need updating as I will make all considerations in the new OVA files.

Flytouch VI Custom Firmware: The Blazing Dragon 0.2

2012-05-01T08:03:00.001-07:00

Currently there isn't much thing in it but the main goal was achieved: the pak file has been edited and now it is proofed that custom firmware can be done with little changes. Of course because we don't have the source code we can't do big changes but I hope in the future there will be even more modification/features/tweaks and you people out there also have ideas about some changes and you can also help me to do them.

Current Version 0.2:
http://adfoc.us/309555089297

Flash tool:
http://adfoc.us/309555090010

The deleted apps from the original rom. If you need something here they are:
http://adfoc.us/309555090019

Here is all of my tools which helped me to make this rom:
http://adfoc.us/309555090025

Use that flash tool which is in this post because if you not use that you will get bootloop. Mine has modified ini file exactly for this problem!

Current features:

Code:

Android 4.0.3.
Has root by default.
Different boot.img.
Changed system apps.
Based on stock 0406.
Custom boot animation support.
The screen calibrate itself on first boot.
Market fix installed by default.

Changelog:
0.2:

Code:

-Better root. It not install itself on every boot, just on the first boot.
-You don't need to calibrate the screen on first boot, it do for itself. Feel free to re-calibrate in the menu.
-Custom boot animation support, and there is an installed one.
-Newer boot logo.
-Fixed YouTube.apk as a system app.
-Removed the stock launcher and replace it with Apex Launcher. This is a modified version of that launcher, but a lot better.
-Titanium Backup updated.
-I planned a lot of build.prop tweak but it override the market fix, so they are not included yet... Stay tuned, for next releases.

Full changelog which contains every releases:
http://adfoc.us/309555090036

How to dual boot Windows 7 and Ubuntu 12.04 with a SSD as boot drive and HDD as the secondary drive

2012-05-01T07:50:00.001-07:00

Here is a guide to help you with dual booting Windows 7/Ubuntu 12.04 with a SSD as boot drive and HDD as the secondary drive.

First partitions. Using my current disks as examples. 1) 128gb SSD and 1) 750gb HDD.

Boot computer using live DVD/USB and open Gparted in your applications. Or open terminal and enter gparted.

The SSD should be /dev/sda and HDD should be /dev/sdb. On your SSD create three partitions.

1) 50gb format as ntfs and then label “windows_7”
2) 15gb and format as ext4 and choose “/”
3) The rest format as ext4 and choose “/home”

For the HDD, you will need to decide if you mainly run Windows or Linux. If you don't need your linux folder more than Windows, I would suggest just formating the entire HDD as “ntfs” and label “windows”. Other wise split up the drive as you see fit. If you are going to symlink common folders used in both systems, I then suggest using more room for windows.

Now comes the fun part. Accept your changes and reboot your device with the windows install disk either in the dvd drive or in the usb port. Reboot and choose to boot drive where your windows disk is located. Follow the prompts to install windows. After the system is installed, do not do any updates just yet. We are going to move “User” to the HDD and as a result saving much needed space on your SSD leaving only system and programs on there. To move /users to HDD follow this handy guide on a clean installed Windows.

1. Once setup and at the desktop, don't bother doing any customisation, but start up Computer Management via Control Panel\System and Security\Administrative Tools.
2. Local Users And Groups\Users, select Administrator and enable the account.
3. Reboot.
4. Logon as Administrator, no password, go into normal User Account management and delete the account created during setup and any and all files.
5. Startup Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
6. Change the ProfilesDirectory from %SystemDrive%\Users to for example D:\Users.
7. Close down regedit and reboot.
8. Logon as Administrator and create a user account.
9. Logoff and logon using new account and let system create profile, which is now on your D: drive which of course now the default location for all your personal files.
10. Start up Computer Management via Control Panel\System and Security\Administrative Tools.
11. Local Users And Groups\Users, select Administrator and disable the account. Leaving this enabled is a big security risk !!!

The benefit to this is the Downloads/Music/Videos/My Documents/Documents folders will all be relocated back to ur HDD saving valuable space on your SSD. We will then symlink those same folders to /home in linux later saving even more space yet having a common place to use the folders to be cross platform compatible.

Next, finish installing and setting up Windows 7. It's a good idea to fully update Windows at this point. After that is complete you will then need to reboot computer with your Ubuntu 12.04 USB or DVD in the appropriate drive and select the correct bootable device. Then in the selection menu, choose to run linux from live DVD/USB.

This is a key part here. When it comes time to select which installation method you want, you will want to choose install Ubuntu next to Windows for dualboot system. Also, in the drop down box for where grub (boot loader) is to be installed, do NOT choose the same as windows loader as it will write over top and you wont be able to boot in to windows. Choose /dev/dba/ in the very root of your ssd. Then Linux will set up the “/” and “/home” in the partitions you made earlier.

After it installs, it will ask you to restart the machine and remove any media from the drives. Do so to let it finish rebooting.

Next up is Grub. Instead of choosing Ubuntu, choose Windows to verify that it still works and then open up computer and then D:/ and verify that D:/Users is located there. If so, reboot and choose Ubuntu and verify the installation took fine. If it doesn't boot Windows, you'll need to re-install windows and probably Ubuntu. This can be a pain in the butt but you will be rewarded later with a very nice setup.

After a successful boot to both systems you should be in Ubuntu to configure it to auto-mount “windows” at each boot.

Tweak Linux to support trim for ssd and other useful modifications

Add discard next to the proper drive in /etc/fstab file. Open a command-line (terminal) and
type:
sudo gedit /etc/fstab

Results will be similar to the following:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=7219b425-9d8d-41e4-a957-e26b1e8ead4c / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=35030494-3d2d-4d4a-a605-32d91e7a6d12 /home ext4 defaults 0 2

The ones highlighted in red should be changed to add discard infront of errors= and
defaults. You can also add noatime if you want to. So it should look like this after the edit.

# / was on /dev/sda5 during installation
UUID=7219b425-9d8d-41e4-a957-e26b1e8ead4c / ext4 discard,noatime,errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=35030494-3d2d-4d4a-a605-32d91e7a6d12 /home ext4 discard,noatime,defaults 0 2

Open Terminal and type:
sudo blkid

Output should be something like this.
/dev/sda1: LABEL="Windows_7" UUID="48AC1276AC125EAE" TYPE="ntfs"
/dev/sda3: UUID="35030494-3d2d-4d4a-a605-32d91e7a6d12" TYPE="ext4"
/dev/sda5: UUID="7219b425-9d8d-41e4-a957-e26b1e8ead4c" TYPE="ext4"
/dev/sdb1: LABEL="windows" UUID="1D3B46DD6CFD93D5" TYPE="ntfs"
/dev/zram0: UUID="4dc3b795-0931-484e-b809-0946253ab710" TYPE="swap"

Cut and paste the output information to a plain txt document for future use. Next you will want to type the following in terminal:
sudo gedit /etc/fstab

Next add this to the fstab at the bottom.
# Mount at boot
UUID=1D3B46DD6CFD93D5 /media/windows ntfs-3g defaults,rw,owner,uid=1000,gid=100
This will auto mount your windows hdd if you have the user folder moved to the hdd. Leaving the ssd mainly for system files, programs, and with linux would be “/” and “/home”. You will see a very responsive system then.

Before you close, add the following to at the bottom of your FSTAB.

tmpfs /tmp tmpfs defaults,noatime,mode=177 0 0
tmpfs /var/log tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /tmp tmpfs nodev,nosuid,size=7G 0 0

Your finished /etc/fstab should look similar to the following.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=7219b425-9d8d-41e4-a957-e26b1e8ead4c / ext4 defaults,discard,noatime,errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=35030494-3d2d-4d4a-a605-32d91e7a6d12 /home ext4 defaults,discard,noatime,defaults 0 2

# Mount hdd at boot
UUID=1D3B46DD6CFD93D5 /media/windows ntfs-3g defaults,rw,owner,uid=1000,gid=100

tmpfs /tmp tmpfs defaults,noatime,mode=177 0 0
tmpfs /var/log tmpfs defaults,noatime,mode=1777 0 0
tmpfs /var/tmp tmpfs defaults,noatime,mode=1777 0 0
tmpfs /tmp tmpfs nodev,nosuid,size=7G 0 0

Hit save then exit /etc/fstab. Then reboot your machine to test the auto-mount of windows.

Next, lets stop the syslog services and clean out your current temp and log directories. We'll also mount the new RAM disks and restart the syslog service. Note: the name of the syslog service will change from distribution to distribution.
sudo /etc/init.d/rsyslog stop
sudo rm -rf /tmp/*
sudo rm -rf /var/log/*
sudo rm -rf /var/tmp/*
sudo mount -a
sudo /etc/init.d/rsyslog start

To symlink important folders from windows to /home saving much is recommended so you can share files between system. In Linux /home/user folder, delete the following folders.
Documents
My Documents
Downloads
Videos
Music

Open terminal and enter the following to symlink windows folders over to linux thus using a centralized spot for both system.

ln -s /media/windows/Users/(USERNAME)/Documents /home/(username)
ln -s /media/windows/Users/(USERNAME)/”My Documents” /home/(username)
ln -s /media/windows/Users/(USERNAME)/Downloads /home/(username)
ln -s /media/windows/Users/(USERNAME)/Videos /home/(username)
ln -s /media/windows/Users/(USERNAME)/Music /home/(username)

*Make sure when putting in username, the first one is username for windows while the second one is the username for linux.

Time to edit the sysctl.conf for some added tweaks for internet boosts and other good things.

Hit cntrl+alt+T to open terminal and enter:
sudo gedit /etc/sysctl.conf

Add the following to the bottom of the conf file. (cut and paste should be fine)
# Tweaks for faster broadband…
net.core.rmem_default = 524288
net.core.rmem_max = 16777216
net.core.wmem_default = 524288
net.core.wmem_max = 16777216
net.ipv4.tcp_wmem = 4096 87380 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_mem = 524288 524288 524288
net.ipv4.tcp_rfc1337 = 1
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.tcp_sack = 0
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_workaround_signed_windows=1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_ecn = 0
net.ipv4.route.flush = 1
net.ipv4.tcp_low_latency=1
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.tcp_mtu_probing=1
net.ipv4.tcp_frto=2
net.ipv4.tcp_frto_response=2
## don't cache ssthresh from previous connection
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
## recommended to increase this for 1000 BT or higher
net.core.netdev_max_backlog = 2500
##enable window scaling
net.ipv4.tcp_window_scaling = 1
##improve desktop reactions
vm.swappiness=10
vm.vfs_cache_pressure=1000
vm.dirty_background_ratio=10
vm.dirty_ratio=30

Save and Exit.

Another one if you are using a ssd drive for main activity, check your scheduler.

Open terminal and enter the following.
cat /sys/block/sdX/queue/scheduler
*where X is the letter for the SSD device.

The readout should be the following.
noop deadline [cfq]

Note: Only switch the scheduler to noop or deadline for SSDs. Keeping the cfq scheduler for all other physical HDDs is highly recommended.

To change this, using the system virtual filesystem is preferred when the system has severy physical storage devices (for example an SSD and an HDD). Add the following line in /etc/rc.local:
echo noop > /sys/block/sdX/queue/scheduler

where X is the letter for the SSD device.

Because of the potential for udev to assign different /dev/ nodes to drives before and after a kernel update, users must take care that the noop scheduler is applied to the correct device upon boot. One way to do this is by using the SSD's device ID to determine its /dev/ node. To do this automatically, use the following snippet instead of the line above and add it to /etc/rc.local:

SSD=(ata-OCZ-ONYX_XA1Y7CE3709UG79OTHVM ata-SAMSUNG_SSD_830_Series_S0VTNYABA01063)

declare -i i=0
while [ "${SSD[$i]}" != "" ]; do
NODE=`ls -l /dev/disk/by-id/${SSD[$i]} | awk '{ print $NF }' | sed -e 's/[/\.]//g'`
echo noop > /sys/block/$NODE/queue/scheduler
i=i+1
done

where SSD is a Bash array containing the device IDs of all SSD devices. Device IDs are listed in /dev/disk/by-id/ as symbolic links pointing to their corresponding /dev/ nodes. To view the links listed with their targets, issue the following command:
ls -l /dev/disk/by-id/

Swap Space on SSDs

One can place a swap partition on an SSD. Note that most modern desktops with an excess of 2 Gigs of memory rarely use swap at all. The notable exception is systems which make use of the hibernate feature. The following is recommended tweak for SSDs using a swap partition that will reduce the "swapiness" of the system thus avoiding writes to swap. In the /etc/sysctl.conf you can Maximize performance by changing the values below:
vm.swappiness=1
vm.vfs_cache_pressure=50

Example of a machine with 8 GB of physical memory:
tmpfs /tmp tmpfs nodev,nosuid,size=7G 0 0

Configuring your system to compile Android Open Source Code.

Java-Oracle 7:

This isn't yet supported with Android compiling that I know of. If you have this listed you will need to uninstall this and re-install java6 JDK/JRE.

Open Terminal and first type in the following.
sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 \ g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown \ libxml2-utils xsltproc zlib1g-dev:i386

Then type "sudo gedit /usr/include/linux/usb/ch9.h" and on line 592 replace
return __le16_to_cpu(epd->wMaxPacketSize);
with:
# return le16_to_cpu(epd->wMaxPacketSize);
return __le16_to_cpu(epd->wMaxPacketSize);

Installing required packages *ubuntu 12.04 (this is taken from source.android.com/source/initializing.html)

Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master. Open terminal and cut and paste the following:
sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \ libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 \ g++-multilib mingw32 openjdk-6-jdk tofrodos python-markdown \ libxml2-utils xsltproc zlib1g-dev:i386

Setting up ccache

You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.
Put the following in your .bashrc or equivalent.
export USE_CCACHE=1

By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.
export CCACHE_DIR=<path-to-your-cache-directory>

How To Decrease Boot Times
**Full credit to PinGuy for suggesting this. Original thread found HERE

If you are finding it is booting slower then it used to there are a couple of things you can do.
The first is to run this command:

Code:
sudo rm /var/lib/ureadahead/pack

Then reboot twice. First time to generate a new ureadahead. Then the second time you boot it, it should be a lot faster. You can read up more about ureadahead here. You can also run BootUp-Manager:

Code:
su-to-root -X -c bum

And Turn off anything that starts at boot you don't want running.

**( I don't take credit for making any of these mods or the brains behind them. I only wanted to sit down and do a lot of research to make my system run very good. After talking to a few developers, they were interested in this and encouraged me to start a tutorial on this setup)

I have a pretty powerful laptop. i7, 16gb RAM, fully loaded with a SSD and a HDD. After using these tweaks, it's possible to boot Ubuntu in about 6.5 seconds from Grub and 8.5-9 for Windows. What most excites me is the ability to share folders between the two systems allowing me to save a tremendous amount of storage space and the ability to use them in both systems.

This is going to be a work in progress thread and urge others to PM tips and tweaks so they can be added on so we all can run our systems the best possible. Also, if you see any errors, please point them out so it can be adjusted. Feel free to PM me if you spot any problems.

Resources:
Download Ubuntu 12.04 LTS Here
https://wiki.archlinux.org/index.php..._State_Drives;
http://www.cyberciti.biz/faq/howto-d...-get-command/;
http://forum.xda-developers.com/show....php?t=1604076
http://source.android.com/source/index.html

For Git setup and SSH keys to commit to git.
http://help.github.com/linux-set-up-git/

How to root Bluestacks Beta

2012-05-01T07:35:00.001-07:00

This is a step by step guide on how to root Bluestacks

DOWNLOAD LIST (assuming you already have BlueStacks installed):

Code:

1. initrd-betahack.img    ***INCLUDED***
2. ramdisk.img     ***INCLUDED***
3. system.img-----------------NOT INCLUDED!!!
4. su.x86   ***INCLUDED***
5. BlueRegistryMOD ***INCLUDED***

--------------------------------------------------------------------------------------------------
Download from Here:
http://www.androidfilehost.com/main/...Stacks%20Beta/

Code:

These are the custom files needed for root and r/w
-initrd-betahack.img
-ramdisk.img
-system.img
-su.x86

FILE: initrd-betahack.img
-From Beta (modified)
-Place it in \%programdata%\BlueStacks\Android\

FILE: ramdisk.img
-From Mod-V3.zip alpha
-Place it in \%programdata%\BlueStacks\Android\

FILE: system.img
-Extracted from xRepinsSporsx Root.fs (for Google Play)
Or
-Extracted from latest BlueStacks Root.fs
-Place it in \%programdata%\BlueStacks\Android\

FILE: su.x86
-From Androidx86 build (extracted from rooted alpha)
-This is the x86 superuser binary that auto-grants superuser-rights
***This file will be pushed to android using adb later on***

-------------------------------------------------------------------------------------------------

Code:

These files are the stock Beta files and remain in place
-kernel.elf
-Data.fs
-Prebundled.fs
-SDCard.fs

FILE: kernel.elf, Data.fs, Prebundled.fs, SDCard.fs
-From Beta
-Placed in \%programdata%\BlueStacks\Android\

---------------------------------------------------------------------------------------
Changes that need to be made to the registry are contained in BlueRegistryMOD.reg

FILE: BlueRegistryMOD.reg

***WARNING***
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) found here:

FIND YOUR SPECIFIC GUID HERE!!!
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”

Example of a GUID:
“USER_GUID”=”8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293”

Example of a modified “BootParameters” with correct GUID and changes made to mount /system:
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Andr oid]
"BootParameters"="root=/dev/sda1 SRC=/android DATA=/dev/sdc1 SDCARD=/dev/sdd1 GUID=8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293 armApps=true GlMode=1 OEM=BlueStacks "

***ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg***
-------------------------------------------------------------------------------------------
THIS IS THE PROCESS:
***Make sure to exit BlueStacks before proceeding***

1. Paying attention to the guidelines above, place the following files in their correct location – this includes initrd-betahack.img, ramdisk.img, and system.img.
2. After finding your GUID and making the appropriate changes to BlueRegistryMOD.reg in 2(two) places, run the registry file.
3. Start/restart BlueStacks – go to the Start menu>type Start Bluestacks
4. Start adb on your computer
a. Connect to bluestacks - #adb connect 127.0.0.1:5555
b. Ensure you have root access - #adb root
i. You should get message: “adbd is already running as root”
c. Mount system as read/write - #adb remount
d. Remove ‘dummy’ superuser - #adb shell rm /system/xbin/su
e. Push x86 superuser to BlueStacks - #adb push su.x86 /system/xbin/su
i. su.x86 must be in the same Windows directory you are running in the console
f. Correct the permissions for superuser - #adb shell chmod 6711 /system/xbin/su
g. Remount system read only - #adb shell mount -o ro,remount t-ext4 /dev/sdb1 /system
h. Exit adb by closing the console window
5. Restart BlueStacks – go to the Start menu>type Start BlueStacks
6. At this point you should have root and read/write access.
a. Verify root using a tool like Root Check. I suggest Root Check Pro because it will point you to what the problem is if you do NOT have root.
b. Verify read/write access using a tool like Root Explorer.
7. Enjoy.

***This is a sure-fire way to get root and read/write access. However, I find that there are still issues with GAPPS (gmail, calendar specifically)

Download from here:
http://www.androidfilehost.com/main/...Stacks%20Beta/

Extended system.img
http://www.androidfilehost.com/main/...%20system.img/

Mount2SD An All-in-one to sd-ext script

2012-04-23T08:24:00.002-07:00

Mounts2SD - An All-in-one to sd-ext script

Mounts2SD is a customizable sd-ext control script that can be used to move content to and from the second sdcard partition known in Android as sd-ext. These scripts comes in many variants with different purposes. Mounts2SD has most of these, and more, build into one single script with controls to set it up after most needs.

Features

Graphical installer with configuration options and auto deletion of almost any existing app2sd script

Control script to manage configuration from shell

SWAP Support

Link Apps from data as system apps

Move Apps to sd-ext

Move Dalvik-cache to sd-ext

Move Apps Data to sd-ext

Move system linked apps to sd-ext

Move Cache to a tmpfs (With auto control)

Internal nand and sdcard readahead optimization

Handles slow sdcards that takes time to initiate

Support for extended partitions

Checks filesystems for errors on boot using e2fsck

Let's you use whatever linux filesystem supported by kernel

Able to revert any prev. options

Fix permissions

Internal/External storage optimization

Fix CyanogenMod dalvik to /cache

Revert the sd-ext/data partitions so that sd-ext becomes the new /data

Android Market 'Not enough space' fix

Checks available free space before moving content

How to install

Note that you need to have a custom ROM installed which supports init.d scripts.

Download the ZIP file in the download section

Copy the ZIP file to your phones SD-Card

Boot you phone into recovery

Make sure that recovery does not check ZIP's signature as the ZIP is not signed

Choose to install ZIP from SD-Card

Select the ZIP file you copied to the SD-Card and fallow the installation process

After installation, you can change any settings you choose during install, by using the shell command 'm2sd <option> <value> from an adb shell or a terminal app on your phone. You can type 'm2sd help' in the shell to get a list of available options and values.

You can also read more about the different option below.

Partition table

Android looks for an Fat32 partition on the first partition on the sdcard. Therefor most app2sd scripts looks for an sd-ext partition on the second partition in the sdcard.

This script however does not care where the partition are placed. You can even put it in an extended partition. However it is Recommended to place sd-ext as the second partition to be compatible with your recovery.

M2SD also supports SWAP partitions. Again there is no rule where to place this, however it is Recommended to place it as the third partition.

Recommended partition table

/sdcard (Fat32)

/sd-ext

SWAP

Safe Mode

As of version 2.2.0, m2sd has a safe-mode state. This is an automatic state that is used when the script can't detect a correct sysinit method. The correct way to execute init.d, is to add "exec /system/bin/sysinit" to the init.rc file and of cause create the script sysinit that will execute init.d

The old way is to create a service for init.d in init.rc.

The problem with the service is that it is executed while the rest of the boot process is working. This means that moving things like /data/data and /data/dalvik-cache will create problems, because the system will keep trying to rebuild the moved content to it's original path while m2sd is moving it.

The sysinit script executed with the exec command however, will stall the boot process until all of the init.d scripts has been executed. That means that m2sd can move the content and bind the original path to the sd-ext path before the system starts it's work.

The Safe mode state will disable dalvik and data no mater what the config says to avoid these problems. So if your ROM runs m2sd in safe-mode, write to the ROM dev's and ask them to include the more correct way of handling init.d

System Apps

By default Android has two app directories in the data partition (/data/app & /data/app-private). Mounts2SD provides a third directory (/data/app-system). Every app placed in this directory will be automatically linked to the /system/app folder, making android believe that it is a system app. Some apps needs this in order to provide additional options. By using /data/app-system, you can achieve this from any file manager without giving write access to the system partition and without taking up two much space on that partition.

Links will be automatically removed again once an app is removed from /data/app-system

Configuration options

Apps - m2sd apps <enable/disable>

By enabling this option, the script will move all apps from /data/app into /sd-ext/app and link that folder to the original path so that Android can find the content. This is the function of the most app2sd scripts.

Dalvik Cache - m2sd dalvik <enable/disable>

By enabling this option, the script will move all content from /data/dalvik-cache into /sd-ext/dalvik-cache and link that folder to the original path so that Android can find the content.

Data - m2sd data <enable/disable>

By enabling this option, the script will move all content from /data/data into /sd-ext/data and link that folder to the original path so that Android can find the content.

Cache - m2sd cache <enable/disable/auto>

By enabling this option, the script will link /sd-ext/cache to the /cache location. This is useful if your cache partition is to small to download big apps from market.

If you don't have an sd-ext partition, the cache will be linked to /data/cache instead.

Also by setting the auto option instead of enable, the script will only remount the cache if the nand cache is below 40mb.

Download Cache - m2sd dlcache <enable/disable>

By enabling this option, the script will only link /cache/download to either sd-ext, data or tmpfs.

File System Type - m2sd extfs <filesystem>

By default M2SD mounts the sd-ext partition using auto file system detection. However some kernels have pure support for auto detection which means that for an example ext4 get's mounted as ext2. This option allows you to define a file system manually to use when mounting the sd-ext partition.

Readahead - m2sd readahead <value in kb>

By default M2SD set's the sdcard readahead to 512kb. This is the recommended value for most use, however if you use a lot of UMS transfers and have a fast sdcard, it might be useful to set this value a bit higher.

Noatime - m2sd noatime <enable/disable>

By default m2sd remounts the system partition with atime and diratime disabled. By enabling this option, atime an diratime will also be disabled on data and sd-ext.

CM Dalvik - m2sd cmdalvik <enable/disable>

For some reason, the CM Team has come up with this fun idea to place the dalvik cache for all system apps in /cache/dalvik-cache instead of /data/dalvik-cache with the rest of it. This is especially fun when you have a cache size of 5mb, because then there is not enough space to build the dalvik-cache and you end up with these really funny reboot loops. However, if you are some boring person that does not find these reboot loop's fun, you can enable cmdalvik to fix this problem. It will force the dalvik-cache in /cache to be placed in the correct /data path among the rest of the dex files.

R-Mount - m2sd rmount <enable/disable>

By enabling this option, M2SD will mount the data partition on /sd-ext and the sdext partition on /data. Your sdext partition becomes your new data partition. Every m2sd command will do their regular job, only instead of moving from data to sdext, it will move from sdext to data since sdext will be the primary data partition.

Downloads

4.2.0 Aroma Installer [mounts2sd-4.2.0_aroma.zip] (Apr 12, 2012) (MD5: 59708d732f591edeb468c5736fc940f2)

[Default Mirror] GoogleCode.com

[Default Mirror] MediaFire.com

This will provide you with the graphical installer Aroma.

-------------------------------------------------

4.2.0 Legacy Installer [mounts2sd-4.2.0_legacy.zip] (Apr 12, 2012) (MD5: 25d8fd97032f145d8bfa21dcdcfb8866)

[Default Mirror] GoogleCode.com

[Default Mirror] MediaFire.com

This will provide you with the standard legacy text installer.

Samsung Conquer 4G root install, CWM, and the FC17 Update

2012-04-23T08:14:00.003-07:00

Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few second

Here are the files you will need -
CONQUER-ROOT.zip

Unzip all the files on your computer and follow these steps.

1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select theSPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.

2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.

3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.

4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.

5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.

Motorola Android Phones new Root method

2012-04-23T08:02:00.001-07:00

The method is far from easy, but it works if none of the existing exploits and tricks don't.

Ok, there are some simple-like steps to root your phones:

1. If you have an unrooted gingerbread, ask for a rooted gingerbread userdata partition image (aka CG37) with a modified local.prop file and USB debugging enabled.

The value that you need to modify is ro.sys.atvc_allow_all_adb from 0 to 1.

IMPORTANT: The best you can do is to double wipe the phone and then modify local.prop an allow USB debugging, so the data partition doesn't have any of your personal information.

Then you can create a userdata partition image by typing this in the shell (with root access)

Code:

dd if=/dev/block/userdata of=/sdcard/CG37.smg

Code:

busybox dd if=/dev/block/userdata of=/sdcard/CG37.smg

and let it do its work.

2. Once you got your CG37.smg in the SD card, you will have to boot into linux (so you can use sbf_flash).

3. When you are in linux, you need to extract the folder contained in the zip that you can download here mediafire.com/?n100jj66130lgra

4. Then you need to copy the CG37.smg and your original SBF (the non rooted one) to that folder.

5. Now you'll have to start a terminal with root permissions, and move to the folder by typing

Code:

cd <folder>

(where folder is the folder I just mentioned, without the <>, you can drag the folder to the terminal if you don't want to type its address)

4. Then you need to resize that partition to 200 Mb, since sbf_flash won't allow you to flash a big image (approx. 1,1 Gb). You have to type this

Code:

efsck -f CG37.smg

resize2fs CG37.smg 200M

5. Then you need to type

Code:

chmod +x sbf_flash

and then you need to start your phone into bootloader and connect it to the computer, then you type

Code:

./sbf_flash -r --userdata CG37.smg ORIGINAL.sbf

(where ORIGINAL corresponds to the name of your SBF)

and let it its work.

5. Once the phone started up, you now need to run this command

Code:

bash finishroot.sh

And let it finish the work.

6. Now you have your phone rooted. You can just reboot into recovery mode and do a double wipe, because the files that we needed are now in system partition.

How to Root Blackberry Playbook

2012-04-16T07:27:00.002-07:00

I've been diggin into the Playbook for a few days now, trying to figure out who against who here. the goal of course is gaining root.

The things we know so far, is that the device is dual-core 1Ghz cortex-A9, armv7 architecture using OMAP4 platform. On top of it runs a QNX linux that uses Adobe air sdk for application.

Its possible to set the device into Development Mode in the security settings, and use the 'blackberry-connect' utility that comes with the Blackberry TabletOS SDK .
First thing you need to be connected with the pc and playbook on the same wifi.
You will need a private key, and a public key created with the ssh-gen utility or you can use the keys I attach in keys.zip.

Use the utility to connect the device on port 4455:

Code:

blackberrysdk\blackberry-connect -targetHost <ip> -devicePassword <pass> -sshPublicKey <yourkey4096.pub>

Then the device will start the ssh server on the ssh port.

In order to connect it, I used 2 utilities: Peagent, and Putty.

By starting Peagent, load the private key (or .pkk in the zip). and use putty to connect the device.
The username is : devuser

There is also a way to execute native code on the device as first discovered by @b3ll.

The idea is to compile the code in the QNX ide for armv7, making them runnable by : chmod +x nativeapp
and zipping them.
Then connect the device using the Blackberry desktop, copy the zip to "Downloads" directory and use the ssh to unzip the files and run them(in /tmp directory).
The Download directory will be located somewhere under the /accounts directory. I added the native app that @b3ll originally published.

Also, the device has 3 connections in the bottom, the most right is the magnetic charger- which cannot transfer data.
The middle one is micro-USB, and the left one is mini-hdmi.
Leaving the micro-USB the only connection that can transfer data.

Key combinations

POWER - turning on the device

Turning on using POWER + Volume-UP - gives unknown special mode for few seconds.

Thats all i figured out so far

ICS for Nokia N9

2012-04-16T07:20:00.003-07:00

Recently Ics was ported to this devices and ive been playing with it, and damn i love it!!!

Heres a quick video of my phone running ics 4.0.4. Keep in mind this is just the 2 alpha release.

Running google maps!

What is working:

- based on Android Open-Source Project (AOSP) v 4.0.4_r1.1 (IMM76D)
- Google Applications (GApps), PlayStore (Android Market)
- dualboot kernel (without reflashing), ability to choose OS after power on.
- 3D drivers, OpenGL
- hwrotation
- touchscreen (multitouch)
- hw buttons (volume, power)
- ECI accessory (headset buttons)
- USB networking
- lcd off in sleep mode, electron beam effect
- alarm driver, RTC
- mounting MyDocs as "SDCard" [realized; NOT FIXED, but HACK EXISTS]
- basic video decoding (sw) and playback, youtube (choppy)
- wifi (only basic functionality: able to connect to AP. no tethering).
- basic CellMo functionality: network registration, USSD, SMS, data (GPRS/EDGE/3G), signaling. Actually, ofono/ofono-ril stack is used: all things that it able to do on the n900.
- bluetooth (scanning, can pair devices. I'm able to send files between SGS2 and N9. I didn't test deeper.).
- charging (note: without any notification in UI)
- sensors: accelerometer
- audio: playback (audio routing to: loudspeaker, headset or earpiece)
- lights HAL (lcd brightness)
- root access (via adb shell; su/Superuser.apk)
- fakeGPS (ability to trick system and set any location as GPS fix), no real GPS support yet!

What is not working:
Critical:
- lcd off in sleep mode
- reboot/halt (in R&D / regular mode) few minutes after entering suspend
- battery status

Installing Google Play Store outside US

2012-03-21T11:01:00.002-07:00

How to install the full google play store with books,music and movies anywhere!

So when google announced that they will add Books and Movies to the Android Market sadly it was restricted to US only,so now after the update to the google play,again outside the US you will only have access to the apps in the play store,so this guide will allow you to shop books,movies,and music in the play store on your android phone no matter where you are.

REQUIREMENTS

Rooted android device
busybox installed

Steps

connect to a wifi network
download market enabler app from the play store
Download DroidVPN from Play store.
Register here to DroidVPN.
login to your email and verify your droidvpn registration,they will send you another email with a password in it.
Open Market enabler and fake any US carrier (i used t-mobile)
Open DroidVPN and put the email you used in registration as username,and the password they have sent it to you by email as password.
press start in droid vpn.
it should show a green icon in the notification bar that mean you are connected.
clear the play store app cache.
run the play store it should open the full US store enjoy

NOTE
You may need Tun.Ko, get it from here if needed

Rooting Nextbook8 Premium and installing Android Market app

2012-03-21T10:51:00.003-07:00

How to Root and install Market on your Nextbook8 Premium

This rom is based on Samhain's release: SamDroid v1.13

Modifications (mostly GUI / cosmetic tweaks):

1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.

2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)

A couple of things to note once you have installed the rom:

- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.

- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.

- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.

- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).

- You can also grab Adobe Flash 11 from the market and it'll work correctly.

- This release boots MUCH faster, and is even more responsive than before.

- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.

VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.

Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.

NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.

Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.

NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.

Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.

Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.

Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:

Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)

Android Home Launcher list

2012-03-21T10:09:00.003-07:00

List of all Android home launchers.

FREE

[SSKIN] Butterfly Launcher 2.1 and up
360 Launcher off-market, 2.1 and up
91 Pandahome Pro 2.0 and up
ADW.Launcher 2.0 and up
ADW.Launcher (donut) 1.6
Android 2.3 Launcher (Home) 2.1 to 2.3
Android Seven-Launcher_Demo 2.2 and up
anTab Launcher lite 2.1 and up
aOS Launcher Free 1.5 and up
Apex Launcher Beta off-market, 4.x
AppsDesktop 4 Demo 1.5 and up
aShell Home Screen Launcher 2.1 and up
Balancer Launcher 2.1 and up
Claystone Launcher 2.1 and up
Crazy Home Lite 2.1 and up
DXHome 2.1 and up
dxTop Lite : Home Alternative 1.5 and up
Espier Launcher 2.1 and up
Espier Launcher 2.1 2.1 and up
EZ Launcher 2.1 and up
FastHome 1.5 and up
For 1.6, Tag Home(Launcher) 1.6 and up
For 2.1, Tag Home(Launcher) 2.1 and up
For 2.2+, Tag Home(Launcher) 2.2 and up
FTL Launcher Lite 2.3 to 3.0
Full Screen Launcher 2.2 and up
Gingerbread Launcher 2.2 and up
Gingerbread Launcher free 2.2 and up
Gingerbread Launcher qDH Free 2.3.7 and up
GO Launcher EX 2.0 and up
Gravity Home 2.1 and up
HCL Launcher 2.1 to 3.2
HelixLauncher 2.0 to 2.1
Hi Launcher 2.1 and up
Home++ beta 1.6 and up
home17 1.6 and up
home35 1.6 and up
home90 1.6 and up
HomeForYou 2.1 and up
homescreen 3D (free version) 1.6 and up
ICS Launcher 2.0 and up
iHome 2.1 and up
iLauncher Lite (iPhone) 2.1 and up
keeworld Home lite 1.6 and up
keeworld L★Home 1.6 and up
KidsProof Launcher 1.6 and up
KidZone Lite Secure Launcher 1.5 and up
Kisekae Lab. 2.1 and up
Ks Launcher for 1.5 1.5
Ks Launcher for 1.6/2.1 1.6 to 2.1
Ks Launcher for 2.2/2.3 2.2 and up
Launcher 2.2 and up
Launcher 2 for QHD 2.2 and up
Launcher 7 2.1 and up
Launcher Sample 2.2 - 2.3.7
Launcher+ beta 2.1 and up
LauncherPro 2.0 and up
Lightning Launcher 1.5 and up
LiveHome 1.5 and up
MAGIC The Launcher 2.1 and up
MAGIC The Launcher SD 2.2 and up
MAGIC The Launcher SD English 2.2 and up
MAGIC-Za_Rancha 2.1 and up
Metro UI Lite 2.1 and up
Minimal Home 1.5 and up
MIUI Launcher off-market, no required Android version listed
MXHome Launcher 2.1 and up
My Home Lite 2.1 and up
My Launcher 2.1 to 2.3.7
Nemus Launcher 2.1 and up
NetFront Life Screen 2.1 and up
Nova Launcher 4.0 and up
Old Crazy Home Lite 1.6 and up
Perfect Home 1.5 and up
Pure Breeze Launcher Lite 2.1 and up
QQLauncher Pro 2.0 and up
Quick Launcher Home 2.1 and up
Regina 3D Launcher 2.1 and up
Rocket Launcher 2.1 and up
RUI Home 2.1 and up
Secret Home 2.1 and up
Simple Home (Lite) 2.2 and up
Smart Launcher 2.1 and up
ssLauncher 2.2 and up
Tap Home 2.1 and up
Target Home Launcher choose app as home, 1.5 and up
vLauncher - best app organizer 2.0.1 and up
Wafu 1.6
Wafu2 2.1 to 2.2
WaterMoon Launcher 2.1 and up
Windows Phone Android Lite 2.1 and up
Zeam Launcher 2.2 and up

PAID

ADWLauncher EX 1.6 and up
Android 2.3 Launcher (Home) + 2.1 and up
Android Seven Launcher-Full 2.2 and up
anTab Launcher 2.1 and up
aOS Launcher Pro 1.5 and up
AppsDesk 4 Suite 1.5 and up
AppsDesktop 4 1.5 and up
BIG Launcher 2.1 and up
Crazy Home 2.1 and up
dxTop Pro : Home Alternative 1.5 and up
EB Launcher 2.2 and up
FTL Launcher 2.3 to 3.0
Full Screen Launcher PRO 2.2 and up
GB Launcher Donate 2.2 and up
GDE - The new home experience 1.5 and up
Gingerbread Launcher qDH 2.3.7 and up
Gravity Home Pro 2.1 and up
HCL+ Launcher 2.1 to 3.2
HomeForYou_Key key, 2.1 and up
homescreen 3D (full version) 1.6 and up
ICS+ Launcher 2.1 and up
iLauncher 2.1 and up
keeworld Home 2.1 and up
keeworld ★Home 2.1 and up
KidZone Secure Home Launcher 1.5 and up
Ks License key, 1.5 and up
Launcher 7 - Donate 2.1 and up
LauncherPro Plus Unlocker 2.0 and up
LiveHome Ads Key key, 1.1 and up
LiveHome Pro Key key, 1.1 and up
Metro UI Pro 2.1 and up
MIUI.ADW iPhone Launcher 2.0 and up
My Home 2.1 and up
Nova Launcher Prime 4.0 and up
OCEAN HOME 2.1 and up
Open Gesture Pro 1.6 and up
Pure Breeze Launcher 2.1 and up
Regina 3D Launcher Pro 2.1 and up
Rocket Launcher FX 2.1 and up
ROSE HOME 2.1 and up
Simple Home 2.2 and up
SKY HOME 2.1 and up
SPB Shell 3D 2.1 and up
VTL.Launcher 2.0 to 2.3.7
Windows Phone Android 2.1 and up
Xperia Arc Launcher 2.1 and up

Android App Store List

2012-03-21T10:03:00.002-07:00

Here is a list of all Adroid application stores.

AllBinary
Amazon Appstore
AndAppOnline
Android Tapp
AndroidPIT
AppBrain
appcity
appitalism
appoke
appolicious
appsfire
AppsLib
AppStoreHQ
Aproov
at&t AppCenter
Bazaar
boostapps
Camangi Market
Cisco AppHQ
djuzz
droydmarket
FastApp
GetJar
Google Play (The Only Official Android Market)
handango
Handmark
Handster
Insyde Market
M1 AppStore
Matchfuel
MiKandi (Adults Only)
mjelly
Mobango
MobiHand OnlyAndroid
MobileApps.com
NVIDIA Tegra Zone
neXva
NOOK Apps
Opera Mobile Store
Slideme
soc.io mall
swisscom
storeoid
YAAM

Temple Run for Android phone

2012-03-21T09:59:00.004-07:00

More recently, the game sweeping iOS users up a vacuum goes by the name of Temple Run. Just like the aforementioned, it is incredibly simple to play, but difficult to master – particularly if you don’t have the steady hand and concentration. You control the direction and position of a continually running Indiana Jones-like character, avoiding obstacles such as fallen trees and large gaps while collecting power-ups and coins in order to survive for longer and unlock additional extras.

This week the folks at Imangi Studios have officially announced availability for their upcoming release of Temple Run for Android. This game has already seen massive success on the iOS platform for both of Apple’s hero devices, iPhone and iPad, and has been the Top Grossing App and Top Free App in the App Store back in January of this year – not an easy feat. There will be a FREE TO DOWNLOAD version of the app available for Android at the end of this month – March 27th to be exact, and the release will almost certainly break records if interest shown thus far is any indication.

While there is no multiplayer feature, the competitive edge is still prevalent in the score achievable. On the iPhone version, the final challenge is to get a total score of 10 million, which is calculated using a combination of distance covered and coins collected, and is, often, the achievement which eludes.

Droidsters will be pleased to learn that Temple Run is now in the process of being ported through to Android, with developer Imangi Studios’ Keith Shepherd stating:

"We are excited to finally share the Android release date with our fans who have been so enthusiastic and supportive of Temple Run. By expanding to more mobile devices, we hope to provide the same addictive and fast-paced gameplay to an entirely new group of players."

Although the release is sure to please Android users, iOS users will also have a larger army of potential rivals in the battle to see who is the niftiest Temple Runner.

This release date appears to be set in stone more or less, with the co-founder of Imangi Studios letting loose the information complete with excited comments abound. This announcement is sure to thrill not only Android fans, but those iPad and iPhone fans that have been waiting to prove themselves against the whole mobile world, not just their Apple compatriots. As Keith Shepherd notes:

“We are excited to finally share the Android release date with our fans who have been so enthusiastic and supportive of Temple Run. By expanding to more mobile devices, we hope to provide the same addictive and fast-paced gameplay to an entirely new group of players.” – Shepherd

The original iOS version of this app has currently broken the 40 million downloads mark, this after its debut in August of 2011. This game is so popular we saw people playing it in Barcelona while we were there for Mobile World Congress – and Apple wasn’t even at the event. It’s time to expand!

Android Browser List

2012-03-21T09:49:00.000-07:00

Here's A List Of Android Browser's Available In Android Market

Installing Ubuntu on Viewsonic G-Tablet

2012-03-19T09:46:00.003-07:00

Ubuntu runs fairly nice on the GTab. Find a video below to see it boot. Performance is not as smooth as Android, but I've already narrowed down some kernel tweaks to speed it up.

What works:
USB Devices
Wifi
Video (not accelerated)
Internal/external storage

What doesn't work (yet):
Touchscreen
Softkeys
Volume/Power buttons
Accelerometer
Camera
Audio (pulseaudio hangs, haven't investigated)

To get it working, I used a custom kernel with added support for various drivers, but otherwise pretty much the stock VS kernel. It gets the rootfs from the micro SD card, so it only requires a boot.img flash (so it doesn't destroy any user data or the Android system partition).

Video for booting Ubuntu on G-Tab

Code:
cd /media/sdcard
tar -xzvf /home/user/Desktop/karmic-rootfs.tar.gz

Install the boot-karmic update zip via ClockworkMod Recovery. ***MAKE SURE YOU HAVE A BACKUP boot update.zip (or grab one from Clemsyn's Kernel Corner)***

Insert the sd card and boot. You will see some yellowish/gold colored text quickly scrolling across the screen - this is normal. This should boot straight to a GDM login screen.

User=gtab Password=gtab

Wireless will work with wicd (not NetworkManager), and you should use a USB hub with a USB keyboard & mouse.

Files:
Karmic rootfs tarball (1.1GB)

Karmic kernel update.zip

Rooting Spice Mi-350n / Fly IQ260(BlackBird)

2012-02-03T10:23:00.000-08:00

ROOTING YOUR SPICE Mi-350n(NOT *350*)/FLY IQ260(BLACKBIRD)

Here is the guide to root your Mi-350/IQ 260:

1.First enable USB Debugging.[Settings->Applications->Development]

2.Download Spice Mi-350n/Fly IQ 260 drivers(ADB driver included) from attachments and extract it on your Desktop.

3.Download SuperOneClick v2.3.1 with the the links given in a '.txt' file from attachments (since i'm unable to upload file >8.0MB and also add external links) and extract it to your desktop.

4.Now connect your phone to your pc with USB debugging mode enabled.

5.Windows will not be able to install drivers on its own. So, go to 'Device Manager'. Under 'Other Devices', you will have your phone's name, Spice Mi-350n/Fly IQ260.

6.Now right click and select 'Update Driver Software...' and select 'Browse my computer for driver software' and browse to the location where you extracted the drivers and click 'Next'.

7.Windows will install all the required drivers.

8.Now unplug your phone and re-plug it to your pc with USB Debugging mode enabled.

9.Now open, 'SuperOneClick.exe' (Run it as administrator).

8.Now under 'exploit' change 'Auto' to 'zergRush'.

9.Now click 'Root'.

10.Your phone will be rooted successfully !!

http://forum.xda-developers.com/showthread.php?t=1472026

Offline Maps for GPS USERS

2012-02-03T10:06:00.000-08:00

So, as I was going through the posts, I saw some users claiming that they cannot find any suitable GPS application with offline maps. So, I am here to post the details which might help many to solve this problem of their.
(Note: I'm not advertising but just helping people)

There are many application in the market which have feature for offline maps or cached maps like google map, rmap, oruxmaps, ublox, locus etc. (these are the maps that i have tested and used by me)

So, here is the guide.

Method 1.

First of all you need one of the above mentioned software installed on your Android phone (all the above apps are free of cost)

Next you need the offline maps and the guide is as follows:

Step 1. You need to download/create offline map and you will need to download Mobile Atlas Creator (also known as MOBAC and it is a free open source software) tool with SQLite library. Java Runtime Environment should be installed on your computer since this software is based on java. ( Google the software to download it )
Step 2. Run Mobile Atlas Creator and from the drop-down box in the left upper corner of the screen select map provider.
Step 3. Using the mouse select the area you want. You can zoom in and out using the scroll button.
Step 4. Choose zoom levels for you offline map. Please note that creating maps of a large area with high resolution will result creating data file several gigabytes in size.
Step 5. Enter a name of your map and click “Add selection” button.
Step 6. Select the desired format from “Atlas settings” drop-box.
Step 7. Press “Create atlas” button and the download of the maps will begin and be quite patient because it might take time depending upon your internet download speed.
Hurry you are half way done with the offline maps.
Step 8. Once completed, open the folder with your atlas file. Copy the file on your Android device to /sdcard/"your app folder"/maps folder.
Step 9. Open the android application and press Menu button and goto settings and select the user defined map i.e. the one you placed on your sdcard.

Method 2.

How to save Google maps for offline use on android and you can save your bucks

Enable the Google Maps Labs Map Pre-caching:

1. Open Google Maps android app.
2. Press Menu button->More->Labs->Precache map area and enable it.
3. Now when you search for a location, click on the map label that appears.
4. In the location view, press Menu.
5. Press Precache map area.

This can be used to view 10 miles around the selected area (offline).

Method 3.

There are many applications which help users download maps from mobile itself, either in setup wizard or in options. Following are the apps that support this features:

1. Mapdroyd
2. Map(-)
3. Google Map
4. Sygic
5. Copilot
6. Wave
7. Locus
8. Maverick
9. Oruxmap
10. MapmyIndia

Here you go. All is set and you are good to go. (Note: The first start up might take time but the consequence will not)

Samsung Galaxy S3 to be released February 5 2012

2012-02-03T09:49:00.001-08:00

With the beginning of the New Year, Samsung is once again working on its new project – Samsung Galaxy s3. Samsung galaxy s3 release date hasn’t been decided yet but is in anticipated that this phone would hit the market this February. Its showcase is set to be the Mobile World Conference of 2012 in Barcelona, Spain.

Till date the Samsung Galaxy S3 release date is finalized to be from Feb. 27th to March 1st 2012 but that is still just a rumor. This is the very same congress and date when last year the Samsung S2 was revealed. Like all other phones, nothing can be said for sure about anything regarding this phone, be it the features or the Samsung galaxy S3 release date.

Waiting for the next iPhone killer i.e Samsung Galaxy s3?. After the release of Samsung Galaxy S II people are anticipating the release of Samsung Galaxy S3. February 2012 is thought to be Samsung Galaxy S3 release date. The awe-inspiring Android smart phone Samsung Galaxy S 2 was released worldwide in May 2011, by more than 140 retailers in over 120 countries. Since that time, the smart phones have gotten tremendous success and have reached sky high demand rate.

Other rumors have it the Galaxy S3 will most probably be powered by Google’s latest OS – Android Ice Cream Sandwich. These buzz indicate that Samsung may divulge Galaxy S3 at a similar time to the iPhone 5. If that happens then the Samsung Galaxy s3 release date will be somewhere in mid-2012.

There will be a lot of competition if both the iPhone 5 and Samsung galaxy s3 release dates will clash. What will be the people’s choice, nothing can be determined yet. We will all have to wait till the release of both the phones.

Samsung’s upcoming Galaxy S3 smart phone which is also known as the “iPhone killer” is expected to include a quad-core processor. It is also claimed to be 5 times faster than its Mali-400 MP chip of its predecessor. Moreover, the Samsung Galaxy S3 is expected to have multitasking feature, which will allow the users to efficiently run multiple applications concurrently.

To enable easy multitasking process and playing games, it is anecdote that this next generation phone will come with 2GB RAM. It is likely to be the first smart phone to boast 2GB of RAM. Furthermore, it is predicted that this phone will come with a generous 32GB of storage. Well, nothing is based on true facts and figures. Whatever is stated is just based on rumors and nothing can be confirmed till the Samsung Galaxy S3 release date is finalized. Only then can true facts start buzzing the market.

Once the Samsung Galaxy s3 release date will be finalized only then can its price be finalized. However, be the Samsung Galaxy s3 release date be Feb. 2012 or mid 2012, the order of availability of the phone is expected to follow in countries with the following order – USA, Canada, Singapore, Europe, Ireland and New Zealand.

Best Video Players for Android

2012-02-02T09:45:00.000-08:00

Here is a non official list for the top video players for Android.

Act 1 Video Player is designed to play iPhone formats like 3gp, h263, and h264 baseline profile. It also claims to play some baseline MP4 files, but not all (it had no problem with mine). Other files will need converting, but thedeveloper page does point you in the direction of some free software that will do the job nicely. Act 1 is not only a tiny 500KB, but it can also be moved to your SD card.

Arc Media player can support a wide variety of video formats, including AVI, DIVX, MKV, MOV, MP4, RMVB, WMV, VOB and XVID. It’s still in beta, but is widely appreciated by testers so far.

Meridian is a huge 2.5MB, but can easily be moved to the SD card. It asks where your media is kept and quickly finds all of it. Gestures for navigating are intuitive and quick to use.

The mVideoPlayer app comes with rave reviews in the Android market. However, this app will only play whichever formats are already supported by your phone. Its 2.6MB install can be moved to the SD card, which is good news. The first search for video files will take a while, but it should load quicker in the future.

RealPlayer is an audio player as well as a video player. It has a handy interface to navigate between media types easily and can even display your photos. Sadly, it’s 3MB and can’t be moved to a SD card, so it’s only useful for users without space issues on their phone. It doesn’t say exactly which files it will play, but it couldn’t play my MP4′s. It played my home videos beautifully though.

RockPlayer is an ad-supported media player which at a massive 13MB fails to live up to the light impression. Thankfully, it can be moved to the SD card. Plays video smoothly and well.

VitalPlayer’s 5MB install can be automatically installed to your SD card. Sorry, VitalPlayer isn’t yet supported on Gingerbread.

VPlayer is my personal favourite simply because it’s so versatile and can be kept on the SD card, which is handy since it’s over 3MB. It plays all the major video formats, plus it can handle a variety of streaming video types. The free trial is fully featured, and the paid version is only a few dollars if you choose to upgrade.

Ultimate, portable gaming system. Sixaxis and DualShock 3 on Android

2012-02-02T08:52:00.000-08:00

Due to the non-standard protocol that the controllers use to communicate with the host, this application requires root access. Additionally, it is incompatible with most HTC devices and some newer Samsung devices. This is due to the required bluetooth protocol not being implemented on these devices. We are actively looking into a work around, but currently the only solution is to install a custom firmware, such as Cyanogenmod, that supports the required protocols.

Sixaxis Controller is an Android application which allows the Sixaxis and DualShock 3 Playstation controllers to be used as bluetooth input devices on many mobile phones and tablets. This enables the ultimate gaming experience to be had in a completely portable form factor.

Up to four controllers are supported at once, and key mappings are completely configurable, as well as the analog sticks, which are currently emulated as digital key presses.

It is strongly recommended that you first test your Android device using the 'Sixaxis Compatibility Checker' app, available for free from the Market, before purchasing the 'Sixaxis Controller' app. If your device is compatible, you will be able to see your button presses show up once you have correctly configured the controllers.

To allow controllers to be used with your device, you must download and install the SixaxisPairTool from here. This will allow you to pair the controller with your device.

Watch the video, to see how it is done..

Webiste : http://www.dancingpixelstudios.com/

Instructions

Download and install the application from the Android Market. It is highly recommended that you first download the 'Sixaxis Compatibility Checker' app to make sure your phone is compatible before purchasing the full application.
Tap the 'start' button and wait for bluetooth to initiate. If you get an 'Error: Missing required protocol' message, your device is not supported.
If not already done, you must manually pair the controller with your phone. This can be done using 'SixaxisPairTool', or with 'MotionInJoy' or the linux utility 'sixpair'. Your phones bluetooth address should be shown at the bottom of the main application window and will look something like 1A:3C:13:00:21:C2; you need to enter this number into the 'SixaxisPairTool' as shown. This process only needs to be done the first time a controller is used on a different device, so if you only use the controller on one phone, you will only need to do it once.
Once paired, unplug the USB cable and press the power button on the controller. If successful, the lights on the controller will stop blinking and a single light will remain on.
If you are running the compatibility checker, and pressing buttons on the controller results in button presses showing up in the app, congratulations, you can now download the full app.
Tap the 'Change Input Method' button and select 'Sixaxis Controller'. You should now be able to use the controller in any games or applications that support key bindings, such as many emulators.
Subsequent controllers can be added at any time by pressing their power buttons.
You can change the fallback input method and key mappings in the applications settings.

Remove pre-installed apps android FOR NAND LOCK PHONE

2012-02-02T08:46:00.000-08:00

Go to the market and install SuperUser, Titanium Backup, BusyBox.

Open Titanium Backup allowing it root access when prompted, go to Backup/Restore and scroll to find one of the preinstalled bloatware apps, I chose the Music app and the Web app.

Long hold on the app you want to remove and scroll down a bit and choose the option "Force remove app (by recovery exploit)"

This will reboot your phone TWICE, you will get the recovery screen up - LET IT RUN IT's COURSE! DO NOT INTERRUPT THIS.

Once it boots back into your normal check that the app is no longer in your App drawer

Repeat for all the Apps that came preinstalled that you don't want, just be careful you don't remove anything that may still be needed!

Link2SD works only on Froyo

2012-02-02T08:30:00.000-08:00

Features:

Creates and removes link for apk, dex and lib files of the applications you select

Lists applications, shows their link status

Sorts and filters applications

Displays available space information of internal storage, SD card and SD card 2nd partition.

What you need:

root permission.

a second partition on your SD card. You should have two partitions on SD card and both should be primary.

The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4 or FAT32.

ext4 is the latest ext format but several ROMs have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.

I use free "MiniTool Partition Wizard Home Edition" (windows application) for this.

You can create the second partition without repartitioning, formatting or deleting your existing partition with this tool. Connect your SD card to PC with a card reader or phone itself and make it visible as a drive. Open Minitool select this drive and resize down FAT partition, you will see an unallocated area at the end of the card. Create ext2, ext3 or FAT32 partition in that area (create as primary, not logical), click apply. Unplug from the PC and reboot the phone. (To be on the safe side backup your data before starting)

That's all. Just install Link2SD, it will do all necessary. No need to copy files or run scripts.*

* Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need a matching ext2.ko or ext3.ko modules and even some additional modules to be able to mount.

Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones.

How it works:

Link2SD mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.

When you select an application and press "Create Link" button you can select which files of the application will be linked and moved to SD card. Apk, dex and lib files can be moved and you can select all three or any two of three or even only one of them.

Then, according to your selection, Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's second partition and creates symbolic links in original directories.

Note: On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if you move the apk file.

Can I remove the links and put application files back to phone?

Yes, just click on application that is linked and press "Remove Link" button. You can select which files of the application will be unlinked and moved back to internal storage.

Then, Link2SD removes the symbolic links and moves the files you selected to original directories.

What happens if I uninstall a linked application?

If you uninstall a linked application apk, dex and lib files will be automatically deleted from the SD card by Link2SD.

What happens if I update a linked application?

If you update a linked application new apk, dex and lib files will be placed in the internal memory at first and then they will be t works:automatically relinked by Link2SD in the background.

You don't have to manually relink after updating applications.

Note: Since the app is linked again, On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if the apk file is linked.

Some points

Link2SD detects applications which are already moved to SD card on Android 2.2+ natively and disables "create link" for them.

System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.

When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted. Therefore linked applications are not affected and can be run without problems.

Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files.

How to Partition SD Card for Link2SD using Minitool Partition Wizard Home Edition

This tool is compatible with Windows 2000/XP/Vista & Windows 7

requirements: USB SD Card reader.

pull SD card from phone, insert into USB SD Card reader. Windows should report new drive and content of the drive should be visible.

step 1: delete old partitions on SD card

Note: this partition manager QUEUES the operations. So nothing is deleted and changed UNTIL you click "APPLY" and then confirm by clicking "OK".

WARNING!

Make sure you are deleting partition on SD card! (not your hard drive for example)

This step deletes everything on SD card, so backup files first!

Dont be afraid, just read everything and think twice before selecting correct drive.

Do you see three gray icons on the bottom? Under each of them the capacity of each drive is listed, and SD CARD has slightly different icon.

Hard drives on the screenshot have 465.8GB and 74.5GB, and on the bottom, the SD card, with 3.8GB capacity.

step 2: create FAT or FAT32 partition
select "Create As": PRIMARY
Select "File System:" FAT when you have 2GB or smaller card.
Select "File System:" FAT32 when you have 4GB or greater card.

step 3: create ext2 or ext3 or swap partition*

select "Create As": PRIMARY

Select "File System:" ext2 - for App2SD

If you want to create both: do not assign all the space for the first one this way you will have space for creating second one.

step 4: finish
finally, click "apply" button on top left corner.
partitions will be created and card will be formatted.

How to Apply Link2SD:

1. install Link2SD
2. run Link2sd and select Ext2
3. Phone Reboot
4. After booting the phone run Link2SD
- move all apps to phone that are saved in SD
- refresh the list
- click the apps then create link (dalvik should also remain checked)
- Reboot
- All files on SD Card will be removed in partitioning process.
- Check your internal memory storage capacity

DISCLAIMER: It is made available for use at your own risk with no warranty of any kind.

Minitool Partition Wizard
http://www.partitionwizard.com/free-partition-manager.html