Hi fellow xda members I'm at my wits end with my s5 the next step is the samsung store but my device is rooted so I'm not sure that's actually an option. So I have the canadian w8 variant with Fido and currently rocking alliance rom no xposed. Now the problem: It actually started a week or so after I got the phone my text messages would just idle at sending and not actually send for sometimes as long as 20 minutes I surfed the interwebs for a solution and all I found was people with the same problem but no solution. I tried messing with my apn settings changing my mms proxy and such and still the problem persisted. It actually got worse. I came to realize that the messaging hanging wasn't the problem it was actually a symptom. The actual problem is that after a call my lte switches to H+ or 3G which is totally normal and I know it.The problem is that after I hang up not only do I stay one 3g for an obscenely long time, all the while, even though I see the signal bars and the H+ or 3G icons I have no internet and I'm unable to send text messages since it relies on my data. 4G or LTE eventually comes back after around 5 minutes and everything is back to normal. Until the next call... What I've done: A couple of factory resets and I also change sim cards since I had one from two phones ago but still NO CIGAR. Fido has no clue, they claim that nobody has that problem. They say I have to take it to samsung for repairs... but I tripped my knox while rooting so I'm not sure what they'll do. I was thinking about maybe flashing a different modem?
Any suggestions?
mrnovanova said:
Hi fellow xda members I'm at my wits end with my s5 the next step is the samsung store but my device is rooted so I'm not sure that's actually an option. So I have the canadian w8 variant with Fido and currently rocking alliance rom no xposed. Now the problem: It actually started a week or so after I got the phone my text messages would just idle at sending and not actually send for sometimes as long as 20 minutes I surfed the interwebs for a solution and all I found was people with the same problem but no solution. I tried messing with my apn settings changing my mms proxy and such and still the problem persisted. It actually got worse. I came to realize that the messaging hanging wasn't the problem it was actually a symptom. The actual problem is that after a call my lte switches to H+ or 3G which is totally normal and I know it.The problem is that after I hang up not only do I stay one 3g for an obscenely long time, all the while, even though I see the signal bars and the H+ or 3G icons I have no internet and I'm unable to send text messages since it relies on my data. 4G or LTE eventually comes back after around 5 minutes and everything is back to normal. Until the next call... What I've done: A couple of factory resets and I also change sim cards since I had one from two phones ago but still NO CIGAR. Fido has no clue, they claim that nobody has that problem. They say I have to take it to samsung for repairs... but I tripped my knox while rooting so I'm not sure what they'll do. I was thinking about maybe flashing a different modem?
Any suggestions?
Click to expand...
Click to collapse
If you rooted with Towelroot, you can use Odin to reflash the stock ROM/Kernel and your Knox counter will be 0x0, so you would technically be under warranty.
I'm already rooted bro towelroot didn't even exist back then.
Sent from my SM-G900W8 using Xparent Cyan Tapatalk 2
mrnovanova said:
Hi fellow xda members I'm at my wits end with my s5 the next step is the samsung store but my device is rooted so I'm not sure that's actually an option. So I have the canadian w8 variant with Fido and currently rocking alliance rom no xposed. Now the problem: It actually started a week or so after I got the phone my text messages would just idle at sending and not actually send for sometimes as long as 20 minutes I surfed the interwebs for a solution and all I found was people with the same problem but no solution. I tried messing with my apn settings changing my mms proxy and such and still the problem persisted. It actually got worse. I came to realize that the messaging hanging wasn't the problem it was actually a symptom. The actual problem is that after a call my lte switches to H+ or 3G which is totally normal and I know it.The problem is that after I hang up not only do I stay one 3g for an obscenely long time, all the while, even though I see the signal bars and the H+ or 3G icons I have no internet and I'm unable to send text messages since it relies on my data. 4G or LTE eventually comes back after around 5 minutes and everything is back to normal. Until the next call... What I've done: A couple of factory resets and I also change sim cards since I had one from two phones ago but still NO CIGAR. Fido has no clue, they claim that nobody has that problem. They say I have to take it to samsung for repairs... but I tripped my knox while rooting so I'm not sure what they'll do. I was thinking about maybe flashing a different modem?
Any suggestions?
Click to expand...
Click to collapse
Im having exact problem and im with Rogers
ChantalCaron13 said:
Im having exact problem and im with Rogers
Click to expand...
Click to collapse
The new update fixes it.
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
mrnovanova said:
Hi fellow xda members I'm at my wits end with my s5 the next step is the samsung store but my device is rooted so I'm not sure that's actually an option. So I have the canadian w8 variant with Fido and currently rocking alliance rom no xposed. Now the problem: It actually started a week or so after I got the phone my text messages would just idle at sending and not actually send for sometimes as long as 20 minutes I surfed the interwebs for a solution and all I found was people with the same problem but no solution. I tried messing with my apn settings changing my mms proxy
Click to expand...
Click to collapse
Next time, please use paragraphs. Your post is painful to read.
If your Knox flag still says 0x0 then you can unroot and seek help from the Samsung store. If your Knox counter is tripped, I don't think that the Samsung store will honour your warranty. Rogers might. Some carriers don't care about Knox, but I don't know how Rogers views this. Try a forum search for insight on that point.
However, as suggested above your issue may be resolved in a simpler manner. The latest 4.4.3 /4.4.4 updates resolve wifi and text issues. So it would probably be a good idea to try the new update and see if that helps. Otherwise, you could try a different modem or a custom ROM. The latter may trip Knox if that matters to you i.e. if it has a custom kernel or recovery, so keep that in mind.
.
mrnovanova said:
The new update fixes it.
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
It didnt fix for me. Maybe it has to do with the apn?
ChantalCaron13 said:
It didnt fix for me. Maybe it has to do with the apn?
Click to expand...
Click to collapse
Just to be sure we're on the same page, by update you mean F3 not D1 right?
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
fffft said:
Next time, please use paragraphs. Your post is painful to read.
If your Knox flag still says 0x0 then you can unroot and seek help from the Samsung store. If your Knox counter is tripped, I don't think that the Samsung store will honour your warranty. Rogers might. Some carriers don't care about Knox, but I don't know how Rogers views this. Try a forum search for insight on that point.
However, as suggested above your issue may be resolved in a simpler manner. The latest 4.4.3 /4.4.4 updates resolve wifi and text issues. So it would probably be a good idea to try the new update and see if that helps. Otherwise, you could try a different modem or a custom ROM. The latter may trip Knox if that matters to you i.e. if it has a custom kernel or recovery, so keep that in mind.
.
Click to expand...
Click to collapse
Thanks I'll make paragraphs next time.
Sent from my SM-G900F using Xparent Cyan Tapatalk 2
Related
Hey guys,
This is actually my first post here but I do A LOT of reading on this forum.
I didn't quite find anything regarding my question (or at least a solid answer), however, so I've decided to post it up.
Has anyone else experienced a sudden loss of data from time to time out of nowhere?
I go from having Full Green 3G bars to grey bars out of the blue. I've heard the green bars is to let you know that you are connected to Google services but I am not able to access anything that uses data.
For instance, when I open up the browser, I receive an error telling me there is no network connection. When I open up anything else that uses a data connection, Market, News, etc, I receive the same error about there not being a connection.
This would make sense if I was moving and going in and out of service areas, but it happens when the phone is simply sitting on my desk and not moving at all. I usually use it to listen to Pandora while at work and have noticed that the songs cut in and out due to this sudden loss of a data connection.
I went from a Nexus One to the Nexus S and have never, not once, lost my full 3G bars in this same exact location. I personally believe its a software bug of some kind and have high hopes for it being fixed in the future. The N1 had similar issues when it first launched and Google / T-Mo were able to remedy that for the most part.
I am actually on my third Nexus S because the first two had some type of hardware issue; the first one's back button didn't work or light up and the second one had a blown ear speaker and would sound like a blown speaker in a car. As an early adopter, I expected this, so it didn't bother me in the least bit.
ALL of them did the same thing, so I know it is not just limited to my exact phone. This is definitely something with the Nexus S in general (or the current build of Gingerbread).
Can anyone shine some light on this situation? Thanks in advance and keep up the great work here guys!
---------------------------------------------------------------
UPDATE: Here are a few steps that I have taken in order to solve my sudden loss of data issue. I'm not guaranteeing this will work for you, but it has worked for me and a couple of users here on the forum.
Do the following:
Activate / Use the Sim Card that came with the phone (this is to ensure you are using the latest sim cards)
Make sure you have a 4G internet plan. (No t-zones, No web2go -- FULL internet only)
Call T-Mobile and have ask them to Reset your phone with their Towers
Here's a more technical explanation posted by Johoja:
1) Having network selection set to manual ( i.e selecting 302490 or TMOBILE) will result in No Service on a reboot. Solutions: - Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker) - OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal. Solutions: -Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery. -Use NoBars to accomplish thesamething ( taskergivesyou a bitmore flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-b...omdryer.nobars - Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane...kalti.airplane
3) WCDMA perferred does not work. - No solution
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40:
I read one users response on a different thread regarding something similar to the issue that I am having.
They said T-Mobile told them to get a newer sim card and that this may remedy the problem. In my case, this has been the only constant in the 3 phones that I have been through. I have had the same sim card for about 3 years or so now.
I will try activating the sim card that came in the box with T-Mo to see if this remedies the problem. Since I'm at work right now I will have to try when I get home later.
Does anyone think this will have any affect what-so-ever?
The galaxy s phones when first released, all variants, had issues of signal dropping from full to zero bars while sitting in one place. I remember because there were YouTube videos of it All over and it was shortly after the apple antenna issue.
Not sure if or how it was ever resolved. But it seems that Samsung may just have this type of radio baseband performance if we see all these individual units doing this. I don't know maybe others can respond.
I have the same issue as the OP. I travel to the same location weekly with NEXUS ONE, signal never drops in the T-MO Country here locally, and streaming CNET POD CAST never a hiccup, however, with the new NEXUS S, I would lose DATA Connection only, while the 3G will show full signal. I had to reboot the phone to get the DATA back.
is it the S issue or 2.3 issue?
food for though....
If you have T-zones or Web2go or Phones 1st web, you will have problems
I had the same problem too, now I fixed the problem. The thing was that had the wrong data plan on the NS, i had my old web plan from my hd2 which seems like different from the one for the NS. I restarted my phone after 5 mins off and now i have my internet working beautifly. A T-Mobile rep said that it was an error in the system that made the phone think that that was the right plan for the NS for a few. A glitch you may say, but all you have to do is put the right data plan that all, easy. Hope this helped and have a wonderful holidays everyone.
Sent from my Nexus S using XDA App
this is happening to me too, last night for a little while and today for about hte last 4 hours can't get connection back. i have full white bars, with 3g icon but can't access anything
So I activated the new sim card last night and I'm still having the same problem. Albeit it doesn't happen as frequent, but it still does it nonetheless.
I will call T-mo again to verify my plan. I am on a 1500 Minute Family Plan which includes unlimited data and messages. I will see if they need to tweak something and let you guys know if this remedies the problem.
Ok, it seems like the issue has been resolved after I spoke to T-Mobile earlier today.
The rep on the phone verified that the data plan I was on was in fact the correct one. He said he was going to reset the signal from the towers to my phone to see if this would resolve the issue. He asked me to turn my phone off for about 15 seconds after we hung up.
Since then, I haven't seen the problem arise again so my guess is that it somehow fixed whatever was going on.
I'll let you guys know if this changes and the problem occurs again.
Sent from my Nexus S using XDA App
peakaboohaha said:
I have the same issue as the OP. I travel to the same location weekly with NEXUS ONE, signal never drops in the T-MO Country here locally, and streaming CNET POD CAST never a hiccup, however, with the new NEXUS S, I would lose DATA Connection only, while the 3G will show full signal. I had to reboot the phone to get the DATA back.
is it the S issue or 2.3 issue?
food for though....
Click to expand...
Click to collapse
What's with the CAPS? ?
On topic: i have a captivate and I can confirm that all galaxy S phones had droppend data. An official ota update fixes it so maybe you guys need to wait for something official. Isn't there a new firmware for the nexus S already? Try flashing that and see if you still have issues.
Sent from my GT-I9000 using XDA App
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
@timur525 Yea, I'm already on 2.3.1.
I manually updated the first hour it came out hoping that it would solve the issue. The problem was still there after the update.
Sent from my Nexus S using XDA App
I have exactly the same issue as the OP. Extremely annoying to reboot the phone every time it happens. One thing I have noticed is that my phone doesn't know its number. If I go to settings, about phone, the number says unknown.
Sent from my Nexus S using XDA App
Memnoch30 said:
I have exactly the same issue as the OP. Extremely annoying to reboot the phone every time it happens. One thing I have noticed is that my phone doesn't know its number. If I go to settings, about phone, the number says unknown.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That shouldn't affect anything. My number shows up in status.
I had this issue resolved a few months ago as the push-to-talk app Tikl requires this in order to use it.
I was having the problem even with my number showing up. Call T-Mobile and have them reset you with the towers like they did for me and see if that helps you too.
Sent from my Nexus S using XDA App
I posted about this same issue on wrong section of the forum. Ive had this issue ever since samsung vibrant. I have applanet installed on my phone and some of the app that i installed accessed my apn and totally changed my apn setting to "Sirious application disabled.epc.tmobile" or something like that so i wyped everthing off from the phone and so far i havent had the issue ever since yesterday. Also i had the locale and language setting to korean so im thinking that might be causing it also.
Sent from my Nexus S using XDA App
adamr240 said:
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
Click to expand...
Click to collapse
That's what I remember too. I think its just an issue with the radio Samsung uses in all their phones. Might not be a way to fix it if even their new phones like the nexus s still have this issue. They prob would have tweakdd it by now if they could.
Same problem here. Xmas eve on shift and I have a phone that had no connection whatsoever (not even phone capabilities) this may be the one thing that takes the phone back. (If it happens again)
robstunner said:
Same problem here. Xmas eve on shift and I have a phone that had no connection whatsoever (not even phone capabilities) this may be the one thing that takes the phone back. (If it happens again)
Click to expand...
Click to collapse
Have you called T-Mobile to see if they can give you a reset to the towers?
I had this done yesterday afternoon and haven't had the problem again since.
Also, if you'really using an old sim, I would suggest activating the one the phone came with just to be on the safe side.
If that doesn't help you then I would at least wait until just before your return period ends to see if there will be an update to address the issue.
Sent from my Nexus S using XDA App
Never had this problem with the captivates I've had.
adamr240 said:
Doesn't every android phone from samsung have this problem?
I know the Moment has that problem, after 3 updates samsung called it quits, I still have to reboot mine 2 to 3 times a day for data lockups.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk
Epiksol said:
Have you called T-Mobile to see if they can give you a reset to the towers?
I had this done yesterday afternoon and haven't had the problem again since.
Also, if you'really using an old sim, I would suggest activating the one the phone came with just to be on the safe side.
If that doesn't help you then I would at least wait until just before your return period ends to see if there will be an update to address the issue.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ill give them a call on Sunday
Sent from my Nexus S using Tapatalk
Hey guys,
Just want to see if anyone else has noticed an issue that has happened to me a couple times. My n4 "loses" its network connection for both received calls and sms.
Status bars indicate a good signal (no hollow triangle) and data works fine during these events. I first noticed when my neighbor came by telling me he sent me a couple messages which I never received although I had been playing with the phone all day.
After rebooting I received many sms and voicemail message indications.
The scary part is there is no way to know when it's happening. There is no indication of lost signal and data service continues to works fine - all calls just go straight to VM and no SMS or VM notifications are delivered.
Any ideas? should I return/exchange it? Thanks for any help.
here's me:
network is Tmo (happened in 2 different cities)
network status bars indicate good signal
data service continues to work ok (3g/4g)
stock, not rooted, phone is only 3 weeks old
still on 4.2.1
I've had this happen to me once don't know why though.
Sent from my Nexus 4 using xda premium
jltyler said:
I've had this happen to me once don't know why though.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
At first I suspected the light flow app because this happened right after installing the app. I thought maybe the app was messing with the notifications so I uninstalled it - but then problem happened again. Also, many people are using the app with no issues so i suspect my phones radio is at fault.
I think I'll RMA it. Thanks!
Crap, i just left Sprint after 11 years of service with them for the exact same reason. Started mid December and by mid Jan and several Network Trouble tickets they had no clue how to fix it and blamed it on network congestion. End of Jan i officially ported to TMO.. Hope this doesnt happen to me again..
I started a thread with similar problems, but I also loose data connection. I get a message on the notification bar about it.
In my case it only happens if I turn wifi on and leave HSPA running, so I have to switch to 2g only for the problem to disappear.
Called Tmobile and they have no clue what is causing the problem.
Sent from my Nexus 4 using Tapatalk 2
IAmSixNine said:
Crap, i just left Sprint after 11 years of service with them for the exact same reason. Started mid December and by mid Jan and several Network Trouble tickets they had no clue how to fix it and blamed it on network congestion. End of Jan i officially ported to TMO.. Hope this doesnt happen to me again..
Click to expand...
Click to collapse
I wouldn't worry too much about it. I've used tmo for years and never had this problem before - only with the nexus 4 the last couple weeks. If this type of issue was more wide spread I think there would be more people complaining about missed calls/txt.
It sure makes me paranoid though. I am now calling my phone a couple times per day (from my work phone) and sending myself SMS messages just to be sure my phone is working.
I just updated to 4.2.2 so maybe that will help. If it happens again I'll exchange it.
SloMotion said:
I get a message on the notification bar about it.
Click to expand...
Click to collapse
What type of notification do you get? In my case there is no notificaion, the only way to tell if its happening is to place a test call or sms from another phone.
I do notice it occurs after heavy HSPA use but I havent been able to duplicate the problem. It's almost as if after heavy use of an HSPA channel the MSC location update is purged - so all calls go straight to voice mail and sms messages are queded in the SMSC (just a guess). Then after flight mode toggle or reboot location update occurs and all is good.
It happened again yesterday so I've gone ahead an ordered a replacement.
I get a triangle notice in the notification bar. And I narrow my problem with my location.
Did you ordered a new phone?
Sent from my Nexus 4 using Tapatalk 2
Which baseband are you on?
I was on the latest 4.2.2 update with the old .33 baseband and I couldn't make or receive calls. To be more specific, my phone was mute as the call was going through. I could not hear the ringing tone. So I flashed the new .48 baseband and it worked.
Well, what I experience sometimes is:
When I leave a WiFi connection, the phone (sometimes) wouldn't reconnect to mobile data (I can only receive calls atm). In order to reconnect it, I have to toggle airplane mode.
Kinda the opposite, but maybe the same solution can be proposed?
My temp solution is to switch to 2g only and turn on wifi. That seems to do the trick
As for baseband I'm rooted with stock rom 4.2.2 and CMW recovery
Sent from my Nexus 4 using Tapatalk 2
---------- Post added at 12:38 AM ---------- Previous post was at 12:24 AM ----------
Ok I got off the phone with customers support and they're aware of the problems.
They're replacing the phone. So I guess I got to return the phone to stock
Sent from my Nexus 4 using Tapatalk 2
I have the exact same issue....
This is really annoying cause you don't know when people sends you message
It first happened to me with 4.2.2 and. 48 radio
Sent from my Nexus 4 using Tapatalk 2
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 was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
BGray210 said:
I was running tx_dbs_tx Hybrid X 3.0 up until this morning when my phone suddenly kept popping up the Data Roaming Guard. Whenever I would attempt to make a call, it would alert me to a Verizon error to reboot my phone -I am on Sprint. I flashed with Odin the stock OK1 software, and besides having Knox and ItsOn back on my phone and battery life being horrible once again, I am still receiving the Data Roaming Guard splash screen and still receiving the Verizon error when making calls. I was able to make a single call after using the Activate Device self-service, but it didn't even last 20 minutes.
Again, back on stock OK1 ROM from Sammobile, re-rooted with Freeza's OK1 stock kernel, SuperSU Beta 2.52, any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
ianmb said:
Do you live in a 4G Sprint area? If not this EXACT same thing happened to me and my wife right before they started 4G in our area. Even service calls went to Verizon first. Evidently even the Sprint reps had no idea that 4G was getting turned on in my area, they had me do all the #* dialer codes and both our phones said we were in roaming for like a day or two.
Click to expand...
Click to collapse
Yes, San Antonio was one of the first markets with Sprint to have 4G WiMax and then 4G LTE. It had been running just fine for months, but suddenly stopped working. Even after flashing stock back on without root or any added apps besides Sprint's auto-downloads, it still had the problem. Took it to the store yesterday and baffled them all for 2 hours before they ordered me a replacement. They even tried a new sim card because I told them that I've had problems intermittently in the past with the Roaming Guard popping up and forums stated it could be a bad sim card. The Sprint # codes wouldn't even work. Anyways, they ordered me a replacement- won't have it until Tuesday but thanks for the response. I had never heard of anything like this happening before and it struck me as odd. I even checked the settings for the network and they all checked out fine, Sprint store reps did the same and were just as perplexed as I was.
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Txdaredvl said:
Mine was doing almost the same. Seemed like it had to go to verizon when it would go between towers. Then back to sprint. So I did the ##72786# that is suppose to launch the hands free activation. Although it didnt launch it(due to custom rom), it did run the provisioning stuff and fixed mine. Hasn't went to roaming yet.
No promise it will work. But hopfully it will fix yours. Assuming you are on a note 4.
Click to expand...
Click to collapse
Yes, I am on Sprint Note 4, but the pound codes wouldn't even work. As soon as I put in the last # sign it just cleared out the dialer. I found a complete list of # codes on sammobile or samfirmware site, can't remember which, and even Sprint attempted them. I had flashed back to stock available on Sammobile prior to going to Sprint, but it still didn't work. You don't think different flashes or ROMs or kernels could have caused this do you?
Anyways, I have the insurance through Sprint and have a new one on the way Tuesday. I just hate not being able to figure out a software related problem. I was also trying to find a way to do it manually while rooted, but couldn't find the right edits because I cannot even remember how to get into the correct settings at the moment-mind cluttered with too many projects.
I appreciate all of the responses though and really enjoy learning about my device on xda and hope to either create my own apps or even cook a ROM in the near future.
A few days ago, my girlfriend renewed her contract with Globe Telecom in the Philippines and she got this Samsung Galaxy S7 Edge as her retention. She gave it to me because she was not a fan. Anyway, the phone was simlocked to that network but since we are based in Singapore, we had no choice but to have it unlocked. Now that i have put in both my Singapore sims, I realised that i have totally no mobile data. I can text and call fine but i can't browse the web. Upon further research, I found out that it might be the APN; but when i did try to access it, it was all greyed out.
Is there a way to fix this? I rooted the phone hoping that would fix it. Will flashing a stock ROM work? I seriously don't want this phone to go to waste. Thanks in advance to anyone who would help me. Also, everytime I boot the phone, a little animation from Globe Telecom plays before reaching the home screen. Not really a big thing, but it would be great if you helped get rid of it. :cyclops::cyclops::cyclops:
edit: in another unfortunate turn of events, I learned today that my device seems to have lost root. I rooted it a few days ago but when I check with root checker today, it says it's not rooted. tried to reroot but no luck.
Hupao03 said:
A few days ago, my girlfriend renewed her contract with Globe Telecom in the Philippines and she got this Samsung Galaxy S7 Edge as her retention. She gave it to me because she was not a fan. Anyway, the phone was simlocked to that network but since we are based in Singapore, we had no choice but to have it unlocked. Now that i have put in both my Singapore sims, I realised that i have totally no mobile data. I can text and call fine but i can't browse the web. Upon further research, I found out that it might be the APN; but when i did try to access it, it was all greyed out.
Is there a way to fix this? I rooted the phone hoping that would fix it. Will flashing a stock ROM work? I seriously don't want this phone to go to waste. Thanks in advance to anyone who would help me. Also, everytime I boot the phone, a little animation from Globe Telecom plays before reaching the home screen. Not really a big thing, but it would be great if you helped get rid of it. :cyclops::cyclops::cyclops:
Click to expand...
Click to collapse
Alright... I think that you may have a problem. I dont see a whole lot of options as they have been locking out the APN's as of late. I'm going to spend some time today seeing if I can't find an unrooted solution to your problem (If we had root GTools would do the trick). I have been messing around with it a bit and may have some options for you but Ill get back with you if one pans out.
Edit: So, are you rooted?
Sent from my SM-G935P using Tapatalk
Yes,i rooted the phone yesterday.
samatagana said:
Alright... I think that you may have a problem. I dont see a whole lot of options as they have been locking out the APN's as of late. I'm going to spend some time today seeing if I can't find an unrooted solution to your problem (If we had root GTools would do the trick). I have been messing around with it a bit and may have some options for you but Ill get back with you if one pans out.
Edit: So, are you rooted?
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
Will rooting it to another ROM fix it? what do you think?