KorhalNexus7

h1. Building

<br />mkdir <sub>/korhal # or wherever you want your checkout<br />cd</sub>/korhal<br />repo init -u git

gitorious.org:korhal/manifest.git
repo sync
source build/envsetup.sh

For each of the tgz's here, extract and execute the binary inside the source tree (<sub>/korhal if using the above instructions):
<br />https://developers.google.com/android/nexus/drivers#grouperjzo54k
<br />The hardware name for the Nexus 7 is &quot;grouper&amp;quot;, thus we initialize lunch with that.
<br />

lunch full_grouper-eng
make j8

<br />h1. Preparing device
<br />This will wipe your Nexus 7 device, make sure you have backed up anything you wish to keep. You only need to follow the instructions in this section once for any given device.
<br />The bootloader needs to be unlocked:
<br />http://www.droid-life.com/2012/07/17/how-to-unlock-the-nexus-7-bootloader/
<br />Short story, enable USB debugging in &quot;Settings</s>&gt; Developer options&amp;quot;. If you don't see it you probably have Android 4.2 and need to go to &quot;Settings <s>&gt; About tablet&amp;quot; and tap the &quot;Build number&amp;quot; entry seven times, and it will tell you &quot;You are now a developer!&quot;.
<br />Then follow these steps:
<br />

./adb reboot bootloader
sudo ./fastboot oem unlock

<br />The adb and fastboot tools come with the Android SDK (adb.exe and fastboot.exe on Windows). You can run &quot;adb devices&amp;quot; to make sure that the computer recognizes the Nexus 7.
<br />At this point you might need to re-enable USB debugging in the settings before continuing with the flashing.
<br />h1. Flashing device
<br />Now we can flash the device with the images that we built earlier (replace <sub>/korhal with your build directory).
<br />

./adb reboot bootloader
sudo ./fastboot flash boot/korhal/out/target/product/grouper/boot.img
sudo ./fastboot flash system /korhal/out/target/product/grouper/system.img # might take a minute or more
sudo ./fastboot erase userdata

<br />h1. Playing
<br />h2. Fonts
<br />To fix &quot;QFontDatabase: Cannot find font directory /system//lib/fonts - is Qt installed correctly?&quot; I needed to do the following in adb shell (run &quot;./adb shell&amp;quot; on the host to start a shell running on the device):
<br />

mount -o remount,rw /system

<br />Then, from the host:
<br />

adb push

/korhal/qt/qtbase/lib/fonts/ /system/lib/fonts/

<br />h2. Touch input
<br />At the moment, you need to manually build qtbase/src/plugins/generic/evdevtouch and push it to the device.
<br />First, on the device, run &quot;mkdir /system/plugins/generic&amp;quot;. Then, from the host:
<br />

cd _{/korhal/qt/qtbase/src/plugins/generic/evdevtouch}
/korhal/qt/qtbase/bin/qmake && make
adb push /korhal/qt/qtbase/plugins/generic/libqevdevtouchplugin.so /system/plugins/generic/libqevdevtouchplugin.so

<br />h2. Visual splendor
<br />To get qmlscene to show something on top of the system UI, you'll need edit</sub>/korhal/qt/qtbase/mkspecs/unsupported/android-g++/qeglfshooks_surfaceflinger.cpp and change mControl</s>&gt;setLayer(0x00000001); to mControl-&gt;setLayer(0x40000000);
<br />Then, re-build the eglfs plugin and push it.
<br />

cd

/korhal/qt/qtbase/src/plugins/platforms/eglfs
_{/korhal/qt/qtbase/bin/qmake && make
adb push}/korhal/qt/qtbase/plugins/platforms/libqeglfs.so /system/plugins/platforms

== Running qmlscene ==

First we copy over a simple qml example, then we run qmlscene remotely. It's also possible to run it from the shell after doing "adb shell".

adb push ~/korhal/qt/qtdeclarative/examples/quick/mousearea/mousearea.qml /data/mousearea.qml
adb shell qmlscene /data/mousearea.qml -plugin evdevtouch:/dev/input/event0