[ROM][OFFICIAL][pioneer][10] LineageOS 17.1

Search This thread
By:
Advanced…
S

Son-Y

Member
Mar 14, 2016
25
1
Hi @ all

My XA2 cannot connect to a WiFi anymore (hidden SSID, MAC-filtering active). It used to work. Device is configured to use original MAC (which is whitelisted).
But from one day to the next it only states "… not in range"

Nothing changed at the WiFi setup.
Other devices as Laptop, other Smartphone, Tablet,… can still connect.

Anybody knows a solution?
Maybe somehow reset WiFi Settings/Saved Networks?
 
S

Son-Y

Member
Mar 14, 2016
25
1
Son-Y said:
Hi @ all

My XA2 cannot connect to a WiFi anymore (hidden SSID, MAC-filtering active). It used to work. Device is configured to use original MAC (which is whitelisted).
But from one day to the next it only states "… not in range"

Nothing changed at the WiFi setup.
Other devices as Laptop, other Smartphone, Tablet,… can still connect.

Anybody knows a solution?
Maybe somehow reset WiFi Settings/Saved Networks?
Click to expand...
Click to collapse

… seems to be a known issue but not fixed yet.

Found this https://gitlab.com/LineageOS/issues/android/-/issues/3045 (2 weeks ago) and this https://gitlab.com/LineageOS/issues/android/-/issues/2678 (4 months ago).
Both Issues still "open".

Hope it will get fixed soon 🤞

Or is there a known workaround I could use meanwhile?
 
samhhmobil

samhhmobil

Senior Member
May 25, 2017
472
239
Hamburg
Hi LuK1337

thanks for all your work in LOS for pioneer, and that for many years.

Now LOS 18.1 is OFFICIAL, but it's for many people not easy to migrate.

Poking around with LOS 18.1 for days/weeks showed me much trouble and many problems due to the new "Scoped Storage Policy". It's really awful.

So I would ask if there are any plans to have the LOS 17.1(!) even in future just only as a monthly security update. Maybe... as UNOFFICIAL again?

I expect, many pioneer users would like to stay with an actual Android10/LOS17.1.

Thank you very very much,
samhhmobil
 
Last edited:
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,824
17,793
Samsung Galaxy S III I9300
Moto G 2014
samhhmobil said:
Hi LuK1337

thanks for all your work in LOS for pioneer, and that for many years.

Now LOS 18.1 is OFFICIAL, but it's for many people not easy to migrate.

Poking around with LOS 18.1 for days/weeks showed me much trouble and many problems due to the new "Scoped Storage Policy". It's really awful.

So I would ask if there are any plans to have the LOS 17.1(!) even in future just only as a monthly security update. Maybe... as UNOFFICIAL again?

I expect, many pioneer users would like to stay with an actual Android10/LOS17.1.

Thank you very very much,
samhhmobil
Click to expand...
Click to collapse
No.
 
M

malerocks

Senior Member
Mar 6, 2018
549
114
samhhmobil said:
Hi LuK1337

thanks for all your work in LOS for pioneer, and that for many years.

Now LOS 18.1 is OFFICIAL, but it's for many people not easy to migrate.

Poking around with LOS 18.1 for days/weeks showed me much trouble and many problems due to the new "Scoped Storage Policy". It's really awful.

So I would ask if there are any plans to have the LOS 17.1(!) even in future just only as a monthly security update. Maybe... as UNOFFICIAL again?

I expect, many pioneer users would like to stay with an actual Android10/LOS17.1.

Thank you very very much,
samhhmobil
Click to expand...
Click to collapse
I guess the best one can do then is take the last released 17.1 and stay on that. But no more updates - just like it happens with an OEM.
 
A

alf-endy

Senior Member
Mar 8, 2015
73
16
malerocks said:
I guess the best one can do then is take the last released 17.1 and stay on that. But no more updates - just like it happens with an OEM.
Click to expand...
Click to collapse
I found a solution here
download.mokeedev.com

删库跑路 - 马丁龙猪的博客

刷机的时代其实早已落幕，迟迟下不定决心只是希望能让魔趣多存续一些时间，但该来的终究会来。 马丁龙猪今天决定删库
download.mokeedev.com download.mokeedev.com
I have been using it for a long time and it is updated daily
 
Q

QQ7Q

Member
May 21, 2020
10
0
I have a latest 17.1(last?) lineageOS at XA2. I have problem with MMS. When I receive MMS there is no picture/photo but link "Tap to download". Despite tapping nothing happend. Just "Downloading" message forever and my WIFI is ON.
How to make MMS download automatically? Is it a bug?
 
samhhmobil

samhhmobil

Senior Member
May 25, 2017
472
239
Hamburg
alf-endy said:
I found a solution here
download.mokeedev.com

删库跑路 - 马丁龙猪的博客

刷机的时代其实早已落幕，迟迟下不定决心只是希望能让魔趣多存续一些时间，但该来的终究会来。 马丁龙猪今天决定删库
download.mokeedev.com download.mokeedev.com
I have been using it for a long time and it is updated daily
Click to expand...
Click to collapse

OFF-TOPIC in this thread, but:

MoKee is not a real alternative.

Yes, it's updated daily, but:...

MoKee is a chinese variant, and...: they're collecting data from your phone (including your country and your mobile provider, for example) and they will give these data to (chinese or other) authorities if "legally" (whatever this means in such countries) requested by them. It is written in their policy that they will do so.

So it's a totally No-Go! It's a kind of a "spy-rom".

Just my 2¢,
samhhmobil
 
samhhmobil

samhhmobil

Senior Member
May 25, 2017
472
239
Hamburg
I found a "workaround" for staying with LOS17.1 on XA2 (for those people who cannot upgrade to 18.1 for different reasons).

It's "iodéOS" for XA2 (to find in this forum), based on LOS17.1, but focused on much better privacy. And it's yet on security patch level of 2021/05. Not frequently updated, but when it's necessary, and OTA-updates are working.

Nice. What else do I want?

samhhmobil
 
I

irgendwer2

Member
Jan 10, 2015
20
15
samhhmobil said:
I found a "workaround" for staying with LOS17.1 on XA2 (for those people who cannot upgrade to 18.1 for different reasons).

It's "iodéOS" for XA2 (to find in this forum), based on LOS17.1, but focused on much better privacy. And it's yet on security patch level of 2021/05. Not frequently updated, but when it's necessary, and OTA-updates are working.

Nice. What else do I want?

samhhmobil
Click to expand...
Click to collapse
Another alternative also based on LOS17.1:

/e/OS
https://e.foundation/e-os/

XA2 ROM install instructions and download links:
https://doc.e.foundation/devices/pioneer/install/
 
Last edited:
  • Like
Reactions: samhhmobil
samhhmobil

samhhmobil

Senior Member
May 25, 2017
472
239
Hamburg
LuK1337 said:
No.
Click to expand...
Click to collapse

samhhmobil said:
Hi LuK1337

thanks for all your work in LOS for pioneer, and that for many years.

Now LOS 18.1 is OFFICIAL, but it's for many people not easy to migrate.

Poking around with LOS 18.1 for days/weeks showed me much trouble and many problems due to the new "Scoped Storage Policy". It's really awful.

So I would ask if there are any plans to have the LOS 17.1(!) even in future just only as a monthly security update. Maybe... as UNOFFICIAL again?

I expect, many pioneer users would like to stay with an actual Android10/LOS17.1.

Thank you very very much,
samhhmobil
Click to expand...
Click to collapse

Thanks to LuK1337 for all his work in LOS for Xperia-XA2.

I understand, that his work is now and in future to LOS-18.1 (or, if coming, higher ones).

Nevertheless there are reasons to me, not to migrate to Android-11, but to stay in Android-10 (LOS17.1), but with actual security patches.

My solution is now to build LOS-17.1 frequently (monthly) by myself, as "UNOFFiCIAL". And, yes, it works as it should. My latest build of LOS-17.1 for pioneer is on security parch level of July 5th, 2021.

So, if someone else is interested in this unofficial ROM, please let me know.

samhhmobil
 
  • Like
Reactions: karenmcd
S

schmatzler

Senior Member
Sep 12, 2009
125
42
I was fed up with the horrible performance of Android 12 on my pioneer, so I made a new 17.1 build from the official sources last night.

So far, it runs extremely stable, just as I remembered it. You can get it here to save you the trouble of building it yourself:

index - powered by h5ai v0.28.1 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.28.1 (https://larsjung.de/h5ai/)
lichtmetzger.de lichtmetzger.de
 
  • Like
Reactions: sieghartRM and samhhmobil
You must log in or register to reply here.

Similar threads

LuK1337
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0
Replies
1K
Views
118K
E
exzombie
LuK1337
[ROM][OFFICIAL][pioneer][8.1] LineageOS 15.1
Replies
615
Views
76K
A
automizzer
LuK1337
[ROM][OFFICIAL][pioneer][11] LineageOS 18.1
Replies
272
Views
44K
M
malerocks
LuK1337
[RECOVERY][pioneer] TWRP Touch Recovery [OFFICIAL]
Replies
272
Views
55K
L
lobotron
LuK1337
[ROM][OFFICIAL][pioneer][12] LineageOS 19
Replies
106
Views
14K
karimin
karimin

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 22
    LuK1337
    LuK1337
    2okPze5.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.

    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 /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][OFFICIAL][pioneer][10] LineageOS 17.1, ROM for the Sony Xperia XA2

    Contributors
    LuK1337
    Source Code: https://github.com/LineageOS

    ROM OS Version: Windows 8 Mobile

    Version Information
    Status: Testing

    Created 2019-10-08
    Last Updated 2020-04-01
    View
    11
    LuK1337
    LuK1337
    [ 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. Reboot to recovery mode (both Lineage recovery and TWRP will work)
    6. Flash https://androidfilehost.com/?fid=4349826312261712574
    7. Profit?
    View
    7
    A
    action_papst
    PSA: Official downloads are back again.
    View
    6
    I
    irgendwer2
    malerocks said:
    Anyone have any clue on when the builds will resume? Is the hacking incident sorted?
    Click to expand...
    Click to collapse
    From Twitter (for the sake of completeness):

    LineageOS @LineageAndroid · 3. Mai

    Around 8PM PST on May 2nd, 2020 an attacker used a CVE in our saltstack master to gain access to our infrastructure.

    We are able to verify that:
    - Signing keys are unaffected.
    - Builds are unaffected.
    - Source code is unaffected.

    See http://status.lineageos.org for more info.
    Click to expand...
    Click to collapse
    https://twitter.com/LineageAndroid/status/1256821056100163584

    From Reddit (haggertk = a LOS director):

    haggertk · 7 days ago

    Well, it looked like the compromise was fairly contained (more details will be forthcoming in a blog post), but burning it all to the ground and rebuilding, using backups where appropriate, is better than hoping you fully cleaned it all.

    (...)

    No, we're in the process of rebuilding pretty much everything except signing - web, mail, gerrit, buildbots, mirrorbits, etc.

    If it's public and up right now it's because it was rebuilt.
    Click to expand...
    Click to collapse

    haggertk · 3 days ago

    Something completely independent from the salt exploitation happened somewhere around/just after April 23. The build trees on some of our build servers got "stuck" and weren't picking up submitted changes. Because the build date would be a lie, and it wasn't worth the effort to map which specific builds came off the "stuck" servers, we removed all builds for all devices after the apparent fault timeframe.

    (...)

    They aren't unsafe, just potentially with a codebase that is a few days older than what's represented in the build info.

    If the concern is in any way related to the infra exploit, I will repeat what we publicly stated a week ago - no completed builds, source code, keys, or signing servers were compromised in any way.

    (...)

    Did we run into problems? Sure, if you call people's actual paying jobs and personal lives a problem.

    Still in work, hoping for by the end of weekend, which is rather good for a "rebuild the entire world" kind of situation. If we miss the date, we miss the date.

    It's important to note that development was only halted for less than two days. And let's be honest, the vast majority of devices haven't had anything truly important submitted in a way that really needs a new build.
    Click to expand...
    Click to collapse
    https://www.reddit.com/user/haggertk/comments/
    View
    5
    LuK1337
    LuK1337
    [announcement]
    I just released new builds /w Nov SPL but there's a c-catch.
    If you're updating from 20191025-20191102 to newer build you'll need to do: `rm -rf /data/data/com.android.providers.downloads /data/data/com.android.providers.media /data/misc/wifi /data/misc_ce/0/wifi` in root shell (adb root && adb shell or adb shell × su if using Magisk or something)
    View

New posts