Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.
erid2thed said:
Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.
Click to expand...
Click to collapse
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4
oldblue910 said:
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Thanks
BTW - i made a kernel for 4.4 roms on the m919/i9505g
dont have enough posts to post it here, but uploading source to github.
Been on it for a few days, and I like
MODS: can i post kernel in this section until I get enough posts? or do i need to wait before I post kernel?
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 have seen that omni rom is not supporting legacy devices like galaxy s,etc..
why is it so....
why there are not included in their mainfesto??
will they include these devices in future...
anurag.dev1512 said:
i have seen that omni rom is not supporting legacy devices like galaxy s,etc..
why is it so....
why there are not included in their mainfesto??
will they include these devices in future...
Click to expand...
Click to collapse
So the thing is, omni as a whole does support legacy devices. However developers may not have legacy devices as a high priority, so support for them will be slow.
They will be added in the future if a developer does bring them up
Sent from my Nexus 7 using Tapatalk
ok.....just answer one more thing..
cybojenix said:
So the thing is, omni as a whole does support legacy devices. However developers may not have legacy devices as a high priority, so support for them will be slow.
They will be added in the future if a developer does bring them up
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
if any other developer brings omni to legacy device by himself will that get treated as official rom from omni developer side...
anurag.dev1512 said:
if any other developer brings omni to legacy device by himself will that get treated as official rom from omni developer side...
Click to expand...
Click to collapse
Amy developer can contribute any patch they/feel suitable to omni, including legacy patches, as long as the quality is to a good standard, it works, and it doesn't break anything else
Sent from my Nexus 7 using Tapatalk
...???
cybojenix said:
Amy developer can contribute any patch they/feel suitable to omni, including legacy patches, as long as the quality is to a good standard, it works, and it doesn't break anything else
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i m asking that now omni is not supporting legacy devices if any other non-omni developer creates rom for legacy device then will that be recognised as official rom from omni..
If they are experienced enough to maintain it, then I guess yes it will be official.
However it is my opinion that many people who "bring up" a rom on a device are not experienced enough to be a maintainer for a team such as omni or cyanogenmod.
Sent from my Nexus 7 using Tapatalk
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Support Samsung Galaxy S2 I9100
tilal6991 said:
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Click to expand...
Click to collapse
Can we just make a poll or something to ask to support Samsung Galaxy S2 I9100.
tilal6991 said:
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Click to expand...
Click to collapse
So Why i9100(not g version) doesn't have official support? Below is list of unofficial builds:
http://forum.xda-developers.com/showthread.php?t=2533946
http://forum.xda-developers.com/showthread.php?t=2494127
Karls0 said:
So Why i9100(not g version) doesn't have official support? Below is list of unofficial builds:
http://forum.xda-developers.com/showthread.php?t=2533946
http://forum.xda-developers.com/showthread.php?t=2494127
Click to expand...
Click to collapse
Encourage your dev to push his changes to gerrit so we can get official builds set up. It's up to him though.
http://forum.xda-developers.com/showpost.php?p=47606886&postcount=79
@nims11 posted link to his github in "Developers - Merging Your Working Device" thread. Something more is needed? I'm not dev and i don't know how exactly gerrit work. Can you add i9100 to gerrit basing on it or something else is needed?
Edit:
I asked both i9100 developers of OmniRom - they can't do anything as long as admin doesn't create directory for i9100 in OmniRom github. Maybe someone with permission to do this will read this post
Karls0 said:
http://forum.xda-developers.com/showpost.php?p=47606886&postcount=79
@nims11 posted link to his github in "Developers - Merging Your Working Device" thread. Something more is needed? I'm not dev and i don't know how exactly gerrit work. Can you add i9100 to gerrit basing on it or something else is needed?
Edit:
I asked both i9100 developers of OmniRom - they can't do anything as long as admin doesn't create directory for i9100 in OmniRom github. Maybe someone with permission to do this will read this post
Click to expand...
Click to collapse
It took a while to get i9100 forked due to the fact that it was a holiday for many of us.
It's forked and the 4.4 bringup patches are on gerrit for review. Rather than forking one of the trees out there, we started from the same origin point as n7000/i777 as I want the commit history for those devices to be similar.
Right now, the holdup for i9100 is that no one who actually owns the device and knows how to apply/review Gerrit patches has reviewed and tested them yet.
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Oh Gr8 news ! Hope we could get custom kernel on OPO soon
Sent from my One using XDA Premium 4 mobile app
I am hoping we get one soon also.
Sent from my One using Tapatalk
SferaDev said:
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Click to expand...
Click to collapse
Mind putting together the flashable zip of the stock kernel so that users who go custom kernel flashing (Franco for now) can fall back to the stock kernel?
A flashable .zip would be great
@SferaDev Thanks for this, I will be using this to build a kernel for our devices
Gamma control is out:
0f98e789af8c12ce3687cbe4515b429aa1e031a3 video: mdss: Add predefined gamma selection
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
DrDaxxy said:
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
Click to expand...
Click to collapse
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
SferaDev said:
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
Click to expand...
Click to collapse
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
DrDaxxy said:
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
Click to expand...
Click to collapse
I haven't faced ANY kernel that doesn't work...
A flashable zip will be great! Can any expert help on this?
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
djsynth said:
Hey guys was just wondering if there any developers who are working on some new ROMS for our MXP as it seems very quiet in the development sections of the forums, couple of variations of stock rom and that's pretty much it.
Was expecting for development to pick up after the MM but its been VERY quiet.
Not a complaint just wondering if there are things going on behind the curtains like development being done or some CM13 or anything along those lines.
Click to expand...
Click to collapse
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
nimrodsv said:
Having MM OTA out is not enough.
Not much can be done until Motorola will release the kernel source
Click to expand...
Click to collapse
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
djsynth said:
Any idea if its going to get released and if yes then when ?
and out of self interest what does the kernel source enable developers to do ?
Click to expand...
Click to collapse
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
nimrodsv said:
It's totally depended on Motorola.
The source enable developers to release AOSP roms and custom kernels.
Click to expand...
Click to collapse
Has Motorola been known to release kernel sources before for previous flagships ?
Would love for them to release the binaries and device tree for AOSP builds...
djsynth said:
Has Motorola been known to release kernel sources before for previous flagships ?
Click to expand...
Click to collapse
They are required to release any changes to the kernel they have made due to the GPL license that the linux kernel is protected by. so its not a matter of if but when.
MM and now kernel source released, and still, slow as hell. Sucks. I thought this phone would be one of the most active in development, was i wrong.
Sent from my XT1575 using Tapatalk
I'm on retail Asia variant which leaves me with 1 rom. And I can't even get mm for my variant let alone custom roms.
What happened to this phone?
Please go to http://forum.xda-developers.com/moto-x-style/help/happened-to-phone-t3283551
to continue this topic if possible, thank you