[DEV] [R&D] Open Android Patcher (OAP) & MIUI Ex - Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
News
CURRENT PROJECT STAGE: Late-Initial R&D
PENDING PROJECT STAGE: Prototyping [No ETA]
2019.02.16
Overhauled this thread to actually represent the current project (all the old stuff is in a spoiler at the bottom)
I made a cool logo! Well, let's consider it a first-draft... if anybody thinks they can do better then you're welcome to share! But please don't be offended if I say "I don't like it" (I can be picky :silly
A GitHub organization for the project has been created! There's only one public repo right now, which is the Linux/WSL-only 'preptool' and has no documentation.
As mentioned above, there is an OAP PrepTool repo released. Alpha though - right now it can unpack and de-opt (deodex) the latest Pie-based MIUI ROM's for Poco, and probably some other devices (it makes a few assumptions though). It's tested in WSL (Ubuntu on Windows) only, but there's no reason why it wouldn't work in any "real" Linux/GNU distro. Note that the repack and reodex of ROM's is not yet finished. But I welcome anybody with a different device to test the unpack/deodex process and report any errors you get from it.
I've been on a break for the past few weeks as I am quitting smoking - successfully (yay me!) - but want to keep stress to a minimum to maximize my chances of success
Haven't heard from Lanchon (creator of DexPatcher, an essential project for OAP) for a couple weeks now, but he's a very busy guy who was always super helpful and cool in the past so I don't want to pester him again just yet. He is aware of what we're doing here though and said he'll get back to me when he can
About
Whew, where to start? The project is still in it's infancy so this is a lengthy 'About' section as I try to convey the vision of this project to any person who might be interested in helping out. Yeah it's a lot to read - but surely worth reading once. In future I'll say in the News section above if any specific section of the thread was updated.
While I consider myself an Android power-user and veteran developer ( [brag] my past XDA and freelance work has landed me several contract in Android development [/brag] ) I'm not ashamed to say I am a huge MIUI fan and prefer stock firmware over any custom ROM's (stability is essential to me). It's a pretty great stock ROM that I missed for a long time - generally reliable yet feature-rich. However, it does lack some functions in key areas (which custom ROM's have enjoyed for a long time) and also has a lot of small issues that Xiaomi haven't acknowledged or fixed for whatever reason (probably a cost-benefit analysis says it's not worth fixing - you know, that typical big business stuff that we're simply not privy to because competitors could use it to get an advantage or something).
I intend to improve on MIUI out of my own love for the system, the memory and nostalgia of my early days in Android/MIUI modding ( [brag] such as this or this, the two projects that launched my professional Android journey [/brag] ) has me inspired to Make MIUI Great Again. However, before working on a another modded MIUI ROM, I wanted to do things right by the community and make things as future-proof as reasonably possible: Make a build system (or "kitchen"), make it developer-friendly and modular, and make it all free and open-source.
This project/initiative has been dubbed the Open Android Patcher (or OAP for short) and, while specific to MIUI for the moment as that's the template used during design, OAP has long-term goals to be generic and modular for any stock-ROM modding.
To simplify, the idea is pretty straight-forward - make a tool kit that lets developers write patches for stock ROM's via mods that are similar in principle (and how they're written) to Xposed mods. Unlike Xposed mods though, the mods are baked-in to the ROM itself rather than performed at runtime. This means that, unlike Xposed, Safetynet still works, performance stays 100%, and NO SECURITY RISKS. However, obviously it won't be as flexible as Xposed - if you want to add or remove a mod you will need to rebuild and/or reflash the firmware and/or changed files.
The end-goal is to do a similar thing as what Xiaomi.eu, Mi-Globe, etc. all do but *NOT* keep the build system a well-guarded secret (I've reached out to *all* these guys and they either ignored me or politely refused to be a part of anything open). That is, everything related to OAP will remain 100% open and transparent (unless a developer makes a mod and ignores the GPL license), welcoming to contributions from others via usual GitHub PR's. There will, however, be many more features than other MIUI-modded ROM's - features which you usually only see in AOSP forks (Omni, RR, etc.) or Xposed modules; part of my previous professional Java work was extensive reverse-engineering of Android applications and ROM's (rebranding Chinese devices for global markets, most Chinese ODM's prefer we reverse-engineer it rather than giving us their source code lol) and there are a lot of possibilities that I want to explore here which I am very confident in doing so. Most of all, though, I want to make it easier for other developers to contribute mods too. After all, that's what open development is all about, right? The thanks and feel-goods we get from others!
I will be sharing regular updates as things develop, and continually seeking feedback from prospective developers and users.
All sources relating to the project will be in repo's at the GitHub.com/OpenAndroidPatcher organization.
Project Goals/Status
A very-draft kind-of-Roadmap. This will be improved soon (it's one of the tasks below, heh).
Key/Legend:
[#] Ongoing/current task in initial/early R&D stage
[!] Ongoing/current task in initial/early R&D stage but might be abandoned for whatever reason (e.g. too difficult and not worth the time unless I attract some genius talent to help, or it's too early to tell if it's even possible or useful)
[@] Ongoing/current task in deep development and/or with unknown or indefinite completion time
[+] Ongoing/current task nearing completion
[-] Future task, blocked by a previous incomplete task
[?] Future "maybe" task
[@] Experiment with MIUI fixes and improvements
[@] Research bugs and issues that Xiaomi/Poco haven't addressed
[@] Create the Java-based OpenAndroidPatcher (OAP) build system (kitchen)
[#] Integrate and adapt DexPatcher for OAP (so we can write stock ROM mods in pure Java with all benefits of IntelliJ IDEA)
[-] Create a more low-level patching system for advanced patches (will probably a wrapper around dexlib2)
[-] Create the OAP framework/library. This is a framework jar + IDE library jar that OAP patches link against at runtime and compile time respectively which aims to take a lot of the boilerplate and tediousness out of writing ROM mods (e.g. Designing an settings UI's, working with apk/framework resources, lots of other shortcuts and helpers that are helpful or necessary when patching stock ROM's)
[-] Design the "OAP Tweaker" app, to act as a centralized app that handles all mod configuration UI's automagically
[-] Formalize "MIUI Ex" - the flagship 'product' (for want of a better word) of OAP
[#] Make a nifty (but actually useful) website
[#] Make a public Freedcamp project for easier collaboration and more transparency
[?] Make a Discord server or Telegram group for senior developers to chat directly on
[?] Easy debugging and testing of OAP patches on a live development device
[!] Create a hosted build server
[!] Create a TRUE OTA system for automatic delta (incremental) updates; none of that "Notification that links to a webpage with full ROM ZIP to manually download and flash" that so many custom ROM's do
[?] Completely replace the build system with a Magisk-powered dynamic patching system, making a custom OTA/build server obsolete. This is a HUGE task but an ultimate-awesome one that I'd love to see one day.
What's this thread for?
TL;DR: A place for other interested developers to show their interest and share ideas. When the project is a bit more mature, a better platform of communication will be established.
Honestly, this thread was written a bit prematurely - but obviously I don't want it locked. In retrospect I would not have started it so early - I did not expect it to blow up with popularity, since then the original goal has changed significantly from "a custom MIUI build" to "a universal and modular stock-ROM patching kitchen initially aimed at MIUI". The purpose of this thread is now fairly vague because development is still in too early stages. I can't really accept any serious help from others yet because the project is still too immature to allow any compartmentalization or delegation of the tasks. In other words - for those trained in Project Management vocations - most of the important tasks right now are all along the critical path. Those that aren't on the critical path are really complicated and I've not had any knowledgable volunteers yet.
So anyway, this thread is mostly used as a blog for me and a place for everyone to spin ideas on how to make MIUI awesome. Anybody with an interest in the project is free to ask and talk about the development or ideas, as long as it's at least loosely related or might be of help to the project. I'm pretty active on XDA, so as long as you don't hijack the thread for some unrelated help on other Poco stuff, I'm happy for anybody to post and happy to answer - even non-developers and dev novices haha (as long as you're not rude, spammy of off-topic of course - at best you'll be silently ignored).
With that said, thank you for stopping by... and check back soon!
Old thread content below (along with the highly-experimental-and-laggy-as-heck port of Mi 8 MIUI to Poco).
------- [START OLD THREAD SPOILER]
Flavors
Xiaomi.eu for Beryllium (Poco) - port from Dipper (Mi 8)
NOT FOR DAILY USE!
Clean port from Xiaomi.eu, all essentials appear working (Camera, Calls, Wifi, Sound, etc.)
[NEW] FBE (File-based encryption) enabled. Requires custom TWRP build or FBE-disable ZIP to remove (see Download section)
[BUG] FM Radio not working (blocked by kitchen development, see GitHub issue #1)
[BUG] MicroSD does not appear on PC when in USB File Transfer mode. External storage works fine otherwise, though.
[ISSUE] Performance is poor (UI jank).
[ISSUE] GPS/Location MIGHT be worse than stock official. Same reason as above (Issue #1).
[ISSUE] Notch cut-out and status bar size/alignment is a little bit too big.
That's the only flavor for now
Known Issues (all flavors)
Device is janky, sometimes even pausing for a couple seconds.
The only current flavor is an experimental port which has issues. This was only built as an experiment for people to try-out Mi8 features/blobs (e.g. Camera).
Downloads
Main ROM's
Latest builds at GitHub - https://github.com/cosmicdan/MIUI_Kitchen/releases
Extra's
The following extras can be found on DevBB and also GitHub (but I will only add them to a GitHub release if it has been updated - so it will be easier to find these downloads on DevBB instead):
A custom TWRP build with MicroSD fixed, FBE (file-based encryption) support, and extra mounts for Backup/Restore
A flashable ZIP to enable FBE on the current ROM. Note that FBE is already enabled by default on some flavors (see above). Requires Magisk 17.1+ (flash Magisk before or after - order doesn't matter - as long as both come after the ROM).
A flashable ZIP to disable FBE on the current ROM if you don't want any encryption. Requires Magisk 17.1+ (flash Magisk before or after - order doesn't matter - as long as both come after the ROM).
Install Instructions
Prerequisites for ALL first-time users:
[REQUIRED] Unlock your bootloader. Do not ask about unlocking bootloader in this thread, it is off-topic.
[DOWNLOAD] Download the desired ZIP from GitHub (there is only one flavor now, so just get whatever is latest)
[RECOMMENDED] Flash my TWRP which has encryption changed to FBE, working MicroSD, and extra partitions added for backup. Nothing special here, just the usual 'fastboot flash recovery twrp-*' command. Do not ask for help about how to fastboot flash here.
[RECOMMENDED] Make a FULL backup of your current ROM in TWRP. These firmware's contain kernel, system, and vendor - just like official MIUI ROM's - so a TWRP backup should allow you to quickly revert if you need to.
Moving from ANY other ROM?
[REQUIRED] Factory Reset (swipe) or "Format Data" (button). If encrypted with stock-style encryption, the full Format Data is essential to clear the incompatible old-fashioned full-device encryption.
[FLASH] Copy the ROM ZIP to device and flash in TWRP
[REQUIRED] Flash Magisk 17.1 (or later).
[OPTIONAL] Flash the FBE-Disabler ZIP if you want to completely disable encryption. This will modify the Vendor partition, so will apply to any GSI's you flash too.
[RECOMMENDED] Boot the ROM and wait for it to boot (will take longer than you are used to). Reboot it again once booted, and keep rebooting until boot becomes fast (fast as stock) again. See Known Issues above for why this is important.
Upgrading, downgrading or reinstalling a CosmicDan MIUI Build ROM?
[OPTIONAL] Factory Reset in TWRP
[FLASH] Copy the ROM ZIP to device and flash in TWRP
[REQUIRED] Flash Magisk 17.1 (or later).
[OPTIONAL] Flash the FBE-Disabler ZIP if you want to completely disable encryption. This will modify the Vendor partition, so will apply to any GSI's you flash too.
[OPTIONAL] Wipe Dalvik/Cache if you encounter a boot loop. This is a very rare requirement - Android is smart enough to know when Cache is old and can recycle it. If you do wipe cache, be aware of the "Reboot again" optimization stuff again, as from a clean flash.
Credits and Thanks
- Xiaomi.eu for the fantastic conversions of MIUI China ROM's
- All those mentioned in README.md in the Kitchen source for making the tools it depends on (I will list them here once the kitchen development settles down)
------- [END OLD THREAD SPOILER]
XDA:DevDB Information
Open Android Patcher (OAP) & MIUI Ex, ROM for the Xiaomi Poco F1
Contributors
CosmicDan
Source Code: https://github.com/OpenAndroidPatcher
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked BL
Based On: MIUI
Version Information
Status: Alpha
Created 2018-09-16
Last Updated 2019-02-15

Reserved

Still first.
Gonna design it now.

SmallTarzan said:
First.
And I still hate you.
Click to expand...
Click to collapse
xD
Just discovered another bug, MicroSD does not appear in File Transfer mode - only storage. Which is really weird because it appears fine in literally everything else.
Updated OP.

Nice to see this..

Trying, congratulations on the "Kickstart" thread

Booted

Is it based on Oreo 8.0 or 8.1? I need an 8.0 miui rom to install xposed so asked.

*****RESERVED*****
Edit 1
First of all I'd like to thank cosmic dan for his support and love for our still infant growing poco
The ROM boots up fine just takes little more time than usual because (read mentioned by Dev in post) you'll probably have to reboot 15 times and devices gets snappier and faster after every boot
For those who wants to know what's a xiomi.eu flavour it's simply MIUI without all the bloatware and most hated Chinese apps
I encourage you use the device for sometime after few reboots to help settle it down but for daily driver I'll still wait for the next build. XD

Gr8 start.:good:

Hi,
Nice to see you working on this...
However, you mention that you think MIUI lacks some features. But, unless I have overseen it, you do not tell what features we will get with your ROM... so what we will get in trade for the little things not working
Could you be more specific so I can see if you're adding that feature I am looking for (that I could add with XPosed but Xposed does not work with MIUI based on 8.x... and a magisk module isn't available for that function).
Regards.

Thanking you for your efforts. I appreciate your work , you are first one who provide a custom rom for poco f1.

i would love to use it if you detail the names of pre-installed apps(*coughs* bloats) except the essential ones.
Also, since it's a derivative from Miui, no custom flashing gapps then?

@CosmicDan does your twrp can decrypt data with lockscreen pin/password?

$hivaM Manav said:
*****RESERVED*****
Edit 1
First of all I'd like to thank cosmic dan for his support and love for our still infant growing poco
The ROM boots up fine just takes little more time than usual because (read mentioned by Dev in post) you'll probably have to reboot 15 times and devices gets snappier and faster after every boot
For those who wants to know what's a xiomi.eu flavour it's simply MIUI without all the bloatware and most hated Chinese apps
I encourage you use the device for sometime after few reboots to help settle it down but for daily driver I'll still wait for the next build. XD
Click to expand...
Click to collapse
Is this based on 8.0 or 8.1?

narora9999 said:
Is this based on 8.0 or 8.1?
Click to expand...
Click to collapse
It's based on MIUI 10 8.1 oreo.

$hivaM Manav said:
It's based on MIUI 10 8.1 oreo.
Click to expand...
Click to collapse
Damn. i need xposed support to make poco my daily driver and it can only be achieved by using miui based on Oreo 8.0 or an Oreo custom rom. till then its just a joke hotspot for me.

narora9999 said:
Damn. i need xposed support to make poco my daily driver and it can only be achieved by using miui based on Oreo 8.0 or an Oreo custom rom. till then its just a joke hotspot for me.
Click to expand...
Click to collapse
why are you so dependent on xposed, if i may ask?

narora9999 said:
Damn. i need xposed support to make poco my daily driver and it can only be achieved by using miui based on Oreo 8.0 or an Oreo custom rom. till then its just a joke hotspot for me.
Click to expand...
Click to collapse
Well if you really can't wait then flash any 8.1 GSI custom ROM everything works except VOLTE in most of them.

$hivaM Manav said:
Well if you really can't wait then flash any 8.1 GSI custom ROM everything works except VOLTE in most of them.
Click to expand...
Click to collapse
Yes i'm looking into them but most gsi's shared here are P based. Face unlock also doesn't work,notch is also buggy. i could manage without volte but other bugs are there too.
How long do you think it'll take before an Oreo custom rom shows up?

Related

[ROM][OFFICIAL][6.0] Omni 6 Nightlies

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Omni?
Omni Gerrit Review
Disclaimer
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Because of the nature of Xposed framework, NO SUPPORT will be given to those running Xposed framework on Omni 6
CHANGELOG:
Code:
[CENTER]
2016-02-01:
Nightlies started :)
2016-01-22:
-Omni Dialer lookup is back
-Lots of changes/fixes
-Kernel leak fixes
2016-01-06:
First build of the year :)
-Omni JAWS (Just Another Weather System)
-Update to Android 6.0.1 r10 ( Include latest security updates)
2015-12-30:
Last build of the year :)
-Chromium is included in this build, and unless poll results change within the next 2 days, it will remain
-lots of bugfix
2015-12-19:
-New boot annimation
-selinux enforced (use system-less supersu beta to get root)
-some bugfix (check gerrit for the changelog)
2015-12-11:
Android 6.0.1 update
A few backported features and bugfix
2015-12-04:
Silent mode back
some bugfix
2015-11-29:
revert clang usage that was breaking sensors (as seen on CyanogenMOD's github)
Latest commits were actually cherry-picked from mako's device tree on CM-13 github.
2015-11-28:
some QCOM camera fix
some deprecated stuff removal
wifi check added (taken from Nvidia shield)
2015-11-19:
add dex2oat speed filter (speed up initial boot and attempt to fix facebook app cache regeneration at reboot)
2015-11-15:
Update to Android 6 r26
In-call audio fixed, force dex2oat uses no-swap, codecs handling
2015-11-9:
DRM blobs updated (Google play movies works, Netflix should work as well, but I can't test it), some more blobs added ( from Nexus 7 2013 )
2015-11-8 (new build):
Doze power saving mode, drm handling should be fixed, media codec updated
2015-11-8:
Use accelerometer for doze, and custom battery lights
2015-11-7:
First update, bugfix and backports
2015-11-5:
Initial Release[/CENTER]
DOWNLOADS:
Omni 6 Nightlies for Nexus 4 / Mako
You MUST DO A FULL WIPE before flashing nightlies, whether you are coming from homemade builds (aka my builds), or a previous version of OmniROM. Be certain to do a full backup of your data, apps, call logs, sms/text and so on before flashing. If you were to flash nightlies over my own builds or your custom made builds, or any other ROM, you would end in a bootloop
GAPPS must be flashed BEFORE initial boot, they will NOT work properly if you flash them afterwards !!!
Don't update gapps on nightlies update, only initial flash requires it. Updating gapps on next nightly would break those, and ROM would become unusable.
You MUST use this version of supersu, latest beta system less
Supersu beta System less
KNOWN BUGS:
Code:
[CENTER]* You tell me[/CENTER]
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
RECOMMENDED TWRP
Source
OmniROM Source​
Only a few changes are taken from CyanogenMod, but thanks to them for those
CyanogenMod Source​
XDA:DevDB Information
OmniROM 6, ROM for the Google Nexus 4
Contributors
kldoc, MaR-V-iN, Maxwen, Entropy512, Xplodwild, Jiangyi
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Nightly
Created 2015-11-05
Last Updated 2016-04-25
Reserved
Thanks, I will give it a try
A list with the features would be very appreciated.
dragos281993 said:
A list with the features would be very appreciated.
Click to expand...
Click to collapse
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
kldoc said:
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
Click to expand...
Click to collapse
I simply asked. All the other ROMs have a list with the basic features in the description, so it was a matter of time before someone came here and asked you for one. Also, flashing a ROM in order to find out what features it has, it's counterproductive. I've got free time when I come home from work, and the last thing I want to do is experiment with ROMs that I have no idea what features include and what don't. I usually read the description of a new ROM, see if it has what I'm interested in, and then decide if I feel like flashing it or not.
Sent from my Nexus 4 using Tapatalk
kldoc said:
Hi! Wow, Marshmallow includes a ton of features, do you want me to make you a list of them? I don´t think so.
Whatever, features in 6.0 are practically the same than the Omni 5.1.1 ones, just some of them are disabled temporaly.
Wanna know what are the features in 5.1.1? Flash the OmniRom nightly for 5.1.1, or, if you want to make the process faster, directly flash this 6.0 build.
Enjoy!
Click to expand...
Click to collapse
Wow, dude, it's just a question
Fatal1ty_93_RUS said:
Wow, dude, it's just a question
Click to expand...
Click to collapse
Actually I said him to write that, just is some kind of advice for all the users.
Backing up current ROM, and testing this ROM is something that could take you just 5 minutes.
Sometimes is really tiring to get messages from hundred of users asking about features, when they can be seen on our OmniRom github or by testing it. We don't provide a feature list as almost all ROMs do, we see that unnecesary, but we asure that the experience with our ROM is going to be great.
Actually the features included for Omni are the next ones:
We are not and probably we never were a feature bloated ROM, as other ROMs do as DU or CM does. Our ROM is just a clean AOSP one with minimal but nice features and with an optimized performance.
We, and also me, will be adding some features to it recently, I just finished yesterday on solving issues for my device, now is time for features.
Anyway sorry if reply was some kind of "unrespecful" but this way I wanted to prevent 50 posts asking for the same think.
I wish you to enjoy the ROM and tell us your feedback
Cheers!
Sent from my A0001 using Tapatalk
kernel source?
brandonabandon said:
kernel source?
Click to expand...
Click to collapse
As mentioned in the main thread, everything is on OmniROM's github or OmniROM's gerrit (in case it's not merged yet).
I try myself to publish non-official builds with available source for everything.
There is one (very tiny) difference between device_lge_mako used in this build and the one present in the non merged commit though, i've added "selinux=permissive" to make your life easier with root process while supersu is still not possible with selinux enabled, but this will never get merged, OmniROM intend to provide a secure ROM.
Here is again the link to OmniROM's github (copy of main thread link with url to kernel repo):
https://github.com/omnirom/android_kernel_lge_mako/tree/android-6.0
Have fun !
EDIT: In case the question rise, kernel is based on the work of Dmitry Ginsberg, except that I did track all the commits in his patch and cherry-picked all of them from google's git, only defconfig was taken from his patch. I removed the cpufreq_stats which is supposedly not implemented in Qualcomm S4 pro, even though some devs are trying to make an implementation, I won't probably include any of this in OmniROM's kernel, this for a few reasons, the first one being that I don't have the C/CPP knowledge to fully understand kernel's changes that "might" break things, second one being that I truly wish Nexus 4 kernel to stay as close as possible to AOSP, which is OmniROM's policy anyway
If one would want to submit patches to support some new features in the kernel, they are more than welcome to do so, patches will be reviewed by people with required experience and knowledge
Not going to try this because of rude dev's....
bdasmith said:
Not going to try this because of rude dev's....
Click to expand...
Click to collapse
Thanks op for the thurough explanation. Im looking to optimize and hack a personal build and was experiencing boot issues.
bdasmith said:
Not going to try this because of rude dev's....
Click to expand...
Click to collapse
As mentioned by @herna, he actually told me to write this answer. I am myself not rude by any mean, and try to give my users as much support as I can. I do work on OmniROM as a hobby, as I'm not even an IT professionally speaking. Currently chain testing gapps packages to be able to recommand one that works perfectly on Omni 6 for Nexus 4.
I am truly sorry if the tone of the message actually did offend people, doing so was not my intention. I published this homemade build to show people progress was being done on OmniROM 6 and let people play a bit with it, but since I knew it was a very early build not meant to be used as a daily driver, that's why I did tag the thread with experimental status, to avoid people with very few free time to actually try to use this ROM as a daily driver, or even features, as many things are yet to be fixed, and that's the reason why @herna actually told me to write this, to avoid the need to give support for bugs that are being solved and need time to be fixed. Because we are all doing this in our free time, none of us is getting paid to do this, we do that by passion for Android and its community.
I once again perfectly understand the message was rude, and I'm sorry if this offended people, I, in future, will avoid to answer with such a tone, and give more complete explanations why some questions can't get straight answers.
In the meantime, I really advise people who don't have much free time to spend on ROM flashing to stay away from this build for now, as it's really intended for people with knowledge and free time to get it running well. Rest assured I'll publish new builds as bugs are being solved in order to improve your experience
Have fun with OmniROM !
kldoc said:
As mentioned by @herna, he actually told me to write this answer. I am myself not rude by any mean, and try to give my users as much support as I can. I do work on OmniROM as a hobby, as I'm not even an IT professionally speaking. Currently chain testing gapps packages to be able to recommand one that works perfectly on Omni 6 for Nexus 4.
I am truly sorry if the tone of the message actually did offend people, doing so was not my intention. I published this homemade build to show people progress was being done on OmniROM 6 and let people play a bit with it, but since I knew it was a very early build not meant to be used as a daily driver, that's why I did tag the thread with experimental status, to avoid people with very few free time to actually try to use this ROM as a daily driver, or even features, as many things are yet to be fixed, and that's the reason why @herna actually told me to write this, to avoid the need to give support for bugs that are being solved and need time to be fixed. Because we are all doing this in our free time, none of us is getting paid to do this, we do that by passion for Android and its community.
I once again perfectly understand the message was rude, and I'm sorry if this offended people, I, in future, will avoid to answer with such a tone, and give more complete explanations why some questions can't get straight answers.
In the meantime, I really advise people who don't have much free time to spend on ROM flashing to stay away from this build for now, as it's really intended for people with knowledge and free time to get it running well. Rest assured I'll publish new builds as bugs are being solved in order to improve your experience
Have fun with OmniROM !
Click to expand...
Click to collapse
Thank you for your kind explanation. I'm willing to experiment now
brandonabandon said:
Thanks op for the thurough explanation. Im looking to optimize and hack a personal build and was experiencing boot issues.
Click to expand...
Click to collapse
You actually need this unmerged commit to be able to boot:
https://gerrit.omnirom.org/#/c/15224/
I didn't merge it yet to allow modifications and keep things clean in the meanwhile, stlport is actually needed, that's the main modification to allow boot if you set selinux to permissive, if you want selinux enforced (no root at the moment), you'll also need the selinux policy changes.
This commit doesn't include permissive selinux, because it's not needed for boot, but if you need it, and don't know how to set it, let me know, i'll give you where and how to set it up.
Hope that solve your boot issue If you still have troubles booting despite that commit, please provide some logs so I can see what's wrong
Have fun
for those who might have issues with Google Keep force closing, I discovered that last version from play store actually doesn't work, you need to install an older one:
http://www.apkmirror.com/apk/google-inc/keep/keep-3-2-435-0-android-apk-download/
I've just uploaded 2 screenshots, don't be alarmed by the "!" next to my wifi icon, I'm in China, google services are blocked, that's also the reason why there's a key, vpn ...
Google keep, Gmail and maps didn't work as expected. As you mentioned Keep kept force closing. Maps and Gmail refused to accept sign in. I downloaded the apks from apkmirror. They work fine now.
The rom is awesome as usual. Thanks kldoc. One feature missing or is a new marshmallow feature is that the phone doesn't unlock after entering just the pin. You have to tap enter.
hashtask said:
Google keep, Gmail and maps didn't work as expected. As you mentioned Keep kept force closing. Maps and Gmail refused to accept sign in. I downloaded the apks from apkmirror. They work fine now.
The rom is awesome as usual. Thanks kldoc. One feature missing or is a new marshmallow feature is that the phone doesn't unlock after entering just the pin. You have to tap enter.
Click to expand...
Click to collapse
Thank you for your feedback ! Really happy to see it went rather well for you
Pin code auto-unlock was an option in Lollipop, have to admit I don't like this security wise. Just checked, and yes, Google removed the option.
I had less issue than you with Gapps, I used banks gapps, that I modified to include Google Now launcher, apart from keep, everything ran well from play store, but I use inbox, not gmail, might be the difference here.
Actually making a new build as I write this mail to verify the update process, will post it here once I'm done verifying that nothing is broken.
I managed to trick location, even if it was much more difficult to accomplish than on Lollipop, allowed me to be located in US and enable google now. Google now on tap also works from what i can see.
kldoc said:
I've just uploaded 2 screenshots, don't be alarmed by the "!" next to my wifi icon, I'm in China, google services are blocked, that's also the reason why there's a key, vpn ...
Click to expand...
Click to collapse
Where are the screenshots?

[ROM] [surnia] Androidov 1.0 M

Androidov 1.0M
Since cyanogenmod removed some features which I used I was looking for some other room which will satisfy my needs. I've tried couple of ROM's provided here but I was very bad surprised. Some users and maintainers probably don't read between the lines, providing unsecure builds to the community by settings Selinux to permissive... or cherry-pick features which can compromise your security. That wasn't problem until I asked " Why permissive?" and the answer was "I like permissive!" ... or some ROM maintainers which answer you just " I am the maintainer and I will do whatever I want ". Well... go on boys!
Anyway... I builded my own ROM. As I use my surnia as one and only I am focusing on stability en security. Because I don't like permissive... this ROM is with Selinux enforced. It is based on Cyanogenmod 13 as it runs more stable than Cyanogenmod 14.1 at this moment. As I do with every software... I will wait about 1 month until I update it to 14.1 - until then much bugs will be gone.
I don't want to bloat this ROM so I will keep the changes as minimal as possible. This ROM is not meant to provide as much features as possible... just pick the best one and include them.
This first build is meant to be tested. It runs stable for 3 days on my phone and I didn't noticed any issues. If you encounter any issues, please let me know.
Every suggestion for features to be included is highly appreciated!!!!
I will update this ROM WEEKLY! As providing nightly builds is not really needed in this case as the changes are minimal and in my case it isn't worth investing my time in setting up a build-bot for it.
Next build I will provide will be reorganized - I will direct all the features in the Settings app under "Extra features" section. I will organise my last changes, commit them to my github and will provide a link with build instructions. It will take me some time as I am working till late next 2 weeks.
Credits
I am not java developer... well I have basic knowledge, but I can't call my self e java developer. I forked features which are already included in some other ROM's and I changed some lines in the code in order to integrate them.
So thats why I want to thank:
Cyanogenmod Team
Android Ice Cold Project (AICP)
SlimRom Team
Sources
Well... here you go:
https://github.com/rpangelov/android
Features
AdAway - Well... maybe I could have replaced the host file and include it in the build... but you won't be able to stop or update the adblocker. In some cases this can cause problems... so I decided to prebuilt AdAway. AdAway is adblocker which does the same - it replaces your host file with one downloaded from the app server. It provides you the choice to stop the adblocker by restoring your original host file or update it with newer version.
KernelAdiutor - there you got even more options and statistic. It provides even init.d emulation! This is cool if you want to run ViPER4Android for example, which is good! Pay attention - it EMULATES init.d function. init.d is disabled in this build as it is suggested again - for security reasons.
Disable fullscreen keyboard in landscape - you can find this option in Language and Input options -> Advanced settings. Because surnia is 4,5'' screen, I use it sometimes in landscape mode and I don't like when keyboard is fullscreen...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Suggest more features and I will add them if they are good to use!
Download
Update: Here I provide the last test build Download
It isn't finished, but I aborted developing this rom for this moment, as cyanogenmod is death. I will rebase the rom. Merry christmas! I will keep you in touch.
Placeholder threads for ROMs/Kernels are not permitted. Closed - can be reopened when code available to download. Remember sources and credits too...
Re-opened to allow file links to be added...
this rom volte supported?
I think u should base this ROM on CM14.1 as it is alot more stable now and also this ROM will gain traction as most users (like me) want to run the latest version of Android for its features and to show their friends (like me). Also as far as security is concerned however secure the ROM is it is rooted so u can't call it secure. Anyway that's my opinion. Good job on the ROM. It works perfectly fine on my device and it is pretty stable. Keep up the good work! I'm not trying to insult ur work, I know it's hard to build ROMs (Speaking from experience and clearly u r better than me at doing it) but I just had a few suggestions and opinions I wanted to share.
Sent from my XT1521 using XDA Labs
ayush rao said:
I think u should base this ROM on CM14.1 as it is alot more stable now and also this ROM will gain traction as most users (like me) want to run the latest version of Android for its features and to show their friends (like me). Also as far as security is concerned however secure the ROM is it is rooted so u can't call it secure. Anyway that's my opinion. Good job on the ROM. It works perfectly fine on my device and it is pretty stable. Keep up the good work! I'm not trying to insult ur work, I know it's hard to build ROMs (Speaking from experience and clearly u r better than me at doing it) but I just had a few suggestions and opinions I wanted to share.
Sent from my XT1521 using XDA Labs
Click to expand...
Click to collapse
About the building... it's not hard, but I needed to clobber couple of times, because I didn't set proper my IDE. The new tools introduced ninja and jack are cool, but I had issues with running jack properly.
I had 3 issues:
1. Hardware fault - as the PC I build on is assembled out of box with lot's of second hand parts I have 2x2GB RAM and 1x4GB RAM. The first issue I came through was segmantation fault's caused by the difference between the Mhz of the RAM modules.... so I had to take out the 4GB module as it was faster than the other two - 1333mhz.
2. As I thought... JACK will run out of memory... and it did. AOSP recommend 16GB of RAM and I have 4 at the moment... which isn't the problem at all, but the builds are generating slow. Anyway... I tried to set 3GB of ram for jack by exporting variable for JACK, but this is probably not that good, because it continued to complain about not enough memory. SO i set this 3GB of ram directly into prebuilts/sdk/tools/jack_server_setup.mk and it was good.
3. What I didn't expected... is that jack wasn't able to reach server, because "the port was used by another PID"... and this PID was JACK it self... so I just deleted ~/.jack-settings . By running jack once more, it will generate exactly the same file with the same settings, but it all works fine. So no idea where this issue is coming from...
I build on Debian Testing as I don't like Ubuntu, and Debian stable doesn't provide the updated packages needed to build Android N. If you have any issues or questions about building CM 14.1 or this ROM, let me know.
I Agree with that. Since CM 14.1 is official I am updating the rom and took me a while, but it is all good.I am testing now the new build - I've already updated the repo's on github. After couple of hours I will upload the new build of all works good. I need to check some log's. Will keep you in touch!
rpangelov said:
About the building... it's not hard, but I needed to clobber couple of times, because I didn't set proper my IDE. The new tools introduced ninja and jack are cool, but I had issues with running jack properly.
I had 3 issues:
1. Hardware fault - as the PC I build on is assembled out of box with lot's of second hand parts I have 2x2GB RAM and 1x4GB RAM. The first issue I came through was segmantation fault's caused by the difference between the Mhz of the RAM modules.... so I had to take out the 4GB module as it was faster than the other two - 1333mhz.
2. As I thought... JACK will run out of memory... and it did. AOSP recommend 16GB of RAM and I have 4 at the moment... which isn't the problem at all, but the builds are generating slow. Anyway... I tried to set 3GB of ram for jack by exporting variable for JACK, but this is probably not that good, because it continued to complain about not enough memory. SO i set this 3GB of ram directly into prebuilts/sdk/tools/jack_server_setup.mk and it was good.
3. What I didn't expected... is that jack wasn't able to reach server, because "the port was used by another PID"... and this PID was JACK it self... so I just deleted ~/.jack-settings . By running jack once more, it will generate exactly the same file with the same settings, but it all works fine. So no idea where this issue is coming from...
I build on Debian Testing as I don't like Ubuntu, and Debian stable doesn't provide the updated packages needed to build Android N. If you have any issues or questions about building CM 14.1 or this ROM, let me know.
I Agree with that. Since CM 14.1 is official I am updating the rom and took me a while, but it is all good.I am testing now the new build - I've already updated the repo's on github. After couple of hours I will upload the new build of all works good. I need to check some log's. Will keep you in touch!
Click to expand...
Click to collapse
Nice to know. Dude why don't you use Linux Mint. It's pretty amazing and has all the required packages. For all the builds I've done (2) I've used Ubuntu and it has never let me down. Also it works very well on old and unpowered hardware.
Sent from my XT1521 using XDA Labs
ayush rao said:
Nice to know. Dude why don't you use Linux Mint. It's pretty amazing and has all the required packages. For all the builds I've done (2) I've used Ubuntu and it has never let me down. Also it works very well on old and unpowered hardware.
Sent from my XT1521 using XDA Labs
Click to expand...
Click to collapse
I will give Mint a try... maybe. I won't use ubuntu because many of reasons... but lets classify them all by - I dont like company products... so my choise will always be for community developed product. I use Debian ever since version 3.0.... so let's say for more than 10 years, so I am really used to it and won't change it for any other OS as in my personal opinion, this is the most stable peace of software you can get.
Anyway... I completed the build, but it is running unstable because of errors in the landscape mode of the keyboard - I didn't implemented it good... as I am not java developer this is my learning process into java. I have traced the issue, checked out the logs and I know which line is causing the problem. This peace of code was not a problem when I builded CM 13, but some things differs in CM 14.1. Anyway... I've founded different implementations of this feature in other rom's, but I have to research it and try it out, because no other rom has proted this feature to nougat at this moment. I am doing my best to get it work properly, but I can't give exact time how long it will take. It won't be long, but it can take me couple of days to fix the issue.
If you have any other suggestions for other handy features, feel free to share it
Greetz
So... as cyanogenmod is shutting down... expected move as 3 weeks ago Steve Kondik lefted cyanogen inc. I will move this ROM to "LineageOS" - the cyanogenmod community follower. Check the website - http://lineageos.org/ This is good, because cyanogenmod was making bad deals... and this was bad for the whole android community as Cyanogenmod is the leader in ROM community. Well... in my point of view - bad deals comes when business is involved... the quality of the product becomes second... and the main priority is money profit. Anyway... every community based product will be better. So I am happy because of this move.
Let's be patient and see what's coming. I won't develop this ROM any further as Cyanogenmod (the base of this rom) is shutting down. As I don't know what the new ROM will provide, is for me hard to say how this ROM will continue.
What about this ROM now? Well... I didn't made any big changes to it. If some one wants, I can give a link to test build based om Nougat - it runs stable, with only feature provided - disable fullscreen keyboard in landscape. No prebuilt apps or anything else.
VoLTE Supported...
And add some screenshots
Deepak5310 said:
VoLTE Supported...
And add some screenshots
Click to expand...
Click to collapse
Yes, VoLTE supported. I didn't provided screenshot's, as they will be the same as Cyanogenmod.
rpangelov said:
Yes, VoLTE supported. I didn't provided screenshot's, as they will be the same as Cyanogenmod.
Click to expand...
Click to collapse
CM 13 based
Deepak5310 said:
CM 13 based
Click to expand...
Click to collapse
I am editing the post - wait couple of minutes and you will see new link with build CM 14.1 based.
PS: As I don't develop it any further, because I will move it to another base-rom, CM14.1 based build was meant to be tested, but it runs stable. I use it without problems.
rpangelov said:
I am editing the post - wait couple of minutes and you will see new link with build CM 14.1 based.
Click to expand...
Click to collapse
Thanks sir

⚡ LIGHT PATCH ⚡

READ CAREFULLY BEFORE YOU START! THE PATCH IS NOT A ROM/MOD/KERNEL​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ABOUT​Rethink about Android customizations. Make it Yours!
The Light Patch ZIP File is a advanced multifunctional Utility, based on the famous AROMA for custom recovery Replacements like TWRP. It comes with everything that is needed to fully unleash the Potential of Your Device. Advanced Techniques from Google, Sony, HTC, Qualcomm and many Others combined into a single Package which fits for all Snapdragon Flagships running the very latest Android Versions. One to rule them All! Use a AOSP System as Base and get the Quality of a Stock Firmware, decide about the System Content, gain extra functionalities and enhance Your Device on a unsuspected Way. Everything is based on Years of intensive Research and deep going Changes on Android which You will find nowhere else. There are to many Features and Changes to list them all, but take a look at the Feature List and check out the insanely long Changelog which includes the Changes of Hundreds of Releases. Or just give it a try now, read the Instructions and Start off! AROMA will guide You thru the whole Patch Utility...​
FEATURES
AROMA 3.0 POWERED BASE
OPTIMIZED MAGISK INCLUDED
OPTIMIZED SUPERSU INCLUDED
OPTIMIZED GAPPS INCLUDED
OPTIMIZED BUSYBOX INCLUDED
DEVICE TRANSFORMING OPTIONS
DPI/DEVICE UI TYPE OPTIONS
LIGHT EXCLUSIVE EXTRA OPTION
OPTIONAL DEBLOATING OPTIONS
UI SOUND OPTIONS
STORAGE WIPE OPTIONS
BOOTANIMATION OPTIONS
LIGHT AUDIO SYSTEM OPTION
4K AND HDR SUPPORT ENABLED
PARTITION TRIMMING ENABLED
USEFUL INIT.D SCRIPTS ENABLED
EXCLUSIVE PIXEL FEATURES
EXCLUSIVE OEM FEATURES
SETUP WIZARD ROTATION
LOCKSCREEN ROTATION
HOMESCREEN ROTATION
ENHANCED UI QUALITY
SMOOTHER UI RENDERING
ENHANCED APP RENDERING
ENHANCED GAMING HANDLING
ENHANCED SENSOR HANDLING
ENHANCED NETWORK HANDLING
ENHANCED ENERGY CONSUMPTION
ENHANCED STORAGE HANDLING
ENHANCED VOICE RECOGNITION
ADVANCED BLUETOOTH SERVICES
ADVANCED AUDIO HANDLING IN/OUTPUT
VARIOUS PERFORMANCE IMPROVEMENTS
ADVANCED VISUAL HANDLING IN/OUTPUT
EXTRA QUALCOMM SERVICES ENABLED
EXTRA STORAGE FEATURES ENABLED
ADVANCED ANDROID SERVICES ENABLED
CONFIGURATION OF NOT EXISTING SETTINGS
BATTERY DRAINING LOGS/SERVICES DISABLED
BATTERY CALIBRATION AFTER CHARGING
ZYGOTE HANDLING OPTIMIZED
VM HANDLING OPTIMIZED
DEX2OAT OPTIMIZED
SERIAL NUMBER UNDER SETTINGS
FORCED ENCRYPTION DISABLED
DM VERITY DISABLED
(YOU ARE FOLLOWING A DEVELOPMENT PROJECT HERE)
(FEATURES MAY CHANGE OVER THE TIME)
(PROBLEMS ARE POSSIBLE)
(GIVE FEEDBACK)
GOOGLE APPS
OPEN GAPPS SUPER LIGHT VERSION
CONTAINING
CHROME/WEBVIEW
DIALER/CONTACTS
SEARCH/ASSISTANT
PLAY STORE
STORAGEMANAGER
AND ALL NEEDED EXTRA SERVICES
WHICH ARE NOT VISIBLE IN THE LAUNCHER
REQUIREMENTS
64BIT SNAPDRAGON SOC
UNLOCKED BOOTLOADER
TWRP RECOVERY SYSTEM
AOSP BASED ROM/OS
DOWNLOAD
INLIGHTNING WEBSITE / LIGHT
(READ THE FIRST THREE POSTS OF THIS THREAD BEFORE DOWNLOADING THE PATCH)
(SHARING DIRECT LINKS TO OUR FILES OR MIRRORING OUR WORK IS NOT DESIRED)
XDA:DevDB Information
LIGHT PATCH, Tool/Utility for the Google Pixel XL
Contributors
Miustone
Version Information
Status: Stable
Created 2017-09-30
Last Updated 2017-11-01
Q&A
Q1: HOW TO USE THE PATCH?
A1: TAKE A LOOK ON POST #3!
Q2: CAN I USE THE PATCH ON MY STOCK DEVICE FIRMWARE?
A1: DEPENDS ON THE OS. TEST BY YOURSELF AND GIVE FEEDBACK FOR OTHER USERS!
Q3: WHICH PATCH WIPE OPTION SHOULD I CHOOSE?
A1: IF YOU'VE CLEAN FLASHED A ROM/OS CAN YOU CHOOSE THE BASIC WIPE!
A2: IF YOU'VE NOT WIPED AND FLASHED A NEW ROM/OS BEFORE USE THE CLEAN OR FULL WIPE!
Q4: THE DISPLAY IS FROZEN WHILE PATCHING, WHAT TO DO?
A1: NO WORRIES, THE PATCH WILL INSTALL BUT TWRP HAS PERFORMANCE ISSUES.
A2: JUST TAP THE RIGHT BOTTOM EDGE WHERE THE NEXT BUTTON IS AND PRESS IT A FEW TIMES.
A3: YOUR DEVICE SHOULD VIBRATE WHEN YOU HIT THE NEXT BUTTON. 3 VIBRATIONS AND YOU'RE DONE!
Q5: SOME APPS ARE CLOSING OR NOT RECEIVING MESSAGES WHILE SCREEN OFF, WHY!?
A1: MAKE SURE YOU'VE CONFIGURED THE SMART BATTERY APP / PUT THEM TO NEVER SLEEP!
Q6: HOW TO SET UP SMART BATTERY?
A1: USE THE MORE SHORTCUTS APP AND START THE SMART BATTERY ACTIVITY!
A2: OR JUST WAIT FOR A NOTIFICATION FROM THE APP. IT COMES WHEN THE SCREEN IS OFF!
Q7: MY WALLPAPERS ARE GONE AFTER WAKING THE DEVICE UP, WHATS WRONG?
A1: MAKE SURE YOU'VE WHITELISTED GOOGLE BACKGROUNDS IN SMART BATTERY!
Q8: I DON'T FIND HELP ON THIS THREAD, WHAT TO DO?
A1: CHECK THE OTHER LIGHT PATCH THREADS. ONE PATCH FOR ALL DEVICES!
Q9: WHAT DOES THE PATCH DO?
A1: GO BACK TO THE FIRST POST AND START READING FROM THERE!
Questions left? Ask @Miustone
Instructions:
BOOT TO THE RECOVERY/TWRP
WIPE DATA, SYSTEM AND THE CACHES
FLASH A AOSP OS/ROM/FIRMWARE/KERNEL
GO TO THE REBOOT MENU AND SELECT RECOVERY
FLASH THE PATCH BEFORE BOOTING INTO THE SYSTEM
REBOOT TO THE SYSTEM NOW. THE FIRST START MAY TAKE SOME TIME
And that's it. If You don't want to flash a new ROM, just choose the Clean or Full Wipe within the Patch.
Welcome to the Family Pixel XL Users! Enjoy full Support from Me for the Pixel and Pixel XL with the coming V1.3 of the PATCH...
BR
So is this a Rom/Custom Kernel or is it a Rom mod? Is it compatible with Android Nougat or Android Oreo?
Leeum said:
So is this a Rom/Custom Kernel or is it a Rom mod? Is it compatible with Android Nougat or Android Oreo?
Click to expand...
Click to collapse
No Mod, No ROM. It's a PATCH which is basically a ROM but it does not include any Device Specific Firmware Files, means Support for all Flagship Snapdragon 64Bit Devices in One ZIP. It Optimizes Your Device without killing Safety Net or any Services like Netflix or Super Mario Run, PokeMon Go and so on.
Dunno about Oreo Support yet. My Axon 7 is still running 7.1.2 but it should work flawless with the next Version of the PATCH. No Warranty so do Backups before flashing it :fingers-crossed:
BTW: The Patch enables all Pixel Exclusive Stock Features on AOSP, and that's what it's meant for. Bringing uber Stock Quality to AOSP. Hope You will like it on the Pixel Devices Folks! Enjoy!
EDIT: I will start the upload of V1.3 in some Hours, it includes the Mgaisk 14.2 Beta as default Option which should enable Support for the Pixel Devices. Fingers crossed for You!
Miustone said:
No Mod, No ROM. It's a PATCH which is basically a ROM but it does not include any Device Specific Firmware Files, means Support for all Flagship Snapdragon 64Bit Devices in One ZIP. It Optimizes Your Device without killing Safety Net or any Services like Netflix or Super Mario Run, PokeMon Go and so on.
Dunno about Oreo Support yet. My Axon 7 is still running 7.1.2 but it should work flawless with the next Version of the PATCH. No Warranty so do Backups before flashing it :fingers-crossed:
BTW: The Patch enables all Pixel Exclusive Stock Features on AOSP, and that's what it's meant for. Bringing uber Stock Quality to AOSP. Hope You will like it on the Pixel Devices Folks! Enjoy!
EDIT: I will start the upload of V1.3 in some Hours, it includes the Mgaisk 14.2 Beta as default Option which should enable Support for the Pixel Devices. Fingers crossed for You!
Click to expand...
Click to collapse
Thanks mate. I am running PureNexus Rom as LineageOS etc just reboots for me.
Holy cow. This sounds amazing. Thanks. This may be a stupid question, but I don't want to mess anything up, do I need to be running a stock rom? I'm using Pure Nexus right now. Can I flash this while using PN, or is this only for Stock users?
Leeum said:
Thanks mate. I am running PureNexus Rom as LineageOS etc just reboots for me.
Click to expand...
Click to collapse
Think You should wait for V1.3. Still working on it. Testing... Can't wait to upload it!
whitak3r said:
Holy cow. This sounds amazing. Thanks. This may be a stupid question, but I don't want to mess anything up, do I need to be running a stock rom? I'm using Pure Nexus right now. Can I flash this while using PN, or is this only for Stock users?
Click to expand...
Click to collapse
AOSP is the best Base for the Patch. Pure Nexus should be a good Base to gain more than a Pixel like Experience- Unlimited Photo Uploads and Tethering besides instant Apps should be also enabled. And Check out the 4K HDR Options in Apps like Youtube... There are to many Features to list them all alone
BR:angel:
Miustone said:
Think You should wait for V1.3. Still working on it. Testing... Can't wait to upload it!
AOSP is the best Base for the Patch. Pure Nexus should be a good Base to gain more than a Pixel like Experience- Unlimited Photo Uploads and Tethering besides instant Apps should be also enabled. And Check out the 4K HDR Options in Apps like Youtube... There are to many Features to list them all alone
BR:angel:
Click to expand...
Click to collapse
Awesome thank you! Just wanted to make sure it would work. I'm so glad that there is still more and more stuff coming to the Pixel! First Magisk and now this!
whitak3r said:
Awesome thank you! Just wanted to make sure it would work. I'm so glad that there is still more and more stuff coming to the Pixel! First Magisk and now this!
Click to expand...
Click to collapse
Upload has started, one Hour left. You will find the File in the Releases Folder. Google Drive handles it pretty well...
Let Me know how it works for You Folks!
EDIT: Would be Awesome to get a dump of a Oreo Stock System from the Pixel XL ! There is more to merge and i need to update some Google Specific Files including Features for the Camera...
Just downloaded version 1.3. I'm at work but I will get it off my GDrive when I get home and test it out. Thanks again man!
One other question. Will it work with ElementalX Kernel?
Leeum said:
One other question. Will it work with ElementalX Kernel?
Click to expand...
Click to collapse
Kernel related problems in combination with my Patch are not possible as far I know. Some Kernels may just work better than Others. Especially that One's who are including the right patches for Audio and Performance...
I'd like to know what things like "OPTIMIZED SUPERSU INCLUDED" mean. What is done? Why are GAPPS optimized?
Things we should know before flashing this to our phones tbh
boostnek9 said:
I'd like to know what things like "OPTIMIZED SUPERSU INCLUDED" mean. What is done? Why are GAPPS optimized?
Things we should know before flashing this to our phones tbh
Click to expand...
Click to collapse
I could write Books about what's done. SuperSU isn't longer available since V1.3 but was included with changed Settings in previous Versions. The GApps are debloated as far as possible while providing all extra Services from Google like Keyboards, WebView/Chrome, TTS, Storage Manager and so. Means actually a Light Version of the Super Open GApps. The Threads are getting a update asap. from Me including all latest available Features. I haven't done anything for a while since I'm moved to a new Home and all that. But think I'm proofed since I'm doing my Patch already for Years on XDA
Miustone said:
I could write Books about what's done. SuperSU isn't longer available since V1.3 but was included with changed Settings in previous Versions. The GApps are debloated as far as possible while providing all extra Services from Google like Keyboards, WebView/Chrome, TTS, Storage Manager and so. Means actually a Light Version of the Super Open GApps. The Threads are getting a update asap. from Me including all latest available Features. I haven't done anything for a while since I'm moved to a new Home and all that. But think I'm proofed since I'm doing my Patch already for Years on XDA
Click to expand...
Click to collapse
Oh ya I'm not saying I don't trust you, I just wanted to know what I'm putting on my phone before I do. Thanks for your info.
Also, where is the download ? I see the link and go to the site but the releases show last updated in July... Is this out yet?
boostnek9 said:
Oh ya I'm not saying I don't trust you, I just wanted to know what I'm putting on my phone before I do. Thanks for your info.
Also, where is the download ? I see the link and go to the site but the releases show last updated in July... Is this out yet?
Click to expand...
Click to collapse
Glad to hear that :angel:
I will redo the Feature Lists this Weekend, hoping for a better Overview. The Homepage gets also some Updates. Let Me know if i missing something important on the Descriptions!
And about the Download: The Release Folder includes always only One File. The File in there is always the latest Patch. The File Names are caused by My automated ZIP Process, and Google Drive handles it by making Copies from older uploaded Versions (Backups). Saves Space and avoids that Users download older Versions. Hope that makes Sense somehow...
BR
not a chance in hell i'd install something like this without looking over the source...
drdrewdown said:
not a chance in hell i'd install something like this without looking over the source...
Click to expand...
Click to collapse
There is nothing included which can't be opened or overviewed. Concerns are misguided here...
Any ROMs/APPs could include more Spyware and Backdoors than My Patch lol

[ROM][GSI] BlissRoms [11.8] 9.0 [Stable][arm64 a/ab][gapps optional] Official

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
team bliss is pleased to present to you
BLISS BASS FOR TREBLE based on Android 9 Pie
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Notice
The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.​We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
Please do not ask for ETA's
We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts
AIO Thread
Bliss Source
[url]https://github.com/BlissRoms[/URL]
BlissRoms Devices Source
[url]https://github.com/BlissRoms-Devices[/URL]
BlissRoms Kernel Source
[url]https://github.com/BlissRoms-Kernels[/URL]
BlissRoms Vendor Source
[url]https://github.com/BlissRoms-Vendor[/URL]
11.8 A/B Build Stock (without Gapps)
11.8 A-Only Build Stock (without Gapps)
OpenGApps Pico (only size that will work besides aroma with barely any apps added)
11.7 A/B Build with Gapps built in
11.7 A-Only Build with Gapps built in
Bliss Builds Website
CUSTOM VBMETA.IMG AVAILABLE TO PIXEL 1/2/3 DEVICES
IF YOU HAVE FOUND YOU NEEDED TO FLASH SOMETHING ELSE IN ADDITION TO THE GSI, PLEASE LET ME KNOW IN THE THREAD AND I WILL ADD IT TO THE OP
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom. Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.​
Download the latest Bliss Rom GSI
Boot into bootloader
Flash Bliss Rom GSI (and custom vbmeta.img if necessary)
Reboot into Rom and let it setup
Flash TWRP installer after booting TWRP.img
Reboot to recovery
Flash Root of your choice
First boot may take some time, be patient
BUGS: none that i can find, you tell me
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
After downloading the Catlog app, go to the app settings, and change the log level to Debug.​Clear all previous logs and take the exact steps to produce the error you are receiving.​As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.​Copy and paste the entire log either to Hastebin or Pastebin​Save the log, and copy and paste the link into the forum with a brief description of the error.
@Jackeagle, @electrikjesus,@rfwaterspf1, @Makaveli_da_dev, @ElfinJNoty, @BitOBSessiOn, @customworx,
@nilac, @sixohtew, @aclegg2011, @Roger.T, @T.M.Wrath, @kanttii, @rev3nt3ch, @techfreak243,@SuperDroidBond, @USA_RedDragon, @bcrichster,
@deadmanxXD, @krittin98, @BlackScorpion, @techexhibeo, @droidbot, @siphonay, @pacer456, @nitin1438, @theGeekyLad, @kunalshah912, @regalstreak, @lordarcadius
A huge thanks to Chainfire, CM/LineageOS, phhusson, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Team Bliss aims to develop and maintain various OS & software projects for educational and the Android community building purposes. Team membership consist of and provides:
training, development opportunities, design opportunities, build servers, download servers, design & development software,as well as professionals and mentors in all fields revolving around Android development.​If someone wants to donate, please do so via this PayPal link:
PayPal Link
WE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
We receive a small donation each time you make a purchase with “Amazon Smile”:
https://smile.amazon.com/ch/82-3580195
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.
Website
https://blissroms.com
Telegram Communities
https://t.me/Team_Bliss_Community
https://t.me/blissx86[/CENTER]
https://t.me/Team_Bliss_Build_Support
https://t.me/Project_Xtremis
Official Platform Links
https://www.facebook.comBlissFamilyOfROMs
https://plus.google.com/communities/118265887490106132524
https://twitter.com/Bliss_ROMs
https://www.instagram.com/blissroms
Thank you for using Bliss! And as always: #StayBlissful
Flashing Instructions for various devices
1. Pocophone F1
-Pocophone F1 on Android Pie with custom ROM AOSiP
- factory reset phone in TWRP.
- ( probably not necessary - but wiped cache dalvik cache , system , data , internal storage)
- since I (mistakenly ?) wiped "system" I reinstalled custom ROM AOSiP and then installed GSI on top of the AOSiP
- rebooted successfully into GSI
( if you wipe "system" and then install GSI you cannot boot into the phone)
- for pocophone users:
I have beryllium-9.4.1-9.0-vendor-firware.zip installed
2. Razer phone 1
https://docs.google.com/document/d/1F7Yhqir9JV9Y72pSXD6Fag3hIMbyQjUaSiLTy35xFHk/edit?usp=drivesdk
3. Pixel/xl 1/2/3
- easiest way to flash this GSI and know you did it correctly, where most stuff should work, download the factory images for pie 9.0.0 and delete the system.img and the vbmeta.img
- download the GSI and rename it to system.img, and download the custom vbmeta.img and put both downloaded files back into the factory images
- use the ./flashall.sh/bat script to flash all the images in correct order
- when you're done, wipe data with fastboot -w
- reboot to rom and make sure you're on the GSI then flash twrp so you can root or maybe backup or restore previous builds
4. YOUR PHONE INSTRUCTIONS HERE - POST WHAT YOU DID TO MAKE YOUR PHONE BOOT THE GSI​
Plz give a description about byilds variants like gapps , stock , foss and go
Afaik -
gapps- gapps included
Foss- free open source apps included
Stock - no additional apps included maybe
Go- for low end devices (go variant)
Plz correct if something is incorrect.
Updated topic and OP to reflect gapps being added to build
Shobit Joura said:
Plz give a description about byilds variants like gapps , stock , foss and go
Afaik -
gapps- gapps included
Foss- free open source apps included
Stock - no additional apps included maybe
Go- for low end devices (go variant)
Plz correct if something is incorrect.
Click to expand...
Click to collapse
Thanks for reminding me, I forgot that the open gapps was still listed, even though this GSI has gapps built in. Also I changed the topic to reflect on this.
sixohtew said:
Thanks for reminding me, I forgot that the open gapps was still listed, even though this GSI has gapps built in. Also I changed the topic to reflect on this.
Click to expand...
Click to collapse
I wanna flash but may i know that will this rom be maintained regularly (monthly basis?)
And when is april security patch including building coming?
Shobit Joura said:
I wanna flash but may i know that will this rom be maintained regularly (monthly basis?)
And when is april security patch including building coming?
Click to expand...
Click to collapse
This will be a weekly/monthly updated, depending on our Gerrit being updated. If there are many changes being pushed upstream, then it will be weekly, if not it will be monthly with updated security patches on or near the 5th of every month. This is honestly the most stable GSI I've ever flashed. Once I test my newest build to see if the VoLTE and VoWifi commits worked, I will update OP with new test build and updated reasonings. Happy flashing!
arm64_a please....
sixohtew said:
This will be a weekly/monthly updated, depending on our Gerrit being updated. If there are many changes being pushed upstream, then it will be weekly, if not it will be monthly with updated security patches on or near the 5th of every month. This is honestly the most stable GSI I've ever flashed. Once I test my newest build to see if the VoLTE and VoWifi commits worked, I will update OP with new test build and updated reasonings. Happy flashing!
Click to expand...
Click to collapse
Thanks for the info ,
Can we have some screenshots?
sixohtew said:
This will be a weekly/monthly updated, depending on our Gerrit being updated. If there are many changes being pushed upstream, then it will be weekly, if not it will be monthly with updated security patches on or near the 5th of every month. This is honestly the most stable GSI I've ever flashed. Once I test my newest build to see if the VoLTE and VoWifi commits worked, I will update OP with new test build and updated reasonings. Happy flashing!
Click to expand...
Click to collapse
Thx for ur hard work :good:
Deleted by user
Please add arm32 variant
thanks, looks really interesting. Long time ago since I last used bliss... I'm gonna build aonly and try it out
Deleted by user
@electrikjesus there is no aonly GSI, just ab
Any chance of a ARM64-A gsi image only, I see only A/B, many thanks.
Patience people. We're working on it
I will be building an aonly version in just a few minutes, and it will take about an hour and a half to complete so there will be a version for a and a/b. Then depending on requests, I will build an arm32, but that's not too likely as Google has dropped support for 32bit devices
sixohtew said:
I will be building an aonly version in just a few minutes, and it will take about an hour and a half to complete so there will be a version for a and a/b. Then depending on requests, I will build an arm32, but that's not too likely as Google has dropped support for 32bit devices
Click to expand...
Click to collapse
oh alright... and I just finshed building an aonly version myself. nevermind, at least I know it´s working :good:
fyi: a-only version is running fine
Many many thanks for your hard work. I have your Test build (03.04.) installed and all works fine on my Xaomi Mi A2 Lite [emoji4]
Gesendet von meinem Phh-Treble with GApps mit Tapatalk
updated OP with new a/b build and new a-only build - both of which have VoLTE and VoWifi. Also I added screenshots of the settings, just to give new users an idea of what Bliss is all about!

Development [ROM][13][UNOFFICIAL] LineageOS 20 [Sunny][Mojito]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Your warranty is now void...
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
About
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Download
- 20230524
Notes
- Don't change kernel.
- Custom recoveries are not allowed to be used.
- Custom kernels are not allowed to be used.
- Inlined with NetErnels.
- SafetyNet is OK.
- Signature Spoofing is OK.
- SELinux is enforcing.
- Encryption is enabled by default so decrypting is not allowed.
- Only use Lineage recovery to flash/format.
- 14.0.3.0 FW is recommended to use.
Flashing instructions
- Download ROM zip, recovery zip and fw if needed.
- Boot to bootloader.
- Run fastboot update LOS20_Recovery_*.zip , according to the build downloaded.
- Run fastboot reboot recovery
- Flash FW if needed (reboot to recovery after flashing)
- Format data with the recovery.
- Click Apply Update.
- Select your preferred method (Sideload/SDCard)
(For Sideload run : adb sideload lineage*.zip)
(For SDCard just select the zip from where you saved it)
- Reboot to system
Update Instructions
- Download ROM zip
- Flash FW if updated (reboot to recovery after flashing)
- Click Apply Update.
- Select your preferred method (Sideload/SDCard)
- Reboot to system
GPL Compliance
- Kernel Source : https://github.com/NetErnels/android_kernel_xiaomi_sunny
Telegram Support
- My PM
- Support Chat
Changelogs
24-May-2023
-- Device Changelog --
Updated blobs to V14.0.3.0.SKGMIXM
Set override_doze_mode prop
Switched to User Build
Added Implementation of ST2W (Single Tap to Wake)
Inherited common perf components from AOSPA
Inherited common Adreno components (updates adreno blobs to [email protected])
Drop perf blobs listing since its inherited from common
Drop Thermal Profiles/Doze from XiaomiParts
Drop PowerOffAlarm.
-- ROM Changelog --
May 2023 Security Patch (r43)
Recovery is now able to flash unsigned zips (magisk , fw , etc).
Removed some more logspam.
Switched to PIHooks for SafetyNet/Play Integrity.
Dropped Google Photos Spoofing.
Dropped Updater.
Ported CLO's Boost Framework.
Updated Prebuilts GApps.
Added MicroG build.
Switch to AVC 3.1 for screen recorder.
Compile for Perf.
Disable ripple animation on unlock.
Remove default aspect ratio limit for old apps.
Change the default value of sync mode to NORMAL.
Require unlocking to use sensitive QS tiles.
Add support for unlinked ringer streams
Enable media background turbulence.
Enable media player surface ripple on button press.
Add kill action to app shortcuts popup
Introduce overview scrolling scale animation.
Show clear all button in recents overview.
Add uninstall button to system. shortcuts.
Only warn on SPL downgrade.
Added Pixel Charger.
Added some missing spanish strings.
Make kernel version clickable.
Expose radio info (##4636##).
WiFi: Remove country code checking.
Move Extra Dim feature to display.
Add a preference to battery optimization page.
Open app when clicking on icon in App Info.
Finally.
I'm gonna have to wait a bit, my device is still locked and I want to wait and see a bit before I **** something up.
What isn't working yet? Really dumb to ask at this point, but what is missing from the ROM to become official?
ChristianWS said:
Finally.
I'm gonna have to wait a bit, my device is still locked and I want to wait and see a bit before I **** something up.
What isn't working yet? Really dumb to ask at this point, but what is missing from the ROM to become official?
Click to expand...
Click to collapse
everything is working... i'm using this rom since release and i finally found my daily driver rom...
maybe you will face some lags on apps but can be easily fixed by adding some props to build.prop (i'll do on next build)
About Official... LineageOS Requeriments are very strict and i'm not a experienced developer (i'm just learning) so i can't make this official
So , i'll provide monthly updates as long as i have server to build it.
Long Live LineageOS...
Cant wait to use it as a daily driver..
@alonsoj636 this is awesome!
many of us have been waiting for this for so long! a true ROM diamond!
..and I'm gonna look into it soon, I need to have a few days off to tinker around with it.
I wonder if it's still possible with haystack needle to get signature spoofing working and with it microG.
also, i guess, after flashing FW 13.x there is no way back to 12.x and lower due to anti-rollback protections.. so it's a one-way ticket to flash.
Zirila said:
@alonsoj636 this is awesome!
many of us have been waiting for this for so long! a true ROM diamond!
..and I'm gonna look into it soon, I need to have a few days off to tinker around with it.
I wonder if it's still possible with haystack needle to get signature spoofing working and with it microG.
also, i guess, after flashing FW 13.x there is no way back to 12.x and lower due to anti-rollback protections.. so it's a one-way ticket to flash.
Click to expand...
Click to collapse
since i use Google Services i didn't look at spoofing and microg but you can always try
For next build i'll look into it
About anti - rollback you can downgrade MIUI but you should ALWAYS choose the correct variant that the phone came with (Global , India , Indonesia , EEA , etc) and avoid locking the bootloader
alonsoj636 said:
About Official... LineageOS Requeriments are very strict and i'm not a experienced developer (i'm just learning) so i can't make this official
Click to expand...
Click to collapse
Beggars can't be choosers and all of that, and I know LineageOS requirements are strict, but it doesn't really spark much confidence.
Let me rephrase that: what is missing from the ROM becoming official?
Hey, i have redmi note 10 pro, and I would love to use lineage 19 on my device. As redmi note 10 and 10 pro are so similar, can please tell if you faced issues while porting it, or was the process straight forward? ( I have never ported a rom before and have little knowledge).
Thank you!
ChristianWS said:
Beggars can't be choosers and all of that, and I know LineageOS requirements are strict, but it doesn't really spark much confidence.
Let me rephrase that: what is missing from the ROM becoming official?
Click to expand...
Click to collapse
i already answered you... everything is working and this ROM is stable enough to be official. But since I don't meet the requirements and I don't have much time to maintain it it will not be possible from my side... Maybe another developer can take Official LineageOS but meanwhile , i will maintain Unofficial.
Stan m said:
Hey, i have redmi note 10 pro, and I would love to use lineage 19 on my device. As redmi note 10 and 10 pro are so similar, can please tell if you faced issues while porting it, or was the process straight forward? ( I have never ported a rom before and have little knowledge).
Thank you!
Click to expand...
Click to collapse
They are completely different devices.
This is only for Redmi Note 10 (mojito/sunny)
alonsoj636 said:
They are completely different devices.
This is only for Redmi Note 10 (mojito/sunny)
Click to expand...
Click to collapse
Yeah. I am not asking if I can use this rom for my device. I am saying as they are similar, I just want to know if you had any problems during developing this rom. If you didn't have any problems, chances are I wont have problems either.
Thank you!
Stan m said:
Yeah. I am not asking if I can use this rom for my device. I am saying as they are similar, I just want to know if you had any problems during developing this rom. If you didn't have any problems, chances are I wont have problems either.
Thank you!
Click to expand...
Click to collapse
i didn't have any problems
alonsoj636 said:
i didn't have any problems
Click to expand...
Click to collapse
So downloaded lineage 19 source code, device tree, oss vendor, and complied them. That is all right?
Thank you!
Stan m said:
So downloaded lineage 19 source code, device tree, oss vendor, and complied them. That is all right?
Thank you!
Click to expand...
Click to collapse
device tree + common device tree + kernel tree + vendor tree + common vendor tree... i suggest to ask in your device community because this is a off-topic conversation
alonsoj636 said:
i already answered you... everything is working and this ROM is stable enough to be official. But since I don't meet the requirements and I don't have much time to maintain it it will not be possible from my side... Maybe another developer can take Official LineageOS but meanwhile , i will maintain Unofficial.
Click to expand...
Click to collapse
Okay, let me rephrase that again: what requirements aren't being met?
ChristianWS said:
Okay, let me rephrase that again: what requirements aren't being met?
Click to expand...
Click to collapse
Why don't you read the requirements yourself. Then it will be absolutely clear.
ChristianWS said:
Okay, let me rephrase that again: what requirements aren't being met?
Click to expand...
Click to collapse
time : i don't have enough time to take care of lineage os ... i just can do builds when i get time.
interest : i'm not currently interested on submitting any ROM to Official Status (reason : i don't care about official rules)
why the traffic network is on the center?
y'know our devices camera is on center right?
FNTX0230 said:
why the traffic network is on the center?
y'know our devices camera is on center right?
Click to expand...
Click to collapse
i have the device i know
ask lineage os developers , they doesn't allow the customization of the traffic monitor

Categories

Resources