[ROM][10.0][FALCON] LineageOS 17.0 [UNOFFICIAL][10/12/2019]

[SirRGB]

Try Magisk hide option to pass safetynet.

 

[moto2020]

Try Magisk hide option to pass safetynet.

Thanks for the quick reply. After installing MagiskManager I always perform two actions:
- turn on magisk hide
- Hide the magisk manager

Did I miss any other steps?

 

[ps_minky16]

New update available.

 

[nikos123211]

New update available.

Hello and thanks for supporting the falcon. But can you create a thread instead of posting your rom in other threads as a reply? I can't get notified when a new update is available.

Thanks, the rom runs great!

 

[moto2020]

Everything was fine and working well until I played with the magisk module "Props Config". I changed the fingerprint to a certified fingerprint to enable device simulation(moto G7 power android10 and moto g7 play android10) and tried safetynet check. The test failed and the torch flashlight no longer worked.

I wiped the cache, dalvik cache, system, data, internal storage from "TWRP3.4" recovery and flashed "lineage-17.1-20200813-UNOFFICIAL-falcon.zip" , "Magisk-v21.0.zip" and installed the "MagiskManager-v8.0.2.apk" and "MagiskWeebGApps-arm-arm64-10.0-4.0.1.zip" module. The safetynet test fails and the torch flashlight does not turn on.

I turned on the torch in mobile and executed the following command:

# cat /sys/class/leds/led:flash_torch/brightness
180
# cat /sys/class/leds/led:flash_torch/led_mode
/system/bin/sh: cat: /sys/class/leds/led:flash_torch/led_mode: I/O error

To get the torch working I even flashed the stock ROM "Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC". Everything installed fine but the torch didn't work.

My question is did I fry my torch/flashlight by enabling and choosing device simulation in MagiskHide Props Config. Why does the safetynet test fails even after a clean flash?

Can someone point me in the direction to fix the safetynet test and the possibly the torch. Any help is very much appreciated.

Switching on the phone without any sim fixed the flash. Could someone(with no safetynet issue) share the output of command:

# getprop

 

[ps_minky16]

Hello and thanks for supporting the falcon. But can you create a thread instead of posting your rom in other threads as a reply? I can't get notified when a new update is available.

Thanks, the rom runs great!

Join telegram. I usually post there first for testing purpose

 

[lipe_riba]

Hi guys,

Android Q dropped Miracast.
Can i use Google Home for this device Moto G 1st Gen.?
My TV is Samsung.
I tried but no success. What am i doind wrong?

 

[ps_minky16]

Hi guys,

Android Q dropped Miracast.
Can i use Google Home for this device Moto G 1st Gen.?
My TV is Samsung.
I tried but no success. What am i doind wrong?

It should work. Never tried it myself tbh.

 

[mubasshir330]

ps minky what is the telegram link?

 

[sahu.dipak]

ps minky what is the telegram link?

This one - t.me/MotorolaG Hope this helps.

 

[Finn1sher]

Download link broken

The drive link for the build is currently not working!
Perhaps you could reply to me when it's fixed! thanks

I did not expect to find a LineageOS 17 build for a phone this old! ?

 

[ps_minky16]

The drive link for the build is currently not working!
Perhaps you could reply to me when it's fixed! thanks

I did not expect to find a LineageOS 17 build for a phone this old! ?

You can find the builds at : https://mega.nz/folder/ys9gjQAA#XwppIsvLOiH-ftOGWzT04g

 

[karzyook24]

You can find the builds at

Thanks to you and everybody bringing that OS for that smartphone!

Used lineage os 14 - 17 for that moto g and while 14 was good and stable 15 & 16 have quite a lot of problems and random crashes.
Your 17.1 build is working - compared to 16 - very smooth, drains battery a lot less, way more apps are working or do not crash (or at least less often).

There are two problems I found. The first one concerns me personally more.
1) It is this one, which started with Lineage OS 15 and was fixed in a later firefox build and lineage OS 16. github com/mozilla-mobile/fenix/issues/14276
I'm restricted to post links < 10 forums posts, so please put a dot between the "com".
Strangely, it was not fixed 100 %, since I got it a few times with lineage OS 16.

If a wireless connection is established and firefox is started, it freezes upon crash (for 3 seconds or so) and then crashes the whole smartphone and forces a restart.
Newly restarted, if firefox is opened again (with wireless connection still established), it crashed again. And so on ...
There is only one solution I know github com/mozilla-mobile/fenix/issues/5663#issuecomment-565421772
Airplane-mode, which means cannot use it at all.

So basically it works with Lineage OS 16 & 17, but now, with firefox updated to the new quantum version, it started to crash again on OS 16 & 17.
It crashes with every firefox quantum version.
I can provide some crash-logs if needed.

2)
Live Display -> Color temperature, which is found in in display settings.
In Lineage OS 16 the Display mode can be changed from "Automatic/Off/Day/Night" and the settings will apply. Now with 17.1 nothing changes.
Color temperature is shown greyed out "Day: 6500K Night: 4800K.
I was able to change color temperature manually regardless of Display mode.

Thanks! :good:

 

[mubasshir330]

Hey rom's great very smooth and everything works great. Any idea of how to fix rectangle boxes for texts in some languages like bengali

 

[-ahtiang-]

Wow, its been years since I last look at my XT1033 and last OS I flash onto it was Lineage OS 14.1
I just found this thread and update it straight to Lineage OS 17.1
Let's see how it goes. This small little buddy is a heavy duty phone which still surviving to-date

 

[Jabba_the_hut]

The 20201025 ROM works really smoothly on my Moto G. I know there are alternatives but has anyone tried squeezing Open GApps onto their device using a gapps config file to remove/omit installing unwanted components? I've tried this using the following in gapps-config.txt, but unfortunately my device boot loops. I've been pouring over logs in open_gapps_debug_logs.tar.gz and Dmesg output, trying to make sense of it...

# Uncomment 'Test' to do a dry-run
# 'Overrride' allows us to remove apps like MMS (Stock SMS app) and WebViewStock 
# Test
Override

# These are mostly apps from the Pico package I don't want
# Removing WebViewStock saves 124928!
CalSync
cmaudiofx
GoogleTTS
packageinstallerstock
phototable
printservicestock
terminal
SimToolKit
WebViewStock

 

[zxcvbnm99]

Hey rom's great very smooth and everything works great. Any idea of how to fix rectangle boxes for texts in some languages like bengali

i too see this issue for languages other than english, even though the non-english languages are installed.

 

[zxcvbnm99]

You can find the builds at : https://mega.nz/folder/ys9gjQAA#XwppIsvLOiH-ftOGWzT04g

Thank you @ps_minky16 for continuing to provide LoS 17.1 builds. Would you be kind enough to post instructions (or point to any existing) on how to build a version of LoS ourselves, using which manifests, which branch(es) of LOS to use, a bare minimal working version and then adding/removing components, backporting/adding security patches etc. Appreciate your efforts. TIA.

 

[moto2020]

Everything was fine and working well until I played with the magisk module "Props Config". I changed the fingerprint to a certified fingerprint to enable device simulation(moto G7 power android10 and moto g7 play android10) and tried safetynet check. The test failed and the torch flashlight no longer worked.

I wiped the cache, dalvik cache, system, data, internal storage from "TWRP3.4" recovery and flashed "lineage-17.1-20200813-UNOFFICIAL-falcon.zip" , "Magisk-v21.0.zip" and installed the "MagiskManager-v8.0.2.apk" and "MagiskWeebGApps-arm-arm64-10.0-4.0.1.zip" module. The safetynet test fails and the torch flashlight does not turn on.

I turned on the torch in mobile and executed the following command:

# cat /sys/class/leds/led:flash_torch/brightness
180
# cat /sys/class/leds/led:flash_torch/led_mode
/system/bin/sh: cat: /sys/class/leds/led:flash_torch/led_mode: I/O error

To get the torch working I even flashed the stock ROM "Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC". Everything installed fine but the torch didn't work.

My question is did I fry my torch/flashlight by enabling and choosing device simulation in MagiskHide Props Config. Why does the safetynet test fails even after a clean flash?

Can someone point me in the direction to fix the safetynet test and the possibly the torch. Any help is very much appreciated.

Finally resolved it. Passed the safetynet test and google play service device certification.

Thanks ps_minky16 for this awesome build. You really changed the life of moto g falcon.

 

[moto2020]

i too see this issue for languages other than english, even though the non-english languages are installed.

I had the same issue and I applied this quick DIRTY fix.

1. Rename the respective local language font file to a corresponding Roboto font filename.
2. Replace the original Roboto font file in /system/fonts directory with your renamed local language font file.

For instance, if I want the phone to support bengali font and I pick "Hind Siliguri" font. All I need to do is:

1. Download the font family and extract it.
2. Rename HindSiliguri-Regular.ttf ----> Roboto-Regular.ttf
3. Rename HindSiliguri-Bold.ttf ----> Roboto-Bold.ttf
4. Replace the original Roboto-Regular.ttf and Roboto-Bold.ttf file in /system/fonts directory with the renamed font file.

IMPORTANT:
==========

Please note that the /system partition is always mounted read-only. So to push the renamed font files boot into recovery and mount the /system partition and move the files to /system/fonts.

P.S. - Roboto font have different font styles and I only replaced the regular and bold styles.