But @GaelDuval tested the same app on /e/ room and it wasn’t reporting so on his phone.
So, I think it is this ROM only.
Right now, I have Magisk hide to protect it. Am I doing something wrong? We can’t root the phone from Fastboot or adb, correct? it can only be done from within ROM by flashing things like Magisk from recovery like TWRP.
I just unlocked the bootlocker, installed recovery and flashed this ROM’s latest .zip.
I was in a bit of a pickle getting /e/ to work and you can read my adventure below.
Current version from 27.01.2020 on Pie 9.0.10 is running fine for now for me. I still have to use my SIM in it and do some app installing, but it looks good!
Hello, any camera app on this build ?
Also the mail app is very buggy and almost freeze the system blinking the screen. But the same happen on official nougat build.
Have some app icon disappearing and reappearing like odd way using the bliss launcher too.
No camera app on the version I downloaded, but there are good camera apps to be found on the app downloader or f-droid. I can’t say for the mail app as I am switching ro proton mail and will use their app.
Eh, i use Protonmail too and also Tutanota mail. Very cool apps for my use but i guess other people might want an email client usable. For camera apps “Simple camera” do the job but in a very minimalistic way for me and “Open camera” (built-in eelo from memory?) as cool features but not user friendly in my opinion.
For information, this rom is good, use it everyday. Last update 20200410 included the official camera (based on open camera) missing on first place. Question : Does the cast feature working for you or it isn’t implemented ? Last question, this rom is now release every month or this is the special circumstances?
Hi @thilo , how did you manage to make OTA updates available for your unofficial build please ?
I know you have to have a server and add a “OTA_URL” line in the docker command but what is the URL you put ? Just https://eota.digitalkr.am/builds/full/cheeseburger/ ? Or is there a more complicated procedure ?
Right. When building with the docker image having the tag “community” you need to add the environment variable OTA_URL when building without docker it’s some source patching to apply. (Refer to the build script of the community docker image for details)
It’s value is the base url where you host the ota server plus a trailing “/api”. In my case: OTA_URL=https://eota.digitalkr.am/api
The application on server side will, based on the device specific query for update, decide which files to offer for this device.