Hi Lads,
Past few days im trying to add the ath9k module to a kernel.
I took the emotion kernel but when i started to make the kernel i constantly receiving errors.
I googled till my eyes burned out of my skull but got no solution. Probably im doing something wrong
Im looking for someone who can build the kernel easily including the ath9k driver.
My purpose is to use Kali Nethunter with the TP-Link WL722N adapter on the Note Edge N915F.
Im so desperate that i want to pay for it. Or maybe a game on steam :highfive:
Please help me out!
Greetings.
Stefjoe
Stefjoe,
I also saw your pm. I know now that you would like that module added to the tblte kernel. Kali Nethunter is not a rom, it is an overlay of sorts. Essentially a chrooted Linux distribution running over the top of your Android phone.
Kali only supports stock roms, or some "CyanogenMod variants", so I could add this to the AOKP kernel for you, but I cannot guarantee that you will have everything you need for this to work. For instance, you are going to need packet injection, module loading and unloading, force modules, etc., etc., much more than just the one item you requested. The note edge is not on the list of supported devices for a reason, it takes much dedication and effort to set it up properly. You would also need to build your custom port of Kali to go on your system. (Unless I am mistaken, no one has made one for the Note Edge yet.)
So, have you already built a working port of kali for your phone?
I say this in the kindest of regards, but if you cannot build the kernel, can you build the kali image?
As a side note, all the tools in Kali Linux are freely available, and you can download them to your phone right now, just not in the glorified package. Having Kali is like having a toolbox. Having a tool box does not make one a mechanic. Having Kali does not make one a pentester, or cacker (unethical hacker) if you are aiming for that.
I am not opposed to you having Kali, I've used it before myself (not on a phone), but in the end, I found Debian to be just as useful, downloading the tools that actually helped me in my job/tasks.
I am just curious if you have already created the kali image you need for the Note Edge phone. In theory, if the only thing you need is a kernel with the above, then it should work with your current kernel, just without that feature. If you have not even made the image yet, then I suspect that you are going to need a lot more than what you asked for.
I hope that makes sense.
AlaskaLinuxUser said:
Stefjoe,
I also saw your pm. I know now that you would like that module added to the tblte kernel. Kali Nethunter is not a rom, it is an overlay of sorts. Essentially a chrooted Linux distribution running over the top of your Android phone.
Kali only supports stock roms, or some "CyanogenMod variants", so I could add this to the AOKP kernel for you, but I cannot guarantee that you will have everything you need for this to work. For instance, you are going to need packet injection, module loading and unloading, force modules, etc., etc., much more than just the one item you requested. The note edge is not on the list of supported devices for a reason, it takes much dedication and effort to set it up properly. You would also need to build your custom port of Kali to go on your system. (Unless I am mistaken, no one has made one for the Note Edge yet.)
So, have you already built a working port of kali for your phone?
I say this in the kindest of regards, but if you cannot build the kernel, can you build the kali image?
As a side note, all the tools in Kali Linux are freely available, and you can download them to your phone right now, just not in the glorified package. Having Kali is like having a toolbox. Having a tool box does not make one a mechanic. Having Kali does not make one a pentester, or cacker (unethical hacker) if you are aiming for that.
I am not opposed to you having Kali, I've used it before myself (not on a phone), but in the end, I found Debian to be just as useful, downloading the tools that actually helped me in my job/tasks.
I am just curious if you have already created the kali image you need for the Note Edge phone. In theory, if the only thing you need is a kernel with the above, then it should work with your current kernel, just without that feature. If you have not even made the image yet, then I suspect that you are going to need a lot more than what you asked for.
I hope that makes sense.
Click to expand...
Click to collapse
Thanks for your reply again! I kinda ported the Nethunter to Note Edge with help from this video on YT ; /watch?v=jhLBJJwB88k
Everything works fine but only the TP-Link WL722N is not working because the kernel does not have this module installed. The adapter takes care of the injection so no worries i guess. I sended u a PM.
I am a certified hacker and i know what Kali Linux is but only missing this tool and it could make my work a lot easier. So i really appreciate if u can do this for me man. Endless thanking
Greetings
stefjoe said:
Thanks for your reply again! I kinda ported the Nethunter to Note Edge with help from this video on YT ; /watch?v=jhLBJJwB88k
Everything works fine but only the TP-Link WL722N is not working because the kernel does not have this module installed. The adapter takes care of the injection so no worries i guess. I sended u a PM.
I am a certified hacker and i know what Kali Linux is but only missing this tool and it could make my work a lot easier. So i really appreciate if u can do this for me man. Endless thanking
Greetings
Click to expand...
Click to collapse
Stefjoe,
I see from your PM that you are not requesting my AKLU kernel, but the TW Emotion Kernel. I can't do that for you.
To build the kernel you need the right source, the source code for the kernel has been updated since r17 ( I think it is r2X? now). That means rolling back through the commits to find the time it was built and working properly and getting that source. It is not as simple as just going straight back to r17, the r17 version you may be using may be anywhere in the commits between r17 and r18.
Then we would need the exact toolchain he/she was building with. He says Linaro 5.1, but which one, 5.1, 5.1.1, 5.1.8? There are several.
Also, I do not build TW kernels. I only build AOSP kernels. I also don't usually build off of someone else's work. I was under the impression you wanted me to add that module to my AKLU kernel instead.
To get that specific kernel built the way you want, I recommend that you ask @Pafcholini to do that for you, since he made it originally.
If you want, I can add that module to my AKLU kernel for you, but I know the rest of the needed kernel items are in there that you need (packet injecting, force module loading, etc.) so I doubt it will work for you. You would also have to switch to AOKP, which may or may not work with your porting guide.
Sorry, but after looking at your full request, I don't think I can help you with what you need.
Related
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
fllash said:
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
Click to expand...
Click to collapse
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Mekrel said:
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Click to expand...
Click to collapse
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
fllash said:
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
Click to expand...
Click to collapse
A git is a repository for source code, developers upload their source code there and can commit changes. The commit can allow descriptions of what was changed and also details the files changed.
The git system allows other people to add to the source if they have permission, or allows others to read the changes and download the source code.
Git links are usually posted by people who release software, as Android is GPL licensed so people have to release their source code if they're distributing their work.
Editing the kernel, take a look into the git and the commits and it will show you which files were changed and how exactly they were changed. That will give you the best understanding.
UV/OC is done by changing the acpu table in the architectures files and changing the minimum/maximum voltage figures in the board_bravo.c file.
The Cyanogen kernels are not Sense kernels no, it's a modified Google Kernel.
Thanks for the explanation. I followed the guide and built the rom, and it works (always a plus )
Now, the next thing is the kernel. How do I build a kernel with the CM tweaks integrated? I understand that all i would be doing is rebuilding the same one that is already installed, but im doing it to learn.
So, if i synced the GIT, does that include the CyanogenMOD kernel source? If it does, where is it and how do i rebuild it. If not, where do i find it?
Thanks,
Josh.
Till now, I still haven't find the isofs.ko and udf.ko for Kernel 2.6.36.4.
I want to mount ISO image files in Android 3.1.
Can anyone compile them for me? Thanks a lot!
My tablet is Samsung P7500
Follow is a detail descriptions of my system kernel.
htt p ://droidbasement.com/db-blog/?p=2395
10.1 3G, Touchwiz UX (HC 3.1 (stock); GT-P7500):
boot-cm_2636.4_p4_ux-oc-xtra-vfpv3-d16_fp-112011.zip
No one can help me
I will try to learn uburtn，....
Johnyea said:
No one can help me
I will try to learn uburtn，....
Click to expand...
Click to collapse
Ubuntu is not that hard to learn, and there are many tutorials for how to compile the Linux kernel, let alone the Android kernel, I would suggest however starting with tutorials to compile a normal linux kernel for your Ubuntu system first, then when you have a good understanding of how to compile it, go ahead and then build an Android kernel with the modules your requesting. Now I'm not sure if the Android kernel configuration supports these modules since Android itself really doesn't use any CD/DVD file systems but nothing is impossible I suppose.
Yes, I got it.
I compiled the modules what I need.
And thery are working fine for my Tablet.
Johnyea said:
Yes, I got it.
I compiled the modules what I need.
And thery are working fine for my Tablet.
Click to expand...
Click to collapse
I'm glad you got it working, congrats
Sent from my LS670 using XDA
First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book
hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD
My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?
hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
Hello, I decided to come up with a project that aims to port higher Linux versions. When I say higher Linux versions, I mean those that are Linux 3.5 and up. The goal is to port Linux major updates as high as I can, but the main priorities are one that are LTS like Linux 3.10, 3.14 or even 3.18.
Only Android 7 will work on non-LTS versions. Oreo/pie and Android 10 support will be added only on LTS versions to lessen the conflicts when merging non-LTS versions.
What works:
Boots
Battery
Charger
Touchscreen
Display
USB
Sound
Buttons
Deep sleep
Camera
Video playback
Fingerprint
The rest of the sensors
WiFi
Bluetooth (works on Linux 3.7 and up)
Internet connection
Anything else I can't mention
What doesn't work:
You tell me
Drivers that can't be updated (yet) due to them being heavily modified by CAF and Samsung:
USB
Sound
MMC
Newer versions are more stable than the other due to the fact that I fix more bugs with every update.
The highest version as of now is Linux 3.8. I can only merge major updates during weekends due to my work.
Sources:
Linux 3.5
Linux 3.6
Linux 3.7
Linux 3.8
Linux 3.9
Feel free to open up issues and submit pull requests
It is highly recommended to delete mpdecision from /system/bin/ before flashing
Reserved
i don't understand what is this, is there some wiki i can read?
saikyom said:
i don't understand what is this, is there some wiki i can read?
Click to expand...
Click to collapse
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
darrendude1 said:
These are kernel updates. Our device comes with Linux 3.4, but I've managed to update that up to 3.8
what are the benefits of updated kernel..cheers
Sent from my Unknown unknown using XDA Labs
Click to expand...
Click to collapse
Read these:
https://kernelnewbies.org/Linux_3.5
https://kernelnewbies.org/Linux_3.6
https://kernelnewbies.org/Linux_3.7
https://kernelnewbies.org/Linux_3.8
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
godofsalt said:
@pascua28
What a Huge Task! As Well as a Pain on the Ares!
Now, I do Have a few Q's for you.
1 IS this "Kernel Patch" Just for your beloved Galaxy S5's ?
2 Will this be for the "Basic" Kernel in an OS (e.g. LineageOS) ?
3 Wouldn't this hurt some of the "Custom Kernels" that we currently have and use?
And of course I must ask, how far do you intend to take this (e.g up and coming 5.7 ) ?
That Said, I am in! I have downloaded all the Kernels . Mostly to compare your changes. Have also saved your GitHub page.
Am wondering though, With some of these "Custom" Kernels..... Wouldn't we see much faster , smoother , and hopefully more Darn Battery with some of the Tweaks that we have with them? Or at least with some kernel manager?
Or, would these break those Kernels (now thinking about it)?
Certainly will be watching this!
Again , this is a huge task to undertake! Sure would love to see 4.1 and above for our phones. Maybe with Your updated Kernel, we could really see some major changes with our phones.... Plus, hopefully easier to Port into the likes of Android 10! ... or Of course jumping a bit here, and a bit positive, but Android 11 !
Good luck sir
Click to expand...
Click to collapse
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
pascua28 said:
1. This is a full Linux upgrade. Nobody has ever done that to our beloved S5 cause it's a truckload of work
2. Uhm, I don't know. LineageOS is very strict on what kernel base to use, but I may propose to use this as a base when I reach 3.10
3. This project might be a good base for custom kernels since it is more updated and I will use this base too for my future custom kernels
4. As far as I can and as long as it works. Of course, I don't wanna die yet by not going too far.
Certainly, it won't break any kernel managers. You can even clone the latest source and add some custom features. It's up to you, but right now, in the process of upgrading, I won't be adding any custom features
Regards
Click to expand...
Click to collapse
Well, Thank You. for the reply, as well as, all the information.
YES your project is a HUGE amount of work. Good guess, IS , you seem to want to take on this challenge! Good for you...
Yes, I do intend to really follow your project. Really looking forward to the great results that I hope we (you) can achieve !
Awesome...
Thanks
Hi guys! Linux 3.9 is up!
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
shmizan said:
this is amazing work!
thank you very much for it.. I bet it's ugly as hell, but you learn a lot..
I'm patiently waiting for 3.10.0 since that's required by docker (running debian using Linux Deploy)
Click to expand...
Click to collapse
Yeah, very tedious and requires a lot of skill
This is huge. Thank you for doing this, I will definitely be following this
pascua28 said:
Yeah, very tedious and requires a lot of skill
Click to expand...
Click to collapse
Yes, as well as time, the correct machine and layout....
Plus I believe it requires most patience than what I have!
BTW... This is great work, have not seen any issues on my S5..... (yet, but don't think that will happen though)
Thank you!
Sent from my Galaxy S5 using XDA Labs
Is this working on 5+ (katcc6)?
robla1000 said:
Is this working on 5+ (katcc6)?
Click to expand...
Click to collapse
Nope, S5 only. And at this point klte only until @pascua28 is finished bringing the kernel up to 3.10
Only working properly is klte, for now. Other variants might work but with bugs. Will fix for other variants when we get to 3.10
3.5 to 3.9 didn't work for me,I have klte
didn't work?
I ran 3.8 for weeks without any issues.. what exactly does not work?
many reboot ,i couldn't use
vlad3647 said:
many reboot ,i couldn't use
Click to expand...
Click to collapse
It's not for higher Android version.. If you have Android 9 or 10 then wait for version 3.10
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release