Slashdot Mirror
Google Launches First Android P Developer Preview (venturebeat.com)
Google today launched the first Android P developer preview, available for download now at developer.android.com. From a report: The preview includes an updated SDK with system images for the Pixel, Pixel XL, Pixel 2, Pixel 2 XL, and the official Android Emulator. Unlike last year, there is no emulator for testing Android Wear on Android P.
[...] Today's preview includes the following new APIs and features (but you can expect much more; this is just the first preview, after all): Display cutout support; HDR VP9 Video, HEIF image compression, and Media APIs; HEIF (heic) images encoding has been added to the platform; multi-camera API; ImageDecoder for bitmaps and drawables; Improved messaging notifications; Data cost sensitivity in JobScheduler; indoor positioning with Wi-Fi RTT: Platform support for the IEEE 802.11mc WiFi protocol -- also known as WiFi Round-Trip-Time (RTT) -- lets you take advantage of indoor positioning in your apps. Other features and their descriptions are listed here.
[...] Today's preview includes the following new APIs and features (but you can expect much more; this is just the first preview, after all): Display cutout support; HDR VP9 Video, HEIF image compression, and Media APIs; HEIF (heic) images encoding has been added to the platform; multi-camera API; ImageDecoder for bitmaps and drawables; Improved messaging notifications; Data cost sensitivity in JobScheduler; indoor positioning with Wi-Fi RTT: Platform support for the IEEE 802.11mc WiFi protocol -- also known as WiFi Round-Trip-Time (RTT) -- lets you take advantage of indoor positioning in your apps. Other features and their descriptions are listed here.
and if the follow up will be Android PP
Maybe P will fix the problems with O and N. If it's ever released for any of my devices that are more than 1 year old.
*closes browser*
Have they said what the code name will be yet? I would think Popsicle would be the obvious choice.
Where Apps can be downloaded and Rendered on the fly, using some sort of interpreted language, that is platform independent, with open specifications.
Where development can happen on any PC, and testing is primary about testing it on the given screen sizes.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
I'd love to try this out on my Nexus 6P (Fi), but looks like I may have to test it on my wife's Pixel. Which means I risk the Wrath of the Woman if I brick it.
It saddens me that Android, with its very advanced features, still doesn't have a straight forward way of letting users schedule an alarm for a future date as an inbuilt capability by default. This is a killer feature for me. I know I am not alone.
Trump approves. New android motto. Grab 'em by the Pussy.
Nothing at all wrong with that. Americans overwhelming agree. Elected a man president knowing this. Hail TRUMP!
I'm a huge Apple fan, have been all my computing life. But I think it instructional for developers (and consumers and fans!) to compare Google's communication style regarding new operating system features and Apple's, cough cough, "communication" style. Google is clear, outlines what features they've added and want to add, and their intent on development track. Apple... well...you get WWDC, and they show stuff, and they'll talk about some stuff, maybe. And maybe what they show and talk about ships, but good luck on getting more information about what is going on if it doesn't ship when planned. And even after that, don't plan on getting adequate, clear documentation; the best resource is the developer forums or Stack Exchange where you will get more (empirical) info from other developers than you do from Apple.
This is NOT how I thought things would go. [Luke was right. (Tell your sister, he was right.)]
Apple users, consumers, developers: we shouldn't stand for it. There –is– a better way. And Google shows it. Apple can pay lip service to the "evil" of Google, but at the end of the dev cycle, that's really all it is. And Apple can utter profundities about secrecy and the delight of surprise, but honestly it's all just nonsense after the "reveal". Apple...Tim Cook...up your game... it is beyond time to stop acting like it is 1997, or 2007.
Scott
"Hokey religions and ancient weapons are no match for a good blaster at your side, kid."
And even after that, don't plan on getting adequate, clear documentation
I'm not sure what your complaint about the Apple documentation is exactly but it's really good. The one area I think Apple could do better with is sample projects, which they do not always have for new or updated frameworks.
Also the WWDC sessions do a really good job of presenting how new features work and how you are supposed to develop for them.
It's true Apple is not necessarily as clear about where they are going, but they are very good at preparing you for new things beforehand by strongly suggesting you adopt certain technologies or tools...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
And Motorola still hasn't finished their rollout of Android O to Moto X4's
Where Apps can be downloaded and Rendered on the fly, using some sort of interpreted language, that is platform independent, with open specifications.
Where development can happen on any PC, and testing is primary about testing it on the given screen sizes.
Congratulations, you just described web development.
You know, the way apps worked on the iPhone at launch, before the public SDK came out?
Never was there such a loud clamor to move to native development... the problem is that developers will always be better able to make use of raw hardware than any abstraction people build for it. Heck, as it is even native development is ALREADY gated in a number of ways where you do not truly program "on the metal".
The closest thing to what you describe are probably the popular gaming engines.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Never owned an Apple device, and yet, I found myself envying anyone with an iThing, right now. Excellent phones like the Nexus 5/6x series (disclaimer: which I own) are going to be dropped by the new OS. Why? Probably, because they lack the newest AI chip to process buzzword at unprecedented speed. In the end, it really sucks to have only two choices: either being owned by the big, flaming Eye of Sauron that all sees, or being locked in the Golden Orchard.
The clock has moved from the far right to the far left people! ..and, colorful settings icons, awesomeness
Parfait.
Have you ever met a person, you say, "Let's get some parfait,"
they say, "Hell no, I don't like no parfait."? Parfaits are delicious!
Parfaits may be the most delicious thing on the whole damn planet!
Google's decision to not support Nexus devices with an OTA update is semi-understandable, but it would be really nice of them to AT LEAST continue with kernels, compatible binary kernel modules built for proprietary peripherals in Nexus devices, and updates to Google's own apps (esp. Play Services & Play store) for another 3 years. Why? Because they're the only ones who CAN make new binaries for Nexus devices. Qualcomm lets THEM have access to source & reference drivers the rest of us will never be allowed to touch directly.
In other words, after the end of formal support, there should bs an additional 3 year period where they do what only THEY ALONE can, so we can do the rest ourselves (vis-a-vis AOSP).
(background: Unlike Windows, Linux makes NO effort to maintain binary driver compatibility between kernels. If you have the source, it's easy to just recompile old drivers for the new Kernel. If you DON'T have the source, you're fucked. Recompiling isn't necessarily HARD... often, it can be mostly automated. But Google has the source... we don't, and never will. So only THEY can do this for us.)
A guerrilla war by angry Nexus owners to associate "P" with "Poop" (and alternate mascot featuring the Android logo with a poop-emoji hat) as revenge for force-obsoleting still-fairly-new hardware by breaking kernel binary drivers without an official solution.
A few hundred developers doing it in every related blog & forum post they make, and within days Google searches will either be suggesting "Android Poop", or Google will have to tamper with search results to suppress it & risk bad press when they're caught.
Think it can't work? Google "Santorum".
Never underestimate the kind of guerrilla negative public relations campaign developers can do. "Regular" people might sigh & move on. Developers will latch on & become OBSESSED with it for months. Hopefully, Google's management knows this AND how easily it could neutralize that anger simply by informally releasing new kernel binaries for Nexus devices.
Assuming my oneplus 3t has the standard Android alarm, I add a new alarm, choose the time, tap okay, tap the 3 dots that are on the line below the alarm time, on the right of the word "repeat" and can then select all days on the popup calendar where I want the alarm to sound at that time.
Perhaps that isn't straightforward enough for you, but I have trouble to imagine a simpler way, especially considering that setting alarms is generally an alarm clock or watch function, where the choice of weekday is the logical priority.
Or maybe oneplus has done something great here. Would surprise me, they've not done much of anything special in terms of software that I know of...
aRTee