The PDF viewer (muPDF) seems to be missing in this build.
Nice build, thank you. Been working nicely. Hope there will be updates.
Another Pie unofficial build : https://www.androidfilehost.com/?w=files&flid=306078
Compiled Feb. 04, 2020.
Some apps (although requested at compilation time) are missing : OpenCamera, muPDF, and maybe some other I don’t use.
Anyway these apps are easy to find on F-Droid or Aurora
Nice one, thank you! Is it going to be updated monthly?
I can publish a build on a monthly basis, until a Pie official one is released.
BTW, I have a fresh build from today, which should include PdfViewer & Camera ([HOWTO] Build /e/ without docker)
I’ll upload it as soon as tested on my device
Working fine so far on my device, so here is the link : https://www.androidfilehost.com/?fid=4349826312261740355
New build (untested) : https://www.androidfilehost.com/?fid=4349826312261762787
New build : https://www.androidfilehost.com/?fid=4349826312261782022
I’ve just discovered this community.
I have a Santoni with LineageOS 16… is it safe to “upgrade” to last 0.8 build?
I have read something about I can break my phone if I do a bad upgrade
If you don’t want of 0.8 build (some user said it is buggy),
there is a recent Oreo Official Dev Build for the Xiaomi Redmi 4(x) (santoni)
Witch is builded with the /e/0.9 Builder version.
But better for you is the pie edition
It’s not about /e/ build level, but Android version
LineageOS 16 is Pie, /e/-maintained builds are Oreo.
I think it would be at risk to downgrade from Pie to Oreo …
That’s why I posted unofficial Pie builds.
As you already running LOS, your santoni is likely to be unlocked already.
I think you can follow the guide https://doc.e.foundation/devices/santoni/install from “Installing a custom recovery” if yours is LOS’s; if you already have TWRP installed you can proceed with a clean (wipe+format) install as you would for LOS.
My device was running the latest Miui (already unlocked) at buying time, I installed /e/ Pie without problem
New Pie build
Tested for 3 days, no problems encountered
So now, it is a 0.9 build of the unofficial pie /e/OS
New tested unofficial build : https://androidfilehost.com/?fid=4349826312261822452
With reworked sync manager, under Accounts.
NB : /e/ has bugs, but not specific to this device; if you find some you think happens only on this device, please tell me
New build here : https://androidfilehost.com/?fid=8889791610682885509
Installed successfully, testing in progress (working fine so far ).
Built with “community” /e/ Docker engine, using v0.9-pie tag (v1-pie branch).
<?xml version="1.0" encoding="UTF-8"?> <manifest> <project name="LineageOS/android_device_xiaomi_santoni" path="device/xiaomi/santoni" remote="github" /> <project name="LineageOS/android_kernel_xiaomi_msm8937" path="kernel/xiaomi/msm8937" remote="github" /> <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" /> </manifest>
<?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="muppets" fetch="https://gitlab.com" /> <project name="The-Muppets/proprietary_vendor_xiaomi" path="vendor/xiaomi" remote="muppets" /> </manifest>
docker pull registry.gitlab.e.foundation/e/os/docker-lineage-cicd:community docker run \ -v "/srv/src:/srv/src" \ -v "/srv/zips:/srv/zips" \ -v "/srv/logs:/srv/logs" \ -v "/srv/ccache:/srv/ccache" \ -v "/srv/local_manifests:/srv/local_manifests" \ -e "BRANCH_NAME=v0.9-pie" \ -e "DEVICE_LIST=santoni" \ -e "OTA_URL=" \ -e "REPO=https://gitlab.e.foundation/e/os/releases.git" \ registry.gitlab.e.foundation/e/os/docker-lineage-cicd:community
Please share your feedback !
Thanks ! Does it include all the packages /e/ should have without modifications ?
(Looks like there was some modifications in previous builds.)
It’s pure, unmodified /e/ build, unless specified
You can see in manifests I’m only using LOS repos, and Muppets Xiaomi vendor.
Consistency with /e/ is ensured by Docker engine.
This applies also for both previous builds.
In May 31th post, “reworked sync manager” was unclear : it was /e/ devs hard work I just wanted to point it out.
Hey pal, could you please update the microg version? I was seeing other builds, including officials with recent versions and 0.10 is using one from 2018, and it can’t be manually updated
I’ll take a look at that next week-end, but without any guarantee …
Unfortunately I have some bad news : I can’t copy android_prebuilts_prebuiltapks to my personal GitLab account, so I can’t build properly with an updated microG
However I succeeded with manually upgrading it using @marcdw’s excellent post found here : How to install unreleased version of MicroG GmsCore - #2 by marcdw
Download source (Services Core) : https://microg.org/download.html
Note #1 : I’m now using /e/ test build from here
Note #2 : 0.2.11 had some troubles (crash in Settings), I had to fall back to 0.2.10
Note #3 : only Services Core is relevant, other are too old at microg.org or missing in /e/
If you need some details for installation please post back, I’ll be happy to help