yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nailyk:
My bad on this. I asked about the issue on 14.1.

I tried to highlight you in Omni riot to talk about maguro.

Great you cannot find it again, this is not supposed to be public ;)

And like it was said, this is not on topic here.
[Samsung Galaxy Nexus] GerardJ:
Sorry; of course you are quite right. However, the origin of the discussion was whether the spontaneous reboots, experienced with LineageOS 13.1, were also experienced with LineageOS 14.1...
[Samsung Galaxy Nexus] hga89:
I looked at the thread for L 14 and it also looks half-finished and not ready for use.
[Samsung Galaxy Nexus] Android-Andi:
I'll upload some device specific builds later today,

- includes security fixes for 2017-11-01 security patch level

- compiled as "user" builds for more security

Note: don't dirty switch from official to unofficial builds - clean flash required!

Edit:

Forgot to mention the build uses the new common ti kernel which is up-to-date with my latest AnyKernel
[Samsung Galaxy Nexus] Amankaif:
Smart lock trusted face stopped unfortunately

I have lineage os 13 , and I want the smart lock trusted face on my gnex but as soon as I click it it says trusted face stopped working . Previously on cm 12.1 it would be the same but on the third screen. It would give me information and when I would press next to start capturing my face , trusted face stopped working message would appear. Please help
[Samsung Galaxy Nexus] hga89:
Are they part of the official build-tree? Which of the bugs that have been mentioned in this discussion have been fixed?
[Samsung Galaxy Nexus] Android-Andi:
Not yet.

Kernel is switched on next official build and maybe the security bulletin changes too, depends on feedback.

"User" builds aren't allowed official on Lineage because they have issues signing those builds.
[Samsung Galaxy Nexus] osm0sis:
Seems like an awful lot is missing in the new kernel.. colorcontrol, zram, gpuoc.. :confused:

I'm finding it very sluggish and getting a lot of hangs/FCs now. Rolled back to 1112 and things seem back to normal. :eek:
[Samsung Galaxy Nexus] Android-Andi:
zRam was disabled in the past already for CMA implementation ( https://github.com/LineageOS/androi...mmit/99b85c6704e66d5fcc47e4540ef41341d2a608e4 )

GPU OC won't be added back by default, [MENTION=2633638]Ziyan[/MENTION] had some dead Tunas because of OC in the past, but we can make an optional AnyKernel for those who need it.

Color Calibration should work without the old kernel interface, using Lineages implementation. ( https://github.com/LineageOS/androi...mmit/f9e5c79f5de76ef376da6c09a17c91933ac9a49f )
[Samsung Galaxy Nexus] osm0sis:
Disabled by default, yes, but still available in the kernel to enable if needed. I have it running on 1112 right now. :)

As for GPU OC, again, sure, not by default, but would be nice to have the option in the kernel for power users.

What are the new sysfs locations for the color settings? Could you please add a link in the interface to the old rgb node location for backwards compatibility?

None of this well established stuff makes sense to be stripped away this late in the life of a device. :(
[Samsung Galaxy Nexus] Android-Andi:
About OC, Option exist:

https://github.com/LineageOS/androi...3101ac3#diff-5fc42b90f9c70c5edc13dcc45f50828d

About sysfs, using omapdss now:

https://github.com/LineageOS/androi...mmit/453e2165e3dcba2274b21b5c0a395c8624d5a354

Edit:

About Color Calibration: best would be an own app independent of the ROM (using same interface we use on cmhw). IDK how much work it'll be to make it standalone as device app.

And yeah, some stuff can change late to make way for new stuff which are better solutions :)
[Samsung Galaxy Nexus] osm0sis:
My Synapse injector enables the Synapse app to control everything. It shows that your new kernel in the 1119 build is missing that gpuoc control (I have both the old and new locations), and of course zram.. I'll look into the omapdss stuff, and see about adding that new location for color control..

But beyond that, ROM or kernel, something is seriously wrong. The device pretty much ground to a halt until I managed to downgrade to 1112. Totally back to normal on 1112. Then I enabled zram and it's even better.
[Samsung Galaxy Nexus] Android-Andi:
Gpu oc and zram are disabled in defconfig, yes. But it won't be a issue compiling one for those who need it

Edit:

Checked dmesg? On "user" builds there might be some more selinux denials which don't show up on "userdebug" builds.
[Samsung Galaxy Nexus] osm0sis:
I needed a working device today to test the upcoming Magisk beta, but I'll venture into the unknown with 1119 again later in the week and post a dmesg if nobody else can get to it first.

Edit: Wait, I thought you said user builds weren't allowed on official Lineage? I'm on the official 1119 build.
[Samsung Galaxy Nexus] Android-Andi:
I am quite busy at work ATM and still need to get ril working on tab2... But I can flash lineage on my maguro sometimes this week and do a quick test too. Besides disabled OC and disabled zRam in kernel config there isn't any change kernel side for tuna (sure, some more CVE fixes). So it could be an problem with "user" build maybe.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=4544860]osm0sis[/MENTION] [MENTION=5153662]Android-Andi[/MENTION]

I don't know anything about the programming side, but from my testing, a CPU overclock to 1.3ghz - 1.4ghz makes a nice improvement to real world performance. It hurts battery life because of reduced power efficiency, but this is not a problem for me because I leave my maguro plugged in most of the time. I have never overclocked the *GPU*, and I have no reason to. It's the CPU overclock that helps in my experience.

ZRAM and CMA are both good, but if we cannot fix their incompatibility, we must find which performs the best. In my old testing, ZRAM could add 100MB+ of memory, with the side effect of longer task switching and probably worse battery life. But it did guarantee more apps would stay open in memory. If it is possible to enable/disable ZRAM and CMA for testing, users could re-run these tests and figure out what works.

Color control is important of course. I think there is a built-in adjustment to the color variables in recent builds, so my maguro looks pretty good without tweaking, which is nice.

In the past I have always used either Kernel Adiutor or Synapse to make ROM/kernel adjustments.
[Samsung Galaxy Nexus] osm0sis:
Alright [MENTION=5153662]Android-Andi[/MENTION] here's a dmesg.log, hopefully it's of some use in figuring out what's going on: https://pastebin.com/QQ1Hbe9t

Setting swappiness back to 60 and page-cluster back to 3, the Android defaults, (they're still set to their respective 100 and 0 to improve zram function) seemed to help the abysmal performance I was seeing a bit. But to be honest, any possible bugs aside, interactive and its tunables could be causing a large part of the perceived performance loss; we'd had an updated interactive on GN for awhile with the updated target_loads defaults which use multiple #MHz:%% values to better scale, and those being gone suggests the whole of interactive is rolled back, so this is naturally a big step back in terms of feel/use.

And for everyone's info, the new color control is here: /sys/devices/platform/omapdss/manager0/cpr_coef

It accepts RGB 0-256 in the format "R 0 0 0 G 0 0 0 B", e.g. my current test values:

echo "205 0 0 0 205 0 0 0 255" > /sys/devices/platform/omapdss/manager0/cpr_coef;

then if it isn't already:

echo 1 > /sys/devices/platform/omapdss/manager0/cpr_enable;

All 0s is basically an off screen, so LOS caps the lower end at 25. You can also go above 256 and it turns more into a tint. :p

If I'm interpreting the documentation correctly the other numbers could likely also be changed to have more of a gamma or highlight/shadow effect: https://github.com/LineageOS/androi...hardware/DisplayColorCalibration.java#L18-L33

With the old colorcontrol (0-400) my calibration of 225 230 385 was nice and bright, and popped without being too oversaturated on my old screen, and compensated for the ancient AMOLED defects well. Doing the math (x/400*256) it doesn't match up and I had to take more green out and jack up the brightness on the new interface to achieve a similar balance and effect.

Edit: Hey, works on TWRP 3.1.1-1 too! :D
[Samsung Galaxy Nexus] bamtan2:
For what it's worth, I'm testing zeelog's latest lineage 14 today, and it seems to work fine. I get a system crash on startup the first time, but after that, everything else seems to work. I wonder if you can compare what you're seeing with what I'm seeing. For example, in kernel adiutor cpu tunables, target loads for me are 70, 920000 at 80, and 120000 at 99. I remember seeing it that way a long time ago, but maybe it was improved since last I saw?
[Samsung Galaxy Nexus] osm0sis:
Yeah LOS13 1112 had that too, that's the updated interactive. 1119 has target_loads at just 70, suggesting it's the old interactive before those updates.
[Samsung Galaxy Nexus] Android-Andi:
Interactive governor can be updated if needed, I might have a few min this weekend. The only major thing different seems that Google devs once synced it with 3.4 kernel while ti didn't in it's kernel.

Not sure if it cherry-picks fine https://github.com/LineageOS/androi...mmit/b33b4fdbb36314cd625b453586cde0060c10a761
[Samsung Galaxy Nexus] bamtan2:
I remember the guy from that OMAP phone company came here and ziyan was hoping to get the latest TI source or blobs from him. TI would have all sorts of perfected code that they never released publicly because no one paid them to. It is possible that this public google code is newer TI code than the public TI code! :eek:
[Samsung Galaxy Nexus] Android-Andi:
Governor is independent from the other ti code you are talking about ;)
[Samsung Galaxy Nexus] Android-Andi:
Posted a new AnyKernel which has the "old" interactive governor. Please test if you like and let me know if it runs better or not.

Have a nice evening!
[Samsung Galaxy Nexus] osm0sis:
Thanks for this! In my testing it definitely feels a lot smoother again with the "old" (new) 3.4 kernel interactive. :)

I've updated my GN Synapse Injector Add-on AK2 zip for the new OMAP DSS color correction, but unlike Lineage's controls I've allowed the full 0-511 range and then forced it to default to 256 256 256 (which is equal to unchanged screen color) since if enabled at the interface's default of 0 0 0 you get a completely black screen.

I experimented with the other 6 channels but found it made things far too complicated, and near impossible to try and get something that looked good when they were anything but the default 0.

Also, I did a bit more experimenting on 1112 and zram works fine until you try and turn it back off with swapoff, at which point swapoff hangs. Doesn't matter if it's busybox swapoff or toybox, so that's interesting. I added a few workarounds to try and keep zram as working as possible from Synapse under these conditions.

https://github.com/osm0sis/GN-Synapse-Injector/commits/master

https://basketbuild.com/devs/osm0sis/osmods

It would be nice if zram could coexist with CMA on this device, since even on the Nexus 5X (which has 2gb of memory) a 1gb zram swap goes a long way for multitasking improvements. Even Google has 500mb of zram swap out-of-the-box on it, so the argument that CMA should be enough for the Galaxy Nexus doesn't really hold a lot of water.. :confused:
[Samsung Galaxy Nexus] bamtan2:
Yeah I never had any luck tweaking the extra channels! But that's okay because I never needed them!

Yeah zram always worked for me, but tweaking it while it was on didn't. Mostly the system would crash if I tried to alter the settings once it was going. But luckily I never actually need to do that ;)

IMO ideally both CMA and zram would work. I believe Zeelog has disabled CMA on his builds because he thinks it causes camera/video trouble. I believe Ziyan disabled zram on his builds because the combination of both methods caused some problems. The best we can do now is figure out how to test all of this from scratch with the latest code, and see if there is any reproducible problem.

The argument against zram would be that it uses precious CPU time to compress and uncompress. In my experience that is not a problem, because in my usage the CPU is slow but works, whereas the memory is too limited to keep enough apps in memory. Furthermore, if I look at the memory stats on Zeelog's LOS14, much of what is kept in zram is irrelevant stuff anyway, like the default email app that no one uses, so it will not frequently be compressed/uncompressed. Basically zram is unquestionably worth it in my real world experience.

That said, if zram and cma were truly incompatible with each other, then we would need to weigh them against each other and choose the best. I don't know how much memory CMA frees right now. Zram, in the average real world scenario for me, would compress 250MB of memory into 125-150MB of space, saving about 100MB of space, allowing an entire extra app or two to run without closing. This makes a huge difference when you can only hold a few apps in memory. In the best case scenario I just tested, I got it up to using 350MB of the 400MB available in zeelog's LOS14. That'd be maybe 150MB-175MB memory created.
[Samsung Galaxy Nexus] Android-Andi:
Those who like to play with zRAM can flash AnyKernel attached here: https://xdaforums.com/showpost.php?p=74658926&postcount=136

I think we can enable it in defconfig without trouble: you won't notice a difference as long as there's no changes to our ramdisk or custom scripts used to enable zRAM.

Let me know if you face any issues with it but not enabled zRAM via scripts/tools or via modified ramdisk.
[Samsung Galaxy Nexus] bamtan2:
Is this appropriate for testing on top of ROMs that use CMA? If flashing this keeps CMA enabled, then we should be able to test how both interact together.

Furthermore, if the need arises, is there a way for users to disable CMA? I think the #1 priority is testing CMA+zram together. But if the need arises, we might need to turn off zram by flashing the old kernel, or turning off CMA by ___.

Thank you very much for your work!:good:
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=4545566]bamtan2[/MENTION] CMA needs to be disabled in defconfig, there's no other way.
[Samsung Galaxy Nexus] MayuraDeSilva:
Issues related to OMAP4 kernel?

I've been using LineageOS 13.0 without any issues and as the daily driver until the 20171112 build, and then updated to the latest 20171126 build yesterday.

Now I'm experiencing reboots when backing up apps using Titanium Backup and downloads are being paused when the screen is turned off too.

Could be related to the new OMAP4 kernel?

Thanks.

UPDATE #1: Had the screen timeout set to 30 mins and then I could backup without any reboots too. Reboots were encountered once the screen goes to sleep.

UPDATE #2: Reinstalled 20171112 build and everything is back to normal. No idea what was going on with the latest build.
[Samsung Galaxy Nexus] andifor:
Thanks for your post. I don't have a solution, but can confirm stability issues with the 20171126 build.

First I thought it's one of my apps, I had several crashes (freezes) a day and I had to restart my phone 2 to 3 times to get it up and running again (some immediate crashes on startup).

Now I'm back to the 20171112 build => this build runs flawlessly. I just installed it over the 20171126 build.

So thanks again,

andifor
[Samsung Galaxy Nexus] Android-Andi:
Hey [MENTION=4912896]MayuraDeSilva[/MENTION] , hey [MENTION=7674404]andifor[/MENTION] !

Please take a dmesg once you face any issues.

If a reboot happens: take a last_kmsg right after it booted again.

You can attach the log(s) here so we can take a look at it.

Some issues could be related to BFQ which is used by default. The old kernel used BFQ from 3.3 kernel instead 3.0 implementation.

I have attached a new kernel which goes inline with old tuna kernel in big parts, you can find it here: https://xdaforums.com/showpost.php?p=74714110&postcount=144

Please let me know if the kernel fixes your issue(s).
[Samsung Galaxy Nexus] Wolfglance:
lineage-13.0-20171203-nightly - Fails

Updated the phone to this : lineage-13.0-20171203-nightly-maguro-signed.zip - 2017-12-03 07:45:45

And since the phone fails to start - Stucked on the google screen. (All was fine on the 2017-11-12 one)

Am I the only one having this issue ?

Thanks.
[Samsung Galaxy Nexus] Android-Andi:
Could you attach dmesg from booting November build?

I have the feeling it's using GCC4.8 and our old known FW patching bug is visible.

You can flash my latest anykernel on top of latest build which is compiled on GCC4.7.

( Missing https://github.com/LineageOS/androi...mmit/d2ffff1fdce097b0557b31fecb7a0fc87630f007 ?)

Edit:

It's using GCC 4.8 by default and found the missing commit to solve the issue for next weekly. Until that you can flash my anykernel to get latest build booting.
[Samsung Galaxy Nexus] MayuraDeSilva:
Hey [MENTION=5153662]Android-Andi[/MENTION] - I've installed 20171203 build to get the dmesg and kmsg, and encountered the stuck-with-Google-logo problem too. Now can't even go into recovery :eek:

Any ideas?

UPDATE #1: Left the device turned off for 5 mins and Vol Up + Down + Power - Voila! Then flashed the latest AnyKernel-2017-12-02-19-27-tuna.zip and now it's booting.

UPDATE #2: Haven't had any reboots so far with the combination of 20171203 build + AnyKernel-2017-12-02-19-27-tuna. Backups are fine too. Anyway, going back to 20171112 build.

Would like to know the benefits of using AnyKernel over the default kernel on LOS 13 too.

Thanks.
[Samsung Galaxy Nexus] Android-Andi:
Not sure why going back to the old build, but ok.

We've switched to one stable kernel base [MENTION=2633638]Ziyan[/MENTION] and I am using on all roms now (makes maintaining easier). Latest AnyKernel adds some parts on top to bring the Kernel more inline with old tuna kernel used on previous lineage13 builds. Those parts will be added back if they are a improvement.

In general the AnyKernel is our stable base + CVE fixes and improvements before we merge them into our stable kernel.

I'll stay away a while from XDA and might not notice any posts here. Next weekly should boot again, I requested to remove 1203 build because of the booting issues.

On a side note: My previous post was removed because I must have said something someone understood wrong - I am sorry!

We've missed

https://github.com/LineageOS/android_kernel_ti_omap4/commit/a333731d11faa838215e0a09e9f9760f25380292

which is sometimes needed if GCC4.8 or newer are used. On Lineage there's no way to use GCC4.7 by default - sadly.

Have a good night together!
[Samsung Galaxy Nexus] Wolfglance:
* Worked by following your suggestion : " You can flash my latest anykernel on top of latest build "

But updating to the latest nightly already messed up with the phone... I had to wipe everything and install the latest build along with your latest anykernel for it to work.
[Samsung Galaxy Nexus] MayuraDeSilva:
Holding up until the stuck-with-Google-logo problem is fixed in next build :) Also trying out 7.1.2 builds these days.

Thank you very much for the detailed explanation, and for working hard to keep the Galaxy Nexus devices alive :)

Have a fantastic week!
[Samsung Galaxy Nexus] Android-Andi:
Would have been enough to boot into recovery and flash the AnyKernel, no need to wipe everything.

If you are unable to boot into recovery directly:

Pull battery and reinsert it -> press the volume button + power -> choose to reboot recovery

Please note:

Since GCC 4.8 is used by default it could always happen again for no visible reason emmc FW patching fails and causes stuck on Google logo.

Another note again:

If you are having trouble/aren't happy with current kernel after we switched the new source: provide a dmesg if something odd happened, if you face any random reboots provide last_kmesg taken directly after it booted again.

After that please test the anykernel i provided and leave some feedback. If made changes to get more inline with old tuna kernel are an improvement well merge the changes into our stable base.
[Samsung Galaxy Nexus] MayuraDeSilva:
+1 - I've been through the same and flashing AnyKernel was enough.
[Samsung Galaxy Nexus] fahrer17:
I tried to flash a friend's maguro today to lineage-13.0-20171203-nightly-maguro-signed.zip doing a full wipe but without success; got stuck with the Google logo. Going back to recovery I discovered that the phone was still empty (=no directories like Download etc. were created).

Flying over the last posts (do you say that in English? :confused:) I used lineage-13.0-20171126-nightly-maguro-signed.zip and it worked within minutes. Trying to update afterwards to the 20171203-nightly failed again.

Since I'm not too familiar with the maguro (and didn't fully understand the last posts): Is this a temporary problem, will later updates work again?
[Samsung Galaxy Nexus] Android-Andi:
Flash https://xdaforums.com/attachment.php?attachmentid=4350474&d=1512239547 and recovery and it'll boot again.
[Samsung Galaxy Nexus] bamtan2:
Temporary :) These builds are what many developers would call "unstable nightly builds". They are automatically uploaded once built, without testing to guarantee they work. A stable build would be tested for days or weeks before you are allowed to download it, and then it would be "certified stable".

Software development is a balance between getting the newest features and fixes, and avoiding the newest bugs!! ;) :laugh:
[Samsung Galaxy Nexus] fahrer17:
Do you refer to me? If so I will tell my friend. But as far as I know this lazy bum he will simply wait for the next update ;)

But thanks for the advice!

Alright, good to know. It's absolutely no problem for me if such things happen from time to time (so what are backups for? ;)). I'm more than glad and thankful that "old" devices like (in my environment) the maguro, serranoltexx, mako etc. are kept alive and save by all those great developers out there!
[Samsung Galaxy Nexus] Wolfglance:
Hi, a beginner question ..

Can I use SuperSU instead of SU (the one in the OP) for root ? Thank you in advance.
[Samsung Galaxy Nexus] bamtan2:
So I think all will work, but only one at a time, of course ;) The official lineage root tool, the classic SuperSU, and the new Magisk. Just pick one. A lot of people are using Magisk these days, but for me, I use just one app that requires root, so I never see root or think of it again, so it doesn't matter which I choose.
[Samsung Galaxy Nexus] garrymar:
[MENTION=5153662]Android-Andi[/MENTION], thank you very much for your contribution!

I noticed the CVEs still tagged as 'on gerrit'. Does it mean the patches are not merged at the moment? Or cve.lineageos.org shows outdated information? Thanks.
[Samsung Galaxy Nexus] Android-Andi:
Haven't had time to mark them on ti kernel as patched. Failed to import cve status from espresso/tuna kernel.
[Samsung Galaxy Nexus] garrymar:
I see you dedicate much free time to fix CVEs for legacy device. Thank you! Nevertheless, there are much unpatched 2017-* CVEs for tuna kernel. Is the kernel not affected really or is it just outdated info too? Thanks!
[Samsung Galaxy Nexus] Android-Andi:
Some outdated information, some don't apply and some aren't added.

Tuna kernel isn't used anymore too.
[Samsung Galaxy Nexus] garrymar:
Ok. Thank you.

Oh, I lagged behind Galaxy Nexus development. :) Just replaced the kernel supplied by LOS13 with Anykernel. Thanks.

By the way, I'd like to post old issue related to maguro on LOS13. When I switch between apps using recent menu, I get OpenGL rendering failure and UI crash after several switching attempts. The issue is 100% reproducible for me. The related log is attached. If the problem is not maguro specific, I'll open a BUGBASH report. Thanks.
[Samsung Galaxy Nexus] andifor:
Might sound like a stupid question: do I still have to update recent LOS13 (of today, 20171224) with AnyKernel 2017-12-02?

I didn't see any related information since the first mention of AnyKernel 2017-12-02, so any information is much appreciated.