[ROM]-[11.0]-[KIEV]-LineageOS-18.1-[UNOFFICIAL]

Search This thread

smartasiankid

Senior Member
May 26, 2019
131
7
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.
 

meisanerd

Senior Member
Nov 17, 2012
110
51
Edmonton
Moto G 5G
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.
Mine responds pretty much instantly, no delay here.
 

smartasiankid

Senior Member
May 26, 2019
131
7
18.1-20220716-NIGHTLY-kiev
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.
 
Sep 18, 2019
39
9
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."
 
Last edited:
  • Like
Reactions: watson007

zigxda

Member
Apr 15, 2021
7
1
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.
 
  • Like
Reactions: RETIEF

zigxda

Member
Apr 15, 2021
7
1
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.
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.
 

moslondon

Senior Member
Sep 30, 2012
197
16
Dallas
Perhaps try joining the Telegram channel? Much A12 things can be found there.
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.
Good to know that. Are all cameras working? VoLTE? 5G? I am with A&TT
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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.
    Perhaps try joining the Telegram channel? Much A12 things can be found there.
    1
    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.
    1
    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.
    1
    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:
    Code:
    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.
    1
    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.
  • 13
    2okPze5.png

    Motorola G 5G / Motorola One G 5G Ace
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */
    Introduction:
    This is the Unofficial Lineage OS 18.1 thread for the Motorola G 5G, codename kiev.​
    Join our Motorola G 5g / Motorola One 5G Ace Development Telegram Group!​

    LINKS:
    Recovery: Unofficial TWRP
    Magisk: Magisk
    Factory Firmware: Stock Firmware Mirror
    "Copy Partitions Zip" - courtesy of @filipepferraz
    (To setup "Slot B")

    How to Install:
    01. Download the ROM, Firmware and GApps from the links above.
    02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    03. Create backup. i.e. EFS / Persist and put somewhere safe.
    ## YOU ONLY NEED THIS STEP ONCE.. When updating Firmwares ##
    04.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
    05. Flash the ROM
    06. Choose Reboot -> Bootloader
    07. boot twrp again "fastboot boot twrp.img"
    08. Install GApps & Magisk.
    09. Reboot -> Bootloader
    10. fastboot -w
    11. Click Start and Enjoy.

    NOTES:
    *Note-1: Slots, ROMS install to opposite (inactive) slot
    If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
    *Note-2: Updating "Dirty Flash"
    01. Boot TWRP
    02. Flash ROM
    03. Reboot -> Bootloader
    04. Boot TWRP
    05. Install Gapps + Magisk
    06. Reboot -> System
    *Note-3: Updating "Dirty Flash"
    Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)​

    XDA:DevDB Information
    kiev-lineageos, ROM for the Motorole G 5G

    Contributors

    erfanoabdi, SyberHexen, Jleeblanch
    Source Code: https://github.com/SyberHexen

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.19
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2021-07-05
    Last Updated 2021-07-22
    6
    I made this tutorial to help in flashing.
    3
    Changelogs:

    09/19/2021
    Device changelog:

    - Fixed Regression with DRM Apps
    3
    Past Changelogs:


    09/16/2021
    Device changelog:

    - Fixed Incoming call audio bug
    - Updated Brightness overlays
    - Updated Kernel Device Trees
    - Misc Improvements
    09/09/2021
    Device changelog:

    - Enforcing Selinux
    - Fixed Off-mode Charging
    - Switched to Racer Off-mode animation
    - Fixed Setting device model between Ace/5g variants
    - Fixed Media studder
    08/12/2021
    Device changelog:

    - carrierconfig: update from kievv tag 'RRV31.Q2-36-14-8'
    - carrierconfig: update from CAF tag 'LA.UM.9.12.r1-10800-SMxx50.0'
    - update defconfig from kievv tag 'RRV31.Q2-36-14-8'
    - Show Turbo Charging instead of charging rapidly
    - enable support for freeform windows and picture-in-picture
    - upgrade bootctrl hal to 1.1
    - increase audio for speaker(s) and microphone
    - Exfat driver included to kernel for LOS recovery support
    07/22/2021
    Device changelog:

    - Minor Fixes
    - Updated Brightness overlays

    07/05/2021
    Device changelog:

    - Minor Fixes
    - Switch to Pixel Power Hal

    07/01/2021
    Device changelog:

    - Initial Build

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