Related
Okay so I'm currently downloading this 'Opensource_Update4.zip' file from Opensource, which I assume is the Official Kernel?
Just a few quick questions that I'd appreciate your help with guys:
1. Am I correct in what I just said above?
2. If so, do I just flash the file through ODIN?
3. Will this wipe my phone back to factory settings?
4. Will this affect my device being rooted?
Thanks in advance
New_World_Order said:
1. Am I correct in what I just said above?
Click to expand...
Click to collapse
No.
New_World_Order said:
2. If so, do I just flash the file through ODIN?
Click to expand...
Click to collapse
Again: no.
New_World_Order said:
3. Will this wipe my phone back to factory settings?
Click to expand...
Click to collapse
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
VAXXi said:
No.
Again: no.
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
Click to expand...
Click to collapse
Woaaaaaah I need a huge slap.
Would you be so kind as to explain please? :$
Sent from my GT-I9100 using XDA
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
VAXXi said:
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
Click to expand...
Click to collapse
Hahahaa okay thanks...
I think I'll just leave it alone! :')
Sent from my GT-I9100 using XDA
hi all
in this Topic i am making android 4.0.4
Part of the ROM files tigrouzen
DOWNLOADS
ROM
MOD EDIT: Link removed.
kernel
nand
MOD EDIT: Link removed.
sd
soon ...
patches
wifi &bt wave 2
MOD EDIT: Link removed.
gapps for this rom
http://www.mediafire.com/download/zfe72bjtnsjt787/google_for_nimaics.zip
features
. ROM: 66mg
. stable
. very smooth and fast
. Excellent battery
. odexed rom
. add file & code for Optimization
. zipaling
. Base rom: slim
. change or deleted app
. Enhanced sound quality
. Space, RAM: 160mg
. other ...
Installation
Bada 2.0 is required
copy rom.zip &kernel (zImage) to memory
flashed boot & fota
for s8500
MOD EDIT: Link removed.
for s8530
MOD EDIT: Link removed.
Reboot the phone holding Power and home
CWM Recovery starts, pick:
go to
install zip/choose zip from from storage/sdcard/rom name.zip/yes
after installed reboot and startup android
THANKS TO
thanks for files & kernel [tigrouzen]
volk204
Rebellos
blue59
alberto96
and other Badadroid devs
reserved
Kernel sources?
volk204 said:
Kernel sources?
Click to expand...
Click to collapse
kernel for tigrouzen (iczenrom)
i just make rom
nima.yavari said:
kernel for tigrouzen (iczenrom)
i just make rom
Click to expand...
Click to collapse
no kernel sources - no ROM here
volk204 said:
no kernel sources - no ROM here
Click to expand...
Click to collapse
why?
So what do I do?
nima.yavari said:
why?
So what do I do?
Click to expand...
Click to collapse
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
volk204 said:
Kernel development is covered under the GNU GPL v2 license. This means that all necessary information should be available to every person interesting in compiling a kernel, including the source, information about the toolchain, etc.
Violating the GPL license means that kernel is technically illegal, and therefore can't be shared. As far as XDA is concerned, it's considered warez, and as such, discussions of this ROM/kernel aren't allowed
from: http://forum.xda-developers.com/showpost.php?p=46855920&postcount=780
Click to expand...
Click to collapse
ok
i can't put just rom?
no kernel to this topic
You are still don't know, Why Tigrouzen isn't here
thnks
cfernr said:
how to perform nand install?
Click to expand...
Click to collapse
read post 1 Installation
nima.yavari said:
read post 1 Installation
Click to expand...
Click to collapse
why not nand 4.4.3?
cfernr said:
why not nand 4.4.3?
Click to expand...
Click to collapse
kernel tigrouzen erorr fc com.phone
need new kernel for 4.4.3
Awesome work bro!
Keep up the good work and make even more ROMs.
is GPS working on this rom?
cfernr said:
is GPS working on this rom?
Click to expand...
Click to collapse
yes
nima.yavari said:
yes
Click to expand...
Click to collapse
i cant have gps working? any app or something to fix it?
imho this is the best rom ever for the wave
The GPLv2 requires you to share the source code if you've modified anything in the kernel. This is not optional, you are obliged to do so. Non GPL compliant works simply do not belong on XDA (please report any you encounter).
OP, you may PM me once you're ready to upload the full, working sources.
You can review the forum rules here and read more about the GPL here and here. Thread closed.
Hello,
This is a stock SeLinux permissive kernel and init.d activated for Samsung Galaxy Note Edge (N915F) for Lollipop 5.0.1.
There are inputs that is working also on N915FY.
The kernel was compiled from Samsung source LL_CIS kernel using Google toolcahin v4.8.
If you want to test it, please flash in cwm the attached file and report back. Please make a backup of your actual kernel (boot.img) befor flashing this one.
Special thanks to @Micky387 who advised me to update the source kernel (MH driverI), @Wuby986 for his support and guidance and @daxgirl for his advices.
My kernel source for N915F (N915FOXE1BOC6) is here.
Happy flashing.
PS. Kernel updated. Same functionality but some different info in "About".
Well you got further than I did .. Kept getting some driver file referenced so it would not complied.. Thanks for effort I hope you work it out soon.. Unfortunately I don't have time at the moment ..
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
micky387 said:
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
Click to expand...
Click to collapse
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
starbucks2010 said:
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
Click to expand...
Click to collapse
No need to flash module. The MHI module will be in the kernel so you have boot.img with all inside.
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
Wait one more day..
Or maybe earlier
Finally done.
Make backup of your actual kernel, flash the attached zip from post 1in cwm and please report back.I didn't check the init.d support but it should work.
Good, I'll try.
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Any chance that you would be willing to make this kernel compatible with the Sprint variety? Man.... I need my viper4android bro. Please. Lol
UpInTheAir said:
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Click to expand...
Click to collapse
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Well done mate ..... Yea
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Boot and works fine , nice one
Can this be used on N915FY as well?
I don't have any reports from N915FY users. You can try and tell us
Don't forget to make a backup first.
starbucks2010 said:
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Click to expand...
Click to collapse
Hey, no problem.
Just to clarify....
If you've made any (even minor) change to "Samsung" source, then you have to upload "your" complete source and link "your" source, not "Samsung" So if you've made the kernel permissive or even use a different toolchain or path, technically you have modified from original and is now "your" source If you use a custom defconfig, don't forget it too
github is well worth the pain I Google for answers all the time (how to do this and that), but still screw things up (sometimes majorly) now and then.
dubart said:
Can this be used on N915FY as well?
Click to expand...
Click to collapse
Using this kernel with a N915FY. Great job btw I can finally use viper audio which I've missed so much. Major props dude!
I'm gonna flash this on sprint variant either that or throw this device out my window
dinaps86 said:
I'm gonna flash this on sprint variant either that or throw this device out my window
Click to expand...
Click to collapse
Lol it booted just no data. Yaaayyy!!!
I see that there are other people who are interested in Selinux permissive kernels.
So, if you want, I can add selinux permissive to any samsung kernel as long as you provide me 2 files: your original kernel (boot.img) from the ROM you want to flash and the Kernel.tar.gz - source kernel from Samsung site. In order to get Kernel.tar.gz file you'll need to download the kernel source file (~ 1Gb) from Samsung site, open the archive and upload ONLY the Kernel.tar.gz (~ 100-150 Mb) and the readme file from the archive to some sharing site. Then, I'll try to compile that kernel for you.
There are also downsides. I cannot stay up to date will all new commits done to the kernel source so I'll compile your kernels only with info that I have at that date. If you fork the github and find kernel source updates, I can add them.
PS. I only set up a working PC with Ubuntu and Google toolchain v4.8. If you find any information that this setup is not suitable for compiling your kernel, then there is no point of providing me the above files.
Best regards.
OP updated with some Antutu screen shots.
STOCK BASED ROM 8.1.0-OREO (OPM2.029.A1, May 2018.)
System :
- Android 8.1.0 opm2.171019.029.a1,May. 2018)
- Stock kernel 3.10.73
- Easy installation through the Aroma
Installation:
- Reboot to recovery
- Take necessary backups
- Wipe system/data/cache
- Flash the appropriate vendor.img
- Flash Rom.zip
- Reboot to system
- Enjoy
What is working:
- Everything
Contributors:
- cile381
Credits:
- Google/AOSP
XDA: DevDB Information
SUPERXE AOSP ROM for the Nexus 6P
ROM OS Version: 8.1.0-Oreo
Kernel: Linux 3.10.73
ROM Vendor:8.1.0 (opm2.171019.029.a1)
Based On: Google/AOSP
Version Information:
Status: Stable
DOWNLOAD ROM 8.1.0-OPM2.171019.029.A1
MD5 [fc884c4e09fad95c27b79cf606ec9158
VENDOR IMAGE 8.1.0-OPM2.171019.029.A1
MD5 [ec5d30b20fb022df2fe26a5b4ef8a0d4
Created 2017-07-25
Last Updated 2018-05-14
DONATIONS
@Signal2Noise
@hawgguy
Bee venom collector
@Samuel Holland
CUSTOM BUILT ROM 8.1.0-OREO (android-8.1.0_r21)
System :
- Android 8.1.0_r21
- Kernel 3.10.73
Clean installation is required!
Installation:
- Reboot to recovery
- Take necessary backups
- Wipe system/data/cache
- Flash ROM
- Reboot to system
- Enjoy
What is working:
- Everything
Vendor is included in the ROM and does not need to be installed separately!
Do not install stock vendor on this ROM!
Contributors:
- cile381
Credits:
- Google/AOSP
XDA: DevDB Information
SUPERXE AOSP ROM for the Nexus 6P
ROM OS Version: android-8.1.0_r21
Kernel: Angler/Linux 3.10.73
ROM Vendor:8.1.0 (OPM3.019/custom)
Based On: Google/AOSP
Version Information:
Status: Stable
If you change the kernel or any part of the system and after that you have a problem, please do not post any questions in this thread.
DOWNLOAD ROM SUPERXE-8.1.0_r21
MD5 641d3bb35cbf4f3b0e457b3c52480fa3
Root - Magisk 16.3
Created 2017-10-03
Last Updated 2018-04-11
Welcome and thank you for the contribution will test this out
Android Rocks
Sent from my Nexus 6P using Tapatalk
SWEET
I think 1st 7.1 based custom ROM..
Thanks @cile381[emoji4]
Where is change log ?......
mukesh22584 said:
I think 1st 7.1 based custom ROM..
Thanks @cile381[emoji4]
Where is change log ?......
Click to expand...
Click to collapse
Uberstock is 7.1 as well it's based on pixel sources.... OP is this the same or is it based on dev preview? Also change log is in first post
Arzee08 said:
Uberstock is 7.1 as well it's based on pixel sources.... OP is this the same or is it based on dev preview?
Click to expand...
Click to collapse
Neither private sources was not used for building.
Rom is 100% synced and built from googlesource..
Gif support on keyboard with Messenger and Allo?
Can I go back to a MM custom rom after i've flashed this?
I've never tried 7.0 or 7.1 . I will stay on this rom if all my apps work and when the battery is good.
Yes.. thanks dev
Wouldn't you flash the vendor image after flashing the ROM in recovery? Rebooting into bootloader is just a extra step or am I wrong???
tarroyo said:
Wouldn't you flash the vendor image after flashing the ROM in recovery? Rebooting into bootloader is just a extra step or am I wrong???
Click to expand...
Click to collapse
Can twrp flash radio imgs?
Lawlrus said:
Can twrp flash radio imgs?
Click to expand...
Click to collapse
Not radio images but if someone makes a flashable zip of new radio and bootloader etc then you can
Sent from my Pixel XL using XDA-Developers mobile app
mickyw1980 said:
Not radio images but if someone makes a flashable zip of new radio and bootloader etc then you can
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Obviously. But that's why it says to boot into the bootloader.
Lawlrus said:
Obviously. But that's why it says to boot into the bootloader.
Click to expand...
Click to collapse
I don't see the point of your question then if you obviously know ?
Sent from my Pixel XL using XDA-Developers mobile app
mickyw1980 said:
I don't see the point of your question then if you obviously know ?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I wasn't 100% if twrp could now do radio images and bl's like it can vendor images now. And I'm not sure what that bit of numbers stands for after you typed know
The point of my question was to answer his question as to why the op says to boot into the bootloader in the op, he offers the BL and radio in IMG form, not flashible..
My stating obviously, was to your stating you can get flashables for twrp for the radio.
Lawlrus said:
I wasn't 100% if twrp could now do radio images and bl's like it can vendor images now. And I'm not sure what that bit of numbers stands for after you typed know
The point of my question was to answer his question as to why the op says to boot into the bootloader in the op, he offers the BL and radio in IMG form, not flashible..
My stating obviously, was to your stating you can get flashables for twrp for the radio.
Click to expand...
Click to collapse
You misunderstood me I was asking about the vendor image only.
Contains 3D touch?
tarroyo said:
You misunderstood me I was asking about the vendor image only.
Click to expand...
Click to collapse
Nope didn't misunderstand you, I answered why it specifically states in the op to go into the BL. Its under the assumption that you need to update all IMG files.
If you don't need to update your BL or radio using the files he provided. Then yes, you can flash just the vendor image however you want.
Hi,
Some of you all (who are reading this thread) might have seen me somewhere on subforums (either this subforum and/or other devices' subforum). I was previously maintained kernels for some devices (which I discontinued them later due to limited free time and I was no longer have them under my control).
Why I make this public?
I want to collect as many information as possible regarding building arm64 kernels (which I never do it before today), not limited to a developer, but as many as possible (if can)
I want to make my comeback on development by making an attempt to build a custom kernel for Redmi 3. So, I have these prepared:
Configured my netbook as building machine with LXLE.
Downloaded the required kernel source (I'm building for CM-14.1 based ROMs)
Grabbed UBERTC 4.9.4 aarch64
To make things easier without need to edit Makefile everytime I change toolchain, I created a script:
Code:
#!/bin/bash
# Placeholder - my system puts warnings everywhere about locale
export LC_ALL=en_US.UTF-8
# Environment variables
export ARCH=arm64
export CROSS_COMPILE=../../toolchains/aarch64-linux-android-4.9-kernel/bin/aarch64-linux-android-
# Actual command
make -s distclean
make -s cyanogenmod_ido_defconfig
make -s -j4
No problems during compilation process. All forbidden warnings triggered could be bypassed safely. Then, I tested my own build by creating a flashable zip. The process did flawlessly. However, it stucks forever on Mi logo.
Oh ya, I use -O3 optimizations on compilation.
Is there something I should do regarding the unbootable kernel?
I don't want to test every single toolchain out there due to my limited internet quota and my expectations on the same result.
Or... maybe suggestions?
Any help, suggestions, and comments are greatly appreciated. Thank you!
Regards.
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Bump.
Seems like nothing noticed this thread. Should I mention every kernel developers here? I'm out of nowhere.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
BlueFlame4 said:
Hey,
well, your way of doing it looks good. Do you get a last_kmsg probably? Also did you use the correct ramdisk, etc?
Click to expand...
Click to collapse
Nope. It stuck all way at Mi logo. No sign of life at all. Tested on official CM-14.1 and MoKee 7.1.1.
I use the modified AnyKernel2 template (removed Busybox requirement and points to Image.gz instead).
I also tried to download other kernel and use the zip as the base and the output is same.
Sent from my ASUS_Z00A using XDA Labs
ghal17 said:
Excuse me sir, i want ask for help for my battery issue. Why my battery drop to 98% after unplug just a few second?_ I am on mokee and RR rom before and now i already flash it to MIUI but still got like that. Please help me if any solution for that ? sorry for my bad english
Click to expand...
Click to collapse
Hi,
It's better to stay on topic.
You may create your own separate thread so people could assist you better and won't mix up with this one.
Regards.
Sent from my ASUS_Z00A using XDA Labs
So you get a last_kmsg?
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Problem solved.
The culprit is the missing DTB!
When I look into the source once again, there's something missing: DTB file.
The file doesn't exist on arch/arm64/boot/dts, but instead on arch/arm/boot/dts. So, I created a link:
Code:
$ ln -s ../../../arm/boot/dts/msm8939-qrd-wt88509_64.dtb ./arch/arm64/boot/dts/msm8939-qrd-wt88509_64.dtb
Then I enabled CONFIG_BUILD_ARM64_APPENDED_DTB and re-compile kernel (using Google's GCC). Re-test it again (but with a boot.img extracted from MoKee zip unpacked with AIK and finally it booted!
Thank you very much, anyway.
Thread marked as Solved for now.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Hey what did you change from original kernel? New features like hotplug? Is it easy to compile an booting kernel?
Click to expand...
Click to collapse
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
For now, kernel patching.
Unless you have ever compiled one.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Sent from my Redmi 3 using XDA-Developers mobile app
rikusuicide said:
Will you release an costume kernel? CM 13, CM 14.1 or miui 8? Ya need testers?
Click to expand...
Click to collapse
Maybe next year, as things go unpredictable.
EDIT: MIUI won't be supported due to lack of resources required.
I'll ask moderators to close this thread to prevent other type of nonsense discussions.
Sent from my ASUS_Z00A using XDA Labs
Thread closed at OPs request