It is not enough to disable CFlumen itself. You have to disable the "Draw over other apps" for CFlumen.
For me it's sufficient to set the CF.lumen driver to "Rootless" and switch back afterwards.
It is not enough to disable CFlumen itself. You have to disable the "Draw over other apps" for CFlumen.
Google Calendar throws a warning about CF Lumen on every entry.
For me it's sufficient to set the CF.lumen driver to "Rootless" and switch back afterwards.
It is not enough to disable CFlumen itself. You have to disable the "Draw over other apps" for CFlumen.
I need more locations / apps / buttons / screens where this stuff happens. I can't seem to replicate this. Which driver are you guys using? Rootless? Root? KCAL?
And is this final 6.0, or one of the previews?
I need more locations / apps / buttons / screens where this stuff happens. I can't seem to replicate this. Which driver are you guys using? Rootless? Root? KCAL?
I need more locations / apps / buttons / screens where this stuff happens. I can't seem to replicate this. Which driver are you guys using? Rootless? Root? KCAL? And is this final 6.0, or one of the previews?
EDIT: To further clarify: I have a few locations where buttons don't work if the overlay (rootless driver) is active, such as modifying device administrators. However, if I 'disable' CF.lumen by tapping on the notification, it proceeds to work fine. Note that if you tap the notification while in sleep mode, it may go to sundown mode (still an overlay) rather than daytime mode (no overlay).
Is anyone seeing this behavior (unclickable buttons) or getting these error messages with the root driver or KCAL ?
I need more locations / apps / buttons / screens where this stuff happens. I can't seem to replicate this. Which driver are you guys using? Rootless? Root? KCAL? And is this final 6.0, or one of the previews?
EDIT: To further clarify: I have a few locations where buttons don't work if the overlay (rootless driver) is active, such as modifying device administrators. However, if I 'disable' CF.lumen by tapping on the notification, it proceeds to work fine. Note that if you tap the notification while in sleep mode, it may go to sundown mode (still an overlay) rather than daytime mode (no overlay).
Is anyone seeing this behavior (unclickable buttons) or getting these error messages with the root driver or KCAL ?
10-08 07:11:02.705 6425 6425 I mount : type=1400 audit(0.0:227): avc: denied { read } for name="mmcblk0p29" dev="tmpfs" ino=5191 scontext=u:r:recovery:s0 tcontext=u:o
bject_r:system_block_device:s0 tclass=blk_file permissive=1
10-08 07:11:02.705 6425 6425 I mount : type=1400 audit(0.0:228): avc: denied { open } for path="/dev/block/mmcblk0p29" dev="tmpfs" ino=5191 scontext=u:r:recovery:s0 t
context=u:object_r:system_block_device:s0 tclass=blk_file permissive=1
10-08 07:11:02.705 6425 6425 I mount : type=1400 audit(0.0:229): avc: denied { ioctl } for path="/dev/block/mmcblk0p29" dev="tmpfs" ino=5191 ioctlcmd=125d scontext=u:
r:recovery:s0 tcontext=u:object_r:system_block_device:s0 tclass=blk_file permissive=1
10-08 07:11:02.705 6425 6425 I mount : type=1400 audit(0.0:230): avc: denied { remount } for scontext=u:r:recovery:s0 tcontext=u:object_r:labeledfs:s0 tclass=filesyst
em permissive=1
10-08 07:11:02.785 6424 6424 I tmp-mksh: type=1400 audit(0.0:231): avc: denied { write } for name="surfaceflinger" dev="mmcblk0p29" ino=525 scontext=u:r:recovery:s0 tco
ntext=u:object_r:surfaceflinger_exec:s0 tclass=file permissive=1
10-08 07:11:02.785 6424 6424 I tmp-mksh: type=1400 audit(0.0:232): avc: denied { append } for name="surfaceflinger" dev="mmcblk0p29" ino=525 scontext=u:r:recovery:s0 tc
ontext=u:object_r:surfaceflinger_exec:s0 tclass=file permissive=1
10-08 07:11:05.765 6464 6464 I reboot : type=1400 audit(0.0:233): avc: denied { write } for name="property_service" dev="tmpfs" ino=10044 scontext=u:r:init:s0 tcontext
=u:object_r:property_socket:s0 tclass=sock_file permissive=1
...
[B]if [ -f /cache/recovery/libcflumen.so ][/B]
then
ui_print "- Installing ..."
...
[B]else
ui_print "- Uninstalling ..."[/B]
rm $SYSTEMLIB/libcflumen.so
[B]rm /system/bin/surfaceflinger[/B]
cp /cache/recovery/surfaceflinger /system/bin/surfaceflinger
Waiting for itThere really is no use trying to get the driver to work on 5.1.1 or 6.0 until I publish an update.
Using KCAL on M, I'm getting "screen overlay detected" warnings that prevent the functioning of various apps like Telegram. I uninstalled CF Lumen to get things working again.
Excitedly awaiting M compatibility. Such an essential application!
I hadn't seen, it but that is weird. I was using KCAL too. I get the "overlay detected issue" which won't go away until I disable CF Lumen's overlay ability. I went KCAL because ChainFire noted that the Root driver causes bootloops and ain't nobody got time fo' dat.