[ROM][UNOFFICIAL][10][Q]LineageOS 17.1 for z5c (suzuran)

Berni-0815 · Dec 31, 2020 at 9:54 AM

esrevinu said:
I can fix this bug by patching 'lineage-sdk'

Do you have a link to this patch?

esrevinu · Jan 2, 2011 32 9 38

Berni-0815 said:
Do you have a link to this patch?

No, I don't. But that diff inserted in my previous comment is all. This diff is made by git-diff commend. This can be apply to 'lineage-sdk' directory(checkout of LineageOS/android_lineage-sdk) under Lineage OS source root.

Berni-0815 · Jan 1, 2021 at 8:01 PM

esrevinu said:
I have solved this issue by modifying audio_policy_configuration.xml.

I've changed this file: Klick
I hope this will help.
BTW: Happy new year!

Berni-0815 · Jan 2, 2021 at 9:52 AM

esrevinu said:
No, I don't. But that diff inserted in my previous comment is all. This diff is made by git-diff commend. This can be apply to 'lineage-sdk' directory(checkout of LineageOS/android_lineage-sdk) under Lineage OS source root.

Are those changes (or the idea behind it) from you? Or have you seen that somewhere? I'm asking because I would like to understand where it comes from.

cdannebe · Nov 23, 2020 6 0 1

cdannebe said:
Hi Berni,
you mean reflash could solve the issue?

Greetings from Saxony , Christian

Hi Berni,
I installed your latest 17.1 image (from 15.12.2020). I reflash the image twice in the last 3 weeks (I cleaned up everything I could find in TWRP). The result is the same. I have about 4% battery loss per hour (even if the display on for not more than 10 minutes per day, WLAN off, BT on, no social network app installed). With the same apps installed and similar configured in 14.1 LOS I had about 2%/hour.

By the way, if I shutdown the phone completely and I charge it, the temperature grow up to more than 50°C on the display surface. That's seems to be too much. What can I do?

Christian

esrevinu · Jan 2, 2011 32 9 38

Berni-0815 said:
Are those changes (or the idea behind it) from you? Or have you seen that somewhere? I'm asking because I would like to understand where it comes from.

Yes, it is from me. I have built a rom from your settings to fix my issues.

1ggn3 · Oct 26, 2020 22 1 3

cdannebe said:
The result is the same. I have about 4% battery loss per hour (even if the display on for not more than 10 minutes per day, WLAN off, BT on, no social network app installed). With the same apps installed and similar configured in 14.1 LOS I had about 2%/hour.

Same here, erasing /data did not improve things for me. Maybe I need to re-flash everything from the Sony tool in the "green led mode". I don't have enough time right now to re-install all the apps I need, but that's all I can think of.

cdannebe said:
By the way, if I shutdown the phone completely and I charge it, the temperature grow up to more than 50°C on the display surface.

see my post here
tldr: If you charge the phone, try measuring the battery temperature with an app than can read the sensor values, they should stay well below 45°C. If they don't, your phone has a problem, otherwise it's just charging with as much current as the battery can take without damage.

Berni-0815 · Jan 3, 2021 at 3:58 PM

cdannebe said:
I have about 4% battery loss per hour

That's way too much! I am now at a loss ...
Have you tried to rewrite your /persist partition?

Code:

restorecon -RF /persist

By the way, if I shutdown the phone completely and I charge it, the temperature grow up to more than 50°C on the display surface. That's seems to be too much. What can I do?

I really don't know. Is the device getting so hot in normal (active/powered up) mode too?

Berni-0815 · Jan 3, 2021 at 3:59 PM

esrevinu said:
Yes, it is from me. I have built a rom from your settings to fix my issues.

Cool! Can I use this code? Of have you tried to submit your fix to the LineageOS team?

cdannebe · Nov 23, 2020 6 0 1

Berni-0815 said:
That's way too much! I am now at a loss ...
Have you tried to rewrite your /persist partition?

Code:

restorecon -RF /persist

I really don't know. Is the device getting so hot in normal (active/powered up) mode too?

... no, in normal mode the charging work as expected.

Berni-0815 · Jan 3, 2021 at 4:44 PM

Hmm. Never tried to charge my device in shutdown state...

1ggn3 · Oct 26, 2020 22 1 3

Oh, you talked about charging the phone while it's powered off, sorry.
If I remember correctly, it should boot into charge mode, which is just the kernel and a simple binary to show the progress. As far as I understand it, that should be enough to manage the charging current, right?

cdannebe · Nov 23, 2020 6 0 1

1ggn3 said:
Oh, you talked about charging the phone while it's powered off, sorry.
If I remember correctly, it should boot into charge mode, which is just the kernel and a simple binary to show the progress. As far as I understand it, that should be enough to manage the charging current, right?

... yes should be enough.
Until now I thought this is controlled by hardware not by software.

1ggn3 · Oct 26, 2020 22 1 3

cdannebe said:
... yes should be enough.
Until now I thought this is controlled by hardware not by software.

I have no idea. My best guess is that there is a charging IC that allows charging independently from any software (since the phone can charge even when there is no OS loaded, f.e. in fasboot mode), but the software (kernel module?) can control the IC over something like i2c.

cdannebe · Nov 23, 2020 6 0 1

Hi Berni,
I just installed your LOS18.1 image, NikGapps, I wipe the Data, Cache, Dalvik and I mount /persist and ran:

Bash:

restorecon -RF /persist

I will report my result in the next days.

&(*) · Jan 3, 2021 at 6:12 PM

Berni, I'd like to chime in. I mentioned something similar to the issues with the thermal temperatures i.e. the battery swelling in my case. My discovery was the USB cable I was using was rather short, 2~3 inches. Try using a much longer cable (3~6 feet) when charging and see if the temperature changes. I believe most of the thermal activity you are feeling is being released from the battery not the board itself. I know from experience that batteries come with a little chip on the cable which I'm pretty sure is the voltage limiter. More than likely the conclusion is to get a new battery unless you alleviate the thermal charging issues with the method described above and are comfortable with the results.

mikaelr · Oct 20, 2012 1 1 23

Hi, First , Big thanks to you Berni for your work here!! , this ROM really revived my z5c running smoother and with more features than the stock ROM.

the only issues I've encountered is with widevine and DRM.
I found that if selinux is enforced then the DRM system will fail, where as if I set it to permissive with `setenforce 0` it works.

It's noticeable in 'drm info' as Clearkey CDM and Widevine CDM sections are missing, whereas if I set selinux to permissive they are there and Widevine is at Level 3 as expected without the DRM keys in the TA partition.

If I enforce selinux, then apps like Netflix and Disney+ will not play because it cannot use the DRM system.

I've captured dmesg with selinux set to permissive and I do believe it can be solved easily using the correct policy settings or context for selinux, currently reading up on how that works on Android.

Code:

[  744.092376] type=1400 audit(1609702796.529:445): avc: denied { open } for comm="[email protected]" path="/data/vendor/mediadrm/IDM1013/L3/certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.092426] type=1400 audit(1609702877.509:446): avc: denied { getattr } for comm="HwBinder:490_3" path="/data/vendor/mediadrm/IDM1013/L3/certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.093537] type=1400 audit(1609702877.509:446): avc: denied { getattr } for comm="HwBinder:490_3" path="/data/vendor/mediadrm/IDM1013/L3/certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.093589] type=1400 audit(1609702877.509:447): avc: denied { read } for comm="HwBinder:490_3" name="certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.093786] type=1400 audit(1609702877.509:447): avc: denied { read } for comm="HwBinder:490_3" name="certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.093818] type=1400 audit(1609702877.509:448): avc: denied { open } for comm="HwBinder:490_3" path="/data/vendor/mediadrm/IDM1013/L3/certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.116210] type=1400 audit(1609702877.509:448): avc: denied { open } for comm="HwBinder:490_3" path="/data/vendor/mediadrm/IDM1013/L3/certP............eg==.bin" dev="mmcblk0p42" ino=695008 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:vendor_data_file:s0 tclass=file permissive=1
[  744.116249] type=1400 audit(1609702877.529:449): avc: denied { call } for comm="Binder:688_4" scontext=u:r:mediadrmserver:s0 tcontext=u:r:hal_drm_clearkey:s0 tclass=binder permissive=1
[  747.350026] type=1400 audit(1609702877.529:449): avc: denied { call } for comm="Binder:688_4" scontext=u:r:mediadrmserver:s0 tcontext=u:r:hal_drm_clearkey:s0 tclass=binder permissive=1
[  747.350083] type=1400 audit(1609702880.759:450): avc: denied { call } for comm="Binder:688_3" scontext=u:r:mediadrmserver:s0 tcontext=u:r:hal_drm_clearkey:s0 tclass=binder permissive=1
[  747.489856] msm_vidc: info: Opening video instance: 0000000000000000, 1
[  747.502150] ueventd: firmware: loading 'venus.mdt' for '/devices/soc.0/fdce0000.qcom,venus/firmware/venus.mdt'

Regards.
Mikael.

esrevinu · Jan 2, 2011 32 9 38

Berni-0815 said:
Cool! Can I use this code? Of have you tried to submit your fix to the LineageOS team?

Yes, you can use it . It would be appreciated if you would submit it to the LineageOS team.

Berni-0815 · Jan 4, 2021 at 1:17 PM

mikaelr said:
the only issues I've encountered is with widevine and DRM.

I'm not longer maintaining los17. I for myself switched to los18.1

casouzaj · Jan 4, 2021 at 1:30 PM

Berni-0815 said:
I'm not longer maintaining los17. I for myself switched to los18.1

Your 18.1 build is already published? What's its thread? Thanks, anyway!

[ROM][UNOFFICIAL][10][Q]LineageOS 17.1 for z5c (suzuran)

Senior Member

Member

Senior Member

Senior Member

Member

Member

Member

Senior Member

Senior Member

Member

Senior Member

Member

Member

Member

Member

Senior Member

New member

Member

Senior Member

Senior Member