571–580 of 658 posts
Earlier quoted context omitted.
> It's the same reason animals age and die. With the difference that younger (newer) animals are better built. :-)
I think most 50+ would disagree on this point... :-)
Earlier quoted context omitted.
Nokia had firmware updates, but only technically savy people would do them. It was done via the desktop application to manage the phone. However one would ususally only get bug fixes on the Series 30 and 40. On Symbian towards the end of it, there were some OS updates still, but usually only once.
By the time iPhone hit, Nokia were doing over the air updating on their more recent models. And Nokia was not alone, my Sony Ericsson C702 were capable of being getting new firmware OTA as well. Keep in mind that this was back with the original iPhone that needed to be wired to a computer with iTunes installed. Frankly the iPhone introduction feels more of a rollback than a upgrade from non-American point of view.
Belle already had lots of features that took Android and iPhone years to catch up with.
I know this is a non-issue for many, but those emojis look really dated. Every update they get harder and harder to read in small form. One of the things I observe, mainly on Instagram Stories is only people with iOS post with emojis attached, I never see Android ones. Too bad there is no way to install custom emojis in any system (without rooting/registry tweaking), like we do with fonts.
I absolutely hate those emoji. It's the gradient and outlines, it looks like bad enterprise design. The flat blobs were great.
Earlier quoted context omitted.
Why is that not a good experience? Now I need to dig through Settings to find all these background services. If they're important enough to be running constantly they're important enough to take up some space to prominently show me that they're running.
Yes, and you're okay with having 20 to 30 notifications at all times just to run open source apps, or would you say "this is too annoying, I'll switch back to the closed ones that spy on me". If you want the open source products to win, they need to be able to provide the same usability as the proprietary solution. This is not possible here - you need Google's FCM or you get major disadvantages, and this is problemat…
If I install 100 apps that have their own messaging implementation should the phone just not be showing that to me, even though my battery is now drained in half the time as a result? I'm pointing out that as a user this is very pertinent info to be showing me, if I have 30 apps running in the background I'd like to see it.
Earlier quoted context omitted.
Yes, and you're okay with having 20 to 30 notifications at all times just to run open source apps, or would you say "this is too annoying, I'll switch back to the closed ones that spy on me". If you want the open source products to win, they need to be able to provide the same usability as the proprietary solution. This is not possible here - you need Google's FCM or you get major disadvantages, and this is problemat…
This doesn't inherently have anything to do with open source, but the problem that whatever license the apps on the phone are under they can't all be implementing their own push/pull message queue, having 30 open network connections constantly waking up the phone is going to drain the battery. If I install 100 apps that have their own messaging implementation should the phone just not be showing that to me, even thou…
I implemented a prototype before, where I had a standardized protocol, and apps give the GCM library (I modified microG’s) a URL to connect to, and an auth token.
microG’s GCM library would keep all those sockets open, just as it does with the sockets for Google’s several cloud messaging services, and upon receiving a message, wake up the app.
As result, only one app runs in background, every app can use its own notification service, you have no battery loss, and you can keep everything open.
All this can work. Google just doesn’t want it to.
Earlier quoted context omitted.
The issue: apps that are only updated with the OS end up outdated. The current solution: Move them out of AOSP, into Google's internal projects, distribute updates via the Play Store. An alternative solution: Move them out of AOSP, onto GitHub, distribute updates via the Play Store. Yes, Google had to decouple them from AOSP. But that’s no reason not to put the code anywhere else in the open. These issues are entirel…
Open sourcing Google's apps is not a solution to Android's core problems though. Not every part of the OS that needs to be updated can be moved into open sourced apps. Also, open sourcing the apps takes away any leverage Google has to recoup the costs of developing Android.
This all worked in the past.
Earlier quoted context omitted.
Open sourcing Google's apps is not a solution to Android's core problems though. Not every part of the OS that needs to be updated can be moved into open sourced apps. Also, open sourcing the apps takes away any leverage Google has to recoup the costs of developing Android.
All the apps were open source in the first place. Google Music, Books, Search, the Phone Dialer, the contacts, the SMS app, Google Talk, all of them used to be open source. This all worked in the past.
Earlier quoted context omitted.
By the time iPhone hit, Nokia were doing over the air updating on their more recent models. And Nokia was not alone, my Sony Ericsson C702 were capable of being getting new firmware OTA as well. Keep in mind that this was back with the original iPhone that needed to be wired to a computer with iTunes installed. Frankly the iPhone introduction feels more of a rollback than a upgrade from non-American point of view.
I only started using around Android 2.3 time frame, because I held to my trusty Symbian until it died on me, by then Nokia was already showing signs of not being sure what to do after Belle. Belle already had lots of features that took Android and iPhone years to catch up with.
they had Maemo, they had Symbian. But they were afraid that focusing on Maemo would lead to Symbian dying before they could get Maemo to the same level.
And then boardroom meddling was added, and they went much the same way as HP...
Earlier quoted context omitted.
Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users If HN allowed emoji in comments, I'd have a U+1F923 here. Since I can't do that, you're adorable. The users, eh? The users are supposed to be burdened with checking the wake status and radio activation schedule of their apps? How was that supposed to work, exactly?
I'm not sure what your point is here and your tone indicates you're not really looking for honest discussion. But FYI Android reports energy usage statistics to the user on a per-app basis. What I don't like is Android the platform telling me the user how my phone is best used. It's pretty crippling. Let's say I'm deploying Android on hardware that is always plugged in--something kiosk-style. Why shouldn't I be able…
My Android phone still randomly lights up its screen several times a day, without a new notification having come in. Reporting overall energy usage doesn't help me track down the culprit.
It's not like anyone's written apps for real work on these devices anyway. It's all just second class software.