Related
Ok so i have a xv6800 that i flashed to sprint and then to DCD 3.0.1, didnt let the sprint customizer run, and had no Data and got the same error some others got about this (PBP: 11, #777 no password)
After a few hours with tech support, we did find a solution however
The problem was (at least for my phone) i had a still active data connection going from before i originally flashed (not that they knew that, to them i just "hard reset", which is also true )
Basically it is an undetectable error that if you arent looking for it, you wont find it
The good news is, there may be a way to avoid this problem (and the A-Key problem as well) Simply put the plane into flight mode BEFORE FLASHING OILPROF, and continuing from there
I set my phone back to stock, got all the data and connections going alright, then put it into flight mode (effectivally disconnecting my data) and flashed it (Unlock, Sprint, DCD, in that order) and the phone retained the A-Key AND i had no more data woes.
I reverted back to stock and re-locked in twice more to make sure this wasn't an isolated insident, and each time i put it into flight mode and THEN flashed it and didnt lose any data
Now it is possible that this is a coincidence, but you can be the judge of that, all i know is it works
For those of you with this data problem already, causually mention (after you have given them a chance to "work out the problem") that you had trouble with the internet and had to hardreset the phone while online and that might have cuased the connection to stay open.
If they seem a little..... suspicious of that answer (my tech guy did lol) just say, "But then again i dont know how your network works, ive just had that happen with various programs before"
That line works well
And remeber.... being nice and laughing with the guy on the other side of the phone goes a long way in getting the problem fixed and making them relax
Because if they guess that you flashed a custom rom, they will write in the records where they can ALWAYS pull it up again
Hope this helps someone, and DCD great rom man, mabye next release can included the radio, lol
GamezR2EZ said:
And remeber.... being nice and laughing with the guy on the other side of the phone goes a long way in getting the problem fixed and making them relax
Click to expand...
Click to collapse
Good advice for almost anything in life when dealing with people.
Okay, here's an interesting observation. Ever since I rooted my phone the other day I have noticed that my phone is roaming for both data and calls 24/7. I have reset the device several times with no luck. I didn't notice this when I first rooted it but seeing how it's been roaming for nearly 2 days I have to assume it has something to do with it. I live outside of Boston and I am in the city very day so there's no reason why I should be roaming. Has anyone experienced anything similiar to this? I am wondering if I should just unroot the device and reset the phone to default settings.
I doubt that the phone would even work if you did this but is it possible you flashed a rom that wasn't meant for your phone and included an improper radio.img? More than likely your phone wouldn't boot at all if that happened though.
I would try flashing the factory ruu and see what happens.
http://forum.xda-developers.com/showthread.php?t=559622
Make sure to get the Sprint one.
flipzmode said:
I doubt that the phone would even work if you did this but is it possible you flashed a rom that wasn't meant for your phone and included an improper radio.img? More than likely your phone wouldn't boot at all if that happened though.
I would try flashing the factory ruu and see what happens.
http://forum.xda-developers.com/showthread.php?t=559622
Make sure to get the Sprint one.
Click to expand...
Click to collapse
I appreicate the input but I flashed the device exactly to the "tee" so I know that everything was done right. I made a recovery backup of my system file so I might just try to revert back and see if that fixes it or not. I just find it extremely weird the roaming just started out of no where.
penbralat said:
I appreicate the input but I flashed the device exactly to the "tee" so I know that everything was done right. I made a recovery backup of my system file so I might just try to revert back and see if that fixes it or not. I just find it extremely weird the roaming just started out of no where.
Click to expand...
Click to collapse
Everyone else that had done their phone right didn't have it roaming non-stop following the root. Not saying you did it wrong but you seem defensive about the possibility that you could have messed it up. Are you familiar with rooting phones? have you done it many times before?
benisntfunny said:
Everyone else that had done their phone right didn't have it roaming non-stop following the root. Not saying you did it wrong but you seem defensive about the possibility that you could have messed it up. Are you familiar with rooting phones? have you done it many times before?
Click to expand...
Click to collapse
I have done this "procedure" several times over again not with just Google's OS but also with the Apple OS as well as WM devices. I also did this with another Hero with no issues so unless there was a "hiccup" during the rooting process of this one particular phone I am at a loss. Again, nothing that can't be undone I suppose but it's a pain.
Could just be something wrong with the network towers in your area. The other day I noticed I was roaming a lot in my own home where I normally get decent service. It's fine now though.
Yeah, it's probably just something with the network. You live near Boston... and isn't Boston getting 4G this November? Maybe they're working on adding it to current towers in your area. Lucky! Well, Chicago is getting it soon too, but I haven't noticed anything yet.
So yeah... I flashed the new MoDaCo 2.0, and then decided I liked Fresh 1.1 better. So, I booted the recovery, and did a nandroid restore to right before I flashed to MoDaCo. Now, my phone is stuck in roaming where I had Sprint signal before... Yeah can someone help?
i forget what thread...
but....
there are some individuals.. that would like to do this !!!
do you still get 3g speeds when on roam only? If so I would love to do this. I only get 1x in my area
animal7296 said:
do you still get 3g speeds when on roam only? If so I would love to do this. I only get 1x in my area
Click to expand...
Click to collapse
I don't think Verizon allows 3g roaming.
Thats a very nice start!! it states then that it's possible to force ROAM our Hero!!! Now we just need to find out how to turn it on and off as desired. Roaming too much will flag your phone and Sprint might cancel your account. But for people with poor reception and good roaming reception in a place like work, its Golden. Nice discovery!!!
The thread about Force Roaming is:
http://forum.xda-developers.com/showthread.php?t=593249&highlight=force+roam
Ok, I have good news, and bad news. We'll start with the good
So if you want to try and replicate what I did to get force roaming, here's what you do (atleast what I did).
Be running Fresh ROM 1.1. Without wiping data, flash to MoDaCo 2.0. Now, if you look in the About Phone menu, it will say Needs Reboot. Reboot the phone. Now, remove "Dropbear". The phone will reboot again. At this point, I installed WaveSecure by using the .zip MoDaCo posted. A few minutes later, I decided I didn't like the MoDaCo ROM, so I did a nandroid restore back to RIGHT BEFORE I flashed to MoDaCo. After the restore was complete, I was back in Recovery Mode. I pressed Reboot System Now, and then once the phone booted, it was in forced roaming. Sadly, I only had 1xEV But hey, atleast it force roamed
Bad news: I rebooted my phone again (because I actually needed to use it), and it was once again using Sprint.
Maybe some dev can look into file changes between Fresh->Modaco-nandroid restore->Fresh? I'm not experienced enough with Android hacking to know how to mess with this stuff
mrinehart93 said:
Ok, I have good news, and bad news. We'll start with the good
So if you want to try and replicate what I did to get force roaming, here's what you do (atleast what I did).
Be running Fresh ROM 1.1. Without wiping data, flash to MoDaCo 2.0. Now, if you look in the About Phone menu, it will say Needs Reboot. Reboot the phone. Now, remove "Dropbear". The phone will reboot again. At this point, I installed WaveSecure by using the .zip MoDaCo posted. A few minutes later, I decided I didn't like the MoDaCo ROM, so I did a nandroid restore back to RIGHT BEFORE I flashed to MoDaCo. After the restore was complete, I was back in Recovery Mode. I pressed Reboot System Now, and then once the phone booted, it was in forced roaming. Sadly, I only had 1xEV But hey, atleast it force roamed
Bad news: I rebooted my phone again (because I actually needed to use it), and it was once again using Sprint.
Maybe some dev can look into file changes between Fresh->Modaco-nandroid restore->Fresh? I'm not experienced enough with Android hacking to know how to mess with this stuff
Click to expand...
Click to collapse
LOL nice explanation . Yeah, while you are roaming, you are limited to 1X, no EVDO. But it's a great start and thanks for sharing! Whomever is knowledgeable please try working on this. I sadly have no clue .
mrinehart93 said:
Ok, I have good news, and bad news. We'll start with the good
So if you want to try and replicate what I did to get force roaming, here's what you do (atleast what I did).
Be running Fresh ROM 1.1. Without wiping data, flash to MoDaCo 2.0. Now, if you look in the About Phone menu, it will say Needs Reboot. Reboot the phone. Now, remove "Dropbear". The phone will reboot again. At this point, I installed WaveSecure by using the .zip MoDaCo posted. A few minutes later, I decided I didn't like the MoDaCo ROM, so I did a nandroid restore back to RIGHT BEFORE I flashed to MoDaCo. After the restore was complete, I was back in Recovery Mode. I pressed Reboot System Now, and then once the phone booted, it was in forced roaming. Sadly, I only had 1xEV But hey, atleast it force roamed
Bad news: I rebooted my phone again (because I actually needed to use it), and it was once again using Sprint.
Maybe some dev can look into file changes between Fresh->Modaco-nandroid restore->Fresh? I'm not experienced enough with Android hacking to know how to mess with this stuff
Click to expand...
Click to collapse
Has anyone been able to replicate this?
I don't get a good sprint signal in my house and sometimes, in the right situation, it will switch to roaming. It then takes a few minutes to get off of the roaming tower and get back on sprint.
I am not saying you didn't force it to roam and don't take any offense, but it sounds like to me you booted your phone and it glitched or something caused it to not pickup the sprint tower (maybe there was a problem with the tower). Once you rebooted it tried again and was able to grab the sprint tower.
I don't see how flashing a rom would force it to roam. That just doesn't seem very likely. Considering a quick grep only brings up a few options for enabling and disabling the ability to roam, I doubt it was a problem with the flashing.
Hopefully, someone figures out how to force roaming soon. And I really hope I am wrong and this leads to a solution.
flexgrip said:
I don't get a good sprint signal in my house and sometimes, in the right situation, it will switch to roaming. It then takes a few minutes to get off of the roaming tower and get back on sprint.
I am not saying you didn't force it to roam and don't take any offense, but it sounds like to me you booted your phone and it glitched or something caused it to not pickup the sprint tower (maybe there was a problem with the tower). Once you rebooted it tried again and was able to grab the sprint tower.
I don't see how flashing a rom would force it to roam. That just doesn't seem very likely. Considering a quick grep only brings up a few options for enabling and disabling the ability to roam, I doubt it was a problem with the flashing.
Hopefully, someone figures out how to force roaming soon. And I really hope I am wrong and this leads to a solution.
Click to expand...
Click to collapse
Nah, it's ok. No offense taken Yeah, it's likely that it was just a glitch... I only posted what I did before the glitch happened, in the case that someone may be able to find it useful (mix match of files from ROM's or whatever).
I was playing around with this and, beyond changing the GPS settings and the navigation volume, I didn't change anything, just browsing.
Well, my phone rebooted a few times while in the ##DATA# section, even though nothing changed (that I am aware of), and now my phone no longer has 1X data, so my data goes away unless I have 3G.
Does anyone know what I may have changed that broke this? I haven't touched any settings in the main phone, as it happened while I was looking around in the secret menus.
Is there a way to restore all of the settings to default if all else fails? I tried doing the *228 option 1 programming, but to no avail. Still no 1X data.
-------------------
UPDATE: For those reading this thread because you have also lost data connectivity, I have solved my issue.
By a recommendation from the IRC channel, I activated a different phone (any phone will do, even a dumb phone), waited a while (I waited a day, just to be safe, but I don't think any delay is needed), then reactivated my Fascinate again. Once I rebooted after activation, the data was all back to normal again. No issues.
Keep in mind, you MUST do a new activation, not simply a *228 opt 1 while the phone is currently activated, as this does not seem to reactivate the data. It must be a new device activation (coming from a different device)
Hope this helps someone avoid the stress I went through.
Bump because this sucks.
Need help from devs!
+1 bump!
This is a serious issue as a result of people releasing the "secret codes" with no explanation of what each menu option does.
I, too, am experiencing intermittent data connectivity as a result of tinkering where I shouldn't have been. The OP and I are not holding anyone liable, but just asking for expert help to get our phones back in original working order. I really don't want to call Verizon, risking this becoming an insurance claim which requires a $150 deductable. I could drop Big Red and get an Epic or Evo with that money (contract is up in a couple weeks).
My problem is that the data connection seems to be going into an on-demand state, but when that demand is present, the connection will drop. If I wake the phone (press the power button to turn on the display and unlock), a 3G connection is present. However, if I try to start browsing the web, for example, the connection will drop completely within 1-2 minutes.
I've tried changing the "Set preferred network type" option (found in *#4636*1111# > Phone Information) to every logical option - WCDMA Preferred, CDMA auto (PRL), CDMA only, EvDO only, etc - to no avail. Looking at this menu right now, the preferred network is set to "Unknown". When I toggle the radio on/off from this screen, the "GSM disconnects" active log takes a few minutes to connect, and I see packet traffic. But, again, when I attempt to use that data connection, it will drop completely in short time. I've done everything I can think of, short of a full Odin restore.
Surely XDA has some cellular experts here - maybe even Verizon network techs - that know how to fix this.
i disagree with your first line. this is a n issua as a result of people who dont know what they are doing. not because it was leaked. if you dont know how to mess with your phones. dont. and if u do and screw up, dont blame anyone but yourself
Thanks for the not helpful reply. Argue in your own thread. I need help, not a finger pointing lecture.
Unless you know what caused my issue, you are just as ignorant as I am. The difference being I didn't climb on a soapbox about it.
Sent from my SCH-I500
lowkee said:
Thanks for the not helpful reply. Argue in your own thread. I need help, not a finger pointing lecture.
Unless you know what caused my issue, you are just as ignorant as I am. The difference being I didn't climb on a soapbox about it.
Sent from my SCH-I500
Click to expand...
Click to collapse
I'm in the same boat, lowkee. I'm just frustrated because I've posted this issue in 2 different forums and no one tries to help.
Just like you, I only changed the GPS Startup Mode to "cold" and looked around at other things - I touched nothing else. Last time I checked the GPS setting, it was back to "hot".
My intent was not to start a flame war or hijack your post. I was only trying to explain what I troubleshooting I've done in hopes that it may help you and, more importantly, get a response from someone who knows this topic front to back.
The response I got is the reason why my post count is only 2 (now). These days you can't go into any forum without risking backlash or flaming.
Back to the topic at hand - does anyone have any helpful suggestions for the OP? I'm just going to do a stock Odin restore and read up.
Let me know if that ODIN restore (and which part of it) fixes the issue. I have a suspicion it won't, and if it doesn't, I'm really worried.
Wiping is not an issue; I don't want to have to wipe for no benefit, though. Thanks for being the test subject
Ok. So I actually had to use the "force close loop" restoration method, including manual voodoo removal even though it should have been removed before - I never reapplied it. Data is staying up... nope, just dropped again. I'm really starting to hate this phone.
Here we go again... baseband version is the DI01 update, but build number is DH12. Removing root and going to try OTA update, IF data will stay connected long enough...
That DInc in my desk drawer is starting to look better every day. It's even one of the first batches that had the (AM?)OLED screens AND it has Froyo!
I hate to start typing this, but I believe I've fixed my issue. Here's what I've done so far (in order):
Removed Voodoo lagfix manually.
Wiped System via stock recovery.
Wiped system/cache/Dalvik cache via Clockwork Recovery.
Flashed stock system partition via Odin w/ PIT loaded.
Flashed stock kernel via Odin w/ PIT loaded.
Followed steps from the post "How to Escape the Force Close Loop of Hell" on AndroidCentral forums (sorry, can't post links yet).
Once fresh ROM loaded, installed CWM, fixed permissions & reboot.
Loaded the latest JT stable kernel.
Installed latest JT CleanROM.
And, of course, while I was typing this post, it dropped data connection when browsing the web, but not during the first time setup when Google Sync was processing. Very odd, but I'm now at a point where I feel I can troubleshoot further. Not going to install any unnecessary apps until I get this fixed. The SpeedTest.net app is good to test your connectivity - data immediately drops when I run it.
Also keep in mind that when I say that the data connection drops, I mean the 3G icon itself completely disappears and I get a network error. So back to the drawing board.
This is what i have had to do to correct 99% of all my issues ... results may vary and I base this off my own personal experiences:
To undo any changes that the hidden menu would have changed, I did a "factory data reset" from within the privacy options. Not from clockwork and not from teh original "-Vol and power". Neither clockwork or stock data and cache wipe clean out dbdata. It has to be done within the system options. Those of you not able to add new gmail accounts and super sekr3t phone code problems need to wipe dbdata via this method. Odin backups only restore kernel, recovery and system. dbdata remains untouched and contains these configurations. Ever wonder why after a clockwork wipe, it still remembers your gps options after you selected english and proceeded to configure? Hope this helps.
I'll give that a shot now, but doesn't the manual method to remove voodoo wipe /dbdata?
BTW, I had to perform the wipes from stock and CWM recovery because the system was stuck in a force close loop.
EDIT: So I did the factory data reset from within the OS and as soon as I try to open the browser, the network connection drops off. Time to call CS for a replacement. :-/
OP: As long as you haven't tinkered with funky ROMs or lag fixes, I bet this will solve your problem. Like you said, a wipe can't hurt anything but convenience.
jokerls240 said:
EDIT: So I did the factory data reset from within the OS and as soon as I try to open the browser, the network connection drops off. Time to call CS for a replacement. :-/
Click to expand...
Click to collapse
well ... crap ... So much for me posting something useful for once
zeiroe said:
well ... crap ... So much for me posting something useful for once
Click to expand...
Click to collapse
The help doesn't go unappreciated. I've just played with too much experimental stuff, thinking XDA has never let me down. I'm glad you stepped up with a logical suggestion!
Let's just hope this works for the OP.
Thanks guys for trying so many methods. I have a feeling the unreachable phone firmware is storing this data, which means it may not have a reset at all. Some guy in a cubicle somewhere has a document which shows all of those settings.. we need to kidnap that guy.
Seriously, though, this may require a phone replacement if we cannot get someone to tell us what setting controls 1X enabling and tell us the value it needs to be set at.
The conspiracy theorist in me wonders if this was intentionally done by the factory (or Verizon) to detect tampering. Say, you always have to change X value to Y when entering a certain menu or the configuration goes pear shaped. If I were trying to detect phone hackers, this would be my method of detection/prevention. I'm evil like that >
jokerls240 said:
I really don't want to call Verizon, risking this becoming an insurance claim which requires a $150 deductable. I could drop Big Red and get an Epic or Evo with that money (contract is up in a couple weeks).
Click to expand...
Click to collapse
The deductible for an advanced device is $89, not $150
This is beyond awful. Now I don't have 3g OR 1x data. I'm using Wifi right now to make this post.
There must be a way to fix this!
Sent from my SCH-I500
If you restore default this settings will go back to default too
Sent from my SCH-I500 using XDA App
Also you can use oddin to restore the stock kernel and software
Sent from my SCH-I500 using XDA App
I think its funny that people havent done a FACTORY RESET before posting here. Then they post they don't want to do one because they will lose all their data. Big wow, back it up, do a reset, restore and boom alls good.
martouf13 said:
I think its funny that people havent done a FACTORY RESET before posting here. Then they post they don't want to do one because they will lose all their data. Big wow, back it up, do a reset, restore and boom alls good.
Click to expand...
Click to collapse
So you really think a factory reset messes with radio settings?
Interesting.
Sent from my SCH-I500 using XDA App
So my girlfriend's Nexus S has been losing the entire voice and data network and going into no service mode, no biggie at first, just cycle airplane mode, then it went on to rebooting because you would select airplane mode from the power off menu but it would not check the box in the wireless settings menu.
After the reboot the box would show checked and airplane mode could be disabled and the service would resume. The the phone started getting stuck in airplane mode and not even rebooting it would bring it out the first few times, then it got to the point of resetting the phone, a wipe cache/data reset didn't fixed it. So off to T-Mobile for a new sim card. Rebooted the network immediately. And as of last night its back in full force and now not even a new sim will resurrect the network.
Have tried wiping, reflashing stock 2.3.3, new sim again, multiple resets, had to get an toggle widget to get it out of airplane mode and still a dead network, all this time the network in the *#*#4636#*#* menu showing unknown and is not able to be changed and reverts back to unknown immediately, OEM specifics settings button is greyed out and you are not able to disable the radio either.
While I'm going to call Samsung on Monday and I guess send the phone off, I worry about mine because it too does it but only once a month or so, but I do constantly have issues resurrecting the phone from airplane mode at times because the box will not be checked in the wireless settings menu but I can see the airplane instead of network bars, problem persists with reboots sometimes.
I also would like to add that even when the box is not checked in the wireless settings menu for airplane mode, if you click it it just hangs forever and will try to select but never will and stays grey like its turning everything off, but if the scren goes off its like you never tried.
Has anyone else seen this? I have seen a lot of people with data network issues or having to reboot to get voice network back but nothing as bad as I'm experiencing.
Both our phones are and have been completely stock and unmodified.
Thankfully we still have her Vibrant and in case I need to send mine in my Nexus One.
Sent from my Xoom using XDA App
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
cdaly985 said:
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
Click to expand...
Click to collapse
Is that true? I am just on the verge of calling samsung. My phone won't connect to or display any available networks, and is pretty much now dumbed down to a small tablet. I've tried everything except another persons nandroid backup. I've been told to stay away from flashing another persons... but I'm really desperate.
If you could provide me with a backup, that would be awesome.
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Gawthorne said:
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Click to expand...
Click to collapse
Can you search for and view available networks?
This sounds like the CM7 powerwidget problem (3g/2g) I used it and I loss all network, phone process will crash every second, however if your phones are stock I can't think in anything causing it.
For CM7 you'll have to reflash and delete userdata or edit the sql database for the providers and change a value to 0, but you need root.
When I went to *#*4636.... my preferred service was "unknown" too, but now it is OK.
Try to dail:
*#*#4636#*#*
and find your network information.
ketchup539 said:
Can you search for and view available networks?
Click to expand...
Click to collapse
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Gawthorne said:
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Click to expand...
Click to collapse
That is the EXACT same problem I have. I too was using Oxygen 2.1.6 and lost all connectivity. I've just locked my bootloader and flashed back to stock ready to send for repairs. That rom must be doing something >.>
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Gawthorne said:
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Click to expand...
Click to collapse
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
ketchup539 said:
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
Click to expand...
Click to collapse
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Gawthorne said:
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Click to expand...
Click to collapse
Ok, it'd be great if you worked something out. I'm so glad i'm not the only person with this issue!
Anyone had any breakthroughs? *hopeful*
I wouldn't call it a breakthrough but I got somewhere!
Ended up putting a extremely thin piece of wire into the external antenna port at the back of the phone. Wasn't too keen on doing this, but my phone now has reception isn't stuck at the dreaded -113dbm.
The reception isn't good, but it's enough to send texts and have calls.
Although the area needs quite good reception for me to receive anything, and it's extremely sensitive. To get 3 bars in a place where I usually get full bars, I have to be outside. While inside it's reduced to none or 1 bar, which is enough to send/receive texts and a sort of lagging phone call (did a few tests). As mentioned before extremely sensitive. The phone seems to like it better when it's up-right. In the middle of the CBD at Brisbane I get full reception and 3G, which is fine but in the places where you usually get 2 bars, you get no signal at all, unless you're outside.
So this is hardly a fix. I will most likely be sending it to Samsung to get it actually fixed. Either that or get it fixed the same day and pay probably close to $100 so I don't have to wait 2 months waiting for Samsung to twiddle their thumbs.
Thats awesome! But I'm going to post mine off to Samsung USA tomorrow, which will take forever considering international shipping. Where could you get it fixed same-day? I'm going to try this wire thing
So it can't be a software issue, but maybe the rom overloaded the antenna and fried it or something? I'm glad we've got that far.
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
RcrdBrt said:
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
Its more serious than that my friend! Thanks anyway
I got a quote from a place in Brissy called "FixMyMobile" and they said if they can fix it, it will cost $99. Although I'll get quotes from different places (if I find them) and see what they charge however I don't think I will be able to get cheaper, most likely around the same price..
So I may do that to not wait the ridiculous time it will take to get it back from Samsung.. Not sure on places in NZ though.
Yeah it seems like a hardware issue definitely. I eventually reverted the phone back to stock everything and it still happened, so that there shouts hardware issue.