• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][10][OFFICIAL] Lineage 17.1 NIGHTLY for MOTO G5. (Cedric)

Search This thread

Lucius Snow

Senior Member
May 10, 2009
174
1
Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"

Is there anything I can do about this?

Thanks!
Hello,

I have the exact same problem. Any help appreciated.

Thanks.
 

dezzo77

Senior Member
Apr 25, 2011
67
11
Nexus 7 (2013)
Samsung Galaxy S5
Did they ever solve the extremely high idle battery drain with the G5?
Every ROM I tried had very poor idle standby time, even with a very minimal set of apps installed, notifications off, etc etc. It was used as a music player only, and spent most of the time idle. On the OEM ROM the standby time would be many days, but with the Lineage ROMS and more conservative settings, it would need to be charged every day.
 

hellwhynot

Member
Feb 28, 2017
18
3
Did they ever solve the extremely high idle battery drain with the G5?
Every ROM I tried had very poor idle standby time, even with a very minimal set of apps installed, notifications off, etc etc. It was used as a music player only, and spent most of the time idle. On the OEM ROM the standby time would be many days, but with the Lineage ROMS and more conservative settings, it would need to be charged every day.
Guess not. I'm on LOS 18.1, with a battery a couple months old and battery life is still not great compared to when I was still on Android 7. Battery drain suddenly became an issue after upgrading to Oreo and it has not improved since.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    OFFICIAL LINEAGE OS 17.1 NIGHTLIES

    The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].

    The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.


    Screenshot_20210219-151625_Settings.pngScreenshot_20210219-152937_Settings.png

    CEDRIC WIKI
    2
    Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !

    Any oero firmware will do as your base
    Flash via fastboot - if you don't know which to choose use the latest retail version

    How to flash rom

    Go to twrp
    Select wipe
    Format data - option on the right (will format everything on phone including personal files so backup first!)
    Restart to twrp
    Wipe then advanced wipe
    Wipe system data and cache
    Select install from main menu
    Install rom zip
    Install gapps (you want arm64 android 10 nano)
    Install magisk (optional for root access & to hide apps from detecting root/custom rom)
    Wipe delvik cache
    Restart
    Encrypt phone again if required once booted from phone settings menu
    1
    It must be manually installed it via TWRP.

    This upgrade should be installed using ADB as stated in https://wiki.lineageos.org/devices/cedric/upgrade.

    If you want to install via recovery then better use the appropriate LOS-recovery from https://download.lineageos.org/cedric and not TWRP.
    It's not necessary to install this one on the phone. Just boot to bootloader and start by fastboot boot <LOS-recovery>.
    1
    Since the very first LOS 17.1 from mid February 2021 and even now on 18.1 I observe a strange behaviour of the Moto G (5) - cedric:
    Even if (particially - no GApps) using the "recipe" of posting #3 by @TheFixItMan the date and time of the phone is not correct when shut down and booted again.
    It's always the date and time of the flashed ROM build that shows up and must be adjusted manually in settings.

    Does anyone have a hint what to do or what I could have done wrong?
    I remember that last year the same issue appeared with another Motorola phone (Moto G4 Play - harpia). It vanished after a few months with one of the weekly nightly updates. So it could perhaps be a ROM issue?
    It can be an ROM issue, but not many users care simply because network time sync is fine.