Its not my wallpaper and dock also showing like thatDid you verify its not your wallpaper?
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
Well somehow its fixed itself
Its not my wallpaper and dock also showing like thatDid you verify its not your wallpaper?
Do you have any root apps that have access to system? They might interfere with Substratum or something. If you flash it alone (Without apps and no other apps) and the issue isn't there, then it shouldn't be ROM related. But still, i hadn't seen this issue, and there shouldn't be commits or modifications that could allow this.Its not my wallpaper and dock also showing like that
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
Well somehow its fixed itself
They have yet to be added.Off screen Gesture its working only double tap wake up working can anyone help me
Nah, no ColorOS at such an early stage.Hi ! Did you tried to includ ColorOS camera blobs like Jgcaap in his builds ?
Why not ?Nah, no ColorOS at such an early stage.
Because CM blobs still don't work fully. That needs to work better before ColorOS blobs can be implemented.Why not ?
Oh okay, I understand. Thank youBecause CM blobs still don't work fully. That needs to work better before ColorOS blobs can be implemented.
SuperSU should install in systemless mode. perhaps wrong zip? However Background light has been fixed on my build locally, should be up in the next build. Also, i'm integrating a button setting in Settings so we can switch between Navbar and HW. Once i'll have that working, i'll release the next build.Very thanks for your amazing ROM, but I have some problems I have disable the hw keys like the picture but the background light is still turn on and the hw keys is useless how can I turn off the background light,and I'm flash the SuperSU 2.78 sr1 but it's don't install in systemless mode how can I do it can install in systemless mode
Yeah I tried actually, but had no luck. If someone has worked with them before, please HMU on Hangouts. I've managed to boot but it doesn't hook up to the camera. Perhaps kernel modifications? I don't know if they run on CAF Drivers or Camerav2Oppo from CM.Hi ! Did you tried to includ ColorOS camera blobs like Jgcaap in his builds ?
I'm not a dev but I think you need kernel side mods to make different camera blobs to work. I know with Jgcaap's CM13, if you flashed Boeffla, camera would not connect. I read that this was due to different camera stuff in his kernel. From what I remember at least...Yeah I tried actually, but had no luck. If someone has worked with them before, please HMU on Hangouts. I've managed to boot but it doesn't hook up to the camera. Perhaps kernel modifications? I don't know if they run on CAF Drivers or Camerav2Oppo from CM.
I'm flash the SuperSU 2.78sr1,but it's really in system mode like the pictureSuperSU should install in systemless mode. perhaps wrong zip? However Background light has been fixed on my build locally, should be up in the next build. Also, i'm integrating a button setting in Settings so we can switch between Navbar and HW. Once i'll have that working, i'll release the next build.
Yeah I tried actually, but had no luck. If someone has worked with them before, please HMU on Hangouts. I've managed to boot but it doesn't hook up to the camera. Perhaps kernel modifications? I don't know if they run on CAF Drivers or Camerav2Oppo from CM.
Thanks for the heads up. I'll run a diff.I'm not a dev but I think you need kernel side mods to make different camera blobs to work. I know with Jgcaap's CM13, if you flashed Boeffla, camera would not connect. I read that this was due to different camera stuff in his kernel. From what I remember at least...
Yeah that's Android's SU binary. It comes bundled with Android (since we're using userdebug builds), and SuperSU need it as a symlink. It's untouched and should be there.I'm flash the SuperSU 2.78sr1,but it's really in system mode like the picture
No,If in systemless mode it should be in /xbin/suThanks for the heads up. I'll run a diff.
Yeah that's Android's SU binary. It comes bundled with Android (since we're using userdebug builds), and SuperSU need it as a symlink. It's untouched and should be there.
Yeah I saw an old changelog quoting that. I'm not really into SuperSU dev stuff, but removing that binary doesn't affect SU. I'm guessing the files are somehow hidden, or root is somewhere in the boot image. Also, it doesn't come up if you remove it and flash the SuperSu zip again.No,If in systemless mode it should be in /xbin/su
But when I to flash the suhide it's say I'm don't in systemless modeYeah I saw an old changelog quoting that. I'm not really into SuperSU dev stuff, but removing that binary doesn't affect SU. I'm guessing the files are somehow hidden, or root is somewhere in the boot image. Also, it doesn't come up if you remove it and flash the SuperSu zip again.
So yeah, i think you can keep it or remove it, shouldn't affect anything. It's probably not even being used, but just being left there. You could ask in the SuperSU thread for clarifications.
Shell command "top" shows no signs of system/xbin/su being used. Also, when flashing it, the log says system-less is compatible.
My bet is: that binary is a leftover.
Thank you for clarifications. All files appear to be in their correspective folder. (/supersu and /data/su.img, but you have to look either with a root explorer, or in recovery. Otherwise they won't appear.)The su binary in systemless mode is in /data/su.img which is mounted in /su/ and then bind mounted around the system
From what i recall, suhide is experimental and unstable. It's in first-stage development. It might be that on my rom it recognizes root as system-root, but it is not. You may ask it in suhide or superset's thread for clarification, as stated above. On my side, everything is as it should be, and there are no major modifications that would not allow SU to run Systemless on my build.But when I to flash the suhide it's say I'm don't in systemless mode