Wednesday, June 20, 2018

Handbrake: downgrade 0.98GB Video to 9.89MB Video

Handbrake version: 1.1 (https://handbrake.fr)
Original:
  • Resolution 1920x1080
  • Audio Bit rate 317kbps Stereo
  • file size 0.98GB
Result:
  • Resolution 240x128
  • Audio Bit rate 32kbps mono
  • file size 9.89MB
The steps are:
  1. Open original video file 
  2. In "Presets" choose "Devices" -> "Apple240p30"
  3. In tab Summary change:
    1. Web Optimized -> checked
    2. Align A/V Start
  4. In tab Dimensions change:
    1. Dimension: 240x128
    2. Keep Aspect Ratio: checked
  5. In tab Video change:
    1. Video codec H.264
    2. Framerate: 20
    3. Constant Quality: 18
  6. In tab Audio change:
    1. Bitrate: 64 
    2. Mixdown: Mono
  7. And last one fill output file name in "Set Save As:"
  8. Then click "Start Encode", wait until it finish. It may take some  times.

Thursday, May 31, 2018

Android Studio 3.1.3: fix warning compile, androidTestCompile and testCompile

Fix Warning:
  1. Configuration 'compile' is obsolete and has been replaced with 'implementation'
  2. Configuration 'androidTestCompile' is obsolete and has been replaced with 'androidTestImplementation'
  3. Configuration 'testCompile' is obsolete and has been replaced with 'testImplementation'
My Android studio:
  • Android Studio 3.1.3
  • buildToolsVersion "28.0.0"
  • Compile Target SDK 28 / min SDK 17
Open Project -> Gradle Scripts -> build-gradle (Module: app)
  1. Change 'compile' to 'implementation'
  2. Change 'androidTestCompile' to 'androidTestImplementation'
  3. Change 'testCompile' to 'testImplementation'
For exmaple my previous
android {
    compileSdkVersion 27
    buildToolsVersion "27.0.3"
    defaultConfig {
        minSdkVersion 17
        targetSdkVersion 27
...
dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
        exclude group: 'com.android.support', module: 'support-annotations'
    })
    compile 'com.android.support:appcompat-v7:26.+'
    compile 'com.android.support.constraint:constraint-layout:1.0.2'
    testCompile 'junit:junit:4.12'
    compile 'org.jsoup:jsoup:+'
    compile 'com.google.android.gms:play-services-ads:11.2.2'

}
After update
android {
    compileSdkVersion 28
    buildToolsVersion "28.0.0"
    defaultConfig {
        minSdkVersion 17
        targetSdkVersion 28
...
dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
    implementation 'com.android.support:appcompat-v7:27.+'
    implementation 'com.android.support.constraint:constraint-layout:1.1.2'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    implementation 'com.google.android.gms:play-services-ads:15.0.1'

Saturday, May 26, 2018

Move/Restore Joomla site to a new server using Kickstart 5.4.2

Tested on Joomla 3.8.3 and Kickstart 5.4.2.
Note: you don't need to install Joomla first, Kickstart will extract your Joomla.
Required:
  1. previous back up using Akeeba Backup for Joomla (jpa or zip file)
  2. MySQL user and password
  3. Read/write permission on web root
Here are the steps:
  1. Download Akeeba Kickstart from https://www.akeebabackup.com/products/akeeba-kickstart.html. Kickstart contains kickstart.php and its supporting files.
  2. Upload and extract Kickstart to your previoes Joomla root for example upload and extract kickstart-core-5.4.2.zip into [your_home]/public_html/joomla.
  3. Upload your backup files to your web root for example upload site-garasiku.web.id-20180104-031734utc.jpa into [your_home]/public_html/joomla. It may take time, depends on your connection speed.
  4. From your browser open URL http://[your_site]/joomla/kickstart.php and click "Click here or press ESC to close this message".
  5. Fill form
    1. Archive file: [your jpa/jps files] e.q. site-garasiku.web.id-20180104-031734utc.jpa
    2. Temporary directory: [your_ftp_temp_folder] e.q. [your_home]/public_html/tmp
  6. Click "Start" to start extracting your Joomla site backup and click "Run Installer" to reinstall and configure your Joomla site.
  7. It will open ANGIE – Akeeba Next Generation Installer Engine v.5.6.3 in a new tab. Click "Next".
  8. Fill your MySQL access
    1. Database server host name: localhost [Note: check your hosting provider]
    2. User name:    [your MySQL user]
    3. Password:    [your MySQL user password]
    4.  Database Name:    [your MySQL database name]
  9. To continue click "Next", It will give a warning, you may click "Ok" or "Cancel".
  10. If Success, click "Next Step".
  11. It will restore your configuration files. Update your preferences if you wish, and fill your Joomla administrator password.
  12. Click "Next" to finish configuration. It will ask your to clean up your Kickstart. It will clean
    1. Kickstart files
    2. folder Installation
  13. Done and conguratulation!  
Additional Option to change Akeeba backup folder
  1. Create folder for example akeebabackup on your home directory for example [your_home]/akeebabackup.
  2. Open your Joomla Administrator page and update Joomla system if necessary.
  3. "Components -> Akeeba Backup" in "Basic Operation" select "Configuration".
  4. Change Output Directory into your akeebabackup folder for example /home/example/akeebabackup
  5. To change non default backup schema, under "Components -> Akeeba Backup" in "Basic Operation" select "Profiles Management"

Reference:
https://www.akeebabackup.com/videos/1212-akeeba-backup-core/1618-abtc04-restore-site-new-server.html

Connecting domain to web hosting from 2 different provider

I have domain registar in at Indosatm2. After my sponsor refuse to fix the server, I decided to hosting my web on web hosting. After searching web hosting, I choose masterweb for web hosting.
The problem arrise how to connect my domain to web hosting. After searching some information, here is how I do that.
  1. At web hosting, find out name server for your web hosting. If you can not find them, issue ticket to ask name server for your web hosting.
  2. Login into your domain registar.
  3. Go to Manage your domain for example garasiku.web.id.
  4. Select "Name Server" and use "Use custom nameservers (enter below)"
  5. You need at least 2 name server.
    1. Nameserver 1: [Nameserver_from_web_hosting]
    2. Nameserver 2: [Nameserver_from_web_hosting]
    3. Nameserver 3...etc: [optional]
  6. Make sure "Registar Lock" is disable to make it easy to transfer from domain registar provideer to web hosting provider.
  7. Go to "DNS Management" and fill Hostname, Record type "A" and IPv4 address. For eample
    1. Host Name: garasiku.web.id
    2. Record Type: A
    3. Address: [xx.xx.xx.xx]
  8. It takes time to propagate your domain about 24 hours. In my case it took about 6-8 hours. You may check using nslookup your domain points to your web hosting.
  9. Done.

Monday, April 23, 2018

Mengganti kartu Sim Indosat lama dengan Kartu SIM Nano Indosat/Ooredoo 4G/LTE

Pastikan nomor SIM-nya terdaftar sesuai data diri di-KTP anda.

Untuk mengeceknya, gunakan URL https://myim3.indosatooredoo.com/registration/index.

Bila anda memerlukan penyesuaian data diri, lakukan dengan mengirimkan SMS ke-4444 dengan format:
ULANG#[no_ktp]#[no_kk]#
tanpa tanda [], contoh ULANG#1234567890123456#1234567890123456#.
Anda akan menerima SMS jawaban "Terima kasih nomor Anda telah BERHASIL diregistrasi ulang". Catatan: hanya berlaku untuk eKTP.

Selanjutnya, siapkan copy KTP dan KK untuk melakukan penggantian Kartu SIM Indosat lama dengan Kartu SIM Nano Indosat/Ooredoo 4G/LTE di-Gerai Indosat/Ooredoo terdekat. Jam operasional gerai 8:00 s/d 20:00, Senin s/d Sabtu.

Petugas akan melakukan validasi data diri anda dan memberikan Kartu SIM Nano Indosat/Ooredoo 4G/LTE. Petugas akan menyampaikan bahwa kartu SIM baru anda baru bisa digunakan 1 jam kemudian dan menginstruksikan agar kartu lama dimatikan/tidak digunakan.

Setelah 2 jam (disuruhnya sih 1 jam), viola, Kartu SIM Nano Indosat/Ooredoo 4G/LTE sudah bisa digunakan tanpa kendala.

Anda juga akan merima pesan SMS "Kartu SIM Anda berhasil diganti, Terima kasih!" dan "Pelanggan Setia Indosat Ooreddo, permintaan layanan Penggantian Kartu Pascabayar Anda 62816xxxxx telah diproses, Selamat menggunakan layanan dari Indosat Ooredoo. Terima kasih.".

Saturday, April 7, 2018

Android adb: analyzing Android

Adb for analyzing Android 

Personal note

in linux

adb logcat -d -b events | grep boot

in windows 

adb logcat -d -b events | findstr /L "boot" or
adb logcat -d -b events | findstr /R "boot"

in linux

adb logcat -d | grep preload

in windows 

adb logcat -d -b events | findstr /L "preload" or
adb logcat -d -b events | findstr /R "preload"

To get android property
adb shell getprop

Friday, March 23, 2018

List AMD Processor does not need AMD Catalyst in Windows 10 x64 and x32

List AMD Processor does not need AMD Catalyst in Windows 10 x64 and x32:

  • AMD A8-7410
  • AMD A8-4500M
  • AMD A6-6310
  • AMD A4-4020

From original  (as a copy in case the reference deleted):

This document provides information about Windows® 10 driver support for APUs with AMD Radeon™ Graphics.

For the purpose of this document the term “APU Graphics” refers to the On-die graphics adapter on an AMD APU that is the designated primary graphics controller on a system.

This document does not apply to Discrete AMD Radeon™ Graphics products. For more information about Windows 10 driver support for Discrete AMD Radeon™ Graphics products, please visit: Windows® 10 Driver Support for Discrete AMD Radeon™ Graphics Products

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 2.0 and DirectX® 12 on Windows® 10:
  • AMD A6/A8/A10/FX-8000 Series APUs
  • AMD A4 Pro/A6 Pro/A8 Pro/A10 Pro/A12 Pro-8000 Series APUs
  • AMD E1/E2/A4/A6/A8/A10/FX-7000 Series APUs (except A4-7300 APUs)
  • AMD A4 Pro/A6 Pro/A8 Pro/A10 Pro-7000 Series APUs
  • AMD E1/E2/A4/A6-6#10 Series APUs
  • AMD E1/A4/A10 Micro-6000 Series APUs
  • AMD A4-5000, A4-5100 and A6-5200 APUs
  • AMD Athlon 5000 series APUs
  • AMD Sempron 2650 and 3850 APUs
  • AMD E1-2000 Series and E2-3000 Series APUs
  • AMD A4/A6-1000 Series APUs

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 1.3 and DirectX® 11 on Windows® 10
  • AMD A4-7300 APUs
  • AMD A4/A6/A8/A10-6000 Series APUs
  • AMD A4/A6/A8/A10-5000 Series APUs (except A4-5000, A4-5100, and A6-5200)
  • AMD A4/A6/A8/A10-4000 Series APUs

NOTE: If your graphics product is included on the list of supported products above, please install the latest AMD Catalyst™ Driver for Windows® 10 to fully enable its feature set. AMD Catalyst™ Driver can be downloaded from: http://www.amd.com/drivers

The following AMD APU products with AMD Radeon™ Graphics support up to WDDM 1.2 and DirectX® 11 on Windows 10:
  • AMD A4/A6/A8-3000 Series APUs
  • AMD E2-2000 APU
  • AMD E1/E2-1000 Series APUs
  • AMD E-200/300/400 Series APUs
  • AMD C-Series APUs
  • AMD Z-Series APUs

NOTE: These APU products must be installed only using the display driver version available via Windows Update. If you have upgraded to Windows® 10, please DO NOT install the AMD Catalyst™ Driver. Instead, enable Windows Update and allow it to detect and install the appropriate driver.

If you have already upgraded to Windows® 10 and installed the AMD Catalyst™ Driver, please follow the steps listed below to resolve this issu
  1. Uninstall the AMD Catalyst™ Driver using the Program and Features option in the Control Pane
  2. Reboot the system
  3. Use Windows Update to install the appropriate graphics driver for the APU.

References: