Frequently Asked Questions
Browse through the most frequently asked questions of our customers, and find the answers to all the most common questions. If not, please use the form on the right to send us your question.
If you want to disable the beeps of the buzzer when you touch the screen, do the following in the serial debug console:
# echo 0 > /sys/bus/i2c/drivers/ft5x06_ts/2-0038/buzopen
You can create your own boot animation for your device. The Android platform provides an easy way to replace its default boot animation by putting a bootanimation.zip file into /
To create your own bootanimation.zip file, see How To Change, Customize, and Create Android Boot Animation.
How to install the boot animation:
- On the host, use the ADB to download the bootanimation.zip file into the device.
$ adb push ~/Downloads/bootanimation.zip /mnt/sdcard
- On the device, remount the /system to writable, and copy the file:
$ mount -o remount -w /system
$ busybox cp /mnt/sdcard/bootanimation.zip /system/media/
$ mount -o remount -r /system
You can reference How_To_Connect_Board_By_Serial.pdf to set it. The default serial baud rate is 115200 8N1.
You can reference IMX6Q_MAC_Address_User_Guide_V1.1.pdf to fix the MAC address.
Since Jelly Bean, the security ADB is enabled by default (ro.adb.security is set to 1). In security ADB mode, the ADB over Ethernet is not allowed. For more details, see “How do I enable and disable security ADB?”
To use the ADB over Ethernet, there are two steps to follow:
- Disable the security ADB by changing ADB security setting in init.rc
- Delete or comment the below line, and then rebuild the boot.img. setprop ro.adb.security 1.
- Keep the board connecting with USB to the PC, and enable the ‘USB debugging’ from Setting->Developer Options, and then follow the steps below to set up ADB over Ethernet.
For Linux OS PC, assuming you had built Android code or had installed Android SDK), complete the following actions
to use ADB over Ethernet:
$ ping IP_OF_YOUR_BOARD (run "netcfg" on board to get IP address)
$ export ADBHOST=IP_OF_YOUR_BOARD
“adb” is a host tool created during Android build.It’s under out/host/linux-x86/bin/. Make
sure you set path properly.
$ adb kill-server (Not sure why this step is needed. Just re-start adb daemon on board.)
$ adb shell
Set the ADB port properly on the device:
$ setprop service.adb.tcp.port 5555
After setting up the ADB listener port, re-enable the USB debug function in the Settings application.
You can use MFGTools in Windows to update the system. Or you can use the prebuilt image packages in Linux System to make one bootable SD card to update the system.
The Bus Frequency driver is used to slow down DDR, AHB, and AXI bus frequency in the SoC when the IPs which need high bus frequency are not working.
This saves the power consumption in Android early suspend mode significantly (playing audio with screen off). In this release, the bus frequency driver is enabled by default. If you want to enable or disable it, perform the following command in the console:
$ echo 0 > /sys/bus/platform/drivers/imx6_busfreq/busfreq.x/enable
$ echo 1 > /sys/bus/platform/drivers/imx6_busfreq/busfreq.x/enable
Note that if you are using Ethernet, the up operation enables the FEC clock and force bus frequency to be high. That means you cannot go into low bus mode anymore, regardless whether the Ethernet cable is plugged or unplugged. Therefore, if you want the system to go into the low bus mode, you must do ‘netcfg eth0 down’ to shut down the FEC manually. If you want to
use FEC again, do ‘netcfg eth0 up’ manually. When FEC is shut down with clock gated, the PHY cannot detect your cable in/out events.
The NXP platform products support 3 RS485 and 2 RS232 default.
To configure the proxy settings for a WiFi network, do as follows:
- Tap and hold a network from the list of added WiFi networks.
- Select “Modify Network”.
- Choose “Show advanced options”.
- If no proxy settings are present in the network, you have to – Tap “None”, Select “Manual” from the menu that opens.
- Enter the proxy settings provided by the network administrator.
- Finally, tap on the Save button.
The versions later than Android JB 4.2.2 introduce public key authentication policy when connecting to PC host via ADB. This feature keeps the ADB offline until the device and PC pass authentication.
With security ADB enabled, Android SDK Platform-tools in PC host side higher than revision 16.0.2 is needed to make a valid ADB connection. Otherwise, the PC cannot connect the device over ADB (the status is always offline).
With the latest Platform tools, the device displays a dialog to remind you to allow ADB to connect or not when connecting the device with the PC through ADB.
Then, you need to select “OK” to allow the PC to connect your devices. If you select “Cancel”, the ADB connection is rejected. For running the CTS, you need to select “Always allow from this computer“. Otherwise, the device still needs your confirmation in each reboot. To disable it,
delete this line or comment it as follows:
#setprop ro.adb.secure 1
The RTL8723BU is supported.
The Android UI framework defines a set of standard logical densities to help the application developers target application resources. Device implementations MUST report one of the following logical Android framework densities:
- 120 dpi, known as ‘ldpi’
- 160 dpi, known as ‘mdpi’
- 213 dpi, known as ‘tvdpi’
- 240 dpi, known as ‘hdpi’
- 320 dpi, known as ‘xhdpi’
- 480 dpi, known as ‘xxhdpi’
Device implementations SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen unless that logical density pushes the reported screen size below the minimum supported. To configure the logical display density for framework, you must define the following line in the init.freescale.rc:
Please contact us if you have any questions or suggestions.
Our team will be happy to provide all the information you need.