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

[ROM] [11] LineageOS 18.1 [OFFICIAL]

Search This thread

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
Next: the now installed LOS 18.1 with Mindthegapps has no play store again.
I could do the same, as before, flashing Mtg, that works, but not gps.

What could be the next step to solve these problems?
I'm interested in doing my own part of finding the faults, may be, my knowledge is to low.
 
Last edited:
Next: the no installed LOS 18.1 with Mindthegapps has no play store again.
I could do the same, as begore, flashing Mtg, that works, but not gps.

What could be the next step to solve these problems?
I'm interested in doing my own part of finding the faults, may be, my knowledge is to low.
TLDR: Flash LineageOS, DO NOT boot into system, reboot directly to recovery, then flash Gapps (MindTheGapps, Nik, etc)

Explaination:
If you flashed Gapps right after flashing LineageOS, you've done it wrong.
This is because, XZ2/C/P/3 has A/B partition, which means, after flashing LineageOS, it will automatically switch to another slot. If you're flashing Gapps at this time, it goes into the slot which you're not gonna boot into. You need to reboot to recovery once to switch the slot (assuming you're using LineageOS Recovery), or switch slot in TWRP, then flash other addons.
 
  • Like
Reactions: farukr1

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
I did it again;-) Start with installing the LOS-Recovery, factory reset, sideload of LOS-18.1.ZIP, (as I remember, Slot b has been shown before starting sideload), rebooting into recovery, sideload of Mindthatgapps.ZIP, once again reboot into recovery, because Slot a was shown again. After reboot, Slot a was shown further.

At that point, unsure, if I did it correct, I did a reboot and it started up with another login-screen. Now, GAPPS seemed to be installed, but I can't login to playstore.
I'd this problem in the beginning of installing LOS 17.1, I did that in different ways, I probably got the right combination of slots by chance, at some point the problem with the login disappeared. Unfortunately I don't know what the reason was.
So, it is a success, but no solution at all.
 

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
Another observation: when I connect to the local WiFi, I can't access the Play Store, but when I use a hot spot on my other smartphone, I can access it, but I can't download all the apps I bought. The App Store interface also does not appear identical to that of the other smartphone. Let's see if there are any updates here.
 

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
I understood it to mean that the boot slot is changed every time I reboot into recovery. I tested this a few times by booting from recovery to recovery several times. However, slot a was displayed to me every time.

What have I misunderstood now?
 

Sjll

Recognized Developer
Jun 4, 2017
510
589
Chongqing
Another observation: when I connect to the local WiFi, I can't access the Play Store, but when I use a hot spot on my other smartphone, I can access it, but I can't download all the apps I bought. The App Store interface also does not appear identical to that of the other smartphone. Let's see if there are any updates here.
Try to feedback to MindTheGapps or NikGapps.
I understood it to mean that the boot slot is changed every time I reboot into recovery. I tested this a few times by booting from recovery to recovery several times. However, slot a was displayed to me every time.

What have I misunderstood now?
No, slot only be changed when your flashable package try to do it. For example, OTA update package.
 

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
Did this just some minutes ago, but same behavior. There is no probleme to use play store, when connected to my XZ2-Hotspot (1. wifi), but many problems, when connected to fritz.box (2. wifi).
With second wifi, surfin' with browser is possible, but not using play store. I'd remarked this first time, when I installed LOS 17.1 2 month ago. This issue disappaered all of sudden with no obvious reason, I could prove. Maybe some limmitations of wifi (2)?
 

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
Did this just some minutes ago, but same behavior. There is no probleme to use play store, when connected to my XZ2-Hotspot (1. wifi), but many problems, when connected to fritz.box (2. wifi).
With second wifi, surfin' with browser is possible, but not using play store. I'd remarked this first time, when I installed LOS 17.1 2 month ago. This issue disappaered all of sudden with no obvious reason, I could prove. Maybe some limmitations of wifi (2)?
Seems to be solved :) The DHCP-range was to small, so the new XZ2 got no IP4-adress ;-( My fault. May be, this embarrassing experience will help others in the future. ;-)

That means, IP6 is not enough to use PlayStore.
 
Last edited:

Ecthelion4

Senior Member
Apr 14, 2017
65
31
If so, why does installation of ROM and gapps in same routine lead to missing gapps? Why is it necessary to reboot after installation of ROM in recovery. Excuse me, but I feal, I'm to sill yto understand ;-(
The XZ2 is an A/B device, i.e. it has two system partitions (one in slot A, one in slot B). This has the advantage that an update of the system can be done by the user while he is still using his device. No long pause for the update is required. Just a quick reboot at the end of the process to switch slots, and that's it.

When such an OTA update comes in or a ROM gets installed via TWRP, then the update gets installed on the currently inactive slot. Let's assume slot A is currently active and we want to install a custom ROM, then the new ROM will get installed in the inactive slot B. This slot then gets marked as the one to boot from on the next restart. Now, to my understanding (otherwise people should please correct me), other zips, like GApps, always get installed into the currently active slot. Since slot A is still active, but you want to have the GApps installed for the new system in slot B, you first have to make slot B active. This can be done by a restart into recovery, because slot B was just marked as the one to become active on next boot. After the reboot into recovery slot B will be active and the installation of GApps will then be done for this now active slot B - which is exactly what we wanted.

Btw., this procedure is this way not only for the XZ2 but for any A/B device.

Hope this helps
 

joska59

Senior Member
Oct 20, 2007
61
7
Xperia XZ2
Another question; if now LOS 18.1 is installed, is then the recovery part of the ROM, or is installed by this with? Can I also install a TWRP afterwards, if so, which one?
Joska
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The Idle Batterylife is pretty good!

    1629370471857.png


    Code:
    Duration / Realtime: 65h9m28.784s                               
    Screen Off Discharge Rate (%/hr) | 0.83  (Discharged: 52%)                        
    Screen On Discharge Rate (%/hr)  | 12.55  (Discharged: 33%)                       
    Screen On Time                   | 2h37m45.703s                                   
    Screen Off Uptime                | 7h57m53.1s                                     
    Userspace Wakelock Time          | 6h28m37.048s                                   
    Sync Activity                    | 33m19.866s (164 times)                         
    JobScheduler Activity            | 5h31m56.985s (789 times)                       
    App Wakeup Alarms                | 1010 times                                     
    CPU Usage                        | 2h10m19.708s user time, 2h3m26.196s system time
    Kernel Overhead Time             | 1h29m16.052s                                   
    Kernel Wakelocks                 | 2h41m21.197s (840046 times)                    
    Wakeup Reasons                   | 45m56.91s (6752 times)                         
    Mobile KBs/hr                    | 8495.77                                        
    WiFi KBs/hr                      | 1988.00                                        
    Total WiFi Scan Activity         | 27.511s (6 times)                              
    Total WiFi Full Lock Activity    | 0                                              
    Mobile Active Time               | 7h56m26.34s                                    
    Signal Scanning Time             | 0                                              
    Full Wakelock Time               | 3m32.836s                                      
    Interactive Time                 | 2h37m20.799s                                   
    Phone Call Time                  | 24.705s                                        
    Device Idle Mode Enabled Time    | 14h48m55.928s                                  
    Device Idling Time               | 15h38m39.172s                                  
    Total GPS Use                    | 0 (0 times)                                    
    Wifi Power Usage                 | 0.00%/hr, 0.00% total                          
    Wifi Transfer Time               | 0                                              
    Wifi Idle Time                   | 0                                              
    Bluetooth Power Usage            | 0.00%/hr, 0.00% total                          
    Bluetooth Transfer Time          | 0                                              
    Bluetooth Idle Time              | 0                                              
    Camera Use                       | 45.107s (5 times)                              
    Flashlight Time                  | 1m54.853s (1 times)                            
    Modem Transfer Time              | 0                                              
    Modem Idle Time                  | 0
    Only 8% unaccounted... okay, nice. Way lower than expected.
    Code:
    Device's Power Estimates:
    Ranking | Name                                   | Uid   | Battery Percentage Consumed
    0       | UNACCOUNTED                            | 0     | 8.24%                     
    1       | SCREEN                                 | 0     | 17.58%                     
    2       | CELL                                   | 0     | 11.93%                     
    3       | org.mozilla.firefox                    | 10177 | 7.81%                     
    4       | me.bluemail.mail                       | 10212 | 4.31%                     
    5       | GOOGLE_SERVICES                        | 10092 | 4.25%                     
    6       | IDLE                                   | 0     | 4.25%                     
    7       | BLUETOOTH                              | 0     | 4.02%                     
    8       | DNS                                    | 1051  | 3.95%                     
    9       | com.maxmpz.audioplayer                 | 10183 | 3.50%                     
    10      | org.thoughtcrime.securesms             | 10178 | 3.46%                     
    11      | ROOT                                   | 0     | 2.50%                     
    12      | com.android.vending                    | 10097 | 1.42%                     
    13      | ANDROID_SYSTEM                         | 1000  | 1.34%                     
    14      | com.google.android.apps.maps           | 10179 | 0.79%                     
    15      | com.mgoogle.android.gms                | 10214 | 0.62%                     
    16      | com.google.android.apps.docs           | 10189 | 0.33%                     
    17      | RADIO                                  | 1001  | 0.32%                     
    18      | com.Splitwise.SplitwiseMobile          | 10185 | 0.29%                     
    19      | SYSTEM_UI                              | 10169 | 0.29%                     
    20      | AUDIOSERVER                            | 1041  | 0.22%                     
    21      | ch.threema.app                         | 10181 | 0.21%                     
    22      | com.synology.DSaudio                   | 10190 | 0.18%                     
    23      | GOOGLE_CALENDAR                        | 10136 | 0.17%                     
    24      | SharedUserID(android.uid.networkstack) | 1073  | 0.11%

    I listen to some music while driving, Poweramp and Blueooth.
    An Mail synchronisation sucks.
    Code:
    Userspace Wakelocks:
    Ranking | Name                                                                                                                | Uid   | Duration / Hr | Count / Hr | Total Duration | Total Count
    0       | me.bluemail.mail : *job*/me.bluemail.mail/com.android.exchangeas.service.sdk_26_eas_job_service.EasJobIntentService | 10212 | 3m44s472ms    | 1.01       | 4h20m15.127s   | 66         
    1       | com.maxmpz.audioplayer : AudioMix                                                                                   | 10183 | 1m17s903ms    | 0.08       | 1h32m48.128s   | 5         
    2       | me.bluemail.mail : *job*/me.bluemail.mail.provider/com.android.exchangeas.bluemail/[email protected]:android          | 10212 | 9s501ms       | 1.46       | 24m44.395s     | 95         
    3       | me.bluemail.mail : *sync*/me.bluemail.mail.provider/com.android.exchangeas.bluemail/[email protected]                 | 10212 | 9s499ms       | 1.41       | 24m44.167s     | 92         
    4       | ANDROID_SYSTEM : deviceidle_maint                                                                                   | 1000  | 10s358ms      | 2.39       | 15m44.979s     | 156       
    5       | ANDROID_SYSTEM : ActivityManager-Sleep                                                                              | 1000  | 3s832ms       | 1.17       | 5m57.986s      | 76         
    6       | RADIO : *telephony-radio*                                                                                           | 1001  | 3s167ms       | 312.01     | 4m33.551s      | 20330     
    7       | AUDIOSERVER : AudioMix                                                                                              | 1041  | 2s853ms       | 2.24       | 4m16.689s      | 146       
    8       | BLUETOOTH : StartingObexPbapTransaction                                                                             | 1002  | 1s656ms       | 0.12       | 3m52.051s      | 8         
    9       | me.bluemail.mail : CoreReceiver getWakeLock                                                                         | 10212 | 1s277ms       | 0.17       | 2m57.164s      | 11         
    
    SyncManager Syncs:
    Ranking | Name                                                                                         | Uid   | Duration / Hr | Count / Hr | Total Duration | Total Count
    0       | me.bluemail.mail : me.bluemail.mail.provider/com.android.exchangeas.bluemail/[email protected] | 10212 | 27s209ms      | 1.75       | 29m32.91s      | 114       
    1       | GOOGLE_CALENDAR : com.android.calendar/com.google/[email protected]                              | 10136 | 2s538ms       | 0.20       | 2m45.431s      | 13         
    2       | GOOGLE_SERVICES : com.android.contacts/com.google/[email protected]                              | 10092 | 357ms         | 0.05       | 23.286s        | 3         
    3       | ch.threema.app : com.android.contacts/ch.threema.app/Threema                                 | 10181 | 195ms         | 0.06       | 12.751s        | 4         
    4       | com.google.android.apps.docs : com.google.android.apps.docs/com.google/[email protected]         | 10189 | 119ms         | 0.03       | 7.772s         | 2         
    5       | org.thoughtcrime.securesms : com.android.contacts/org.thoughtcrime.securesms/Signal          | 10178 | 94ms          | 0.05       | 6.183s         | 3         
    6       | GOOGLE_SERVICES : com.google.android.location.reporting/com.google/[email protected]             | 10092 | 77ms          | 0.05       | 5.069s         | 3         
    7       | GOOGLE_SERVICES : subscribedfeeds/com.google/[email protected]                                   | 10092 | 55ms          | 0.05       | 3.599s         | 3         
    8       | GOOGLE_SERVICES : com.google.android.gms.people/com.google/[email protected]                     | 10092 | 16ms          | 0.02       | 1.099s         | 1         
    9       | GOOGLE_SERVICES : com.google.android.gms.drive.sync/com.google/[email protected]                 | 10092 | 10ms          | 0.05       | 665ms          | 3         
    
    JobScheduler Jobs:
    Ranking | Name                                                                                                                                                      | Uid   | Duration / Hr | Count / Hr | Total Duration | Total Count
    0       | me.bluemail.mail : me.bluemail.mail/com.android.exchangeas.service.sdk_26_eas_job_service.EasJobIntentService                                             | 10212 | 4m21s732ms    | 1.18       | 4h44m13.954s   | 77         
    1       | me.bluemail.mail : me.bluemail.mail.provider/com.android.exchangeas.bluemail/[email protected]:android                                                      | 10212 | 27s224ms      | 1.78       | 29m33.907s     | 116       
    2       | org.thoughtcrime.securesms : org.thoughtcrime.securesms/.jobmanager.JobSchedulerScheduler$SystemService                                                   | 10178 | 3s594ms       | 3.85       | 3m54.189s      | 251       
    3       | com.android.vending : com.android.vending/com.google.android.finsky.scheduler.process.mainimpl.PhoneskyJobServiceMain                                     | 10097 | 2s678ms       | 0.45       | 2m54.494s      | 29         
    4       | com.android.permissioncontroller : com.android.permissioncontroller/.permission.service.LocationAccessCheck$LocationAccessCheckJobService                 | 10173 | 2s662ms       | 0.06       | 2m53.469s      | 4         
    5       | ANDROID_SYSTEM : android/com.android.server.content.SyncJobService                                                                                        | 1000  | 1s844ms       | 0.03       | 2m0.213s       | 2         
    6       | com.google.android.apps.docs : com.google.android.apps.docs/.drive.appindexing.AppIndexingJobService                                                      | 10189 | 1s458ms       | 0.02       | 1m35.029s      | 1         
    7       | org.mozilla.firefox : org.mozilla.firefox/androidx.work.impl.background.systemjob.SystemJobService                                                        | 10177 | 1s1ms         | 1.03       | 1m5.232s       | 67         
    8       | GOOGLE_CALENDAR : com.android.calendar/com.google/[email protected]:android                                                                                   | 10136 | 695ms         | 0.17       | 45.331s        | 11         
    9       | com.google.android.apps.docs : com.google.android.apps.docs/com.google.android.libraries.internal.growth.growthkit.internal.jobs.impl.GrowthKitJobService | 10189 | 482ms         | 0.21       | 31.452s        | 14

    Most wakelocks seem bluetooth related.
    Code:
    Kernel Wakesources:
    Ranking | Name                 | Duration / Hr | Count / Hr | Total Duration | Total Count
    0       | 898000.qcom,qup_uart | 41s488ms      | 33.10      | 45m3.308s      | 2157       
    1       | hal_bluetooth_lock   | 41s487ms      | 29.90      | 45m3.212s      | 1948       
    2       | radio-interface      | 16s559ms      | 61.17      | 17m58.953s     | 3986       
    3       | IPA_WS               | 12s252ms      | 166.44     | 13m18.33s      | 10845     
    4       | IPA_RM12             | 10s689ms      | 48.51      | 11m36.521s     | 3161       
    5       | [timerfd]            | 4s173ms       | 189.28     | 4m31.961s      | 12333     
    6       | suspend_backoff      | 4s92ms        | 0.51       | 4m26.634s      | 33         
    7       | NETLINK              | 3s820ms       | 1956.66    | 4m8.955s       | 127492     
    8       | alarmtimer           | 2s560ms       | 1.26       | 2m46.849s      | 82         
    9       | qcril                | 2s559ms       | 486.46     | 2m46.75s       | 31697  
    
    Kernel Wakeup Reasons:
    Ranking | Name                                                               | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time
    0       | unknown                                                            | 12s296ms      | 37.95      | 13m21.237s     | 2473        |                   
    1       | 103:qcom,glink-smem-native-xprt-modem                              | 11s567ms      | 34.09      | 12m33.715s     | 2221        |                   
    2       | 667:qpnp_rtc_alarm                                                 | 2s48ms        | 4.88       | 2m13.448s      | 318         |                   
    3       | Abort:Pending Wakeup Sources: IPA_WS                               | 2s440ms       | 4.13       | 2m38.989s      | 269         |                   
    4       | 109:gsi:108:ipa                                                    | 2s403ms       | 3.48       | 2m36.623s      | 227         |                   
    5       | Abort:Pending Wakeup Sources: ipc000000a7_1299_qcrild              | 2s811ms       | 3.42       | 3m3.218s       | 223         |                   
    6       | Abort:Last active Wakeup Source: ipc000000a7_1299_qcrild           | 2s570ms       | 3.35       | 2m47.483s      | 218         |                   
    7       | 109:gsi                                                            | 1s792ms       | 3.28       | 1m56.771s      | 214         |                   
    8       | Abort:Some devices failed to suspend, or early wake event detected | 1s243ms       | 0.92       | 1m21.014s      | 60          |                   
    9       | 1012:dma-grant                                                     | 449ms         | 0.87       | 29.306s        | 57          |
    1
    Hi
    I've read a lot of hours about installing magisk on the xz2, but know I'm more confused as before. Does somebody know how to do this and give me a hint, how to do it right. Some sources to read, or a got how-to/manual? I did that sometimes before on a Sony Z1cm Sony Z5c, on a Samusung Tab, but alltimes using twrp. Now, twrp is not on the xz2, I installed LOS 18.1 with installation-guide on LOS-webside, i.e. with the LOS-recovery. Did not find any exolanation, how to change to twrp.

    Thank you for any hint. Joska
    1
    Magisk-Installation:
    (P.S.1: If your device has boot ramdisk, you can also install Magisk with a custom recovery, but it is not recommended)

    Tha'ts, why I am in doubt, what to do :)

    Did somebody flash a magisk.zip with lineageos.recovery. On different sides, i have read, a lot of bootloops are told of.
    The reason why I mentioned this is that I used this method myself and Ive had no problems so far.
    1
    @Haldi4803 How did you make that chart?
    phew... you never heard of battery historian?

    Simply create a Bugreport.zip file and upload it here: https://bathist.ef.lc/
  • 17
    Good news, we will go 18.1 official in next week.
    13
    2okPze5.png

    Code:
    #include <std_disclaimer.h>
    /*
    * 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.
    */
    About LineageOS
    LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
    which is designed to increase performance and reliability over stock Android for your device.

    All the source code for LineageOS is available in the LineageOS GitHub repo.
    And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    Official LineageOS website : http://lineageos.org
    About LineageOS Legal : http://lineageos.org/legal/

    Important Information
    1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
    2. This ROM will never work with any versions of Google Camera (GCam)!
    3. You need to flash Stock Android 10 before flashing this ROM.
    4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!


    Downloads Links
    LineageOS website

    Google Applications (optional):
    MindTheGapps
    Information: Flash the GApps before the first boot. If not, a clean flash is recommended.

    Flashing and updating
    How to flash

    Make sure you are upgrade to Official Android 10.0 from Sony
    Unlock bootloader is necessary.
    To disable AVB 2.0 using fastboot:
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    For vbmeta.img, you can download it anywhere you found.
    More steps see wiki

    Never flash oem from SODP!!
    If you flashed oem and meet any issues, I could only say you are a hanhan.

    Root access:
    Flash Magisk in recovery.

    Twrp:
    You could download it here: Link
    Code:
    fastboot boot twrp.img

    Issues and reports

    Report issues only if you are using the ROM kernel
    If an additional mod is installed, make sure it's unrelated, and mention it
    Make sure the issue wasn't discussed earlier in the threads
    Share a log of the error with CatLog for example

    Also thanks to:
    Olivier
    Luk1337
    The LineageOS Team
    The CyanogenMod Team
    The SODP Team
    Everyone involved in working and testing

    XDA:DevDB Information
    Lineage 18.1 for Xperia XZ2, ROM for the Xperia XZ2

    Contributors
    Sjll, Olivier
    Source Code: https://github.com/sony-sdm845

    Donation
    https://paypal.me/sjllls

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.9
    ROM Firmware Required: Official Android 10.0 firmware
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2020-11-27
    Last Updated 2021-05-26
    5
    Glad to tell everyone who are waiting for LineageOS 18.1.
    I uploaded the 20210515 build for Akari, but I don't have device to test.
    From the result on XZ3, everything works fine.
    Please test and feedback, if there is no bug, we will get official 18.1 support sson.
    5
    If so, why does installation of ROM and gapps in same routine lead to missing gapps? Why is it necessary to reboot after installation of ROM in recovery. Excuse me, but I feal, I'm to sill yto understand ;-(
    The XZ2 is an A/B device, i.e. it has two system partitions (one in slot A, one in slot B). This has the advantage that an update of the system can be done by the user while he is still using his device. No long pause for the update is required. Just a quick reboot at the end of the process to switch slots, and that's it.

    When such an OTA update comes in or a ROM gets installed via TWRP, then the update gets installed on the currently inactive slot. Let's assume slot A is currently active and we want to install a custom ROM, then the new ROM will get installed in the inactive slot B. This slot then gets marked as the one to boot from on the next restart. Now, to my understanding (otherwise people should please correct me), other zips, like GApps, always get installed into the currently active slot. Since slot A is still active, but you want to have the GApps installed for the new system in slot B, you first have to make slot B active. This can be done by a restart into recovery, because slot B was just marked as the one to become active on next boot. After the reboot into recovery slot B will be active and the installation of GApps will then be done for this now active slot B - which is exactly what we wanted.

    Btw., this procedure is this way not only for the XZ2 but for any A/B device.

    Hope this helps
    5
    So latest build is 18.0 from November?
    Seems a big pause in development.
    I will try building with the 18.1 sources on Lineage GitHub and see what happens.....

    Edit: Fixed the build errors but it wont boot and devs seem to have moved on.
    Back to 17.1 nightlies