{
"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
Related
{
"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?
{
"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... still valid?
*
* 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.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review ( http://review.lineageos.org ).
Important:
This thread is for stock LineageOS 13.0 and any mods, kernels or Xposed framework will not be supported.
If features, options or code is NOT in the official source code, it will not be in my builds.
Recommended Firmware:
Most recent firmware for OOS 3.6.1 is recommended.
Known Bugs:
None
Installation:
Download the zip(s)
Install a compatible Recovery (TWRP recovery recommended)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon http://opengapps.org/ ( I tested nano and stock pkgs)
Reboot
Note: Built in root is available in Dev Options, but I'd use magisk
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Downloads:
AFH
How to enable Volte.
You can read the full instructions HERE
XDA:DevDB Information
LOS 13.0 Unofficial, ROM for the OnePlus 2
Contributors
monark88, LineageOS Team & Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: OOS 3.6.1
Based On: LOS-13.0
Version Information
Status: Stable
Created 2018-01-21
Last Updated 2018-06-24
I know some of you may wonder why even post something as old as marshmallow. I still get a lot of use from LOS 13, and have been building it for myself for a while. I figured I'd upload the latest with Jan security patches, for those who want it. Happy flashing.
Not sure about the support we'll get from LOS going forward. They never merged February security patch, but they may have just been busy. We'll see.
does it have hal3 with hdr and all that cool quality we used in marshnallow?
chxei said:
does it have hal3 with hdr and all that cool quality we used in marshnallow?
Click to expand...
Click to collapse
It does, HAL3 and hdr
I run mine with amplify, greenify, android n-ify, gravitybox, and alert slider app
monark88 said:
LOS 13.0 Unofficial, ROM for the OnePlus 2
Click to expand...
Click to collapse
wow, this is great!
thank you mate!
You can get volte by flashing the kenzo patches. Just saying.
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Woodzrul said:
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Click to expand...
Click to collapse
The download link now points to a signed version. You can download it here:
https://www.androidfilehost.com/?fid=673956719939814327
using 22nd Jan build since yesterday.
I missed so much the great customization that CMTE brings to LOS!
as far as I can see 'til now, there's no issue at all with your ROM.
excellent work, thank you!
utkarsh102 said:
You can get volte by flashing the kenzo patches. Just saying.
Click to expand...
Click to collapse
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
GuyGotMadNameGame said:
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
Click to expand...
Click to collapse
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
I'll add this to the first post
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
Thanks for this. I updated first post.
Does anyone know of any cm13 theme which properly themes all the essential apps?
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
aiwan3 said:
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
Click to expand...
Click to collapse
I've got a new build, but nothing is significantly changed. I've been working on a custom kernel for MM, with extra governors and upstream merges. I'm running this ROM myself, so you can bet when there is a security patch, I'll upload it for us all.
I'm with you on anything above android 6.0. When LOS 14.x kernel was reworked, I was on RR unofficial. I remember the drastic changes. I compiled this not soon after and have been on it since. I've watched on the forums as everyone has scrambled after HAL3, and balancing HAL3 with HDR (or the lack there-of) and all the non-sense that goes with it.
Meanwhile we've got manufacturer supported blobs and code for everything our phone was meant to do, in a nice stable OS.
If you're reading this, and thinking about trying it, just download the ROM, flash xposed (or use xposed magisk) and get Android N-ify, Amplify, Greenify, Alert Slider, and GravityBox. You'll be kicking it on the OP2 old school, updated, and stable.
That's right. Many people don't seem to be very methodical when testing new ROMs. Mostly noted on comments about battery life. I don't use my phone much as the majority of my daily work / comms happens on PC - so its easy for me to see changes when I update the phone. I don't use gapps either, so my testing is purely based on the kernel and the ROM performance. This ROM can go up to 5-6 days in idle / light usage, whereas the latest official LineageOS 14.x is probably around 4 days same use. Feel free to test. Same applies to boeffla-kernels, they consume much more battery on idle than the LineageOS stock.
I'm not a developer myself but it's easy to understand that all this hacking for newer Android versions than the source code provided by manufacturer, can very easily lead into problems. It could be ok, but unfortunately many people always think that the latest is always better. I think it's fair to say that new android versions just complicate the menus and slow down devices more than the useful features provided. As long as security is updated, I don't really see any need for Oreo in my phone.
It's nice to hear that you are also testing for new things in kernel, I might test them if provided as separate update.zip. However I assume most people using LOS 13 or your build are probably after stability.
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Jackill said:
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Click to expand...
Click to collapse
Lol, for the most part (and in my opinion) yes.
The catch is that if you like the latest cutting edge features, we don't have that built-in here. All we offer is a stable phone that has ALL of the features working in some form or another, without wondering what will break in the next build.
For the record, I still flash Oreo ROMS on MultiROM to stay aware, but I run this as a daily driver.
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Pre-Disclaimer:
THIS IS AN DEV PREVIEW BUILD. The intent is to showcase what is coming up soon.
Please keep any problems with those builds in this thread, we don't accept any bugreports for preview builds anywhere else.
Also, we know this works on other treble devices. Please be aware that we can only provide limited support for those.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Notice:
This build includes GApps for now.
Before you flash, make sure you're on the latest 8.x stock builds, then flash the system.img in fastboot.
Download Mirror
Changelog
GitHub
Gerrit
Device and Kernel sources
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Honor View 10
Contributors
Myself5, CarbonROM, berkeley-dev Team
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-02-22
Last Updated 2018-04-15
Many thanks for bring us this ROM
Enviado desde mi BKL-L09 mediante Tapatalk
Great. Now development has gained speed. Love to see these roms for our beloved v10
Nice job in the release Chris!
Sweet. Nice job
Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
shihabsoft said:
Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?
Click to expand...
Click to collapse
Not yet, but we're working on it.
sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
I guess you could. I honestly didn't try.
Myself5 said:
Not yet, but we're working on it.
I guess you could. I honestly didn't try.
Click to expand...
Click to collapse
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device
sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
U can try flashing like a img in install menu. But idk if it works [emoji17]
Enviado desde mi BKL-L09 mediante Tapatalk
What its caffeine?
When you implement fingerprint gestures?
VivekBhagat said:
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device
Click to expand...
Click to collapse
Most vendors define those gestures as keyevents. Huawei obviously uses an API to perform them (and not native Linux keyevents support). Anyways, you have a plethora of third party apps that can do this for you.
Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.
BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
Interceptor777 said:
Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.
Click to expand...
Click to collapse
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you
BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Fingerprint gestures should be in the next build
download link not working...
ink718 said:
download link not working...
Click to expand...
Click to collapse
It's working. Just downloaded.
Myself5 said:
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you
Click to expand...
Click to collapse
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)
Interceptor777 said:
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)
Click to expand...
Click to collapse
I never said it can't be disabled
As a slight OT: its not mandatory to fully disable AVB on ROMs that are designed for taimen. taimen ROMs ship vbmeta images, that contain the AVB signatures. Due to the design its necessary to disable AVB for /vendor, which is done in the kernel by removing the AVB mount flag in the dtb. Although we're currently looking into properly generating the vendor avb signatures too.
Nonetheless, flashable GApps are likely going to cross those plans and will require to disable AVB on system. Therefore, I'd be happy if you could share that AVB disabler zip me (or release it to the public) so that @frap129 and me can do some testing with seperate GApps.
Now on to your question. I just spent an hour trying to gather some facts for the following statement:
Treble is not supposed to give you "one ROM for all devices", nor will it ever be able to provide just that.
Trebles requirement is that you can use "stock AOSP" on the device. Yes. HOWEVER: That doesn't mean it has to the be same single AOSP image for every device. Treble still requires configurations on that System image.
The system images VNDK is configured to work with an 8.0 treble vendor. That would mean you need to use an 8.0 vendor on your Pixel too.
The compatibility matrix and the manifest.xml on system specify what HAL treble has to expect/load from /vendor. Those likely differ.
There will always be some small overlay differences, features that one device supports which the other doesn't or configs that differ. Auto-brightness steps would be a good example for that.
It is true, that this ROM works on multiple devices, yes. So far, those are pretty much all very similiar in terms of HALs to load and hardware. There is barely any difference between the View 10, Mate 10, Mate 10 Pro and others. Things that are different are handled in the kernel (like the Display Technology) and don't affect HALs.
TL;DR + My personal opinion: Whereas treble ROMs might boot (assuming you match all those requirements) a "common ROM for all devices" (which I am starting to think is what everyone expects from treble) is not what you want to use, nor what treble has been designed for.
A new build (systemCarbon_20180303.img) has been uploaded.
It includes support for the US Model, and Fingerprint Gestures. To enable them, go to Settings -> CarbonFibers -> Buttons and tick enable navbar. That will disable the navbar and automatically enable the FPC gestures.
Additionally some new features got merged to the codebase. Happy flashing
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Known issues:
....
Instructions:
Download the latest build, official TWRP (3.3.0 and newer)
Boot the downloaded TWRP via fastboot
Flash the latest build
Reboot
Downloads:
Unofficial build: SourceForge-CAN EAT YOUR CAT
Official Rom and recovery: LineageOS
Google Apps: OpenGapps
XDA:DevDB Information
LineageOS 17.1 Harpia, ROM for the Moto G4 Play
Contributors
jeferson1979
althafvly
Device tree
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: lineage
Version Information
Status: Stable
Current Stable Version: 17.1
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-03-22
Reserved
Always giving thanks to @facuarmo and @Akyanonimous for the great support
Help. i tried to flash this ROM and my phone have bootloop.
I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.
Indiawallah71 said:
I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.
Click to expand...
Click to collapse
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.
Indiawallah71 said:
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.
Click to expand...
Click to collapse
Yes, i did every step to flash this ROM but no result. The phone have bootloop.
latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.
bacanos said:
latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.
Click to expand...
Click to collapse
Thank you very much. You are an genius.
@jeferson1979 Your roms are what a rom should be! I have never thought that android 10 can run this smooth in this tiny device. All Thanks to you. Rom is very stable and is best rom available right now after AEX pie which is again your offering.
Unlike past developers your focus is more towards usage and fixing things rather than pure compiling/half baked pieces and that's what old time developing was...
Thanks to keeping this device alive. I use it because of it's light and small and easy to carry.
Now the only thing remaining is- I guess SELinux.
Thanks for all the work, I will flash this later today and post my feelings. Would it be possible to make this an official build? I loved the automatic updates via OTA from the official builds.
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
you can manually set SELinux to enforcing by enabling the terminal shell in the Developer options and using the command, "setenforce enforcing"
this enables enforcing but i have no idea if the SELinux policy is written or doing what it needs to be doing, and this manual enforcing only lasts until reboot. does anyone know more on this subject?
Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
That's great, I'll be waiting for the next update. After a day using it, I have to say that it is indeed a wonderful ROM, very fluid and responsive.
Flashed this ROM, till now everything works great. Thank you!
Gesendet von meinem GM1903 mit Tapatalk
jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.
newinnov said:
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.
Click to expand...
Click to collapse
You will see some minor improvement at memory management, but we will loose in other side. Maybe we can do some tests
I agree with newinnov. In fact i think it should be nice for the LineageOS team to keep supporting older devices (like ours) officially but in Android GO form. It would keep millions of phones out of landfills.
In our case I think the benefits overcome the loses. At this point i'm sure all of us are using our g4p for bare minimun tasks like whatsapp, email, browsing, social networking, and such. Mostly no functionality-intensive apps. Given that all of that can be done with Android GO i don't think we would lose that much
Warning: bugs and outdated SP ahead...
Spoiler
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Stellar OS is an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
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.
Click to expand...
Click to collapse
We offer vanilla and gapps variants. If you install a vanilla variant, the only supported Gapps package is MindTheGapps (gapps builds are not available for a few devices due to space issues).
Download & instructions:
Build 23th September 2021
• 1.1 source update (September SP + new features)
• Fixed fast charging display
Vanilla | Gapps
Old releases:
Spoiler
Build 12th August 2021
Initial release
If you are coming from an older build (beta testers), clean flash is required
Vanilla | Gapps
IMPORTANT: If you are coming from another ROM, you need to format data (there where you type yes in twrp).
IMPORTANT: OTA updates require enabling recovery update in Setup Wizard (or, if you already set your device up developer options) - they do not support TWRP.
About:
Features:
All Mint 2.1 features
September security patch
SafetyNet passing WITHOUT Magisk Hide
Many optimizations
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Stellar Tweaks customization section
Navbar Tuner
Improved Trebuchet+
OmniJaws weather service
Many lockscreen clocks
Statusbar ticker
Signed official builds
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more (we accept suggestions)
The focus for the inital release was an neccessary set of tweaks and optimizing android.
What's working:
WiFi
Camera and Camcorder
Bluetooth
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE
USB tethering/audio
SELinux: Enforcing
Bugs:
You tell me
Sources are available at https://github.com/Stellar-OS and https://github.com/Stellar-Devices
Screenshots from ocean are attached
ROM OS Version: 1.0
ROM Kernel: Linux 3.18.140
ROM Firmware Required: Must be on latest Oreo Stock firmware
Based On: LineageOS 18.1
Version Information
Status: Stable
Current Stable Version: 1.0
SELinux Status: Enforced
Release Date: 15th August 2021
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
doug888 said:
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
Click to expand...
Click to collapse
I'm not sure, as this is a android version jump, but it's worth to try.
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
listm said:
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
Click to expand...
Click to collapse
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
nift4 said:
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
Click to expand...
Click to collapse
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
listm said:
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
Click to expand...
Click to collapse
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
TheFixItMan said:
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
Click to expand...
Click to collapse
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Unfortunately I don't use it else I would test it out and try get it to work
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
This is due to a slow driver, an issue that is known and present in all Android 11 builds for Moto G5, even official Lineage OS.
Idk if kernel 4.9 will get usuable any time soon, but that will hopefully resolve that issue.
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Hide props is not needed on this rom, for general information. I built it into the source.
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
Formatting system and data is an good idea actually. It prevents leftovers (on system, some things like Gapps packages store restore scripts). Formatting vendor is useless. No harm done, just time wasted.
Thanks for your replies and explanation!
It's amazing to see Android 11 on such an "old" device!
regards, Andy
@nift4 Are you still working on kernel 4.9?
xenondroid said:
@nift4 Are you still working on kernel 4.9?
Click to expand...
Click to collapse
Yes. Jarl & wiktorek140 made it work near to perfect on montana and I am trying my best to replicate that on cedric. Jarl said he will only bringup 4.9 ports to LineageOS 19...
Flashed this to replace Mint 2.1 no problems. Even the Seedvault backup worked. Battery seems to last longer too. One strange thing I'm experiencing since I flashed Stellar is that whenever I reboot my phone I get 5 text messages within a couple of minutes from O2 (my mobile network operator) saying my number doesn't support Visual Voicemail. I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Thanks
doug888 said:
I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Click to expand...
Click to collapse
Probably because it's enabled by default in Android 11. You can disable it in Dialer settings, I think.
Thanks! That worked
Hi,
Thank you for your work !
My questions may be slightly off-topic... and from a newbie but I am wondering why SafetyNet is OK on this ROM (checked with an application, without Magisk installed) BUT some applications still refuse to work or complain :
- WhatsApp just warns my device is not supported
- HID Approve (an MFA auth. app) refuses to run
- My banking app refuses to enable basic features at launch
What kind of checks have been implemented within these applications (are they well-known ?) and is there a way to workaround these issues ?
Otherwise, I could relock my bootloader and reinstall Oreo Stock but I tried many times a few months ago and never managed to do it without losing my IMEIs (I have not done EFS backups before installing MintOS...). Any suggestion to make this work without buying another phone ?
Thank you !