Lineage-16.0 (Android Pie) Nightly

[chrmhoffmann]

You can provide /proc/last_kmsg after reboot?

Chris

[lklaus]

Running on LOS from jul 19, when trying to change notification settings for one app, i get:

FATAL EXCEPTION: main
Process: com.android.settings, PID: 19105
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.support.v7.preference.Preference.setOnPreferenceChangeListener(android.support.v7.preference.Preference$OnPreferenceChangeListener)’ on a null object reference
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3822)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3854)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.support.v7.preference.Preference.setOnPreferenceChangeListener(android.support.v7.preference.Preference$OnPreferenceChangeListener)’ on a null object reference
at com.android.settingslib.core.AbstractPreferenceController.displayPreference(AbstractPreferenceController.java:28)
at com.android.settings.notification.NotificationSettingsBase$ImportanceListener.onImportanceChanged(NotificationSettingsBase.java:410)
at com.android.settings.notification.BlockPreferenceController.onSwitchChanged(BlockPreferenceController.java:118)
at com.android.settings.widget.SwitchBar.propagateChecked(SwitchBar.java:277)
at com.android.settings.widget.SwitchBar.onCheckedChanged(SwitchBar.java:287)
at android.widget.CompoundButton.setChecked(CompoundButton.java:171)
at android.widget.Switch.setChecked(Switch.java:1080)
at com.android.settings.widget.ToggleSwitch.setChecked(ToggleSwitch.java:57)
at com.android.settings.widget.SwitchBar.setChecked(SwitchBar.java:189)
at com.android.settings.notification.BlockPreferenceController.updateState(BlockPreferenceController.java:81)
at com.android.settings.dashboard.DashboardFragment.updatePreferenceStates(DashboardFragment.java:307)
at com.android.settings.dashboard.DashboardFragment.onResume(DashboardFragment.java:169)
at com.android.settings.notification.NotificationSettingsBase.onResume(NotificationSettingsBase.java:157)
at com.android.settings.notification.AppNotificationSettings.onResume(AppNotificationSettings.java:82)
at android.app.Fragment.performResume(Fragment.java:2568)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1341)
at android.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1576)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1637)
at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3046)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:3008)
at android.app.FragmentController.dispatchResume(FragmentController.java:204)
at android.app.Activity.performResume(Activity.java:7322)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3814)
… 11 more

[WoBoW]

@chrmhoffmann, I found the problem after trial and error with the wireless settings of my accesspoints!
Somehow the current nightly releases of LOS16.0 don’t support IGMPv3 anymore.
Is this something you can fix?

[juniorprofi]

Will do Chris!
Shall I send you a PM or upload these somewhere?
And since yesterday I’m having massive problems with internet, mobile data and Wifi are both working max. 5% of the time.
I had these problems directly after upgrading to LOS 16, but they were gone after 2 days, now they are back.

[clsbln]

Just wanted to add that I’m also affected by the WiFi issues. The router is an AVM Fritz!Box 7590 and I tried both 2.4 + 5 GHz.

[avamk]

Thank you @ChuckMorris!

@ChuckMorris

if you encrypted in 15.1, you can upgrade to 16. If you encrypted in 14.1 and then upgraded to 15.1, you can’t upgrade to 16.

Great to know! Unfortunately I can’t remember if I encrypted my Fairphone 2 in LineageOS 14.1 or 15.1!! Is there a way to find out???

@ChuckMorris

TWRP has nothing to do with that. Stay on 3.2. 3.3 is buggy as f***.

Also good to know. I will stay on TWRP 3.2.x for now, then!

[ChuckMorris]

Check if you can access the data partition in TWRP. This only works if you encrypted in 14.1.

[DorKeinath]

I wiped all and installed 16.0 with TWRP, encrypted data again, installed necessary apps and put my data back again, and everything works VERY fine. Even the search in settings works contrary to 15.1. And I’ve got the feeling that my battery charges better and works longer.

[DorKeinath]

So I like LOS 16.0 very much but the following two privacy setting should be set as standard but aren’t currently set:

1. Pull-Down-Menu: Location/Device only (instead of High accuracy)
2. Calls-App: Settings/Phone number lookup: all disabled (instead of lookups enabled)

[maba007]

But does encryption work reliably from scratch with LineageOS 16 (independent of TWRP)?

This way doesn’t seem to work anymore to remove and re-encryption. Are there new ways?

[AnotherElk]

@maba007

But does encryption work reliably from scratch with LineageOS 16 (independent of TWRP)?

For me, yes.

@maba007

This way doesn’t seem to work anymore to remove and re-encryption. Are there new ways?

Whenever I had trouble with encryption or wanted to make sure I wouldn’t get any in the first place, I did the following …

@AnotherElk

• Booted TWRP
• Destroyed the LUKS header to really seriously get rid of prior encryption (Advanced - Terminal - dd if=/dev/zero of=/dev/block/mmcblk0p20 bs=4096 count=512 )
• Formatted data to get a valid Ext4 partition again (Wipe - Format Data)
• Resized data to not regret later that I left that out (Wipe - Advanced Wipe - data - Repair or Change File System - Resize File System)

[avamk]

@ChuckMorris

Check if you can access the data partition in TWRP. This only works if you encrypted in 14.1.

Uh oh, looks like the TWRP 3.2.3 I have installed can see /data and its contents from the TWRP file manager. I was also able to use the “Mount” option in the TWRP main menu to unmount and re-mount the “Data” partition in Internal Storage. This means I must have encrypted my phone in LineageOS 14.1, right?

If so, and just to confirm, if I want to upgrade to LineageOS 16.x, I have to completely wipe my phone (but presumably not my micro SD card, right?) and install 16.0 from scratch? If so, exactly what should I wipe from within TWRP? After selecting “Wipe” from the TWRP main menu, I see that the default option is to wipe “Data, Cache, and Dalvik”. Is that enough, or should I do an “Advanced Wipe”, if so what partitions should I wipe???

Thank you @ChuckMorris !!

P.S. If I wipe, I’ll remember to back up settings and files stored in the phone’s internal storage.

[avamk]

Also, in reference to this post above by @AnotherElk :

@AnotherElk

Destroyed the LUKS header to really seriously get rid of prior encryption (Advanced - Terminal - dd if=/dev/zero of=/dev/block/mmcblk0p20 bs=4096 count=512 )

Is the encrypted partition always /dev/block/mmcblk0p20? Or is there a way to find out?

[AnotherElk]

@avamk

Is the encrypted partition always /dev/block/mmcblk0p20 ?

Not across different devices, but on all Fairphone 2s the partition layout should be the same.

@avamk

Or is there a way to find out?

This is an excellent point you are making, so to be safe here’s a source for this dd command including how to find out the exact path …

https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery

"Destroy the LUKS Header for Filesystem Encryption

1. You need a recovery which will allow you to drop to a shell as root , so TWRP works in my case.

2. Locate the userdata partition by looking around in
/dev/block/platform/*/by-name/userdata .

3. Write out a ton of zeroes to the beginning of that partition to wipe the LUKS header:
dd if=/dev/zero of=$PATH_TO_YOUR_USERDATA bs=4096 count=512

I claim no responsibility for what you do with this command. If you screw this up, you can brick your phone by overwriting your bootloader or other critical partitions. Make sure that $PATH_TO_YOUR_USERDATA points to the real userdata partition. Check the size of that partition to make sure you’re wiping the right thing. I have a 16GB phone and userdata is 10.4GB, with the rest being dedicated to system , but your phone will be different.

4. Reformat that partition as ext4 using make_ext4fs $PATH_TO_YOUR_USERDATA . There might be errors, but usually they relate to not being able to find the internal “sdcard,” this is okay."

Hints:
The “looking around” in point 2 amounts to the “ls -l” command.
Reformatting the partition as in point 4 can comfortably done in TWRP with Wipe - Format Data, as already pointed out in my earlier post.

[ChuckMorris]

@avamk

This means I must have encrypted my phone in LineageOS 14.1, right?

Right.

@avamk

If so, and just to confirm, if I want to upgrade to LineageOS 16.x, I have to completely wipe my phone

Right. And not just “wipe”, but format the data partition. A “wipe” will just delete the files.

@avamk

but presumably not my micro SD card, right?

Right, if it is formatted as portable storage.

@avamk

If so, exactly what should I wipe from within TWRP?

This is explained pretty well in the official install guide.

The procedure @AnotherElk explains (overwriting the first 2 MB of the data partition with zeros) is not always necessary. I switched from official Fairphone OS (Android 7) to LineageOS 16 and the standard procedure from the install guide was sufficient. Phone was encrypted in Fairphone OS. Not sure why this special treatment seems to be required sometimes.

[lklaus]

I had to reinstall from scratch, due to some glitch, and restored via TiBu backup. System settings were included in the backup. Now, when i switch network allowance in the app info, the setting app crashes, and the the updated network allowance is only activated after a reboot. Anyone else, or do I have to start from scratch and not restore settings?

Edit: this seems only to happen when apps are blocked in the beginning. If net access is allowed, i can toggle it without settings crashing, and change is immediate

Edit2: I got a logcat:

07-27 21:23:02.783 11571 11571 E AndroidRuntime: FATAL EXCEPTION: main
07-27 21:23:02.783 11571 11571 E AndroidRuntime: Process: com.android.settings, PID: 11571
07-27 21:23:02.783 11571 11571 E AndroidRuntime: java.lang.IllegalStateException: command '2410 bandwidth addrestrictappsonwlan wlan0 10191' failed with '400 2410 Bandwidth command failed'
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Parcel.createException(Parcel.java:1958)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:1918)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Parcel.readException(Parcel.java:1868)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.net.INetworkPolicyManager$Stub$Proxy.addUidPolicy(INetworkPolicyManager.java:352)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.net.NetworkPolicyManager.addUidPolicy(NetworkPolicyManager.java:168)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.settings.datausage.AppDataUsage.setAppRestriction(AppDataUsage.java:414)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.settings.datausage.AppDataUsage.setAppRestrictWlan(AppDataUsage.java:408)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.settings.datausage.AppDataUsage.onPreferenceChange(AppDataUsage.java:277)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v7.preference.Preference.callChangeListener(Preference.java:1060)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v7.preference.TwoStatePreference.onClick(TwoStatePreference.java:67)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v7.preference.Preference.performClick(Preference.java:1122)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.settingslib.RestrictedSwitchPreference.performClick(RestrictedSwitchPreference.java:138)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v7.preference.Preference.performClick(Preference.java:1107)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v14.preference.SwitchPreference.performClick(SwitchPreference.java:210)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.support.v7.preference.Preference$1.onClick(Preference.java:172)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.view.View.performClick(View.java:6597)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.view.View.performClickInternal(View.java:6574)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.view.View.access$3100(View.java:778)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.view.View$PerformClick.run(View.java:25906)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:873)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:193)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6718)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.server.NetworkManagementService.restrictAppOnWlan(NetworkManagementService.java:1914)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.server.net.NetworkPolicyManagerService.updateRulesForDataUsageRestrictionsULInner(NetworkPolicyManagerService.java:4000)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.server.net.NetworkPolicyManagerService.updateRulesForDataUsageRestrictionsUL(NetworkPolicyManagerService.java:3975)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.server.net.NetworkPolicyManagerService.setUidPolicyUncheckedUL(NetworkPolicyManagerService.java:2565)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 	at com.android.server.net.NetworkPolicyManagerService.setUidPolicyUncheckedUL(NetworkPolicyManagerService.java:2527)
07-27 21:23:02.783 11571 11571 E AndroidRuntime: 
07-27 21:23:02.826  1107  5731 W ActivityManager:   Force finishing activity com.android.settings/.SubSettings
07-27 21:23:02.835 11571 11571 I Process : Sending signal. PID: 11571 SIG: 9

[chrmhoffmann]

And this worked before? Multicast is disabled for some reason on the kernel - I think since day one.

Chris

[chrmhoffmann]

There are some new sim lock fixes coming in next nightly. I think some people here complained about dual SIM / lock issues.
https://review.lineageos.org/q/topic:"master-fixes"+(status:open%20OR%20status:merged)

Chris

[taurui]

@WoBoW

IGMPv3

Any update on this? Still waiting for my LOS16 upgrade until the Wifi issues are fixed

[JeroenH]

@WoBoW

For the last 2 weeks or so, my WiFi ‘freezes’ and I have to disconnect and connect again to get it online again. I have updated to the latest release, but it’s not fixed yet. No other phones/tablets/laptops are experiencing the same problems with my wireless network.
Anyone with the same issue?
Could updating the modem firmware fix this?

I have the latest modem firmware, Ubiquiti AP, I run LOS 16 (microG version) and I cannot confirm your issue. You can disable multicasting and IGMP on your APs as well. Maybe I did this, not sure.