Home / Archives for Oktober 2013

Google Has in Store for Android 4.4 ??

Posted by Unknown Kamis, 31 Oktober 2013 0 komentar
The rumored release dates came and went, but judging from a flurry of leaks and pre-release app updates, the wait for Google's (NASDAQ:GOOG) official announcement to Android 4.4 may soon be over. But while Oct. 31 does seem like the most natural date to announce an OS named after a staple Halloween candy it's still up in the air whether Google will finally lift the veil on KitKat for its legion of Android fans. However, with recent leaks and screenshots purportedly taken of the new mobile OS, we already have a pretty good idea of what to expect in the upcoming release.

Google Experience Launcher

As we've started to see in the months leading up to the new OS, Google has begun to "take back Android" from the clutches of meddling manufacturers. Google apps like Gmail and the Google keyboard have been lifted from OS updates and plunked onto the Google Play Store, allowing them to be both downloaded and updated separately from the big OS updates. But with OS skins like Samsung's (OTCMKTS:SSNLF) TouchWiz and HTC's (OTCMKTS:HTCXF) Sense slapped on top of the stock operating system, Android devices from different manufacturers still have a distinctly different look and feel from one another. And all that tinkering not only irritates users who prefer the "Pure Google Experience," it leads to heavy delays for software updates that could have otherwise been immediate if the device was running an un-skinned version of Android.

Well, that all might change with the release of the Google Experience Launcher. What it aims to do, presumably, is unify all the stock and skinned Android devices into a single UI that mimics (or essentially is) stock Android. Not only that, but analysts believe the Google Experience Launcher won't necessarily need 4.4 to run and could be compatible with versions all the way back to 2.2 Froyo, granting Android users with ancient phones the ability to run a current UI. While most of the details remain speculatory, they do fall in line with the company's recent "reacquisition" of Google apps.

Low-End Device and Wearable Support

Speaking of ancient phones, you know fragmentation is bad when devices released just last year may not see an OS update. For Android users, many have seen support disappear even before the contracts with their carriers expire. Of course, the lion's share of the blame lies with the skin-happy manufacturers and the bloatware-touting carriers -- all of whom hope users tire of waiting for an update and simply upgrade their phones. But some of this is due to how older devices simply don't have the muscle to run newer OS platforms.

However, recent rumors have claimed Android 4.4 will support low-end devices and be able to run smoothly despite outdated processor speeds and limited RAM. Also, it could point to compatibility with wearable devices like, say, a watch or a Google Glass.

Open NFC and Better Bluetooth

As Apple (NASDAQ:AAPL) waits to forge headlong into Bluetooth low energy (see: The Biggest iPhone 5S Feature Nobody's Talking About), Google appears to be sticking with near-field communication (NFC) as a possible entry into the future of commerce. But Google Wallet, which used to rely on NFC to work, continues to languish due to a lack of support among retailers, not to mention carriers like Verizon (NYSE:VZ), AT&T (NYSE:T), and T-Mobile (NYSE:TMUS) outright banning it from their phones in favor of an even less-supported NFC payment system called ISIS.

But once again, Android 4.4 is suspected to eschew the heavy hand of carriers. The newer, more open NFC will be able to operate without a secure element like a Google Wallet app. Rather, developers will be able to emulate credit card functionality without needing the secure element to store data. It's still a bit unclear where the information will be stored, but anything that takes power away from carriers is welcome to end users.

Also, Bluetooth support will see an upgrade in Bluetooth HID over GATT and Bluetooth Message Access Profile. This will allow for compatibility and better connectivity with a greater number of devices like joysticks, in-car entertainment systems, and possibly some as-yet-unseen wearable technology.

More Sensors and Native IR Blaster Support

It's pretty incredible that our phones can already act as pedometers and tell which direction is north. But Android 4.4 is tossing in even more sensors to detect how your device moves and is being held. Three new sensor types -- geomagnetic rotation vector, step detector, and step counter sensors -- will have native support in the updated OS. This likely points to the release of more smartwatches that monitor your stride and direction during your morning jogs.

On the other side of the metabolism coin, couch potatoes aren't left out in the new release. Native IR blaster support is coming, giving developers the ability to build more apps that use a phone's IR blaster to control TVs and entertainment systems. This will make phones with built-in IR blasters like Samsung Galaxy S4 and the HTC One the ultimate universal remote controls.

...And the Rest

Although Android 4.4 isn't a full version upgrade, it isn't without its share of changes and enhancements. Transparent navigation bar, white system icons, and altered icons are among some of the different aesthetic changes 4.4 will bring. Plus, better integration with Hangouts and Google Voice will soon mean VoIP will finally be possible (take that, carriers!), and location settings are getting overhauled to be faster and use less battery power.

And then there's the Nexus 5, Google's highly anticipated device in the Nexus line with LTE support over multiple carriers. Specs have already been leaked and the new device is said to rival flagship phones like the iPhone 5S and Samsung Galaxy S4. As excited as fans are for KitKat, the buzz has never been more frenzied for a Nexus release.

 
All that's left is to count the hours until Google officially announces its latest OS and phone.


Baca Selengkapnya ....
Categories:

Research says Samsung sold more smartphones than Apple, BlackBerry and Nokia combined in Q3 2013

Posted by Unknown 0 komentar
 Smartphone sales

Samsung is riding at the top of the smartphone food-chain — let's hope they remember how they got there

I was looking through the data at ABI Research today about Q3 2013 smartphone sales. At first glance, I saw the pie chart I expected to see, with Android having over 80 percent of the worldwide smartphone market and was ready to close the tab. We know Android outsells everyone, and that just wasn't news I wanted to share. But right before I clicked away, a number at the top caught my eye.
Samsung sold 35 percent of all smartphones sold in Q3 of 2013. That's a figure that's fairly easy to come up with in the past if you wanted to do a little work, but there it was, laid out just like that. After a little poking around at their data, and calling in Andrew, our financial and numbers wünderkind, we realized just what that means.
According to ABI Research, Samsung sells more smartphones than Apple, Nokia and BlackBerry combined.
They also sell more than all other Android vendors singly, and likely more than the rest of the top five combined. We don't have that data handy, and aren't about to guess. And quite frankly, none of the other vendors have the history or the weight of total sales behind them that Apple, Nokia and BlackBerry do. It wasn't too awful long ago that they were the big three — the ones to beat, if you like — when it comes to domination of the mobile market.
This matters. Since the huge majority of these are likely to be Android phones (more data we don't have from ABI and won't guess at) it matters even more to us as Android enthusiasts. Samsung is clearly the dominant player in the entire Android ecosystem. If you had any doubts before, wash them away.
We just got finished seeing all the new tools Samsung is using to attract more interest in their smartphones. Regardless of what you may read elsewhere, this was an event centered around five new SDKs, four of which were Android only and one that was Android, iOS and JavaScript / HTML 5 (for the multiple screen APIs). Samsung is certainly all-in with Android, and Google has carried them to the top of smartphone mountain by giving them Android to fold, spindle and mutilate as they please.
Google has carried Samsung to the top of smartphone mountain
With their new push for the enterprise market, these numbers are going to grow. You and I may not be enamored with things like boosted security and Knox support, but we don't matter to Samsung. We're outliers. Samsung will spend the money to do what it takes for their phones to be as popular in a business environment as they are with us "common" folks. That's good news for people forced to use locked-up corporate phones. Let's hope Samsung also starts to offer more "developer" phones without all the extra security — and that people see the benefit in buying them.
For now, all this is still a good thing. Samsung isn't likely to abandon an entire platform that someone else writes for them and improves yearly for free, but we also need to watch closely. Samsung will do what is best for Samsung, like any other company. I don't expect Samsung to suddenly really care about Tizen, or provide more than the token support they now offer (note that I am a Tizen fan, I'm just realistic knowing that Samsung doesn't really care about it). Not when Google does the heavy lifting for them, and they are still free to make it Samsung on the top. But I can't completely ignore the Chicken Littles out there who are certain Samsung is ready to leave Android and ruin everything — because if they did, things would not be pretty for Android sales and support.

Baca Selengkapnya ....
Categories:

Voice commands In Google Glass firmware's new feature: Exclusive report

Posted by Unknown Kamis, 24 Oktober 2013 0 komentar

As our report on the latest Google Glass firmware hints at what features may come to Google's high-tech gadget & also its source of uses.

Google seems to be preparing many more features for Google Glass ahead of an eventual public launch. An examination of the latest Google Glass firmware by Android Police hints at what features may come to Google's high-tech specs. Most notably, users could have a much longer list of voice commands to work with.
Here's the full list of new commands that Android Police spotted in the firmware:
  • Add a Calendar Event
  • Call Me a Car
  • Capture a Panorama
  • Check Me In
  • Create a 3D Model
  • Find a Recipe
  • Learn a Song
  • Play a Game
  • Play Music
  • Record a Recipe
  • Remind Me To...
  • Show a Compass
  • Start a Bike Ride
  • Start a Round of Golf
  • Start a Run
  • Start a Stopwatch
  • Start a Timer
  • Translate This
  • Tune an Instrument

This is simple, everyone wanted to use all this staff in one, check for this

Apps may provide some features
 
Keep in mind that not all Glass functions are built in by default. Some of them are enabled by third-party apps. (For instance, Glass users can currently say "Take a Note" to record their thoughts in Evernote.) Commands such as "Tune and Instrument" or "Start a Bike Ride" could very well be tied to a third-party app. Right now, the app selection on Glass is tightly restricted, but that could change with a proper app store coming next year when the device is supposedly coming available to the general public.
Related to the "Play Music" functionality, the latest firmware hints at music controls coming to Glass, with mentions of album art, track listings, and a radio icon. It's possible that users could someday play music through the device, but the more-likely possibility is remote playback controls for other devices, such as televisions and tablets.
The other big discovery is the theoretical expansion of eye controls for Glass, with a "double blink" detector mentioned in the firmware. I say "theoretical" because Google does not officially support eye control, though the unsanctioned " Winky" app allows users to snap photos with a blink. Google is treading lightly with eye controls due to the privacy implications, but we do know the company is interested in eye tracking as an advertising tool.
The current "Explorer Edition" of Google Glass is only available to a limited number of people who filled out an application, at a price of $1,500. Google hasn't said when it will launch a final product for consumers, but sometime next year seems likely. In the meantime, some of the features of Glass, such as Google Now integration , could also find their way into a smartwatch if recent rumors prove accurate.

wanted in touch with google & Apps, stay in touch with MakersOfAndroid 

Suhan Gorya

Baca Selengkapnya ....
Categories:

Why Apple Wants Its Software to Be Free??

Posted by Unknown Selasa, 22 Oktober 2013 0 komentar

Fear Or Plan ?


Craig Federighi, senior vice president of software engineering at Apple, unveils the new OS X at the Yerba Buena Center in San Francisco

Craig Federighi, senior vice president of software engineering at Apple, unveils the new OS X at the Yerba Buena Center in San Francisco

Who knew Apple would become such a big shareware company?
Today’s product event in San Francisco will be known more for the introduction of new iPads, MacBooks, and Mac Pros, but what might be even more interesting is how Apple has decided to give away key software for free, including its long-awaited upgrade to Mac OS X, code-named Mavericks.
Mavericks and two other software suites, iWork and iLife, are now available for download free of charge. This continues an ongoing trend at Apple of lowering software prices—the previous version of Mac OS X, Mountain Lion, cost only $30. Compare that with Microsoft (MSFT), which charges $120 for the base version of its latest operating system, Windows 8.1, and $200 for Windows 8.1 Pro.

By going free, Apple has acknowledged something that’s been true in the industry for years: Software is a means to sell hardware. Sure, there are some specialized applications that can command a hefty profit margin, but bread-and-butter applications used in the mainstream are not things you sell. They are things people get when they turn on that shiny new object they just shelled out for.
This runs counter to Microsoft’s DNA as—at least until very recently—a software company. And let’s give Redmond some credit: That strategy worked really, really well for a while. But just as there’s been a shift in interest to well-designed devices (as opposed to the beige boxes that defined the PC era), so has there been an expectation that software be as seamless and costless as possible. Your browser is free, so is Gmail/Yahoo Mail/etc. and Google Maps doesn’t cost anything.
Apple’s strategy here is to get you on a device and with the latest version of its software as quickly and painlessly as possible. Does it want to get caught up in the intricacies of a pricing scheme for OS X Mavericks? No, it does not. Better to just remove price as a consideration and make it part of the device you’re using. Apple Chief Executive Officer Tim Cook likes to talk about the perfect integration of hardware and software that Apple aims to achieve. By making OS X, iLife, and iWork free of charge, it can achieve that goal even faster.
Suhan Gorya.

Baca Selengkapnya ....
Categories:

(New Record) BBM Appliication installation in its first day on Android more than 1 million: Update Review

Posted by Unknown 0 komentar


BBM is again on top, but not by its own. This time  because of Android. check out
We're getting our first look at the popularity of the recently released BBM for Android. Fresh out of the gate, the Google Play listing has placed the app in the 1 million to 5 million category. Those are total installations, and not "current" installs, so you've got to keep those numbers in context. Still. More than 1 million installs — and potentially as many as 5 million (we've got an e-mail in seeking more specific numbers) in a day is nothing to sneeze at.
Additionally, BBM's garnered more than 87,000 star reviews on Google Play — with the vast majority a full five stars.
A pretty big caveat, though — remember that there's a waiting list. So you can install the app, but you might not be able to use it just yet.
It's also worth keeping in mind that BBM doesn't work on nearly 30 percent of existing Android phones. BBM runs on Android 4.*, which as of the beginning of October made up 69 percent of active devices, according to the Android platform versions chart.
But either way, it's pretty damned impressive for BlackBerry — and for what many of us consider a dying platform.
Sure, but we can say, its was good for android user or for BBM?

Suhan Gorya



Baca Selengkapnya ....
Categories:

Nokia Duel boot phone Vs Android: Officeil update.

Posted by Unknown Senin, 21 Oktober 2013 0 komentar

"I am pretty sure there are many peoples like me who are sick of *Nokia Must Go Android* argument."

Nokia and Microsoft Windows Phone

I have explained it many times in comments the reasons why Nokia mustn’t go with Android but I guess a entire article must be necessary to get those people to understand why Nokia shouldn’t Go Android (However, I am sure they won’t understand this either).
1. Android is Big Pond with so many fishes and even sharks. Nokia is what I define right now is the wounded fish which is trying to recover, however when you jump on a big pond with so many threats its not easy to survive.
2. Now there are peoples who suggest that Nokia should go for Android as well as Windows Phone. No matter how bright this idea sounds it has its cons that are enough to suggest that its a bad decision
a. Android has so many OEMs and so many options even if Nokia makes an Android Phone how are they supposed to differentiate from the crowd, sure 1020 is super different but just based on that who wanna buy all products Nokia will put out?
b. Given Nokia has what you call Best Brand Value it still doesn’t have a brand value inside of Android for example like Samsung has with Galaxy.
c. Jumping on two boats is never a smart option
d. They will lose their identity as only Windows Phone Maker.
e. Nokia is not healthy enough to push android devices not enough capital to experiment(NSN Purchase)
3. Android is a Open Source OS with every XYZ company making a SmartPhone and also calling it the *Best SmartPhone Ever*, so small players will eventually phase out Samsung, LG, Sony etc etc. Don’t believe me? Read the IDC analysis it will give you a hint of future of Android.
4. Microsoft practically plays nice with Nokia because Nokia is making their Windows Phone a Viable Option, Yes I love Microsoft but truth be told if it wasn’t for Nokia, Windows Phone would have been over by now. So now when Nokia faces issues Sugar daddy is there and if Nokia goes android they are giving away a reason for MIcrosoft to back away.
5. Think about Nokia what comes in your Mind, whatever the thoughts are i am sure Windows Phone is also a part of it, so when someone shows their android phone to me I pull out my Lumia from my pocket and frankly they are like WOW. Because its different not blends in with crowd of Android Phones from every cheap company ever.
6. Windows Phone are taking of now, Yes it wasn’t this late Elop has thought but strategy is paying off, sales of Lumias are increasing every quarter that’s a positive sign.
7. Nokia is a company I know from my early days of phones, Playing Space Impact, Snake, Taking my first Photograph from a phone ever and I am sure many peoples have same memories and have a special place for Nokia and by being different from crowd they make em special(I know this one doesn’t have much logic but in all fairness i am a Nokia Fan)
So, these are my reasons for why Nokia shouldn’t go Android what you all think?

Baca Selengkapnya ....
Categories:

Galaxy Note 10.1 - 2014 Edition spotted in U.K. sporting 16GB of storage for £499

Posted by Unknown 0 komentar


Galaxy Note 10.1 - 2014 Edition

Tablet to actually go on sale to consumers next week

We're just over a week since the Galaxy Note 10.1-2014 Edition made its way to the U.S., and now the latest big tablet from Samsung is popping up at U.K. retailers. A reader has just sent in this image from a Currys/PC World in the U.K. where the tablet is up on display at £499.99 for 16GB of storage and Wifi connectivity. Interestingly the processor is listed as "quad core," even though the model hitting the U.S. is an octa-core (but we wouldn't be surprised if this was a typo in the end).
The tipster indicates that the store will actually sell you one starting next week, even though they're already on display this weekend. We don't have any other solid indication of pricing or availability at other stores, although some online retailers such as Clove have the tablet listed at £479.99 for the Wifi model.

Suhan Gorya


Baca Selengkapnya ....
Categories:

Sony SmartWatch 2 is IP57 water and dust resistant

Posted by Unknown 0 komentar



Sony SmartWatch 2

The Sony SmartWatch 2 doesn't mind a little dunk or three

There seems to be a little confusion out there among wearable enthusiasts and soon-to-be wearable enthusiasts about the Sony SmartWatch 2 and any level of water resistance. A representative of the company has assured me that the SW2 is indeed IP 57 rated for water and dust resistance. This is the same as the Xperia Z, and it means:
  • 5: Ingress of dust is not entirely prevented, but it must not enter in sufficient quantity to interfere with the satisfactory operation of the equipment.
  • 7: Ingress of water in harmful quantity shall not be possible when the enclosure is immersed in water under defined conditions of pressure and time (up to 1 m of submersion). 
That's all I needed to hear. Hit the break to see the Sony SmartWatch 2 meeting a glass of ice-cold West Virginia mountain spring water.

Suhan Gorya


Baca Selengkapnya ....
Categories:

Nexus 5 makes a brief appearance on Google Play, listed at $349

Posted by Unknown 0 komentar

Nexus 5 Review:


Nexus 5

The tag line, as you can see, reads:
"Capture the everyday and the epic in fresh new ways. Starting at $349."
That's a pretty good sign that we'll see more than one SKU (aka retail version), meaning we'll (obviously) see more than one storage size. 16-gigabyte version, so that's a pretty good starting point. also points to a "black" version — a pretty good indication we might see other colors as well. Figure white, of course.
For more information about Android device and system check
Suhan Gorya

Baca Selengkapnya ....
Categories:

Android 4.4 KitKat May Be Dominated By The 'Google Experience'

Posted by Unknown Jumat, 18 Oktober 2013 0 komentar


Today`s hot topic, everyone wanted to know, what will the next step of android, If we piece together some of the rumors swirling around what Android 4.4 will entail and combine it with what we know about how Google has been updating Android and its pertinent features over the last year, we get a pretty good idea. 
It leads us to a new Android experience. What some people are calling “the Google Experience.”

Waiting For The Big Android Update

Android 4.4 KitKat is expected to be announced by the end of October. The hype cycle is beginning to hit full tilt as stream of leaks and rumors illuminate what Google will unveil the next version of Android and the flagship smartphone that will accompany it, the Nexus 5.
KitKat will be the first new named version of Android in more than a year since Jelly Bean 4.1 was introduced at Google’s I/O developer conference in the spring of 2012. Google has offered up two updates to Android since then—versions 4.2 and 4.3—that have both been rolled up in the Jelly Bean moniker. Now that Google is almost ready to unveil the “K” desert version of Android (Google normally names each new version of the operating system after sweet treats in alphabetical order), users, developers, manufacturers and consumers are expecting a lot.
The last two versions of Jelly Bean haven’t given us a ton to be excited about. The biggest feature in version 4.3 was the integration of Bluetooth Low Energy to the Android hardware specification along with OpenGL for Embedded Systems. These are good updates for app developers out there but leave much to be desired for users that are looking for a fresh coat of paint and improved user experience. 

The Google Experience

In that vein, the rumor mill points towards a major feature that will change some of the fundamental usability of Android: the “Google Experience.” 
Source: Android Police
The Google Experience Launcher is rumored to be a hub launcher for Google apps and widgets on Android devices. Google Experience will be a form of launcher within Android that will not be tied specifically to version 4.4 KitKat but will rather be an app through the Google Play app store that will be compatible with devices running Android back to version 2.2 Froyo. 
A launcher is also known in general terms as a “skin” but the terms are not mutually exclusive. The Google Experience Launcher is rumored by the blog Android Police to be a widget that live on the Android homescreen in which Google features like Search and Google Now are heavily integrated, can read the data within the widget and update itself. A launcher would also control aspects such as app folders and homescreens (which are rumored to be infinite instead of limited to five as they are in current builds of Android).
What would Google Experience mean for Android users? Speculation is that KitKat 4.4 will enable support for lower-end Android devices. Google Experience would likely be the vehicle for that. 
If you have been following the evolution of Android as an operating system, you will note that the Google has made some pretty significant changes to how Android works on a smartphone. In the past, Google used to tie almost all of the functionality of its own apps to the Android kernel. That meant developers and consumers would need a certain version of Android to get new features. Wanted the latest update to the Google Play app store (formerly Android Market)? You needed to update your Android software. How about the latest APIs and user interface in Google Maps and Navigation? Update Android. Gmail, Calendar, Talk (now Hangouts) or any other Google service? It was tied to the Android kernel.
Google changed all of that with the release of Android 4.1 Jelly Bean, decoupling its own apps from the Android operating system. Instead of being tied to Android, features and APIs like Maps either stand alone as their own apps that live in the Google Play store and/or are tied to what is called Google Play Services.

Google Experience As A Front-End Extension Of Google Play Services

Google Play Services is what is known in the computing world as a “shim.” Here is the definition of a shim, from Wikipedia:
In computer programming, a shim (from shim) or shiv is a small library that transparently intercepts an API and changes the parameters passed, handles the operation itself, or redirects the operation elsewhere. Shims typically come about when the behavior of an API changes, thereby causing compatibility issues for older applications which still rely on the older functionality. In such cases, the older API can still be supported by a thin compatibility layer on top of the newer code. Web polyfills are a related concept. Shims can also be used for running programs on different software platforms than they were developed for.
In Android, Google Play Services is a stand-alone app that runs in the background. It updates itself with functionality directly from Google without the user doing anything. It downloads its own code and enacts its own functionality. For example, if there is an update to the Google Play Store or Maps, it is downloaded and implemented through Google Play Services. 
If the Google Experience is really going to be a primary feature in KitKat 4.4, as the rumors say it will, then what Google is doing is giving Google Play Services a front-end user interface for Android devices. 
By extension, the Google Experience can be transported back to older versions of Android. If we look at the definition of a shim in that, “the older API can still be supported by a thin compatibility layer on top of the new code” then it is possible for Google to bring just about all of the Android features and functionality that are not explicitly tied to hardware back to any phone running a previous version of Android. 
 Suhan  Gorya

Baca Selengkapnya ....
Categories:

Android 4.4 KitKat release date expected on October 28: Top features, Suhan Gorya

Posted by Unknown 0 komentar


latest on news: check the date below


Here something interesting is in waiting, Finally after a long wait there seems to be some hope that Android 4.4 KitKat release date is set for October 28. The new version will come with top features and will further enrich Android OS.  
The frenzy-awaited Android 4.4 KitKat gets official release date. It is likely to go public on Oct. 28, just around the date we got Android 4.2 JB update last year (Oct. 29). Though Google surfaced codename of the next Android update, the company has for the first time shared a clue on its release date through a funny teaser via Twitter.
KitKat has shared a teaser image that just scribbles “THIS IS IT” in the central part and “Have a Break, Have a KitKat” in the bottom. Though the teaser doesn’t explicitly mention the release date, the words “THIS IS IT” tell everything, referring to Oct. 28 release as Michael Jackson’s popular film of the same title was released on Oct. 29 back in 2009.
It means that we are most likely to get the next Android version released on Oct. 28. The new software update, as anticipated, will be premiering in the next Google Nexus 5, which is reportedly under making at LG, developer of the last year Nexus 4 as well. Alongside Nexus 5, Google may also surface its next edition Nexus 10 with the KitKat under the hood.
KitKat is going to be one of the most radical versions of Android mobile OS. In battle to the iOS 7 and Windows Phone 8.1, Google might design it as a feature-rich alternative with a lot of exciting features and upgrades. One most important thing expected for the KitKat is its ability to support all devices even including the ones with basic and meager specs.
As you will simple guess, the name KitKat derives from Nestle’s chocolate bars of the same name. Google has struck a deal with Nestle to name its next Android version so as part of a mutual product marketing campaign.
 Suhan Gorya

Baca Selengkapnya ....
Categories:

Full Tutorial on android application developer by Suhan Gorya

Posted by Unknown Kamis, 17 Oktober 2013 0 komentar

Suhan Gorya

This time i come with the tutorial, about how to make new Android application,
if any problem or error occurred during the programming tutorial, just tell me or E-mail  me, will reply you with solution. 
so now try it, surely you will feel good to be application developer, here is the steps, simply follow the tutorial given as:

 

1. What You Need to Begin


Because Android applications run within the Dalvik VM, you can write them on any platform that
supports the developer tools. This currently includes the following
a. Microsoft Windows (XP or later)
b. Mac OS X 10.5.8 or later (Intel chips only)
c. Linux (including GNU C Library 2.7 or later)

2. To get started, you’ll need to download and install the following:


1.The Android SDK starter package
2.Java Development Kit (JDK) 5 or 6 

You can download the latest JDK from Sun at http://java.sun.com/javase/downloads/index.jsp.

3. Downloading and Installing the Android SDK


There’s no cost to download or use the API, and Google doesn’t require your application to pass a review to distribute your finished programs on the Google Play Store. Although the Google PlayStore requires a small one-time fee to publish applications, if you chose not to distribute via the Google Play Store, you can do so at no cost.
 
You can download the latest version of the SDK starter package for your chosen development platform from the Android development home page at
 http://developer.android.com/sdk/index.html

Unless otherwise noted, the version of the Android SDK used for writing this was version 4.3 (API level 18).
As an open-source platform, the Android SDK source is also available for you to
download and compile from http://source.android.com.

The starter package is a ZIP fi le that contains the latest version of the Android tools required to
download the rest of the Android SDK packages. Install it by unzipping the SDK into a new folder.
Take note of this location, as you’ll need it later.

If you are developing from a Windows platform, an executable Windows installer is available (and recommended) as an alternative to the ZIP fi le for installing the platform tools.
Before you can begin development, you need to download at least one SDK platform release. You can do this on Windows by running the SDK Manager.exe executable, or on Mac OS or Linux by running the “android’’ executable in the tools subfolder of the starter package download.

The screen that appears (see Figure-1) shows each of the packages available for the download. This includes a node for the platform tools, each of the platform releases, and a collection of extras, such as the Android Support Package and billing/licensing packages.


 FIGURE-1

You can expand each platform release node to see a list of the packages included within it, including the tools, documentation, and sample code packages.
To get started, simply check the boxes corresponding to the newest framework SDK and the latest
version of the tools, compatibility/support library, documentation, and sample code.
 
FIGURE-1
For testing the backward compatibility of your applications, it can often be useful
to download the framework SDK for each version you intend to support.
To use the Google APIs (which contain the Maps APIs), you also need to select the Google APIs by
Google package from the platform releases you want to support.

When you click the Install Packages button, the packages you’ve chosen will be downloaded to your SDK installation folder. The result is a collection of framework API libraries, documentation, and several sample applications.
The examples included in the SDK are well documented and are an excellent
source for full, working examples of applications written for Android. When you
fi nish setting up your development environment, it’s worth going through them.
Downloading and Installing Updates to the SDK As new versions of the Android framework SDK, developer tools, sample code, documentation,compatibility library, and third-party add-ons become available, you can use the Android SDK Manager to download and install those updates.

All future packages and upgrades will be placed in the same SDK location.


4. Developing with Eclipse


The examples and step-by-step instructions in this tutorial are targeted at developers using Eclipse with the Android Developer Tools (ADT) plug-in. Neither is required, though; you can use any text editor or Java IDE you’re comfortable with and use the developer tools in the SDK to compile, test, and debug the code snippets and sample applications.
As the recommended development platform, using Eclipse with the ADT plug-in for your Android development offers some significant advantages, primarily through the tight integration of many of the Android build and debug tools into your IDE.
 
Eclipse is a particularly popular open-source IDE for Java development. It’s available for download for each of the development platforms supported by Android (Windows, Mac OS, and Linux) from the Eclipse foundation (www.eclipse.org/downloads).
Many variations of Eclipse are available, with Eclipse 3.5 (Galileo) or above required to use
the ADT plugin. The following is the configuration for Android used in the preparation of
this tutorial:

a. Eclipse 3.7 (Indigo) (Eclipse Classic download)
b. Eclipse Java Development Tools (JDT) plug-in
c. Web Standard Tools (WST)
 
The JDT plug-in and WST are included in most Eclipse IDE packages.
Installing Eclipse consists of uncompressing the download into a new folder, and then running the eclipse executable. When it starts for the fi rst time, you should create a new workspace for your Android development projects.
Using the Android Developer Tools Plug-In for Eclipse The ADT plug-in for Eclipse simplifi es your Android development by integrating the developer tools, including the Emulator and .class-to-.dex converter, directly into the IDE. Although you don’t have to use the ADT plug-in, it can make creating, testing, and debugging your applications faster and easier.
 
The ADT plug-in integrates the following into Eclipse:
 
a. An Android Project Wizard, which simplifies creating new projects and includes a basic
application template
b. Forms-based manifest, layout, and resource editors to help create, edit, and validate your
XML resources
c. Automated building of Android projects, conversion to Android executables (.dex), packaging to package fi les (.apk), and installation of packages onto Dalvik VMs (running both
within the Emulator or on physical devices)
d. The Android Virtual Device manager, which lets you create and manage virtual devices to
host Emulators that run a specifi c release of the Android OS and with set hardware and
memory constraints
e. The Android Emulator, including the ability to control the Emulator’s appearance and network
connection settings, and the ability to simulate incoming calls and SMS messages
f. The Dalvik Debug Monitoring Service (DDMS), which includes port forwarding, stack, heap,
and thread viewing, process details, and screen-capture facilities
g. Access to the device or Emulator’s fi lesystem, enabling you to navigate the folder tree and
transfer fi les
h. Runtime debugging, which enables you to set breakpoints and view call stacks
i. All Android/Dalvik log and console outputs
 

5.Installing the ADT Plug-In

Install the ADT plug-in by following these steps:
1. Select Help Í Install New Software from within Eclipse.
2. In the Available Software dialog box that appears, click the Add button.
3. In the next dialog, enter a name you will remember (e.g., Android Developer Tools) into the
Name fi eld, and paste the following address into the Location text entry box: 
https://dl-ssl.google.com/android/eclipse/

4. Press OK and Eclipse searches for the ADT plug-in. When fi nished, it displays the available
plug-ins, as shown in Figure 2-3. Select it by clicking the check box next to the Developer
Tools root node, and then click Next.



FIGURE 2
5. Eclipse now downloads the plug-in. When it finishes, a list of the Developer Tools displays
for your review. Click Next.
6. Read and accept the terms of the license agreement, and click Next and then Finish. As the
ADT plug-in is not signed, you’ll be prompted before the installation continues.
7. When installation is complete, you need to restart Eclipse and update the ADT preferences.
Restart and select Window Í Preferences (or Eclipse Í Preferences for Mac OS).
8. Select Android from the left panel.
9. Click Browse, navigate to the folder into which you installed the Android SDK, and then
click Apply. The list updates to display each available SDK target.
Click OK to complete the SDK installation.

 

 

6. Updating the ADT Plug-In


In most cases, you can update your ADT plug-in simply as follows:
1. Navigate to Help Í Check for Updates.
2. If there are any ADT updates available, they will be presented. Simply select them and choose
Install.
Sometimes a plug-in upgrade may be so signifi cant that the dynamic update mechanism
can’t be used. In those cases you may have to remove the previous plug-in
completely before installing the newer version, as described in the previous section.
Using the Support Package
The support library package (previously known as the compatibility library) is a set of static libraries that you can include as part of your projects to gain either convenience APIs that aren’t packaged as part of the framework (such as the View Pager), or useful APIs that are not available on all platform releases (such as Fragments).
The support package enables you to use framework API features that were introduced in recent
Android platform releases on any device running Android 1.6 (API level 4) and above. This helps you provide a consistent user experience and greatly simplifi es your development process by reducing the burden of supporting multiple platform versions.

1. Add a new /libs folder in the root of your project hierarchy.
2. Copy the support library JAR fi le from the /extras/android/support/ folder in your
Android SDK installation location.
 
You’ll note that the support folder includes multiple subfolders, each of which represents
the minimum platform version supported by that library. Simply use the corresponding JAR
fi le stored in the subfolder labeled as less than or equal to the minimum platform version
you plan to support.
For example, if you want to support all platform versions from Android 1.6 (API level 4)
and above, you would copy v4/android-support-v4.jar.
3. After copying the file into your project’s /libs folder, add it to your project build path by
right-clicking in the Package Explorer and selecting Build Path Í Add to Build Path.


7. Creating Your First Android Application


You’ve downloaded the SDK, installed Eclipse, and plugged in the plug-in. You are now ready to start programming for Android. Start by creating a new Android project and setting up your Eclipse run and debug confi gurations, as described in the following sections.
 

Creating a New Android Project
To create a new Android project using the Android New Project Wizard, do the following:
1. Select File Í New Í Project.
2. Select the Android Project application type from the Android folder, and click Next.
3. In the wizard that appears, enter the details for your new project. On the fi rst page
(Figure 3), the Project Name is the name of your project fi le. You can also select the location
your project should be saved.
 

4. The next lets you select the build target for your application. The build target is the version of the Android framework SDK that you plan to develop with. In addition
to the open sourced Android SDK libraries available as part of each platform release, Google
offers a set of proprietary APIs that offer additional libraries (such as Maps). If you want to
use these Google-specific APIs, you must select the Google APIs package corresponding to the platform release you want to target.
Your project’s build target does not need to correspond to its minimum SDK or
target SDK. For new projects it’s good practice to build against the newest version
of the SDK to take advantage of effi ciency and UI improvements in newer platform releases.
5. The final step allows you to specify the application properties. The Application
Name is the friendly name for your application; the Package Name specifies its Java package;
the Create Activity option lets you specify the name of a class that will be your initial
Activity; and setting the Minimum SDK lets you specify the minimum version of the SDK
that your application will run on.

Selecting the minimum SDK version requires you to choose the level of backward
compatibility you want to support to target a wider group of Android devices.
Your application will be available from the Google Play Store on any device
running the specifi ed build or higher.
At the time of this writing, more than 98% of Android devices were running
at least Android 2.1 (API level 7). The latest Ice Cream Sandwich SDK is
4.3 (API level 18).
6. When you’ve entered the details, click Finish.
If you selected Create Activity, the ADT plug-in will create a new project that includes a class that extends Activity. Rather than being completely empty, the default template implements Hello World. Before modifying the project, take this opportunity to confi gure launch 
configurations for running and debugging.
 
Creating an Android Virtual Device
AVDs are used to simulate the hardware and software confi gurations of different Android devices, allowing you test your applications on a variety of hardware platforms.
There are no prebuilt AVDs in the Android SDK, so without a physical device, you need to create at least one before you can run and debug your applications.

1. Select Window Í AVD Manager (or select the AVD Manager icon on the Eclipse toolbar).
2. Select the New... button.
The resulting Create new Android Virtual Device (AVD) dialog allows you to confi gure a
name, a target build of Android, an SD card capacity, and device skin.
3. Create a new AVD called “My_AVD” that targets Android 4.0.3, includes a 16MB SD Card,
and uses the Galaxy Nexus skin, as shown in Figure 2-8.
4. Click Create AVD and your new AVD will be created and ready to use.
 
Creating Launch Confi gurations
Launch confi gurations let you specify runtime options for running and debugging applications.
Using a launch confi guration you can specify the following:
a. The Project and Activity to launch
b. The deployment target (virtual or physical device)
c. The Emulator’s launch parameters
d. Input/output settings (including console defaults)

You can specify different launch configurations for running and debugging applications. The following
steps show how to create a launch configuration for an Android application:
1. Select Run Configurations… or Debug Configurations… from the Run menu.
2. Select your application from beneath the Android Application node on the project type list,
or right-click the Android Application node and select New.
3. Enter a name for the configuration. You can create multiple configurations for each project,
so create a descriptive title that will help you identify this particular setup.
4. Choose your start-up options. The first (Android) tab lets you select the project to run and
the Activity that you want to start when you run (or debug) the application. Figure 2-9
shows the settings for the project you created earlier.
5. Use the Target tab, as shown in Figure 2-10, to select the default virtual device to launch on,
or select Manual to select a physical or virtual device each time you run the application. You
can also confi gure the Emulator’s network connection settings and optionally wipe the user
data and disable the boot animation when launching a virtual device.

The Android SDK does not include a default AVD, so you need to create one
before you can run or debug your applications using the Emulator. If the Virtual
Device selection list in Figure 2-10 is empty, click Manager... to open the Android
Virtual Device Manager and create one as described in the previous section.
Further details on the Android Virtual Device Manager are available later in this
chapter.
6. Set any additional properties in the Common tab.
7. Click Apply, and your launch configuration will be saved.


8. Running and Debugging Your Android Application

You’ve created your first project and created the run and debug confi gurations for it. Before making any changes, test your installation and confi gurations by running and debugging the Hello World project.
From the Run menu, select Run or Debug to launch the most recently selected confi guration, or
select Run Configurations… or Debug Configurations… to select a specific configuration.
If you’re using the ADT plug-in, running or debugging your application does the following:
a. Compiles the current project and converts it to an Android executable (.dex)
b. Packages the executable and your project’s resources into an Android package (.apk)
c. Starts the virtual device (if you’ve targeted one and it’s not already running)
d. Installs your application onto the target device
e. Starts your application
If you’re debugging, the Eclipse debugger will then be attached, allowing you to set breakpoints and debug your code.
If everything is working correctly, you’ll see a new Activity running on the device or in the
Emulator, 



Understanding Hello World
Take a step back and have a good look at your fi rst Android application.
Activity is the base class for the visual, interactive components of your application; it is roughly
equivalent to a Form in traditional desktop development 


“Creating Applications and Activities”). 
 Hello World

 
package suhan.gorya.helloworld;
import android.app.Activity;
import android.os.Bundle;
public class MyActivity extends Activity {
/** Called when the Activity is first created. **/
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
}
}
code snippet Suhan_gorya_HelloWorld/src/MyActivity.java
In Android, visual components are called Views, which are similar to controls in traditional desktop development. The Hello World template created by the wizard overrides the onCreate method to call setContentView, which lays out the UI by infl ating a layout resource, as highlighted in bold in the following snippet:

@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
}

The resources for an Android project are stored in the res folder of your project hierarchy, which
includes layout, values, and a series of drawable subfolders. The ADT plug-in interprets these
resources to provide design-time access to them through the R variable,
 
Listing shows the UI layout defined in the main.xml file created by the Android project template
and stored in the project’s res/layout folder.
 
LISTING Hello World layout resource

<?xml version=”1.0” encoding=”utf-8”?>
<LinearLayout xmlns:android=”http://schemas.android.com/apk/res/android”
android:orientation=”vertical”
android:layout_width=”fill_parent”
android:layout_height=”fill_parent”>
<TextView
android:layout_width=”fill_parent”
android:layout_height=”wrap_content”
android:text=”@string/hello”
/>
</LinearLayout>

code snippet Suhan_Gorya_HelloWorld/res/layout/main.xml
Defining your UI in XML and infl ating it is the preferred way of implementing your user interfaces (UIs), as it neatly decouples your application logic from your UI design.
To get access to your UI elements in code, you add identifi er attributes to them in the XML definition.You can then use the findViewById method to return a reference to each named item. The following XML snippet shows an ID attribute added to the Text View widget in the Hello World template:

<TextView
android:id=”@+id/myTextView”
android:layout_width=”fill_parent”
android:layout_height=”wrap_content”
android:text=”@string/hello”
/>

And the following snippet shows how to get access to it in code:
TextView myTextView = (TextView)findViewById(R.id.myTextView);
Alternatively (although it’s not generally considered good practice), you can create your layout
directly in code, as shown in Listing 


LISTING : Creating layouts in code
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
LinearLayout.LayoutParams lp;
lp = new LinearLayout.LayoutParams(LinearLayout.LayoutParams.FILL_PARENT,
LinearLayout.LayoutParams.FILL_PARENT);
LinearLayout.LayoutParams textViewLP;
textViewLP = new LinearLayout.LayoutParams(
LinearLayout.LayoutParams.FILL_PARENT,
LinearLayout.LayoutParams.WRAP_CONTENT);
LinearLayout ll = new LinearLayout(this);
ll.setOrientation(LinearLayout.VERTICAL);
TextView myTextView = new TextView(this);
myTextView.setText(getString(R.string.hello));
ll.addView(myTextView, textViewLP);
this.addContentView(ll, lp);
}
code snippet Suhan_gorya_Manual_Layout/src/MyActivity.java

All the properties available in code can be set with attributes in the XML layout.
More generally, keeping the visual design decoupled from the application code helps keep the code concise. With Android available on hundreds of different devices of varying screen sizes, defining your layouts as XML resources makes it easier for you to include multiple layouts optimized for different screens.


So far this is the end of the todays tutorial ,
create and enjoy the application,,
if any error occur just tweet me or comment,
enjoy.

Suhan Gorya

Baca Selengkapnya ....
Categories:
Trik SEO Terbaru support Online Shop Baju Wanita - Original design by Bamz | Copyright of android apple.
Diberdayakan oleh Blogger.