Hi XDA
My phone randomly crashes to a blue screen of death, stating that there is a subsystem crash due to the external modem. I am running CM 10.2 stable, but this also occured with the Thinkingbridge ROM. The kernel is the one included in CM. Is there any known solution for this? Or is it possible to make the phone automatically reboot - rather than stay at the BSOD? I use my phone as an alarm clock (as most people), and this morning i was late for a lecture because my phone had crashed, and stayed at the BSOD screen.
Cheers
Niels
Related
I've got a Verizon G'NEX and I flashed DroidViscious's 4.1.1v1 rom with Franco's kernel about a month ago and everything was smooth sailing up until last week. I've been experiencing random instances of my screen freezing for about 10 seconds followed by my device rebooting. Upon startup right after a reboot I can enter my pattern lock and then it freezes immediately after and reboots (I can tell it's responsive during the unlocking of the pattern because of the haptic feedback). This will happen several times before I'm able to get back to the homescreen without it freezing.
I thought there was a problem with the rom since it was an older build Jelly Bean so I wiped the device and flashed the latest build of Pete's BuglessBeast using his default kernel hoping that would solve the problem. Unfortunately it didn't. I'm still experiencing these random freezes and reboots and the only way I can get it to boot without freezing is to pull the battery out for a couple of minutes and try again.
I'm wondering if the device is thinking it's getting too hot so it shuts down but I don't really have any way of knowing (it happens a lot when I'm in the car or when the phone is charging). Anyone have any ideas on what the problem is and how to resolve it? Or any ideas on how I can debug the problem myself? It's happening fairly often now when I need my phone the most.
The phone isn't even a year old so if relock the bootloader and return it to stock it should be covered under warranty still if there's a hardware issue.
Well, this problem seems to be exclusive to Jelly Bean. I reverted back to ICS and everything seems to be fine. Is anyone else having this problem with Jelly Bean roms?
yeah I get alot of random reboots and some freezes here and there. not sure what it is. but i have to gsm version gnex.
Hi everyone, my gnex maguro started to crash just suddenly, i thought it was 4.4 nightly build problems, but i reflashed into other rom same problem, i just don't know how to describe the problem, it happens very randomly, it makes a ticking sound and screen turns off then a power-up vibration. could it be a hardware issue ? if so which part ?
BUMP
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?
like most people I was using CM12.1 Nightly for tomato(Yu Yureka) as there was no initial issue at first other then a random reboot, heat up nothing much that really concern, so I noticed a lag in the phone after surfing the net, and watching some videos and taking some pictures with the camera, so as to ease the lag of, I decided to restart the phone only then the phone went crazy of keep on restarting after boot up so I disable the WiFi and noticed that it was still constantly rebooting, now something is serious wrong, I did tried to get the logs which it fail to the point due to its random restart over and over again, good thing is I had TWRP recovery (life saver) I was able to back up some of my important pictures and conversation, and went back to 4.4 KitKat CyanogenOS, the issue was resolved no more reboot for now. so if you are flashing Nightly be warn it is highly unstable. I wont really recommand to update to till the green light is given in
* random reboot is fixed
* heat up issue is mild
* proximity sensor is fixed
* other lag issues
I used to own a Xperia Z and given that this phone is octa core with DDR3 RAM it should performed better but sadly it isn't.
Somebody HELP!!!!!!!!
I'm running Resurrection Remix LP v5.5.8 on my T-Mobile Galaxy S4 (SGH-M919). I love this ROM, but I'm having a persistent problem with Bluetooth crashing, within minutes of starting up. This a consistent problem, not even remotely intermittent - happens every single time I try to turn on Bluetooth - it shuts itself off, refuses to turn back on again, and on occasion, gives me the error message "Unfortunately Bluetooth share has stopped."
I have tried clearing the Bluetooth share app cache and data to restart - it will then turn back on, but soon turns back off.
The problem was bad enough that I took RR off my phone and tried some other ROMs, including basic CM12.1. I came back to RR because the other ROMs had more critical issues, but they did help me eliminate causes of my problem, in that I didn't have Bluetooth issues with them like I do with RR, and I was still running all the same apps, same devices I was trying to attach, etc.
I've also played with several of the settings in the Kernel Aduitor, including completely shutting off the task killer. No difference - problem persists.
I also tried some of the apps on Google Play that say they're supposed to cure problems like this. Fixed nothing.
Please help. Is there an alternative something that I can flash - Bluetooth driver, different kernel, something, that can fix this issue once and for all?
Got the same problem. Android V6 RR Remix. Any suggestions?
Seems to be a consistent MM ROM issue, currently. Some seem to work better than others on some phones.
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Anyone have any resolution to this issue? I'm having the exact same symptom, but I'm on a different phone.
Note II / T-889, Conch Republic. Might've been from a radio update I did a while back, trying different ones now.
denverjoe72 said:
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Click to expand...
Click to collapse
You might give this AOKP 6 MM ROM a try:
http://forum.xda-developers.com/showthread.php?t=3391994
Users are reporting that after a week of testing the Bluetooth seems to be working rather well.
Sent from my SGH-M919 using XDA-Developers mobile app