447
People want 'dumbphones'. Will companies make them?
(www.bbc.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 May 2024
447 points (93.9% liked)
Technology
59583 readers
2308 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Thank you so much for sharing your experiences - that should definitely help people!:-)
I wonder if they perhaps have some QA issues, so you got a lemon, or maybe the design itself is just that bad. You wouldn't necessarily know, I'm just musing out loud!:-P
One thing I do want to ask if you don't mind - b/c I don't know how to interpret the specs and I no longer trust paid reviewers - is how smooth does it handle? Like, noticeable lags or no? If it is basically a cheapie smartphone for a sub-flagship price, I might even be okay with that but wanted to know before getting into it.
Keep in mind that my basis for comparison is a Galaxy S9. The Fairphone feels smoother and more responsive most of the time, but you do occasionally get freezes and lag spikes, mostly when you try to minimise an app that is currently loading something from my experience. Particularly heavy websites also slow it down sometimes, but pretty rarely.
And I wouldn't really call the design "that bad", I was listing off my issues with it, so it might have come across that way, but the majority of the time it works completely fine.
So on a scale of 1-5, responsiveness might be a 4?
About the design, I mean like a poorly-placed power button that is easily triggered (and then whatever confirmation procedure is in place can be performed by your pocket), or the sudden drainage of battery issue could be something about poor Quality Assurance when they pick batteries at the factory to put into the devices prior to shipping them out. Or worse, you could replace the battery and that effect could still happen!?
I had a Nexus 5 that would dial things, like even emergency #s (fortunately I don't think it would actually do the call, just dial the numbers) while in my pocket - it may have had something to do with turning the screen on while a headphone jack was plugged into it. I replaced the OS for other reasons and that happened to solve that issue as well:-). So I would not turn a phone away for such a thing, especially if there is a software/configuration fix.
But responsiveness is as much due to hardware as software - e.g. if Firefox runs slow b/c it was compiled for and websites (even mobile) designed for higher-end specs.
Yeah, I'd say 4 is about right. And the power button is a bit recessed (it doubles as the fingerprint reader), so it's really hard to press it accidentally. I genuinely have no idea how it could randomly turn off in my pocket. As for the battery, I'm pretty confident it's a software issue. It's only happened twice in the 4 months I've owned the phone and a restart fixed it both times.
Thanks for the additional feedback!:-) That does greatly reassure me.
Since you said the phone would come right back on immediately thereafter, it sounds to me like it does not seem connected to the battery issue.
Unless the battery issue wasn't "really" a discharge but the sensor somehow being tricked into thinking that the battery was dying - in which case the phone likely shut down gracefully rather than risk a brown-out situation, but then when you powered it up later it realizes once again that it has battery.
But in a more normal scenario, if you have either tap-to-wake or if hitting the power button results in a screen prompt confirmation that does not require a fingerprint or PIN, and especially if you were walking or cycling or some such, then the screen likely rubbed up against your pocket lining and managed to cause the proper combination of actions to shut it off. It could not start up an app that way - that would need your login - but turning a device off usually requires lesser security.
Fortunately the latter may be possible to fix with a configuration setting or other software fix:-).
Hmm, I do have tap to wake and that is giving me an idea. You can pull down the status bar while the phone is locked and in the bottom right corner there's a power button. So theoretically my leg can double tap the screen, pull down the status bar, tap the power button and confirm. Feels like a bit of a stretch but who knows. I've never had it randomly turn off while I was using it or while sitting on my desk after all ¯\_(ツ)_/¯
That's likely it. Weirdly, turning off that feature may not make all that much of a difference, bc it's so incredibly rare, but if you don't need it - like a long press of the power button would do just as well, in the also rare event that you want to turn it off at all - then disabling that feature would give you peace of mind.
Either way, I'm glad I could help by giving you the idea of how to (maybe) fix it!:-)
The frequency of this issue happening probably varies per person like depending on pockets and usage patterns and such. Like nowadays when I go cycling I either put the phone into an attachment on the front of the bike, or after that broke I put it in my backpack, and either way it never randomly turned off. And in my old Nexus where the issue did happen, the headphone jack working to pull the phone up more than it would have done all on its own probably contributed. i.e., for some people it will never be a problem with their patterns, but if it is for you, then presuming that's it, disabling that power-off feature (if you can) should make you much more satisfied!:-)