Sunday, March 18, 2012
Introducing Google Play
For more than a year we’ve been focused on expanding the reach, content, and monetization opportunities of Android Market. We started by extending the store to users on the web and then went on to add books, movies, and music. The number of people who have visited, registered, and downloaded from the store has been amazing.
Today we’re launching Google Play, an integrated destination for apps, books, movies, and music, accessible to users on Android devices and to anyone on the Web. As part of this launch, Google Play replaces and extends Android Market — users everywhere can now find their favorite apps and games in Google Play, with other digital content, all in one place.
We believe that with a strong brand, compelling offerings, and a seamless purchasing and consumption experience, Google Play will drive more traffic and revenue to the entire ecosystem.
We’ll be investing in the brand to bring Google Play to as many people as possible, and we’ll also invest in the latest digital content to keep Google Play fresh, relevant, and engaging. Apps and games remain the core of Google Play, so we’ll continue investing in new ways to connect users with their favorite apps, and developers with new customers.
As we grow and promote Google Play around the world, we’ll be marketing your apps and games at the same time. Our policies have not changed and our goal is still the same — to create a great, open marketplace for distributing Android apps.
Google Play is built on the same infrastructure as Android Market, so the transition for users and developers will be seamless. Users can sign into their existing accounts with the same credentials as before and purchase content using the same payment methods. As a developer, there’s no change needed to your published products and you can continue to use the same publishing tools to put your app in front of hundreds of millions of Android users. If your app was in Android Market yesterday, it’s in Google Play today.
We’ll be rolling out Google Play to devices in a phased OTA update, starting today and continuing over the days to come. With the update, the Android Market app will upgrade to the Play Store app and the Music, Videos, and Books apps will upgrade to Play Music, Play Movies, and Play Books. This update is for devices running Android 2.2 or higher, and users on other devices will continue to have the same access to your apps as before.
You can start sending customers to your products in Google Play right away. Check out the updated “Get it on Google Play”badges and look for an email with more details on the transition. In the meantime, you can check out the Google Play web site at the link below and join the discussion on +Android Developers.
CyanogenMod 7.2.0-RC0 v2.0 For Galaxy5
Installation:
1: Open the ROM Manager application.
2: Ensure that you have the latest ClockworkMod build by checking the version information in the Flash ClockworkMod Recovery section, and updating if necessary.
3: Select Download ROM -> psyke83.
4: Select the ROM version that you wish to download, and press the Download button.
5: You will see a popup: ROM Addons. Place a checkmark beside the entry for Google Apps (even if you already have it installed). If there are other ROM Addons available, select them as you please.
6: When the download completes, you’ll see a ROM Pre-Installationdialogue. Here are the options with an explanation of what to select:
7: Backup Existing ROM – this will make a full backup of your current ROM and user settings before proceeding to install the ROM. This is entirely optional.
8: Wipe Data and Cache – this will wipe all user data. If you’re upgrading from Froyo or any other custom ROM, you must select this option (and a backup is also recommended, since your apps and data will be wiped). Otherwise, don’t select this.
9: Wipe Dalvik Cache – this will ensure that the ROM upgrade works smoothly by forcing all applications to rewrite their dalvik cache (.dex files). This is a non-destructive option that should be used by everyone.
10: Press OK to allow ROM Manager to reboot into ClockworkMod Recovery and perform the installation. When installation finishes, the phone will automatically reboot.
Note: if you chose any of the “wipe” options, the first boot of the new ROM will take 5 minutes or longer (depending on how many applications you have installed) in order to regenerate the dalvik cache.
Sumber : http://madteam.co
Android 5.0 Jelly Bean
Google’s Android’s 4.0 Ice Cream Sandwich operating system has a great many new features for the user that are still on their way to becoming widely used. However, even before this has happened, Google are getting ready to launch the next version in the form of Android 5.0. Taiwan’s DigiTimes has reported that the company are planning to release this next version surprisingly soon, in the second quarter of this year. Android 5.0 will be focused more on tablets.
The Android 4.0 system is still being explored by users however. It is a system which offers linked social profiles for users, so that all their contacts are integrated with each other. This means that whether a user is rushing to meet a friend or busy playing partypoker, they will not have to put too much effort into accessing this type of data if they need to get in touch with someone. It also has a new font system that allows users to take screenshots easily and without having to install any apps or rooting their phone. This new system is called Roboto and it is also able to transcribe words into text straight away.
Many other new features are also available, however Google is already thinking of the next step, which apparently is offering an Android 5.0 operating system that is optimized specifically to cater for tablet PCs. The company are planning to enable users to switch between the two operating systems of Android 5.0 and Chrome, without needing to reboot their device. They are pushing this dual-operating system design, in the hope that they can do better than rivals such as Apple’s iOS 5.
Email ThisBlogThis!Share to Twi
Controlled payment number entropay
A controlled payment number (also called a substitute credit card number, a one-time use credit card, or a virtual credit card number) is an alias for one's credit card number. It is generated through the use of either a web application or a specialized client program, interacting with the card issuer's computer, and is linked to one's actual credit card number.
Typically, a controlled payment number has a limit, and an expiration date between two and twelve months from the issue date, both chosen by the account owner, and while it can usually be set up to allow multiple transactions, it can only be used with a single merchant. This alias number is indistinguishable from an ordinary credit card number, and the user's actual credit card number is never revealed to the merchant. Thus, if it is compromised, a fraudulent user can usually do little or no damage.
The system was developed by Orbiscom, a Dublin-based payment processing company, and is used by a number of credit card issuers. In the USA, these include Bank of America (which inherited its system, "ShopSafe," when it acquired MBNA), Citibank (Virtual Account Numbers), Discover Card's Secure Online Account Numbers and NetSpend's "virtual accounts". Examples from other countries are MBnet, which can create a payment number linked to virtually any credit or debit card emitted in Portugal, and UK-based Neteller which offers a "virtual card" with card details generated uniquely for each transaction.
Google Public DNS versus OpenDNS
Today, Google announced their Public DNS offering. It is a valiant effort to speed up the web and make it safe for all of us on the web. The fact is, OpenDNS started this trend four years ago today. Was it a coincidence that this happened? I’m not entirely sure it wasn’t.
Users who want to try out the new Google DNS servers can change their DNS settings to 8.8.8.8 or 8.8.4.4. If you would like to use OpenDNS, visit their website and create a free account or just change your DNS settings to 208.67.222.222 and 208.67.220.220. Personally, I like using the free account because you have access to the dashboard and can tweak your experience.
Now the question comes down to what you should use. This is entirely up to you. Since I prefer OpenDNS here’s a quick outline of what it does that Google doesn’t.
1. OpenDNS let’s you define your experience. You can choose what to block, not block, and allow or not allow to be seen. Google doesn’t do any of that. Yes, they both offer some measure of phishing and malware blocking and other nefarious sites, but OpenDNS gives you much more control whereas Google does not. You can go back and see your peak internet usage, what sites are most popular, even what types of traffic are most popular. For a computer geek like myself, it’s pretty cool.
2. Google claims their site is better because there is no ads. On OpenDNS you only see ads if you try to navigate to a domain that doesn’t exist. If there are other ads I don’t know. Since I use Firefox with adblock I never see the ads anyway. Remember, Google is the largest advertiser on the Internet. Do you think your data, even anonymously, won’t be used to increase their smarts to deliver more and better ads?
3. By using OpenDNS instead of using Google you are using one less thing from the Google Giant. While I love Google, I don’t have to use everything they offer. I like Google Chrome and think it’s an awesome browser. I also use Google Talk, Google Analytics, Google Mail, Google Voice and Google Webmaster Tools. I use a lot of Google stuff, maybe too much. At least, in this one aspect, I’ll use something else that just happens to be, in my opinion, better.
One positive thing out of all this is that Joe Clickpack has become aware, for at least a fleeting moment, about DNS. The average end user has no idea there even is a DNS or just how important it is to making the Internet work. Maybe, just maybe, they will wonder what this is all about and realize that there is a better option to their ISP’s DNS. No matter what you choose, either Google or OpenDNS, as long as you choose one of them that will be better then using your ISPs. And that, my friend, is a difference.
New Release CyanogenMod 7.2.0-RC0 v2.1 for Galaxy5
MADTeam developer psyke83 has released new updated version of CyanogenMod ROM for G5 users. The new released version is CyanogenMod 7.2.0 v2.1. This version has OuNao’s libsensor code(which was closed source by Samsung and remade by OuNao from scratch) which completely fix Accelerometer lag. Big Thanks to OuNao! This release has updated kernel – merged Samsung source with Code Aurora kernel 2.6.32 (froyo_almond branch) with performance improvements.
Known issue: NONE.
This release may not be available on ROM Manager!
Download: update-cm-7-20120305-MADTEAM-galaxy5-signed.zip
Latest HotFix: galaxy5-v2.1-hotfix1.zip
Google Apps: 20110828
Latest HotFix: galaxy5-v2.1-hotfix1.zip
Google Apps: 20110828
Installation:Note : If you are upgrading from an older CyanogenMod version, you always need to re-install the Google Apps package, even if you had previously installed it.
- Reboot into ClockworkMod. You can do this via adb reboot recovery, or by choosing the Reboot -> Recovery menu if you are already using CyanogenMod.
- If you are upgrading from Eclair or Froyo, you absolutely must perform a data wipe: Select wipe data/factory reset and confirm the operation. Note that you will lose all of your user data, so be sure that you have performed a backup. Otherwise, skip to the next step.
- Choose the option install update from sdcard -> choose zip from sdcard. You will see the two (or three) .zip files in the list.
- You must install the two files in this exact order:
- The base package named update-cm-20120305-MADTEAM-galaxy5-signed.zip
- The Google Apps package, named gapps-gb-DATE-signed.zip
- The latest hotfix package for the same base package version, named galaxy5-v2.1-hotfix1.zip
- Once all packages are installed, you can now reboot.
What’s new?
- 20120305 [v2.1]
- Hotfix 1 [6th March]: New wireless driver (AR6kSDK.build_3.1_RC.563) from Freescale i.MX53 source release – wireless is now stable. Modified source is available on github (freescale branch).
- Updated CyanogenMod source
- New ar6000 driver (adapted from AR6kSDK3.1 source package used by the Sony PRS-T1/JP e-book reader); enabled combo scanning in wpa_supplicant_6.
- libaudio: fixed combo device issue (ringtone in speaker + headset/headphone)
- libsensors: using OuNao’s libsensors with change to further reduce battery consumption during idle. This completely fixes sensor lag. Thanks to OuNao.
- Adjusted smartassV2 CPU scheduler to idle at lower frequencies
- Enabled CGROUPS in kernel to minimize data starvation issues.
- Updated fake-dualtouch module to v9.1 (fixed).
- Enabled Goo-inside.me OTA update support requires Goo-inside.me app
Subscribe to:
Posts (Atom)






