yashsingh1/xdaforums huggingface dataset:
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] User092741:
Good question, wondering the same thing. The stock camera doesn't work on the Nov 2021 build (at least on mine), and I've tried 7 different versions of GCam with various amounts of functionality, but all are buggy and none truly work properly.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RobEKu:
Anyone know how to get back the three button navigation? Gestures and three button navigation are gone, not in any setting, in the code, says package has zero bytes.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RollinCajun:
Has anyone gotten this to work on AT&T network? When I install my Sim card the network symbol at the top goes crazy. Shows that it's connected then disconnected and it does this over and over then crashes the whole phone and reboots. It won't let me stay in the phone for more then about 2 minutes and then it crashes. I've reflashed and still the same thing. I can take the SIM out and use the phone on wifi everything seems to be working so far. Just not on mobile network.

EDIT: it works for a few minutes on LTE then it tries to switich to 5G and it goes ape **** and starts disconnecting and connecting then eventually crashes the phone.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RollinCajun:
Search for Gestures under System Navigation you can search for either of those in your settings and it comes right up. I had no issues finding it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] User092741:
Anybody have the issue that calls can be made but there is no sound? Looked in build.prop for the persist.vendor.audio.fluence.voicecall=true line, but nothing like this exists.

Also, data is not working on the (US) AT&T network, I can get SMS but that's it. Any idea what might fix this? I had network set to "Global" but have tried different settings with no luck.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] cvcdrk:
Hello yes I have this exact same problem. After extensive research and screwing with my OS and the android system I have eliminated all other issues. it is absolutely the att network rejecting us. they have a few different "whitelist" published now and one has the 5g ace with an asterisk saying "will requite a software update to use HD voice calls" or something like that.

I believe that the Att network is rejecting the phone but I cannot figure out what they're asking for. its not the model code because I changed mine in build.prop and still nothing. like you I can get on LTE for a min before it starts freaking out. at this point I am out of options unless a genius here can figure out what att's network is asking for in the handshake.

Yes. I dont know what's causing it but I have this issue. it is fixed by turning on and off the speakerphone quickly. i experience this intermittently.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] User092741:
Thanks for the reply. Tried this and unfortunately didn't help. Getting to the point when I may just give up on Lineage 18.1. Too many things aren't functioning properly.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
I am having this issue with both your roms. I have tried everything I can think of. Wiping partitions, formatting data, full restoring latest android 11 stock firmware(multiple times), however I am still not able to install gapps. Every time I attempt to install gapps I get code 70(not enough space), I am able to mount system in the options however I do not get a "system" partition in the wipe partition selection. I have zero idea what I am doing wrong, I followed the instructions step by step. Please help, thanks!

Tdlr: Roms flash fine, gapps does not. Tried everything I can think of except full edl restore.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
@Articul8Madness​

Is this the issue?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fddm:
No. It says what you're trying to flash is simply too big. Try a smaller gapps bundle.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
I fixed the issue by flashing the android 10 firmware, it resized the system partion. Then I was able to flash the micro pack. Before that I could not flash even pico. I heard that the system partition can also be resized by flashing a really large gsi.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] baland3r:
I managed to install the ROM but because I don't have otg I couldn't root the phone. I sideloaded the Gapps but I can't sideloae the magisk.

I put magisk zip to SD card but I can't install it. Also the TWRP shows the internal storage 0.

How can I root the phone?! Maybe to extract three boot.img from the payload from the file lineage os? And install it from magisk app?!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fddm:
You'd put your recovery in sideload mode and send the file over usb with "adb sideload file.zip".
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] baland3r:
I had to RENAME the APK file to zip in order to work.....
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fddm:
Sorry, long day, I misread.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RobEKu:
My point was it wasn't there. I was removing a lot of Google packages via ADB and odds are that removed the buttons., when it shouldn't have but possible. Had to reinstall the code.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RobEKu:
Thank you for creating updated builds. But I am wanting to be able to use the updater or at least not reflash my phone which means i have to back up my data and apps and then reinstall them. I was about to update to the 3/22 ROM but wondering if I'm missing something and are there different instructions to update when the version is LineageOS 18.1, same build env. etc. ? Thanks so much for this, mine is working great!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
Great job on the rom! Will the official release be getting a new thread? https://wiki.lineageos.org/devices/kiev/
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] theburrus1:
According to this Link Lineage OS Official is ready for the Moto One 5G Ace. However, after clicking the link for the download I get this error. Can anyone provide an alternative mirror for download if such a place exist?? Syber Hexen? Is there truly an "Official Lineage build" ready?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
It will probably take up to a week for the official build to be generated.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] theburrus1:
Thanks for that info. I'll keep my eyes peeled then.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] peter go:
I should change the title of the topic, it's already official and I think the instructions are too to avoid confusion
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RobEKu:
I just installed the official nightly, 04.09.22, from lineageOS site and wiki for kiev and so far it's rock solid. I find I almost have to root my phone to get full backups, including messages and to restore everything. I never could get the unofficial twrp recovery really working for the official lineageOS kiev recovery works like a charm. So awesome, I can avoid amd bypass MetroPCS, T-mobile hotspot blocks, even though I have hotspot on my account. On both Mot and Samsung stock Rom, hotspot is blocked with unlocked devices. Using HedgeCam and it's GPL and really seems to correctly enable all of the quad camera features so far.

Very very happy, thank you, thank you,, thank you SyberHexen!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
@SyberHexen (and others who contributed to making this device "official"),

Thank you for your time and effort, It is much appreciated.

After inspecting bootloader.img from XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (which had been flashed to my bootloader unlocked device before lineageos) it looks like avb2 might be supported.

With lineage-18.1-20220409-nightly-kiev-signed.zip installed (works fine so far after almost a week), attempting

fastboot erase avb_custom_key
Erasing 'avb_custom_key' OKAY [ 0.009s]

works.

I also extracted the public key from the currently installed lineageos vbmeta.img (to output.img) and

fastboot flash avb_custom_key output.img
Sending 'avb_custom_key' (1 KB) OKAY [ 0.001s]
Writing 'avb_custom_key' OKAY [ 0.009s]
Finished. Total time: 0.011s

also works (I've rebooted the device into lineageos after this without issue - not surprising given I didn't expect the key to be checked).

I have NOT attempted relocking the bootloader yet nor do I plan to until I can get a device I'm comfortable experimenting on. However, I am curious if anyone else has tried relocking the bootloader with either the lineageos keys or their own keys using avb2 on this device.

Thanks again.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Apparently re-locking the bootloader with a custom os is not currently possible using the methods others have described for avb2.

I flashed the factory firmware and verified that I could re-lock the bootloader and have the device boot into the stock android 10 os.

Re-locking is much simpler than prior motorola devices I've used:

fastboot oem lock

and follow the on screen instructions will re-lock the bootloader and wipe data.

One can then unlock the bootloader after this (and again wipe your data) via

fastboot oem unlock

Note, during all the messing about I did, I was careful to validate that the "allow bootloader unlocking" toggle in the developer menu was always enabled. Thankfully this never changed.

Apparently after unlocking the bootloader for the first time using the code from motorolla, this code is not required again to unlock the bootloader.

From here and with the bootloader unlocked I tried flashing lineageos as usual (booting into twrp, sideload copy partitions, followed by sideload the latest lineageos image to slot b, slot a retained the stock firmware I believe). Reboot to verify lineage was working. Return to fastboot, erase avb_custom_key, and flash lineageos public keys to avb_custom_keys as described in my post above. I can then relock the bootloader from fastboot but lineageos will not boot. I get the red "No valid operating system ..." message and I have to hold the power key and vol down key for about 10 seconds to get back to fastboot.

I can unlock the bootloader after this and then boot into lineageos no problem (obviously all user data is wiped). I tried several variants of this including having lineageos on both the A and B parttions (attempting to boot from A). Nothing I tried got me past the "No valid os" screen. But I could always get back to fastboot, unlock the device, and boot into lineageos.

I'll try again if the device gets a stock motorola update to 12.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] nasdaq0:
hello friends, hello syberhexen, great work.

I was wondering about the 19.1 that runs quite nice on my device; the one i found on the unoffical androidhost site. Any information on it?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Fandroid Tech:
There is no official 19.1 release for this device yet, and it seems like syberhexen doesnt really update his threads often. You probably downloaded a generic gsi rom.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] foureightyi:
For those interested, I found a way to get the stock Camera working after a lot of trial and error thanks to a hint from this post in the Havoc thread. It's kinda hacky though and would definitely backup before trying.

I'm not sure it's worth it however as It seems to not work if Magisk is flashed to your system. The boot screen just hangs forever upon rebooting, forcing me to reflash the os. I don't know, maybe I'm missing something and someone more knowledgeable can find a cleaner solution, that allows for Magisk.

Anyways, it seems that placing /system/framework/com.motorola.motosignature.jar and /system/etc/permissions/com.motorola.motosignature.xml from the stock rom into the same locations on Lineage and rebooting, allows the motcam3 apk to install.

There is an annoying popup every time you open it complaining about needing an update for "Shot Optimization" but otherwise seems to work just as it's supposed to.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
I just booted into a lineageos 18.1 self signed user build on this device with the bootloader locked.

I spent a little time with avbtool inspecting the stock vbmeta.img and comparing to that produced by lineageos official builds and self signed builds (both userdebug and user builds). I made several changes to the BoardConfig.mk wrt AVB but i think the relevant addition is

BOARD_AVB_ROLLBACK_INDEX := 12

The value 12 comes from the stock vbmeta.img (also from XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip that i mentioned above) i.e.

python avbtool info_image --image vbmeta.img | grep Rollback
Rollback Index: 12

I also eliminated vbmeta_system.img in the build process (commenting out the relevant lines in BoardConfig.mk and editing the partition table in device.mk). I don't think this is necessary - I did it before I tried changing the rollback index in an attempt to make lineageos vbmeta.img files similar to the stock one. I still haven't figured out how to get sha256 hashs for the hashtree entries, something for later i guess.

Obviously, one still needs to

fastboot flash avb_custom_key releasekey-pkmd.bin

where releasekey-pkmd.bin comes form the keys you generate when doing your own self signed builds and when the bootloader is still unlocked.

I have a fair amount of testing I'm going to do yet before I start using a lineageos user build with a locked bootloader as a daily driver, but that is the plan. If I can build it myself, I don't need root. Also I want tamper detection enough to do my own builds for updates now on.

I don't want to add too much to the fud around re-locking your bootloader, but it is totally possible to brick your device doing this. For example, during my testing to get to this point, I was able revert to stock, flash the copy partitions zip, re-lock the bootloader, fastboot boot into my own self signed userdebug lineageos recover (i.e. the bootloader is locked and will work on stock - no lineageos, but my own key flashed to avb_custom_key), and then flash a stock lineageos image on slot b. The device would not boot with the bootloader locked; however, as soon as I unlocked it, it booted right into lineageos. Imagine doing this without the ability fastboot flashing unlock.

Anyway,

Happy bricking
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] dooshbagel:
Anyone else having issues with mobile data? It stopped working for me after a few days.

More details:

Mobile/cellular/LTE data stopped working on Motorola Moto G 5G (kiev) (#4636) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Mobile/cellular/LTE data should (and did) work. Current Behavior Mobile data...

gitlab.com
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] dooshbagel:
Same here, to add to my previous comment.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Is the lineageos fm radio app not outputing sound for anyone else?

The app runs, detects a headphone, tunes stations but I get no sound out of the headphone or phone speaker. I do get sound out the headphones and phone speaker otherwise so it is not volume or speaker issue.

I do see some errors wrt the fmradio via logcat and I can submit a bug report if one does not already exist. Just want to check if this is just me or others experience the same.

I am using my own "user" build (repo synced today) using the muppets if that matters.

EDIT: I won't be submitting a bug report anytime soon. Lineageos requests users not submit bug reports for "UNOFFICIAL" builds (which I'm using).

It looks like the FM2 app is not detecting the ro.vendor.fm.use_audio_session property. This prop is set to true, this can be seen in the image build.prop and, if from a root adb session using a userdebug build, one can see this is the case. However, from a non-root adb session, this prop is not "visible."

If I force mUseAudioSession in fmradio/FMRadioService.java to true (which is what ro.vendor.fm.use_audio_session is suppose to do), audio functions as expected for me. I spent some time trying to puzzel through the sepolicy setting api for props, but that will take some time.

Note, I can not contact the device devs via telegram. I've tried several times over the past couple of weeks to get access - no code is ever sent and telegram has yet to respond to email request for assistance.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Creeper36:
My Review After 1 Day:

Running Android 11 - Lineage OS 18.1 Unofficial Nightly

Just wanted to give you all my opinion. This is a very stable rom so far.. I just bought this phone today and had the bootloader unlocked, TWRP installed, this ROM with Gapps, and Magisk (both zip and apk).. all in about 2 hours. I have been ROMing for 10 years now and this was not that bad for someone with experience. I really didnt run into a problem. I have the stock firmware unbrick tool if I needed it. I did have to reflash my twrp after the initial rom install.. lineage has its own recovery which overwrites the twrp I wanted.. I just had to fastboot flash recovery to put the correct one on. Whats with this Slot A/B thing .. thats a strange concept that I need to select a Slot.. thats a new one. also the bootloader unlock code.. i have never had to enter an unlock code before for a bootloader but was easy to submit the request and my email came in 2 minutes.. this is a great rom with many more features than the stock firmware. I was able to switch the back and recents buttons to the older way with the back button on the right. I am testing GCam for a faster camera.. lineage stock camera has a little lag (after you press the button it takes a half second for the click sound and image preview to show). GCam is a little faster so far but I need to stress-test for stability.

enjoy this rom.. its got my approval.

EDIT: I attached my GCam config file. Everything is working.. all functions have been tested and no freezes or issues with instability. I will report back with issues.

= GCam likes Google Photos app to load the images from within GCam.

= I just snapped 50 pics one right after the other, non-stop, very fast beat.... there was lag but it was totally expected.. it did not freeze up and eventually caught up fine and would continue for a couple pics then lag again.. I would expect all this to happen and its stability was very good.

Battery Drain is 2% over 5 hours sitting on my desk with screen off on standby. Battery Drain is a little more than I like while using apps. This needs some battery management but its not that bad.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] baland3r:
how can i update to the latest version?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Skel40:
Update to the latest version here https://download.lineageos.org/kiev
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Droid4200:
Does anyone know if there is any way to get the network traffic activity speed monitor (the one that comes with LineageOS) off of the front facing camera? It makes most of the info not show up because its being displayed where the camera is. Other than that this is a pretty nice ROM. I had a G7 River that the cam was in a U shaped notch at the top and everything knew to display around it. Can that be done with Kiev?

Thank you
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
In the event you give up on the lineageos default camera app (I did), you may want to try the alternate camera app hedgecam2 v2.14b (hinted at by others elsewhere in this thread). I don't observe issues with the front camera bezel when using hedgecam2.

Also, I could not access the macro or wide angle camera's with the lineageos default camera app, but I can with hedgecam2.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Murderburger:
Tried out the new lineage on his directory seems to be working fine so far.. Android auto not working but I think there's a fix online.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] xStealth:
Sadly it would seem that FM radio still doesn't play sound even with the newest Lineage nightlies. Sad, it's the only thing keeping me from switching at this point.

I know a lot of people scoff at the need for FM radio, but I expect my device to be an all-in-one form of communication if worse comes to worse. That's why I tend to go with Motorola devices because many other companies are phasing out FM radios.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
This commit (not merged yet) might fix it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
There is also this proposed commit in gerrit: sm7250-common: Add gaurd to ipa based on bootloader build version..

Will users run into issues if the latest retus version (android 11) is flashed and then lineageos is installed (without the guard to ipa commit)?

nvmd - this looks specific to racer - my bad.

EDIT: FWIW I unlocked the bootloader (coming from lineageos), flashed:

XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip

and then booted into the retus android 11. This obviously wipes data. Boots fine, I didn't spend much time on it tho.

One concerning observation, the allow OEM unlock in developer options was grayed out and toggled to the "deny" position even tho the the text below it said the bootloader was unlocked. Note this option was in the green "allow" position before flashing the android 11 stock image. I am still able to use `fastboot flashing lock` despite this (more below).

Building a new "user" version of lineageos with the June security patches plus DIY patches that allow the bootloader to be relocked and enabling FM radio audio went without issue. Note that I updated the rollback index to 13 from 12 based on the stock android 11 image above.

After flashing copy-partitions, flashing the new lineageos image with the bootloader unlocked and booting into lineageos all went without issue. Allow OEM unlock is still grayed out, in the deny position, and indicating the bootloader is unlocked. Reboot to bootloader, lock the bootloader (wiping data again), and then rebooting into lineage went without issue. At this point, the allow OEM unlock is still in the deny position but at least I can (and did) toggle it to allow.

Seedvault restored apps and all the settings it can - this is still not the greatest backup option but it does save me some effort.

So far no issues running this way.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] mathew2214:
is this compatible with the XT2213-3 (Austin)? i diddnt see it in the supported models list. this is the thread for the Motorola Moto G 5G right?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] SyberHexen:
No this fourm is for the Kiev

Moto g 5g (2022) aka 'Austin' will have its own forum. But probably too new to have a home on xda yet..

On another note I would be surprised to see roms on that device as it has a mediatek processor.

Good luck!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] zigxda:
I have a Motorola One 5G Ace (non-UW) XT2113-2 "kiev" and a Motorola One 5G Ace UW XT2113-1 "kievv" both on Verizon.

The kiev is fully unlocked and working well on LineageOS 18.1-20220702-NIGHTLY-kiev.

The kievv, however, is apparently subsidy locked to Verizon and entering the necessary codes causes the Motorola web site to report that unlocking the bootloader is blocked. I bought the kievv outright and I assume eventually it will be possible to unlock the bootloader, but at that point will the kiev image work on the kievv also?

As I understand it, the only difference is that the kievv adds support for mmWave (n260/ n261) bands.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RETIEF:
The kiev cannot be bootloader unlocked to my understanding.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] SyberHexen:
Unfortunately Kievv can't be bootloader unlocked. Also if it was its got a different partition structure so the rom would not work anyways =/