Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Azuske said:
Device: LG G2X
Rom: MIUI 1.11.11 (2.3.7)
Issue: Black Screen After Phone Call
Failed Fix Attempts: Turning Off Proximity Sensor, Reflashing Rom
Question: Does anyone know how to fix this issue? The only way to turn the phone back on after some calls is to pull the battery and turn the phone back on. It's starting to get a little frustrating. Any help is appreciated.
Click to expand...
Click to collapse
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
gman87 said:
Its more a kernel issue than a rom issue.
If your using Trinity kernel than that would be I'm guessing the reason why. I always had the call SOD when using Trinity kernel new or old. Ive used different kernels to see if it would help and that fixes it for me. Currently am running eagle blood with faux's 4.3 kernel and that resolved my call SOD. I could be wrong in your case but for me it worked switching kernels.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
That would explain it because I actually was using Trinity. Now I am using Dragon-G2X and its working perfect (so far). Thanks for your input.
Related
I am running the stock rooted rom with nechary 1.3.4 bfs and my sd keeps unmounting. is it the clockworkmod? I can not find any answers here. Any help would be great.
Sorry wrong section
takes about 4 or 5 reboots to get it to mount again once that happens
I switched from the stock rom, and haven't had the issue since
I read that happens on trinity kernels, I always run cfs on net's kernel so never ran into that problem
The same thing happened to me the other day with the same kernel. Fixed it by wiping cache and dalvik 3x and reflashing the kernel. No problems since.
Sent from my Nexus S 4G using XDA App
So what's going on here bc I'm about to get a brand new one off Craigslist for 270 pretty strait deal I just hope me ditching my epic for the nexus is a good idea
Sent from my SPH-D700 using Tapatalk
From what I have found it is due to bfs kernels. I read that somewhere here when I was experiencing the problem, flashed a new kernel and problem solved. I am still running a bfs kernel (matrix now instead of netarchy) but the issue hasn't come back.
bckoolaid said:
From what I have found it is due to bfs kernels. I read that somewhere here when I was experiencing the problem, flashed a new kernel and problem solved. I am still running a bfs kernel (matrix now instead of netarchy) but the issue hasn't come back.
Click to expand...
Click to collapse
Me too, same exact thing. Matrix is running fine, as well.
Hello XDA
I am loving this new build for MIUI I am running the new 108050 and I was wondering what kind of Kernal I can run with this rom or if you can help me figure out my problems.
In the OP jface states that one of the bugs that needs to be fixed is get the kernal support up to date because it would support anything up until nightly 85
I have downloaded fauxs kernals from 3.3 onward and everytime I load the kernals I get no sound and things start to get buggy?
Does the new Rom have this kernal issue fixed or do I just have a special phone
Same here
Sent from my LG-P999 using XDA Premium App
Likely that it doesn't play nice with these kernels
Miui doesn't play nice with the CM7 Kernels. It has bugs, even wit hthe new version(I had two battery pulls yesterday and some apps don't run). I tred Faux's kernel and wasn't able to hear calls....so I stuck to stock. It almost works, and with it being so pretty, that's enough for me.
I had read somewhere that morfic's trinity kernals play are compatible with MIUI...but that the camera can get a little wonky at times- and i have experienced this with the 1.7.29 version where the colors get messed up- but has anyone tried the trinity kernal on the 1.8.5 yet?
Thank you for your response I really do love MIUI I just wanted to undervolt
can someone help me out, i have 3 nexus s 4gs each on different roms but some of the same problems.
first, my phone (nscollab+franco kernel) and my wife's phone (Matr1x rom + kernel) will sometime shut down, and the power button wont work, i have to pull the battery to get it to work again
second, this is rare but every now and again the phones reboot and play the boot animation in inverted colors not sure why.
but is there something im missing, new radio, spl? or are my settings for the kernels not right, any help would be appreciated.
Does this happen on Matr1x v11.5?
Sent from my Nexus S using XDA App
Hey mathkid. No I tried to dl that version but flashing was failing, has the link been fixed? I would like to get new version on my phone as well, also could you recommended settings for nstool for me, like voltages, CPU government, ext.
Oh man I just looked and you closed the rom thread so you mean the kernel and no I'm running franco and my wife has the old matr1x rom so. what do you suggest I flash
Try Matr1x v11.5 cfs and start off w/ 1000/100 ondemand w/ no deep idle
if that runs well we can adjust further
K will try, I'll report back
I am trying to find out why my phone is doing this? Could it be a rom or kernel issue? I am running asop+ 2.2 rom and glados 2.7. Or could it be a radio issue?
Sent from my Nexus S using Tapatalk
Glados has a problem with rebooting while calling
It's a known issue in GLaDOS thread. However, some users get a lot of reboots, some never get one.
If you want a quick fix then try flashing another kernel.
Thanks any suggestions on kernals? I have had nothing but issues with matr1x and now it seems glados is giving me issues.
Sent from my Nexus S using Tapatalk
Known issues with GLaDOS. If you want to stay with GLaDOS, you can try:
-Up the voltage a bit if you are using liveoc (or disable liveoc)
-Don't overclock at all
-Disable deep idle
Or you could try matr1x again and maybe up the voltage 25mV across the board (except for 100 and 200mhz) as it is underclocked by default which your phone may not like. Otherwise i'd be trying netarchy, eugene's icup or francos kernel.
Harbb said:
Known issues with GLaDOS. If you want to stay with GLaDOS, you can try:
-Up the voltage a bit if you are using liveoc (or disable liveoc)
-Don't overclock at all
-Disable deep idle
Or you could try matr1x again and maybe up the voltage 25mV across the board (except for 100 and 200mhz) as it is underclocked by default which your phone may not like. Otherwise i'd be trying netarchy, eugene's icup or francos kernel.
Click to expand...
Click to collapse
Matr1x was a nightmare....but I will try some of the others.
Sent from my Nexus S using Tapatalk
djwyman said:
Thanks any suggestions on kernals? I have had nothing but issues with matr1x and now it seems glados is giving me issues.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I'd suggest you start with Eugene's kernel (ICUP) because I have used it for a week without a single reboot
Disable deep idle, fixes most problems.
99 problems but a deep idle ain't one.
I switched to icup and it seems to be doing good. Thanks guys. I never had deep idle enabled so that was not my issue
Sent from my Nexus S using Tapatalk
djwyman said:
I am trying to find out why my phone is doing this? Could it be a rom or kernel issue? I am running asop+ 2.2 rom and glados 2.7. Or could it be a radio issue?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I'd try to upgrade to ICS or reinstall the ROM. Also check your battery. It it heats abnormally, that might be the issue as well...
Aosp+ 2.2 is ics... but regardless changing kernels fixed the issue.
Sent from my Nexus S using Tapatalk
has anybody had this problem with the CM9 20p1 alpha? My phone rebooted twice just now. Really annoying!
zyrill said:
has anybody had this problem with the CM9 20p1 alpha? My phone rebooted twice just now. Really annoying!
Click to expand...
Click to collapse
I'm on cm9 a20p1 and glados 2.7 and not a single reboot in 1.5 days now. Still testing though.
Sent from my Nexus S using xda premium
djwyman said:
Matr1x was a nightmare....but I will try some of the others.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Couldn't handle the Matrix eh?
Haha
Is this v14.0?
Sent from my Nexus S using XDA App
Pretty ironic, considering if you read my thread most people are happy with 14.
Sent from my Nexus S using XDA App
Yeah idk why you would be having problems with matrix, I doubt it's the kernel.
flodb113 said:
I'm on cm9 a20p1 and glados 2.7 and not a single reboot in 1.5 days now. Still testing though.
Click to expand...
Click to collapse
Did you try to have prolonged phone calls as well? That's when it crashed... Every 3 minutes or so. The rest is perfectly fine...
Hello !
I have a problem with my g2x : if I flash another kernel than stock with stock ROM, I get question mark in the battery indicator. I have to disable airplane mode to get the battery percentage.
I tried CM7, CM9, stock 2.3.4 with faux 14b2… The only custom kernel that works is FAUX CM7 kernel with DebauchedSloth's battery driver.
Any idea ?
Thank in advance !
I'm not certain, but have you tried mazout360's kernels? They were based on faux and maybe that would work. Its been a long time since I had this phone though... Are you running stock 2.3.4?
Sent from my Nexus 5 using XDA Premium 4 mobile app
It was working on stock 2.3.4 until I flashed faux kernel but it sudently reworked after a rebot. I'm actually on mazout's cm10.1 ROM ans it is working to. I don't understand. Could it ne related to my multiples batteries ?
As far as I know for the cm10.1 they never got it working fully. I'm not sure about the multiple batteries though if it's already not working it probably doesn't help to confuse it more lol. I think at some point they had mentioned the battery indicator being tied to the ril. I don't know what one has to do with the other but if you're not using the radio at all it might also affect the battery indicator.
Sent from my Nexus 5 using XDA Premium 4 mobile app