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

[ROM][OFFICIAL][pioneer][9] LineageOS 16.0

Search This thread

wtflawlxd

Member
Sep 4, 2014
28
8
OK, I see.

Does really nobody else has seen this issue?

samhhmobil

I've got a similar problem on a Hyundai ix20 2010: the XA2 connects automatically to the car's oem stereo, but no sound gets out from it. I have to disable and enable again the XA2 bluetooth, and connect it again to the car's stereo. After that it works fine for hours, even though sometimes it pauses the music for a moment.
 

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
I've got a similar problem on a Hyundai ix20 2010: the XA2 connects automatically to the car's oem stereo, but no sound gets out from it. I have to disable and enable again the XA2 bluetooth, and connect it again to the car's stereo. After that it works fine for hours, even though sometimes it pauses the music for a moment.
That seems to be another issue. For me the BT connection itself is stable with media and contacts. Just the "phone"-connection does not work as it should.

samhhmobil
 

inestion

Senior Member
Jun 19, 2012
216
42
You're right, of course, but... the 5GHz net of the AVM FritzBox (7390 and very stable) reaches not further as 5m around... sigh

And even the Miracast Dongles I have are working only in this mode.

But your build from 2020-03-02 did work really great without any trouble! (...and now it doesn't, sigh)

samhhmobil

To be honest I've bought a fritzbox 7590 last summer and I've had the wifi on the xa2 disconnecting randomly for months, so I'm not sure that it was broken on a recent build.
 

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
To be honest I've bought a fritzbox 7590 last summer and I've had the wifi on the xa2 disconnecting randomly for months, so I'm not sure that it was broken on a recent build.
Maybe you're right (I'm new to the XA2 since two weeks or so), and maybe I've had a bit luck only, with the build of20200302, that WiFi (and especially WiFi-Direct) was stable for a few hours... but now it randomly disconnects every few minutes... either with 2.4GHz or with 5GHz too.

I tried again with the same Fritzbox,:
HTC One M7 (LOS 14.1): stable connection
HTC One M7 (LOS 17.1): some disconnects
Xperia Z C6603 (LOS 15.1): really stable connection
2nd XA2 (even LOS 16): disconnect every few minutes too

So the Fritzbox is OK (my other WiFi-Devices — PC's, TV, etc. — are running stable since months/years), and it really seems to be a bug in LOS 16 (and possible 17.1 too?).

Just my 2¢,
samhhmobil
 

inestion

Senior Member
Jun 19, 2012
216
42
So the Fritzbox is OK (my other WiFi-Devices — PC's, TV, etc. — are running stable since months/years), and it really seems to be a bug in LOS 16 (and possible 17.1 too?).

If I recall correctly it happens on the stock rom too, I'm pretty sure I've tried. I agree that it doesn't seem like any other device is affected, I don't have any IoT device but other smartphones (both android and ios) are fine.
 

Meloferz

Senior Member
May 8, 2014
395
100
Asunción
Sony Xperia 10 II
Hi @LuK1337, CTS is failing after March security patch update, is there any way to fix it? IMG_20200312_150759.jpg

Enviado desde mi H3123 mediante Tapatalk
 

samhhmobil

Senior Member
May 25, 2017
349
187
Hamburg
Hi @LuK1337, CTS is failing after March security patch update, is there any way to fix it?
Look in the thread "Magisk General Support / Discussion".

As published there... Google has changed the methods to detect rooted devices, and from now on it is (and will be) impossible to hide rooted phones from this detection.

Game over!

We have to live with the fact, that devices with open bootlader and custom ROMs, rooted or not rooted, will not pass the SafetyNet check anymore, from now on.

samhhmobil
 
  • Like
Reactions: Meloferz

Meloferz

Senior Member
May 8, 2014
395
100
Asunción
Sony Xperia 10 II
Look in the thread "Magisk General Support / Discussion".

As published there... Google has changed the methods to detect rooted devices, and from now on it is (and will be) impossible to hide rooted phones from this detection.

Game over!

We have to live with the fact, that devices with open bootlader and custom ROMs, rooted or not rooted, will not pass the SafetyNet check anymore, from now on.

samhhmobil
I don't know what happened, but today is passing... I don't have Magisk, or root, or whatever... Just stock LOS 16 and GAPPS... I just disabled developer options [emoji848] But yesterday wasn't passing CTS
IMG_20200313_111324.jpg

Enviado desde mi H3123 mediante Tapatalk
 
  • Like
Reactions: Untot

malerocks

Senior Member
Mar 6, 2018
440
103
I noticed that for the last few builds, the LineageOS site also has a link to a recovery. Does this mean that we are now supposed to start using this one instead of TWRP?
 

Attachments

  • Screenshot_20200401-183428_Via.png
    Screenshot_20200401-183428_Via.png
    190.9 KB · Views: 120

Top Liked Posts

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


    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 :
    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
    14
    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?
    7
    @Marteng69 here is what i did -> i was stucked on pie + flickering screen (model h3113):

    1. i used emma (https://developer.sony.com/develop/open-devices/get-started/flash-tool), just install and run it, boot your phone in flash mode (vol down + usb connect = green light). then the app will recognize your phone (assuming you have drivers installed) and give you phone info. on the right side download and flash offered firmware (at the moment there is the uk oreo one, download it and you'll have it in case it's replaced with pie). flash the complete firmware (the "Software Update Content Erase" image) and reboot after flashing completed

    2. boot the phone, let it boot up for a few minutes then turn it off with holding power + vol up for a few secs (let it vibrate 3 times to make sure it's off)

    3. then boot it in fastboot mode (vol up + usb connect = blue light) and then via cmd run "fastboot boot 1d66175c6ce8e04865d041cbcac8ba3013a02b1e.img" (please check your exact .img name)

    4. that's it, the phone should boot (normal looking) twrp and then reboot your phone and... say thanks to @LuK1337 ;)
    7
    Hello Luk,

    are you going to develop LineageOS 17 for this Device?

    Until 50.2.* kernel source is out I'm not planning to do anything.

    btw see https://talk.sonymobile.com/t5/Kernel/50-2-A-0-400-kernel-source/td-p/1390917 ^^
    6
    Yes, 2.4 works fine. I'm 100% sure that 5GHz used to work tho, but nevermind. At least now I have hotspot working lol

    ...yeah I booted some old ass kernel HEAD and it works there. Looks like i'm going to have fun time finding the change that broke it...

    EDIT: Should be working again in next builds ^.^