Related
http://downloads.sourceforge.net/pr...xz?r=&ts=1439784880&use_mirror=skylineservers
SHA1: 463f818fc8b57525981a46e31ea5ee63f2987742
MD5: 88d8db5d4c9637daeb339eb79878c93a
Mirror: https://mega.nz/#!j4s1WYLK!DpK2bMfznrt_ih3-UtE6xvUgFSAujw9LBu4qgSCSzkU
Thanks to @neilownz for notifying us in the system image thread! Let the rom development begin!
Oh and xposed framework also works for the idol 3 as of yesterday.
Click on mirrors. I already finished downloading it in case it disappears.
Yay. Let the development begin
Yes, thx alcatel !
thanks for noticing
damn you've been faster than me
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
frankee207 said:
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
Click to expand...
Click to collapse
Yes it is. Plus 1.8 GB external tools.
Game of Roms.
Roms are coming...
My favourite season of game of ROMs xD
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
yazzabo said:
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
Click to expand...
Click to collapse
No, the 6045 has a 64bit Snapdragon 615. The OnePlus One has a 32-bit Snapdragon 801.
someone could compile a kernel?
cpu -snap615-msm8939
board msm8916
32bits-arm.......64 bits -Aarch64 for gcc? or armv8?
arm64-defconfig
gcc version for compiling?
Woohoo cyanogenmod (or another ROM) here i come!!!
Successful compilation
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series? I'm waiting for the day someone generates a kernel with some of the newer governors like intellidemand or interactiveX...perhaps would solve any of the remaining lag and heat issues. I honestly thought they would have made factory rom downloads available first before source but certainly won't complain.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
franq36 said:
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
Click to expand...
Click to collapse
I use the prebuilts from the Cyanogen repo. Also the recommended architecture of the host machine for compilation of Android is x86_64 from long time.
@franq36 ... In case that you are curious. This is the list with the installed gcc packages on the host machine.
Code:
gcc install
gcc-4.7 install
gcc-4.7-base:amd64 install
gcc-4.7-multilib install
gcc-4.8 install
gcc-4.8-base:amd64 install
gcc-4.8-multilib install
gcc-4.9-base:amd64 install
gcc-multilib install
franq36 said:
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
Click to expand...
Click to collapse
Here are two logs from my virtual machine. The first build is for 32 bit architecture while the second is for 64 bit. The TARGET_KERNEL_ARCH in both cases however is arm. arm64 cannot be compiled successfully, as returns the following error:
Code:
make[2]: *** No rule to make target `zImage'. Stop.
make[1]: *** [sub-make] Error 2
franq36 said:
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
Click to expand...
Click to collapse
I don't understand what you mean here. The idol347 however is with Snapdragon 410 not 401.
franq36 said:
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
Click to expand...
Click to collapse
This is strange indeed.
---------- Post added at 19:52 ---------- Previous post was at 19:10 ----------
famewolf said:
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series?
Click to expand...
Click to collapse
I'm not sure about this. The devices are different, the boards are different, the kernel configuration and respectively the kernel is different, the display resolution of the devices is different. These are too much differences I think.
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
i think you can contact the guy named mario tomas serrafero hes the one that writes the main page articles
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
for now it is early, still are not completely operational ... I think for 6045
and I managed to fix compilation errors through installed ubuntu 14.04.3 64 bits and all the tools ...
idol3_defconfig is only arm64 and gives -mgeneral-regs-only error.
I could cheat and load it from arm but having to fix several compilation errors and dependencies bad in defconfig.
I am having many compilation errors which explains that the GCC is not quite right. NDK official gcc 4.9. arm-linux-androideabi have to look any more current or Linaro to check
I think there is a gcc 4.9.3
I'm half compilation with many problems ... I hope it's not the fault of sources and it is time lost
has any one started on porting CM12/12.1 ? you could count on me for testing
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
Hey guys, I'm starting this thread in the hopes that somebody can explain to me the following:
I wanted to play around with the Galaxy Grand's kernel source (just to get an idea of how a kernel works) so i downloaded it from sir @GHsR 's repo (stock branch)... now, the unpacked size is a whooping 478MBs... what i don't get is how all that fits into grand's 8MB boot.img's ramdisk.
could somebody help me out here?
FriendlyNeighborhoodShane said:
Hey guys, I'm starting this thread in the hopes that somebody can explain to me the following:
I wanted to play around with the Galaxy Grand's kernel source (just to get an idea of how a kernel works) so i downloaded it from sir @GHsR 's repo (stock branch)... now, the unpacked size is a whooping 478MBs... what i don't get is how all that fits into grand's 8MB boot.img's ramdisk.
could somebody help me out here?
Click to expand...
Click to collapse
Cross compile it with toolchain (for example : Uber Toolchain
Get that here : https://bitbucket.org/matthewdalex/ I generally use arm-eabi-5.x version )
ABSathe said:
Cross compile it with toolchain (for example : Uber Toolchain
Get that here : https://bitbucket.org/matthewdalex/ I generally use arm-eabi-5.x version )
Click to expand...
Click to collapse
hey man.... i think you misunderstood me. I'm not planning to work on kernels (hopefully yet), i just wanted to know how the source fits into the boot.img. nevermind, i got my answer from two friends : most of the source is optimised and stuff... some other stuff like legal mumbe-jumbo & documentation is ignored while compiling, and it's done. hope somebody who was searching for this kind of info finds it.
Sent from my GT-I9082 using XDA Labs
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.
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
That is all we need ! A custom kernel thant can handle GSI !
Voodoojonny said:
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
Click to expand...
Click to collapse
I've updated the link, you should see the uncompressed file in folder !
Or direct link : https://drive.google.com/file/d/1TvihsIa_XbtC66yaWRZ1EPY5UR6LLD5g/view?usp=drivesdk
Thanks
WiwiPouPou said:
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Click to expand...
Click to collapse
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
I've tried, maybe my image is bad, strange (I originally tried my stock source too, Google 4.9 toolchain, no luck). Can you test with the one in the link please ?
I will have access to my PC only next week...
Thanks a lot for your feedback !
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
WiwiPouPou said:
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
Click to expand...
Click to collapse
I used the original source code with some small changes (which are now included in official source) to make it compile.
Don't mind about the toolchain for the moment, gcc4.9 is most stable.
I don't have time trying this out atm, busy compiling los 15.1 but if you share exactly how you did it, (terminal log in pastebin and most importantly the exact errors, "doesn't work" doesn't help ) me or someone else might be able to help you (and you don't have to ask next time you get the error.
If you want you can start adjusting the lineage kernel, so i could build with los kernel which could save time towards working custom roms.
I successfully repack. But phone don't boot. (9.11 ROM)
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
artyom5613 said:
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
Click to expand...
Click to collapse
On which roms did you test your kernel?
Voodoojonny said:
On which roms did you test your kernel?
Click to expand...
Click to collapse
8.1 stock. 9.11
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
artyom5613 said:
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
Click to expand...
Click to collapse
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Thanks! O try to add kcal with this commits.
Yea, source for pie is not pushed. Xiaomi cant fix 8.1 kernel... Stock compiled kernel issue: wifi don't work...
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Can you tell me what version of kernel you use whyle compile kernel? I tryed on new 9.11, but phone dont boot.
Maybe when you compile version be 9.10 or ealier.
becouse ramdisk and kernel image can conflict
I hope this can support settings for "display temperature" so that we dont need app for calibrating warmth or coolness of display
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
artyom5613 said:
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
Click to expand...
Click to collapse
Kcal is working ?
Strange for WiFi, module not compiled ?