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

[ROM][11] LineageOS 18.1 [OFFICIAL]

Search This thread

zpunout

Senior Member
Aug 26, 2015
59
12
Samsung Galaxy S5
Moto G5 Plus
can we consider LOS as a good daily driver for our xz2c now ?
I'm still on 52.0.A.11.3 but i miss magisk and can't find a boot.img..
I'm considering updating from LineageOS 17.1 with functioning stock camera (with help from Magisk and SELinux switcher) to a much more secure LineageOS 18.1 without Magisk. The only thing holding me back is that I'll lose the stock camera's enhanced functionality. Any news about whether it's technically possible to port Semc Camera to work on LOS18.1 without the need for root?
 
  • Like
Reactions: mailx

jontis

Member
Jul 1, 2015
12
0
can we consider LOS as a good daily driver for our xz2c now ?
I'm still on 52.0.A.11.3 but i miss magisk and can't find a boot.img..
I'd say no. While I do love both the x2zc, and the LOS concept, I have been suffering for a long time from poor connectivity, both mobile data and phone calls. I have issues registered on github about that if you want a more detailed description. As it is now, I'm looking into getting a pixel 4a instead.
 

landsome

Senior Member
May 4, 2015
379
95
I'd say no. While I do love both the x2zc, and the LOS concept, I have been suffering for a long time from poor connectivity, both mobile data and phone calls. I have issues registered on github about that if you want a more detailed description. As it is now, I'm looking into getting a pixel 4a instead.
In my case, LOS works much better than stock. My stock phone would fail to reconnect to the tower in some cases if it lost connectivity for a short while. It's a bug other people had, which sony failed to solve for years, and LOS resolved. Plus better battery life and customization.
 
  • Like
Reactions: userx404
I'd say no. While I do love both the x2zc, and the LOS concept, I have been suffering for a long time from poor connectivity, both mobile data and phone calls. I have issues registered on github about that if you want a more detailed description. As it is now, I'm looking into getting a pixel 4a instead.
Same here. I have to give up los since I can barely use mobile network, which is definitely essential to me. Only stock works fine.
 

zpunout

Senior Member
Aug 26, 2015
59
12
Samsung Galaxy S5
Moto G5 Plus
Same here. I have to give up los since I can barely use mobile network, which is definitely essential to me. Only stock works fine.
Using my H8324 variant with no connectivity issues. I did have a few other strange bugs after first boot because I installed over LOS 17.1 but they were resolved after going into the menu and doing a factory reset.
 
Yes, make sure to install over stock (or at least full reset).
Of course I did a clean install over stock (52.1.A.3.49). The issue was still there. I'm pretty much sure there's nothing to do with clean/dirty flash and I did it right. sjll and I tested about this few months ago and, so far, no result, at least for the carrier I'm using (China Unicom).
 

zpunout

Senior Member
Aug 26, 2015
59
12
Samsung Galaxy S5
Moto G5 Plus
Of course I did a clean install over stock (52.1.A.3.49). The issue was still there. I'm pretty much sure there's nothing to do with clean/dirty flash and I did it right. sjll and I tested about this few months ago and, so far, no result, at least for the carrier I'm using (China Unicom).
Which frequency bands are being used by China Unicorn? Maybe the answer can be found by looking at that?
 

jontis

Member
Jul 1, 2015
12
0
I'm curious about one thing, I've been trying to get vowifi to work.
The way I've seen it recommended is turn on vowifi in the settings, which I find, and it shows vowifi turned on.
Then set it to airplane mode and turn on wifi. You are then supposed to be able to make calls by vowifi.
However, the SIMs are disabled, and the settings are not accessible anymore. Has it lost it's knowledge about the phone numbers and that identity? Then how is it supposed to make the vowifi call? I only get "mobile network not available", and no option to select any of the 2 SIM accounts it has. Am I missing something or is this an issue?
 

Cerhio

Senior Member
Feb 25, 2013
205
29
Are there any issues with updating via the built in updater? I've noticed it doesn't ask me to restart the phone after the install.
 
I'm curious about one thing, I've been trying to get vowifi to work.
The way I've seen it recommended is turn on vowifi in the settings, which I find, and it shows vowifi turned on.
Then set it to airplane mode and turn on wifi. You are then supposed to be able to make calls by vowifi.
However, the SIMs are disabled, and the settings are not accessible anymore. Has it lost it's knowledge about the phone numbers and that identity? Then how is it supposed to make the vowifi call? I only get "mobile network not available", and no option to select any of the 2 SIM accounts it has. Am I missing something or is this an issue?
Curious as well. But seems our issues are not the same. I DO HAVE signal and SIM(s) enabled, LTE enabled, but I just can't connect to the internet, even just resolving domain names will fail (e.g. nslookup in termux), no connection at all. I even thought if it's LOS set DoH default and the default server doesn't work here in China so I turned it off, however nothing changed... From then I'm sure there's something wrong with the modem/los network stack/something else.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    has anyone else been having touch issues
    I had it in the past. Thought it was caused by an old scratch. I replaced the LCD front a few month ago. No issue so far.
    1
    Which frequency bands are being used by China Unicorn? Maybe the answer can be found by looking at that?
    Yesterday I asked China Unicom to replace my SIM card since I suspect it might be faulty, and enabled a service called "visited place access" (translated from Chinese via DeepL), without that my IP is where this card belongs to but apparently I'm far away from that city, and now I can get the IP from the city I'm at right now. And after replacing the card, my LTE connection seems fine now. @jontis maybe you should also try a SIM card replacement.
  • 10
    The first official 18.1 build is up, enjoy: https://download.lineageos.org/xz2c
    10
    A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
    7
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png


    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.

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

    NOTE
    Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
    Hint: "It doesn't work" is not a bug report and posts like this will be ignored.


    KNOWN ISSUEs
    • The Sony stock camera does not work at the moment.

    INFO
    This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.

    DOWNLOAD
    Official builds

    NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.

    All unofficial builds

    INSTRUCTIONS
    Just flash the builds as usual. Make sure to be on the latest stock firmware.

    SOURCE
    LineageOS
    Kernel
    4
    CHANGELOG
    20210516:
    - fixed WiFi display/screen casting
    - addressed performance issues and lags

    20210515:
    - updated to 18.1
    - fixed remaining most of the bugs
    - set SELinux to enforcing

    20201128:
    - fixed NFC

    20201127:
    - initial public release.
    3
    After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.

    General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).

    Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
    Use a STOCK TWRP
    Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.

    Newflasher:
    I used v42, probably newer versions work, too, try not to use an older version

    Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.

    Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.

    Now let's get to the process of flashing LOS:

    Step 1 - Flash an original working SONY image into Slot A:
    Boot into fastboot mode, so the blue light is on.
    Type:
    fastboot reboot bootloader
    (Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).

    fastboot --set-active=a
    fastboot reboot bootloader

    You can check that Slot A is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: a

    Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.

    Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.

    When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.

    You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.

    Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.

    Step 2 - Flash an original working SONY image into Slot B:
    Boot into fastboot mode, so the blue light is on.
    Type (similar to Step 1):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    You can check that Slot B is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: b

    WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.

    Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.

    Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.

    When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.

    You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.

    At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.

    Step 3 - Boot the original SONY image up to the home screen where the apps show:

    Actually you should be in Slot B already, but if you are not:
    Boot into fastboot mode, so the blue light is on.
    Type (similar to Step 2):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    You can check that Slot B is active by typing the command
    fastboot getvar all
    in the output check the line current slot active: b

    Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).

    Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.

    Power off your phone.

    Step 4 - Flash twrp into Slot B

    Type (similar to Step 2):
    fastboot reboot bootloader
    fastboot --set-active=b
    fastboot reboot bootloader

    fastboot flash boot twrp.img

    This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.

    Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.

    Boot your TWRP in Slot B.

    WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.


    Step 5 - Flash LOS into Slot A

    Once TWRP is running, go to Wipe.

    WARNING: DO NOT perform factory reset.

    Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'

    WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.

    Go back to TWRP home screen.

    From there go to Advanced and from there to ADB Sideload.

    From the computer start installing your LOS image (sideload).

    On the computer type:

    adb sideload <Your LOS image>.zip.

    ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.

    Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c

    Download the zip file, don't unpack it, use adb sideload to upload the zip file.

    Forget about the Recovery image on the LOS homepage. You don't need it.

    When flashing completes, you can wipe Delvic Cache.

    WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.

    Do NOT install the TWRP app, skip this step.

    Reboot

    Step 6 - Boot LOS

    LOS is in Slot A, TWRP is in Slot B.

    You can alternate between the slots from fastboot.

    fastboot reboot bootloader
    fastboot --set-active=a
    fastboot reboot bootloader

    A reboot should boot LOS.

    ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.

    Let me know as feedback, if I can clarify better or if this description is ok.