yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
@ace2nutzer why did you remove the 2574MHz from the Big cores frequency table? The abrupt drop from 2652 to 2496 due to throttling in benchmarks kills scores. I recently got a new Geekbench 4 highscore at 2214 single and 7556 multi at 2652MHz, but I believe that if the phone resorted to 2574MHz, it could cross 7600. This thing gets up to 100°C fast when OC'ed and therefore to maintain max performance you gotta make sure frequencies are lowered as little as possible while remaining under the limit.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Removed cause to close clock the must be deletes because 2496 is close to 2.5 ghz and 2.6 is sweet spot i think
[Samsung Galaxy S8 & S8+ Cross Device Development] adrimixfire:
I can't get my own voltage table, can you help me?

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

adb server version (41) doesn't match this client (39); killing...

* daemon started successfully

su

cd /sys/power

echo 1 > print_dvfs_tabledreamlte:/ $ su

dreamlte:/ # echo 1 > print_dvfs_table

/system/bin/sh: can't create print_dvfs_table: Read-only file system

1|dreamlte:/ #

Kernel reports 90% battery health and 280 cycles for s8 dreamlte, it's almost new.

I have bought the app and it seems to me the most complete kernel I have tried on any phone

Thanks you
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@adrimixfire

after the print cmd, use "dmesg" cmd to see current voltage table.

To reduce freq switching related lags and performance loss.

There was just too much useless freq steps that was too close.

2500 & 2575 MHz is nearly the same.

I don't think so, since everything > 2000 MHz can't be sustained for long time.

No, it's great how it's right now.

If you don't like it, download source code and re-add the freq steps you want. Just search for the related commit(s) and revert them.

Edit2: @adrimixfire

I've uploaded a patched stock kernel for testing Netflix in L1 (HD).

Let us know if it works in HD.
[Samsung Galaxy S8 & S8+ Cross Device Development] adrimixfire:
I want to try it, but currently only my s8 g950f is rooted, could you add it? *
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I've uploaded the stock kernel for all supported models. Here for S8. Just flash it over a2n kernel. You can also fash magisk, but it's not required for testing Netflix. No need to wipe anything. When you are done, just flash latest a2n kernel and then magisk for root access.

As already mentioned, you need Samsung ROM with working TWRP.
[Samsung Galaxy S8 & S8+ Cross Device Development] adrimixfire:
Stock kernel works with L1 and netflix in HD even with Dual Speaker Mods installed, i like it.

unfortunately for my s8 with A2n it is very hot and performs less in 3dmark score, undervolt improves that but it is not enough
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
R56 is upppp?

@ace2nutzer hasn't uploaded it tho :(
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I could make a flashable zip but Im not rlly in a position rn to do anything, im still sick becus a stupid flu since previous saturday and besides i dont think ace likes it if i release builds without his permission. Anyway so far i saw there were some nice commits this week😛
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
indeed, the commit lists many memory management changes, looking forward to test this out.

no worries, official build should always be released and announced by the author anyway. maybe ace is still debugging if it's stable or not
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
R56 works stable so far.

App V56 is also done. (Will upload later)

But I wonder why Netflix works fine with HD with the patched stock kernel from me, even the fact that many things are the same:

Bootloader unlocked

Magisk installed ...

And even without to pass safetynet, DRM L1 works properly.

The only difference maybe due to SELinux enforced or some other stuff like knox and tima. I'll try if I can bring L1 back on a2n kernel, after that i'll release R56.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer i can comfirm my commit about moro sound is working, just tested it with mtweaks. also i reforked ur repo becus i dont want to have that hassle rn to manually revert everything lol just started from scratch. not a huge deal besides the kvm stuff but yea i repatch it again. :P
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
hmm its weird indeed, thought a while back i readed a mention about something with missing knox what causes it and knox is a security part after all so its logic widevine uses something from it.
[Samsung Galaxy S8 & S8+ Cross Device Development] adrimixfire:
I did not have magisk installed in the netflix tests, I carried out the tests with Dsam mod installed with twrp. I'm sorry I explained myself wrong, I'll try installing magisk.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@ up

don't post such long logs without proper formatting as to not spam the thread. Please edit your post.

Use [ HIDE][ CODE]put your code here ...[/CODE][/HIDE ]

remove the space from HIDE ...
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
alright thanks, will do that.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
How I should check what you did wrong if you don't push your local changes to git?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Just move

#ifdef CONFIG_KVM
#error "RKP and KVM cannot coexist!"
#endif

below

(L 482) #ifdef CONFIG_RKP_KDP
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Okay thanks. there were more errors in the building process complaining about wrong positions or something i remember.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
OK, check your latest commit, I've commented which line you should remove.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Alright, so (L 482) #ifdef CONFIG_RKP_KDP and (L 733) void, needs to be removed to fix the compile issues, okay will do hopefully😄 thanks! Its so confusing sometimes lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Nope, read again my post 5613 ... "move" not remove.

And the other error, remove "void preinit_hyp_mode(void);" (L733).
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I mean move yes, and okay😛
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Did it compile boot.img without any errors now?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Didnt try yet😅 i'll let you know
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@ up

No need to post everytime the whole output... the first error is enough.

Always fix the first error ... often are subsequent errors the cause of the first error. I'll tell you in github how to fix. So far you had only very easy errors to fix. But for beginners it seems hard to fix.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
okay, yea its hard becus its not a thing i understand to fix errors in program language lol
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
This is enough:

init/main.c: In function ‘start_kernel’:
init/main.c:733:5: error: implicit declaration of function ‘preinit_hyp_mode’; did you mean ‘print_ip_sym’? [-Werror=implicit-function-declaration]
preinit_hyp_mode();
^~~~~~~~~~~~~~~~
print_ip_sym

Fix:

add in L107 in init/main:

extern void preinit_hyp_mode(void);

btw: i'll help you to fix all errors for this patch.

For further patches I'll not help because I don't have much time, but you can learn basic know-how for the C language and you can search the web how to fix such errors. For instance, stackoverflow is very well for this, you can learn a lot from there.

OK, fix this and run again ./build.sh.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Alright, so i have to readd the line i deleted and add "extern" before it? (Without the quotes ofcourse)
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes, but in the right place.

A good place is always below the include stuff at the beginning of every source file, of if you like, it can be added also above (and outside) the function. But if you want to call this function above the "extern void...) then you may get again error about "-Werror=implicit-function-declaration".
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Okay thanks again, and thats a good tip to make a note about somewhere😄 like much things u said i noted somewhere to reread if i forget or something.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Good idea my friend!

btw: check my previous post, I've added more info.

In addition, it's not always that easy... sometimes it'll fix the error but in the end when LD vmlinux is linking all symbols, you may get error that the function points to no real function. In this case it means that the function in nowhere declared, hence it's missing and you need to search in Linux Kernel archives or in AOSP Android kernel source and add it to your source.

For instance some useful links:

The Linux Kernel (all versions)

AOSP Android Kernel (all versions)

edit: @Ryujin96

but in your case, it's not missing, but declared in another source file: here.

And as you can see, the function is not declared "static" because we want to use it global in the whole kernel. Otherwise if it's "static" you can use it only in the same source file where the function in declared.

It's also possible that you need to use some static function in another source file, in that case just remove "static" and outside in another file where you want to call this function, add at the beginning extern void ... or what so ever it's. You will see that almost many errors will be the same and later you can fix them very quick and easily.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I see, so long somewhere is a particular function declared i can call it in with eg "extern" etc? If not i can either remove it or look in the linux / android sources if it is declared somewhere and if it is i have to backport some things? Will be fun then😅
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes.

Nope, if you remove you may get further errors and moreover the driver will not work properly then.

Sometimes it's just enough to copy paste the whole function.

But sometimes it's not enough, ... missing dependencies etc .. then you need to cherry-pick the needed commits.

Also this is not a backport, I would call it fixing the source code.

A backport is if you e.g. want to add or update the zRam driver and you use the zRam driver from a newer Linux kernel and you backport it to an older kernel. This is something that I already did in this kernel... especially with memory management. But this is really difficult for beginners, because you can face many difficult errors to fix. Most of the time what makes it appear so difficult is the thing that in newer kernel version many functions / symbols are renamed or they have modified structure what to pass to the function. Because you need to rename them "back" to the old style as to make it compatible with the older kernel. That's why it's called "backport" But as long as you add patches that are coming from the same Linux kernel version, then you should get only a few easy to fix compile errors, like it's now the case for the KVM patch. ;)
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
New Kernel & App for your S8/S8+

Changelog

A2N Kernel R56

Updated wireguard to the latest version

CPU DVFS: removed hardcoded voltages for stock Freqs (since it's painful)

CPU: re-added Samsung patch for app launch boost (all cores at max Freq while opening an app)

CPU: fixed big CPU hotplug feature

A2N: removed kernel settings lock caused by 3rd-party apps or (wrongly applied) user init.d scripts

Memory management: sync with Android kernel 4.4.194 + some other optimizations

LMK: updated driver

CPU/GPU: reduced device heat (since it's painful for the battery)

A2N Kernel Control V56

CPU: disabled CPU input booster by default

CPU/GPU: disabled CPU boost by default

Audio: set PM-QOS-BIG to 741 MHz (if you face audio issue, increase it)

CPU/GPU: removed voltage control for stock Freqs (still possible over shell script)

CPU: fixed CPU boost and up_threshold doesn't able to change after using CPU hotplug feature

CPU/GPU: set DVFS temp to 60 °C

Fxed other minor bugs

Debug menu: added DRM L1/L3 patch (only in demo version available or Google will kill me!!!) :LOL:

Note: patched SafetyNet out of the box. (No matter if Magisk is installed or not).

You can use now latest Magisk version without any issues!
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer how do i fix this error?

LINK vmlinux
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
FATAL: modpost: Section mismatches detected.
Set CONFIG_SECTION_MISMATCH_WARN_ONLY=y to allow them.
make[1]: *** [scripts/Makefile.modpost:97: vmlinux.o] Error 1
make: *** [Makefile:1049: vmlinux] Error 2
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
The things I’m doing to make this phone not throttle
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
whole frankestein build :ROFLMAO:
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Is it not self explained?

Enable CONFIG_DEBUG_SECTION_MISMATCH.

Then rebuild from scratch. (clean.sh and build.sh)
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I'll try to run AnTuTu V7 and get 250,000. Frequencies I'll use are 2652MHz for big, 2002MHz for little and 764MHz for GPU. 2496MHz big, 1898MHz little and 683MHz GPU achieve about 240,600. Not bad. 250,000 definitely possible, and if run is flawless, I'll try GPU at 839MHz, even though it will most definitely throttle a bit then.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
which file do i have to edit for enabling it? defconfigs?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes the one for your phone. For S8 g950x it's g950x_defconfig.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
btw question, can i ignore those errors about not finding stuff?

cp: cannot stat 'fs/cifs/cifs.ko': No such file or directory
cp: cannot stat 'fs/nfs_common/grace.ko': No such file or directory
cp: cannot stat 'fs/nfs/nfs.ko': No such file or directory
cp: cannot stat 'fs/nfs/nfsv2.ko': No such file or directory
cp: cannot stat 'fs/nfs/nfsv3.ko': No such file or directory
cp: cannot stat 'fs/nfs/nfsv4.ko': No such file or directory
cp: cannot stat 'fs/lockd/lockd.ko': No such file or directory
cp: cannot stat 'net/sunrpc/sunrpc.ko': No such file or directory
cp: cannot stat 'net/sunrpc/auth_gss/auth_rpcgss.ko': No such file or directory
cp: cannot stat 'lib/oid_registry.ko': No such file or directory
cp: cannot stat 'net/ipv4/udp_tunnel.ko': No such file or directory
cp: cannot stat 'net/ipv6/ip6_udp_tunnel.ko': No such file or directory
cp: cannot stat 'net/wireguard/wireguard.ko': No such file or directory
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
im impressed about your scores with this phone😮
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You get this because you have disabled those drivers .... if it sucks just remove these lines from your build.sh script.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
alright, it was more if it were caused by building issues and not finding files related to that. but now i know they are not find errors becus i disabled drivers i dont worry about it then.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer well guess the kvm patch didnt work for the g950x device, it boots but it didnt make a /dev/kvm still, guess we'll have to wait till someone port it to a exynos 8895 platform. till then i revert my patching and try something else.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Did you fix the mismatch error properly? What was the error and how did you fix it?

As for /dev/kvm device missing:

it's possible that you need to add it yourself by a shell script. Search the web for this... or the kvm app or what so ever will add it automatically.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I almost got to 250,000 with 2.65 big and 2 little as well as 764MHz gpu. Problem is I was totally unable to reliably run 839MHz past the second benchmark for GPU. This makes my life a LOT harder to cross 250,000. I'll try with 2.7GHz CPU, which should boost UX score and HOPEFULLY not impact CPU score a lot. Which in turn should get me to barely 250,000. Shame that 839MHz refuses to work. I don't know why. I probably need to run it while phone is charging and not at 100% (Charge idle). It doesn't receive enough power. 839MHz is very power hungry.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I didnt, but i start from scratch again, i saw there was an edk.patch aswell by an other author and some pmu backports i have to do aswell. I know the other errors i solved with "#define" before the function somehwhere in the file and didnt show up afterwards but the last i got was one causing a mismatch somehow and have too look into that when im ahead again with patching. It would be a lot smoother too becus i know now a bit to solve those errors.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Hmm I doubt that you did it right.

Try again from scratch an push just 2 commits.

1. Add kvm patch.

2. Fix build errors.

Then Ill check if everything is right.

Because you can fix build errors even if your code is conpletely BS. The compiler doesn't have an KI lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I actually managed it. If only 839MHz was reliable...GPU Score would be 110,000+
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Someone can test if Netflix works in HD on this latest release?

If not, try to add the L1 patch from the a2n demo app.
[Samsung Galaxy S8 & S8+ Cross Device Development] leonidasZ953:
I try add L1 and not working..Reinstall Netflix and its same results..
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Try this:

Patch to L3 ..

Open Netflix app ...

Should be only SD now ...

Patch to L1 ...

Open Netflix ..

Should work in HD.

It's not needed to re-install Netflix.
[Samsung Galaxy S8 & S8+ Cross Device Development] adrimixfire:
I'm sorry, it may not work well when I tried it with stock.

I'm trying now and it's impossible to finish a chapter on netflix with l1
[Samsung Galaxy S8 & S8+ Cross Device Development] leonidasZ953:
I try this 2 times and still same..
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
what sorcery is this?

it's now detecting as L1 !!! it used to show L3 on the green marked fingerprint

what i did to get this to work :

1. patch L1 from demo app

2. check status from netflix, didn't work, still shows L3

3. reboot

4. check netflix again, didn't work

5. force stop netflix, clear data (everything)

6. open netflix again, relogin, check status and now it's L1
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
And now test if you can stream in HD for at least 20 minutes. If yes, then it works.
[Samsung Galaxy S8 & S8+ Cross Device Development] heukpyo:
Why did you remove the voltage settings of cpu 2314mhz and gpu 572mhz from the app settings?
[Samsung Galaxy S8 & S8+ Cross Device Development] leonidasZ953:
I try this and worked 😁🤩 Thank you..!!
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Because it's not the proper way to do so. Every phone has different voltage table. A2N API is outdated and only works with hardcoded values.

That means the voltage that we was using was taken from my phone. On some of you it might be higher than stock, causing more heat and higher battery usage for no reason and on some other phones this was way too low, making the phone unstable by default and therefore I've decided to remove it.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
yep it works .. BUT, i see some "watched/ongoing" movies/titles are having problem loading, minor issue that i will look for workaround later today
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Sounds great and now that it works what happens if you apply again the L1 patch? Will it stay on L1 or will it switch to L3 in Netflix app?

Then I can improve the patch.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
the question is how did you patch it?

did it patch the crypto lib?

or did you replace it?

honestly i'm kind of leaning towards you're practicing sorcery 😂

edit: if you're patching it, i learned something or two way back years ago .. if you're interested i can send you my script

edit2: on second thought you could just see one of my thread for the script
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I'm not sure, needs more testing.

But what I can tell you, the patch just restore the liboemcrypto.so from *.bak ...it's just the original lib.

Plus one more thing, but i'm not sure if this is the real "hack"... but at least it fixes DRM error in logcat... so I think maybe that works. Try to add L1 patch... if it still works, then it's ok. Otherwise i've one more idea to make it working with just one tap ... so without to reinstall the app.

But better to not talk too much, otherwise they will patch it back and you guys will have again only L3 on all rooted devices.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
i backuped the lib, then pressed the patch L1 again, it says done, refreshed the root browser and it's still there.. as if nothing happened or the demo app didn't handle that exception if renaming fails..

got curious and pressed the L3, refreshed the root browser, it's renamed to bak

pressed the L1 again and got it renamed again..

so i think we're good here.. thanks ace

edit: i think i know what you're thinking.. lsmod it?
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
wait.. i think i posted too soon, i forgot to check the netflix app..

right after i test those steps above (back to L1), i opened netflix and it says device error, forgot to screenshot it coz i instinctly rebooted

then after booting and opening netflix, i was asked to login again and turns out L3 was on the fingerprint again..

i force stopping it then clearing the data, opening netflix again and login.. L1 is active again :D
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
aaand i think i posted too soon again, this time while playing netflix less than a minute a popup appears "error 5.7.6"..

this morning i tested out watching "red notice" until it's done with L1 mode active.. i don't know if i did something very wrong or i did something very right :/

edit: i think i'll just leave it at L3, my eyes doesn't care for the details that much, especially not on an S8 screen
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Do this:

Logout from Netflix..

Close the app...

Apply L1 patch...

And test if you can watch in HD.

No need to reboot, also no need to force stop... the patch already do this for you.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
i did what you suggested, but after logging in again the device fingerprint still has L3 on it, and playback specifications says L3.. no dice man

edit: i cleared its data and it detects L1 again, but playing a video i watched just stucks on loading.. workaround for it is to remove it from watched list and reopening the movie again, then it loads.. but, after 2 minutes error 5.7.6 pops up back and closes the video i'm watching
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Okay thanks for testing.

I'll provide one or two different patches for testing. Anyway don't wipe data.
[Samsung Galaxy S8 & S8+ Cross Device Development] archeiii:
How do I downgrade to R55? Since updating to R56, it's like CPU and GPU boost is always disabled despite enabling boost in the settings.