MerkMod v1 test builds - Samsung Galaxy Nexus

Testers are needed to know that our builds boots on your devices so we can officially release for your devices.
The Rom's based on Omni source but removed various things that aren't needed at the moment.
Please let me know as soon as possible in their thread itself and test builds will be uploaded in
get.MerkMod.com/merk
our source is located at
www.github.com/MerkMod
and we have gerrit as well to keep up with the changes as well
http://review.merkmod.com

Related

[Q] Various Cyanogenmod Roms

Hi,
I'm trying to get a grasp on the various CM7 ROMS built by various folks in the community.
I know Quarx is hosting his builds here:
http://ge.tt/8rDd1nC
Epsylon3 is here:
http://www.defy-cm.net/
KANG builds are here:
cm72-120131.0531-NIGHTLY-Defy (1)
Is there anything I'm missing? Does Maniac release CM7 builds?
I'm building mirrors of all the files for archival purposes and want to make sure I have everything. May eventually release it for the public. I know the serivce Quarx uses to host his files goes over its limit every now and then, so nobody can download.

[Q] When are we going to Taste Lollipop?

Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
well,
just a suggestion
if u just want to know the LP work progress and collect the news/info into this thread,
maybe u should change the title,
cause the title it's little 'demanding'
and for the first start, maybe u could collect the link and put in here,
also give some brief update about the progress, for example
1. Mokee 5.0.1 (link to source thread/info) - status WIP - RIL bugs
and so on...
cheers
naved97 said:
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
Click to expand...
Click to collapse
asking for ETA both explicit or implicit is a no no no... it's top rules in XDA.
if you want it really soon, use Mokee by syhost and try to fix RIL bug using kernel source code.
beside how hard is to see armani-dev commit in CM12 in github?
https://github.com/armani-dev/android_device_xiaomi_armani/commits/cm-12.0
Sorry I didn't get you.?

SlimRom 6.0 for Galaxy S6 - V2 - 12/21/2015

SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
Important links:
slimroms.org - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for S6 from here
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Thanks!
The entire team who helped with the device tree to make this device get CM. Hats off guys. Really appreciate your hard work.
For dual boot, kindly follow this link.
If you have any other queries, kindly see this link for any issues other users face before posting here.
Working and Not working:
Everything as in CM
/* Supported devices */
Galaxy S6 International (SM-G920F/I, zerofltexx)
Galaxy S6 SK (SM-G920S, zeroflteskt)
Galaxy S6 KT (SM-G920K, zerofltektt)
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRom 6.0 for Galaxy S6 , ROM for the Samsung Galaxy S6
Contributors
a2441918
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2015-12-21
Created 2015-12-16
Last Updated 2015-12-23
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
virulentt said:
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
Click to expand...
Click to collapse
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
a2441918 said:
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
Click to expand...
Click to collapse
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Dude you dont get it. According to XDA you should publish a source for the kernel and I did. Go ahead with the link I posted and it will direct you to the kernel source. It is not necessary that the kernel should belong to Slim.
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Nevermind keep it coming
Sent from my SM-G920F using Tapatalk
bio4554 said:
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Click to expand...
Click to collapse
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
a2441918 said:
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
Click to expand...
Click to collapse
It's like steeling the bigmac sauce's receipe to make your own burger restaurant, but saying that you use a different bread.
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
a2441918 said:
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
virulentt said:
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
Click to expand...
Click to collapse
You could have pointed that out in the first post itself rather than us spamming this thread. I will remove the download link and keep this thread closed for now.
virulentt said:
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Click to expand...
Click to collapse
The only source required to be posted by GPLv2 and XDA requirements is kernel source. Also Slim and CM both have posted open permissions to build.
New build up. See OP for download link.
Download Link is dead for me.
a2441918 said:
New build up. See OP for download link.
Click to expand...
Click to collapse
ripv2 said:
Download Link is dead for me.
Click to expand...
Click to collapse
Try it out now mate.
Up and reachable Ill give it a shot!
a2441918 said:
Try it out now mate.
Click to expand...
Click to collapse
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
bigbossclk said:
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
Click to expand...
Click to collapse
I guess its usable. But a different build for S6 Edge is in the works.
Doesnt Boot on my 920f latest recovery clean install with and without gapps. Never finnishing Boot animation.

[REFERENCE] [OOS/CUSTOM] OnePlus 5 kernel source with linux-stable (4.4.162)

Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs
rav101 said:
From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).
nathanchance said:
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).
Click to expand...
Click to collapse
If you're doing the work anyway and it's just a simple push to mailing list then might as well. Others can choose whether to use it or not but at least it's there. :good:
Sent from my OnePlus 5 using XDA Labs
where to download the link?
Gayrat1999 said:
where to download the link?
Click to expand...
Click to collapse
This isn't a kernel you flash, this is something for developers to use in their own work. For example, my kernel Flash already has all of this, which you can flash.
Nice. How about GCC error fixes and wifi stack driver in this base?
neobuddy89 said:
Nice. How about GCC error fixes and wifi stack driver in this base?
Click to expand...
Click to collapse
I toyed with the idea of doing two branches (one for building, one for usability) but decided against it as 1. I want this source to be as plain as possible and 2. It doesn't fully fit with the idea of this project. This purely to help developers get up and running with linux-stable, not a fully fledged custom kernel. I will consider adding the GCC fixes to the usability README though, that could be useful.
You are a true asset to this community!
4.4.103 has been merged in, with conflict notes updated accordingly.
Oh boy oh boy it might be time for a rebase for me
4.4.104 has been merged in, with conflict notes updated accordingly.
I truly apologize to anyone who was tracking the tree because I just force pushed. I decided to update the location and branch name and wanted everything to be consistent. It is now up to date with 4.4.105.
I have updated the OP with the notes and tree location. The new notes are on the staging branch right now, they will be merged into master once everything is finalized.
I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?
zainifame said:
I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?
Click to expand...
Click to collapse
Most likely yes. For the future, this thread is geared towards the generic CAF trees (msm-3.18 and msm-4.4). Feel free to ask me anything over there.
4.4.106 has been merged in (conflict notes).
4.4.107 has been merged in.
4.4.108 has been merged in.
4.4.109 has been merged in (conflict notes).
4.4.110 has been merged in (conflict notes).

[REFERENCE] Pixel 2 kernel source with linux-stable (4.4.162)

Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.116 and the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/wahoo
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
4.4.103 has been merged in.
This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.
Telperion said:
This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.
Click to expand...
Click to collapse
It depends. Longer DPs like the initial release of a new major number (7.0, 8.0, etc) typically get kernel source within a month of the new DP version dropping. Smaller DPs usually don't get source until release (7.1 is the only other small DP that has ever happened so not much history).
:good::good::good:
I dont mean to go too offtopic here, but does that apply to the android source codes too? I meam does it usualy take that long for them to release the sources? I am guessing we still dont have any custom roms because the sources were not released by google yet?
4.4.104 has been merged in, with conflict notes updated accordingly.
The repo location has changed (new link is in the OP).
Additionally, an 8.1 branch has been created. Google went from 4.4.56 to 4.4.88 so the branch was redone to avoid conflicts and go with Google's resolution. The notes have been updated as well. Happy kerneling!
4.4.106 has been merged in (conflict notes).
4.4.107 has been merged in.
4.4.108 has been merged in.
4.4.109 has been merged in (conflict notes).
4.4.110 has been merged in (conflict notes).
4.4.111 has been merged in.
Just as a heads up, I started school on Monday so while the updates will still continue, they may not be as timely as they have in the past, especially if there are conflicts that I need to document.
4.4.112 has been merged in (conflict notes).
I used this conflict in my video talking about thinking through linux-stable conflicts, check it out! https://www.youtube.com/watch?v=yWvU8_0O66A
4.4.113 has been merged in (conflict notes).
4.4.114 has been merged in.
4.4.115 has been merged in (conflict notes).
4.4.116 has been merged in.
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy

Categories

Resources