yashsingh1/xdaforums huggingface dataset:
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
New build android-9.0.0_r34

Build: https://androidfilehost.com/?fid=1395089523397910546

device:

cc79094 fp_c1212: fix delete of the zip file once patched

04bfd57 sanders: add surfaceflinger to pinner

26ccb94 sanders: enable BOARD_VENDOR_QCOM_LOC_PDK_FEATURE_SET

e9ff97e fp_c1212: print bootloader version to recovery UI

62b563b fp_c1212: keep in-line with N bootloader rootdir

677e807 fp_c1212: prevents merge of older folders into the zip

c5a6011 fp_c1212: correct zip file path

5c6a0f6 sanders: let the build system zip our files

006d9c1 patch_fingerprint: move checking and patching to our script

8091bdf sanders: GPS doesn't work for some devices with this turned on

1436df0 Revert "sanders: compile kernel with clang 6.0.2"

f1b79e4 Revert "sanders: init.qcom.rc: add eas changes"

dedfc07 sanders: include built in support for bootloader 0xC212

2145725 sanders: move wcnss_service to vendor

fc40910 sanders: build Trust and Livedisplay HALs

24408ed sanders: Added ISO_DEP_MAX_TRANSCEIVE value to libnfc config

a0744e2 sanders: init.qcom.rc: add eas changes

5814144 sanders: change default GPU power level to 6

7a80350 sanders: update power profile for P

c1cc632 sanders: reduce vm swappiness to rely on RAM more

9e3a6b8 sanders: fix makefile

e5f783e sanders: compile kernel with clang 6.0.2

vendor:

6504391 sanders: update GPS blobs from deen PPK29.68-16-8

kernel:

92e697730753 Linux 3.18.136

0be92054ad78 ax25: fix possible use-after-free

d3b6580acdbd mISDN: fix a race in dev_expire_timer()

5a587af110e6 net/x25: do not hold the cpu too long in x25_new_lci()

40497e60d49b kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)

b249460e1538 hwmon: (lm80) Fix missing unlock on error in set_fan_div()

346f8e72f1a4 net: ipv4: use a dedicated counter for icmp_v4 redirect packets

c1f808ef87e1 net: stmmac: Fix a race in EEE enable callback

c7b4ff7223db vsock: cope with memory allocation failure at socket creation time

79fed893bd28 vxlan: test dev->flags & IFF_UP before calling netif_rx()

cf7d3be51d89 tcp: clear icsk_backoff in tcp_write_queue_purge()

530e73cb47d9 tcp: tcp_v4_err() should be more careful

ea9557dca2b3 sky2: Increase D3 delay again

4234e6d76afb net: fix IPv6 prefix route residue
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
Fp not working after latest build. Fresh flash, tried fpa and fpb
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
I had the same issue, hence the clean flash
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] testeraphy:
by adding qemu.hw.mainkeys=1 to build.prop itll remove nav bar. Or, use other means (example, fluid navbar gestures, and disable it from settings) since IF you dont have any means to "back" (in case fp broke), you're pretty screwed up.

meaning? you have fp issue and it got fixed by clean flash?

or

you have fp issue too, then you suggest to clean flash everytime since it might not booting replying to my "encrypted" part?

in case you mean the second, then i do a clean flash since i cant get my pattern right. And i literally never do a clean flash until my device refuse to boot, which is, very rare in my experience. BUT DONT imitate what i do, im just being lazy, restoring everyting is killing my precious nap time.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
I had to do a clean flash because I couldn't decrypt. Neither in TWRP.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Hmm, that's odd can you get me the entire dmesg instead of the error logs. Did the fpshal start?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
Don't have m, all clean now
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] testeraphy:
Lets see if i can pull that w/o a pc [MENTION=5321417]MasterAwesome[/MENTION] hope this is good enough, https://www.dropbox.com/s/i39p0p6efoop4ia/liveboot.log?dl=0
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
This works.

4,1005,3824336,-;init: Parsing file /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.rc... 11,1006,3824400,-;init: Unable to read config file '/vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.rc': Skipping insecure file 11,1007,3824412,-;init: could not import file '/vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.rc'

Hmm seems like it's not initialising the fingerprint interface because of its permissions sigh another permission and context issue I believe. Can you stat that file and give me the output? Also as a temporary you can start the service given in the rc file manually through the terminal and it should work
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] testeraphy:
are.biometrics.fingerprint@2.1-service.rc
-rw-rw-r-- 1 root root u:object_r:unlabeled:s0 348 2019-03-09 17:43 /vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.rc

I don't know how to run rc but some chmod and chcon fix that. Thanks.

In case something comes up, how to run rc? for example is "start fps_hal" will do?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
I'd also like to know how to manually start the service.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Jagx:
The ROM is just awesome, thanks for the update, i hope it can be official
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Just a root terminal and ./*insert full path for biometric-service-binary* and you can force the system to run the HAL.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
sanders:/ # su ./vendor/etc/init/android.hardware.biometrics.fingerprint@2.1-service.rc

result: FP not working yet

then I tried:

sanders:/ # start fps_hal

result: FP not working yet

next try:

sanders:/ # am startservice fps_hal

Starting service: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=fps_hal }

Error: Not found; no service started.

result: FP not working yet
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Not the RC file execute the binary mentioned in the RC file
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] maosilva:
In this latest version (v7) has the fingerprint problem been corrected or do you still need to install the patch (FPb_sign.zip)?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] TheKicKer69:
Can u again give me the command for that? and do i flash the one u updated 20190309?

Tx Master

Update: flashed latest build. says WRONG PATTERN lol. under TWRP works fine. now i'm gonna CLEAN flash AGAIN :(

UPDATE2: ur last build has a MAJOR flow!!!! i CAN'T use the pattern! 7 more tries and my device will b WIPED.(pattern works fine in TWRP) reverting back to the previous build (can't even get into my fone lol)

UPDATE3: flashed Feb version fone working again (pattern that is)

UPDATE 4: setting fone up and BANG! asks me for FP+Pattern. i set 5 of my FPs like b4!!!!! now finishing apps and data restore. even though i flashed everything yet some traces of ur last update made my FP work (mind u i am using FEB ROM not March one and will never risk trying it yet again cuz 3 times said WRONG PATTERN even though pattern was correct ^^ ) hope when i get into my fone nothing else would b malfunctioning cuz prior to that only FP wasn't
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
I had a serious issue after dirty flashing the latest build and had to restore from backup. I have no idea what happened but at one point i couldn't get into recovery and thought my phone was bricked.

I would do a clean install. Im not sure if this was my fault or not but i didnt do anything different from the other times I've flashed the newest build

Edit : not my daily driver and had to leave home after putting it into restore so i can't provide anything additional atm.

So after the flash I was able to get in with limited functionality and went through the apps section and noticed some type of Android system keyboard that said it was disabled by default which I found strange as I had never saw it before. After restoring I double checked and there is no trace of that in the apps folder which there shouldn't be.

Is it possible that the ZIP I downloaded was corrupted? I'm sure I could replicate and provide more details but I'd rather not.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Wow a lot of weird bugs on this one. Let's hold using this build for now. I'm running that build and it works for me so maybe the upload is bugged out a little? Idk; either way I'll upload another one soon. Just to make sure you guys don't have any problem for the next update remove the pattern before updating unless you wanna get into /data and wipe the pattern keystore
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Akshayps:
Battery drain

Android system-2%

Mobile standby-4%

Android os-2%

Phone idle-1%

How to fix this!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
I really wish I could be more help and I've put a lot of thought into it trying to figure out if it was me. If I have some time tomorrow morning I may try this build again. I'm not going to rule out fault until then. If you're running stable then maybe it was me.

I've enjoyed LOS and all your previous builds. Overall things have been great.

Is there anything I could do or provide that would help?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Yep it works for me, as for the fingerprint it's a permission issue which will be fixed next build. I'll release it soon.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
New build android-9.0.0_r34

Build: https://www.androidfilehost.com/?fid=1395089523397911962

device:

5288d40 fp_c1212: label the new files since it doesn't get automatically set?!?!

f1a7c2b fp_c1212: rebuild biometric 64-bit HAL

88d7dd9 fp_c1212: make sure our unzipping rewrites existing files

cc79094 fp_c1212: fix delete of the zip file once patched

04bfd57 sanders: add surfaceflinger to pinner

26ccb94 sanders: enable BOARD_VENDOR_QCOM_LOC_PDK_FEATURE_SET

e9ff97e fp_c1212: print bootloader version to recovery UI

62b563b fp_c1212: keep in-line with N bootloader rootdir

677e807 fp_c1212: prevents merge of older folders into the zip

c5a6011 fp_c1212: correct zip file path

5c6a0f6 sanders: let the build system zip our files

006d9c1 patch_fingerprint: move checking and patching to our script

8091bdf sanders: GPS doesn't work for some devices with this turned on

1436df0 Revert "sanders: compile kernel with clang 6.0.2"

f1b79e4 Revert "sanders: init.qcom.rc: add eas changes"

dedfc07 sanders: include built in support for bootloader 0xC212

2145725 sanders: move wcnss_service to vendor

fc40910 sanders: build Trust and Livedisplay HALs

24408ed sanders: Added ISO_DEP_MAX_TRANSCEIVE value to libnfc config

a0744e2 sanders: init.qcom.rc: add eas changes

5814144 sanders: change default GPU power level to 6

vendor:

6504391 sanders: update GPS blobs from deen PPK29.68-16-8

kernel:

92e697730753 Linux 3.18.136

0be92054ad78 ax25: fix possible use-after-free

d3b6580acdbd mISDN: fix a race in dev_expire_timer()

5a587af110e6 net/x25: do not hold the cpu too long in x25_new_lci()

40497e60d49b kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)

b249460e1538 hwmon: (lm80) Fix missing unlock on error in set_fan_div()

346f8e72f1a4 net: ipv4: use a dedicated counter for icmp_v4 redirect packets

c1f808ef87e1 net: stmmac: Fix a race in EEE enable callback

c7b4ff7223db vsock: cope with memory allocation failure at socket creation time

79fed893bd28 vxlan: test dev->flags & IFF_UP before calling netif_rx()

cf7d3be51d89 tcp: clear icsk_backoff in tcp_write_queue_purge()

530e73cb47d9 tcp: tcp_v4_err() should be more careful

ea9557dca2b3 sky2: Increase D3 delay again

4234e6d76afb net: fix IPv6 prefix route residue
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
Yep, fingerprint works. Dirty flashed new build. First thing to do is to disable and re-enable the fingerprint in the moto actions settings, then it worked again. Thank you.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
woo thats great news. Dual firmware support lets go bois
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] TheKicKer69:
i cannot believe my FP is working that i'm scared to DEATH trying or upgrading to a newer build ^^
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
Woooo! Dirty flashed updated build without issue. All is running well.

edit: as I was flashing i realized that last night before my dirty flash instead of just wiping Dal/art cache that i may have wiped dal/art, data and possibly system without thinking. not really sure but it's a possibility. had a new born that was being very fussy, a hungry mother yelling at me to go get food and to stop playing with my damn phone. So who knows what happened. Prob my fault.

edit 2: my FP is still working fine and i have had no issues with it on any build. XT1803 hardware p4 if that helps

thanks sir
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
Bug: I have tinkered with my display settings. Played around with settings like Adaptive brightness and LiveDisplay. The current settings are: Adaptive brightness is turned on. LiveDisplay is disabled. The bug is that when I now lock my phone and unlock it, all colors are messed up. To fix it I have to go to LiveDisplay and change the colour profile from hal_adobe to for example hal_native (or any other setting). This makes the colors normal again. Will keep checking to see if I can make it more reproducable.

edit: changing to hal_native may have fixed the saturated display issue.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] mackikzy:
Dirty flashing works i had tested myself too. And finally network meter had fixed too. According to me everything works smooth. Except for selinux security weaken Problem. And one more thing is it only me or someone else has problem too auto sync option enable by itself even though i keep it off from setting it's really bugging me alot. Other than that i m all ok with this rom. Thanks Dev bro:good:

Ps: 1 more thing i think i lost my fast charging capabilities in this new build. Anyone else facing this problem???
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] schoebi_zh:
I bought this phone about a year ago and run another lineage oreo on it with microg.

Unfortunately that rom has not been updated since july.

Question:

1. How can I check my bootloader version?

2. Which one is necessary?

3. How do I have to update it?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
This rom supports all bootloaders currently available. You can just flash it
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Jagx:
No, i dont have problem with fast charging in this build :fingers-crossed:
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
I have no issues with fast charger either and haven't with any build.

One thing I've noticed is my notification led seems to be a lot more stable than past builds

Still no SElinux but Mr. Awesome has indicated in the past he is working on it

Edit: seems to be the most stable version yet and I've noticed that all around things seem snappier.

Very pleased
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] mackikzy:
Thanks ?

Yep you are right this is the most stable version so far now.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] housert:
Does vibrate only for calls work for you guys?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] saumyajit:
Please mention whats new in each updates from the previous one.

Thanks.

---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------

working
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] MasterAwesome:
Read the posts for when the updates come out.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] hmlwilliams:
I cannot use device encryption with the latest build, even after a full wipe and format of /data. Phone boots OK and setup can be run, but once set up opening the encryption menu and selecting Encrypt Phone sends the phone into a boot loop, which can only be fixed by another full wipe and format of /data. Has anyone got device encryption to work?

[EDIT] Just to clarify, when 'Encrypt Phone' is selected, the green android appears briefly as if encryption is beginning but then the phone shuts down and goes into an endless boot loop with the 'android' boot splash appearing each time. Phone is fully charged and plugged in when encryption is started.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
I feel like by asking this you are taking for granted the amount of time he puts in already and kind of rude.

For me personally I'm just thankful we have a person like him who is able to build this Rom for us so we can all enjoy it.

You can find what's new in each version by reading through the thread because he posts it when he releases. It might take a little effort to find sometimes but nothing compared to what the dev puts in I'll bet
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] DoctorStrange96:
Does DTV work with this build? Or any Pie ROM for that matter... I have a XT1802 (Brazilian variant) coming my way and I would like to know.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Uchiha Fabio:
No. It doesnt. I tried using and it crashes.

I would ask this too but the two times I tried to report bugs I got ignored. (I am not a dev, i am an enthusiast, i find bugs but i am unable to create a logcat)

So unless if they do answer me I wont report any more bugs.

I find this really rude.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] hmlwilliams:
Asking for a logcat can hardly be described as rude, they are generally pretty essential for fixing bugs. If the dev does not have a device with DTV capability and you provide no logs there is very little they can do. There a re plenty of guides available on how to create a logcat: https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Uchiha Fabio:
I am not calling that rude

I am calling being ignored rude.

And thanks for the link

---------- Post added at 02:46 PM ---------- Previous post was at 02:21 PM ----------

Right. Referring to DTV not working here are the logcat (first one ever made)

START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.motorola.dtv/.activity.main.MainActivity (has extras)} from uid 10209 Start proc 2906:com.motorola.dtv/u0a83 for activity com.motorola.dtv/.activity.main.MainActivity Start proc 2957:com.motorola.dtvservice/u0a73 for service com.motorola.dtvservice/.DTVService No permission grants found for com.motorola.dtv START u0 {cmp=com.motorola.dtv/.activity.main.AntennaWarningActivity} from uid 10083 Process: com.motorola.dtvservice, PID: 2957	at com.motorola.dtvservice.DTVService.<clinit>(DTVService.java:14) Process com.motorola.dtvservice (pid 2957) has died: fore BFGS Scheduling restart of crashed service com.motorola.dtvservice/.DTVService in 1000ms duplicate layer name: changing com.motorola.dtv/com.motorola.dtv.activity.main.AntennaWarningActivity to com.motorola.dtv/com.motorola.dtv.activity.main.AntennaWarningActivity#1 Displayed com.motorola.dtv/.activity.main.AntennaWarningActivity: +548ms Start proc 3032:com.motorola.dtvservice/u0a73 for service com.motorola.dtvservice/.DTVService Process: com.motorola.dtvservice, PID: 3032	at com.motorola.dtvservice.DTVService.<clinit>(DTVService.java:14) Showing crash dialog for package com.motorola.dtvservice u0 Killing 3032:com.motorola.dtvservice/u0a73 (adj 0): crash duplicate layer name: changing Surface(name=dcd51b0 Application Error: com.motorola.dtvservice)/@0x341dd99 - animation-leash to Surface(name=dcd51b0 Application Error: com.motorola.dtvservice)/@0x341dd99 - animation-leash#1 Attempting to destroy on removed layer: dcd51b0 Application Error: com.motorola.dtvservice#0 START u0 {cmp=com.motorola.dtv/.activity.scan.ScanActivity (has extras)} from uid 10083 Start proc 3112:com.motorola.dtvservice/u0a73 for service com.motorola.dtvservice/.DTVService Process: com.motorola.dtvservice, PID: 3112	at com.motorola.dtvservice.DTVService.<clinit>(DTVService.java:14) Showing crash dialog for package com.motorola.dtvservice u0 Attempting to set client state on removed layer: com.motorola.dtv/com.motorola.dtv.activity.main.AntennaWarningActivity#0 Attempting to destroy on removed layer: com.motorola.dtv/com.motorola.dtv.activity.main.AntennaWarningActivity#0 Killing 3112:com.motorola.dtvservice/u0a73 (adj 0): crash Attempting to destroy on removed layer: 450b6b8 Application Error: com.motorola.dtvservice#0 Killing 2906:com.motorola.dtv/u0a83 (adj 900): remove task Attempting to destroy on removed layer: AppWindowToken{d83a57d token=Token{7a6afd4 ActivityRecord{cd6a127 u0 com.motorola.dtv/.activity.scan.ScanActivity t39}}}#0
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Akshayps:
My WiFi speeds have dropped radically idk how!

But performance is good and battery fine too

One more thing is that colors get inverted automatically

Even when I don't touch display presets!!
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] DoctorStrange96:
Well then... :( Thanks anyway!

I checked both the device tree and the kernel sources, and all necessary DTV stuff seems to be in both. I can only take a better look at that when my phone arrives.
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] attackwap:
wow nice rom only use this rom NFC work perfect ,this first pie rom is NFC work with emoney card thanks [MENTION=5321417]MasterAwesome[/MENTION]
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] fealuin:
This looks like freezing
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Aryan Kedare:
[MENTION=5321417]MasterAwesome[/MENTION] is WFD working?
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] apratul Vasu:
Master awesome the ROM is awesome as your name suggests but one thing I've noticed that my device isn't certified on playstore, due to this I'm not able to download some apps, and there is a fix for it but it requires magisk and i don't want to use magisk only for that fix, my request is that please fix it in next update :o

---------- Post added at 03:53 PM ---------- Previous post was at 03:08 PM ----------

Another thing is that WFD or miracast isn't working , i can provide logs if you want
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Uchiha Fabio:
If you have magisk, enter on downloads and search for the module "device spoof 4 magisk" it changes your id and fingerprint so your device will be certified (now that i read your full post i realised you already know about that) oh well.......
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] Uchiha Fabio:
Here is a png of the ongoing bug
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] apratul Vasu:
Set colour profile in live display settings to native_hal and it'll be fixed

---------- Post added at 06:22 AM ---------- Previous post was at 06:20 AM ----------

It can't be captured in a screenshot

---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------

@MasterAwesome another issue is that ambient display doesn't trigger when i pickup my phone, it only triggers when i wave my hand over the phone or take it out of pocket
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] apratul Vasu:
I tried to change kernel in this ROM but it gave me bootloop and stock kernel having LED notification light issue, it doesn't blink at equal intervals...
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] 0ddj0b7:
[/COLOR]@MasterAwesome another issue is that ambient display doesn't trigger when i pickup my phone, it only triggers when i wave my hand over the phone or take it out of pocket[/QUOTE]

I have also experienced this for a few builds i believe
[Moto G5S Plus ROMs, Kernels, Recoveries, & Other D] QkiZMR:
Do you have name of this module?

Sent from Moto G (5S) Plus via Tapatalk