NGCam_7.4.104-v2.0_eng.apk in conjunction with Aux_Mod_V2.1.zip can use the auxiliary camera separately. Additionally OnePlus5&5T-DotFix-v6.0.zip should be installed for best results.
You can change the magisk file extension to zip and flash with TWRP, it's covered in the magisk Wiki.Hi folks, sorry if this has been asked, I searched and could not find a definitive answer.
As you all know for magisk 23 to install you need a ramdik image.
I read somewhere that you can not just use the ramdik.img that's in the root folder of lineage 18.1.
So how do you root lineage 18.1 with magisk 23?
Sorry for the basic question I might be missing something obvious.
Thank you in advance.
Yup, that could be the issue. Try inserting a sim on your phone and see.
May I ask what the Aux_Mod changes/enables on a OnePlus 5/5T? On my 5T with the mentioned gcam and dotfix package the second camera is already usable (as a separate camera - I can choose between camera 1 and 2).
Yes I confirm you can use Magisk 23 with LineageOS 18.1 on the OP5T.
Same issue here on 5T. Don't see an always on option as hinted by the AOD commit.Timi, I noticed in the latest build this was merged in
https://review.lineageos.org/c/LineageOS/android_device_oneplus_msm8998-common/+/312168 and thought AOD has been enabled on the devices. In the settings of ambient display I don't see the option to have ambient display always on though. Am I missing something or is it only working on dumpling and not cheeseburger?
This doesn't bother me that much as I use GCam most of the times but I can reproduce this issue on latest build.
I had installed that module at the time when I installed the camera app (was on 17.1) and things worked ever since. That is why I wrote about my experience with them. Because you wrote that you don't need the module I unistalled it now and can confirm that the app can still use the second camera selectively. Obviously the module is not needed by the app on a OP5.
I don't see anything on OnePlus 5 either.
Why is it not possible to use the OnePlus cam...? If proprietary blobs are placed at expected location, will it not work?
Problem solved. Because the phone was no sim card and therefore only 2.4 Ghz hotspot mode was available. I put in the sim card and immediately got to choose the 5 GHz frequency.
Using the Magisk Hide Props Config module
I can't find any option to enable gesture navigation (or swipe navigation).
Initially, I thought it was the Gapps I installed does not support, then I re-flash latest ROM with either MindTheGapps or OpenGApps, still not able to find this option in Settings.
Does anyone have the same?
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":View attachment 5278115
I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
Issue was caused by CAF change in kernel a while back.Same here. Happened three times since I'm on 18.1. In all three occurences I plugged in the charger directly after I had a usb audio dac connected while using the usb audio player pro app. I use this dac and app regularly and normally the phone charges fine afterwards, so not sure if there is any relation.
For the rest very happy with 18.1!