Related
Hello,
For the last 6 months or so, I've experienced many lag issues with my device. At the begging, I had a CM11 ROM installed on my phone, so I decided to revert back to the V20B official european firmware because I thought those lags were related to the ROM. But nothing changed, and as of today I still have responsiveness issues.
This lag issue appears from time to time, and makes my device basically unusable. It feels like the whole CPU is hogged by an application, or like I underclocked my device to 53mhz on purpose. During these lags, trying to wake up my device will take up to 5 seconds, and navigating the main screen will be nearly impossible. Also, my phone will get very hot which would imply that my CPU is indeed used by an application. Sometime the issue will disappear by itself after a few minutes, but I usually reboot the device which temporarily fixes the problem.
I have tried to disable LG MLT, and I think it helped but the lag still occasionally occurs.
I don't really use third party applications either.
I think these lags might be related to the Google Chrome browser, but it doesn't make any sense as it is an official app.
Anyway if any of you have an idea on how to fix the issue or how to find the application/service/whatever hogging the CPU I'd be grateful
Thanks !
I did experience such lags in CM11 after a few days of usage.But talking about stock, these freezes sound bit weird.You might want to check your installed apps.Download watchdog lite from play store and let it watch on agressive mode.Also check if your phone is hot when these freezes occur, might be the throttling kicking in.
I also experienced this kind of lags due to bad gapps I had installed back in the day, though stock ROM comes with gapps so it's not that.
Thanks for your reply,
I installed Watch dog lite and I'm now waiting for an alert. I hope it will give me the name of the culprit
If you are rooted which i assume you are. You can try app from playstore called "lagfix" (fstrim)
Sometimes really helps. Sometimes it doesn't
So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!
ShrekOpher said:
So I had been running the same ROM without any issue for almost 18 months. The note 4 is my backup phone so I do not mess with it too often. I did use it almost every day though for a media remote for my family room. However the other day the phone rebooted after seeing a weird error message pop up. It was not like any I had seen before, looked like an error related to the hardware.
Now no matter what ROM I flash onto it I it struggles to boot. If it does boot the ROM is really slow and choppy and often freezes or gives me the black screen of death and I have to pull the battery. I have tried multiple ROMs both TW and AOSP base and all are having the same issue. Even using ODIN to go back to stock did not fix the issue.
Is it possible the phone just had a hardware failure and is toast? Just curious if anyone has had this issue and if they have any ideas on how to fix it.
Thanks!
Click to expand...
Click to collapse
Many have had similar issues, for example:
http://forum.xda-developers.com/note-4-tmobile/general/marshmallow-updates-issues-t3415914
http://forum.xda-developers.com/note-4-tmobile/help/major-phone-issues-reboots-freezes-t3440870
A proposed solution has been to downgrade to LP, although some people have reported it not fully fixing the issues.
So recently I've been running the smurf kernel to play games like pubg with OC. But all of a sudden my note began glitching and caused graphic glitches. I thought that this might just be in game but it happens when I exit. When I exit usually the display just goes black but the digitzer underneath is still working. Any ideas on what's going on. Oh also. I thought this might be a smurf kernel glitch so I switched to notorious but it just repeats. This happens at random too . Screenshots.
Skulldron said:
So recently I've been running the smurf kernel to play games like pubg with OC. But all of a sudden my note began glitching and caused graphic glitches. I thought that this might just be in game but it happens when I exit. When I exit usually the display just goes black but the digitzer underneath is still working. Any ideas on what's going on. Oh also. I thought this might be a smurf kernel glitch so I switched to notorious but it just repeats. This happens at random too . Screenshots.
Click to expand...
Click to collapse
Does it happen in other games? Graphically glitches such as that typically means that the GPU is not capable of process the visuals at the settings requested and bottlenecks. At least when it comes to PC.
Sent from my SM-N950U using Tapatalk
GPU artifacts. Your phone's GPU is overheated.
It doesn't happen in other games. Also, are you sure that it's just an overheating issue than a defect?
Try reinstalling the stock OS back onto your device. There is a chance that the GPU drivers may have gotten corrupted
Skulldron said:
It doesn't happen in other games. Also, are you sure that it's just an overheating issue than a defect?
Click to expand...
Click to collapse
Most likely. The common factor is artefacts during PUBG. Since the issue doesn't occur during other intense games (if you've tried others), then PUBG is the factor causing the issue.
Sent from my SM-N950U using Tapatalk
Ok so an update on the situation. Switching to a different kernel doesn't appear to help at all. In fact the situation can get a little worse at times. It doesn't happen instant but can happen at random times. It's spread to other games but only if I play the game for a while (2 hours usually). Honestly don't know what to do at this point. Usually when you overheats it downclocks automatically right? So I doubt it's overheated. I am about to wipe everything off and start new. Maybe then my problem will disappear. If anyone can please give me the direct cause of this error I will be forever grateful
Skulldron said:
Ok so an update on the situation. Switching to a different kernel doesn't appear to help at all. In fact the situation can get a little worse at times. It doesn't happen instant but can happen at random times. It's spread to other games but only if I play the game for a while (2 hours usually). Honestly don't know what to do at this point. Usually when you overheats it downclocks automatically right? So I doubt it's overheated. I am about to wipe everything off and start new. Maybe then my problem will disappear. If anyone can please give me the direct cause of this error I will be forever grateful
Click to expand...
Click to collapse
I would do a full wipe, go back to latest stock firmware with Odin, and then test from there. If the problem persists, then I think it's safe to say it's hardware failure of some type, which would require repair.
Any updatess?
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Skulldron said:
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Click to expand...
Click to collapse
Thanks for the update, glad to hear things have improved! PUBG is kind of buggy overall, so those new minor glitches could possibly just be the app itself. Keep testing and see, but hopefully everything goes smoothly
Skulldron said:
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Click to expand...
Click to collapse
https://www.redmondpie.com/pubg-mob...s-fix-lag-more-heres-how-to-configure-it-all/
Decent write up of how to fix some of PUBG glitches and lag. I haven't tried that game but could possibly help.
Ok everyone! I believe the issue is solved!. A reflash of the stock ROM appears to have fixed the glitches. Even on low battery it doesn't seem to affect the device so I'm going to put it down to corrupt gpu drivers. Thanks everyone for your help, y'all have been awesome.
Are you doing Dream UX for the galaxy tab s2. If you are, I have a SM-T813 and I am willing to test on it since you do not have one for this device and I don't expect for Samsung to release 8.0 Oreo on it.
Please and Thanks
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!
Hi,
first of all sorry for my bad english and screenshots with german text .
The situation:
I have a total of two Tab S2 (T-813). The first is 4 years old, the second is less than 2 years old. The newer is now causing problems.
The reboots occur:
- When using the tablet. Definitely with a high load, but also sometimes with only light loads
- When it is charging
- completely random
Edit1: reboots are not related to the battery percentage
Edit2: never experienced a reboot while in TWRP.
I didn't really find anyone with the same problem on the Internet. It is not a boot loop. Sometimes you can use the tablet for hours/ days. Then again not at all, because it starts again after a minute. To narrow down the problem, I formatted both tablets and installed the same lineage version and firmware. Since it restarts, log files are unusable, right?
Is there any way to narrow down the error?
I suspect overheating, but I would like to know if I have any way to isolate the fault exactly. Maybe there is also another (hardware) forum, which can help better in this case, then I would also be grateful for a tip.
I would have no problem opening the tablet. I've already done this with my smartphones.
Thx for your time.
Solution:
It is an overheating problem if you have exactly the same problems as I had.
You can test it simply like this: fill a plastic bag with cold water and some icecubes. Use it like a pillow for your tablet so it can rest on the bag while you use it. I had no problems at all while doing this.
I send it to Samsung and they repaired it.
It's just as new now.
I actually have the same problem, just only when its at 15 or less battery
Hi.
Well, it sounds for me like a different problem, cause it's battery related. My battery is fine and I have reboots not related to battery status.
Have you tried anything (factory reset, newest lineage and firmware,...)?
Hi,
same here. A SM-T813 running LineageOS that started with random freezes and reboots about a week ago. Sometimes I can use it for about half an hour without problems, next time it reboots while rebooting ...
Seems to be completly random, only thing I noticed that it never reboots while in TWRP.
Cleared and reinstalled LineageOS, but didn't change anything. First time rebooted while still in the setup wizard, next time I could finish the wizard and install serveral apps before the next reboot.
Maybe a problem with the memory?
Yes, that is exactly the same.
I never experienced a reboot in TWRP. No problem with reinstalling lineage.
But while reinstalling Android, it reboots while configuring and while reinstalling apps.
The last days I could watch Amazon prime every evening. Now it reboots after a minute even without using it. I shut it off and hope it will work this evening again.
I have the same issue, sent it in for repair asked to flip battery and swap mainboard. Got it back. Worked a few days, then had random reboots again. I am 100% sure it is a battery issue, and when you get under a specific voltage, maybe when it gets under 30% or so, the chance for reboots rise dramatically, with high cpu or flash memory usage. It happens more often when doing a update in Google Play store for example. So totally have no idea, if Samsung flipped the battery or not, but this was my last Samsung product ever. I would assume there is an issue with too much current drain and then it reboots, and the battery used in them are not designed for the units properly.
same to me. i was on stock rom. never root or anything. and got random reboots most of them when i open google play or google chrome. now im on lineage and same. also i notice that the tablet didnt reboot until i install gapps. and the tablet never reboot on recovery or TWSR. reboots on high or low battery. and if it was overheating maybe the tablet will reboot on recovery. dont know its weird. i will try lineage with out gapps to see what happend.
just testing lineage without gapps no reboot. run browser and netflix with no problems. then i install youtube from aptoid store. and reboot start again. o unistall youtube and no reboot for now.
Same here. I have random reboots but also wifi disconnections (unable to reconnect until i reboot the device)...
Not evident cause...
Someone got a solution for this?
Have the same problem on my T813
You can find the solution for the problem I described at the end of the first post.