Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!
snakehater said:
Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!
Click to expand...
Click to collapse
You can't build a closed source rom like NothingOS, they only provided device tree and kernel sources for custom rom development and custom kernel building.
acuicultor said:
You can't build a closed source rom like NothingOS, they only provided device tree and kernel sources for custom rom development and custom kernel building.
Click to expand...
Click to collapse
Alright, but, if I were to compile and flash the kernel sources, what would be missing from the system that is proprietary? Would I even have a UI or would it only be the core kernel?
You answered your question, if you build the kernel source you'll get only the kernel which doesn't have any ui itself, you still missing everything from the rom.
snakehater said:
Alright, but, if I were to compile and flash the kernel sources, what would be missing from the system that is proprietary? Would I even have a UI or would it only be the core kernel?
Click to expand...
Click to collapse
acuicultor said:
You answered your question, if you build the kernel source you'll get only the kernel which doesn't have any ui itself, you still missing everything from the rom.
Click to expand...
Click to collapse
Alright, so basically, this is only a fork from the original android repo, with changes so it runs on the nothing phone, and nothing more?
The kernel just allows the operating system to talk to the hardware so you still need an operating system. Your best bet is to grab a custom ROM if you really want to build from scratch or you can create a magisk mod that customizes the stock ROM.
snakehater said:
Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!
Click to expand...
Click to collapse
Gotta have it working on the OnePlus Nord N200 and I'd be interested
Related
I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta
csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?
gitHub link dead
http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/
Wow man latest news isn t it?? Using Internet Explorer??
And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk
It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?
What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse
dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Nice! What's the status of your efforts?
How to the testing .....
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
F0L said:
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
Click to expand...
Click to collapse
Ok, should have read it better. Are you able to just compile a kernel for testing. Once you have a working one, that would be a good base for updating rom.
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
Any update on this?
Guess this is not going to happen. Just wish I still had the time I used to. I would have had a go my self, as the vanilla kernel is what kills this cool bit of kit.
I managed to get it to a usable state with google play installed, by installing SkyNET. Which tweaks the system on the fly when needed. Helps keep as much memory as possible.
Would the kernel source of the Nokia X help? as it uses the exact same hardware.
I have it downloaded, so if it will help, I can link.
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
F0L said:
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
Click to expand...
Click to collapse
Can you post how you did it? Thanks
@fol I would also be interested in it.
killervette said:
Can you post how you did it? Thanks
Click to expand...
Click to collapse
I used rom kichen to mess with ramdisk (it was very risky as messing with boot image can brick pine). I manually added init.d support. Then repacked it. Luckly it worked fine. I even flashed it to my sons.
I extracted stock system.zip and tweaked it the way I wanted (debloated added apps I owned), then flashed that. As I added init.d, I could use scripts on boot to alter running of pine.
Im currently using Project skynet vr4, which runs very nice.
@fol What is skynet? Do you have a link?
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.
Can i use it for making recovery for moto m
The P9000 has a kernel on github anyway ...
I am going through the build guide on the [AOSP][1] page and found a requirement called "device binaries"
Can anyone tell me how to get binaries for op2 to build a pure AOSP working ROM ?. I am a complete noob in this field so if I require anything device specific (op2) apart from those binaries please do enlighten me.
Also is it possible to get the binaries from lineage repository ?
[1]: https://source.android.com/setup/build/building#obtaining-proprietary-binaries
paulplusx said:
I am going through the build guide on the [AOSP][1] page and found a requirement called "device binaries"
Can anyone tell me how to get binaries for op2 to build a pure AOSP working ROM ?. I am a complete noob in this field so if I require anything device specific (op2) apart from those binaries please do enlighten me.
Also is it possible to get the binaries from lineage repository ?
[1]: https://source.android.com/setup/build/building#obtaining-proprietary-binaries
Click to expand...
Click to collapse
Short answer, you can't
anupritaisno1 said:
Short answer, you can't
Click to expand...
Click to collapse
Can you please elaborate why? Also how do lineage OS devs get those binaries or any other independent aosp developers?
paulplusx said:
Can you please elaborate why? Also how do lineage OS devs get those binaries or any other independent aosp developers?
Click to expand...
Click to collapse
You can get those binaries but you can't boot aosp at all on the op2 without a few commits from lineageos. We need a lot of hacks on op2 to even get Oreo to boot
Also those commits will obviously not work just by simply picking them and you'll have to adapt them for aosp. None of our HALs are ready for being built without the kernel source (aosp doesn't support inline kernel builds)
You can get the binaries from https://github.com/TheMuppets/proprietary_vendor_oneplus
anupritaisno1 said:
You can get those binaries but you can't boot aosp at all on the op2 without a few commits from lineageos. We need a lot of hacks on op2 to even get Oreo to boot
Also those commits will obviously not work just by simply picking them and you'll have to adapt them for aosp. None of our HALs are ready for being built without the kernel source (aosp doesn't support inline kernel builds)
You can get the binaries from https://github.com/TheMuppets/proprietary_vendor_oneplus
Click to expand...
Click to collapse
Wow! a lot of information in a single comment. Is there a way I learn more about OP kernels, roms, hals so that I gain some information at least for a start. Any proper references ? or shall I start by building LOS For op2 without knowing anything and work my way through to the top. Your advice would be helpful in this. I plan to know more about ROMs and build them with customizations... major customizations. Thank you.
paulplusx said:
Wow! a lot of information in a single comment. Is there a way I learn more about OP kernels, roms, hals so that I gain some information at least for a start. Any proper references ? or shall I start by building LOS For op2 without knowing anything and work my way through to the top. Your advice would be helpful in this. I plan to know more about ROMs and build them with customizations... major customizations. Thank you.
Click to expand...
Click to collapse
I'll tell you this. All of the guides you'll ever find are utter nonsense. You have to find your own way to do it and no guide can really help you. There really is no one size fits all guide
anupritaisno1 said:
I'll tell you this. All of the guides you'll ever find are utter nonsense. You have to find your own way to do it and no guide can really help you. There really is no one size fits all guide
Click to expand...
Click to collapse
This is true from what I have seen till now. Guess I'll start building LOS directly as a start (as it is readily available for op2), tweak it little by little and keep learning bits and bytes from everywhere. Thanks