yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] MSe1969:
I am building LineageOS and your screenshot seems to come from RR. LineageOS also lets you customize many things, but yes, RR has many more options to play with in regards to customize the look & feel. It's known for many customizable options, and most of them aren't really trivial to implement.

So short answer: NO. (Neither have I the time/bandwidth nor - honestly - the true interest to work into that direction.)
[Moto G Android Development] MSe1969:
The methods, which are used for "root detection" by certain apps are various and different, and also is the philosophy and motivation behind originating from the app developers.

Some apps aim at determining whether the phone really is rooted (i.e. su binary is present and callable). In those cases, there should not be any issue using this ROM without root solution flashed.

In such cases, Magisk could also be helpful to hide itself from being detected.

However, some app manufacturers have something against custom ROMs in general, as they could potentially be rooted, which in case of a Custom ROM is fairly easy, as you need a custom recovery to be able to flash a custom ROM and with a custom recovery, you can flash anything and also access every part of the file system. It depends on how to define the term "phone is rooted": The narrow definition is the existence of the su binary, whilst the wider point of view would be "being able to gain full control and flash everything", which would include also the fact that a phone has a custom recovery and/or a custom ROM. Further, the build flavor "userdebug", which is the default flavor also for LineageOS and thus for this ROM, allows root via ADB, which can be allowed in the developer settings also when you don't have a root AddOn flashed.

LineageOS does not make any secret about being LineageOS and does not try to spoof to be a stock ROM, it also does not hide the fact that the build variant is "userdebug". So if the specific app simply refuses to run on a Custom ROM as such, or if e.g. Google's "Safetynet" does not pass (I don't know whether SN passes on this ROM, and honestly, I don't care), there is nothing, you can do about it - except for simply not using the specific app.

The question - next to the real personal need for such an app (there are many things, which can be done as well using an ordinary web browser) - would be, why the app does those controls:

My personal opinion: It seems legitimate to me, that the part of banking apps being used to trigger payments refuses to work on a rooted phone (many banking apps still accept root, if you use them for display-only purposes), as there seems to be some kind of certification standard to follow (even if this is technically spoken BS and in general, it is not safe to use any smartphone payment app for more than display-only). And okay, I understand that some streaming apps, which offer to save content on the parts of your phone, where you only have access with root, would like to prevent, that you grab this content (as their license model is streaming and not providing copies to you).

However, there are some extremely nosy apps of other categories (e.g. a famous dating app), which sometimes have more code to spy on you than code for the function, they are supposed to provide. The developers of those apps simply don't like the fact that Custom ROMs allow you to restrict their spying and questionable data collection. Such apps should be a No-Go . . .
[Moto G Android Development] MSe1969:
So far, I never had such issues - I am btw using TWRP 3.2.1, as newer versions basically had been developed to support higher Android versions, so I never had the urge to update TWRP, as all works fine for this device. So maybe even try TWRP 3.2.1 ? Otherwise, I would need some time (which I currently not really have) to re-test with my own test device (backup, format /data, clean flash, encrypt, restore), but this may take a while . . .
[Moto G Android Development] Bludwurst:
Unfortunately your suggestion didn't work.

Hopefully this'll be resolved... Someday.

I think I'll try clean-flashing, but IIRC encryption didn't work back when I first clean-flashed the ROM (...I just never got around reporting it until now, I guess).

Hopefully second time's the charm.
[Moto G Android Development] peelie:
oops sorry did not read our post correctly, ignore my comment link!

/edit/ this was supposed to be a replay to mhdasif899 comment , sorry the **** day re UK politics has done me head in!
[Moto G Android Development] Lordlight:
About Gallery

I think the Lineage gallery on nougat is very good but I find that it only can set wallpaper for both lockscreen and homescreen .

Can you add change the lockscreen only and change the homescreen only !

Thanks in advanced ! and sorry for my bad English !
[Moto G Android Development] MSe1969:
If you directly use the Gallery app, when you want to change the backgrounds, the describes behavior indeed applies.

However, if you use the "Backgrounds" app instead of the Gallery app, that feature works, and via the "Backgrounds" app, you are also able to select photos.

Hence, you get what you want: A different background picture/photo for your lock screen and your home screen.

In LineageOS 15.1, the Gallery app is not even offered, when you want to change the backgrounds, but only the backgrounds app. This means, that I won't even be able to find a commit in the Gallery app to "fix" its behavior. So the way, which I recommend, is to simply use the backgrounds app.
[Moto G Android Development] hib1000:
*EDIT*

Ignore me, sorted :)
[Moto G Android Development] Lindien51:
Brilliant! Thank you!

Thank you, MSe1969!

I needed to clean up and reactivate a Moto G that had been lying in a drawer for a while.

This has given it an entirely new lease of life!

Thank you so much for your work creating and maintaining this :D
[Moto G Android Development] Lordlight:
Is this a bug ?

My phone disconect to wifi suddenly and then auto reconect again many times when I conect to wifi from my Samsung phone ( glx A10) but this doesn't happen with router !
[Moto G Android Development] MSe1969:
You say, that if you use your Samsung as WiFi hotspot and connect your falcon to that hotspot, you experience disconnects, but if you connect your falcon to your router, all works fine, correct?

Without log, difficult to say. Maybe issue with your Samsung? Or check the Samsung's hotspot settings (e.g. other protocol).
[Moto G Android Development] Lordlight:
Here are some lines in my log file, please read it !
[Moto G Android Development] rintinfinn:
Hi, I just heard google will no longer provide security updates for android 7. Does this mean the end for this rom? I also read something about security backports from android 8. Will those provide enough security or is there still a huge risk, as android 7 specific bugs are no longer fixed? I really like this rom and it seems the most well thought out one I have found so far when it comes to security (with hardening and even kernel updates no one else seems to integrate). But missing support by google seems like a huge security danger to me.
[Moto G Android Development] MSe1969:
Short answer: Don't panic :)

Long answer:

Google does that already since the November ASB for 7.1 and stopped already last Summer for 7.0 and as you can see, the ASB patches for Nov and Dec have been delivered. In fact, Google usually only publishes so-called "tags" for their latest major versions, right now 10, 9, 8.1 and 8.0 - they did not publish a tag for Nougat since longer time! In those cases indeed, it is fairly easy to cherry-pick the respective patches directly. For lower versions, it was also before only publicly visible, which of those patches have also been applied to e.g. Nougat (7.1). Partners got the patches also from Google for those still supported versions (i.e. Google delivers to own devices still running on that version), but those weren't public and subject to NDAs.

So, when a lower android version isn't officially supported any longer by Google, there are in fact three consequences:

Indeed, the real patch info and code for those lower versions is not provided any longer to partners - but those aren't public and have to be back-ported anyhow

Indeed, patches, which would only apply to an older version, would not be shown any more, but in such rare cases, all you could see before was, that such an issue existed. But as no tag was published, the patch anyhow wasn't publicly available. Such cases were rare, but have happened. In other words - cases, which you anyhow could not fix, aren't shown any longer.

You don't see directly, if a patch applies to N or not in the bulletin, but once you look at the patch, it becomes obvious, so no issue: n/a or backport.

So, yes - theoretically, there could be unpatched issues. However - even modern phones with Stock ROM don't always receive updates in time, there are enough phones in the wild running on Stock Oreo and having months old patch levels... - this ROM, as all other ROMs here on XDA as well, is a "best effort" approach and as you mentioned yourself, kernel is being patches as well.
[Moto G Android Development] jaux1:
this is only for motorolas?

this roms is only works for motorolas?
[Moto G Android Development] thewhitewolf89:
Anyone has problem with ads, every 20 seconds i am getting ads (pop up by itself) on main screen, how can i stop this very annoying.
[Moto G Android Development] MSe1969:
This is definitely not related to the ROM, I guess you have installed some really ****ty app... (this junk can also be found on the Google play store, and not only on dubious apk sites...)
[Moto G Android Development] MSe1969:
Normally, each ROM is device-specific, and this one is only for the Moto G (2013)
[Moto G Android Development] jaux1:
ok thanks

jejeje bad luck for me jajaja
[Moto G Android Development] MSe1969:
I am doing LineageOS 14.1 builds for falcon, peregrine, osprey and gts210ltexx and LineageOS 15.1 builds for oneplus3 and amami (and very soon LineageOS 16.0 successors for the last two devices) - if you have a different device, you would need to either build yourself or find a good ROM here on XDA...
[Moto G Android Development] jemail:
Definitely not a problem with the ROM. I've been using MSe1969's ROMs on multiple Moto's pretty much since they were made available by MSe1969 with absolutely no problems.

I guess you have installed a suspect app.
[Moto G Android Development] ChrisRM:
A question; do you feel that 14.1 is as far as you would take the Falcon/Peregrine hardware? Or could a later version run as well as 14.1? I ask out of curiosity, not because 14.1 doesn't do what I want (thanks to your work)...
[Moto G Android Development] MSe1969:
I think 14.1 is "the end", if you are interested in a stable, reactive daily driver with a decent battery behaviour - that's my opinion.

Yes, there are builds here on xda with 15.1 and 16.0 (with permissive kernels and "mostly everything" working, so nothing to consider for a stable use).

I myself am not good at " bringing up" a device, so my opinion is maybe not that relevant, this is what I simply have observed.

Maybe some genius will manage to get a 16.0 build with "daily driver quality", but each new Android version usually has higher demands to the hardware - and the falcon/peregrine hasn't got the most powerful hardware - it was designed as low budget device and has indeed, if you look back to 2013, offered quite something for its price.

So I think even if there was a stable 15.1 or 16.0 build with strict SELinux and all features working, it would be slower and thus not worth to really switch.
[Moto G Android Development] MSe1969:
New builds with January 2020 ASB patches

Hi all,

new builds ready for download - they will soon also be offered via OTA update:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

ASB Security string 2020-01-05

Standard flavor only: System Webview on 79.0.3945.116

microG flavor only: Bromite Webview on 79.0.3945.107

microG flavor only: AuroraStore updated to 3.1.5

microG flavor only: AuroraServices updated to 1.0.5

Regards, M.
[Moto G Android Development] ChrisRM:
As Ryan Reynolds said in 'The Hitman's Bodyguard', "Boring is best.". OTA variant B just dropped in as usual.
[Moto G Android Development] Scranalot:
Happy 2020

Good Morning

And a belated Happy New Year to you MSe1969 & everyone else here in this thread :)

Your latest (January) release came through OTA & was duly installed without a hitch thank you MSe1969 - just a minor note for you though you have actually updated AuroraStore to 3.1.7 ;)

Initially there was an issue with AuroraStore for me it was sat there with 'No Network Connection' for quite a while then proceeded to 'loading Google API' before eventually fully opening & functioning OK :good:

In full agreement with both of those quotes & your efforts are certainly appreciated MSe1969

I wish you a Happy & prosperous 2020 :)
[Moto G Android Development] jemail:
A belated happy new year to you too?.

I agree. The hardware is what it is. I've had the "latest shiny" discussion on other threads. For me as I get older there are more demands on my time. If I have something that works reliably and fulfils my current requirements I see no benefit in changing it.

If it ain't broke don't fix it ?.
[Moto G Android Development] Coleby:
EDIT: Managed to solve my problem, I had to do a complete data cleanup and then reboot to do the usual (format cache, data, dalvik and system)
[Moto G Android Development] skizz98:
Encryption and latest TWRP

Problem:

TWRP 3.3.1-0 and 3.3.0-0 have problem with encryption (does not ask to decrypt and so you can't mount data and other things).

Fix:

Going back to the "official supported" version (aka 3.2.1-0 aka the one used by MSe1969) fix the problem.

Not a big deal but I wanted to report it nontheless to help others who might finds themselves in the same situation.

P.s. coming back from Android 9 and 10 and this rom with android 7 is simply the best option for Falcon at the moment. Thank you OP
[Moto G Android Development] seawoofer:
Hello, I try the variants A. Default LineageOS 14.1 with substratum and microG patch work well but i have battery drain compared to lineage-14.1-20190207-nightly-falcon-signed.zip.

10-15 % for hour with LineageOS 14.1 with substratum and microG

3% for hour with lineage-14.1-20190207-nightly-falcon-signed.zip.
[Moto G Android Development] MSe1969:
Thanks for your feedback - I have updated the install instructions to recommend version 3.2.1, as there have been similar reports already in this thread.

And thanks for the positive feedback.
[Moto G Android Development] MSe1969:
Thanks for reporting this. It is however difficult to really analyse this - I'd be interested on the opinion of other forum members using the ROM and also, whether this can somehow be pinned to a specific release, where it started? Also, this could also depend on the specific device setup and the installed apps - does the battery usage monitor indicate anything in particular?
[Moto G Android Development] seawoofer:
Hi, I started lineage-14.1-20200113-UNOFFICIAL-oms-falcon.zip with Gapps: open_gapps-arm-7.1-pico-20200114.zip.

and google restore my backup app.
[Moto G Android Development] ChrisRM:
I'm running the variant B, and I've noticed no major battery drain. The Moto G concerned is mostly a backup phone for personal use and so sits there not doing much, except checking personal emails.
[Moto G Android Development] ChristianWS:
I keep running into this weird bug where the Notifications, Quick Settings, Recents and Home Button stop working, a bunch of preferences are reset too, like the keyboard.

It doesnt matter which variant I use, the bug happened with both, and I don't know how to fix it, besides reflashing, but I dont really want to do that
[Moto G Android Development] MSe1969:
Not aware about such an issue. Can you somehow reproduce or even provide a log?
[Moto G Android Development] ChristianWS:
Already wiped my phone.

It appears to have something to do with the Profile being corrupted, I've found some users that had the same problems, and it seems like forcing the phone to redo the SetupWizard makes it fix the corrupted profile, however, the methods to force a redo doesn't seem to work because the SetupWizard is replaced by a custom one made for LineageOS(which is still called Cyanogenmod in the package name)

I think the last two times it happened after my phone rebooted when it's storage was full, so maybe the system is so full it messes up something with the profiles.

Idk, this only happened while I was using this ROM, maybe adding signature spoof screwed something that made sure the profile wasn't corrupted?
[Moto G Android Development] MSe1969:
Thanks for the feedback.

Yes, LineageOS 14.1 has an own SetupWizard, and yes, this one was developed, when the project still was CM, and after it has run, it is deactivated, so indeed, you can't easily "force a redo".

That sounds like an explanation, if the internal memory is full: The storage / Internal memory technically is part of the /data partition sharing the free space, and if it is full, the entire /data partition is full! So the Android OS can't write any more, that is definitely much more severe than it may appear on first sight!

If you look at the code and look, what is does, you will see, that signature spoofing has NO impact. The app willing to use has to bring the signature as a resource and you as phone owner have to manually grant the respective runtime permission (build variant A) or the app willing to use has to be a part of the OS being a privileged app signed with the platform key (build variant B). If these prerequisites aren't met, the flow in the Java code is exactly the same as if there was no signature spoofing patch present.

Why you had the issue, I still can't properly explain, but a completely full /data partition definitely is a recipe for trouble. Shouldn't there be a "memory almost full" alert before the crash, so you can still react?
[Moto G Android Development] ChristianWS:
I was just spitballing, since I don't recall seeing this issue in other roms, I thought it might have to do with something unique to this ROM in comparison to others I used.

See, both times I was downloading something big that I only needed to use once, I was going to delete it anyway, bug the bug always happens after a reboot. This time it happened overnight (I did set Tasker to reboot every night), the previous time this happened it was because my phone was getting hot (42°C), it's summer in the southern hemisphere, and my phone can get kinda hot, I just reboot it to try and see if it cools down a little.

Both times I basically ignored the warning because I was planning to fix the lack of storage after a reboot.

Thinking about, I think both times I was using an app to manage my downloads, maybe the app fills more than a browser would, which would explain why this didn't happen before.
[Moto G Android Development] MSe1969:
New builds with February ASB

Hi all,

new builds are ready and are already offered through the updater app as OTA update:

A. Default LineageOS 14.1 with substratum and microG patch

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

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

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

ASB Security string 2020-02-01

Standard flavor only: System Webview on 79.0.3945.136

microG flavor only: Bromite Webview on 79.0.3945.139

microG flavor only: AuroraStore updated to 3.1.8

Cheers, M.
[Moto G Android Development] ChrisRM:
As usual, just worked. The only difference between Falcon and Peregrine was that the Peregrine picked up that there was an OTA update, whilst I had to poke the Falcon to go look. Still just worked, mind you, so many thanks for continuing the work,

Chris M
[Moto G Android Development] methuselah:
Doing a great job mate. ?
[Moto G Android Development] MSe1969:
I uploaded the falcon file a little later than the peregrine one, also - the updater app can be configured in regards to the check for updates frequency... - Anyway, thanks for the feedback, it's important to get all kinds of feedback, that's the only way to get aware of potential (and real) issues.
[Moto G Android Development] seawoofer:
Hi, I try the version A. Default LineageOS 14.1 with substratum and microG patch

work very well, no battery drain, thank.
[Moto G Android Development] The-Saint2k:
Hello [MENTION=7929484]MSe1969[/MENTION]

I have two Moto G phones. One with option A and one with option B. On the mobile phone with variant B I cannot activate the network filtering in the APP "Netguard" under advanced options, this is not compatible. With variant A this is possible without problems. I suppose it will be due to the kernel adjustments. Are the kernel adjustments too strict or does the APP have a bug? Is it possible for you to adjust this or are the kernel adjustments not strict enough anymore?
[Moto G Android Development] MSe1969:
Hi, yes - the stricter sepolicy prevents any user app to access /proc/net - reason explained in the linked article. I see however that Netguard could be considered a legitimate use case. I could "whitelist" in my next build the F-Droid version of Netguard, if you want...
[Moto G Android Development] The-Saint2k:
Hi, yeah, that would be really phenomenal if you were Netguard Withlists. So I could continue to use variant B.

Thank you for the terrific work.
[Moto G Android Development] jemail:
Hi,

Do you build the nvidia shield tablet LineageOS ROMs here on xda?

If you are, I'd love it if you could add OMS support to your builds.

You'll find that MSe1969 has OMS support in his builds, which is fantastic and I can't thank him enough for graciously implementing it when asked if it was possible some time ago.

Many thanks to you both for keeping 2 pieces of good hardware secure and reliably usable as daily drivers.
[Moto G Android Development] MSe1969:
Hi, due to the fact, that the feature you're after is a "pro-feature", I can't test myself. I have created a test build here - please download and flash manually and tell me, whether it is working or not.

Please note, that as mentioned before, I used the F-Droid package signature of Netguard - this means:

NOT

the G* Playstore version!

Regards, M.
[Moto G Android Development] The-Saint2k:
Thanks a lot.

It works perfectly.

Are you accepting donations?

---------- Post added at 09:07 AM ---------- Previous post was at 09:01 AM ----------

Yes I am the one who published two builds for Shieldtablet. However, I am a newbie, I use docker image to create. ( I recently described some in the thread )

I would like to acquire the knowledge, but I lack the knowledge and the time to acquire the knowledge.
[Moto G Android Development] rintinfinn:
Hi,

I am having problems with the aurora store for the last 2 releases. When I open the app it loads and logs into the (fake) account. But the user interface is missing, there are no options to chose from or apps to install. Maybe something went wrong loading the api?
[Moto G Android Development] MSe1969:
I don't have any issues - but what you describe sounds familiar: Try logging off from the fake account and logon again using anonymous login, normally it will then work again.
[Moto G Android Development] rintinfinn:
Oh, right. What an easy solution... It's working again...