Post moved to:
[Kernel] [AOSP] Sandwich Kernel for J700F/H/M
Sandwich Kernel for J7 2015:- This kernel works in android 9 to 12L roms, in J700F/H/M only, we will not take any responsibility if anything goes wrong. Introduction:- A custom kernel made for J7 2015 AOSP roms. Sandwich kernel is based on...
forum.xda-developers.com
whats the difference :troll:
i was already using the A10 sandwich kernel on 12L
NullCode said:
whats the difference :troll:
i was already using the A10 sandwich kernel on 12L
Click to expand...
Click to collapse
The difference can be seen in the source code commit history, simple
Why don't u see commit history bro...u may get the differences...
***Moderator Announcement***
Keep the public arguments to a minimum. Settle your conflicts via PM; if you are unable to come to a peaceful resolution, seek arbitration via the moderator staff.
All members are reminded that you are expected to adhere to the XDA Forum Rules; flaming will not be tolerated.
Further, you are advised to read the Development Post Rules and the XDA GPL Policy.
Compliance is mandatory. Violations will result in administrative action.
Thread closed per OP request.
Related
I've seen ROMs like Paranoid Android who only have 5 or 6 official team members listed on their website and they only support nexus devices and the Opposed Find5.....but then I see ROMs that say "Official Paranoid Android" for the note 2 or w/e phone....
Does "official" mean that its compiled from source no matter who makes it and an unofficial ROM or Port is just that....unofficial?
I mean I've seen this for a lot of ROMs not just Paranoid
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Dubbsy said:
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply man
Dubbsy said:
Official is compiled and maintained by a team member or maintainer from the group who developed the ROM in general.
Unofficial is compiled and maintained by whoever decided to build it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
hi ,which one is better and why?
or which one do u preffer? n why?
ahmad990 said:
hi ,which one is better and why?
or which one do u preffer? n why?
Click to expand...
Click to collapse
Official is better to go with if possible, as know when the source is updated and will push out updates since they're assigned to it. Unofficial just may be behind on updates but that's really it.
Sent from Black<3's I337 running Hyperdrive
DeadlySin9 said:
Official is better to go with if possible, as know when the source is updated and will push out updates since they're assigned to it. Unofficial just may be behind on updates but that's really it.
Sent from Black<3's I337 running Hyperdrive
Click to expand...
Click to collapse
Didnt get .Sorry
Hii..I have to ask that is there any risk in installing unofficial custom ROMs like AICP for lenovo k3 note
What is the difference between official build and weekly build
Vinay chintu said:
What is the difference between official build and weekly build
Click to expand...
Click to collapse
Your confusing the Release Type and the Build Type...
Hello Everyone!
I, personally, have always defined the differences of the different Firmware ROM's as follows:
RELEASE TYPES
OFFICIAL = From Original Development and signed off by one or more of the Original Developer(s).
UNOFFICIAL = A Development based upon the Original Development by a third party developer.[/B]
BUILD TYPES
EXPERIMENTAL = Typically an Experimental build is a tool used to aid in Migrating/Transitioning from an older Android version to a newer one.
NIGHTLY/WEEKLY = Are builds that's automated by software and are released on a daily/weekly basis (in most cases they are approximate timing). In Most (but, not All) cases there are no/little real human interaction in this. Typically an automated process for the release.
*** One example of the automated process is If you look at Open GApps... This is typically all automated with human interaction being little to none (the human interaction is usually on a case-by-case basis when the need calls for it).
SNAPSHOT = (aka STABLE) This is typically when an actual individual has reviewed and deemed that everything within it is considered "feature-complete" and "reliable". In most cases, these releases are considered being without bugs.
*** I specified "in most cases" because I've seen those releases with a missed issue/bug but, this doesn't happen very much at all (thankfully).
This is not a Dictionary definition and there's much much more to it.
I just did my best i could (via text) to simplify it to help any noob members...
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Ibuprophen said:
Your confusing the Release Type and the Build Type...
Hello Everyone!
I, personally, have always defined the differences of the different Firmware ROM's as follows:
RELEASE TYPES
----------------------
OFFICIAL = From Original Development and signed off by one or more of the Original Developer(s).
UNOFFICIAL = A Development based upon the Original Development by a third party developer.
BUILD TYPES
-----------------
EXPERIMENTAL = Typically an Experimental build is a tool used to aid in Migrating/Transitioning from an older Android version to a newer one.
NIGHTLY/WEEKLY - Are builds that's automated by software and are released on a daily/weekly basis (in most cases they are approximate timing). In Most (but, not All) cases there are no/little real human interaction in this. Typically an automated process for the release.
***One example of the automated process is If you look at Open GApps... This is typically all automated with human interaction being little to none (the human interaction is usually on a case-by-case basis when the need calls for it).
SNAPSHOT = In short... A Stable build. This is typically when someone reviewed and deemed that everything within it is considered "feature-complete" and "reliable". In most cases, these releases are considered being without bugs.
This is not a Dictionary definition and there's much much more to it.
I just did my best i could (via text) to simplify it to help any noob members...
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Click to expand...
Click to collapse
Thanks for the information
Currently I'm using resurrection remix and they release official builds every week
I mean why is that. They rolled out weeklies for 3 out 4 weeks and then official builds and these officials are also published weekly. What is the difference in these builds
Vinay chintu said:
Thanks for the information. Currently I'm using resurrection remix and they release official builds every week. I mean why is that. They rolled out weeklies for 3 out 4 weeks and then official builds and these officials are also published weekly. What is the difference in these builds
Click to expand...
Click to collapse
I can't speak for them (and I may be wrong) but, I believe that this is because of that "human interaction".
More than likely (i can't state definitely) an actual individual reviews and signs off on them before it's released.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Ibuprophen said:
I can't speak for them (and I may be wrong) but, I believe that this is because of that "human interaction".
More than likely (i can't state definitely) an actual individual reviews and signs off on them before it's released.
______________
PLEASE NOTE: I welcome any member to help with further valuable information/clarification for any of my posts.
×MY DEVELOPMENTS×
[APP][TOOL][4.2+]The SELinux Toggler
[ZIP][TOOL][AIO]BusyBox Stericson Binary Installer v1.26.2 {BB/TB Auto-Symlink}
×IN DEVELOPMENT×
[APP][TOOL][4.2+][OFFICIAL]The SELinux Switch
Will Supersede "The SELinux Toggler"
×IDEAS FOR DEVELOPMENT×
[APP][UNOFFICIAL][4.2+]XDA Forum {Classic}
[APP][UNOFFICIAL][4.2+]XDA Reader {Classic}
Click to expand...
Click to collapse
Thank you
The following are most likely “Original Development”:
Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
Your own “unofficial” stock build of your favourite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Click to expand...
Click to collapse
ALSO ALWAYS REMEMBER THE GPL LICENCE:
In order to be fully GPL compliant, your sources must:
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released)
Click to expand...
Click to collapse
To put it short,
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL 2.0 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what is best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
- Sources must be posted in first post of development.
Rule No.2 - If you are about to post a new Rom, you don't have to post source since they are covered by Apache, BUT you must be in compliance with XDA rules and with good sense. Remember that publishing sources is a very polite manner.
New Roms thread must contain:
- Exactly say which base rom do you used : Stock, custom from another developer, CyanogenMod.
- Permission to use said ROM as your base by the original developer(s).
- Credits given to original developer(s) in your first post: (Ex: Credits and thanks for this Rom goes to XXXXX)
- Credits given, if possible, to the people from whom you grabbed scripts, themes and apps.
- Your ROM MUST BE free of paid apps, NO WAREZ ALLOWED.
- Your first post must contain as much info as you can provide, "this is my ROM" and a link is not tolerated (screens, installation procedure, CM version, kernel version etc.)
- Thread Title : " [ROM]xxxxxxxxxxx[date of release][kernel version/kernel required]
Rule No.3 - AdFly, or other ad-revenue related redirecting links, are NOT allowed. Thread will be closed and links be deleted.
Click to expand...
Click to collapse
Reference taken from Micromax A110 forum
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
If anyone wants to reupload to a better file hosting site please do.
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Can you please link to the kernel source, if not all repos used to build this?
jisoo said:
Can you please link to the kernel source, if not all repos used to build this?
Click to expand...
Click to collapse
They are located on the OP under "Instructions used to build"
jahrule said:
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Click to expand...
Click to collapse
MODERATOR NOTICE:
The development section is not a place to share ROMs or hope that someone will take up developing a ROM that you post here. In this section you are only allowed to post your own work, and it must meet the requirements for posting in the Development section as laid out in the sticky titled Device Forum Rules (Please Read before posting).
THREAD CLOSED
Invictrix ROMFor the Moto G5 Plus (potter)
Welcome to Invictrix!! Our goal is to provide users with a unique staple in Android Development which aims at stability and optimizations along with what we feel is the perfect amount of features. We hope you enjoy this ROM as much as our great team has had while building it. With that said, We are in no way shape or form responsible if you brick your phone.
Features:
More features to come
Downloads:
ROM -
Here
GApps -
Pico | Nano | microG
Installation:
See Below
Issues:
See Below
Source:
ROM - InvictrixROM
Device Trees - InvictrixROM-Devices
Kernel - Kernel Source
Reporting Bugs:
Logcat, Logcat, Logcat
Please submit logs if you're having an issue. If there is no log we cannot help you. Simply clogging the threads with “This issue happened, fix it” will get you nowhere and you will be ignored. To Also add to the Log Criteria, Your bug report won't be used if:
- You are not on a clean flash of the ROM
- If you're using Xposed
- If you’ve flashed any other mod that tweaks System in any way
So help us to help you and provide logs for issues. Thanks.
Other:
Feel free to join our Telegram community, Google Plus, and check out our website
https://invictrixrom.com
Google Plus
Our Telegram Chat
XDA:DevDB Information
Invictrix, ROM for the Moto G5 Plus
Contributors
coldhans, Snuzzo, Yuki Coc
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: GZOSP
Version Information
Status: Nightly
Current Stable Version: 1.0
Stable Release Date: 2018-07-21
Created 2018-06-29
Last Updated 2018-07-21
Reserved
Reserved
meh.
Natd32 said:
meh.
Click to expand...
Click to collapse
Assuming you've tried the ROM since you're posting in its development thread, did "meh" mean it was only so-so, and what specifically did you like or not like about it?
Screenshots courtesy of @dhinesh_cool
Dahenjo said:
Assuming you've tried the ROM since you're posting in its development thread, did "meh" mean it was only so-so, and what specifically did you like or not like about it?
Click to expand...
Click to collapse
Dont mind him every thread has atleast one troll.
deleted
Fine, it's odexed now, you savages: https://www.androidfilehost.com/?fid=11050483647474829562
sinchan_nohara said:
Dont mind him every thread has atleast one troll.
Click to expand...
Click to collapse
He's the troll on every thread.
New build
Download: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180706-2220.zip
Telegram: https://t.me/InvictrixROM
Official weeklies should be ready soon... :highfive:
coldhans said:
New build
Download: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180706-2220.zip
Telegram: https://t.me/InvictrixROM
Official weeklies should be ready soon... :highfive:
Click to expand...
Click to collapse
Bugs?
apexashwin said:
Bugs?
Click to expand...
Click to collapse
The only very minor issue I've had is that in the "About phone" part, if i touch "System updates" then the settings app closes. There aren't any updates, so no real reason to touch that, but it's something I've noticed.
New build with July security: https://potterroms.me/Invictrix/Invictrix-potter-8.1.0-1.0-UNOFFICIAL-20180714-0333.zip
Official Invictrix is here!
Official OTA builds have begun as of this week. The first can be downloaded HERE.
I've updated the OP with new links to the Invictrix OTA page and recommended GApps packages from GZR (pico gapps) and Beans (nano gapps), as well as a link to NanoDroid's microG implementation by @Setialpha if you prefer to go without Google.
Happy flashing!
What WireGuard module version is included in this ROM?
wrkerr said:
What WireGuard module version is included in this ROM?
Click to expand...
Click to collapse
Check the kernel source link in the OP. Wireguard-related commits are in there. iirc, it pulls the latest version via http when the build is started, so it should always be up to date.
Has anyone tried dirty flashing this over Omni?
ThundeRStormS Galaxy S10/N10 family for OneUI Q
SM-G970F, SM-G970N, SM-G973F, SM-G975F, SM-G977B
SM-N970F, SM-N971N, SM-N975F, SM-N976N, SM-N976B
ThundeRStormS "testers group - for now only I look for people who wants to test my kernel"
Compatibility notes :
Android OneUI Q odexed and deodexed roms S10/N10 family ROMs
I will update this thread and kernel source after make first release of ThunderStorms kernel.
Kernel is based on Cruel Kernel source with a lot of Linux updates and new features.
Please send priv message to me for join to TS testers team or write here Your Telegram name.
I'm looking for G790F, G977B, all N10 types.
CREDITS : @evdenis Denis Efremov and Cruel Team for source, Samsung updates and help.
Reserved
reserved
Reserved 2
reserved
Reserved 3
reserved
I'm down to try. I run a note 10 F D/s
Problem is you need to post the download link and source code or they'll close this as a place holder
TheMadScientist said:
I'm down to try. I run a note 10 F D/s
Problem is you need to post the download link and source code or they'll close this as a place holder
Click to expand...
Click to collapse
I want to control for now who has TS kernel and which device he has....
Source - is not a pblic for now no files, etc. so no needed. I will update this thread whene I will be sure so TS kernel works on All devices S10/N10.
So don't be afraid about it.
Thread closed per OP request.