Hi guys,
Since about a month, my Nexus S sometimes (often) does not allow me to answer the phone when it rings : I can see the caller, I have the buttons to answer, the screen is animated as intented, but the phone does not accept any input from me, as if the "touch" part of the screen were desactivated.
I have to lock and unlock it to be available to answer.
I have this phone since may, and it happens since about a month
I had this issue with MIUI ans ICS (kwiboo v3, with franco kernel)
I've experienced this on nscollab as well. Running latest Glados kernel, if that helps. Not annoying enough to get me to change though.
Sent from my Nexus S using Tapatalk
Having that problem too on stock rom!
Have to turn off and on the phone to answer a call...
BillWieGates? said:
Having that problem too on stock rom!
Have to turn off and on the phone to answer a call...
Click to expand...
Click to collapse
confirm: push power button 2 times
Happend to me on Oxygen ROM with Franco kernel and on CM9 ICS.
uansari1 said:
I've experienced this on nscollab as well. Running latest Glados kernel, if that helps. Not annoying enough to get me to change though.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
No, it does not bother me so much, but if I take time to answer, I may miss a call...
Just have discovered that this has been already posted several times to the Android Issue database:
code.google.com/p/android/issues/detail?id=13853 (Jan 8, 2011)
code.google.com/p/android/issues/detail?id=18377 (Jul 10, 2011)
code.google.com/p/android/issues/detail?id=18454 (Jul 12, 2011)
To give it some priority, you should "star" the issue (without posting simple "me-too" messages).
Hope it will get fixed, as it is quite annoying... maybe with ICS!
I still have the issue with official ICS.
An answer has been posted on one of the tickets :
Starting to suspect static electricity.
The unresponsive areas of the display usually works fine after a "close-steamy-breath". Like the one you do before wiping the display clean. Another thing that works on my Nexus S (both 2.3.x & 4.0.3) is to wait without touching the display for 6+ seconds.
Click to expand...
Click to collapse
I'm not really conviced, since everything works just with a lock/unlock, but I'm not a specalist...
Related
Fully rooted, soff, hspa unlocked, and cm 7.2 rom.
the phone about a week old,,
Let say I start to send a text msg, for example
"hey this is E" before i can finish spelling EDDIE the D
key becomes unresponsive, and i have to hit the lock and unlock screen
and works
has happen other times with the keys at the btm, just kinda of annoying
was wondering if anyone has noticed this issue, or this issue on this rom?
thank u
d4redevil said:
Fully rooted, soff, hspa unlocked, and cm 7.2 rom.
the phone about a week old,,
Let say I start to send a text msg, for example
"hey this is E" before i can finish spelling EDDIE the D
key becomes unresponsive, and i have to hit the lock and unlock screen
and works
has happen other times with the keys at the btm, just kinda of annoying
was wondering if anyone has noticed this issue, or this issue on this rom?
thank u
Click to expand...
Click to collapse
i had same problem but i was running better keyboard 8 and it was on RcMix rom..what keyboard are you using?
Has happened to me stock, not stock, gingerbread and froyo. Seems like its a random bug(possibly with touchscreen driver, which can probably be fixed). Already planned on messing with the driver to see if it can be fixed.
Happens all the time. Running latest cm7 nightly. Rather Annoying.
Sent with a hint of unicorn horn.
this happens to me all the time.
I have the same problem, it's rather annoying.
Im having the same problem. is this only on cm7?
Used to happen to me, but interestingly enough, Swype fixed it.
I have owned two android phones now (n1 and the inspire) and they both had crazy annoying keyboards. It's like google is trying to mess with us!
I have had the same issue on CM7 and now UD 1.8.
Though... this has all been pretty recent.
xda Premium | Inspire |
CM7 | Cattleprod 4.3.1 - 1.8
DAMN!! no way!! I just ripped off a perfectly nice RealLook screen protector because i kept thinking it was the coating and my finger oils causing it not to work. I was even going to post a thread saying to not buy them because it causes letters not to work every once in awhile. It happens to me ALL the time, and seems to happen much more frequently when i use the HTC IME mod keyboard, not sure if that has anything to do with it.
Di11i....it would be amazing if you could get this working better!
Never had this problem for the first month with my first inspire, when i swapped it out for a new one (unrelated problem) had this issue sine.
Had this problem on cm nightly but since those builds are on android 2.3.4, I have not had any issues
Sent from my Desire HD using XDA App
Have this same issue....ffffff
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
UPDATE:
The issue happens in all CM based ROMs that I have tested so far, including the beta ICS CM9 ROMs
J-C.Martin said:
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
Click to expand...
Click to collapse
Interestingly enough it does not work in CM9 either. Tried the build, love it but hate the missing mute function.
mansa_noob said:
Interestingly enough it does not work in CM9 either. Tried the build, love it but hate the missing mute function.
Click to expand...
Click to collapse
That's too bad. I was hoping it would've been fixed on CM9.
Oh well. Just need to keep being careful and using the mute feature of the conference itself, instead of the phone.
BTW if you don't have an issue downgrading you can go to 2.3.3 and the problem goes away.
A BT connect problem may arise (as for me) but still worth a shot.
Sent from my LG-P999 using XDA App
J-C.Martin said:
I just wanted to share something that I found the hard way.
The Mute is NOT working if you are using Bluetooth with a CM7 based ROM.
I actually am using EB 2.4 ROM and I was listening to a conference call with my Bluetooth headset with the Mute selected on the phone when I got an e-mail from a colleague telling me to mute my phone
This issue is already listed in the cyanogenmod project page as issue# 4439.
I just wanted to let people know of this bug and hopefully be saved from some embarrassing moments.
Click to expand...
Click to collapse
I think I remember something about the CM team saying bluetooth will never fully work, they had to do a workaround just to get bluetooth headsets working in the first place. Also, you should update your Eaglesblood build, 2.8 has some nice new things.
IRASadPanda said:
I think I remember something about the CM team saying bluetooth will never fully work, they had to do a workaround just to get bluetooth headsets working in the first place. Also, you should update your Eaglesblood build, 2.8 has some nice new things.
Click to expand...
Click to collapse
That's too bad. I was hoping to hop on the ics as soon as this issue got fixed .
Sent from my LG-P999 using XDA
Ping... CM7 issue #4439 is marked as fixed. If you have the bandwidth please try and spread the word if fixed.
This is great news but my wife broke her Amaze 4G and is currently using my G2X so I am phone < and hence can't try myself :crying:.
mansa_noob said:
Ping... CM7 issue #4439 is marked as fixed. If you have the bandwidth please try and spread the word if fixed.
This is great news but my wife broke her Amaze 4G and is currently using my G2X so I am phone < and hence can't try myself :crying:.
Click to expand...
Click to collapse
I've seen the new status, I've not tested yet because I'm not sure if I need the new baseband with CM7.2 or not....
I'm affraid of trying to install the new baseband and mess up my current ROMs.
Thanks for following this issue.
Mute when on Bluetooth still not working
I am a very new and mostly very happy CM7 user with an LG G2X that was in desperate need of getting off of the stock ROM. I did the installation last night and just found out the hard way that my mute button does not work when I'm on my bluetooth headset. I came across this thread when searching for a remedy.
I'm not sure if my exhibiting the bug confirms that it still exists, or if there are other files/etc. that I need to upgrade or swap out. (i.e. radio, etc.) that did not come with my download last night.
My details:
Android 2.3.7
Baseband M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel 2.6.32.55-cyanogenmod [email protected]) )
Mod version CyanogenMod-7.2.0-p999
Build date Fri Jun 15 19:45:03 PDT 2012
Build number GWK74
Any advice/assistance would be greatly appreciated! Thanks!
wolfe42 said:
I am a very new and mostly very happy CM7 user with an LG G2X that was in desperate need of getting off of the stock ROM. I did the installation last night and just found out the hard way that my mute button does not work when I'm on my bluetooth headset. I came across this thread when searching for a remedy.
I'm not sure if my exhibiting the bug confirms that it still exists, or if there are other files/etc. that I need to upgrade or swap out. (i.e. radio, etc.) that did not come with my download last night.
My details:
Android 2.3.7
Baseband M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
Kernel 2.6.32.55-cyanogenmod [email protected]) )
Mod version CyanogenMod-7.2.0-p999
Build date Fri Jun 15 19:45:03 PDT 2012
Build number GWK74
Any advice/assistance would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
7.2 stable: the problem still exists.
Sent from my LG-P999 using xda app-developers app
Ive never seen anywhere where it stated tht bluetooth did work correctly on CM7 roms.
On a BT note, I'm typing this with an Apple BT Keyboard paired to my G2x, go figure...lol
What works and what don't!
Sent from my pimped LG G2x temasek build 135.1 w/Trinity Kernel --The Best G2x GB Solution
Any resolution in sight?
mansa_noob said:
7.2 stable: the problem still exists.
Click to expand...
Click to collapse
Thanks for confirming. Any resolution in sight or work-around to get it to work right?
wolfe42 said:
Thanks for confirming. Any resolution in sight or work-around to get it to work right?
Click to expand...
Click to collapse
Yeah. Before v21y I was running Weapon and now running stock 2.3.4.
Bluetooth mute is more important for me than a ROM
Sent from my LG-P999 using xda app-developers app
Actually just found out that blueant Bluetooth headsets can be muted by holding vol+ and vol- for 3 seconds... go figure.
You may want to check your headset manual too.
Sent from my LG-P999 using xda app-developers app
Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium
What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.
joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints
CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks
I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.
Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium
Where is this getril app?
Sent from my LG-P999 using XDA
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?
Hi guys. I just picked up a used G2x off of craigslist, assuming it was going to much better than my Optimus T...not so much. The phone is great, but it's got two major issues I can't stand:
1. it randomly reboots all the time. Drives me insane.
2. The phone apparently makes a lot of odd noises (according to my girlfriend), i'm going to just label this bad "call quality".
My phone is on 2.3.4 official rom, v21y software, and has the March 2012 baseband.
I've been digging through piles of threads, and most of them are from last year. I can't find anything that suggests how to fix the random reboots. I can't handle it. Any help here would be greatly appreciated.
As for the bad call quality, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1776843
and there's three possible basebands. I think I'm on the latest one (March 2012), but is there one that's better for call quality or newer?
Any help with these two things would be great. I'd just like to make this thing useable for a couple months til I get the S3.
Thanks,
Gunnar
PS: I already did a ton of searching, so please don't give me the whole noob speech about using the search button. Thanks.
Did you do a factory reset?
Sent from my LG-P999 using xda premium
There is no fix for it. It just happens. Some it happens less with, some it happens more with. However, I've been able to minimize mine and actually haven't had it at since I've went to CM 7.2 Official with Faux123 Version 52 Kernel. This works VERY well for me and I really like the phone now once all of the problems are eliminated. This entire setup works on the new baseband too so no worries there. Not sure if you are rooted and into flashing ROMS but that is the setup has worked best for me. I tried stock and then Weapon G2x but none of them remedied the problem until I flashed CM 7.2. I still had it occasionally with other Faux123 Kernels but since the release of Versions 51 and 52 I have not has one single random reboot or shutdown.
gunnarizbeast said:
Hi guys. I just picked up a used G2x off of craigslist, assuming it was going to much better than my Optimus T...not so much. The phone is great, but it's got two major issues I can't stand:
1. it randomly reboots all the time. Drives me insane.
2. The phone apparently makes a lot of odd noises (according to my girlfriend), i'm going to just label this bad "call quality".
My phone is on 2.3.4 official rom, v21y software, and has the March 2012 baseband.
I've been digging through piles of threads, and most of them are from last year. I can't find anything that suggests how to fix the random reboots. I can't handle it. Any help here would be greatly appreciated.
As for the bad call quality, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1776843
and there's three possible basebands. I think I'm on the latest one (March 2012), but is there one that's better for call quality or newer?
Any help with these two things would be great. I'd just like to make this thing useable for a couple months til I get the S3.
Thanks,
Gunnar
PS: I already did a ton of searching, so please don't give me the whole noob speech about using the search button. Thanks.
Click to expand...
Click to collapse
Well... If you did a search.... *ducks* Sorry.. J/K
Like others have said, you'll find sanctuary in using one of the CM 7.2 ROMS that are currently available. They are GingerBread 2.3.7 ROMs, that are upgrades from stock 2.3.3 / 2.3.4. Since you are on the current baseband (March 2012) I would decide if Bluetooth Calling is valuable to you. If it is, then DO NOT UPGRADE to a CM7 / CM9 ROM. Bluetooth Calling breaks when you use any of the CM ROMS with the new baseband (unless this has very recently changed).
Alright, I guess I'll give CM 7.2 a shot once I get up to college and get moved in tomorrow (along with that kernel you mentioned). The thing is, eventually this phone is gonna get unlocked and sold on eBay, so I just wasn't sure if I could fix any of these problems or if I should just get rid of it now...
I don't bluetooth calling, so that isn't an issue.
Does CM 7.2 alleviate any of the pops/bad call quality? And as for that Faux123 kernel, I found the thread but I can't find version 52, only 51, is that good enough?
Thanks,
Gunnar
If you go with hellfire phoenix it's cm7.2 based with extra goodies baked in.. and it also already has faux kernel baked in.. Im running it right now and it's awesome... Although I did flash faux 048 kernel today, had some weird issue with wifi on and my phone overheated in my pocket and shut down on faux 052 kernel. Never happened till I had wifi on. Now running 048 and it's smooth as butter..
Sent from my LG-P999 using xda app-developers app
cainG2x said:
If you go with hellfire phoenix it's cm7.2 based with extra goodies baked in.. and it also already has faux kernel baked in.. Im running it right now and it's awesome... Although I did flash faux 048 kernel today, had some weird issue with wifi on and my phone overheated in my pocket and shut down on faux 052 kernel. Never happened till I had wifi on. Now running 048 and it's smooth as butter..
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Alright, I may give that a shot. Do you have any random reboots or any other problems with it besides the overheating?
gunnarizbeast said:
Alright, I may give that a shot. Do you have any random reboots or any other problems with it besides the overheating?
Click to expand...
Click to collapse
no, no reboots or anything like that. just overheated that one time.. the 048 kernel is on this page, post #4044.. http://forum.xda-developers.com/showthread.php?t=1420972&page=405
just remember to go to settings-applications-developement and check stay awake while charging.. this prevents the overheat issue while charging that faux kernels have.. enjoy!! oh and you will also need the new BB fix if your on v21y..
Here are the Faux Kernels.
LG-P999 is our model. Also if you go with CM make sure you get the CM versions of the Kernel.
http://faux.androidro.ms/
Here are the older versions: http://faux.androidro.ms/archive
cainG2x said:
no, no reboots or anything like that. just overheated that one time.. the 048 kernel is on this page, post #4044.. http://forum.xda-developers.com/showthread.php?t=1420972&page=405
just remember to go to settings-applications-developement and check stay awake while charging.. this prevents the overheat issue while charging that faux kernels have.. enjoy!! oh and you will also need the new BB fix if your on v21y..
Click to expand...
Click to collapse
What does BB fix stand for (I'm guessing baseband)? I feel like such a noob when it comes to android...I can flash an xbox 360 and do anything I want on iOS...but seriously Android is the land of the unknown.
It's flashable .ZIP that you to flash with any G2X rom to make it usable with your baseband version. For instance, I have the march 2012 baseband and if I don't flash the fix I get pops and feedback during a call.
This thread has combined them all into one post:
http://forum.xda-developers.com/showthread.php?t=1776843
gunnarizbeast said:
Hi guys. I just picked up a used G2x off of craigslist, assuming it was going to much better than my Optimus T...not so much. The phone is great, but it's got two major issues I can't stand:
1. it randomly reboots all the time. Drives me insane.
2. The phone apparently makes a lot of odd noises (according to my girlfriend), i'm going to just label this bad "call quality".
My phone is on 2.3.4 official rom, v21y software, and has the March 2012 baseband.
I've been digging through piles of threads, and most of them are from last year. I can't find anything that suggests how to fix the random reboots. I can't handle it. Any help here would be greatly appreciated.
As for the bad call quality, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1776843
and there's three possible basebands. I think I'm on the latest one (March 2012), but is there one that's better for call quality or newer?
Any help with these two things would be great. I'd just like to make this thing useable for a couple months til I get the S3.
Thanks,
Gunnar
PS: I already did a ton of searching, so please don't give me the whole noob speech about using the search button. Thanks.
Click to expand...
Click to collapse
Get rid of it no ics for us
Sent from my LG-P999 using xda app-developers app
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
lirong said:
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
Click to expand...
Click to collapse
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
mrfeuss said:
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
Click to expand...
Click to collapse
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
lirong said:
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
Click to expand...
Click to collapse
I've had this problem with all kinds of roms (stock, custom, aosp, etc). Sometimes it happened more often sometimes less. I've even had this happen to me on three different phones (SE x8, i9100 and i727r). Most often it happens with CM7, CM9 and CM10. But it did and does also happen with official roms. I'm on the Rogers JB now and it still happens, but relatively rare. This has been discussed before and with no result. Apparantly this is a common android issue..
Same issue talked about here:
http://forum.xda-developers.com/showthread.php?t=2164921
http://forum.xda-developers.com/showthread.php?t=2168656
I had such problem too and hadn't found the reason.
Anyway, after I flashed UXUMA7 radio, I haven't experienced it any more.
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Sent from my Nexus 7 using xda app-developers app
livefree79 said:
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Click to expand...
Click to collapse
The last m release that I know of (I haven't been on straight CM for a few weeks) was released before a commit that fixed the no in-call audio bug. I'd read through the thread and look to see which nightly has been the most stable, if I were you. If you do decide to switch to another ROM I can personally vouch for Sons of Android or Slim Bean (onlychevys has an unofficial build out).
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
lirong said:
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
Click to expand...
Click to collapse
Embryo is tw, doesn't have the issue
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2