Any lags on S6?

Which is odd because that doesn't seem to be the case on other devices. T-Mobile should have kept these until the 10th like everyone else. This hasn't been the best pre-launch so far.

Posted via the Android Central App

The tortoise won the race if you recall.
 
Not fixed on my S6 edge...very laggy browser performance because of the re-drawing but also affects Facebook, Twitter and other apps. Scrolling on the S6 has very little momentum is the best way I can describe it...it scrolls a bit then stutters and stalls (obviously waiting for the re-draw).

Completely opposite of the experience of my iPhone 6 Plus which I used before this which had utterly brilliant scrolling momentum, like glass. Hoping there's a quick software update that fixes this. I can't imagine anybody but early adopters putting up with this because you really notice it in day to day use.

Man, I've been trying to help you on your issues since the first time I saw your review post, but come on man, you keep posting negative posts without even tell us what exactly you are doing to try to fix those weird issues you have.

You were the first one and as far as I can remember the only one that has posted that you lost 30+% of battery overnight, the first one that says that is laggy and stuttering, but I've been suggesting doing a couple of adjustments to try to pinpoint your issue, some troubleshooting but I haven't read a single post of yours telling us what you have done, if anything.

Like I said in other post, if you really have an issue, it won't magically fix itself, you either be pro active and try to find what may be the issue, or wait for T-Mobile to fix it. But according to all the things you have posted, I've said it a couple of times already, just go to T-Mobile or contact them and ask for a replacement, because if you don't have a Rogue app causing all your issues then you have a faulty device. Rogue App will require from you to look for it because if not you may get 10 replacements and none of them will work as you expect.

For the last time, post your battery stats, let us see here what is causing your issues at least with the battery, maybe one is causing the other, but you keep posting negative post after another but without any proof that you even have the device it has beginning to look suspicious to me. I don't want to imply anything here, but come on, as you can see, what I'm describing here has been a good summary of all your posts but not a single, I did this or that, here is my Screenshots, etc..., Nothing.
 
So it appears that all these issues/concerns are with S6's including edges on T-Mobile only? Maybe they jumped the gun a little and should have waited for later hardware/software builds to show up before allowing them out in the wild??? I even read one post (I think it was on XDA) where the person received his with a scratched screen with dead pixels, and then the replacement he got overnight had a scratched screen also! :mad: :( :confused:
I know Verizon is the slowest, but maybe it's wisdom on their part to be last.
Did T-Mobile get a deal on these early release phones so that they could make more $$$$ up front and figured it was worth the risk of a few disgruntled customers???
Didn't they already release a software update like on day one? That is surely unusual!
Could be the other three carriers are waiting for these issues to fixed up front before the rest of us lemmings get ours. :D
 
Which is odd because that doesn't seem to be the case on other devices. T-Mobile should have kept these until the 10th like everyone else. This hasn't been the best pre-launch so far.

Posted via the Android Central App

I am not sure what this would have accomplished?
 
Regarding the browser redrawing issue, how is connection quality when this happens? I am curious because I noticed the WiFi speed was poor at BB demo units when I saw. Usually their free WiFi is not very good as I had the same slow speed on S5. If this happens on T-mobile unit, I wonder if it's affected by signal quality.
 
If there's issue with the firmware, pushing them out early would be a mistake.

Posted via the Android Central App

But .. A week won't fix it. They just have to release another update. They already released the firmware update. I just don't see how a week would make a huge difference... especially when they wouldn't know the issue until users actually use it and report it. So therefore .. it is more beneficial that they're finding out about it / can possible get something out before a full on public release.
 
But .. A week won't fix it. They just have to release another update. They already released the firmware update. I just don't see how a week would make a huge difference... especially when they wouldn't know the issue until users actually use it and report it. So therefore .. it is more beneficial that they're finding out about it / can possible get something out before a full on public release.

They'd know because they'd still release review units and those units would show these flaws. If AT&T launches with none of these issues, it'll be a shame because that could have been the first impression T-Mobile users got if they had waited. Don't get me wrong; I'm happy you guys got your phones. I'm jealous.

Posted via the Android Central App
 
They'd know because they'd still release review units and those units would show these flaws. If AT&T launches with none of these issues, it'll be a shame because that could have been the first impression T-Mobile users got if they had waited. Don't get me wrong; I'm happy you guys got your phones. I'm jealous.

Posted via the Android Central App

But AT&T having the same issue could be unlikely if it is tied to something like WiFi calling since that is a T-Mobile thing. Sure the review units may have flaws .. but still .. delaying a week won't be enough to code, test, and deploy just because a review unit had the issue. Most bugs aren't noticed till released to the masses and tons report the same thing. Especially with something like battery which can vary greatly user by user.
 
But AT&T having the same issue could be unlikely if it is tied to something like WiFi calling since that is a T-Mobile thing. Sure the review units may have flaws .. but still .. delaying a week won't be enough to code, test, and deploy just because a review unit had the issue. Most bugs aren't noticed till released to the masses and tons report the same thing. Especially with something like battery which can vary greatly user by user.

I'm not sure it is tied to the WiFi Calling, honestly, but we'll have to see. Since they were delivered as soon as Saturday the 28th of March (though most got it that following Monday/Tuesday), it's 2 weeks of time to notice the bugs. I'm not saying it's blasphemy they released it early, but it could have potentially avoided these issues. We know they were still testing at that point because they updated less than a week into the shipments.
 
I'm not sure it is tied to the WiFi Calling, honestly, but we'll have to see. Since they were delivered as soon as Saturday the 28th of March (though most got it that following Monday/Tuesday), it's 2 weeks of time to notice the bugs. I'm not saying it's blasphemy they released it early, but it could have potentially avoided these issues. We know they were still testing at that point because they updated less than a week into the shipments.

I mean I get what you're saying but .. see we aren't even sure what it is tied to so .. They wouldn't be able to identify, code, and deploy to solve. Bugs happen .. That is why even video games have open betas. They do closed .. squash a bunch .. then release open because once the masses get in and try doing stuff they never dreamed of .. They go ... "Oh man we messed that up" and fix it :).

Don't get me wrong I would rather not have this issue.. Just don't think that week would matter. Just going to take some troubleshooting to solve .. Sounds like the story of my life (due to my job) lol :P.
 
I mean I get what you're saying but .. see we aren't even sure what it is tied to so .. They wouldn't be able to identify, code, and deploy to solve. Bugs happen .. That is why even video games have open betas. They do closed .. squash a bunch .. then release open because once the masses get in and try doing stuff they never dreamed of .. They go ... "Oh man we messed that up" and fix it :).

Don't get me wrong I would rather not have this issue.. Just don't think that week would matter. Just going to take some troubleshooting to solve .. Sounds like the story of my life (due to my job) lol :P.

Either way, I hope it's fixed for you guys soon. I also hope that the AT&T variant has zero of these issues. Ha.

Posted via the Android Central App
 
Approximately half a day in, after reinstalling the 30 apps I used to have on my HTC One M7, importing thousands of text messages, and downloading dozens of podcasts and audiobooks the only lag I have experienced is from the well reported Flipboard home screen (which can be disabled), and the most minor delay associated with the default Samsung keyboard. Having now switched to an alternate keyboard I can report stutter free usage, it positively flies!

What keyboard alternative do you use?
 
I mean I get what you're saying but .. see we aren't even sure what it is tied to so .. They wouldn't be able to identify, code, and deploy to solve. Bugs happen .. That is why even video games have open betas. They do closed .. squash a bunch .. then release open because once the masses get in and try doing stuff they never dreamed of .. They go ... "Oh man we messed that up" and fix it :).

Don't get me wrong I would rather not have this issue.. Just don't think that week would matter. Just going to take some troubleshooting to solve .. Sounds like the story of my life (due to my job) lol :P.

What issues are you speaking of? How does the device perform compared to the Note 4?
 
Man, I've been trying to help you on your issues since the first time I saw your review post, but come on man, you keep posting negative posts without even tell us what exactly you are doing to try to fix those weird issues you have.

You were the first one and as far as I can remember the only one that has posted that you lost 30+% of battery overnight, the first one that says that is laggy and stuttering, but I've been suggesting doing a couple of adjustments to try to pinpoint your issue, some troubleshooting but I haven't read a single post of yours telling us what you have done, if anything.

Wow...not sure what your deal is but you are really obsessed with me for some strange reason! No, it was not me that posted I lost 30% overnight...that was somebody else's Thread (but I chimed in, along with MANY others, that I was seeing huge standby losses too that were perplexing at the beginning of the week).

You seem not to recall but I responded directly to some of your suggestions and thanked you for your perspective and complimented you on the S5 post you had of YOUR battery savings tips that work for YOU. You have suggested I take my screen down to 20% dim (sorry, can't live with that), you wanted me to turn off Location Services (doesn't work for ME either, I'm sure it's fine for YOU and I'm happy that YOU are willing to give up these and other things to optimize your battery life but I'm not).

I have done a Factory Reset of my phone with zero improvement. What an utter waste of time that was.

You seem to be missing the point here. These are not issues with trying to "optimize" my battery or solve lag - these are software issues that T-Mobile/Samsung/Google need to fix (software flaws that I have no control over) and I'm sorry if me reporting them disturbs you for some reason. I'm one of a small number of people that have been using an S6 edge for 5 days so I thought the community would be interested in my experiences (which are the same experiences many others are having as well).

You seem to think these issues are "mine". This is not my Thread but the OP asked about lag and I have noted lag on my phone from the time I got it on Monday. There is an 8 page thread on XDA Forums of people having the exact same battery life issue I am which seems to be narrowed down to a WiFi bug. It is causing HUGE Cell Standby numbers that drain the battery in Standby. Attached is a pic from last night showing Cell standby and Android system draining my battery down to 57% with almost no use on my part. And, yes, WiFi and WiFi Calling were on - those are important features to me.

I have turned off WiFi (at the suggestion of XDA) and battery life did improve dramatically, but no offense to you but I didn't just pay $1000 coming back to Android for a phone without WiFi and to lose WiFi calling which is needed at my house and usually at my office because of spotty cell coverage. That's a ridiculous solution and I'm not on an unlimited data plan so it wouldn't be a solution for me anyway.

I'm sorry that you feel some compulsive need to criticize me anytime I mention that the S6 has some lag and poor battery life. I get it - you think you have the solution by turning off half of your phone's services.

I've said lots of good things about the S6 in a number of posts and think if these issues can be fixed with a quick update, it will be a stellar phone - one of the best ever made. I am truly hopeful that they fix these issues before YOU get YOURS so that you won't also have to report the same issues (which I wouldn't criticize you for), but I'm not going to sit back and be quiet and be an apologist for Samsung on this when people about to spend nearly $1000 for a phone ask questions about it from those of us who actually own them.

I'm not a Fanboy of any platform and think they all have their merits but the fact is that the S6 does not scroll with good momentum like an iPhone and the battery life, at the moment, is atrocious if WiFi is on. That's ridiculous for a $1000 phone and I'm going to keep sharing my experiences so that T-Mobile/Samsung/Google take some action to fix these issues. Thanks.

NOTE: Almost all this drain came during the S6 in Standby yesterday evening (almost no on-screen time) with WiFi and T-Mobile WiFi Calling on.
Screenshot_2015-04-02-21-03-58.jpg
 
Last edited:
What issues are you speaking of? How does the device perform compared to the Note 4?

It is worse in battery than the Note 4 but that is pretty much to be expected since the Note 4 has a big battery. Performance wise it actually is very snappy and the new animations actually help as well.

The issue seemed to be with "Cell Standby" draining the battery unnecessarily but it has calmed down after the first day or two. It seems if i shut WiFi calling off it helps a lot.

See here -- http://forums.androidcentral.com/sa...rs-how-s-your-battery-life-9.html#post4328218