Recent submissions

Comment · 11 years ago
Run fast and go to sleep has always been the primary power policy.

A sleeping core is obviously the most efficient core, however you have said nothing to discount what I said. Putting a core to sleep is a very costly activity, which is exactly why it happens at the millisecond scale.

Before that happens, the core will likely have been frequency scaled to more appropriately fit the window's loading. I mean, we know this is the case right now, and that "run fast and go to sleep" is not the primary policy. It's "run as fast as appropriate for the workload to fill a quantum, and sleep when there is no workload". There are many if not most workloads that are externally bound, or event triggered enough that sleep is completely out of the question and running faster does nothing.

Your words have been used (out of context and inappropriately) to bolster DannyBee when they represent, literally, all that is wrong with Hacker News.

Comment · 11 years ago
You don't want A53's "handling the majority of the workload".

Yes. You do. If I'm casually browsing non-intensive web pages, e-reading, or watching a Netflix movie, or even encoding a video, the background is doing IO rate limited system updates and basic data logging, etc, the vast majority of the time the CPU demands are very low, but frequent enough that putting a CPU to sleep is completely out of the question.

An A53 has a much lower ceiling, but a much better middle tier power usage level, than the A57. Yes, if you want to run a benchmark the A53 is not a good bet (and is generally worse in a workload power usage), but it is a very good bet for most real world usage.

Comment · 11 years ago
The 808 is also a big little architecture, with two A57 cores and four A53 cores. The A53 cores will likely carry the vast majority of every day use, and redouble the battery savings.

As a Nexus 5 user I'm pleased with most of the changes and non-changes. 2GB is fine for a smartphone, and an image sensor with more than double the light capture area per pixel is brilliant, and if it delivers the better photographs will be worth it right there. Losing OIS...I don't think that's a downgrade as OIS was always suspect to begin with (not least because OIS only helps for lateral movements. It does nothing for rotational movements, and of course make subjects stand still. It yielded a tonne of unusable photos).

The only thing I'm really displeased about is the removal of wireless charging. That was a really nice feature.

Between the Snapdragon 810 and 808, the only real items of concern is that the 808 does not have h265 hardware encoding (the 810 does), and its image processing DSP is 12-bit per pixel rather than the 14-bpp of the 810.

Comment · 11 years ago
I pay $30 for 6GB of LTE data per month (Rogers, via a promotional plan that they've offered countless times). And I generally use about 200MB in an average month as I'm virtually always around WiFi of some sort. Which is exactly what Google envisions, with most of their cloud solutions defaulting to only operating over WiFi.

SD storage has always been a mess on Android because it was originally added just as an easy way to port music and movies over. It was essentially supposed to be read-only memory. Then of course apps and users started using it and the ugly, messy history is notorious.

Comment · 11 years ago
Updates to Xcode added what Android's tools have had for years, which is the notion of generating multiple binaries for different devices/profiles. Xcode then signs those independent sections and packages them together in an archive, while Google has you send them up separately, each signed separately.

Apple sort of presented it like the App Store is picking and choosing, but it's the enhancements to Xcode that actually enable the functionality. Google could add some tooling improvements to make it slightly easier, but really they've already done all of the hard parts.

Expansion files were a hack, and remain a hack. They are necessary for large games obviously, but really 100MB encompasses the enormous bulk of apps with ease. It would be ideal if Google simply abolished expansion files and folded the sizing into normal APKs.

Comment · 11 years ago
Google announced smart updates and then enabled it (they had already been using this for Nexus system updates). There is absolutely nothing any developer or user has to do, so there is no documentation on it because none is needed. If you actually monitor the connection during a smart/delta update, while the UI shows the full size of the APK it actually downloads 1/4 or less of that.

It is absolutely enabled. It is absolutely working. There is no conspiracy about this. It is one of the reasons most updates take hours to propagate.

You complained about managing thin binaries, so I don't see how the developer managing that would improve anything, not to mention that it adds difficulties to cryptographic signing and verification.

Comment · 11 years ago
What does "too little, too late" mean? Is Android now doomed?

Android updates have been incremental updates for three years now (introduced at the 2012 I/O, and immediately enabled). Your point on that is confused in any case -- why can't it do delta updates (it does...), and why can't the developer do it, but also why does the developer have to do it? You're incredibly complaining about a situation you invented.

And larger APKs are a problem because now the ridiculously easy tools that Google already provides (generating thin binaries for varied targets is extraordinarily simple. A bug regarding expansion files...what is the point of even linking that?) will somehow be unused?

Your post is a very poorly informed rant. I have no idea how it sits on the top.

Comment · 11 years ago
The other comment about electronics is completely off the mark as well -- people often see financial transactions that don't seem to make logical sense (whether pricing bots that recursively keep pricing off of each other, as in the linked story, or prices that seem too good to be true, which more likely are gray market or arbitrage) and immediately explain it as money laundering. But consider the electronics sales, where the premise is that people are selling electronics that they apparently bought from Amazon using gift cards under the market just to launder cash.

There is an enormous financial black hole that is just as vulnerable to inspection as simply depositing $1,000,000 in cash in your account. The whole point of money laundering is not only to legitimize the output, it's to make the sources untraceable and arguably viable as well.

The components of a transaction, particularly for the sales of goods, cannot simply appear out of nowhere, or they've done absolutely nothing in the way of money laundering. The people who will ever care about this (the ones who money laundering is constructed to fool) aren't so naive, and if you're selling 100,000 hard drives to justify your income, they're going to ask where you got the hard drives, and demand a financial trail.

Cash businesses that have little variable costs outside of manpower (such as carwashes, laundrymats, even some small restaurants, or selling small crafts on Etsy) are absolutely lucrative tools for money laundering, and can only really get caught if put under heavy scrutiny (e.g. car wash with 10 cars over the week claims revenue of $100,000). As are casinos, and Vegas was built on money laundering -- there are few checks on how much you spend, so whether you spent $1,000,000 in unexplained cash to leave with $950,000 in legitimate winnings, or $10 in legitimate cash to leave with $950,000 in legitimate winnings, it's almost impossible to prove.

There are many, many financial vehicles that are used for money laundering, including life insurance. Selling hard drives on Amazon is not one of them.

Comment · 11 years ago
I worked for years on AML systems for banks. This isn't money laundering. Indeed, I don't believe I've ever seen a "this is money laundering!" comment on a social news site that wasn't entirely and completely off the mark of real money laundering, but just seems to be a go-to for things that people don't understand.
Comment · 11 years ago
And the vehicles in question -- the ones that are causing VW these issues -- do not have any urea injection system. That's the whole point.

http://ask.cars.com/2012/11/why-do-some-volkswagen-diesels-u...

VW claimed to have a trick that removed the need for it on their smaller, lighter cars. But that trick was a trick that only allowed them to pass EPA tests.

Comment · 11 years ago
Both of those platforms use Urea systems, as do larger and more expensive VW/Audio vehicles. The issue is purely in the small, inexpensive vehicles.

The NOx problems were mostly resolved through the injection of urea into exhaust gases (e.g. AdBlue), dramatically reducing NOx emissions while leaving the efficiency and power unaffected. Urea systems add an extra cost and complexity to the vehicle though (not to mention that you need to top up your urea additive occasionally), and VW seemed to find a loophole that allowed them to make small, inexpensive cars without urea injection. They did this by injecting fuel into the exhaust in the absence of Urea, but to achieve the same effect. But this can gunk up the NOx trap if used endlessly (it is far less precise than urea, obviously), reduces fuel economy, etc, so they built this One Little Trick that only actually does that during identified tests.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton