[ROM][10][OFFICIAL] Lineage OS 17.1

Valentinatg

Member
Jun 25, 2015
7
0
0
So I can comfirm power pack work with no efficient mod, thank you for answer.
So to confirm jbl still doesnt work?

Can we hope this will work in near future?
 

heithered

Senior Member
Nov 15, 2013
365
78
48
Izmir
Before official Lineage OS 16 launch (versions that @erfanoabdi release) battery efficient mod was working, I don't now why it didn't came to official Lineage OS.

Good workaround, but only works when charging from USB without power pack, if you have a power pack attached to phone this workaround become not useful because:

1) Power pack never fully charge because phone charges to 80% and power pack only around 20-40%
2) Power pack never charge if discharged and the pone is charged 80% or more
2) If power pack is charged it charges the phone to 100% anyway

Edit: I made a clean install of Lineage OS 16 formatting all partitions installing only lineage and openGapps, no problem with camera apps and others Gapps crashing anymore.
Edit2: Ambient gesture display is not working anymore. Aways grayed.
Edit3: Connectivity issue still present needing the workaround: https://forum.xda-developers.com/showpost.php?p=79307782&postcount=415.
Did you check the magisk module ACC? It can act as an efficiency mode replacement.
 
  • Like
Reactions: ischninet
Jun 17, 2015
17
1
0
Dresden & Düsseldorf
Wifi EAP TLS

Dear All,

My impression is that basically everything does work (thanks!!) and that this is an easy device to install. What I could not get to work is wifi EAP TLS. The device does just not connect. Other certificate applications (e.g., client certs in exchange accounts, client cert in chromium) except for wifi do seem to work. I find this problem on some 16.0 devices (e.g, bardockpro, kiwi) while others do work flawlessly (e.g., oneplus3). Is this shared?

I hesitate to submit a bug report through lineageos, as I did install the microg variant. That will have nothing to do with this issue, but bug reporting management usually just replies that microg is not supported. Should I post logs here?

Regards,

Michael Schefczyk
 
Jun 17, 2015
17
1
0
Dresden & Düsseldorf
Dear All,

My impression is that basically everything does work (thanks!!) and that this is an easy device to install. What I could not get to work is wifi EAP TLS. The device does just not connect. Other certificate applications (e.g., client certs in exchange accounts, client cert in chromium) except for wifi do seem to work. I find this problem on some 16.0 devices (e.g, bardockpro, kiwi) while others do work flawlessly (e.g., oneplus3). Is this shared?

I hesitate to submit a bug report through lineageos, as I did install the microg variant. That will have nothing to do with this issue, but bug reporting management usually just replies that microg is not supported. Should I post logs here?

Regards,

Michael Schefczyk
Dear All,

What I would very much like is (a) to understand the EAP-TLS wifi issue and (b) ideally get it solved. With the device, EAP-TTLS (eduroam, with just a CA certificate) does work, not EAP-TLS, however. I have full logcat information. Key excerpts of errors include:

07-25 18:02:22.480 27283 27283 I wpa_supplicant: TLS - SSL error: error:0900006e:pEM routinesPENSSL_internal:NO_START_LINE
07-25 18:02:22.480 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
07-25 18:02:22.499 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...
07-25 18:02:22.500 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...

07-25 18:02:22.536 1992 2150 I keystore: 1 0
07-25 18:02:22.544 1992 2150 W keystore: Error in finish: -1000
07-25 18:02:22.545 27283 27283 W keystore-engine: Error during sign from keystore: 1
07-25 18:02:22.545 27283 27283 I wpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:00000000:invalid library (0)PENSSL_internal:invalid library (0)

07-25 18:02:33.733 23506 23622 E WifiVendorHal: getTxPktFates(l.2219) failed {.code = ERROR_NOT_AVAILABLE, .description = }


This one below is from kiwi, but same issue with different certificate:

07-25 21:10:24.974 3057 3057 I wpa_supplicant: TLS - SSL error: error:0900006e:pEM routinesPENSSL_internal:NO_START_LINE
07-25 21:10:24.974 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
07-25 21:10:24.974 363 3223 I WifiHAL : Unknown EAPOL message type
07-25 21:10:24.986 363 3223 I chatty : uid=1010 [email protected] identical 2 lines
07-25 21:10:24.995 363 3223 I WifiHAL : Unknown EAPOL message type
07-25 21:10:24.997 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...
07-25 21:10:25.000 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...

07-25 21:10:25.027 2308 2361 I keystore: 1 0
07-25 21:10:25.052 2308 2361 W keystore: Error in finish: -1000
07-25 21:10:25.052 3057 3057 W keystore-engine: Error during sign from keystore: 1
07-25 21:10:25.052 3057 3057 I wpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:00000000:invalid library (0)PENSSL_internal:invalid library (0)


If required, I can supply more information.

The same certificates does work flawlessly on other devices (jfltexx, h870).

Regards,

Michael Schefczyk
 
Jun 17, 2015
17
1
0
Dresden & Düsseldorf
Dear All,

What I would very much like is (a) to understand the EAP-TLS wifi issue and (b) ideally get it solved. With the device, EAP-TTLS (eduroam, with just a CA certificate) does work, not EAP-TLS, however. I have full logcat information. Key excerpts of errors include:

07-25 18:02:22.480 27283 27283 I wpa_supplicant: TLS - SSL error: error:0900006e:pEM routinesPENSSL_internal:NO_START_LINE
07-25 18:02:22.480 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
07-25 18:02:22.499 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...
07-25 18:02:22.500 27283 27283 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...

07-25 18:02:22.536 1992 2150 I keystore: 1 0
07-25 18:02:22.544 1992 2150 W keystore: Error in finish: -1000
07-25 18:02:22.545 27283 27283 W keystore-engine: Error during sign from keystore: 1
07-25 18:02:22.545 27283 27283 I wpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:00000000:invalid library (0)PENSSL_internal:invalid library (0)

07-25 18:02:33.733 23506 23622 E WifiVendorHal: getTxPktFates(l.2219) failed {.code = ERROR_NOT_AVAILABLE, .description = }


This one below is from kiwi, but same issue with different certificate:

07-25 21:10:24.974 3057 3057 I wpa_supplicant: TLS - SSL error: error:0900006e:pEM routinesPENSSL_internal:NO_START_LINE
07-25 21:10:24.974 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
07-25 21:10:24.974 363 3223 I WifiHAL : Unknown EAPOL message type
07-25 21:10:24.986 363 3223 I chatty : uid=1010 [email protected] identical 2 lines
07-25 21:10:24.995 363 3223 I WifiHAL : Unknown EAPOL message type
07-25 21:10:24.997 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...
07-25 21:10:25.000 3057 3057 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=DE/ST=.../L=.../O=.../emailAddress=.../CN=...' hash=...

07-25 21:10:25.027 2308 2361 I keystore: 1 0
07-25 21:10:25.052 2308 2361 W keystore: Error in finish: -1000
07-25 21:10:25.052 3057 3057 W keystore-engine: Error during sign from keystore: 1
07-25 21:10:25.052 3057 3057 I wpa_supplicant: OpenSSL: openssl_handshake - SSL_connect error:00000000:invalid library (0)PENSSL_internal:invalid library (0)


If required, I can supply more information.

The same certificates does work flawlessly on other devices (jfltexx, h870).

Regards,

Michael Schefczyk
My impression is that wifi 802.1x EAP TLS not working is due to a cert store issue. I find identical problems on kiwi and griffin. On the other hand, oneplus3 and (brand new official lineageos 16.0) jfltexx are able to use wifi802.1x EAP TLS without issues based on the very same certificates. The reason I suspect the cert store issue is bardockpro. That device did have the same problem one month ago, but it does work fine now. The positive change did seem to happen after this appeared under "recent changes": https://review.lineageos.org/c/Linea...urity/+/251056 Unfortunately, I do not understand the issue in any greater depth beyond this speculative thought. Is there something which may need to be done in order to extend the same benefit to griffin as well?
 

isgakbrfc

Senior Member
Apr 2, 2014
54
5
0
Good day everybody

i hope somebody can help this noob. i rooted my Moto Z, and installed Twrp... However, im literally struggling to install custom roms. Getting an error message sayin the roms are only for the Z model which i have. Question is, have i somehow wiped or forgot to add in my device detail or description, which twrp doesnt recognise as a Moto Z?

would appreciate an easy guide on how to fix this.thanks all
 

isgakbrfc

Senior Member
Apr 2, 2014
54
5
0
explain exact what are you doing
so basically i enter into recovery ie twrp.. have already downloaded the Rom, gapps and Magisk. As soon as i swipe to Flash, i get an error saying that the rom is only compatible with Moto Z devices(which i have)

i managed to install the Viper 7.1 Rom, but cant do anything when it comes to Android 9

Ill try and get some screenshots up

---------- Post added at 12:37 PM ---------- Previous post was at 12:17 PM ----------

as per the below pics, you can see i could flash Viper, but when i try this rom it doesnt recognise my device. anything in there that im missing?

https://imgur.com/undefined
 

numlock_

Senior Member
Oct 11, 2012
58
12
0
so basically i enter into recovery ie twrp.. have already downloaded the Rom, gapps and Magisk. As soon as i swipe to Flash, i get an error saying that the rom is only compatible with Moto Z devices(which i have)

i managed to install the Viper 7.1 Rom, but cant do anything when it comes to Android 9

Ill try and get some screenshots up

---------- Post added at 12:37 PM ---------- Previous post was at 12:17 PM ----------

as per the below pics, you can see i could flash Viper, but when i try this rom it doesnt recognise my device. anything in there that im missing?

https://imgur.com/undefined
You need to be on stock android to flash LineageOS. Search for stock moto z android, flash it and then flash lineageos 16. https://wiki.lineageos.org/devices/griffin/install
 
  • Like
Reactions: isgakbrfc

isgakbrfc

Senior Member
Apr 2, 2014
54
5
0
No, via adb sideload, there is a thread here explaining how to flash search about
Out of interest, why could I flash Viper? I basically tried flashing Lineage, off of stock Android the 1st time. So I had no other custom ROM loaded.

Sent from my XT1650-03 using Tapatalk
 

numlock_

Senior Member
Oct 11, 2012
58
12
0
Out of interest, why could I flash Viper? I basically tried flashing Lineage, off of stock Android the 1st time. So I had no other custom ROM loaded.

Sent from my XT1650-03 using Tapatalk
I don't know why, the screen you posted is broken, maybe you tried the wrong way, you need latest twrp and flash trough adb sideload.
 
  • Like
Reactions: isgakbrfc

isgakbrfc

Senior Member
Apr 2, 2014
54
5
0
I don't know why, the screen you posted is broken, maybe you tried the wrong way, you need latest twrp and flash trough adb sideload.
Okay thanks. I'll check the version of Twrp. Can I just flash the latest version over the current one via cmd?

Sent from my XT1650-03 using Tapatalk
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone