Android M Developer Preview and Tools • Hacker News Board

Re: Android M Developer Preview and Tools

#51

Post by higherpurpose » Thu, May 28, 2015, 9:33 PM UTC

ignoramous wrote: post #38

IMO, the most game changing feature announced today is 'Now on tap' Google isn't releasing more details on it, but with it, Google would be able to understand what you do, when you do it, who your pals are, who you go out to movies with, who you chat with the most, are you looking to quit your job, are you about to break up, are you going through a depression and so on... They haven't revealed anything about how exac…

> Google would be able to understand what you do, when you do it, who your pals are, who you go out to movies with, who you chat with the most, are you looking to quit your job, are you about to break up, are you going through a depression and so on...

Sounds a lot like the NSA.

Re: Android M Developer Preview and Tools

#52

Post by vardump » Thu, May 28, 2015, 9:43 PM UTC

27182818284 wrote: post #28

Google is showing off Android M dev previews while devices sold new last fall in major US retailers are still running KitKat with no updates from Google or their providers. They continue to actively create the "fractured" world of Android. In other words, that's cool about Android M, but most people aren't even using L. (40% on K, 9% on L whose preview was the 2014 IO) Can Google not poach one or two of Apple's negot…

> Can Google not poach one or two of Apple's negotiators to go to the right meetings at Motorola, Verizon, etc to talk about updates?

I don't understand why things like these are necessary in the USA. Why should network operator have control to which version you're running? Most other places you can just get new firmware directly from manufacturer.

Re: Android M Developer Preview and Tools

#53

Post by hadrien01 » Thu, May 28, 2015, 9:48 PM UTC

> Android Design Support Library - Making Material design apps gets even easier with the new Android Design support library. We have packaged a set a key design components (e.g floating action button, snackbar, navigation view, motion enabled Toolbars) [...]

Finally! I had to start developing for Android not too long ago, and I couldn't stand seeing "mandatory" material components for certain usages that weren't supported in the official SDK.

Re: Android M Developer Preview and Tools

#54

Post by kllrnohj » Thu, May 28, 2015, 9:50 PM UTC

27182818284 wrote: post #28

Google is showing off Android M dev previews while devices sold new last fall in major US retailers are still running KitKat with no updates from Google or their providers. They continue to actively create the "fractured" world of Android. In other words, that's cool about Android M, but most people aren't even using L. (40% on K, 9% on L whose preview was the 2014 IO) Can Google not poach one or two of Apple's negot…

Your post was word for word identical to posts made 2 years about KitKat when it was released. Only instead being compared against Gingerbread. And several years before THAT when Gingerbread was released people were saying it about Donut & Eclair.

So yes you'll have to wait ~2 years for the majority to be on M or higher. Oh well. Does that suck? Yeah. Is it a major, show stopping, "omg google why haven't you devoted 100% resources to fixing this?" issue? No, that's absurd.

And why do you think Apple has negotiators for this? Apple doesn't license iOS to anyone. They've never attempted to solve this problem. Ever. For anything.

Re: Android M Developer Preview and Tools

#55

Post by vardump » Thu, May 28, 2015, 9:51 PM UTC

rentnorove wrote: post #49

calvin_c wrote: post #42

Earlier quoted context omitted.

They've actually set the number of permission groups to 8. But at least you can accept/decline each individually. EDIT: The permission groups are Location Camera Microphone Contacts Phone SMS Calendar Sensor

Conspicuously absent: - Read external storage - Internet

Can't agree more. It always bothers me all apps can access my external storage by default.

But I have to use Android, because it's the most open established mobile ecosystem. Only system that supports the mobile web browser I find tolerable to use for instance (hint - it's not the default browser or Chrome). Only system that allows developers to map executable pages. Only system that allows me to customize user experience as I see fit, and not offer one size fits all. And so on.

Re: Android M Developer Preview and Tools

#56

Post by Sargos » Thu, May 28, 2015, 9:52 PM UTC

Roritharr wrote: post #39

ignoramous wrote: post #38

IMO, the most game changing feature announced today is 'Now on tap' Google isn't releasing more details on it, but with it, Google would be able to understand what you do, when you do it, who your pals are, who you go out to movies with, who you chat with the most, are you looking to quit your job, are you about to break up, are you going through a depression and so on... They haven't revealed anything about how exac…

What scared me about that announcement was that "no changes in the app are necessary" which basically means that google from now on will parse the text that is displayed, regardless of the type of app that is open. Without any further clarification i have to expect Google now to send the displayed data of my mobile banking app to its servers everytime i hit that "Now on Tap" button, accidentally or not, while its ope…

This only works if the developer uses app indexing where Google can search through the content and make it searchable to end users and other endpoints. It doesn't come for free so Google has no access to things like your bank app's screen.

Re: Android M Developer Preview and Tools

#57

Post by digi_owl » Thu, May 28, 2015, 9:53 PM UTC

e40 wrote: post #48

calvin_c wrote: post #42

Earlier quoted context omitted.

They've actually set the number of permission groups to 8. But at least you can accept/decline each individually. EDIT: The permission groups are Location Camera Microphone Contacts Phone SMS Calendar Sensor

What I see missing, that Xposed + App Ops gives me is the "Keep Awake"... having revoked this permission from almost all non-Google apps, my battery life is a full 50% longer than other people with my phone report.

Best i can tell, Doze is supposed to cover that automatically. But then Doze will wake the device up if a GCM priority notification comes down the wire. And i expect Facebook and the rest to start spamming those to make sure they get every nanosecond of your life to their servers.

Re: Android M Developer Preview and Tools

#58

Post by CountSessine » Thu, May 28, 2015, 9:53 PM UTC

vardump wrote: post #52

27182818284 wrote: post #28

Google is showing off Android M dev previews while devices sold new last fall in major US retailers are still running KitKat with no updates from Google or their providers. They continue to actively create the "fractured" world of Android. In other words, that's cool about Android M, but most people aren't even using L. (40% on K, 9% on L whose preview was the 2014 IO) Can Google not poach one or two of Apple's negot…

> Can Google not poach one or two of Apple's negotiators to go to the right meetings at Motorola, Verizon, etc to talk about updates? I don't understand why things like these are necessary in the USA. Why should network operator have control to which version you're running? Most other places you can just get new firmware directly from manufacturer.

I don't understand it either. How should the carrier have any say/input into when the firmware on these phones is updated?

Re: Android M Developer Preview and Tools

#59

Post by kllrnohj » Thu, May 28, 2015, 9:54 PM UTC

heyheyhey wrote: post #11

> Battery - We’re making Android devices smarter about managing power through a new feature called Doze. With M, Android uses significant motion detection to learn if a device has been left unattended for a while. In this state, Android will exponentially back off background activity, trading off a little bit of app freshness for longer battery life. Will this improve wakelock performance that has been plaguing Andro…

Wakelocks have just been a scapegoat for people to pretend to sound smart when just saying that they want better battery life. They haven't actually been an issue for years.

No, this won't magically fix bugs in apps that lead to poor battery life. If an app opens the camera and forgets to close it, yeah that's gonna murder your battery.

Re: Android M Developer Preview and Tools

#60

Post by Aldo_MX » Thu, May 28, 2015, 9:54 PM UTC

rentnorove wrote: post #49

calvin_c wrote: post #42

Earlier quoted context omitted.

They've actually set the number of permission groups to 8. But at least you can accept/decline each individually. EDIT: The permission groups are Location Camera Microphone Contacts Phone SMS Calendar Sensor

Conspicuously absent: - Read external storage - Internet

  Application YourTypicalMobileApplication is asking for access to the Internet
  to display advertisements powered by Google AdMob.

                                                             [ D̶E̶N̶Y̶ ] [ ALLOW ]

  (Do you think we would give you the option to easily cut our income?)