WiFi direct has a shell tool for doing configuration changes called "p2p_cli". I can't find a newer version compiled to run on Android 5.0 with the new PIE security requirement.
It seems to be part of the Android platform source code, here: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master/src/p2p
Reference on PIE compile:
http://stackoverflow.com/questions/...id-l-error-only-position-independent-executab
Some ROM developer can maybe compile it for me and provide a download of the binary? Thank you.
Related
Hi all,
Found cyanogen source code a great one to start playing with Android and I have compiled the source code. The compiled ROM is working perfectly in my N1. Then I decided to start working with Eclipse. I copied .classpath file from development/ide/eclipse to root directory of the source code and created a new Java project from existing source in Eclipse. Thing ended up with an error about build path:
Code:
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Enum. Fix the build path then try building this project
Does anyone know how to fix this error?
Hello,
I actually have successfully build some kernels. Mainly, this is the linux way:
- get kernel sources
- get hardware specific changes
- get the toolchain -> i'm using google prebuilt tree, with ARM tool chain 4.4.3 already compiled
- build with usual steps: def_config, configure, kernel, modules
All is ok.
Now, i found Android.mk files. Precisely, a previous kernel, with sensors related to my device, that i would like to port.
But here comes the trouble. I have hard time to do the link between Linux kernel for ARM and Android makefile. I don't see how it goes with my kernel, how i could compile this using the prebuilt tools i could grab from Google.
In short, how to include .mk files into a classic kernel ? What should i get in the end ? A module ? A replacement binary ? More precisely, what is exactly NDK and where it stands in the above layers ?
ARM Linux Kernel <--> Dalvik JVM <--> APK
Last, is it possible with Google prebuilt to compile the .mk without referencing your kernel ?
Thank you !
Thank you for your help
Damn ! Either the questions is too obvious, either it is too complex. Any help ?
Self reply: downloading the NDK is mandatory
- you can use your favorite toolchain, provided with the NDK
- you can embed the .mk into your application, for Eclipse / Android studio, it will use the NDK to compile
Is there any way to download Android Source Code (Android 5.0.0 branch) from google git in Windows without running virtual box???? If yes, please provide the brief description for download it.
http://stackoverflow.com/questions/14223302/is-there-a-version-of-googles-repo-tool-for-windows
Read all of that, comments+links
I'm learning how to port Ubuntu Touch to this device, but I'm not sure what files I need of Android to can do it.
Porting guide:
https://developer.ubuntu.com/en/phone/devices/porting-new-device/
Kernel, device & vendor by Nofearnohappy:
https://github.com/nofearnohappy/kernel_6.0_hermes
https://github.com/nofearnohappy/android_device_xiaomi_hermes
https://github.com/nofearnohappy/android_vendor_xiaomi_hermes
I'm stuck in this:
Enabling a new device
If you're repository is compatible with the AOSP tree, it's just a matter of adding the device specific git repositories and the vendor files (usually blobs that you need to extract from the original android image). Once that is done, you should be able build a small android system image that can be used by Ubuntu Touch in order to make it fully compatible with the device.
Device
Add your device specific git repositories under phablet/device ("phablet" is the repository you cloned by following the previous build example and/or Touch/Building).
Make sure it's respecting the format used by AOSP (device/<vendor>/<device name>).
Hardware
Add your hardware specifig git repositories under phablet/hardware.
Make sure it's respecting the format used by AOSP (hardware/<vendor>/<component>). As an example:
Code:
$ ls hardware/qcom/audio/
Android.mk hal legacy visualizer voice_processing
Vendor
Add your vendor specific binary blobs under phablet/vendor.
Make sure it's respecting the format used by AOSP (hardware/<vendor>/<component>).
Code:
$ ls vendor/asus/flo/
BoardConfigPartial.mk BoardConfigVendor.mk device-partial.mk device-vendor.mk proprietary
Retrieving the proprietary blobs from Android
Ubuntu Touch Preview uses some pre-compiled binary drivers from the Android layer for rapid enablement of devices. These are referred to as binary or proprietary blobs, as their source code is not available for the build, and are included in binary form.
Since we use AOSP as a base, for supported devices all you need to do is to download and extract and run as mentioned in the downloads from https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
Any help apreciated.
I'm trying to compile Android for a dragonboard 410 clone, and would like to enable a firmware level functionality so that the device reboots if there is some kind of OS level failure.
I noticed on the Linux Github (Documentation/watchdog/watchdog-API.txt) that the Linux source has exactly what I'm trying to implement. (sorry, new user so can't post links)
I'm unfamiliar with compilation from source on Android, is there a compilation flag or option I can use to enable this functionality on Android?