Related
I tired to search but unsure if I pulled CDMA 100% or not..
None the less, Im going to move over to Verizon and Im after the Nexus. I see people say the signal is bad etc etc. Im coming from the HTC evo and Ive always prety much ran AOSP roms. As we know ( or us Evo users ) the AOSP roms dont show " full " signal. But it shows actual signal. Is this the issue people are ***** about? IS this what they are talking about, in terms of bad radios etc?
AOSP roms show the true signal, but not a masked/boosted signal similar to HTC phones done, right?
The bad radio rumor isnt a bad radio, just the way AOSP roms show the signal... right?
The bar reading was jacked up a notch in 4.0.4 (2 bars of signal in 4.0.1/2 will show up as 3 or even 4), but the db reading in Settings is still correct (though, read issue #2 below). The phone is fine hardware wise. What confuses (or convinces) people are three things:
1) Some people got duds. This will be very obvious because you won't get signal even in areas where other people on VZ can connect. You need to get the phone swapped.
2) The GN has a weird way of reporting signal strength. They completely over-do the hysteresis, so if you test/compare with another phone, you have to keep the GN in one spot for 10-20 seconds before you get the same reading.
3) Software bugs in the baseband which will crash the radio interface and leave you without data for up to a minute. There also appears to be some hand-off issues that may keep you on 3G when you should be on 4G.
The GN has no worse reception than any other Verizon handset, aside from the fixable bugs in the baseband, which really aren't "reception" issues anyway.
So with what you said, all the apparent issues that are there, are fixable in terms of ROMs or official fixes? I like to tinker with my phone, but not to keep it running correctly, ya know?
Is this issue still reported on the current batch of Gnex's?
I just got my Nexus a week ago, but it has worked perfect in terms of signal and data. No dropouts. My radio is whatever it came with, but my ROM is BAMF Paradigm
mroneeyedboh said:
So with what you said, all the apparent issues that are there, are fixable in terms of ROMs or official fixes? I like to tinker with my phone, but not to keep it running correctly, ya know?
Is this issue still reported on the current batch of Gnex's?
Click to expand...
Click to collapse
Personally, I've had fewer issues with the Galaxy Nexus than I did with the Nexus One (that phone DID have bad reception. Great call quality though) or the WinMo phone I had before that. Whenever I have connection issues, I just turn on and off airplane mode and the phone will come back and reconnect to 4G in ~15 seconds. Nothing serious beyond that.
Some people have had more serious issues, and I can't say if it was their phone or the network equipment used in their area or what. Only way to be sure is to try one out. I have little doubt that ~99% of GN users have little/no issue, but the ~1% that do have problems are vocal about them (they should be, this thing isn't cheap).
EniGmA1987 said:
I just got my Nexus a week ago, but it has worked perfect in terms of signal and data. No dropouts. My radio is whatever it came with, but my ROM is BAMF Paradigm
Click to expand...
Click to collapse
ROM has nothing to do with signal. Only the baseband matters.
ATnTdude said:
ROM has nothing to do with signal. Only the baseband matters.
Click to expand...
Click to collapse
Actually, if they have updated telephony, it can. For example, there are signal improvements in 4.0.4, but you must run the rom and the radios.
That said, Paradigm has made no telephony changes from aosp 4.0.3.
adrynalyne said:
Actually, if they have updated telephony, it can. For example, there are signal improvements in 4.0.4, but you must run the rom and the radios.
That said, Paradigm has made no telephony changes from aosp 4.0.3.
Click to expand...
Click to collapse
I was really simplifying things since this was a non-technical question. If you go from 4.0.2 to 4.0.3+, you may have more hooks into the kernel and from there into the baseband, but jumping randomly from ROM to ROM isn't the best way to solve a signal problem. Changing the baseband is the best way, kernel the next, and finally the Android version. Basically go in order of distance from the hardware, noting that each level is significantly less likely to cure you.
ATnTdude said:
I was really simplifying things since this was a non-technical question. If you go from 4.0.2 to 4.0.3+, you may have more hooks into the kernel and from there into the baseband, but jumping randomly from ROM to ROM isn't the best way to solve a signal problem. Changing the baseband is the best way, kernel the next, and finally the Android version. Basically go in order of distance from the hardware, noting that each level is significantly less likely to cure you.
Click to expand...
Click to collapse
After reading hundreds of posts on connectivity issues, yours is the first to bring some lucidity and sanity to the hardware issue. Now someone needs to focus on the BS from the carriers and the inadequacy of their distribution systems.
Hey everyone...Yesterday, on my stock, 4.0.4 GNex, I noticed I was getting terrible 3G speeds, and no 4G data whatsoever (even though the 4G signal existed). I thought maybe there was a temporary outage, but no dice...VZW support said there were no issues. Today, the issues still remain, and I have no idea what the problem could be. I took some screen shots, so if anyone could offer some advice, I'd really appreciate it. I'd love to try and resolve this myself instead of bringing it to some of the inept VZW techs at the local store. I'm located in Western NY and there is normally a great 4G signal here.
I can post screenshots once I am allowed since I'm a newbie here.
THANKS!
EDIT: I should add, I've experienced the 4G dropping to 3G for a while, and I know this is an ongoing issue with GNex users, but this is completely different.
rms2219 said:
Hey everyone...Yesterday, on my stock, 4.0.4 GNex, I noticed I was getting terrible 3G speeds, and no 4G data whatsoever (even though the 4G signal existed). I thought maybe there was a temporary outage, but no dice...VZW support said there were no issues. Today, the issues still remain, and I have no idea what the problem could be. I took some screen shots, so if anyone could offer some advice, I'd really appreciate it. I'd love to try and resolve this myself instead of bringing it to some of the inept VZW techs at the local store. I'm located in Western NY and there is normally a great 4G signal here.
I can post screenshots once I am allowed since I'm a newbie here.
THANKS!
Click to expand...
Click to collapse
Another case, same awnser, considering what you said, the device is running the latest official release, and it seems 4g never works at all: return it and get a new one, probably has a bad radio.
If we can get a NYC vzw user as yourself who doesnt have the issues you're describing, i think that would kill it as faulty hardware.
Sent from my i9250
bk201doesntexist said:
...and it seems 4g never works at all: return it and get a new one, probably has a bad radio.
If we can get a NYC vzw user as yourself who doesnt have the issues you're describing, i think that would kill it as faulty hardware.
Click to expand...
Click to collapse
Meaning the radio just went bad? I've had this since launch day and never experienced a problem until yesterday. Also, I'm far from NYC, so if anyone in Western NY (Rochester/Buffalo area) has the same issue, let me know please.
Well, you said you have a stock phone and it doesn't sound like yourself have made any changes to cause this. So, what is it that you want to do? Flash the radio firmware? Root the phone and try different ROMs? Go through all this so in the end you take it to the store anyway? If your description of the problem is accurate, then it does sound like you have a hardware issue. Just take it in and deal with the inept VZW techs.
netbuzz said:
Well, you said you have a stock phone and it doesn't sound like yourself have made any changes to cause this. So, what is it that you want to do? Flash the radio firmware? Root the phone and try different ROMs? Go through all this so in the end you take it to the store anyway? If your description of the problem is accurate, then it does sound like you have a hardware issue. Just take it in and deal with the inept VZW techs.
Click to expand...
Click to collapse
No I didn't want to do any of the things you listed. I was asking if anyone here could help me diagnose the problem, in other words, see if there's any way to prove it's a hardware issue. I wasn't sure if there were any applications I could get to run diagnostics checks.
rms2219 said:
Meaning the radio just went bad?
Click to expand...
Click to collapse
If you never experienced these issues before, yes.
I would eliminate a few things (simcard, check another 4g capable phone, side by side, see if it works fine) first and do some testing.
Sent from my Galaxy Nexus using Tapatalk 2
It ended up being the SIM card. They replaced it, and instantly the 4G worked again.
Galaxy S3 in midtown NYC and I've been having the same issue for the last day and a half....
bk201doesntexist said:
If you never experienced these issues before, yes.
I would eliminate a few things (simcard, check another 4g capable phone, side by side, see if it works fine) first and do some testing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
enigmaisdead said:
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my phone. I have actually gotten 3 new phones only to have them all do the same thing. I flashed to Jelly Bean hoping it would fix the issue but no luck.
Sounds like a hardware issue. I have flashed many roms, ICS and JB and all are good for reception. Once we got new radios 5 months ago it fixed my 3g to 4g handoffs when I would lose data for minutes if not an hour. All good now.
It's common issue for Google nexus. I am also having same problem. You may ask a replacement or switch network mode to "CDMA only" instead of "LTE/CDMA".
Sent from my Galaxy Nexus using Tapatalk 2
It happens to my Galaxy Nexus too. >_<
Happens to me too. From HSPA (which should bei constant high-quality in my area) down to 2G, and if I am in areas with bad coverage, it looses signal completely.
Finally, after several ROMs, and basebands haven't fixed it, I'm going to send it in, as soon as possible now.
Sent from my Galaxy Nexus using xda app-developers app
This is a hardware issue. I515.10 is the one I have and it does this as well, the I515.9 however does not seem to be affected. The .10 was made in china and the .9 in korea... or maybe the other way around, hell who cares... Bottom line is, its a huge issue that samsung should have addressed long ago.
For more info check out the samsung forums. I'm waiting on a replacement to come Monday.
Sent from my VS910 4G using xda app-developers app
Same thing
This is happening on mine too. I installed the stock rom on my Verizon GNex and the signal has deteriorated significantly, almost like 4.0.2
I'm hoping a fix, or the new binaries fix this issues and put it back to it's 4.0.4 state.
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Crandolph2001 said:
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Click to expand...
Click to collapse
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
enigmaisdead said:
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
Click to expand...
Click to collapse
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Crandolph2001 said:
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Click to expand...
Click to collapse
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
enigmaisdead said:
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
Click to expand...
Click to collapse
When it started acting up I hadn't rooted / romed yet. I am now rooted and have flashed to 4 different roms and every single one of them still had the issue. I may have had the issue on the first couple days and not noticed it for whatever reason...
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.
Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working
did you check your apn?
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up
Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!
I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.
Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)
i have 12.01
will try reflashing the latest radios
tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?
unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal
Any updates? I'm having the same problem
Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?
It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.
PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.
I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.
I recently reverted to stock on my at&t note 2. I am having wifi issues. The phone gets a strong signal from my router (-50) but I get authentication errors connecting if I am not very close. Standing 5 feet from the router I get terrible throughput. I am running dd-wrt and can see that the router is only getting -90 signal from my phone. Every other device is much stronger.
I have tried disabling wifi power save mode and have tried the OTA update to ucamh3 baseband.
Any suggestions greatly appreciated.
With a weak or malfunctioning wifi setup over multiple roms ....I might suspect a bad antenna ??
Not a for sure thing...but it should be considered...
Several of these devices were returned early on with antenna issues...
With a pure stock UCAMH3 rom running...wifi has been excellent...
I would try a clean slate data reset in recovery...and a router reset as well...
Then set up the wifi again on the device...
It's a long shot...but is certainly a good first step in diagnosing the device and the antenna...
Does the device suffer the same in other wifi areas ??
If not...look back to your home system....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.
kevingt01 said:
Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.
Click to expand...
Click to collapse
I'm on CyanogenMod now with no improvement. Router sees strength of -85 and SNR of 9 when I'm 5 feet away from it.
exact same issues here with i317. wifi worked great for about a year while rooted, and running multiple roms. i loaded SkyNote4.3 and it's been down hill ever since. I'm currently on DN3 4.3 and it works fine if i am close to my router as well. have S4, and Nexus 7 on same router, and they work fine with great signal, so it's not the router. I even removed security from my wifi as a test, and same results.
I have tried reverting to 4.1.2 and still no change. Appears to be SNR related at the moment, as my other wifi devices have 38-50 SNR values on DD-WRT, but my i317 has 10-12. No microwaves or any of that jazz going on, all 3 of these devices sitting next to each other when pulling values.
still investigating, but if anyone has any suggestions i'm open to ideas at this point.
what has been tried: reverting to 4.1.2 stock firmware from sammy, 4.2 bootloaders, 4.3 bootloaders, different modems, different kernels, different roms.
I got a replacement Note 2 from AT&T for this reason. I Googled the problem and found many mentions of it, so I called AT&T and had the CSR Google the problem while I was on the phone..
Of course I hadn't opened it up or anything...
I sent my phone to Samsung twice. The first time they just tried to update the software and claim it was fixed. That obviously did nothing to resolve the problem. I just got it back from a second visit to the service center where they replaced the mainboard. I haven't tried it yet, but expect that solved the problem. I'll confirm later tonight.
yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.
white8785 said:
yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.
Click to expand...
Click to collapse
I thought mine was antenna related so I bought a new housing. That didn't fix it. I read where one person bent up the contacts a little so I tried that and it didn't fix it. I never used to believe software would screw up the hardware, but I really believe some firmware has a bug that's pushes too much power to the wifi transmitter and damages it. That's just a hunch from a few posts I've read. It sounds like this may have happened to people with a Samsung OTA update.
If I were you, I'd log onto Samsung's site and just double check that you don't have any warranty left with them. If not, I'd even try chatting with them expressing disappointment in the device. let them know that apple geniuses would take care of you anyways. Maybe they'll be generous.. worth a shot.
So good and bad news. After getting my phone back from Samsung the second time, wifi authentication issues and drops are gone. The strength is good enough to keep me connected around the house, and speed is fairly consistent throughout the house, and is good enough for browser, etc. However, the speed still isn't up to par with other devices. I'm now experiencing 4-5mbps on speedtest.net (vs. ~20mbps on my other wireless devices). :/