Android 8.0????

[ansa82]

I keep thinking it will be any day now...waiting waiting lol

 

[talon1189]

Nothing about Oreo from AT&T either.

 

[Mooncatt]

Once again Verizon will be last.....

When it first came out, Verizon was always the first with V20 updates. I'm ok bout getting Oreo, though.

 

[Mike Dee]

Once again Verizon will be last.....

They should just go straight to 9

 

[dawghowse]

I agree but can't imagine how long that would take.

 

[Mike Dee]

I agree but can't imagine how long that would take.

That's what they should have done....they could have waited just a bit longer at this point and saved the cost of skinning 8.

 

[talon1189]

Oreo has been out about a year now? It should be near bug free by the time we get it

 

[Mooncatt]

Oreo has been out about a year now? It should be near bug free by the time we get it

Let me introduce you to the term "persistent beta." Nothing is ever bug free anymore. Lol

 

[Mike Dee]

Oreo has been out about a year now? It should be near bug free by the time we get it

What's left aren't bugs.... they're features.

 

[stackberry369]

Let me introduce you to the term "persistent beta." Nothing is ever bug free anymore. Lol

Even humans aren't bug free

 

[Mooncatt]

Even humans aren't bug free

Nor should we. Many bugs are beneficial.

 

[Mike Dee]

Nor should we. Many bugs are beneficial.

This conversation is starting to bug me.

 

[Bildriver]

After a cpl. of weeks of oreo. Pretty much got it figured out. Most impressed w/battery life. It's been excellent. Thanks

 

[tickerguy]

Biggest improvement in Oreo is the automatic demotion of processes when the phone goes into deep sleep. An app that wants to get around this has to intentionally do so and in a way you can detect and shut down (e.g. making itself exempt from battery management, which it must ASK FOR and can't force.) Same deal with notifications; the app must register for them and you can shut them off even if the app writer doesn't want you to (which lets you stop the app from spamming you with them.)

There are a LOT of crappy app-writers -- even among "big name" apps.

I have an Android app that runs my Home Control software (HomeDaemon-MCP); it's not in the store, but it required a bit of work to run on Oreo without being molested by these new features.

 

[gipper69]

Bad idea for the short run for anyone using the device with their corporate apps. Pie is not certified, and premature upgrade will render those apps non-functional.

 

[flyingkytez]

Biggest improvement in Oreo is the automatic demotion of processes when the phone goes into deep sleep. An app that wants to get around this has to intentionally do so and in a way you can detect and shut down (e.g. making itself exempt from battery management, which it must ASK FOR and can't force.) Same deal with notifications; the app must register for them and you can shut them off even if the app writer doesn't want you to (which lets you stop the app from spamming you with them.)

There are a LOT of crappy app-writers -- even among "big name" apps.

I have an Android app that runs my Home Control software (HomeDaemon-MCP); it's not in the store, but it required a bit of work to run on Oreo without being molested by these new features.

I thought that was already a feature in Nougat? Doze Mode? I guess this will completely force apps to freeze and hibernate, such as Facebook and FB messenger which somehow bypasses the hibernation and force push updates regardless of battery saving measures...

 

[tickerguy]

I thought that was already a feature in Nougat? Doze Mode? I guess this will completely force apps to freeze and hibernate, such as Facebook and FB messenger which somehow bypasses the hibernation and force push updates regardless of battery saving measures...

Exactly -- an app that wishes to override the system's classification used to be able to "just do it"; it can't do that in Oreo and beyond. It can try to stick a foreground service (for example) but unless you authorize it specifically to do so even though it would otherwise post a notification it still can't make the service "stick." In addition even repeating alarms (which used to reliably allow an intent to be sent and thus an app to be "woken" or "activated") will be deferred despite the app's attempt to make it otherwise, UNLESS you specifically exempt the app from battery management.

Further there are rules for Oreo-and-beyond for when you can include that privilege in the manifest (allowing the app to request it from the user in the first place) and if you submit an app that has that privilege in the manifest you have to justify why it's there. If what the app wants to do CAN be served by FCM (see below) it MUST use FCM, or Google won't approve it.

The exception is that an app can register for what is called "Firebase" (FCM) which is a cloud-based notification system, and that goes through the system itself. However, high priority notifications (which can wake the device out of doze), if abused, now become something Google can detect since ALL such notifications go through their systems and they have fairly explicit developer rules on when it's legit to use those (e.g. for delivery of instant messages) and when it's not (e.g. other sorts of content, for the most part.)

Same deal with notifications -- an app HAS TO register a channel to post them (if it doesn't then NOTHING goes through!) and once it does YOU have control over whether they are delivered, if vibrate works, if sound works, etc -- and the app CANNOT change it back. All it can do is send you to the system's app notification page (where you can make the changes) but it can't force them -- if you turn 'em off then they're off, period. An app can register multiple notification channels if it has multiple "types" or "classifications" of things to notify you about, but in any event you can always modify or shut it off and the app writer cannot override what you've done.

 

[stackberry369]

This conversation is starting to bug me.

Get a can of Raid lol