yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] giofrida:
Thanks for your replies. For some reason I couldn't find OpenMaps, but I tried with Sygic and it seems to just hang crash, too, so I guess nlp isn't configured. How do I activate a location provider?

Edit: If by provider you mean a location module/backend in microG settings, then I only have a Mozilla Location Service. I tried to activate it but the apps keep misbehaving.
[Moto G Android Development] rn3prokate:
Do I need root to install MicroG on Build A? How do I install it?

I want to use an app, which requires Google Play Services, but I do not want flash Gapps only for this app.
[Moto G Android Development] MSe1969:
New builds available with August 2021 ASB patches

Hi all, new builds are available and already offered via Updater app:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20210810-UNOFFICIAL-oms-falcon.zip/download

Security string 2021-08-05

System Webview 91.0.4472.164

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

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20210810-UNOFFICIAL-mG-oms-falcon.zip/download

Security string 2021-08-05

Bromite System Webview updated to 92.0.4515.134

F-Droid updated to 1.13

Regards, M.
[Moto G Android Development] MSe1969:
Please refer to post #3 of this thread - you do not need root.
[Moto G Android Development] ChrisRM:
This is very good; it just pops up on the OTA notification and just works. Excellent stuff!
[Moto G Android Development] MSe1969:
Then the answer already given by @zagzag99 is the explanation.

microG cannot 100% replace the genuine Google Spy Services and also does not aim at doing so. Many apps having Google dependencies work fine, but in general, apps developped by Google themselves usually very deeply integrate and hence have issues with microG and also apps making use of a deep integration with Google Maps are supposed to have problems with microG.

So if you can't make use of alternative apps, i.e. it is an absolute must for you to use those specific apps, then there may be only two options:

a. Not sure, whether this is still the case or not, but earlier, GMaps itself did not need the Google play services, so you may want to try installing Google maps as a regular user app and see what happens?

b. As indicated by zagzag99, you would have to go with the genuine Google stuff and variant A
[Moto G Android Development] Uusijani:
Firstly, a big thank you @MSe1969 for keeping my old Moto G (falcon) secure!

My question is about a specific feature: for some reason, Motorola has apparently disabled charging the device when the camera (flash) LED is on (I've found at least one Reddit thread confirming this). Do you happen to know if this is a hardware-level limitation, or if there's any way to override it in the OS/kernel?

I've been testing the phone as a security camera, and while it's otherwise working, in practical use not having the flash LED means having to have a separate light source, adding its own complications (timers and so on).
[Moto G Android Development] GrayNinja33:
Best ROM for falcon ever!
[Moto G Android Development] XDAnewone:
Added my thanks.
[Moto G Android Development] MSe1969:
Interesting, I wasn't aware about that - so I assume, that you have observed that behavior yourself and not only read about that?

I guess, this would be a hardware limitation, I can't think about a setting controlling this - however, honestly, I don't know.
[Moto G Android Development] Uusijani:
Yes I have: with a charger plugged in and the flash LED on, the phone does show the charging indicator, but the charge level is still dropping. Ampere also shows that it is in fact draining the battery:

Okay, thanks anyway. Motorola probably had a good reason for this limitation, such as temperature control, and overriding it would thus be risky too, even if it were possible.
[Moto G Android Development] MSe1969:
Maybe even only a result of the simple hardware design - the device was in 2013 a low budget device with still some notable offerings. As internal memory for example, the content of an ordinary SD card is used, so I would not be surprised, if this simply is a side effect of a clever, but very minimalistic hardware design
[Moto G Android Development] koshikas:
and may i remind, for a budget device the LED was pretty powerful, i've only found few that can match it in light emitted(lumens). personally i use it as a "smart" torch now
[Moto G Android Development] d4foasta:
Hi peelie,

sorry for digging this up, but i have exactly this problem after using this directions

Which permissions did you have to change, do you remember?

kind regards,

d4foasta

EDIT: Sorry i overlooked that this was only the last post on the first page *facepalm* MAY BE DELETED :)

EDIT2: It seems i am not able to find any information on this topic other than the reference in Post #22

EDIT3: If someone is interested, i managed to get it all checked. I think what finally did the trick is moving the NetworkLocation.apk from priv-app/UnifiedNLP/NetworkLocation.apk to /system/app/NetworkLocation.apk

Ah, and maybe after moving the apk removing the backends and reinstalling them + rebooting.
[Moto G Android Development] MSe1969:
It seems you use the build variant A and install UnifiedNLP to it. I am wonderng, why you don't use variant B then, which brings all pre-installed. UnifiedNLP is a subset of microG, and if you simply switch off the device registration and GCM, you have in fact UnifiedNLP.

Of course, your choice - but I don't really see the advantage...
[Moto G Android Development] MSe1969:
New builds available with September 2021 ASB patches

Hi all, new builds are available and already offered via Updater app:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20210917-UNOFFICIAL-oms-falcon.zip/download

Security string 2021-09-05

System Webview 92.0.4515.159

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

https://sourceforge.net/projects/lin14-mgoms/files/falcon/lineage-14.1-20210917-UNOFFICIAL-mG-oms-falcon.zip/download

Security string 2021-09-05

microG 0.2.22.212658-2

Regards, M.
[Moto G Android Development] ChrisRM:
Good, production-class stuff. Good work!
[Moto G Android Development] phpbb3:
Pretty tickled to see another security patch for falcon, thank you kindly @MSe1969 ...

Last time I fresh installed this, I used some weird mod I found somewhere to give me a Play Store I could turn on/off at whim. I did this because Aurora store was rough around the edges.

probably 3 months ago, this modified play store won't load anymore (likely because it can't be updated).

No big deal, as the music apps I needed were already installed.

HOWEVER, decided today to re-enable Aurora and it's service and I am amazed how much better it has gotten both in UI and functionality.

My falcon still runs better than ever, appreciate your hard work bringing it all together for this old ARM.
[Moto G Android Development] MSe1969:
Info about Sec. String

FYI: CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

Depending on the point of view, it could be argued, whether the shown sec. string should therefore not be lifted...
[Moto G Android Development] phpbb3:
Dont these CVEs impact only 8.1 and newer?
[Moto G Android Development] MSe1969:
Well, the answer is not so trivial as the question may indicate:

Google does not support Android 7.1 since longer times, if I'm not mistaken, the last ASB with official 7.1 fixes is the October 2019 one. Any later ASB simply does not mention any more Android 7.1.

The community however has continued to back-port the announced patches, if they were showing Android 8.x as being relevant and if the code would be fitting and the LineageOS directors have merged those patches, if this was strictly ASB patches.

The mentioned CVE's in fact have been addressed by Google with a major version upgrade of the V8 engine (instead of a couple of simple commits). The code changes themselves seem to apply, but the blocking point at the moment is, that the newer version uses the .bp soong-style make files instead of the older .mk format, and an Android 7.1 buildenvironment can't deal with that. The Android.bp file of that newer version is nightmarishly complex and cannot be easily "back translated". Assuming that issue is solved, we still would need to see, whether it really works or not.

So the above question cannot be answered with a simple yes or no at the moment. Further, an ASB usually contains three parts:

The "platform part" (date string ending with -01, like e.g. 2021-09-01)

This is absolutely required.

The "device-dependent part" (date string ending with -05, like e.g. 2021-09-05).

This part usually contains the kernel fixes, which depend on the kernel release and device-specific situation. They are required, if they apply. Funny enough, the mentioned CVE's are listed here and not in the platform section, which could be interpreted as also being 'device-dependent' - Google does not call them "device-dependent", but as a matter of fact, this is what happens in almost all cases.

"Pixel" bulletin - in a nutshell: "optional" (but recommended, if applicable)

Official LineageOS project's point of view is, if the above CVEs are not fixed, the official build string will not be lifted in the official LineageOS repo.
[Moto G Android Development] zagzag99:
My daughter uninstalled the camera app somehow. I thought it's a system app.

I tried reflashing but it didn't return.

What camera app do suggest for installing ?
[Moto G Android Development] koshikas:
this; https://xdaforums.com/t/app-camera-galery-non-root-users-advanced-features-17-01-16.3216944/

stock moto camera ripped for any ROM
[Moto G Android Development] zuaumlinds:
Did I do something wrong? After install the ROM and gApps, i got stuck in 'checking for updates' after the restart. Is there something that I can do to by pass it?
[Moto G Android Development] Tiki Thorsen:
Did you double check that the app is not hidden from the app drawer?
[Moto G Android Development] MSe1969:
Does the app really complain about the android version or maybe the "Google play services" version? Based on our recent conversation I assume you use microG, I am however not sure whether you use the regular ROM from the OP and manually installed microG or you use the "hardened" build with pre-installed microG?
[Moto G Android Development] oscarmbv:
The app complain about the android version, it's the only one that I have issues, all other apps work fine (even about google play services), I clean installed the rom and installed microg with the method you recommend in the op (manually with F-Droid), my microg self-check is everything ticked. I think is a problem with the app detecting an older version (but with lineageos 14.1 for microg I haven't that problem) I wouldn't be a hassle with this if the app wasn't important to me, but it's vital. I already also write to the developers of that rom, maybe it's an issue related with the app.
[Moto G Android Development] MSe1969:
Which microG version is shown, when you call the microG GMS core app?

EDIT:

I am on vacation right now and don't have my falcon device with me, therefore can' t try to reproduce your issue.

Did you install the latest (unstable) microG GMS core app?

Or maybe you could make a backup with TWRP and then try my "hardened" build with the pre-installed microG to see, whether this would work?
[Moto G Android Development] oscarmbv:
Yes I install latest version from F-Droid

I don't think it's a microg issue, because that app doesn't use any google play service. This it's the app, if someone could try, the issue is that the app doesn't open and automatically redirect to a web page (because android version doesn't support the app) but link is broken actually.

I tried also to install another version of the app and it doesn't even let me finish installation, it told me that the app isn't compatible with the phone (but with other roms works fine).
[Moto G Android Development] MSe1969:
As indicated, I can only try to reproduce the issue after my vacations. But I have made the following observations:

1. Some complaints in the reviews on playstore (my Spanish however isn't that good, but I understand a little bit)

2. When I access the playstore link with my tablet and yalpstore, I am offered version 1.6 indeed w/o playservices dependency, but when I access from my OP3 phone with Lineage 15.1 and pre-installed microG, I am offered a 4.3xxx version WITH playservices dependency! Based on device info, different app versions are offered, which often happens on playstore. And microG usually spoofs a current play services...

So how do you access the play store?
[Moto G Android Development] oscarmbv:
That´s ok, thank you for trying to help me, when your finish our vacation you could try it.

I notice that too, I already write an email to them, but the case is that the app works for me on my previous rom, that it was LOS with microg also.

I didn´t notice that until now, I access on yalp store also and offer me 1.6 (that version redirects me to a website), however I try with newer version 4.3.1 and with that version I can´t even able to install it because it says that my phone is not compatible. I think app detect wrong android version, it´s very weird.

Thank you again for your help, and sorry for the inconvenience
[Moto G Android Development] vegenbe:
ok, this is the best rom currently available for original moto g, tested them pretty much all and for much of the time thought something is wrong with my phone.

just wanted to post this for people like me that couldn't find the right one. many thanks MSe1969 for providing this incredible super stable beauty. :good::good::good:
[Moto G Android Development] meistadieb:
[MENTION=4197225]oscarmbv[/MENTION] [MENTION=7929484]MSe1969[/MENTION] I was able to install the APP on my moto g with this Rom and play services from gapps
[Moto G Android Development] oscarmbv:
Thank you so much for trying, I was thinking trying also with gapps, so the issue is microg indeed. Thank you again.
[Moto G Android Development] oscarmbv:
OK, I confirmed that the problem is installing microg with F-Droid method, I try first installing the rom without microg and gapps, and the app continue having problems, then I try install gapps, and the app works, then I try installing microg with this version https://xdaforums.com/android/development/microg-unofficial-installer-t3432360 and also works, I think I'm going to choose third method. What do you think? Thank you all.
[Moto G Android Development] Scranalot:
Update

Thanks for your response MSe1969

Your first point:

is what I was thinking & makes logical sense. However I didn't flash them to the /system partition I 'installed' them by first extracting them from open_gapps-arm-7.1-pico-20190412.zip pushing them to corresponding newly made directory's:

/system/app/GoogleContactsSyncAdapter/ & /system/app/GoogleCalendarSyncAdapter/

Making sure the ownership & permissions were correct - root:root & 755 for the directories - root:root & 644 for the .apks. :good:

Prompted by what you said:

I did a little investigation & have now 'made' a script lifted directly from this already installed one:

/system/addon.d/50-cm.sh

Here:

#!/sbin/sh
#
# /system/addon.d/91-cm.sh
# During a LineageOS 14.1 upgrade, this script backs up GoogleContactsSyncAdapter.apk,GoogleCalendarSyncAdapter.apk,
# /system is formatted and reinstalled, then the files are restored.
#

. /tmp/backuptool.functions

list_files() {
cat <<EOF
GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
EOF
}

case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/"$FILE"
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/"$FILE" "$R"
done
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac

Hopefully that will work - not 100% convinced as it will not be replacing anything?? :fingers-crossed:

Also prompted by:

I have installed & set that up & have it working in tandem with DejaVu with no issues (no Mozilla backend) :good:

Well I've been on your 'hardened' version (https://www.androidfilehost.com/?fid=1395089523397936839) for nearly 3 weeks now MSe1969 & it has performed flawlessly for me :D

I don't do social media but use standard stuff phone-calls & texts (obviously), web-browsing, camera, email, videos, Wifi, tethering, 'Hotspot' etc.

The vast majority of apps are FOSS from the F-Droid repos + 3 'saved' during GAPPS install from playstore - MetOffice Weather (best for me ;)), Dropbox & eBay ('necessary evil' for me :p)

I don't know if you are still on holiday & if so please enjoy it & do not rush to respond on my account, & I am certainly not asking for an ETA, however when you are available I have a question for you; will be continuing with the development & releasing an updated to this 'microG-oms hardened' version this month?

In conclusion I'm an extremely happy bunny MSe1969 Many thanks. :)
[Moto G Android Development] MSe1969:
I am back now :) - As there has been some interest in regards to the hardened oms build, I will continue providing it.

Your script looks okay from a technical point of view (haven't really validated, but looks OK) - if you're already using alternatives to big G* it may be worth considering alternatives to synch contacts and calendar, too. (Of course, not my call, just my opinion)

When you flash a ROM zip to update, the following happens: The content of /system/addon.d is copied into a temp dir on the recovery RAM disk. Then, the scripts are executed with the respective "backup" parameters to e.g. copy stuff from the /system partition also to the recovery RAM disk. Then /system is entirely wiped and replaced with the contents of the ROM zip. Afterwards, the scripts on the recovery RAM disk are executed again with the "restore" parameters to copy things back to the system partition, delete stuff, whatever. Finally, the addon.d folder is restored from the temp dir.
[Moto G Android Development] Scranalot:
Thanks for your continued development MSe1969 much appreciated

Indeed my intention is to move away from Google, Dropbox & go as open source as possible in the long run - but it won't happen overnight for me, unfortunately :rolleyes:

Look forward to the new release & I'll let you know if my addon.d script works OK ;)

The ROM is 100% slick, stable, lightweight, up-to-date & almost (for me) google free :)

Cheers MSe1969
[Moto G Android Development] MSe1969:
Okay - back from vacations, I was able to try stuff out:

I can 100% confirm your observations - when microG is installed as user apps, exactly what you describe is happening: Version 1.6 is offered by Yalp and any attempt to manually install a downloaded apk ends in the "app is not compatible to your phone" error

Now I tried the same on my "hardened build with pre-installed microG" build: Yalp offers the most current version is offered for download and installs without issues.

It seems, that the GmsCore.apk must meanwhile be a privileged system app, which also confirms your observations.

As mentioned before, I will start offering the 2nd build variant ("hardened with pre-installed microG and F-Droid") regularly, also the with pre-installed Yalp.

So in fact, that would be the recommendation going forward for those using microG. (Will update the thread/OP once May ASB are available)

So coming to your question above, using my "hardened build with pre-installed microG" would be my recommendation going forward.
[Moto G Android Development] JuanVCS:
Installed it and loving it, not only is it great for the security updates, but it's also much snappier than stock lollipop. Thanks for maintaining it!
[Moto G Android Development] MSe1969:
New builds with May 2019 ASB

Hi all,

new builds are available for download with May 2019 ASB fixes - as announced, this time with two build variants:

A. Default LineageOS 14.1 with substratum and microG patch

This is the build variant, which was provided here all the time (see OP):

https://androidfilehost.com/?fid=1395089523397962256

B. Hardened build with pre-installed microG and F-Droid (and substratum patch)

Pre-installed microG and security hardening features (see OP) - in fact recommended for those using microG.

https://androidfilehost.com/?fid=1395089523397962255

Happy flashing!

M.
[Moto G Android Development] Scranalot:
More Marvellous MicroG Mods In May from MSe1969

Flashed! (the B. variant) :good:

Plus with addition of the Yalp store, which I have already used to update Dropbox (they were no longer going to support my old version - so I would of had to 'upgrade' to a newer version - probably more to their benefit than mine :rolleyes:)

My /system/addon.d/ script didn't work so I had to re-install the Google*sync*.apks - but I found my error - which I have now corrected so hopefully work next time (amendments in red):

#!/sbin/sh
#
# /system/addon.d/91-cm.sh
# During a LineageOS 14.1 upgrade, this script backs up GoogleContactsSyncAdapter.apk,GoogleCalendarSyncAdapter.apk,
# /system is formatted and reinstalled, then the files are restored.
#

. /tmp/backuptool.functions

list_files() {
cat <<EOF
[COLOR="red"]app/[/COLOR]GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
[COLOR="red"]app/[/COLOR]GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
EOF
}

case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/"$FILE"
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/"$FILE" "$R"
done
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac

Terrific thanks MSe1969 :D
[Moto G Android Development] meistadieb:
In general I was keeping track on the changes through the official lineageOS page and after the EOL of their 14.1 builds through independent lineageOS log pages (cmxlog, lineageoslog). But that seems not to work properly anymore. Can you give me a hint where to find the changes? I had a look at the lineage gerrit and the git, but wasn't able to find the changes for the 14.1 branch :(
[Moto G Android Development] MSe1969:
Hi, these are the ASB changes for May 2019 on the LineageOS Gerrit:

https://review.lineageos.org/q/topic:"n-asb-2019-05"+(status:open OR status:merged)

They haven't been merged into the git, yet.

Regards, M.
[Moto G Android Development] peelie:
how to get google sync working on B variant?

hi there how did you get google sync working on B variant?

i had google sync working on A variant (using these flashable zips - https://shadow53.com/android/downloads/google-sync-adapters/) but now when i try to connect to google it is hanging after the login screen? i.e. i can't add any google accounts?

thanks for any pointers
[Moto G Android Development] Tiki Thorsen:
This happened to me many times, all you need to do is reboot and it will load normally.
[Moto G Android Development] Guttergorm:
I've got a question while preparing good old Moto G for my son with this superb ROM.

I gave encryption a try, but I am not able to mount data partition in latest TWRP. Does it work if I use a password before encryption instead of a PIN? I slightly remember that this procedure was a workaround for TWRP not 'knowing about the encryption key'. Or do I have to use a different TWRP version (currently 3.5.0_9 from twrp.me)?
[Moto G Android Development] Tiki Thorsen:
MSe1969 recommends using this version of TWRP to avoid issues.
[Moto G Android Development] Guttergorm:
@Tiki Thorsen

Thanks for the reminder. Using a password first, encrypt, change password back to PIN worked for me with last trwp.me-version (3.5.9_0).