Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Taking the final wrapper off of Android 7.0 Nougat

android-developers.blogspot.com

Post reply on HN
Print view View original

231–240 of 250 posts

Re: Taking the final wrapper off of Android 7.0 Nougat

#231

Post by jaxondu »

codedinosaur wrote: post #207
telesilla wrote: post #204

Earlier quoted context omitted.

Unfortunately this also forces me away from the Nexus family. I just can't handle the size of the Nexus 6 - being a fairly petite female a large phone is just unwieldy. I'm not sure the phone developers ever take physical size into consideration. If anyone can recommend a small replacement phone that supports running the original Android OS instead of a OEMified mess?

The Nexus 5x should be great for you. It's a 5-inch screen and may have a couple more years of new Android versions left in it. Or better yet, wait for the new Nexus phones set to be released this year. Should add another year of Android support from Google.

Nexus 5X is listed at Google support site ( https://support.google.com/nexus/answer/4457705#nexus_device... ) to have "No guaranteed Android version updates after September 2017". You might want to wait for the new Nexus according to rumours will release in September.

Re: Taking the final wrapper off of Android 7.0 Nougat

#232

Post by laingc »

adamors wrote: post #143
drusepth wrote: post #115

Earlier quoted context omitted.

iOS 9 runs hilariously badly on the iPhone 5.

It runs just fine on my iPhone 5 and it's my daily device.

Same for me, although there is some slowdown compared to iOS 7. I am extremely impressed with the longevity of Apple phones in general, and my 5 in particular.

Re: Taking the final wrapper off of Android 7.0 Nougat

#233

Post by Oletros »

Ologn wrote: post #151
Oletros wrote: post #34

Earlier quoted context omitted.

How is the split screen breaking the API when the app works like ever has worked in the main screen?

> the app works like ever has worked in the main screen If the app always works like it ever has worked in the main screen, why do they say: > If your app does not declare a fixed orientation, you should launch your app on a device running Android 7.0 or higher and attempt to put the app in split-screen mode. Verify that the user experience is acceptable when the app is forcibly resized.

To check if it is displayed fine in a split screen, nothing mire

Re: Taking the final wrapper off of Android 7.0 Nougat

#234

Post by Sylos »

int_19h wrote: post #57
qznc wrote: post #3

Personally, I don't care for any [0] of the new features. This is the greatest feature, because it means Android is mature now. [0] Sure, better performance is always nice, but I don't care for Vulkan, VR Mode, or Multi-Window.

There is one awesome new feature that is not mentioned on most "best new features" list: built-in night mode (blue light filter). Works much better than similar apps from the store - those work by placing a translucent overlay window on top of everything else, which gives everything (including black!) a reddish hue. The new built-in filter, on the other hand, just removes blue, and blacks remain black.

As in it's available without root? Because this has been available with root since KitKat, and there were also some apps which allowed you to use it...

Re: Taking the final wrapper off of Android 7.0 Nougat

#235

Post by infinityplus1 »

tdkl wrote: post #113
benzor wrote: post #41

Earlier quoted context omitted.

FWIW, I've deliberately kept my Nexus 5 on Android 4.4.4 and it runs as well as the first day I bought it 2.5 years ago. Multi-day battery life, no compatibility issues (because no OS updates), all the latest apps still run on it, etc. Not to mention it was an affordable phone even when it was brand new. Very happy with it overall; I can easily see it lasting me another few years.

Classic "don't fix it if it ain't broken". How have you manage to disable the System update annoyance ? Shitty Lollipop made me sell the Nexus 5 last year with its bad battery life and memory leak (and they still didn't fix the mobile radio wakelock), but when downgrading to 4.4 it was next to impossible to block the notification. I remember methods used at time just caused the Google Play Services to hold the wakelo…

Press and hold the notification, select App Info, disable notifications. That has worked for me very well.

Re: Taking the final wrapper off of Android 7.0 Nougat

#236

Post by faviouz »

JohnTHaller wrote: post #196
faviouz wrote: post #133

Earlier quoted context omitted.

Looks awesome, but no support for the Nexus 5 :(

Nexus 5 has a Snapdragon 800 with no 64-bit support. So, it's out. Same with the 805 in my Nexus 6. They're both kinda long in the tooth. The project supports the current (soon to be previous) generation of Nexus devices: 5x, 6p, 9.

I realized that quickly after I posted my comment.

Guess I'm gonna have to keep looking...

Re: Taking the final wrapper off of Android 7.0 Nougat

#237

Post by ktta »

vbezhenar wrote: post #206
ktta wrote: post #189

Earlier quoted context omitted.

depends on what your definition of 'fine' is. I also use an iPhone 4S with iOS 9, and looked at how fast iOS 9 runs on iPhone 6S and iOS 8 on a friend's iPhone 4S. I don't think I'd call it anywhere close to fine. I'm numb to the slow response times, but the crashing applications make me want to ditch this for a 50% cheaper android phone which runs faster, and doesn't have planned obsolescence[0] (the link talks abou…

I agree. Especially considering the fact that it's possible to revert to iOS 6 with iPhone 4S. That's what "fine" looks like. I don't want to blame Apple, but iOS works fantastically bad on old devices, and hard to impossible downgrade doesn't add much love either. I bought iPhone at the time because it was responsive and Android was laggy. Guess it's reversed now.

> fact that it's possible to revert to iOS 6 with iPhone 4S

wait, can I get some more info about this? I assumed to cannot go back to old releases. Or are you talking about jailbreaking?

> iOS works fantastically bad on old devices

that's understating it. I actually think my nokia (symbianOS) from almost decade ago is faster. And I mean it is faster even today!

Re: Taking the final wrapper off of Android 7.0 Nougat

#239

Post by kuschku »

gcr wrote: post #150
kuschku wrote: post #139

Earlier quoted context omitted.

Except when you try to ensure someone gets notifications while the phone is in an intranet. Or when you try to transmit notifications without going through Google/Apple servers, because those require you to control the messaging server (due to API auth limitations), which does not work with distributed systems. A messaging app that only works when the screen is on is useless.

Why not use Apple's servers to deliver a ping, and then the app checks with your own server what the content of the message should be? That way, you get realtime event notifications without the privacy risk of exposing content to Apple's servers.

To send any message to Apple’s push service, you need to have a certificate.

That same certificate can be used to replace your app on the store, or so on.

Basically, that is your one key to the kingdom.

So, I obviously can’t give everyone who hosts a server for the app that key.

So I have to host a server transmitting all those pings then.

Even ignoring the obvious DDoS risk, and assuming it’s only used in good ways, I end up with having to buy an entire additional server, just for that.

And I still leak metadata, which – as the NSA has shown – can be easily correlated with who is whom if you have enough data.

Re: Taking the final wrapper off of Android 7.0 Nougat

#240

Post by kuschku »

xorcist wrote: post #148
dragonwriter wrote: post #110

Earlier quoted context omitted.

> With Nougat, no background tasks will be run at all while the screen is off – except for Google services. Untrue. First, mobile Doze doesn't kick in immediately when the screen is off. Second, mobile Doze apparently doesn't stop all background tasks except "Google services" from running, since "wake locks" from apps for background tasks are still supported.

Is that true? Will my email client stop notifying me of new email? That doesn't sound appealing at all.

In most cases, notifications might be delayed by several hours, yes.

Or never happen at all.

Or just work normally.

Depending on when the heuristics think you are less likely to use your phone.

There is one way to keep getting notifications, by using proprietary Google services, and sending a ping from your server via Google to the device, or sending the actual notification that way.

Which, for email, means either everyone who does that has to build every app themselves from source, or you have to send that data to a third party server which then sends it to Google

Post reply on HN