Related
Every time I open a app that need portrait view, I get stuck in portrait mode until I restart the phone. Please help or is their anyone else out there with this same problem? Or wait for another PTA update.
jalyn02 said:
Every time I open a app that need portrait view, I get stuck in portrait mode until I restart the phone. Please help or is their anyone else out there with this same problem? Or wait for another PTA update.
Click to expand...
Click to collapse
I am finding the same issue. It seems to happen for me if I have been using Google Sky Map or Street View in Google Maps.
After using either the Auto Rotate stops working and I have to re-start the phone
Listed as a known issue in the sticky, guys.
The accelerometer becomes locked after using Google Sky Map. Its a bug either on GB or Sky Map/Street View apps themselves.
Sent from my Nexus S using XDA App
It happened to me using 20 different apps.
Sent from my Nexus S using XDA App
jalyn02 said:
It happened to me using 20 different apps.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Then you might have a bad accelerator, mate
Sent from my Nexus S using XDA App
Google should fix this soon because this sucks plus, I don't want to hack the phone for a fix.
Sent from my Nexus S using XDA App
I think that it's gingerbread a software issue not a hardware issue.
Sent from my Nexus S using XDA App
jalyn02 said:
I think that it's gingerbread a software issue not a hardware issue.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I doubt it because I haven't had any issues like this in any other app besides skymap. Mind listing some of the apps you've noticed this in? I'll see if I can duplicate.
Sent from my Nexus S using XDA App
Well it's not that bad but, it's bad. especially when I purchase unlocked for hundreds of dollars and I had highly expected a great experience from gingerbread as a Google os. It happened in XP moto and maps and GPS but not all the time and the only fix is to restart the phone so it's a software problem. I also have a Samsung vibrant and never had this issue with it but they are similar hardware specs...
Sent from my Nexus S using XDA App
jalyn02 said:
Well it's not that bad but, it's bad. especially when I purchase unlocked for hundreds of dollars and I had highly expected a great experience from gingerbread as a Google os. It happened in XP moto and maps and GPS but not all the time and the only fix is to restart the phone so it's a software problem. I also have a Samsung vibrant and never had this issue with it but they are similar hardware specs...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Similar hardware specs, yeah, but that doesn't rule out the fact that you might have picked up a phone with a bad piece of hardware. It could have been damaged in assembly, or shipment, or by an act of God.
I've only been able to duplicate this issue thus far in Sky Map. I just tried Street View on my phone and had no problems, and I'm not sure what those other apps you mentioned might be.
More information please.
Well if me and you and dozens of others who own this device are having somewhat the same issues it should not matter rather if it's the hardware that's at fault or software that's at fault but, indeed I would like to hope it's a software issue because it can be simply fixed with a ota update other then shipping back to bestbuy. This is a growing issue and it's only going to get bigger every day. Odd but Google+gingerbread=Epic Fail?
Sent from my Nexus S using XDA App
since I've had my nexus s I have noticed that It keeps wanting to shutdown during phone calls. Anyone else seeing this?
Sent from my Nexus S using XDA App
yellathcir said:
In the since I've had my nexus s I have noticed that It keeps wanting to shutdown during phone calls. Anyone else seeing this?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
and buy shut down you mean physically power off? or the screen turn off?
Cuz if its just the screen that is normal, its the proximity sensor
Power down
Sent from my Nexus S using XDA App
Its weird, I haven't had this problem on any other android phone, its happened twice in the last 24 hours. I'm completely stock. Unrooted
Sent from my Nexus S using XDA App
I can count on one hand the number of phone calls I've been on since I got the thing, but I haven't had it shut down on me any of those times.
I've had it happen every time when rooted and had apps. I went back to no apps and still had it happen. I went back to stock 2.3.1 via the nandroid around here and locked it back up, still doing it.
The only thing I didn't test was 2.3 vs 2.3.1 but I do believe it started happening to me, at least, when going to 2.3.1, now that I think about it.
I have this problem but rarely. It will reboot the phone show the nexus startup screen without the backlit LED. Is that whats happening to you?
Sent from my Nexus S using XDA App
Same here, and I have used every T-Mobile Android phone to date, never seen anything like this before! This is the only phone I haven't rooted yet, not sure what the issue is...
It only happened once so I didn't think anything of it.
I didn't know it was a common problem.
Btw I will be exchanging my phone cuz this one has done really annoying bugs, like freezing in between homescreen slides and apps constantly fc during use
Sent from my Nexus S using XDA App
ya i havent made very many calls, but thats why it kind of concerns me. i have probablly made 10 calls and i think its rebooted 3-4 times while on the call or at the end of the call. i wonder if its a bug with the phone app?
did you root the phone or something ? if its still on stock firmware like how you bought it, then try to restore factory sittings, if its still doing that you then you have a I/O chip problem. and you will need to replace your phone.
thats what the HTC care told me when my HD2 used to have this issue
ll_l_x_l_ll said:
did you root the phone or something ? if its still on stock firmware like how you bought it, then try to restore factory sittings, if its still doing that you then you have a I/O chip problem. and you will need to replace your phone.
thats what the HTC care told me when my HD2 used to have this issue
Click to expand...
Click to collapse
I would believe it was hardware if it happened randomly, but for phone calls only, that sounds like software.
Sent from my Nexus S
Happened to me just now. Stock 2.3.1 with an international call.
I'm not rooted, I just cleared data for the dialer app and cleared cache on the whole system, we'll see if that does anything. Good thing I rarely use my phone for making calls or I'd be pissed
Sent from my Nexus S using XDA App
So I've getting the no sound+drop signal problem these last weeks where you don't hear anything when making a call and then the phone loses all signal. Looked everywhere online no solution. I really need my phone these days and i am having to use skype to make a call which is total crap. Then today all of the sudden the phone stops recognizing the sdcard out of the blue, also can't seem to find any solution online. I don't want to send the thing to repair because I use it a ton. This is really inconvenient.
Just venting here , sigh.....
This isn't your blog, go back to facebook or wherever you came from.
Choristav said:
This isn't your blog, go back to facebook or wherever you came from.
Click to expand...
Click to collapse
This is the general forum, you know, GENERAL.
ManuC84 said:
So I've getting the no sound+drop signal problem these last weeks where you don't hear anything when making a call and then the phone loses all signal. Looked everywhere online no solution. I really need my phone these days and i am having to use skype to make a call which is total crap. Then today all of the sudden the phone stops recognizing the sdcard out of the blue, also can't seem to find any solution online. I don't want to send the thing to repair because I use it a ton. This is really inconvenient.
Just venting here , sigh.....
Click to expand...
Click to collapse
I had this issue with my old LG Optimus T P509 T-Mobile.. it was unlocked so I was using it on AT&T.. I never figured out what the problem was but I'm glad to know I wasn't the only one. Haven't had this issue with my S3 yet. Running stock 4.1.2 JB with ADW Launcher.. what service provider are you currently using?
Sent from my GT-I9300 using xda app-developers app
Have you tried a factory reset? or a different ROM?
Even before that, wiping cache's?
If you're looking for help, more detail needed. If your venting, I agree with Choristav. No offense intended.
dusty1268 said:
I had this issue with my old LG Optimus T P509 T-Mobile.. it was unlocked so I was using it on AT&T.. I never figured out what the problem was but I'm glad to know I wasn't the only one. Haven't had this issue with my S3 yet. Running stock 4.1.2 JB with ADW Launcher.. what service provider are you currently using?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Which problem you mean, the call issue or the micro sdcard issue? I am running stock 4.1.2 jb and i have orange. The worst is that these problems start on their own all of the sudden with no previous warning. It drives one insane because it's so hard to pinpoint what happened and how to fix it.
ManuC84 said:
Which problem you mean, the call issue or the micro sdcard issue? I am running stock 4.1.2 jb and i have orange. The worst is that these problems start on their own all of the sudden with no previous warning. It drives one insane because it's so hard to pinpoint what happened and how to fix it.
Click to expand...
Click to collapse
Sorry.. The calling issue. I would make a call and it wouldn't make a dial or ringing tone and there was no sound coming from the speaker. This isn't happening on my S3. It was was happening on my old LG phone.. it was running stock 2.3 gingerbread of course, but it was surely mind boggling.
Sent from my GT-I9300 using xda app-developers app
ceasee said:
Have you tried a factory reset? or a different ROM?
Even before that, wiping cache's?
If you're looking for help, more detail needed. If your venting, I agree with Choristav. No offense intended.
Click to expand...
Click to collapse
I am sorry but I read the rules and didn't see anything that said that no venting was allowed here, this is a general forum and in most forums general means general chat, venting included, or anything else that doesn't fit in more specific boards. Now regarding your question I didn't do wiping nor factory reset but I did reinstall the Jelly bean ROM I am using, and also I tried reinstalling the modem making sure it was the right one. I didn't do more because I've read in the big "no sound during calls" thread that those methods haven't solved most users' issues so far so seems like a waste of time. Anyway spending my time fixing the phone is my idea of a good time. I've had it for one year btw.
dusty1268 said:
Sorry.. The calling issue. I would make a call and it wouldn't make a dial or ringing tone and there was no sound coming from the speaker. This isn't happening on my S3. It was was happening on my old LG phone.. it was running stock 2.3 gingerbread of course, but it was surely mind boggling.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I have that happen and then suddenly signal drops to nothing and I get a circle with a crossed line symbol for a few seconds until it comes back. It's weird as hell and there's no solution anywhere online. I fixed it for a while tapping the back of the phone but now that ain't working anymore. Very frustrating.
ManuC84 said:
I have that happen and then suddenly signal drops to nothing and I get a circle with a crossed line symbol for a few seconds until it comes back. It's weird as hell and there's no solution anywhere online. I fixed it for a while tapping the back of the phone but now that ain't working anymore. Very frustrating.
Click to expand...
Click to collapse
Could your case, assuming you have one, possibly be the culprit? I had the same exact issue but on a stock rom, which is odd, but possible I guess lol.
Sent from my GT-I9300 using xda app-developers app
dusty1268 said:
Could your case, assuming you have one, possibly be the culprit? I had the same exact issue but on a stock rom, which is odd, but possible I guess lol.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I actually have a stock JB rom, which was working great for a few months before this started. I had the original ICS restore data in the micro sdcard, the one that stopped working today Btw you mean the phone's case? Why would that cause any problems?
ManuC84 said:
I actually have a stock JB rom, which was working great for a few months before this started. I had the original ICS restore data in the micro sdcard, the one that stopped working today Btw you mean the phone's case? Why would that cause any problems?
Click to expand...
Click to collapse
I have heard of signal problems due to cases but not too common.. just using process of elimination. Also, that's a pain you lost your SD Card.. maybe try banking up your stuff on your phone and doing a clean wipe? Factory reset?
Sent from my GT-I9300 using xda app-developers app
dusty1268 said:
I have heard of signal problems due to cases but not too common.. just using process of elimination. Also, that's a pain you lost your SD Card.. maybe try banking up your stuff on your phone and doing a clean wipe? Factory reset?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I have the original case so I doubt it. And yeah I am gonna have to go do a factory reset I guess, a pain in the ass. Thanks for the suggestions anyway. :good:
ManuC84 said:
I have the original case so I doubt it. And yeah I am gonna have to go do a factory reset I guess, a pain in the ass. Thanks for the suggestions anyway. :good:
Click to expand...
Click to collapse
No problem. Post back with results if you get it working right again. :thumbup:
Sent from my GT-I9300 using xda app-developers app
dusty1268 said:
Could your case, assuming you have one, possibly be the culprit? I had the same exact issue but on a stock rom, which is odd, but possible I guess lol.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
cant be, im using a thick as hell otterbox commuter case and im getting full bars plus LTE support. my carriers koodo btw.
Sent from my SGH-I747M running Liquidsmooth JB 4.2.2
psp9000333 said:
cant be, im using a thick as hell otterbox commuter case and im getting full bars plus LTE support. my carriers koodo btw.
Sent from my SGH-I747M running Liquidsmooth JB 4.2.2
Click to expand...
Click to collapse
Yeah usually only when a metal case is used does it ever really interfere I suppose.
Sent from my GT-I9300 using xda app-developers app
Possible problems:
1) Wrong modem. Flash one that worked previously.
2) Mobile phone network problems (we tend to overlook this a lot). Contact your carrier and ask if your networks keep going down.
3) Signal interference (maybe some casing, maybe something in your house)
4) Damaged phone (maybe the signal receiver got damaged in a fall)
I've been having similar signal drop issues. Phone shows 2 bars but no data use, no sound when trying to ring out, can't receive a call. If I toggle 2g, signal will spring back to life and data will show. Changed bloody everything trying to resolve it. Orange UK.
Sent from my GT-I9300 using xda premium
Choristav said:
This isn't your blog, go back to facebook or wherever you came from.
Click to expand...
Click to collapse
I think you are the one who should go back, were you came from. Seriously right, it's people like you who joined xda yesterday, who have no clue whatsoever about the principles and tradition of xda, who tarnish the name of this great website. The op is talking about an s3, in a s3 forum, were would you want him to go, other than here. If you can't help, just shut it, and let the people who can help go ahead, like the people who posted after your senseless post to help the op.
1. Solar flares got you.
2. Reception problems, UK austerity hair cut, you get 10% of any signal you had before.
Sent from my GT-I9300 using xda app-developers app
Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.
It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.
So the knock on feature is supposed to be more reliable if I do this?
in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.
Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app
Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....
Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks
I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app
I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4
Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.
jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
Hello, I have been experiencing moments of "freezing" or unresponsiveness as well.
For me, it seemed to be due to chrome or using power saving mode. (People in another forum were blaming their droid maxxs freezing problem on chrome) I disabled chrome and disabled power saving mode.
Then I started using opera. I experienced another moment of unresponsiveness using opera without the power saving mode.
I was thinking back to the first times that it happened and it seemed to be paired to the wifi download and upload symbol being active in upload and download activity.
I know that correlation does not mean causation, but I think it is worth exploring if the network activity is causing it to somehow hang.
This bizzar occurance made me perform a factory wipe leading to another round of issues involving processing err_0000, but that is another story; sadly, it didn't even fix the issue.
OP, are you still experiencing the moments of unresponsiveness? If you are, have you noticed the events that are correlated with the event?
Has anybody else experienced this or found a remedy?
It could be one of the apps from the play store that is not playing nice with kitkat, but due to the multitude of other issues, I'd say it is a kitkat or touchwiz flaw.
Thanks for any help.
Lago
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
I had an issue with screen not responding sometimes .....I figured out it was due to the flip case (original by Samsung). Although lately I haven't experienced that either.
Try using the original non flip case and see if you still have the issue.
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Try using the original non flip case and see if you still have the issue.
Click to expand...
Click to collapse
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
lagoboss said:
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If your phone isnt hanging up and freezing, that gives me hope. I'll gsm reset, clear the cache and then flash.
Thanks
Sent from my SM-N900 using xda app-developers app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just cleared the cache, factory wiped, and installed the Russian update N900XXUDNC4 and so far, the phone is a lot smoother. No hangups in the browser yet, but time will tell lol.
It is annoying setting up the phone like new lol. I'll update the post as to if I have moments of freezing or the screen becoming unresponsive.
Sent from my SM-N900 using xda app-developers app
Cheers mate..do tell me how the battery is..if its good I might flash Russian as well ,currently have but flashed
Sent from my SM-N9005 using XDA Premium 4 mobile app
Had this problem too, as well as lots of lag. Reflashed and did a factory reset. Took care of both.
Sent from my SM-N900W8 using xda app-developers app
Battery life is looking good. Power Saving off, bluetooth on and connected to my smart watch.
I made one short call. I don't talk on the phone that much. I mostly use it for Internet browsing, music, and instant messaging/texting. I'll update on Tuesday when I have a full day at school.
Keep in mind though that the n9005 is the lte version. I have a n900, the non lte international variant; our battery life may be different.
Edit: 4/20/2014 same charge 70% 1 day 6 hours bluetooth, wifi, gps, and 1 Gmail account in sync.
Sent from my SM-N900 using xda app-developers app
Even I experienced the same. My phone came with Kitkat installed. Freezing happens when a webpage is loading or the time i turn on Sync etc. strange thing is phone seems smooter when power save mode turned on.
I think it may be a problem that was not fixed until the March 31st 2014 KitKat build. I have been using Chrome heavily since I installed the most recent official rom; I have not experienced any lag or hanging system wide or in the browser. It reminds me of 4.3.
When I wiped and reinstalled the previous rom, I noticed the lag and unresponsiveness right away.
I'm going to use the browser heavily next week. If I have no issues, I think it may be safe to say that the bug was fixed in the latest kitkat with March 31st 2014 build date.
People with lag, do you have the lte variant or the regular SM-N900? I'm starting to think only the SM-N900 are being impacted by sour Sammy updates.
And if you guys wipe your phones, make sure to turn reactivation lock off because it could cause an error that will not recognize your real Sammy account and password. This phone has become stressful; I'm not updating it again lol
Sent from my SM-N900 using xda app-developers app
I just experienced another moment of unresponsiveness using the google search box within the chrome app running DNC4 :/ Going to try the latest Russian KitKat
Sent from my SM-N900 using XDA Free mobile app