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.
Related
My Omnia 7 keeps loosing it's 3G connection. To restore it I have to restart the phone. T-Mobile say that this happens from time to time, but it's happening every day now. It's annoying as it stops my push email from being up to date, and of course prevents the use of any internet based services until the phone is restarted.
Has anyone else noticed their phone has switching to GSM?
Had mine for 6 days.Been fine up until today,then I had the same problem.Only the once so far.
Confirm loosing 3G
Confirm loosing 3G connection, and also have phone call failures.
Factory reset did not solve the problem.
Bring it back to shop
Blackstone is back now!
At first this was occasional with my phone, then more frequent, and it's all the time. If I want to use the Internet I have to restart the phone. My house is covered by full HSPA, but the only way to get it is to take the battery out while the phone is switched on. I can sometimes get 3G by a simple restart, which I lasts about 40 minutes.
I like the phone, so I'm going to hold out for a software update. All it needs to do is check available networks and I think that, if this is a wide spread issue, Samsung/Microsoft will fix it. Hope so.
Please post here if you have this issue too.
I have also been having this issue... sometimes it doesnt come back straight away when i restart it but after about 10mins its back.
When I activated it with orange I was told to expect a few txt msg's that would need deleting and the phone restarting... I only got 1 msg, maybe this has something to do with it, maybe the phone hasnt been sent enough updates.
I also have this issue and have done for weeks. Orange couldn't solve it either.
It only happens overnight at home. I either need to reset the phone / rescan available networks or turn flight mode off and on again for the connection to restore.
I was thinking it may be an issue with t-mobile since it only happens at my home where orange signal is poor and i roam over to t-mobile.
If i stay in an area with good Orange signal i don't get the problem.
Good to know i'm not the only one with this problem. It's very annoying!
Hi y'all.
I had the same problem: 3G was lost every time. I was fed up restarting the phone every time, so I looked for another way to get 3G back. I found out that disabling and enabling SIM security (phone > setttings) got me 3G again... for a short while.
But: after disabling SIM security permanently, 3G kept on going (in fact for over a week now).
I think that changing the PIN to some other number, might cause this. I haven't yet tried changing it to the default PIN again, to see if using that for SIM security solves it. For the moment I'm too happy it works again.
I have suffered from poor reception issues ever since I got my Omnia 7.
It seems like the reception comes and goes. I will receive e-mails, which proves that the phone has been connected, but as soon as I try to use data myself, by visiting a web page or refreshing an app like facebook, the reception disappears and the "no reception" symbol drops down from the status bar.
Also, often when I try to send an SMS, it will appear to have been sent, yet 10 minutes later I will receive a "Can't send...try again" message. Once I have received this, the SMS will never successfully send. However, in the meantime I can receive SMS messages, which shows that the phone has been getting a signal.
This is SO frustrating and is ruining my experience with the phone.
I have posted requests on the Microsoft Answers forum and the only suggestions have been to reset the phone or turn WiFi off. Neither of these have had any effect. I have never enabled SIM lock.
I have heard that there is a firmware update due soon which includes a new radio stack. I am desperately hoping that this will improve the situation, as at the moment I cannot rely on my Omnia 7 as my only phone.
Alex.
Hi Loco,
You are right in saying that social answers doesn't really help much .
Luckily there IS a new firmware from a couple of days ago! Check out the Omnia 7 Dev section. There are only a few posts.
And here is also a good link for you. You are right to assume that it comes with a new radio stack which improves on performance.
http://wmpoweruser.com/new-samsung-omnia-7-firmware-and-news-of-a-keyboarded-omnia-8-leaks/
Finally found a thread on this... I have been having a similar problem since I got my phone from Optus here in Australia. I took it back and they replaced it for me but the new phone is exactly the same. I don't lose the 3G icon but anything data related just ceases from loading. Right now I'm trying to refresh the Facebook app and it just comes up with 'Unable to connect', even though I have full 3G reception.
I flashed it to the newer leaked firmware and it hasn't changed anything, problem still persists unfortunately. This is a major problem that isn't getting enough attention! It seems quite widespread and Omnia 7 specific.
Had similar problems, but after I changed my provider ( O2-Germany), 3G is stable.
For the people having this problem, have you tried setting the phone to prefer 3g? Details of how to do this are here http://forum.xda-developers.com/showthread.php?t=915813
johnnymatrix said:
Finally found a thread on this... I have been having a similar problem since I got my phone from Optus here in Australia. I took it back and they replaced it for me but the new phone is exactly the same. I don't lose the 3G icon but anything data related just ceases from loading. Right now I'm trying to refresh the Facebook app and it just comes up with 'Unable to connect', even though I have full 3G reception.
I flashed it to the newer leaked firmware and it hasn't changed anything, problem still persists unfortunately. This is a major problem that isn't getting enough attention! It seems quite widespread and Omnia 7 specific.
Click to expand...
Click to collapse
Same here man. On Optus and my reception sucks with this device. What the hell is samsung doing? FIX IT!
I have been having this problem with my Omnia 7. The frustrating thing is this is a replacement phone I had for an LG which I had replaced THREE TIMES due to random resets. So now I have a phone that I have to turn off and on EVERY MORNING in order for the data connection to start working again. Needless to say I am very frustrated. I am on Orange in the UK. I suspect it could be related to when being an a poor reception area and it tries to switch to tmobile. I am going to try turning roaming off. Please, if anyone finds a solution to this let me know.
Thanks
m4tthall said:
I have been having this problem with my Omnia 7. The frustrating thing is this is a replacement phone I had for an LG which I had replaced THREE TIMES due to random resets. So now I have a phone that I have to turn off and on EVERY MORNING in order for the data connection to start working again. Needless to say I am very frustrated. I am on Orange in the UK. I suspect it could be related to when being an a poor reception area and it tries to switch to tmobile. I am going to try turning roaming off. Please, if anyone finds a solution to this let me know.
Thanks
Click to expand...
Click to collapse
My problem got worse with the Mango update. I'm now on my 2nd handset after having a replacement from Orange warranty. This one still loses it's connection but much less frequently.
TBH i don't think it will ever get fixed. I started an MS Answers thread months ago and lots of people had the same problem but we never got a response from MS.
Conisdering the age of the model now I doubt Samsung care, well they didn't seem to care a year ago so they won't now... For this reason I will not buy another Samsung phone. It's infuriating.
Looks like I am stuck with it until December then when I can upgrade to a Nokia lumia. A long wait :-(
i have this issue, too.. but for me i only have to set airplane mode on and off. sometimes i deactivate data connection, go to a random website, get the 'no connection' error, then activate data connection back and it works.
however, after installing the latest drivers & firmware, i get this issue A LOT less frequent. like once in 2-3 days.
i hope ms or samsung will fix this because it can get really annoying. especially when you need eg. a quick google-search..
Just flicking the flight mode wouldn't be so bad but that doesn't work for me, I have to restart the phone each time. I love WP7 but this and the other problems with the LG is driving me nuts. Almost wondering whether I should have just followed the crowd and gone for an iPhone.
m4tthall said:
Just flicking the flight mode wouldn't be so bad but that doesn't work for me, I have to restart the phone each time. I love WP7 but this and the other problems with the LG is driving me nuts. Almost wondering whether I should have just followed the crowd and gone for an iPhone.
Click to expand...
Click to collapse
Same as me - Flicking flight mode on-off doesn't solve it, needs a soft-reset.
Like I say, there are quite a few with Omnias on Orange with this problem.
I'm in the same boat, I've had this for months now so I guess I'll just deal with it until I can upgrade the start of April and get a Lumia (hopefully the EU 900/910 will be here by then!). There is no way on this earth Samsung are getting any more of my money. Nokia seem fully commited so they can take my cash next time!
I have the same problem with the data stopping working on o2 in the UK. But I also sometimes cant receive calls even though the phone has service, then there are the times where it site there going GPRS/3G/3G+/No Service and you cant do anything with it apart from pull the battery.
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
I have N910F variant, when I enter in flight mode and leave it like that for a longer time, let's say over night, the phone cannot find reception only after a reboot. It either says cannot connect or no sim card... I have the latest NK4 firmware but I had thid problem since day one. Also many times per day the recrption freezes. It looks like I have reception but in fact I cannot make or receive calls or messages. Again only a reboot helps. I took the phone to the service center of my career (Orange Romania) they only did a wipe and reinstall the software. Wich of course didn't help. Did any of you experience something similar?
Should be a firmware bug.
vndnguyen said:
Should be a firmware bug.
Click to expand...
Click to collapse
I sure hope so, but after 2 firmware updates everything is the same...maybe I will wait for thd Lollipop update and if that doesn't help, I eill have to send the device again to service.
I've noticed this happen on my Nexus devices as well (using note 4 currently). Could it be carrier related rather than a firmware bug?
I don't think it is the carrier's issue.
I forgot to mention that the first thing I did was to change the SIM card. That didn't help. I still have my Note 2 with which I have no problem with. So I don't think it is the career.
Hi guys, i know this is a common problem, but i have yet to find a solution to it. My S4 (Bell Canada, KOT49H.I337MVLUFNI2, completely stock unrooted) will drop the mobile network (both voice & data), and the only way to get reconnected to Bell is by rebooting my device. After a reboot I might be good for a few hours or for a few days but it always happens again. At first the mobile signal will grey out, then eventually turn to a circle with a line through it. In the network mode setting becomes blank and non-selectable.
Suggestions around the web include selecting WCDMA only, clearing the cache, factory resets, and reflash the full firmware package with Kies3 & Odin. Ive tried them all and the problem always inevitably returns.
Here are a few links to people with similar problems, but nobody seems to have a solution in any of these threads either:
https://community.sprint.com/baw/message/773419
http://forums.androidcentral.com/sa...fter-update-won-t-stay-connected-network.html
https://support.t-mobile.com/thread/68518
http://thedroidguy.com/2014/02/samsung-galaxy-s4-4g-wont-stay-connected-84465
http://community.koodomobile.com/koodo/topics/samsung_galaxy_s4_4_4_2_connectivity_issue
https://www.youtube.com/watch?v=GlHK11pE7kA
Other than returning it for a replacement under warranty, does anybody have any other suggestions to fix this? Thanks.
anyone?
Are you sure your problem isn't the same as the sim card removed problems? Because the symptoms sound the same in the effect they have, and what is required to temporarily fix it.
See here and here.
I've experienced the same problem, but it seems to have cleared itself.
It first started happening after the update to the latest Bell stock firmware.
I had read some people blaming it the Amazon app store as well as the Skype app. I had both installed, but have since removed Skype but can't say 100% that this is what solved the issue for me.
Sent from my SHIELD Tablet using XDA Free mobile app
I have the same problem, this is not the sim card removed problem, this is a bug in Android 4.4.2 because the problem was not present in 4.3 maybe the recent update to 4.4.4 solve this, has someone try out ?
FarmGeek4Life said:
Are you sure your problem isn't the same as the sim card removed problems? Because the symptoms sound the same in the effect they have, and what is required to temporarily fix it.
See here and here.
Click to expand...
Click to collapse
My SIM card is still in place and detected, the phone just disconnects from the network. After a reboot it will be fine sometimes for a few hours - sometimes a few days, but it always inevitably disconnects.
If you check any of the several links I posted you'll see there are hundreds (if not thousands) of people on all different carriers all experiencing the same problem.
emptyPD said:
I have the same problem, this is not the sim card removed problem, this is a bug in Android 4.4.2 because the problem was not present in 4.3 maybe the recent update to 4.4.4 solve this, has someone try out ?
Click to expand...
Click to collapse
I've had my device since Jan of 2014 and the problem only appeared in the last few months following the 4.4.2 update.
I'm having the same problem. It disconnects and reconnects again. Stays disconnected for about 2 mins. Happens like 12 times a day. I re enter the apn setting and still does it..it happens with every rom I flash. I've notices that it mostly happens when it switches from 4g lte to 4g. I'm on At&t 4.4.4
bump. anyone ever find a solution to this?
so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance
I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem
krishelnino said:
I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem
Click to expand...
Click to collapse
Did you pay the $20? I didnt want to pay the 20 so i sent the device to samsung. Should get it back friday or monday. The issue is definitely phone related. Im using a verizon s7 now and no issues like that arose. I even tried new sim.. My father is having same issue t-mobile s7 edge
Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk
I've suffered the same issue from time-to-time and just do a restart....annoying as hell to be honest
Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.
This happens to me all the time. It's so annoying. At work, in the car, at home--it doesn't matter where I am. Have reset firmware multiple times and even rolled back once too. I think it has to do with the latest software because I never had this issue before the Fall/Winter. Hopefully Nougat fixes this!
Quickvic30 said:
Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.
Click to expand...
Click to collapse
I happens randomly in different places. For me i lose complete signal, and then only get back signal without data. I have to restart when this happens to get back data. Annoying as hell !
frappe33 said:
so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance
Click to expand...
Click to collapse
I am having the same problem, this will be my 3rd phone 4th sim. I wish I knew how to fix it
I would try flashing different radios/modems, its worth a shot. Maybe try flashing the "U" firmware radios.
Nougat will fix it
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...
I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.
You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.
ronstopable12 said:
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...
Click to expand...
Click to collapse
I hope so! Been waiting for that before I try anything drastic, even though this issue is a huge pain in the ass. I'm glad others have come out of hiding to express their concerns with it as well. I thought I was the only one for the longest time having this issue.
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
jimfun said:
I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.
Click to expand...
Click to collapse
Many of us have tried new SIM cards, but it's worth a shot if it's still not working consistently after Nougat is released.
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
geeserver said:
You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.
Click to expand...
Click to collapse
My and my friend's phones are both running pure 100% OEM Tmo stock without any apps disabled or touched at all and we have this issue and have done multiple resets. Pretty sure it's an actual hardware defect, or hopefully just a software one with the modem/radio.
krishelnino said:
Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.
4ringsa6 said:
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.
Click to expand...
Click to collapse
I received a refurb. Other than this problem, the phone is alright. I noticed this problem on receiving the phone it was running on T firmware. Then I switched to U firmware and radio but no difference. I called customer support yesterday, they said to go to a retail store to get the phone replaced. My worry is going through this process again and if I receive a bad device again what to do? After all refurb phones are like playing Russian roulette!
Sent from my SM-G935U using Tapatalk
I just had this start happening on mine... I really wish they would release nougat already. It is ridiculous they won't post an Odin flashable version of the release candidate if it does indeed fix the issue.
I also think its a specific tower configuration that is causing the issue that the radio can not understand. (Maybe 3xCA). Its happening in the same areas every time.
I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?
flarbear said:
I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?
Click to expand...
Click to collapse
If you were able to fix without a reboot you didn't have the same issue as this.
rocket31337 said:
If you were able to fix without a reboot you didn't have the same issue as this.
Click to expand...
Click to collapse
I guess I wasn't clear about that as I have several problems that are probably related, but behave a little differently.
BT dropping - can usually turn it back on, but sometimes it refuses. Usually don't need to reboot to fix this.
Wifi dropping - often have trouble turning it back on and have seen the widget toggle off and on repeatedly by itself. Sometimes have to reboot to fix that.
Mobile Network data (and voice sometimes) dropping - usually have to reboot. I think I may have recovered that once without a reboot, but the other few times it's happened in the past month since it started I have rebooted and that fixed it in all but one of the reboots - one time I rebooted and still had to fiddle with it a bit after the reboot before it came back. That may have been because I played too much with the network settings before the reboot and so had to undo that damage after the reboot. But, definitely rebooting is a fairly reliable step in fixing this problem.
All 3 started happening around the same time which is why I thought it was a software issue (I remember a small update a little over a month ago, but forget the details of it). It's nice to hear that others also have the mobile network problem, but if that is isolated in those cases then maybe I'm not seeing exactly the same problem. But, it is clear that rebooting is almost always required to get my mobile network data back so that again suggests that at least that part is the same as what this thread is discussing.
In looking at the T-Mobile updates page for the S7 Edge I see that the version I have (G935TUVU4APK1) was updated in early November - which tracks when I started having problems, and it includes a fix for "Domestic data roaming improvements", which definitely sounds like they may have played with the radios.
I am so ready for the Nougat update...