Yes, that is kind of the case - as sites get heavier and heavier, it's harder for older devices to keep up. An old laptop that I keep around for travel (no camera, GNU/Linux) has a very hard time with modern websites. The Core2Duo fans just scream when you load something these days.
That's not too much of an issue, I rarely browse the internet on my phone, it's just not an enjoyable experience on a small screen. The changing protocol (GSM -> VoLTE) isn't something I can get around, however. Protocols change, oh well.
It is getting very hard to find used phones too, especially forward thinking and without updates. All these recycling programs take them out of circulation. And those that survive are susceptible to engineered killer software that is designed to work properly the allowed phone but will kill the old forward thoughtful phones. I used to have one such phone and it was killed by an app. Once the app killed it there was no fixing it. I tried everything short of sending back for repair. It needed a new charger chip or reprogramming the charging chip.
That's weird, it must have done a microcode update. The charger device is typically it's own little circuit.
What application did you install? I'd be interested in looking at that to see if I can figure out why.
I don't remember that now, it was a long time ago. But yes it something to the battery charging chip, either tried to add code or erased the chip. I can't even get it to stay on if I hotwire it. I might get it to stay on for 5 or 10 minutes. It was kick ass phone too.
To break compatibility, Twitter has and Google brought us enforced (non-optional) scoped storage cancer.
Twitter's API still allows you to return stuff without issues if you're so inclined. I use that to scrap the weather service feeds.
You could have said "Google is Cancer" and stopped.
Twitter's API, last time I checked, requires a key that needs to be requested. Their M2 mobile site just worked.
(post is archived)