bruben7886
Diamond Member
- Joined
- Dec 6, 2011
- Messages
- 1,687
- Reaction score
- 1,728
Shhhhh.....Come closer.....Got a secret for you.....THE RUSSIANS DID IT!
Sent from my SM-G935V using Tapatalk
Sent from my SM-G935V using Tapatalk
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Samsung makes amazing devices, and as a complete package no one else really matches them. If they'd get a backbone and stop allowing carriers to add bloat they'd pretty much be the best of the best in every way.
Sent from my SM-N910V using Tapatalk
None of them are even remotely comparable to Samsung in terms of the revenue they help bring to wireless providers. The point is that they have the clout to stop it, but they cater to carriers and not consumers.because HTC, Sony, Moto & LG don't allow bloat?
S7 Edge tap'n
Apple has bloat also, Safari being just 1 example.That's besides the point. Bloat is big business plain and simple and no manufacturer, regardless of size, is going to stop installing bloat. (Or stop allowing bloat to be installed by carrier's) Even Nexus devices have bloat....it may be small Google bloat, but it's still bloat nonetheless. If the average consumer truly cared about bloat on their device, Nexus would be the number one selling device, not Samsung.
S7 Edge tap'n
I'm not going to give up the out of the box features and functionality that Samsung offers to avoid that, it simply would be a nice change. And you're quite wrong: Apple absolutely keeps all that carrier garbage off of their devices. Strangely enough, they seem to have smother overall performance over Android devices year after year. Yes, their hardware helps with that, but carrier bloat that is horribly unoptimized and constantly running on Androids sure doesn't help.That's besides the point. Bloat is big business plain and simple and no manufacturer, regardless of size, is going to stop installing bloat. (Or stop allowing bloat to be installed by carrier's) Even Nexus devices have bloat....it may be small Google bloat, but it's still bloat nonetheless. If the average consumer truly cared about bloat on their device, Nexus would be the number one selling device, not Samsung.
S7 Edge tap'n
Bloat has nothing to do with "smoothness" of ios. Here is the technicals of why it feels smoother.And you're quite wrong: Apple absolutely keeps all that carrier garbage off of their devices. Strangely enough, they seem to have smother overall performance over Android devices year after year. Yes, their hardware helps with that, but carrier bloat that is horribly unoptimized and constantly running on Androids sure doesn't help.
With Touch Wiz it's "someone is touching me. What do I do now?" Then "oh yeah , I'm supposed to react".Bloat has nothing to do with "smoothness" of ios. Here is the technicals of why it feels smoother.
In iOS, UI rendering processes occur with dedicated threads in real-time priority, halting other processes and focusing all attention on rendering the UI. . In other words, every time you touch your finger to your iPhone’s display, the OS literally goes crazy: “Someone’s touching us! Someone’s touching us! Stop everything else you’re doing, someone’s touching us!”
In Android, though, UI rendering processes occur along with the main thread with normal priority. In other words, it treats rendering the UI the same way as it would, say, downloading a podcast in the background, checking for SMSes, or anything else. Hence, a choppy UI.
With Touch Wiz it's "someone is touching me. What do I do now?" Then "oh yeah , I'm supposed to react".
Support Our Troops!!!
Beast Mode 4
<><
So extra processes constantly eating up RAM and CPU power has zero to do with the extra lag on Android devices? Not buying that for a moment. Both hardware and software side issues cause Android issues, and carrier bloat is doing nothing to lessen that, especially because the carriers by no means bother to optimize for each divice.Bloat has nothing to do with "smoothness" of ios. Here is the technicals of why it feels smoother.
In iOS, UI rendering processes occur with dedicated threads in real-time priority, halting other processes and focusing all attention on rendering the UI. . In other words, every time you touch your finger to your iPhone’s display, the OS literally goes crazy: “Someone’s touching us! Someone’s touching us! Stop everything else you’re doing, someone’s touching us!”
In Android, though, UI rendering processes occur along with the main thread with normal priority. In other words, it treats rendering the UI the same way as it would, say, downloading a podcast in the background, checking for SMSes, or anything else. Hence, a choppy UI.