[ROM]-[13]-[KIEV]-LineageOS-20-[OFFICIAL]

[zigxda]

Good to know that. Are all cameras working? VoLTE? 5G? I am with A&TT

Cameras work.

I'm on Verizon. VoLTE works. When I get 5G coverage, it works.

 

[RETIEF]

Good to know that. Are all cameras working? VoLTE? 5G? I am with A&TT

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.

 

[moslondon]

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.

Thanks for clarifying that. I just cancelled my order.

 

[Randy3011]

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

What GAPPS did you use and please provide a link. Thanks.

 

[Randy3011]

What GAPPS did you use and please provide a link. Thanks.

Never mind found NIKGapps. Installed without problem. Everything appears to be running fine. Thankis anyway.

 

[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?

 

[Deleted member 10134073]

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?

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.

 

[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.

 

[Deleted member 10134073]

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 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.

 

[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.

 

[Deleted member 10134073]

installing Havok and seeing if it works

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.

 

[meisanerd]

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.

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.

 

[meisanerd]

OK, tried the Privacy -> Trust this morning, still not working.

 

[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

 

[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

    User 0: ceDataInode=5258 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false
    overlay paths:
      /product/overlay/NavigationBarMode3Button/NavigationBarMode3ButtonOverlay.apk

lineage replaces "AndroidAutoStub" with "AndroidAutoStubPrebuilt":

Spoiler

  Package [com.google.android.projection.gearhead] (bacdaee):
    userId=10224
    sharedUser=SharedUserSetting{5478f33 com.google.android.projection.gearhead/10224}
    pkg=Package{561eb8f com.google.android.projection.gearhead}
    codePath=/product/priv-app/AndroidAutoStub
    resourcePath=/product/priv-app/AndroidAutoStub
    legacyNativeLibraryDir=/product/priv-app/AndroidAutoStub/lib

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

Spoiler

      android.test.base
    timeStamp=2008-12-31 16:00:00
    firstInstallTime=2008-12-31 16:00:00
    lastUpdateTime=2008-12-31 16:00:00
    signatures=PackageSignatures{ea08069 version:3, signatures:[159c4de5], past signatures:[]}
    installPermissionsFixed=false

most of these are missing from lineage:

Spoiler

Queries:
  system apps queryable: false
  queries via package name:
    com.google.android.projection.gearhead:
      com.google.android.apps.maps
    com.google.android.apps.maps:
      com.google.android.projection.gearhead
  queries via intent:
    com.motorola.actions:
      com.google.android.projection.gearhead
    com.motorola.gamemode:
      com.google.android.projection.gearhead
    com.android.vending:
      com.google.android.projection.gearhead
    com.motorola.appforecast:
      com.google.android.projection.gearhead
    com.google.android.apps.maps:
      com.google.android.projection.gearhead
  queryable via interaction:
    User 0:
      [com.android.keychain,com.android.settings,com.android.inputdevices,com.android.dynsystem,com.qualcomm.qti.xrvd.service,com.motorola.android.providers.settings,com.android.localtransport,com.android.location.fused,com.motorola.android.jvtcmd,android,com.android.wallpaperbackup,com.android.server.telecom,com.motorola.ccc.mainplm,com.trustonic.teeservice,com.android.providers.settings]:
        com.google.android.projection.gearhead
      com.android.bluetooth:
        com.google.android.projection.gearhead
      [com.android.calllogbackup,com.android.providers.userdictionary,com.android.providers.contacts,com.android.providers.blockednumber]:
        com.google.android.projection.gearhead
      com.android.providers.calendar:
        com.google.android.projection.gearhead
      com.google.android.googlequicksearchbox:
        com.google.android.projection.gearhead
      [com.google.android.gms,com.google.android.gsf]:
        com.google.android.projection.gearhead
      com.google.android.projection.gearhead:
        [com.android.keychain,com.android.settings,com.android.inputdevices,com.android.dynsystem,com.qualcomm.qti.xrvd.service,com.motorola.android.providers.settings,com.android.localtransport,com.android.location.fused,com.motorola.android.jvtcmd,android,com.android.wallpaperbackup,com.android.server.telecom,com.motorola.ccc.mainplm,com.trustonic.teeservice,com.android.providers.settings]
        com.android.settings.intelligence
        com.google.android.googlequicksearchbox
        com.android.vending
        com.google.android.apps.maps
      com.android.vending:
        com.google.android.projection.gearhead
      com.google.android.inputmethod.latin:
        com.google.android.projection.gearhead
      com.google.android.apps.maps:
        com.google.android.projection.gearhead

All except the READ_PHONE_STATE below are false in lineage:

Spoiler

    User 0:
      gids=[3002, 3003, 3001]
      runtime permissions:
        android.permission.READ_CALENDAR: granted=true, flags=[ GRANTED_BY_DEFAULT]
        android.permission.READ_CALL_LOG: granted=true, flags=[ GRANTED_BY_DEFAULT|RESTRICTION_INSTALLER_EXEMPT|RESTRICTION_SYSTEM_EXEMPT|RESTRICTION_UPGRADE_EXEMPT]
        android.permission.ACCESS_FINE_LOCATION: granted=true, flags=[ GRANTED_BY_DEFAULT]
        android.permission.RECEIVE_SMS: granted=true, flags=[ GRANTED_BY_DEFAULT|RESTRICTION_INSTALLER_EXEMPT|RESTRICTION_SYSTEM_EXEMPT|RESTRICTION_UPGRADE_EXEMPT]
        android.permission.ACCESS_COARSE_LOCATION: granted=true, flags=[ GRANTED_BY_DEFAULT]
        android.permission.READ_PHONE_STATE: granted=true, flags=[ SYSTEM_FIXED|GRANTED_BY_DEFAULT]
        android.permission.SEND_SMS: granted=true, flags=[ GRANTED_BY_DEFAULT|RESTRICTION_INSTALLER_EXEMPT|RESTRICTION_SYSTEM_EXEMPT|RESTRICTION_UPGRADE_EXEMPT]
        android.permission.CALL_PHONE: granted=true, flags=[ GRANTED_BY_DEFAULT]
        android.permission.RECORD_AUDIO: granted=true, flags=[ GRANTED_BY_DEFAULT]
        android.permission.READ_CONTACTS: granted=true, flags=[ GRANTED_BY_DEFAULT]

Most of the below are missing from lineage:

Spoiler

Package Changes:
  Sequence number=1448
  User 0:
    seq=0, package=com.motorola.contacts.preloadcontacts.overlay.vzw
    seq=1, package=com.tmobile.m1
    seq=2, package=com.metro.minus1
    seq=3, package=com.tmobile.rsuadapter.qualcomm
    seq=4, package=com.metro.rsuapp
    seq=5, package=com.motorola.carrierconfig
    seq=6, package=com.google.android.apps.messaging
    seq=7, package=com.motorola.sprintwfc
    seq=8, package=com.motorola.tmo.setupext
    seq=9, package=com.motorola.easyprefix
    seq=10, package=com.motorola.android.messaging.overlay.tmo.testsim
    seq=11, package=com.motorola.android.server.telecom.overlay.metro
    seq=12, package=com.motorola.launcherconfig.overlay.tmo
    seq=13, package=com.facebook.system
    seq=14, package=com.motorola.att.phone.extensions
    seq=15, package=com.sprint.w.installer
    seq=16, package=com.facebook.appmanager
    seq=17, package=com.coremobility.app.vnotes
    seq=18, package=com.sprint.ms.smf.services
    seq=19, package=com.google.android.apps.subscriptions.red
    seq=20, package=com.motorola.setup.overlay.pai
    seq=21, package=com.motorola.launcherconfig.overlay.metropcs
    seq=22, package=com.motorola.setup.overlay.tmo
    seq=23, package=com.motorola.android.server.telecom.overlay.tmo
    seq=24, package=com.sprint.ms.cdm
    seq=25, package=com.amazon.appmanager
    seq=26, package=com.amazon.avod.thirdpartyclient
    seq=27, package=com.motorola.omadm.sprint
    seq=28, package=com.tmobile.pr.mytmobile
    seq=29, package=com.tmobile.echolocate
    seq=31, package=com.lookout
    seq=32, package=com.roaming.android.gsimcontentprovider
    seq=33, package=com.facebook.services
    seq=34, package=com.motorola.fmplayer
    seq=35, package=com.motorola.tmo.settingsext
    seq=36, package=com.tmobile.pr.adapt
    seq=37, package=com.motorola.android.messaging.overlay.tmo
    seq=38, package=com.metropcs.metrozone
    seq=39, package=com.tmobile.rsuapp
    seq=41, package=com.sprint.ce.updater
    seq=42, package=com.motorola.hotspotlauncher
    seq=43, package=com.motorola.omadm.vzw
    seq=44, package=com.roaming.android.gsimbase
    seq=45, package=com.tmobile.rsusrv
    seq=47, package=com.motorola.settings
    seq=48, package=com.motorola.vzw.pco.extensions.pcoreceiver
    seq=49, package=com.nuance.nmc.sihome.metropcs
    seq=50, package=com.motorola.spectrum.setup.extensions
    seq=51, package=com.motorola.nfwlocationattribution
    seq=52, package=com.motorola.rcsConfigService
    seq=53, package=com.att.iqi
    seq=54, package=com.google.android.permissioncontroller
    seq=55, package=com.android.systemui
    seq=165, package=com.google.android.cellbroadcastreceiver
    seq=188, package=com.motorola.actions
    seq=213, package=com.motorola.faceunlock
    seq=214, package=com.android.nfc
    seq=215, package=com.motorola.screenshoteditor
    seq=299, package=com.google.android.documentsui
    seq=310, package=com.motorola.help
    seq=327, package=com.motorola.msimsettings
    seq=329, package=com.android.stk
    seq=336, package=com.android.contacts
    seq=337, package=com.android.dialer
    seq=338, package=com.android.providers.contacts
    seq=339, package=com.android.soundpicker
    seq=341, package=com.android.traceur
    seq=353, package=com.google.android.apps.wallpaper
    seq=439, package=com.google.android.partnersetup
    seq=514, package=com.google.android.gsf
    seq=649, package=com.motorola.hiddenmenuapp
    seq=659, package=com.motorola.ccc.ota
    seq=674, package=com.motorola.messaging
    seq=678, package=com.google.android.syncadapters.contacts
    seq=681, package=com.motorola.coresettingsext
    seq=820, package=com.motorola.paks
    seq=930, package=com.motorola.discovery
    seq=1149, package=com.android.vending
    seq=1257, package=com.google.android.setupwizard
    seq=1260, package=com.google.ar.core
    seq=1261, package=com.google.android.as
    seq=1262, package=com.google.android.tts
    seq=1263, package=com.motorola.gamemode
    seq=1265, package=com.google.android.trichromelibrary_519513633
    seq=1266, package=com.google.android.webview
    seq=1269, package=com.google.android.marvin.talkback
    seq=1270, package=com.motorola.timeweatherwidget
    seq=1271, package=com.motorola.imagertuning_V2
    seq=1278, package=com.google.android.calculator
    seq=1281, package=com.motorola.ccc.notification
    seq=1287, package=com.android.chrome
    seq=1289, package=com.google.android.apps.wellbeing
    seq=1290, package=com.motorola.genie
    seq=1291, package=com.google.android.apps.photos
    seq=1292, package=com.google.android.ims
    seq=1298, package=com.motorola.mototour
    seq=1301, package=com.motorola.moto
    seq=1302, package=com.google.android.deskclock
    seq=1303, package=com.motorola.motodisplay
    seq=1309, package=com.motorola.aiservices
    seq=1310, package=com.google.android.apps.turbo
    seq=1311, package=com.google.android.apps.nbu.files
    seq=1333, package=com.motorola.livewallpaper3
    seq=1379, package=com.google.android.apps.tachyon
    seq=1381, package=com.google.android.gm
    seq=1407, package=com.google.android.inputmethod.latin
    seq=1409, package=com.google.android.calendar
    seq=1419, package=com.motorola.camera3
    seq=1423, package=com.android.shell
    seq=1424, package=com.android.settings
    seq=1425, package=com.google.android.projection.gearhead
    seq=1426, package=com.google.android.googlequicksearchbox
    seq=1427, package=com.google.android.apps.googleassistant
    seq=1428, package=com.google.android.youtube
    seq=1429, package=com.google.android.apps.maps
    seq=1443, package=com.google.android.gms
    seq=1447, package=com.motorola.audiofx

missing from lineage:

Spoiler

      used by other apps: [com.google.android.apps.maps]

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

Spoiler

Compiler stats:
  [com.google.android.projection.gearhead]
     base.apk - 4719
     AndroidAutoStub.apk - 260

APEX session state:
  Session ID: 472246030
    State: STAGED

Active APEX packages:


Inactive APEX packages:


Factory APEX packages:

 

[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.

 

[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.

 

[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.

 

[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!

 

[LunchStrong5016]

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!

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.