[ROM][OFFICIAL][pioneer][12] LineageOS 19

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,711
17,507
Samsung Galaxy S III I9300
Moto G 2014
2okPze5.png


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 organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.

Instructions :
Downloads :
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)
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:
 
Last edited:

aztorius

New member
Feb 25, 2022
1
0
Thank you !
Just tested lineage-19.0-20220219_132428-UNOFFICIAL-pioneer.zip

A pretty good start for Android 12.

Tested and working :
- fingerprint sensor
- WiFi
- video playback on youtube with default browser
- camera front and rear + video recording + flash light
- USB MTP
- Gyroscope

Comments :
- audio playback working but crackles a bit when at maximum
- The settings menu overlaps the 3 buttons controls
Screenshot_20220225-175234_Paramètres.png


Not tested :
- SIM card and everything related (calls, SMS, ...)
- Bluetooth
- GPS
- GApps
And other things.

Really love to see Android 12 on this one.
 

AsonyUser

New member
Dec 31, 2019
2
0
Android 12 on my sony xa2 will not boot past the lineage os logo even after changing a/b and factory resetting it is there a fix?
 

lecler_i

New member
Oct 26, 2017
1
0
Rolling the lineage-19.0-20220301_131228-UNOFFICIAL-pioneer.zip with firmware 50.2.A.3.77

Tested and working:
- Wifi
- 4g / lte
- rear camera

Flakie :
- selfie camera is not working when switching from back, but then is working

When switching from back to selfie camera :

Code:
[  627.762250] type=1400 audit(1646511939.837:2926): avc: denied { read } for comm="[email protected]" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[  627.763506] type=1400 audit(1646511939.837:2927): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[  627.763858] type=1400 audit(1646511939.837:2928): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[  627.782361] PU: mGpioCnt[4]: 1
[  627.793963] PU: mGpioCnt[5]: 1
[  627.817922] msm_cci_init:1439: hw_version = 0x10060000
[  627.818168] msm_sensor_match_id CAM_ID_8M: 0
[  627.823084] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
[  627.853709] msm_vfe47_process_error_status: camif error status: 0x264
[  627.853760] 0x0000: 00000001 00000040 00000000 098f0cbf
[  627.853769] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[  627.853779] 0x0020: ffffffff ffffffff 0014095d 00000264
[  627.853786] 0x0030: 00000000 00000001 00000001
[  627.953623] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[  627.953655] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[  627.953689] overflow processed
[  627.988483] msm_isp_axi_halt: VFE1 Bus overflow detected: start recovery!
[  627.988686] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 1
[  627.989818] msm_ispif_restart_frame_boundary: ISPIF reset hw done, Restarting
[  628.020401] msm_vfe47_process_error_status: camif error status: 0x264
[  628.020452] 0x0000: 00000001 00000040 00000000 098f0cbf
[  628.020462] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[  628.020471] 0x0020: ffffffff ffffffff 0014095d 00000264
[  628.020479] 0x0030: 00000000 0000000f 0000000f
[  628.053631] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[  628.053667] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[  628.053700] overflow processed
[  628.910196] FG: fg_somc_get_real_temp: batt:257 aux:-2730 -> real battery temp:257
[  628.910263] FG: fg_somc_jeita_step_charge_work: [Charging] RTEMP:257 IBATT:-40mA VBATT:3981mV VCELL:3982mV VCELL_MAX:4034
[  628.910340] PMI: smblib_somc_handle_jeita_step_fv: set fv:4380000
[  630.264121] q6asm_callback: payload size of 8 is less than expected.
[  630.422670] msm_private_ioctl:Notifying subdevs about potential sof freeze
[  630.422783] MSM-SENSOR-INIT msm_sensor_init_subdev_ioctl:119 default\x0a
[  630.422965] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0xff
[  630.423006] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR0 = 0x0
[  630.423021] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR1 = 0x1
[  630.423037] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR2 = 0x0
[  630.423051] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR3 = 0x20
[  630.423065] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR4 = 0x0
[  630.423079] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR5 = 0x0
[  630.423094] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR6 = 0x4
[  630.423109] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR7 = 0x0
[  630.423123] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR8 = 0x80
[  630.423138] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR9 = 0x40
[  630.426309] type=1400 audit(1646511942.497:2929): avc: denied { read } for comm="CAM_mct_freeze" name="clk" dev="debugfs" ino=4921 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:debugfs:s0 tclass=dir permissive=0
[  630.454176] ispif_process_irq: PIX0 frame id: 2383
[  630.488551] ispif_process_irq: PIX0 frame id: 2384
[  630.521908] ispif_process_irq: PIX0 frame id: 2385
[  630.555239] ispif_process_irq: PIX0 frame id: 2386
[  630.587439] ispif_process_irq: PIX0 frame id: 2387


When closing camera app, re-opening, selfie is working but following trace :
Code:
[  520.236493] type=1400 audit(1646511832.307:2918): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[  520.238093] type=1400 audit(1646511832.307:2919): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[  520.238408] type=1400 audit(1646511832.307:2920): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[  520.252543] PU: mGpioCnt[4]: 1
[  520.263611] PU: mGpioCnt[5]: 1
[  520.290503] msm_cci_init:1439: hw_version = 0x10060000
[  520.291319] msm_sensor_match_id CAM_ID_8M: 0
[  520.362722] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800


Had a issue on first boot after flash :
- top menu was not acessible (nothing when pulling down)
- only back button was showing on the "virtual button" down

Fixed after a reboot.

You mind sharing your build configs? You are rolling this kernel : https://github.com/luk1337/android_kernel_sony_sdm660/tree/lineage-19.0

With main branch 19.0 of lineage official repo ?
 
Last edited:
Hi
Thx for making Android 12 possible on my XA2 :)
Anyway i somehow cant connect properly to wifi!

So i logged into my wifi in the setup (I installed NikGapps) but even tho he says "Connected" he doesnt let me go to the second step of setup. I already tried different Wlans but still nothing.

Hope someone can help me. ;)
 

k2helix

Member
Jan 30, 2022
7
1
Hello

Just installed the latest version available (19.1 - 26/03) and it worked fine. The problem is that, when I went to TWRR to flash gapps, TWRP did not ask for the device encryption password and thus it did not work. I don't know how to proceed.
 

k2helix

Member
Jan 30, 2022
7
1
Ok so I installed the latest version and installed NikGapps through lineage recovery. It works indeed!
Tested:
SIM and SMS
WiFi
Camera
Gapps (I had some problems with Bromite System Webview but disabling the module solved it)
Torch
Location
Cell data
Magisk canary

I miss an option to select the system accent instead of the adaptive one that selects it based on the wallpaper, but everything else is fine.
TWRP still does not ask for a pin and the data keeps encrypted so it is not usable, but as I said flashing through lineage recovery works (at least for gapps)
 

kereth

Member
Oct 2, 2014
12
2
Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.
 

Hiero

Senior Member
Jun 29, 2007
72
17
Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.
Everything you asked for works absolutely fine without any issues.
You don't need gApps for that.

I can't say how active the developers are, but an update was released just yesterday (16.04)
Thanks a lot @LuK1337
 
  • Like
Reactions: kereth

malerocks

Senior Member
Mar 6, 2018
528
110
Now that LineageOS 19 is officially out, will this thread be converted to one for the official build or will there be a separate thread that we have to join?
 

malerocks

Senior Member
Mar 6, 2018
528
110
Don't know about you guys but I have a mixed feeling about the theming in Android 12. Anyone know if there is a way to choose the colour I want the system to use like we had in the previous versions?
 

samhhmobil

Senior Member
May 25, 2017
452
231
Hamburg
@LuK1337

LOS 19.1... Great ROM, and now it's official. Have many thanks for that!!

One (first?) question:
I see, the camera app has changed from former snap-camera to standard android-camera now. How can I switch this camera into silent mode? I can't find any switch for that.

Or, is it possible to have snap-camera even in LOS 19.1, as in former LOS-releases?

Thanks a lot,
samhhmobil
 

emc02

Senior Member
Jul 4, 2010
238
70
Vienna
Should I clean flash updates or can I dirty flash them without losing any data?
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.

I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?

has anyone tried to go to TWRP after updating?
 

malerocks

Senior Member
Mar 6, 2018
528
110
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.

I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?

has anyone tried to go to TWRP after updating?
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.
 

emc02

Senior Member
Jul 4, 2010
238
70
Vienna
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.
ok, with 18.1 I had issues using the LOS recovery, so I flashed always with TWRP. But I've installed it now on the other partition with LOS recovery and it's working well.
So you think a normal OTA Update of LOS will work now out of the box?
 

malerocks

Senior Member
Mar 6, 2018
528
110
Yes. I tried an OTA today and it went all fine. I never had issues with OTAs with the previous LineageOS version either.
 

samhhmobil

Senior Member
May 25, 2017
452
231
Hamburg
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
[...]Has anyone tried to go to TWRP after updating?
You're right, since installing LOS 19.1, TWRP (even the newest one, but the older ones too) cannot decrypt the user data.

samhhmobil
 
  • Like
Reactions: emc02

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    2okPze5.png


    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 organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.

    Instructions :
    Downloads :
    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)
    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:
    1
    Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
    Is the ROM still under development?
    Thank You in advance.
    Everything you asked for works absolutely fine without any issues.
    You don't need gApps for that.

    I can't say how active the developers are, but an update was released just yesterday (16.04)
    Thanks a lot @LuK1337
    1
    I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
    I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
    I was using the latest version of TWRP (2.6.1_9)
    [...]Has anyone tried to go to TWRP after updating?
    You're right, since installing LOS 19.1, TWRP (even the newest one, but the older ones too) cannot decrypt the user data.

    samhhmobil
    1
    Bit confused and wondered if I am I right in thinking I should use these instructions to upgrade from 18.1. Never upgraded a phone quite this new before. :)
    I would recommend that you start from scratch i.e. reset the phone, clear everything and start
    1
    Hi, where can I download the firmware 50.2.A.3.77? Can I just flash it using LOS recovery?
    Mine is still 50.1
    You can use XperiFirm to Download and Newflasher to install the firmware inclusive baseband.
    I wrote a short summary about flashing the XA2 - however reading the newflasher thread isn't false to know what you're doing.

    After flashing the vanilla Sony firmware and installing LineageOS right after it, I had the problem that my SIM card wasn't detected. So boot at least one time into the Sony firmware/Android before flashing LineageOS.