Saturday, July 3, 2010
Santa Cruz Berharap Tak Adu Penalti Lagi
Tuesday, June 29, 2010
Germany thrash England 4-1 in controversy-filled World Cup
LIVE COMMENTARY
| 90' | The second half is over. The match ends 4 - 1. | |
| 90' | Germany's Bastian Schweinsteiger is whistled for offside at Free State Stadium. | |
| 90' | Jorge Luis Larrionda will wait an extra 2 minutes before blowing the whistle to end the second half. | |
| 89' | In Bloemfontein, Gareth Barry in England is presented with a shooting opportunity. But the strike is blocked by the covering defence. | |
| 89' | At Free State Stadium Steven Gerrard (England) takes a corner from the right. | |
| 89' | England's Wayne Rooney is on target but unsuccessful. | |
| 89' | Frank Lampard in England fires in a shot on goal in Bloemfontein. Without success, however. | |
| 88' | At Free State Stadium Wayne Rooney (England) lifts in a corner from the right. | |
| 87' | Germany's Sami Khedira has run offside. | |
| 87' | Fabio Capello is making the team's third substitution at Free State Stadium with Shaun Wright-Phillips replacing Glen Johnson. | |
| 83' | Stefan Kiessling is replacing Mesut Ãzil in Germany at Free State Stadium. | |
| 82' | Glen Johnson in England has been booked for unsporting behavior and is shown a yellow card by Jorge Luis Larrionda. | |
| 81' | Steven Gerrard in England smashes in a shot on target. The keeper saves, though. | |
| 80' | Germany are coming forward and Mario Gomez gets in a strike. Which is off target, however. | |
| 79' | Lukas Podolski (Germany) goes for goal but the shot is blocked by an alert defence. | |
| 72' | Joachim Low is making the team's second substitution at Free State Stadium with Mario Gomez replacing Miroslav Klose. | |
| 72' | Piotr Trochowski is on as sub for Thomas Muller in Germany. | |
| 71' | Fabio Capello (England) is making a second substitution, with Emile Heskey replacing Jermain Defoe. | |
| 70' | At Free State Stadium Steven Gerrard (England) takes a corner from the left. But the chance is unproductive. | |
| 70' | Goal! Thomas Muller extends Germany's lead to 4 - 1 at Free State Stadium. | |
| 70' | Mesut Ãzil assisted. | |
| 69' | Steven Gerrard in England gets in a strike at Free State Stadium but the shot is cleared by Germany | |
| 69' | Germany are pushing forward but Thomas Muller's finish is wide of the post. | |
| 67' | Frank Lampard (England) is given an opening but the shot is blocked by a defender. | |
| 67' | Germany move up to a comfortable 3 - 1 lead thanks to Thomas Muller. | |
| 67' | Bastian Schweinsteiger assisted the goal. | |
| 64' | England make their first substitution with Joe Cole replacing James Milner. | |
| 64' | Jerome Boateng of Germany gets in a strike, but is off target. | |
| 63' | Germany's Bastian Schweinsteiger breaks free at Free State Stadium. But the strike goes wide of the post. | |
| 62' | James Milner in England fires in a strike at Free State Stadium but the ball is blocked by an alert defence. | |
| 60' | Germany's Thomas Muller misses with an attempt on goal. | |
| 58' | Steven Gerrard (England) with an attempt in Bloemfontein. The shot goes wide, though. | |
| 56' | Steven Gerrard in England drives towards goal at Free State Stadium. But the finish is unsuccessful. | |
| 55' | Jorge Luis Larrionda has awarded Germany a corner. Mesut Ãzil takes the kick from the right corner flag. | |
| 53' | In Bloemfontein Germany's Miroslav Klose is caught offside. | |
| 52' | Frank Lampard (England) gets in a shot at Free State Stadium â but hits the bar! Ohhhh so close. | |
| 49' | England's Steven Gerrard breaks free at Free State Stadium. But the strike goes wide of the post. | |
| 48' | James Milner of England gets in a strike, but is off target. | |
| 47' | Arne Friedrich (Germany) has been given a first yellow card. | |
| 46' | Jorge Luis Larrionda has blown to start the second half. | |
| 45' | The 1st half has ended. | |
| 40' | England are coming forward and Steven Gerrard gets in a strike. Which is off target, however. | |
| 39' | In Bloemfontein Germany attack through Lukas Podolski. The finish is off target, however. | |
| 38' | England apply pressure and a brilliant scoring opportunity is created for Frank Lampard. But the ball crashes against the crossbar! | |
| 37' | Jorge Luis Larrionda has awarded Germany a corner. Mesut Ãzil takes the kick from the right corner flag. | |
| 37' | Matthew Upson (England) strikes with a header to reduce the score to 1 - 2 at Free State Stadium. | |
| 37' | Steven Gerrard assisted. | |
| 36' | Germany's Miroslav Klose gets in a shot on goal at Free State Stadium. But the effort is unsuccessful. | |
| 35' | England push forward through Frank Lampard, whose finish on goal is saved. | |
| 32' | Thomas Muller fed the ball. | |
| 32' | Goal! Germany extend their lead to 2 - 0 through Lukas Podolski. | |
| 32' | Jermain Defoe in England is pulled up for offside. | |
| 31' | Germany drive forward and Miroslav Klose gets in a shot. Without netting, however. | |
| 26' | England's Gareth Barry is on target but unsuccessful. | |
| 24' | England are pushing forward but Wayne Rooney's finish is wide of the post. | |
| 20' | Manuel Neuer set up the goal. | |
| 20' | Germany take a 1 - 0 lead at Free State Stadium. The scorer: Miroslav Klose! | |
| 19' | Frank Lampard (England) gets in a strike but the shot is blocked by a defender. | |
| 17' | Sami Khedira in Germany gets in a strike at Free State Stadium but fails to hit the target. | |
| 11' | Germany push forward at Free State Stadium and Lukas Podolski gets in a strike. This is blocked, however, by a determined England defence. | |
| 6' | Germany drive forward but Mesut Ãzil is judged offside. | |
| 5' | In Bloemfontein Bastian Schweinsteiger in Germany takes a corner from the left-hand flag. | |
| 5' | In Bloemfontein Germany drive forward through Mesut Ãzil. His shot is on target but it's no goal. | |
| 4' | Jorge Luis Larrionda blows England's Wayne Rooney for offside. | |
| 1' | The first half is just kicking off. | |
| 0' | Joachim Low and Fabio Capello have now revealed their starting line-ups. | |
| 40510 spectators are following this match. |
Thursday, June 24, 2010
Exercising Our Remote Application Removal Feature
[This post is by Rich Cannings, Android Security Lead. — Tim Bray]
Every now and then, we remove applications from Android Market due to violations of our Android Market Developer Distribution Agreement or Content Policy. In cases where users may have installed a malicious application that poses a threat, we’ve also developed technologies and processes to remotely remove an installed application from devices. If an application is removed in this way, users will receive a notification on their phone.
Recently, we became aware of two free applications built by a security researcher for research purposes. These applications intentionally misrepresented their purpose in order to encourage user downloads, but they were not designed to be used maliciously, and did not have permission to access private data — or system resources beyond permission.INTERNET. As the applications were practically useless, most users uninstalled the applications shortly after downloading them.
After the researcher voluntarily removed these applications from Android Market, we decided, per the Android Market Terms of Service, to exercise our remote application removal feature on the remaining installed copies to complete the cleanup.
The remote application removal feature is one of many security controls Android possesses to help protect users from malicious applications. In case of an emergency, a dangerous application could be removed from active circulation in a rapid and scalable manner to prevent further exposure to users. While we hope to not have to use it, we know that we have the capability to take swift action on behalf of users’ safety when needed.
This remote removal functionality — along with Android’s unique Application Sandbox and Permissions model, Over-The-Air update system, centralized Market, developer registrations, user-submitted ratings, and application flagging — provides a powerful security advantage to help protect Android users in our open environment.
Wednesday, June 23, 2010
Android Market Problem
Earlier today we had a brief outage in Android Market. For a period of about thirty minutes, some users were unable to find any apps. The problem was detected and corrected, and we believe the user experience is now back to normal. We apologize for the outage.
Lawan Australia, Serbia Buru Sejarah
Kini, Serbia memiliki peluang untuk lolos. "Beli Orlovi" sementara ini berada di posisi tiga dengan perolehan tiga poin. Hasil seri sebenarnya sudah cukup untuk lolos, jika dalam partai lain Ghana sukses menekuk Jerman. Namun, alangkah lebih baiknya jika Serbia menang telak guna mengalahkan selisih gol Jerman, sekaligus memastikan tiket ke perdelapan final."Kami tahu, kami memiliki kesempatan untuk mengukir sejarah saat melawan Australia dan kami akan berusaha sebaik mungkin. Saya tidak akan menaruh tekanan kepada para pemain untuk mengatakan bahwa mereka harus menang. Tapi ketika saya bilang bahwa saya percaya kepada tim saya, saya berkata jujur. Saya tak hanya asal bicara," kata Antic."Saya optimisitis karena saya tahu bagaimana performa pemain saya saat latihan. Ini adalah sesi latihan terbaik kami dari sebelum-sebelumnya. Ini menunjukkan semangat mereka dan sekarang kami memiliki kesempatan untuk menunjukkan semangat ini," lanjut mantan pelatih Barcelona tersebut.
The Froyo Code Drop
[This post is by Jean-Baptiste Queru, who moves truck-loads of source code in and out of the Googleplex. — Tim Bray]
Today is one of those days that has my heart racing; we’ve just released the source code for Android 2.2. This is a big step forward for the entire Android ecosystem. Please don’t melt the servers down again while trying to download that latest source code.
This blog typically talks about developing Android applications using the SDK and NDK. However, the skills of a platform contributor aren’t fundamentally different from those of an application developer. Those are simply different roles using the same skill set. I’m providing an update here to the experienced Android programmers all around the world on some of the recent developments in the Android Open-Source Project.
For Google engineers working on Android, releases are mostly known by their code names which are chosen alphabetically after tasty treats. I’ll call Android 2.2 “Froyo” throughout this post, since that was its code name. Raw version numbers don’t make me salivate as much as the thought of a cold dessert in the California summer.
Let’s have a look at some cool aspects of the new Froyo source, and let’s then take a few steps back to look at other noteworthy aspects of the Android Open-Source Project.
I had been increasingly involved in all previous open-source releases of Android, from testing the initial code drop to doing all the open-source-related git-level work in Eclair. Following that path, Froyo is the first release where my primary focus has been the Android Open-Source Project from start to finish. I thank the entire Android team for helping me all along with much of that work. Here are some aspects of Froyo that I am proud of, and that kept me busy for the last few months:
Hundreds of platform changes that people everywhere uploaded to the Android Open-Source Project were accepted and merged into Froyo. That process is now a well-oiled machine and will translate well to future contributions.
The open-source release happened in a single step. The whole source tree for the entire Android 2.2 platform is now available, with its full change history. That will accelerate everyone’s migration to Froyo from older releases. It is also already fully merged into the open-source master tree. Consequently, we can immediately review and accept platform contributions based on Froyo. That will therefore reduce the risk of merge conflicts between contributions to the open-source tree and changes in Google’s internal master tree where those contributions are meant to end up.
In order to make it easier for device manufacturers and custom system builders to use Froyo, we’ve restructured our source tree to better separate closed-source modules from open-source ones. We’ve made many changes to the open-source code itself to remove unintentional dependencies on closed-source software. We’ve also incorporated into the core platform all the configuration files necessary to build the source code of Android Open-Source Project on its own. You can now build and boot a fully open-source system image out of the box, for the emulator, as well as for Dream (ADP1), Sapphire (ADP2), and Passion (Nexus One).
Speaking of device support, we also open-sourced several additional hardware-related libraries that had been closed-source in previous releases, which will open the door to more contributions. Some examples are the recovery UI code for Dream, Sapphire and Passion, and the interface between the media framework and Qualcomm chipsets.
Besides the Froyo source code release, I wanted to mention several other improvements in the Android Open-Source Project:
We’ve been receiving contributions from more than twenty different companies, and many individuals. We have close to 4,000 registered users on the Gerrit code review server, with an average of 2 contributions per user. Those contributions have been in all areas of the system, from the depth of the C library all the way to the UI of the lock screen. They’ve covered the full range of complexities, from fixing typos in the documentation or reformatting code to adding developer-visible APIs or user-visible features. I want to thank everyone who got involved for their work and patience.
We’re now responding to platform contributions faster, with most changes currently getting looked at within a few business days of being uploaded, and few changes staying inactive for more than a few weeks at a time. We’re trying to review early and review often. As I’m typing this, only about a dozen platform contributions haven’t been looked at yet, with the oldest of those being 3 days old. More than 90% of contributions to the platform code itself have been actively looked at during the last 2 weeks. I hope that the speedy process will lead to more interactivity during the code reviews. I realize nevertheless that time differences around the world can make real-time communication a challenge.
Over the last 2 months, we’ve reached a final decision on more than 1,000 changes that were uploaded to our public Gerrit server. That means that those changes were either accepted or rejected after being reviewed. The high quality of the contributions we’ve been receiving throughout the history of the Android Open-Source Project has allowed us to steadily merge about 80% of them into the main repository, from where they migrate to official releases. That means that an average of 20 changes have been accepted through the Android Open-Source Project into the public git repositories every business day over those last 2 months.
We recently created two new official Google Groups related to the Android Open-Source Project. Android-building is meant to specifically discuss build issues (be sure to search the archives thoroughly before posting). Android-contrib is used to discuss actual contributions (don’t post if you don’t really intend to contribute and follow through on the review process, and if you haven’t already spent an hour or two researching things on your own).
We’re developing the developer tools directly in the open-source project, with no work in those areas happening behind closed doors. This covers the Eclipse plug-in and the emulator, and more than a dozen other SDK-related tools.
Once a platform version is open-sourced, all improvements to the Compatibility Test Suite related to that version are made directly to the open-source tree. In fact, release 2 of the 2.1 CTS was done 100% that way, with the development, testing and release process all happening straight in the open-source tree. This is now true for Froyo as well, and we are now accepting contributions into the Froyo branch of the CTS project.
I believe that those last two aspects are important to application developers. If you’re an application developer and you’d like to improve the tools that you and your fellow developers use, the process to make changes in that area is now a lot more transparent. Similarly, if during application development you find incompatibilities between devices and believe that those incompatibilities aren’t within the letter or the spirit of Android compatibility, you can help improve the situation by contributing a CTS test for that area.
With Android 2.2 now being available to the open-source world, and with the review process working smoothly, I’m looking forward to seeing a lot more high-quality contributions that will be used to build future versions of Android. My sweetest dream, which is also my worst nightmare, is to have so many contributions that I can’t keep up with them. Please don’t wake me up.
Tuesday, June 22, 2010
Hands-on at OSCON
This year at OSCON we and O’Reilly are co-presenting Android Hands-on. The event is on the evening of Wednesday, July 21 after the Expo-hall reception. Led by Google Android experts, the Hands-on will run from 7:00 pm-10:00 pm, and will be intense, technical, and structured. The goal is that you leave the room with foundation skills for writing interesting code for an open-source stack that runs on a pocket-sized Internet-connected device.
Some specific topics we’ll cover:
Porting existing C codebases to Android
Integrating Android apps with RESTful web interfaces
UI patterns and best practices
Sign-up in advance is required, and is restricted to registered full conference attendees and speakers. Spaces are limited and will be given out on a first-come-first-served basis.
If you’re considering participating, you might want to keep these things in mind:
Android apps are written in the Java programming language, with the exception of some performance-critical code (typically for games) written in C and C++. If you aren’t familiar with at least one of these languages, you won’t benefit much from the session.
To prepare, you might want to go to developer.android.com and download the SDK (available for Linux, Mac, and even Windows). Try building the HelloAndroid app and running it on the emulator.
You might also benefit from attending the Android for Java developers tutorial on Monday and/or Dan Morrill’s Android: The Whats and Wherefores session on Wednesday morning.