yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@ up .. alright ! Yeah the 10.01 build is almost stable too, but not fully stable. I had noticed that it just takes more time to trigger memory corruption. That's why it's still stable for you. Btw could us show what you change in default.prop ?

Be carefully with ramdisk changes as it can harm overall user experience.

Even if you just mess it up with file permissions, which is likely the case if you use Windows.

@Driieel - Thanks ! But you guys are also amazing people !

Without hard testing it's not possible to make a really good kernel.

So far i couldn't face any issues, let us hope memory management issues (apps FC & random reboots) are now fixed in latest build. Didn't test it much and just uploaded so that you guys can test as well. But in theory it should be fixed now. If some of you is curious to see what i've changed in latest build, see this commit.

It was an upstream patch that Samsung just merged with the DTA6 stock ROM. It's long time ago .... i never suspected this and i was searching the issue elsewhere. Anyway, according to dmesg it seems that this latest patch causes "null".

So i've just reverted it.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Alright i just changed this in default.prop, the overal app performance is slightly faster when they are compiled/optimized with dexopt set to speed. Only thing when wiping dalvik it takes longer to optimize the apps but i dont mind lol. It doesnt seem it does take more ram when using apps when they are optimized with the new variables🤷‍♂️

Well im glad to help out lol, we maked so much progress in a short time with testing and fixing stuff😄 hope its finally stable😛
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
OK, that's great, but it uses Max space on flash memory. With speed-profile you get the same speed after 4 - 5 days like "speed" taking less space.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Hmm yes, but i dont like to wait 4-5 days to its automaticly optimized and meanwhile that my phone runs sluggish, thats why i choosed speed instead speed-profile, even i have to loose some storage space😅 anyway it sucks for making nandroid backups in recovery so i have to buy a larger sd or have to connect a flashdrive or whatever for in that case😛
[Samsung Galaxy S8 & S8+ Cross Device Development] pranil60:
hard reboot.. 3rd within 24 hrs
[Samsung Galaxy S8 & S8+ Cross Device Development] pranil60:
well i was late
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Got also a hard reboot right after i flashed the pre kernel, its a few hours ago and not sure if it is caused by kernel issues or something else, anyway still gonna post it.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
In the pre-kernel the battery is lasting longer, even with the safe overclock, it's also not getting as hot as before. No reboot yet.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
New bug ... it's coming from zRam driver.

I'll sync zRam driver from Android kernel 4.4.194.

Then it should finally work stable. It'll also work faster.

Already taked a look in source code, looks promising.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Where you got the idea to change build.prop ? And can you give the build.prop file i want try your build.prop and last question are you use stock rom ? Any modify ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Its not rlly a build.prop, its a default.prop, also its located in the boot partition where also magisk and the kernel are. You can only modify that file if you push the boot.img file from your phone to your computer and unpack it & edit the default.prop and repack the file again and flash it back to your phone. Also there is easier way to do it, i unpack the a2n kernel flashable zips and use the boot.img file from that and unpack it & edit the default prop and repack the boot.img and flashable zip. Voila a modified a2n kernel with a modified default.prop file inside😊 only thing when after you flash it and wipe dalvik is thay it uses more space and maybe what ace said it uses more ram but i dont see rlly the difference🤷‍♂️ but also the first boot optimalisation process is longer, in my case it is like 20-30 mins before its done.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I've a better idea, you can add those flags for dalvik optimizations to build.prop if they are missing, then it's easier to change them. No need to edit default.prop.

The flags from build.prop will override the ones from default.prop.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Hmm didnt know that kinda easier indeed, but i have then also to copy the build.prop to the internal storage & edit it & copy it back to /system (if im right) and test it.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes or just edit with any root file manager. In every case after edit make sure permissions are right.

It should be root root rw r r.

Reboot to apply new build.prop.

If it doesn't boot, just flash the ROM again then kernel and so on. (Noob way)

But the proper way is to keep calm reboot to twrp, connet phone with PC and use adb:

Mount /system in twrp..

On PC:

adb shell

nano system/build.prop

Edit, save, reboot to system, done.

@Ryujin96

Or another way ....

In twrp + adb

adb pull system/build.prop

Edit ...

adb push build.prop /system

adb shell

cd system

chown 0:0 build.prop

chmod 644 build.prop
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
Hey. For now, in the pre-kernel there were only standby reboots, nothing else.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
The fight against random reboots continues !

So i've uploaded pre-build V. 13.01.

Changelog:

Backported zRam driver incl. zsmalloc and LZ4 lib from Android kernel 4.9.194.

If it still doesn't work stable, i'll go to mars lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
Não nos deixe assim 😂.

Vou começar a testar agora.

Edit: Or maybe not, where's the link? 😂
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
On the same place. Check FTP server.

Pre-release folder.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
Is it really necessary to clear cache and dalvik? the cell phone is slow 😅. there was a soft reboot in pre build v2, I didn't delete the cache/dalvik when I switched.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Only mandatory if i write it, otherwise no wipes required. How to reproduce the soft reboot ? For me still no issues.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I wipe always dalvik/cache after flashing something just be sure there is not issues. Anyway i putted the pm.dexopt variables in build.prop, lets see hows that gonna work out😄 anyway gonna now flash the new pre kernel.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer are you sure if i put something in build.prop from default.prop it overrides it? Becus the optimalisation processes looks kinda fast compared to normally with a patched boot.img with a editted default.prop in it and wipe the dalvik its like a 15-20 min before its done, doesnt seem like its do something with those variables😅🤷‍♂️
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I wiped art cache too for latest build, because i had one app fc (YouTube vanced) ... but it happened after Google Play updated. And this time even with speed-profile the phone is fast. But i let it on charger during apps optimizations and then rebooted the phone after little cpu goes to 598 MHz. Then again wait till little cpu goes to idle.

That's the trick. Takes around 7 minutes uptime. Then it's fast. Because dex optimization is active while it's on cable. In my case connected to my notebook USB 2.0. 500 mA.

As for build.prop:

I didn't test it, but i think build.prop should override default.prop because build.prop is loaded after default.prop. Or default.prop forces everything ?!
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Alright, i guess default.prop forces everything seems like it, anyway im go back to my method to just edit default prop again etc, not rlly easier but yea only way it worked out so far, anyway glad i tested it out if putting in build.prop it does something or not lol😄
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Sure, but try my method ... it works as well. 😃

Build.prop works too, but not if it's already defined in default.prop.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Thats true, if its not defined in default.prop then should theoraticly build.prop take it over. Anyway i tried again the exynos-m2 instead of m1 in buildprop and checked after reboot if it returns a error or something and it doesnt, so its then used and compatible?
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
The apps also started to stop. I'm going to clear cache/dalvik, after I did that in the previous build, I had no problems. Disregard the soft reset I got. I will restart the tests again with cache/dalvik clean
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Then it seems wipe dalvik cache is required for latest build, because after wiping cache i'm facing no issues.

As for exynos-m2 flag, you need to check logcat after you boot with new build.prop.

If unsure post the logcat, i'll check for you.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
I would appreciate it if you could check for me.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
same for me😅
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer i dont know what happend but my phone got a hard froze, didnt get the screen turn on anymore for some reason so had to force restart it.
[Samsung Galaxy S8 & S8+ Cross Device Development] XDA.Samsung:
G950W please
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Just like Ace said. The S8's chassis cannot even dissipate 2314MHz without going over 95°C and throttling in intensive multi core workloads. Maybe S8+ can do that. So I tried running Geekbench 5 on stock and with a conservative 2496MHz on Mongoose and 1898MHz on Little cores to see if I could reach even higher scores thanks to the lower throttling. The cooling system is very bad. I also ran 2652MHz just to see how badly throttling affected the score or if the extra performance managed to show up before the 95°C mark, hence yielding better performance and maintaining the idea that higher clockspeed = better performance even on bad cooling as long as we can stay at normal idle temperatures.

NW: I need charger assistance for 2652MHz. The battery can't keep up with the voltage requirement on its own at low temps (low temps = lower battery voltage -> instabilities).

Ace's work is still amazing though because at stock speeds we get scores much higher than the average 1400-1500 on stock Kernel, and therefore, significantly better performance.

Stock (2314MHz M2 and 1690MHz A53)

I got up to 395 and 1733 in this config. With my external cooling that is. The improvement was small, so I assume that the external cooling manages to make the 2314MHz frequency actually unable to throttle at all.

2496MHz M2 + 1898MHz A53.

The Single Core score improved much more than the multi core. There is clearly some degree of throttling. It's small, but it's there. This frequency is probably the soft spot if one wants an overclock but decent temperatures in games.

2652MHz M2 + 1898MHz A53

Here the throttling gets really bad. According to my calculations, in the worst case scenario this clockspeed would've gotten 1850 in multi core, without throttling. But exceeding 95°C probably brought some aggressive fall in the frequency. It's visible that the single core improved even more since one M2 does not produce enough heat to throttle the device. The multi core is basically the same as 2496MHz. I managed to reach 1800 on 2574MHz. It throttles too but it's the frequency that gives me the most performance before throttling. A friend of mine managed to score above 1810 with 2652MHz on his S8+ and a fridge. And it still throttled.

From stock Kernel, in any case, the improvement is insane. And it's best the OC options are kept because they give a nice performance boost in games, where the CPU isn't as stressed as a benchmark.

It'd be amazing if Ace started working on Exynos 9810 powered devices once development on G950F is complete. N960F seems to have the most potential and a great cooling system that keeps the stock frequencies at decent temperatures and allows overclocking realistically. It would be amazing to see how much he could push that SoC, since it has a lot of potential that Samsung restricted.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
In your studies, what would be the best frequency to overlock in games?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
To be honest, after I noticed that 2314MHz CPU tends to 95°C+ on stress test loads, and after I discovered that it still can manage 1700+ on Geekbench 5, I'd say that 2314MHz is a good choice for moderate gaming sessions on G950F. If the environment allows it, 2496-2574MHz are great too. G955F can more comfortably maintain those frequencies. I don't recommend 2652MHz.

You also have to take into account GPU. Even at 546MHz, it runs pretty hot on stress tests (76-81°C). 572 is a little hotter.

So It'd go like this as far as G950F goes:

Endurance (Hours of gaming)

2002MHz big (Highest Freq that does not Overheat)

1690MHz little

455MHz GPU

Moderate

2314-2496MHz big

1898MHz little if possible. If not, 1794MHz

546MHz GPU

Short sessions or optimal ambient temps:

2574MHz big

1898 Little

572MHz GPU

Light games

1807MHz big

1690MHz little

385MHz GPU
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
Thank you for sharing your research with us!

So if we overclock to the maximum would we be losing performance due to overheating?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Maximum? 2808MHz? Careful not to lose your phone there :eek:

Seriously now. Yes. You'll lose performance, if you can even reach 2704-2808MHz at all. The former is rare and the latter I yet have to see stable on an S8. Exynos 8895 had pretty bad yields, especially on GPU (Silicon quality).

A sustained 2GHz is better than a 2.8GHz that drops to 1.5 after 10 seconds. The frequency switches can also cause stuttering in games, no matter how fast it happens.

Besides with this Kernel and no change on frequencies at all, performance still far surpasses stock Kernel. It takes almost all of 8895's potential out. You'll have a great esperience regardless of frequency settings. This Kernel is one of a kind. I'd argue it's the best Kernel ever developed by a third party for a mobile device. I wish other devices had devs as skilled and dedicated as Ace. We'd be living in 3022 if that was the case

:LOL:

I really really admire our developer. He ain't only the Nutzer of the Galaxy Ace. He is also the Ace in the hole of mobile development. My wallet is at hand If this legend makes something new in the future.
[Samsung Galaxy S8 & S8+ Cross Device Development] huanngo3011:
Any plans for Q ?

Thanks in advanced!
[Samsung Galaxy S8 & S8+ Cross Device Development] PC Exploring:
Hi, im not much aware what rom and kernel works together but im trying things so need some help here.

I have Samsung S8 running Renovate Ice Rom 15. I tried to install this kernel by entering twrp flashing the zip and rebooting but it got stuck on samsung logo. Am i doing somwthing wrong or this kernel wont work with Renovate?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@TechNoobForSale

Many thanks for your compliments.

You decoded my username correctly.

I was just a user of Galaxy Ace 2 phone. Then later i started development on Ace 2 and later on S8. Didn't even learned any programming language at the school.

But still managed somehow to make some things better than Samsung and Google developers. Don't know how is that possible, but it works. I know actually this kernel may be not fully stable and therefore worse than stock kernel, but i think it's just a little bug that is causing this.

I don't know what i'll develop in future, but for now i want to stay on S8. Once this kernel is stable i want to start building AOSP for S8.

Note 8 support will come too.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Once the little instabilities left are solved, this Kernel will just be better than stock on anything (tbh I didn't experience a single random reboot for a long time now). One person being able to do things better than whole companies.

That is a big flex bro lmao
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
This Kernel doesn't work on ROMs that aren't One UI 1.0 based as far as I'm aware
[Samsung Galaxy S8 & S8+ Cross Device Development] PC Exploring:
Okay, so Renovate Ice Rom might not be One UI 1.0. Thank you for help
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Only for Android 9 for now.
[Samsung Galaxy S8 & S8+ Cross Device Development] PC Exploring:
Oh okay got it. Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
For latest build: 13.01, yes.

Which ROM are you using ?

It looks like it's ROM bug, maybe something like that ?

Only works if you set exynos-m2 flag, reboot to twrp and wipe dalvik-cache, then finally after Android is booted up, grab logcat.

Then post the log, i'll check.

In the log you have posted there is no error about exynos-m2, so if you did everything right, then it's supported.

Which ROM are you using ?

It looks like it's ROM bug, maybe something like that ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
I'm using the EclipseStock ROM. Apps are not stopping after I cleared dalvik and cache. I had the same freeze as @Ryujin96, I had to force restart too.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Hmm weird, well im using latest devbase rom still but didnt get that anymore so yea guess its a onetime thing what happend🤷‍♂️ about the exynos-m2 flag im kinda suprised it didnt throw errors becus i use a close to stock samsung rom and like you said a while back its unsupported on samsung roms😅
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
OK, then the kernel is so far stable.

After wiping dalvik cache i'm facing also no apps FC.

Anyway, in your logs (logcat) there are errors about CONSCRYPT.

It's a ROM or user app bug. Unfortunately i can't say exactly what the problem is. it's also possible that it's coming from bugged gapps package you guys flashed.

Because so far i'd never ever faced that CONSCRYPT error in logcat using stock ROM.

Therefore if you face again a soft reboot, i suggest to switch to stock ROM with A2N kernel, if you want a stable phone.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Alright, isnt conscrypt a module of play protect? If it is then i know then why there are errors then i disabled it in playstore becus i got those annoying notifications about a malicious app🤷‍♂️anyway not flashed gapps so thats not the problem here😅
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I didn't search a lot for what conscrypt is required.

But yeah, it's possible what you say. In my case i keep that annoying play protect always disabled in order to save battery, due to frequently useless scanning of apps. I know which apps i do install, so no need to waste battery in useless scanning hehe. Well then try to fix that conscrypt errors. I think this is really the real reason for the soft reboots.

If you find out it's coming from gapps package, i can provide stock Google Play and stock Google Play Services if it helps to fix the issue since they work properly for me.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I dont rlly have a clue where else it comes from lol, maybe i have a broken rom on my phone becus i bricked my phone with trying stuff and restored system and data from backup afterwards, dont know if that causes conscrypt errors, but else i dont have a idea🤷‍♂️
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@Driieel same for you, since you have the same errors in logcat !

According to the log you had posted there ... there are a lot of CONSCRYPT errors.

just grep for CONSCRYPT like this:

cat logcat | grep CONSCRYPT
//or directly from phone:
su
logcat | grep CONSCRYPT

I think system_server just gives up and it forces a soft reset aka soft reboot.

As it turned out it's coming from Google Play Services package.

But there is also a jar file in:

/system/framework/conscrypt.jar

This bug probably happens if you use a ROM with outdated gapps or outdated conscrypt.jar file. You should report it to your ROM developer. Or if the ROM is EOL or just abandoned, then you can try to fix it yourself if you don't want to switch to stock ROM.

I think it should be quite easy to fix it.

For instance first do what i wrote, check actual CONSCRYPT errors in logcat. After that, start do modify the system by simply replacing conscrypt.jar file taken from stock ROM. (attached here).

Then reboot the phone, and run again on phone:

logcat | grep CONSCRYPT

this will track errors live while you use the phone ... open many apps ... especially Google Play and some apps that depends on Google Play Services. In order to trigger conscrypt.jar usage.

If you don't see any errors anymore, then it's now fixed !

Let me know, if it works, i can implement that fix directly in kernel installer lol.

Permission for conscrypt.jar is root root 644 or rw r r.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
@ace2nutzer I realized that there was something buggy in the play services apps. Yesterday I went to install an application and the Playstore just crashed, the system was normal, but the play store was only in the image of startup. If conscrypt is the problem, could you help me fix it? I know very little about Kernel development or etc.

Had to force restart for Play store to work again.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@Driieel

check what i've posted, it's not difficult.

For running logcat command on the phone you just need "terminal emulator" app. type first "su" then the logcat command.

And for replacing the conscrypt.jar file you just need any "root filemanger" app. See post #3365 what you need to do.

If it doesn't help, we can try to replace Google Play Services with the stock one.

Edit: maybe Play Store or Play Services was updating in that moment, then it's normal that some apps just crashes while trying to use Google Play or Play Services !
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
According to logcat reader it throws still errors, checked with that becus im not sure which are errors when i checked it on termux, anyway i post a log incase it says something else now.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes.. still the same .... hmm.

I've attached another file to replace.

Unpack it, and replace it with:

/data/app/com.mgoogle.android.gms-*/lib/arm64/libconscrypt_gmscore_jni.so

or if there is nothing, try arm folder:

/data/app/com.mgoogle.android.gms-*/lib/arm/libconscrypt_gmscore_jni.so

If there is also no file, then search it elsewhere, but don't put it there if there is nothing. Only replace it.

Then reboot and check logcat.

Anyway, it's like always a good practice to backup first the original file, for just in case it works worse than before !
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Still not fixed. I dont have a idea what else it can be🤷‍♂️
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
@ace2nutzer I'm returning the stock rom with A2N to see if it resolves these issues.
[Samsung Galaxy S8 & S8+ Cross Device Development] Driieel:
@ace2nutzer what to do to not show "your phone is security encrypted"? I forgot that part. xD