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
Will the i9500 ever get an aokp rom? I would ask developers to please make an aokp rom for it since that is an amazing rom.
If anyone knows any information about this please do but without spamming
Stay Cool
Samsung doesnt release the source code for its exynos processor. So, till now there hasnt been a cyanogenmod rom yet. But it is in progress. First cm, then aokp because aokp is based on cm roms.
Sent from my GT-I9500 using Tapatalk 4 Beta
Hello, everyone.
I have downloaded the kernel source code(HTC One) and android source code, and I have compiled them successfully.
But I don't know how to use the file(zImage, system.img, etc) to make a ROM for my HTC one, is there a step-by-step tutorial to make it?
Thank you.
supplement
I want to know what has CyanogenMod done and how to do it.
If anybody know, may you give me a hand?
Thank you.
Why not built a CM rom for your HTC one? you would learn much from building CM rom.
Only kernel and aosp source are not enough to cook a custom rom, because there are many device specified properity binary files are need (such as ril, graphics, wifi)
Sent from my GT-I9508 using XDA Premium 4 mobile app
trulyliu said:
Why not built a CM rom for your HTC one? you would learn much from building CM rom.
Only kernel and aosp source are not enough to cook a custom rom, because there are many device specified properity binary files are need (such as ril, graphics, wifi)
Sent from my GT-I9508 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
then i wanna know this too. how to build a cm rom for my device? i had an s2
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app
Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk
All I really want is gamma correction and maybe overclocking and U/V.
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!
:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.
I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.
gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.
20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?
I heard that Samsung has released the kernel source files for the exynos. Does that mean that we will get a lot of roms like cyanogenmod and miui? I bought the S6 and I never knew it is hard to make roms for my device. Is it the same case with the S7?
Still the same ....exynos is closed source processor ... They have to release kernel source but not propriety files like drivers etc
Sent from my Nexus 6 using Tapatalk