yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] rammingspeed:
Hi,

I am having issues with the camera flash/flashlight

whenever I try to enable the flashlight it turns on for a split second then turns off while it remains enabled in the drop down menu

and in the AOSP Camera app the flash option is just greyed out.

Do you know what is causing it?
[Moto G Android Development] MSe1969:
Don't have my falcon with me right now, so can't test myself to give a truly verified response; I have to leave that up to other forum participants.

However - my usual spot check tests after building did not reveal anything in particular, so I assume, it is not related to the ROM itself. (I remember having used the cam, but not sure, whether I tested the light this time, too)

Can you produce a log? Please also provide some more details, like build variant and build date, use of custom kernel (y/n), camera mod (y/n), magisk modules (y/n) etc.

Also - to narrow down your issue, make a backup in TWRP and then do a factory reset via TWRP to see, whether the issue persists. If not, it definitely points to your specific setup, if yes, and others won't confirm, it is related to your device (hardware). In the case, that others report same issue, I'll check after my return.
[Moto G Android Development] rammingspeed:
It was a firmware issue, I got the original images from Lolinet's mirror. After flashing them, it worked fine.
[Moto G Android Development] PhillipJC:
Installed build B. Very happy with the ROM. ;)
[Moto G Android Development] ChrisRM:
[MENTION=7929484]MSe1969[/MENTION],

Are you going to be able to include the covid exposure-tracing add-in from Google (https://github.com/google/exposure-notifications-server/) ?

Chris M
[Moto G Android Development] MSe1969:
The link points to the SERVER part used by health authorities to manage and push the tokens in case of a reported infection case. Haven't seen yet, whether the CLIENT part of the Android OS providing the API to any app is also already open sourced by Google. Haven't seen that, yet. However, assuming it is or will be, I could think of the following:

a. The microG project picks it up - then of course it would find its way into the B variant eventually (maybe the most logical step, as it is currently provided through the genuine Gapps) - as the /e/ project meanwhile sponsors/supports the microG project, I have some hope towards that direction, but I have no clue really...

b. LineageOS or maybe the /e/ project would pick it up, or any other CustomROM project to make it part of the OS. If that is the case, I could look at trying to down port / take over the implementation.

c. I however do not see myself as a "Pioneer" for this...

EDIT: [MENTION=5188438]ChrisRM[/MENTION] - just noticed yesterday a couple of commits in the GmsCore repo of microG from the last couple of days. Seems they work on getting the Exposure Notification API functional in microG ...
[Moto G Android Development] ramjisrk:
Hi [MENTION=7929484]MSe1969[/MENTION],

Great Thanks for this ROM (i've installed Variant B with Aurora) in my 1gb/8gb xt1033. The fact that it's been given latest security patches itself is outstanding,kudos to your effort. Apart from that it's super smooth, very good battery backup.i stopped playing with custom ROMs in this falcon.

i really wish similar os s available for other devices also. keep it up. one small thing/issue is wrt to cast to tv,which i suppose is related to Google sign in ,may be ,I'm not sure,which I'm fond of,but considering the overall experience of this rom i don't mind. once again thanks.
[Moto G Android Development] zagzag99:
Thanks [MENTION=7929484]MSe1969[/MENTION]

I've recovered a falcon device, just to prepare it for a first grader.

It's my first try with microg.

All seems working.

My only question is what do people do with Gmail, Calendar is there away to get these working with the Google account?

Also the AuroraStore shows me microG services core update but it doesn't seem to install it. Did I forget to install something additional on variant b ?
[Moto G Android Development] MSe1969:
Regarding Aurorastore, DON'T "upgrade" the microG GmsCore!!! In fact, microG spoofs to be the genuine Google spy-services, that is why they are offered through Aurora.

Rather set the GmsCore updates to be ignored by Aurora (long press on the update item and you'll see that option).

Regarding Gmail, Calendar etc., it depends on what you want:

Usually, microG is for people aiming at getting away from Google, so it offers to still maintain some compatibility for (non-Google produced) apps with Google-dependencies. In that case, people would choose a different mail provider and by doing so, there is usually also options to synch contacts, calendar etc. to this provider (e.g. posteo.de, mailbox.org, etc.) using the DAVx5 app.

Other people however simply want to use microG for older devices not having too much space (like e.g. the falcon), but would like to continue using Google services with their account. It has to be said, that the Google-produced apps are usually very deeply integrated with the genuine Google play-services and thus it will become a little bit tricky to make them collaborate with microG. The shadow53.com site gives you some input on how to achieve this.

For GMail, you can also logon via Webbrowser to your account and enable your GMail account (in settings) to allow to be used by a standard mail app supporting the IMAP protocol, then you can even use the shipped AOSP mail app of LineageOS.

Just for Info: Google does not like that idea too much, so be prepared to confirm a couple of "security" warnings (if you replace the word 'security' with the word 'fingerprint' for all those warning messages coming from Google, also e.g. in case of warnings for logons from unknown devices, you are closer to the real reason behind those activities).
[Moto G Android Development] Guttergorm:
My first bootloop on falcon, tried to fix it with latest complete zip (20200808-oms), but did not work. Fastboot and adb accessible, TRWP working. Before, I updated via OTA. BTW: Are the delta updates stored on the device (and where?) [MENTION=7929484]MSe1969[/MENTION].

Any ideas what to try before I flash the latest stock rom? Or is data loss inevitable? Would a TWRP-backup provide any higher chances than just dirty flashing latest ROM version?

Would this be the correct stock ROM: XT1032_FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip

BTW: great ROM, would still use only falcons if mine had 4G.
[Moto G Android Development] MSe1969:
There are no delta updates, thus not stored anywhere - always a full update of the /system partition.

In regards to your boot loop, as TWRP is accessible, I don't see a need for a stock ROM flash, if everything else would not help, you can always factory reset via TWRP and flash the lastest ROM (aka "clean flash"), but this means loss of data.

Did it happen directly after an OTA update? Also, do you use magisk?
[Moto G Android Development] Guttergorm:
I only care about the data, not serious, but keeping them would be nice. Thanks for the suggestion to factory reset and clean flash.

I did not happen directly after an update, falcon rebooted itself and got stuck in a bootloop. And yes, I use Magisk.

Are the update-zips deleted after flashing, could not find it an the device?
[Moto G Android Development] Scranalot:
Go to:

Settings > About Phone > LineageOS updates

Click on the 3 dots in the top right corner & a menu should pop up.

Click on 'Preferences'

I've attached a screenshot of mine - you might want to take a look at yours ;)
[Moto G Android Development] Guttergorm:
Sure, if it boots again ;)
[Moto G Android Development] Guttergorm:
Worked, thanks.
[Moto G Android Development] MSe1969:
New builds with September 2020 ASB patches

Hi all,

new builds are up with Sec. string 2020-09-05 and updated webviews to M85 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

Happy flashing!

Regards, M.
[Moto G Android Development] seawoofer:
Why this question ?

Magisk can give problems with this rom?

Thank.
[Moto G Android Development] MSe1969:
There is a very specific situation with Magisk during OTA updates:

Different from the "standard" update flash process, where in fact only the /boot and the /system partition are replaced (with a backup/restore process triggered from "survival scripts" in /system/addon.d), the "survival script" for Magisk requires read/write access also to the /data partition during the upgrade. Magisk uses a certain space on the /data partition to spoof system components and uses a modified kernel making use of it.

So, if all of the below applies (if only one point does not apply, you are safe), you will end up in a mess and have a bootloop:

- Your /data partition is encrypted

- You have Magisk installed

- You perform an OTA update and don't flash manually

- Your TWRP version either does not ask you for the decryption password when rebooting to recovery for the OTA update, OR you cancel this dialog instead of entering your passphrase (password, PIN, pattern, whatever you have configured)

=> In that very specific case, the /data partition is not accessible, when the Magisk script runs to re-install Magisks after the new system partition has been flashed.

=> As explained above, Magisk uses a certain space on the /data partition to spoof system components and uses a modified kernel making use of it

=> If that link is broken, because of above scenario, you will be in trouble, as part of the Magisk re-flash is to re-establish that link properly

EDIT: This is not specific to this ROM, this applies to all ROMS - it was e.g. an issue with TWRP 3.3.x, which on purpose did not ask you for the decrypt passphrase during an OTA update.

Regards, M.
[Moto G Android Development] ashutoshmn:
Hey [MENTION=7929484]MSe1969[/MENTION]

I'm using your builds since the beginning and must say you've done an outstanding good job!

What I'd like to ask is about an issue that has bothered me every time irrelevant of the build/variant. It's about the phone soft rebooting and getting stuck at lineageOS boot animation (not booting into OS) whenever the wifi is turned ON. And it happens randomly (sometimes within a month of fresh install, sometimes may stretch to more than that but usually in that time frame). I've have nothing unusual installed, just the magisk.

For the workaround, going into TWRP and deleting this file from system/etc/firmware/wlan/prima/WCNSS_qcom_cgf.ini makes it boot again into the OS.

Maybe it's related to WCNSS crash or something idk. Need your guidance here.
[Moto G Android Development] MSe1969:
Thanks for your positive feedback!

In regards to your WiFi issue, I haven't ever experienced this (and nobody reported so far). I am using WiFi on my falcon all the time - but I also have to clearly state, that the falcon is NOT my daily driver, so my use of it is rather "light" - mainly, when I test a new build, tbh

Further, generally speaking, a log is always helpful... ;)
[Moto G Android Development] phpbb3:
#nice

Thank you!

I see a bit of discussion about magisk and los updater: for me, this was unknowingly avoided by not needing a screen lock - it's just a bt music phone no personal stuff here!

But now I am curious, [MENTION=7929484]MSe1969[/MENTION] do your builds include Lineage recovery? If so maybe I will reinstall without twrp on my recovery partition. More curiously, could it resolve the user's problem with decrypting data partition for Magisk? My knowledge on lineage recovery is limited especially on older android versions.

-Posted from XDA Labs on my 2013 8GB falcon ;)
[Moto G Android Development] ashutoshmn:
Thanks for your worthy input!

EDIT: Actually solved it by deleting 'wifi' folder under data/misc

Cheers!
[Moto G Android Development] MSe1969:
No my builds do not include any recovery. I also have no idea about lineage recovery. The lineage recovery is created during the build process as a side product, but not included in the ZIP. I use TWRP.

The (potential) issue is that Magisk needs the /data partition available during flash, and ANY situation - independent from the recovery used (there was simply the specific situation with TWRP 3.3.x) - where /data is not accessible during an upgrade flashing, will cause an issue with Magisk.
[Moto G Android Development] phpbb3:
I'm confusing this with devices which use recovery in boot partition. Ignore my comments and continue on. Thanks again!
[Moto G Android Development] MSe1969:
Exposure Notification API / microG

Good news for you: Please find here a test build with the newest version of microG (have replaced the e.OS fork with an own build of the "original" microG, where I only have added a patch to enable GCM and Check-In by default to avoid issues when overwriting microG again) - it contains now an implementation of Google's Exposure Notification API, so it is now possible to use "Corona tracing" apps, which are built for this API:

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

This will be part of the next regular build - people interested to test and/or use it together with a "Corona app" can however manually download and flash.

Apart from the microG update, no difference to the recently published September build. I'd be interested in a general feedback about the general microG behavior (anyhow, I can't help if you feel that your specific "Corona app" would not work properly).

EDIT:

To make it clear - this only affects the "microG" build variant (B) - if you use the standard variant A and have the genuine Gapps flashed, the EN API is present by default.
[Moto G Android Development] billthefarmer:
Interesting email issue

I have flashed the latest version - lineage-14.1-20200913-UNOFFICIAL-oms-falcon. Previously I was using the last official build. Everything works fine except for the email widget (com.android.email, version 7.1.2). It just sits there displaying 'Touch to set up' despite having been set up several times. AFAICT it's identical to the email app in the official build. Weird!
[Moto G Android Development] ChrisRM:
Just installed the test version and it hesitated at the Moto logo until I poked the power button; after that, the Lineage logo executed and the phone came up OK. I suspect this is me still using the 'wrong' TWRP. Now I can wait until 24th September when our 'world beating' government is supposed to release the official track&trace app, along with a massive, legally-mandated raid on personal data. In the meantime, the falcon still flies...
[Moto G Android Development] MSe1969:
I can confirm your described behavior on with LineageOS 14.1, also on a different device, so it's related to the app.

So indeed, the widget does not work right now.

That's all I can state right now.
[Moto G Android Development] MSe1969:
I really feel with you in regards to "Brexit-BoJo"... For sure nothing to be discussed here on XDA, but scary, that living proofs of the "Dunning-Kruger effect" make their way into leading responsibilities of more and more nations...
[Moto G Android Development] ChrisRM:
It's alive!

Your work seems excellent, as the NHS app went straight on and appears to work as documented. I shall see if the local supermarket is using the check-in QR, but that's probably as far as I'll go on the venturing-out bit. I work from home anyway, and I don't feel the need to put myself at risk just yet. Well done, though!
[Moto G Android Development] MSe1969:
Thanks for the positive feedback. In fact it's not "my work", I've just included the newest microG version by making an own APK build of the GmsCore app.
[Moto G Android Development] ChrisRM:
WiFi failing

Here's a new thing after this update; WiFi fails after a time. By 'fails', I mean that the WiFi connection is lost and the WiFi widget no longer sees any WiFi instances. Restarting the phone restored things, nothing else seems to. Is there anything in this latest build that might affect WiFi or is this falcon on its last legs?
[Moto G Android Development] derfraenk:
Thanks for mentioning that. I've been seeing this too with my falcon and I also thought it may be just my device. For me it's not only with the latest release, I think I've had it for a bit longer already.
[Moto G Android Development] MSe1969:
I have recently observed this, too - could be something with the kernel, need to investigate...

EDIT: Please tell me, which build variant and which version (build date) you use
[Moto G Android Development] PhillipJC:
I have seen this too. I am on the latest version B.
[Moto G Android Development] derfraenk:
Thanks for your reply. Currently I'm using the 20200913 build, variant A. To be exact, I can't recall whether I've had it happen with this build yet, because I only flashed it a few days ago. But I've definitely had it for some time, with a few of the older builds.

Unfortunately I don't think I can pin-point to which build it started with. If you need assistance with getting more info, I'll try to help.

Edit: While I'm at it, I'd like to say a huge thank you for maintaining this firmware for this old phone. It works really well and I'm happy that I can still use this trusty little thing with an up-to-date software. :)
[Moto G Android Development] MSe1969:
If you could try to save a log/logcat when you have this behavior, before restarting the device, that definitely would help...
[Moto G Android Development] MSe1969:
To all - One observation, which I have made on my 1st falcon today:

My router is configured to switch off the WiFi at night and re-enable in the morning. It seems that then the device had issues to reconnect and the described behavior (no WiFi found at all, also not the neighbors') occurred.

BUT: This one had no SIM card and date/time was entirely out of sync. After manually correcting date and time, all was fine again. No restart required.

The 2nd falcon did not show this issue.
[Moto G Android Development] derfraenk:
That's some fine detective work. I will try to provoke the behavior on my falcon and get a logcat. I will also make sure to check whether the system time is accurate or off, when it happens. My phone also has no SIM card. Because I only use the falcon as a podcast player these days, it may take me some time to get it reproduced. If others can also help out in the mean time, that'd be great.
[Moto G Android Development] MSe1969:
Good news:

It has bothered me already longer time, that the TimeService.apk foreseen in the vendor blobs for msm8226-common (thus falcon and peregrine) isn't able to auto sync the time w/o SIM card, so I have yesterday created a test build (variant B) with the TimeService.apk from the msm8916-common tree (osprey / Moto G3).

Result:

- Auto sync also works w/o SIM card

- The issue with lost WiFi seems to be gone, at least in my test setup

I'll publish my test build today, feedback appreciated.
[Moto G Android Development] derfraenk:
Amazing, thanks for your hard work. Just a question: I'm using variant A; will you also create a variant A test build or is it too much effort?
[Moto G Android Development] MSe1969:
Here is the test build (variant B) :

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

A test build for variant A is currently being compiled and will follow (probably tomorrow).

EDIT: Here is the link for variant A:

https://sourceforge.net/projects/li...1-20200927-UNOFFICIAL-oms-falcon.zip/download
[Moto G Android Development] ChrisRM:
Excellent stuff, but there are some changes. In (B), Signal and the 'NHS/Serco Covid-19' apps simply stop; Signal did function before, although the Serco app wouldn't do the QR code location check-in. Email, the default browser and the Aurora store all work. Phone calls can be made and wifi seems stable, but I've only had this running for the last 30 minutes...
[Moto G Android Development] MSe1969:
Hi,

just to be sure - as there are two test builds for variant B:

- The one from SEP-17 with the new microG version allowing to use the exposure noitification API for the Covid-apps

- The one from SEP-27, which includes the stuff from the previous SEP-17 test build

and

the updated TimeService.apk

So I assume your issue with Signal and the UK Covid app are valid for both test builds either way, correct?

Or are you saying that the updated TimeService.apk from the SEP-27 has caused issues and Signal and the Covid app were working in the SEP-17 build?

(I don't think so, but would like to be sure about that).

In general:

Due to the new microG version, which in fact does not "update", but replace the apk, you would need to re-enable the coarse location providers in microG settings.

Regarding Signal:

Could you please check in microG, whether Signal shows as registered app for cloud messaging and report back?

If it does not show, please try the following:

1. Dial *#*#2432546#*#* (*#*#CHECKIN#*#*) with the phone app and restart the phone

2. If no success, make a local backup of the Signal app (via menu in Signal, in fact, backup your messages), de-install Signal, make sure Device reg. and GCM is enabled in microG settings and install Signal again (which should then automatically take your local backup)

Regarding the NHS/Covid app:

Please try revoking the location permission from microG GmsCore and afterwards start the Covid app to force the permission dialog appearing again (and then grant the perm again).

If it does not appear, please grant the location perm manually again.

Regards - M.
[Moto G Android Development] ChrisRM:
SEP-17 worked with Signal and Serco, albeit without the camera-based QR check-in working. The issues start with SEP-27.

The CHECK-IN thing appeared to make no difference.

Now I have to recover Signal, as (through old age-related stupidity) I cleared the various caches to see if that would improve things...

There will be a short delay whilst I rebuild the wretched thing...
[Moto G Android Development] billthefarmer:
Possible email fix

I tried replacing the email app with the Email.apk extracted from the last official build using TWRP, which works, but causes the exchange service to keep crashing. So I extracted the Exchange2.app from the build and replaced that, which appears to work fine, including the widget. So something in this build appears to be causing the email app to be build with this bug.
[Moto G Android Development] MSe1969:
Thanks for the hint - that may help me chasing the bug down. I remember that many months ago, the EMail app has received some ASB patches, so maybe some follow-on stuff needed for the widget...

While you may be happy with the old app version, keep in mind that the old versions lack an important security fix!