yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
3300mV, the minimum, of course. I'm still obsessed with performance. Can't have it throttling every now and then! So if the threshold is that low and still didn't cause a crash, I'm guessing the mechanism is doing its job well

Have you seen how quiet the thread is, lately? I think that it's because people aren't experiencing crashes and stuff anymore. Maybe you finally realized your ambition of creating a 100% stable Kernel. This algorithm surely did help, in my opinion. Now I can finally savor CPU miscalculations again (screen freeze, home sweet home) and not battery fail anymore :LOL:

I have a question though, might be silly. On your Github, is it possible to use this Battery Throttling commit (giving credits, of course) to make this algorithm function on other similar devices? It goes without saying that I'll do the porting work myself, again, if you're fine with it.
[Samsung Galaxy S8 & S8+ Cross Device Development] Scroogeyy:
I also don't have the Bixby button. If it's still working, you can use a paper clip or something similar to press the button inside. That's what I do.
[Samsung Galaxy S8 & S8+ Cross Device Development] archeiii:
Hello! Can anybody recommend me a good settings to be able to run multiple apps consistently? I use some sort of floating window and it closes after some time. Tried some adjusting in RAM section but no luck... 😅
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Be sure to turn battery optimalisations for ur apps off becus if u dont chances are it gets closed after a while
[Samsung Galaxy S8 & S8+ Cross Device Development] archeiii:
Already did alot of changes including that and unfortunately the floating window still gets closed but the app still running in background. I'll try change the ROM, do I have to pay for the paid version of a2n if I change to another ROM?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Seems that in latest Kernel revision, CPU performance is very slightly superior too. This is so nice
[Samsung Galaxy S8 & S8+ Cross Device Development] aniketqwerty:
Hi! Can anybody suggest me some settings to improve the battery life ? Thanks.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Just study the whole app to understand which settings are preferable for battery life.

For quick results: follow the tips from the "suspend max freq.." check "disable boost" ... check "hotplug" + "only while suspend" .. use "Balanced" profile and keep all the other settings by default.
[Samsung Galaxy S8 & S8+ Cross Device Development] aniketqwerty:
Thanks for the reply... was a bit hesitant with the settings 👍
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
@ace2nutzer is there any particular reason why Battery Charge speed will decrease as battery temperature goes down?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You need to tell me more information about mA and temp in °C, then I can check in source code.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Trying to run AnTuTu V10 with a high OC. Ace's Battery Voltage algorithm is hard carrying the phone. The CPU frequency is consistently throttling to avoid shutdown. Man. This battery is dead.

However it DID fail once. Sometimes even this failsafe can't do anything when battery dies too fast
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yup, it's a race in the ms range ... Also it's initial version lol.

I'll try to update it to reduce CPU Freq instead to reduce DVFS Max Temp @ 60 °C, makes more sense. But the problem is every battery has different behavior, so it'll be impossible to find the perfect CPU Mhz that works stable on every phone. So the user will need to adapt his CPU limit himself in combination with battery voltage of course.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I'm not complaining lmao. I'm glad it does its job. Now I can actually use Overclock frequencies for daily usage without fearing a phone shutdown. Benchmarks are another thing. I'll have to replace battery for those, no choice.

It's really a shame that Samsung gave these phones such weak batteries
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Not really much to say. Phone will start off strong at 2800mAh so long as battery is between 15 and 70% charge and 18-30°C but as the charge goes up, the charge current goes down. Same applies if the temperature goes down (Or if it's higher than 35°C), charge speed will initially throttle down to 1500mAh and then reach a min at 700-900mAh.

I haven't seen this behaviour on Huawei or Nokia phones. Seems to be Samsung exclusive and this makes charging while running benchmarks pretty useless, because battery won't have sufficient current coming from the cable to, well, not die.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah, that's normal.

Full charge current is only as long as the battery voltage is below the max of 4,4 V ... once it reaches 4,4 V then it'll slowly reduce charge current till it's 100 %. But input current is all the time = the value you had set in A2N app!. That means for S8 if you set 3000 mA and your battery is 100 % level, then you have 3000 mA from the battery and 3000 mA coming from the cable = 6000 mA!!, of course if battery health is good. otherwise you have only those 3000 mA from cable + maybe 1000 mA from battery = 4000 mA which is still a lot usually to have stable CPU OC .. .at least for 2,7 GHz should be enough, but not for 2,8 GHz for sure, especially not with increased CPU voltage for 2,8 GHz step. The increase in power consumption between 2,7 @ 2,8 GHz is insane and that's why I don't recommend at all to use it, even not if it works stable.

The value you set in A2N app is the "AC (input!) Current Max" it's not the real effective charging current. This value only applies if the phone is in IDLE with screen OFF. Every time you see current drops, it means the difference is going to the phone itself.

I can literally change this behavior and increase the input current. But the problem is I don't know what current limit the hardware is capable to sustain without to burn some wires or the charger chip.

For now our max fail-safe is to use max input current like the battery cap, so it's called "1C charging". For S8 it's 3000 mA and for the S8+ it's 3500 mA. I can try with max input current 4000 mA or even 5000 mA.

For this it would require a charger that is able to provide 2,77 A @ 9 V instead of the 1,67 A @ 9 V like the original USB fast charger. And here starts the problem, not every user owns a more powerful charger.

And the chip will burn for sure, because it touches already 70 - 80 °C @ 9 V @ 3000 mA. With 5 V the temperature is a bit less, but the original charger only provides around 2200 mA max, so it's even worse.

With proper cooling the charger chip + powerful charger + better battery + proper CPU cooling like the one user did with peltier + water cooling ... you can have extreme performance boost ... but that's an overkill to the fullest! lol
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I see. This is a lot of useful information actually. Thank you! Maybe my phone is power throttling due to algorithm even when charging because I didn't touch the input current settings. I never knew what it did exactly. I only tuned the charge current limit
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
So, I tested immediately as soon as you said those things and I'm so happy to see it's true. By raising input current (USB PD in a2n manager, I believe?) and turning on battery idle while at 97% battery, the phone handled a full 2652MHz CPU load without power throttling! My total capacity should be 5214mAh with this setup.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Checked right now in sources, if you enable Battery IDLE feature then you don't need to change your custom input/charging current in the app. On every power source except USB 2.0 / 3.0 and WC, it'll set automatically the highest allowed input current.

Once your battery is empty you can set input current at max value ... then after 2 min. check the "Charging Current" .. if it's still 3000 mA then you know that your setup is stable. Then later you can use this for battery IDLE. (the charger and cable)

It works this way: if the phone need 3500 mA actually, then it'll take 3000 mA from the cable and the rest from battery .. so the 500 mA. So the battery acts like a BIG CAP ... like the ones you know from car amplifiers.

The total capacity is then not in mAh .. because it's only the case for battery, but it's 3000 mA + ??? depends how much the battery can still provide ... my battery is still able to provide 3000 mA. I think your battery is much worse .. likely only 1000 - 1500 mA .. so you can say a total power of min 4000 mA = 4 A.

Note: also don't forget to set the max charging temp to the max as well to avoid input current throttling to 500 mA.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I suspect that when phone is charging in battery idle mode, it will prefer drawing power from the charger rather than the battery still because when I lowered input current, the S8's CPU responded with lower performance, even though the battery presumably supplied the same amount of power. This is kind of bad because it would mean that when you are in battery idle at full 3A input current, you are closer to actually 3A flat current rather than 3A from the charger + 2-3A from the battery.

I might as well be wrong, but so far, this is the impression I get.

I tried to replicate that behavior on my Note 9 which has a far stronger battery (3700mAh considering its current health), and lowering input current did appear to throttle CPU performance there too.

I'm also confused because Samsung officially stated that S8 can charge at like 9V/1.67A. But here we are pushing 9V/3A with battery idle on and input current at 3000mAh, aren't we? Or is input current different from that specification?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes, that's the main purpose of battery idle feature. Battery will only be used if the input current is not enough depending on power consumption.

I don't know what you mean.

Phone doesn't draws 3000 mA all the time. On idle with screen on it's only 120 mA. Also remember that the charger was never designed to supply the phone without battery. It's only for charging the battery. Don't compare a phone with a notebook, it's not the same and never will.

With OC ?

Samsung stated just nothing.

They only say AFC charger (adaptive fast charging)

The charger algorithm between stock kernel and this kernel is completely different. I've worked on charger control for about 3 weeks every day 10 h. except sunday. The specs on the charger only means what this charger is able to deliver. But the effective input current accepted by the phone and the decided charging current depends on the charger driver in kernel.

On stock kernel it's 1800 mA with fast charging disabled (5 V) and if it's enabled it's 2200 mA @ 9 V.

Those values are for charging current.

The phone nominal voltage is 3,8 or 3,85 V. In general the phone only need 5 V input voltage to work and charge properly. The phone doesn't need the 9 V at all. But it's preferable for higher current. That means the phone will convert the 9v always to 5v before it can be used. And this converting work just increases the heat of the phone. But it has one more nice advantage... if you try to charge the phone with 2000 mA with a long USB cable @ 9 V ... then it'll charge with 2000 mA ... stable.

But try the same with 5 V .. and you'll see the current will drop to around 1000 mA. Because the wire is too long and 5 V is very low voltage ... and due to the resistance of the cable, it'll loose some voltage and once voltage gets lowered .. it also lowers current.

On this kernel you can enable or disable fast charging in Android settings --> battery ... and will change only the input voltage of 5/9V.

Input current and charging current remains the same, at least as the charger still can sustain it.

Therefore as long as your desired charging current works stable @ 5 V, then you should prefer to charge with 5 V to reduce a bit the heat of the phone.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Oh well that makes sense

Eh forget about this. I checked further and I noticed that this behavior is actually absent on our S8, but it is present on the Note 9. Your custom DVFS must have removed that feature. What I meant is that if I put USB PD to, for example, 3000mAh in battery idle, CPU will perform as expected, but if I lower USB PD to 1500mAh for example, CPU performance will drop a lot under load, not due to temp or voltage throttling. It behaves very similarly to Desktop CPUs POWER throttling. But this doesn't apply to our S8 so it's off topic. Just clearing it up.

Not gonna lie to you here, no. The M3 cores are insanely power hungry even at stock. Either way like I said before, this is off topic since our S8 doesn't show that behavior as far as I can tell. It prefers to crash :ROFLMAO:

Wait so what you're telling me is that charge current and wattage isn't actually hardware limited by the phone's charge controller, but by the CHARGER?

Wouldn't this imply that S8 could theoretically charge at speeds of 20-25W, if the temperature of the charging chip wasn't a problem?

I believe my charger can switch between 5V/3A and 9V/2A. It uses Qualcomm's Quick Charge 2.0. I'm guessing that isn't enough to use the full 9V/3A that the max USB PD setting can handle.

So I could grab a 45W Quick Charge 3.0 charger and actually benefit from it in battery idle? That's really good to hear lmao. Hope I didn't misunderstand you
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Really? - Please check again, as there is no such limit.

But in fact there was such a power limit on stock DVFS driver, but I've it completely disabled since we use only our custom DVFS driver.

The stock DVFS driver isn't active at all.

Note: once you change CPU/GPU Freq, DVFS Max Temp or plug/unplug the charger, the device peak voltage value will reset.

This is to avoid throttling as much as possible.

Yes Charger, then Cable and the kernel charger driver.

Of course also the charger chip inside the phone, but nobody knows how much it can handle. According to the source code it has only a overheating protection.

Yes if I change some things in kernel, then you can charge even with 6000 mA .. having the 3000 mA battery from 1 - 100 % charged in 30 minutes, but it's not good for the battery.

This charger should be supported on this kernel.

@ 9 V it can give 3600 mA to the phone.

9V/3A = 5400 mA converted to the 5 V.

Yes and no, it depends on the limits that are hardcoded in charger control driver. For now it's 3000 mA in battery IDLE mode, no matter what you set and no matter what charger you use. You can't go over the hardcoded 3000 mA.

For now input_current and charge_current uses the same current value what you set in A2N app.

The charger_current is taken from the input_current.

The input_current gives the power for the phone itself and for charging the battery.

I'll try to update charger control to use in some cases 5000 mA for input_current. Basically that would replace the battery entirely having stable CPU OC and a hell of heat. lol
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ok Ace. Thank you so much for your time. Now I have a better idea of how things are looking.

PS: At 100% battery and Battery idle on, my S8 sometimes still shuts down at 2652MHz. Maybe my battery is very dead. Incredible that 2652MHz can apparently overpower the charger. Phone is rock solid at 2496MHz.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Don't OC CPU and GPU at the same time. First make CPU OC stable.

Then make GPU OC stable ... then try to use both together. If it's not stable it's a power issue.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Bold of you to assume that me, the benchmark wizard, would run overclocks without giving them proper voltage first :cowboy:

Phone reboots. It's power issue, somehow. My CPU really dislikes 2652MHz. 2496MHz is perfect, runs barely hotter than stock. As soon as I switch to 2652MHz, if I even think of opening CPU-Z, boom, 85°C on CPU :eek:. 2496MHz requires 1.035V for me but 2652MHz jumps to 1.2V. Anything below freezes. I'll find a way though. Perhaps a more powerful charger, a shorter and better cable. This isn't your DVFS's fault. It's just physics which I'll find my way around. Perhaps a custom battery :unsure::alien:
[Samsung Galaxy S8 & S8+ Cross Device Development] aniketqwerty:
my phone randomly reboots sometimes throughout the day (2-3 times-ish)... any help with that please ??
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
If you're using OC, you can't report this type of problem. Specify your current Kernel settings
[Samsung Galaxy S8 & S8+ Cross Device Development] Badger50:
Thread lightly cleaned.

A friendly reminder to all regarding XDA Rule 2.3:

Spoiler content hidden.

Please keep your posts polite and "on topic" out of respect for the developer, and just report rules violations rather than responding to them.

Your cooperation is appreciated. Thank you.

-Regards: Badger50
[Samsung Galaxy S8 & S8+ Cross Device Development] aniketqwerty:
using "balanced" in profiles and the settings recommended to me in my last post...
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
You still aren't specific enough. Does it reboot while idling or while you are using it? The way you portray the problem, it looks like your battery is very old and giving out. The battery crash prevention algorithm can't always succeed in its purpose.
[Samsung Galaxy S8 & S8+ Cross Device Development] aniketqwerty:
been using this phone since 2018... reboots usually happen when idle. But it only happened once since like the past 5 days.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Since 2018 = very old battery. If it’s been 5 days and it didn’t reboot yet, it probably sorted itself out. Perhaps something you installed was causing problems.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
When it happens post the last_kmsg.

You get it in the red a2n app in debug menu.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ace I remember you saying something about Kernel Controls being unlocked for other Kernel managers once A2N App does the license check and all, right?

But ThunderTweaks seems unable to modify any parameters. I'm trying to mimic the E9810 Big Cores hotplugging but since the modifications don't apply, I'm unable to do so.

The reason why I'm trying this in the first place is that I noticed that your statement about "High frequency, less cores being inferior to low frequency, many cores" argument is theoretically correct but practically it's not (for some reason). Several apps (and especially games) seem to be massively single threaded the moment they enter loading phases and unwilling to share the workload across cores. This means that a higher single core frequency can and will improve UX in these scenarios (at the cost of battery life). This also shows in benchmarks that specifically target the CPU with single core workloads, such as AnTuTu (And those see an especially significant gain in CPU scores, too).
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Keeping this phone from crashing at high OCs is like balancing on a thin rope that will snap as soon as the littlest breeze of wind blows by, at least on an old battery.
[Samsung Galaxy S8 & S8+ Cross Device Development] romasik:
ace2nutzer

Not actual. I've already found places in the code to overclock. little core.

Hello, please help unlock Little core freq on Galaxy S7 Exynos8890 , i try edit dts but unfotunely( this fork moro kernel :

https://github.com/roma21515/MoRoKernel-S7 . Please help, i see you overclock s8, i try edit but freq on little core not unlock(

dtsi in attach.

Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] _Zacon01_:
Good morning, since last night the app tells me to update but the play store doesn't update, now the phone is with factory base frequencies
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Thanks, I'll fix it ASAP.
[Samsung Galaxy S8 & S8+ Cross Device Development] _Zacon01_:
not if you need it but that's the problem
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Fixed!
[Samsung Galaxy S8 & S8+ Cross Device Development] _Zacon01_:
Thank you
[Samsung Galaxy S8 & S8+ Cross Device Development] m7mod6969:
i've been seeing this from the last day please fix

sent from a galaxy note 8
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Tap on Update please.
[Samsung Galaxy S8 & S8+ Cross Device Development] m7mod6969:
I click on update and there's no update
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Okay, then Google it's still rolling-out.

Usually it's done automatically if auto update is enabled in Play Store.

Try to reboot the phone ... and then check for app update. If there is no update then you have 2 options:

1. Wait 1 day till Google will update it.

2. Uninstall and install the app will fix the issue but you need to reconfigure the a2n app.

It's not an update from me, it's Google its own security update.

They do this every 3 months or something like that.
[Samsung Galaxy S8 & S8+ Cross Device Development] m7mod6969:
Thanks for your help
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Bruh. This had to happen right as I wanted to benchmark :rolleyes::coffee: bummer
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Update still not out. I'll just reinstall the Manager.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
ANNOUNCEMENT

R64 soon online.
[Samsung Galaxy S8 & S8+ Cross Device Development] Maxdi3:
Hello, my friend, I'm from Iran, and because of sanctions, I couldn't buy the pro version of the kernel controller from the Play Store. is there any other way to get it through other platforms? I'm excited to test your app.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No, but you can try to bypass it with a German proxy server.

Good luck!
[Samsung Galaxy S8 & S8+ Cross Device Development] _Zacon01_:
the kernel download site doesn't work, what happened?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I have a feeling the site is suspended somehow. But wait first if @ace2nutzer knows what happend to it before making conclusions.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah it looks like the FTP server is down. It was a FTP server from an xda friend. A few years ago he told me that one day he'll take it down for private reasons. So that's the day.

I'll upload all the needed files soon in a new server or to my github. Likely once R64 is done.

If someone needs to download R63, it would be cool if someone could upload the original zip file here, as I don't have a backup.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Not sure if its the latest one, but its from a nov release atleast. https://mega.nz/file/3MZixaSJ#8-_kvB8PD_UCzoDU6QsTTs-MLbS5Pz0L3NZj0ksxffA
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes it's R63 for the S8.

So new users can download this for now.

Thank you very much! (y)
[Samsung Galaxy S8 & S8+ Cross Device Development] blueeyeblue:
@ace2nutzer - Where can I download the latest stable & nightly for SGS8+ (G955F)?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
19.36 MB file on MEGA

mega.nz
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
It's not for S8+.

Note8 also has different package.

I'll check if I've them on my build Laptop.
[Samsung Galaxy S8 & S8+ Cross Device Development] blueeyeblue:
@ace2nutzer I have also some time for flashing tomorrow. Would be glad if you could provide me with the very latest stable version for the SGS8+ Thanks!