I noticed that Bluetooth Dual Channel turns off after every disconnect, is it possible to enable it permanently?
Well... I clean flashed the lineageos nightly, but at first sight, it seems to be having the same problem. I was going to test it for a few days, but I wanted my apps, but I forgot to backup them (using migrate). So I restored my nandroid to be able to create the backup. But when I restored my nandroid, I noticed something: wifi was working a lot better (like right after I first flashed your test kernel, which seems to be working back then). And LiveDisplay was working again (which was broken for me). So I decided to keep using it for a few more days. Now, after it been using for a few days, LiveDisplay is still working, and wifi is still much better than before (still not perfect, but improved noticeable).
But did you try the new kernel I posted on November 2nd?Well... I clean flashed the lineageos nightly, but at first sight, it seems to be having the same problem. I was going to test it for a few days, but I wanted my apps, but I forgot to backup them (using migrate). So I restored my nandroid to be able to create the backup. But when I restored my nandroid, I noticed something: wifi was working a lot better (like right after I first flashed your test kernel, which seems to be working back then). And LiveDisplay was working again (which was broken for me). So I decided to keep using it for a few more days. Now, after it been using for a few days, LiveDisplay is still working, and wifi is still much better than before (still not perfect, but improved noticeable).
So I didn't test a clean flash for a long time, as my current setup is working better than before, and it's alot of work to setup and configure a complete new rom (and I would rather be using your rom, than the 'standard' LineageOs one).
I'll update to the new november build, hopefully it stays working the way it is now.
Yes, I'm using it now. It didn't resolve the issue, but after flashing the Lineageos nightly and restoring my nandroid, it is working quite well.
ro.secure=1 is already set. Try to add ro.debuggable=0 in the /system/build.prop file, it should override the value in the default.prop.hello,
sorry for being out of topic..
I don't root my phone as it will make my banking app unusable..
using this rom is okay as long as I modify these lines on build.prop and default.prop..
ro.secure=1
ro.debuggable=0
on last rom, I was able to modify those lines using abd push, pull, chmod,
maybe i am doing some wrong step this time but on latest rom i couldn't modify default.prop at /
it will revert on reboot..
build.prop and default.prop in /system or /system_root could be modified just fine..
is there a way for me to modify default.prop at / ?
I am not really techsavvy,
but I tried aik but I couldn't fine anything in ramdisk folder after unpacking boot.img,
well, I just used the boot.img from downloaded rom..
thank you..
ro.secure=1 is already set. Try to add ro.debuggable=0 in the /system/build.prop file, it should override the value in the default.prop.
I guess something is wrong, try to update to the latest official MindTheGapps: https://androidfilehost.com/?fid=7161016148664811245hi, in my folder /data/system/dropbox/ there are a lot of files with the same content and they appear nonstop. i use your gapps. this is normal? I attach the file and logcat (log.txt)
another small problem is that systemUI often crashes if the lock screen is disabled, but with swipe unlock everything is fine. for some reason I cannot reproduce the crash, so there is no log.
Let me check this - I'll let you know.Had to return to my good old trusty OnePlus One after my Pixel 2XL's usb-c port fried itself and won't work with usb hub adapters anymore nor fast charge... such garbage from Google.
I'm so glad to see you're still developing @Tomoms! I just tried your kernel with /data and /cache formatted as f2fs running full disk encryption and it still won't boot since your last 2020 build where it stopped working... I noticed the official lineageOS 18.1 December '21 Rom/kernel work perfectly fine.
Is there something different with the f2fs drivers between your kernel and lineageOS's official one?
Happy holidays my friend
I'll check everything and will update you in a few days!In my case, your last 6th November build do constant reboot at the time it shows decryption pattern.
I mean, it loads, shows first boot animation, then shows pattern (I'm using 4x4) and immediately reboots.
Previous build run fine.
OPO is my spare device now, and I have no time to install that build at the time you release it, so try it only today...
I do full format of /system and wipe /data and /cache. Also do fsck from twrp.
And, yes - I still have f2fs and FDE.
This new release seems to have fixed the issue of sharing images from inside the gallery to apps such as Signal.
This new release seems to have fixed the issue of sharing images from inside the gallery to apps such as Signal.
Nice! I have no idea why, though xD
Just attempted to upgrade (OTA as always). Download was OK, there was no flashing error, but when the system came back up, it presented me with the same update (and kept reporting it was still at Jul 8).
Also booting into TWRP and running the install manually gave no hint at something going wrong (Magisk was renewed as expected).
At the moment I have no way to check whether the version *in* the zip might be still at the old date, which is what I'd suspect now...
I was just about to ask if anyone else has the same problem as me and @steve8x8 . Update seems to be fine in TWRP but the build date is still 8.7. after reboot.
/system/vendor/etc
ro.debuggable=0
by default (fixes root detectors reporting system as rooted when it is not)