Hiya.
Since today in the morning I keep getting random freezes followed by reboots.
At first I thought it was the GPUOC, so I got back to the kernel stock 446 from 520 MHZ.
Reboot.
Then I returned to the stock max 1.3 GHZ CPU
Reboot.
Then turned on fsync.
Reboot.
Reflashed ROM + Kernel.
Reboot.
Yelled at it.
Reboot.
I am currently running at ParanoidAndroid 3.0 and the m-kernel r37 .
Something I can do against those reboots?
Related
So I rooted my tf using nvflash, installed the 1.4 prime US version, then installed the clemsyn-blades version 8a kernel. In the beginning, everything was fine. Overclock my TF to 1.6ghz and everything was running smoothly. recently, installed the clemsyn newest kernel version 11. Installation went smoothly but the next day I started to notice my tf freezing. I had to reboot a few times because it keeps freezing. then when I check SetCPU, I notice my cpu cannot reach 1.6ghz no more. I set the governor to performance and still can't hit 1.6ghz, only 1.4ghz. I reinstall everything all over again but still show the same results. Does this mean there's something wrong with my cpu?
try cpu master. if that don't work maybe your rd just can't bangle 1.6
Hi everyone,
I got this Rom installed + Glados 2.3 Kernel on my I9023EU.
This combo solved:
-ICS increased battery drain: lazy governor, 100 mhz min freq
-lag in app drawer
Issues:
-font installed not properly displayed
-random reboots (no OC)
any hint?
EDIT:
-WiFi staticIPs not working ... when asked for subnet mask, only the last segment is to be inserted. Then it works..
EDIT 2:
-upgraded to GlaDOS 2.4
NEW ISSUES (not related ti the upgrade, i dare to say):
-BLN BLINKING: if when unlocking, lights are in the off-phase of blinking, the remain off.
-DSP MANAGER 2.0: Equalizer is not working
Thanx a lot
No problem with the ROM NexusBeam 4.1.0, but I didn't change the kernel...
Maybe, if i have any time this weekend, I'll try to install Glados 2.3 Kernel.
I will report issue(s) if I have some.
Try to use the new matr1x kernel
anyone of you heard about wipe cache/dalvik/data
even AFTER having flashed NB4.1. ?
someonedon'trememberwho said this solved some probs..
No problems with Nexus Beam, the best rom at all (imho).
Now i've tryed to use Glados 2.3
Have you wiped data/factory and cache before installing Nexus Beam?
pastikk said:
Have you wiped data/factory and cache before installing Nexus Beam?
Click to expand...
Click to collapse
yep. and someone says also after... what about it?
I encountred some random reboots while making a call with 3G enabled.
Random reboots seem to have disappeared after reinstallation. This time I flashed nb4.1 and glados2.4 at once, without reboot inbetween.
Still short battery life and no correct fontinstall
Sent from my Nexus S using XDA App
Hey all,
I'm on 4.4.2 stock with Xposed (gravity box).
Using Trickster mod and have tried both M-Kernel (latest) and Faux kernel (latest).
With both, after using the tablet for 1-2 days, the max frequency seems to be stuck on 666mhz (for M-Kernel) and 700mhz (for Faux). I have to manually make it 1.2ghz and apply. Turning screen off/on doesn't fix the problem either. I've tried to remove trickster/clear data but same results. I think it's the same with other kernel manager apps too.
Does anyone have any idea what could be causing this? It's quite annoying
Hi. I have random reboot problem on my note 3. Screen freezes (gaming, settings, menu or idle) and reboots when i have installed ANY costom ROM or Kernel. I noticed screen freezes mostly when Synapse app is installed with Kernel, second notice phone freezes then my favourite PegasusQ governor is applied. Phone was working perfectly without any issue on official 5.0 with Minimalistic kernel, no issues about whole year (no synapse). Phone was two times in warranty. First time they instaled stock KK firmware and replaced micro usb port (that whole part in note3 ) ?? , second time simply installed stock Lollipop. And then everything starts from beggining...
Yesterday I zipped all LOGS with SysLog app when random reboot appeared (i was on synapse changing governor from interactive to precognition). If it helps reboot happened yesterday after 02:00 hour.
Zip here: https://www.dropbox.com/s/a3svst1yhhtj23u/2016-02-08_11.20.zip?dl=0
Warranty didn't fixed that so I hope real developers will detect what couses this RR.
Sorry for bad English
My phone is now on Phronesis ROM, CivZ_Xplorer-9005-Rev5.0.3-note5port Kernel
Do you have an SD card installed? If so remove it from the phone and see if the phone is stable
I was using external sdcard on official 5.0 lollipop with minimalistic kernel and phone was working without random reboots whole year.... Reboots only on costom roms and kernels with synapse.... I never used costom voltages and higer cpu freequency than 2.5 ghz... no gpu overclocks more than 450mhz, never played with performance governors, no overheating...
Reflash different stock firmware it worked for me
Sent from my SM-N900 using Tapatalk
bump
??
Hello, I flashed CM 12.1 and sometimes the system hangs and reboots, the phone is rather in good condition and it was stable on stock. Any ideas?
Model: SM G900F
CM: Latest Version - Not Nightly
Try changing the kernel gouvernor to interactive. If its on interactive try ondemand or else. If these tips don't help, try underclocking your phone or try to change the kernel.
Never done that is it noob-proof?
Okay, I have changed it to ondemand from interactive.
Mine reboots even if nothing is being touched I wiped and re-flashed and same issue, gonna check and wait for the results of governor change.
Update : rebooted after few minutes of changing.
Dhammadassi said:
Mine reboots even if nothing is being touched I wiped and re-flashed and same issue, gonna check and wait for the results of governor change.
Update : rebooted after few minutes of changing.
Click to expand...
Click to collapse
Get a logcat of the reboot.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Changing kernel governor to performance seemed to do the trick I will make a catlog in case of a reboot.
Update: The phone rebooted on it's own again.
Here's the logcat I ran.
Dhammadassi said:
So If I have logcat running and the mobile will reboot will the information be saved ?
Click to expand...
Click to collapse
If you're doing it over adb from another computer/device yes it will. Through catlog on the phone I'm not too sure
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
If you're doing it over adb from another computer/device yes it will. Through catlog on the phone I'm not too sure
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I do not know if I performed it properly I ran adb catlog -v long than saved to file and uploaded, I do not know if you want me to keep it running until it reboots but gonna post that log anyway. If it doesn't have any good information I will run catlog overnight until it reboots. I've tried ondemand CPU governor and performance on ondemand I've got 5-6 screen freeze then reboot and the phone was taking a long time to boot so I took out the battery and it booted normally.
I'm thinking about dropping CM 12.1 and swappin' to Ressurection ROM to check if it will work possibly ?
Update: Same issue as CM 12.1 rebooting as well so it's not the issue of a ROM. Any suggestions ?
http://forum.xda-developers.com/galaxy-s5/orig-development/kernel-amplitude-kernel-0-1-klte-t3018492
Installed this kernel but boot loop.
Update : Installed http://forum.xda-developers.com/gal...ar-googy-max4-kernel-1-0-tw5-linux-3-t3048773 and it runs fine but the phone also restarted I noticed it must be an over-heating issue because when I install a rom the phone is warm and reboots.
I fixed the issue by downloading Googy's kernel and changing the maximum freq to 2.3Ghz, I am not sure what was happening but it seems that the kernel was forcing a setting that my phone did not like on the CPU and after changing the CPU freq to it's maximum as the specification of the CPU shows stopped the phone from rebooting.
Update: Also the phone rebooted once again when I set the CPU Governor from Interactive to SmartMax then back to Interactive and no reboots.