Develop Bugs

[DDK 1.9] OmniROM DDK 1.9 Test Version

Introduction
This is a test version of OmniROM with SGX DDK 1.9 graphics drivers, as well as many OMAP-related kernel updates. No, this isn't 3.4, but a LOT of TI updates were packed into the kernel. Currently, this is only for maguro, but anyone can build it for toro/toroplus with the sources.
Click to expand...
Click to collapse
Features
The ROM and the kernel has a stock feeling - no mods were added.
Most notable new features:
- SGX DDK [email protected]
- GPU governor
- Enabled 384 MHz GPU frequency (as a part of the OMAP updates)
- Tons of background changes for the kernel
Click to expand...
Click to collapse
Important notes
Camera and OMX is not working yet! This turned out to be a harder task for me to fix than implementing the new GPU drivers...
Other bugs are not known yet, but there may be some! Bug reports are welcome.
Thanks to everyone who helped me, especially Hashcode, as I used his repos as an example on how to set up things properly.
Click to expand...
Click to collapse
FAQ
How can I install this?
Just flash the ROM zip (and optionally GAPPS), and you're done.
Can I install this on top of Omni roms?
Yes, you should be able to do so without data loss.
Can I revert to non-1.9 Omni after this without data loss?
Yes.
Is this faster than the current ROMs/kernels?
As this is a stock-like ROM and kernel, not necessarily - there are no optimizations, etc added.
However, if one adds the optimizations used on current custom roms and kernels, this should be faster than them.
Can I install another kernel?
No, the new drivers require the ROM and the kernel side to match each other. Only this combination will work.
When will you fix camera?
I'm trying, but I don't have much success...
Can I help?
Sure, I appreciate any help, as I'm running out of ideas on how to fix camera and OMX.
Can I build this stuff myself?
Of course - everything needed is on my github. You'll need the following repos added to your Omni sources:
omni_android_device_samsung_tuna
omap (newpvr2 branch)
proprietary_vendor_samsung_tuna
Click to expand...
Click to collapse
XDA:DevDB Information
OmniROM DDK 1.9 Test, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: OmniROM
Version Information
Status: Testing
Created 2014-07-13
Last Updated 2014-07-13

Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk

aliesz said:
Where is the download link?!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Click on the downloads button above the thread title

If you're on tapatalk you'll need to go to Web view..
To see the download
Sent from the "DOG" pound

Yes I found it just seconds ago
Sent from my Galaxy Nexus using Tapatalk

Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound

cujo6801 said:
Also OP there 3 types of gnexes...
You might want to add to the OP which one it is for
Sent from the "DOG" pound
Click to expand...
Click to collapse
Thanks for the suggestion, added it to the introduction text.

Amazing! I will try out tommorow

I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work

Nice work! Seems a lot more responsive although it may be placebo effect.

Thanks for posting this, I'm going to try building for toroplus, since we seem to get left out of the excitement so often. My internet connection is slow and so is my computer, so you will probably have everything fixed before I get a chance to even look for bugs.

Great work! I hope you manage to get camera working soon.

Amazing work bro, wishing u best of luck !!
I'm on F2Fs otherwise would have tested this asap...

Awesome work!

Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?

matoushybl said:
I've installed it and it feels smooth, I've not encountered any bugs yet. Have you tried removing "kitkat workarounds" from frameworks/native?
Thanks for your awesome work
Click to expand...
Click to collapse
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
apollo07 said:
Thanks for the amazing work you've brought to the gnex, but since i'm on F2FS i was wondering if you could make a F2FS compatible version of this rom?
Click to expand...
Click to collapse
Not yet, I'm focusing on camera for now

Ziyan said:
The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
Click to expand...
Click to collapse
How about using SurfaceFlinger's Sync framwork now?
https://github.com/omnirom/android_...mmit/d677ae87b2466b03a6ca1cda6ee532c6ba407f8c

@Ziyan https://gerrit.omnirom.org/#/c/8141/
https://gerrit.omnirom.org/#/c/8156/ cherypick those and recompile

Ziyan said:
Yeah, but the glitches are still there. Actually, that may be a bug in android itself (it affects a lot of devices), they may have fixed it on L... and those workarounds are really not important, as the problem only comes when taking screenshots. And since android takes screenshots for the rotation animation, etc, those glitches appear there as well. The workarounds just force it to take screenshots on CPU-path, they don't change anything else.
I think they fixed it in DDK 1.12 (which is the next version after 1.9), but that's another story, as I think it does not support our GPU (but it may in the future).
Not yet, I'm focusing on camera for now
Click to expand...
Click to collapse
Ziyan, thanks for the awesome work

It 's possible to have some screenshots?

Android Lollipop for SM-T210(R)?

Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...

TrendingTech said:
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
Click to expand...
Click to collapse
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305

why?
Minto107 said:
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
Click to expand...
Click to collapse
How come, I don't understand, there are serveral other ROM's for KITKAT, why would it be impossible to build a Lollipop ROM? I have NO idea how to build a rom, otherwise I would give it a try.
What makes it so difficult?

We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305

Minto107 said:
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Click to expand...
Click to collapse
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?

TrendingTech said:
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
Click to expand...
Click to collapse
None of TAB 3 family devices got 5.x so there's nothing to port. Tab 3 7,8,10 won't be updated to 5.x
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka

Tab 3 8.0 has unofficial cm-12.1
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,

Grynot said:
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Click to expand...
Click to collapse
Omg but 8.0 uses Exynos 10.1 uses Intel and 7 uses ****ty Marvel CPU! You don't have source so no CM for you
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka

So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !

rheecollinskelley said:
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
Click to expand...
Click to collapse
You know that Tab 3 8.0 is only 4.2.2 supported, not even close to KitKat, although you can find yourselves SM-T21x Kit Kat roms. Lollipop will not be supported by any chance, even for custom roms man!

It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.

vorpalblade77 said:
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
Click to expand...
Click to collapse
Yeah but XDA is full of noobs that only asks when, why it takes so long time... Bringing Lollipop to TAB 3 7inch is very hard work... This tablet wasn't a beast, since release date it was low end tablet with such tragic performance. For such noobs who just want and doesn't want to help I've got an advice. Get Nexus 7 2013... 6.0 on board, noob friendly
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka

As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.

DroidTwe4kz said:
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
Click to expand...
Click to collapse
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.

vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.

vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
DroidTwe4kz said:
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
Click to expand...
Click to collapse
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.

gr8nole said:
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
You already did more than enough for our device and I'm thankful for that. Someone will continue to build CM based on your source.

gr8nole said:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO

vorpalblade77 said:
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
Click to expand...
Click to collapse
I haven't looked at any of this in a long time, and have no real desire to at this point.

gr8nole said:
I haven't looked at any of this in a long time, and have no real desire to at this point.
Click to expand...
Click to collapse
Fair enough. I'll probably look into once I know I have my build environment set up correctly. E.g., I can build a recovery and have it work correctly.

[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][4.4][UNOFFICIAL] LineageOS 16.0 with 4.4 kernel

LineageOS 16.0 for Xiaomi Mi 5 with 4.4 kernel
Remember this is a beta release, althought I've been using it for more than a week and it's working perfectly.
If you experience any bugs, panics or so, please report full logs to me (logcat and dmesg, you can look in /sys/fs/pstore)
Installation:
You can flash it on top of OFFICIAL 3.18 LOS also you can always go back within a dirty flash.
For safety reasons always perform a backup of your important data!
Features:
This is well-known LOS, none of the functionalities have been altered.
Build is running 4.4.189 kernel with many improvements over 3.18, it will keep this device alive for upcoming Android releases.
Kernel is suited with initial bug fixes, however, it's a stock kernel without any advanced tweaks. It's built with CLANG (!).
Working:
Probably everything!
Not working:
Kernel is permissive
Temporary MTP fix (I didn't have enough time to investigate it well):
Developer settings -> Default USB conf -> MTP -> connect cable -> profit
READ ONLY IF YOUR DEVICE IS ENCRYPTED:
There is an incompatibility between 3.18 and 4.4 kernels, you have to flash new TWRP with 4.4 kernel, otherwise your data partition will be DAMAGED!
Nevertheless there could be a need to full wipe your /data (magic Format Data button in TWRP) so perform a FULL BACKUP.
Download:
LineageOS zip
TWRP
Future development:
Device tree will be created from scratch over new Qualcomm tag to get rid of old junk. Full Treble compability will be provided.
More kernel bug fixes
Vendor update
FAQ:
Can I install XXX ? Does it support XXX ?
- It's still LOS, it supports everything what stock LOS does.
Can't you ship kernel package only?
- No, ROM has to be modified to meet 4.4 requriements. You can't flash 4.4 kernel on top of 3.18 ROM.
But why 4.4? Do I need it?
- More fixes, more performance, more support. If you want, search for kernel changelog.
EAS?
- Not now, there are more important things to work on.
If you want to buy me a coffee, please consider donating, I've put much effort to make it working.
DONATE
Join Mi5 group on Telegram
Huge thanks to Zuk kernel team for initial 4.4 support!
Credits:
@DD3Boh
@YaroST12
@kenny3fcb
@Luk1337 - fix for USB
@Jawor245 - random stuff
@RadixCube
XDA:DevDB Information
LineageOS 16.0 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre/msm-4.4
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-01
Last Updated 2019-09-01

Reserved

Reserved

In Antutu 7.2.3 tested fresh, stock LOS + nano gapps and fresh this rom + nano gapps on my 32Gb version. Biggest improvement for my device is memory +22% in Antutu points.
Stock: 144 086 overall
CPU: 50 420
GPU: 53 892
UX: 34 159
MEM: 5 615
4.4 LOS: 148 079 overall
CPU: 50 600
GPU: 54 615
UX: 35 657
MEM: 7 207

@xNombre great job!
I'll be testing your ROM in the future for sure. Looks very promising.
It would be great if you pulled the Floppy Kernel mods to tweak your 4.4 kernel
(Just my wish)
However, congratulations man.

I really appreciate your effort I would love to test your ROM But I only want to know 2 things before if someone can help.
1. Can I use it as daily driver?
2. Android Auto is working?
3. Will I need to do clean flash for future updates? Atleast for couple weeks.
Thanks

I'm using it for two weeks and no problems here.
If Android Auto is working on official LOS it will for for mine, too.
Nope, not for now.
#edit
Here is the new kernel you can flash on top of my LOS. (DON'T FLASH IT ON ANYTHING ELSE)
https://androidfilehost.com/?fid=1899786940962575411
Changelog:
add exFAT and NTFS
fix problems with wakelocks
use LZ4 for ZRAM
debloat a bit
skip sync for better battery

@xNombre What is the reason behind choosing 4.4 instead of a newer LTS version like 4.9 or 4.14? Or was the decision out of your hands?

Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.

xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Whoa, calm down, mate. I just wanted to know the rationale. Knowing that msm8996 supports 4.4 is good enough for me. :good:
Sorry to hear about the two damaged devices, though. That must have been extremely frustrating.

xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Lots of love for 4.4 kernel.

Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?

Thank you for your work. This is quite big actually.

Thx

Myxomatom said:
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Click to expand...
Click to collapse
There it no correlation between kernel and RIL. No changes here. Maaybe sth nice will happen with new vendor blobs but you have to wait for it.

great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!

bido1 said:
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
Click to expand...
Click to collapse
yeah ... been using it for the last 3 days ... the battery performance is better than the official one without any tweak

can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?

netrixken said:
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
Click to expand...
Click to collapse
Are you using TWRP provided in first post?