[ROM] [UNOFFICIAL] [13.0] LineageOS 20.0 [ALPHA] - Galaxy S6 / S6 Edge Unified Development

[ROM] [UNOFFICIAL] [13.0] LineageOS 20.0 [ALPHA] - Galaxy S6 / S6 Edge Unified Development

/*
* 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.
*
Click to expand...
Click to collapse
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. 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.
Based on the Exynos7420 source code.
I get asked for a Lineage 20.0 release every so often, so I figure I release something in a semi-working state for you all to play around with.
This ROM is in an ALPHA state, meaning that it is probably not ready to daily drive. Please keep this in mind before wiping your stable builds. Thanks
G920F only supported at this stage.
What's working:
Audio
Bluetooth
Telephony (Calls, SMS, Mobile Data)
WiFi/Hotspot
NFC
Camera
Fingerprint
HWC
GPS
What's not working:
VoLTE and other proprietary Samsung stuff
SELinux Permissive
OMX codecs in some scenarios might not work
You tell me
Download Link:
LineageOS Releases on my GitHub
Source Code:
https://github.com/samsungexynos7420/android_kernel_samsung_universal7420/tree/lineage-20.0
ROM OS Version: 13.0 T
ROM Kernel: Linux 3.10.108
Based On: LineageOS
Version Information:
Alpha/Testing
ROM creation date: 15/05/2023
Last release: 15/05/2023
If you would like to support me, visit my donation page.
Thanks to:
LineageOS-UL: Various lineage patches used
Ivan_Meler: Various lineage and device patches
Enesuzun2002: Original exynos7420 source code this project was based off, various device/slsi patches
html6405: Various patches

Common FAQI have echo in phone calls!
Echoing in calls has been a problem for Samsung devices for a long time. Not aware of a fix, but using some old mixer_paths tweaks, the problem can be mitigated somewhat
Why won't VoLTE work?
Because Samsung has a proprietary implementation of this which has yet to be integrated into Lineage.
Why won't my banking or other apps work?
We do not natively pass safetynet currently, however with magisk modules you can pass it relatively easily, and this should be enough to get most apps working.
I have a problem not on this list!
Post a bug report, preferably on GitHub. Provide relevant details to the issue, such as what the issue is, how you produced it, your model, OS version and logcats.

This is going to be one hell of a journey

fakemanoan said:
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. 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.
Based on the Exynos7420 source code.
I get asked for a Lineage 20.0 release every so often, so I figure I release something in a semi-working state for you all to play around with.
This ROM is in an ALPHA state, meaning that it is probably not ready to daily drive. Please keep this in mind before wiping your stable builds. Thanks
G920F only supported at this stage.
What's working:
Audio
Bluetooth
Telephony (Calls, SMS, Mobile Data)
WiFi/Hotspot
NFC
Camera
Fingerprint
HWC
GPS
What's not working:
VoLTE and other proprietary Samsung stuff
SELinux Permissive
OMX codecs in some scenarios might not work
You tell me
Download Link:
LineageOS Releases on my GitHub
Source Code:
https://github.com/samsungexynos7420/android_kernel_samsung_universal7420/tree/lineage-20.0
ROM OS Version: 13.0 T
ROM Kernel: Linux 3.10.108
Based On: LineageOS
Version Information:
Alpha/Testing
ROM creation date: 15/05/2023
Last release: 15/05/2023
If you would like to support me, visit my donation page.
Thanks to:
LineageOS-UL: Various lineage patches used
Ivan_Meler: Various lineage and device patches
Enesuzun2002: Original exynos7420 source code this project was based off, various device/slsi patches
html6405: Various patches
fakemanoan said:
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. 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.
Based on the Exynos7420 source code.
I get asked for a Lineage 20.0 release every so often, so I figure I release something in a semi-working state for you all to play around with.
This ROM is in an ALPHA state, meaning that it is probably not ready to daily drive. Please keep this in mind before wiping your stable builds. Thanks
G920F only supported at this stage.
What's working:
Audio
Bluetooth
Telephony (Calls, SMS, Mobile Data)
WiFi/Hotspot
NFC
Camera
Fingerprint
HWC
GPS
What's not working:
VoLTE and other proprietary Samsung stuff
SELinux Permissive
OMX codecs in some scenarios might not work
You tell me
Download Link:
LineageOS Releases on my GitHub
Source Code:
https://github.com/samsungexynos7420/android_kernel_samsung_universal7420/tree/lineage-20.0
ROM OS Version: 13.0 T
ROM Kernel: Linux 3.10.108
Based On: LineageOS
Version Information:
Alpha/Testing
ROM creation date: 15/05/2023
Last release: 15/05/2023
If you would like to support me, visit my donation page.
Thanks to:
LineageOS-UL: Various lineage patches used
Ivan_Meler: Various lineage and device patches
Enesuzun2002: Original exynos7420 source code this project was based off, various device/slsi patches
html6405: Various patches
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Very exicted to try it out!!

Any plans to build one version for s6 edge?

Fingerprint sensor not scanning. It's detecting the finger when placed to record print but it's not scanning

**request**
Please add these item in your project if possible:
--change lineage launcher, like the Pixel phone rom's, which can set the color of the apps icons with the wallpaper.
--Stereo speaker ((DolbyAtmos)) like oneu ui and >>Fade led notification like floyd oneui rom
--Try to fix IR sensor, because I use it everyday.
Thanks for make lineage 20 for this old phone

i tested the rom for days now and heres my feedback:
1-same performance and bugs as the 19.1 rom ,but you arleady know that ,however i noticed something important ,a small detail but that can make a big difference for the ui performance. its the display HZ ,i tested almost every rom on the s6 and noticed that roms who has 60hz like the pixel experience plus android 10 is very fluid and fast, while others are set to 59hz make the ui laggy sometimes .and its logical even on pc if you have a 60 hz dont put it at 59hz you can get some fluidity issues.even the samsung rom for the s6 its at 59hz and thats make it laggy sometimes. so please in the next builds try to put it a 60hz it will really help the phone to get stable performances, and wil surely help you in your builds. now i not a phone expert but here what i think and noticed.
2-the sound keeps getting out of the speaker when the headphones are plugged in .
3-sometimes the fingerprint laggs or dont recognize.
In general i really love this rom ,its the best for the s6 at this time and i will keep this one,almost perfect ,so thank you fakemanoan and all who helped makin it possible and hope it will be perfect in the next builds . very nice work man!

Ramtin.j said:
**request**
Please add these item in your project if possible:
--change lineage launcher, like the Pixel phone rom's, which can set the color of the apps icons with the wallpaper.
--Stereo speaker ((DolbyAtmos)) like oneu ui and >>Fade led notification like floyd oneui rom
--Try to fix IR sensor, because I use it everyday.
Thanks for make lineage 20 for this old phone
Click to expand...
Click to collapse
if you want pixel launcher and all google goodies its simple ,just flash the NikGapps full edition ,it will replace all the lineage open source apps.

Testing for 3 days for now:
+ Bluetooth audio doesn't work on calls.
+ Notification bar animations are a bit laggy.
+ In some games like OSM animations are a bit laggy as well. Probably the same reason as the notification bar.
+ Instagram videos have bad quality. (This was fixed by enesuzun on LineageOs 18.1, maybe you can get help from him and his work.)
+ In-calls, sometimes I can't hear anything for a few seconds after that it's okay.
+ In-calls, sometimes the other person can't hear my voice and I have to reboot when that happens.
+ Even though it is 480p Netflix works surprisingly, good job.
+ Battery life is much better than the stock ROM, especially on standby.
+ Camera doesn't work only on Instagram. In other apps, it works perfectly fine.
+ In the camera app and other apps, it is difficult to focus on things and it doesn't recognize the objects automatically.
+ Notification light works weirdly.
+ Wifi performance can improve. It disconnects and reconnects sometimes.
+ Sometimes wifi and mobile data don't work at the same time. It says no internet on wifi and doesn't connect to mobile data. When I reboot it's fine.
+ Adding changing the screen resolution would be nice.
? Is there any way to change the screen resolution I couldn't find the way.
Overall a very well-built rom I can say. Just it can be a little smoother.
Thank you @fakemanoan for all your hard work. Patiently waiting for new updates.

<<zeroltexx ((s6 edge user))>>
alfha ver is here:
lineage-20.0-20230520-zeroltexx.zip
drive.google.com
ported by channel48 on yt

timmyd21 said:
Testing for 3 days for now:
+ Bluetooth audio doesn't work on calls.
+ Notification bar animations are a bit laggy.
+ In some games like OSM animations are a bit laggy as well. Probably the same reason as the notification bar.
+ Instagram videos have bad quality.
+ In-calls, sometimes I can't hear anything for a few seconds after that it's okay.
+ Even though it is 480p Netflix works surprisingly, good job.
+ Battery life is much better than the stock ROM, especially on standby.
+ Camera doesn't work only on Instagram. In other apps, it works perfectly fine.
+ Notification light works weirdly.
+ Wifi performance can improve. It disconnects and reconnects sometimes.
? Is there any way to change the screen resolution I couldn't find the way.
Overall a very well-built rom I can say. Just it can be a little smoother.
Thank you @fakemanoan for all your hard work. Patiently waiting for new updates.
Click to expand...
Click to collapse
I've been trying a couple hours and have the same issues as yours. Disabling the hw overlay in developer option seems reduced lagginess, idk. I also noticed that this build has "always on" fingerprint. Btw, you can use fde.ai apk to change your screen resolution

topolinoob said:
I've been trying a couple hours and have the same issues as yours. Disabling the hw overlay in developer option seems reduced lagginess, idk. I also noticed that this build has "always on" fingerprint. Btw, you can use fde.ai apk to change your screen resolution
Click to expand...
Click to collapse
Both of these advices helped me. Thank you a lot.

Ramtin.j said:
<<zeroltexx ((s6 edge user))>>
alfha ver is here:
lineage-20.0-20230520-zeroltexx.zip
drive.google.com
ported by channel48 on yt
Click to expand...
Click to collapse
heats a lot and horrendously lagging

Ramtin.j said:
<<zeroltexx ((s6 edge user))>>
alfha ver is here:
lineage-20.0-20230520-zeroltexx.zip
drive.google.com
ported by channel48 on yt
Click to expand...
Click to collapse
But without Fakemanown Zerofltexx it would not be possible so considder it His Rom aswel ..

Hi . can make this room for s6 edge plus zenlte ? Sorry
Thx

methythebozo said:
heats a lot and horrendously lagging
Click to expand...
Click to collapse
thats a lie , I tested device on heating up , rendered a 10 minuted video with Kinemaster on the S6 Edge running Los 20 Port , Before rendering 23 Degrees Celcius . after rendering 35 degrees Celcius and thats not Overheating but that is a normal Temp at hard work , so IDK what You are doing with your phone and what you all installed but over heating is a hoax. I suggest your hands temp are heating up the phone , use it in a cover and dont spread mis information scaring users with nonsense

Concept48 said:
thats a lie , I tested device on heating up , rendered a 10 minuted video with Kinemaster on the S6 Edge running Los 20 Port , Before rendering 23 Degrees Celcius . after rendering 35 degrees Celcius and thats not Overheating but that is a normal Temp at hard work , so IDK what You are doing with your phone and what you all installed but over heating is a hoax. I suggest your hands temp are heating up the phone , use it in a cover and dont spread mis information scaring users with nonsense
Click to expand...
Click to collapse
dude chill out I just said what happened on my device

C'mon what do you guys expect from a phone from 2015. Heating issue is obvious. And it has always been an issue even in the stock rom, "thanks" to its thin and glassy build. Also they already stated that THIS ROM IS IN ALPHA STATE, so of course lagging/heating will occur occasionally. Go find another rom that reaches stable.

Related

[Q] CM7 settings question

I have been looking for a good CM 7.1 based ROM and am having a hard time deciding on one. The main thing I am looking for is the advanced lock screen delay and timeout settings. I cannot tell if this is a difference between CM 7.1 and 7.0.3 or if it is just a setting that some ROMs have and some do not.
Can someone shed some light on this for me? Is there a way to add this functionality? (I care because work enforced a security lock on my phone for email access, but I don't want to have to type i tin EVERY time the screen goes off. iPhones and WinMobile don't. It seems to be a flaw in Android's ActiveSync).
Thanks in advance.

This feature is new in CM 7.1. However, other users have reported success using Delayed Lock + WidgetLocker apps from the market to effect the same functionality, though I am uncertain how well they play with the Exchange server's demands.
Alternately, if you really don't want this security lock feature at all then you can find versions of Email.apk that will just lie to the Exchange server about the phone's configuration. Then you can configure your lock settings however you like. Ah, the classic fallacy of a security model that trusts the client...

I actually like the security of the password. I just wish it behaved like ActiveSyns on every other type of device (Win Mobile, iphone, etc) and let you set a delay (defined by the system administrator) for when the device security locks, not every time the screen goes off.
I wish we had a good CM7.1 ROM. Oh Z, wherefore art thou?

Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).

organophosphate said:
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
Click to expand...
Click to collapse
Care to share?

rearview said:
Care to share?
Click to expand...
Click to collapse
You know, I realized after posting that I probably look like a jerk for not offering. I apologize. There are issues that seem to preclude this, however.
The target of the relatively minor code changes necessarily included one of the fundamental framework jars.
When I was developing the feature, I only compiled CM for the Droid Incredible. Didn't make sense to compile for platforms I can't use/test, especially given the next point.
It takes my machine 90+ minutes to compile a ROM for a platform.
I believe that if I gave you a flashable update.zip to replace the affected jars it would have a high probability of cacking your ROM and would result in bootloops. Not absolutely certain, but fairly concerned about the possibility. I believe you would have better luck running a nightly that people report as "relatively stable" in the forums (some nightlies are better than others).
When the feature was merged, I really thought CM 7.1 would be out soon. RC1 dropped a month *before* the new feature was merged. That sounds odd in retrospect, because most projects freeze feature additions before entering the RC phase of a release (ie. they accept bugfixes only).

I just assumed it was for an X10 since we were in the X10 forums. Since this phone isn't officially CM supported I'm at the mercy of ROM developers to make a nice CM7.1. There are a couple out there, and they all have issues. One is close, but the dev seems to have gone missing. I hope he returns soon.

Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.

rearview said:
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
Click to expand...
Click to collapse
I like your train of thought. Unfortunately, even if that were to work you would be unable to configure the feature, because the UI is in the CM Settings apk (ie. the apk that makes "CyanogenMod Settings" menu option appear in your Android settings). If you were to also grab the CM 7.1 settings APK and install it, then that would replace the old version. The CM 7.1 version has all sorts of changes, controls for other new features, and so forth; therefore, that would break much of your other functionality.
How conversant are you in software development? You may be able to join one of those CM 7-derived ROM projects for your platform. It should be relatively easy for someone with a CM dev environment configured for your platform to grab these patches via git cherry-pick and build a 7.0.3 "Gold Edition" with this feature added. Because it should be easy, you might be able to persuade one of those custom ROM developers to grab this feature and include it.
If you are interested, here are the links to my patchsets that were merged to implement the feature:
Framework Implementation
CM Settings UI
I believe the patches will merge "nearly cleanly" into a CM 7.0.3 derived branch. That is to say, if there are merge conflicts they will not be substantive and will merely involve wholesale cut/paste reordering of methods within the given class files rather than requiring a rewrite of any part of the actual implementation.
I know that this simple reordering is all I changed between my 7.0.3 development version and the 7.1-derived submission. Seems Steve Kondik did a little further rearrangement to accommodate other patches that had been accepted/merged while mine was pending. Same deal there: still should be relatively simple.

I'm not much of a developer, though I'm an IT guy with some unix background. I'll look at it.

CM 10.1 mr1-staging

Is this source meant to be compiled for devices other than non AOSP because I got device files and everything and so far its going well.
Droid RAZR XT912
Sent from my XT912 using xda app-developers app

Nvm. I need some file called init
Sent from my XT912 using xda app-developers app

From 11/19:
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
and 11/21:
Cry havoc and let slip the...
...developers of CM. Hmm, not quite the same oomph to it. Back on topic...
mr1-staging as it's manifested in github right now, is good to build. Theme Engine support is not yet enabled, so if you attempt to build, remove vendor/tmobile. Everything else is in working shape with regards to AOSP devices, so if any of you are waiting for a working tree to move on to har
dware support, you can start now.
A bunch of our repositories have already been merged into mr1. The usual CM externals are in place, the CM build scriptage is also in and working. Features are not incorporated wholesale, and will be applied as conflicts with 4.2 changes are resolved.
Those watching at home, you should be able to break out a Mako (unofficial) build at this time. Our frequent contributors have been given the green light to send patches for review as features are rebased, recoded, and uploaded.
*Nightlies will not be available immediately, as even though CM may be build-able we consider it incomplete at its current stage. When we are happy with the product, the flood gates will open.*
Happy Dev'ing and say thanks to your patient lady/man for putting up with you
Click to expand...
Click to collapse

Why don't custom roms include AppLock?

Many people use AppLocks to secure certain apps that they wouldn't want others to have access to when they pass over a phone to family or friends. MIUI's inclusion of Applock into it's ROM goes on to prove my point.
Why don't the custom roms then have AppLock implementation directly to the ROM in general? Never seen a custom rom include this feature, although several of them providing a ton of features.
The Applock's implementation directly into the ROM provides better security too (Being part of the system apps) and is a more seamless interface.
I'd be glad if anyone can answer my query.
Also if it's possible do tell me if I can implement Applock into my ROM directly through someway maybe a zip to flash?

thedarkraven said:
Many people use AppLocks to secure certain apps that they wouldn't want others to have access to when they pass over a phone to family or friends. MIUI's inclusion of Applock into it's ROM goes on to prove my point.
Why don't the custom roms then have AppLock implementation directly to the ROM in general? Never seen a custom rom include this feature, although several of them providing a ton of features.
The Applock's implementation directly into the ROM provides better security too (Being part of the system apps) and is a more seamless interface.
I'd be glad if anyone can answer my query.
Also if it's possible do tell me if I can implement Applock into my ROM directly through someway maybe a zip to flash?
Click to expand...
Click to collapse
LineageOS 14.1 has this feature

Noter2017 said:
LineageOS 14.1 has this feature
Click to expand...
Click to collapse
Yeah but then LineageOS 15 again removed it. Why was that? Does that cause problems or affects performance?

thedarkraven said:
Yeah but then LineageOS 15 again removed it. Why was that? Does that cause problems or affects performance?
Click to expand...
Click to collapse
Changing from 14.1 to 15.0 they removed many features and are bringing them back one by one. They currently focus on stability.
Even a simple feature like center clock was added 3 only weeks ago. So it can take a while till App Lock is back

You care about your privacy? --> /e/ foundation could be our solution

/e/ is a Google-free LineageOS fork for several devices that is fully open source and keeping your data save while still providing services like app store etc. and it was recently covered in the XDA news and as our device is now officially supported by LOS 15.1 chances are really good to get it maintained officially from /e/ foundation...
all that is needed is that we vote for it in the /e/ foundation community vote for next device support... if we only get about 25+ votes more it will easily become number one :good:

Put my vote in for Nougat and posted in comments a request to add us to Oreo list

ELI5: What is the difference between microG and this e?

miniwire said:
ELI5: What is the difference between microG and this e?
Click to expand...
Click to collapse
MicroG is not a full ROM, it's a replacement for Gapps that allows you to use Google-like services, without any Google apps(like a Maps clone). This e/ is a full ROM, like LineageOS(based on LOS actually), that also bundles their own Gapps replacements(their own Email, Drive, even an Assistant). So think of it like LOS + MicroG, except it's made together by the same developers and so more integrated(LOS preserves support for Gapps, e/ will not work with any Gapps). Plus, e/ is focused on privacy, so all of its Android code has been modified to remove any kind of Google branding or prioritisation(I'm quite sure the Android system actually gives things like Google Play Services extra powers/permissions, e/ won't). LOS though is focused on providing (some useful) customizations, while working with most packages out there(Gapps, MicroG, or neither). So LOS still preserves those Google-first code built into Android that e/ removes
EDIT: Oops clarification I read up a bit more on /e/, they actually bundle microG lol so it actually is a LOS + MicroG setup(for now), but they are looking to add more of their own services(currently just their own Email) so that might change in the future Still it is true that it's more integrated than a simple LOS + microG will ever be because that's their focus, unlike LOS and MicroG

haoyangw said:
MicroG is not a full ROM, it's a replacement for Gapps that allows you to use Google-like services, without any Google apps(like a Maps clone). This e/ is a full ROM, like LineageOS(based on LOS actually), that also bundles their own Gapps replacements(their own Email, Drive, even an Assistant). So think of it like LOS + MicroG, except it's made together by the same developers and so likely more integrated(LOS preserves support for Gapps, e/ will not work with any Gapps). Plus, e/ is focused on privacy, so all of its Android code has been modified to remove any kind of Google branding or prioritisation(I'm quite sure the Android system actually gives things like Google Play Services extra powers/permissions, e/ won't). LOS though is focused on providing (some useful) customizations, while working with most packages out there(Gapps, MicroG, or neither). So LOS still preserves those Google-first code built into Android that e/ removes
Click to expand...
Click to collapse
Thank you very much, e/ sounds like a real solution for enhancing privacy on android!

Thanks folks, nice improvement -> from 8th rank to forth rank in two days... Only some more votes and we achieve first rank!

Voted!
I registered and voted! Thank You!

Registered and voted. Thanks.

Voted yeeehaaa

Nice one guys, Axon 7 is ranked first one now :victory:
Please continue to vote if you haven't already and ask for Oreo support in the comments, too :good:

I really wish I could have something like this, and still have Google Play, but maybe have it running in a VM? Running sandboxed? I'd like to still access all the apps I've bought on my Google account without giving Google everything on my phone.

My number is through hangouts, so unless I have an alternative to google voice/hangouts, I can't use this

You did it! Nougat is now officially supported... rests Oreo 15.1 version
"Dear all,
following the recent poll at https://community.e.foundation 1, we have added 4 new devices to regular /e/ builds:
Xiaomi Mi 5 (gemini)
ZTE Axon7 (axon7)
Samsung Galaxy S7 edge (hero2lte)
Google Nexus 6 (shamu)"
--> source

You did it! Nougat is now officially /e/ supported... rests Oreo 15.1 version
"Dear all,
following the recent poll at https://community.e.foundation 1, we have added 4 new devices to regular /e/ builds:
Xiaomi Mi 5 (gemini)
ZTE Axon7 (axon7)
Samsung Galaxy S7 edge (hero2lte)
Google Nexus 6 (shamu)"
--> source

[ROM][ANDROID 12.1][UNOFFICIAL] CalyxOS [beryllium]

CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.
Learn more out CalyxOS.
Working:
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
WiFi
Bluetooth
Camera (and flashlight)
Audio (Record and Playback)
Video Playback
Sensors
GPS
DM-Verity Enabled
Encryption
Bugs:
You tell me
Installation:
Wipe /system, /vendor, /cache
Format data
Flash calyxos zip
Notes:
Do NOT flash gapps
It is a user build
Not encrypted by default
I do not work for the calyx institute
Poco F1 does not maintain the android security model as much as the officially supported devices. It does not have complete android verified boot, but dm-verity is enabled
Download:
Get CalyxOS for Poco F1
Kernel Source:
Kernel source
If you like my work, please consider buying me a coffee.
Telegram support

Reserved 1

Reserved 2

Godlike rom! So far only notification delays. I don't know if this is a calyx issue in general or this rom in particular

CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)

Dev_Mashru said:
CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)
Click to expand...
Click to collapse
Took a while but thanks for keeping it up with this ROM.

Dev_Mashru said:
CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)
Click to expand...
Click to collapse
Hi, the Link is not correct.
This is the correct Link: calyxos_beryllium-3.6.0.zip

a170xda said:
Hi, the Link is not correct.
This is the correct Link: calyxos_beryllium-3.6.0.zip
Click to expand...
Click to collapse
Thanks for bringing it to my notice. Updated.

Hi, I wonder why you care about privacy and at the same time recommend Signal/whatsapp/duckduckgo.
Although the rom seems promising.

Glad to see Calyx for our Poco!!! Thanks for your work!
So far I only noticed that the "Display cutout" settings does not work properly (to hide the notch). Otherwise it runs really great!

Dev_Mashru said:
Thanks for bringing it to my notice. Updated.
Click to expand...
Click to collapse
You should also updates the Notes in OP: Not encrypted by default to Encrypted by default, since in ur recent changelog you wrote that you fixed it.

Retrial said:
You should also updates the Notes in OP: Not encrypted by default to Encrypted by default, since in ur recent changelog you wrote that you fixed it.
Click to expand...
Click to collapse
It is still not encrypted by default unlike in A11. Earlier it wouldn't boot if you were encrypted, now you can manually encrypt and it will boot.

Dev_Mashru said:
It is still not encrypted by default unlike in A11. Earlier it wouldn't boot if you were encrypted, now you can manually encrypt and it will boot.
Click to expand...
Click to collapse
Hmm I see. It would be nice if you could work to make it encrypted by default especially in this ROM. However I understand it may need some of your time.
BTW, I checked fast some screenshots, I saw some dots, seems there is a padding issue in status bar. (not sure tho since I checked from screenshots, I haven't tried the ROM yet). If you want take a look at crDroid values here, it may help with padding.

Does this build also receive OTA updates? Wishful thinking I'm sure, but i'm very interested. Do you have any plans to bring your project up to the newest iteration of CalyxOS? I think it's on 4.6.0 now. Any clarity you can offer on how your build copes with updates and what other manufacturer specific updates you've had to keep an eye on would be good to know as well please.
I think your build might have a specific application at the intersection of privacy fanaticism and audiophile listening with external DAC/AMP. The user can luxuriate in the use of interchangeable micro SD storage slots and the infinitely expandable, offline library it affords them. This means they can do away with depending on an internet connection and subscriptions to lossless music services like Qobuz, Tidal, Deezer, etc.
Alternatives in the android-based DAP market often have limited, non-expandable storage, and rely on versions of android which are outdated but no less privacy invasive. Whereas using a Poco F1 with custom ROM opens things up entirely. It also allows users to incrementally upgrade their DAC whilst always relying on this phone as their DAP playing hi-res files over USB. No need to upgrade DAP.
I'm really keen to learn how you built this. I think this phone is an ideal candidate for DIY, cost-effective, privacy respecting lossless listening.

airgappedromproject said:
Does this build also receive OTA updates? Wishful thinking I'm sure, but i'm very interested. Do you have any plans to bring your project up to the newest iteration of CalyxOS? I think it's on 4.6.0 now. Any clarity you can offer on how your build copes with updates and what other manufacturer specific updates you've had to keep an eye on would be good to know as well please.
I think your build might have a specific application at the intersection of privacy fanaticism and audiophile listening with external DAC/AMP. The user can luxuriate in the use of interchangeable micro SD storage slots and the infinitely expandable, offline library it affords them. This means they can do away with depending on an internet connection and subscriptions to lossless music services like Qobuz, Tidal, Deezer, etc.
Alternatives in the android-based DAP market often have limited, non-expandable storage, and rely on versions of android which are outdated but no less privacy invasive. Whereas using a Poco F1 with custom ROM opens things up entirely. It also allows users to incrementally upgrade their DAC whilst always relying on this phone as their DAP playing hi-res files over USB. No need to upgrade DAP.
I'm really keen to learn how you built this. I think this phone is an ideal candidate for DIY, cost-effective, privacy respecting lossless listening.
Click to expand...
Click to collapse
Here is the latest A13 version. (Also use that thread)

Better Mobile App

welcome