yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bamtan2:
I am testing this now on UA 6 because people are complaining about a memory leak on 7.

I note some things from my experience:

1. On first boot the UA 6 setup gets a connecting error at the WiFi stage. Googling found that the workaround is to reboot.

2. The governor is not BFQ. Last I heard we were testing BFQ to make sure it is stable. I think ziyan thought it might be faster. I don't remember having any problem with it.

3. There is no zram enabled. We turned zram off because the combination of CMA and zram was buggy. If CMA is too buggy to use alone, we must reclaim the zram feature. It should be set to 250-350mb and swappiness=100.

4. I still think color control and CPU (not GPU) overclocking are important features to have to extend the usable life of the device. Overclocking to 1300 or 1400mhz burns more battery and hits thermal limit quickly under load, but it gives a slightly more snappy response, and I personally use my device plugged in anyway. The default screen color looks good with this kernel and ROM, so I'm guessing you guys have tweaked the default settings to lower the green level for all of us. Both color control and overclocking are optional features. Stability is more important.

Thank you, and I will continue testing. Keep up the good work!

Edit: Two more things I want to get on the record for new galaxy nexus ROM builds: touch sounds and volume button screen wake are important to have tweaked by default in the ROM. Touch sounds need to be off by default because I think I still hear the crackling sound effect bug when touch sounds are on, and new users won't know that they need to turn this feature off. And enabling volume button wake is important to reduce the mechanical load on the power button of older devices like ours. It is possible to break the power button at this age, so it is important to have this feature on by default to potentially save some devices. Again this is a hidden feature that most people won't know to turn on, so it should be on by default.

Two more UA 6 bugs I observed: 1. the aosp browser crashes when trying to download a file, I assume because of a permission problem. 2. An app installing from play store stopped installing with no error and I had to start installing it again. I cannot reproduce this. The device was under load at the time, so maybe this contributed.
[Samsung Galaxy Nexus] Android-Andi:
New AnyKernel passes SafetyNet on "user" builds, thanks to [MENTION=2633638]Ziyan[/MENTION] !

Some small updates, also again one for L/M/N without CMA for those who like to test.

Enjoy!
[Samsung Galaxy Nexus] Nonno Cicala:
Thanks [MENTION=5153662]Android-Andi[/MENTION] !

I tested AnyKernel-2017-11-11-18-22-tuna-NO-CMA with ua_tuna-7.1.2-20171109050541 (latest at the moment), on a clean installation without GApps, without root, with only 8 apk installed with adb:

https://f-droid.org/repo/eu.siacs.conversations_236.apk

https://f-droid.org/repo/me.zeeroooo.materialfb_52.apk

https://storage.googleapis.com/goog...roid/ebookdroid-arm7-cortex-a9-neon-1.5.1.apk

https://www.apkmirror.com/wp-conten...inAPI15(armeabi-v7a)(nodpi)_apkmirror.com.apk

https://www.apkmirror.com/wp-conten...nAPI21(armeabi-v7a)(320dpi)_apkmirror.com.apk

https://f-droid.org/repo/com.philliphsu.clock2_113.apk

https://f-droid.org/repo/acr.browser.lightning_96.apk

http://mirror.e4a.it/vlc/vlc-android/2.5.7/VLC-Android-2.5.7-ARMv7.apk

In less than 24 hours the RAM used by the System alone grew over 830MB, so the memory leak I found in Nougat on my maguro ( https://xdaforums.com/showthread.php?p=74519478#post74519478 ) is not affected by CMA.

The system is actually more stable with CMA, because with more available RAM it takes more time to fill it to the point of soft reboot. :)

It seems there are only advantages in using CMA here, so I think it's better to keep it enabled by default.

Thanks again.
[Samsung Galaxy Nexus] _yen_:
[MENTION=7328533]Nonno Cicala[/MENTION], please can you test on UA 7.1.2 also if adding ro.egl.destroy_after_detach=true property can mitigate memory leaks? I'm using it for some time (on slim7) and it seems having a beneficial effect (thought it not completely solve) for the suspend/waking memory leak.

Thanks for all the time you spent testing memory behavior on tuna.

bye

yen
[Samsung Galaxy Nexus] Nonno Cicala:
:)

Now I wiped System partition, flashed ua_tuna-7.1.2-20171116-0522, added ro.egl.destroy_after_detach=true to build.prop and wiped ART cache and cache partition. I didn't factory reset from the previous ua_tuna-7.1.2-20171109050541 with 8 apks for lack of time, but I think it shouldn't compromise this test.
[Samsung Galaxy Nexus] Nonno Cicala:
After less than 24 hours the system sucked more than 850MB RAM, so if there is an effect of ro.egl.destroy_after_detach=true is of an order of magnitude smaller and difficult to quantify. :(
[Samsung Galaxy Nexus] _yen_:
Thanks for having tested anyway [MENTION=7328533]Nonno Cicala[/MENTION], sadly it seems that memory leaks are really a big problem on tuna. For what is in my experience the ro.egl property slow down system memory increase, but it seems not enough on long term.

Thanks again.

bye

yen
[Samsung Galaxy Nexus] musical_chairs:
That property requires a patch like this: https://review.lineageos.org/#/c/65040/

So it won't do anything on UA, but it will work on other roms like LOS (and apparently Slim). I'm going to run a test build of UA with that patch and see if that helps.
[Samsung Galaxy Nexus] musical_chairs:
If you want to test it, here is a build of UA 7.1 with the EGL_destroy patch applied: https://www.androidfilehost.com/?fid=673791459329062290
[Samsung Galaxy Nexus] bamtan2:
Just to be clear, we're talking about this right? https://jira.lineageos.org/browse/BUGBASH-733

And we think this might be the cause of the 7.1-exclusive memory leak? Very cool!
[Samsung Galaxy Nexus] musical_chairs:
Yes, that's what we're talking about. If it helps, we'll get it merged so everybody can enjoy a less leaky 7.1 :)

This turned out to not be a kernel issue; sorry for taking the thread O.T.
[Samsung Galaxy Nexus] Nonno Cicala:
Now testing. After about 14h the system is using 410MB. This is much better, it's a result compatible with no leak. Thanks!
[Samsung Galaxy Nexus] _yen_:
As i remember this post from July:

shouldn't safer for now to add the ro.egl.destroy_after_detach property in relevant branch of device tree instead of in stable branch of hardware/ti/omap4? (please note that i can't test it on 4.4 as I'm currently waiting to have my maguro back)

Sorry all for having derailed this thread in a big OT.

bye

yen
[Samsung Galaxy Nexus] Android-Andi:
It's ok in stable because it doesn't hurt if the frameworks patch isn't added , the prop only don't do anything in that case

Edit:

Else we'll have it to all devices and every branch which is a lot of commits ;)
[Samsung Galaxy Nexus] musical_chairs:
I forgot about that. I'll have to test it again on 4.4. Android-Andi is right, it should do nothing at all on 4.4 because the frameworks patch isn't there. But I'll test it again.
[Samsung Galaxy Nexus] Nonno Cicala:
After more than 27 hours my system is taking 440MB. So I'd say that ro.egl.destroy_after_detach really works! :D
[Samsung Galaxy Nexus] Android-Andi:
Ok, so let's move this discussion to the rom thread ;)
[Samsung Galaxy Nexus] Nonno Cicala:
Yes, sorry for the OT, I just wanted to give it a happy ending. :)
[Samsung Galaxy Nexus] Zenroid:
The no CMA kernel seems much more stable in my case on CM12, thanks
[Samsung Galaxy Nexus] Herrie82:
Regarding newer toolchains. For our LuneOS (Open source distro based on Open webOS we maintained support for the Galaxy Nexus (Maguro) for a long time and we used the Yocto/OpenEmbedded project for our builds which always included newer GCC toolchains. We have been able to build the Maguro kernel and run it without issues using GCC 5 and 6 for example. Patches we used are available at https://github.com/shr-distribution/linux/commits/tuna/3.0/cm-12.1 (The ones from December last year and January this year). We unfortunately had to drop support for the Galaxy Nexus at our end due to a hard requirement of a working 3.4 kernel from Yocto for some recent systemd and glibc version.
[Samsung Galaxy Nexus] Android-Andi:
Some people have been disappointed on Lineage 13 because interactive governor is different on the omap based kernel. Attached AnyKernel is in sync with previously used interactive governor on tuna (synced with 3.4 kernel).

I've had no time to test, yet. Please let me know if it runs better for you now.
[Samsung Galaxy Nexus] The Doctor04:
So would this be a downgrade to them previous update? I am on latest and greatest Slim ROM and have no complaints
[Samsung Galaxy Nexus] Android-Andi:
You can always go back to previous anykernel ;) the 3.4 kernel based interactive governor might improve your feelings :)
[Samsung Galaxy Nexus] Android-Andi:
Following changes on attached AnyKernel:

tuna: defconfig: enable LZ4-backed zRAM
dccp/tcp: do not inherit mc_list from parent (CVE-2017-8890)

(LZ4-backed zRAM as requested by [MENTION=4544860]osm0sis[/MENTION])
[Samsung Galaxy Nexus] osm0sis:
Could you add back the 512 step to the GPU overclock as well? As with zram, its mere existence doesn't hurt anything since it's not enabled by default (the default overclock remains at 384). :D:fingers-crossed:
[Samsung Galaxy Nexus] Android-Andi:
No, we are not going to add back the GPU OC for security reasons. Like mentioned previously [MENTION=2633638]Ziyan[/MENTION] broke some tunas because of OC.
[Samsung Galaxy Nexus] osm0sis:
Okay, but to be clear, 384 is also an overclock, so you're already overclocking by default. 307 was the factory max on this device.

I don't see the harm in allowing a person to choose to possibly harm their own device by putting it up to 512, my device has been running at 512 for literal years; even when 512 is available it defaults to 384. Shrug. :eek:
[Samsung Galaxy Nexus] bamtan2:
Thank you for this, I will test it with the latest UA and report back after a few days!
[Samsung Galaxy Nexus] Android-Andi:
384 MHz was added by TI in the 3.0 kernel update. the old tuna kernel couldn't handle 384 MHz (some OPP problems...), but they fixed it
[Samsung Galaxy Nexus] bamtan2:
I'm trying this with the latest UA, and nothing is exploding! But I don't see any indication of zram being enabled. The zram apps on the Google store don't work with zeelog's LOS14 either. But the diskinfo app and the system settings app section mention zram on that LOS14, but not on this UA + kernel.
[Samsung Galaxy Nexus] Android-Andi:
https://github.com/LineageOS/androi...e5ce2bc#diff-7757ae3d5fee7079ec3e1c9d061f4d29

https://github.com/LineageOS/androi...7695d03#diff-7757ae3d5fee7079ec3e1c9d061f4d29

https://github.com/LineageOS/androi...130d9c7#diff-7757ae3d5fee7079ec3e1c9d061f4d29

Those aren't added so it's not supposed to work without ramdisk changes or special scripts
[Samsung Galaxy Nexus] MayuraDeSilva:
Installed this over DU 11.7 and improved the performance :)
[Samsung Galaxy Nexus] Bludwurst:
Installed AnyKernel over LOS 13 for toro and the difference in performance is like night and day.

My toro does have some issues remaining; Instagram tends to close itself (not "App stopped responding" force close. It just dies suddenly) and Twitter force closes sometimes. The camera sometimes fails. I believe the problem lays in the kernel as the same issues were present with Slim7... Or the ROMs just happen to have similar bugs? ?

It is otherwise fine; it's not really a "main" phone/daily driver.
[Samsung Galaxy Nexus] Android-Andi:
New AnyKernel attached.

Changes:

dd27c97 defconfig: tuna: Modular OMAPLFB
4398e15 defconfig: espresos: Modular OMAPLFB
81ac9e4 omaplfb: Prepare for modular build (omaplfb.ko)
8b08733 mfd: twl6040: Set i2c mode correctly.
7d306af ASoC: tuna/sdp4430: fix mismatched mcbsp rx/tx threshold set.
39225d8 ASoC: tuna: simplify some logic.
[Samsung Galaxy Nexus] Android-Andi:
Another one, previous changes plus the following:

d2414c7 SELinux: do not allocate stack space for AVC data unless needed
78c76be selinux: don't transliterate MAY_NOT_BLOCK to IPERM_FLAG_RCU
1a07dd6 lsm_audit: don't specify the audit pre/post callbacks in 'struct common_audit_data'
3e52d03 Yama: add PR_SET_PTRACER_ANY
575c5a9 security: Yama LSM
63ee3e8 capabilities: initialize has_cap
e28294b capabilities: do not grant full privs for setuid w/ file caps + no effective caps
64d62ad selinux: fix off-by-one in setprocattr
288c0a4 inet_diag: Partly rename inet_ to sock_
484951f rcu: treewide: Do not use rcu_read_lock_held when calling rcu_dereference_check
995867f selinux: Fix Kernel panic due to NULL pointer dereference
9c23e17 selinux: remove unused|deprecated includes
364f5cc4 SELinux: check OPEN on truncate calls
9e2bea0 SELinux: include definition of new capabilities
81ef3d4 SELinux: remove avd from selinux_audit_data
2e477cf LSM: shrink the common_audit_data data union
2efa0b5 get rid of pointless includes of ext2_fs.h
393b3e3 selinuxfs: merge dentry allocation into sel_make_dir()
5940c71 SELinux: selinux/xfrm.h needs net/flow.h
42ef646 selinux: Casting (void *) value returned by kmalloc is useless
550e224 selinuxfs: remove custom hex_to_bin()
169c48d selinux: sparse fix: fix several warnings in the security server code
8dde0ae selinux: sparse fix: include selinux.h in exports.c
6c2c392 selinux: sparse fix: fix warnings in netlink code
0100b82 selinux: sparse fix: eliminate warnings for selinuxfs
928f5e0 selinux: sparse fix: declare selinux_disable() in security.h
0da4356 selinux: sparse fix: move selinux_complete_init
5b31a53 selinux: sparse fix: make selinux_secmark_refcount static
a19256d doc: Update the email address for Paul Moore in various source files
2e90e97 security,rcu: Convert call_rcu(sel_netport_free) to kfree_rcu()
9b59fb3 security,rcu: Convert call_rcu(sel_netnode_free) to kfree_rcu()
1f5b1f9 ->permission() sanitizing: don't pass flags to ->inode_permission()
381ff1a audit: treat s_id as an untrusted string
[Samsung Galaxy Nexus] guest4711:
No new problems detected during boot and first checks. Deep sleep seems to work, too. Thanks again, Andi.

Edit; Sorry, wrong thread. It's belonging to espresso...
[Samsung Galaxy Nexus] Android-Andi:
There'll be another one tomorrow [emoji23]
[Samsung Galaxy Nexus] bamtan2:
This one isn't booting for me, stuck at Google logo ;)
[Samsung Galaxy Nexus] Android-Andi:
Which ROM?

Edit:

there might be some roms not using init.omap4.rc , those roms would need a different patch.
[Samsung Galaxy Nexus] Android-Andi:
Let's see if https://github.com/nathanchance/AnyKernel2/commit/a892e4ff979227f19c5f9d9570262ada33f85fc1 fixes it, I'll test myself tomorrow. For now the check is removed until it's fixed.
[Samsung Galaxy Nexus] osm0sis:
There is no reason to make system rw just to read build.prop.. it's already mounted ro at that point. :confused:
[Samsung Galaxy Nexus] Android-Andi:
Modules aren't added with:

https://github.com/andi34/AnyKernel2/commit/034132c91ee11b15f306544e864edb05d2a9f91b

https://github.com/andi34/AnyKernel2/commit/7298ddeb5892f9c7e3fbc46f8b3e26abcf7792f3

I am not sure, but could be the unmount is the issue and it'll be fixed with mentioned commit. Need to test.
[Samsung Galaxy Nexus] Android-Andi:
[MENTION=4544860]osm0sis[/MENTION] any idea how to handle also supporting roms without init.omap4.rc and old pvrsrvkm_sgx540_120 (example: https://github.com/syphyr/android_d...ommon/blob/cm-11.0/rootdir/etc/init.tab2.rc)?

https://github.com/andi34/AnyKernel2/commit/7391e270be4947d1ae0d60f2256b796b6e130af5

insert_line init.espresso.rc "omaplfb.ko" before "insmod /system/lib/modules/pvrsrvkm_sgx540_120.ko" " insmod /system/lib/modules/omaplfb.ko";

Will it be simply ignored if it doesn't find

"insmod /system/lib/modules/pvrsrvkm_sgx540_120.ko"

Inside the init.espresso.rc

?
[Samsung Galaxy Nexus] osm0sis:
Yup. It shouldn't do anything if the match string doesn't exist. That way properly crafted AK2 tweaks are always dirty-flashable with no change to the output ramdisk.

On devices without init.omap4.rc I'd imagine there must be an equivalent file, so I'd just add a little bit of target logic like:

test -e init.omap4.rc && target=init.omap4.rc || target=init.tuna.rc;

or wherever, then just use $target for your tweak filename. :)
[Samsung Galaxy Nexus] Punkiderma:
On your Slim6, this is stuck at google logo!
[Samsung Galaxy Nexus] Android-Andi:
Use the one posted today :)

Edit:

Added ROM check caused issues and didn't flashed needed modules. Rom Check removed until I fixed it.
[Samsung Galaxy Nexus] Android-Andi:
Just as an information, I'll publish new ROMs soon. Please don't flash AnyKernel on top of ROMs compiled on 27.01.2018 and newer!

Our common kernel finally has (WIP) DMA-buffered ION, so we'll use the standard libion instead of TI's old libion.

Because of the switch to the standard libion old kernel won't work on these ROMs!

ROMs still using TI's libion and still compatible with old AnyKernel:

Official LineageOS

Official Unlegacy-Android (builds starting on 15th feburary use the default libion)
[Samsung Galaxy Nexus] osm0sis:
Does that include Lineage?
[Samsung Galaxy Nexus] Android-Andi:
Yeah, I'll compile one too with the changes included.

ROMs still using TI's libion and still compatible with old AnyKernel:

Official LineageOS

Official Unlegacy-Android
[Samsung Galaxy Nexus] rahimali:
I hope I'm not going entirely OT on this...

I'm using a 2014 Vanir KK ROM but getting a bit of artifacting on some (but not all) videos I receive on WhatsApp. Is that CMA related and would flashing an AnyKernel (with or without CMA enabled) have any positive impact? No other issues otherwise, the ROM is rock solid stable, battery life is awesome, everything perfect except for the occasional artifacting...
[Samsung Galaxy Nexus] Android-Andi:
Your DOMX and Camera HAL aren't up to date. You might need to update those too. You can extract them e.g. from my Omni4 build.
[Samsung Galaxy Nexus] runekock:
Some people have found that the Ducati firmware from stock 4.2 works better than the 4.3 firmware that most roms include. See this thread:

https://xdaforums.com/galaxy-nexus/general/how-to-to-solve-hw-video-playback-t2559138
[Samsung Galaxy Nexus] bamtan2:
Yes I believe this could be the 4.3 ducati bug, and I also believe Ziyan switched UA ROM back to the 4.2 ducati recently, so that should help anyone using it!
[Samsung Galaxy Nexus] Kralle_bw:
[MENTION=5153662]Android-Andi[/MENTION]

I've tested your AnyKernel-2018-01-27-13-19-tuna on latest UA 7.1.2 build.

Everything seems to work fine except the camera.

This problem still exists on my maguro for me on all kernels with CMA.

Last no-CMA kernel is AnyKernel-2017-11-11-18-22-tuna-NO-CMA.

So is it possible to provide us also a no-CMA version for new builds?
[Samsung Galaxy Nexus] rahimali:
I tried out the fix in the link and it did fix the problem somewhat i.e., the artifacting has gone away if I use software decoding using MX Player but still present if using hardware decoder (although to be honest I never tried software decoding before applying the patch)

I partially tried the solution posted by [MENTION=5153662]Android-Andi[/MENTION] as follows: I replaced libdomx.so with the one from the latest Omni and while that fixed the artifacting, camera wouldn't work any more...

Then I replaced the three camera files I found: libcamera_client.so, libcamera_metadata.so and libcameraservice.so and ended up with a bootloop. It could be that I have to replace one or two of these rather than all of them to fix the issue or one (or both) of the two files mentioned below:

There are yet two more files that I haven't investigated: camera.omap4.so and libOMX.TI.DUCATI1.VIDEO.CAMERA.so - maybe [MENTION=5153662]Android-Andi[/MENTION] meant one of these when he suggested replacing camera HAL?

Again, apologies for taking this thread OT :angel:
[Samsung Galaxy Nexus] Android-Andi:
Maybe, maybe not. We are testing switching to default libion ATM to get rid of the old ICS TI libion. Old AnyKernel won't work on these builds - camera and domx will be broken. Maybe once the switch is done I can do a no CMA version again.

Please note that the latest build can't be used to take the blobs because it's using a different libion, use one build before latest available.

You'll need the following I think:

camera.omap4.so (replaces camera.tuna.so)

libdomx.so

libOMX_Core.so

libOMX.TI.DUCATI1.VIDEO.H264E.so

libOMX.TI.DUCATI1.VIDEO.H264SVCE.so

libOMX.TI.DUCATI1.VIDEO.VC1E.so

libOMX.TI.DUCATI1.VIDEO.MPEG4E.so

libOMX.TI.DUCATI1.VIDEO.DECODER.so

libOMX.TI.DUCATI1.VIDEO.DECODER.secure.so

libOMX.TI.DUCATI1.VIDEO.CAMERA.so

libOMX.TI.DUCATI1.MISC.SAMPLE.so

libstagefrighthw.so

libI420colorconvert.so

libtiutils.so
[Samsung Galaxy Nexus] Android-Andi:
Attached kernel works on ROMs using the default libion.

Should fix RIL Audio on Toro - please let me know.
[Samsung Galaxy Nexus] musical_chairs:
Yep, it works. Thanks!
[Samsung Galaxy Nexus] Android-Andi:
Thanks for the quick feedback. Merged in all places, will be included in every new build.
[Samsung Galaxy Nexus] contrecon:
Can It run on maguro?
[Samsung Galaxy Nexus] musical_chairs:
Yes, it works on all tunas (provided it is on a build with the default libion). The previous release of this kernel included a change that broke RIL audio on toro, this one fixes it again.
[Samsung Galaxy Nexus] bamtan2:
This new kernel is only for his new ROMs, though!
[Samsung Galaxy Nexus] int0x19:
This kernel works with the latest builds of unified OmniROM 4.4.4 from https://xdaforums.com/galaxy-nexus/development/rom-omnirom-t3655326 ?
[Samsung Galaxy Nexus] contrecon:
I have lineage os with android 6.0.1 anda muy phone is maguro i9250. Can It run It?

I am new un this.
[Samsung Galaxy Nexus] Android-Andi:
Yes but not needed as the lastest build includes all Changes already.
[Samsung Galaxy Nexus] Android-Andi:
Only if you use my build. Official lineage13 build doesn't come with the default libion on builds before 11.02.2018.

You can use one of the older kernel I provided.
[Sprint Samsung Galaxy S6] monroe0328:
Just wanna see if i can start a discussion/information depot as to which new phones we root toot and twrp booting, majisk using, custom rom lovin' and xposed framework abusing SOBs can look forward to... after our s6's vaporize from all the xposed mods were runnin' (some of us at least :p ).

Is it an unlocked s8? Does that even have any dev'ing going on?

How about a nexus 6p? Or maybe the next nexus phone...

If your like me you have only had sammys since the s1... remember the epic 4g with a slide out keyboard, or ill do ya one better, the moment? Is keyboard button mapping Emulator heaven worth the downgrade? LOL

Or are we gonna just keep our s6s forever?

Life is tough and ever since these locked bootloaders on our beloved flagships, its not fair either.

What are we gonna do? What have you guys heard/learned about the competition?

Yes i could do all the research myself, or we can have a fun discussion about it and save us all a few google searches!

:)
[Sprint Samsung Galaxy S6] spammy l:
I think it's the s8 for me...

I think it's the s8 for me.

I'm super disappointed the the Snapdragon version (US Version) of the galaxy s8 is apparently unable to be rooted by either a SuperSU method or a Magisk method (or any other method)- and I will have to find a way to live without Titanium Backup, Xposed, PMP, etc etc etc.

That said- it appears that "Package Disabler Pro" https://xdaforums.com/galaxy-s8/help/package-disabler-pro-safe-to-disable-t3593305 will at least give me some granular control back, especially as I fight to minimize the spam and bloatware.

I think I'll have to combine that with whatever non-root methods I can to piece together some sanity.

Too bad, but the battery on my S6 has started to drift badly with age, and I think it is just time to move on. :rolleyes::(

Good news I suppose is that it is waterproof. Always irked me a bit that s5, s7, and s8... but NOT s6 were...