[ROM][NIGHTLIES][8.1.0] LineageOS 15.1 for Xperia ZL

Ronan Lutiane

New member
Jan 7, 2018
2
0
0
With LOS 15.1 I have the issue with the wifi drop again. I always had the Problem with LOS 14 and any other Android 7.x Rom.

With LOS 15 it seemed the issue is gone but now with LOS 15.1 it is back. Anyone else noticed this Problem? I use the kodi remote APP frequently, so this issue is a pain in the ass.

Need a logfile?

Gesendet von meinem Xperia ZL mit Tapatalk
Sometimes I got some drops even when I at the same room as my router... It only disconnect and doesnt conect anymore til I turn off the WiFi...
 

Saronga

New member
Nov 24, 2013
4
0
0
Bug Whatsapp files

Problem reading files in whatsapp. Files sent and received are in memory but do not appear in whatsapp.

File Managers show duplicate folders.

Folders automatically duplicate several times.

Sorry for the bad English.

See screenshots:

 

Godlydevils

Senior Member
Jan 19, 2015
188
17
0
How to root?? At the website i can only find to the version 14.1 pls help
Inorder to root, you need make sure your bootloader is unlockable,
follow this link
https://forum.xda-developers.com/showthread.php?t=2201148

and for 8.1, the last ROM from here
https://drive.google.com/drive/folders/0B9yrk5QZnasiV1BaY1libUdBbWc?usp=sharing

make sure you flash rom and then Gapps, and then Addon su in one go, without restarting, else you won't be able to get TWRP as your recovery, which will enable you to take backups, and flash more updates, or additional flashables
 

BeatB

Senior Member
Sep 24, 2010
299
72
0
Vienna
Here I got an issue with WiFi. I got connected but it "falls" like 2 or 3 times randomly every 5 minutes. Any fix for that?
I also have this issue since the newest update. Already mentioned this some posts above.

Gesendet von meinem Xperia ZL mit Tapatalk
 

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
Changes included in build lineage-15.1-20180206:
- Newer Android GO Configuration build (Please test this. We need feedback. GO Configuration uses less storage and is easier on graphics, reference: https://www.xda-developers.com/android-go-old-android-8-1-oreo/).
- Lineage specific changes are all included (2018-02-06)
- No progress on Camcorder at the moment. It's still broken.
 

rituj_b

Recognized Developer
Nov 26, 2012
1,036
1,566
143
Jaipur

rituj_b

Recognized Developer
Nov 26, 2012
1,036
1,566
143
Jaipur
Changes included in build lineage-15.1-20180206:
- Newer Android GO Configuration build (Please test this. We need feedback. GO Configuration uses less storage and is easier on graphics, reference: https://www.xda-developers.com/android-go-old-android-8-1-oreo/).
- Lineage specific changes are all included (2018-02-06)
- No progress on Camcorder at the moment. It's still broken.
Hey the rom is working fine but the previous builds were a lot smoother and better overall. I think the Android Go addition is not playing out good with our phone. Our phone is fairly powerful and has 2 GB RAM
 
  • Like
Reactions: Daedroza

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
Hey the rom is working fine but the previous builds were a lot smoother and better overall. I think the Android Go addition is not playing out good with our phone. Our phone is fairly powerful and has 2 GB RAM
Agreed on 2GB RAM.
However, the graphics rendering felt quite slow to me on previous builds. What about you?
Thanks for the feedback :)
 

rituj_b

Recognized Developer
Nov 26, 2012
1,036
1,566
143
Jaipur
Agreed on 2GB RAM.
However, the graphics rendering felt quite slow to me on previous builds. What about you?
Thanks for the feedback :)
In my opinion this the level of stuttering is similar if not more. But I don't see any significant improvements and I liked the previous build more :p
 

BeatB

Senior Member
Sep 24, 2010
299
72
0
Vienna
Thanks for the update. The wifi issue still occurs. Attached a log file. Let me know if you need something else.

Code:
  02-09 21:45:16.112 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAKELOCK_RELEASE
02-09 21:45:16.112 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAIT_POLL
02-09 21:45:16.114 D/QC-QMI  (340): qmi_client [340] 3: Received 56 bytes on fd = 9
02-09 21:45:16.114 D/QC-QMI  (340): qmi_service.c RX indication for conn=18, srvc=3
02-09 21:45:16.115 D/QC-QMI  (340): Processing indication: Mesage4 ID=  81, Service ID = 3
02-09 21:45:16.115 D/QC-QMI  (340): Client 12010300 gets indication callback
02-09 21:45:16.855 E/JSON Parser(6309): Error parsing data org.json.JSONException: No value for Error
02-09 21:45:17.719 I/WifiService(556): requestActivityInfo uid=1000
02-09 21:45:17.720 I/WifiService(556): reportActivityInfo uid=1000
02-09 21:45:17.720 I/WifiService(556): getSupportedFeatures uid=1000
02-09 21:45:17.757 E/WifiHAL (313): acquire_supported_features: requestResponse Error:-3
02-09 21:45:17.758 E/WifiHAL (313): wifi_get_logger_supported_feature_set: Error -3 happened. 
02-09 21:45:17.760 E/WifiVendorHal(556): getSupportedFeatureSet(l.891) failed {.code = ERROR_NOT_SUPPORTED, .description = }
02-09 21:45:17.760 E/WifiHAL (313): acquire_supported_features: requestResponse Error:-3
02-09 21:45:17.761 E/WifiHAL (313): wifi_get_logger_supported_feature_set: Error -3 happened. 
02-09 21:45:17.791 E/BatteryExternalStatsWorker(556): no controller energy info supplied for wifi
02-09 21:45:17.791 E/BatteryExternalStatsWorker(556): no controller energy info supplied for bluetooth
02-09 21:45:17.822 E/BatteryExternalStatsWorker(556): modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
02-09 21:45:18.991 E/JSON Parser(6309): Error parsing data org.json.JSONException: No value for Error
02-09 21:45:20.433 I/Sensors (556): **** No Motion ****
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAKELOCK_ACQUIRE
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAIT_READ
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_CLIENT_TX
02-09 21:45:20.579 D/QC-QMI  (323): qmi_qmux: TX/RX - RX 22 bytes on conn_id=18
02-09 21:45:20.579 D/QC-QMI  (323): qmuxd: TX message on fd=19, to qmux_client_id=0x3, len=56
Gesendet von meinem Xperia ZL mit Tapatalk
 
Last edited:

BeatB

Senior Member
Sep 24, 2010
299
72
0
Vienna
Can anyone provide me the update before the 6th January? The old link doesn't work anymore.
I prefer this version because I didn't notice any wifi issues.

Gesendet von meinem Xperia ZL mit Tapatalk
 

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
Thanks for the update. The wifi issue still occurs. Attached a log file. Let me know if you need something else.

Code:
  02-09 21:45:16.112 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAKELOCK_RELEASE
02-09 21:45:16.112 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAIT_POLL
02-09 21:45:16.114 D/QC-QMI  (340): qmi_client [340] 3: Received 56 bytes on fd = 9
02-09 21:45:16.114 D/QC-QMI  (340): qmi_service.c RX indication for conn=18, srvc=3
02-09 21:45:16.115 D/QC-QMI  (340): Processing indication: Mesage4 ID=  81, Service ID = 3
02-09 21:45:16.115 D/QC-QMI  (340): Client 12010300 gets indication callback
02-09 21:45:16.855 E/JSON Parser(6309): Error parsing data org.json.JSONException: No value for Error
02-09 21:45:17.719 I/WifiService(556): requestActivityInfo uid=1000
02-09 21:45:17.720 I/WifiService(556): reportActivityInfo uid=1000
02-09 21:45:17.720 I/WifiService(556): getSupportedFeatures uid=1000
02-09 21:45:17.757 E/WifiHAL (313): acquire_supported_features: requestResponse Error:-3
02-09 21:45:17.758 E/WifiHAL (313): wifi_get_logger_supported_feature_set: Error -3 happened. 
02-09 21:45:17.760 E/WifiVendorHal(556): getSupportedFeatureSet(l.891) failed {.code = ERROR_NOT_SUPPORTED, .description = }
02-09 21:45:17.760 E/WifiHAL (313): acquire_supported_features: requestResponse Error:-3
02-09 21:45:17.761 E/WifiHAL (313): wifi_get_logger_supported_feature_set: Error -3 happened. 
02-09 21:45:17.791 E/BatteryExternalStatsWorker(556): no controller energy info supplied for wifi
02-09 21:45:17.791 E/BatteryExternalStatsWorker(556): no controller energy info supplied for bluetooth
02-09 21:45:17.822 E/BatteryExternalStatsWorker(556): modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
02-09 21:45:18.991 E/JSON Parser(6309): Error parsing data org.json.JSONException: No value for Error
02-09 21:45:20.433 I/Sensors (556): **** No Motion ****
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAKELOCK_ACQUIRE
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_WAIT_READ
02-09 21:45:20.579 D/QC-QMI  (323): Thread state: conn_id=18, state=RX_THREAD_CLIENT_TX
02-09 21:45:20.579 D/QC-QMI  (323): qmi_qmux: TX/RX - RX 22 bytes on conn_id=18
02-09 21:45:20.579 D/QC-QMI  (323): qmuxd: TX message on fd=19, to qmux_client_id=0x3, len=56
Gesendet von meinem Xperia ZL mit Tapatalk
We don't have the latest supported features hence the error. Nothing to worry about. Pretty much normal for 8960 devices.
Still, I don't understand, there are no changes in connectivity HAL. There aren't any differences. How could one build provide better results than older one? Logically it's incorrect :silly:

Try this, Developer Options -> Disable Mobile data always Active
That way, there will be more aggressive selection on either one of connectivity providers.
 

BeatB

Senior Member
Sep 24, 2010
299
72
0
Vienna
We don't have the latest supported features hence the error. Nothing to worry about. Pretty much normal for 8960 devices.
Still, I don't understand, there are no changes in connectivity HAL. There aren't any differences. How could one build provide better results than older one? Logically it's incorrect :silly:

Try this, Developer Options -> Disable Mobile data always Active
That way, there will be more aggressive selection on either one of connectivity providers.
Thanks for the suggestion, but the problem still occurs. I need the build before 01.06.

Code:
02-13 19:53:32.465 D/CommandListener(275): Setting iface cfg 02-13 19:53:32.478 W/BroadcastQueue(560): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.quoord.tapatalkpro.activity/com.sense360.android.quinoa.lib.visit.WifiConnectionReceiver 02-13 19:53:32.480 D/DhcpClient(560): Scheduling renewal in 43199s 02-13 19:53:32.480 D/DhcpClient(560): Scheduling rebind in 75599s 02-13 19:53:32.480 D/DhcpClient(560): Scheduling expiry in 86399s 02-13 19:53:32.490 W/LastMileLogger(560): Failed to stop event tracing: /sys/kernel/debug/tracing/instances/wifi/tracing_on (No such file or directory) 02-13 19:53:32.491 D/ConnectivityService(560): NetworkAgentInfo [WIFI () - 158] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to CONNECTED 02-13 19:53:32.494 D/ConnectivityService(560): Adding iface wlan0 to network 158 02-13 19:53:32.503 W/BroadcastQueue(560): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.quoord.tapatalkpro.activity/com.sense360.android.quinoa.lib.visit.WifiConnectionReceiver 02-13 19:53:32.503 D/ConnectivityService(560): Setting DNS servers for network 158 to [/195.34.133.21, /212.186.211.21] 02-13 19:53:32.506 I/GCoreUlr(1414): Starting service, intent=Intent { act=com.google.android.location.reporting.WIFI_TRIGGERED_FLUSH_AND_UPLOAD cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService }, extras=null 02-13 19:53:32.514 I/WifiService(560): getConnectionInfo uid=10013 02-13 19:53:32.522 I/GeofencerStateMachine(1414): sendWifiConnectivityChanged: connectivity=true 02-13 19:53:32.524 W/BroadcastQueue(560): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.quoord.tapatalkpro.activity/com.sense360.android.quinoa.lib.visit.WifiConnectionReceiver 02-13 19:53:32.530 I/WifiService(560): requestActivityInfo uid=1000 02-13 19:53:32.530 I/WifiService(560): reportActivityInfo uid=1000 02-13 19:53:32.530 I/WifiService(560): getSupportedFeatures uid=1000 02-13 19:53:32.532 E/WifiHAL (314): acquire_supported_features: requestResponse Error:-3 02-13 19:53:32.533 E/WifiHAL (314): wifi_get_logger_supported_feature_set: Error -3 happened. 02-13 19:53:32.533 E/WifiVendorHal(560): getSupportedFeatureSet(l.891) failed {.code = ERROR_NOT_SUPPORTED, .description = } 02-13 19:53:32.534 E/WifiHAL (314): acquire_supported_features: requestResponse Error:-3 02-13 19:53:32.534 E/WifiHAL (314): wifi_get_logger_supported_feature_set: Error -3 happened. 02-13 19:53:32.540 E/BatteryExternalStatsWorker(560): no controller energy info supplied for wifi 02-13 19:53:32.541 I/WifiService(560): getConnectionInfo uid=1000 02-13 19:53:32.553 D/RecurrenceRule(560): Resolving using anchor 2018-02-13T19:53:32.553+01:00[Europe/Vienna] 02-13 19:53:32.558 D/RecurrenceRule(560): Resolving using anchor 2018-02-13T19:53:32.558+01:00[Europe/Vienna] 02-13 19:53:32.566 D/RecurrenceRule(560): Cycle 13 from 2018-02-07T00:00+01:00[Europe/Vienna] to 2018-03-07T00:00+01:00[Europe/Vienna] 02-13 19:53:32.567 D/NetworkStats(560): Resolving plan for NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=232170..., matchSubscriberIds=[232170...] 02-13 19:53:32.573 D/NetworkStats(560): Found active matching subId 1 02-13 19:53:32.579 I/WifiService(560): getConnectionInfo uid=1000 02-13 19:53:32.581 D/WifiNetworkAgent(560): NetworkAgent: Received signal strength thresholds: [] 02-13 19:53:32.583 E/WifiVendorHal(560): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = } 02-13 19:53:32.584 D/NetworkStats(560): Resolved to plan null 02-13 19:53:32.594 D/RecurrenceRule(560): Resolving using anchor 2018-02-13T19:53:32.593+01:00[Europe/Vienna] 02-13 19:53:32.596 I/GnssLocationProvider(560): WakeLock acquired by sendMessage(UPDATE_NETWORK_STATE, 0, 158) 02-13 19:53:32.607 I/GnssLocationProvider(560): WakeLock released by handleMessage(UPDATE_NETWORK_STATE, 0, 158) 02-13 19:53:32.608 D/RecurrenceRule(560): Resolving using anchor 2018-02-13T19:53:32.608+01:00[Europe/Vienna] 02-13 19:53:32.616 D/RecurrenceRule(560): Cycle 13 from 2018-02-07T00:00+01:00[Europe/Vienna] to 2018-03-07T00:00+01:00[Europe/Vienna] 02-13 19:53:32.618 D/NetworkStats(560): Resolving plan for NetworkTemplate: matchRule=MOBILE_ALL, subscriberId=232170..., matchSubscriberIds=[232170...] 02-13 19:53:32.623 D/NetworkStats(560): Found active matching subId 1 02-13 19:53:32.640 D/NetworkStats(560): Resolved to plan null 02-13 19:53:32.644 I/WifiService(560): getConnectionInfo uid=1000 02-13 19:53:32.673 I/Places (1414): Converted 12 out of 12 WiFi scans 02-13 19:53:32.676 I/WifiService(560): getConnectionInfo uid=10013 02-13 19:53:32.684 I/GCoreUlr(1414): Starting service, intent=Intent { act=com.google.android.location.reporting.WIFI_TRIGGERED_UPLOAD cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService }, extras=null 02-13 19:53:32.696 I/LocSvc_eng(560): I/===> loc_eng_inject_location line 1790 02-13 19:53:32.696 D/LocSvc_utils_q(560): D/msg_q_snd: Sending message with handle = 0x8D845920 02-13 19:53:32.696 D/LocSvc_utils_ll(560): D/linked_list_add: Adding to list data_obj = 0x8D845920 02-13 19:53:32.696 D/LocSvc_utils_q(560): D/msg_q_snd: Finished Sending message with handle = 0x8D845920 02-13 19:53:32.696 D/LocSvc_utils_ll(560): D/linked_list_remove: Removing from list
Gesendet von meinem Xperia ZL mit Tapatalk
 

luisx010

Member
Apr 1, 2015
7
0
0
Uploaded a new build:
1. Reverted GO Configuration as taken from feedback.
2. Synced newer Lineage sources
Hello! First, thank you for your work. I have two questions.
Is the video recording working? I was reading that is not working for the previous release

Can I install gapps of ARM 8.0? Or we only can install 7.x?

Thanks!
Sorry if I can't explain it better, because English is not my primary language.
 

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
Hello! First, thank you for your work. I have two questions.
Is the video recording working? I was reading that is not working for the previous release

Can I install gapps of ARM 8.0? Or we only can install 7.x?

Thanks!
Sorry if I can't explain it better, because English is not my primary language.
Video recording is broken, super experienced developer from Sony Xperia SP (@AdrianDC) is working on fixing it.
Also, LineageOS recommends this GApps (https://androidfilehost.com/?w=files&flid=170282)
But I haven't gotten time lately to test them.

Any 8.1 GApps should work.
8.0 GApps would also work but requires some editing in zip.

Thanks :)
 
  • Like
Reactions: 156and and luisx010