Database Users

[REQUEST] N8000 Kernel Source

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

[Kernel][Linaro] Stock KK kernel for Falcon

This is a near stock falcon 4.4.4 kernel built with the latest Linaro toolchain (Linaro GCC 4.9-2014.12) for all of those who prefer stock kernels and absolutely need those 10 extra points in Antutu
Differences from stock are just a few Cortex-A7 optimizations, F2FS patches from mainline 3.18 and linaro toolchain.
All credit goes to @bedalus, who started his kernel thread for Peregrine, fixed all the small bugs that made compiling with newer Linaro toolchains impossible and cherry picked all those F2FS patches.
Sources and tools used:
MotorolaMobilityLLC/kernel-msm
MotorolaMobilityLLC/vendor-qcom-opensource-wlan-prima
bedalus' patches
Christopher83's Linaro Toolchain
My repo, where all sources are merged
Changelog:
falcon_stock_4.4.4_linaro_4.9.3.zip
- stock kernel
- added necessary patches to make it compile with linaro
- some Cortex-A7 optimizations
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
The zip can be flashed with TWRP or CWM. Not flashable through fastboot.

Thanks @knizmi. I think stock users will appreciate this

Anyone tested? How the battery?
Wysłane z MOTO G

Dizzyrul3z said:
Anyone tested? How the battery?
Click to expand...
Click to collapse
This is the stock kernel, so the batttery is as good as with stock kernel (you really can´t make it much better in any way). These screenshots are taken after some 7 hours of sleep.

Works pretty good on XT1031. Nice work! Any chance you could make a build with the kexec hardboot patch to use it with multirom?

I immediately noticed a performance improvement after flashing this kernel. Thanks!

Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
This is my preferred way to grab commits. Did you add my repo as a remote?

Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app

bedalus said:
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
Click to expand...
Click to collapse
Thanks a bunch, this should really make merging those patches easy!
bedalus said:
This is my preferred way to grab commits. Did you add my repo as a remote?
Click to expand...
Click to collapse
I have added your repo as a remote now. I was fighting with git last week quite a bit (never used that devil's tool before), but now I think I am getting used to it. For my first build I've just "patched" those files with gedit...

syrkles said:
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up, but compiling someone else's sources doesn't make me a dev

New version uploaded.
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
Thanks @bedalus.

amarc78 said:
Any chance you could make a build with the kexec hardboot patch to use it with multirom?
Click to expand...
Click to collapse
Sorry, the aim of this is to stay as close to stock as possible and only add optimizations/update drivers.

knizmi said:
For my first build I've just "patched" those files with gedit...
Click to expand...
Click to collapse
If you've got my repo as a remote you should be able to see my commits with
Code:
git log -- bedalus/moggy
depending on what you named your remote.
Once you see what commits you want, copy their hashes (the long string of letters/numbers) then
Code:
git cherry-pick *hash*
If there's a problem with the cherry-pick you can fix it manually with
Code:
git mergetool
or abort with [git cherry-pick --abort[/code]
I've installed meld as my mergetool. I'm using a debian derivative so I did
Code:
sudo apt-get install meld
That's a pretty comprehensive quick-start guide to cherry-picking from any remotes you've fetched.

Cannot downgrade to default stock.
can you make a zip with libs to go back.

everb00b said:
Cannot downgrade to default stock.
can you make a zip with libs to go back.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=2649763

That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.

amarc78 said:
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
Click to expand...
Click to collapse
You mean in the thread I've posted. I've thought that too at the beginning, but they are there separately, look for Stock Kernel Modules: [XT1032] - 4.4.2 | 4.4.3 | 4.4.4 | 4.4.4 (GPE) | 5.0.1 (GPE) | [XT1033] (Dual-SIM) - 4.4.4. You just have to flash two zips instead of one.

Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Edit: never mind. They look the same.

amarc78 said:
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Click to expand...
Click to collapse
Not sure, you can try. If there is a problem you can always reflash stock /system, backup those modules and perhaps send them to @lost101

bedalus said:
If you've got my repo as a remote you should be able to see my commits
Click to expand...
Click to collapse
Thank you for the info again. You are very helpful.
Do I understand it correctly that I need to fetch your repo before I can start cherry-picking? Searching around the internet , it looks like it. I may give it a try one day, but for now I will stick with git am, which seems like the perfect tool to pick single commits from many repos.

Neptune Pine - Custom Rom Infomation and Testing

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?

Is this a source code for K8?

On this link there is source code for K8 maybe for K10 I didn't search for it (use find in page). When download it inside there is 3 files:
K350_Marshmalow_Android.tar.gz
K350_Marshmalow_Kernel.tar.gz
K350_README.txt
So I wonder is this what we need to build custom ROMs if not than what the hell is this?

This files for build stock firmware. But you can use the kernel source for build custom kernel.

Singular777 said:
This files for build stock firmware. But you can use the kernel source for build custom kernel.
Click to expand...
Click to collapse
Yeah, so I can use this kernel source to build kernel for let's say Lineage or any custom ROM?

Professor Woland said:
Yeah, so I can use this kernel source to build kernel for let's say Lineage or any custom ROM?
Click to expand...
Click to collapse
Yes, but you can use the stock kernel for build LineageOS or any custom ROM

Singular777 said:
Yes, but you can use the stock kernel for build LineageOS or any custom ROM
Click to expand...
Click to collapse
Jus one more question, can I get a device tree from this? Is it maybe included somwhere in theese files?

Professor Woland said:
Jus one more question, can I get a device tree from this? Is it maybe included somwhere in theese files?
Click to expand...
Click to collapse
No, it must be done by yourself or look something like

Question Build Nothing OS source code?

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