[ROM][OFFICIAL][pioneer][9] LineageOS 16.0 - Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other

[ROM][OFFICIAL][pioneer][9] LineageOS 16.0 - Sony Xperia XA2 ROMs, Kernels, Recoveries, & Other

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/pioneer
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-08-30
Last Updated 2020-02-28

How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?

Jozinek said:
Reccomended Gapps for this build?
Click to expand...
Click to collapse
dunno, just try any gapps you want.
btw I recommend downloading new build, I fixed wvm and camera no longer takes an eternity to launch.

Does it use 4.9 kernel or 4.4?

Casserole said:
Does it use 4.9 kernel or 4.4?
Click to expand...
Click to collapse
4.4

Unable to boot?
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.

techboy11 said:
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.
Click to expand...
Click to collapse
Stop flashing twrp lol.

LuK1337 said:
Stop flashing twrp lol.
Click to expand...
Click to collapse
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.

techboy11 said:
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.
Click to expand...
Click to collapse
Try fastboot -w reboot.

LuK1337 said:
Try fastboot -w reboot.
Click to expand...
Click to collapse
That worked. Now boots. Thanks for your help!

Thanks dude

Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!

Schritti said:
Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!
Click to expand...
Click to collapse
Yeah it's a temporary camera app until Snap is back so I won't bother figuring out what's wrong with it.

Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs

Schritti said:
Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs
Click to expand...
Click to collapse
No, I don't.

please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks

zsolt64555 said:
please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks
Click to expand...
Click to collapse
yeah i need to figure out a way to test it without leaving my room first.

LuK1337 said:
yeah i need to figure out a way to test it without leaving my room first.
Click to expand...
Click to collapse
THX your hard work!
Keep it Up.

Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.

zsolt64555 said:
Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.
Click to expand...
Click to collapse
i cant reproduce that, on youtube and twitch with 1080p 60fps everything is smooth, no lags and no glitches

Related

[ROM][UNOFFICIAL][instantnoodlep][10] LineageOS 17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
Instructions :
Download the latest build
$ adb reboot bootloader
$ fastboot -w (this will wipe your data)
$ fastboot flash recovery recovery.img
$ fastboot reboot fastboot
$ fastboot erase scratch
$ fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=314077
http://downloads.codefi.re/jdcteam/luk/lineage-17_1/instantnoodlep
https://sourceforge.net/projects/luk-lineageos/files/instantnoodlep/lineage-17.1
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodlep][10] LineageOS 17.1, ROM for the OnePlus 8 Pro
Contributors
LuK1337
Source Code: https://github.com/luk1337
ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-06-25
Last Updated 2020-11-20

Yessss, thanks mate. Any known bugs?

Great to see LOS builds popping up, thanks for the efforts.

"ROM OS Version: Windows 8 Mobile" dafuq? ?

LuK1337 said:
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.
Instructions :
Download the latest build and gapps
$ adb reboot bootloader
$ fastboot -w (this will wipe your data)
$ fastboot reboot fastboot
$ fastboot update lineage-*-UNOFFICIAL-instantnoodlep(-gms).zip
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=314077
http://downloads.codefi.re/jdcteam/luk/lineage-17_1/instantnoodlep
https://sourceforge.net/projects/luk-lineageos/files/instantnoodlep/lineage-17.1
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodlep][10] LineageOS 17.1, ROM for the OnePlus 8 Pro
Contributors
LuK1337
Source Code: https://github.com/luk1337
ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-06-25
Last Updated 2020-06-25
Click to expand...
Click to collapse
Can this be flashed in TWRP?

Can this be flashed in TWRP?

Burt Squirtz said:
Can this be flashed in TWRP?
Click to expand...
Click to collapse
No.

Are gapps included or do we need to flash separately?

blaze9090 said:
Are gapps included or do we need to flash separately?
Click to expand...
Click to collapse
Look at downloads list and answer this question yourself.

Running great on my end. Fingerprint is working too!! Awesome work Dev!

Flashing ROM via fastboot for the first time, getting the following error
PS E:\android\platform-tools_r30.0.3-windows\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 5.457s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 5.466s
PS E:\android\platform-tools_r30.0.3-windows\platform-tools>
PS: proceeded to flash the files anyway and it is stuck in OOS bootanimation.

Thanks for your work!

areyouanand said:
Flashing ROM via fastboot for the first time, getting the following error
PS E:\android\platform-tools_r30.0.3-windows\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 5.457s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 5.466s
PS E:\android\platform-tools_r30.0.3-windows\platform-tools>
PS: proceeded to flash the files anyway and it is stuck in OOS bootanimation.
Click to expand...
Click to collapse
What recovery are you using?

Panzer87 said:
What recovery are you using?
Click to expand...
Click to collapse
Latest TWRP, but was flashing through bootloader using the given commands.

bencozzy said:
Change file type to ext4 then try again
Click to expand...
Click to collapse
Format to ext4 from TWRP?

areyouanand said:
Format to ext4 from TWRP?
Click to expand...
Click to collapse
Only if you don't want to boot up.
You can also just flash recovery from my package and wipe data there.

LuK1337 said:
Only if you don't want to boot up.
You can also just flash recovery from my package and wipe data there.
Click to expand...
Click to collapse
Following are the steps i followed.
1. Reboot to bootloader from OOS.
2. fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
3. fastboot erase scratch > Filed with an error saying "check device console".
4. fastboot -w > wipe everything, with log provided in original post.
5 follow the instructions to flash all the images and reboot.
Lineage recovery boots, fastbootD works, gets stuck in OOS boot animation.
6. wipe/format from Lineage recovery> no profit.
When i tried to redo the step, it said "no such file/partition".
Did MSM and back to OOS. Please let me know if i have to do something differently.

areyouanand said:
Following are the steps i followed.
1. Reboot to bootloader from OOS.
2. fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
3. fastboot erase scratch > Filed with an error saying "check device console".
4. fastboot -w > wipe everything, with log provided in original post.
5 follow the instructions to flash all the images and reboot.
Lineage recovery boots, fastbootD works, gets stuck in OOS boot animation.
6. wipe/format from Lineage recovery> no profit.
When i tried to redo the step, it said "no such file/partition".
Did MSM and back to OOS. Please let me know if i have to do something differently.
Click to expand...
Click to collapse
>fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
Update your fastboot and then follow the guide again... If you'll be stuck feel free to join my irc channel and ask me there.
( also don't use twrp, either stay on OOS recovery for now or use lineage recovery )
( btw updated the guide to make user flash proper recovery+dtbo images before rebooting to fastbootd )

does magisk work?

areyouanand said:
Latest TWRP, but was flashing through bootloader using the given commands.
Click to expand...
Click to collapse
What I ended up doing was downloading 10.5.9 fastboot stock rom and pasted lineage images into there and ran the flash all file in there. Worked perfectly. I had the same issue.
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Nekromantik said:
does magisk work?
Click to expand...
Click to collapse
Working for me!

[ROM][OFFICIAL][voyager][11] LineageOS 18.1

[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?

First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.

hamirali said:
First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.
Click to expand...
Click to collapse
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.

LuK1337 said:
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.
Click to expand...
Click to collapse
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.

hamirali said:
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.
Click to expand...
Click to collapse
Are you on first or second build?

LuK1337 said:
Are you on first or second build?
Click to expand...
Click to collapse
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!

hamirali said:
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!
Click to expand...
Click to collapse
No idea about gapps, I don't have them on my current R devices.

LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
Successfully flashed and running well without any issues. Thanks!

LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!

hamirali said:
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!
Click to expand...
Click to collapse
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.

LuK1337 said:
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.
Click to expand...
Click to collapse
You were absolutely right...issue resolved. Thanks!

Currently on lineage-18.0-20201011 and enjoying the slide out volume panel and enhanced display size setting. Great!

Testing lineage-18.0-20201019 and all seems good. The only small issue I keep having is with the camera, it freezes.... but I do not use it that much anyway.

how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting

jacky51 said:
how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting
Click to expand...
Click to collapse
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.

I will wait for LineageOS 18.0 20201018 to work fine thanks

hamirali said:
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.
Click to expand...
Click to collapse
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.

LuK1337 said:
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.
Click to expand...
Click to collapse
OK, I was rebooting to recovery between flashing Lineage and gapps, but I was doing an initial wipe before flashing the newer build...

Everything works fine. Thanks for your work!

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 support Google Camera (GCam)! You need to flash Gapps at first.
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6.This ROM works fo both dual and single models.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link
Recovery: Link
Google Applications (optional):
NikGapps, MindTheGapps. OpenGapps.
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 11.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
You can install google's usb debug drivers.
2. Download Lineage Recovery from AFH above.
3. Put your device into fastboot by volume up key.
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot recovery
5. Sideload the ROM package.
6. If you are first time to flash LineageOS, Wipe data plz.
Gapps:
After flashing ROM via siddeload, Reboot to recovery, choose Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
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:
See this: Link
Gcam:
Recommond this one with my xml config.
Notice: You could only switch to front camera from telescope camera in Gcam.
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:
Cubbins
The SDOP team
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-18.1 for Xperia 10 II, ROM for the Sony Xperia 10 II
Contributors
Sjll
Source Code:
https://github.com/sony-sm6125
Donation
https://paypal.me/sjllls
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-01-16
Last Updated 2021-10-10

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Reserved

Will it work on the dual SIM version XQ-AU52?

ig2205 said:
Will it work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
Of course.

i wish we can have it for our xperia 5ii lol

Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?

dreDREb13 said:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
Click to expand...
Click to collapse
Flash directly, if you don't meet any issue, there is no need to wipe the data.
flyl0 said:
i wish we can have it for our xperia 5ii lol
Click to expand...
Click to collapse
Coming.

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Coming.
Click to expand...
Click to collapse
It would be even better Resurrection Remix
But I'm glad LOS 18.1 is coming, can't wait to try it!

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Click to expand...
Click to collapse
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?

erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?

dreDREb13 said:
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
Click to expand...
Click to collapse
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.
ig2205 said:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?
Click to expand...
Click to collapse
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Will this rom be rebased on the Android 11 stock ROM sources once we have them?

You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?

KriiXOne said:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
Click to expand...
Click to collapse
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
ig2205 said:
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?
Click to expand...
Click to collapse
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.

Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.

Sjll said:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.
Click to expand...
Click to collapse
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.

ig2205 said:
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Post the result here plz.

Sjll said:
Run
Code:
fastboot getvar all
Post the result here plz.
Click to expand...
Click to collapse
Is that the point?

So I installed and everything booted up fine, but I hit a couple snags.
One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.
Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.
Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.
EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...
All looks good otherwise and this is turning out great!

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy Tab S6 Lite Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl/tree/lineage-19.1

Requirements:
Any R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me

I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!

fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.

Sim card dont work, IMEI dont show, gapps cant install. Any ideas?

electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?

Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!

Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S

Hi, it seems audio is not working.
It's just me?
Any help please.
M

minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9

Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!

guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab

langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.

Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.

First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware

how is newest recovery

Screenshots please

Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.

lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.

[ROM][UNOFFICIAL][12][OTA][OSS] LineageOS 19.1 for Galaxy S9/S9+ Exynos

Requirements:
Latest firmware
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk

This build does not use the stock vendor, instead it's built on top of new trees which have been worked on for some time. The source is on our github, link in OP. You also get a few neat features like fingerprint gestures, and bixby button that actually works with both normal and long press.
I suggest using OpenCamera since stock one has some issues with flash.
These builds are signed with our release keys.
star2lte and crownlte support will come a bit later as i don't own the devices, but they will be supported eventually.
THESE BUILDS HAVE FORCE ENCRYPTION ENABLED, AND ONLY LINEAGE RECOVERY IS SUPPORTED. THESE THINGS WILL NOT CHANGE. IF YOU DON'T USE LINEAGE RECOVERY, AND SUFFER FROM DATA LOSS, DON'T COMPLAIN HERE.

Build uploaded, enjoy

Woah!!! Nice

How did you get OTA to work, I wanna try it too

nice
will try
been trying your work in PE, congrats on that and now curious to try this rom,
if I understood correctly this is your work along with Rob now?
Keep up the good work and thanks once again for reviving our devices

does LTE is supported in this ROM ?

quakze said:
does LTE is supported in this ROM ?
Click to expand...
Click to collapse
LTE/4G works with this ROM

Hey, thank you very much for this ROM, it's really smooth! Everything works except my second SIM.
For the first release this is pretty nice... and ... this is my first experience with Android 12 / LineageOS 19

star2lte build is up as well, find it at the link in the OP

BIG THANKS to the devs... NOW my S9+ will get a new life.
Edit: Did a test with 2 SIMs and only SIM1 is detected - no SIM2 so far... the Rest is really great work!!!

Great Job, Fresh install and my S9+ is (almost) Brand New!
I installed it with Samsung tool Odin recovery Lineage
Installing the rom with a sd card in de recovery, no sideload use! That works great!
Keep up the great work!

Razuuu said:
LTE/4G works with this ROM
Click to expand...
Click to collapse
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable

quakze said:
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable
Click to expand...
Click to collapse
See my picture

Feels damn fast but no second sim in S9

Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?

Mr-Dutch said:
Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?
Click to expand...
Click to collapse
I don't know the reasons (time/effort?), but TWRP doesn't support encrypted partitions which this rom forces.

Is there a list of working/non working features in this rom?

I just wanna say : This ROM is amazing, is blazing fast, super easy install flow, no problems at all; I have no seconds SIM to test however, in my phone the "App Switcher" from the bottom nav bar isn't working, I'm the only one? Keep the amazing work @DeHuMaNiZeD

Database Develop

welcome