Develop Bugs

[ROM][5.1.1 LYZ28N][November 2016][Maintainer builds]OmniROM for n8000/n801x

​
About OmniROM
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Click to expand...
Click to collapse
Info from omnirom http://omnirom.org/general/android-l-omnirom-progressing/
Disclaimer
Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.
This is an early stage release so many things are broken since many patches and fixes haven't been imported from old branches yet.
How to install:
Reboot to recovey
A backup is Recommended, you're gonna loose all your data
Wipe data
Flash rom
Flash SuperSU 2.19 2.40 or up just after the rom
http://download.chainfire.eu/supersu -> This is IMPORTANT
Flash Netflix fix if you need it -> Download
Reboot
Around 5 minutes are required for the first boot
Reboot again to recovery
Flash Gapps (See below)
How to update from a previous version:
Reboot to recovey
Flash rom
Flash SuperSU 2.40 or up just after the rom http://download.chainfire.eu/supersu -> This is IMPORTANT (not needed anymore)
Flash Netflix fix if you need it -> Download
Reboot
Gapps download:
Check http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
How to report a bug
Use the search function, if the bug has already been reported and I or another person has answered do NOT report it again. I'm tired of writing ten times the same thing.
A bug report function is embedded in XDA forum look at the top there's a section called "Bug Reports". Use it
Provide a logcat and/or dmesg. Search on XDA if you don't know how to get a proper log
Always provide which model you are using and other information that you think could be useful to solve the bug
Downloads:
This is an early preview with lots of bugs and not usable as a daily driver. You have been warned. Flash this only if you are sure about what are you doing.
Download folder: https://www.androidfilehost.com/?w=files&flid=21696
Starting from 20150506 I'm uploading automated builds: this means that they should be treated as nigthlies (I won't create a new one every 24 hours though). All the new files will be placed in the "Download folder" automatically, so, if no new changes from my part, I will NOT update the changelog. These builds will include all the updates and commits from official Omnirom repos plus my commits not yet merged for our tablets. Good luck
Commits: -> Updated to 5.1.1_r2
Necessary commits
In frameworks_native: https://gerrit.omnirom.org/#/c/13068/ and https://gerrit.omnirom.org/#/c/13069/
In frameworks_av: https://gerrit.omnirom.org/#/c/12528/, https://gerrit.omnirom.org/#/c/12529/ and https://gerrit.omnirom.org/#/c/12530/ (in this order)
In kernel_samsung_smdk4412: https://gerrit.omnirom.org/#/c/12223/ (SELINUX to permissive) , https://gerrit.omnirom.org/#/c/13055/ (Kernel compression)
Optional commits:
Enable Stylus pointer toggle: https://gerrit.omnirom.org/#/c/13606/, https://gerrit.omnirom.org/#/c/13650/, https://gerrit.omnirom.org/#/c/13651/
And finally, if you want to test and/or help:
Netflix experimental codecs fix: https://gerrit.omnirom.org/#/c/13716/
Other commits not made by me:
Nothing here as of now
If you wish to have a kernel with overclock and other features, you can find the kernel sources for my custom kernel "mm_alpha" at https://github.com/marco9333/android_kernel_samsung_smdk4412 . See branch mm_alpha_lollipop for the working and updated version working with this rom (and other lollipop roms). I can share a compiled version, PM me if interested
Screenshots -> Click here
Donations:
Many thanks to Heide Ruehle and @Rand_
Thanks to:
Omnirom core devs
@iofthestorm(ported omnirom 4.4 and made it official for our devices)
@humberos (various patches and asked for an official new android-5.0 branch)
@lirokoa (for his advices on wifi and camera hal)
I forgot someone ???
XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy Note 10.1
Contributors
marco9333
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-11-23
Last Updated 2016-11-13

Status of things:
Broken:
Charging off mode isn't working
Using torch tile causes a forced reboot, use torch app instead
Wi-fi tethering isn't working
Screen recording causes an hard reboot (Now it just does nothing or System UI crashes and restart)
I haven't tested other things yet....
Report if you found something new to add here
Notes:
Using a proxy in APN settings doesn't work. Thanks to @farinjini for pointing this out -> I don't know if this is working now or not
Changelog:
Older versions changelog
20141123
Initial release
20141125
Fixed stylus (S-PEN input)
Fixed graphical glitches in screenshots and while rotating screen Thanks to @lirokoa
Upstream changes -> updated to android release LRX21V and other "under the hood" changes
20141126 for N801x
Solved bootloop problem, I hope (not booting kernel)
20141130 for N8000
Partially working RIL (this has been really hard )
20141204-05
Upstream changes -> updated to android 5.0.1 LRX22C
Gps fixed. Thanks to @humberos
Added Performance control and Advanced in settings as in omnirom 4.4.4 (thanks to omnirom core devs)
Mobile partially fixed (need to run a script to make it completely work) (only N8000)
20141207 for N8000
Mobile data completely fixed
20141218
Upstream changes
Added advanced reboot (normal reboot, reboot to recovery and reboot to bootloader)
Fixed the problem with keyboard (need to disable physical keyboard from settings)
Fixed forced reboots caused by Youtube and G+
Minor fixes about technical things
20150108
Switched to android 5.0.2_r1 LRX22G
Upstream changes
Random reboots should be fixed -> see https://gerrit.omnirom.org/#/c/11024/ and https://gerrit.omnirom.org/#/c/10997/
20150206
Upstream changes -> See https://gerrit.omnirom.org/
Lots of code cleaning -> Better stability (I hope)
20150326/27
Switched to android 5.1 LMY47D
Upstream changes
20150401
Upstream changes
Switched to android 5.1_r3 LMY47I
Youtube, G+, firefox, etc. reboot fixed (experimental fix please report if problems)
20150407
Upstream changes
Netflix fix (experimental.. please report)
Properly "keyboard not showing" fix
20150506
Upstream changes
Android 5.1.1 LMY47V
New DRM vendor libs (Report if they "work miracles" with netflix)
20150510
Upstream changes
Pointer disabled by default when using S-Pen (Can be re-enabled in Settings see screenshot at #372)
Reintroduced keyboard fix (sorry about that)
20150519
Upstream changes
Android 5.1.1_r2 LMY47X
Netflix codec fix -> See https://gerrit.omnirom.org/#/c/13716/
20150628
Upstream changes
Android 5.1.1_r5 LYZ28E
20150928 or 20150927
Upstream changes
Android LYZ28J
Stagefright fixes
20151104
Upstream changes
Video playing fixed (Sorry guys and girls )
Chrome is now working
You need to enable the showing of keyboard after first boot: go to settings, language and input, current keyboard and enable Hardware(Show input method)
20161110
Untested build
Upstream changes
Android LYZ28N

Reserved
Workarounds and advices
Smoothness: Go to settings, about tablet and press repentantly Build_number until it gives you that you're now a developer, Go back, press on Developer options, scroll down and set Window animation scale, Transition scale and Animator scale to .5x
Toggle stylus (S-pen) arrow pointer:
Go to Settings, Language & input, put a tick or not on "show icon when using stylus" option

marco9333 said:
Status of things:
Working:
Boot
Bluetooth (switching on and scanning)
Rotation
Suspend/Resume (need to keep wifi on though)
Audio
Root (flashing SuperSU from recovery)
Gapps install and start (I've tried CM Gapps but login in is impossible)
Vibration
Hd videoplayback (tested youtube)
I forgot something ???
Partially working:
Screen -> Rotation causes graphics glitches
Video playbackaudio is working, decoders too but black video
Wifi (something wrong with this module, suspending the device with wifi off causes an hot reboot)
Broken:
RIL (phone calls, 3g and so on) for n8000 -> I'll try lirokoa advice -> need to import samsungRIL from android-4.4 tree
Camera (videos) -> Imported opensource camera hal -> taking pictures is fine but video are completely broken
Gps ->I 've waited enough and no position found -> some error regarding this in the logcat
I haven't tested other things yet....
Click to expand...
Click to collapse
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed

lirokoa said:
Hey marco,
For graphics glitch when rotating you need:
https://github.com/CyanogenMod/andr...mmit/540345f70db4f0cea6ad3f1150d2cb2fac18da25
https://github.com/CyanogenMod/andr...mmit/4e7f61fd6a36345e7994c236d1c128c4c8a6a0ea
https://github.com/CyanogenMod/andr...mmit/db4cec0e189b84e5999ae5b3bef0e7a6c2bb3087
you can probably find those in 4.4 omnirom branch as well.
Then it should be fixed
Click to expand...
Click to collapse
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.

marco9333 said:
Thanks I've already merged one of them yesterday (the first), and I need to check the second one. I don't know about the last one because I haven't found any settings in the various configs that enable BOARD_USE_MHEAP_SCREENSHOT. I need to check better though.
Click to expand...
Click to collapse
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app

i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:

LastStandingDroid said:
i'll try and see if YT even works
Running N8010 device with N8000 BL
seems imposible to get it to work :silly:
Click to expand...
Click to collapse
It's working I've just tested with a 720p video

marco9333 said:
It's working I've just tested with a 720p video
Click to expand...
Click to collapse
i'll see if it'll work for me i've never got it working with any build

LastStandingDroid said:
i'll see if it'll work for me i've never got it working with any build
Click to expand...
Click to collapse
I'm in the same boat as you, stuck with the leaked N8000 bootloader on my N8010, and youtube works great for me on last CM 11 build.

Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:

Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.

TheMorpheus said:
Nice work Marco!!
I've flashed your build (while building mine... ) and I've noticed that the keyboard doesn't show up, I had to go to Settings>Language & input>Current Keyboard and switch on the Hardware flag to make the keyboard appear.
Youtube works fine (audio and video)
I've played a couple of mp4 videos with a default gallery without a problem
Music plays fine with Apollo
It seem very good for such an early build...If only the log in with Google Account worked...:fingers-crossed:
Click to expand...
Click to collapse
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
mysarasaid said:
Sooo nice rom only network works on N8000 and it will be my rom
- There is a problem with the default browser as it closes after opening on few seconds
- Graphics errors at multi tasks cards.
Click to expand...
Click to collapse
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.

marco9333 said:
I've tried CM gapps but it chrashes on login.... maybe some others google apps will work. I'll try to extract them from my nexus 5 official L rom.
I usually use chrome. Default browser should be "deprecated" and replaced by chrome. Graphical errors are still there (during switching off screen, rotation, taking screenshots and so on), lirokoa pointed some commits I'll try with them, but they should do the job. RIL is a priority for me too, but it's quite complex and the code changed a lot so I'll need some time to merge that part.
Click to expand...
Click to collapse
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.

lirokoa said:
For RIL, many things are needed and I can't test since I have N8013, but I can point you to some to a repo that might help you:
https://github.com/ArchiDroid/android_frameworks_opt_telephony/commits/cm-12.0
Looks to all SamsungExynos4RIL / Samsung STK commits. That should help.
Click to expand...
Click to collapse
I'll give it a try because when I tried to merge RIL from omnirom 4.4 I've got an enormous amount of conflicts. Thanks maybe them will speed up the fix
Sent from my Nexus 5 using XDA Free mobile app

I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)

marco9333 said:
I've tested latest Banks google apps for android L and they are working. This is the link http://fitsnugly.euroskank.com/?rom=banks&device=gapps (added in OP too)
Click to expand...
Click to collapse
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
lirokoa said:
Yes maybe the one for heap screenshot is not needed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?

LastStandingDroid said:
it did remove my recovery after flashing this rom not sure why i was just unable to reboot to recovery (regular key combination)
used philz recovery rom worked and booted but recovery was gone (also using adb reboot recovery) made my phone go into bootloop
N8010 device with N8000 BL just to mention,
---------- Post added at 10:24 PM ---------- Previous post was at 10:22 PM ----------
@llirokoa do u know what lib is patched to fix the graphic issue? is it the surfaceflinger?
Click to expand...
Click to collapse
I've written quite big in the third post that you need to flash supersu beta just after the rom or you won't be able to boot into recovery: you've been warned. I'm working on merging the fixes for graphics issues.
By the way I've fixed the stylus input which is working ok now. New version soon....

New version 20141125 out
I've just uploaded a new build. See OP for download links and second post for changelog. Before signaling a bug or something that isn't working, please read the third post, too.
Another bug I've found is in charging off script, please recharge your tablet while on until next release

On my n8013, every time I flash the ROM, then gapps, then superSU, I get a boot loop, never makes it to Omni logo. I tried to redownload all files from the OP, and still no luck. Tried 4 times now

[UNOFFICIAL][KERNEL] Custom kernel (codename Noire) for SM-T560NU (CM14.1)

This release is only tested on the SM-T560NU USA (gtelwifiue).
This kernel is based on vince2678's port of LineageOS, with a couple of updates and optimizations.
This kernel has only been tested with vince's cm14.1 releases.
Flashable zips use a modified version of the AnyKernel2 system. While only tested on cm14.1, it may work on other ROMs, since it does not modify your initrd.
Very special thanks to vince2678.
Without his effort on this device, this release would not be possible.
Updates:
2017-06-10:
First build for CM14.1
Features:
DriveDroid Mass Storage and CD-ROM Support
Built with gcc-linaro-4.8-2015.06-x86_64_arm-eabi toolchain
Additional CPU optimizations
Updated CPU assembly optimizations
Various security patches
XPad (xbox 360 and xbox one) gamepad support
Known issues:
None
How to Install:
1. Download the latest release zip
2. Transfer zip to your device (or skip this step if sideloading)
3. Reboot into TWRP Recovery [Volume Up+Home] (If you need TWRP, first install mine or vince2678's.)
4a. Find the zip in the TWRP install browser, and install it
-OR-
4b. Sideload the zip using adb.
5. Reboot to system and enjoy
How much faster is it with the new optimizations?
Standard Kernel (click for full benchmark):
Noire Kernel (click for full benchmark):
What does "dirty" mean?
Whenever you modify a git repo and do not commit the changes, it will flag the kernel as "dirty".
Rather than forking the git repo, I use a clean copy of vince's repo, then apply my patches over it.
Because this isn't really how git was designed to be used, the build system sees it as "dirty".
It is nothing to worry about, as it is not harmful in any way.
Getting the kernel
Releases can be found on my site. (Check the header on the download page for a link to the source directory for tools to build your own):
https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/cm14.1
If/when there are more than one release, the most recent release should be on top, but verify the Last Modified date to be sure of the latest release.
Also be aware you will need to reflash anytime you update the main CM14.1 OS, as it will overwrite the kernel.
Bugs and issues
As vince's CM14.1 release is a rolling release, depending on many different sources, unexpected issues may come up in either the upstream code, his code, or my code.
Before submitting any reports to vince, be sure you are using his kernel (reflash the cm zip without flashing mine, preferably with a clean install)
Before submitting any reports to me, be sure the issue is not caused by the current release of CM14.1 (aka doesn't happen when you try the above).
No warranty is implied or provided. Be sure to have backups before flashing. But this is a no-brainer.

bump, because new release and target (was cm13, now cm14.1)

This kernel helped me to finally have USB OTG working by default, great job! :good:

Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?

jon355 said:
Can you give us more detailed info about optimizations? Does your kernel have any impact on battery life?
Click to expand...
Click to collapse
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)

Sm-t560 <> smt560nu
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?

Akineesan said:
Hey,
I'd like to Install this ROM, but obviously i get the message that it's not supported for my Device (in TWRP on flash attempt)
Mine is from the EU so, probably why..
Any chance to get this ROM to work for it?
Click to expand...
Click to collapse
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.

zefie said:
No.
Unfortunately, Samsung made several hardware changes, including the CPU, when they brought this device to the USA.
You could almost think of the SM-T560NU as the "SM-T560 New".
It is a newer model with revamped hardware, and thus not compatible with ROMs made for the other.
Sorry.
Click to expand...
Click to collapse
Alright, thanks for the Quick follow-up!

zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.

Jacsd said:
Great info. What optimizations were done on OTG mass storage? On stock LOS 14.1 kernel, USB OTG wasn't working for me while with your kernel it works flawlessly.
Click to expand...
Click to collapse
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.

zefie said:
Honestly none of my patches do anything USB related, except DriveDroid, but that lets the tablet be a device (by hosting disk images), not anything to do with connecting a device to it. Therefore, I cannot take the credit for that. Vince must have fixed it in his kernel. I built this with the latest code at the time, code that may have been more recent than the last lineage build of his that you tried.
Click to expand...
Click to collapse
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?

Jacsd said:
I tried latest build and a few older builds, on every I was stucked in the loop of mounting and unmonting USB device. I only managed to enable USB OTG when I installed StickMount. It seems Drive Droid does the same. Will you continue work on this kernel?
Click to expand...
Click to collapse
I'll update it if there are any necessary updates for performance or security, or any issues are found, but for now it seems fairly stable and should be alright for a while.

zefie said:
I haven't tested thoroughly but they shouldn't.
The optimizations are some patches that update the arm assembly functions to use features available in our CPUs that were not previously used.
As well as compiling while telling the compiler that we are using a cortex-a53 (in armv7 mode) (by default it just compiled generic armv7 with old armv5/6 assembly).
In short, they aren't overclocks, just using more of the processor's full potential, which is already sitting there doing nothing. Therefore, it shouldn't have a huge impact on battery life.
The CPU patches are here: https://files.persona.cc/zefie/files/cell/SM-T560NU/kernel/common-source/cpu_opts.patch.xz
Fun fact: Our CPU is actually armv8 64-bit, but we can't use it because we depend on Samsung's proprietary binaries, which are compiled in 32-bit (armv7 mode)
Click to expand...
Click to collapse
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?

jon355 said:
Tnx for detailed answer. Btw, I tested your LOS 13 build and it's very smooth and battery life is great. Only issue I encountered so far is when charging offline, screen doesn't go off and there is no charging percents showed. Also, can you sync with the latest LIneage changes? Can you replace stock browser with the Jelly and stock camera with the Snap camera?
Click to expand...
Click to collapse
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.

Wondering if this is still supported?
zefie said:
The thread for that is over here:
https://forum.xda-developers.com/showthread.php?t=3632745
Also, I am unable to reproduce the issue with the screen not shutting off. There is no percentage, but my screen shuts off while locked when charger is plugged in. Percentage and timeout can probably be configured in settings. I sync with Lineage every update. An update will come sometime this month with July's security patches.
As for replacing stock apps, I'll look into it. As the thread says, this is mostly for my use, hence why it wasn't publicly announced before. If I find the apps useful I will see about integration.
Click to expand...
Click to collapse
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet

Bigority said:
From the title you can tell if this still works. For example will it work with official LineageOS and what not. Hoping to get a response so I can overclock my tablet
Click to expand...
Click to collapse
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).

zefie said:
Should still work. I haven't messed with the SM-T560NU in a while. If I recall the Lineage build system was creating broken builds, I'm running 14.1-20171121-NIGHTLY-gtelwifiue and Noire Kernel still works with that.
As for newer builds, last time I tried (some time between xmas and new years), all of the more recent Lineage builds would not boot, with or without my kernel. If trying newer Lineage NIGHTLYs, try without my kernel first, then try with if it does boot.
Vince has kinda abandoned the SM-T560NU, although I'm not sure it is a fair reason to abandon us, because we didn't test on a completely different device, but his choice is his alone, and as such, without him working on Lineage, the newer builds are likely to stay broken unless either he comes back to fix it, or someone else takes over (don't look at me).
Click to expand...
Click to collapse
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?

Bigority said:
For it to work properly should I try your port of LINEAGEOS or should I try Vince's port of Cyanogen Mod?
Click to expand...
Click to collapse
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that

zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
Alright thanks

zefie said:
This kernel is for vince's 14.1. My 13.0 already uses Noire kernel and this release should not be flashed with that
Click to expand...
Click to collapse
The link isn't working to download the kernel :l
Edit: It was working just my internet was too ****ty too load it.

[Kernel][LOS/CAF][M/N] Linux 3.10 custom kernel v3

Linux 3.10-based kernel for Oneplus One (bacon)
Info:
use this kernel at your own risk. Flashing it the wrong way might brick your device. I'm not responsible for any software/hardware damage.
This kernel is based on top of erorcun's 3.10 kernel. erorcun has spent an enormous time working on this project and he deserves a huge "Thank you" for having succeeded in one of the most difficult tasks in Android development: upgrading a device to a newer Linux release.
Features:
v3 (12th December)
built with O3 optimizations
CAF CPU boosting driver (replaces cpu_input_boost - might be a temporary switch)
kernel code base updated to Linux 3.10.60
sdcardfs updates
minor miscellaneous improvements
old releases:
v2.1
minor stability fix
v2 (12th November)
kernel code base updates reverted, then re-applied only up to 3.10.54
compiled with an improved set of GCC flags
tuned AIO for SSD-only machines
v1 (30th October)
built with GCC 5, UBER Toolchain and the optimal compiler flags for Krait CPUs
kernel code base upgraded to Linux 3.10.88
power-efficient workqueues
sound control by francisconfranco
CPU voltage control
cpu_input_boost by Sultanxda
sdcardfs & f2fs support
support for both LineageOS's and Sultan's camera HALs
Compatibility
The kernel is compatible with all the Marshmallow/Nougat ROMs that use either LineageOS's camera HAL or Sultan's (a.k.a. CAF's). Just make sure you download the right version
Currently, the kernel has been tested only on LineageOS 14.1, but I'm sure the CAF build is safe to flash and works properly as well.
The kernel doesn't work on Oreo (yet)!
Download
The kernel can be download from AFH: 3.10 kernel on AndroidFileHost
Thanks to:
erorcun, franciscofranco, Sultanxda, CAF & UBER, Mecca EL.
XDA:DevDB Information
Tom's Linux 3.10 kernel, Kernel for the OnePlus One
Contributors
Tomoms, erorcun
Source Code: https://github.com/Tomoms/neon_kernel_bacon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.0
Stable Release Date: 2017-12-12
Created 2017-10-30
Last Updated 2017-12-12

thanks man! any plans on oreo version?

criminality said:
thanks man! any plans on oreo version?
Click to expand...
Click to collapse
Everything will come in due time
It's one of the things I'll work on soon. Be patient, and you'll eventually get what you want

Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.

Fatsodonkey said:
Thank you for this.
Don't know if it's your Lineage rom or this kernel, but video that i record is really stuttery. Like very janky.
I recorded the video with the build-in snap camera.
Click to expand...
Click to collapse
Could you tell me the exact resolution you used?

Tomoms said:
Could you tell me the exact resolution you used?
Click to expand...
Click to collapse
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.

Fatsodonkey said:
Happens with all resolutions. I already tested Sultans Lineage as well with this kernel and the same thing happens. Don't know if it tries to record it too fast as it seems to be too quick and stutters a lot.
The Los kernel seems to work fine with video recording altough i just dirty flashed it on top of Boefflas kernel.
E:It definetly is the kernel that is causing the stutter.
Click to expand...
Click to collapse
I'll compare the camera driver present in this kernel and the one in Sultan's kernel, then try to fix this. Unfortunately at the moment this is the best thing we can achieve, CAF camera support had always got some small problems even in erorcun's build if I recall correctly, and these problems are inevitably "inherited" by my kernel.

Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.

TbMa said:
Thank you for working on this, I was looking forward to release since I saw your announcement in erorcun's thread.
Firstly i tried to dirty flash kernel on top of LineageOS build (N) by idprophecy, since i got positive experience changing kernels (3.4 ones) this way even with encrypted phone. So when i tried to boot up with new kernel, unfortunately it did not work and phone says my password is correct but encryption partition is broken and i need to hard reset.
I went to clean install, removed encryption and flash same LinOS build + your kernel. Then i encrypted phone again and everything went fine. However now my TWRP refuses password for decrypting partitions (its was like that in early N development for bacon on many roms).
Overall perfomance is not really smooth comparing with 3.4 kernels, but i didnt bothered to play with kernel setting.
Also i cant get MTP working, phone only charging via usb and PC (Windows) cannot see its memory.
I know this report is probably useless without kmsg logs, but i didnt have time to pull them off, so sorry about that. I try do it later
Click to expand...
Click to collapse
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.

Mecca EL said:
Definitely would need a log, to see what the issue is, with your experiences.
I've been alpha and beta testing this kernel, and I'm not experiencing any of the problems you and other users are describing. Clean install @idprophecy LOS14.1, flash this kernel, reboot back to recovery and flash MagiskSU, enjoy an ultra responsive OPO.
Click to expand...
Click to collapse
What about encryption? Are your TWRP able to decrypt data with this kernel?

Tomoms said:
I faced the same MTP problem when I started developing this kernel several months ago. But I'm sure it appeared at a later stage of development. So MTP shouldn't be an issue as of now. Also, according to @Mecca EL, there should be a substantial performance improvement.
So can you confirm MTP is working on this kernel? What about video recording? Is it lagging or not? I still haven't had enough time to thoroughly try my own kernel :/
Thank you.
Click to expand...
Click to collapse
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
TbMa said:
What about encryption? Are your TWRP able to decrypt data with this kernel?
Click to expand...
Click to collapse
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.

Mecca EL said:
I'll double check, and do a complete run down on this latest one, in case it differs from the last one you sent me.
---------- Post added at 08:56 AM ---------- Previous post was at 08:53 AM ----------
I've not set encryption. I've seen way too many problems with that across almost all android devices. I'll see if it's not too much trouble to set and test for you, if I'm able to revert to unencrypted easily.
Click to expand...
Click to collapse
Well i am using encryption since early MM and not a single problem if developer of rom and kernel did his work fine. Biggest payoff its hit battery.
Unfortunately you cant revert encryption without formating whole internal storage, so its a little bit complicated with backups and etc

MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.

SirSoviet said:
MTP is not working for me either, I'm using the CAF kernel on LineageOS by Sultan.
Click to expand...
Click to collapse
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?

Tomoms said:
Thanks for your feedback, I'll do my best to fix this issue as soon as possible. Do you face the video recording issue?
Click to expand...
Click to collapse
I never record videos, so I don't know. I'll check later today.

@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).

Mr.Ak said:
@Tomoms ,just a heads up: kernel works fine with Marshmallow(los13).
Click to expand...
Click to collapse
Thank you for letting me know. I'll immediately update the thread.

SirSoviet said:
I never record videos, so I don't know. I'll check later today.
Click to expand...
Click to collapse
Nothing wrong with video recording here.

SirSoviet said:
Nothing wrong with video recording here.
Click to expand...
Click to collapse
Hmm... I'll try it myself soon. In the meantime, my main concern will be fixing MTP, and it won't take me too much, fortunately.

[ROM][WIP] Sailfish OS 2.1 Nexus 10

An alpha build of Sailfish OS 2.1 for Nexus 10 (manta)
Its in rough shape but we are slowly but surely getting there.
YOU CAN DUEL BOOT WITH ANDROID! - See second post for info
UPDATE July 9th 2018: I am still still working on this. I have some stuff to try, mainly rebuilding the old June 2017 audio jack kernel in both hybris hal and the base rom, meaning, HOORAY - I'll be forced to start building my own android base. in the mean time things are the same in the OP, use the new build if you want the latest release and don't mind a lack of video, use the old one for creepy silent videos. I am counting down for Sailfish OS 3.0 to come out, I already know that its going to break anything I fix. And a big sigh is released.
Credits:
Lineage OS team for the LOS 14.1 Base (seriously, THANKS)
Jolla for that perfect software
followmsi for the fixed kernel sources that don't inherit those dirty lineage audio jack issues.
All the people on the #sailfishos-porters IRC who kept me motivated and full of hope (mal, krnlyng, Mister_Magister, sledges, m4r0v3r, piggz, r0kk3rs, just to name a few)
LOS14.1 Base: https://drive.google.com/file/d/1W3k2PzWKQU_-1qbhho_8MespNzr5zBlD/view?usp=sharing - I didn't make this at all.
Sailfish OS 2.1.3.7 alpha 0.1.2 rootfs: https://drive.google.com/file/d/1QKux9YkUHi7XZtGEJbUh_xYms5-BsLjo/view?usp=sharing - I did for sure make this (well, I ported it, credit to Jolla for sillica and stuff)
Sailfish OS 2.2.0.29 alpha 0.2 rootfs: https://drive.google.com/file/d/1IkWtZxAPGeiSiqCpMcbct-M43QlCsG8m/view?usp=sharing - THIS IS THE SUPER SPOOKY UNSTABLE RELEASE!!! BEWARE!
Adaptations Libhybris page: https://wiki.merproject.org/wiki/Adaptations/libhybris/Manta
My Video Review of alpha 0.1.3: https://www.youtube.com/watch?v=NmEGKZHquhQ
I have a lot to test so Ill populate this list more later but:
What works:
- Rotation
- ALS
- Magnetic Sensor
- Video
- Touch
- Hardware Keys
- Power Management and Sleep
The Checklist of What I Need to Fix
- Audio
- Video (droidmedia is broken in my latest clean build, this does not effect the rom in the OP, I would never update a rom with this many regression bugs)
- USB Charging
- Bluetooth
- GPS
- Haptic Feedback/Vibration
- Camera
CAMERA DOES NOT WORK IN THE BASE ROM SO IT WILL NOT WORK IN SAILFISH OS
Change log:
alpha0 - initial working release
alpha0.1 - added rotation fix, defined MALI_QUIRKS, applied a ton of random patches that did nothing
alpha0.1.1 - fixed taking screen shots, built gst-droid (you can now play mp3s but sound is still broken along with video)
alpha0.1.2 - built SDSVideoFix droid media! we can now play video but there is still ZERO sound at all.
alpha0.1.3 - unreleased, REGRESSION BUG: Video is broken - trying again.
alpha0.2 - Updated image to Sailfish OS 2.2.0.29, droid media still broken. I recommend staying on the old alpha 0.1.2 build.
Our device is the highest resolution device to ever run Sailfish OS (for now). Let's all feel extra special for a bit.
General About
Linux Kernel: 3.4.113
Rom Base: Lineage OS 14.1
Sailfish OS Version: Sailfish OS 2.2.0.29 | 2.1.3.7
Sources:
(This is on the to do list)
Also my Discord ID is dirtymikelikesfeet#9871

Tips and Tricks
Get landscape rotation in ALL apps
Go to warehouse, and install patch manager and autorotate anywhere (or something like that)
Reboot
voila.
Dual Boot Lineage OS 14.1 and Sailfish OS
This is super easy, so basically the Hybris installer doesn't touch /system or /data (at least none of the installed android files) so you can boot between the two rather easily. You will need a Lineage OS 14.1 boot image (Inside the Lineage OS 14.1 zip) and Hybris boot (inside the Sailfish OS zip). When you want to boot between the two, boot into TWRP Recovery, and flash the appropriate boot image. This should make it easier for testers.
Q/A
Does flashing a new Sailfish OS image wipe my android files? - As far as I know? No. But I haven't really tested this. It shouldn't.
"Is this usable as a daily driver?" - No. not right now. Once I fix audio maybe, but as it stands now, unless all you do is read emails, watch silent movies, and play simple games and read books, its pretty garbage. You can browse the web with web cat but it has 1/3 of the screen not used.
"Why did you use the LOS14.1 base you idiot? you realize we will never have working camera now right???" - Lesser of all evils. Once I get a good stable LOS 14.1 based sfos port (working everything), and a list of all my tweaks to fix everything, I will try making an LOS 13 based sfos port. I like camera too, and do occasionally use it on this tablet.
"Does it have android app support?" - No. Maybe one day I will hack alien dalvik onto it and post a concept install for Nexus 10, but no promises.

Looks interesting,I will have to follow your work to see how far this goes. ?

Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk

aheeejd said:
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
Thanks for the interest, the current thing to do is add minimer to m N10 so I can fix hwcomposer, it is wonked real bad and I think it's why jolla-startupwizard won't work right now.

*bump* because it finally ****ing works (sort of)

sailfish for nexus 10
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
a better browser please??or a new version??

ted111 said:
a better browser please??or a new version??
Click to expand...
Click to collapse
browser bugs are proving near impossible to solve, and manually rebuilding qtmozembed did nothing. I am going to try and crank out a 2.2 build tonight with the vendor repos included but I doubt much will change. As far as browser, the cut off is a problem with qt that I am still figuring out how to solve.
OKAY! Building new image with mic as I type this. it's at 162/473, hope it doesn't fail but it rarely does at this point. Using followmsi's new 0611 build as a base, and I have thrown in TheMuppets vendor repos for broadcomm and the like, hopefully something cool happens, but I am 99% sure this build will be the same broken build accept based on sailfish OS 2.2. This means no gstreamer, i.e. no videos, no mp3 files, no nothing. Also I doubt Audio will just fix it self either.

Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works

ted111 said:
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
Click to expand...
Click to collapse
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.

Galaxyninja66 said:
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Click to expand...
Click to collapse
any news about it?

123123123123123213 said:
any news about it?
Click to expand...
Click to collapse
I no longer own the device, 10.1 and 11 sources had hwcomposer errors (but working audio afaik). 12-13 sources failed to boot for reasons entirely unknown since the logs looked fine (and no, it wasn't a no UI/display error, I checked and it was in telnet still, again, for seemingly no reason). 14.1 worked like a charm but sadly the audio issues were just a mystery. Rotation was an easy fix and I think at that point GPS had very little mw so it was hit or miss and debugging it was not done often so it was mostly undocumented. Don't know about now.
tl;dr
10.1-11 - broken hwcomposer, wayland is gimped in 2.0 and beyond period, and fbdev wouldn't work either
12-13 - refuses to boot past the telnet stage for unknown reasons
14.1 - audio is broken, using followmsi and the stock lineage sources/matching base images.
I'd love to work on this again actually, but a new N10 would cost me 80 AUD and I'd have to prep a new VM since I wiped all mine switching to macOS.

Lineage OS 17.1 on old blobs - possible?

Ever since LineageOS started using the OxygenOS 9.0.x blobs for OnePlus 3 I have had lots of issues with the phone. The worst being total lockup during the night on airplane mode. Basically white light comes on and you have to force reset. If not found until morning then the battery will also be totally flat. When this happens pstore is totally empty so zero logs of the event.
Stock OxygenOS 9.0.x is the same.
As I am stubborn I don't want to buy a new phone due to something introduced by software, even if the "bug" doesn't affect all hardware. Downgrading to Oreo consistently fixes the problem!
Anyway, I was wondering how possible would it be to run the old blobs, old firmwares but on Android 10?
So far I have tried the following:
https://forum.xda-developers.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 - Running the old bootloader and keymaster. Issue persists.
Modifying my NON-HLOS partition to use the modem binaries from the Oreo NON-HLOS partition. RIL doesn't play nicely. Issue persists anyway.
Building LineageOS, but using old blobs. Took proprietary files from this commmit, https://github.com/LineageOS/androi...mmit/d6915c5315d7a3272860f8fc940aab8ba076d6e3, the last one before the new blobs were introduced. Got the blobs from checking out the equivalent commit on The Muppets repo. Phone wouldn't boot errors in pstore about not being able to talk to most of the blobs (keymaster, gnss, etc). I guess its because theres a tonne of commits that Android 10 requires after this point, but its complete spaghetti working out whats what.
Tried without Soter/Alipay as I don't want to run that stuff anyway and soter was introduced at this time also, but issue persists.
I am also beginning to think the new blobs are an actual requirement for Android 10, so I might be wasting time anyway.
There are no Kernel commits around this time. https://github.com/LineageOS/android_device_oneplus_oneplus3/ A block of commits on 16th June 2019 is when things broke. By process of elimination, it isn't: the boot loader, the key master, the old modem (but COULD be the RIL), the kernel.
So I am guessing what would be really helpful to me would be:
How can I debug this? It seems its not a Kernel panic as there is no pstore, but white LED comes on (if lineageos) or no LED (if oxygenos).
Is it possible to build LineageOS 17.1 but with old blobs/firmwares? I don't want a step by step or anything but pointers if its possible even...