At this point I don’t even care about the hardware anymore if I am basically expecting that there will not be security updates for as long as I want to use the functioning hardware. That is true for all the Android phone manufacturers.
I think that companies are subject to SoC manufacturers here (except Apple/Samsung that build their own chips). You, as a manufacturer, buy the SoC from say Qualcomm and they only maintain Android builds of it for a set period of time - and then you (and your users) are screwed because Qualcomm of course doesn’t share specs with you so you can write your own kernel drivers for it.
I don’t see how that would be my problem as a customer.
Of course it’s in the company’s best interest to sell me a new phone after just 2 years but then they’ll lose me as a customer after that one phone. If the open source Android distros manage to get security updates for older devices shipped I fail to see how large companies would, except that they simply don’t care/deliberately don’t.
I was excited for a bit, bit seems this won’t actually be a small phone. I’d like to see something in the size of the Iphone 4S or so (3.5 inches IIRC).
I’d love a small phone, but this seems completely unrelated to what I’d want out of one. My ideal would be basically a Moto G (1st generation - 4.5 inches), but with modern-ish specs and better materials and official GrapheneOS (or minimally, LineageOS) support. I really don’t want an overpriced, slightly-smaller than typical flagship phone focused more on the camera than anything else. When I saw the title, I was thinking eInk screen, but I see that’s nowhere on the radar.
At this point I don’t even care about the hardware anymore if I am basically expecting that there will not be security updates for as long as I want to use the functioning hardware. That is true for all the Android phone manufacturers.
I think that companies are subject to SoC manufacturers here (except Apple/Samsung that build their own chips). You, as a manufacturer, buy the SoC from say Qualcomm and they only maintain Android builds of it for a set period of time - and then you (and your users) are screwed because Qualcomm of course doesn’t share specs with you so you can write your own kernel drivers for it.
I don’t see how that would be my problem as a customer.
Of course it’s in the company’s best interest to sell me a new phone after just 2 years but then they’ll lose me as a customer after that one phone. If the open source Android distros manage to get security updates for older devices shipped I fail to see how large companies would, except that they simply don’t care/deliberately don’t.
Once bitten twice shy with pebble.
I was excited for a bit, bit seems this won’t actually be a small phone. I’d like to see something in the size of the Iphone 4S or so (3.5 inches IIRC).
I’d love a small phone, but this seems completely unrelated to what I’d want out of one. My ideal would be basically a Moto G (1st generation - 4.5 inches), but with modern-ish specs and better materials and official GrapheneOS (or minimally, LineageOS) support. I really don’t want an overpriced, slightly-smaller than typical flagship phone focused more on the camera than anything else. When I saw the title, I was thinking eInk screen, but I see that’s nowhere on the radar.
Title might be toned down to something less clickbait-y and more related to the Small Android Phone project. Feel free to use the suggest feature.
It sounded pretty good until:
I would have thought the bare minimum would be 3 and surely it should be more like 5.