Understanding Android Properties: Get, Set, and Use System Properties with Examples
Android system properties are key-value pairs maintained by Android’s property service, used by the operating system and … Read more
Lynxbee topic
NDK / Middleware / HAL
Creating a Native Daemon and Running It from init.rc in Android : Step-by-Step Guide
In Android development, creating and running a native daemon can be essential for managing background processes that … Read more
Use property_set and property_get in Android Native Code: A Complete Guide with Examples
In Android development, system properties are a powerful tool for managing various configurations and settings within the … Read more
How to extract android boot.img ?
boot: The boot partition contains a kernel image and a RAM disk combined via mkbootimg. In order to flash the … Read more
How to create / change Android Boot Animation ?
Android boot animation is the loading animation that is played when your device starts up. In this post, … Read more
How to install Android NDK on Ubuntu Linux ?
The Android NDK is a toolset that lets you implement parts of your app in native code, … Read more
How to check the list of available sensors in Android ?
In android you check the list of all the supported sensors in your device by two ways. … Read more
Analyse android booting using Bootchart
Bootchart provides CPU and I/O load breakdown of all processes for the whole system. It doesn’t require … Read more
How Android System Properties Work Across Partitions
Android system properties are a system-wide string key/value mechanism, but they are not an unrestricted global preferences store. Reads use shared property areas; writes are validated by init’s property service and SELinux policy. Modern cross-partition contracts should use generated typed Sysprop APIs.
Link Libraries Correctly in Android.mk
LOCAL_LDLIBS is appropriate for stable NDK system libraries such as log or z. External libraries should normally be declared as source-built or prebuilt ndk-build modules so headers, ABI selection, dependency order, packaging, and runtime loading remain reproducible.
Fix “No Toolchains Found” Android NDK Error
The mips64el toolchain error usually means an old Android Gradle Plugin or native build expects files removed from newer NDKs. Diagnose the version boundary, modernize the build, and use a legacy NDK only as a controlled archival fallback.
Cross compiling C/C++ programs for Android using NDK Toolchains
If you are using NDK version more than r19, the toolchains which comes as part of NDK … Read more
Solved: java.lang.UnsatisfiedLinkError: no hello in java.library.path
When we were developing the JNI example as mentioned in our another post, “Java Native Interface ( … Read more
Understanding Android Bluetooth Code : part 1 – Application Framework
At the application framework level is the app’s code, which utilizes the android.bluetooth APIs to interact with … Read more
Compile native C library and daemon using Android.mk
To compile any c library inside android, we need to write an Android.mk makefile, for reference please … Read more