Database Info

Anyone else with problems like this?

Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?

leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.

could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.

Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect

Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app

same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.

Are you using 4x5 Rosie?
Sent from my VENOMized HoxL

area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .

You could try increasing the voltage.

ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.

just stopped using a custom kernel. i stopped using them cause of freezing issues.

[Bug] Screen doesn't turn off

Hey. In latest nightly versions I noticed that screen doesn't turn off automatically after specific time. Even if "15 seconds" is set it's still permanently on. I even clobbered my homemade build to make sure that nothing is wrong on my side.
Of course issue persists after full wipe and I'm talking about automatic turn off because if you hit power button then everything works fine.
Did anybody notice it as well? i9300 here.

JustArchi said:
Hey. In latest nightly versions I noticed that screen doesn't turn off automatically after specific time. Even if "15 seconds" is set it's still permanently on. I even clobbered my homemade build to make sure that nothing is wrong on my side.
Of course issue persists after full wipe and I'm talking about automatic turn off because if you hit power button then everything works fine.
Did anybody notice it as well? i9300 here.
Click to expand...
Click to collapse
Hmm, I'll check this again. No problems here last I checked... This is with the device unplugged?

Entropy512 said:
Hmm, I'll check this again. No problems here last I checked... This is with the device unplugged?
Click to expand...
Click to collapse
Yes it is.
I built clobbered build from source and also I make my best to blame everything else before I blame the base . However this time really device doesn't turn off automatically, both after first boot and after value set. Everything else works great.
I'll try to find a root of this issue. However screen off should work as long as rom works, am I right?

Consider this report as closed. Suddenly build compiled ~15 minutes ago started working properly .
Thanks for your time Entropy.

It's a bit odd - I DID have an issue this morning where I couldn't even turn off the device with the power button for 20-30 seconds after boot.
The issue disappeared, never to return...

No idea what this problem is? anybody able to offer advice?

I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated

It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk

Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?

nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that

hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol

ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen

OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks

One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk

ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.

Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.

Sleep of Death befalls my SGN 12.2

Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?

To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.

ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).

Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.

Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.

Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?

Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.

Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.

random freezes on my s6 edge

hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???

anyone??? ☹

zinou111 said:
hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???
Click to expand...
Click to collapse
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.

tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?

tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
It happened again, this time the device wasn't hot, no apps on background, no gaming, nothing. i was just on home screen swiping looking for an app, it suddenly froze. with those glitchy lines, rebooted itself with white solid LED light. i didn't use it for like 10min.. i came back again, unlocked it, swiped up for apps menu.. BOOM, froze again with those glitchy lines. this time it didn't reboot, it blacked out after 5sec.. i tried different button combinations to turn it on again, no luck. i plugged in the charger and waited for 2min, nothing. then i got into download mode [warning screen] (while plugged). i pressed the vol- button to restart, it booted up normally. now I can't really use it cause i don't want it to get worst. btw, sometimes when it freezes & reboot itslef, All settings are reset to default.
Any suggestions on what to do?

zinou111 said:
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?
Click to expand...
Click to collapse
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.

tiktakt0w said:
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.
Click to expand...
Click to collapse
okay.. but why it sometimes happens while doing nothing... and sometimes it doesn't freeze at all even while gaming for hours...
one more thing, when i shake thr phone near my ear, i hear something like (tick tick tick...). i taught that maybe that's it. but i asked my friend who has an s6e too (G925T) he said that he has that sound too when he shakes it, but doesn't encounter any problems with his phine... soo??

What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.

Bryan48765 said:
What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.
Click to expand...
Click to collapse
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??

zinou111 said:
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??
Click to expand...
Click to collapse
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.

Bryan48765 said:
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.
Click to expand...
Click to collapse
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.

zinou111 said:
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.
Click to expand...
Click to collapse
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.

Bryan48765 said:
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.
Click to expand...
Click to collapse
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.

zinou111 said:
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.
Click to expand...
Click to collapse
Hello @zinou111 how has your phone behaved after what you did? I am currently having the same issues you had and I'm looking for a solution.
Yours is the only hope after a couple hours of searching.

really? same symptoms as mine?
well... i didn't do anything at all... I turned it off and threw it for like 4 days... and last few days, i was bored, so i got it back and turned it on.. i faced this problem only 4 times within this week... i didn't do anything..
it used to be +10 times a day... now its just gone i think & i hope... it didn't freeze last 3 days & it works flawlessly!
i hope this can help you

Solution! And Cause!
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!

ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again

Yes I can safely say...
zinou111 said:
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again
Click to expand...
Click to collapse
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!

ArkPly said:
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!
Click to expand...
Click to collapse
okay man! that was really helpful! ill try it and keep u up to date!
thanks alot bro!

ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
Hello
I dont understand this : Upvolt all values under 1000mHz to 800mAh in both big and small cores
Maybe have you a screenshot ????
thx