So recently many users were saying that the four core were maxed out to 2.2Ghz, I faced the same problem, so instead of rooting my phone and putting the CPU governor in On demand/power saving I tried some methods and bought the clock frequency to 1.1Ghz/1113Mhz. I'm still not sure how this happened but here are the things I tried
After a full day use yesterday nearly 3hrs of screen on time and my battery percentage was left to 37% so, I charged my phone to 90% cleared the cache using fastboot, uninstalled useless apps like clash of clans, pubg, Internet speed meter, and some other.
Note clear only cache
And the results see the images. I can't guarantee that it will work for you, but it worked for me.
As you can see I don't have root accces, so this is done without rooting.
Check for some more time and report here
I can report that clearing cache (complete wipe) totally worked in my case. I had this issue and i reported it to xiaomi, anyway.. i was going through the process of rooting and enabling HAL3 for google camera and the phone was completely wiped (I did not play around with the CPU ) anyway surprisingly the battery life improved so yeah it might be a cache problem.
Chaitanya Kumar said:
So recently many users ...
Click to expand...
Click to collapse
DiesFrae said:
I can report that clearing cache (complete wipe)...
Click to expand...
Click to collapse
Which is the command to clear cache guys, please?
Thanks!
bixirulo said:
Which is the command to clear cache guys, please?
Thanks!
Click to expand...
Click to collapse
Fastboot erase cache
Does this definitely solve the issue? Has it come back?
I'll try later, I have this problem too.
k278467 said:
Does this definitely solve the issue? Has it come back?
I'll try later, I have this problem too.
Click to expand...
Click to collapse
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...
hugopg said:
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...
Click to expand...
Click to collapse
That's so annoying... Is this the kind of bug Xiaomi would normally fix? I bought this phone 4 days ago and still can return it, I'm seriously considering it...
k278467 said:
That's so annoying... Is this the kind of bug Xiaomi would normally fix? I bought this phone 4 days ago and still can return it, I'm seriously considering it...
Click to expand...
Click to collapse
If you can, and you're unhappy... why not? I mean, this bug happened in pixel 2 XL months ago and was fixed. Its a software problem and it will likely be fixed in the future, but an ETA only Xiaomi can give you
hugopg said:
No it does'nt. At least for me. I've unlocked the bootloader (which wipes everything) and changed the scaling governor. This was the 'default solution'... I've experienced the problem 2 more times after that, but it is waaaay less common...
Click to expand...
Click to collapse
For me i was just playing around and unlocked the bootloader (wipes everything) and re-locked the bootloader (also wipes everything) but i didn't change anything and the problem seems to go away like today i had 37 mins SoT with only 9% battery drain so by this rate the battery should be drained in almost 7 hours SoT and that's really good IMHO
Someone can post the complete process or give link with the process?
Enviado de meu Mi A2 usando o Tapatalk
maybe a weird question , but i found that my phone have bootloader unlocked. this is te problem that i cant do ota updates...i know the trick power down and powerbutton to get in the fastboot mode....what im doing wrong when i press those keys i wont get into fastboot i will get a black screen nothing more.....help me pleaseeee
Related
Hello,
Is there a possibility to disable the delay that I have from the moment I press the unlock button to the moment the screen turns on?
At the moment I have 2.5 seconds delay from the moment I push the button until the screen turns on.
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
larry200ro said:
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
Click to expand...
Click to collapse
My phone has the same behaviour and the "problem" (if you want to call it a problem) is also described in some german forums - so no, it seems that this is absolutely ordinary.
I had the chance to compare it with a I9000 and the I9000 will outperformance the I9001 at this point, but nonetheless for me it is not really disturbing or so.
any updates on this one? Can someone please help? It's driving me crazy
Hy
I've read about the same problem on a hungarian forum, but I don't have it, mine turns on in less then a secound.
I think if this is such a common problem, Samsung will fix it. Maybe write them a mail.
When the screen has been turned off for a long time, the first unlock takes a lot longer than the following unlocks. For me, I think the 'cold' unlock is 2.5 seconds while a 'warm' unlock is just 1 second.
But yeah, this clearly is a standard problem. Let's hope Samsung brings out a firmware update soon to fix issues like these.
Mine has same "problem". It seems that the phone is in somekind of sleep.
i believe that problem is fixed in 2.3.4. Try flashing that and i hope you won't have that problem...i mean this is how it works:
1. I9000 uses SGX540 which uses less ram for its vram so you have around 250mb+ free ram
2. I9001 uses Adreno 205 which uses a lot of ram for its vram so that you have about 120mb left only
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Unfortunately it is not fixed with 2.3.4 as I still have the issue.
I will try your suggestion with the CPU frequency
shad0wboss said:
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Click to expand...
Click to collapse
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Edit:
Even with 1.4Ghz as frequency there is a delay, not that long but still about 1,5 sec.
reneph said:
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
Click to expand...
Click to collapse
yup it will...then you should wait for a better custom rom with all those JIT and ram compress tweaks enabled and then you can enjoy the speed.
To be honest if you guys want your problems to be fixed, do support the devs as much as possible in this thread
Psyco_01 said:
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Click to expand...
Click to collapse
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
reneph said:
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
Click to expand...
Click to collapse
mate, you can never have performance with battery conversations...it's inversely proportional.
1. Set maximum value to 1 ghz with minimum of above 245
2. Do a hard reset from going into settings -> privacy -> factory reset because i just did it recently and my phone's running much faster.
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
larry200ro said:
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
Click to expand...
Click to collapse
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Csapi007 said:
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Click to expand...
Click to collapse
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
shad0wboss said:
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
Click to expand...
Click to collapse
No, I mean getting the battery out and then putting it back.
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
Interesting....what version of android do you have (also kernel)
Mine reacts slower if I leave it longer. (samsung explanation "It is because the phone is entering in some kind of sleep state"). When I said that Galaxy s2 reacts instantly the answer was that Galaxy S2 has a better microprocesor and has a different platform.. hmmm
If you find this useful, press the Thank you button
Csapi007 said:
No, I mean getting the battery out and then putting it back.
Click to expand...
Click to collapse
well, i've done that a couple of time already without knowing it being a fix for random shutdowns...but really it's a bit annoying, it just turns off by itself..
Good day.
I wonder if anyone else has experienced this problem!
I bought a Xperia SP (c5303), the phone came with .211 firmware, updated to 2254, made the root, installed the recovery, unlocked the bootloader, installed Antutu Benchmaker. When during the tests reach 21%, the phone restarts.
I can only take the test when I install DoomKernel, and even then, the test 3d always gets zero score. So I only get 15000 points.
In others benchmakers, the test is completed. (such as quadrant).
Can anyone help?
New install Antutu. :laugh:
I've installed, but don't work. Keeping restart my phone.
Someone had the solution?
Delete please.
Sorry again, delete please.
i got the same problem.
Flash stock and try again. If it is a hardware issue your phone will shut down again. If not than you know what to do
mrjraider said:
Flash stock and try again. If it is a hardware issue your phone will shut down again. If not than you know what to do
Click to expand...
Click to collapse
I did this, I used flashtools put the firmware in 2254, when the phone call, asked to turn off. I hung up, waited a bit called again, did all the installation process, I installed Antutu, and in 21% the phone is restarted. I do not know what to do, how to use Antutu, but not with SP. I even uninstalled it and am waiting for an update to see if that resolves the problem. Sorry for the English, Google translator.
Sent from my C5303 using XDA Premium 4 mobile app
leandroprez26 said:
I did this, I used flashtools put the firmware in 2254, when the phone call, asked to turn off. I hung up, waited a bit called again, did all the installation process, I installed Antutu, and in 21% the phone is restarted. I do not know what to do, how to use Antutu, but not with SP. I even uninstalled it and am waiting for an update to see if that resolves the problem. Sorry for the English, Google translator.
Sent from my C5303 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Very very stange. 21% Is also the beginning of the test and the GPU comes a bit later.. Weird.
Could you get your hands on the old version of antutu? If you could see if that helps..
mrjraider said:
Very very stange. 21% Is also the beginning of the test and the GPU comes a bit later.. Weird.
Could you get your hands on the old version of antutu? If you could see if that helps..
Click to expand...
Click to collapse
I did it. I installed an old version 3.3.1 and it worked perfectly. I tried to upgrade from that. And the problem returned. I think the problem is the compatibility of the new ui Antutu.
Sorry for English, Google Translator.
Sent from my C5303 using XDA Premium 4 mobile app
Weird since v4 works here perfectly
Sent from my C5303 using xda premium
leandroprez26 said:
Good day.
I wonder if anyone else has experienced this problem!
I bought a Xperia SP (c5303), the phone came with .211 firmware, updated to 2254, made the root, installed the recovery, unlocked the bootloader, installed Antutu Benchmaker. When during the tests reach 21%, the phone restarts.
I can only take the test when I install DoomKernel, and even then, the test 3d always gets zero score. So I only get 15000 points.
In others benchmakers, the test is completed. (such as quadrant).
Can anyone help?
Click to expand...
Click to collapse
hi,actually,if u have anything want to know about antutu or question you can send email to [email protected]. they can answer your question ASAP.
How to stop your Xperia SP turning off at 21%
Hi there,
I had exactly the same problem, antutu got to 21% and then my phone would restart.
Fixed it by turning off stamina mode, now runs fine and indeed I got : 21983
21 % antutu bench. and restart
coLEmanmusicproject said:
Hi there,
I had exactly the same problem, antutu got to 21% and then my phone would restart.
Fixed it by turning off stamina mode, now runs fine and indeed I got : 21983
Click to expand...
Click to collapse
STAMINA mode I disabled and still it did not help still restarts at 21 percentile: (
I installed 3.3 and antutu test has been successful
and today I rebooted and when writing sms voice dictated to about 45 words, I rebooted and I have someone stym experience?
English translated by Google Translator: D
How much your free space on internal sdcard?
Try Free your internal sdcard must be above 1GB availble.
i got this problem too before on stock rom
hope this is work with you too.
coLEmanmusicproject said:
Hi there,
I had exactly the same problem, antutu got to 21% and then my phone would restart.
Fixed it by turning off stamina mode, now runs fine and indeed I got : 21983
Click to expand...
Click to collapse
Actually... Yes! I had the same problem, but when i turned off the STAMINA mode i try again and i get the same restart. BUT... when i try again i make the full test with no problems. There is something weird... Before the restart my phone was on almost 20 hours battery life and 62%... After the restart my phone was still 62% but 18 hours battery life... ?!
I had the same problem and once I got a system message that the phone is overheated so it gonna shutdown. sAfter that I just searched for the program that done that and I deleted it. Unfortunately I can't remember the name of it.
Same for me, I've try it 2 times and the my xperia sp always restarting when the benchmark reach 21%. It's not make my phone broken, right?
i have already stated this issue to Antutu > https://play.google.com/store/apps/details?id=com.antutu.ABenchMark&hl=en
and they replied on it. please be patient they are working on it.
I hope this is not hardware problem as antutu 3.3.2 is working properly without any issue , some Nexus users are also facing this similar issue
find Fix For 21% reset :
1.Test Cpu Only ...
2.Test Full
Benchmark go to 100 % without problem .
For Me this way solve reset forever .
Press Tanks if My Way help you
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
baconbeacon said:
So, my issue is as the title shows.
The A53 cores do not stop, and A57 cores only work like 0-1 core at a time, usually doing nothing.
Which causes my phone to be heating up whenever it isn't sleeping, sometimes drains battery even when charging at 2A.
I'm using E6533(dual sim version), and it happened when I updated my phone to 7.1.1(32.4.A.0.160) from 7.0.0(32.3.A.2.33) firmware with flashtool.
Yes, I've rooted my phone, but just for removing shutter sounds.
I tried to rollback to my TWRP backup, factory reset, rollback to 32.2.A.0.305, using custom ROM(lineage), quite everything I know, but nothing worked.
Does anyone have a clue of what might be the problem, and what might work?
Thank you.
Click to expand...
Click to collapse
did u tryed to install a custom rom? or a stock but flashing a kernel?
op3n said:
did u tryed to install a custom rom? or a stock but flashing a kernel?
Click to expand...
Click to collapse
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
baconbeacon said:
I was using stock ROM, but while trying to fix the issue, I've tried custom ROM too. Though nothing has changed…
Click to expand...
Click to collapse
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
op3n said:
i think is normaly to run even 1 cpu. to me is working permanently 2 - 2 from big, and 4 from little and battery is ok. is normaly to bicom hot our *****es z4; u want to say is permanently hot even is in standby or blabla?
Click to expand...
Click to collapse
Well, if that's normal, this shouldn't be an issue. Though I do wonder where's the big little concept gone.
Did it ever occur to you guys that it might be dynamic hotplugging and a specific configuration/setup is being used ?
Or is it in your case really being buggy and broken ?
You left something working in the background and monitored how the cores behaved ?
Using different apps ? (say: kernel adiutor [or kernel adiutor mod], EX Kernel Manager, CPU Z, etc.)
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
My situation has improved, so I'll update my situation, hopefully it'll help someone.
After updating to stock 7.1.1(without modifications), my phone got just very hot while the screen was on., consuming more than 2A.
Rolling back did solve the problem(becomes normal heat), but as for me, I chose to use lineage OS, which was great. The only drawback I'm having now is that the camera button's function isn't as versatile as the stock ROM, especially while opening the camera app from sleep state, is a bit unstable.
A great thanks for all of you guys for giving me advices.
I am out of things to try on this thing, I bought it used in February and ever since upgrading to Pie the phone will beginning shutting down during use, even while only watching youtube. Something is causing the cores to ramp up to 100%, it begins to warm up but not overheat and then shuts down usually around 70c I believe, no overheating message just straight cuts power. The only way to get it to power back on is to cool it down in front of a fan or car AC for a minute or so, then it will stay on and I can watch the CPU usage drop after a few minutes and then I can use it again. I have factory reset, cleared cash but the issue remains. As Android no longer allows seeing what is using CPU I have no way of trying to figure this out further. Any ideas?
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
I havent tried this, kind of terrifies me. I have touched firmware since my S3. lol kind of afraid it might shut down while doing this and brick it
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Click to expand...
Click to collapse
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.
drosenberg85 said:
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.
Click to expand...
Click to collapse
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.
MrMike2182 said:
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.
Click to expand...
Click to collapse
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?
drosenberg85 said:
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?
Click to expand...
Click to collapse
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.
MrMike2182 said:
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.
Click to expand...
Click to collapse
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out
drosenberg85 said:
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out
Click to expand...
Click to collapse
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..
butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
Happy Thanksgiving bro!
Same to you bro
Sent from my SM-A205G using Tapatalk
MrMike2182 said:
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..
Click to expand...
Click to collapse
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol
drosenberg85 said:
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol
Click to expand...
Click to collapse
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?
MrMike2182 said:
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?
Click to expand...
Click to collapse
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol
drosenberg85 said:
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol
Click to expand...
Click to collapse
Then get away from that version just go back one lol.
MrMike2182 said:
Then get away from that version just go back one lol.
Click to expand...
Click to collapse
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?
drosenberg85 said:
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?
Click to expand...
Click to collapse
Yep definitely hardware! You need a new phone or board!
my phone heats up during normal use and while charging. And dhuring playing games it gets upto 44°c idk its common or something is wrong with my device is there any solution to it.
Same here bro.did you find any solution.???
yea even I'm facing the same issue Indian variant
No bro could not find any fix, but having a small hope i removed the cache partation but still it does not work.
Sadish000 said:
No bro could not find any fix, but having a small hope i removed the cache partation but still it does not work.
Click to expand...
Click to collapse
yea even i tried that long back but i doesn't work maybe only solution is to do a factory reset
hi! did any one found any solution? after May security update, i find my s10 (Indian variant)heating more even on normal usage.