S4 temporary freezing problem (not lag) - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

My S4 works great. Finally convinced my iPhone buddy to get a Galaxy. Problem is his S4 (att 16gb,stock rom) freezes often. The phone becomes totally unresponsive for ten seconds to a few mins. It's normally on the lock screen, but does it on others too.
The screen image is frozen, I can see the traffic signal on the top bar stuck, instead of moving from 1-2-3 dashes like normal.
Any it won't acknowledge any touch.
Please help with any tips or links. Thanks guys.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Not a normal problem... Try reset.. If that doesn't work.. Try exchanging. Might be bad components like ram, cpu, gpu etc..lag has been an issue for some but freezing had not..
Sent from my SAMSUNG-SGH-I337 using xda premium

yeah, i would def exchange it "now"

Related

New YouTube App causing G2 to crash

Is anyone else having issues with the new YouTube app that was recently released?
Every time I press "back' during a video playback the phone freezes & crashes on me - is this happening to any of you??
yup. Happens to me each and everytime. I can only remedy it with a damn battery pull
Same happens to me, I had to force a reboot though ADB (It didn't fix anything when I uninstalled Youtube from ADB effectively killing its process).
It crashed once while watching a video and I pressed the back button. However, I've tried to recreate the issue and I can't get it to crash at all now.
Nope, working perfectly fine here.
It locks up on me when pushing the "back" button, too. Battery pull required. Boo.
Looks like I'm not the only one having this issue.... I hope they update it soon, the new apps pretty sick!
Sent from my T-Mobile G2 using XDA App
The same thing happened to me today. Had to pull out the battery to restart.
Sent from my DETHFONE (G2)
Same here on both of our g2's. One rooted and on normal. When hitting back it locked the phone up tights. Have to pull battery to restart.
sheek360 said:
yup. Happens to me each and everytime. I can only remedy it with a damn battery pull
Click to expand...
Click to collapse
Same here
Sent from my T-Mobile G2 using XDA App
Works fine here
Yeah push the back button then it gets all messed up... what an update.. I'm sure it'll be fix but not right away.. plus its really just the UI, just uninstall until its fix
Meaning about the UI isn't that the only real update?? Everything else seems the same..EXCEPT for the video playing on the spot once instend of extending the info
Sent from my T-Mobile G2 using Tapatalk
Yeah, it's good to see it's not just me. It's happened at least half a dozen times in the past couple days to me. Personally, I loathe battery pulls so I just sit and click back and home a few hundred times to get a fc option.
Sent from a Macbook Wheel
Happens to me too... Though not every time. But most of the time.
Sent from my T-Mobile G2 using XDA App
Yea this is VERY annoying. Sucks too because I really like the new UI.
Sent from my T-Mobile G2 using XDA App
yes same here because the rent is to damn high
It freezes on me as well
Hmm.. seems like I'm one of the few for whom the new Youtube is working perfectly.
It does the same thing for me - near frozen when I hit the back button on a video. The first time I did this I had the patience to eventually go through a power-off sequence (15-30 seconds between hitting buttons and getting a response). The second time I just did the 3 finger salute to reboot it.
Note that you don't have to pull the battery. Power-VolumeDown-Trackball is an instant reboot sequence (though it did take 5 to 10 seconds to perform it when Youtube was acting up).
Just a question here... most of you with issues do you have 1st batch/pre-release G2's? I only ask because I had a pre-release G2, and I had a crap load of issues with it. I sent that one back for an exchange to Tmobile, and got my new one yesterday. I have zero issues at all. New YouTube works great, I have full signal now, and, well the phone works the way its meant to work.

Slowdown

Hi guys, anybody here experiencing slowdowns on their Note? Currently experiencing slowdowns in various UI areas:
Keyboard visible delay when pressing a key especially if haptic feedback is enabled.
Slide to unlock in the lockscreen has visible response issues. I needed to do it slowly to have a successful unlock. Else I would need to slide 2-3 times.
Opening the app drawer has visible lag. Take a few milliseconds before it starts to open.
Some of my apps and games display a black screen when opening. Like it is loading instead of instantaneously opening it like the first time I got my Note. Doodling with the S-pen for a few minutes slows down the entire phone.
---------------
My Note is on Stock firmware with ChainFire's cf-root kernel. Any advice on what I should do?
Keith
Samsung Galaxy Note
XDA Premium
Same here with Stock KKJ
Sent from my GT-N7000 using XDA App
Same here too
Sent from my GT-N7000 using xda premium
So is it only us three? What are we doing wrong?
Sent from my GT-N7000 using XDA App
I got the same problem, though it seldom happens.. especially when in S Memo..
Sent from my GT-N7000 using xda premium
Every Note will be a little laggy, those that say they don't have any must have come from a lower end android device or from one which had similar lag, I have mentioned this in another thread, if you have come from a high end one, like the galaxy s2 like me for instance, you will notice the lag. It will be sorted in a couple of future firmware updates, don't worry
I notice a big slow down when the battery is less than 10%. Nothing works.
Flash KKA firmware (if you prefer to stay stock) or some Custom ROM based on KKA, overclock it a little, freeze or uninstall some crapware and it'll get better. I wouldn't expect it go get buttery smooth though. The sheer amount of pixels the Note has to move around will have it's effect. We'll have to wait till they start using GPU accleleration on OS UI level (ICS). I managed to get mine to the point where lag is noticeable when I'm looking for it but not annoying anymore. And I'm fussy.
@sharp - well, I would expect that below 10% goes into power saving mode and the CPU gets seriously downclocked. It happens for a reason. They may be some way around it but my guess is that it's a very short way. Like 5 minutes and the phone is dead or something.

4.1.2 broke swiping?...

Is anyone else having problems with swiping left and right etc since 4.1.2?
My device recognises the swipe but doesn't complete ie when ctolling through home screens the page won't move to the next page it will stay where it is and you just see the page move a little bit and then go back.
Hope that makes sense.
Please reply if you're having this problem or not
Sent from my Nexus 7 using xda app-developers app
I've noticed this as well since 4.1.2 but it only happens for the first few seconds after switching the screen on. I've had to apply a bit more force in swiping to bring down the Notifications or to go from screen to screen on Home and the app drawer. Gently flicking the screen doesn't work and stuff like Notifications just flips back up, but after 20-30? seconds it works fine again.
I've noticed this aswell, but don't think the new update is the cause as I was experiencing it before.
Just out of curiosity do you use another device such as HOX? Because I have a HOX, and the swiping is much smoother on that, flicking goes from screen to screen rather than a drag which the Nexus required, if you do use another device perhaps its just the change in device like my case ?
Hmmm.
Cant decide whether or not to take it back and try a replacement.
As said above i have to now use a full swipe across the screen with my finger while holding the tablet in the other hand. I cant just use one hand and flick it with my thumb like i used to be able to.
Ive done a factory reset but that hasnt helped at all.
Ill upload a video of the problem soon so you guys can compare it to yours.
OK heres a video of the problem...
Let me know if you guys have the same
Bump
Sent from my Nexus 7 using xda app-developers app
I've noticed that my home screen is not as responsive, though I can't tell in your video if it's as severe. I have to make a strong swipe to move to the next page or it will just bounce back to the current page I'm on. So sometimes it takes me a couple times to switch screens since I'm used to it normally changing. Hope that makes sense.
I run CNA 3.8.0 which uses 4.1.2; I haven't noticed that problem previously on 4.1.1
I also have to swipe the notification bar further in order for it to stick. I used to only have to go 1/3 to less than 1/2 of the screen for it to work.
I have the same issue
Rom is pa 2.23 kernel isn't changed
Sent from my Nexus 7 using XDA Premium HD app
I have %100 same issue. Just like in your video.
I hope google will solve this with 4.2
Same issue, would agree that it is worse for the first 20-30 seconds after waking up the screen. Really is quite a pain.
This definitely happens for me, and it definitely started with the 4.1.2 update. It's not a big deal to me, but I can't believe Google didn't catch it.
Sent from my Galaxy Nexus using xda premium
I hope google solve this with 4.2. Because it's very annoying .!!
Glad its not just my device thats broke.
Lets hope 4.2 sorts it out.
How did google not notice this when they were doing tests...
Only place I notice this is home page and app drawer. New with 4.1.2, and quite irritating. I blame the Apple rubber band patent!
Sent from my Nexus 7 using xda app-developers app
I've got a new c9O 32GB and mine does the same thing. Its better if I use one hand to hold it from the edges while using the other hand to touch. Using one hand to hold and swipe/scroll/ anything is an effort in futility. And its not just at the Home screen/App menu for me. It also locks up completely from time to time. Do we know what kind of memory the 32GB model uses? Not happy about this at all. Asus really screwed up on this one.
Sent from my DROID BIONIC using XDA Premium HD app
I have this issue as well. My first nexus which was a 16gb didnt have this problem but my current one which is a 32gb does this, especially with the notification bar which is quite annoying. Not sure if its because of 4.1.2 or if its the hardware itself because it updated immediately when i got it so didnt have a chance to use the 32gb before it updated.
has anybody tried the 4.2 update to see if it has fixed this?
Bump . I'm waiting for mine to come in the mail from Asus.
Sent from my SPH-L710 using Tapatalk 2
I think the problem is gone in 4.2.
At least I have not seen it yet - swipe across half the screen works again to change page.
I still get it in 4.2 :crying:

Galaxy S4 Dialer slow

Hi,
Any help most appreciated as I am struggling to solve this bizarre issue. Both my wife and I picked up Galaxy S4s in the last 30 days. Over time as you use the phone the dialer seems to slow down considerably. When you click the green phone icon to call a contact it will take upwards of 10-15 seconds to get to the caller screen and actually place the call. It's so slow that you would think the call was not even happening sometimes!
Now. The weird thing is that at first I thought it was a handset thing, but exactly the same thing happens on my wifes phone now! (I re installed and fixed mine twice now)
The dirty solution is to backup, factory reset and restore everything (logs, contacts etc.). This works fine, so I know that the issue it is not the size of the call logs, number of contacts etc.
I honestly don't think we are running any strange apps, pretty mainstream stuff.... Otherwise phone is awesome. Have scoured the net but not found specific threads on this issue with the S4.
I have tried disabling all syncing to extendable address books ( face book. Linkedin , etc)
Thanks in advance for your thoughts and or comments.
Jamie
Sent from my SGH-I337M using xda premium
Unfortunately the S4 will clean the phone and contacts app from background and foreground (cache) ram when the system needs extra ram for another app like facebook or netflix.
When this happens the phone and contacts apps need to be reloaded from scratch.... which takes a little longer than if they were not removed from memory in the first place.
These first versions of the samsung s4 software needs some polish to reduce its ram demands. It is a bit bloated at the moment.
Imo... it will significantly improve next few updates.
Sent from my GT-I9500
I agree its early days with the s4 and im having problems with the qwerty keyboard and the predictive text not keeping up and the purple haze issue on the settings screen, its just a case of waiting for the updates to arrive ive heard its been released in germany and Malaysia.
Sent from my GT-I9505 using xda app-developers app
Do I need to report this type of thing to Samsung direct? Or just patiently await the updates?
Sent from my SGH-I337M using xda premium
So this is supposed to be normal? How come more people are not complaining about it.? It is ridiculously slow, after pressing the send button you shouldn't have to wait a few seconds to even see the dialer let alone wait for it to initiate a call. I would like to know how many people are experiencing the same thing. I've owned a galaxy nexus, galaxy s3, Samsung focus, galaxy s4 and galaxy note 2 amongst numerous other non Samsung phones and it's really annoying. I own a ROGERS s4, wonder if it's a specific model issue.
This is ridiculus! This issue has progressively gotten worse over time, and it has come to the point where it takes about 20 seconds from the time I press the phone number until it actually makes the call. Phone is unresponsive in the meantime. Shame on Samsung...
It's completely normal with sangsuga phones ....I've got Samsung from gs1 nexus, note and now s4 and s4 active. .... my opinion is....I just don't care. If you clean dalvik cache it will work better you need to do this sometimes unfortunately
But hey guess what.....Samsung knows that and finally and maybe they will give us a fresh ui based in ART
Enviado do meu GT-I9505 através de Tapatalk
Is there any mod/hack to put the damn dialer in Memory so that it don't delay when phone icon pressed ? I searched on Google and all galaxy phone from first to the recent have all this stupid lag/delay and It is crazy that the main core function of a so powerful phone is till not fixed after so many years :S

Verizon LG G2 over sensitive touch

Anyone else having the issue where the touch screen is overly sensitive making typing or swyoing nearly impossible? Makes it hard to control movement of pages via browser.
Sent from my VS980 4G using xda app-developers app
ready5 said:
Anyone else having the issue where the touch screen is overly sensitive making typing or swyoing nearly impossible? Makes it hard to control movement of pages via browser.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
I have noticed that my AT&T G2 is a bit too sensitive to my touches as well. It's not a big deal but it's a little bit annoying sometimes.
Maybe don't drink so much coffee?
Haven't had this issue...
Sent from my Nexus 7 using Tapatalk 2
Starting to think I should report this as defective because I went to test store model...not nearly as bad
Sent from my VS980 4G using xda app-developers app
Same issue with Verizon model for me. Not that common but very annoying when I do notice it.
I fixed it by wiping the screen with a micro fiber cloth and doing a full factory reset. I don't know which one fixed it. It works perfectly now. Using an AT&T G2.
I've been looking for a way to fix the over-sensitivity on the vzw device. The screen will seem to scroll extremely fast out of nowhere.
I thought it was just me. When I'm texting sometimes it will put two or three of the same letter in a row from just one touch. VZW model
Occasionally experiencing something of this nature on my VZW phone as well. Not frequent, though.
Having this same issue right now. I feel like it started happening after last week's software update (verizon).
Sent from my LG G2 using Tapatalk 4.
I had the same issue when scrolling thru the screens using Zedge to look for notifications and ringtones. It was a big pain in the butt.
has anyone figured this out? I literally can't use a browser because when I try to scroll, it just zooms in. so annoying
On the phone with a vzw rep at technical support now... She said that they don't have any reports of that on a mass scale. I told her that it doesn't happen all the time and she said that it was probably a fluke... Whatever! Obviously this isn't just a problem on my phone..
It doesn't happen mass scale because most people won't address or report the issue. Just bad on verizon for not testing
sensitive touch
I have the very same issue with the touch sensitivity, obviously since i have found this thread. I find that by turning the screen of then back on it tends to reset it. I just wish i didn't have to do it so often. I would rather not factory reset my phone being how it was already a pain to make the transfer of data in the first place. Plus in theory, the reset shouldn't work being that it came of the production line this way. No amount of resets will change the outcome of the hardware that was installed, until production fixes it for the next line. But if others have found solid longer lasting methods, minus tge reset, I'm willing to test them til i simply get tired of itand replace it.
I am on Verizon and get it occasionally. I just turn the screen off and back on, and that has corrected it every time so far. Not too annoying yet, but if it gets worse I'll try getting it switched out.
I'm guessing this is a software issue, but it only happens to me while web browsing
romeyjdogg said:
I'm guessing this is a software issue, but it only happens to me while web browsing
Click to expand...
Click to collapse
It only happens to me on xda forums lol
Quite honestly this whole phone seems to lag and have some sort of bugs here and there, very disappointed so far. The Note 2 is calling me.
Sent from my LG-D801 using Tapatalk 4
romeyjdogg said:
I'm guessing this is a software issue, but it only happens to me while web browsing
Click to expand...
Click to collapse
When mine does it it happens on any Web page and I tried on both chrome and Firefox and it still happened.

Categories

Resources