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

[zupert]

Check with your network provider. Some of them don't allow WiFi tethering.

My network provider does not block it: i had it working before and it still works today on another lineage 16 phone.

 

[malerocks]

My network provider does not block it: i had it working before and it still works today on another lineage 16 phone.

Just found that some people on the LineageOS thread for the oneplus 3 are facing the same issue as well. Maybe it is a recent issue in LineageOS rom then

 

[Rhino Cracker]

backup TA before unlock?

Hi, I'm a little bit confused about the processes until the phone is flashed.

The installation manual clearly states, that you should backup your Trim Area Partition (in short TA) before unlocking the bootloader

WARNING: Unlocking the bootloader will erase all data on your device! This also includes your DRM keys, which are stored in the Trim Area partition (also called TA). Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed. If you wish to backup the TA partition first, you can find tutorials related to your device on the internet.

I cannot find useful informations on how to backup and restore it (including the DRM keys).
The most promising and detailed article just told that he gave up on trying to backup DRM keys. Which, in his words, will disable his device e.g. from playing back Netflix in more than 480p.

Thus I'm cutting off this project with the decision to not back up the DRM keys. However, I will use TWRP Recovery to back up the TA partition (minus DRM keys) after unlocking the bootloader.

So, how do I backup and restore the Trim Area Partition including DRM Keys on my XA2 Dual?
Or - if it is not necessary - why does the official installation manual say, that I have to ensure, that I backed it up, before unlocking the bootloader?

 

[xleng]

Hi, I'm a little bit confused about the processes until the phone is flashed.

The installation manual clearly states, that you should backup your Trim Area Partition (in short TA) before unlocking the bootloader


I cannot find useful informations on how to backup and restore it (including the DRM keys).
The most promising and detailed article just told that he gave up on trying to backup DRM keys. Which, in his words, will disable his device e.g. from playing back Netflix in more than 480p.



So, how do I backup and restore the Trim Area Partition including DRM Keys on my XA2 Dual?
Or - if it is not necessary - why does the official installation manual say, that I have to ensure, that I backed it up, before unlocking the bootloader?

Obviously, when unlocking the boot loader and installing a custom, you're leaving the application scenario as envisaged by the manufacturer, and in the case of most Sony devices (including the XA2), when unlocking the bootloader, the DRM keys are erased and thus the functionality of using the Sony's proprietary photo processing algorithms is lost. This is not really recoverable (at least not without sending the device back, don't know if Sony repair can do this in exchange for some money) and the instructions include a warning of this effect.

Now, in order to backup the keys, you would need to have root access first. Personally, I'm not aware that anyone in the community has identified / developed a rooting script or app for the Sony Xperia XA2, in order to gain root access prior to unlocking the bootloader.
Of course after unlocking the bootloader it would be relatively easy to enable root, but then it's already too late.
I think most people here who have installed Lineage have simply accepted the consequence to lose this functionality. Of course this is at your own risk.

 

[Rhino Cracker]

Obviously, when unlocking the boot loader and installing a custom, you're leaving the application scenario as envisaged by the manufacturer, and in the case of most Sony devices (including the XA2), when unlocking the bootloader, the DRM keys are erased and thus the functionality of using the Sony's proprietary photo processing algorithms is lost. This is not really recoverable (at least not without sending the device back, don't know if Sony repair can do this in exchange for some money) and the instructions include a warning of this effect.

Now, in order to backup the keys, you would need to have root access first. Personally, I'm not aware that anyone in the community has identified / developed a rooting script or app for the Sony Xperia XA2, in order to gain root access prior to unlocking the bootloader.
Of course after unlocking the bootloader it would be relatively easy to enable root, but then it's already too late.
I think most people here who have installed Lineage have simply accepted the consequence to lose this functionality. Of course this is at your own risk.

Thanks for your detailed explanaton!
So, I just misunderstood, what this warning box was trying to tell me. ("you will loose it and there is no known way to avoid it" instead of "back it up or you will loose it")

Maybe the text should say something like "there is no known way for this device to backup the drm keys, you will loose widevine, cameraAlgorithms, ... which will lead to Netflix only 480p, Camera having effect XYZ, ..."
or "for this device, there is this way <link to tested tutorial> to backup and restore Trim Area Partition. If you don't do this, you will loose <same as above>"
then, instead of literally "TA (...) ensure, the data (...) is backed up (...). You can find tutorials (...) on the internet", while there are non?

 

[xleng]

Thanks for your detailed explanaton!
So, I just misunderstood, what this warning box was trying to tell me. ("you will loose it and there is no known way to avoid it" instead of "back it up or you will loose it")

Maybe the text should say something like "there is no known way for this device to backup the drm keys, you will loose widevine, cameraAlgorithms, ... which will lead to Netflix only 480p, Camera having effect XYZ, ..."
or "for this device, there is this way <link to tested tutorial> to backup and restore Trim Area Partition. If you don't do this, you will loose <same as above>"
then, instead of literally "TA (...) ensure, the data (...) is backed up (...). You can find tutorials (...) on the internet", while there are non?

Sure one can always improve user guidance and manuals. You could also decide to volunteer to lineage in consideration of your free time and skills


Frankly speaking (please don't take it personally), I think there is not much interest in this point. From a developer's perspective, you want to focus on the code itself and not loose too much of your time on such elements. You rather want to keep consistent manuals, with a good amount of "re-use" of explanations across devices. The existance of such root scripts etc depends rather strongly on the actual device. I'm sure, with the above suggested additional explanations, you would also have people complaining

In summary, it's still a fair and correct assumption that this functionality is lost in the first place. Possibility to recover eventually depends on many things, is not tested etc, and can therefore be considered as not existent.

On the other hand, I was running Cyanogenmod on the Xperia L before, for which I made a backup of the drm keys thanks to such root scripts, but I never used this drm key backup...

 

[zupert]

Hello,
i can't get the Wifi hotspot to work
It starts, and other devices can connect to it, but they report having no internet connectivity.
Am i missing some config step, or is it a known bug?

For the record: the issue was caused by Blokada.
It is unclear if only the custom DNS are causing it, or the whole filtering.
But without Blokada, the wifi thetering works just fine. So problem solved.

Also LuK1337, I wanted to say thanks for your time and efforts in this project! :good:

 

[action_papst]

Recently got a new XA2 and set up this ROM. Works quite nice and I flashed 50.2.A.3.22 firmware. Is there a zip to flash latest version (ending in 77 I think) in recovery?

 

[malerocks]

A weird thing is happening on my phone. In the last 2 weeks, the used space has increased by about 6 GB. It seems that suddenly all the apps have started increasing a lot of the user data that they store. My usage pattern is the same. And its weird that all the apps are going this. Not sure why this is happening. I am now down to only 2 GB free space.

 

[80c535]

A weird thing is happening on my phone. In the last 2 weeks, the used space has increased by about 6 GB. It seems that suddenly all the apps have started increasing a lot of the user data that they store. My usage pattern is the same. And its weird that all the apps are going this. Not sure why this is happening. I am now down to only 2 GB free space.

Same here, down to 2.6 GB free space.
I saw the first warning some days ago in Google Play Store.

 

[cojocar.andrei]

Same here, down to 2.6 GB free space.
I saw the first warning some days ago in Google Play Store.

Check app_webview browser metrics. It seems that chrome webview is spilling hundreds of files of browser metrics ...Just delete them, but I do not know how to stop them ...

 

[malerocks]

Check app_webview browser metrics. It seems that chrome webview is spilling hundreds of files of browser metrics ...Just delete them, but I do not know how to stop them ...

Noobie question here, but how to delete them?

 

[cojocar.andrei]

Noobie question here, but how to delete them?

Root explorer, go to data/data/app_xxx/app_webview/BrowserMetrics/ and delete everything from there. You can view which app is swalling itself up with 1tap clear pro...I had 6gb of browser metrics for one app!!!

 

[malerocks]

Root explorer, go to data/data/app_xxx/app_webview/BrowserMetrics/ and delete everything from there. You can view which app is swalling itself up with 1tap clear pro...I had 6gb of browser metrics for one app!!!

Thanks. That helped tremendously!

 

[malerocks]

Root explorer, go to data/data/app_xxx/app_webview/BrowserMetrics/ and delete everything from there. You can view which app is swalling itself up with 1tap clear pro...I had 6gb of browser metrics for one app!!!

Thanks. That helped tremendously!

 

[samhhmobil]

A weird thing is happening on my phone. In the last 2 weeks, the used space has increased by about 6 GB. It seems that suddenly all the apps have started increasing a lot of the user data that they store. My usage pattern is the same. And its weird that all the apps are going this. Not sure why this is happening. I am now down to only 2 GB free space.

Same here too. But I can see the collected (garbage) files in BrowserMetrics are going back until October '20...

What happens there in LOS since that times?

samhhmobil

 

[malerocks]

Same here too. But I can see the collected (garbage) files in BrowserMetrics are going back until October '20...

What happens there in LOS since that times?

samhhmobil

My guess is that is around the time system webview was updated to v86 and that started this. All a wild guess though.

 

[samhhmobil]

My guess is that is around the time system webview was updated to v86 and that started this. All a wild guess though.

OK. You may be right.

JFYI... I cleared all */app_webview/BrowserMetrics (8GB of data erased).'

Then I did install via PlayStore(!) „Android System Webview“ by Google(!). It's version 87.x! Then I switched in Developer Settings the Webview engine to this Google-Version 87.x (away from the LOS-shipped Version 86.x).

It seems, the bug is gone now.

But I will report in a few days again...

--
samhhmobil

 

[malerocks]

OK. You may be right.

JFYI... I cleared all */app_webview/BrowserMetrics (8GB of data erased).'

Then I did install via PlayStore(!) „Android System Webview“ by Google(!). It's version 87.x! Then I switched in Developer Settings the Webview engine to this Google-Version 87.x (away from the LOS-shipped Version 86.x).

It seems, the bug is gone now.

But I will report in a few days again...

--
samhhmobil

Awesome. Hopefully v87 will be merged in the webview that comes with LineageOS

 

[cojocar.andrei]

Or change temporarily the permissions to read only for BrowserMetrics dir ...