yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] jajk:
[MENTION=7929484]MSe1969[/MENTION] 1 vote for hardened version to become the "standard" version on offer and thanks for your continued Moto G support;)
[Moto G Android Development] Scranalot:
I would like to second that, if the Dev thinks its a good idea? Even if not hopefully there will be enough interest :fingers-crossed:

Just downloaded: https://www.androidfilehost.com/?fid=1395089523397936839 & will install. Obviously what with it being a test build will report back;)

I have your latest 'standard' ROM with Micro G setup as per my post https://xdaforums.com/showpost.php?p=79214849&postcount=33

As shown the only additional 'modification' is the install of GoogleCalendarSyncAdapter.apk & GoogleContactsSyncAdapter.apk following the guidance from here:

https://shadow53.com/android/no-gapps/setup-guide/3/

So do you recommend clean flash or will 'dirty' suffice? :)
[Moto G Android Development] jemail:
I would be interested in hardened version as standard with the hardened oms version as an optional download. These are the builds I download from your osprey thread.

Many thanks for your work and help.
[Moto G Android Development] MSe1969:
"Dirty" will suffice, BUT: I recommend to uninstall all microG stuff before doing a dirty-flash and also the Google*SyncAdapter.apk to be on the safe side.
[Moto G Android Development] Scranalot:
Success

Well would of tried this but the Google*SyncAdapter.apks had disappeared from where I installed them & I couldn't locate them (don't know if when I flashed the April release of your standard ROM it may have done something :confused:)

So clean flash it was, yesterday - as per your OP ;)

Installed fine however ran into a problem in MicroG with UnifiedNlp Backend - 'Has no known last Location' in self test.

Couldn't figure it out after half a day of messing about :eek: & eventually went back to re-installing your standard ROM.

Thorough check through my settings & I realised I didn't have my Location Settings set to High Accuracy (which I had set in the standard ROM).

So today reinstalled, Location Settings set to High Accuracy, & it works :good:

There was after a bit of faffing on my part - in your standard ROM I use Deja Vu satisfactorily as the location backend. I chose it because the Mozilla backend does the location calculation onlinewhereas the Déjà Vu backend combined with the device’s GPS remembers locations associated with various WiFi APs and cell towers and recalls that information if it recognizes them again (which I believe is your preference MSe1969 ), but I couldn't get it to work satisfactorily on this Hardened MicroG_oms version so had go with the preinstalled Mozilla backend - though I have run them concurrently, which works satisfactorily, but is probably a waste of resources.

But so far so good - everything reinstalled now & appears to be working fine :fingers-crossed:

I'll keep you posted & thanks once again for this ROM :)
[Moto G Android Development] Scranalot:
Don't want to speak out of turn here but I presume as you are here in this thread & are talking about a dirty flash then you have installed the ROM in the OP MSe1969 has developed?

And followed the directions for installing MicroG that he provided?

This what I did - adding the MicroG repo to F-Droid.

So I just uninstalled the 3 MicroG apps plus the UnifiedNlp Backends that I had also installed with F-Droid.

HTH :)
[Moto G Android Development] MSe1969:
The referred ROM in this thread's OP only contains the patch, so normally microG would be installed as apps. In order to remove, this would simply mean to uninstall them. Unless you would have flashed something onto the system partition.
[Moto G Android Development] oscarmbv:
Hello, do I have to clean install the rom coming from lineage.microg.org ?? Thank you
[Moto G Android Development] MSe1969:
The lineage.microg.org ROM is signed with a specific key, you would have to migrate. Please look at the lineageos wiki (linked in a post by me at the beginning) and the lineage.microg.org FAQ. Or clean flash, whatever you prefer. This build is not signed with a special key, only with the default "test key"
[Moto G Android Development] oscarmbv:
Maybe I better clean install to be sure everything run smoothly
[Moto G Android Development] MSe1969:
Hi, just realized I did not answer yet to this post.

Regarding the Google*sync*.apk stuff, if you had flashed them to the /system partition before and had no script in /system/addon.d to restore after an update, indeed they were gone, as the /system partition is entirely replaced during a ROM flash.

Yes, the UnifiedNlp requires the coarse location to be enabled (so either high accuracy or energy saving mode) - otherwise it won't work.

Regarding Mozilla Location, i bundle it same way as the lineage.microg.org project (but I don't use it myself, except for testing purposes). The good thing is, it works out of the box (because it calculates online), but I myself use DejaVu together with GSM Location (also from F-Droid microG repo) - I think DejaVu first has to "learn" - and it can only do so, if location is determined by a 2nd location provider . . . - so only using DejaVu on a fresh system will not make you happy fro a while...
[Moto G Android Development] MSe1969:
My advice to uninstall all microG stuff, which you had quoted, was in regards to coming from my standard build linked in the OP to my "hardened-oms" build.

That advice is still 100% valid.

Your question however was related to coming from the lineage.microg.org build to one of "my" builds. And here, the main issue is that the microg.org build is signed, and you would have to first execute a migration script to replace the keys. You would have to e.g. take the one from the LineageOS wiki and modify it as explained in te lineage.microg.org FAQ.

Indeed, the keys migration stuff can become messy, that is why I recommend to do a clean install. It is no "rocket science", but as already indicated in one of my initial posts - quote: "if you don't understand these instructions, it really is better and in your own interest, if you don't do it"
[Moto G Android Development] oscarmbv:
Thank you, I already clean installed the rom and everything is ok so far.
[Moto G Android Development] oscarmbv:
Actually I have a little issue with this rom, but just with one app in particular, I use an app from an online banking (BBVA), for other roms I had no problems at all, but with this rom the app told me the android version isn't compatible (the app supports 4.0+).
[Moto G Android Development] Tiki Thorsen:
I understand and sorry, I was mistaken about Adclear, confused it with Blokada.
[Moto G Android Development] The-Saint2k:
Hello,

I still have the problem that after a few hours the wifi turns off. Is there any prospect of improvement here?

Thanks for your great work on this old device.
[Moto G Android Development] MSe1969:
Unfortunately, I don't have a good idea. If it cannot be specifically reproduced (except that it seems to happen after a couple of hours on some devices), it is difficult to grab a log to see, what happened
[Moto G Android Development] ChrisRM:
Another good reason to avoid Google: https://www.theregister.com/2020/12/03/google_play_core_library_android_rfi_vuln/
[Moto G Android Development] The-Saint2k:
Hi,

I could now probably make a connection why the WLAN goes off.

As soon as the Corona Warnapp is activated, the WLAN breaks down after some time. If I deactivate the APP, the WLAN remains constantly on.

Can anyone who also has the WLAN problems confirm?
[Moto G Android Development] Allenw33:
Hi

in all builds does not activate wifi. Just do not accept to connect the wifi
[Moto G Android Development] Crescent Spirit:
Hello! I decided to give your hardened build a try since it seemed very interesting but I run into a rather serious issue; the Wi-Fi isn't working on your latest build. Even right after the first boot, it's disabled and there's no way to turn it on. Unless this is tied to some weird security option you have added, if you are aware of this issue, shipping a ROM like this seems like a weird decision... :confused:

I'm not sure if my device is at fault here but right before flashing your ROM I was running an Android 10 build and the Wi-Fi was fully functional. It even resumed operation right after restoring the backup of said build. This problem is also present in your October release, haven't checked any earlier ones though. Maybe there's a workaround a user can perform from his end? Because I would very much like to start using this light ROM as my daily driver; it's perfect for this old device :)

Thanks in advance!
[Moto G Android Development] jajk:
@Allenw33 @cresent Spirit WiFi works in all builds. You are doing something wrong so don't be too quick in blaming the ROM. On first boot, some toggles need to be turned on, then off and back on again before they work.

The only fault with WiFi is the phone will reboot after using WiFi Hotspot for a long time. That problem has been around for a very long time and is most likely a fault introduced in the original Lineage ROM that this ROM is based on.
[Moto G Android Development] Crescent Spirit:
That's some nice but rather abstract advice my man; what would those specific toggles be, mind you? I have used this ROM before about half a year ago and this behavior wasn't present there, no toggles of any kind needed to get things working right off the bat. Especially something as essential as Wi-Fi functionality, which is why I used that tone for which I apologize to the creator if it came off too strong. I felt it was needed however as doing something "wrong" on my part wasn't really true as all I did was follow the normal, routine install procedure according to the instructions provided by the creator (aside from the recommended 3.2.1 TWRP version, since I'm using the latest one, 3.4.0; however unlikely, this might be the actual culprit so I will check and report back on that). Regardless, the ROM alone installs perfectly without any additional bells and whistles to burden it down or make things complicated in some way. Plus, as I mentioned, the Wi-Fi works just fine with the other ROMs including past LineageOS builds, official or otherwise, so... I had to say something 🤷‍♂️

Anyway, the situation is that the Wi-Fi right after boot is offline and cannot be toggled on, it seems like it's stuck somehow in a perpetual "trying/about to be enabled" state as evidenced by the loading bar visual cue on the Wi-Fi settings page. Restarting (obviously) doesn't solve the issue, so like I mentioned in the previous post as well, if there is in fact some kind of setting or a procedure involving toggling stuff on and off, that you know can resolve this, please provide it so it can also potentially be added as a definitive troubleshooting note for future reference. As always, thanks in advance! :)

Btw, as a side note, the fact that (at least) another person experiences the same problem at about the same time is a rather strong indication in itself that the problem isn't user/device-specific but rather, a more widespread phenomenon that's ready to be... "bumped" into :3
[Moto G Android Development] Crescent Spirit:
@Allenw33 please test this 3.2.1 TWRP version theory yourself if you can. This might be our solution... :unsure:
[Moto G Android Development] MSe1969:
Thanks for the hint - when I find the time, I will look deeper into it.
[Moto G Android Development] MSe1969:
I never experienced any WiFi difficulties in my two builds - except for the already discussed issue, that under - yet not exactly identified conditions - WiFi drops after some hours. See also comments by @jajk
[Moto G Android Development] MSe1969:
See my other comment - if WiFi entirely stopped working, I would not ship a build! On my devices, it perfectly works in both build variants. The only topic around WiFi is the discussed one, that under - not yet 100% identified conditions - WiFi drops after some hours in some cases.

Thanks for your in general positive feedback about my build. I have no specific idea, but the fact, that you have played around with Android 10 on the falcon rings somehow an "alarm bell" to me. If you scroll back at this post in this thread:

https://xdaforums.com/t/rom-lineage...r-moto-g-falcon.3808428/page-21#post-83104675

and read the follow-on posts, you will see the exact same issue, as you experience. It is worth to read through the respective posts.

The solution finally was presented as well - please try, whether that fixes your issue as well:

https://xdaforums.com/t/fix-cant-turn-wifi-on-you-are-missing-this-file.3007540/

In general:

Although I can understand being curious about the "latest and greatest" Android version, the falcon simply is too old for such "experiments"!

I have stated that a couple of times already.

After 'Nougat', there hasn't been any build with enforcing SELinux, which makes the whole build

useless

as daily driver! W/o SELinux, the build is entirely vulnerable and updating a permissive ROM to most recent ASB patches would be like enforcing the roof of a house, which only has the openings in its wall foreseen for the doors and windows, but actually has no doors and windows, to "improve its security". Permissive builds are simply an interim step to get all the features work, but the "slave work" to get SELInux enforcing is the pre-requisite to make a build suitable as a daily driver. Besides, each newer Android version has higher hardware demands, so you most probably wouldn't be happy with an enforcing Pie or 10 build...
[Moto G Android Development] Crescent Spirit:
@MSe1969 you are right, guess I messed up a bit... I figured it had something to do with the "higher" ROM installs at this point. Ignorance got the better of me; it's true, the Pie/Q experiments were a risk but I was very careful with which ROMs I was gonna test and I only did that because I, and apparently a few others, was under the assumption that no essential files even had a chance of being tampered with by a ROM outside the regular Cache/Data/System partitions. I have been using the SuperiorOS build (https://xdaforums.com/t/rom-10-0-falcon-superior-os-phoenix-unofficial-20-02-2020.4021631/) for a while now with Magisk root along with a few select modules from trustworthy developers and had no noteworthy issues. Never used any weird apps or scripts that could potentially harm the device. But I guess, as demonstrated by the series of posts you linked me to, the situation is indeed a little more complicated than that... I was actually about to start fiddling with the files placed in the /root folder to find out what had gone wrong but to be honest, I wasn't really looking forward to that, and besides, the plan was to check in here first to get some advice from you and other experienced members :)

Anyway, I will give this "MAC address file replacement" solution a try and report back, thanks! (y)

P.S. Curiously enough, the last official LineageOS build (from the archive) doesn't have this issue present; the Wi-Fi functions as expected... :confused:
[Moto G Android Development] Scranalot:
Good Afternoon

Just like to agree - I was originally on the 'A' Build (when it was the only build) & I'm exclusively on the 'B' Build - on both my Falcons the XT1032 & the XT1033.

I use WiFi almost exclusively on the XT1033 with no issue to speak of (check my previous posts here on in this thread).

I do occasionally have an issue when using the phone as a WiFi hotspot whereby I sometimes have to toggle the 'Hotspot' tile on, off & on again to make the connection & once connected there are no issues for me - this however is a different matter from the one being stated, but I thought it worth mentioning in passing.
[Moto G Android Development] ChrisRM:
FWIW, I'll second the shift back to TWRP3.2.1 from 3.3.0; I saw the new TWRP ('Ooh, shiny!') and put that on to install a new version of the Falcon ROM, and then things weren't so good. No clear causal link back to the new shiny, just nowhere near as reliable. Downshifted back to 3.2.1 and reliability regained.
[Moto G Android Development] Crescent Spirit:
Hi again. Seems like placing (or replacing) the Wi-Fi file provided in this post: https://xdaforums.com/t/fix-cant-turn-wifi-on-you-are-missing-this-file.3007540/ does indeed manage to restore Wi-Fi functionality but requires a procedure involving root access and a root explorer to move the file at that

root/persist

folder. Not the biggest deal but can complicate things a bit for the casual user;

@MSe1969 please add/note this troubleshooting instance to your extensive installation page/part because a lot of people might be coming from a later Android build and (potentially) run directly into this issue, saving them the trouble of going through the initial confusion and a few hundred posts in search of a solution : P

I am however perplexed by the fact, as mentioned in my previous post, that the last, official LineageOS build works right out of the box, without having to tamper with the Wi-Fi file. Could you maybe consider replacing the file yourself and ship it with future ROM releases? Unless of course, this is just a part of a series of optimizations (featuring other files as well) on your part that the ROM needs, in which case, I guess such an action wouldn't be worth it. Don't exactly know how this works so... please excuse my ignorance on the subject :3
[Moto G Android Development] jajk:
So there are 2 clear problems using wifi hotspot:

On a fresh reboot, the wifi hotspot tile has to be toggled on to off and back on again before it works.

After a couple of hours using wifi hotspot, the phone will reboot. There seems to be a memory leak if you watch your free memory diminishing.

I think both of these problems are inherited from the original Lineage 14.1 so we are kinda stuck with them. Not a deal breaker compared to the many woes of trying to run the higher version ROMs.

@MSe1969 It is probably worth listing these 2 faults plus whatever the fault is with wifi (if it can be defined accurately) in the OP to head off the repeated questioning on these issues.
[Moto G Android Development] MSe1969:
Done.
[Moto G Android Development] MSe1969:
New builds available with December 2020 ASB

Hi all, new builds are available for download and also offered as OTA updates:

A. Default LineageOS 14.1 with substratum and microG patch

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

ASB Security string 2020-12-05

System Webview on 86.0.4240.198

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

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

ASB Security string 2020-12-05

Bromite Webview on 87.0.4280.68

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

F-Droid updated to 1.10-alpha1-114

Happy flashing!

Regards, M.
[Moto G Android Development] ChrisRM:
As usual, variant B just got on with it. I'm beginning to take this for granted ... 😁
[Moto G Android Development] jajk:
I was faced with the failure of my Falcon's speaker and thought that was the end of a very long love affair...😢

Then I discovered the battery had puffed up so far that it was lifting the mid frame speaker contacts off the motherboard. The battery was a Chinese counterfeit type (sold as genuine) that does not have a real temp sensor so battery life is diminished. So the question was: Do I replace the battery for a 2nd time or promote my Samsung A20 to my primary phone? The Samsung has very poor audio volume, no notification LED thanks to the obsession with notch displays and is a pain in the proverbial to carry around , not to mention the hopeless reception😖

The December update has again sealed the fate of the lesser Samsung and a new Falcon battery is on its way. Samsung goes back to being abused as a boat GPS - a fitting punishment for a piece of rubbish!

Thank you so much for your continued support of the beloved Falcon @MSe1969

Edit: New battery arrived.... another fake advertised as genuine but that was fully expected....gotta love ebay and all the false claims :rolleyes:

For those who wonder how to detect a fake battery - it is easy if you use an app like cpu-z that reports the battery temperature. All fake batteries ( for any model phone) report a constant battery temperature because they have a fixed value resistor emulating what should be a temperature sensor. So if you see something like 22 or 25 degrees all the time, you have a fake battery. Should still get another 1 or 2 years out of the faithful Moto 😀
[Moto G Android Development] ChrisRM:
Here's slightly interesting; what3words sort of works on the Moto G. Because it had previously not shown any maps, I'd assumed that the app was broken but the location aspect of the app does work. The /// address found agreed with the one provided by my Note8, give or take a difference from the earlier generation of GPS. Seems accurate to 15 or so m, so still a very useful locator in emergencies. Still can't show map or satellite of where one is, so navigation is not available, but still useful.
[Moto G Android Development] MSe1969:
Interesting observation, thanks. No idea yet, where that would lead...
[Moto G Android Development] MSe1969:
Done.

Your proposal sounds logical, however - this requires some further analysis and is less trivial as it may initially sound. I may get back to that at a later point in time . . .
[Moto G Android Development] matbarni:
WiFi disconnects all the time. Can't keep connection for more than 20 secons anymore. Tried resetting network config, the problem persists.

Wiped the whole phone, everything, data, storage... reflashed... and WiFi connnects, disconnects, and can't obtain IP anymore.

I can set a fixed IP, but it does not recognize internet access. I set a fixed IP at the router based on phone MAC, and it does not matter, phone disconnects after any attemp of using the WiFi.

And yes... I download that file some people said to be downloaded and put it inside the /persist folder... rebooted... and the problem is the same.

I had to revert to stock and do all the procedure to come back to Lineage and the WiFi seems fine.

Everytime I update the Lineage OS I get strange bugs that appear after a while...

The best option is to do always an 100% clean install of newer versions... at least for me.
[Moto G Android Development] Tiki Thorsen:
Yesterdays I did the standard proccesure to flash the Android 10 AOSP Extended 7.0, then decide to re-install this ROM and the WiFI refuses to turn on.

From what I read matbarni post, I need to flash a stock rom of... Android 5?
[Moto G Android Development] Tiki Thorsen:
Update, when flash either of the Android 10 Custom (AOSP & Superior) the Wifi works again, but going to back this ROM and the WiFi is still broken.
[Moto G Android Development] MSe1969:
Just to be sure: You did scroll back in this thread, found this link here:

https://xdaforums.com/t/fix-cant-turn-wifi-on-you-are-missing-this-file.3007540/

and have already tried?
[Moto G Android Development] Tiki Thorsen:
I did but I could not figure out how to do that.

I fixed it by flashing "XT1032_Retail_Brazil_51_Optimized_v1.0" from here and then this ROM again.
[Moto G Android Development] Tiki Thorsen:
When I try to encrypt the phone, it reboots but it does not encrypt, just boots straights into the OS as normally.
[Moto G Android Development] MSe1969:
Which recovery product and version do you use?

I recommend in the OP not to use the latest TWRP, but version 3.2.1 to overcome encryption issues. There has been already some discussion in this thread about that topic.