WARNING:
This is NOT a custom kernel!
GPL requires that source is released for Android kernels.
It does not, however, require that the source is tracked.
Samsung Open Source
opensource.samsung.com
Each release is downloaded, extracted, and added to git in a single repo in order to create a kernel changelog. Some commits may be added to improve building the kernel as a standalone binary. The core functionality and features will remain unchanged.
https://github.com/StarKissed/FLIP_3_SM-F711B
Related
http://consumer.huawei.com/en/support/mobile-phones/p9-en.htm
http://download-c.huawei.com/downlo...oadId=80183&version=318892&siteCode=worldwide
I have written a linux kernel module for my Pixel2, and compile it under AOSP source: kernel/msm.git android-msm-wahoo-4.4-oreo-dr1
But when I insmod my module, dmesg reports "disagrees about version of symbol module_layout".
Google told me that the kernel source version I used to compile my kernel module is not corresponding to the kernel source version used to building the official Pixel2 kernel.
Where can I find the kernel source version/branch of AOSP used to build the official Pixel2 kernel?
https://android.googlesource.com/device/google/wahoo-kernel/
Thanks, but this link only has some binaries used for pixel device.
I want to have the kernel source location and its branch and version used to build the pixel 2 official kernel.
Hello,
I'm just here because I'm very happy to announce that less than 2 hours ago, Samsung complied with a request that I made for the source codes of the Samsung Galaxy A20e (SM-A202F).
These sources can be found here.
I've also compiled two GitHub repositories with the kernel/platform sources, just in case anybody needs it:
Kernel sources
Platform
NOTE: The platform sources also include the vendor tree.
AlwaysLivid said:
Hello,
I'm just here because I'm very happy to announce that less than 2 hours ago, Samsung complied with a request that I made for the source codes of the Samsung Galaxy A20e (SM-A202F).
These sources can be found here.
I've also compiled two GitHub repositories with the kernel/platform sources, just in case anybody needs it:
Kernel sources
Platform
NOTE: The platform sources also include the vendor tree.
Click to expand...
Click to collapse
Pls Build a twrp or custom Recovery
As title is saying, nothing less, not much more.
Samsungs official source can be optained on github
https://github.com/ASKSAP/android_platform_samsung_a32x.git
https://github.com/ASKSAP/android_kernel_samsung_a32x.git
I've created partially working dev tree using https://github.com/SebaUbuntu/TWRP-device-tree-generator
Available at
https://github.com/netbospl/android_device_samsung_a32x.git
Lookng forward to read what You think about this.
Unpackbootimg that I've used and is/was working was compiled from
https://github.com/osm0sis/mkbootimg
Source was release for A326U variant by Samsung, so I've uploaded it to github.
A326USQU1AUCF/A326USQU1AUD4 - SM-A326U_NA_RR_Opensource
GitHub - netbospl/android_kernel_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source SM-A326U_NA_RR_Opensource.zip
A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source SM-A326U_NA_RR_Opensource.zip - GitHub - netbospl/android_kernel_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source...
github.com
GitHub - netbospl/android_platform_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform source SM-A326U_NA_RR_Opensource.zip
A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform source SM-A326U_NA_RR_Opensource.zip - GitHub - netbospl/android_platform_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform ...
github.com
Is anyone here knowlage-able in Andorid building process that's willing to walk through my out images for PitchBlack Recovery and AOSP R/11 images??
If there is no red flags, I should be able to do same for A32XU/A32XU1
Edit: also please note that device tree on my repo is not up to date/that I've used to successfully build AOSP, master should be fine for PitchBlack CWM A326B, and that's where I'll intentionally leave it for now
You got that AOSP ROM ready yet?
Good
I'm new to the android build system but have been running stripped kernels for years. I'm working on a custom rom for a TCL A30 (MT6762/MT6765).
I've looked at the AOSP code base and TCL source, for a similar device, and it looks like the TCL source generates the needed kernel .config file with scripts. There are multiple scripts for different archs and cellphone carriers. My TCL A30 has a Bangkok_CC (ConsumerCellular) tag and I found arch/arm64/configs/bangkok_TF_defconfig (TracFone). There do not appear to be any patches in the TCL source. The source I found:
TCL-Mobile on sourceforge
Has the Tracfone TCL A3:
Tracfone TCL A3x product link
That source contains Bangkok_TF_defconfig.
I was able to adb pull /proc/config.gz directly from the device and it's running 4.19.126+ released last month.
First question: Can I generate a bangkok_CC_defconfig from /proc/config.gz in the AOSP code base? It is mosttly monolithic
Code:
cat .config | grep =m > kernel_modules.txt
CONFIG_IKHEADERS=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_SERIAL_OF_PLATFORM=m
CONFIG_BATTERY_MT6359=m
CONFIG_SND_SOC_MT6359_ACCDET=m
CONFIG_USB_DUMMY_HCD=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMSTAT_TRACER=m
At the time of this post the latest upstream is 4.19.244
Second question: Are most Android projects like Debian/RHEL where they back patch kernel vulnerabilites? Would the most up-to-date kernel result from the latest AOSP source and would building it just be a matter of dropping in my /proc/config.gz and setting the build environment that I found in the TCL source?
I suspect that AOSP is contributing back to kernel.org. Third question: AOSP vs Kernel.org source? Does Google backport like RHEL/Debian? Or would I get a more recent,, secure kernel using upstream kernel.org source?.
Last question Clang vs GCC. I've just setup my Arch Linux build box w/ arm64_gcc. Speed is less important to me than stable builds. What are the arguments for one compiler over another?