I bet if you took a look at the majority of these people who have really laggy phones you would find many sideloaded apps, tons of widgets, and lots of memory sucking apps in general. Of course the phone will lag.
Oh thank you. I didn't really know much about those options.
I'm not sure why there is so much denial on the stutter and lag with Galaxy devices. I'm a Samsung fan and at this point I don't care if there are little stutters or dropped frames occasionally because I now prefer the Samsung/Grace UX over both iOS and vanilla Android.
During the months I had the S7 there was noticeable lag when clicking the home button. It was definitely noticeable when compared to the Pixel, which I traded in my S7 for. Pressing home didn't take you to home as quickly on the S7 as it did on the Pixel. There was a slight delay from the time your finger presses home and you see home. Pixel was instant. I refer to that delay as lag. I don't know what else to call it.
And on all of the S8 demo models I've tried, there are dropped frames when swiping up for the app drawer and again dropped frames when opening apps from the app drawer, though it doesn't seem to happen 100% of the time.
Again, like I said, I don't care. I'll accept those things because I prefer the hardware and UX of the S8 over all current competition. But I find it perplexing when people swear that those little stutters and lags don't exist on their specific devices, as if it's just a one-off occurrence for it to happen, even though it has happened for every single Galaxy device I've owned or used in store.
I'm not sure why there is so much denial on the stutter and lag with Galaxy devices. I'm a Samsung fan and at this point I don't care if there are little stutters or dropped frames occasionally because I now prefer the Samsung/Grace UX over both iOS and vanilla Android.
During the months I had the S7 there was noticeable lag when clicking the home button. It was definitely noticeable when compared to the Pixel, which I traded in my S7 for. Pressing home didn't take you to home as quickly on the S7 as it did on the Pixel. There was a slight delay from the time your finger presses home and you see home. Pixel was instant. I refer to that delay as lag. I don't know what else to call it.
And on all of the S8 demo models I've tried, there are dropped frames when swiping up for the app drawer and again dropped frames when opening apps from the app drawer, though it doesn't seem to happen 100% of the time.
Again, like I said, I don't care. I'll accept those things because I prefer the hardware and UX of the S8 over all current competition. But I find it perplexing when people swear that those little stutters and lags don't exist on their specific devices, as if it's just a one-off occurrence for it to happen, even though it has happened for every single Galaxy device I've owned or used in store.
I've posted these same complaints before.
https://forums.macrumors.com/threads/nexus-n-pixel-xl-2016.1951300/page-62#post-23759153
And if the lag is too much for people, there are plenty of other options in the Android space. The end.
I think the frustration though is that this has been a common and frequent complaint for years now and it doesn't seem like Samsung has fully resolved the issue.
For me, if they would fix the lag as well as get rid of that horrible warning that comes up anytime you want to turn your volume up more than halfway, I would seriously consider making a full switch from iOS.
That's an EU directive though, isn't it?
Hard Brexit should allow you to abolish all EU protections UK citizens enjoy today.That's an EU directive though, isn't it?
I think the frustration though is that this has been a common and frequent complaint for years now and it doesn't seem like Samsung has fully resolved the issue.
For me, if they would fix the lag as well as get rid of that horrible warning that comes up anytime you want to turn your volume up more than halfway, I would seriously consider making a full switch from iOS.
Biggest annoyance ever!!!!!! Please for the live of God, give me the warning once and then let me disable it forever!For me, if they would fix the lag as well as get rid of that horrible warning that comes up anytime you want to turn your volume up more than halfway, I would seriously consider making a full switch from iOS.
I think the frustration though is that this has been a common and frequent complaint for years now and it doesn't seem like Samsung has fully resolved the issue.
For me, if they would fix the lag as well as get rid of that horrible warning that comes up anytime you want to turn your volume up more than halfway, I would seriously consider making a full switch from iOS.
I thought they got rid of the volume thing? When I was beta testing Nougat on my S7E, it seemed like it never popped up again. Or there was a checkbox that said don't warn again? I forget, but I thought that was solved.
If not, fully agree. It was one of my biggest complaints all the back to the S6. It's a very Apple-like thing to do; baby their users with repeated warnings and obnoxious security measures.
As for the lag, it's milliseconds of difference that grows smaller and smaller per iteration of their software. It's a shame that that's stopping people from experiencing all the good that TouchWiz has to offer, but I understand preferences. Thankfully plenty of Android choices.
That's an EU directive though, isn't it?
As far as I know its from 2013 directive and applies to all mobile devices that play music and come with headsets so not applicable to tablets/Ipads
I understand the only way to avoid it on an IPhone is to jailbreak it or get a non EU version
I've never once seen this warning on the iPhone. Just Samsung devices.
I've never seen the warning on any non-Samsung phone.
It is on the pixel, but it only asks you once, after you dismiss the warning it never asks again, which is how it should be handled on all devices.Nor on the Pixel.
The only frustrating aspect about the design of the Galaxy S8 and S8+ seems to be the placement of the fingerprint sensor. There’s a good chance of the rear-facing camera lens getting smudged due to the abnormal placement of the fingerprint sensor, and Samsung knows that. Why did the company choose to place the fingerprint reader right next to the camera sensor then?
A new report from The Investor claims that Samsung poured a lot of money into Synaptics to help them in developing an on-screen fingerprint reader to allow users a larger-than-ever Infinity Display as well as an easier way for them to unlock their phone. However, Synaptics reportedly failed to develop the technology in time for the mass production of the Galaxy S8 and S8+. As a result, Samsung had no option but to relocate the fingerprint reader beside the rear-facing camera.
“Samsung poured resources into Synaptics’ fledgling technology last year, but the results were frustrating. With the production imminent, the company had to decide to relocate the fingerprint scanning home button to the back of the device at the last minute,” a source briefed The Investor on the matter on condition of anonymity. An industry insider told the Korean publication that it’s extremely difficult to make transparent sensors and components
Leaked images of a Galaxy S8+ prototype, which we reported yesterday, showed a dual-camera setup and no fingerprint sensor beside it. Moreover, the Exynos 8895 SoC also supports a dual-camera setup. This leads us to believe that Samsung had plans to use a dual rear-facing camera for the S8+, but had to ditch it to fit the fingerprint sensor without affecting the placement of the battery and wireless charging coils.
Apple is reportedly making efforts to make an iPhone with an on-screen fingerprint reader, which would help it in ditching wide bezels. If Apple debuts an iPhone with such a technology, Samsung would be on the back foot. Currently, China’s Goodix and South Korea’s CrucialTec are said to be working on such on-screen fingerprint readers, and they showcased their technologies at MWC, but no time frame was provided for their commercial launch.
I'm not sure why there is so much denial on the stutter and lag with Galaxy devices. I'm a Samsung fan and at this point I don't care if there are little stutters or dropped frames occasionally because I now prefer the Samsung/Grace UX over both iOS and vanilla Android.
During the months I had the S7 there was noticeable lag when clicking the home button. It was definitely noticeable when compared to the Pixel, which I traded in my S7 for. Pressing home didn't take you to home as quickly on the S7 as it did on the Pixel. There was a slight delay from the time your finger presses home and you see home. Pixel was instant. I refer to that delay as lag. I don't know what else to call it.
And on all of the S8 demo models I've tried, there are dropped frames when swiping up for the app drawer and again dropped frames when opening apps from the app drawer, though it doesn't seem to happen 100% of the time.
Again, like I said, I don't care. I'll accept those things because I prefer the hardware and UX of the S8 over all current competition. But I find it perplexing when people swear that those little stutters and lags don't exist on their specific devices, as if it's just a one-off occurrence for it to happen, even though it has happened for every single Galaxy device I've owned or used in store.
I've posted these same complaints before.
https://forums.macrumors.com/threads/nexus-n-pixel-xl-2016.1951300/page-62#post-23759153
Exactly. I am not anti Samsung, I think the best phone they made was the Galaxy S4 GPE ( Google Play Edition ), which was the S4 running stock Android, directly updated by Google. At the time when that phone was new, to compare the standard Touchwiz S4 version, next to the S4 GPE version, was night and day difference, in overall smoothness and performance, like a radical difference.
Sure fast forward a few years, and TW has gotten better, but along with their brute force method of state of the art fastest hardware to force it to be smooth. It works mostly, but that lag and hiccups are still there, and they typically come out after the phone ages, 6 months down the road, or one year later.
You want a lag free, or way less lag phone, then get the iPhone 7 Plus, or Pixel XL. Otherwise put up with the acceptable chop the Galaxy line has always had, but seems 99% of the user base is just ignorant to it, and doesn't know they should care.