Earlier quoted context omitted.
This is a fair point but everything is online and at our finger tips. Having it on your phone just means you’re not sitting at your computer for longer hours, hurting your back, neck and even fingers.
Lots of people having fingers and neck pain due to phone usage. I see lots of bad posture as well
The 2020 iPhone SE
151–160 of 317 posts
Re: The 2020 iPhone SE
#152Compared to my first gen SE, I'd like the faster processor, better camera and better battery life. But I'm not sure I'm willing to go up in size and weight, and get the rounded edges that make it even harder to grip one-handed. For me, a bigger screen isn't a plus - after years of following the trend and being on my phone more and more, I managed to kick the habit and I'm very happy that my phone has now found its ri…
Re: The 2020 iPhone SE
#153Earlier quoted context omitted.
Well, apart from a decent Android phone with a small screen.
I think the Samsung Galaxy S10e is the closest current model. It's not as small as I would like, but it's at least a sane size.
The old SE that I’m currently using in 58.6mm
Neither google or android serve this market.
Re: The 2020 iPhone SE
#154I don't really see his attempts to use the new gestures on the old-design iPhone as proof that the new UI is better. People still tell me to "tape" long after it was obvious that DVRs are better. It's simply muscle memory. Still not sure that this my next phone though, probably going to stick with the old school SE. I had asked work for an upgrade, got the giant XR, and after five days put it right back in the box an…
It's cool that Apple made a cheap phone, but what I actually wanted was a small phone and price wasn't that relevant. What most of the world wants is a quality cheap phone, and size isn't that relevant. This is especially true as the world enters a global recession.
Re: The 2020 iPhone SE
#155Earlier quoted context omitted.
FaceID doesn't work when I'm using my phone in bed. I lie on my side, and can't unlock my phone. Maybe that's weird, but it's something that I've been frustrated with every single day since upgrading from the 6s.
Same, switched to Samsung A70. Every night at bedtime I swear at the FaceID not working nor (!) the under the screen Touch ID until the 8:th try. Even a headphone cable touching the screen will wake the screen up. Having rounded sides is also something that just reeks of Windows XP blue theme to me. Playful but utter useless (for the grip). I have to remember to not squeeze the phone too hard every time because then…
Also headphone cable doesn't wake up my iPhone 11.
Re: The 2020 iPhone SE
#156Earlier quoted context omitted.
Same, switched to Samsung A70. Every night at bedtime I swear at the FaceID not working nor (!) the under the screen Touch ID until the 8:th try. Even a headphone cable touching the screen will wake the screen up. Having rounded sides is also something that just reeks of Windows XP blue theme to me. Playful but utter useless (for the grip). I have to remember to not squeeze the phone too hard every time because then…
Hm.. have you tried the Face ID on iPhones or just the Samsung A70 and other single-camera style Face ID? My iPhone 11's Face ID works without issues even at night in bed, but I've used Honor 10 before and had a lot of issues with its face recog including night usability, so I rather disabled it.. Also headphone cable doesn't wake up my iPhone 11.
Re: The 2020 iPhone SE
#157Those benchmarks are impressive. iPhone SE beating the 2019 MBP in single core performance? That's fantastic! I wish I could comment on or know what he was talking about with the iPhone X vs "old iPhone" interaction paradigm. I personally thought the "single button" hardware interface was an incredible innovation that changed everything. Even Android relies on it. My Galaxy S9+ has a "software home button" (like most…
the real question is why we need that performance in your phone? I'm honestly asking, because with every flagship phone (no mater the brand) there is the hype about performance (X's processor is 2x quicker than Y) and it always makes me think. I don't think that in the last 10 years I ever had thought "I wish my phones CPU had higher clock speed"...
As the screen size and refresh rate increase, the needs of the CPU/GPU and Flash will increase.
Mobile phones tend to be more interactive and thus have a larger negative experience with slow/jerky scrolling, slow response to taps including app launch, etc.
Microcontrollers tend to have options from slowing down the clock rate to going into a deep sleep mode when there is no scheduled work. There has been a lot of work to optimize the scheduling of network/driver/app tasks to minimize power draw. It is also fairly common to see a CPU have lower power cores, typically for the OS to leverage for hardware support and background tasks separate from what might be considered the 'main' CPUs for this reason.
Likewise, Apple has stopped shooting for a 50-100% increase in performance year over year, instead going for a mix of performance and power efficiency improvements. They have also started to do significantly more custom silicon design to support their hardware features, such as the Secure Enclave and neural engine additions used to support Face ID.
10 years is a long time though. Four years ago would be what, the iPhone 3GS? Apple went several years doubling the CPU, GPU, _and_ Flash performance and it was extremely noticeable.
Re: The 2020 iPhone SE
#158Re: The 2020 iPhone SE
#159Earlier quoted context omitted.
Fun fact: iPhone's buttons are not mechanical buttons starting with iPhone 7. The click you feel when you press it is just the taptic engine. If you have an iPhone 7 or 8, try turning it off and try to press the button.
You shouldn't need to turn it off, it feels like a knockoff of a real button, like a fake designer bag. Don't know what was wrong with a regular button that presses.
Re: The 2020 iPhone SE
#160Earlier quoted context omitted.
Do mobile chips focus less on floating point for some reason? Could that explain the seemingly massive difference in perf/watt?
Floating point tends to matter for classic 'number crunching' workloads- crypto, media encoding, anything to do with modeling the physical world, image processing, AI. Phones tend towards 'control flow', e.g. display an interface, accept a user input, communicate with a server, display information... and media decoding & gps both have dedicated hardware. FP workloads can be incredibly power hungry, so it's fortunate…