Actually, from what I understand, UMTS towers don't broadcast their geographic coordinates, but CDMA towers do. And I'm sure almost every wifi base station does not know their coordinates.
So, yes, the data does have to be downloaded from Apple since otherwise, you'd have no idea where these points are on the map. It's not like you can trilaterate the location of these radio devices when you only have your 1 phone as a detector, yeah?
You probably missed this since you're obviously not a Filemaker Pro fan: Filemaker Pro now has integration with external sources like Oracle and MySQL, and also can be accessed via ODBC. Exporting and migration shouldn't be a problem.
Then again, I haven't tried it myself since I've long exported all my active data from FMP. But I do still use FMP to rapid prototype new DBs schema layouts. In my opinion, FMP's one of the best DB prototyping tools ever.
Why the heck do people complain about the lack of something... that IS ALREADY BUILT IN?!?
Because it's not accurate. It doesn't seem to take into account background data usage, at least from my observations.
I had a problem where something on my phone (must have been a Google app too since there wasn't any market apps installed) was causing excessive data usage while the phone was off. So I charged my phone to 100%. Let the phone sit on the table for most of a day. (about 8 hours). Came back, looked at the battery usage screen and it said the thing that consumed the most power was "Music". Given that I hadn't ran the music app during that day, that couldn't be the reason I only had 15% battery left. The rest of the things listed didn't help me either.
In the end, I found that the phone becomes usable if I disable background data.
I think what he's saying is not that you shouldn't have it at all. He's saying you shouldn't "need" to have it.
Having a utility like top to show resource utilization when you feel like it IS FINE. Having an OS be so shitty so that having top is a requirement in order to get a decently working phone, is NOT OKAY.
You're right that for BaseBridge to infect your Android phone, you would have to actually dig through some shady parts of the internet. But wasn't the DroidDream infections originating from apps on Google's Android Market?
Um, I'm certainly not a radio engineer but doesn't shielding mean that no signals get in? So, if no external signals get in, how do you shield nav electronics and radios?
(It's been a while since I checked this out, so I could be wrong.)
It's mostly camcorders and drives. Not cameras. All miniDV camcorders use Firewire. The ones you see now using USB are AVCHD camcorders. All HDV (pro-level) camcorders use Firewire as well.
One of the benefits of firewire is that it's fast and predictable enough to allow for direct streaming in realtime from one piece of video hardware to another, building up your realtime processing pipeline.
As in, you can take a HDV video source, connect it to a computer, run effects in realtime, and output it again as firewire to a HDV recorder, monitor, or some other destination. USB2 can't do this because latency can't be guaranteed and bandwidth is inferior. Oh, and having firewire devices be able to talk to each other on their own helps too. High end external audio devices use firewire, while prosumer and lower external audio devices use USB2. This is also because of latency and bandwidth. Once you start adding more channels, you need to be sure you can force your data link to allocate time for each channel to guarantee that your audio does arrive under your latency requirements.
If you look at many of the HDV camcorders now, they have USB but it's just for the picture mode, not video.
Cuz pretty much nobody uses linux on the desktop. If there's nobody to trick into installing a trojan, then there's no point to writing said trojan, yeah?
Besides, for Linux, they'd rather check to see if you're running an old copy of Debian and SSH right in. Just because you didn't notice didn't mean it didn't happen, yeah?
"Your computer has been infected. Please install this program to clean it."
It's social engineering, and you can't protect against that. The installer needs admin rights to install, so people have to enter their password - and they do.
Seriously - how are you supposed to protect against that?
iPad. It has to come from the App Store, which means it's been statically analyzed so that it's highly improbable that would ever escape the sandbox. Nor can it run in the background uncontrolled. Hard to make a botnet when your bots keep killing all their apps, yeah?
I mean, we're already facing the same problem with Android, except that doesn't even need an admin password, and malware can apparently root the device. If you're a botnet vendor, who you going to target now?
And compared to the monopoly days of yore, MS has gone downhill from there. Quite far downhill.
I'd say that MS has an actual legitimate business need for gaining trust amongst customers and developers or else they're totally fucked. There's no reason not to take them at face value now (but always have an abandonment plan given their past) given that it is now in their best interest to not fuck customers and developers over.
The alternative is that those FLOSS-supporters become exactly what they fought against: dictators and control-freaks telling people what they can or cannot do.
Hasn't opencores.org been around for 11 years already? Arn't most FPGA projects involving a CPU core considered a SoC? I mean, like most people won't have one FPGA be the CPU and the other FPGA be the peripherials, yeah?
Heck, my last project in college would be considered a SoC on FPGA and that was like in 2003. (We implemented our own core, cache, and memory controller from scratch. Would have done a basic VGA output but ran out of time and couldn't afford to get myself a Virtex board afterwards)
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection.
kat_skan is right. There's actually two separate articles in this submission. Bill isn't judging the success or failure all the devices in the collection, so the headline doesn't fit. Chris, on the other hand, picks out 5 to make fun of.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection.
Actually, his comments are not evaluating the success or failure of these devices, but rather whatever he notices about them.
There's actually two separate articles in this submission.
Bill Buxton's collection is simply a collection of interesting input devices he's gotten over the years. Yes, he makes comments on them, but it's mostly to show off something unique or special about it. Or about why he may or may not use it. Or maybe some history. It's just comments.
The other article, from some guy named Chris, picks out 5 of the items he considers a failure.
What people seem to be doing, like you, is thinking that something shows up in the collection because it's a failure. That's not correct. It shows up because it's unique. On the other hand, the first link we're given on this submission points to a what a different guy (Chris) thinks are failures, drawn from the images in Bill's collection.
(note: I haven't read any docs regarding this case and have no interest in doing so, but have used a samsung capitvate before.)
It's more than a grid and a roundish flat touchscreen phone.
The F700 uses the grid in the same way as ASOP does. Basically a vertical menu of apps. Nothing new. It's a copy from the even older feature phone designs like Nokias, Samsungs, Pantechs, etc. Oh, and the Palm Pilot. (I wonder where mine went) Heck, it's even the same format WinMo/WinCE uses.
The problems I see with TouchWiz3 is that it: 1) Adds a dock, a UI widget typically used only by Apple's OSX and iOS devices. Introduced in NeXT and the Apple Newton. 2) Changes the vertical scrolling to the horizontal paging, and adds the "highlighted dot" page indicator. First time I've ever seen it was on the iPhone launch. 3) Adds both the rounded square icon asthetic typical of the iPhone as well as the red corner circle. (Touchwiz3 uses the circles as deletes as opposed to unread notifications, but the design asthetics are clearly similar)
Oi oi... yeah, I now do dev on both platforms too. And while you've certainly got the seniority on me.... several of your argument points are just flat out useless.
Android is built on a GPL'd kernel, yes. But Android's uniqueness lies primarily in it's Apache-licensed components. Most of which are not being worked on by 3rd parties. In Android, GPL means practically nothing since if Google and the handset manufacturers wanted to, they could switch to practically any kernel as long as they wanted to write drivers. Including Posix on NT, Darwin, and any-popular-BSD.
Your point about developer community is nullified by the fact that the developer community, like CyanogenMod, merely ships out their own distributions which are the same codebase as ASOP except with tweaks and settings put in place that the distro maintainers think are cool to use. Did they write most of the code necessary to make these changes work? No. Does this reduce Google's dev costs? Doubtful since Google and their partners wrote most of the code. Are they bringing something useful to the community? Yes, of course.
Installing a 3rd party speed optimized ROM on a phone is equivalent to taking a HP PC out of the box, and installing TinyXP on it. Of course the new distribution's faster, it's got all the manufacturer crap removed, and updated conf/registry settings.
But you've missed Microlith's point: "The core OS is only part of the equation."
In the end, you're focused on who's doing kernel work. But the kernel's almost completely irrelevant to the equation since it's so stagnant. In fact, most of the significant changes for both the kernel for Android and iOS were built back when desktops ran off 4 megs of DRAM and a 33Mhz CPU.
You've seen the Android contribution back to the linux mainline, yeah? It's just the power management lock. If (and obviously it didn't) that took a significant amount of effort to do (in terms of competing with Apple), then Linux is doomed.
What makes Android and iOS special is not that one's running on Linux and the other on Mach. Users don't and shouldn't care about that. What makes the two platforms special is the code that drives the app development AND the code that controls the user interface. Without Google's Apache-licensed library stack and Dalvik, Android would be MeeGo, a failure. Without iOS's UIKit and compositing engine, iOS would be OpenDarwin, another failure.
Google's Honeycomb pretty much proves Dow-Cow's point: Google's platform development process isn't any more open than Apple's, despite Google's commitment to Open Source.
Once Honeycomb's source is released, that statement still remains true. Afterall, it's still Open Source if the source is available regardless of whether or not the source was open during development. And that should not be a problem for anyone, regardless of which cheerleading squad you're on.
Actually.... I think it's not the iPhone's logging the data, but rather it's a cache of data downloaded FROM Apple.
Somebody mentioned to me a while back that at some conference, somebody from Apple mentioned a hotspot cache to help get location faster without being online. Your post just jogged my memory of this. So it actually makes sense. You'd want it to propagate to all your devices because it helps you get location data, and Apple doesn't take it because it was data from them in the first place. And you get faster lookup of location data even when offline.
CDMA phones don't have this file because towers transmit location assistance data without a data connection session open anyways.
.... doesn't turning on wifi location services on Android pop up a dialog that says "by turning this on, you're letting Google track your every move even when your phone is idle?"
Besides, with the SMS bug, who knows where your messages go:P
Here's a workaround: Require that all Android users turn off WiFi before idling their phones, and also turn off auto sleep.
Is that a reasonable workaround? Well, you tell me. Personally, I'd be pretty annoyed if I wanted to use WiFi that I'd have to turn it on and off and wait for a lease every time I needed it. But yeah, it's a workaround.
Funny enough, I speculate that if one to find exact Android units which don't exhibit the problem, they'd probably have significant correlation to shitty battery life.
Pretty simple. Yeah. Look at it. Seriously, look at it.
ASOP, Sense, and Blur don't have the grid/dock layout that Samsung uses.
The G1, the Droid 1/2, and N1 hardware all look significantly different from the iPhone: like keyboards, trackballs, sharper edges on some, rounder edges on others.
The Droid X is thinner plus a bump to support that allows them to house a better camera than the iPod Touch.
Seriously, if it wern't for the lack of gloss on the icons, and the subtle extra buttons on the front, the Samsung really does look like an iPhone clone.
Speaking of which, the Samsung Nexus S looks like a clone of the HTC Magic, except the NS has crappier buttons.
Android is lying. (at least on stock 2.3) On a Nexus S, I get 8 hours of battery life when the phone is untouched sitting on a table for a day. Despite the screen being on for less than 2 minutes, "About Phone" still thinks my display took the majority of the power.
Slashdot Mirror
Actually, from what I understand, UMTS towers don't broadcast their geographic coordinates, but CDMA towers do.
And I'm sure almost every wifi base station does not know their coordinates.
So, yes, the data does have to be downloaded from Apple since otherwise, you'd have no idea where these points are on the map. It's not like you can trilaterate the location of these radio devices when you only have your 1 phone as a detector, yeah?
japanese Karakuri ningy, or clockwork doll.
It's "ningyo" not "ningy".
You probably missed this since you're obviously not a Filemaker Pro fan:
Filemaker Pro now has integration with external sources like Oracle and MySQL, and also can be accessed via ODBC. Exporting and migration shouldn't be a problem.
Then again, I haven't tried it myself since I've long exported all my active data from FMP.
But I do still use FMP to rapid prototype new DBs schema layouts. In my opinion, FMP's one of the best DB prototyping tools ever.
Why the heck do people complain about the lack of something... that IS ALREADY BUILT IN?!?
Because it's not accurate. It doesn't seem to take into account background data usage, at least from my observations.
I had a problem where something on my phone (must have been a Google app too since there wasn't any market apps installed) was causing excessive data usage while the phone was off. So I charged my phone to 100%. Let the phone sit on the table for most of a day. (about 8 hours). Came back, looked at the battery usage screen and it said the thing that consumed the most power was "Music". Given that I hadn't ran the music app during that day, that couldn't be the reason I only had 15% battery left. The rest of the things listed didn't help me either.
In the end, I found that the phone becomes usable if I disable background data.
I think what he's saying is not that you shouldn't have it at all. He's saying you shouldn't "need" to have it.
Having a utility like top to show resource utilization when you feel like it IS FINE.
Having an OS be so shitty so that having top is a requirement in order to get a decently working phone, is NOT OKAY.
You're right that for BaseBridge to infect your Android phone, you would have to actually dig through some shady parts of the internet.
But wasn't the DroidDream infections originating from apps on Google's Android Market?
Um, I'm certainly not a radio engineer but doesn't shielding mean that no signals get in?
So, if no external signals get in, how do you shield nav electronics and radios?
(It's been a while since I checked this out, so I could be wrong.)
It's mostly camcorders and drives. Not cameras.
All miniDV camcorders use Firewire. The ones you see now using USB are AVCHD camcorders.
All HDV (pro-level) camcorders use Firewire as well.
One of the benefits of firewire is that it's fast and predictable enough to allow for direct streaming in realtime from one piece of video hardware to another, building up your realtime processing pipeline.
As in, you can take a HDV video source, connect it to a computer, run effects in realtime, and output it again as firewire to a HDV recorder, monitor, or some other destination. USB2 can't do this because latency can't be guaranteed and bandwidth is inferior. Oh, and having firewire devices be able to talk to each other on their own helps too.
High end external audio devices use firewire, while prosumer and lower external audio devices use USB2. This is also because of latency and bandwidth. Once you start adding more channels, you need to be sure you can force your data link to allocate time for each channel to guarantee that your audio does arrive under your latency requirements.
If you look at many of the HDV camcorders now, they have USB but it's just for the picture mode, not video.
Makes it kinda obvious why Google won't release Honeycomb source code, eh?
Cuz pretty much nobody uses linux on the desktop. If there's nobody to trick into installing a trojan, then there's no point to writing said trojan, yeah?
Besides, for Linux, they'd rather check to see if you're running an old copy of Debian and SSH right in. Just because you didn't notice didn't mean it didn't happen, yeah?
This isn't exploiting privileges.
"Your computer has been infected. Please install this program to clean it."
It's social engineering, and you can't protect against that. The installer needs admin rights to install, so people have to enter their password - and they do.
Seriously - how are you supposed to protect against that?
iPad. It has to come from the App Store, which means it's been statically analyzed so that it's highly improbable that would ever escape the sandbox. Nor can it run in the background uncontrolled. Hard to make a botnet when your bots keep killing all their apps, yeah?
I mean, we're already facing the same problem with Android, except that doesn't even need an admin password, and malware can apparently root the device. If you're a botnet vendor, who you going to target now?
And compared to the monopoly days of yore, MS has gone downhill from there. Quite far downhill.
I'd say that MS has an actual legitimate business need for gaining trust amongst customers and developers or else they're totally fucked.
There's no reason not to take them at face value now (but always have an abandonment plan given their past) given that it is now in their best interest to not fuck customers and developers over.
The alternative is that those FLOSS-supporters become exactly what they fought against: dictators and control-freaks telling people what they can or cannot do.
Unusual? Really?
Hasn't opencores.org been around for 11 years already? Arn't most FPGA projects involving a CPU core considered a SoC? I mean, like most people won't have one FPGA be the CPU and the other FPGA be the peripherials, yeah?
Heck, my last project in college would be considered a SoC on FPGA and that was like in 2003. (We implemented our own core, cache, and memory controller from scratch. Would have done a basic VGA output but ran out of time and couldn't afford to get myself a Virtex board afterwards)
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection.
kat_skan is right.
There's actually two separate articles in this submission. Bill isn't judging the success or failure all the devices in the collection, so the headline doesn't fit. Chris, on the other hand, picks out 5 to make fun of.
Overall Mr Buxton is really, really bad at evaluating the success or failure and the usefulness or not of many of the items he has in his collection.
Actually, his comments are not evaluating the success or failure of these devices, but rather whatever he notices about them.
There's actually two separate articles in this submission.
Bill Buxton's collection is simply a collection of interesting input devices he's gotten over the years. Yes, he makes comments on them, but it's mostly to show off something unique or special about it. Or about why he may or may not use it. Or maybe some history. It's just comments.
The other article, from some guy named Chris, picks out 5 of the items he considers a failure.
What people seem to be doing, like you, is thinking that something shows up in the collection because it's a failure. That's not correct. It shows up because it's unique. On the other hand, the first link we're given on this submission points to a what a different guy (Chris) thinks are failures, drawn from the images in Bill's collection.
*sigh* You're not reading what fuzzyfuzzyfungus said.
fuzzyfuzzyfungus DID NOT say that data isn't being sent to Apple. We all know that data is being sent to Apple cuz Apple said it was.
fuzzyfuzzyfungus DID SAY that "consolidated.db" (aka "this file") is not being sent to Apple.
There is no cognitive disassociation or newspeak. There's just evidence that Belial6 needs to get his/her's eyes checked.
(note: I haven't read any docs regarding this case and have no interest in doing so, but have used a samsung capitvate before.)
It's more than a grid and a roundish flat touchscreen phone.
The F700 uses the grid in the same way as ASOP does. Basically a vertical menu of apps. Nothing new. It's a copy from the even older feature phone designs like Nokias, Samsungs, Pantechs, etc. Oh, and the Palm Pilot. (I wonder where mine went) Heck, it's even the same format WinMo/WinCE uses.
The problems I see with TouchWiz3 is that it:
1) Adds a dock, a UI widget typically used only by Apple's OSX and iOS devices. Introduced in NeXT and the Apple Newton.
2) Changes the vertical scrolling to the horizontal paging, and adds the "highlighted dot" page indicator. First time I've ever seen it was on the iPhone launch.
3) Adds both the rounded square icon asthetic typical of the iPhone as well as the red corner circle. (Touchwiz3 uses the circles as deletes as opposed to unread notifications, but the design asthetics are clearly similar)
Oi oi... yeah, I now do dev on both platforms too. And while you've certainly got the seniority on me.... several of your argument points are just flat out useless.
Android is built on a GPL'd kernel, yes. But Android's uniqueness lies primarily in it's Apache-licensed components. Most of which are not being worked on by 3rd parties. In Android, GPL means practically nothing since if Google and the handset manufacturers wanted to, they could switch to practically any kernel as long as they wanted to write drivers. Including Posix on NT, Darwin, and any-popular-BSD.
Your point about developer community is nullified by the fact that the developer community, like CyanogenMod, merely ships out their own distributions which are the same codebase as ASOP except with tweaks and settings put in place that the distro maintainers think are cool to use. Did they write most of the code necessary to make these changes work? No. Does this reduce Google's dev costs? Doubtful since Google and their partners wrote most of the code. Are they bringing something useful to the community? Yes, of course.
Installing a 3rd party speed optimized ROM on a phone is equivalent to taking a HP PC out of the box, and installing TinyXP on it. Of course the new distribution's faster, it's got all the manufacturer crap removed, and updated conf/registry settings.
But you've missed Microlith's point: "The core OS is only part of the equation."
In the end, you're focused on who's doing kernel work. But the kernel's almost completely irrelevant to the equation since it's so stagnant. In fact, most of the significant changes for both the kernel for Android and iOS were built back when desktops ran off 4 megs of DRAM and a 33Mhz CPU.
You've seen the Android contribution back to the linux mainline, yeah? It's just the power management lock. If (and obviously it didn't) that took a significant amount of effort to do (in terms of competing with Apple), then Linux is doomed.
What makes Android and iOS special is not that one's running on Linux and the other on Mach. Users don't and shouldn't care about that. What makes the two platforms special is the code that drives the app development AND the code that controls the user interface. Without Google's Apache-licensed library stack and Dalvik, Android would be MeeGo, a failure. Without iOS's UIKit and compositing engine, iOS would be OpenDarwin, another failure.
Google's Honeycomb pretty much proves Dow-Cow's point: Google's platform development process isn't any more open than Apple's, despite Google's commitment to Open Source.
Once Honeycomb's source is released, that statement still remains true. Afterall, it's still Open Source if the source is available regardless of whether or not the source was open during development. And that should not be a problem for anyone, regardless of which cheerleading squad you're on.
Actually.... I think it's not the iPhone's logging the data, but rather it's a cache of data downloaded FROM Apple.
Somebody mentioned to me a while back that at some conference, somebody from Apple mentioned a hotspot cache to help get location faster without being online. Your post just jogged my memory of this. So it actually makes sense. You'd want it to propagate to all your devices because it helps you get location data, and Apple doesn't take it because it was data from them in the first place. And you get faster lookup of location data even when offline.
CDMA phones don't have this file because towers transmit location assistance data without a data connection session open anyways.
.... doesn't turning on wifi location services on Android pop up a dialog that says "by turning this on, you're letting Google track your every move even when your phone is idle?"
Besides, with the SMS bug, who knows where your messages go :P
Here's a workaround:
Require that all Android users turn off WiFi before idling their phones, and also turn off auto sleep.
Is that a reasonable workaround? Well, you tell me. Personally, I'd be pretty annoyed if I wanted to use WiFi that I'd have to turn it on and off and wait for a lease every time I needed it. But yeah, it's a workaround.
Funny enough, I speculate that if one to find exact Android units which don't exhibit the problem, they'd probably have significant correlation to shitty battery life.
Pretty simple. Yeah. Look at it. Seriously, look at it.
ASOP, Sense, and Blur don't have the grid/dock layout that Samsung uses.
The G1, the Droid 1/2, and N1 hardware all look significantly different from the iPhone: like keyboards, trackballs, sharper edges on some, rounder edges on others.
The Droid X is thinner plus a bump to support that allows them to house a better camera than the iPod Touch.
Seriously, if it wern't for the lack of gloss on the icons, and the subtle extra buttons on the front, the Samsung really does look like an iPhone clone.
Speaking of which, the Samsung Nexus S looks like a clone of the HTC Magic, except the NS has crappier buttons.
Android is lying. (at least on stock 2.3)
On a Nexus S, I get 8 hours of battery life when the phone is untouched sitting on a table for a day. Despite the screen being on for less than 2 minutes, "About Phone" still thinks my display took the majority of the power.
Or.... El Cazador de la Bruja
http://www.youtube.com/watch?v=_O2nPSddhJg
Wrong, iOS prompts you when the phone tries to get your location data; regardless of how. (As in, not just GPS, but wifi trilateration as well)