yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Pretty sure it's possible but it also seems experimental, much more easy with it.

Did you try to select "Recovery mode" in fastboot instead, in my experience TWRP loads at least ones. Then it would just be a matter of getting magisk from github change extension to .zip and flash.
[OnePlus 3 & 3T Cross Device Development] :
You need a recovery able to flash arbritary flashable zips and/or images and/or an unlocked bootloader. Since stock oos recobery doesn't support this the answer is obviously no.

To use los you need los recovery or twrp anyway. If your question relates to stock oos this is obviously the wrong place to ask.

Please also read and respect OP:

Magisk is a mod altering system files.
[OnePlus 3 & 3T Cross Device Development] hemantkarandikar:
My question was regarding first time flashing of twrp and then booting in twrp which was a trial and error processi keeping power and vol buttons pressed. Naturally it was stock os. I was asked to use magisk that's why I asked the question.

So it was in all in context.

Coming from stock to Lineage 18.1 is part of this thread. I followed the OP procedure and had a problem at twrp stage itself, that's why I asked. So don't think it is OT.

btw way I have also raised this in 1+3 twrp thread.

It is a problem. Whether to alert people about it is OP's decision. I felt I should raise it.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Well, one could try to install magisk "manually":

How to Root Android Devices Without TWRP Recovery

In this comprehensive tutorial, we will show you the detailed steps to root any Android device via Magisk patched boot.img file without TWRP

www.droidwin.com

But why make this any more complicated than it needs to be.
[OnePlus 3 & 3T Cross Device Development] :
You need to read my posting more carefully. I wtote:

To manually root the device, you need to flash the patched boot image via fastboot. To flash the patched boot image, you need an unlocked boot loader.

Since this makes no sense, because you need a custom recovery for running los.

You can always boot a custom recovery with an unlocked bootloader, without flashing it (fastboot boot twrp*.img), flash los and boot the flashed los (which will boot with unlocked bootloader) I see no reason to install magisk on oos in order to install los.
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Yeah I couldn't see a reason either not to use a custom Recovery but went ahead answering the question anyway which was:

Then I strongly suggested to use TWRP.

My point was that you don't have to lock the bootloader to make Twrp stick regardless of OS. Last time I did install magisk in OOS was when I flipped the experimental VoLTE bit in the firmware, still wonder if that was necessary.
[OnePlus 3 & 3T Cross Device Development] Keyvannn:
Any hope for android 12?
[OnePlus 3 & 3T Cross Device Development] snyperius:
There's always hope, but this topic is for LOS 18.1 based on Android 11
[OnePlus 3 & 3T Cross Device Development] bian_ki:
I can't use NFC for working with Mifare Classic tags and Yubikey token.

I don't know about payments, I don't use them.

Is this a known issue for LineageOS 18.1?
[OnePlus 3 & 3T Cross Device Development] nasana3:
VoLTE works with these instructions:

https://xdaforums.com/t/vowifi-volt...n-t-mobile-germany-and-possibly-more.4166511/
[OnePlus 3 & 3T Cross Device Development] generalprobe:
Is there a way to find out what drains my battery? I know there is better battery stats, but even though my phone consumes 2% of battery per hour (full idle for 10 hours overnight) I do not see anything noteworthy under "partial wakelocks", also "kernel wakelocks" do not add up to the full "awake / screen off" time.

I even did a full reset of the phone end of September, it worked for two or three weeks, but out of the sudden it started again. I did not even update to the next nightly ...

This is such a great phone, but it is barely useable for me, if it runs out of battery after a few hours of useage.

Please help!
[OnePlus 3 & 3T Cross Device Development] :
And also the overview when clicking on the percentage under battery is not giving any hints? When you are talking about wakelocks I am almost sure you checked that, but just to be sure... 😉
[OnePlus 3 & 3T Cross Device Development] generalprobe:
@Jan_L

Yes, the built in "Battery App" shows me 4-5% consumed but my phone is at 60% battery. Even if I enable all system apps on the "three dots" i roughly get up to 1/2 of the drained battery (which would be the normal/expected level of drain)
[OnePlus 3 & 3T Cross Device Development] hlfire:
First and foremost, like to thank everyone for making 18.1 official alive and well with OP3T.

I custom rom multiple phones even with nightlys regularly so I know the process well and even tried tinkering sideload vs internal storage, Gapps, no-Gapps, etc.

I still have a nagging issue that makes this ROM a major pain and unusable.

My phone boots fine and works without any problems until i lock the screen (or timer locks it). When i unlock it i can hear i unlocked the screen properly, by power button press or by fingerprint. The screen is still black and dark.

I did enable double click toolbar top to re-enable lock to troubleshoot. So what i do is able to relock by double clicking top part of the black screen and hear the phone relock. I unlock via fingerprint and it's dark again. It would do this 9/10 times with the odd 1/10 times screen showing.

I know i'm going into lock and unlock properly not just from sounds but also by setting LEDs on the touch buttons turning on. I can replicate this over and over and found on avg 1/10 times to be successful in getting screen displayed (not black). FYI when it's black, you can still open apps and do other stuff but you are doing it blind.

I experimented with changing display options, font sizes, color,, you name it but unable to find a workaround fix.

Anyone have a fix, workaround, suggestion or solution? Else i just need to wait for the next latest nightly to release and retry and hope one day this bug is fixed on my OP3T.
[OnePlus 3 & 3T Cross Device Development] :
@hlfire:

What about other non-oos based, source build roms? Is the diaplay panel original or replaced with a third party panel? Sounds to me like the well known panel bug, but maybe my memory tricks me. Please search the older los (15.1 to 17.1) threads.
[OnePlus 3 & 3T Cross Device Development] spaniard:
Hi there, anyone knows wich would be the best Gcam available for 18.1? No config files for Oneplus 3T in the latest versions.

Many thanks
[OnePlus 3 & 3T Cross Device Development] hlfire:
The panel I cannot confirm is original as I'm was given the phone (not brand new). However, i didn't have such issues running stock rom. I see issues with older threads which i searched prior to this post but found nothing similar.

I may just load 17.1 and see.
[OnePlus 3 & 3T Cross Device Development] :
I can't tell if you havn't found the conversations on black screen after panel replacement (then you havn't searched hard enough, or has been too lazy to search for "replacememt screen wake" over the forum, after my last posting), or if your issue is completely different (then you are on your own, necause you are the only one suffering from this).

A few examples:

https://xdaforums.com/t/rom-officia...r-oneplus-3-3t.3866517/page-180#post-81298117

https://xdaforums.com/t/rom-officia...r-oneplus-3-3t.3866517/page-168#post-80480431 fff.

Initial search:

https://xdaforums.com/search/287164...c[child_nodes]=1&c[nodes][0]=6157&o=relevance
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I have replaced my screen before. Just clear the cache and all is good.
[OnePlus 3 & 3T Cross Device Development] hlfire:
I tried that. Thanks for tip anyways. I tried other roms like pixel experience doesn't have this issue.

@nvertigo67 thanks for additional suggestions. Will debug see what display is since I don't know if it's original.
[OnePlus 3 & 3T Cross Device Development] Kani222:
My battery drain without any use
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Had a kernel panic restart after swiping away a notification. First time I've had this problem since installing the rom 16 days ago.
[OnePlus 3 & 3T Cross Device Development] :
Sorry, but the ramops is from a boot the system was up for 160 seconds. So I'm pretty sure it's not from the crash but from a boot after the system crash.

For the hotspot test: 2.4 or 5GHz? If 5GHz: which channel? (Not urgent at all!)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Hmm. I took a cat of /sys/fs/pstore/console-ramoops after phone restarted from the panic. That is supposed to be the last kernel, right?

The hotspot was 2.4 GHz because my PC doesn't support 5 GHz.

PS: unless it wasn't a kernel panic just a system UI reboot? I have no idea. I just assumed it was a kernel panic based on the behaviour: swipe a notification and the phone reboots - but not a full reboot because I wasn't prompted for the on-boot password.
[OnePlus 3 & 3T Cross Device Development] :
EDIT:

Yes, exactly from the previous boot.

The log you've posted says:

[ 0.000000] Linux version 3.18.120-lineageos-g4a67382 (gitlab-runner@lineage-runner) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Apr 15 11:05:48 UTC 2019

and as last line:

[ 199.298383] msm_restart_prepare : cmd is , set to reboot mode

From the Linux version git hash (4a67382) you can see the last boot hasn't been a system boot (neither los 18.1 nor los 17.1 is currently - or even lately - on this hash), so I guess it's the twrp boot (I have no idea where the current twrp kernel for our device lives).

From the last lime we know the last boot ended after 199.3 secomds of uptime. This is not nearly the 16 days you mentioned and fits better for a short recobery session.

The current 18.1 kernel supports pstore:

(End of EDIT)

android_kernel_oneplus_msm8996/arch/arm64/configs/lineageos_oneplus3_defconfig at lineage-18.1 · LineageOS/android_kernel_oneplus_msm8996

Contribute to LineageOS/android_kernel_oneplus_msm8996 development by creating an account on GitHub.

github.com

You can always check, if pstore is enabled by booting from running system to system and check if console-ramoops and pmsg-ramoops-0 are present.

Maybe. A kernel panic leads to an unresponsive device, but not to a reboot.

You can trigger a kernel panic by these two commands in a rooted shell:

echo 1 > /proc/sys/kernel/sysrq && echo c > /proc/sysrq-trigger

Leading to an unresponsive device, the screen blanks after about 10 seconds (only if the screen was on ;) ) and after another 10 seconds the notification light goes white. To recover press power until the white light wents off and switch on the device again.

Maybe related, maybe not:

Which twrp are you using?

I've just tried to copy pstore after triggering a kernel panic. Booted directly to twrp-3.5.0_9-0 and pstore was empty. :(

After checking in a running rom console-ramoops and pmsg-ramoops-0 were present, I normally rebooted to twrp-3.5.0_9-0. I found pstore empty. :(

Rebooted from twrp-3.5.0_9-0 to twrp-3.5.0_9-0: pstore empty. :(

Flashed twrp-3.4.0-0 and rebooted to twrp: console-ramoops and pmsg-ramoops-0 were present. :)

Rebooted to system, loged in, rebooted to twrp-3.4.0-0: console-ramoops and pmsg-ramoops-0 were present. :)

Rebooted to system, log in, triggered a kernel panic, booted directly to twrp-3.4.0-0 and found console-ramops, pmsg-ramops-0, dmesg-ramoops-0 and dmesg-ramoops-1.enc.z.

Conclusion: with twrp-3.5.0_9-0 it's not possible to get pstore from the previous crash. Since this is fixed I strongly recommend to use twrp-3.4.0-0 - especially on an experimental rom (to provide mandatory information on crashes)!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I love that you explain how things work.

I now understand that I didn't have a kernel panic and that the kernel messages I posted were from a recovery session. So I must have had a UI restart and I should have posted a logcat. I'll do that if the problem happens again.

I also found that:

1. After a reboot into recovery, console-ramoops is present in TWRP (3.5.0) and contains the kernels messages showing the reboot to recovery.

2. After a reboot from recovery to system, console-ramoops shows the last TWRP kernel log.

3. Triggering a kernel panic and then rebooting produces no console-ramoops.

So it seems to me that there's no way to capture the kernel log from the kernel panic.

Question: what does the pmsg-ramoops-0 file contain? I looked at it but it looks nothing like the kernel log or the system log.
[OnePlus 3 & 3T Cross Device Development] :
twrp-3.5.0_9-0 is broken at this point. twrp-3.4.0-0 will work fpr gettimg pstore. You can also get the pstore if directly booting to system again after a kernel panic, but accessing pstore from within the rom tequites root previlegs.

That's a good one. It contains userspace messages the kernel can capture at the time of the kernel panic. Honestly, I've never found something usefull/helpfull when debugging some crash (don't get me wrong, I don't mean it doesnt contain usefull information, I'm just saying I havn't found it... ;) ).

The linux lernel documentation may shine some mote light on pmsg:

https://www.kernel.org/doc/Documentation/devicetree/bindings/reserved-memory/ramoops.txt

Or the linux kernel's admin guide:

https://www.kernel.org/doc/html/v4.15/admin-guide/ramoops.html (though not available for 3.18)[/QUOTE]
[OnePlus 3 & 3T Cross Device Development] nate1975:
Sadly, it doesn't seem to be. I've never seen this before and have used Android Auto many times in the past (2018 Chevrolet Cruze).

Maybe on your car it would be ok?
[OnePlus 3 & 3T Cross Device Development] ash1425:
I had same message. I installed Android Auto addon from NicksGapps and it's working now.
[OnePlus 3 & 3T Cross Device Development] nate1975:
Good to know if I ever run into that again.
[OnePlus 3 & 3T Cross Device Development] matrixino:
Would be nice to have a real confirmation before formatting everything to switch to A11. No one is using LOS with Auto?

Also Screencast still not working right?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
A bit more information on getting logs after a kernel panic.

I decided to test collecting console-ramoops with both TWRP 3.4 and 3.5 but I needed a baseline.

So I also checked the contents in /sys/fs/pstore by booting back into the system after a kernel panic.

My procedure was:

1. Power off the phone

2. Boot into system

3. Verify that /sys/fs/pstore was empty

4. Trigger a kernel panic

5. Wait until the WLOD (white light of death)

6. Reboot the system

7. Check the contents of /sys/fs/pstore

To my surprise only 2 out of 5 of these test produced a console-ramoops!

So much for getting a baseline. I decided it was pointless to compare TWRP versions given that I couldn't get a consistent baseline.
[OnePlus 3 & 3T Cross Device Development] :
The base line is: stupid me!

Since pstore is a reserbed area in ram, it's lost if the ram isn't powered anymore.

Following my instructions (leaving the power button alone, when WLOD goes of, and then powering the device on again) the time between letting go the power button and pressing it again is crucial! If done immediatly, pstore survives in 8 out of 10 tests.

If I wait for 15 seconds after WLOD is off before powering on again, pstore is empty in 10 out of 10 tests.

If I doesn't stop pressing power after WLOD goes off but press power until the vibration signals power on and use the "unlock warning" to boot to recovery, pstore survives in 13 out of 13 tests (1-10 twrp-3.4.0-0; 11-13 twrp-3.5.0_9-0 - sick to test more, the bootanimation has burned in my retina).

Remarks:

- After the second test I've switched off the encryption passphrase.

- All kernel panics was issued via adb over network (adb via usb starts powered off charging, which boots the system's kernel, which popuöates pstore).

Sorry for being a moron, who blames twrp-3.5.0_9-0 for being buggy regarding pstore.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That's the way I did all my tests, even the earlier ones: once the WLOD is showing, I hold down the power button until the phone reboots and then either let it boot normally or select recovery by pressing the volume button.

I agree, typing in the password and watching the boot animation gets very boring. But I now know that my phone takes 45s from the time I press enter on the password screen until the three circles show up 😊.

Thanks for your tests. At least we know that TWRP 3.5 is fine.

Question: did you do your tests on Los 17.1 or 18.1? Because I find it odd that 18.1 didn't consistently produce the console-ramoops file in my tests.
[OnePlus 3 & 3T Cross Device Development] nate1975:
Yes, it works if you flash the gapps addon. Sorry Android Auto has always seemed like more trouble than it's worth to me, so I didn't bother checking until today.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Had another "UI restart" (not kernel panic 😊). The phone froze for a few seconds and then rebooted (didn't prompt for the on-boot password, so not a full reboot).

I've attached logcat and dmesg taken after the restart.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Can confirm this issue.
[OnePlus 3 & 3T Cross Device Development] :
3.4.0-0 and 3.5.0_9-0 use the same kernel. If I compare the current 18.1 kernel against the twrp kernel version (still not found the sources for twrp kernel, but the commit is somewhere deep in the lineageos kernel repository) for fs/pstore, I get (< means That commit is in lps 18.1 but not in the twrp kernel):

git log --left-right --graph --cherry-pick --oneline FETCH_HEAD...4a67382 -- fs/pstore/
< e5902aa2ae77f Merge 3.18.123 into android-3.18
|\
| < 36a9916189b46 pstore: Fix incorrect persistent ram buffer mapping
< caed67240e185 Merge 3.18.121 into android-3.18

This is only kernel related, I use an upstreamed kernel with some additions, fixes and aditions (https://github.com/nvertigo/android...tree/66c8c90d00aaffafdcd050db356ee80a2271ca1e )

If I compare that (< means the commit is in los 18.1 but not in my kernel; > means the commit is not in the los 18.1 kernel, but in my kernel):

git log --left-right --graph --cherry-pick --oneline FETCH_HEAD...66c8c90d00aaffafdcd050db356ee80a2271ca1e -- fs/pstore/
< e5902aa2ae77f Merge 3.18.123 into android-3.18
< caed67240e185 Merge 3.18.121 into android-3.18
> 9a18b3b1adfe6 pstore/core: drop cmpxchg based updates
> c407a0d8cb1fc pstore/ramoops: fixup driver removal
> ba85c198619e1 pstore/ram: Write new dumps to start of recycled zones
> 718cd091a84af pstore/ram: Do not treat empty buffers as valid
> 06ec9c678bda3 pstore: Convert console write to use ->write_buf

Maybe this helps to narrow down the bug. The real problem in hunting this down is the fact that you have pstore to debug, if the bug doesn't kick in, but when it kicks in, there is no pstore to debug. That's a dilemma. :(

Looks like willyweather is killing the SystemUI on zygote level (I have no idea if the system should avoid that and willyweather is only trihherimg the rom's bug, or if willyweather needs an update - maybe you can uninstall willyweather and check if the crash is happening again):

--------- beginning of crash
03-01 22:49:59.936 11193 11193 E AndroidRuntime: FATAL EXCEPTION: main
03-01 22:49:59.936 11193 11193 E AndroidRuntime: Process: au.com.willyweather, PID: 11193
03-01 22:49:59.936 11193 11193 E AndroidRuntime: android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{be8a332 u0 au.com.willyweather/heyalex.widgethelper.WidgetUpdateService}
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2005)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:106)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:223)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:7660)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
03-01 22:49:59.936 11193 11193 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
[OnePlus 3 & 3T Cross Device Development] :
See my previous posting, please check the crash in your logcat.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
I don't have 18.1 anymore, I reinstalled 17.1 because of these random reboots, so I can only confirm that the issue exist and it's not only of Bill, but thank you for looking at it.
[OnePlus 3 & 3T Cross Device Development] Super Jamie:
I have a OP3T which has been running LineageOS 16. I'm trying to update to 18.1 but I keep getting the error:

E1001: Failed to update system image.
Updater process ended with ERROR: 1

I'm running latest TWRP twrp-3.5.2_9-0-oneplus3.img. I tried extracting boot.img from the ROM and flashing that to boot with TWRP. I tried Formatting and Repairing all filesystems with TWRP. I tried flashing the latest 9.0.6 firmware (iirc I had done this before anyway). I tried flashing the current 20211108 and previous 20211101 official images and the unofficial microG version, same error so it doesn't seem like a bad download. I tried both adb sideload and copying the ROM to the phone with MTP. I tried flashing latest OxygenOS and LineageOS 17, but they both fail with Error 7.

Any help would be appreciated.
[OnePlus 3 & 3T Cross Device Development] kash_si:
Before flashing in TWRP - if your System partition is mounted, unmount it and try flashing.
[OnePlus 3 & 3T Cross Device Development] Super Jamie:
Thanks for the suggestion. I made sure I had System unmounted, and selected the TWRP option to unmount System before flashing any zip. Still no luck.
[OnePlus 3 & 3T Cross Device Development] kash_si:
Thanks for your feedback. Out of curiosity you are Not Encrypted, Correct ?

In TWRP, I always Wipe ALL Partitions and then Format Data Partition. Then I flash the Rom, GApps.

I have successfully flashed multiple Custom Roms on my OP3/3T over the years and never received any error message like yours.
[OnePlus 3 & 3T Cross Device Development] Super Jamie:
Correct, I've never had encryption enabled. I am also doing those same steps as you. I also tried old TWRP 3.4.0 but same result.

I'm starting to wonder if the phone has faulty storage and I just haven't noticed because I haven't flashed a ROM since the LineageOS 16 which I put on there many years ago. I've used the phone daily until recently, but that doesn't mean the storage is all working.
[OnePlus 3 & 3T Cross Device Development] spaniard:
Hi there, does it exist a way to get aptX bluetooth codec other than installing the Magisk module?
[OnePlus 3 & 3T Cross Device Development] borisSweden:
Now on 18.1, I dont get a single profile with PDC. Only SW and HW.
[OnePlus 3 & 3T Cross Device Development] :
Did you check the downloaded zip's sha256 checksum? Whats the complete error message in the recovery log?
[OnePlus 3 & 3T Cross Device Development] :
I don't see the relation to the init extension. Please explain what's wrong with the model setting in the init extension.