Hey guys,
I'm using an LG-E975 Optimus G, unlocked by FreeGee and rooted with motochopper.
I'm getting these random crashes, which normally happens once every day. Typically when I'm sleeping.
I get a Demigod crash handler : External Modem
I flashed a 4.2.2 ROM (Thinking Bridge) onto it, seems to be a build off of CM, I don't know if that makes any difference to you :3
Googleing the error doesn't really lead me anywhere, there's one guy on XDA that had the same problem, but the thread is dead :/
I noticed that my Google Apps for some reason eats almost all the battery, maybe that's related ?
peecee DOT dk/uploads/092013/Screenshot_2013-09-07-12-51-24.png
peecee DOT dk/uploads/092013/Screenshot_2013-09-07-12-50-52.png
I don't mind that it happens once a day, especially if I'm asleep, but the screen stays on with the Demigod crash handler, maybe there's a way to just make the phone reboot ?
I would really appreciate your help ,
use betterbatterystats and cpu spy to see if the phone works right.
BBS is to see what is eating the battery and if there are wakelocks and cpu spy to see if the phone goes into deepsleep.
And it's known, custom roms will drain more the battery than stock. it's normal, custom roms are unofficial builds,not supported by lg.
kimitza said:
use betterbatterystats and cpu spy to see if the phone works right.
BBS is to see what is eating the battery and if there are wakelocks and cpu spy to see if the phone goes into deepsleep.
And it's known, custom roms will drain more the battery than stock. it's normal, custom roms are unofficial builds,not supported by lg.
Click to expand...
Click to collapse
I don't mind the battery usage, it's fine, i know what's using the batery, cause i can keep track of it all days, and when the phone throws a panic at night, it lays there with full screen brightness and never dims down or anything, that's what's eating battery.
You don't have any suggestion to the actual problem ?, the exception caught by Demigod ?
Nonetheless it's nice of you to reply
it may be an app causing this. it happened to me when i tried to use spirit ul for fm radio. my guess is something is trying to acces a function not available and you get this.
make a clean install of the rom you want and try not to restore apps with titanium. install them from playstore.
kimitza said:
it may be an app causing this. it happened to me when i tried to use spirit ul for fm radio. my guess is something is trying to acces a function not available and you get this.
make a clean install of the rom you want and try not to restore apps with titanium. install them from playstore.
Click to expand...
Click to collapse
It was a completely fresh ROM, i installed it 2 days ago, happend on the very first night
Will logcat or something pick up what's happening ?
Just tried flashing the RC of Cyanogenmod, same problem, about once or twice a day it throws a demigod error :/
Hey mate I was having the exact same issue as u so I thought I'd experiment by flashing the custom ROM I wanted then flashing the original hong Kong baseband 10A afterwards. Its been 2 days no crash yet. I don't know what area ur in but try the baseband that's best for u. There's a thread on here where someone uploaded the Canada, Brazil and HK stock baseband.
I'm still waiting right now to see if it crashes but its lasted longer than just flashing a custom ROM alone. If this proves to be successful I'll post a thread for those who experience this issue and how to fix
bikerboi85 said:
Hey mate I was having the exact same issue as u so I thought I'd experiment by flashing the custom ROM I wanted then flashing the original hong Kong baseband 10A afterwards. Its been 2 days no crash yet. I don't know what area ur in but try the baseband that's best for u. There's a thread on here where someone uploaded the Canada, Brazil and HK stock baseband.
I'm still waiting right now to see if it crashes but its lasted longer than just flashing a custom ROM alone. If this proves to be successful I'll post a thread for those who experience this issue and how to fix
Click to expand...
Click to collapse
Hey friend, I'm in Denmark
Today i got so fed up with the crashing etc. so i KDZ'ed it to stock.
However if you do decide to post a guide, I'll be happy to follow it n.n
Click my signature, it's easy to use kdz updater. Another suggestion, flash open EU kdz,not branded one. user zenalc can confirm that flashing open eu kdz solved his problems posted here http://forum.xda-developers.com/showthread.php?t=2436647
kimitza said:
Click my signature, it's easy to use kdz updater. Another suggestion, flash open EU kdz,not branded one. user zenalc can confirm that flashing open eu kdz solved his problems posted here http://forum.xda-developers.com/showthread.php?t=2436647
Click to expand...
Click to collapse
Already flashed it with open EU, E97510B_00
Hi, I have exact the same external modem error! It's verry annoying, I am wondering wether it's a baseband error or some hardware faillure. On stock I don't have the blue screen, but often the signal falls out and I think the modem is restarting (not able to have signal for 2 or 3 minutes). On custom roms, the kernel panic value is set so that there is an immediate panic, so that's why there is a blue screen. I installed trickster mod and went to sysctl kernel settings and typed panic in the searchbox and made all the values equal to 0 (which means off). Now I don't have blue screens, but I have the annoying signal drop issue.
How do I flash a korean baseband on my device? It solved tons of issues on my Optimus 2x too, but there was a risk of imei loss.
Do you solve this problem? I have the same situation. ...
Wysłane z mojego LG-E975 przy użyciu Tapatalka
M4jQ said:
Do you solve this problem? I have the same situation. ...
Wysłane z mojego LG-E975 przy użyciu Tapatalka
Click to expand...
Click to collapse
I might have found the solution thanks to Faust93! I googled a bit and found certain confirmations too. The modem seems sensitive for C2 and C3 power states (when the modem tries to idle, it enters a power saving mode).
You can disable this setting with fauxclock.
Im on stock right now, but LG must have disabled this power state on her modem (or just let the modem crash, which might also happen from time to time). I think mine is crashing on stock too, I see a red cross about 10 times a day, but no bluescreen, just disappearing signal for 20 seconds.
http://forum.xda-developers.com/showthread.php?t=2342175 << search for C2 and you will find!
unfortunately it did not help. modem still reseting. but on omnirom + f93 kernel it is only modem reset without crash (same situation on stock). i think it must be hardware problem. i send phone to lg service and they send me back with note "test ok"
Hey All,
I purchased the Optimus G (E975) in February and immediately installed CM11 on it. It worked perfectly until late June where it randomly started giving me a Blue Screen of Death (BSOD). The error message was something like
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
followed by jargon.
Initially I felt that perhaps it was some setting I changed or some app that caused this. So I did a factory wipe and reinstalled CM11 (I think we were at M6/M7 at that point) but no dice. Even after that I kept getting the error at random times.
I reflashed the stock KDZ (Jelly Bean), rooted with MotoChopper, installed recovery using FreeGee, and installed CM11 and Google Apps again. The problem persisted. I would update my CM every time a new Milestone release came out - and the problem persisted with all releases right up to M10. I never got around to installing M11.
Initially the BSOD used to appear if I left my phone idle for a long time. If at night I forgot to plug my phone in, it would be completely out of charge by the morning. Recently the problem started appearing during normal usage also - not frequently but once or twice a week.
I looked into the problem and from what I gather it has something to do with low power state of the CPU or maybe the modem. It would cause the system to crash. I also read that the problem was caused by a hardware issue - which is good because my phone is covered.
So last week I flashed the original LG Firmware (Kit Kat) and was hoping for the problem to persist so that I could hand it in to LG. But lo and behold ... the problem is gone ...
I don't know whether to be happy or sad. I hate this Android Optimus UI ... and I want CM back. Perhaps its something I did wrong, or ... I don't know.
If anyone has any inputs or ideas - I'd really appreciate the help. Thanks.
try installing cm 11 m11 now that you have installed kit kat, maybe everything will work. https://towelroot.com/ and after that do the same old...
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.
A fair number of unlucky LG G3 owners using AOSP/CM-based ROMs, myself included, have a major problem with the issue where a reboot/power-on cycle results in the phone getting stuck at the LG or boot splash screen ad infinitum.
The only way around it is to do a battery pull, sometimes several times, before the phone eventually recovers, but not until after it's gone thru its "Optimizing" or "Upgrading" apps, which takes 5-10 extremely annoying minutes.
I'm using a D851 and have this issue with every ROM I've used (Xenon, Exodus, AICP, to name a few).
This is not a battery issue as I've had the same problem using batteries from 3 different manufacturers. I've also had the same problem when plugged in.
If anyone knows of a fix - would be greatly appreciated (please don't say factory reset or root back to stock - I've already done this and it doesn't fix this issue).
I also have this problem with aosp and cm roms, i also get bsod sometimes. I think that maby the battery is broken, but im not sure since i dont got any problems on stock. When i get money for a new battery i will reply here with results.
I got my new battery today and it bootet up instantly
I had this issue on my d852 running cm12.1. It turns out using autorec is what caused it for me. I fixed it by flashing a kitkat tot then installing twrp using flashify. Once I had twrp installed I flashed the modem.bin from a lollipop d852 kdz. I haven't had a shutdown/reboot hang in a week now.
I have the same problem D851, it happens on latest builds of exodus and aicp. candy and blisspop works fine without any issues. I have changed the battery but the problem persist on exodus and aicp
Hello I have got some strange things a week after I received this phone..there is some simcard reading issue its just randomly stops reading until u remove battery and simcard and re insert then it does work again but after some time again stops reading I had this problem for a while I thought it was just normal thing until I googled..I tried everything change simcards, unrooted rerooted installed custom ROM still had the same problem, I'm on custom ROM called XenonHD/Android 5.1 custom ROM and just few minutes ago simcard was reading well...it just stopped by its own (never dropped the phone tho) so my QN is what can I do to fix this cuz I love this phone so much...I don't mind at all I'm just asking for help if anyone having maybe similar problem and how can I fix it