Monday, February 13, 2012

Set Chrome incognito mode as default in ubuntu Unity



    In Ubuntu 11.10, if you alike me so addicted to Chrome incognito mode, 
    below is the steps how to make it as default under ubuntu Unity 3D:

    1. Modify the file /usr/share/applications/google-chrome.desktop
    e.g. sudo nano google-chrome.desktop

    2. Update the first Exec option as below:
    e.g. Exec=/opt/google/chrome/google-chrome --incognito %U

    3. Save the changes.


    If you would like to set it up in GUI, you can follow the steps in below link:

    http://shuffleos.com/3572/how-to-run-firefox-chrome-in-privacy-mode-automatically-in-ubuntu-11-10/

Thursday, February 9, 2012

Problems and Fixes during cm9 alpha 0.6 touchpad installation



Getting a used touchpad from Amazon and I so want to install ICS for a while since so many praises are there for cm7 and cm9. Last night, I did install cm9 alpha 0.6 on my touchpad and I hit on 4 problems. After a week, I hit on the touchscreen malfunction problem.
  1. ClockWorkMod not shown on Moboot menu
  2. Gapps didn't install
  3. Wifi doesn't work
  4. cm9 can not boot properly because of applying the charging fix to cm9 alpha 0.6
  5. touchscreen malfunction in the lock screen


Here is the details:
1. ClockWorkMod not shown on Moboot menu
The cause is the ClockWorkMod zip file I downloaded is a zero byte file.
So, I redownload it and using the acmeinstaller2 to reinstall it.


For those of you alike me as newbie, here are the steps:-
a. Download it from rootzwiki links there.
b. Transfer the file ACMEInstaller2 thru USB drive in WebOs touchpad boot up
c. Run the command: novacom.exe boot mem:// < ACMEInstaller2 in C:\Program files\Palm, Inc directory. (I'm using PC).


2. Gapps didn't install
Though Gapps zip file was copying to the cminstall directory, it did not install.
The cause is obvious. It requires ClockWorkMod to be functioning before it can be installed.


So, basically, I followed the same steps listed in liliputing website to install charging fix to
install the Gapps. Dada.... the Google Market is up!!!! Here is the details steps.


  1. Place the zip file in the cminstall directory of your TouchPad’s 
  2. Press-and-hold the power button to reboot the touchPad.
  3. From the Moboot menu, choose ClockworkMod.
  4. Use the volume keys to scroll down to the entry that says “install a zip from SDcard” and tap the home button to select.
  5. Using the volume and home keys, highlight the Gapps file and select it.
  6. Scroll down to select yes.
  7. When it’s done installing reboot into CyanogenMod.


3. Wifi doesn't work.
Googling it, it is a known problem most ppl would encounter. There are three ways to fix it.
a. Boot up WebOs on touchpad and turn off and on the Wifi.
b. Remove all files under the wifi directory (/data/misc/wifi )
c. Use fxr wifi fix and rescue


Somehow method a) doesn't work for me. I never tried c) . So, I try method b. Below is the details steps.
1. Run the Terminal app from cm9 touchpad (assume your cm9 is running well now)
2. Run su and confirmed to use su from dialog box
3. Change directory to /data/misc/wifi (i.e. cd /data/misc/wifi)
4. Run the command to delete all file inside the /data/misc/wifi
                 rm -R *
5. Reboot your touchpad
6. Connect to the WIFI with password
Notes: After playing around the whole day. I got reconnect problem too. The wifi is on, but when I connect it. It failed to connect and get IP address. I found pressing the "SCAN" button will resolve the reconnect problem. It works for me once. See if it can resolve the problem next time. 


Update on 2-15-2012 :  FXR Wifi Fix and Rescue works like a charm. I played around the cm9 touchpad for a week. On and off, the wifi will be malfunction again like after the first installation. So, I tried c) method. It works like a charm.


4. cm9 can not boot properly because of applying the charging fix to cm9 alpha 0.6
This one is the most stupid one. As the author in liliputing is already mentioned
that don't install the charging fix if you have cm9 alpha 0.5 or later installed. But I overread it. and install it right away. What a mess to me!!!!


I got the error message "unfortunately, the process com.android.phone has stopped ..." prompting to me continuously while booting up cm9 and this error required me to press ok to close it. After the dialog closed, the error will show it again in less than a seconds. So, this prevents me to do anything even the simple task on the touchhpad to unlock or reboot the touchpad.


Struggling it a while, I manage to fix by reboot your touchpad to moboot menu to use clockworkmod to install the touchpad alpha 6.


The procedure is exactly the same in liliputing for those ppl already installed the cm9 alpha 0.5 and wanting to upgrade it to cm9 alpha 0.6.


Details steps are:
  1. Copy cm9 alpha 0.6 zip file update-cm-9.0.0-RC0-Touchpad-alpha0.6-fullofbugs.zip  and to the cminstall folder on your TouchPad.
  2. Connect your TouchPad to your PC.
  3. Reboot the TouchPad, pressing the volume-up button until the USB icon appears.
  4. Run ACMEInstaller2:  novacom.exe boot mem:// < ACMEInstaller2 in C:\Program files\Palm, Inc directory.
This problem is tough. I almost gave up since I ran out of ideas to reboot the cm9. At the end, YAY, my cm9 touchpad is revived!!!!!


5. touchscreen malfunction in the lock screen (Update on 2-15-2012)
It can be resolve by force reboot: i.e. press and hold the power and home button for 30 seconds. 


Sources:
1. Liliputing cm9 installation instructions:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
2. Links to download all the files you needed:
http://rootzwiki.com/topic/15509-releasealpha06-cyanogenmod-9-touchpad/
3. wifi solution c: Forum suggest fxr wifi fix and rescue can fix the wifi issue
http://forum.cyanogenmod.com/topic/41320-cm9-wifi-trouble-tp-sometimes-do-not-really-scans-for-wifi/
4. Wifi solution b: to remove every files from /data/misc/wifi directory (need su priviledge)
http://forum.cyanogenmod.com/topic/41320-cm9-wifi-trouble-tp-sometimes-do-not-really-scans-for-wifi/