Hello. I'm running Cyanogenmod 10.1.0-RC5 on my maguro device, and franco-kernel r378. I've been experiencing random reboots, sometimes as often as 2-3 per hour. The phone doesn't even feel warm when it happens. Sometimes I'm using it, but sometimes it's just sitting there doing nothing and it reboots anyway. I've uploaded the last lines of my last_kmsg here, to see if any of you can help me figure out how to solve this annoying issue.
Thank you very much in advance!
Ivan.
I have the same setup no reboots. Do a clean install. Fix per,missions after installing Franco kernel. I have on demand and bfq. Stock speed' and don't use trickster mod
I did a clean install. I'm running the on-demand governor too, and 'deadline' instead of 'bfq' scheduler. I fixed permissions as well, I didn't change the CPU speeds, and I have no idea what the trickster mod is
I might add that i was having this same random reboot problem even with the CM stock kernel.
Any info from the last_kmsg file uploaded?
Thank you!
Best regards,
Ivan.
Small update: I did a fresh ROM install, again. I'm running the stock CM kernel, with the default parameters for CPU speed, scheduler and governor. The problem remains.
Please see an updated version of last_kmsg here.
Try to reflash stock. If the problem remains I am afraid it can even go worse. I mean reboots can become more frequent.
Did u changed your radio?
Had the same problem when I was on AOKP+Franco combo. Actually it was the radio for me which caused the problem.
Reflash everything, including radio, while returning to stock, it worked for me.
good luck :good:
Related
I am running CM7 on my EVO and for some reason every now and then the phone decides to reboot on its own. Is it something within CM7? DId the fix it if others were experiencing the same problem? I haven't d/l the newest one as of yet. Thanks in advance.
You can get the random reboots if you didn't flash correctly, or over clocking too high. So I would suggest to:
-Download the latest version
-perform a full wipe [factory/data, cache, dalvik]
-flash latest gapps
And you should be good to go.
It's great
mjs1231 said:
Evo running cm7. My done started rebooting in the last two days. I. think its the new update to 1tap clleaner on the market. Lowered my CPU to 245-800. Still reboots . Wiped dalvik and cache part. Still rebooted. NOTE. Cm7 has been working fine since it was posted online. Its some app fubar
Click to expand...
Click to collapse
What kernel are you running? Some kernels are undervolted quite a bit, and some phone's don't tolerate undervolting well. Reboots can possibly result. I had flashed the 3.3.7 Tiamat kernel the other day, running salvage mod. I was getting major and constant reboots. I used ViperBoy's overvolt script, and I've had no reboots since. My phone simply doesn't like to be undervolted, and getting rid of the the undervolt fixed it. So possibly if your kernel is undervolted a lot, your phone may not agree. So consider flashing viperboy's over volt script. His thread is in the dev section.
I have the Verizon Galaxy Nexus running on CM10; and just this morning my phone began to randomly reboot. I had been running this configuration stably for the past month or two.
The random reboots manifest themselves as a frozen/locked screen for a few seconds before the phone reboots. It looks to be a hard reboot, since it does go back to the Google screen. I have found that using my phone heavily (e.g. gaming) seems to slow the frequency of these reboots(if not stop them completely). At worst; they appear to happen every couple of minutes.
Coincident with the random reboots, my phone appears to have lost all cell network connectivity - it does not even report a signal strength anymore. No phone calls, nothing.
So far, I have tried re-flashing CM10 with ROMManager; fixing permissions, and uninstalling some apps. I don't know enough on where to look to fix the issue, and any help would be appreciated.
you try to flash a custom kernel?
k786 said:
you try to flash a custom kernel?
Click to expand...
Click to collapse
No. I haven't done any major tinkering lately. Never even tried a custom kernel.
FWIW, when I get to the screen with the Android on its back (on the way into recovery mode), it says that my CDMA baseband version is Unknown. Is that normal? Realted maybe?
What radio are you using? Check to make sure it's the latest, I don't know the Toro radios but if it's the same as Toroplus its FH05.
Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man
Hi All,
My Tab S 10.5 is in a bad way. It was running a custom rom & kernel. However, it has been acting strange with random reboots and battery percentages all out of whack. It can go from 50ish percent to 80 percent, then back down to 8 percent.
So, I wiped everything in TWRP. (everything save ExtSD), wiped data and formatted data. Installed factory image from the thread in Android Development but the issue persists.
Is there something I'm missing or more that can be done?
Thank you!
Was it like this when you stock? I would guess it was the settings you had on when you had a custom kernal and ROM but since your in a factory image it might be your battery/tab s. Some people had problems with their battery and I think it was some sort of lose connector. Since Knox has been tripped I'm not sure if you can take it back. Try a factory reset perhaps? Hope this helps.
Sent from my SM-T800 using Tapatalk
Don't overclock our undervolt anything in the first time when you are on a custom kernel. If you can work stable only change one parameter at a time so you can see when the tab gets unstable.
There is an app in the Playstore which has the name "BatteryCalibration". Maybe this helps you.
This only happens to me when i OC
Video about the Issue
So here is my problem...
Since Chupachups Rom updated to 3.0, I've been experiencing problems about the kernel control (both with stock and skin1980's own kernel) using Trickster Mod.
I just can't seem to set and lock CPU/GPU frequencies
I did check the kernel settings to set them on boot, but there isn't the issue; when I choose and set a frequency, upon tapping on the tick, the frequency immediately jumps back to the previous one (Which strangely forces itself at around 1.1Ghz-1.9Ghz for max freq and sometimes 960Mhz for Min freq)
As for the GPU it sometimes underclocks itself.
I was wondering it could be just a read bug, or something else.
I tried by a fresh flashing but still the issue is here.The .zips I flashed though are:
The rom itself
Kickoff's updated Lollipop theme
skin1980's kernel
Oversharpening Script
The oversharpening script also seems to lose and set the value to 0 after a while when I picked other values (ex: 28) (the UI seems as blurry as when I set it to 0 since the beginning.)
Try reflashing rom and kernel. I am on CC 3 and everythings fine.
And, do you really need that oversharpening fix? You really see the difference after?
DelBoy said:
Try reflashing rom and kernel. I am on CC 3 and everythings fine.
And, do you really need that oversharpening fix? You really see the difference after?
Click to expand...
Click to collapse
The updatedLollipop theme removes the oversharpening (I think?)...
You don' know many times I flashed, format my phone... I'm losing hope (I even went back to Kitkat and start all other again) I format my internal SD, etc