I'm watching YouTube at night and it suddenly freeze for 5 sec and then reboot itself and stuck on Samsung GALAXY NOTE 4. And nothing happens after that, it just stuck there. I can't go to recovery mode but I can go to download mode. So what's Happened to my phone ?
So I was going out today and be nice with people. I'm so sad about my dog just died few days ago and then I went back home tried to open it one more time and its working again like the new one I'm just shock and don't know what's happening.
Could be that your device was overheating and need to cool off before you could use it....
Look at the 100% fix thread in q&a section. Its typical of the emmc error. A known problem when the chip that loosens from the mainboard. It's pretty easy to fix.
Maybe is problem in Cpu Governor, if you use custom ROM like I ,and if you change in kernel auditor Cpu governor, it's happens to phone reboot if you not choose the right one . its happens to me a couple of times until I didn't find the perfect set up for kernel.
Related
I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?
had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.
Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though
If it was a PC you would say its overheating .
jje
Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why
quick answer. Reflash the phone .
I guess reflashing and removing some dangerous apps will be good for you phone.
Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it
Here's the rundown ...
Last night I was playing a little Nimble Quest before bed. I started to get tired so I quit out of the game and as I was turning the phone back into portrait mode the screen went black (still on) and seemingly froze. I let it chill for a bit, then it vibrated and I heard my notification sound. I let it go again and a few seconds later it did it again (vibrate/sound). This happened a couple more times before I decided to hold down the power button and attempt to shut it down. After holding the power down for about 5-6 seconds, the phone rebooted itself. It stayed on the CM boot screen for what seemed like 5 minutes--long enough for me to think it was bootlooping. Finally I saw the screen brightness lower and the lockscreen came up. My background was there but all of my homescreen icons were gone. All of my apps were there, but all of the data was gone. Rather than deal with it at 1AM, I put it on the charger and let it go.
This morning I did a full wipe and restored a nandroid backup from the 20th. Everything seemed back to normal. When I got to work I reflashed the CM10.1 stable that just came out and faux's mainline 16 kernel, effectively bringing my phone back to the state it was before last night's drama. I got up from my desk to get coffee and when I returned I noticed my phone was on with a yellow screen that read:
HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
There was some other stuff too but I decided to Google it before I did any of the things listed on the screen. I found a post in the Optimus G forum describing the same thing. One of the members said to hold down the power button until the phone shuts down, then restart and everything would be cool. No one else in the post seemed to see it as a big deal.
I went ahead and did what was recommended and my phone seems to be OK. Nothing weird has happened since then.
I guess my question is: what could've caused this? Is it my ROM/kernel combo or is it more likely the actual hardware? Should I be alarmed? My phone is less than a month old. Any help would be appreciated. Thanks!
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Johmama said:
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Click to expand...
Click to collapse
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
daewond3r said:
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
Click to expand...
Click to collapse
Hm, this is an interesting bug indeed. I guess first, I would try
illhangon said:
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
Click to expand...
Click to collapse
.
If that doesn't work, I would at least try a different kernel. If that does nothing, I would try changing ROM, and without restoring any apps or data. Is the only time you can get this problem with that specific game? If so, the game itself might be a faulty-coded game. If you get this problem elsewhere, try messing around on the newly-flashed ROM in the other areas you can replicate this. If you can't get it to soft-brick, try downloading that game and playing it on the fresh ROM/kernel. If you still get it, try flashing another kernel again. Basically, try 2 different ROMs, each with 2 different kernels, with and without Nimble Quest. Might seem like overkill, but I'm just trying to completely eliminated ROM/kernel problems, and any app problems. If none of that works, I really don't know what to say, maybe it really is a hardware issue.
Tonight, I'll try downloading Nimble Quest and playing it for a bit to replicate the issue. Is it just playing the game in general that crashes, or is it specific actions that you've found that really trigger it? From what I've read, the issue seems to pop up when you quit the game. I assume that just means hitting the Home key? I've read the reviews on the Play page and can't find one that complains about system-wide problems. I have a feeling it isn't the app, but it doesn't hurt for me to try and replicate the issue. If I get it, that means it's either the game, or specific settings both you and I share, and we will need to dig a little deeper to find out what it could be. Anyway, I'll mess with it a bit tonight and get back to you tomorrow if you haven't already found the cause/solution.
It happens every time the modem crashes. Earlier it just used to reboot without giving the message.
Sent from my Nexus 4 using xda premium
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
As many others here I started to have mmc_read and mmc_write errors with my N910F plus freezes and restarts or no boot. For me is another case of programmed obsolescence from our beloved Samy as I previously had with the Note 2 chip bug. I supposed that the problem comes from overheating (from a short-circuit or a failing transistor) and I got confirmed. The phone cpu and gpu go up to 90-100deg Celsius. In case you still want to keep your phone and save money until the Note 8 is out here is a possible workaround:
- In case you get mmc errors when flashing with odin you have to take out the battery an keep them both somwhere cool for 15 minutes. Then flash immediatly after starting in download mode, before is heating again.
-If you managed to boot and root you can install Kernel Adiutor or something similar and keep the processors at a max frequency around 1000MHz .
For me it worked and after 2 weeks of testing all kinds roms with repartitioningn, nand erase etc. I have a working if little less performant phone for a week now.
Edit: Device Control is another app that seem more stable and it has a thermal dedicated control over CPUs. Even with intensive use the phone doesn't freeze now. It still needs to be cool to boot.*I also flashed RamKernel and I don't know it KernelAdiutor works with factory kernel.
Edit2: Wakelock app with level 4 setting > 3 days and going with no lag and no restart. So maybe all above is wrong...
Hello XDA
I have the Note4 N910F, it start to random reboot tow month's ago
i decided to look why is that happen i noticed it reboot when its get hot
i installed the Device Control app it show the CPU temperature 84C° TO 86C° with out doing anything in the device so i decided to UC The max CPU frequency from 2649MHz to 1958MHz the temperature now never across the 75C° and its never reboot anymore
but when i reboot the device it go through the boot process and reboot when the home screen appears i have to cool it with cold air to boot normaly so i can UC the cpu again
why is that happening and is there away to UC the CPU permanently?
by the way its the same on stock firmware and the same on other roms
Thanks XDA
AOWS said:
Hello XDA
I have the Note4 N910F, it start to random reboot tow month's ago
i decided to look why is that happen i noticed it reboot when its get hot
i installed the Device Control app it show the CPU temperature 84C° TO 86C° with out doing anything in the device so i decided to UC The max CPU frequency from 2649MHz to 1958MHz the temperature now never across the 75C° and its never reboot anymore
but when i reboot the device it go through the boot process and reboot when the home screen appears i have to cool it with cold air to boot normaly so i can UC the cpu again
why is that happening and is there away to UC the CPU permanently?
by the way its the same on stock firmware and the same on other roms
Thanks XDA
Click to expand...
Click to collapse
Hello!
I'm afraid that I can't really tell you why this is happening. I strongly think of a hardware issue.
But I think I know a way how to prevent your phone from overheating while booting. You mentioned the Device Control app on your post, so let's start with my first suggestion:
Is there an option in the app like "apply settings on boot" or anything like that? If yes, try to enable this option and reboot your device to proof if it worked.
If Device Control does not support this feature, I recommend you Kernel Adiutor. I used it for over one year and also used the "apply settings on boot" option that worked like a charm for me. It's basically the same application, just with another design, another name and so on, but practically it does the same.
Vygravlil said:
Hello!
I'm afraid that I can't really tell you why this is happening. I strongly think of a hardware issue.
But I think I know a way how to prevent your phone from overheating while booting. You mentioned the Device Control app on your post, so let's start with my first suggestion:
Is there an option in the app like "apply settings on boot" or anything like that? If yes, try to enable this option and reboot your device to proof if it worked.
If Device Control does not support this feature, I recommend you Kernel Adiutor. I used it for over one year and also used the "apply settings on boot" option that worked like a charm for me. It's basically the same application, just with another design, another name and so on, but practically it does the same.
Click to expand...
Click to collapse
Hello
Thank you for respond
The Device Control doesn't have Apply On Boot so I used the Kernel Adiutor You recommend
It do have Apply On Boot and i switched it on but It didn't make a different because it apply the setting after the boot process complete not before or during the boot process
you mentioned a great app thank you for that, the thermal option is useful it turn of cores if the CPU Temperature Get higher than a temperature i chose which i set to 50C°
i will learn to live with the (Cooling during booting) what really bothering me is the rebooting when i am on the middle of a call or working or playing on the phone
now it's solved with Kernel Adiutor
here is a picture of the CPU and GPU temperature before changing frequency and setting the thermal control
seconds after booting
______
and this after make changes
Thank you
AOWS said:
Hello
Thank you for respond
The Device Control doesn't have Apply On Boot so I used the Kernel Adiutor You recommend
It do have Apply On Boot and i switched it on but It didn't make a different because it apply the setting after the boot process complete not before or during the boot process
you mentioned a great app thank you for that, the thermal option is useful it turn of cores if the CPU Temperature Get higher than a temperature i chose which i set to 50C°
i will learn to live with the (Cooling during booting) what really bothering me is the rebooting when i am on the middle of a call or working or playing on the phone
now it's solved with Kernel Adiutor
here is a picture of the CPU and GPU temperature before changing frequency and setting the thermal control
seconds after booting
______
and this after make changes
Thank you
Click to expand...
Click to collapse
You're welcome!
At least I was able to help regarding the phone's random reboots due its heat development while using it.
I something comes to my mind that could help with preventing the phone from overheating while booting, I'll let you know.
But for now, I'm happy you can use your phone under normal conditions again. Have a nice day!
Vygravlil said:
You're welcome!
At least I was able to help regarding the phone's random reboots due its heat development while using it.
I something comes to my mind that could help with preventing the phone from overheating while booting, I'll let you know.
But for now, I'm happy you can use your phone under normal conditions again. Have a nice day!
Click to expand...
Click to collapse
It's almost normal it just have fever hope it'll recover soon
You have a nice day too