yashsingh1/xdaforums huggingface dataset:
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
Do i need to flash stock rom every time i move to a different custom rom or can i just go straight to a different rom wo flashing stock first?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] bluesy_92:
Is there anything I need to update to go to Havoc 5.7? Vendors, radios, anything like that?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fddm:
You can just flash the new firmware.

None that you really need to, afaik. Still good to keep your radio up-to-date.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Unlocked and flashed the 2022-06-30 RETUS update. Booted into stock to provision the radios and check on visual voicemail (more about that below). I noticed the same behavior as before wrt the oem unlocking, otherwise didn't stay here long.

Then flashed a DIY unofficial build (updating the rollback index to 14 from 13). Booted fine so i went ahead and re-locked the bootloader. No issues - I was able to toggle the oem locking to allow (after locking the bootloader) as before.

Restored a backup via seedvault and went through a couple of hours of additional tweeks that seedvault misses (some of which I don't expect seedvault should backup like firefox, nextcloud, davx accounts, k9 email passwords, etc).

The FM radio is back! No need for me to apply hackish patches - thank you for that.

The (new to lineageos) moto camera seems to work well. Hedgecam2 filled a need, but I think I'll switch to the lineageos provided moto camera. Thank you for that.

I have visual voice mail without having to use my carriers bloatware app! For the longest time (years), I could not get visual voicemail working and so just lived without it. I'm not sure what brought it back. Some bug fixed in the updated stock rom radios? Bugs fixed in the updated blobs? As mentioned above, I did use visual voice mail on the stock rom with the thought that maybe something needs to be provisioned for it after updating the radio. Any event, it's nice to have the option to use it.

Very pleased atm. My thanks to those that made this possible.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
Instagram opening animation on lineageos is choppy on both 18.1 and 19.1, though shakeuptech said it was not. Can you comment on that?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Sorry, I don't use instagram. I do turn off blur (but just because I don't like it).

BTW wifi calling is working for me but I have not used it in the past. I'm not sure if you might need to "provision" that as well while on stock before installing lineageos tho. I did test it out on stock before my most recent lineageos update. I wonder if that is part of the reason I've got visual voicemail now.

@SyberHexen

Regarding using stock to provision kiev's radios, is it necessary to do this when roaming between carriers? (i.e. if i provision on TMobile, but then travel to an area serviced by ATT only (in this case I think TMobile customers use ATT's network as "roaming") will I lose service? What about changing sims to verizon (RETUS should work with verizon if I'm not mistaken) or traveling to Europe, Asia, etc? Will I need to reload stock to provision each time I change networks/sims?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
Oh but the thing is the retus version for me doesn't have WiFi calling (I'm on at&t) but if i flash the Canadian firmware WiFi calling works fine on stock.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Out of curiosity, have your tried flashing the most recent (6/30/2022) RETUS stock to upgrade the radios? Also, I believe the lineageos binary blobs are were updated from this RETUS version.

I have little experience and even less knowledge wrt "provisioning", wifi calling, when to update radios, and binary blobs (hence why I keep editing my prior post).
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
No I have not. Will probably try it when a new build for lineageos is out.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
See just how laggy that animation is? It is definitely broken. And settings also has that issue sometimes when opening the app.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] J_Woo:
@notmyrealhandle which LineageOS version are you using with the Moto camera in it? Online, Lineage OS latest official build for Kiev is still 18.1 from July 16. Lineage OS 19..1 build (unofficial) is from June 29 and does not have the Moto camera if I remember correctly from when I tried it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
I do my own builds of lineageos 18.1. The build I'm currently using is from 07/14/2022 and has com.motorolla.camera3 v 8.0.77.76. I did not add this my self, I believe this is the new default camera from inspecting this commit (and others associated with it).

I expect this is included in official builds starting with lineage-18.1-20220709-nightly-kiev-signed.zip
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] AviBharti35:
It might be there just did not catch my eye. Glad it was resolved with the app update.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] J_Woo:
Cool. Last question. Getting GAPPS to load nicely with Lineage OS seems to be finicky. Which GAPPS are you using?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
No. The app update did not fix it either. Its still present.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
I have been gapps free for more than 5 years. I just recently started playing with microg, but this is simply personal interest - I currently have no use for it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] J_Woo:
MicroG does not have the Google Play Store. So how does one accommodate the many apps we use, such as banking or shopping apps?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fddm:
Use Google Play, an alternative gplay client like Aurora Store, or an alternative app market. The Google Play Store works well with MicroG.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
Anyone else facing a one second delay after pressing the power button or using the fingerprint scanner to unlock the device or to check the lock screen? Like the display turns on at least one second after pressing the power button or using the fingerprint scanner. If @SyberHexen fixes it then lineageos 18.1 will be my daily driver.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
Mine responds pretty much instantly, no delay here.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
What version/ build date are you on? All the recent ones have a delay.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
18.1-20220716-NIGHTLY-kiev
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
And what gapps are you using? Perhaps that affects the screen wake up delay when using fingerprint/ power button? Also i am pretty sure i tried that version and i still had an issue. Could you video tape it by any chance? Try to turn the screen on and turn it off and after like five seconds wake the screen up again w fingerprint/ power button and do that a couple of times so that it is consistent.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
well the only temporary solution is to have aod always on
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Latest lineage 18.1 updates as of 2022.08.10 apply cleanly for a "user" build and a locked bootloader.

Wth microg, It is possible to pass all safety net checks with

a patch to set ro.boot.verifiedbootstate=green (I did not try leaving this set at yellow),

a patch to set the build finger print to "motorola/kiev_retailu/kiev:11/RZKS31.Q3-45-16-8-3/018f4:user/release-keys" Note this string is from `fastboot getvar all` and is one character different than the current lineageos 18.1 default.

a patch to set the PLATFORM_SECURITY_PATCH to "2022-05-01"

In my case, the bootloader is locked and it is a user build so there is no need to reset those variables.

It may be possible to use magisk to accomplish the same thing with an unlocked bootloader and userdebug build. I no longer use magisk and I have not attempted this.

I did try ih8sn; however, this did not work with a "user" build as ih8sn seems to depend on the su binary being present from a userdebug build. For compiling your own "unofficial" builds, I suspect ih8sn would work for a userdebug build, an unlocked bootloader, and the appropriate variables set via ih8sn. I have not verfied that this works.

Using microg, I can include the android auto stub app plus the required permissions (described here). This builds without error, Android auto seems to run fine, but my limited testing (using a rental vehicle - I don't own a vehicle that supports android auto) did not succeed. I was not using my vendor supplied device usb cable for this test. Based on testing with an iphone and a non standard apple usb cable (which also did not work until the offical apple cable was used), it's possible the failure is due to the cable. Android auto seemed to recognize it had been connected to the vehicle, but the vehicle (a recent honda) refused to connect. I tried both using the "gapp" stub app and the full google app, google maps was installed and functioning.

Since I don't need micro g, safety net, or android auto, the above testing with microg was "just for fun."
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] smartasiankid:
@SyberHexen once android 13 source code is released could you please work on pe+ android 13? appreciate it
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] zigxda:
I just upgraded my "kiev" from LineageOS 18.1 (Android 11) to 19.1 (Android 12) and it seems to have gone successfully with no trouble.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] moslondon:
Can this rom be installed on north American version?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] zigxda:
I used it successfully on the North American (US) version.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] moslondon:
I am tempted to buy this phone now that is at especial price $210 but, it seems it has been abandoned, no more updates from motorola and i don't see any thread about android 12 here xda.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] xStealth:
Perhaps try joining the Telegram channel? Much A12 things can be found there.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] zigxda:
I'm running LineageOS 19.1 on it, which is Android 12. I upgraded from LineageOS 18.1 (Android 11) with the first release on 20 Aug 2022. Today, I again upgraded to the 03 Sep 2022 build. I've had no problems.

https://download.lineageos.org/kiev

BestBuy has it in stock at many brick-and-mortar stores for $210 with or without activation.

https://www.bestbuy.com/site/motoro...memory-frosted-silver/6441181.p?skuId=6441181

I have been very happy with this device for several months under both versions of LineageOS.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] moslondon:
I think I'll give this device a chance.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] moslondon:
Good to know that. Are all cameras working? VoLTE? 5G? I am with A&TT
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] zigxda:
Cameras work.

I'm on Verizon. VoLTE works. When I get 5G coverage, it works.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] RETIEF:
On AT&T, you will not get 5g if you unlock the bootloader. This is AT&T madness. Your phone will be restr from 5g at the towers. Otherwise, everything works.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] moslondon:
Thanks for clarifying that. I just cancelled my order.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Randy3011:
What GAPPS did you use and please provide a link. Thanks.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Randy3011:
Never mind found NIKGapps. Installed without problem. Everything appears to be running fine. Thankis anyway.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
Has anyone used Android Auto on a car screen successfully with either Lineage 18 or 19.1? I've made sure my kiev worked with my car and USB cables using original OEM Comcast ROM and TMO ROM from https://mirrors.lolinet.com/firmware/motorola/kiev/official/ before I attempt LineageOS. Both Comcast and TMO roms flashed via fastboot just fine and AA worked on both with my car and USB cables.

But I followed the LineageOS guide for flashing 19.1 and 18 onto my phone and everything works except AA projection onto my car screen. When I plugin the phone, the phone shows a "Android Auto connected" notification, but my car says no compatible phones are connected.

I have tried flashing 19.1 with MindTheGApps, OpenGApps (pico upto mini) and NikGApps (core to full) with no success with AA on car screen. I even flashed LineageOS 18 w/MindTheGApps and get same error.

Can anyone confirm if they got AA working on a car screen with either LineageOS 18 or 19.1?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
I tried with microg (using the AA stub from MindtheGApps) and got the same symptoms as you describe. Until I read your post, I had thought it might be the cable that caused my issue. I have not retested since my last attempt described above.

One thing I did observe is that the usb connection permissions were difficult to get correct. Eventually, I got the device to allow the vehicle (file transfer I think) but it took a few attempts. One thing that came to mind reading your post is to try removing the sdcard (if you have one in the device) and then try again.

Otherwise, you'll have to get a logcat and start looking through them for clues.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
I tried your recommendation and it yielded weird results. I couldn't change the USB connection type from anything but the default "USB controlled by 'This Device'" and "Use USB for 'File Transfer'". For "Use USB for..." if I select "USB tethering", "MIDI", "PTP", "or "No data transfer", the screen "crashes" and then comes back with "File Transfer" selected. For "USB controlled by..." if I select "Connected device" it doesn't crash the "USB" settings screen and instead fails with error "Couldn't switch" and reselects the "This device" for "USB controlled by..."

I think you're onto something with weird USB permissions in the LOS builds for Moto One 5G Ace (kiev). I think I may need to actually submit a bug report and this isn't user error on my part.

I tried grabbing a logcat on both a working OEM TMO ROM where AA worked on my car and a logcat when using LOS 18 (same Android 11 as the OEM TMO ROM) and am going through them to look for PII before I submit a bug report to LOS. I'm not a programmer so it's a lot of log files to go through for me.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
I had a thought about permissions and found this.

If you can pull the android auto (AA) granted permissions from kiev running stock (after validating that AA is working on stock), i.e. via adb:

adb shell dumpsys package com.google.android.projection.gearhead

then you could compare that to the AA granted permissions on your lineageos 18.1 build to see if they are different. While your at it, do the same for the google assistant app (I think the package name is com.google.android.googlequicksearchbox) as the failure might be lack of permissions with that app.

You also might want to grab permissions for these apps (from stock) with and with out the external sdcard inserted.

I'd be looking for a granted permission related to the external sdcard from a working AA stock permissions just because I've experienced strange behavior related to external sdcards in the past (Google apparently does not support external sdcards well). Also I think the reports of AA working on devices running lineageos 18.1 do not have external sdcard capability. Perhaps someone else can confirm or contradict that.

At a minimum, comparing permissions might help eliminate a lack of permission(s) as a cause.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
I've also been unable to get AA working on my phone. I have an aftermarket head unit running Android, with an AA adapter, but it keeps telling me to connect my phone, and the AA notification on my phone keeps popping in and out. So, doesn't really help you, but at least this doesn't appear to be an issue with your phone specifically.

I'm still running 18.1, I haven't had the time to update to 19 yet. I've also debated installing Havok and seeing if it works on that, but also haven't had time.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] :
Trying Havok is a good idea. I think Havok (based on android 11) comes with gapps/AA already installed. I'd actually be surprised if it did not work there.

A kiev user also asked on the lineageos redit about AA. WRT lineageos 19, AA is not supported as google apparently migrated the AA function into the google assistant app. I don't have a need for AA, do not want google assistant, and can't easily test, so I'm not going to be much help. Good luck.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
Regarding AA in 12, they didn't remove the AA function overall, it should still work in cars as it did before. The change in 12 is that you can no longer run the AA interface on your phone, that interface is now built into Google Assistant.

I saw one comment about going into Settings -> Privacy -> Trust, apparently there was a bug that didn't set a permission for connecting USB devices until that page was viewed, it has supposedly recently been patched. I've done that and will give mine a try tomorrow to see if it fixes it. There are a couple spots that also reference giving something the Phone permissions, but Im not finding concrete steps on what needs that permission or how to do it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
OK, tried the Privacy -> Trust this morning, still not working.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] PatrickJK:
I was told on telegram in the one 5g ace chat that AA has never worked properly on kiev with custom roms. Something about a Bluetooth issue I think
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
EDIT2: okay, looks like PDF files are okay, so I attached those.

EDIT: hmm, looks like I couldn't attach .html or .diff files. Perhaps because I'm too new a member. I'd use pastebin but the diffs are Winmerge .html reports that make it easier to see the differences.

@notmyrealhandle That poster in reddit was likely me, I made sure to use the same username to avoid confusion. Different people visit the reddit and xda.

@meisanerd I'm going to try that Trust setting anyways. Maybe I'll get lucky. 🤷‍♂️

@PatrickJK I'll tripple check to see if bluetooth is turned on automatically with AA in LOS when I plug the phone in and get the AA notification on the phone. When just using bluetooth audio alone w/o AA working, bluetooth worked right away in LOS 18 & 19 and I could get google assistant to respond to me via the car speakers. I really hope the devs didn't giveup on AA on kiev.

I have not had enough time to go through the logcat yet, but did manage to pull all the permissions for all apps on kiev. Attached is a Winmerge listing (diffs.html) of the apps with different permissions, some are just present on lineage, some are just present on tmo stock ROM. Most differences are trivial with a hex line ID (either a time stamp or thread ID?) but there are some differences between the TMO (left) and LOS18 (right). I didn't want to upload the logcat or dumpsys without checking for personal info in them either.

I also attached the detailed diff of just the `com.google.android.projection.gearhead` app. Notable differences are:

dumpsys_com.google.android.projection.gearhead.txt

missing from lineage in 2 places:

Spoiler content hidden.

lineage replaces "AndroidAutoStub" with "AndroidAutoStubPrebuilt":

Spoiler content hidden.

lineage change "2008-12-31 16:00:00" to "1970-01-13 01:11:13" in:

Spoiler content hidden.

most of these are missing from lineage:

Spoiler content hidden.

All except the READ_PHONE_STATE below are false in lineage:

Spoiler content hidden.

Most of the below are missing from lineage:

Spoiler content hidden.

missing from lineage:

Spoiler content hidden.

Most of below is missing in lineage, and lineage uses "AndroidAutoStubPrebuilt.apk - 230" instead of below:

Spoiler content hidden.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
FYI, tried Havoc and still same problem: AA notification appears on phone but car head unit never triggers. I think I'm going to try an unofficial PE build next, just gotta figure out how to flash the `.img` file. I think that requires fastboot flashing vice zip file flashing via recovery.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
Discovered something interesting: if I use desktop-head-unit.exe from the Android SDK as a test car head unit (tired of running in/out to actual car), it appears AA works. The only difference being forwarding of ports via adb forward tcp:5277 tcp:5277, USB debugging ON, and enabling AA Developer Mode and manually starting the "Head Unit Server" in AA Developer Settings.

If I fail to start the Head Unit Server when testing with desktop-head-unit.exe, AA notification on the phone still appears but the desktop-head-unit.exe always shows a "Waiting for phone" message. Could the problem be an issue with LOS not starting the Head Unit Server when I plug my phone into my car? The behavior from the phone looks almost identical as if the Head Unit Server failed to start.

Based on this minor success, I tried combos of USB debugging on/off, Start/Stop Head Unit Server on my actual car with no success.

I have also flashed different ROMs such as Pixel Experience (regular and Plus) and phh's AOSP ROMs with no success either.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] meisanerd:
If it is indeed a bluetooth stack issue, that would explain why it works on your desktop, but not on your device. As I am guessing the adb port forwards are probably sending the wireless communications over the usb cable for the emulated setup, which bypasses the bluetooth stack and thus wouldn't be affected by issues in that.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] ema.002:
Anyone able to update LineageOS 19.1 beyond September 3, 2022 update? Tried 19.1 updating from September 3, 2022 to September 10 through October 1, 2022 they all fail at Lineage splash screen after update and reverts and boots to September 3rd one. Tried through online LineageOS 19.1 and also thru adb with no success. The update_engine has errors with "[ERROR:snapshot_stub.cpp(163)] UnmapAllSnapshots should never be called.". If anyone is able to update kieve with LineaseOS 19.1 beyond September 3, 2022 update help is appreciated. Thanks!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
I ran into the same issue. I think there's an issue with Sept 3rd which was the original ROM I started flashing onto kiev. When I attempted to update to Sept 10th, it failed on reboot and switched to the other slot to boot Sept 3rd version. So I flashed older Aug version and then from there let the system update to Sept 10th and it worked.

NOTE: I did flash an OEM ROM from lolinet mirror after this so it might've fixed things (doubt it).

Recently, due to troubleshooting Android Auto, I had always made sure to flash the 2nd newest ROM followed by testing an upgrade. So as of right now, I flashed Sept 24th and let it upgrade to Oct 1st. This is to catch any other update issues like I (and you) experienced with Sept 3rd ROM.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] LunchStrong5016:
I'm leaning towards it not being a bluetooth issue based on a new workaround I found. From my open gitlab issue ticket:

I wonder if this

skip_frx

property can be baked into LOS in future builds so they can work with GM head units. Unsure if this will negatively affect other brands of head units, though.