Related
(UPDATE- I searched and found this is a known issue: code.google.com/p/android/issues/detail?id=28133)
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2
I had this problem when using Juice Defender. Any chance you are using it?
No juice defender or even any similar app running.
Sent from my Galaxy Nexus using Tapatalk 2
untruestory said:
I9250 on ST
Radio XXLA2
North central US
I travel to a lot of very rural areas for work. Often while in these areas I will unlock my phone and see no service. A minute later I may have up to 2-3 bars showing and I'll receive vm and sms notifications. I've tried different kernels and ROMs with no change.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i started noticing the same issue recently...no service when i press the power button (on the lockscreen)...shortly after i unlock my phone, service/data restores...not sure if its kernel related as i believe (not 100% sure) that it happened around the same time i switched from glados to popcorn
i am also on XXLA2....in NYC
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure
msedek said:
You all need new radios lol.. Try the radios thread in general section and flash as many as you need until you find whats works for you..
Id start testing uglc1 wich are the lastests basebands..
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.
nodstuff said:
Its not the radios, I have seen some posts in kernel threads about minimum CPU clock speed.
If you are using 192mhz bump it to 384mhz and see if that helps if not then try 729mhz. I've seen people sort it by doing this.
Those are Franco clock speeds but you get the idea.
Click to expand...
Click to collapse
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago
no signal on wake
jdiddy_ub said:
ive read that the min cpu speed and even low VOLTAGES can affect signal stability as well....but i didnt change any of that.. currently its at 384 mhz and the default voltages on the popcorn kernel...the problem just started out of nowhere..its been fine for the past 2 weeks or so...just started happening like 2 days ago
Click to expand...
Click to collapse
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.
I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2
blanktree said:
I too experience the same issue. I am currently running aokp_maguro_build-36and have tried various basebands and now currently back at I9250UGKL1 .
I have been installing AOKP builds with the same behavior in that it goes to sleep the radio stays sleeping unless I reboot. I have the min CPU set to 700 mhz.
I have been reading the forums for weeks but cannot find anything where someone has fixed this. I love everything about the Galaxy Nexus with exception of this.
Click to expand...
Click to collapse
Try cm rom
Sent from my Galaxy Nexus using XDA
untruestory said:
I've tried several ROMs and kernels. They make NO DIFFERENCE at all, including using stock.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Try different radios. Ive noted that the radio is not changed when I flash different roms.
Sent from my Galaxy Nexus using XDA
jdiddy_ub said:
ive tried different radios before...UGLC1 included...went back to XXLA2 which gives me the best signal
this issue has only recently started happening...like i said, maybe related to the kernel because it started happening around the same time...not sure
Click to expand...
Click to collapse
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3
msedek said:
Id say try a Stable rom(not nightly) like AOKP Milestone 5 or stock.. And see if the problem persist.
After flashing new roms do a wipe of everything.. Dalvik/sd/cache/system
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
i am already on AOKP MS5...i flashed the stable jame bond kernel last night...havent seen the issue since...hopefully that solved it
Aite cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Since its not the radios, the kernels, or the ROMs, then what else (other than a hardware defect) could be creating this problem?
Anyone?
Sent from my Galaxy Nexus using Tapatalk 2
Me too experiencing the same issue. Currently I'm on AOKP B37, and the bug is still there. The funny thing, is that despite no signal icon on wake, the phone is still on air and accepts calls. I've installed the No Signal Alert app, which hasn't registered any signal loss so far, but I know it works fine (I used it before on my old Galaxy I5800, which was loosing service). Very strange...
That is odd. I've missed calls in areas I should have gotten them. I'm hoping they hurry up and release a fix.
Sent from my Galaxy Nexus using Tapatalk 2
Signal Loss
I've been having the same issues for about a week or two now. Actually sent a phone back in and had it exchanged out because of this. Yes, I tried all radios and tons of different roms. Same result for all. And I mean I tried ALL THE RADIOS, so quit suggesting that.
And I also swapped out a phone, redid my things, and now getting back to same issues again.
However, my observations.....
I never had issues from Dec thru about a month ago. Then had a Rez for two weeks, then back to GNexus. First thing I did was load most current CM9. Played well for the whole day I had it at that. Then I realized I had forgot to update radios. Before (month ago) it was still at leaked 4.0.4 radios, however when I looked em up, the official 4.0.4 radios were posted. So I dabbled with them instead. But I also saw the bootloader update and blah blah, so I did the whole shabang for official 4.0.4, then rerooted and cm9'd. This was where problems began....at this point is when I started having exact same problems as OP. So I went back to old radios. Same problems. Then different radios. Same problems. Then different roms. Same problems. Then rolled all the way back to completely stock 4.0.2 image file. Bootloader, radios, recovery, everything. SAME PROBLEMS STILL.
Thats when I swapped out the phone.
New phone comes. I redo everything again, but just use official 4.0.4 radios rather than the bootloaders and blah blah but still with CM9. All is good. Then I wanna play with the full official 4.0.4 OTA update. So I do all of it. All if fine but I realize hey, battery life sucks again now. Back to CM9. Then I reroot and rom. And holy ****, all the problems are back again now with signals. New roms, same problems. Literally everything I had problems with before is all back again.
So I'm wondering if this obviously has something with OFFICIAL 4.0.4 image/bootloader/recovery or whatever the hell is being written when I'm doing that flashing.
Thoughts?
Your case might have some other cause. Did you try swapping your sim card?
Meanwhile, I was able to find a workaround. Just raised the min CPU freq. from 350 to 525. Since then there was not a single signal loss so far. Battery drain increase in idle mode ain't registered as well. I'm on AOKP b37 currently.
Here are the steps to take at least on AOKP (other roms may have similiar settings available):
Go to ROM control in the settings menu.
Open the Performance
Set the Min CPU to 525
Ensure, that Scaling govenor is set to Interactive
Enable the Set on boot option
Hope, it works for you too. Good luck!
Отправлено с моего GT-P7500 через Tapatalk
My Gnex randomly drops its signal entirely for a minute or so. I thought it was maybe the phone, but I recently had the phone replaced and it still happens.
It seems to happen with multiple ROMs and radios. Right now I'm on the rooted 4.0.4 with the FC04/FC05 radio and franco milestone 3 kernel.
Does anyone else experience this, or have a fix?
Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
Vangelis13 said:
Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
Click to expand...
Click to collapse
This is a fix for those experiencing the screen off bug.
Deep Sleep = No Service.
Personally...I'm on a VGNex as well.
Never experienced ANY signal problems...including the deep sleep drop.
I also use LeanKernel, though. And IMO had the fixes merged from the kernel source long before they dropped...and didn't even realize it until a bit after.
Maybe change kernels?
(Though...they all should be updated at this point. This was some time ago.)
I've changed the radio to the 4.0.2 radio and the ROM to Android Revolution (and kept its kernel).
It also happens while I'm actively using the phone - yesterday I was streaming Pandora in the car and the signal dropped. The screen was on and everything.
Clearly I'm doing something wrong. Could it be some app or something causing it?
I'm in the same boat as you. I've also replaced my phone several time with the same result. Currently I've only found one fix for this problem. This fix seemed to work perfectly for 4.0.2, but when I upgraded to 4.0.4, it only works 90% of the time. What you have to do is go to your mobile network setting and choose CDMA only. It sacrifices 4G, but at least your phone will run consistently. There are people who are not experiencing this problem at all, so maybe they can chime in on how they fixed it.
It's a phone issue..
You aren't doing anything wrong. Some people never have this problem and other people have it all the time.. doesn't seem to reproducible.
pas prbarre
joshnichols189 said:
It's a phone issue..
You aren't doing anything wrong. Some people never have this problem and other people have it all the time.. doesn't seem to reproducible.
Click to expand...
Click to collapse
I've heard lots of people say that after the new update, their phones started functioning properly. However, I can't reproduce their results.
@ OP and Kim
This is a device issue. I had the same experience with the GN. I went through 3 phones and three weeks of dropping service every 10 mins or so. Finally the third phone didn't have the problem. I did everything - Going into multiple Verizon stores for tech support, calling tech support (Going through tier 1,2,3 multiple times), changing SIM cards, flashing new ROMS, RADIOS, KERNALS.... nothing worked for me. Verizon even came out and tested 4G in my neighborhood.
It is just poor quality control from Samsung. Send the phone back and keep sending it back till your signal is fine.
That is what I did (sent mine back for a refurbished device), my data drops were UNBEARABLE, look at what happens in just over 5 hours of being in a strong 4G area...
I'm hoping this fixes my problem, but I'm not holding my breath.
Yep same here, had that issue and no amount of flashing would fix it.
Got a replacement from VZ and its been perfect, zero drops.
Just got a galaxy nexus last week and it is the baseband version I515.10 with FC05. As soon as I got home with it I updated it to 4.0.4 (which was suppose to fix the random drops) and thought it was working well. Sure enough a couple hours later drops again.
I did a couple tests. Rooted it and installed different ROMs and radios. NO FIX
Made test calls with 4G, dropped the calls after 30 seconds.
Turned on CDMA only (3G), calls never dropped.
My analysis:
-4G is having issues with the baseband I515.10. I hear with the I515.9 it is working fine.
-Hoping Verizon fixes this soon as I hate being on 3G and having a 4G phone.
It won't get fixed. You most likely have the same faulty hardware that I had so you should get a replacement.
Has anybody else experienced a loss in overall signal quality moving through to more recent firmwares? I remember my signal used to be great when I pulled the phone out of the box just over a month ago, and now its almost total crap.
I'm running vanilla 4.1, not rooted or anything. I did flash the very latest radio to see if it would help but its about the same (XXLF1).
I'm using the US GSM Unlocked Nexus, with AT&T.
Emission said:
Has anybody else experienced a loss in overall signal quality moving through to more recent firmwares? I remember my signal used to be great when I pulled the phone out of the box just over a month ago, and now its almost total crap.
I'm running vanilla 4.1, not rooted or anything. I did flash the very latest radio to see if it would help but its about the same (XXLF1).
I'm using the US GSM Unlocked Nexus, with AT&T.
Click to expand...
Click to collapse
I have the same issue.
devilkuro said:
I have the same issue.
Click to expand...
Click to collapse
Same here. Could it be hw problem? A lot of people in this thread are saying that when they get their replacement phone everything went fine...
What bother me is the fact that in the beginning it was working fine.... so could it be really an hw detect appearing after a short time??
I am not having luck with Android devices... On my phone the signal strength varies wildly and I get drop outs in places I never did had any issues with my iPhone. To be honest with you there seems to be a problem with the thing switching between towers, it just hangs on to one tower for way too long and then signal drops, then 200m down the road it's back to 3 or 4 bars
Hi,
I've been using JB since the version from io12 was out. Currently I use Bigxie's deodexed 4.1.1 and all is wonderful. Except one thing that is. The wifi signal is weaker than I'm used to from ICS. Especially the wifi range seems worse. Connections that I've used with ICS are now out of range. Some of my friend or family's connections are now very weak and I drop out of range very often. This goes for any JB rom/kernel I've tried.
I've tried several roms, trinity and franco kernels, dirty flashing, full wipe. I've even tried a couple of different basebands, even though I don't think they affect wifi.
So I'm wondering if other GSM GNex users are experiencing the same thing? I've seen a thread with a flashable "poor wifi fix" for the Verizon GNex, but nothing for the GSM version.
Verizon GNex wifi/gps fix:
http://forum.xda-developers.com/showthread.php?t=1739097
Any suggestions? Coukd a similar solution like the Verizon fix help?
Best regards,
P
Ok, allow me to explain whats going on with the "fix".
There were some folks who ported the GSM version to Verizon (myself included). However, they failed to use the correct wifi/BT firmware (I did but thats besides the point). They left in the GSM version. So that above fix is merely the bcm4330.hcd firmware and bcmhd.cal calibration file for wifi/BT from 4.0.4 for Verizon. It is not meant to be used for GSM and only applies to those who ported GSM to CDMA. Even with the fix, wifi is weak.
Verizon users currently have a newer version now, specifically for them from Google. However, the weak wifi issue still exists even for us. There are some who have strong wifi routers or are always close to them that do not see the issue, but it does exist for every JB user. Wifi is simply weaker, and BT is fairly janky.
It is a Jellybean specific problem, and I am assuming it will be fixed in time. You could try a 4.0.4 bcm4330.hcd, bcmhd.cal on Jellybean, but I doubt it will help, and it could end up hurting. I am thinking that broadcomm needs to fix these files.
Thanks for the reply and the precise info about the problem and the background for the Verizon fix. Very much appreciated.
I guess I'll have to wait and hope for an update.
volapyk said:
Thanks for the reply and the precise info about the problem and the background for the Verizon fix. Very much appreciated.
I guess I'll have to wait and hope for an update.
Click to expand...
Click to collapse
I am right there with you.
Wifi is horrible!
WiFi does kind of blow chunks. WTF.
burhanistan said:
WiFi does kind of blow chunks. WTF.
Click to expand...
Click to collapse
The more I think about it, the more I think it can probably be resolved by tweaking the calibration file. However that is a bit beyond my abilities as I don't understand whats contained in it to know what it needs tweaking to.
wifi weakness
I'm not sure why it does this but when I am in my house about 15 feet away from my router I would notice my wifi signal dropping down to 2 bars where my other phone would stay at full strength until I got around 15 yards away.. I decided to see how far I could get away from my router before completely losing signal. I walked a total of about of 30 yards from my router to the edge of my street and stopped every time the signal decreased down to one bar(which was between every 5 or 10 yards)... every time I thought the signal was about to drop out it would return back up to 3 bars after a moment of adjusting. Once I got to my furthest point it dropped out completely and then came back to 1 bar. When I came back inside where I previously had 2 bars I then had full signal throughout the house. I tested this a couple times and it seems that it only uses what it needs. If someone could do a similar experiment to confirm this isn't specific to my router set up I would appreciate it. I also did not notice any drop off in performance in speed from 1 bar to full signal while I was within 20 yards of my router, however, I didn't run a speed test, I just used my youtube app to load a video... I will run some speed test when I get home this evening to get a solid figure on the speed difference. This may not be a bug but a feature to conserve energy to increase battery life.
PROlific666 said:
I'm not sure why it does this but when I am in my house about 15 feet away from my router I would notice my wifi signal dropping down to 2 bars where my other phone would stay at full strength until I got around 15 yards away.. I decided to see how far I could get away from my router before completely losing signal. I walked a total of about of 30 yards from my router to the edge of my street and stopped every time the signal decreased down to one bar(which was between every 5 or 10 yards)... every time I thought the signal was about to drop out it would return back up to 3 bars after a moment of adjusting. Once I got to my furthest point it dropped out completely and then came back to 1 bar. When I came back inside where I previously had 2 bars I then had full signal throughout the house. I tested this a couple times and it seems that it only uses what it needs. If someone could do a similar experiment to confirm this isn't specific to my router set up I would appreciate it. I also did not notice any drop off in performance in speed from 1 bar to full signal while I was within 20 yards of my router, however, I didn't run a speed test, I just used my youtube app to load a video... I will run some speed test when I get home this evening to get a solid figure on the speed difference. This may not be a bug but a feature to conserve energy to increase battery life.
Click to expand...
Click to collapse
A good theory, but I am dropping wifi in some of my rooms. Switching to and fro like that doesn't save power
didnt people have poor performance with their wifi signal on ics? did broadcom leave everything the same of did they change/update drivers for our phones with jb.
adrynalyne said:
A good theory, but I am dropping wifi in some of my rooms. Switching to and fro like that doesn't save power
Click to expand...
Click to collapse
Me too, I only need to move to the next room or so sometimes. The main problem for me is range. The range for me was better with 4.0.x.
slimb9 said:
didnt people have poor performance with their wifi signal on ics? did broadcom leave everything the same of did they change/update drivers for our phones with jb.
Click to expand...
Click to collapse
ICS wifi performance on the GNex wasn't exactly perfect for me, but it was better than what I get with JB. My router at home is giving me an okay performance and range, but the routers I normally connect to at family and friends are giving me problems since I moved on to JB.
I believe JB does come with new drivers. At least I've read that it does, in other threads.
slimb9 said:
didnt people have poor performance with their wifi signal on ics? did broadcom leave everything the same of did they change/update drivers for our phones with jb.
Click to expand...
Click to collapse
I had better performance on ICS with WiFi.
adrynalyne said:
I had better performance on ICS with WiFi.
Click to expand...
Click to collapse
Same
Sent from my Galaxy Nexus using xda premium
Wi-Fi has been fine for me, but only when using 2.4GHz—5GHz, on the other hand, is horribly broken. If you are using 5GHz, I recommend trying 2.4GHz instead—hopefully Google will have this sorted before the Galaxy Nexus II ships.
you may want to revert back to ICS to verify if the phone hardware is not a problem? otherwise for me I have used both... ICS and JB, and I don't find any difference..
ibraheeemz said:
you may want to revert back to ICS to verify if the phone hardware is not a problem? otherwise for me I have used both... ICS and JB, and I don't find any difference..
Click to expand...
Click to collapse
I’ve found 5GHz to be broken on both ICS and JB and this is with more than one phone.
BinkXDA said:
Wi-Fi has been fine for me, but only when using 2.4GHz—5GHz, on the other hand, is horribly broken. If you are using 5GHz, I recommend trying 2.4GHz instead—hopefully Google will have this sorted before the Galaxy Nexus II ships.
Click to expand...
Click to collapse
I'll try 2.4.
BinkXDA said:
I’ve found 5GHz to be broken on both ICS and JB and this is with more than one phone.
Click to expand...
Click to collapse
5 Ghz was fine for me on ICS. It works on JB too, but the range...ugh.
I'm pretty sure it's not hardware related. It's definitely related to JB. It's not a 5 GHz problem either, that's what I use at home on my d-link. Family and friends have both 5 and 2.4 GHz. I'm sure it depends on the quality of the routers also but I didn't have any real range problems with any of them before JB.
adrynalyne said:
5 Ghz was fine for me on ICS. It works on JB too, but the range...ugh.
Click to expand...
Click to collapse
Same here, except my d-link at home, which is kinda okay at 5 GHz.
volapyk said:
I'm pretty sure it's not hardware related. It's definitely related to JB. It's not a 5 GHz problem either, that's what I use at home on my d-link. Family and friends have both 5 and 2.4 GHz. I'm sure it depends on the quality of the routers also but I didn't have any real range problems with any of them before JB.
Click to expand...
Click to collapse
2.4 is pretty weak for me too.
I looked at the calibration file from ICS to JB. I don't think the difference warrants the problems seen.
From ICS to JB, these are the changes:
# 2.4G ACR
rxgaintbl100=1
# 5GHz Starting Tx Gain Index
initxidx5g=96
I'm at a loss here, but I know something is wrong for sure. I'm familiar with the low signal strength 'problem' on LTE networks as described at rootzwiki's thread entitled "This is why your Verizon Nexus signal "sucks" " I do not understand it inside and out, but I know enough to be at least 80% sure that this is not my issue. That thread describes a low signal strength, as in the dBm, but my problem is actual performance. I'm not comparing numbers (at least not on LTE networks), but results.
The problem is pretty bad, and pretty consistent. Without fail, my signal strength will be butchered, and with it data and even voice/text service will be unreliable or non existent inside any building. Not just some buildings, but any building. If I'm in a 4G area, I almost always lose the 4G, and it's switched to 3G with very poor performance (even for 3G standards). If I don't loose the 4G, the speed test results are horrid. I've had several cases where inside a building I still have 4G but the speeds might be 500-700 Kbps down/up or even worse, but when I step outside into the parking lot, 10-15 Mbps down 5-15 Mbps up. I realize structures absorb wireless signals and sometimes it can be pretty bad, but this is too much and too frequent to just be normal wireless signal degradation. It also doesn't seem to be the area because I've traveled through these areas before with my droid charge and I've never experienced issues anywhere close to this bad with my charge.
Some examples; the first time I noticed it was in the Greensboro, NC 4G area. Specifically at the Travel Centers of America about 10 miles east of the greensboro's border. When I first pulled into the truck stop (I drive a strait truck with a sleeper) I was pissed because my phone was on 3G, and I looked this area up before I came here on verizon's detailed 4G coverage map. This very truck stop was sitting in a dark maroon 4G area, NOT an extended 4G area. So I was angry, but I figured that there was an issue with the network, or the storm coming through was causing problems. Later the storm passed and I noticed (while walking back to my truck) that I was getting a strong 4G signal and good speeds, 5-10 Mbps down and 5 ish up. But as I sat back in even just the driver seat the signal strength dropped, and so did the speeds. I did a lot of tests later outside. I was performing speed tests at different locations all over the parking lot and I noticed the closer I got to the trucks, the poorer the performance. When I was inside my truck, and back in the sleeper, 4G was gone completely, taken over by a very poor 3G signal with slow speeds. I found that if I had my phone mounted on the windshield I was able to get reasonable 4G speeds, but still only a fraction of what I was able to get outside in the parking lot.
Another similar case happened in the Washington DC area at a walmart (Landover, MD). This time the 4G stuck even in the sleeper, but speeds were 2-3 Mbps down and about 700 Kbps up. While outside, however, 15 Mbps down and up.
Here I sit at another truck stop. This time, however, I'm in an extended 4G area (which of course means I have 3G) and I'm comparing my 3G signal strength to my Charge's signal strength. I know what I said earlier, but from what I understand about that "issue", gingerbread phones and earlier would give the CDMA signal strength because they couldn't read the 4G signal strength, but ICS and later can and so it displays the LTE signal strength. So wouldn't that mean that if you are in a 3G area, you can, in fact, accurately compare signal strength since they should both be displaying the CDMA signal strength? If that's the case, then what I'm getting is -100 dBm on my Galaxy Nexus and -87 dBm on my charge.
Something is most definitely wrong with my phone, but I don't know if it has anything to do with the Vicious JB stock rom I installed or not.
Vicious JellyBean 4.1 V5 is the version I installed, and I realize now that I did not install the latest (4.1.1 V1) but nonetheless I could not see it reported anywhere in the changelog, or any of the replies to the thread that there were very noticeable problems with the radio performance. I'm just at a loss and I really hope someone's reading this going "ah, I know exactly what that problem is". Although I'm never lucky enough to have a well known problem happen that there are fixes readily available for
Thanks very much for your time and help!
Bippity, boppity, bump!!
Sent from my Galaxy Nexus using xda app-developers app
I suggest you upgrade to the AOSP version that was released a couple of days ago. I have been running it for about 20 hours with very good results.
http://forum.xda-developers.com/showthread.php?t=1797996
JB issues?
Soundfx,
I've noticed some strange data problems as well. I've only had my nexus for 3 days. The first thing I did was throw a JB ROM (actually, about 9 of them to try them all out) on the device. (Vicious was one of them) What I noticed was that pretty consistently, about 5-10 minutes after the flash, my phone would go from having 4 bars of LTE to no signal at all. My connection would drop completely. Although I didn't figure this out until the latter flashes, I did remember having connection issues when I tried going to the play store or the internet on all the ROMs. I'd have to switch of LTE, and then I'd start working again. At first I just figured that I'm in some sort of LTE dead zone or something. But it seemed strange that my connection would drop completely and I couldn't get it back for 30-60 seconds.
SO, this morning I took my device back to stock. Unrooted ICS from Verizon. And although I wasn't at home for more than a minute to do testing, it appears that my connection problems have gone away. So I'm wondering if it is a radio issue for JB roms. All that to say that I don't think your problem is just the vicious rom. If you wouldn't mind, I'd suggest you trying another ROM and seeing if you have the same issues.
I figure it could be a few things for my own issues, which could be similar to yours:
1. Toro JB roms just have radio issues. (Seems like more people would be clamoring on this forum though if that were true, and I haven't seen any other than you)
2. I have a bad piece of hardware. (Running my stock ICS rom should shake that out.)
3. I live in a verizon dead zone and will experience drops no matter what ROM I use. (Again, stock ICS should shake that out for me.)
4. Gnex has inferior radio hardware, and there is nothing to be done about it. (Doesn't seem likely.)
ALL that to say that, while I don't have an answer for you, I seem to be experiencing similar problems, and I'm trying to figure it out too.
I'll keep you updated as I hone in on a culprit of my problems. (IF I can)
JR
stickerbob said:
I suggest you upgrade to the AOSP version that was released a couple of days ago. I have been running it for about 20 hours with very good results.
http://forum.xda-developers.com/showthread.php?t=1797996
Click to expand...
Click to collapse
You say "the AOSP" version that was released, but what exactly does AOSP mean? I know what it stands for, Android Open Source Project, but every jelly bean rom I've seen (or most) has AOSP in it and I guess I don't grasp it's actual meaning.
The only thing I know for sure is that I want stock stock stockity stock stock! When devs build roms they tend to always have some sort of a bug or two, and I just never feel like they are stable enough. So I want as stock as I can get! Which is why I installed Vicious Stock JB.
I just really don't know though...I know the nexus apparently has radio problems anyway, but...I guess I can just try the latest roms and see what happens. Are there any radios that I can install maybe that would fix this? :\
whozamazinka said:
Soundfx,
I've noticed some strange data problems as well. I've only had my nexus for 3 days. The first thing I did was throw a JB ROM (actually, about 9 of them to try them all out) on the device. (Vicious was one of them) What I noticed was that pretty consistently, about 5-10 minutes after the flash, my phone would go from having 4 bars of LTE to no signal at all. My connection would drop completely. Although I didn't figure this out until the latter flashes, I did remember having connection issues when I tried going to the play store or the internet on all the ROMs. I'd have to switch of LTE, and then I'd start working again. At first I just figured that I'm in some sort of LTE dead zone or something. But it seemed strange that my connection would drop completely and I couldn't get it back for 30-60 seconds.
SO, this morning I took my device back to stock. Unrooted ICS from Verizon. And although I wasn't at home for more than a minute to do testing, it appears that my connection problems have gone away. So I'm wondering if it is a radio issue for JB roms. All that to say that I don't think your problem is just the vicious rom. If you wouldn't mind, I'd suggest you trying another ROM and seeing if you have the same issues.
I figure it could be a few things for my own issues, which could be similar to yours:
1. Toro JB roms just have radio issues. (Seems like more people would be clamoring on this forum though if that were true, and I haven't seen any other than you)
2. I have a bad piece of hardware. (Running my stock ICS rom should shake that out.)
3. I live in a verizon dead zone and will experience drops no matter what ROM I use. (Again, stock ICS should shake that out for me.)
4. Gnex has inferior radio hardware, and there is nothing to be done about it. (Doesn't seem likely.)
ALL that to say that, while I don't have an answer for you, I seem to be experiencing similar problems, and I'm trying to figure it out too.
I'll keep you updated as I hone in on a culprit of my problems. (IF I can)
JR
Click to expand...
Click to collapse
Thank you kindly sir, and I will give a few other roms a shot just to see what I can find out and report back!
I tried flashing a few different roms; Liquid TORO Alpha 6, Vicious CM10 Toro, and Vicious JB 4.1.1 v1. All three of them as soon as the phone booted up showed the exact same poor 3G signal quality in the back sleeper while I'm in a dark maroon 4G area. Although I don't think I did a proper rom installation. They roms definitely installed, but it upgraded and installed over what I had...which I didn't realize it would do at all. I'll try doing it properly rom installation with a JB toro rom and then I'm going back to stock ICS to see what it looks like. I'm actually, right now, back at the truck stop that I originally noticed this problem. I'll post back.
I tried flashing back to stock 4.0.4 ICS build with the most recent radios, then I tried EK06 EK05 radios. It was the same across the board. No matter what rom/radios i use, the signal quality was the same. I lost service completely inside the building and in the sleeper it drops to 3G with incredibly poor signal quality :\ -100 dBm -120 dBm I'm going to try and get a new SIM card. if that doesn't solve it...then I guess it's time to look for a new phone :\
It seems like the developers are in a holding pattern until new radios are leaked. If it's that bad, there's no real harm in sticking w/ ICS until we get radios. Some really sweet things have been done by the community in the meantime.
Sent from my Xoom using xda premium
well I already had vicious 4.1 installed with my apps and all that stuff and it's the same across the board. So I'll be sticking with this until something pops up I guess :\ I'm still definitely going to check about getting a new SIM card; it's the only option, short of another phone, that I can try at this poing. -shrugs- :\