[ROM][Unofficial][9.0.0][microG][signed]LineageOS 16.0 for Osprey

[MSe1969]

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.

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?

 

[Tiki Thorsen]

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!

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.

 

[maxwell80]

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?

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/

 

[bravo97]

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.

Ah, yes, i forgot that privacy guard was dropped.
Makes the issue irrelevant. Disregard
(the rom still works)

 

[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?

 

[MSe1969]

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?

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.

 

[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.

 

[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!

 

[KamiOh]

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.

mirror?
sourceforge is so soooooooooooo slow speed download.

 

[maxwell80]

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.

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

 

[MSe1969]

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.

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 . . . ?

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

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

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

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

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 am considering to maybe implement an exception for Whatsapp to still be able to connect to FB.

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?

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:

1. You can use a switch in the developer options to stop the /system/etc/hosts file to be updated with ROM updates
2. 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.

 

[maxwell80]

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:

1. You can use a switch in the developer options to stop the /system/etc/hosts file to be updated with ROM updates
2. 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.

Thanks for the reply!
Log is added to my recent post now.

 

[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.

 

[alanthelinuxguy]

New (16.0) builds available with December 2020 ASB

M

New build downloaded, installed, and working fine. Many thanks.

Couldn't download the 17.1 trial but I believe that this was only available to users of Variant B. I'm using Variant A, but I look forward to switching once you have a final product ready to go for "mere mortals"! {grin}

Alan

 

[MSe1969]

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.

Hi - in fact, this is something, what can be even observed in the "official" LineageOS 17.1 builds for the Osprey device. So this is not related to my build in particular. Anyhow, I'll try to have a deeper look - I have observed already, that the LineageOS 16.0 build (as mentioned, this is mainly chil360's work) uses the TimeService.apk (Qualcomm time service) from the Motorola blobs, whilst LineageOS 17.1 (both, chil360's unofficial builds as well as the LineageOS official build) uses 'Sony Timekeep' - don't know why, but I may want to try in my builds with the Qualcomm TimeService (although I suspect, that there must be a reason for this...)
Regards, M.

 

[MSe1969]

Switching from LineageOS 16.0, build variant A, to official LineageOS 17.1 builds for the Osprey device

Hi all,
here comes a tutorial how to switch from my current LineageOS 16.0 build variant A to official LineageOS 17.1 build without having to do a clean install (e.g. to keep your data):

1. Download my migration build from below URL and place it into the internal memory or SD card of your Osprey device:
   
   https://sourceforge.net/projects/lin17-microg/files/MIGRATION/lineage-17.1-20201218-MIGRATION-osprey.zip/download
2. Download the latest official build from LineageOS and also place it into the internal memory of SD card of your device:
   

   LineageOS Downloads

   download.lineageos.org
3. Download any further flashable ZIPs, you may need for your specific setup, such as Gapps (remember: arm and Android 10, flavor of your choice), Magisk, etc. and also place it to your phone
4. Reboot to recovery
5. Make a nandroid backup, to be able to restore the current LineageOS 16.0 Setup
6. Wipe the /system partition
7. Flash my migration build, afterwards - without rebooting - Gapps (if applicable) and afterwards (also only, if applicable) Magisk and any other additional stuff - but DON'T flash the official build yet!
8. Wipe cache & dalvik and reboot into LineageOS 17.1
9. You are now with my Migration build - remember, that this build is not secure - simply verify, that the system seems to work as expected and that you can re-setup, what might be missing. However, don't install new stuff and only have the migration build active for a short time.
10. Reboot to recovery and flash/install now the official LineageOS 17.1 build and reboot - DONE.

This does not have to happen immediately, but I wanted to provide this information - feedback welcome.

Regards, M.

 

[sponk0]

Switching from LineageOS 16.0, build variant A, to official LineageOS 17.1 builds for the Osprey device

Thank you very much for providing these instructions and the migration build. I followed the instructions 1 by 1, and everything went smoothly and looks fine so far.

• I started from the 16.0, Variant A build from Dec. 18
• Test device is a XT1541 (16GB/2GB)
• I installed opengapps from 2020-12-09, arm / android10 / "nano" version and official lineageos-nightly from 2020-12-18
• The phone is operated without a SIM at the moment, so I only tried WiFi (can't comment on calls and mobile data), and I haven't done real-life testing over a longer period of time yet (just installed a few minutes ago). If anything comes up that is looking odd, I'll let you know.

 

[sponk0]

If anything comes up that is looking odd, I'll let you know.

Just for the sake of completeness: phone is still running fine with no hiccups

 

[alanthelinuxguy]

here comes a tutorial how to switch from my current LineageOS 16.0 build variant A to official LineageOS 17.1 build without having to do a clean install (e.g. to keep your data):

M:

Following the above instructions (Dec 19, 2020 at 7:38 PM), I have now installed LineageOS 17.1. The flashing process worked exactly as advertised. I have yet to try out Android 10 to any great extent, but I do have two questions for you regarding the new build:

(1) Are you switching to LineageOS 17.1 builds going forward, such that there will be future updates of this new variant and, presumably, if this is the case, the recent 16.0 series will be abandoned at some point?

(2) I ran into some storage issue with 16.0 where the free storage dropped precipitously to about 300 MB and Google Play refused to download and install any new apps or updates (see: https://linuxnorth.wordpress.com/2020/12/19/tracking-down-android-storage-space-hogs/).

Initially, I thought that this was the K-9 E-mail client grabbing almost 1 GB of storage in app_view/BrowserMetrics. I cleaned out this folder, checked the web for references to BrowserMetrics and found a bug report on GitHub:

Webview’s BrowserMetrics should be regularly cleaned by K-9 #5061

Webview's BrowserMetrics should be regularly cleaned by K-9 · Issue #5061 · thunderbird/thunderbird-android

Describe the bug I noticed that K-9 Mail occupies 800MB of internal storage and decided to check what eats so much space. Running du -h /data/data/com.fsck.k9 revealed the WebView's BrowserMetrics ...

github.com

The OP indicated that "we (the group of people maintaining legacy LineageOS including MSE1969) resolved the problem by switching system webview to Bromite."

However, before I could research Bromite, I found that free space was still being eaten up and it turned out that many apps were using considerable amounts of storage in the same manner. A post on GitLab noted the same issue.

WebView produces a lot of garbage in cache

WebView produces a lot of garbage in cache (#2820) · Issues · LineageOS / issues / android · GitLab

Apps using WebView (e.g.Jelly) are collecting a lot of garbage in their app_webview/BrowserMetrics directory, which never gets deleted. I just manually deleted several hundred MB in seveal apps....

gitlab.com

A recent post on this forum noted that "This will be resolved by any builds dated 20201227 or later..."

Can you confirm that this is indeed the case for your build of LineageOS 17.1 ?

As usual, many thanks for all your work on these custom ROM's and Happy New Year!

Alan

 

[MSe1969]

M:

Following the above instructions (Dec 19, 2020 at 7:38 PM), I have now installed LineageOS 17.1. The flashing process worked exactly as advertised. I have yet to try out Android 10 to any great extent, but I do have two questions for you regarding the new build:

(1) Are you switching to LineageOS 17.1 builds going forward, such that there will be future updates of this new variant and, presumably, if this is the case, the recent 16.0 series will be abandoned at some point?

Hello Alan,
yes, my plan is to open a new thread for the LineageOS 17.1 "microG" build variant and to stop the LineageOS 16.0 builds eventually. I won't provide a "default" LineageOS 17.1 build any longer, that is why I have published the instructions to help people, who have so far used the build variant A of my 16.0 builds to take advantage of the official LineageOS 17.1 builds. I have provided the build variant A for LineageOS 16.0, as there hasn't been any official 16.0 build for the Osprey device, but providing a build variant with almost no difference to the official builds does not really add any value - that's why.

(2) I ran into some storage issue with 16.0 where the free storage dropped precipitously to about 300 MB and Google Play refused to download and install any new apps or updates (see: https://linuxnorth.wordpress.com/2020/12/19/tracking-down-android-storage-space-hogs/).

Initially, I thought that this was the K-9 E-mail client grabbing almost 1 GB of storage in app_view/BrowserMetrics. I cleaned out this folder, checked the web for references to BrowserMetrics and found a bug report on GitHub:

Webview’s BrowserMetrics should be regularly cleaned by K-9 #5061

Webview's BrowserMetrics should be regularly cleaned by K-9 · Issue #5061 · thunderbird/thunderbird-android

Describe the bug I noticed that K-9 Mail occupies 800MB of internal storage and decided to check what eats so much space. Running du -h /data/data/com.fsck.k9 revealed the WebView's BrowserMetrics ...

github.com

The OP indicated that "we (the group of people maintaining legacy LineageOS including MSE1969) resolved the problem by switching system webview to Bromite."

However, before I could research Bromite, I found that free space was still being eaten up and it turned out that many apps were using considerable amounts of storage in the same manner. A post on GitLab noted the same issue.

WebView produces a lot of garbage in cache

WebView produces a lot of garbage in cache (#2820) · Issues · LineageOS / issues / android · GitLab

Apps using WebView (e.g.Jelly) are collecting a lot of garbage in their app_webview/BrowserMetrics directory, which never gets deleted. I just manually deleted several hundred MB in seveal apps....

gitlab.com

A recent post on this forum noted that "This will be resolved by any builds dated 20201227 or later..."

Can you confirm that this is indeed the case for your build of LineageOS 17.1 ?

Just to be sure, that things don't get mixed up or confused:

1. The build variant B ("microG build") of my builds uses Bromite Webview instead of the default System Webview, hence those builds aren't affected that much, as Bromite seems to clean up this directory frequently. There is however an issue opened for Bromite to entirely remove that feature - one of the next releases of Bromite will include it.
   
   
2. The build variant A (Standard build) makes use of the default Webview shipped by LineageOS, that is why those builds were affected. LineageOS has now patched their Webview, so any new official builds including that patch will stop wasting that much space (you may however still have to manually do some cleaning)
   
   
3. As indicated above, I will stop providing the build variant A for LineageOS 17.1 - people who were using my build variant A for LineageOS 16.0 should switch to the official builds of 17.1.

Regards, M.