|
mod sassinator posted:Regardless I still think it's a crap user experience to waste time with this stuff in the foreground. If optimization from the very start is so darn important, why doesn't Google cache the precompiled binaries for important devices (like the Nexus devices they build!) in their cloud and just download precompiled binaries from the start? The precompiling takes all processing power your device has (that's why they heat up quite a lot during it). You wouldn't like the user experience while the device is basically running at 100 % with a background process. So you're force to wait a few minutes to half an hour (if you have 200+ Apps installed like me), which seems fine to me - but I simply take another device or do something else instead of waiting for it to finish because I'm not glued to my device or get withdrawal symptoms if I don't have a screen in my hand for 10 minutes. Pre-Compiling for a fictional device wouldn't work and cause more problems than it solves. Apple controls a lot tighter than Google what their device are/make sure the system is the same on every one and even they can't do it without doing it on the device itself. Decius fucked around with this message at 07:27 on Dec 11, 2014 |
# ? Dec 11, 2014 07:23 |
|
|
# ? May 26, 2024 16:11 |
|
Why wouldn't downloading precompiled and optimized apps works? It's pretty crazy to think how many millions of Android devices are spinning away wasting power to do the exact same precompilation. Google already has to store every single app in their app store, it's not insane to make copies of the binaries that are precompiled for the most popular architectures and devices. They have hundreds of petabytes of storage for their web crawling, etc. I would bet the total size of everything in the Android app store is on the order of tens of terrabytes at most. Adding a few copies of binaries would be a rounding error.
|
# ? Dec 11, 2014 08:07 |
|
Maybe they'll worry about it when the number of devices using ART is more than a tenth of a percent. Or maybe they can worry about it when they fix things that we use daily instead of something that already works properly and takes a few extra minutes a few times a year.
|
# ? Dec 11, 2014 15:34 |
|
Before Android had to recompile ART binaries, it had to optimize dexes. Windows updates need to "configure updates" after a reboot. Even on Linux, after the new packages are installed the package manager does reconfiguration and cleanup. System updates take some time, always, on every device and on every operating system.Decius posted:I simply take another device or do something else instead of waiting for it to finish because I'm not glued to my device or get withdrawal symptoms if I don't have a screen in my hand for 10 minutes.
|
# ? Dec 11, 2014 16:01 |
|
You guys don't get it. When I turn on my tablet, I'm not using a device, I'm having an experience. And that experience is ruined if I have to wait 5 minutes for some files recompiling after an update. My experience is ruined!
|
# ? Dec 11, 2014 20:15 |
|
Guys I have to put down my tablet and browse on my phone for 5 minutes. Stupid Android.
|
# ? Dec 11, 2014 20:20 |
|
SpaceGoatFarts posted:You guys don't get it. When I turn on my tablet, I'm not using a device, I'm having an experience. And that experience is ruined if I have to wait 5 minutes for some files recompiling after an update. My experience is ruined!
|
# ? Dec 11, 2014 20:25 |
|
Put it this way, if you had the choice between two tablets that were exactly the same but one that took an hour to update every few weeks (these are 0.0.x releases that are requiring full recompilation!) or one that never bitched about updates and made it all happen in the background silently (like Chrome, CoreOS, etc.) which one would you choose? Of course you'd go for the better experience. This is purely a technical issue, one that Google claims to be amazing at solving with its cadre of 'rockstar' engineers. The fact that I ever have to see or be aware of an update (beyond stuff like giving an approval for new functionality that requires new access) is a bug IMHO. In ~5 years I guarantee none of the major mobile devices will make updates something people can even control or stop.
|
# ? Dec 11, 2014 20:55 |
|
It's a god drat update it's going to take some time jesus gently caress. The Nexus 5 has been out for a year and has had 5 updates so even if it takes an hour to update (it doesn't) it's only once every 10 weeks. When I updated my Nexus 7 to 5.0.1 I went and made a sandwich and when I came back it was done.
|
# ? Dec 11, 2014 21:02 |
|
butt dickus posted:It's a god drat update it's going to take some time jesus gently caress.
|
# ? Dec 11, 2014 21:05 |
|
It's not any fun if I can't be mad about it.
|
# ? Dec 11, 2014 21:12 |
|
In any case, suppose you're a program manager on the Android project. There is an endless litany of Android bugs and feature requirements that cost users' time on a daily basis. There's also this thing where every 10 weeks on average people have to wait a few minutes for an update, and a few more minutes for ART to chew on their apps. When it comes to scheduling engineers' time, which is going to take precedence?
|
# ? Dec 11, 2014 21:14 |
|
One thing to note is your tablet IS continually updating in the background, silently, without you knowing about it. That's the Google Play Services update and more functionality is coming from those updates week to week than any forklift OS version update.
|
# ? Dec 11, 2014 21:15 |
|
OS updates do not come out every few weeks. Like most of this thread, I've had Nexus devices for about as long as there has been Nexus devices. Having a 5 minute "reboot for updates" every 3-4 months does not ruin the appeal of an instant-on device. I'm almost afraid to find out everyone's opinion on app updates.
|
# ? Dec 11, 2014 21:16 |
|
With the slight exception of the project manager, I'm not sure why it's so hard to just ignore the update until you're ready to put the thing away for awhile *then* hit the update button. Certainly for 0.0.1 updates, it's never going to be anything that will completely change your experience.
|
# ? Dec 11, 2014 21:23 |
|
mod sassinator posted:Why wouldn't downloading precompiled and optimized apps works? There's also a real risk of this breaking if the AOT compiler is different, and incompatible, on device as compared to what Google uses for the store binaries. Not sure about ART, but in Dalvik days there were sometimes non-trivial changes to Dalvik made by SoC vendors compared to what Google released in AOSP. Not that this is intractable, but it's a risk they'd have to accomodate. So, basically, there's challenges in doing it. Of course, it can be done and maybe they will someday. Also sideloaded apps would still have to be updated on device, hopefully that's not the majority of everyone's apps.
|
# ? Dec 11, 2014 21:36 |
|
pairofdimes posted:You'd think the origami cover would be the easier one to produce, so something really must have gone wrong with the entire batch. The Origami cover is now available for purchase on the HTC Nexus 9 website. Scroll down to accessories (third dot on their goofy Web 2.0 navigator thing on the right) and click on "soft shell case".
|
# ? Dec 12, 2014 20:00 |
|
Rastor posted:The Origami cover is now available for purchase on the HTC Nexus 9 website. Cool, hopefully play and amazon get theirs soon.
|
# ? Dec 12, 2014 20:07 |
|
Rastor posted:The Origami cover is now available for purchase on the HTC Nexus 9 website. Wow, they'll sell a bunch of those since they've basically hidden it.
|
# ? Dec 12, 2014 20:31 |
|
Rastor posted:The Origami cover is now available for purchase on the HTC Nexus 9 website. Yeah, but only the red/pink one is available.
|
# ? Dec 12, 2014 20:34 |
|
So, uh, i still don't have Android L on my Nexus 7 - 2013... what percentage of users should have the update by now?
|
# ? Dec 12, 2014 21:23 |
|
Mister Fister posted:So, uh, i still don't have Android L on my Nexus 7 - 2013... what percentage of users should have the update by now? Do you have the LTE model? Mine doesn't have the update either and the LTE one usually takes a while.
|
# ? Dec 12, 2014 21:35 |
|
Geektox posted:Do you have the LTE model? Mine doesn't have the update either and the LTE one usually takes a while.
|
# ? Dec 12, 2014 21:43 |
|
Geektox posted:Do you have the LTE model? Mine doesn't have the update either and the LTE one usually takes a while. I have the non-LTE version, it's my understanding that the rollout takes a while and it's a random thing if you get it or not, but i would have thought most people have gotten it by now. Oh well. I was just wondering if there's a table as to what percentage of people should have it by now.
|
# ? Dec 12, 2014 21:54 |
|
Mister Fister posted:I have the non-LTE version, it's my understanding that the rollout takes a while and it's a random thing if you get it or not, but i would have thought most people have gotten it by now. Oh well. I was just wondering if there's a table as to what percentage of people should have it by now. I just got mine on Monday or Tuesday and my dad got his the day after so it's definitely still rolling out.
|
# ? Dec 12, 2014 22:01 |
|
Mister Fister posted:So, uh, i still don't have Android L on my Nexus 7 - 2013... what percentage of users should have the update by now? Maybe a slight delay to just go straight to 5.0.1?
|
# ? Dec 12, 2014 22:12 |
|
Mister Fister posted:So, uh, i still don't have Android L on my Nexus 7 - 2013... what percentage of users should have the update by now? I sideloaded the OTA as soon as it became available (because I am impatient). Anyway skipping 5.0 wasn't necessarily a bad thing because it was all kinds of broken on the N7. 5.0.1 performs much, much better on that device.
|
# ? Dec 12, 2014 23:47 |
|
The Merkinman posted:Maybe a slight delay to just go straight to 5.0.1? I had to the update on my N7 2013 for the last few days. I tried updating but it got a fun error message so still waiting to see if Google will fix it before the NYE. IIRC users have been exp a uncommon number of problems so I don't think you're missing out on much.
|
# ? Dec 13, 2014 00:31 |
|
So apparently the LTE modem in the Nexus 9 is a bolt on radio, not one intergrated into the chipset, I wonder what kind of blow that is going to take to battery life.
|
# ? Dec 13, 2014 00:53 |
|
TraderStav posted:I'm constantly having touchscreen issues on both KitKat and Lollipop on my '13 N7. Pretty sure it's a well known issue in the hardware. Yeah, it's some kind of grounding issue on the Nexus 7 2013 where the screen just goes absolutely loving nuts sometimes and thinks you're pressing when you're not. Makes drawing things with it hard. :/
|
# ? Dec 13, 2014 04:17 |
|
Three Olives posted:So apparently the LTE modem in the Nexus 9 is a bolt on radio, not one intergrated into the chipset, I wonder what kind of blow that is going to take to battery life. NVIDIA strikes again.
|
# ? Dec 13, 2014 05:57 |
|
Three Olives posted:So apparently the LTE modem in the Nexus 9 is a bolt on radio, not one intergrated into the chipset, I wonder what kind of blow that is going to take to battery life. I don't understand why it is so hard for two of the biggest chip tech companies - Nvidia and Intel - to integrate a loving LTE-modem on their chips. Intel took 5 years until they finally managed it.
|
# ? Dec 13, 2014 08:47 |
|
Decius posted:I don't understand why it is so hard for two of the biggest chip tech companies - Nvidia and Intel - to integrate a loving LTE-modem on their chips. Intel took 5 years until they finally managed it. I'd imagine its a patent nightmare. Even with FRAND licensing for essential patents its probably a hassle.
|
# ? Dec 13, 2014 13:34 |
|
.
maskenfreiheit fucked around with this message at 21:42 on Apr 28, 2019 |
# ? Dec 13, 2014 17:52 |
|
Drivers.
|
# ? Dec 13, 2014 18:05 |
|
My name is Eric. I watch this show that has basically become a 45 minute period where I wonder what happened to Laurel's face. And the Confused flashes on the screen with Laurel's dedicated face behind it.
|
# ? Dec 13, 2014 18:11 |
|
.
maskenfreiheit fucked around with this message at 21:42 on Apr 28, 2019 |
# ? Dec 13, 2014 18:18 |
|
Why are you connecting a cable to your tablet? There's pretty much never a reason to outside of fastboot.
|
# ? Dec 13, 2014 19:02 |
|
LastInLine posted:Why are you connecting a cable to your tablet? There's pretty much never a reason to outside of fastboot. Because wireless is slow you big nerd.
|
# ? Dec 13, 2014 21:03 |
|
|
# ? May 26, 2024 16:11 |
|
e: nah
Vykk.Draygo fucked around with this message at 23:54 on Dec 13, 2014 |
# ? Dec 13, 2014 21:48 |