SO now that the source for ICS is out I have a question. Please excuse my ignorance as I am still trying to learn a few things.
The main question is if a kernel can be made for the note directly from the source and then the current modem files be flashed to it to make it work or do we have to wait for Samsung to release a version built of the source with custom drivers. I guess I am just not sure if the source contains drivers for some hardware or if it is all custom added on top of the rom.
Related
Hey guys,
As a software developer myself I feel a bit embarrassed that I need to ask this, but I really can't think of the answer myself. Here goes:
Why do we always need the latest sources from Samsung to be able to build an AOSP rom?
The way I see it, unless the kernel's internal APIs that Samsung's device drivers use have changed dramatically between, say, Froyo and Gingerbread, wouldn't it be possible to simply check out AOSP, paste the driver source files from Froyo into the appropriate folder in the kernel tree, and compile? Even if the kernel's internal APIs have changed a bit, they would be minor and well documented changes, so it should only be a moderately difficult task to fix the Froyo sources to work with Gingerbread. Sure, the drivers would still be "Froyo quality," but they seem to work pretty well to me. I'd be happy with a Gingerbread AOSP build w/ Froyo drivers.
It's kind of like what VMWare's tools do in a Linux guest OS - if you update your distro's kernel, the ABI is broken and you just recompile the modules. Same VMWare source code, different kernel, but it works.
Ok I admit that this might be a silly question, but here it goes:
In the froyo open source kernel from samsung open source release center, there is a file called 'drivers'. Are these the drivers from the phone's hardware? If that's the case then it is possible to compile the 2.3 kernel based on those drivers (provided that you download the 2.3 kernel from google).
We have new source from Samsung
I hope to resolved freeze device and bootloop
http://opensource.samsung.com/
AW: New Kernal Source Update2 i9100_JB
Bump for interest
Greetz
Alliance6.1|Dorimanx7.47|i9100¬Tapa2
Good news?
Can anybody confirm if this is what the developers require to keep i9100 alive?
source kernel international is out today for i9100 JB
http://opensource.samsung.com/
Well, they released the JB sources, yeah. The more important question: Are the driver sources for the proprietary hardware in there?
i hope it's the thing that devs need
For anyone playing with the new source, the cypress driver is missing from /drivers/input/keyboard. I re-added it and can now build a working kernel. I emailed sammy asking if it was a simple mistake :silly:
Here's the patch:
https://github.com/jeboo/kernel_JB_...ade672a810b9ac93eb5ff94fced3471e524048e.patch
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
https://github.com/DonkeyCoyote
So for my i9100 (Samsung SII (intl)) I had to add
Code:
<project path="vendor/samsung" name="DonkeyCoyote/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
inside the
Code:
<manifest> ... </manifest>
tags in
Code:
.repo/local_manifests/local_manifest.xml
FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
In general, the blobs are first obtained by pulling all of the contents of /system from a device running stock.
Sometimes the blob archive winds up being a bit of mix-and-match of stuff from multiple sources...
It's a real mess and unfortunately there is no way to simplify the mess without raising some potential legal issues, as blobs are a bit of a grey area here.
FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers#grouper
Here are all the stock blobs, Extract to your build folder then run the scripts in bash
They will then after accepting the license install to the correct vendor location.
( i just learned this last week )
Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?
barkley128 said:
Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?
Click to expand...
Click to collapse
In general, if you're doing the bringup for a given device, you pull the blobs from a stock firmware for that device, then try to integrate them. Sometimes in the end you wind up grabbing blobs from another device (such as Adreno GPU blobs from a Nexus or a newer device with same chipset), but people always start with the stock firmware and go from there.
Incase anyone is looking for the same
See this thread here. http://forum.xda-developers.com/showthread.php?t=2794413 :good:
Hello,
For those interested in the original kernel source code for the SM-T813 :
As I am learning how to make ports for Android, I am trying to train on the original sources of the Linux kernel for the SM-T813.
After several weeks of research, I couldn't find the origin of the different kernel repositories.
Also on https://opensource.samsung.com, it was impossible to find the sources. So I contact them at the end of January to have an access to this sources...
... And they are now available !
You can download them on https://opensource.samsung.com (search SM-T813 at mobile phone on release center) or on my repository at https://github.com/Akipe/android_kernel_samsung_gts210vewifi_original_samsung
It is based on the T813XXS2BTK3 firmware with Android 7 Nougat.
I will see to ask for sources of similar tablets.
Will this help with porting new Adnoid version to these tablets?
Pawel_ said:
Will this help with porting new Adnoid version to these tablets?
Click to expand...
Click to collapse
I don't think so,
Kernel sources for this tablet already exist, and are ported to newer versions.
It is more useful for those who want start from scratch, and want to inspect the unmodified source code.
But my goal would be to successfully create from scratch for the SM-T813 LineageOS 14.1 (Android 7); and then try to move to the latest versions.
Since I am a beginner, I still have a lot to learn, and I don't have much time, so we will see