Database Users

4.3 kernel sources released! grab them here

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.

New Kernel Source's

Hi friends. Can you check this kernel source's is real or useless?
https://github.com/nofearnohappy/android_vendor_xiaomi_hermes
https://github.com/lbule/android_device_xiaomi_hermes

This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~

SkiFire13 said:
This isn't a kernel source, it's a device tree for build CyanogenMod
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
ho great so cyanogenmod is comming?

tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.

tailslol said:
ho great so cyanogenmod is comming?
Click to expand...
Click to collapse
For now someone built it but it's very unstable
~ Xiaomi Redmi Note 2 Prime ~

Sad news about this device's kernel source.

is this usefull?
http://forum.xda-developers.com/cro...al/marshmallow-source-codes-mediatek-t3218602

chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that

chris5932 said:
We will see, it is very hard to port when kernel is not given. There are people working on it and doing a very good job!
Sadly, the complete kernel (custom kernel with drivers) was leaked for a short period and a few devs have it.. but they are afraid to use or publish it because they don't want to be sued.
Click to expand...
Click to collapse
Sued? The ones to be sued are mediatek and/or xiaomi for not complying gpl license

adaltavo said:
Wow didnt know that, really the full source kernel was leaked??? And some devs have it D:?. If its true i hope they decide one day to make a nice ROM build, i guess everyone of us would wait for that
Click to expand...
Click to collapse
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).

chris5932 said:
At least someone has it.. I am not so sure on how many have it. Don't be too excited yet, we might not get it (soon). The source can not just be published to the public, the one who does will face some problems.. (see what happened to incomplete source).
Click to expand...
Click to collapse
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen

adaltavo said:
May i ask what happened?. And i know is not that easy, what i meant is that he (or they) could make a nice ROM build with that source, maybe as an anonymus guy or something like that, is not necesary to publish full source code. Our another hope is wait for MTK to release it , but it wont be soon, even could never happen
Click to expand...
Click to collapse
We can build roms ourselfs, just need proper kernel. Just let me say that much: I have a reliable source that told me someone has it. I don't think (anymore) it was leaked to the public ever, all kernel leaked on git were incomplete.

All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.

https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?

tailslol said:
https://github.com/omlet05/MediaTek-HelioX10-Kernel
yay?
Click to expand...
Click to collapse
Check the date and please stop posting same thing again and again. This is the original broken half source that was leaked over 2 months ago now.

I.nfraR.ed said:
All kernel sources I've seen for X10 are not for our device. Another thing is the AOSP sources are very buggy and unfinished.
I finally made progress on my AOSP 5.1 and fixed the slow app launch (maybe you've seen one youtube video posted here - this is my build).
Unfortunately I don't have kernel source for Redmi Note 2 and it is impossible to build a custom kernel, so I'm trying to finish the ROM and will use prebuilt kernel.
If you think it is easy as porting, then you're wrong. Compiling something from source and fixing all bugs is completely different animal.
CM 12.1 also booted, but a lot of work needs to be done there too.
Click to expand...
Click to collapse
What is time to wake? On miui time is long :/ On our last phone (A820) time to wake is much better.
How aboute "tap to wake"? What is result on antutu? When you publish rom?

AOSP boots up and works faster than MIUI and also has much much better ram management, although it would be good if we could make a custom kernel.
Tap to wake normally needs to be supported in kernel, so the answer is "no".
Antutu score is irrelevant, but normally I get about 48K with the basic model. I've seen higher, seen lower.
It also depends on kernel.
Don't forget that for A820 I have a custom optimized kernel.

Hello
When you share rom? How to progress?

Known XDA rule, don't ask for ETA He'll tell us when ready

bumcykcyk said:
Hello
When you share rom? How to progress?
Click to expand...
Click to collapse
It will be shared when it is done.. Ussd/BT working but camera still doesnt

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems

reserved

Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).

drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)

Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.

drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.

Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.

so does that mean that there is a chance for cm12+?

Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?

Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.

Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.

drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.

Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.

Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks

rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.

Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia

Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?

drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.

How to get device binaries to build a working ROM for oneplus 2 with AOSP code ?

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

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