Hi folks,
I just bought my S4 i9500 a couple of days ago. since the box opening I am facing the issue my Sim card shows the signals and then loose them, and this keeps on doing it after numerous restarts and battery pulling ultimately my phone connects to the network. It's a factory unlocked S4 bought form official store. I have tried almost 5 other sim cards as well only one has been able to connect without any issue, the rest have same problem. Phone recognized the sim, but when u try to make a call or sent a text msg signals drops.
I gotta know if any other fellow has faced such issue. As I have also concluded one thing, if my phone's internal temperature goes beyond 45c then all the sims are recognized by it, but as soon as I go down 40c sim cards just connect and disconnect.
I need your opinion, what might be the problem and is there any other fellow who has faced this issue.
I am seeing the exact same issue on my i9500, the signal just goes to null out of nowhere, and comes back a few seconds later. It's happened on both my US carrier (AT&T) as well as the Taiwan carrier I'm currently using (Chunghwa), so it's NOT carrier specific.
As a comparison, I used the exact same SIMs in my i9300 and never saw such issues. This is NOT good...
cmd512 said:
I am seeing the exact same issue on my i9500, the signal just goes to null out of nowhere, and comes back a few seconds later. It's happened on both my US carrier (AT&T) as well as the Taiwan carrier I'm currently using (Chunghwa), so it's NOT carrier specific.
As a comparison, I used the exact same SIMs in my i9300 and never saw such issues. This is NOT good...
Click to expand...
Click to collapse
So far what I have concluded that, if the temperature of my phone goes above 45C then this signal problem seems to be gone, but as son as the temperature goes below 40C signals start to drop. Well I would recommend you to try to raise phone temperature by playing some games or performing antutu benchmark or use it on wifi etc to increase it's temperature and then see what's the outcome.
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.
Bought an s7 edge 2 weeks ago, works like a charm.
But most of the time when i pick the phone, it just vibrates, when i turn on the screen, there are no notifications.
Is anyone else also experiencing this problem??
Samaksh. said:
Bought an s7 edge 2 weeks ago, works like a charm.
But most of the time when i pick the phone, it just vibrates, when i turn on the screen, there are no notifications.
Is anyone else also experiencing this problem??
Click to expand...
Click to collapse
What model is it ? And check for software update
@shazore
Its the SM935FD. I cant update because many people have reported their phones getting soft/hard bricked, if the update the phone with root access
Any other solution??
Samaksh. said:
@shazore
Its the SM935FD. I cant update because many people have reported their phones getting soft/hard bricked, if the update the phone with root access
Any other solution??
Click to expand...
Click to collapse
What region does your phone belong ?
I bought it from UAE and imported to india(where i live)