Related
I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
Let's discuss, I don't know enough about it. But if the processor would overheat it could break right?
Aronuser said:
Let's discuss, I don't know enough about it. But if the processor would overheat it could break right?
Click to expand...
Click to collapse
Do you mean "safe"? ("security" is about criminals hacking your phone, "safety" is about not damaging things or self).
I'd say it's like with PC overclocking - if you don't do anything crazy (like increasing voltages too much) then you're safe.
From what I can see, we can overclock our phones with voltages *lower* than stock, so that's as safe as it's going to be
There's also a related safety issue: if your phone crashes, its filesystem "might" become broken and the phone "might" not boot. I haven't seen that happening, but having a nandroid backup is just common sense.
Yep, wrong term. Instead of 'secure' should change it to 'safe'.
Like overclocking in any environment, risk is involved. One has to weigh the pro and cons themselves. But, unless you want higher benchmark result or lagging in games - one doesn't need to overclock.
sysKin said:
Do you mean "safe"? ("security" is about criminals hacking your phone, "safety" is about not damaging things or self).
I'd say it's like with PC overclocking - if you don't do anything crazy (like increasing voltages too much) then you're safe.
From what I can see, we can overclock our phones with voltages *lower* than stock, so that's as safe as it's going to be
There's also a related safety issue: if your phone crashes, its filesystem "might" become broken and the phone "might" not boot. I haven't seen that happening, but having a nandroid backup is just common sense.
Click to expand...
Click to collapse
TNCS said:
Yep, wrong term. Instead of 'secure' should change it to 'safe'.
Like overclocking in any environment, risk is involved. One has to weigh the pro and cons themselves. But, unless you want higher benchmark result or lagging in games - one doesn't need to overclock.
Click to expand...
Click to collapse
Thanks guys, well yeah i meaned "safe" sorry.
Hi,
I'm planning to buy LG G3 (32 GB version). It's very cheap right now considering it's specs but I have some questions before buying it.
1- How is general performance and gaming on stock ROM (lollipop or kitkat)?
2- Does it overheat or force the screen brightness to be lowered?
3- How is battery life (screen-on time) with moderate to heavy usage?
4- How is development going? Does it have stable AOSP ROMs without major issues or camera problems?
5- Are there any problems or any thing that I need to know before buying?
I would really appreciate it if some one can help me. Thanks in advance
1- I don't game
2- Overheat yes but it never forced me to lower the brightness
3- It's not bad, I can last 2 day with it
4- LG G3 camera is bad in every custom rom (unless you install the moto cam, or another (I don't remember witch one))
5- Overheat is the biggest downside for this device, I can go to 75C+ easily
75 c with general usage?! Does it affect perfermance or cause lagging?
Navios92 said:
75 c with general usage?! Does it affect perfermance or cause lagging?
Click to expand...
Click to collapse
The phone overheats but it isn't causing any performance or lag in my case. It is not getting up to 75. Also the gaming is very good. The battery gives me about 5+ hours of SoT.
Sreerag ag said:
The phone overheats but it isn't causing any performance or lag in my case. It is not getting up to 75. Also the gaming is very good. The battery gives me about 5+ hours of SoT.
Click to expand...
Click to collapse
On stock or custom rom? And what is your brightness settings?
Sent from my SM-G313HU using XDA Free mobile app
Navios92 said:
On stock or custom rom? And what is your brightness settings?
Sent from my SM-G313HU using XDA Free mobile app
Click to expand...
Click to collapse
On stock I got about 4+. Using custom ROMs like cloudy and exodus gives me much more. My brightness is at 50% auto.
Navios92 said:
Hi,
I'm planning to buy LG G3 (32 GB version). It's very cheap right now considering it's specs but I have some questions before buying it.
1- How is general performance and gaming on stock ROM (lollipop or kitkat)?
2- Does it overheat or force the screen brightness to be lowered?
3- How is battery life (screen-on time) with moderate to heavy usage?
4- How is development going? Does it have stable AOSP ROMs without major issues or camera problems?
5- Are there any problems or any thing that I need to know before buying?
I would really appreciate it if some one can help me. Thanks in advance
Click to expand...
Click to collapse
1) According to my experience, stock rom is a bit laggy, but absolutely tolerable.
If you flash an AOSP rom, lags should completely disappear, you can find the difference in heavier games.
But I can't compare the old KitKat rom to Lollipop one, since I immediately upgraded my device.
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
3) It strongly depends by installed apps and mainly by the "damned" Google Play Services, which often cause a quicker battery drain.
During standby, the autonomy is excellent, during the utilization it's similar to the other devices, probably "a bit" longer.
4) The stock development is stopped to the February release (20H), but is also true that G3 was the first terminal to receive the Lollipop update.
On stock camera, 4K video recording is laggy, personally I prefer the excellent and smaller Full HD recording.
On AOSP roms (Resurrection Remix in my case) camera app is qualitatively comparable to the stock one... except for the audio quality in videos: volume become inexplicably lower and suffocated after some second of recording, it sounds me like a microphone which is turned off.
If you accept this issue (hope it will be solved) or you prefer to use a 3rd-party camera, I strongly suggest you to flash an AOSP rom, but be careful about rooting, if your intention is to immediately flash a custom rom, do not upgrade to Lollipop, or you'll have problems with "non-bumped" recoveries.
5) You have to know that G3 (according to many amateur crash videos) has a weak digitizer (so I suggest you to buy absolutely a proof cover like my Ringke Max).
Then... the already cited overheating, which would be a problem only for the laggy experience, no damage risks.
If you want to flash a custom rom, prevent to upgrade to Lollipop.
For the rest... you'll have a great device [emoji41]
I have found AOSP roms to be quite flakey, ive tried many of them and keep going back to stock - random reboots, crap battery etc.
Thermal throttling mod def helps with heat.
Simone98RC said:
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
Click to expand...
Click to collapse
Honest question... do people actually use their devices at 100% or even 90? I currently have my G3 set to 67% and I never really change it. My Nexus 7 I keep at around the same unless I'm reading in bed and it's too bright, so I knock it down some. The only situation I could see using it at 100% would be in direct sunlight, but the glare makes this a bad idea in general.
Just curious I guess.
Simone98RC said:
1) According to my experience, stock rom is a bit laggy, but absolutely tolerable.
If you flash an AOSP rom, lags should completely disappear, you can find the difference in heavier games.
But I can't compare the old KitKat rom to Lollipop one, since I immediately upgraded my device.
2) Yes, one of the worst problems of this phone is the overheating.
If you reach high temperatures (70 °C and above), device become to be laggy, as CPU need to be cooled by a process called "throttling".
On stock rom the maximum brightness is automatically decreased to 90%, or to 80% in very hot conditions, in AOSP roms brighteness is untouched.
3) It strongly depends by installed apps and mainly by the "damned" Google Play Services, which often cause a quicker battery drain.
During standby, the autonomy is excellent, during the utilization it's similar to the other devices, probably "a bit" longer.
4) The stock development is stopped to the February release (20H), but is also true that G3 was the first terminal to receive the Lollipop update.
On stock camera, 4K video recording is laggy, personally I prefer the excellent and smaller Full HD recording.
On AOSP roms (Resurrection Remix in my case) camera app is qualitatively comparable to the stock one... except for the audio quality in videos: volume become inexplicably lower and suffocated after some second of recording, it sounds me like a microphone which is turned off.
If you accept this issue (hope it will be solved) or you prefer to use a 3rd-party camera, I strongly suggest you to flash an AOSP rom, but be careful about rooting, if your intention is to immediately flash a custom rom, do not upgrade to Lollipop, or you'll have problems with "non-bumped" recoveries.
5) You have to know that G3 (according to many amateur crash videos) has a weak digitizer (so I suggest you to buy absolutely a proof cover like my Ringke Max).
Then... the already cited overheating, which would be a problem only for the laggy experience, no damage risks.
If you want to flash a custom rom, prevent to upgrade to Lollipop.
For the rest... you'll have a great device [emoji41]
Click to expand...
Click to collapse
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Navios92 said:
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Click to expand...
Click to collapse
1. Yes it does. I get 70C while using facebook and similar apps within 15mins of usage. Still not too much lagg even with high temperatures.
2. You will probably be able to achive root on lollipop but the problem is the aboot(bootloader) that comes on lollipop. It's not compatible with bump that needs to be applied to recovery and boot partitions so you would recive Secure Boot Error.
Although you could use benders autorec app on lollipop which flashes kitkats aboot and laf imgs along with TWRP.
3. While I can't compare the screen with any of these phones as I have not used them, personally I don't have issues with my contrast. I can see things well under suns reflection as well.
Navios92 said:
That was really helpful. Thanks alot.
I just have three more questions.
1- Does it reach 70c if I don't game?
2- Why shouldn't I upgrade to lollipop if I want to install custom ROMs? I've seen root method here for lollipop, what will be the problem exactly? And can't I just roll back to kitkat?
3- I've read some reviews saying that the screen is dim and has a low contrast ratio. Is it true? How does it compare to other LCDs like M8 and Z2 or the older G2?
Click to expand...
Click to collapse
1) It may happens in every CPU stress condition, when device works at maximum clock (2.5 Ghz). Mostly in heavy games, but in other scenarios too, like continous switch between mobile data and Wi-Fi, or accidental screen on in pocket (which I encounter on my AOSP rom).
2) The Lollipop update enable the Secure Boot, which verify the signature of some critical partition of your device: if it find any inconsistency, the phone won't boot and send an alarming "blue-red" sequence of LED colours like a police light.
I've tried that on my device, I still get shivers!
Since you do the update, nor the downgrade to KitKat want to reverse the existence of Secure Boot, so you'll need to install only "bumped" recovery to prevent the issue.
It means that you have to manually flash TWRP recovery, since the standard "no-bumped" version will get your device in those terrible conditions.
3) I can't do a comparison since I'm not informed about these devices.
Personally for a long time I've disliked the "weak" colour intensity of G3, but after 6 months of experience I've understand that was the LCD of my old SGS3 to be abnormal, with a graceful but false contrast.
The real problem is not the contrast ratio, but the low brightness which you'll surely note in sunny conditions.
In the successor G4 the screen brightness is fixed by an increasing of almost 25%.
Simone98RC said:
1) It may happens in every CPU stress condition, when device works at maximum clock (2.5 Ghz). Mostly in heavy games, but in other scenarios too, like continous switch between mobile data and Wi-Fi, or accidental screen on in pocket (which I encounter on my AOSP rom).
2) The Lollipop update enable the Secure Boot, which verify the signature of some critical partition of your device: if it find any inconsistency, the phone won't boot and send an alarming "blue-red" sequence of LED colours like a police light.
I've tried that on my device, I still get shivers!
Since you do the update, nor the downgrade to KitKat want to reverse the existence of Secure Boot, so you'll need to install only "bumped" recovery to prevent the issue.
It means that you have to manually flash TWRP recovery, since the standard "no-bumped" version will get your device in those terrible conditions.
3) I can't do a comparison since I'm not informed about these devices.
Personally for a long time I've disliked the "weak" colour intensity of G3, but after 6 months of experience I've understand that was the LCD of my old SGS3 to be abnormal, with a graceful but false contrast.
The real problem is not the contrast ratio, but the low brightness which you'll surely note in sunny conditions.
In the successor G4 the screen brightness is fixed by an increasing of almost 25%.
Click to expand...
Click to collapse
Screen quality is very important to me as I watch a lot of videos.
But heating problem is a turn off. I live in a hot country and had the same problem with Optimus 4X which was unbearable.
I might wait till G4 price goes down and buy it or get A5 and wait for a proper flagship next year.
Hello
Lots of G4 devices gets boot loop in time.
warranty fixes it free for now. but even new 1.1 v hardware versions gets bootloop (according to reddit pages)
I think there is no safe device. So how can i avoid this problem ?
According to people this problem caused by overheating, that makes solder weak. then some cpu core connections gets loose and causes boot loop.
My desperate solution is lowerclocking the device. I'm using cpu tuner for disabling 4 cores.
I tested this with benchmarks and games. It seems not overheating.
But cpu performance only 1/3 and there is tiny lags in every app.
If you have better solution, let us now. You are the only hope !
i really like this device and i dont want to buy some mid level f 2.0 camera devices.
excuse my english
orcnd said:
Hello
Lots of G4 devices gets boot loop in time.
warranty fixes it free for now. but even new 1.1 v hardware versions gets bootloop (according to reddit pages)
I think there is no safe device. So how can i avoid this problem ?
According to people this problem caused by overheating, that makes solder weak. then some cpu core connections gets loose and causes boot loop.
My desperate solution is lowerclocking the device. I'm using cpu tuner for disabling 4 cores.
I tested this with benchmarks and games. It seems not overheating.
But cpu performance only 1/3 and there is tiny lags in every app.
If you have better solution, let us now. You are the only hope !
i really like this device and i dont want to buy some mid level f 2.0 camera devices.
excuse my english
Click to expand...
Click to collapse
I think flashing a custom kernel and underclock A57 cores (the bigs). This could prevent overheating, losing very little performance.
in the next few days I receive my phone, i will do that and test what happen. I think that could be a good solution to avoid a bootloop issue.
orcnd said:
Hello
Lots of G4 devices gets boot loop in time.
warranty fixes it free for now. but even new 1.1 v hardware versions gets bootloop (according to reddit pages)
I think there is no safe device. So how can i avoid this problem ?
According to people this problem caused by overheating, that makes solder weak. then some cpu core connections gets loose and causes boot loop.
My desperate solution is lowerclocking the device. I'm using cpu tuner for disabling 4 cores.
I tested this with benchmarks and games. It seems not overheating.
But cpu performance only 1/3 and there is tiny lags in every app.
If you have better solution, let us now. You are the only hope !
i really like this device and i dont want to buy some mid level f 2.0 camera devices.
excuse my english
Click to expand...
Click to collapse
are you under warranty.? if yes keep using it like always if you try to prevent from happening and dont bother running it then disable the cores..
a point
Why on earth the phone
redmi note 7 pro which have snapdragon 675 and antutu of 210,000 can play pubg on 61.2 fps after screen overclocking and no heat after 1 hour of playing pubg
But the
Samsung S9+ with snapdragon 845 and antutu of 345,000 and a GPU that has more than 4 times the performance of the snapdragon 675 in antutu and after only half an hour it can't sustain 40 fps and a heat degree that can cook eggs on the frame of the device
Not even taking about battery life
The request
To make it short
Iam not a developer (too bad)
So I wish if some awesome developer can port one of these kernels
[Crimson Kernel] or [Hydra+ Kernel]
The reason
Again to make it short
225%-245% performance increase
Noticeable in gaming fps
More importantly
Way less heat while gaming
And better battery life
How on earth
Simple
Just see for your self the videos down below
Since the s9+ have Havoc OS
We need the Kernel
Please watch those 4 minutes videos
I'm sure it deserve your time
The videos
Links
https://github.com/uditkarode/crimson
From redmi note 7 pro
https://tweakguy.com/download-crimson-kernel-66-hz-for-android-phones/
The reason a developer should care
This device the samsung galaxy s9/s9+ had its last major update a month ago
So no major updates are coming to this device again
Only 2-3 security update left
So your work is what will write a new life for this device
So please help
at least comment or something so developers can hear us
I can confirm that this device has some problems with heat. But it's not what you think. Mostly it's related to the kernel thermal framework, which is responsible to avoid big increasements in temperature. You can think of it like a process that monitors heat and power. When a certain threshold of temperature is reached, thermal fw will throttle down the CPU/GPU freq until the heat is significantly lowered (that's not entirely exact, but it can be explained that way). I think that Samsung somehow messed up this in some way - because this problem happens on many S9 devices, even on stock.
This process is also responsible for decreasing performance in apps and games, because to archive lower temperatures, it throttles down power. That's most likely why you get lower FPS after some time.
The device's hardware itself doesn't require a power boost, because it has more than enough power to beat most games in high FPS. If you now would increase the kernel's power and freqs, you would only get higher heating.
We need whether a better thermal throttling mechanism, which can only be done via kernel. ALternately you can modify and tweak the settings to stay in lower freqs in order to avoid the overheating. For example a kernel module. Or, for easy use, FDE.AI and set it to powersave (NOT anything else! Because it includes a boost mode fdor CPU/GPU that actually increases the frequencies, which will result in more heat). But even in powersafe mode, it won't decrease your gaming performance! I've tested this a long time. However, if you know what you're doing, just tweak settings by yourself. Or look for another solution, like LKT maybe.
Another idea: Here's a custom kernel. It's up to date for now. The developer has stopped the support a few days back. But it includes the current security patches, so you can use it without worries. It includes a solution for the overheating issue. I didn't test it yet, but I will. Here is the link: https://forum.xda-developers.com/ga...t/kernel-rz-kernel-samsung-galaxy-s9-t4081191
dtrail1 said:
I can confirm that this device has some problems with heat. But it's not what you think. Mostly it's related to the kernel thermal framework, which is responsible to avoid big increasements in temperature. You can think of it like a process that monitors heat and power. When a certain threshold of temperature is reached, thermal fw will throttle down the CPU/GPU freq until the heat is significantly lowered (that's not entirely exact, but it can be explained that way). I think that Samsung somehow messed up this in some way - because this problem happens on many S9 devices, even on stock.
This process is also responsible for decreasing performance in apps and games, because to archive lower temperatures, it throttles down power. That's most likely why you get lower FPS after some time.
The device's hardware itself doesn't require a power boost, because it has more than enough power to beat most games in high FPS. If you now would increase the kernel's power and freqs, you would only get higher heating.
We need whether a better thermal throttling mechanism, which can only be done via kernel. ALternately you can modify and tweak the settings to stay in lower freqs in order to avoid the overheating. For example a kernel module. Or, for easy use, FDE.AI and set it to powersave (NOT anything else! Because it includes a boost mode fdor CPU/GPU that actually increases the frequencies, which will result in more heat). But even in powersafe mode, it won't decrease your gaming performance! I've tested this a long time. However, if you know what you're doing, just tweak settings by yourself. Or look for another solution, like LKT maybe.
Another idea: Here's a custom kernel. It's up to date for now. The developer has stopped the support a few days back. But it includes the current security patches, so you can use it without worries. It includes a solution for the overheating issue. I didn't test it yet, but I will. Here is the link: https://forum.xda-developers.com/ga...t/kernel-rz-kernel-samsung-galaxy-s9-t4081191
Click to expand...
Click to collapse
First thanks for replying
And
Not talking as a developer but
Samsung firmware and maybe kernel focuses on security and nox integration and alot of unused features for many people
And to your knowledge how the redmi note 7 pro can jump from 26 fps to 62 fps and less heat by only changing the Kernel to Crimson Kernel
That moment when I discovered that g965u1 has no bootloader unlock
???????????????????
TIP
I managed to solve the problem, I just did the following: I took root, installed a thermal, disabled battery saving for pubg, and run the game using the pubg gfx app. it was smooth I played + 1 hour without dropping frames.
Bruh
Oh thanks
The s9+ never needed half it's performance to play pubg on 60 fps
And still overheat too much
Look here
@mhmedahmed1996 Maybe instead of complaining here like a kid, you should learn how to code and make one yourself. The developers here work for free and are not vending machines where you ask for something and you get it immediately.
I know and I'm sorry
When I posted this thread I thought I will try my best as someone who can't code
Maybe test and send logs but now I discovered that my g965u1 has no bootloader unlock
You can't imagine how I feel now
erickgta222 said:
I managed to solve the problem, I just did the following: I took root, installed a thermal, disabled battery saving for pubg, and run the game using the pubg gfx app. it was smooth I played + 1 hour without dropping frames.
Click to expand...
Click to collapse
What exactly do you mean by "installed a thermal"? At least for the S9 starlte I couldn't find any custom kernel with a custom thermal fw and I don't have the time to develop one by myself. So if you know something I missed, I'd appreciate to get it
Gesendet von meinem SM-G960F mit Tapatalk
I installed a thermal module through the maginsk manager.
erickgta222 said:
I installed a thermal module through the maginsk manager.
Click to expand...
Click to collapse
And what module exactly?
I've been searching that for a long time, but I can assure you that I never found one. I'm curious what module you're talking about.
Edit: well, whether you've installed something that is doing something entirely different - like disabling thermal throttling. Those do exist.
or it's for another device - there is a thermal mod for Xiaomi phones. But it actually tweak TFW for less throttling to increase performance.
Or there is a module that can only be found by getting a certain link, which is hidden to the public - but why would that be?
Or it's just nonsense.
I'd appreciate it if you could post a link to that module.
Otherwise I'll end up developing one for myself (maybe, if I have enough time! Because first I'd have to get more knowledge about how to develop kernel modules for magisk, that are compatible with my device. I developed custom kernel for OMAP4 devices a few years ago. But that's a little different I suppose... And it wasn't magisk.)
Gesendet von meinem unknown mit Tapatalk
You'll have to hack it together but here's the source code.
GitHub - MiCode/Xiaomi_Kernel_OpenSource at violet-q-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com