yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] MSe1969:
microG: Exposure Notification API for "Corona apps"

Hi all,

below is applicable for the "microG" build variant (B):

microG has published an implementation of the "Exposure Notification API" in tag v0.2.12.203315.

So it should now be possible to run "Corona apps", which are designed to make use of Google's Exposure Notification API, with this build, too.

I have created a test build containing this version, which currently runs on my device - with the German "Corona app" active on it (and - most important - no Google Spy services involved). The test build can be downloaded and (dirty-)flashed manually here, for interested people:

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

This will become part of the next regular build onwards. Feedback welcome (I obviously can't help with any EN API issues, that would find its way into microG through the microG project, but a general feedback and also feedback concerning the overall microG functionality is welcome, there may be e.g. some useful patches in the e.OS fork, which haven't yet found their way into the mainline...)

Regards, M.
[Moto G 2015 Android Development] MSe1969:
Hi,

wanted to add some information, as I just had to solve exactly that problem with the device of my son, but with a "more advanced difficulty level", which made the proposed approach above not possible:

Developer options not available and root disabled! So no chance to get a root terminal within android.

Solution:

Reboot to TWRP and edit the file /data/system/users/0/settings_global.xml

Add the below line within the XML tags (i.e. last line before the </settings> tag:

<setting id="94" name="device_provisioned" value="1" package="org.lineageos.setupwizard" defaultValue="1" defaultSysSet="true" />

How to edit within TWRP?

Either, via adb shell and using the vi editor (TWRP does not have a more comfortable one).

Or, (this is what I did), while connected to the phone in TWRP recovery mode:

adb pull /data/system/users/0/settings_global.xml

Edit the file on your PC; if you use windows, make sure to use an editor which is capable of saving a text file in

Unix format

(e.g. notepad++)!

adb push settings_global.xml /data/system/users/0/settings_global.xml

Restart the phone
[Moto G 2015 Android Development] bravo97:
slow memory leak or paging out

I am running this rom and have the following experience to discuss:

When the phone is actively used with various apps it seems to function fine. The speed, app switching, page loading (firefox), audio playing etc.

However when the phone is left unused for many hours (esp overnight; on/charging/etc) the android system itself seems to expand in size (memory leak?) and page out memory for one or more running (user) apps.

When the phone is begun to be used again(in the morning), it will be VERY sluggish and slow on first use (even when doing the same things that were done just before the phone was set aside for the night). Opening a Firefox page before bed will take seconds as normal. Opening a page after the phone is picked up in the morning might take30-60seconds.

This sluggishness will continue for a few minutes as apps (seem) to page their memory back from SD, load caches back up, etc. After a few minutes have passed the phone will again seem to work at regular speed again and things will speed back up to normal.

(The sluggishness and how many minutes it takes to get back to 'normal' seem to depend on how long the phone was left unused.)

This phone has almost no applications installed on it; Most apps are disabled to run in the background. The internet/wifi/cell is not on overnight. Basically nothing is running in the background (APP wise; obviously the system is running; javascript is even turned off on Firefox).

My best guess is that while running unused the Android system (for this rom) has some sort of leak or some program that 'expands' mem usage slowly and squeezes out (pages) the user level apps. Whatever is expanding or paging out user memory does NOT seem critical or 'root' level or whatever term you want to use because, as I said, the phone does NOT run out of memory-once the apps are accessed and used again they PUSH BACK and re-exert themselves in memory (and surpress whatever was taking space).

It also doesn't seem like a 'normal' memory leak because such leaks don't tend to reverse themselves. A normal leak will expand until system crashs usually...(although a Java memory leak of abandoned mem/objects that collect and then get garbaged out could act like this I suppose.)

That's my best description of what is going on.

1) Is there I way I can tell what is happening between setting the phone down over night and picking it up in the morning? A way to determine what is slowly paging out cache/apps, etc?

2) does this problem/issue seem to exist with any other people?
[Moto G 2015 Android Development] MSe1969:
Thanks for your detailed description - that sounds weird. The osprey is not my daily driver and also not "heavily" loaded with apps - in fact it can lay around idle a long time and I haven't ever observed that behavior.

What build variant do you use?

Can you try to grab a log, when you pick the phone after being idle?
[Moto G 2015 Android Development] bravo97:
1) using "standard build A";

2) I'm also using the April 1 patch level and haven't loaded/used sept (although I have no reason to suspect the security fixes would change this problem; maybe I'm wrong; if there is a change since april 1 that would be 'major' to account for an issue like this then please mention it-i'm willing to update ROM, but it will take time);

3) this problem happens not just with Firefox - I just used that since it is a commonly known app that isn't designed to mis-behave or act weird; The same 'push the app/mem out overnight' and then it is slow to page back in in the morning will happen with Opera, Camera, Messaging, whatever.

4) I'm not as experienced with android logs, but I get your request. Let me dig up the info/instructions and get a copy. (My initial post was to see if there was quickly any obvious solution or explanation. Seems like there isn't so log is next step.)
[Moto G 2015 Android Development] MSe1969:
Well, the April build was still a test build, this thread has started with the May build. I am not sure any more about details, but there for sure have been some fixes in regards to device config (encryption, switching off some unneeded services, which have caused lags, if Bluetooth and WiFi were enabled simultaneously, ...) - So I would like to ask you to fist update to the newest build and then report back, if there are still issues.
[Moto G 2015 Android Development] MSe1969:
New builds with October ASB

Hi all,

new builds with October ASB patches are available for download and will soon be offered through the Updater as OTA:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0201013-UNOFFICIAL-signed-osprey.zip/download

ASB Security string 2020-10-05

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

ASB Security string 2020-10-05

Bromite Webview 86.0.4240.73

microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps

Additional hardening: bionic and constified JNI method tables

A remark to the upgraded microG:

- If you have location providers configured, you need to re-enable them after flashing the upgrade as a one-time activity.

- The exposure notification API allows you to run Covid tracing apps, which are designed for its use (most of those apps are)

- If you had already used my previous test build, there is no change in regards to the microG version

Happy flashing, regards - M.
[Moto G 2015 Android Development] alanthelinuxguy:
M - OTA build received, downloaded, installed, and working fine. Many thanks - Alan
[Moto G 2015 Android Development] MSe1969:
microG interim update

Hi all,

the below applies only to users of the build variant B:

An interim update of microG GmsCore is available for download here:

https://sourceforge.net/projects/li...llaneous/GmsCore_20201017-signed.apk/download

The apk has been built from the microG source and signed with the specific key of this ROM.

(This means, it

cannot

be used on any other ROM, except the signed LineageOS 16.0 ROMs for the various devices provided by

me

)

This update contains the following fixes:

GCM sign-in issues

Mapbox issues

Various improvements of the exposure notification API

There is currently no official new version of microG, but due to some issues, which I have experienced myself in regards to the Covid tracing app and GCM sign-in and which were fully solved after applying the update, I wanted to offer it for those of you, who are interested. To update, simply download the linked apk and install.

Important hints:

One of the possible issues with the EN API is an incredible growth of the database and thus, the space used by the microG app (the respective Covid tracing app may also start to behave weird due to that). If you get the system message, that memory is becoming short, you may not be able to directly update the apk. In that case, don't delete the app data of microG (the EN-DB will properly reorganize after the update), but reboot to TWRP, and either connect the phone with your PC to use adb or use the internal root shell of TWRP and enter the following commands (assuming, the downloaded apk file is located in the Download directory of your phones internal memory):

mount /system
cd /system/priv-app/GmsCore/
cp /sdcard/Download/GmsCore_20201017-signed.apk GmsCore.apk
chmod og-w GmsCore.apk

The UI has been re-shaped internally. If you start the microG UI and what you see looks "weird" (e.g. Exposure notifications API now shown, or device registration and GCM looking "disabled"), don't panic and DON'T change any settings. Instead, please go to Settings - apps, pick the microG GMS Core app and purge the app's cache (only the cache,

and not the app data

!) - Afterwards, all will be fine.

Regards, M.
[Moto G 2015 Android Development] bravo97:
MSe1969,

I posted a little while ago about how overnight (or charging long period) my rom/phone would seem to leak memory and page/'push out' regular user apps...which then would be slow to use again in the morning until they (seemingly) paged their memory back in.

You noted (which I was not aware of) that the April build i was using was test/beta - I thought it was more solid release. I have since upgraded to the Oct release and those issues went away. Just fyi. thanks for the rom.
[Moto G 2015 Android Development] MSe1969:
New builds with November ASB patches available

Hi all,

new builds are available for download and offered as OTA updates:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/li...0201114-UNOFFICIAL-signed-osprey.zip/download

ASB Security string 2020-11-05

Additional Fix for CVE-2020-15999

Fix of AOSP E-Mail widget

System Webview 86.0.4240.185

B. Security hardened microG build

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

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. I therefore recommend to connect the phone via adb and enter the command adb shell pm uninstall-system-updates for a clean up, in case you had before updated F-Droid. Otherwise, there will be issues using F-Droid.

ASB Security string 2020-11-05

Additional Fix for CVE-2020-15999

Fix of AOSP E-Mail widget

Bromite Webview 86.0.4240.181

Updated microG with fixes in GCM and EN API

Replaced weak F-Droid signatures with ROM's V2 signatures

Happy flashing!

Regards, M.
[Moto G 2015 Android Development] alanthelinuxguy:
M - New build downloaded, installed, and working fine. Many thanks - Alan
[Moto G 2015 Android Development] bravo97:
bug: privacy guard shows all apps using 'coarse location'

I believe I have found a bug in rom (or upstream to the project). I'm using the recent Nov 2020 rom that came out yesterday (My previous rom was from April so this bug may be present for a while and I also don't remember if I saw it in April release. Unknown how long present.)

REPRODUCTION: Go to settings->privacy guard

In privacy guard screen go to "Advanced" from top right 3 dot menu.

(Advanced screen shows you all the privacy category groupings and then apps within each of those groupings.)

The first grouping is "Location".

BUG: notice that ALL apps are listed in this category and shown as using/requesting 'coarse location'. (including 'built-in apps' if you check that box on top right to show them). This is plainly not true (if you look at your apps - I don't know exactly what you have installed. Just use your discretion and check a few and you will see.)

You can click on a number of obvious apps and verify that they don't use ANY location data (I have a simple calculator, a stock brokerage app, Google Authenticator, etc...none actually use location on the app detail screen but show that they use "coarse location" on the Advanced screen "Location" summary list).

For 'built-in apps' you test this with "FM Radio" which says it uses coarse location, but when you tap it, it uses NO permissions. You can look at "Phone Services" as another example, Android System, Bluetooth, etc, etc.

For some reason pretty much every app in the system is showing up using/requesting "Coarse Location" when most don't.
[Moto G 2015 Android Development] MSe1969:
Well, the answer is two-fold:

1. Your observation is correct - in fact, this is an upstream project bug (or "feature"), I could observe this even in a standard LineageOS 14.1 build.

I have a suspicion and even looked at the LineageOS code, but so far I did not get any clue yet, what is wrong: The AppOps are numerical and simply numbered from 0, 1, 2, ... till last. The Coarse location AppOp is the 1st one and has value 0. The value for "no Op" is -1. My suspicion is, that at one place, a zero with the meaning "nothing" is interpreted as Coarse location AppOp. Maybe I'll be motivated to find the issue ...

2. It is an intended feature, that you cannot change the AppOps of privileged apps (such as FM Radio) - so if you click on any privileged app in the extended view, no Ops are offered to (dis)allow.
[Moto G 2015 Android Development] bravo97:
"...Your observation is correct - in fact, this is an upstream project bug (or "feature"), I could observe this even in a standard LineageOS 14.1 build..."

If you know this is upstream at LineageOS would you want to submit the bug to them directly yourself? ( When I posted this bug to you I could not tell if it was only my rom/phone or was the entire project.)
[Moto G 2015 Android Development] maxwell80:
Hi!

Since the October build ( also with Nov.) I have issues with mapbox.

The app "wien mobil" doesn't show the map anymore.

When I check the logfile for mapbox it says:

[11-17 18:23:26.745 15293:15293 D/GmsMultiArchLoader]

Loading mapbox-gl from /data/user/0/at.wienerlinien.wienmobillab/cache/.gmscore/lib/armeabi-v7a/libmapbox-gl.so

[11-17 18:23:27.887 15293:15416 E/Mbgl]

{en.wienmobillab}[Setup]: loading style failed: A valid access token parameter is required when using a Mapbox service.

Please see https://www.mapbox.com/help/create-api-access-token/ to learn how to create one.

More information in this guide https://www.mapbox.com/help/first-steps-android-sdk/#access-tokens.Currently provided token is: invalid

Does mapbox work flawlessly on your device?

Thank you for your help,

and this great rom!

m.
[Moto G 2015 Android Development] Tiki Thorsen:
I am trying to download from several sourceforge links but they are either down or the failed after a few seconds.

Anyone else having this issue?
[Moto G 2015 Android Development] MSe1969:
I can try. I am however afraid it won't help much: LineageOS 18.0 is close to be officially released, which will make 16.0 "legacy" (I.e. no ROM shipping and only community supported). Privacy Guard was dropped with 17.1, so I am not too optimistic.
[Moto G 2015 Android Development] MSe1969:
Haven't tried downloading things recently, but facing issues to upload my stuff since couple of weeks, need often 3-4 attempts, before I finally succeed - weirdest is, that I get sometimes a failure message at 100%, but 5 minutes later the uploaded file is there!
[Moto G 2015 Android Development] MSe1969:
Not really using mapbox, simply compiling the existing microG sources "as is" (plus two patches) - haven't checked microG issues and recent commits, yet (short on time), did you already look there?
[Moto G 2015 Android Development] Tiki Thorsen:
That is strange, oh well I will try again tonight/tomorrow.

Right now I need to unbrick my XT1542 to enabled OEM unlock so I can install your ROM.
[Moto G 2015 Android Development] maxwell80:
Found something:

Problems with in maps is a known issue with the newest microg and a fix should be coming soon.

https://www.reddit.com/r/CalyxOS/comments/jtyphz/problems_with_microg_on_pixel_4a/
[Moto G 2015 Android Development] bravo97:
Ah, yes, i forgot that privacy guard was dropped.

Makes the issue irrelevant. Disregard

(the rom still works)
[Moto G 2015 Android Development] Tiki Thorsen:
Hello, thanks for for great ROM, just as good as your Lineage for the Moto G!

Is there an alternative to Google Contact with MicroG? or is a must to I do a manual import via a .vcf file?
[Moto G 2015 Android Development] MSe1969:
Hi, the answer is more complex and depends on your specific requirements.

First of all, microG does not interact with Google servers to synch. your contacts. But you don't need Google to store your contacts on a server - a couple of mail providers (e.g. posteo.de or mailbox.org) offer that option for an encrypted and protected contacts repository - you would need the app DAVx5 (FDroid) for that - this is my recommendation and what I do.

To simply get your contacts exported from your previous setup and migrated to a microG setup, the .vcf option is the easiest - afterwards, you could e.g. use the DAVx5 setup to synchronize your contacts with an e-mail provider.

Finally, on the site shadow53.com you will find instructions, how to take the Google contact synch. adapter from a Gapps zip file and flash it to a microG setup to continue using your Google account for that under microG - I personally wouldn't recommend this approach, but that is your decision.
[Moto G 2015 Android Development] MSe1969:
LineageOS 17.1 Test build for microG build variant

Hi all,

I have created a fist test build for LineageOS 17.1 variant B (microG variant) - for the "standard" variant, there is - as you all know - official LineageOS 17.1 support:

https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download

I am planning to switch to 17.1 in the near future (don't worry, for December, there will definitely still be LineageOS 16.0 builds) and to offer this in a new thread.

(For the people using the standard variant, I'll provide - once I decide to switch - a migration build to be able to switch over to official LineageOS).

I would like however, after some promising tests on my end, to gather feedback also from others before following that path.

How to install:

1. Make a backup in TWRP to be able to get back to lineage 16.0 after your test!

2. You can directly "dirty-flash" over my lineage-16.0 build (

variant B only

, of course!)

Features:

Pre-installed microG and F-Droid same as the LineageOS for microG project

Pre-installed AuroraStore

eSpeak TTS engine (FOSS TTS solution)

Bromite as default browser

Additional security hardening features listed below

Cloudflare as default fallback DNS (instead of Google)

Privacy-preferred default settings

Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)

Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)

Increased max. password length of 64

No submission of IMSI/phone number to Google/Sony when GPS is in use

Default hosts file with many blocked ad/tracking sites

Privacy-enhanced Bromite SystemWebView

Extra control of sensor access for additionally installed user apps (Special access under app permissions)

Firewall (control internet access per app - under Trust)

Constified JNI method tables

(Note: Access restrictions to /proc/net are now implemented by default in Android 10)

Lost features

LineageOS 17.1 (Android 10) does not offer any longer:

LockClock app to show calendar entries and Weather widget

Privacy Guard

Looking forward to your feedback.

Thanks & regards - M.
[Moto G 2015 Android Development] HTCDreamOn:
Does anybody have mirrors for the latest builds? I'm having no luck with sourceforge. Either painfully slow or I just get '503 Service Unavailable'. Thanks!

Don't worry, all good now!
[Moto G 2015 Android Development] KamiOh:
mirror?

sourceforge is so soooooooooooo slow speed download.
[Moto G 2015 Android Development] maxwell80:
Hi M;

feedback for 17.1

Device boots with wrong system time (build time, I guess) and is not able to correct, even if network time is chosen.

After time and date is set manually device reboots with corrected time - however, working network time would be fine.

Log added.

Problems with apps that use mapbox are the same as in your 16 build.

Otherwise I have seen no other flaws yet - great work!

Please allow me two suggestions/questions regarding the usability of your rom:

Would it be possible to split the Google/faceboock-blocker into two separate options?

While I would like to block Google, I have to allow Fb for receiving pics, vids and other files on Whatsapp.

I like your idea of providing an adblock with your rom - however - some websites do not work with adblock, and white-listing them is not really user-friendly in your solution.

What speaks against adding - for instance - adaway to your build?

Again, thank you for your great work!

Best regards,

M
[Moto G 2015 Android Development] MSe1969:
Thanks for your feedback! I need to have a deeper look into that. You mentioned an added log, but I don't see anything, yet . . . ?

This is something, only the microG folks can address, I only pick from their repo . . .

As mentioned already, many thanks for the feedback and your tests.

I am considering to maybe implement an exception for Whatsapp to still be able to connect to FB.

AdAway has been designed as a user-app, which requires root access (in the newest version it also offers a non-root VPN solution). As replacing or editing the /system/etc/hosts file requires to mount the system partition read-write, which only works with root access, this does not make sense, as LineageOS 17.1 does not come with a built-in root solution.

However - you have the following options:

You can use a switch in the developer options to stop the /system/etc/hosts file to be updated with ROM updates

You can e.g. install Magisk as root solution on top, and then you can install AdAway - Adaway and Magisk even work together to make the hosts file replacement a system-less functionality.

Regards, M.
[Moto G 2015 Android Development] maxwell80:
Thanks for the reply!

Log is added to my recent post now.
[Moto G 2015 Android Development] MSe1969:
New (16.0) builds available with December 2020 ASB

Hi all,

new builds are available for download and already offered as OTA updates:

A. Standard LineageOS 16.0

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20201218-UNOFFICIAL-signed-osprey.zip/download

Security String 2020-12-05

System Webview on 87.0.4280.101

B. Security hardened microG build

https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20201218-UNOFFICIAL-microG-signed-osprey.zip/download

Security String 2020-12-05

Bromite System Webview on 87.0.4280.106

F-Droid updated to 1.10-alpha1-114

microG updated from upstream to 0.2.14.204215-15 (picked until 720b089)

Happy flashing!

Regards, M.