• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[DISCONTINUED] /e/ Pie for Payton

  • Thread starter Thread starter Deleted User
  • Start date Start date
D

Deleted User

Guest
/e/

As always, you take responsibility for what you do to your phone. Don't go filing civil lawsuits against me if your alarm fails to get you up for work in the morning.

The Hell's An /e/?
"/e/ is a non-profit project, in the public interest. We build open-source mobile operating systems that respect users’ data privacy. We’re an international core team of experienced entrepreneurs, developers and designers, and a growing community of contributors." --taken from their website.

Basically think Lineage AOSP but instead of just leaving gapps out of it, they're trying to take it a step further and really give Google the finger. Their ultimate goal for the future is to make a mobile OS featuring an entire ecosystem (/e/cosystem?) that respects users' privacy and avoids the "big-companies-that-sell-your-data". They will have alternatives to the most popular Google services baked in: F-Droid instead of Google Play, something like Telegram instead of Google Hangouts, Lawnchair instead of a proprietary Google launcher, etc. As of the time I'm writing this message this is still really early on in the /e/ project though, so don't expect too much just yet.

What Works?
Exactly the same as what's in Lineage 16 for Payton, WITH THE ADDITION OF VIPER AUDIO (YOU NEED TO USE V2.7.X FROM MAGISK THOUGH)

What Don't Work?
There's no market for apps built in yet (or web browser) so be prepared to sideload your own APKs over ADB to get that stuff on for now, until I fix it in a new build

Where's My Source Code, and How'd You Build this?
Don't worry, this took me forever to find too. I used the v1-pie branch which is Lineage 16.0 based

Here's the roomservice XML I used so you don't have to manually add all the trees yourself:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_payton" path="device/motorola/payton" remote="github" />
<project name="LineageOS/android_device_motorola_sdm660-common" path="device/motorola/sdm660-common" remote="github" />
<project name="LineageOS/android_kernel_motorola_msm8998" path="kernel/motorola/msm8998" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_system_qcom" path="system/qcom" remote="github" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" />
</manifest>


To get the custom /e/ apps in your build you have to edit the portion of vendor/lineage/config/common.mk that talks about "Custom CM Packages". Go to /prebuilts/prebuiltapks for a list of folders' names you can add to this list. Note that not everything will add properly, and adding some things may mess up your ROM, so experiment at your own risk

Where's My Download Link?
  • MY MEGA BUILD FOLDER
  • To run this ROM you need to have installed Pie stock firmware for the phone. If you were on Oreo stock and never upgraded before flashing this ROM things will probably break. Look for the latest firmware for you specific variant HERE.

Who Should You Give a Special Thanks To?
  • The /e/ team (including but not limited to Gael Duval)
  • All the guys here on the payton forums for their hard work in building the trees for this thing
  • @bcrichster for showing me how to get the /e/ apps to build with the ROM on this thing so I don't have to steal from AOSP anymore, also for letting me steal his manifest to build with
  • XDA user erfanoabdi for his excellent work maintaining Lineage 16 trees for Payton to get this thing stable
 
should probably give it a try.. MicroG it
Yeah what he said. MicroG can sometimes be a PITA to install depending on what "version" you use but it really does beat having to deal with apps complaining about no play services spamming your status bar
 
I hope everyone's happy with my current build here, because I'm trying to make a new one but I'm having lots of issues. The primary one has to do with the "cryptfs_hw: Support devices use metadata as key" change included with Lineage 16, because /e/ here doesn't know how to handle that flag. Even when I manually remove it there's still other kernel problems and missing dependencies I don't know how to solve. Sorry for the delay, because I really wanted to make timely updates for this thing since Payton's device trees and everything are undergoing a lot of cool changes recently and I'd like you all to have access to them
 
A build actually built. Sent to the x4 telegram group for testing to ensure it actually boots

To outline what I had to do here, I had to do a real redneck way of fixing this that I normally would not recommend doing as it's not best-practice for this kind of thing. I synced the kernel from @SyberHexen (pie-base branch) and tried to build with that. It got past the weird fde flag part, but then failed at some other point. I then went to the roomservice xml and changed the kernel BACK to the normal lineage one, force synced with repo, then restarted a build with brunch payton WITHOUT RUNNING A MAKE CLEAN FIRST. It was at this point it was actually able to build all the way through. Well, it built to about 98% and had some random error, but then restarting with another brunch payton fixed it somehow. Anyway, hopefully despite this thing's weirdness it works for you guys. I'm excited to have eelo start working for this phone again
 
New build is up, according to the group it works just fine. Someone also flashed gapps with it and it worked... Google-infested eelo is too dangerous of a contradiction and should not be tried at home
 
New build is up, according to the group it works just fine. Someone also flashed gapps with it and it worked... Google-infested eelo is too dangerous of a contradiction and should not be tried at home
Agreed, Playstore balks at gapps cuz it was designed to be Goober free, Lol
 
Sorry to do this so abruptly, but certain things were brought to my attention about this ROM and its organization. Granted, I knew this was pretty much nothing more than a reskinned Lineage, but apparently they've got some shady practices they participate in.

Because of this, I will be discontinuing all of my eelo builds, effective immediately. Read about it here: https://ewwlo.xyz/evil
 
Sorry to do this so abruptly, but certain things were brought to my attention about this ROM and its organization. Granted, I knew this was pretty much nothing more than a reskinned Lineage, but apparently they've got some shady practices they participate in.

Because of this, I will be discontinuing all of my eelo builds, effective immediately. Read about it here: https://ewwlo.xyz/evil
I could modify your eelo build to remove theose shady shit such as the dns bullcrap and other things but im kinda lazy at the moment lol
 
Back
Top Bottom