"This accessory is not supported" messages for most of my off-brand Lightning cables. Worked before the update, work with all my phones that didn't have the update, don't work now (this is based on the public beta).
For those looking for data, try here:
http://www.behardware.com/articles/862-7/components-returns-rates-6.html
Now, I work in this industry, and so I'm not trying to disparage any particular vendor, but this is the only external datapoint that I know of at this point, and explains some of the frustrations being expressed.
EMC's Syncplicity allows you to have a "cloud" backup that's actually domain authenticated and resides in your own data center. Some of the Dropbox-esque features people want, with the in-house security.
NAND does not have its own reliability controls on-die. Items such as wear-leveling, file management, and ECC mechanisms need to be handled somewhere. So the options are in software, which would then need to be validated and designed for each NAND manufacturer, die, and process; and would consume CPU and batter power from the tablet OS, or it can be done via a separate off-die controller.
And as to the choice of eMMC, it's a cost/performance/reliability trade-off. eMMC is relatively inexpensive (very small die), and includes all of the aforementioned reliability mechanisms at a low-power, and low-cost method, in an I/O language supported by most mobile architectures (SD/MMC). However, it severely lacks in relative performance to an SSD. The other option is an optimized SSD controller, which may cost many times more, but has much higher performance. The problem is how to include a $100 SSD in a $100-200 tablet BOM... impossible.
In my college program on electronics design, we actually did a lot of system-level programming on 8085 machines. We went so far as to build DAC converters to build volt meters out of computers. What it gave us was the ability to understand the basics of CPUs interacting with memory, signals, IOs, assembly language. That said, with two years of that under my belt, I am no closer to understanding any real-world programming that can get me a job, than had I not taken the class.
Yes, the basics of computers are much easier when you don't have massive clock frequencies adding insane complications to applications. No, programming has nothing to do with understanding what JMP does. Do I think it's valuable? Sure. Do I think it'll make any difference on whether you can call yourself a "programmer?" No way.
God of War wasn't AO either, and you had to pound out a sex scene rhythm at one point... not just all sex is AO and removed, just explicit and graphic sex.
There are a lot of posts just like this, so I'll respond to this one.
Web code is simplistic, for sure, but how many hours have to be spent making a page render the same in IE4-8, Safari 2-3, Firefox 2-3, Opera, mobile browsers, etc.
I can code a beautiful page for any one, or maybe two, of those in no time. It's double the work or more to get it to render in all of them accurately. And all of this with solitary HTML/CSS/JS. Now I have be a DBA, I do program in C/Perl/Java/PHP, yet I have respect for the need to actually work knowledgably in HTML/CSS. It's not the code that's tough, it's how different the definitions of that simple code are across the ecosystem.
There's one other reason to choose NTFS: the file system is spread across the drive, versus having a localized FAT table. Unless the wear-leveling on the drive is good (and most controllers for USB sticks are more than sufficient for what they're designed for, but I wouldn't call "good," they're designed for price), you end up with very uneven wear on a finite-life product. Add in that the USB market takes the lowest grade of memory available, and I'd trust NTFS over FAT, generally.
That said, I still use FAT, because as long as my thumb drive works long enough to move my presentation from my laptop to my customer's, it's done its job. I don't expect it to have a long life, and I have an unlimited stream of new drives to play with.
As someone who works in the industry... don't use these storage devices if you really hope something will last.
SD cards, USB cards, and all get the worst quality memory. Unreliable, unready, pre-production... the main reason is that it's still good enough for 99.9% of people's use for these types of drives. You copy the data off pretty soon, maybe rewrite the drive ten or twenty times before you've gotten one four times bigger to replace yours, or lost it, or broken it, or moved on to a camera with a new device style.
They're great for what they are, but they're not meant for long term storage.
If you care why:
The majority of drives use MLC technology, and one manufacturer (and soon to be most) use a three-level cell. NAND memory stores data in a floating gate, where electrons are trapped in the gate of a transistor. In time, some of these electrons will dissipate. In higher-reliability SLC, there's more space between a 1 and a 0 for these bits to fade, and not change the data value. In MLC, there are four levels... thus each are closer together, and moving from a 00 to a 01 is going to happen.
In a normal system, wear-leveling and basic use model designs will refresh the data, so this won't happen. But if you unplug that system for years, that's not happening.
So couple a technology that is designed to last ten years on a fresh drive, with low quality versions of the memory (based on the needs of USB/SD markets), and I DO NOT recommend this for long-term storage.
Symbian's OS might be great once open sourced, but the breadth and depth of applications built for Linux, as well as the design of Symbian OS for handhelds, not MIDs, says to me that it's a long ways from being better for this type of platform. Symbian can grow from small to larger, but I myself would rather have a full featured OS on my MID than a phone system turned OS.
ZOMG, they're working on their next version, this one must have sucked!
"Leopard=fail, Apple is already working on 10.6"
Since when is working on the next version of your OS a sign of failure, and not a sign of good business sense and continual development?
So sensor technology that was funded by expensive military research, which finally came down to prices to be used in consumer products, are now coming full circle to be used again for military purposes? Sounds like the interweb all over again.
*cough* Please. Maybe the few simple web 2.0 apps in the world, but the majority of applications are not simply and cleanly built. Have you tried running a powerpoint-like application via Web2.0? Native apps run MUCH cleaner. I need more cpu power to run a few 2.0 apps simultaneously than most native apps, thanks to the hoops they have to run through as a client-server application. Add in a few Flash anythings and now my system is crawling.
In fact, the densities of nand units has continually doubled for several years, but only loosely tied to Moore's law. Moore talked about the doubling of the transistor densities, but if you do some simple calculations of the gate width and silicon lithography nodes, it is not truly following a doubling -- at least not at the same size.
Traditional lithography nodes scaled in 72% increments, which in two dimensions, is 50% scaling. If you track the NAND lithography nodes, they're moving at smaller and smaller increments. 90/70/60/50/45... these are not 72% increments, and thus, though the density is growing, die size is continually increasing.
The SLC to MLC moves jumpstart this a step; however, don't expect this to go on much longer.
Sprintusers has a utility for uploading your own applications, as well as a quite active userbase doing everything from development to featue discussions. Try your questions there, and utilize their utilities for uploading images, applications, and more to your phone, if you want. Just a huge forum board, nothing more.
That's assuming that you're IP provider still has active data connections, the wind hasn't knocked over the cables you're relying on, and any number of things. I swear, a lot of you need to go to one RACES meeting and realize what emergency communications is really like. You can't rely on the base infrastructure to be in place below you in an emergency.
Hear hear! This is business, not emergency planning. To put in the infrastructure to support 100% of people making calls would be a bankrupcy waiting to happen. Batteries only last so long, especially when supporting real equipment...
I've been using litestep for a few years, on Win95, 98, 2k... loved it on all of them.
LS is basically a module loader plus some, but the community support has allowed modules for pretty much anything you want.
There are a lot of LS clones, and different LS builds, but they all work great! One just needs to not mind tweaking with preferences and their own setup...
Some great LS sites:
www.joeblade.com
www.shellfront.org
www.litestep.net -- down for now
Slashdot Mirror
"This accessory is not supported" messages for most of my off-brand Lightning cables. Worked before the update, work with all my phones that didn't have the update, don't work now (this is based on the public beta).
Asus did this with WebWare as well. Looks like it died after 2007, but I could remember that someone did it...
Meant to be logged on as I posted this, not an anonymous coward. That was me who said that...
For those looking for data, try here: http://www.behardware.com/articles/862-7/components-returns-rates-6.html Now, I work in this industry, and so I'm not trying to disparage any particular vendor, but this is the only external datapoint that I know of at this point, and explains some of the frustrations being expressed.
EMC's Syncplicity allows you to have a "cloud" backup that's actually domain authenticated and resides in your own data center. Some of the Dropbox-esque features people want, with the in-house security.
I'm an avid fantasy reader, and started with these books as a kid. I didn't even know the Disney movie (and video game!) existed until years later.
Speaking as someone in the NAND industry...
NAND does not have its own reliability controls on-die. Items such as wear-leveling, file management, and ECC mechanisms need to be handled somewhere. So the options are in software, which would then need to be validated and designed for each NAND manufacturer, die, and process; and would consume CPU and batter power from the tablet OS, or it can be done via a separate off-die controller.
And as to the choice of eMMC, it's a cost/performance/reliability trade-off. eMMC is relatively inexpensive (very small die), and includes all of the aforementioned reliability mechanisms at a low-power, and low-cost method, in an I/O language supported by most mobile architectures (SD/MMC). However, it severely lacks in relative performance to an SSD. The other option is an optimized SSD controller, which may cost many times more, but has much higher performance. The problem is how to include a $100 SSD in a $100-200 tablet BOM... impossible.
In my college program on electronics design, we actually did a lot of system-level programming on 8085 machines. We went so far as to build DAC converters to build volt meters out of computers. What it gave us was the ability to understand the basics of CPUs interacting with memory, signals, IOs, assembly language. That said, with two years of that under my belt, I am no closer to understanding any real-world programming that can get me a job, than had I not taken the class.
Yes, the basics of computers are much easier when you don't have massive clock frequencies adding insane complications to applications. No, programming has nothing to do with understanding what JMP does. Do I think it's valuable? Sure. Do I think it'll make any difference on whether you can call yourself a "programmer?" No way.
God of War wasn't AO either, and you had to pound out a sex scene rhythm at one point... not just all sex is AO and removed, just explicit and graphic sex.
There are a lot of posts just like this, so I'll respond to this one.
Web code is simplistic, for sure, but how many hours have to be spent making a page render the same in IE4-8, Safari 2-3, Firefox 2-3, Opera, mobile browsers, etc.
I can code a beautiful page for any one, or maybe two, of those in no time. It's double the work or more to get it to render in all of them accurately. And all of this with solitary HTML/CSS/JS. Now I have be a DBA, I do program in C/Perl/Java/PHP, yet I have respect for the need to actually work knowledgably in HTML/CSS. It's not the code that's tough, it's how different the definitions of that simple code are across the ecosystem.
There's one other reason to choose NTFS: the file system is spread across the drive, versus having a localized FAT table. Unless the wear-leveling on the drive is good (and most controllers for USB sticks are more than sufficient for what they're designed for, but I wouldn't call "good," they're designed for price), you end up with very uneven wear on a finite-life product. Add in that the USB market takes the lowest grade of memory available, and I'd trust NTFS over FAT, generally.
That said, I still use FAT, because as long as my thumb drive works long enough to move my presentation from my laptop to my customer's, it's done its job. I don't expect it to have a long life, and I have an unlimited stream of new drives to play with.
As someone who works in the industry... don't use these storage devices if you really hope something will last. SD cards, USB cards, and all get the worst quality memory. Unreliable, unready, pre-production... the main reason is that it's still good enough for 99.9% of people's use for these types of drives. You copy the data off pretty soon, maybe rewrite the drive ten or twenty times before you've gotten one four times bigger to replace yours, or lost it, or broken it, or moved on to a camera with a new device style. They're great for what they are, but they're not meant for long term storage. If you care why: The majority of drives use MLC technology, and one manufacturer (and soon to be most) use a three-level cell. NAND memory stores data in a floating gate, where electrons are trapped in the gate of a transistor. In time, some of these electrons will dissipate. In higher-reliability SLC, there's more space between a 1 and a 0 for these bits to fade, and not change the data value. In MLC, there are four levels... thus each are closer together, and moving from a 00 to a 01 is going to happen. In a normal system, wear-leveling and basic use model designs will refresh the data, so this won't happen. But if you unplug that system for years, that's not happening. So couple a technology that is designed to last ten years on a fresh drive, with low quality versions of the memory (based on the needs of USB/SD markets), and I DO NOT recommend this for long-term storage.
Symbian's OS might be great once open sourced, but the breadth and depth of applications built for Linux, as well as the design of Symbian OS for handhelds, not MIDs, says to me that it's a long ways from being better for this type of platform. Symbian can grow from small to larger, but I myself would rather have a full featured OS on my MID than a phone system turned OS.
ZOMG, they're working on their next version, this one must have sucked! "Leopard=fail, Apple is already working on 10.6" Since when is working on the next version of your OS a sign of failure, and not a sign of good business sense and continual development?
So sensor technology that was funded by expensive military research, which finally came down to prices to be used in consumer products, are now coming full circle to be used again for military purposes? Sounds like the interweb all over again.
I find it obscurely funny that the servers doing much of this demo are msbluelight -- the new technology that belongs on the back shelves of K-Mart.
*cough* Please. Maybe the few simple web 2.0 apps in the world, but the majority of applications are not simply and cleanly built. Have you tried running a powerpoint-like application via Web2.0? Native apps run MUCH cleaner. I need more cpu power to run a few 2.0 apps simultaneously than most native apps, thanks to the hoops they have to run through as a client-server application. Add in a few Flash anythings and now my system is crawling.
It looks like flash is outpacing Moore's law, a perception reinforced by marketing and reality by the manufacturers of NAND, such as Samsung's roadmap images http://www.samsung.com/Products/Semiconductor/NAND Flash/index.htm.
In fact, the densities of nand units has continually doubled for several years, but only loosely tied to Moore's law. Moore talked about the doubling of the transistor densities, but if you do some simple calculations of the gate width and silicon lithography nodes, it is not truly following a doubling -- at least not at the same size.
Traditional lithography nodes scaled in 72% increments, which in two dimensions, is 50% scaling. If you track the NAND lithography nodes, they're moving at smaller and smaller increments. 90/70/60/50/45... these are not 72% increments, and thus, though the density is growing, die size is continually increasing.
The SLC to MLC moves jumpstart this a step; however, don't expect this to go on much longer.
Sprintusers has a utility for uploading your own applications, as well as a quite active userbase doing everything from development to featue discussions. Try your questions there, and utilize their utilities for uploading images, applications, and more to your phone, if you want. Just a huge forum board, nothing more.
That's assuming that you're IP provider still has active data connections, the wind hasn't knocked over the cables you're relying on, and any number of things. I swear, a lot of you need to go to one RACES meeting and realize what emergency communications is really like. You can't rely on the base infrastructure to be in place below you in an emergency.
Hear hear! This is business, not emergency planning. To put in the infrastructure to support 100% of people making calls would be a bankrupcy waiting to happen. Batteries only last so long, especially when supporting real equipment...
I've been using litestep for a few years, on Win95, 98, 2k... loved it on all of them. LS is basically a module loader plus some, but the community support has allowed modules for pretty much anything you want. There are a lot of LS clones, and different LS builds, but they all work great! One just needs to not mind tweaking with preferences and their own setup... Some great LS sites: www.joeblade.com www.shellfront.org www.litestep.net -- down for now