• 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

klubad

Member
Sep 17, 2014
5
0
I installed the official LineageOS image for cedric a month ago, from a stock phone (I never installed a custom rom on this phone before).

I have some issues, but I don't find any comments about these issues here or in the official LineageOS gitlab tracker.
  • the dual sim is quite buggy (sometimes, i just can't get incoming call, sometimes I don't have data). for the moment I just dropped one sim card, things are better
  • the camera do not work. Right after some reboots, it works for a while (several hours), then the official camera app and OpenCamera refuse to open.
I followed the official instructions to flash. Is it possible I did something wrong? Or these bugs are really here for everyone?
 

nift4

Senior Member
May 22, 2019
586
200
nift4.github.io
Moto G5
F(x)tec Pro1
I installed the official LineageOS image for cedric a month ago, from a stock phone (I never installed a custom rom on this phone before).

I have some issues, but I don't find any comments about these issues here or in the official LineageOS gitlab tracker.
  • the dual sim is quite buggy (sometimes, i just can't get incoming call, sometimes I don't have data). for the moment I just dropped one sim card, things are better
  • the camera do not work. Right after some reboots, it works for a while (several hours), then the official camera app and OpenCamera refuse to open.
I followed the official instructions to flash. Is it possible I did something wrong? Or these bugs are really here for everyone?
I don't think so, if you did something wrong, it would have more effects. I suggest opening a report there.
 

rtd4

Senior Member
Jan 31, 2021
87
17
bugs

radio fm
front camera does not work in some applications
 
Last edited:

rtd4

Senior Member
Jan 31, 2021
87
17
wow thank you very much to the developer only change I made was the dpi from 420 to 480

captures

0.png
1.png
2.png
4.png
5.png
6.png
7.png
8.png

Screenshot_20210422-012854_Geekbench_4.png
 
Last edited:

rtd4

Senior Member
Jan 31, 2021
87
17
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.


View attachment 5226757View attachment 5226761

CEDRIC WIKI
Is there any way to activate low ram, no matter how much I edit build.prop, it is not applied
 

dschrempf

Member
Jul 17, 2018
17
9
Hi! Thanks for this ROM! I have two questions wrt the recovery:
- Do I need the 32 or 64bit version of TWRP?
- Should I use the official latest version advertised in the neighboring thread TWRP 3.5.2_9?
 
Aug 3, 2019
41
31
Berlin
  • Like
Reactions: Tiki Thorsen
Aug 3, 2019
41
31
Berlin
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?
 

nift4

Senior Member
May 22, 2019
586
200
nift4.github.io
Moto G5
F(x)tec Pro1
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.
 
  • Like
Reactions: shutdown-h_now
Aug 3, 2019
41
31
Berlin
It can be an ROM issue, but not many users care simply because network time sync is fine.
Unfortunately network sync of date and time doesn't seem to work.
The phone only uses a "guest" WLAN, not the "normal" WLAN. So I guess it doesn't have the rights to use the sync feature. It also has no SIM card, so no sync via moblie network possible. But nevertheless thanks for your hint.
 

iansterguy

New member
These two updates were working mostly fine for me
18.1-20210610 and an OTA upgrade to 18.1-20210617. I installed 18.1-20210624 right after without restarting to automatically upgrade the recovery. The WiFi would not turn on. After wiping data and flashing from scratch, WiFi worked.

The google play store didn't work though. I tried clearing app data and cache partition I bypassed my routers VPN, logged out of google, updated google services logged out, restarted logged back in. None of that worked so I gave up.

To make it work I ended up reverting to 18.1-20210617. I decided to skip all the setup wizards and left googles privacy at defaults just in case google was upset. Works fine now like before.

Bugs: In 18.1-20210610 at least The default camera app works at boot-up but can consistently fail to launch later. Restarting fixes it and when it works, it seems to work fine. Choosing a wallpaper from photos closes the app unless I switch to another On-Device Wallpaper first.

Overall 18.1-20210617 seems good, and for what it's worth I recommend it.
 
Last edited:

TheFixItMan

Senior Member
Jul 8, 2012
7,833
4,027
London
These two updates were working mostly fine for me
18.1-20210610 and an OTA upgrade to 18.1-20210617. I installed 18.1-20210624 right after without restarting to automatically upgrade the recovery. The WiFi would not turn on. After wiping data and flashing from scratch, WiFi worked.

The google play store didn't work though. I tried clearing app data and cache partition I bypassed my routers VPN, logged out of google, updated google services logged out, restarted logged back in. None of that worked so I gave up.

To make it work I ended up reverting to 18.1-20210617. I decided to skip all the setup wizards and left googles privacy at defaults just in case google was upset. Works fine now like before.

Bugs: In 18.1-20210610 at least The default camera app works at boot-up but can consistently fail to launch later. Restarting fixes it and when it works, it seems to work fine. Choosing a wallpaper from photos closes the app unless I switch to another On-Device Wallpaper first.

Overall 18.1-20210617 seems good, and for what it's worth I recommend it.
Wrong thread - this is for lineage os 17.1

And for lineageos 18.1 you need to use bitgapps 64 bit - not open gapps
 

SirRGB

Senior Member
Unsafe? If you're going to say something like that you are going to have to back it up with some facts.

Nothing wrong with bitgapps. I have full safetynet pass using it
What Rose tells you in cedric chat group:
no. Not BitGapps. They disable security features because the "dev" of BitGapps is to lazy to copy files from OpenGapps. Installing BitGapps means no support.

Edit:
someone said
To be exact, it disables priv app permission enforcement instead of configuring it like any normal gapps package.


Edit:
outdated information, sorry
 
Last edited:

iansterguy

New member
Wrong thread - this is for lineage os 17.1

And for lineageos 18.1 you need to use bitgapps 64 bit - not open gapps
Sorry, I should have known the correct thread now is rom-unofficial-cedric-11-lineageos-18-1.4260293 I know the official maintainer is JarlPenguin. Just thought it meant something that he didn't update the thread name to official.

Note I didn't use Open gapps, I used, MindTheGapps for 18.1 from the suggested link in Lineageos Installation instructions. Seems I will be switching when I update.
 
Last edited:

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.