For instance if you create a picture in PhotoShop, then Adobe would have no claim to it.
Creating a picture in Photoshop and uploading it to a webserver as a static image is different than scripting Photoshop so that it operates on images received from a web service, and returns live results to the user. Try asking Adobe if their EULA covers the second case.
When a radio station plays a song, they play it in a private studio, and beam the results of playing it out to all their listeners. This is classed as public performance, and needs separate licenses beyond the usage rights that owning the CD gives you.
The GPL doesn't allow additional restrictions on users. The additional requirement of the AGPL gives users an additional freedom, and the GPLv3 was planned with this in mind already (the GPLv2 is not compatible with this, which was part of the motivation for creating GPLv3).
If the FCC really wants to encourage that, then they should adopt the same bidding process as the UK used for the 3G spectrum auction. The highest bidder pays the price of the second highest bid. This encourages bubble-headed companies to put in ridiculously high bids, secure in the knowledge that even if they win, they won't have to pay as much as they bid. But oops, more than one company adopted the same strategy.
ARM926EJ-S is not a chip, it's a core which is licensed by a number of chip manufacturers. But the Qualcomm MSM7k family, which Google just released a Linux kernel port for (big hint there) is ARM11 based, so I think the ARM926EJ-S is probably just the most recent ARM core that QEMU can emulate.
Same for Japan - DoCoMo is GSM/UMTS. KDDI is CDMA2000 I believe. Fairly certain Softbank is also GSM, as many HTC GSM devices are rebranded by Softbank.
I think Korea is one of the few (if only) countries that has no GSM service at all. (And they may have a GSM carrier.)
Docomo and Softbank use PDC for their 2G services, not GSM. They don't have dual 2G/3G phones, it is one or the other, so many 3G phones sold over there now come with GSM for roaming with. Korea and Japan were the only two countries listed by Vodafone UK where you could not roam with a triband GSM phone a few years ago.
Which Korean network is using GSM? When I travelled there on business a few years ago, Japan and Korea were the only two countries I couldn't roam in with a tri-band GSM phone (the US is patchy, but at least most major cities have a GSM signal). After getting a WCDMA phone, only Korea was left, but now I think they have a WCDMA network too.
Nokia published some figures for EDGE vs 3G chips a while back, but I can't find them now. At idle, 3G uses slightly less power than GSM/EDGE. On voice calls, 3G uses roughly double the power. For data, 3G uses about a quarter of the power for the same data throughput.
The biggest drain for 3G phones is that they have to keep the GSM radio polling so they can fall back without going off air for a period when they lose the 3G signal. In Japan where there is no GSM network, you don't have that inefficiency to worry about.
Sorry, that should read:
And of course, there's the third reason that the Linux port for the Qualcomm MSM7K family is being maintained at git.android.com.
Most iPhone applications will look just as much like on future VGA or WVGA models, since the current hardware encourages developers to develop for HVGA. At least with Android, developers are aware that they are designing for a variety of hardware, and those with half a brain will avoid sizing things in pixels where possible.
If only they'd had the foresight to put 3G in it, you could have used your iPhone as a phone instead of an expensive, battery hungry, short on disk space iPod.
It should also have a companion option "Fill my notification area with lots of little static icons for programs I seldom use, but to the developers they were the most important thing in the world so they want them to be already started on the rare occasions I might want to use them, least I judge the developer by the 5 second delay of starting their program, on startup."
There are about 4 J2ME vendors that cover 90% of the phone market. The main problem comes from developers who assume that every phone has the snazzy new API they want to use, then find that people with older phones want to use their app too.
This is just plain wrong. Once you start looking at graphics, audio, keyboard input, bluetooth, gps, network, photo or video capture or anything beyond very basic apps, you reach the murky world of JSRs, which are bits of java that may or may not be included in a particular j2me installation. If they are included, many of them have lots left up to the implementation to decide, for example MMAPI leaves it up to the implementation whether to support MIDI sound, whether to support playing audio directly from code rather than from a file, whether to support recording, what file formats to support etc. You can't even reliably play audio files across platforms, let alone do interesting things like get at the camera, get video frames etc.
You obviously missed the section on optional APIs in the Android docs. And do you think they have everything covered that will come up in the next 10 years? This platform will get into the same state as J2ME very quickly.
Nokia would be the main non-member Google has to worry about. They are already using Linux on their Internet tablet devices, and are already porting WebKit to GTK so they can use it in place of Opera (which they currently use on those devices), so forking their own version of this platform might be quite attractive to them. Any smaller companies probably have more to gain by using the platform as-is, so they benefit from the upgrades and applications developed by/for their bigger competitors.
According to some guy's blog, Dalvik is going to be released under the APL. But Dalvik is released now, and there is no sign of any source, and a no-reverse-engineering license to go with it. I haven't seen any definite commitment from Google to release the Dalvik VM under the APL or any other open source license. What they did say is that they will release some APIs under an Apache license, but if they don't release the VM which is required to run them, they might as well be closed.
ARM license their architectures out to Marvell, TI and others. They don't actually build their own chips anymore, so it isn't a case of "other" implementors. That said, the XScale line is based on the ARM5 architecture, and I'm not aware of any Marvell/Intel chips with the Jazelle extensions, which are available on ARM9 and ARM11 cores with a J in the full model number (ARM-926EJ-S).
Aplix and Esmertec are both Jazelle licensees, and also members of the Open Handest Alliance, so there might be some Jazelle capabilities in Dalvik that ARM doesn't know about.
Slashdot Mirror
Creating a picture in Photoshop and uploading it to a webserver as a static image is different than scripting Photoshop so that it operates on images received from a web service, and returns live results to the user. Try asking Adobe if their EULA covers the second case.
When a radio station plays a song, they play it in a private studio, and beam the results of playing it out to all their listeners. This is classed as public performance, and needs separate licenses beyond the usage rights that owning the CD gives you.
Legally, public performance is not normal use.
Copyright law allows the copyright holder control over public performance of their work.
If your "private development" in use on a public website, then it isn't really private.
The GPL doesn't allow additional restrictions on users. The additional requirement of the AGPL gives users an additional freedom, and the GPLv3 was planned with this in mind already (the GPLv2 is not compatible with this, which was part of the motivation for creating GPLv3).
If the FCC really wants to encourage that, then they should adopt the same bidding process as the UK used for the 3G spectrum auction. The highest bidder pays the price of the second highest bid. This encourages bubble-headed companies to put in ridiculously high bids, secure in the knowledge that even if they win, they won't have to pay as much as they bid. But oops, more than one company adopted the same strategy.
Softbank has a UMTS network. UMTS is also compatible with Docomo's FOMA network.
ARM926EJ-S is not a chip, it's a core which is licensed by a number of chip manufacturers. But the Qualcomm MSM7k family, which Google just released a Linux kernel port for (big hint there) is ARM11 based, so I think the ARM926EJ-S is probably just the most recent ARM core that QEMU can emulate.
Docomo and Softbank use PDC for their 2G services, not GSM. They don't have dual 2G/3G phones, it is one or the other, so many 3G phones sold over there now come with GSM for roaming with. Korea and Japan were the only two countries listed by Vodafone UK where you could not roam with a triband GSM phone a few years ago.
Which Korean network is using GSM? When I travelled there on business a few years ago, Japan and Korea were the only two countries I couldn't roam in with a tri-band GSM phone (the US is patchy, but at least most major cities have a GSM signal). After getting a WCDMA phone, only Korea was left, but now I think they have a WCDMA network too.
Nokia published some figures for EDGE vs 3G chips a while back, but I can't find them now. At idle, 3G uses slightly less power than GSM/EDGE. On voice calls, 3G uses roughly double the power. For data, 3G uses about a quarter of the power for the same data throughput.
The biggest drain for 3G phones is that they have to keep the GSM radio polling so they can fall back without going off air for a period when they lose the 3G signal. In Japan where there is no GSM network, you don't have that inefficiency to worry about.
Sorry, that should read: And of course, there's the third reason that the Linux port for the Qualcomm MSM7K family is being maintained at git.android.com.
And of course, there's the third reason that the Qualcomm MSM7K family is being maintained at git.android.com.
Most iPhone applications will look just as much like on future VGA or WVGA models, since the current hardware encourages developers to develop for HVGA. At least with Android, developers are aware that they are designing for a variety of hardware, and those with half a brain will avoid sizing things in pixels where possible.
If only they'd had the foresight to put 3G in it, you could have used your iPhone as a phone instead of an expensive, battery hungry, short on disk space iPod.
It should also have a companion option "Fill my notification area with lots of little static icons for programs I seldom use, but to the developers they were the most important thing in the world so they want them to be already started on the rare occasions I might want to use them, least I judge the developer by the 5 second delay of starting their program, on startup."
There are about 4 J2ME vendors that cover 90% of the phone market. The main problem comes from developers who assume that every phone has the snazzy new API they want to use, then find that people with older phones want to use their app too.
try {
...
...
}
catch (NoClassDefFoundError e) {
}
Works on any Java VM.
You obviously missed the section on optional APIs in the Android docs. And do you think they have everything covered that will come up in the next 10 years? This platform will get into the same state as J2ME very quickly.
Nokia would be the main non-member Google has to worry about. They are already using Linux on their Internet tablet devices, and are already porting WebKit to GTK so they can use it in place of Opera (which they currently use on those devices), so forking their own version of this platform might be quite attractive to them. Any smaller companies probably have more to gain by using the platform as-is, so they benefit from the upgrades and applications developed by/for their bigger competitors.
According to some guy's blog, Dalvik is going to be released under the APL. But Dalvik is released now, and there is no sign of any source, and a no-reverse-engineering license to go with it. I haven't seen any definite commitment from Google to release the Dalvik VM under the APL or any other open source license. What they did say is that they will release some APIs under an Apache license, but if they don't release the VM which is required to run them, they might as well be closed.
ARM license their architectures out to Marvell, TI and others. They don't actually build their own chips anymore, so it isn't a case of "other" implementors. That said, the XScale line is based on the ARM5 architecture, and I'm not aware of any Marvell/Intel chips with the Jazelle extensions, which are available on ARM9 and ARM11 cores with a J in the full model number (ARM-926EJ-S). Aplix and Esmertec are both Jazelle licensees, and also members of the Open Handest Alliance, so there might be some Jazelle capabilities in Dalvik that ARM doesn't know about.
In Italy, contests are only allowed if Berlusconi wins.