Live data from Hacker News

Android Oreo

android.com

461–470 of 658 posts

Re: Android Oreo

#461
post #108

The most interesting part is the way they are planning on tackling fragmentation in O onwards with Project Treble [0] If your device ships with O it should be running an immutable semantically versioned HAL. In essence you should be able to be able to flash AOSP on every new device. No matter what the vendor does. Edit: I can see it now, in the technical specs of each device you will see a list of HAL Versions. The n…

As someone who knows nothing about this, I wonder (and hope) if this is helpful for UBPorts/Halium.

https://ubports.com/ https://halium.org/

Re: Android Oreo

#462
post #377
post #347

Earlier quoted context omitted.

Google Now is malware that can't be removed and is constantly showing you ads and spying on your behavior (look at the app integrations menu). The best you can do is go through the disable-athon menu, but that only works until the next update. It's an impressive bit of technology though, I've never seen an app so good at telling me exactly what I didn't care about, exactly 10 minutes after I would have cared about it…

Now is optional. I've never used it.

If it can't be deleted then it's not optional. Even disabling it is obfuscated behind signing out, but I don't know if it still sends data to google or not.

Re: Android Oreo

#463

Earlier quoted context omitted.

huh .. I always suspected Fuchsia/Magenta were going to be a basis for Android going forward to get around the fragmentation situation. They still could be in the future, since no one is really sure what they're being developed for.

i haven't read up on fuchsia/magenta too much yet, but my impression is that it's going to be a much larger shift in general. If Google can take some less drastic strides to fix this problem before a huge change like fuchsia, theres probably a better chance for an easy(er) transition.

There cannot exist an easy transition because they are completely different,

Java/Kotlin/C++ vs Dart for user space, Linux vs Magenta for the kernel and drivers.

Re: Android Oreo

#464

Earlier quoted context omitted.

Can you replace the battery with an extended one? That's a deal-breaker for me, and battery cases are not a good replacement since I can't rely on the phone's own battery indicator, have to manually turn on/off and looking at ZeroLemon's case for the S7, it seems to require a headphone extender. As for the S3's screen I have no complaints. It's readable in the sun with max brightness, I keep it at minimum the rest of…

I'm using an S7 edge and it's on the default 1080p resolution. It's not blurry at all. The difference in quality between this screen and the screen on S3 is very noticeable. The non removable battery is the only downgrade I see. Everything else is a huge leap forward. Even battery life is much much better. You likely would not need an external battery.

I'd have to see it for myself. My 4k laptop makes me gouge my eyes out in 1080p mode.

As for the battery life you mention, that's probably just the Android upgrade. I've easily doubled my battery life in 3 major Android version upgrades. 10-15 days (depending on usage) is normal now with a 7000mAh battery.

Re: Android Oreo

#465
post #308
post #287

Earlier quoted context omitted.

Can you point me to the relevant info? This is news to me (and sounds exciting). No doubt we've seen it coming for awhile. But I'm still sad to see it finally come to this, at least ideologically. iOS is a closed ecosystem that's been opening up. Android was an open ecosystem that's becoming more locked down.

[1] Seems to do the trick but I don't do Android dev so I don't know any details about this. [1] https://github.com/siacs/Conversations/blob/2b9cdde558ed96c2...

I looked into this. It seems this is something that was added in M pertaining to Doze and App Stanby modes and is not related to the new O background execution limits (which apply generally). In any event, app exemptions must be approved by Google so we've already crossed the open platform line. They do list that voip-style/message apps will receive approval if they can't use FCM for some technical reason: https://developer.android.com/training/monitoring-device-sta...

Re: Android Oreo

#466
post #343

Earlier quoted context omitted.

That actually got some decent cheers at Google I/O iirc, it's bigger than it sounds at first. It's scaling the font size of the text to fit the available space, which is a fairly unique twist and is great for localization efforts (looking at you, German...)

Don't get me wrong, the feature itself is indeed useful. It's just that its so.. minor. If you ever wanted to implement this in your app then there are multiple ready-made solutions for this or you could write your own in a short amount of time. Presenting this as one of the key new features in a major new OS versions seems just strange.. like there wasn't anything else substantial.

Not only that but would non Android developers even understand the feature?

Re: Android Oreo

#467
post #108

The most interesting part is the way they are planning on tackling fragmentation in O onwards with Project Treble [0] If your device ships with O it should be running an immutable semantically versioned HAL. In essence you should be able to be able to flash AOSP on every new device. No matter what the vendor does. Edit: I can see it now, in the technical specs of each device you will see a list of HAL Versions. The n…

Android have been promising to finally tackle fragmentation in every release since KitKat. It seems people have a very short memory.

Functional planned obsolescence. Hardware vendors will find a way to break hardware abstraction layers... so they can sell more hardware. Its the business model.

Re: Android Oreo

#468
post #405

Earlier quoted context omitted.

Do you have any facts to back this up? Prior to the iPhone changing how phones were sold-- carriers meddled with everything so they could get their hands in media playback, app sales, feature upgrades etc. I don't think much has changed in this where anyone gives them an inch (which is nearly everyone but Apple). Note: I worked for T-Mobile for four years prior and a little after the originals iphone came out.

Before the iPhone, how prevalent were software updates to phones? I know of no one who ever got had an update. There is absolutely no reason for carriers to need to do anything at all, else it would not make sense that I can change the SIM card out and voila I’m on a new carrier. The manufacturer is the one doing the testing, and the carrier simply provides the infrastructure. I feel US perhaps has a different experi…

Sony Ericsson's non-smart phones (e.g. K800) had OTA software updates. They would pop up a dialog from time to remind you to check for updates, then download them and update, all on the phone. (Carriers would often hold them back, though, if you had a carrier-customized model.)

I'm pretty sure I got an actual update at least once.

Re: Android Oreo

#470

Earlier quoted context omitted.

I’m fine with receiving years and years of security updates. I paid for the features I got. Anything new is a bonus. But an up to date secure OS is non-negotiable.

If it's non-negotiable for you, you have a choice: Google phones or Apple phones. Everything else is out, unless you want to try your luck with stuff like LineageOS and hope that they support your device for whatever timeframe you consider reasonable.

Well I don't consider Google's collection of my data to be a secure practice from the standpoint of my privacy. So the one remaining option is Apple.
Post reply on HN