kandi X-RAY | platform_system_core Summary
kandi X-RAY | platform_system_core Summary
platform_system_core
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of platform_system_core
platform_system_core Key Features
platform_system_core Examples and Code Snippets
Community Discussions
Trending Discussions on platform_system_core
QUESTION
I found the following source code linked to below, but I don't see any implementation. I would like to know what happens on the device side when install is called.
https://github.com/aosp-mirror/platform_system_core/blob/master/adb/client/adb_install.h
...ANSWER
Answered 2019-May-16 at 14:11The implementation of this header is located in the same directory, named adb_install.cpp
. Typically the name of an implementation file (.c
/ .cpp
) matches the name of its corresponding header file (.h
).
QUESTION
In adb shell
ANSWER
Answered 2018-May-20 at 16:05The logcat
code is pretty clear:
QUESTION
I'm reading the source code of ADB, which comes from AOSP. I traced the flow of receiving the command adb devices
. I found that the client sends this command to the server and then reads the answer from the server. But where is the logic of the server that handles this message? I can't find it. Can you point it out for me? The source can be found here. I'm referring to the Linux version.
ANSWER
Answered 2018-Mar-13 at 09:14Ah, it's in adb.cpp
, following this line.
QUESTION
https://android-developers.googleblog.com/2017/07/seccomp-filter-in-android-o.html
As "seccomp filter" section of this article saids,
Android O's seccomp filter blocks certain syscalls, such as swapon/swapoff, which have been implicated in some security attacks, and the key control syscalls, which are not useful to apps. In total, the filter blocks 17 of 271 syscalls in arm64 and 70 of 364 in arm.
Now, some syscalls are blocked and throws error signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr -------- Cause: seccomp prevented call to disallowed system call 55
.
But I cannot find the above list of 17 syscalls in arm64 and 70 syscalls in arm. Which syscalls are restricted? How can I find the syscalls for cause of crash?
Edited:
It seems that this error message is generated in here.
...ANSWER
Answered 2018-Feb-16 at 09:49The syscall filter source files are autogenerated, but the text files from which the filters are generated are located in the next directory up. Here we find a list of all syscalls of interest, as well as a couple of whitelists and blacklists. Presumably the app blacklist is what you are looking for; I've summarized it below.
Edit: Syscall Filtering BackgroundThe filtering itself is a standard feature provided by the Linux kernel, called seccomp. All AOSP does is make use of this feature to filter the system calls listed in the app blacklist linked above. A script processes that blacklist into a platform-specific autogenerated filter that is then fed to seccomp for the process from which all Android apps are launched (ie Zygote). Once this filtering is active, making a matching syscall from the filtered process (ie any app) will result in a SIGKILL signal being delivered. See here for some general information on Linux signals. The error message printed by the AOSP source that you linked is just the system trying to give you some useful information when it notices that your process was killed - notice that the method name is dump_probable_cause
.
QUESTION
I've checked this and this and STFW before I ask. Because of ROM's Difference , I want to cross compile an ADB server(N+) running on my aarch64 device from the [adb source code].
You can see here for the difference changes of android.mk in the following lines:
Latest Android 7.+ version , Lollipop Android 5.+ version This Version contains adb for device-on-target feature.
QuestionI can't find a proper MakeFile and it's just a Android.mk in the folder.How should I convert it to makefile in order to using make
to build a adb for device-on-target. I've already built a cross compiling environment and installed the ndk-build
,repo
,build-essential
on my ubuntu 16.04 lts.
Or on the other hand, can I only build ADB for device-on-target without compiling the whole rom?Which argument should I use with ndk-build
?Please give me more detailed info and caution.
ANSWER
Answered 2017-Mar-02 at 17:32Instructions on setting up a platform build environment are on the AOSP website: http://source.android.com/source/requirements.html
The ADB client program is not configured to be built for the device. We only support that for hosts. If you want to build it for the device, you'll need to add that build configuration (see system/core/adb/Android.mk) and then most likely do some porting work to get it functioning.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install platform_system_core
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page