In a lot of apps, the only obvious way to go back used to be to press the Home button and restart the application. Now that the iPad has multitasking, the apps just come up in the state you left them.
This is certainly true if you measure productivity in value of output per unit of time worked. OTOH, if you have exempt employees, your labor costs don't scale with hours worked, and you may, within a certain range, get more output per unit of labor cost by expanding hours past the point where that would be beneficial in a system of hourly wages.
Indeed. Studies have shown that the peak point for knowledge workers is something like 7.5 hours a day, 4 days a week, so going up from the standard 8 hours a day, 5 days a week (which we have Henry Ford to thank for - he carefully researched the optimum working time for assembly line workers) is already giving you diminishing returns.
Most video acceleration is just accelerating common unpatentable operations like vector arithmetic, interpolation, block copies, frame expansion, interpolation etc. This is made available to developers through the OpenMAX API by almost all hardware accelerators. More specialised acceleration exists for MP4 and H.264 video, but even some of that is unpatented and identical to the blocks used by WebM.
And if Google is actually successful in making WebM, not H.264, the standard codec for web video, they're literally going to render hundreds of billions of dollars worth of tablets, smartphones, set-top boxes, etc. with H.264 hardware support obsolete.
WebM can use many of the same acceleration blocks as H.264, it is a matter of writing the codecs that use the hardware.
They go to high beam just fine, but they don't dim themselves as early as I would choose to do so, and I find I'm constantly overriding them.
Personally I think such a feature should only dim, not go the other way. It should be a backup for when the driver forgets to dim their lights, or is too slow to dim them. Automatic systems in a car should not be there to encourage the driver to forget about some aspect of driving, they should be a backup.
The CAN buses in a car are not wireless. The wireless key fob receiver may be connected to the ECU via a CAN bus, but it is not simply a router - you cannot inject arbitrary CAN messages through the wireless protocol.
Wow, you mean they rebuilt the infamous "White Elephant" Bullring carpark on the other side of town, after knocking it down 10 years ago after it was derilict for 30 years?
That system of counting entries and exits is quite common for closed parking lots, and many towns in the UK have signs on major roads approaching the town centre with a list of parking lots and spaces available, so you don't need to be physically close. Also in Singapore they broadcast this info over TMC, so your satnav can direct you to a parking building with spaces available. The innovation here seems to be applying it to roadside parking, where there is no control of vehicles entering and exiting the parking area.
See comment #34. Anything after that is just worthless "me too" responses from people who probably don't even own an Android phone and just have too much time on their hands over the holidays.
Mostly this is a beat up. There does appear to have been a bug that was promptly fixed, but the original submitter of the bug report is still having the problem with one of his two identical devices after the upgrade. Also a small handful of other genuine responders to the report may have the same problem.
Over at Google Code, Issue 9392 — SMS are intermittently sent to wrong and seemingly random contact — carries a priority of 'Medium,' even though it has 600+ comments and has been starred by 3,600+ people."
And yet it took 6 months to get to comment number 34:
Comment 34 by stephenlgo, Dec 20, 2010
I wonder why this "technical issue" is not well-known by the public? There should be a facebook page about this problem.
Unfortunately the new EU law only covers roaming within EU borders. If you travel beyond the EU, you're still in for a shock when your bill arrives, especially if you leave data switched on. An international data plan helps, but watch the limits, they tend to be very low.
Wellington's trolleybuses have been there since 1949, and they were by no means the first. Pyongyang has also had electric buses since 1964. You'd think they'd check these things before making a song and dance about it and handing a propaganda opportunity to their neighbours on a platter.
Regenerative braking, by virtue of not being a method of implementing perpetual motion, is limited to generating less energy than is required to get the bus back up to the speed it was going before braking. So it won't extend the range at all, just avoid reducing the range too much in stop-start traffic.
important accounts such as email, banking or shopping and social networking sites
I think some people have a distorted view of what is really important. Banking obviously. Email yes because it is used to verify password reset requests. Shopping maybe, if the shop keeps your credit card details on file. Social networking? Only if you suffer anxiety problems that would cause you to have a breakdown if someone posted false information to your profile/wall whatever.
I don't expect write once run anywhere will ever really be true but It's a fair expectation that something written for a specific os will run on that os.
For a significant subset of applications that don't need access to specific hardware and have not been written with dependency on other software that does not form a core part of the OS, this is already true. Your expectation that all software will run on all hardware and all versions of the OS is unrealistic, and is not true of any OS or platform.
It is not the variation that is new in the mobile space. It is the fact that you can write an app that runs on all the devices with those variations. The previous expectation that once an app was available for a mobile platform it would run perfectly, since it by definition only supported one device, has been broken (really it was broken by Windows CE years ago, but Windows CE did so little to help developers cope with the issues that effectively apps were still considered as targeting only single devices). Now mobile apps have the same problems as desktop apps dealing with different hardware and user configurations, but the expectations have not caught up because the competitors using this "fragmentation disadvantage" as a marketing ploy. On the desktop it clearly wasn't a disadvantage, and time will prove that this is the case for mobile
Android's open source status means that manufacturers can and do modify the OSs that they ship.
I keep seeing this claim, but can anyone give any actual example of where a manufacturer has made an incompatible change to the Android APIs? It seems to me that when pressed, all that people come up with are the Home screen cosmetic changes that manufacturers have made like Sense UI, Moto Blur etc.
Slashdot Mirror
How could that possibly be true, MS Access only supports 255 columns.
Facebook needs one column for every privacy violation.
In a lot of apps, the only obvious way to go back used to be to press the Home button and restart the application. Now that the iPad has multitasking, the apps just come up in the state you left them.
Indeed. Studies have shown that the peak point for knowledge workers is something like 7.5 hours a day, 4 days a week, so going up from the standard 8 hours a day, 5 days a week (which we have Henry Ford to thank for - he carefully researched the optimum working time for assembly line workers) is already giving you diminishing returns.
Not on the processors I have experience with.
Which parts of the world would that be?
Most video acceleration is just accelerating common unpatentable operations like vector arithmetic, interpolation, block copies, frame expansion, interpolation etc. This is made available to developers through the OpenMAX API by almost all hardware accelerators. More specialised acceleration exists for MP4 and H.264 video, but even some of that is unpatented and identical to the blocks used by WebM.
WebM can use many of the same acceleration blocks as H.264, it is a matter of writing the codecs that use the hardware.
And you will request that the bank returns your money, and they will without argument, because UK law protects you against unauthorized direct debits.
Diamorphine is the generic term used in UK hospitals, where it is still commonly used as a fast acting and powerful painkiller.
Personally I think such a feature should only dim, not go the other way. It should be a backup for when the driver forgets to dim their lights, or is too slow to dim them. Automatic systems in a car should not be there to encourage the driver to forget about some aspect of driving, they should be a backup.
The CAN buses in a car are not wireless. The wireless key fob receiver may be connected to the ECU via a CAN bus, but it is not simply a router - you cannot inject arbitrary CAN messages through the wireless protocol.
Wow, you mean they rebuilt the infamous "White Elephant" Bullring carpark on the other side of town, after knocking it down 10 years ago after it was derilict for 30 years?
That system of counting entries and exits is quite common for closed parking lots, and many towns in the UK have signs on major roads approaching the town centre with a list of parking lots and spaces available, so you don't need to be physically close. Also in Singapore they broadcast this info over TMC, so your satnav can direct you to a parking building with spaces available. The innovation here seems to be applying it to roadside parking, where there is no control of vehicles entering and exiting the parking area.
See comment #34. Anything after that is just worthless "me too" responses from people who probably don't even own an Android phone and just have too much time on their hands over the holidays.
Mostly this is a beat up. There does appear to have been a bug that was promptly fixed, but the original submitter of the bug report is still having the problem with one of his two identical devices after the upgrade. Also a small handful of other genuine responders to the report may have the same problem.
And yet it took 6 months to get to comment number 34:
Unfortunately the new EU law only covers roaming within EU borders. If you travel beyond the EU, you're still in for a shock when your bill arrives, especially if you leave data switched on. An international data plan helps, but watch the limits, they tend to be very low.
USB 2.0 also allows 900mA when the port is not communicating, and more if it is a dedicated charging port.
$700 for a simple utility to remember passwords? And that assumes the price stays constant.
Wellington's trolleybuses have been there since 1949, and they were by no means the first. Pyongyang has also had electric buses since 1964. You'd think they'd check these things before making a song and dance about it and handing a propaganda opportunity to their neighbours on a platter.
Regenerative braking, by virtue of not being a method of implementing perpetual motion, is limited to generating less energy than is required to get the bus back up to the speed it was going before braking. So it won't extend the range at all, just avoid reducing the range too much in stop-start traffic.
I think some people have a distorted view of what is really important. Banking obviously. Email yes because it is used to verify password reset requests. Shopping maybe, if the shop keeps your credit card details on file. Social networking? Only if you suffer anxiety problems that would cause you to have a breakdown if someone posted false information to your profile/wall whatever.
For a significant subset of applications that don't need access to specific hardware and have not been written with dependency on other software that does not form a core part of the OS, this is already true. Your expectation that all software will run on all hardware and all versions of the OS is unrealistic, and is not true of any OS or platform.
It is not the variation that is new in the mobile space. It is the fact that you can write an app that runs on all the devices with those variations. The previous expectation that once an app was available for a mobile platform it would run perfectly, since it by definition only supported one device, has been broken (really it was broken by Windows CE years ago, but Windows CE did so little to help developers cope with the issues that effectively apps were still considered as targeting only single devices). Now mobile apps have the same problems as desktop apps dealing with different hardware and user configurations, but the expectations have not caught up because the competitors using this "fragmentation disadvantage" as a marketing ploy. On the desktop it clearly wasn't a disadvantage, and time will prove that this is the case for mobile
I keep seeing this claim, but can anyone give any actual example of where a manufacturer has made an incompatible change to the Android APIs? It seems to me that when pressed, all that people come up with are the Home screen cosmetic changes that manufacturers have made like Sense UI, Moto Blur etc.