yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] ChrisRM:
Hi [MENTION=7929484]MSe1969[/MENTION],

Is this going to impact the Falcon (https://www.theregister.com/2020/11/06/android_encryption_certs/ )?

Chris M
[Moto G Android Development] MSe1969:
No, don't worry - since July 2018, the LineageOS 14.1 build tree tracks the CA certificates from Google's Android 8.1 tree:

https://github.com/LineageOS/android/commit/1784c3e4853a0e10345c99c18cdb0f128df2c28f

Btw, please fix the link in your post as shown below, it currently does not work (makes ")?" part of the URL):

your post: . . . https://www.theregister.com/2020/11/06/android_encryption_certs/)?[/url]
correction: . . . https://www.theregister.com/2020/11/06/android_encryption_certs/[/url])?
[Moto G Android Development] MSe1969:
New builds with November 2020 ASB fixes available

Hi all,

new builds are available for download and will soon be available via OTA updates:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...1-20201107-UNOFFICIAL-oms-falcon.zip/download

ASB Security string 2020-11-05

Fix of AOSP E-Mail widget

Fix for CVE-2020-15999

System Webview updated to 86.0.4240.185

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0201106-UNOFFICIAL-mG-oms-falcon.zip/download

ASB Security string 2020-11-05

Fix of AOSP E-Mail widget

Fix for CVE-2020-15999

Bromite Webview on 86.0.4240.181

Updated microG with fixes in GCM and EN API

Replaced weak F-Droid signatures with ROM's V2 signatures (see note below)

Please note:

The F-Droid and F-Droid privileged extension have been re-signed with this ROM's signing key. F-Droid keeps compatibility also to older Android versions, which however results in the necessity to use weak V1 signatures. In addition, they don't use V2/V3 signatures. To overcome this issue, the F-Droid apps have been built from source and V2-signed with the ROM's signing key.

You therefore need to de-install any updates, if you have made any - do do so, simply deactivate F-Droid and F-Droid privileged extension, delete app data and cache and activate them again. In case there were any updates, they will be de-installed and you will have as a result the delivered re-signed apps in their newest version.

EDIT: If you experience issues, connect the phone via adb and run the command adb shell pm clear org.fdroid.fdroid

Happy flashing!

Regards, M.
[Moto G Android Development] ChrisRM:
What effect does this release have on that bit of code you punted a short while ago?
[Moto G Android Development] Rosuz52:
My First Successful Install

Thank you for this, I'm new to flashing ROMs onto mobiles, after a week of trying with various ROMs this was my first successful load.

One very important think I learnt was that it's best to have a version of TWRP from the same era as the ROM, I kept getting error 7 messages with TWRP 3.4.0 but when I installed 3.0.1 everything came up fine. I've also now learnt all about Microg and Aurora which is an added bonus.

Is there an Android 8.0 version with these options , I'd be very interested to know because I need a phone that can run the NHS COVID-19 track and trace app in the UK
[Moto G Android Development] ranggakumal:
Android OS

Memory usage of Android OS take about 221mb , is this not too big for falcon?

System UI 68mb

Android System 59mb
[Moto G Android Development] MSe1969:
Regarding microG, the current release contains 2 or 3 further upstream commits, which deal with improved GCM processing in higher android versions.

So it shouldn't have an impact - if you compare it with the status of having flashed the posted zip over the October release.
[Moto G Android Development] MSe1969:
As far as I know, for the falcon, there is no regularly maintained build above Android 7.1 (like i.e. my build). There have been test builds here on XDA for Android 8 and 9, maybe even 10. But all of them have no enforcing SELinux, so using such a build as a daily driver is not at all recommended. (Permissive SELinux is an important step to bring up a device, but then the "slave work" to get a working policy in place to secure the device for daily usage is necessary)

In regards to the NHS Covid app:

The microG app provides the Exposure Notification API, which is used by many Covid apps - e.g. the German Corona Warn app works. Each app of course can have additional requirements and dependencies.

I think [MENTION=5188438]ChrisRM[/MENTION] has some experience with using my build with the UK NHS Covid app and can step in here.
[Moto G Android Development] MSe1969:
From where do you get those figures? Settings - Apps - <selected app> - memory usage?

In that case, these figures are really extremely high. On my devices, this more in the KB range...

Or did you get those figures elsewhere?
[Moto G Android Development] ChrisRM:
I did try the Serco Track&Trace thing and without success. It wouldn't open the camera for the 2D QR codes and, since I deliberately don't socialise, I can't say whether the app could tell whether it had contacted any others of its ilk. 'Checking-in' therefore was a bust.

I do have the thing running on my work phone, a Note8, and it's happier in that. Still have no idea whether the plague is near, but at least the check-in facility works if I was sociable enough...
[Moto G Android Development] ranggakumal:
from memory tab.

[IMG="mydevice"]https://lh3.googleusercontent.com/pw/ACtC-3dL7rrZjrRzAE4YdAY7PXgIa3_eE-nSHxeOGx3eUuge6jJlri4Izo_nmZWuT-kdvAv67M3XYluukbafGQ63rz1P8zFRmCpsVZqFuR8yC--q757fGPUwhOw7XV6VvkTybUc4rP5tRhhtOWvHhBcAnrjO=w493-h657-no?authuser=1[/IMG]

[IMG="mydevice2"]https://lh3.googleusercontent.com/pw/ACtC-3etVycjmh7dg7-d8QBMolc0CtQ9BTGr0zu1uz0k3XCStWskyX_FNy1Cj3bmuO6nbEJ-ds2M_MPr8k6bQFFfHD5HD1CarkbGuNIJ5DEjmcpMMTIBGlKEMVBCH_IglAwKDmr9JtGl-JjpP5LD45T1ADpc=w493-h657-no?authuser=1[/IMG]
[Moto G Android Development] MSe1969:
This is normal, don't worry - this is the (RAM) memory of the phone - it has ~1GB, of which "usable" ~ 890MB in total and shows, which apps are making use of it.

Android usually cleans the memory and kicks out inactive apps - nothing to worry about.
[Moto G Android Development] Scranalot:
Good Evening

Firstly thank you for the latest update MSe1969 :good:

Regarding your note above: because I had updated my F-Droid app I did the

to both F-Droid & F-Droid privileged extension by disabling them in

Settings > Apps

& then re-enabling them & as you state the upgraded F-Droid was downgraded to the original install (as per your ROM).

I did this before I upgraded to your latest Nov OTA release.

Now after I updated I had some app updates but they failed to install with this message:

My permissions for my F-Droid privileged extension:

-rw-r--r-- 1 root root 289 2008-12-31 23:00 privapp-permissions-org.fdroid.fdroid.privileged.xml

<?xml version="1.0" encoding="utf-8"?>
<permissions>
<privapp-permissions package="org.fdroid.fdroid.privileged">
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
</privapp-permissions>
</permissions>

F-Droid is Version 1.10-alpha1-1-gc8dcb6260

F-Droid privileged extension is Version 0.2.11-5-gdf95fd5

Any thoughts MSe1969??
[Moto G Android Development] MSe1969:
Please try to also delete the app- and cache- data of both FDroid apps. Afterwards, please reboot to recovery and wipe cache & dalvik. Let me know, whether it works.

EDIT:

For info, the message is misleading. It appears at any error raised by the privileged extension. The extension however compares the calling package's signature with an internal whitelist and raises an error, if the comparison fails. This leads to exactly the same message. The package signature is correct, if you have properly removed any upgrades, but maybe it is still cached somewhere.
[Moto G Android Development] Scranalot:
Thanks for the swift response MSe1969

I had already rebooted to recovery and wiped the cache & dalvik but just followed your instructions regarding app(s) data & cache plus for extra measure I wiped the cache & dalvik from recovery but no same issue I'm afraid.

---------- Post added at 10:19 PM ---------- Previous post was at 10:10 PM ----------

Just tried reinstall of the Nov OTA update.zip - still the same :confused:

---------- Post added at 10:31 PM ---------- Previous post was at 10:19 PM ----------

Can't uninstall apps either - same reason/ message - should of been more disciplined (ala our Germanic cousins) & taken a nandroid backup before updating - my last one is July :silly:
[Moto G Android Development] peelie:
hi

re f-droid should/can we update it after installing new rom (and following procedure for de-activating f-droid and clearing f-droid app cache mentioned in above posts)?

thanks
[Moto G Android Development] MSe1969:
OK, I was able to reproduce your issue. Actually, I did not have this specific situation on my falcon/peregrine, and flashing the ROM on an un-updated FDroid did work flawlessly.

In higher releases of android, one would run the command

adb shell pm uninstall-system-updates

But I was able to solve it on my test-falcon, so don't worry - this is what you do:

1. Deactivate both FDroid apps and delete their app data and cache

2. Connect the phone via adb (aka usb debugging) and run the following command:

adb shell pm clear org.fdroid.fdroid

3. re-activate the apps
[Moto G Android Development] MSe1969:
F-Droid and the privileged extension will carry a different, stronger package signature after updating the ROM.

This means, that in future, any update to those will be shipped via the ROM, as you cannot update those apps any longer through the F-Droid app.
[Moto G Android Development] Scranalot:
Thanks for the attention & swift response MSe1969 - I followed your instructions & unfortunately its still the same as before :(

---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------

Would a logcat or anything help?
[Moto G Android Development] MSe1969:
Hi, yes - a logcat is never wrong, although I am pretty sure I know, what it'll show.

Please try to clear also the privileged extension package:

adb shell pm clear org.fdroid.fdroid.privileged

In my test, which I did yesterday, I had only an "upgraded" FDroid client, but no upgraded privileged extension.

(Also: Connect the phone via adb, while still running Android, and not TWRP!) To be on the safe side, execute the pm clear command again for package org.fdroid.fdroid

If that does not help, please send me the logcat.

If clearing both packages via adb does not fix the issue, there is the "ultimate" option remaining:

Reboot to TWRP, mount /system and either use TWRP's built-in file manager or connect via adb in TWRP mode.

Check, that in /data/app, there is no directory for any FDroid app (if yes, remove those directories - they would be called here org.fdroid.fdroid and org.fdroid.fdroid.privileged)

Afterwards, purge the directories /system/app/FDroid and /system/priv-app/FDroidPrivilegedExtension, wipe cache & dalvik again and reboot into Android.

During this boot, all data, settings, signatures etc. belonging to the FDroid apps will automatically be removed and your OS does not have FDroid any longer.

Finally, flash my last build again in TWRP, which will bring the FDroid apps back in a clean state.
[Moto G Android Development] Scranalot:
Tried the first option of clearing the privileged extension package aswell but the issue persisted but your "ultimate" option seems to have worked a treat MSe1969 :D

Once again many thanks for your assistance - over & above what you already do in providing this ROM - much appreciated :good:
[Moto G Android Development] peelie:
doh!

hi what do you mean by "purge the directories /system/app/FDroid and /system/priv-app/FDroidPrivilegedExtension", do you mean delete?

if so i can only seem to see these directories when booted in android via adb but not when in TWRP via adb?

and i cannot delete the Fdroid.apk as it says it is a Read-only file system?

in anycase followed the rest of the instructions but no FDroid is installed?

after activating Fdroid still getting error message (Error installing *******

The privileged permissions have not

been granted to the extension!

Please create a bug report!)?

thanks for any help!

---------- Post added at 03:01 AM ---------- Previous post was at 02:45 AM ----------

hi

forget my previous post, have decided to full wipe and install latest rom!

thx
[Moto G Android Development] Scranalot:
Hello peelie

Being as I've recently done this I feel I'm qualified to give you an answer to some of your questions raised - not withstanding the fact that you have already resolved the situation by doing a full wipe & reinstall :eek:

Yes delete the FDroid & FDroidPrivilegedExtension directories/folders including their contents (1 .apk in each)

Via adb from your computer you have obviously enabled root access for adb both in 'Developer options' on the phone & on the PC/laptop i.e.

adb root

however it is necessary to remount adb for write privilages by the command

adb remount

Via TWRP its necessary to mount the system partition to be able to see the directories in question because of their location - that is done from the 'Home' screen > Mount check 'System' under 'Select Partitions to Mount' -

Note:

ensure 'Mount system as read-only isn't checked if you want write permissions

HTH ;)
[Moto G Android Development] peelie:
thanks Scranalot for this info on adb!
[Moto G Android Development] MSe1969:
Thanks, perfect and complete answer. (Wasn't at home during the day, wanted to answer the same now and saw, that you did it already) :good:
[Moto G Android Development] Tiki Thorsen:
[MENTION=7929484]MSe1969[/MENTION]

Thank you for your (continued) work on this. It makes a night and day difference in usability (and specially battery life) the Moto G, with the extra awesomeness that is the "B" hardened build.
[Moto G Android Development] Tiki Thorsen:
I just installed the variant B but I has the Google Play Services, not the traditional MicroG.

Maybe I am speaking out of ignorance, but when i installed MicroG on my G5 it was different.
[Moto G Android Development] MSe1969:
Variant B has the string -mG- in its zip file name. It comes with microG pre-installed, and definitely not with the "original" play services.

However, as it mocks them, the package name and its signature are the same, so that apps relying on them assume the "real" stuff (and e.g. Aurora store may even suggest to "update" them, which you should of course NOT do!).

I hope you 'clean-installed' the B variant and did not flash it over any existing different ROM?

What makes you convinced to have the "real" play services? Do you have a screen shot?
[Moto G Android Development] Tiki Thorsen:
Thanks for the clarification, I was due my ignorance as I never seen MicroG pre-installed so neatly before, so it confused me.

Yes, it was a clean install, I was using an old build of the A variant and formated before installed this:

https://sourceforge.net/projects/li...ge-14.1-20201106-UNOFFICIAL-mG-oms-falcon.zip

Sadly, I did update the services with Aurora Store. Can I roll them back or the damage is done at this point?
[Moto G Android Development] MSe1969:
Did it even update? Does it show "play services" or "microG Services Core" in the app overview in Settings?

To be safe, please do the following:

Deactivate the "Play Services" / "microG Services Core" and reboot to TWRP and wipe cache & dalvik, reboot back to the OS and reactivate microG Services Core.

If the system behaves weird, you have to do a factory reset in TWRP...
[Moto G Android Development] Tiki Thorsen:
That is the strange part, not only it did update successfully them but I can not find any trace of MicroG anywhere.

(Sorry that the language is on Spanish, is my Mum's phone)

Did I the correct ROM/installer? I have no problem reinstalling, just want to make sure I did not made a mistake if I need to re do it.
[Moto G Android Development] MSe1969:
As said, please deactivate the "play services" - you should get a message telling something about restoring the factory version. Afterwards, please reactivate and check, what is the app info & tell me. It should show microG.
[Moto G Android Development] Tiki Thorsen:
It does not allow me deactivate the Play Services. I will try the cache & dalvik wipe.
[Moto G Android Development] MSe1969:
I am afraid then you need to do a clean setup. Reboot to TWRP, wipe /system, /data, /cache and dalvik - manually flash the microG ROM again.
[Moto G Android Development] Tiki Thorsen:
Update: I did the wipe and nothing changed, every remains the same.

---------- Post added at 12:30 AM ---------- Previous post was at 12:29 AM ----------

This is because I updated via Aurora Store?
[Moto G Android Development] MSe1969:
I need to do some "crash testing" with my device to get down to the issue.

If you are reluctant to wiping, I have some other ideas, too. But you told me, it isn't an issue and that the device is your mom's - so before messing around the next days, do it once the hard way.
[Moto G Android Development] Tiki Thorsen:
I will format and reinstall from scratch tomorrow (I have TWRP 3.2.1) and double check. Since I am curious that I cannot find any trace of MicroG. (even on F-Droid does not show as installed).
[Moto G Android Development] MSe1969:
I have tried to "update" microG on my device via Aurora, and as expected, the update was refused ("conflicting package"), everything else would have been a surprise for me.

So I am wondering, what you did, as you have mentioned, there was an old variant A before, and I guess, that the following has happened in your case:

The old ROM had Gapps installed and you did not wipe the system partition, but you've only done a factory reset.

Hence, your system partition still had the "Gapps survival script" active, which had restored the Gapps after flashing variant B and thus overwritten microG.

That is why you were wondering, why all looked like Gapps and why you could update via Aurora.
[Moto G Android Development] Tiki Thorsen:
Correct, the old ROM had the OpenGapps installed, but what is strange is that I formatted with TWRP but I did not wiped anything. I will re-do it now.

Thank you for your assistance. I will report back once is done.

Edit: After formatting and manually wiping everything, MicroG is installed correctly. You were right about the "Gapps survival script".
[Moto G Android Development] Tiki Thorsen:
All apps keep asking me permission to access to the motion sensors, can I disable that?
[Moto G Android Development] MSe1969:
You don't need to format the data partition, wipe is enough, the key here was to also wipe the system partition
[Moto G Android Development] MSe1969:
You can configure the privacy guard accordingly. Don't know which apps are asking, some system apps indeed would need one to allow it for them, no issue.

User apps (those you install e.g. from Aurora or F-Droid) should not need that access (yes, everybody wants to collect all kinds of data, but seriously - no!) - unless you e.g. use a step-counter app etc. or other apps really needing to access motion sensors and it is obvious that the app's main purpose is to access them.

For the device orientation however, this information comes from the system, no app needs to access the sensors itself to know how you hold your device, for example.

Rule of thumb: User app wants motion sensor access => nosy, no need to. Exception may be fitness trackers or step counters.
[Moto G Android Development] Tiki Thorsen:
Thank you for the explanation, everything is working great now. I am surprised how neatly integrated MicroG is, amazing work on that.

I have a small suggestion; consider including Adclear (it is OSS) on the variant B for future updates.
[Moto G Android Development] MSe1969:
Pleased to read you like it :)

I only ship additional apps with my build, if the fact, that they come as system apps, makes a functional difference - like e.g. F-Droid / Aurora allowing to install apps w/o enabling "unknown sources" or microG being neatly integrated, or e.g. the Netmonitor app being part of a different SELinux domain to be able to access /proc/net. For all other cases, every user has the freedom to install additional apps at his/her own personal preferences. So shipping such apps as part of the ROM does not provide any benefit.

P.S.:

Btw, I did not find at first sight any reference to AdClear's source code, so don't see it being OSS. I also don't like its dependency on Google play services (yes, I ship microG to support apps with G'Play dependencies, but I value apps more without). Having said so, that does not mean any judgement about the app - might still be a terrific app, I don't know (the company behind at least makes an effort in maintaining their XDA thread and openly communicating with their audience).

Similar apps making use of VPN to block ads etc., which indeed

are

FOSS, include: NetGuard, Blokada, dns66, . . .
[Moto G Android Development] MSe1969:
ok, glad to read (sometimes "fun" with AFH, best solution is to keep trying...)
[Moto G Android Development] skizz98:
Couple of questions

Will you build also the other branches of this modified LOS?

I was interested in the cm-14.1-mG-oms branch of yours but I'm not ready yet to build it myself.

I've tried already but had some troubles with shared libraries (that I fixed, Ubuntu 18.10 related) and some other problems I have yet to resolve.

I'm still a noob on the "build it yourself" side of things and having many different ways to build every ROM out there is not really dumb proof.

Have you any advice on documentation I should look up to learn more?

I have already read everything on your github and on the Lineage Wiki but still not enough to really understand the basics.

Final question: how much time would it take to setup an ota update server using the CMUpdater? (even just for myself)

Thanks in advance! ;) ;)
[Moto G Android Development] MSe1969:
Normally not for the falcon device; but I am doing this in my thread for the osprey device. However, you're lucky:

I have indeed made a "microG-oms" test build this time, so I've just uploaded it: https://www.androidfilehost.com/?fid=1395089523397936839

In general: If there

really

is interest (and I receive respective feedback from multiple persons here), I can offer that build more frequently. . .

On source.android.com you may also find further info, further, on XDA, there are also some comprehensive step-by-step guides.

Also, you may get help on freenode, as advised in the LineageOS wiki.

If you have a very specific issue, you may also ask here in this thread, but please don't expect too much support. . .

Eventually, it is in fact "learning by doing" / "learning the hard way" - the positive side of it is, once you have solved your issues, you have gained a lot of additional knowledge and experience.

Not worth the effort, if you ask me - but you're free to have a different opinion :)
[Moto G Android Development] skizz98:
Many thanks!

Thank you for the build! Really appreciated! Going to flash it asap.

Hopefully there'll be more people interested in the "microG-osm" build but, given how trivial is to install both microG and osm after flashing the standard build, I don't really think so.

Thanks. I'll take a look.

Not planning to ask for support in here: ROMs maintainers are already stressed enough with the free work they donate to the community. ;)

Absolutely true!.

Being involved in web development, setting up a basic server seems much easier than maintaining multiple ROMs on XDA hahahaha

I'll investigate a bit more and maybe setup something that can be scaled for some small distribution like yours. I'll keep you posted.
[Moto G Android Development] MSe1969:
Well, the 'cm-14.1-mG-oms' branch and the 'cm-14.1-microG' branch actually also contain some security-hardening features, for a detailed description, see e.g. my osprey thread and especially here - so it is definitely more than just pre-installed microG.

Sounds interesting :)
[Moto G Android Development] skizz98:
Oh. My bad!

Thought every branch was hardened. That change the value of the other branches for sure :good: :good: