[OFFICIAL][ROM][PAYTON]LineageOS 19.1 (Android 12.1)

Search This thread

nfsllow

Senior Member
Mar 27, 2015
51
14

ThE_MarD

Recognized Developer
Dec 10, 2014
3,231
3,704
Grande Prairie
LeEco Le Max 2
Moto X4
@leetripper and @nfsllow, thanks for that information fellas! So it seems there could be certain stock ROM firmware that could be outdated or incompatible with the custom ROM setup on LineageOS (and I'm guessing other Payton custom ROMs that use a similar device/vendor tree setup too) and the proper solution is to indeed try different stock ROM and see if that device firmware works better. @Knuxyl I recommend seeing what they wrote and to try that if you are still having issues with LTE.

nfsllow, I from what others have told me? Apparently that issue isn't isolated to LineageOS for payton as they recommend trying other apps. You can maybe try Magisk with SafetyNet mods to see if that might somehow fix it, but it doesn't sound like it would unless that app is maybe checking for unlocked bootloader or something too?

They did say to try mparivahan or digitlocker apps. Those might also require Magisk and SafetNet mods to work though
 

Knuxyl

Senior Member
May 20, 2009
237
99
Google Pixel 5
thats not true, system_b is flashed.
in that case though we can just add _b to all flash files excluding system and we wouldnt need copy partitions then. this doesnt explain why copy partitions breaks lte band 13.

@leetripper and @nfsllow, thanks for that information fellas! So it seems there could be certain stock ROM firmware that could be outdated or incompatible with the custom ROM setup on LineageOS (and I'm guessing other Payton custom ROMs that use a similar device/vendor tree setup too) and the proper solution is to indeed try different stock ROM and see if that device firmware works better. @Knuxyl I recommend seeing what they wrote and to try that if you are still having issues with LTE.

nfsllow, I from what others have told me? Apparently that issue isn't isolated to LineageOS for payton as they recommend trying other apps. You can maybe try Magisk with SafetyNet mods to see if that might somehow fix it, but it doesn't sound like it would unless that app is maybe checking for unlocked bootloader or something too?

They did say to try mparivahan or digitlocker apps. Those might also require Magisk and SafetNet mods to work though
i already fixed my problem like weeks ago. I flashed stock, copy partitions and then LOS and I get no LTE band 13. I then flashed stock and then LOS and everything works fine. I have no idea what in the world is going on, nor do I care anymore. Copy partitions zip causes me problems. It doesn't make any sense, but it does.
 
  • Like
Reactions: Douglas Miranda

nfsllow

Senior Member
Mar 27, 2015
51
14
@leetripper and @nfsllow, thanks for that information fellas! So it seems there could be certain stock ROM firmware that could be outdated or incompatible with the custom ROM setup on LineageOS (and I'm guessing other Payton custom ROMs that use a similar device/vendor tree setup too) and the proper solution is to indeed try different stock ROM and see if that device firmware works better. @Knuxyl I recommend seeing what they wrote and to try that if you are still having issues with LTE.

nfsllow, I from what others have told me? Apparently that issue isn't isolated to LineageOS for payton as they recommend trying other apps. You can maybe try Magisk with SafetyNet mods to see if that might somehow fix it, but it doesn't sound like it would unless that app is maybe checking for unlocked bootloader or something too?

They did say to try mparivahan or digitlocker apps. Those might also require Magisk and SafetNet mods to work though
Yup, i got same issue with PE Rom. So system reboots due to app checking for unlocked bootloader?. Digilocker and mparivahan works though
 

wkn000

Senior Member
Jan 19, 2017
92
54
I used this Motorola Stock Firmware from lolinet on first install of Lineage OS on my Moto X4 (17.1 in 2020): XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (which was latest there). Also used one time copy_partitions.zip then.

No issues on updates or even upgrades since (Latest: 1 hour before).
 
  • Love
Reactions: ThE_MarD

leetripper

Senior Member
Mar 18, 2016
57
15
Funny thing, since today Chrome Bookmarks Widget is unusable. No navigation possible anymore. Anyone else? Any idea?
 

jeremywh7

Senior Member
Sep 16, 2013
246
116
Indy
Motorola Atrix 4G
Moto X
in the first post, item 7 is optionally.....(google apps)
if i don,t install, anyway i will be able to use the google services? playstore and others?
No, Gapps is required for any google services. Just depends on which provider and package to use; bare minimum* all the way up to ... everything. I use NikGapps; I have earlier posts with details. ;-)

* If you just want the bare minimum, use e.g. NikGapps Core or 'Mind the Gapps'.
 
Jul 31, 2018
8
3
Moto X4
No, Gapps is required for any google services. Just depends on which provider and package to use; bare minimum* all the way up to ... everything. I use NikGapps; I have earlier posts with details. ;-)

* If you just want the bare minimum, use e.g. NikGapps Core or 'Mind the Gapps'.
tks for information!

already installed and working perfectly!...

after back to stock rom and with patiently installed the LOS Rom, the only problem is installing certains app, like as star+, netflix, gb whatsapp, its coming the message " There was a problem parsing the package".....
someone with the same problem
 
  • Like
Reactions: ThE_MarD

rseiler

Senior Member
Jun 24, 2012
232
69
@Jer
after back to stock rom and with patiently installed the LOS Rom, the only problem is installing certains app, like as star+, netflix, gb whatsapp, its coming the message " There was a problem parsing the package".....
someone with the same problem
Aren't some of those not eligible to be installed at all, like Netflix? That's what Google Play tells me, anyway. So in that case, how are you doing it to get the error your speak of? I would try Aurora Store via F-Droid.
 
  • Like
Reactions: Douglas Miranda
Jul 31, 2018
8
3
Moto X4
@Jer

Aren't some of those not eligible to be installed at all, like Netflix? That's what Google Play tells me, anyway. So in that case, how are you doing it to get the error your speak of? I would try Aurora Store via F-Droid.
i understand!

i,m trying to install these apps in the sites like uptodown, apkpure etc...
i.m trying F-Droid. but these apps not found!

the gbwhatsapp was downloaded direct from jimtech site, like the other times... and never had a problem...

Tks for your attention!
 
  • Like
Reactions: ThE_MarD

rseiler

Senior Member
Jun 24, 2012
232
69
i understand!

i,m trying to install these apps in the sites like uptodown, apkpure etc...
i.m trying F-Droid. but these apps not found!

the gbwhatsapp was downloaded direct from jimtech site, like the other times... and never had a problem...

Tks for your attention!

Understood. Not sure why direct apks aren't working, but in F-Droid install "Aurora Store" and then use that as sort of your Google Play replacement for the problem apps. May work, may not, but easy to try. I know Netflix works that way, at least.
 
  • Like
Reactions: ThE_MarD

bz2022

New member
Jul 4, 2022
2
1
Upgraded from 18.1 to 19.1 for one of my x4s. Had a strange wifi problem. The 19.1 had no issue connecting to my home wifi router, but cannot connect to the hotspot on the other x4, which is running 18.1. It constantly loops between connect/disconnect with an error msg, "Cannot provide internet service ...". Any ideas what is happening?
 

bz2022

New member
Jul 4, 2022
2
1
Upgraded from 18.1 to 19.1 for one of my x4s. Had a strange wifi problem. The 19.1 had no issue connecting to my home wifi router, but cannot connect to the hotspot on the other x4, which is running 18.1. It constantly loops between connect/disconnect with an error msg, "Cannot provide internet service ...". Any ideas what is happening?
It turned out to be an issue on 18.1 hotspot. After restarting the x4 with 18.1 and enabling hotspot on it, the x4 with 19.1 connected to the hotspot without any problem.
 
  • Like
Reactions: exzombie
Jul 31, 2018
8
3
Moto X4
Anyone has experimented battery problem after flash The New weekly (05/july)rom?

I changed The batt because my old battery was bad Life

After battery change, using during 1 week, installed The weekly 05/july/22 via OTA, The New batt is not receiving The charge...

I noticed that The temperature of battery is -30°C.....

The question is....
Is The sensor of temperature is in the battery? Or in the Phone?
Is The problem of The rom?
 

Attachments

  • IMG-20220714-WA0002.jpg
    IMG-20220714-WA0002.jpg
    52.5 KB · Views: 10

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I can't really tell if you're saying that it coincided with the battery or the ROM, but if it's the battery I'd see if it happens with the old one now, even if its life wouldn't be as good. At least you'd know if any battery can receive a charge. If it's the ROM, see about the Jul 12 one, though I note these two things that will be in next week's build:
    1
    Anyone has experimented battery problem after flash The New weekly (05/july)rom?
    I was having battery drain issues ever since I installed the 20220621 build. The latest build is 20220712, and the issue is now resolved.
  • 8
    2okPze5.png



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



    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.



    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.



    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.



    Introduction

    This is the official Lineage OS thread for the Motorola Moto X4, codename payton.



    We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.



    How to install via Lineage Recovery

    Please follow the official instructions



    HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY

    Please follow the official LineageOS Wiki instructions for our device




    How to install via TWRP

    1. Boot the newest TWRP .img from the Official TWRP Project Site.
    2. IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
    3. In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
    4. ADB sideload the newest weekly
    5. (Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
    6. Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
    7. (Optionally) Flash GApps
    8. Reboot


    How to upgrade from the previous version via Lineage Recovery

    Please follow the official instructions



    How to upgrade from the previous version via TWRP

    1. Boot the newest TWRP .img from the Official TWRP Project Site.
    2. IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
    3. In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
    4. ADB sideload the newest weekly build or copy it to your device and install the zip
    5. (Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
    6. Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
    7. (Optionally) Flash GApps
    8. Reboot


    Notes

    Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
    Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.


    Download


    Official:

    Unofficial test builds:



    Google Apps (GApps)

    MindTheGapps:


    GCam Mods



    Contributors

    erfanoabdi, SevenRock, ThE_MarD, Moto sdm660 devs, the Lineage Team

    Source Code: https://github.com/LineageOS

    ROM Firmware Required: Official Pie
    4
    Important extra links

    Payton Stock firmware:

    Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
    4
    Heyyo, a new test build is going up! lineage-19.1-20220416-UNOFFICIAL-payton contains Moto Camera 2 app and fixes for offline charging as well


    VERY special thanks to SevenRock for doing the majority of the LOS 19.1 trees for Moto sdm660 and payton (y)
    3
    I only boot to TWRP temporary for "some" operations. Usually, Lineage recovery is installed permanent and has no issues at all with OTA updates done with System Updater. Reboot after update and everything is fine, no thinking about slots and so on.
    3
    @Knuxyl , system_b is flashed with system_other which is just a basic partition flash to prepare it for OTA is all. It isn't a full flash. You'll see in that script that system_a flashes multiple sparse images as Motorola breaks up their system image into multiple files. System_other is 67MB so it's definitely not a full system image. The sparse system images for partition a adds up to 3.31GB.

    It's too late in Payton's lifecycle to change a flashall file and expect all users to always use it if they flash fbrom. Besides, copy partitions script works without issues on other A/B partitioned devices so I don't see how it could break payton as I haven't heard of anyone else losing an LTE band by flashing it.

    Anyways, I don't see how copy partitions would break any LTE band as those are usually hardware locked, not software locked. You can always try a different region of stock ROM and then run copy partitions and see if something changes?
    Had the same problem losing LTE on my XT1900-7. Flashed to stock with this ROM, which I kept for this purpose: XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
    I realized that there was still no LTE. Used this one instead: PAYTON_RETAIL_9.0_PPW29.69-40-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
    Now it worked again and I could flash copy partitions and LOS and everything works fine...