Hi everybody,
I bought a note 3 from Verizon about one year ago, I started to have an WIFI issue that was not able to turn on (the button stayed in black-gray but never changed to on state), I thought with a hard reset that should be fixed but didn't remember that I had activated the activation lock(In that moment I was using stock lilipop), when the phone came up again I still wasn't able to access the WIFI so I'm stuck in there, I have tried flashing older ROM versions with no luck, the behavior was the same, do you know is this is a common issue or if there is anyway that I can modify a file in the system to fix this issue?, I'm in the Dominican Republic so I can't use the Verizon network to activate it.
Stock Android versions that I have tried:
4.4.2
4.4.4
5.0
In this screen it is supposed to show me all the available networks but instead when I press the Refresh button is saying this message but there is no wifi button to turn it on.
View attachment 4063616
Thanks in advance for your help.
bicefalo04 said:
Hi everybody,
I bought a note 3 from Verizon about one year ago, I started to have an WIFI issue that was not able to turn on (the button stayed in black-gray but never changed to on state), I thought with a hard reset that should be fixed but didn't remember that I had activated the activation lock(In that moment I was using stock lilipop), when the phone came up again I still wasn't able to access the WIFI so I'm stuck in there, I have tried flashing older ROM versions with no luck, the behavior was the same, do you know is this is a common issue or if there is anyway that I can modify a file in the system to fix this issue?, I'm in the Dominican Republic so I can't use the Verizon network to activate it.
Stock Android versions that I have tried:
4.4.2
4.4.4
5.0
In this screen it is supposed to show me all the available networks but instead when I press the Refresh button is saying this message but there is no wifi button to turn it on.
View attachment 4063616
Thanks in advance for your help.
Click to expand...
Click to collapse
I presume the turn on wifi note at the bottom is not an active button and settings->general->wifi won't activate.
My first guess, all else being equal, is that the WiFi radio died.
Sent from my SM-N900V using Tapatalk
I thought that but how can happen suddenly like that?, I was looking in the Internet and I see this is a common issue in Samsung phones but some of them can be fixed so I would like to test everything before buying a new phone.
donc113 said:
I presume the turn on wifi note at the bottom is not an active button and settings->general->wifi won't activate.
My first guess, all else being equal, is that the WiFi radio died.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
bicefalo04 said:
I thought that but how can happen suddenly like that?, I was looking in the Internet and I see this is a common issue in Samsung phones but some of them can be fixed so I would like to test everything before buying a new phone.
Click to expand...
Click to collapse
That's how most electronic parts work these days, they either work or don't.
If it was working, and suddenly stopped, with nothing else changed.. That's a good indication the radio itself crapped out.
Sent from my SM-N900V using Tapatalk
Related
Got my phone two weeks ago and I'm getting a problem with my search button. it keeps going off by itself like some one is pressing them and the speak now screen come up.
Any one else here having the same issue? Theres people in the internet also having the same problem but so far no answers.
Sent from my Nexus S using XDA App
I have this problem too but it only seems to happen intermittently when I am in an area with a poor signal (1 or less bars).
I've also taken to restarting my phone every day or two and It hasn't happened in awhile.
I had this problem with mine and when I looked it up it seemed I wasn't the only one. Most people seemed to think it was a hardware issue. I exchanged my nexus for a new one and the problem is gone so I guess it was hardware.
Sent from my Nexus S using XDA App
I got fed up so I called in for a new one sent to me. I hope this one is problem free!
It happens randomly but yes it seems to happen more when the signal is low.
I may have found the problem but not a solution. I noticed when playing with the phone that its always in Roaming mode. If you go to:
Settings>Wireless & Networks Settings>Mobile networks>
you will see that the "Data Roaming" feature is ENABLED which I believe has to be on since the phone is unlocked and you wont get data service if that is not enabled(for me anyway). Try Disabling this feature and just connect with a Wi-fI and play around with the phone. See if the issue still occurs. Mine stopped with this feature disabled and only comes back when it is enabled. The phone however is useless if this feature is not enabled if I'm not around any wi-fi.
Let me know if I'm right. Maybe someone good can create some sort of fix. looks like a software/program issue?
Having the same problem with my Droid X. Seems to be a software issue that is affecting Nexus S phones in Canada most severely, but also Droid X phones in the USA.
I'd include the link to the Google support forum thread but I'm too new of a user...
Flipst4r said:
I got fed up so I called in for a new one sent to me. I hope this one is problem free!
It happens randomly but yes it seems to happen more when the signal is low.
I may have found the problem but not a solution. I noticed when playing with the phone that its always in Roaming mode. If you go to:
Settings>Wireless & Networks Settings>Mobile networks>
you will see that the "Data Roaming" feature is ENABLED which I believe has to be on since the phone is unlocked and you wont get data service if that is not enabled(for me anyway). Try Disabling this feature and just connect with a Wi-fI and play around with the phone. See if the issue still occurs. Mine stopped with this feature disabled and only comes back when it is enabled. The phone however is useless if this feature is not enabled if I'm not around any wi-fi.
Let me know if I'm right. Maybe someone good can create some sort of fix. looks like a software/program issue?
Click to expand...
Click to collapse
Its not tied to roaming but to 3G. In your case turning roaming off turns of 3G.
Sent from my Nexus S
Over in the google forums, google has admited to the problem and will push out an ota to fix. No timeline
Sent from my Nexus S
Same problem here.. search button keeps triggering by itself. I see the button going on and off.. Trying to de-activate / unmap the button.. :silly:
Nexus S (Canada Rogers)
4.1.1 Cyanogenmod CM9 Final
Flipst4r said:
Got my phone two weeks ago and I'm getting a problem with my search button. it keeps going off by itself like some one is pressing them and the speak now screen come up.
Any one else here having the same issue? Theres people in the internet also having the same problem but so far no answers.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Had the problem last year on stock gingerbread with radio KB3, seemed to go away when fiddling with radio settings.
Have it again this year with ICS. Using radio KB3.
Notice when travelling in/out coverage zones. (Right at the edge, when coverage is weakest.)
Sent from my Nexus S using xda app-developers app
Supposedly a fix here:
http://forum.xda-developers.com/showthread.php?t=1815071
It doesn't provide a fix for us but there is a whole solution thread by the Samsung Fascinate section that seems to work!
http://forum.xda-developers.com/showthread.php?t=1551580
Since one of the solution is a kernel fix, maybe you can get one of the nice kernel developer to look at it to see if they can include it within their custom kernel
Hey all
I recently got my contract phone upgrade and got myself the motorola defy
The first phone I received, as soon as it would connect to 3G or Hsdpa it would reboot, forcing it into 2G helped but didn't solve the issue, it would still reboot without reason
So I sent it back
The second phone I received and currently using, has been mostly ok, except when you put the phone into airplane mode and then take it out, the phone tries to connect to the network, it connects for a few moments and then drops, it then does that a few times and then the phone reboots
Forcing it into 2G mode when it's in this loop fixes this, it connects fine and then I can put it back to automatic and it connects to 3G fine
Is this software issue with the phone? Or some odd conflict with my provider?
My phone is currently running stock 2.1 Rom, if that helps at all
Hi
Had a similar issue with the first Defy Plus I got. I sent it back. Have seen some similar threads about this but no solution, sorry. I am awaiting replacement number three after the second one had a faulty touch screen.
Regards
Dead_lemon said:
Forcing it into 2G mode when it's in this loop fixes this, it connects fine and then I can put it back to automatic and it connects to 3G fine
Is this software issue with the phone? Or some odd conflict with my provider?
My phone is currently running stock 2.1 Rom, if that helps at all
Click to expand...
Click to collapse
Could be hardware related. I think that the initialisation of the 3g module is not working as it should. Maybe the power management of the 3g module is broken? If you did not installed any custom firmwares or modded the stock one I would give it back and ask for a new one.
iRegistry said:
Could be hardware related. I think that the initialisation of the 3g module is not working as it should. Maybe the power management of the 3g module is broken? If you did not installed any custom firmwares or modded the stock one I would give it back and ask for a new one.
Click to expand...
Click to collapse
Mmm... I think I will restore to factory default, if it still does it then I guess I should take it back, really annoying, for such an awesome phone, it sure does have a lot of issues
And it will be another week and a half wait for it again :/
Thanks
Well doing a full factory default achieved nothing
Think I should take it in
Thanks for the advice
Now, my problem started when I updated my OS from jellybean to kitkat about 2-3 days ago (but my phone has a contract and was bought 13 Nov 2013). About a day after, I suddenly noticed some problems on my phone. Frequently, my Menu button, Home button, and back button will suddenly not work even when you press it. When this happens, the half portion of the screen is also not functioning to my touch. I can only make it work again if I press the LOCK screen or if I pull out the S pen. On the passcode pattern, only the two upper portions are working. Same method if I want to get it working again.
I tried to factory reset my phone and still the problem persists.
Does anyone of you had this problem during the update?
Hope anyone can shed light on this matter. Thanks.
Hi,
My n9005 had a similar behaviour when updated to kk then I took out it's unofficial cover. Screen and buttons are ok now, but I am having some other issues:
- sometimes when people call me, they think my phone is off, even it's on and displaying strong signal.
- No way to use 3g (only gsm and cdma options are available in setting menu, tried every single config, can't get 3g to work).
- camera is slow to save and react.
If any one have a clue about what I should do to fix this, please dont hesitate to suggest a fix (essentially for 3g issue, I can live with the other glitches).
Thanks again.
(Hope I didn't hijacked your post)
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hmm... mine is also SM-N9005 (or note 3). The guy from samsung said they better check it first and it could not be caused by the recent update...probably from hardware issues...
Imho, i's not hardware. I know a bunch of guys who suffer these symptoms just after updating via OTA to 4.2.2. Have to say that the unresponsive screen, mainly when entering phone passcode. Cicking the power/sleep button also worked for me when screen freezes. Samsung admitted that the kitkat update has changed the rules and that third party accessories(s-pen and other stuff) won't work with its devices (they said it's a bug that they gonna fix in the coming update)
I got my phone from Vodafone Spain, it was on jelly bean and working perfectly. Then I traveled to Morocco and wanted to use it with a local network provider (Maroc Telecom). Got it imei unlocked and he phone worked just ok. Then I was prompted for the kit lat update, did it via OTA and immediately the phone started to behave strangely (the kit kat syndrom).
The strangest thing is I can't get Maroc Telecom 3G network or any of the 2 other Moroccan providers' to work. When I looked at the settings, surprise: instead of listing "GSM only, 3g only, Lte only, Automatic..." it just shows " wcdma/gsm (auto)/wcdma only" options.
So till now, I can't get 3g to work, ever after checking APN, wiping, reseting, hard resting. I've read somewhere that this is had something to do with the network radio bands, but I am not sure about what to do to fix this (thinking about installing the cm11 nightly).
I hope you'll be luckier that I was and solve your note issues.
skalium said:
Imho, i's not hardware. I know a bunch of guys who suffer these symptoms just after updating via OTA to 4.2.2. Have to say that the unresponsive screen, mainly when entering phone passcode. Cicking the power/sleep button also worked for me when screen freezes. Samsung admitted that the kitkat update has changed the rules and that third party accessories(s-pen and other stuff) won't work with its devices (they said it's a bug that they gonna fix in the coming update)
I got my phone from Vodafone Spain, it was on jelly bean and working perfectly. Then I traveled to Morocco and wanted to use it with a local network provider (Maroc Telecom). Got it imei unlocked and he phone worked just ok. Then I was prompted for the kit lat update, did it via OTA and immediately the phone started to behave strangely (the kit kat syndrom).
The strangest thing is I can't get Maroc Telecom 3G network or any of the 2 other Moroccan providers' to work. When I looked at the settings, surprise: instead of listing "GSM only, 3g only, Lte only, Automatic..." it just shows " wcdma/gsm (auto)/wcdma only" options.
So till now, I can't get 3g to work, ever after checking APN, wiping, reseting, hard resting. I've read somewhere that this is had something to do with the network radio bands, but I am not sure about what to do to fix this (thinking about installing the cm11 nightly).
I hope you'll be luckier that I was and solve your note issues.
Click to expand...
Click to collapse
Okay, so here's the update. Last Sunday I was already set to bring this to Samsung Singapore for an assessment. So what I did was to put back the original casing (I am previously using a third party flip cover). I was observing it the whole day and suddenly my note 3 worked fine. Because of this I didn't bring it to Samsung. Now I am still observing it and so far no problems. I believe the reason is the flip cover... but it's strange as the affected portion is the lower half of the screen, home button, menu button and back button.
I hope you solve your problem on your note 3 as well.
skalium said:
Imho, i's not hardware. I know a bunch of guys who suffer these symptoms just after updating via OTA to 4.2.2. Have to say that the unresponsive screen, mainly when entering phone passcode. Cicking the power/sleep button also worked for me when screen freezes. Samsung admitted that the kitkat update has changed the rules and that third party accessories(s-pen and other stuff) won't work with its devices (they said it's a bug that they gonna fix in the coming update)
I got my phone from Vodafone Spain, it was on jelly bean and working perfectly. Then I traveled to Morocco and wanted to use it with a local network provider (Maroc Telecom). Got it imei unlocked and he phone worked just ok. Then I was prompted for the kit lat update, did it via OTA and immediately the phone started to behave strangely (the kit kat syndrom).
The strangest thing is I can't get Maroc Telecom 3G network or any of the 2 other Moroccan providers' to work. When I looked at the settings, surprise: instead of listing "GSM only, 3g only, Lte only, Automatic..." it just shows " wcdma/gsm (auto)/wcdma only" options.
So till now, I can't get 3g to work, ever after checking APN, wiping, reseting, hard resting. I've read somewhere that this is had something to do with the network radio bands, but I am not sure about what to do to fix this (thinking about installing the cm11 nightly).
I hope you'll be luckier that I was and solve your note issues.
Click to expand...
Click to collapse
I'm not an expert but it seems to me you updated hardware for Spain with Morocco firmware. I'm totally guessing here but you probably would need at least to flash different modem software to match your hardware. If I was you and Knox flag =0 I would probably try Samsung service first, once you start flashing custom stuff, most likely you will trip Knox flag and you may be totally on your own to fix it and there may not be many people with similar set up to help you out.
I here lots of people have trouble with KITKAT update OTA method.Try manual flash official stock rom with odin.
>mxv588t
Glad you could solve your problem
>pete4k
Thanks for the advice. Samsung guys are useless. They are formated to answer specific questions.
Will try to flash a compatible modem because I beleive Moroccan devices did not have kitkat update yet( and the ones that are officially sold here aren't strait n9005 but some variant (n9000ZWE, with this bizarre stock n900xxxubmhc_llc).
Thanks guys
Sent from my SM-N9005 using XDA Premium 4 mobile app
Same issue - did you find a solution ?
skalium said:
>mxv588t
Glad you could solve your problem
>pete4k
Thanks for the advice. Samsung guys are useless. They are formated to answer specific questions.
Will try to flash a compatible modem because I beleive Moroccan devices did not have kitkat update yet( and the ones that are officially sold here aren't strait n9005 but some variant (n9000ZWE, with this bizarre stock n900xxxubmhc_llc).
Thanks guys
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the same issue today. Did you find a solution?
guichankr said:
I have the same issue today. Did you find a solution?
Click to expand...
Click to collapse
Don't update through OTA. Download full firmware and flash through odin, and after that do full wipe. There should be no problem after that.
Sent from N9005 4.4.2 NB7 rooted device
antique_sonic said:
Don't update through OTA. Download full firmware and flash through odin, and after that do full wipe. There should be no problem after that.
Sent from N9005 4.4.2 NB7 rooted device
Click to expand...
Click to collapse
I have same problem with my Note 3 after upgrade to KK. Tried to flash full firmware and wipe after instalation,but problem with accidental freezing still persist.
Please help
Solved for my case : HW cover issue
antique_sonic said:
Don't update through OTA. Download full firmware and flash through odin, and after that do full wipe. There should be no problem after that.
Sent from N9005 4.4.2 NB7 rooted device
Click to expand...
Click to collapse
Hello,
I changed the back cover of the note 3 to bring it to the customer service.
I had the same experience as the other guy : with the original cover, the bug disappear.
Guillaume
guichankr said:
Hello,
I changed the back cover of the note 3 to bring it to the customer service.
I had the same experience as the other guy : with the original cover, the bug disappear.
Guillaume
Click to expand...
Click to collapse
Weird.
I use a fake cover. Everything is just fine.
Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.9.3 OC
excuse me, is it possible to go back to 4.3 via odin?
darkshaft said:
excuse me, is it possible to go back to 4.3 via odin?
Click to expand...
Click to collapse
Nope.
Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.9.3 OC
I confirm it, since I am back with the original back cover of my note 3, the freezing issue disappeared (since 1 week)
Is there a chip or a pin on the cover that could detect the phone ?
Sent from my SM-N900 using xda app-developers app
guichankr said:
I confirm it, since I am back with the original back cover of my note 3, the freezing issue disappeared (since 1 week)
Is there a chip or a pin on the cover that could detect the phone ?
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Yep. But I dunno which one. Hehhe
Sent from N7105, powered by DittoNote3 v.3.2 with AGNi PSN purestock v3.9.3 OC
Note 3 lock screen crash after kk update
ok so ive been following the forums for a while now, living with the lock screen crash, most anoying...
ive done all the above,.. put oem back cover back, problem seemed to go away, and only happen intermittently, but now its come back more frequently.
for me the most annoying part is not being able to answer phone calls when the lock screen lags, but ive gotten around this by either using my blue tooth ear piece or my gear.
my next step is go format the dam phone and reload from scratch, but im really not wanting to do that, given the rather large games installed, and the download times on my 2 meg connection takes days.
im hoping somebodie has a fix before i do the format reinstall
opiuz said:
ok so ive been following the forums for a while now, living with the lock screen crash, most anoying...
ive done all the above,.. put oem back cover back, problem seemed to go away, and only happen intermittently, but now its come back more frequently.
for me the most annoying part is not being able to answer phone calls when the lock screen lags, but ive gotten around this by either using my blue tooth ear piece or my gear.
my next step is go format the dam phone and reload from scratch, but im really not wanting to do that, given the rather large games installed, and the download times on my 2 meg connection takes days.
im hoping somebodie has a fix before i do the format reinstall
Click to expand...
Click to collapse
update, manually loaded firmware via odin, of the bat problem seems to have gone away, will let you know if it still persists.
help
mxv588t said:
Now, my problem started when I updated my OS from jellybean to kitkat about 2-3 days ago (but my phone has a contract and was bought 13 Nov 2013). About a day after, I suddenly noticed some problems on my phone. Frequently, my Menu button, Home button, and back button will suddenly not work even when you press it. When this happens, the half portion of the screen is also not functioning to my touch. I can only make it work again if I press the LOCK screen or if I pull out the S pen. On the passcode pattern, only the two upper portions are working. Same method if I want to get it working again.
I tried to factory reset my phone and still the problem persists.
Does anyone of you had this problem during the update?
Hope anyone can shed light on this matter. Thanks.
Click to expand...
Click to collapse
My note 3 has a problem that I recently noticed on kitkat official.
When I use a pattern lock frequently after unlocking a blank screen shows up for a second or 2. Help its really annoying
Hi all, basically had the UK 4g version of the Galaxy Note 3 kitkat 4.3 for about 3 months now. I now seem to be getting auto rotation problems (as in it not working) every hour or so that requires a reboot to get functionality back. It also seems to think all wifi networks are unstable and will frequently switch back to 4g data mode. Has anyone experienced this, and are there any fixes?
ICSVortex said:
Hi all, basically had the UK 4g version of the Galaxy Note 3 kitkat 4.3 for about 3 months now. I now seem to be getting auto rotation problems (as in it not working) every hour or so that requires a reboot to get functionality back. It also seems to think all wifi networks are unstable and will frequently switch back to 4g data mode. Has anyone experienced this, and are there any fixes?
Click to expand...
Click to collapse
Try to factory reset
bekasulaberidze said:
Try to factory reset
Click to expand...
Click to collapse
Have done so a couple of times so far, seems to just keep coming back.
ICSVortex said:
Have done so a couple of times so far, seems to just keep coming back.
Click to expand...
Click to collapse
You have to bring your phone to service centre, this is the solution..
I think we have the same issue
http://forum.xda-developers.com/showthread.php?t=2666250
think i also have the same been back into interlink b,ham samsung repair centre) three times now and the can't find a fault, been onto samsung and they say it has to have been repaired three times before the will escalate the complaint, i said its been in your repair shop three times. that don't count it has to have had parts changed three times.
very frustrated with it now does anyone have any suggestions?
tkwish said:
think i also have the same been back into interlink b,ham samsung repair centre) three times now and the can't find a fault, been onto samsung and they say it has to have been repaired three times before the will escalate the complaint, i said its been in your repair shop three times. that don't count it has to have had parts changed three times.
very frustrated with it now does anyone have any suggestions?
Click to expand...
Click to collapse
Go to WIFI in settings, when you can pick which wifi network you want hit the menu button at the bottom of the screen and select "Advanced". Untick "Scanning always available" and "Auto Network Switch". This will stop the auto matic switching from your home wifi to 4G and stop the battery drain of searching for wifi hotspots to link for even when wifi is off...
Not sure what to do about rotation as I'm on KK and have rooted already. Can use xposed modules to fix that but you can't if you're not rooted...
Sorry, but this will help with your wifi issues at least...
Hi all,
Regular reader but hardly ever post!
I have a Galaxy S4 (GT-I9505) - with Android 4.4.2. Unrooted.
Purchased and used in Singapore on the Starhub network since around October 2013. Everything was working fine until approx Feb or March when the latest Android version, 4.4.2 got rolled out.
Ever since then I am experiencing regular disconnections from the network. But the phone does not re-connect back to the network again, the only fix is to restart the phone.
These disconnections are often once or twice a day, and are very frustrating because if I don't notice it, I may be off the network for hours before noticing it - and are therefore missing out on calls emails etc etc.
This only happened after the Android 4.4.2 got rolled out, so I am pretty confident this is the cause of the problem.
What I tried myself to fix:
- restore APN's back to default state
- Factory reset (both via settings, and via boot screen)
What I have been able to narrow down troubleshooting, is:
- Disconnects seem to only happen when Network Mode is "LTE/WCDMA/GSM (auto connect)"
- If I use network mode "WCDMA/GSM (auto connect)" the disconnections have not happened (yet!)
- When the disconnection does happen in the first mode, I cannot manually change the network mode. The radio buttons are greyed out, and if I try to select "WCDMA/GSM auto connect" the request times out (I forget the exact message - it does respond to the tap but then nothing happens)
So it seems to me this is some sort of software bug/fault introduced with Android 4.4.2 that affects 4G connections.
After that, I have taken it to Samsung for warranty service. I have now had 4 visits to them and they have not been able to fix it yet. This is what they have done so far:
- First visit - factory reset (despite telling them I already did that) - did not fix
- Second visit - checked hardware and replaced mainboard. Did not fix.
- Third visit - checked hardware again and factory reset again. Did not fix.
- Fourth visit - who knows. I think same as visit three but done via a Service Manager instead of staff, Did not fix.
When I first called them back in Feb or March, they said it was a "known Issue' and sugegsted to "wait for a patch". However since visiting them, they said the known issue was only with Note 3's (not with S4's) and replacing the mainboard on the Note 3's fixed the problem. In my case replacing the mainboard - twice - has not fixed it.
I'm getting very annoyed with Samsung who seem to just be trying the same thing each time and are not fixing it. Staying in 3G only mode is a workaround but not an acceptable solution.
Now they've asked me to take if back again - for a 5th time.
Beginning to wish I had never bought the S4, or at least never got Android 4.4.2.
So I thought I would turn to here for help instead, I think you guys and gals probably know more than the Samsung service staff!
Any suggestions?
By the way, I don't run any memory/battery saver apps. I do run one data usage monitoring app that I thought perhaps was conflicting, so I tried not installing it after one of the resets, but the problem continued.
Chikara71 said:
Any suggestions?
Click to expand...
Click to collapse
you CAN try other modem flash, but be careful with your warranty.
I do not know about the warranty conditions in your country, but in EU normally 3 unsuccessful repairs = phone refund or replacement.
I would try reflashing stock file or just flash a different modem
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Dial *#1234# and paste here what appears.
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUFNBE
CP: I9505XXUFNBE
CSC: I9505OLBFNB3
I should add, I took it in *again* to Samsung, to the Service Manager. Said they would replace the antenna and try that, which they did.
Still have the same problem though.
Not sure who to believe, Samsung are starting to run out of ideas and starting to say it may be a network issue. But if the network is down, then the phone should automatically reconnect once the network is back available again. And it doesn't.
I'm convinced it's a bug introduced with KitKat, as the problem only started then, but of course I cannot prove it...
felgrab said:
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Click to expand...
Click to collapse
Sounds very similar to my problem, that it just started with Kitkat only. I'm sure it can't be just us two having this problem! I don't have anything special or different installed on my phone, and it's too suspicious that it was working fine, 100% perfectly until the KitKat software came out...
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUGNE5
CP: I9505XXUGNE5
CSC: I9505OXAGNE5
Thank you so much for giving us a hand!!
Chikara71:
I know it just cant be the two of us from such diferent places in the world but, i just cant find any similar in any post or google. It has been almost 3 months from the update an me using another phone...
Well I thought I would post again to close the loop.
After Samsung tried 5 times to fix my phone, checking hardware and trying to reinstall the OS with no luck, they suggested I try replacing my SIM card.
Surprise surprise, it has fixed the problem with no recurrence yet after a week so far.
I still don't understand how the sim card could be the problem, especially as my phone was working perfectly right up to the Kitkat software update. All I can assume is somehow KitKat either had an incompatibility with my simcard (maybe the new sim is technically slightly different?) or maybe KitKat somehow changed something on the simcard, if that's even possible.
Interestingly, I did contact my telco first, and they told me to contact Samsung. As it turned out, the fix was in the control of the telcom right from day one.
Anyway, so far the problem is resolved, so I thought I would post this here to help anyone that may have this problem.