Samsung testing Samsung Pay with local companies to address difficulties
Samsung is believed to be targeting the announcement of the Samsung Galaxy Note 5 in September as the official launch of their new Samsung Pay platform. Samsung Pay was already delayed from a joint launch with the Samsung Galaxy S6 earlier this year. However, Samsung reportedly is struggling with technical issues prompting the company to test with local companies to get more “real world” feedback. Sources indicate Samsung is having trouble getting the system to work as smoothly as desired, especially with older equipment still used by retailers.
Samsung Pay, which incorporates technology from Samsung’s acquisition of Loop Pay, is unique in that will create a magnetic field that replicates the magnetic strip found on the back of credit and debit cards. This means Samsung Pay could be used at existing pay terminals that retailers already have installed rather than requiring an investment in NFC capable readers.
Samsung is apparently dealing with two different issues in getting the system to run in a manner that will encourage its use by consumers. First, the process of authenticating using a fingerprint sensor built into a smartphone that then triggers the magnetic field for a given card is still experiencing a high number of errors. Second, the huge number of different pay terminals – over 100 with more than half over 10 years old – is presenting problems in getting the pseudo-magnetic strips to be recognized.
Samsung really needs the platform to work as smoothly as possible in order to see it become widely adopted. Existing pay systems from other vendors continue to struggle in the marketplace for acceptance. The inclusion of the magnetic field technology is believed to be a key to Samsung’s success as it eliminates the “will it work or not” question consumers may have when trying to use Samsung Pay at a retailer.
source: BusinessKorea
Come comment on this article: Samsung testing Samsung Pay with local companies to address difficulties
#ICYMI: NFC Cognac Caps, play a Virtual Neymar, and More
![]()
Today on In Case You Missed It: Remy Martin installs NFC-enabled caps on its cognac bottles to prevent shady saloons from pulling the old switcheroo, Nike lets Google Cardboard users to play soccer as Neymar Jr., and a London-based artist creates custom Power Gloves that can carve through wood and stone.
From the cutting room floor: This Auburn Fire Department quadcopter makes a special delivery of lifejackets and tow lines to a couple of guys stranded in the middle of a river.
Let the team at Engadget know about any interesting stories or videos you stumble across by using the #ICYMI hashtag @engadget or @mskerryd.
Casio preparing to enter the smartwatch field
The smartwatch industry has a new player ready to enter, this time coming from the world of watchmakers hoping to add some “smarts” to its devices instead of a tech company looking to cram smarts into a watch form factor. Casio has revealed plans to produce a smartwatch for release in 2016. With the company’s history, the move to finally get into the market should probably not be a surprise.
In the past Casio has managed to tack on all sorts of technology and gadgets on its watches. These have ranged from the now seemingly mundane calculator to heart-rate monitors, digital cameras, and even portable gaming systems. Casio’s new president, Kazuhiro Kashio, admits that, “at times we just showed off with quirky features and then pulled those products when they didn’t sell well.”
Despite the success and failure of past devices from Casio, the company does have a solid history of understanding consumers in the watch marketplace and their desire for something easy to use, durable, and a pleasure to wear.
Kashio, who recently took over leadership at Casio from his father, has been leading a team for the past four years working on the smartwatch device. He says he has already rejected a variety of prototypes as not meeting his requirements. Whatever eventually hits the market, currently scheduled for March 2016, Kashio expects it to be priced in the $400 range.
Kashio says the initial sales target will be around $80 million from smartwatch devices. Overall watch sales for Casio totaled $1.2 billion for the year ended March 2015 and accounted for about half of the company’s sales.
source: Wall Street Journal
Come comment on this article: Casio preparing to enter the smartwatch field
How to develop a simple Android Wear app
Early last month, Alex Mullis wrote an excellent article discussing everything you need to know about developing for Android Wear. We are going to take this a step further by developing a simple Android Wear App. Developing for Android is an exciting endeavor, but including Android Wear features in your app is even more fun, trust me!
Before we begin, please keep the following at the back of your mind. Wearable apps, even though they are very similar to apps built for handhelds, should be quite small in size and functionality. You do not want to attempt to replicate the entire functionality of your handset app on a wearable. Rather, you should look for ways to complement the handheld app using the wearable. Ideally, most operations should be performed on the phone, and the results sent to the wearable.
Preparation
Our app will be a simple Android app, that sends a notification from a phone to a paired Wear device, with a corresponding wearable app, with a single clickable button.
For this article, we assume you are using Android Studio. Android Studio is the de-facto standard for Android app development. To develop apps for wearables, you need to update your SDK tools to version 23.0.0 or higher, and your SDK with Android 4.4W.2 or higher.
You should then set up either an Android Wear Device or an Android Wear Emulator.
For an emulator,
- Create an Android Wear square or round device using AVD Manager
- Start the emulator device
- Install the Android Wear app from Google Play
- Connect your handheld to your development machine through USB
- Forward the AVD communication port to the handheld device with the command
adb -d forward tcp:5601 tcp:5601
(this must be done every time you connect/reconnect your handset)
- Start the Android Wear app on your phone and connect to the emulator through the app settings.
For an Android Wear Device,
- Install the Android Wear app on your smartphone via the Google Play Store
- Pair your handset and wearable using the instructions in the app
- Enable developer options on your wear device (tap build number seven times in Settings > About)
- Enable adb debugging
- Connect your wearable to your development machine, and you should be able to install and debug apps directly to your wearable.
Create your Project
The complete source code for this tutorial is available on github, but you might want to create your own project to get a feel for the process. Android Studio provides wizards to help create a project, and they are the best way to setup your Android wearable project. Click File > New Project, and follow the instructions
The process is similar to creating a phone/tablet project. Simply make sure you select both “Phone and Tablet” and “Wear” in the “Form Factors” window.
When the wizard completes, Android Studio will have created a new project with two modules, mobile and wear. For each module, you can create activities, services, layouts and more. Remember, the smartphone app (mobile module) should do most of the work, like intensive processing and network communications, and then send a notification to the wearable.
“mobile” module
The mobile module is the same Android development you are used to. For our mobile module, we create a simple Activity, with an EditText field, and a Button. The text entered into the EditText gets sent to the Wear device as a notification, when the Button is tapped.
The layout is pretty straightforward:
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
android:paddingBottom="@dimen/activity_vertical_margin"
tools:context=".MainActivity"
android:orientation="vertical">
<EditText
android:id="@+id/editText"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_marginBottom="16dp"/>
<Button
android:id="@+id/actionButton"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
style="@style/Base.Widget.AppCompat.Button.Borderless"
android:text="@string/show_notification"
android:onClick="sendNotification" />
</LinearLayout>
The MainActivity is also pretty straightforward:
public class MainActivity extends AppCompatActivity
EditText editText;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
editText = (EditText) findViewById(R.id.editText);
public void sendNotification(View view)
String toSend = editText.getText().toString();
if(toSend.isEmpty())
toSend = "You sent an empty notification";
Notification notification = new NotificationCompat.Builder(getApplication())
.setSmallIcon(R.mipmap.ic_launcher)
.setContentTitle("AndroidAuthority")
.setContentText(toSend)
.extend(new NotificationCompat.WearableExtender().setHintShowBackgroundOnly(true))
.build();
NotificationManagerCompat notificationManager = NotificationManagerCompat.from(getApplication());
int notificationId = 1;
notificationManager.notify(notificationId, notification);
Notice that when building our Notification, we called the extend() method, providing a NotificationCompat.WearableExtender() object.
Running the mobile module
You run the mobile module the same way you run any other Android app. As long as you have it paired with a Wear device (emulator or real), running the project on your device will display notifications on your wearable.
“wear” module
At this point, you should be able to view notifications from your mobile device on your wear device. We, however, are not content with that, and are going to build and run an actual Wear app. Wear devices, generally have a far less screen estate than handhelds, and are usually round or rectangular. This brings it’s own set of layout challenges. True to type, Google has some excellent design guidelines and UI patterns for Android Wear developers. The Wearable UI Library is included in your project automatically when you use the Android Studio project wizard to create your wearable app. Confirm that it’s there, if not then add it to your wear build.gradle file:
dependencies compile 'com.google.android.support:wearable:+'
If you created your project using the Android Studio Project Wizard, you will have an activity setup already for you with two different layout files for Round and Rectangular wear devices. The activity_wear.xml file is shown below:
<?xml version="1.0" encoding="utf-8"?>
<android.support.wearable.view.WatchViewStub
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:id="@+id/watch_view_stub"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:roundLayout="@layout/round_activity_wear"
app:rectLayout="@layout/rect_activity_wear"
tools:context=".WearActivity"
tools:deviceIds="wear">
</android.support.wearable.view.WatchViewStub>
Take note of the base widget. It is a WatchViewStub, which is a part of the Wearable UI library. You must declare the “app:” XML Namespace xmlns:app=”http://schemas.android.com/apk/res-auto” because the Wearable UI widgets declare their attributes using the “app:” namespace.
Take special note of the app:roundLayout and app:rectLayout items. This specifies the layout file to load depending on the shape of the wearable screen. Nifty!
Both our round_activity_wear.xml and rect_activity_wear.xml files are quite similar, except for a few caveats. The widgets in round_activity_wear are centered vertically and horizontally, while for rect_activity, they are simply centered horizontally. Using WatchViewStub, you have the freedom to design your layout completely differently for round and rectangular screens.
round_activity_wear.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
app:layout_box="all"
tools:context=".WearActivity"
tools:deviceIds="wear_round">
<Button
android:id="@+id/button"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
android:text="@string/hello_round"
android:onClick="beginCountdown" />
<android.support.wearable.view.DelayedConfirmationView
android:id="@+id/delayedView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center"
app:circle_border_color="@color/green"
app:circle_border_width="20dp"
app:circle_color="@color/white"
app:circle_radius="60dp"
app:circle_radius_pressed="60dp"
app:circle_padding="16dp"
app:update_interval="100"/>
</FrameLayout>
rect_activity_wear.xml
<?xml version="1.0" encoding="utf-8"?>
<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical"
tools:context=".WearActivity"
tools:deviceIds="wear_square">
<Button
android:id="@+id/button"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"
android:text="@string/hello_square"
android:onClick="beginCountdown" />
<android.support.wearable.view.DelayedConfirmationView
android:id="@+id/delayedView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"
app:circle_border_color="@color/green"
app:circle_border_width="20dp"
app:circle_color="@color/white"
app:circle_radius="60dp"
app:circle_radius_pressed="60dp"
app:circle_padding="16dp"
app:update_interval="100"/>
</FrameLayout>
WearActivity extends android.app.Activity (note not AppCompatActivity), just like any normal Android smartphone or tablet Activity. We set an OnLayoutInflatedListener object on our WatchViewStub, which gets called after the WatchViewStub has determined if the wearable device is round or rectangle. You locate your widgets using findViewById() in the onLayoutInflated method of the OnLayoutInflatedListener. In our case, we instantiate the Button and DelayedConfirmationView, and then call showOnlyButton() to hide the DelayedConfirmationView and show only the Button.
public class WearActivity extends Activity
private Button button;
private DelayedConfirmationView delayedView;
@Override
protected void onCreate(Bundle savedInstanceState)
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_wear);
final WatchViewStub stub = (WatchViewStub) findViewById(R.id.watch_view_stub);
stub.setOnLayoutInflatedListener(new WatchViewStub.OnLayoutInflatedListener()
@Override
public void onLayoutInflated(WatchViewStub stub)
button = (Button) stub.findViewById(R.id.button);
delayedView = (DelayedConfirmationView) stub.findViewById(R.id.delayedView);
delayedView.setTotalTimeMs(3000);
showOnlyButton();
);
public void beginCountdown(View view)
button.setVisibility(View.GONE);
delayedView.setVisibility(View.VISIBLE);
delayedView.setListener(new DelayedConfirmationView.DelayedConfirmationListener()
@Override
public void onTimerFinished(View view)
showOnlyButton();
@Override
public void onTimerSelected(View view)
);
delayedView.start();
public void showOnlyButton()
button.setVisibility(View.VISIBLE);
delayedView.setVisibility(View.GONE);
Running the wear module
To run the wear module, select the wear run/debug configuration, and click the play button (or type Shift+F10). Since this is a debug build, you install directly to your wear device (or emulator). Make sure your device is connected (or a wear emulator is running) and select your device when prompted.
Deploying a release version
While you install your app directly unto a wearable during development, publishing and releasing an app for users is quite different. Your wearable app must be embedded in a handheld app, and it is automatically pushed onto wearables that are connected with the user’s handheld. Visit the Android Developer page on packaging wearable apps for more information on properly packaging your wearable app.
As usual, the complete code is available on github for use as you see fit. Happy coding.
Customers prefer the One M9 in “blind tests”, says HTC ad
There’s nothing like a blind trial to remove people’s preconceptions and HTC’s latest video ad campaign suggests that the One M9 is the people’s choice when it comes to selfies, sound and speed, so long as they can’t see the logo.
HTC asked some “strangers” to pick their favourite of two concealed handsets after testing out the front facing camera in low light, listening to music playing through speakers and running through a series of app challenges in the fastest time. Although a rear camera test is sadly absent, perhaps because the handset didn’t fair too well in our own blind camera sample test.
The One M9’s front facing BoomSound speakers performed well in our own review and the larger pixel Ultrapixel front facing camera should certainly outperform some other handsets in low light. It looks like the Snapdragon 810 is performing pretty well in these tests too.
HTC based its speed exercise on another test that pit the HTC One M9 against the Galaxy S6 and iPhone 6, but HTC doesn’t actually reveal who it has picked as the competition in its version. Here are the other two videos:
There are also longer versions of each of the tests available to watch on HTC’s Youtube channel, which show much the same thing done over and over again with different passers-by.
While certainly not the most scientific of tests, HTC may have a point about the difference between brand perceptions and reality. Do you think that HTC suffers from a lack of positive brand recognition?
Fallout Shelter hopefully hitting Android devices next month
A few weeks ago, in anticipation for Fallout 4, Bethesda Software released a mobile game for iOS by the name of Fallout Shelter that has taken the Apple App Store by storm. However, when Fallout Shelter was announced, Bethesda also noted that there would be an Android version coming with no type of ETA other than “later this year”.
@kolos_kovacs coming along nice. haven’t announced a date, but should be out next month. we’ll let you know when we have specifics
— Pete Hines (@DCDeacon) July 1, 2015
Well thanks to user @kolos_kovacs on Twitter, we now have a better idea of when Fallout Shelter should be coming to Android devices. @DCDeacon, or Pete Hines, is a gentleman who works directly for Bethesda who gave us the bit of insight as to when Fallout Shelter should be released for Android.
According to the tweet above, Fallout Shelter SHOULD be released “next month” for Android devices, so that we all can join the fun. I’ve been playing Fallout Shelter since it was released for iOS, and I must say, I can’t wait to be able to play it across all my devices. When Fallout Shelter does come out, try not to set your Vault on fire or it could be bad news bears.
Source: Android Authority
The post Fallout Shelter hopefully hitting Android devices next month appeared first on AndroidGuys.
Surprise, surprise: Casio is making a smartwatch
style=”display:block”
data-ad-client=”ca-pub-8150504804865896″
data-ad-slot=”8461248232″
data-ad-format=”auto”>
(adsbygoogle = window.adsbygoogle || []).push();
Casio have some of the most iconic looking watches ever – almost everyone will have a memory of owning or remembering a Casio watch at some point in their life. With timepiece makers all over the world joining the smartwatch race, it’s no surprise to see Casio jump on the bandwagon too. Unlike other big name watch makers like Tag Heuer, Fossil and Swatch, however, Casio actually has a pedigree in making watches that do more than just tell time – the scientific calculator watches of old immediately come to mind.
Casio says that they’ve actually be working on a smartwatch for a few years already and that it will be ready to ship in March, for the price of around $400. This is surprising to me seeing as other watchmakers only made their announcements earlier this year and are planning to launch this year as well – what Casio is doing that takes so long is unknown, but we’re willing to believe it’s going to be something that sets them apart. At least, that’s what we hope.
What do you think about Casio making a smartwatch? Let us know your thoughts in the comments below.
Source: The Wall Street Journal via engadget
Originally published on WatchFaceADay.com where I am the founder
The post Surprise, surprise: Casio is making a smartwatch appeared first on AndroidSPIN.
Uber suspends UberPOP in France
The conflict between Uber and France takes another turn with the news that the company will suspend UberPOP from 8pm (France time) today. The ride-sharing outfit has suffered plenty of protest from taxi drivers, who have attacked cars and drivers in recent weeks. In order to protect the safety of both the company’s personnel and passengers, Uber has agreed to halt operations until at least September 30th. That’s when the nation’s constitutional court will rule on if a decision to ban the service was legal.
“The main factor here is not coercion, but violence” according to Uber France CEO Thibaut Simphal, who was speaking to Le Monde. The executive is currently awaiting trial in the country after being arrested on charges of running UberPOP as an illegal taxi service. The reason for the hostility is down to the fact that taxi drivers pay a high fee for a license to pick up passengers on the street. Uber, meanwhile, blurs the line between a private hire vehicle and a taxi, which has left the incumbents feeling threatened. Unfortunately, this has led to some truly stupid people taking their protests far too far, as you can see in the clip below.
Filed under: Transportation
Via: TechCrunch
Source: Uber France (Translated), Le Monde
Google’s ‘GG1’ teases a new version of Glass
Before a company announces a device, it has to pass through the FCC’s secretive bunker to ensure that it’s wireless radios are safe for human contact. Droid Life has trawled through the most recent list of anonymized gadgets to find A4R-GG1, a Google-hewn offering that might, just possibly, be the new version of Google Glass. The clues aren’t exactly concrete, but include the fact that the hardware isn’t classified as a smartphone, tablet or media device. It’s equipped with 802.11 a/b/g/n/ac dual-band WiFi, Bluetooth LE and a built-in rechargeable battery, so clearly it’s also meant to be taken around with you.

Now, a lot of devices are moving toward e-labels, but the documents reveal that the e-label (pictured) for this device has been formatted to the same sort of aspect ratio as Google Glass’ display. Oh, and we could mention the fact that the GG1 in the codename would be a fairly obvious allusion to the wearable’s name, but we won’t. Of course, it doesn’t necessarily mean that we’re merely weeks away from seeing Tony Fadell’s reimagining of the face-worn computer. If all of this stuff is true, however, then perhaps we can expect to see some testers hanging around the Mountain View area hoping that you’re not paying attention to their glasses.
Filed under: Wearables, Google
Via: Droid Life
Source: FCC
New Android One phone rumored for India launch on July 14

According to a “person with knowledge” of the plan, Google and Lava are gearing up to launch the next Android One handset in India. The new smartphone is expected to launch on July 14, will feature renewed specifications and will have a retail price of Rs. 12,000.
The first wave of Android One handsets were not exactly what we would call a success, with less than 800,000 units in consumer hands in India at the last count. That’s considerably less than MediaTek’s ambitious target of two million handsets by the end of the first year.
There are probably two main factors that have held Android One back. Firstly, a lack of retail store presence prevented customers from being exposed to the products. This time around Google is apparently working more closely with Lava, to make sure that the next Android One phone is available online and in shops. Google is also expected to spend around 10 to 15 million in marketing and promotion.
“The first-phase partners took devices from original device makers (ODMs) in China and had no say over hardware and software. The latest device is controlled by Lava, which would be in a position to provide an enhanced experience,”
Secondly, the hardware wasn’t really competitive with other handsets that have shown up the country since. To address this issue, the next Android One phone is rumoured to arrive with better mid-range hardware. MediaTek will still be providing the SoC but the phone will also come with 2GB of RAM and a larger 5-inch display, although we don’t know at what resolution. Google and Lava are also said to be working on specific software features tailored to the region.
By working more closely with individual partners, perhaps the hope is that the next Android One phones provide a more refined experience, but this looks like it will come at a higher price point. The expected retail price of Rs. 12,000 is almost double what the first generation of handsets cost.
Perhaps more will be revealed at the rumoured launch event on July 14th in Delhi. Google India decline to comment.











