search

carleewang / cm9-msm8960

Automatically exported from code.google.com/p/cm9-msm8960
0 stars 0 forks source link

Phone loses signal after some time. #145

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I am on CM10 (Oct 2nd nightly) with stock kernel. The phone loses signal very 
frequently. The signal bar is shown as empty for few seconds and I am unable to 
make/receive any call for those few seconds. The phone automatically reconnects 
to the network after some time but this happens very frequently which is 
resulting in lot of missed calls.

Thanks

Original issue reported on code.google.com by tarandee...@gmail.com on 3 Nov 2012 at 4:59

GoogleCodeExporter commented 9 years ago 
I am on Nov 2nd nightly and not Oct as stated above.

Original comment by tarandee...@gmail.com on 3 Nov 2012 at 6:04

GoogleCodeExporter commented 9 years ago 
I am on the stable version and also having intermittent signal drops. Changing 
radio doesn't seem to help.

Original comment by milespro...@gmail.com on 14 Nov 2012 at 11:54

GoogleCodeExporter commented 9 years ago 
I am having this exact same problem. I just recently flashed the AT&T 2.20 
radio and am hoping that it helps alleviate the problem, but I'm not holding my 
breath...

Original comment by milne.mi...@gmail.com on 16 Nov 2012 at 11:43

GoogleCodeExporter commented 9 years ago 
I see similar behavior but only when using maps - the GPS and cellular signal 
die simultaneously and return to normal within a minute or so. On the 20121117 
nightly.

Original comment by neilfair...@gmail.com on 21 Nov 2012 at 1:39

GoogleCodeExporter commented 9 years ago 
I, too, have also now noticed that the data connection only drops when certain 
apps or websites request use of the GPS in conjunction with the data 
connection. However, it doesn't happen every time; only intermittently.

Original comment by milespro...@gmail.com on 21 Nov 2012 at 4:58

GoogleCodeExporter commented 9 years ago 
I have noticed this issue as well on 20121124 nightly. It happens when using 
Navigation for me or sometimes Foursquare, but it is definitley related to the 
GPS. One thing I am going to test is to see if I have my wi-fi turned off and I 
still get the issue. Some quick tests have shown no issues if wi-fi is off, but 
I need to test that in the real world on my drive home from work

Fyi, I upgarde dto the AT&T radio and saw no improvemnet, in fact it might be 
worse.

Original comment by Jonz...@gmail.com on 27 Nov 2012 at 7:41

GoogleCodeExporter commented 9 years ago 
I have seen this as well and I believe it is related to location services, not 
GPS. I turned location services off (can still use GPS) and do not lose the 
connection. I also believe it may only affect people with LTE.

Original comment by Pro75...@gmail.com on 29 Nov 2012 at 11:28

GoogleCodeExporter commented 9 years ago 
i have this problem as well, carrier connection is full strength, then loses 
everything for a minute or two, then reconnects at full strength and repeats. 
very irritating especially when using Google navigator

Original comment by brendanp...@gmail.com on 4 Dec 2012 at 3:26

GoogleCodeExporter commented 9 years ago 
My testing has been consistent with Pro75...I am on 20121203 Nightly and it 
seems that after a fresh install of of a nightly, it works fine without turning 
Location Services off...but a reboot then requires that this be turned off to 
use Navigator and Waze...anything that would be requiring many points of 
triangulation to get the best results.

I have flashed many nightlies in between the one I am currently on and have 
seen the issue repeated the same each time. I agree that this might have 
something to do with LTE and is not a GPS issue, but a radio issue that needs 
to be looked into.

Original comment by Jonz...@gmail.com on 4 Dec 2012 at 4:12

GoogleCodeExporter commented 9 years ago 
Nocturnal team fixed this in their cm10/aokp hybrid ROM.

Original comment by derek...@gmail.com on 10 Dec 2012 at 2:47

GoogleCodeExporter commented 9 years ago 
The bug is back in Nocturnal's Dirty ROM.

Original comment by dax...@gmail.com on 19 Dec 2012 at 7:54

GoogleCodeExporter commented 9 years ago 
I noticed that myself...I wiped my phone clean and installed the Dirty ROM and 
had the same bug....frustrating! went back to CM10 form a Nandroid I made.

Original comment by Jonz...@gmail.com on 19 Dec 2012 at 3:34

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by h8r...@gmail.com on 25 Dec 2012 at 12:51

GoogleCodeExporter commented 9 years ago 
Won't be fixed in cm10. Moving towards CM10.1

Original comment by h8r...@gmail.com on 14 Jan 2013 at 11:35