Develop Bugs

[Toolchain] UberTC optimized for A8 & A9 [GCC 4.9 to 6.0]

UberTC optimized for A8 & A9​
This is basically UberTC toolchain built for A8 and A9 CPUs.
If you don't know what a toolchain is made for don't post here please
Note that i haven't tested A9 builds. If you find any bug, feel free to post it here.
Downloads: https://bitbucket.org/Coldwindofnowhere/
All credits goes to @Cl3Kener
Contributors
 @Cl3Kener
Source: https://github.com/UBERTC/
Version Information
Status: Stable
Created 2015-11-09
Last Updated 2015-11-09

Which version should i choose ? ​
- Use A8 version if you want to build for any Cortex-A8 based device : i9000 (and all of it's variants), i9001, ...
- User A9 version if you want to build for any Cortex-A9 based device : i9100, i9300, i9305, ...
How to use this toolchain for your builds ?​
Add this to your local manifest (for arm-eabi 4.9 with A8 optimisations)
Code:
<remote fetch="https://bitbucket.org/" name="bitbucket" />
<project name="Coldwindofnowhere/arm-eabi-4.9-cortex-a8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" remote="bitbucket" revision="master" />
(I will add more stuff later)

Reserved

Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?

gsstudios said:
Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?
Click to expand...
Click to collapse
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.

Coldwindofnowhere said:
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.
Click to expand...
Click to collapse
Sure, I'll try building with your toolchain builds on the s2. I'm pretty sure that the differences will be minor, considering how great the toolchain is even without any tuning at all.
thanks, gsstudios
Edit: Please disregard what I've just said. Don't have time due to commitments to exams. Maybe sometime later this week I will be free.

I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.

Coldwindofnowhere said:
I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.
Click to expand...
Click to collapse
Yup i'd like to try the A9 ones for eabi 6.0 if possible

aaz03 said:
Yup i'd like to try the A9 ones for eabi 6.0 if possible
Click to expand...
Click to collapse
Sure, i'll build it in a bit.
Edit : uploaded, tell me if you face any issues.

Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?

djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.

Coldwindofnowhere said:
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.
Click to expand...
Click to collapse
Thanks! The same error is also in UberTC from https://bitbucket.org/UBERTC
What build system do you use? Standard Omni build system or some other?

djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Umm, what compiler flags are you using ?

Coldwindofnowhere said:
Umm, what compiler flags are you using ?
Click to expand...
Click to collapse
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .

djkoloda said:
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .
Click to expand...
Click to collapse
Compiling without these flags has not given results. I tried to arm-linux-androideabi-4.8 UberTC instead of that of the Omni and everything compiled.

Android 7.0 on wave - Possible?

Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?

Hello,
it's possible to compile N for the wave... But I don't really see the use in it...

Wave's ram is too low....using android 7 with it will be so slow
Honestly best ROM made for wave till now is ICS....it is fast and uses less ram
Best Regards

yes
yesterday , galaxy s1 has released cm 14
so lt will be posible
---------- Post added at 09:31 AM ---------- Previous post was at 09:25 AM ----------
ghostbiceps said:
Dear @Alberto96 @volk204 @fire855 and @hero355.
Is it possible to port android 7.0 into our Wave's?
Android 6.0 is great.. But I know, that you can make 1 more step.
Can you..?
Click to expand...
Click to collapse
yes
yesterday , galaxy s1 has released cm 14
so lt will be possible

Very possible. @fire555 you can apply commits from kernel N of S1 to Wave and port CM14 of S1 to Wave?
You can tell me version of gcc to build kernel for wave? Thanl you

i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank

thinhx2 said:
i´m patched commits to boot android 7.0 for wave from ss s1 via source kernel of @Coldwindofnowhere
check here https://github.com/thinhx2/android_kernel_samsung_aries @fire855 tell me version gcc to build kernel for wave. thank
Click to expand...
Click to collapse
Using GCC 4.7 should be fine. Maybe newer too.

fire855 said:
Using GCC 4.7 should be fine. Maybe newer too.
Click to expand...
Click to collapse
You can send me link of gcc 4.7?

@fire855

thinhx2 said:
@fire855
Click to expand...
Click to collapse
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.

xc-racer99 said:
Because you're not building inline (eg the kernel with the ROM), you need to remove the leading "source/" from the paths in usr/wave_initramfs.list
BTW, I'm assuming you're building AOSP, otherwise you should be building the kernel with the ROM.
Click to expand...
Click to collapse
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs

thinhx2 said:
I try make zImage bug dont complete,i had change nam folder aries to source but have bug same first build. I dont see file initramfs_data.cpio in urs
Click to expand...
Click to collapse
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)

xc-racer99 said:
I think you misunderstood me. You need to edit the file in KERNEL_SOURCE/usr/wave_initramfs.list (where KERNEL_SOURCE is the folder you downloaded the kernel source to), removing "source/" from any of the lines in that file that have it.
However, because you seem to be trying to just build the zImage, you need a prebuilt ramdisk.cpio and ramdisk-recovery.cpio as the ramdisks are built into the kernel (however the i9000 and series have switched them over to their own partitions on 7.0, see https://github.com/xc-racer99/andro...mmit/503a411a16c3671b5da9775450de582cc8c2ce85 and follow-up commits https://github.com/xc-racer99/andro...mmit/345ca93aa0877a9f1f382cfb284c752290b02c91 https://github.com/xc-racer99/andro...mmit/a5a2d012566390ac363e6950e8b7d73417a3b4a1 in the kernel, changes are need to your equivalent of aries-common)
Click to expand...
Click to collapse
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try

thinhx2 said:
I need add line of ramdisk from here https://github.com/xc-racer99/andro...82cc8c2ce85/drivers/mtd/onenand/samsung_gsm.h
To https://github.com/fire855/android_...ndroid-6.0/drivers/mtd/onenand/samsung_wave.h ? I think partitions of both device ís different. But thank you so much, i will try
Click to expand...
Click to collapse
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.

xc-racer99 said:
Well, it really depends on which partition format you want to use:
1) Continue using the "traditional" partition layout where the ramdisks are integrated into the kernel. This is probably recommended.
or
2) Switch to having the ramdisk and ramdisk-recovery each on their own partition. The i9000 has gone to this system in 7.0 - advantages are that things like SuperSU and Magisk can then easily modify the ramdisk without having to rebuild the kernel. This requires the changes in both device/samsung and the kernel and is more difficult.
However, I'm still unclear as to what ROM you're building. You shouldn't be trying to build just the kernel unless you're building pure AOSP.
Click to expand...
Click to collapse
I no build rom,because wave can run rom of s1 normal with kernel of wave. I think no need build rom. I only merge new commits of kernel 7.0 s1 to wave. I patched comeplet but i have problem. I will try tonight

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13

Reserved

Edit 1:initial build didn't boot for me, no adb can't get log

Ok im gonna try it.
If you want, i can leave logcat for you

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.

Ofc, it doesn't boot. And don't create threads without testing.

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought

Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

how to compile redmi 2 kernel from source?

I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot. I tried to boot lp-kernel from @premaca it booted.
Also, my compiled compiled kernel size is a megabyte bigger than the great premeca's.
I used the config file from premeca's source & kernel.
@ premeca, Please help me .............
Which compiler should I use ?I used ndk
& the one from Google source.
Thanks in Advance!
I want to compile final-lp version.
EDIT:-
Fixed it myself,
I was using Ubuntu's preinstalled Archiver to extract the Kernel source zip.
Using "unzip *.zip" solved the problem (idk why).
Just get the source, download toolchain from googlesource
And follow the steps in video

Naveen Singh said:
I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot:...
Click to expand...
Click to collapse
I've never built a Kernel but, I believe that the following thread is the closest to what your looking for that's specific to the Redmi 2.
https://forum.xda-developers.com/showthread.php?t=3155130
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Naveen Singh said:
I tried to compile redmi 2 kernel from source, & yes I compiled it successfully but it doesn't boot. I tried to boot lp-kernel from @premaca it booted.
Also, my compiled compiled kernel size is a megabyte bigger than the great premeca's.
I used the config file from premeca's source & kernel.
@ premeca, Please help me .............
Which compiler should I use ?I used ndk
& the one from Google source.
Thanks in Advance!
I want to compile final-lp version.
Click to expand...
Click to collapse
Found any reason why it didn't boot? you have any ramoops file or something so you can know better? Link your kernel source for better help.

Some say it's compiler.
premaca said:
Found any reason why it didn't boot? you have any ramoops file or something so you can know better? Link your kernel source for better help.
Click to expand...
Click to collapse
@premaca
I used your kernel source for redmi 2 lollipop.
https://github.com/premaca/Xiaomi_Kernel_OpenSource/tree/Final-LP
Some people say that it maybe wrong compiler.
I also think so because my compiled zImage size is bigger than the one you have already compiled.
Yourcompiled kernel booted successfully. ( here it is )
Which compiler do you use to compile kernels for redmi 2 ?

Port for Kali.Nethunter kernel

Thread closed.
For new thread , go to this link.
https://forum.xda-developers.com/le...t/kernel-kali-nethunter-t3813746/post77016833
I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!

Atharva Ambre[AT said:
;76155798]I request out developers to pls port the kali nethunter kernel for our device z2 plus. U can use mostly oreo roms as base for kernel since its much optimized and this device is best for pen testing pls pls developers spare ur lil time and make history!
Click to expand...
Click to collapse
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready

Atharva Ambre[AT] said:
Update I have created the changes for the kernel but I'm getting this error while compiling ...pls do suggest me the fix den the nethunter kernel is ready
Click to expand...
Click to collapse
Wrong architecture maybe? Z2 is arm64.

JashanjotSidhu said:
Wrong architecture maybe? Z2 is arm64.
Click to expand...
Click to collapse
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try

Atharva Ambre[AT] said:
Thanks for the reply but nope I have ported rightly for z2 plus 64 bit defconfig file so I don't think its an arch issue since Kali nethunter kernel is for both arch 32 and 64 bit its something else.....thanks for ur try
Click to expand...
Click to collapse
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?

JashanjotSidhu said:
Yeah my bad that was Linux x86....
Can you share include/linux/cpufreq.h file?
Click to expand...
Click to collapse
Ya sure
Note the major errors are in proc.c

Atharva Ambre[AT] said:
Ya sure
Note the major errors are in proc.c
Click to expand...
Click to collapse
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.

JashanjotSidhu said:
You uploaded cpu.h bro... I asked for the cpufreq.h...
Proc.c errors point to the above file as per your screenshot.
Click to expand...
Click to collapse
Oh I'm sorry my bad here's the right file

Atharva Ambre[AT said:
;76282414]Oh I'm sorry my bad here's the right file
Click to expand...
Click to collapse
Sorry again same wait take this

Atharva Ambre[AT] said:
Sorry again same wait take this
Click to expand...
Click to collapse
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.

JashanjotSidhu said:
Try deleting the 657th and 658th line of cpufreq.h and then make again....
From where did you get the kernel sources? I couldn't find any 820chipset kernel sources with those lines.
Here's Z2 plus's file.
Click to expand...
Click to collapse
Will try and I got it from github its the open sources kernel , its available on most of the ROM first page , I got it from aex intro page on XDA
U won't find it bcoz the CPU freq file is inside Linux/include/CPU so its not android based file it's the main working of Linux so u won't find any specific chip based also it won't mention sd820 bcoz its open source u can port it as long as u are able to get it right without bugs its an open source so its open for many devices and many chipsets.

Update :
I tried again from start I think its the problem with the compiler of ndk will download older version and try out tomorrow...still getting many other errors while compiling from the source kernel
Pls provide me the link of latest stable ROM with it sources updated!thank you!

Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel

Atharva Ambre[AT] said:
Update:
I'm gonna switch to Ubuntu distro it maybe can be distro problem.....have been trying to compile on Kali Linux..but failed despite many tries ,also re downloaded latest sources of kernel
Click to expand...
Click to collapse
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.

JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
Idk I have just right now running Ubuntu on VM I m downloading the files I don't think so that the problem is associated with kernel version bcos the thing is many new Android devices like one plus 3 and other many update android version devices like nexus have official nethunter support so latest android means the kernel will be upgraded to more newer version such as 3.18.xx and all so is our z2 plus to the same version ....anyways gonna give a try in Ubuntu or else have to wait till I get a proper source for kernel.
Can u suggest any good source for this project ?
I'm currently using the Oreo ROM and the source of the kernel is DDrb0h kernel which is the branch of lineage 15.1.

Also I have identified the major error which is in CROSS COMPILE step for android ndk idk why but in Kali Linux I'm not able to get CROSS COMPILE so kinda in lil problem...

JashanjotSidhu said:
I don't think linux distro could be a problem... maybe kernel version isn't compatible? Try using a different source.
Click to expand...
Click to collapse
I think the problem is associated with the kernel sources same error on ubuntu

Update
Tried my best to compile yet ran into another error
Changed the sources to latest treble one
I got new error with arm-linux-androideabi- gcc error some command is invalid ....I require a little guidance here . So kernel developers pls show me which version of ndk shld I use and sources shld I refer and what extra commands shld I run?

@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..

SteelBodyX said:
@Ayush Rathore.. Could you help this guy in solving his problem.. I think it's a interesting project..
Click to expand...
Click to collapse
Thank you for ur suggestion. Ya I haved pm him already but didn't receive any update from him and also the work is done.I have made the changes for the project just one step I'm lagging is compiling it......then its free for distribution here.