[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] TheSSJ:
Indeed, odd. It seems to have broken along the way, but I see logs mentioning the brightness sensor spitting out values, so I most likely broke it with some overlay settings, will restore to the last known status and check again.

Glad you like it. Prime video works, so is Netflix complaining really about a custom ROM? I could think about DRM components missing, which cause Netflix to abort (a log would help to confirm). Will build it in to see if this fixes the errors, just to make sure it's not because of missing DRM. Regarding fingerprint I am using it right now with my banking app and it works? Unbelievable how different a ROM can behave...........

Sorry for the late notice - the test build about fixing BT calls really fixed the issue :) will upload the version as soon as my company network is not blocking me anymore ^^

EDIT: just so you know what I am currently fighting with regarding hotspot:

:/sdcard # cat dmesg.txt | grep -i iptables
[06-12 15:54:49.477] [4][660: iptables-resto]Unable to handle kernel NULL pointer dereference at virtual address 00000000
[06-12 15:54:49.477] [4][660: iptables-resto]pgd = ffffffc0a2fe9000
[06-12 15:54:49.477] [4][660: iptables-resto]Internal error: Oops: 96000005 [#1] PREEMPT SMP
[06-12 15:54:49.477] [4][660: iptables-resto]CPU: 4 PID: 660 Comm: iptables-restor Tainted: G W 3.10.84-perf-ga485a113149-dirty #2
[06-12 15:54:49.477] [4][660: iptables-resto]task: ffffffc0ac3dd240 ti: ffffffc0a33f4000 task.ti: ffffffc0a33f4000
[06-12 15:54:49.477] [4][660: iptables-resto]PC is at destroy_conntrack+0x98/0x1b4
[06-12 15:54:49.477] [4][660: iptables-resto]LR is at destroy_conntrack+0x90/0x1b4
[06-12 15:54:49.477] [4][660: iptables-resto]pc : [<ffffffc000becfe0>] lr : [<ffffffc000becfd8>] pstate: 20000145
[06-12 15:54:49.477] [4][660: iptables-resto]sp : ffffffc0a33f7bb0
[06-12 15:54:49.477] [4][660: iptables-resto]
[06-12 15:54:49.477] [4][660: iptables-resto]Process iptables-restor (pid: 660, stack limit = 0xffffffc0a33f4058)
[06-12 15:54:49.477] [4][660: iptables-resto]Call trace:
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000becfe0>] destroy_conntrack+0x98/0x1b4
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000be7614>] nf_conntrack_destroy+0x28/0x38
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c0b784>] xt_ct_tg_destroy.isra.7+0x44/0x50
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c0b7a4>] xt_ct_tg_destroy_v1+0x14/0x20
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c65e4c>] cleanup_entry+0x6c/0x80
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c665c4>] __do_replace+0x11c/0x18c
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c6749c>] do_ipt_set_ctl+0x198/0x218
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000be8628>] nf_setsockopt+0x68/0x88
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c26940>] ip_setsockopt+0x78/0x9c
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000c43820>] raw_setsockopt+0x10/0x50
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000baa570>] sock_common_setsockopt+0x14/0x20
[06-12 15:54:49.477] [4][660: iptables-resto][<ffffffc000ba67f4>] SyS_setsockopt+0x88/0xb8
[06-12 15:54:49.477] [4][660: iptables-resto]Code: 9101e2f7 94060915 f84f0f35 910d737b (f94002ba)
[06-12 15:54:49.477] [4][660: iptables-resto]---[ end trace 077158e32f8f2461 ]---
[06-12 15:54:49.917] [4][660: iptables-resto]Kernel panic - not syncing: Fatal exception in interrupt
[06-12 15:54:49.917] [4][660: iptables-resto]scm_call failed: func id 0x82000301, arginfo: 0x1, args: 0x1, 0xffffffc0a33f75c0, 0xffffffc000a01368, 0xffffffc0a33f75d0, ret: -5, syscall returns: 0x0, 0x0, 0x0