yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] MSe1969:
Thanks for pointing this out.

To be honest, when I applied the fixes (and amongst those fixes, also the 'spectre' commits) to several kernel sources of the devices, which I build, I did not check this in particular.

However, those patches are part of the Linux upstream kernel and they also "do not harm". It all points into the direction, that user-space controlled components must not do certain things.
[Moto G Android Development] legendavey:
Thanks for keeping our Moto G updated with the latest patches! LOS plus subs is the best option in terms of stability and functionality for an old device like this. :)
[Moto G Android Development] DrFossil:
This ROM is so stable and works flawlessly. Really appreciate the work and thank you for putting your precious time on our Moto G.
[Moto G Android Development] MSe1969:
As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds.

The 14.1 tree will however continue to be maintained for security patches by the community (I am one of these contibutors, btw).

So this build will normally continue.
[Moto G Android Development] peelie:
thanks good to hear : )
[Moto G Android Development] MSe1969:
New build with March security updated

Hi all,

a new build with March Security updates is available for download:

https://www.androidfilehost.com/?fid=1395089523397913539

It also contains an updated System Webview (version 72.0.3626.121), which includes CVE-2019-5786.

Regards, M.
[Moto G Android Development] Lemmy554:
Thanx mate :good:
[Moto G Android Development] capz21:
Is it recommended to use a custom kernel with this ROM?
[Moto G Android Development] MSe1969:
The kernel used in this build is a fork of the LineageOS kernel (cm-14.1 branch) with many additional security patches from the android security bulletins (ASB). Depending on how you define "Custom Kernel", i.e. any other kernel than the oficial one in the LineageOS repo, this is already a Custom Kernel. I felt the necessity to add further security patches, because the LineageOS kernel hasn't received some for a while. Meanwhile, due to cm-14.1 being in "legacy" mode, the LineageOS kernel definitely won't get any further fixes (only the device-independent repos). When applicable and possible, I will continue adding patches to "my" kernel here.

If you are keen on finding another kernel for this device with further tweaks, by all means please go ahead. (Of course, I can't, so I won't support issues with that). The device runs smoothly with the delivered kernel of this build, the kernel is already upstreamed to the latest linux-stable tag, before 3.4 went EOL, so only reasons to look for another one, if you ask me, would be areas like "overclocking" or specific features/modules.

I won't give you a "yes" or "no" as answer, this would be your decision and the info given by me may hopefully help you.
[Moto G Android Development] Scranalot:
Thethering

Good Day

Firstly I wish to thank you for this ROM & keeping the venerable old 'Falcon' viable & up to date.

I had previously been on LineageOS 14.1 & I'd been very happy with it till it's demise last month. But even then I was toying with the idea of LineageOS + Micro-G, for privacy & size reasons, however development on both has now ceased because of the decision by the Official LineageOS to drop 14.1 now that 16.0 has now been released mainstream.

So I came here to your project MSe1969 via a link from the 'official lineageos 14.1 for falcon nightly' forum.

After 2 'installs' with no-gapps/micro-g implemented & a 'dirty' re-flash after the 2nd install (had to revert back to official LineageOS 14.1 after the 1st install - all down to database issues - pulling & pushing contacts, calendar & messages over adb) I'm happily up & running almost flawlessly thank you very much.

However I have encountered an issue with trying to tether via either USB or Wi-Fi Hotspot when trying to use the phone as a mobile access point - the phone connects to the device (laptop) but fails to get an IP & the connection then fails.

Firstly I would like to know if this a bug or maybe something I have messed up on - especially due to the multiple flashes (though I'm pretty confident all went well it is of course possible) ? Is it something related to using Micro-G? & has it just occurred on this release?

I don't know what the uptake of your ROM is MSe1969, but I don't see any other reports of this occurrence here but its possible other people just don't use tethering. Also tethering worked fine with the official LineageOS - right up till the final Feb 2019 build. :confused:

Apart from that I'm really happy with the ROM it's pretty much everything I'm after - stable, secure, up to date, more private & leaner (thanks to micro-g) & responsive - but I do use mobile tethering a reasonable amount so its obviously pretty important to me.

Again many thanks for this excellent ROM & keeping 'falcon' alive. :good:
[Moto G Android Development] MSe1969:
Hi, thanks for the positive feedback.

I just have tested successfully both, hotspot and also USB tethering on my falcon device - no issues, worked like a charm.

I don't think it is related to microG, I have microG installed on my device, where I just did the test and microG does not tamper with network functionality.

Why you have those problems, I can't say - but I have two ideas to maybe look at:

1. You said you went to official LineageOS and then 'dirty-flashed' my build. Did you follow the instructions on the LineageOS side to convert the signatures accordingly? (See also my post in this thread)? (Well, if not, you definitely would have much more trouble than a non-working tethering . . .)

2. Are you using AfWall+ or any other firewall? That causes trouble in conjunction with tethering - I use it normally (including some extra-scripts), but to test tethering, I simply switch it off.

I did not spend too much time to fine-tune AfWall+ to have working tethering.

Hope that helps... Regards, M.
[Moto G Android Development] Scranalot:
SOLVED

Hello Again MSe1969

Thanks for the swift response & I'm pleased to say that you have resolved the problem :).

Your second idea was the solution for me - I'm using NetGuard https://f-droid.org/en/packages/eu.faircode.netguard/ I turned it off & bingo tethered no problem USB & Wi-Fi. Now I had been using NetGuard whilst on Official LineageOS & I was tethering no problem so I have looked back into NetGuard & as listed in the 'Features' of the app "Tethering supported" & if you go to https://github.com/M66B/NetGuard/blob/master/FAQ.md

Section: (22) Can I tether (use the Android hotspot) / use Wi-Fi calling while using NetGuard?

I therefore presume I must have set this up whilst on Official LineageOS & since forgot! :o

My apologies for being a nuisance & my stupidity but I'm happily now sorted.

Regarding the first idea of your reply I would like to make it somewhat clearer what I did. I pulled my contacts, calllogs, calendar & messages databases over adb from the Official LineageOS (Feb release). I did an initial clean flash of your ROM (March release) with no-gapps/micro-g implemented, pushed my contacts, calllogs, calendar & messages databases over adb to the correct system directories, deleted the db-journals for each & it turned out to be a mess (I don't know if I should have copied over profiles too?). So I reverted back to my Official LineageOS (Nandroid backup ;)). I then reinstalled your ROM (March release) clean flash again with no-gapps/micro-g implemented & following the guidance from here: https://shadow53.com/android/no-gapps/setup-guide/3/

I installed the GoogleCalendarSyncAdapter.apk (as directed) & my pulled contacts, calllogs, & messages databases over adb. Calendar now showed fine but again contacts, calllogs, & messages failed to show names & other attributes, so I removed the contacts database, installed the GoogleContactsSyncAdapter.apk too then did a dirty flash reinstall of your ROM to reset the system & things worked fine.

I recommend looking at https://shadow53.com site - some very helpful stuff there.

So hope this is a better explanation & not more confusing lol :silly:

Thanks again for your assistance & your ROM MSe1969 :good:
[Moto G Android Development] ChrisRM:
April Security Bulletin?

What are your thoughts on the April Android Security Bulletin? Will you be rolling them into the ROM, or doing an update package of some kind?

Chris M
[Moto G Android Development] MSe1969:
Yes, I will. A new ROM version will be available, as in the previous months, but it'll still take a couple of days. As mentioned, the LineageOS community continues to update the cm-14.1 branch. Right now, Google has not yet updated the source code links in the ASB, which is a prerequisite to start working on it. Depending on how complex/difficult it is to back port the code changes, and whether testing goes smoothly, the update will be ready.

To the 2nd part of your question - it is always a full package, but as explained in the OP, you simply flash it without doing any wipe, so it's a simple update.
[Moto G Android Development] allrightlite:
It's good to have this rom. 7.1.2 is on many older decices the best choice. For example on old P8 Lite, S3 Mini, moto e4 and this phone for sure. Pie is better on newer phones, that's my opinion. So, it's cool that this is keep alive :o
[Moto G Android Development] MSe1969:
New build with April ASB patches

Hi all,

a new build with April ASB patches incorporated is available for download here:

https://www.androidfilehost.com/?fid=1395089523397936122

Regards, M.
[Moto G Android Development] ChrisRM:
Link not working well....

Having all sorts of 'fun' trying to get hold of this; Android File Host is setting off warnings from my browser security, and then not coming back with a working mirror...

---------- Post added at 03:07 PM ---------- Previous post was at 02:35 PM ----------

Android File Host finally succumbed and gave me the new version, which went on as described and just work. Nice!
[Moto G Android Development] JuanVCS:
All working well, thanks for another update.

Does anyone know if it's possible to run the stock Motorola FM Radio app? Can't even find it in the play store and can't install it thru aurora.
[Moto G Android Development] phpbb3:
Just popped back in to remind the developer that I am thankful for these builds... My device is repurposed and lives in my garage as a media and browsing device... Great to still have decent performance and latest security patches... YouTube with the latest non-Magisk Vanced mod works well, as does the Plex Media app and few other things I use... Excellent... I was using the microg prebuilt up until I started using Plex, then I did end up having to switch to GPS version for Plex app licensing to work, but even with GPS battery life is still better than my modern dd
[Moto G Android Development] PhillipJC:
Installed and running smooth with gapps.
[Moto G Android Development] ChrisRM:
How about this one? https://motorola-mobility-llc-fm-radio.en.aptoide.com/app
[Moto G Android Development] Untot:
[MENTION=7929484]MSe1969[/MENTION] thank you so much for keeping this relic alive!!!

The download link for standard version in first post refers to the latest microG build.

And the link the microG build refers to the may build
[Moto G Android Development] MSe1969:
Thanks for letting me know and sorry about that.

I'll fix that tomorrow night (have only mobile access right now and fixing an OP like that isn't a good idea)

EDIT: Download links in OP are fixed now.
[Moto G Android Development] JuanVCS:
That tries to install some "aptoide" app I don't feel comfortable with.

I can find the package thru aurora, it's just not installable under this rom (device not compatible) so I wonder if there's a way.
[Moto G Android Development] MSe1969:
New builds with July 2020 ASB patches

Hi all, new builds are up with Sec. string 2020-07-05 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

This build variant has in addition the following changes:

updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues

F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11

Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

Happy flashing!
[Moto G Android Development] peelie:
great work thanks!

got a question about building rom from source - seems rom cannot build with python3? is that right?
[Moto G Android Development] ChrisRM:
Still good...

Thanks for this, update found of variant B OTA. Not as smooth as usual, as it hung thrice; once on the TWIRP splash screen, once during the update script itself and then on the reboot. Each time, the power button was enough to remind it to continue. All good, finally, but slightly surprising...
[Moto G Android Development] MSe1969:
Funny... Have tested OTA on both my falcons yesterday and all went well. Which TWRP version are you on?

I have 3.2.1 on one and 3.3.0 on the other.

EDIT: Sorry 3.2.1-0 on both
[Moto G Android Development] ChrisRM:
TWRP 3.3.0.0; worth downgrading?
[Moto G Android Development] MSe1969:
Had to correct myself, 3.2.1-0 on both

Well, 3.2.1 was the current for N, 3.3 was made to cope with O and 3.3.1 with P, more or less. Don't know to what extent changes in higher releases have an impact on flashing builds on older devices and Android versions.

But yes, I'd give it a try, if you experience issues. And I on purpose didn't upgrade TWRP - never touch a running system (unless you need a feature of the higher version)
[Moto G Android Development] PhillipJC:
No problems encountered..... Thanks! Great ROM.. Upgraded with OTA. TWRP 3.3.1.
[Moto G Android Development] MSe1969:
Not aware of issues, could you pls. elaborate further?
[Moto G Android Development] peelie:
hi

that my build seems to stop quicker with errors when python3.6 is used compared to python2.7? (why the build won't continue with python2.7 is another matter!)

edit

looks like i messed up which python system used, sorted now, let's hope build proceeds!
[Moto G Android Development] peelie:
whay got a build : ) - but not attempted to test it yet

can i ask when do you usually repo sync and build? 8th of the month?

thx
[Moto G Android Development] MSe1969:
There is no fixed schedule. I look when the topic for ASB is up in review.lineages.org - and normally, I prepare for my builds as follows:

- first of all, repo sync (to get all "foreign" Repo's synched)

- then, check & bring my own forks up to date

- pick the ASB topic (and others, if applicable) from lineage gerrit

- pick the kernel fixes
[Moto G Android Development] Scranalot:
Yes same here & for the same reason - I had briefly updated my TWRP to v.3.3.0 some time ago but read on this thread a post by MSe1969 stating basically the same thing so I downgraded to v.3.2.1 - having said that I don't recall having any issue updating with either TWRP version.

Thanks for the latest updated release MSe1969 - again much appreciated :good:

---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------

You are aware that the android FM radio app is installed by default with this ROM ? :confused:
[Moto G Android Development] peelie:
thx so i followed your instructions here https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms to get my build, that is okay for future builds?
[Moto G Android Development] JuanVCS:
I am, it's just nowhere near as good as Motorola's. Notifications get on the way, don't seem to report the current station correctly, recording is prone to failing, and for some reason it adds a delay on the transmission when compared to every other FM radio device I own.
[Moto G Android Development] Tiki Thorsen:
Thank you for keeping this alive and updated!

I am happy to report that it installed successfully the A variant on my old and battered XT1032 (8GB) with the Pico package from the OpenGapps.

So far everything works great and is such a big difference from the bloated stock 5.1.

Note: As you mentioned, it failed to install with newer versions of TWRP othern than 3.2.1.0.
[Moto G Android Development] MSe1969:
As you are aware, there is a link further up in this thread pointing to Aptoide, provided to you by a fellow thread participant. I have no idea, whether the linked app there works OK on this build, you may want to give it a try and report back...?

Aptoide as such isn't that bad, but it depends on the specific repo, from which the app is offered, so watch the feedbacks and Aptiode's own rating symbol...
[Moto G Android Development] Scranalot:
No worries - I haven't actually used it - in fact I on switched it on briefly the other day before I posted to confirm that it works (which it did) - but I have no experience of prolonged usage so I cannot comment on what you state from my perspective.

For radio I use Transistor via F-Droid - smashing little app for me, allows me to listen to sport ;)

It is internet based so obviously requires data. The developer has just re-written Transistor from scratch in Kotlin for his v.4.0 release & it is causing a number of issues - indeed, for the time being, I have reverted back to v.3.2.4 which works fine for me :good:
[Moto G Android Development] MSe1969:
Yes, assuming you understand the ratio behind.

I have read my instructions again, and I think I should add the below to be clear for resynchronization and rebuilds:

*Before* doing a `repo sync` again for a new build,

- cd into the local_manifests directory and execute the command `git pull`

- execute the `patches_reverse.sh` script, if you have executed, as recommended, the `patches_apply.sh` script

*After* `repo sync` has been performed, execute the `patches_apply.sh` script again
[Moto G Android Development] JuanVCS:
I tried it, the download actually installed that aptoide app and I had to search the FM Radio there.

But then, the FM Radio installer failed with a "device not compatible" error (albeit in spanish, so that might not be the exact wording).
[Moto G Android Development] peelie:
ok thanks!
[Moto G Android Development] ChristianWS:
Pls help

So, I was using last month b Variant, I decided to flash the new one while making It a factory reset, but since I was going to reset anyway, i decided to see what was going on with a Android 10 Rom, i thought I was smart and made a backup before hand.

I flashed a Android 10 rom, decided i had my Fun, and went back to your ROM, i flashed the current version and discovered some bug where the wi-fi wouldn't turn on, It appears that the mac address was corrupted. Well, no problem, I can just restore right? Wrong, the backup has some issue and I can't restore correctly. Well, last time I flashed I did reset the phone, I picked last month version....and it didn't work, same issue. I even picked the A Variant.

I'm dealing with this **** since morning, i've tried replacing the file that holds the mac address, i tried dirt flashing, I tried downgrading TWRP, I tried a bunch of weird stuff and i don't know what to do.

The Android 10 rom Works, but only see my wi-fi It its on Channel 1, I don't want to use It as a daily driver due to lack of space to install Gapps or NanoDroid, some guy in the thread said to use WeebGapps on magisk, but its available on Telegram, which I currently don't have.

Please help
[Moto G Android Development] MSe1969:
When you say "backup has some issue" - does that mean TWRP complains already when attempting to restore the backup?

Further, did you also wipe the system partition for a clean flash? (Recommend to do so)

What happens, if you really clean flash my ROM, i.e. wipe system, data, cache & dalvik?

And - as a last resort - format data partition?
[Moto G Android Development] ChristianWS:
First of all, thank you. Now then:

TWRP complained almost at the end of the restore process, I tried booting, but it got stuck, I tried restoring and then wiping only Cache & Dalvik, didn't work, tried restoring then wiping Data, Cache & Dalvik, didn't work, tried restoring then Dirt flashing to current month B Variation, didn't work. Due to this, I deleted the backup. I suspect that TWRP rebooted while ending the backup process, It was finishing and I went to the bathroom, when I got back TWRP was on its main menu, at the time I didn't think much, but looking back now....

Before I changed ROMs I wiped System, Data, Cache & Dalvik, and I even wiped Cache & Dalvik afterwards just for good measure. I did this everythime i flashed a ROM. At some point I even wiped internal data.

If I'm not mistaken here's the route of what I did:

Wiped system, data, cache & Dalvik, flashed this ROM, TWRP threw a fit, realised it was because I wasn't on the latest TWRP, rewiped, flashed last month B Variant(I had the same I clean flashed last time), and Wifi didn't work, it couldn't turn on, Mac Address was set to 02:00:00:00:00.

Okay then, I upgraded TWRP to latest version, flashed the 17.1 ROM, discovered the wifi worked(but it only saw networks that are on channel 1), it worked, but I decided I'd rather go back to Nougat due to lack of Gapps. I've flashed current month B Variant and... wifi couldn't turn on. I went back and forth reflashing and wiping everything I could. I've found some mentions of the same problem, the solution was to replace a file in root/persist, I did it, but it didn't work.

Desperate I grabbed the flashable radio and flashed it, it didn't work, it was late, so I decided to at least use 17.1 for now.... except that now it doesn't work anymore, Wifi stopped working even on 17.1

I also flashed the lastest official firmware, but it didn't appear to work, I will keep trying using other firmware. The weird thing is: I didn't know you could mess this stuff across roms, I thought the whole problem with Android was that everything had to be included in a ROM, thus, when you wiped System there was nothing left to mess with the ROM.
[Moto G Android Development] MSe1969:
Hmmm . . . - following your description, either - something messy seems to have happened already during your 1st flash attempt (but normally, the way a ROM flashable ZIP is composed, only the /system and the /boot partition are flashed, other partitions aren't touched - so normally, you can't irreversably mess up a device) - or, coincidentially, the WiFi chip has decided to give up.

I think trying to flash a stock ROM, as you started already to do, would also be my approach (I can't however give any trustworthy recommendation, where to look) - important is to also use the respective flash method/tool, which comes along with the stock ROM.

Sorry, that I can't give you any better advice, but what you describe sounds really weird...
[Moto G Android Development] ChristianWS:
Wait, so.... are mac addresses stored in a partition that isn't supposed to be touched by ROMs? Cause I'm at a loss of what the heck happened here, I'm not the first one to have this issue happen(although I can't fix the same way as them, some things changed during Android versions, so their solution doesn't work here), and the problem seem to be with Mac Address getting corrupted, but since the problem is happening across multiple ROMs it means that Mac Address isn't changed when ROM's change, so what the heck

This is on the same level as "Cosmic Rays flipped the exact bit to make a glitch in Mario 64".

My phone is automatically rebooted everynight, if the chip was simply waiting for a reboot it is really unlikely it just died at the exact same moment I decided to Flash

I can't just flash a Stock Rom using TWRP?

Edit:

Flashed Stock Rom, Kernel, Kernel Fix and Radio using TWRP, none of it worked. Do I need to bother with ADB? It's a hassle and I'd rather not