Develop Bugs

[Q] Possible overheating issue?

I am running Fresh 3.4.0.1 with the netarchy 4.1.9.1 cfs universal kernel. Other info is as follows:
Software number: 3.30.651.2
PRI: 1.77_003
PRL: 60662
Radio: 2.15.00.09.01
When using internet for any length of time under any signal strength conditions, 4G included where applicable, my Evo will reboot itself out of nowhere. This issue occurs most frequently when using wireless tethering. I have noticed the temperature reading on the wireless tether app in the high 30s before reboot, and the phone will just continue to reboot unless I remove the battery and let it sit for a while.
Could this be something with the kernel/another software related issue? Or should I flash it back to stock and utilize the warranty/insurance option? Any help would be greatly appreciated.

Bumping this, still having issue

captaincrunch said:
I am running Fresh 3.4.0.1 with the netarchy 4.1.9.1 cfs universal kernel. Other info is as follows:
Software number: 3.30.651.2
PRI: 1.77_003
PRL: 60662
Radio: 2.15.00.09.01
When using internet for any length of time under any signal strength conditions, 4G included where applicable, my Evo will reboot itself out of nowhere. This issue occurs most frequently when using wireless tethering. I have noticed the temperature reading on the wireless tether app in the high 30s before reboot, and the phone will just continue to reboot unless I remove the battery and let it sit for a while.
Could this be something with the kernel/another software related issue? Or should I flash it back to stock and utilize the warranty/insurance option? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I wouldn't consider high 30's overheating at all. When I tether with 4g my evo gets to high 40s, if I have it charging, low 40s otherwise. Never had a reboot. I've read around here of people saying that some of nets kernels have caused reboots, but that's just what I've read, I've used nets with mo issues. I would suggest trying a different kernel ( not sure what to recommend, as I've never used Fresh Rom, so don't know what works well) just keep in mind that what works for one evo might be terrible on yours. They all react differently. So try a few out, see why works well. Always make sure to have a good nandroid backup before flashing, and always wipe davlik and cache prior to any kernel flashing you may try. Oh yea, some evos seem to have rebooting issues regardless of what Rom or kernel you use. My girlfriends reboots randomly, and hers isn't even rooted. Hopefully this helps you a little.

Is happening with me too, I used to use my evo a lot and never felt the phone before get hot even with slingbox for three hours but now I dont want to use it bc gets hot and reboots, I have tried most of the roms and kernels and the same. When I install a rom works fine for two days and start rebooting every hour until I flash another kernel and wipe cache, I tried stock ruu and the same.. . I am going to flash back the old radio a see if that helps..... or any idea?

update: I have tested this with the latest cyanogenmod, as well as damagecontrol and ava froyo. Multiple versions of wireless tether, as well. Stock kernels for each of those mods, respectively. The issue remains.
I believe I am going to un-root my Evo and take it to my local repair/service center. In the past, they replaced my rooted Palm Pre free of charge when it was having touchscreen issues and they were generally pleasant to deal with overall. I left it rooted, even!

My EVO just recently started rebooting when the battery temperature gets into the high 30C range. It doesn't take much to get it that high, just simple web browsing is enough. Depending on how hot it is, sometimes it will start to boot loop and require the battery to be taken out until it cools down before it can properly start again. I know in the past it would run perfectly fine up to and even over 50C. It has the problem on all the roms I've tried, even unrooted stock with no apps installed other than a battery temp meter. If I keep the temperature down below about 35C it never reboots ever, although doing that is kind of a pain because it can go above it with only 5 minutes of active use.
I suspect the problem could be the battery itself, I'm getting a third party replacement in the mail soon and I'll see if that helps. Otherwise I guess I'm at Sprint's mercy, kinda wish that I didn't take TEP off my account a month ago :/ . That and there's no corporate stores that do repairs nearby, so I have to deal with a auth. retailer store, ugh...
The worst thing is... I can't play Angry Birds anymore- that thing heats up the EVO fast :<
BTW my hardware version is 0003 and it's a launch day EVO for anyone who may be tracking these things.

has anyone found a fix for this? my evo heats up to mid 30's just from having the screen on, and i can play with it for about 30 mins before it starts a reboot loop and i have to pull the battery and let it cool down.
this has been going on since mid February, really annoying. switching kernals doesnt help, neither does switching roms.
currently running:
cm7 rc4, savagedzen 1.0.1 cfs nosbc

I'd try a different kernel. I had random reboots when I was using ziggy's kernel (sense). Disabled all the undervolting and other battery saving scripts... The issue continued. Switched to net's kernel and haven't had a reboot since. Because these are tweaked excessively, some phones work better with one kernel than another.

captaincrunch said:
update: I have tested this with the latest cyanogenmod, as well as damagecontrol and ava froyo. Multiple versions of wireless tether, as well. Stock kernels for each of those mods, respectively. The issue remains.
I believe I am going to un-root my Evo and take it to my local repair/service center. In the past, they replaced my rooted Palm Pre free of charge when it was having touchscreen issues and they were generally pleasant to deal with overall. I left it rooted, even!
Click to expand...
Click to collapse
There seems to be two separate reboot issues going on here. One is the heat reboot at about 38 degrees (which I have not experienced) and the other is the GPS/Phone combo reboot which may be hardware related since it's independent from rom or kernel. I had this happen a lot running fresh on my 002 phone and figured it was the rom, but I got a refurb 003 and it does the same thing stock

I've had this problem for about two months now, even though I have a launch-day Evo, hardware version 0003. When it first started happening, I had no idea what was causing it, though heat was my first guess, as the phone was getting hot. Then I installed the Clarus Battery widget on one of my homescreens so that I could monitor it. When the phone got to about 42-43°C is when it would reboot (and possibly bootloop). The more it happened, the lower the temperature threshold got, until it would start acting up at as low as 36°C.
After more investigation, I noticed that the phone would only reboot when it was using 3G. When I'm at home, I use my wi-fi, and though heavy usage would still cause the phone to get hot, it wouldn't reboot. Turn off the wi-fi and switch over to 3G, and poof! reboot.
I'm fairly convinced that the problem lies in the 3G radio. It's almost as if the heat at some point fouled a solder connection.
My device is rooted, I've used various radio baseband versions, ROMs, and kernels, and nothing made any difference. Expecting to return the phone to Sprint for a replacement, I unrooted and factory-reset the phone and still had the problem.
I took the phone to a Sprint store yesterday. After an hour of waiting, the tech told me that he factory-reset it, and installed and executed some sort of "stress test" application on the phone, and it passed with flying colors. It's some sort of graphic intensive application and to the best of my knowledge, doesn't use 3G - which I think is what the triggers the reboot. He gave it back to me, and the Market was auto-updating a few applications, which I canceled (leaving icons in the notification area). I opened the browser and after a minute or so, it reached 36°C and rebooted before his eyes. He tried to tell me that I had "lots of stuff running in the background" (i.e., the Market updates in the notification area) and that's why it was happening - because I'm "not using the phone correctly". I told him that I knew he was going to try to tell me that there was nothing wrong with my phone and push me out the front door as quickly as possible. To tell me that there's no problem with my phone and I'm using it incorrectly is completely outrageous and unacceptable. After "pulling rank" as a 12-year-long Sprint Premier customer that has never been late on a single payment, pays the $7 TEP every month, and has never returned a phone before, I made it quite clear that I would not be leaving the store without a new Evo in my hands. Begrudgingly, he finally gave me a new one.
Based upon other threads I've read on this subject and my own experience, getting a new phone is the only resolution to the problem.

Reception Problems

Is anyone else having reception problems? My cell connection keeps dropping. NO phone I've ever had before has EVER had reception problems where I am now... GAAHHHH

Yes, there are a lot of complaints about this. Mine seems to drop once or twice a week. You need to toggle airplane mode on and off to get signal back. Usually occurs when bringing the phone back from sleep mode.
This doesn't seem to be happening with the stock ROM, just custom ones. Something to do with radio firmware voltage. I've tried switching to the latest North America radio to see if that fixes the issue for me.

That's really frustrating. I might move back to AOSP for a while.

Some people have moved back to 4.0.3 until the issue is fixed.

zuberio said:
Some people have moved back to 4.0.3 until the issue is fixed.
Click to expand...
Click to collapse
4.0.3 custom ROMS? or 4.0.3 AOSP

4.0.3 customs

Tynen said:
Is anyone else having reception problems? My cell connection keeps dropping. NO phone I've ever had before has EVER had reception problems where I am now... GAAHHHH
Click to expand...
Click to collapse
I have an AOSP Galaxy Nexus with Bell in Canada and my connection drops at least a once a week... Used to have the N1 with Rogers and wherever I was on my daily routine, I always had full connection.
Triggering the Airplane mode sometimes work but it randomly just hang during the process of switching. When it get to that point, reboot is required and often I will get full signal after...
This last weekend, I was in a cottage and my friend would have full signal on her device while I would have no coverage at all... I had to get out the building to get 1 bar.
Starting to wonder if it's not simply an hardware problem since I kept the regional build on until now and that the carrier doesn't seem part of the equation.
Any thoughts?

I recently switched from the XXLA2 radio (international) to the UGLC1 radio (North America) and haven't experienced a drop yet - though it's only been a day or two.
One other thing I noticed, however, is that on XXLA2 my phone was on the Rogers Communication Network, but after UGLC1 it now says Fido.

Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
(I just replied that to another Q actually. Amazing how many people don't know / try that..)

Vangelis13 said:
Try either using the 7xx Mhz as minimum frequency or up the voltage by 25-50 on the 3xx frequency.
(I just replied that to another Q actually. Amazing how many people don't know / try that..)
Click to expand...
Click to collapse
I've actually never messed with voltages before. How would you suggest doing that? I'm on AOKP Build 4

Tynen said:
I've actually never messed with voltages before. How would you suggest doing that? I'm on AOKP Build 4
Click to expand...
Click to collapse
Aokp 4!? Why don't you update to 5 at least? That might be fixing your issue as well.
I think Aokp has a kernel tinker option built in somewhere, does it not? If not, try Franco's or Morfic's kernels & apps, they have it. Or search for SetCpu here on xda, it's free for members.
Flashing a new kernel might fix it.

[Q] Galaxy Nexus Signal degrading consistently from 4.0.2 through 4.1

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

JB 4.1.x wifi range/signal (GSM GNex)

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

[Q] VZW Extremely poor CDMA/LTE performance (Vicious JB 4.1 v5)

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- :\