Forgot your password?

Comment: Re:Wait for it... (Score 2) 752

by Andy Dodd (#47477421) Attached to: Malaysian Passenger Plane Reportedly Shot Down Over Ukraine

Some of what I've been reading indicates that the "AN-26" the rebels thought they shot down was actually this 777.

If you splode something at 25-30k feet with an "illicitly acquired" SAM battery that you're probably not properly trained to use, unless you're an aircraft engineer you might have issues properly identifying the wreckage.

Comment: Re:Free space (Score 1) 91

Android encryption is done on a partition basis - so the entire partition is going to get clobbered by the encryption process.

The only way data might "leak" out of this is if the eMMC wear leveller saves off the information somewhere - but this requires a pretty sophisticated attacker to recover. Also, Android's wiping facility has done an eMMC secure erase since ICS (exception - Samsung Galaxy S2 family does either a standard format or a nonsecure erase, since firing a secure erase at Samsung's defective eMMC will send the wear leveller out into la-la-land 5% of the time, and once it goes there, there is no coming back.)

Comment: Re:Solaris not well supported by OSS toolchain (Score 1) 183

by Andy Dodd (#47423909) Attached to: Ask Slashdot: Best Dedicated Low Power Embedded Dev System Choice?

Yeah. People are asking questions because HIS questions are, when taken together, nonsensical.

He's looking for a good host machine to do development for ARM, MSP430, and other MCU embedded targets.

When doing embedded development, there is usually a very clear distinction between "target" and "host" - it is rare in the embedded world for people to use a device as both host and target (since the target is usually pretty weak CPU-wise), but he's implying that he wants to use a device that is usually a target (Raspi, BBB) as a host... Which to anyone that has actually DONE this sort of development is nonsensical. There's some benefit to a BBB self-hosting, but it's silly to do AVR or MSP development on a BBB, unless what he's really looking for is a heterogenous target (e.g. the BBB is part of the target solution, and loads an AVR or MSP at runtime to do realtime tasks - but even this doesn't really make sense due to the BBB's PRUSS, other than the fact that the PRUSS is a bit more difficult to work with.)

If you want a low-power low-cost development environment for ARM Cortex-M, AVR, MSP430, etc. targets, your ideal host system is probably a Chromebook with crouton installed on the SD card.

So either he has VERY special unique requirements that he hasn't clearly communicated, or he's looking in an entirely wrong direction for solutions. Either way, his actually needs haven't been properly communicated.

Comment: Re:Dual or quadricopters (Score 2) 103

Yeah. Quadcopters are far less efficient than single-rotor aircraft, and multicopters (hexa, octa) are even less efficient.

The reason people go to hexas and octas is that scaling a quadcopter up to the payload sizes of some of the octas/hexas starts causing issues with blade inertia - an octacopter is more stable.

The main reason quadcopters are doing so well for small aircraft is that at that size class, the mechanical complexity (tail rotor with transmission and collective pitch, plus collective and cyclic pitch control for the main rotor) of a single rotor or dual-rotor aircraft adds a LOT of cost. (The only flight controls of quadcopters are motor speed, with a few exceptions of quads with collective pitch which is still FAR simpler than cyclic pitch control) Once you get to a fullsize helo - it turns out that the quadcopter approach becomes more expensive than a single-rotor AND it's far less efficient.

Kind of similar to how LEDs dominated the flashlight industry for years but only recently became feasible for residential/commercial lighting - incandescent bulbs suffer significantly reduced efficiency and bulb lifetime when scaled down to flashlight sizes.

Comment: The article is a failure (Score 1) 129

by Andy Dodd (#47406715) Attached to: Android Wear Is Here

From TFA: "On the other hand, the Samsung watch is the clear winner on overall build quality."

From reality:

That's right - it's been only 2 weeks or so since Google I/O and Samsung devices are ALREADY breaking with multiple reports of the same failure mode.

In addition, there are frequent reports of display corruption that doesn't happen with the LG:

Comment: Re:Illegal and Dangerous? (Score 1) 200

by Andy Dodd (#47399435) Attached to: The View From Inside A Fireworks Show

Well, as far as flying too close to an airport - I think there are a lot of people in that category that aren't trying to hurt someone, but are just plain stupid.

As far as your assertion that the jet will last long enough to turn around and land again - The landing and takeoff phases for an aircraft (most likely cases where it will hit a small RC aircraft) are the most dangerous ones. Typical RC aircraft have components that are harder/stiffer (worse for a jet engine) than a bird - and a bird into a jet engine on takeoff can be disastrous (see the Miracle on the Hudson - yes that was a rare dual-engine birdstrike, but even a single engine out during the most dangerous parts of a flight is a big deal).

I think the problem is that this video was done by a guy who was screwing around and probably not thinking about negative consequences - if he'd coordinated with the fireworks people to ensure that they agreed there were no safety issues he didn't think about, it would be fine. But now, there's likely to be legislation that is going to be directed at this but contain collateral damage.

See the recent rulings on FPV flight - - I believe this was primarily driven by incidents like (due to timing, not THAT specific one most likely, but similar incidents). End result is - because of some people being completely reckless with FPV flights, the FAA has created an effective blanket ban on FPV flights.

Comment: Re:Good (Score 1) 376

by Andy Dodd (#47212041) Attached to: Theater Chain Bans Google Glass

So by "keeping a running commentary", do you mean that it was obvious the person was actually using Glass to record his companion narrating the whole thing?

If so, then yeah, he's a Glasshole and deserved to get kicked out.

If not, then assuming that he was recording when he probably wasn't (was the display lit up the whole time?) is BS.

Don't call Glass users Glassholes unless they're actually BEING assholes.

Programmers do it bit by bit.