May | 2015 | My Technical Blog

Archive for May, 2015

28 May

Installing CyanogenMod KitKat 4.4.2 for my Galaxy Ace GT-S5830

Posted by Peter Teoh in Android. Leave a comment

Update Galaxy Ace GT-S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM [How to Install]: proven working ROM for my Galaxy ACE

http://www.ibtimes.co.uk/update-galaxy-ace-gt-s5830-android-4-4-2-kitkat-cyanogenmod-11-rom-how-install-1430916

My procedure (different from above, assuming you are running on Linux as hosts, Android SDK installed, and “adb” is in your $PATH environment variables, otherwise just enter the full path for “adb”):

a. Download the “cm-11-20131229-UNOFFICIAL-cooper++XR.zip” file from above:

md5sum:

2845c7099dc4d4c7645d32d420d0f8af cm-11-20131229-UNOFFICIAL-cooper++XR.zip

b. Connect Samsung Galaxy Ace to computer via USB, and use adb to put it into recovery mode: adb reboot recovery

c. In the menu on the phone, choose “update zip” option, and then navigate to sideload.

d. In the computer, issue “adb sideload <FULL_PATH_of_cm-11-20131229-UNOFFICIAL-cooper++XR.zip>”, and you should see percentage by percentage the CM file is being uploaded into phone.

e. After it has been uploaded and updated, choose “reboot” on the phone.

f. After it has rebooted into the new image, now go to settings, and then “about phone” and tap on the “Build Number” 7 times: developer option is enabled, and ensure adb debugging via the different option is enable (default it is NOT), and you can also choose to have “root” enable as well (SuperUser–>Allow).

Viola….a fully rooted CynogenMod KitKat 4.4.2 for Galaxy Ace!

http://www.droidthunder.com/update-samsung-galaxy-ace-gt-s5830-official-android-2-3-6-gingerbread-xwktq-firmware/

http://www.droidthunder.com/install-android-5-0-lollipop-rom-on-galaxy-ace-gt-s5830/

The above page has two download link. The rule (for me) is NEVER download or run any download with “exe” as the extension. The other download is “zip” as the extension, and using “unzip” in my Linux terminal, I can see (via unzip -l ) all the contents inside – and it clearly has all the usual contents of an Android ROM image.

http://androidxda.com/samsung-galaxy-ace-s5830-stock-rom

http://alchemistar.blogspot.sg/2012/03/samsung-galaxy-ave-s5830-rom-list.html

The advantage of the above procedure using “adb” is that different phone has different key combination of putting it in recovery mode. And from recovery mode, you have to navigate to the SD card that contained that ROM (which is the zipped file). Not always, eg, in Xiaomi Mi Tablet, you have to put it in the root directory of the internal storage, not SD card. All these procedures is rather cumbersome. The method described above just need one USB cable to connect to the host Linux computer, where you downloaded all the ROM file, and you issued the “adb reboot recovery” command to put it in recovery mode, and then the “adb sideload” command to load the ROM image into the phone/tablet: one-stop location to do everything. What is the catch? Sideloading is a feature only available in CWM recovery, so you will have to flash that using the non-sideloading means first.

23 May

What is happening in Ubuntu?

Posted by Peter Teoh in desktop, ubuntu. Leave a comment

Just look at the following spawned processes:


     \_ init --user
         \_ dbus-daemon --fork --session --address=unix:abstract=/tmp/dbus-QUZeqof8X5
         \_ upstart-event-bridge
         \_ /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge
         \_ /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
         \_ upstart-dbus-bridge --daemon --session --user --bus-name session
         \_ upstart-file-bridge --daemon --user
         \_ upstart-dbus-bridge --daemon --system --user --bus-name system
         \_ /usr/lib/at-spi2-core/at-spi-bus-launcher
         |   \_ /bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
         \_ /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
         \_ /usr/lib/gvfs/gvfsd
         \_ /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
         \_ /usr/bin/ibus-daemon --daemonize --xim
         |   \_ /usr/lib/ibus/ibus-dconf
         |   \_ /usr/lib/ibus/ibus-ui-gtk3
         |   \_ /usr/lib/ibus/ibus-engine-simple
         \_ /usr/lib/unity-settings-daemon/unity-settings-daemon
         \_ /usr/lib/ibus/ibus-x11 --kill-daemon
         \_ /usr/lib/x86_64-linux-gnu/hud/hud-service
         \_ gnome-session --session=ubuntu
         |   \_ compiz
         |   \_ /usr/lib/unity-settings-daemon/unity-fallback-mount-helper
         |   \_ nautilus -n
         |   \_ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
         |   \_ nm-applet
         |   \_ /opt/google/chrome/chrome --type=service
         |   \_ telepathy-indicator
         |   \_ zeitgeist-datahub
         |   \_ update-notifier
         \_ /usr/lib/unity/unity-panel-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk
         \_ /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service
         \_ /usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service
         \_ /usr/lib/evolution/evolution-source-registry
         \_ /usr/lib/x86_64-linux-gnu/notify-osd
         \_ /usr/lib/evolution/evolution-calendar-factory
         \_ /usr/lib/dconf/dconf-service
         \_ /usr/lib/gvfs/gvfs-udisks2-volume-monitor
         \_ /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
         \_ /usr/lib/gvfs/gvfs-mtp-volume-monitor
         \_ /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
         \_ /usr/lib/gvfs/gvfs-afc-volume-monitor
         \_ /usr/lib/gvfs/gvfsd-trash --spawner :1.9 /org/gtk/gvfs/exec_spaw/0
         \_ /usr/lib/gvfs/gvfsd-burn --spawner :1.9 /org/gtk/gvfs/exec_spaw/1
         \_ /usr/lib/gvfs/gvfsd-metadata
         \_ /usr/lib/telepathy/mission-control-5
         \_ /usr/bin/zeitgeist-daemon
         \_ /usr/lib/x86_64-linux-gnu/zeitgeist-fts
         |   \_ /bin/cat
         \_ gnome-terminal
             \_ gnome-pty-helper
             \_ bash
                 \_ ps auxwf

These processes are created simply just by logging in passed the Gnome session authentication prompt. No applications other than the gnome-terminal is started yet.

Yet, applications like Chrome can already start by itself.

Frankly this is getting really bloated, and sounds more like trojans than ever.