[CyanogenMod 10]No sound after a while - Eee Pad Transformer Q&A, Help & Troubleshooting

I downloaded CM10 from here.
http://forum.xda-developers.com/showthread.php?t=1858295
But after a while, usually several hours of standby, when i wake TF101 up, there will be no sound, and I have to reboot it to make the sound back.
Does anyone have the same problem?
Thx

I reverted back to stock because of this (and other issues). It's really annoying to reboot just to get audio back.
See:
http://forum.xda-developers.com/showthread.php?t=1523358
http://forum.xda-developers.com/showthread.php?t=1884295
http://forum.xda-developers.com/showthread.php?t=1920025
etc.. lots of people having issues. I believe an update fixed it, though I'm not sure.

figure it out,
there is an issue with the Kernel or the CPU Governor. to fix the No Sound Issue (on calls or on any type of sound) just do the following:
1. under settings, go to performance
2. chose processor
3. set the "set on boot" which will restore processor settings on each reboot, thos will make the phone reset the processor settings.
4. reboot
alternative :
I know that changing the Kernel can also do the trick, but this way is less dirty
good luck

Related

HELP: Phone locks up and dies at random

I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.

[Q] Scroll lag

Does anyone get this; open something with a long list (e.g. gallery), then scroll quickly by flicking the list up/down and do it so the list keeps scrolling. I get lag when doing this, and its not smooth (believe the effect i'm after is called "buttery..?"). What ends up happening for me is that the scroll stutters and it ends up opening a file in the list that i'm scrolling.
I get this with a fair few ROMs and have always lived with it until today when I decided enough is enough and I need to man up and ask for help, plus I really want to use the Viper S rom effectively as the comments about this ROM suggest that this should not be happening.
I've wiped (factory reset in recovery then wipe all excpet sd, then cleared cache and dalvic PLUS i also select the wipe function in the viper aroma before install) and installed the ROM 3 times. Strange thing is, i don't get the problem after the first few restarts (not FC but me restarting it) but then for no reason at all, this lag issue appears (i have yet to restore titaniaum apps/download any apps at this point).
Sometimes it happen.
If you can't live with it, you can try the following:
a. Change the governor. On demand or lag free will offer you better performance. (affecting negatively your battery life)
b. Overclock a bit.
c. Change your kernel. Sebastian's seems to be working nice.
d. Use system tuner to check the apps that auto start and use your resources.
I hope it helps.
Regards
Sent from my HTC Sensation

Revelation Rom random reboots

Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.
Use 1188 mhz max cpu frequency, no cpu control software, I don't have reboots.
Sent from my HTC Sensation Z710e using Tapatalk 2
I have already tried to set 1188, 1296 and 1512 during install, all options gave me the same results, so i think it is not realted to CPU max freq.
I don't know if we have the same problem, I have my sensation turning off randomly for no reason what so ever. The weird thing is when it is plugged in, it doesn't turn it self off. I already brought a new battery so shouldn't be that. I also tried putting some paper in the battery section in case there was a lose connection. Played around with software, got nothing changing ROM, changing CPU freq, changing radio... nothing helps. I think mine problems are random reboots + shutdown, so it is not all ways the case it has rebooted. But when it does do the random reboot, it is often when I am trying to wake the device. I have no idea when it shuts down since when I try to wake it, it was shut down. Then I had to hold the power button to turn it on. Lastly, I think i get mostly shutdown.
Well, i don't know what is causing your problem. If you change between different roms/kernels/firmwares/radios/etc. and problem always exist, it can be hardware related.
Mine only appears on Revelation rom, and i always get the full reboot (no soft reboots or shutdowns).
Lubosz said:
Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.
Click to expand...
Click to collapse
These reboots are caused by kernel 3.4.10, not ROM, so we may continue this discussion on my kernel related thread. Reboots occurs only on few devices. I received many kernel logs, but I didn't find the reason, errors are different for each user.
The 12th day on the Revelation ROM and not a single reboot.
Also writing here due to the 10 post's rule eek
Will go back to the Revelation thread after this post because I really like the SebastiamFM's work and I have none of there mantioned problems (maybe one or two).
I was havign problems on the begining thoe... i couldnt startt the phone. It rebooted when I had to insert the PIN code or before the Sense even managed to load. Then I formated everything (including the SD card) to eliminate any "remains" of previous ROM's and i set the GPU on 300 and the MAX freq to 1520 and from than till now not a single lag.
Lubosz said:
Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.
Click to expand...
Click to collapse
Try using performance governer instead of ondemand.
Happy to help.
You could try reseating the battery or securing it a bit tighter, some users have reported reboots because of the battery being somewhat 'loose'.

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

Categories

Resources