Install Ubuntu with Windows UEFI dual boot

I tried to install Ubuntu with my existed Windows 7 today, and have the Ubuntu / Windows dual OS boot up. The most guides on web are out of date, special for currently most PC use UEFI as default boot configuration, there are a lot of mistakes. So I take a as-is notes for today: 2017-09-24

To install Ubuntu without wipe existed Windows with UEFI:
1. Prepare ubuntu install USB stick and empty disk space in Windows.  You can search on web about this step, a lot of guides.
2. Boot up with the ubuntu install USB stick. IMPORTANT:  DO NOT select "install ubuntu" in boot menu!! Select "Try ubuntu" to boot into live ubuntu (it runs on your USB stick, does not install any things) firstly, then select "Install Ubuntu" --- These two "Install Ubuntu" are different because you need boot up into ubuntu for detecting UEFI mode.
3. Select "Install ubuntu" -> "Something else", create the first partition , for 300MB size, of your empty space as a "EFI partiton"!!! You MUST have this partition.
4. Then create /boot after that EFI partition. And create /, /home, /swap as your wish.
5. Select "Install boot at" option to the EFI partition you just created!!!
6. Then continue the install process as normal.

The key point is to boot into ubuntu then do the installation, and the EFI partition. Another thing must aware is, DO NOT use "hybird display card" option in BIOS, otherwise ubuntu will show an empty desktop because pci issue.
 

Thrift fails on Windows - thrift failed error: The command line is too long.

Meet a thrift compiling failure on my project on Windows 7. Using Maven in IntelliJ so I choiced maven-thrift-pluging for thrift files. For one project, the thrift failed as below:

[INFO] — maven-thrift-plugin:0.1.11:compile (thrift-sources) @ xxxxxxxxxxxxxxx —
[ERROR] thrift failed output: 
[ERROR] thrift failed error: The command line is too long.

Executed the thrift --gen manually did not meet this issue, so most likely caused by how maven-thrift-plugin call the compiler. Finally I had a workaround to decrease the thrift temp file folder path to pass the build:

Below configuration changed the folder name from default "thrift-dependencies" to "td", lucky my project pass build, otherwise I think I have to move my project to a up-level folder to get a shorter path.

<plugin>    <groupId>org.apache.thrift.tools</groupId>    <artifactId>maven-thrift-plugin</artifactId>    <configuration>        <thriftExecutable>${thrift.compiler}</thriftExecutable>        <generator>${thrift.generator}</generator>        <temporaryThriftFileDirectory>${project.build.directory}/td</temporaryThriftFileDirectory>    </configuration></plugin>

Gradle Failed for Google Guava: transformClassesWithDexForDebug TransformException

Meet the compile issue when adding Google Guava into my Android project:

dependencies {
  compile 'com.google.guava:guava:21.0'
}

Error:

10:16:43.803 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > com.android.build.api.transform.TransformException: com.android.ide.common.pro
cess.ProcessException: Error while executing java process with main class com.android.multidex.ClassReferenceListBuilder with arguments {xxxxxxxxxxx\build\intermediates\multi-dex\debug\componentClasses.jar xxxxxxxxx\build\intermediates\transforms\jarMerging\de
bug\jars\1\1f\combined.jar}

After downgrade guava to version 19 the project passed build successfully:

dependencies {
  compile 'com.google.guava:guava:19.0'
}

Have no time to dig into the root cause yet, record here for reference.

How to build React-Native behind proxy

Recently I tried to setup and build react-native app (mostly for Android), behind a proxy server. To pass the gradle build, need set proxy config as below:

• Edit AwesomeProject\Android\gradle.properties, add proxy config:
•     systemProp.http.proxyHost=10.255.247.227
•     systemProp.http.proxyPort=8080
•     systemProp.https.proxyHost=10.255.247.227
    systemProp.https.proxyPort=8080

error: undefined reference to '__android_log_print' in Android Studio 2.1

Need load the android log lib in app/build.gradle:

    android.ndk {
        moduleName = "[the_module_name]"
        ldLibs.addAll(['android', 'log'])
    }

Make TextView scrollable without using ScrollView

2 steps, firstly, set scroll bar rotation in AndroidManifest.xml:
         android:scrollbars="vertical"

Then, set the scrolling method for the TextView, mostly in onCreate() function:
        ((TextView)findViewById(R.id.textview)).setMovementMethod(ScrollingMovementMethod.getInstance());

Parent Activity is destroyed when providing Up navigation

If providing Up navigation behavior as Android doc: http://developer.android.com/training/implementing-navigation/ancestral.html, when click the Up button on the navigation bar, the parent activity is destroyed then re-created. It is different behavior as pressing back key.

To avoid destroy parent activity, one solution is setting launch mode <singleTop> for the activity in AndroidManifest.xml:

android:launchMode="singleTop"

The different between Up key and Back key is, when pressing Back key, by default, the currently activity is popup from activity stack and finished, so the previously activity shows up. When pressing Up key, the currently activity is popup from stack too, but the parent activity, which is defined in AndroidManifest.xml and maybe not the previously activity, is created to show. By default the launch mode is <standard> so the existed activity task is destroyed then re-create. To set the launch mode to <singleTop>, Android will launch the existed one instead of create a new task.