yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] guest4711:
Sorry, could not add the screenshots. Here they are now:
[Samsung Galaxy Nexus] nokiagye:
Where you find roms?I see purenexus7.1 on a photo.. Du..?
[Samsung Galaxy Nexus] guest4711:
You'll find unofficial DU-ROMs (both 6 and 7) on AFH https://www.androidfilehost.com/?w=files&flid=50101 , unofficial LOS14.1 on AFH: https://www.androidfilehost.com/?a=show&w=files&flid=157598
[Samsung Galaxy Nexus] Android-Andi:
Noticed previous kernel had some issues with usb, says connected while it wasn't. Hopefully fixed.
[Samsung Galaxy Nexus] guest4711:
Did not see any problems with usb: When I connected the phone to computer, a notice about usd debugging was displayed and cleared when disconnected...

But I'll test the new kernel, too:
[Samsung Galaxy Nexus] Android-Andi:
A lot more sync with espresso kernel
[Samsung Galaxy Nexus] guest4711:
Boots without problems. I'll test it (until I get severe problems or there is another new kernel).
[Samsung Galaxy Nexus] h4xx0rr:
Is DU Rom 7.1.2 faster than slim?

Do you use gapps with DU rom ?

Is camera on 7.1.2 same as 6.0.1 rom ? or there are green line or something..?
[Samsung Galaxy Nexus] Android-Andi:
Wrong place to discuss different roms :)
[Samsung Galaxy Nexus] _yen_:
mtp connections are more stable now on my linux box, good as usual on seven (at work). Using staging branch with yesterday's commits on slim7.

Thanks

yen
[Samsung Galaxy Nexus] Android-Andi:
One more, we are reaching a good state now :)
[Samsung Galaxy Nexus] guest4711:
Yeah, flashed on top of latest DU-7 and using eith actual beta of magisk13. All seems to be well on the first look, but I like to stress the kernel with some work (synching calenders and contact via myphoneexplorer, decoding videos and livestreams, phoning with telegram, up- and downloading some data ...)

Thanks again for your efforts! :good:
[Samsung Galaxy Nexus] guest4711:
Running well, battery usage seems to be ok (good while sleeping). :good: Attached screenshot shows battery while under heavy load (spotify, voice over telegram, youtube) and then sleeping, then surfing in the www.

Nightlight does not tint the screen yellow anymore as in previous versions. :confused:
[Samsung Galaxy Nexus] bamtan2:
I tested this kernel on cm12.1 for a day, and I noticed weird behavior just like I did with Android 6/7. Unexpected crashing from multitasking. Twitch app freezing. No video playback. I tried the "restart camera service" app and it didn't help.

I think it is actually very encouraging if I have isolated my main problem with Android 7 being inside the kernel instead of in Android 7!

I should add: cm12.1 restarts on its own sometimes WITH THE ORIGINAL KERNEL, so it DOES crash and error. I need to acknowledge this because, for all I know, every distro has the exact same problem, exactly as often, but they handle it differently. This is a trouble with software testing! Details matter! ;)
[Samsung Galaxy Nexus] Android-Andi:
Get a last_kmesg if it reboots, else a dmesg after crash should be good to take a look.

Maybe i have some more time tomorrow and we can test without CMA.
[Samsung Galaxy Nexus] Android-Andi:
A lot more sync with espresso, CMA still enabled (i like to get the sync with espresso kernel done before we are disabling it)
[Samsung Galaxy Nexus] bamtan2:
I actually think I had similar problems with zeelog's rom (with cma off), so that might not be it. Will still test!
[Samsung Galaxy Nexus] Android-Andi:
If all goes fine we can test the commonized kernel on espresso and tuna devices later today ?

Been on creating it more than 100 hours now, lol.
[Samsung Galaxy Nexus] bamtan2:
Making these devices easier to maintain in the future + bringing communities together = very valuable to us. You may be helping developers 10 years from now maintain this device! Thank you, and [MENTION=2633638]Ziyan[/MENTION], and our other friends!
[Samsung Galaxy Nexus] Android-Andi:
Success! Espresso boots now after conditional reverting a bunch of tuna changes - felt like hell, haha.

I'll run another tuna kernel after i had a shower and upload it.
[Samsung Galaxy Nexus] Android-Andi:
Here's the result of > 100 hours of working on a common OMAP4 Kernel source for tuna and espresso variants - one source for 11 devices! Sounds great IMO!

Have fun testing this one :)

Edit to avoid confusion:

You can't boot tuna with espresso kernel or espresso with tuna kernel but maintaining our kernel will be a lot easier in future since we don't have to apply same kernel patches on different source (e.g. CVE fixes)
[Samsung Galaxy Nexus] beymanlope:
how i can activate Zram in this kernel?
[Samsung Galaxy Nexus] Android-Andi:
Edit: disabled on tuna by default. You'll need to compile your own zImage and also modify the ramdisk of your boot.img
[Samsung Galaxy Nexus] Nonno Cicala:
Last build of this kernel never goes in deep sleep state on my maguro running Slim7, draining a lot of battery while idle.

Previous build ( https://xdaforums.com/showpost.php?p=72954032&postcount=43 ) worked fine.
[Samsung Galaxy Nexus] Android-Andi:
I'll look at it once my internet is working again. someone was working on our cable... And broke my TV and internet connection... Should get fixed tomorrow hopefully l.
[Samsung Galaxy Nexus] Android-Andi:
You can try attached kernel?
[Samsung Galaxy Nexus] guest4711:
Works for me (DU-11.5) :good:

Nightlight does not...
[Samsung Galaxy Nexus] Nonno Cicala:
Deep sleep is back! :)
[Samsung Galaxy Nexus] Android-Andi:
Another Update. Adresses

CVE-2014-4656

CVE-2014-7822

CVE-2012-6704

CVE-2014-3145

CVE-2014-2706

CVE-2014-1739
[Samsung Galaxy Nexus] guest4711:
Thank you, Andi. Running also on DU v11.6 (7.1.2)
[Samsung Galaxy Nexus] musical_chairs:
RIL is broken on toro with the latest update. Toro running Kitkat.

Log with latest Anykernel: https://pastebin.com/PPZAdDQM

Log with 07-09 Anykernel: https://pastebin.com/g2ZGpA8Z
[Samsung Galaxy Nexus] Android-Andi:
Can you share a dmesg too please?

Edit:

I switched to Linaro 4.7 14.01, wonder if this could cause problems (tuna doesn't love some toolchains, e.g. GCC4.8 & 4.9 can cause bootloops)/

I'll attach one compiled with Linaro 4.7 13.04 (using on Slim) and one compiled with GCC 4.7 in some min.

Edit2:

Please let me know if any of the attached works for you, if you have still issues attach a logcat please.
[Samsung Galaxy Nexus] _yen_:
I can confirm problems with last 28/07 anykernel which doesn't boot at all on my maguro (slim7, current weekly). Previous build on 18/07 boots OK on same ROM.

Let's say that my maguro is quite a b*tch and doesn't like kernel built with toolchains other than stock gcc4.7. linaro 13.04 used by slim or even sabermod 4.7 gives me mixed results (sometimes boots, sometimes don't... more the second), at least for my own builds.

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
Another Update because we missed some tuna parts (to get toro modem working, also some board config changes have been missing),

CVE fixes updated a littlebit more while on it:

CVE-2014-4656

CVE-2014-7822

CVE-2012-6704

CVE-2014-3145

CVE-2014-2706

CVE-2014-1739

CVE-2015-9004

CVE-2016-10200

LVT-2017-0004 (needed if LineageOS Su is used)

Thanks to [MENTION=4531957]musical_chairs[/MENTION] for testing some kernel until the issue on toro was solved :)

Compiled with GCC 4.7 because some maguro hate other toolchains.
[Samsung Galaxy Nexus] _yen_:
thanks, boots fine here :good:

bye

yen
[Samsung Galaxy Nexus] guest4711:
My maguro with latest DU (11.6) and magisk13 booted fine. Wifi is working @2.5 GHz and 5GHz. :good:
[Samsung Galaxy Nexus] Regina Rainbow:
Kernel: AnyKernel-2017-08-01-20-30-KitKat-tuna.zip

ROM: ua_tuna-4.4.4-20170601033511.zip

Boots fine on my maguro, basic functionality seems to be OK - including deep sleep. But I see a strange quirk: I can't get a dmesg using the above combination of ROM and Kernel (klogctl: Operation not permitted).

Turning on bluetooth makes my phone reboot. last_kmsg shows a kernel panic and some backtraces which are not in kmsg, when BT is turned off. [Standard Kernel of ua_tuna-4.4.4 shows the same behavior, see also #1663 in UA Thread]
[Samsung Galaxy Nexus] Android-Andi:
Thx, I'll look at it this weekend if I find some time

About dmesg:

adb root

adb shell echo 0 > /proc/sys/kernel/dmesg_restrict
[Samsung Galaxy Nexus] Regina Rainbow:
Ahhh... I'll never stop learning roaming these forums - thanks!
[Samsung Galaxy Nexus] Radder124:
Can I install this Kernel on a UA 6.0 maguro ? Thanks in advance
[Samsung Galaxy Nexus] guest4711:
Should be ok. Just flash the kernel, but don't wipe cache nor dalvik. Afaik you should re-root your phone afterwards (I flash kernel and magisk13 together and reboot afterwards).

If you are not satisfied you can everytime dirty reflash your current ROM...

So try and report, please.
[Samsung Galaxy Nexus] Android-Andi:
Flashing the kernel doesn't change the ramdisk, only replaces the zImage and places the modules.
[Samsung Galaxy Nexus] Android-Andi:
Some more CVE fixes
[Samsung Galaxy Nexus] musical_chairs:
I ran it through the paces and everything worked: RIL, bluetooth, GPS, WiFi. Looks good. Toro running KitKat.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=5153662]Android-Andi[/MENTION] You mentioned overclocking :) I want to go on record and say that in my experience, the extra 200mhz from overclocking CAN make a significant difference to performance. There are slow performing things I've seen, whether video playback or app GUI, that went from slow to fast with a CPU overclock. Our CPU is just barely fast enough for some things, so the little extra speed makes an important difference. I will also note that with good governor settings, this overclock doesn't seem to hurt idle battery life. I especially like using overclocked devices when they're plugged into the wall to charge, because then there are no battery concerns at all ;)

1.4ghz is a typical safe speed in old kernels. Some people found 1.5ghz an 1.6ghz could work. I ran stability tests and found 1.4ghz was flawless on my device. Furthermore, just increasing the temperature limit by 5 degrees or 10 degrees can increase performance under load, because mobile devices throttle due to temperature after working for a few seconds or minutes. My understanding is that manufacturers usually set the CPU temperature limit to make the user's hand comfortable, and the system can work hotter than that.

So, I would encourage anyone to release a kernel with overclocking enabled. I also think color control is incredibly important because our displays have lost all calibration with age. Thank you for your work :)
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=4545566]bamtan2[/MENTION] I have never looked at OC for tuna. There's an slight OC option in our kernel for GPU OC, I think LineageOS has it enabled for tuna.

I once tested to add OC for espresso, ended in bootloop. Our old OC interfaces need an update and I really don't like to look into it.

There's still a bunch of CVEs left I need to look at.

Based on cve.lineageos.org I made a spreadsheet for our omap4 kernel

http://andi34.github.io/cve_omap4.html

Patched will be shown once I merge open commits.
[Samsung Galaxy Nexus] Android-Andi:
Forgot one:

About color control:

I can enable it, but ROM need to support it too.
[Samsung Galaxy Nexus] _yen_:
I totally agree with [MENTION=4545566]bamtan2[/MENTION], due to the increasingly yellowish display color of my maguro I'm using color control for several months now and can't get back on this. [MENTION=5153662]Android-Andi[/MENTION], is it still 3.0/staging the ti omap4 branch to build for testing?

Slightly OT, just built ti omap4 inside slim7 with GCC 4.7, all OK on my maguro, thanks.

Edit: although I prefer using scripts, kernel adiutor can manage screen colors well

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=2375847]_yen_[/MENTION] it's the 3.0/common branch now, what's missing is on our Gerrit.

My latest Slim7 uses GCC 4.7 too, uploaded yesterday.

About color control: there's an app available? Or only LineageOS13 supports it rom side?
[Samsung Galaxy Nexus] _yen_:
Thanks, so going to 3.0/common... for color control sorry but I don't know a more specific app then kernel adiutor, which anyway works well.

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
One more update.

updates to dsscomp & dss/manager,

enabled ColorControl for tuna

enable 512 MHz GPU frequency slot for tuna WARNING: I have added it as requested. I talked to [MENTION=2633638]Ziyan[/MENTION] and he says he don't recommend gpu oc anymore. A lot of his tunas died, and he used gpu oc for a lot of time. GPU OC could be the cause!

It might be still disabled userspace.

enable BFQ-v7r8 I/O scheduler

Why there's 2 Kernels?

1st kernel use BFQ-v7r8 I/O scheduler for 3.0 kernel

2nd kernel uses BFQ-v7r8 I/O scheduler for 3.3 kernel - needs a bunch of backports from 3.3 kernel to work (would be good if we don't need them)

I have never added BFQ scheduler on espresso because it was always buggy (crashes frequently, e.g. if you switch from bfq to anything else after boot)

Only added for testing. - if it works well, we can discuss to add it by default.
[Samsung Galaxy Nexus] bamtan2:
Thank you for adding color control! Like yen, I have used Kernel Adiutor and similar tweaking apps for color control in the past.

Good to know! When I mentioned overclocking, I was thinking about CPU overclocking. I don't know anything about GPU overclocking.

Which of the 2 kernels is stable, and which should we be testing for scheduler bugs? What kind of bugs should we expect to see with the scheduler?
[Samsung Galaxy Nexus] Android-Andi:
lol, thought you meant that because it is enabled that way on LineageOS13.

I think I'll disable it again on next update.

Maybe I take a look at CPU OC at a later point, but don't make much hope.

Both need to be tested. Bugs could be simple lag, freeze or kernel panic with reboot.

As it is used in LineageOS (but not on any other Rom Ziyan and I support) I wanted to make sure we test it again and maybe say hello or goodbye to it.

CM team wanted to use it on all supported devices in the past, but on old 3.0 kernel this didn't run well while I tested it - but things could have changed.
[Samsung Galaxy Nexus] _yen_:
I'm running bfq from 3.0 kernel and GPU OC (which was my standard setup years ago)

no noticeable bug until now, let's see how it works today...

Thanks

yen
[Samsung Galaxy Nexus] musical_chairs:
Lineage supports color control from ROM side, it can also be managed in any ROM from a root enabled app like Kernel Aduitor or TricksterMOD.
[Samsung Galaxy Nexus] Android-Andi:
There's the "Old" ColorControl in tuna kernel and the "new" way Lineage uses. I need to test if kernel auditor can manage it now without the old ColorControl config.
[Samsung Galaxy Nexus] bamtan2:
Whoops! I did mention "1.4ghz" (the overclocked CPU speed), but it was a whole paragraph after I mentioned overclocking :P I should have been more clear, but I forgot GPU overclocking even existed! I've never done GPU overclocking because I never had a reason to because I don't play games. But *C*PU overclocking helps with running apps.
[Samsung Galaxy Nexus] n_petr:
@Android-Andi, please, is it possible to add Wireless-Extensions to your kernel?
[Samsung Galaxy Nexus] bamtan2:
I'm running the first one, AnyKernel-2017-08-06-12-55-tuna.zip and it seems noticably faster. Not sure if I'm just running less stuff in the back ground or what. Feels faster than I'm used to so far. I'm skeptical though so I think it must just be me ;)

Edit: I did manage to crash Android by multitasking between video (twitch), browser (chrome), and messenger (telegram) a few times. It felt like they all used a lot of memory and the system couldn't page between them fast enough at some point.
[Samsung Galaxy Nexus] int0x19:
What assemblies cm11(kitkat) does your kernel work with?

On cm-11-20151108 does not work
[Samsung Galaxy Nexus] nobbi123:
Hello [MENTION=6395194]Android-andy[/MENTION], thanks a lot for your efforts for the Galaxy nexus.

I have a question regarding the Any-Kernel and the LineageOS. Are your CVE fixes to the kernel already included in the official LineageOS or do I need installiert the kernel afterwards?

Gesendet von meinem Nexus 7 mit Tapatalk
[Samsung Galaxy Nexus] Android-Andi:
No, lineage kernel isn't up to date. Ziyan might merge some of the cve but we don't waste time on tuna kernel from now and we'll switch to the common Kernel at a later point on lineage too.

For now: flash the kernel after lineage :)
[Samsung Galaxy Nexus] _yen_:
Hello [MENTION=5153662]Android-Andi[/MENTION], I saw [MENTION=6979267]nailyk[/MENTION] saying you on gerrit that he build his los kernel with gcc 4.8 and it works fine. As I've never saw a gcc 4.8 built kernel booting on my maguro in five years I do some test today.

He is perfectly right and his los 14.1 build successfully boot on my maguro after a good wipe.

I try to double check this building a gcc 4.8 anykernel of current TI OMAP4 and dirty flashing it on my usual slim7 rom, but it ends with a totally unresponsive phone and a black screen. BUT after a wipe Slim7 successfully boots and now i've restored all my settings, tested basic functionality and all seems working... I also briefly tried it on a fresh flashed UA (last build on server) and it boots here too...

So it seems that, after all kernel improvements made in last weeks, it is now possible to use a kernel built with gcc 4.8 even if it may require a wipe when starting from an existing rom.

Needs some more testing, i think...

bye

yen
[Samsung Galaxy Nexus] nailyk:
After reading your post I was more worried to say something wrong.

Thanks to jenkins, I can confirm it had been built with 4.8 with only one warning who looks related:

/var/jenkins_home/workspace/CM-14.1/kernel/samsung/tuna/drivers/mmc/core/quirks.c:480:9: warning: #pragma GCC target is not supported for this machine [-Wpragmas]
#pragma GCC pop_options

Feel free to ask me if you need more tests.

EDIT: screenshot replace to workaround XDA bugs
[Samsung Galaxy Nexus] _yen_:
No need to be worried, "adb shell cat /proc/version" show me exactly what you say ;)

And thanks for your work [MENTION=6979267]nailyk[/MENTION]
[Samsung Galaxy Nexus] Nonno Cicala:
Hi [MENTION=5153662]Android-Andi[/MENTION] . I've been using your latest kernel from this thread on my maguro with your Slim7 1.5, enabling BFQ. I tested for 4 days the first one, without backports from 3.3, and today will be the eighth day of the second one, with the backports.

I use to leave the phone in airplane mode during the night, to save battery and to use the phone as an alarm to wake up in the morning. One night I left the phone with a bit more than 50% charge left, and I found it shut off in the morning, with the battery completely drained. Luckily I didn't need to wake up that morning. :P When I charged it and booted it I looked at the battery log in the Settings, and there was nothing after about 50%, no data. I suppose the kernel locked and drained all the battery. This is pretty bad and never happened before.

The second kernel worked well, without issues besides those I usually have (like the RAM used by the System slowly increasing with time, to the point that it crashes if I don't reboot it before, but this always happened).

In my experience enabling BFQ made the system really more responsive, so please keep BFQ with the 3.3 backports!

I also really appreciate the availability of the GPU OC. I usually keep the clock at the default, normal speed, but when I play some games I can OC and have a slightly better experience. I hope this way to use the GPU OC won't reduce the lifespan of my phone too much. Being able to OC the CPU would be appreciated too. :)

Thank you very much!
[Samsung Galaxy Nexus] bamtan2:
[MENTION=5153662]Android-Andi[/MENTION] I left my phone charging for some days without checking it, and the screen would not turn on even though the LED was blinking. The screen was hot, so it was working in a loop. This is on 5.1 so I'm not sure if you want to see the syslogs after rebooting.
[Samsung Galaxy Nexus] Android-Andi:
Last_kmsg?

Bfq? If yes, which of both?
[Samsung Galaxy Nexus] PGHammer:
Why there are Two Kernels

One is for L and above; the other is for KK.

The L+ kernel I use as my default for all my L+ ROMs (including Lineage) - rather amusingly, it normally solves my radio issues (which makes little sense - since when would a kernel update do that?).
[Samsung Galaxy Nexus] Android-Andi:
It's needs some changes in the USB driver for radio, so it makes sense if it runs better now - we minimalized the needed addition to a minimum on our new kernel :)
[Samsung Galaxy Nexus] Nonno Cicala:
I've been suffering memory leaks for a long time. The RAM used by the System starts at about 450MB and slowly grows over 900MB. After that the phone usually reboots. It takes days to leak so much, but it happens every time. Since this happened with latest zzpianoman's ROM ( https://xdaforums.com/galaxy-nexus/development/rom-t3297218 ), Slim7 since first release and a recent build of UA on a different device (still maguro), I suspect [MENTION=4695183]zeelog[/MENTION] could be right when he dropped CMA in his LineageOS build due to memory leaks ( https://zeelogkang.blogspot.it/2017/05/lineageos-141-unofficial-712-gnex-tuna.html ).
[MENTION=5153662]Android-Andi[/MENTION] , would you kindly build a kernel without CMA for me to test if it would affect the leak? Thanks!
[Samsung Galaxy Nexus] edu24lal:
I just need a kernel that doesnt stop video playback :(
[Samsung Galaxy Nexus] Android-Andi:
I need peace on earth
[Samsung Galaxy Nexus] Android-Andi:
Fixes CVE-2017-0706 and CVE-2017-1000251
[Samsung Galaxy Nexus] Nonno Cicala:
Hi [MENTION=5153662]Android-Andi[/MENTION] . Today I had a kernel crash just after I pressed on Reboot from the Power menu. I enabled the advanced reboot options, so it shouldn't reboot at that moment. As you can see in the log it was a kernel panic. Last version (2017-09-17-12-14) with BFQ enabled. last_kmsg attached.
[Samsung Galaxy Nexus] kerpert:
Am I wrong or this kernel heavily improve fluidity and battery life? What trick on settings do you use?

Any new version is arriving?
[Samsung Galaxy Nexus] Zenroid:
Seems a number of freezing during charging using this kernel other than that it seems fast and fluid
[Samsung Galaxy Nexus] MayuraDeSilva:
Double Tap to Wake

Does this kernel support Double Tap to Wake option?

I'm hoping to try this on LineageOS 13.0. Is this same as the one in LOS13?

Thanks.
[Samsung Galaxy Nexus] Android-Andi:
No, it's not the same as on Lineage13 and no, no dt2w
[Samsung Galaxy Nexus] guest4711:
No, it doesn't. But you may use WaveUp (Turn the display on by waving) - https://f-droid.org/app/com.jarsilio.android.waveup for this purpose...

It's not. But it should work...
[Samsung Galaxy Nexus] MayuraDeSilva:
I'm already using Gravity Screen too. Wondering if the kernel supports DT2W, so I won't need another app :)

Thanks for the prompt reply.
[Samsung Galaxy Nexus] Android-Andi:
As requested and i also before told i'll add one once i have time:

CMA disabled on this kernel

works on Android 5.x, 6.x and 7.x

free RAM ~890 MB (while with CMA enabled we have ~970 MB)

Please let me know if you feel it's more stable :)
[Samsung Galaxy Nexus] musical_chairs:
The camera starts up faster. :D Other than that it's the same for me. Currently running ua7.1 on toro. 'System' still eats up all the available memory after a day or so and the phone gets very sluggish. I do not have the random reboots that others complain of on either setup.