Slatedroid info

Everything about android tablet pc [slatedroid]

Updated Google Play Developer Distribution Agreement enforces quicker response times

Posted by wicked September - 26 - 2014 - Friday Comments Off


Google has quietly updated its official Google Play Distribution Agreement to introduce some new clauses that are targeted at developers to take more responsibility for their products, which should, in turn, make things a wee bit easier on us, the consumer.

The first of these new clauses states that developers who offer paid applications or in-app purchases will have a maximum of three business days to respond to customer support inquiries, or just 24 hours if a customer’s issue is deemed urgent by Google.

Next we’re looking at amendments to some of the company’s marketing language, which now prevents developers from embedding links directed to people, applications or games that aren’t supplied through the Play Store.

Lastly, Google has made some changes to the wording surrounding its VAT and tax policy. Starting today, the firm will handle all VAT charges for applications and services purchased via the Play Store.

If you’re a developer we’d love to hear what you think of the new Distribution Agreement clauses, so be sure to drop us a comment in the section below.

Source: Google Play

Come comment on this article: Updated Google Play Developer Distribution Agreement enforces quicker response times

HTC’s former Product Manager Snatched up by Cyanogen

Posted by wicked September - 24 - 2014 - Wednesday Comments Off


Cyanogen is on the prowl again, looking for more employees to sway over to its team. HTC’s former Product Manager of 3.5 yrs. was the latest target. She will assume the role of Product Evangelist starting Friday for Cyanogen Inc., which will presumably include multiple public relations campaigns for the software company.

Cyanogen’s recent deals with Oppo and OnePlus have helped it gain some sturdy legs to grow on as a company, and more recent acquisitions of a few more quality employees have only helped. Even the fact that Cyanogen has a need of a product evangelist means it’s molting into a much larger company that we will see affecting the industry in the future.

Source: Google+


Come comment on this article: HTC’s former Product Manager Snatched up by Cyanogen

MediaTek Labs launched to support development of wearables and other devices

Posted by wicked September - 23 - 2014 - Tuesday Comments Off


MediaTek announced today the launch of a new global initiative they are calling MediaTek Labs to provide resources for the development of wearables and “Internet of Things” (IoT) devices. The new project tries to provide support for a variety of groups that may be involved in efforts to create new devices across a wide range of skill levels. According to Marc Naddell, vice president for the new MediaTek Labs, “with the launch of MediaTek Labs we’re opening up a new world of possibilities for everyone — from hobbyists and students through to professional developers and designers — to unleash their creativity and innovation. We believe that the innovation enabled by MediaTek Labs will drive the next wave of consumer gadgets and apps that will connect billions of things and people around the world.”

The heart of the new initiative is MediaTek’s LinkIt development platform. The platform provides an operating system for wearables and IoT that run on a MediaTek Aster chip and also supports MediaTek’s WiFi and GPS chipsets. MediaTek also created a LinkIt Hardware Development Kit to be used for prototyping devices and the LinkIt ONE from Seeed Studio, a third-party development board compatible with the new hardware reference design.

MediaTek is also making a preview release available of the MediaTek SDK for Android so developers can start working on adding support to their code.


You can read the full press release announcing the new MediaTek Labs below:

TAIWAN, Hsinchu — Sept 22, 2014 — MediaTek today launched MediaTek Labs (, a global initiative that allows developers of any background or skill level to create wearable and Internet of Things (IoT) devices. The new program provides developers, makers and service providers with software development kits (SDKs), hardware development kits (HDKs), and technical documentation, as well as technical and business support.

“With the launch of MediaTek Labs we’re opening up a new world of possibilities for everyone — from hobbyists and students through to professional developers and designers — to unleash their creativity and innovation,” says Marc Naddell, vice president of MediaTek Labs. “We believe that the innovation enabled by MediaTek Labs will drive the next wave of consumer gadgets and apps that will connect billions of things and people around the world.”

The Labs developer program also features the LinkIt™ Development Platform, which is based on the MediaTek Aster (MT2502) chipset. The LinkIt development Platform is the one of the best connected platforms, offering excellent integration for the package size and doing away with the need for additional connectivity hardware. LinkIt makes creating prototype wearable and IoT devices easy and cost effective by leveraging MediaTek’s proven reference design development model. The LinkIt platform consists of the following components:

System-on-Chip (SoC) — MediaTek Aster (MT2502), the world’s smallest commercial SoC for Wearables, and companion Wi-Fi (MT5931) and GPS (MT3332) chipsets offering powerful, battery efficient technology.
LinkIt OS — an advanced yet compact operating system that enables control software and takes full advantage of the features of the Aster SoC, companion chipsets, and a wide range of sensors and peripheral hardware.
Hardware Development Kit (HDK) — Launching first with LinkIt ONE, a co-design project with Seeed Studio, the HDK will make it easy to add sensors, peripherals, and Arduino Shields to LinkIt ONE and create fully featured device prototypes.
Software Development Kit (SDK) — Makers can easily migrate existing Arduino code to LinkIt ONE using the APIs provided. In addition, they get a range of APIs to make use of the LinkIt communication features: GSM, GPRS, Bluetooth, and Wi-Fi.
To ensure developers can make the most of the LinkIt offering, the MediaTek Labs website includes a range of additional services, including:
Comprehensive business and technology overviews
A Solutions Catalog where developers can share information on their devices, applications, and services and become accessible for matchmaking to MediaTek’s customers and partners
Support services, including comprehensive FAQ, discussion forums that are monitored by MediaTek technical experts, and — for developers with solutions under development in the Solutions Catalog — free technical support.

“While makers still use their traditional industrial components for new connected IoT devices, with the LinkIt ONE hardware kit as part of MediaTek LinkIt Developer Platform, we’re excited to help Makers bring prototypes to market faster and more easily,” says Eric Pan, founder and chief executive officer of Seeed Studio.

Makers, designers and developers can sign up to MediaTek Labs today and download the full range of tools and documentation at
About MediaTek Inc.
MediaTek is a pioneering fabless semiconductor company, and a market leader in cutting-edge systems on a chip for wireless communications and connectivity, HDTV, DVD and Blu-ray. MediaTek created the world’s first octa-core smartphone platform with LTE and our CorePilot™ technology releasing the full power of multi-core mobile processors. Through MediaTek Labs™, the company is creating a worldwide ecosystem in support of device creation, application development and services based around MediaTek offerings. With an emphasis on enabling technology for the masses and not the chosen, everyone can be an Everyday Genius. MediaTek [TSE:2454] is headquartered in Taiwan and has offices worldwide. Please visit for more information.

Come comment on this article: MediaTek Labs launched to support development of wearables and other devices

The Play Store could start listing in-app purchase price ranges later this month

Posted by wicked September - 19 - 2014 - Friday Comments Off


You probably have noticed that many apps in the Play Store have “offers in-app purchases” listed near the install icon. The only problem with that is you really don’t know if it’s one small purchase to get rid of ads or if there is a slew of options. Well it looks like Google will start listing in-app purchase price ranges soon.

This information came from Google support when they contacted the developer of GoneMad Music Player regarding Google’s new policy that all developers of paid and in-app purchase apps must provide their publicly visible address. Hit the break for the full text.

Thanks for contacting Google Play Developer Support.

As of September 30, 2014, we are implementing a number of new changes to how apps are listed and displayed on Google Play, in accordance with consumer protection laws and current best-practices, ensuring a more transparent and positive experience for users. They include:

  • We are requiring developers to provide a physical address for all paid apps or apps that enable in-app purchases. The address will be displayed to users in the app store listing page. By September 30, 2014, you’ll be able to add a physical address by going to your Settings page on the Developer Console ([1]). Please comply within 30 days of the warning notification on the developer console. If you do not provide an address within this period, Google may take action affecting your account. This may include restricting your ability to update apps or publish new apps. Continued failure to provide an address may result in published apps being removed from the store.
  • We will display the price ranges for apps that offer in-app purchases and/or subscriptions on the app’s store listing page.

Please let me know if you have any additional questions and I’ll be happy to help.

Google is saying these changes are to comply with the “consumer protection laws.” Expect to see this change by September 30th.

What do you guys think? This has to be an improvement right?

source: Android Police


Come comment on this article: The Play Store could start listing in-app purchase price ranges later this month

Is your Android Wear app randomly closing on you? Check this out

Posted by wicked September - 16 - 2014 - Tuesday Comments Off

using android wear aa (4 of 20)

We’ve been keeping a close eye on Android Wear since it was first rumored and announced earlier this year. Not only are we huge fans of all mobile technology, including wearables like smartwatches, we’re also interested in how it all works and where it is headed in the future. We’ve stumbled across a little quirk in the Android Wear system that may be causing you, or at least the developers of your favorite Android Wear apps, some grief.

If your Android Wear app keeps closing unexpectedly, you are not alone.

Here is the scenario that developers are facing: when building a full screen Android Wear app that collects data from the accelerometer – this goes for many fitness related app out there – you may find that the app unexpectedly closes and returns you to the home screen of the device.

What is going on with that? The answer is pretty simple, Android Wear itself is also collecting accelerometer data, updating the pedometer step count. Android Wear is so exciting for your progress, it fires up a new info card and presents it to you on the home screen of your device.

Android Wear App call to halt

As we keep tabs on this concern through the Android bug tracker, no official answers are available just yet. Perhaps developers are not supposed to build full screen apps for Android Wear that use the accelerometer, perhaps it is a bug, or maybe we’re just doing it wrong.

Luckily, the same user that filed the issue has a workaround. Developers, this is for you:

Instead of starting your app as a full screen activity, try creating a persistent notification in the context stream, then, give that notification an action to go full screen. This should prevent other cards from stopping your activity, so you can continue to collect accelerometer data and display it to your users.

We want to hear from you: Have you encountered an Android Wear app that closes unexpectedly? Are you a developer with any experience or insight into this particular situation, how did you overcome it?

Via: Android Bug Tracker;

New leaked image of Android L shows possible UI refinements

Posted by wicked September - 9 - 2014 - Tuesday Comments Off


A new image of a device running what appears to be a new build of Android L reveals some minor tweaks to the user interface.  The photo is of a Nexus 5 running a version of Android with build number LRW66E which appears to have been created on September 4th. Along with the information gleaned from the shot of the screen on the Nexus 5, information in Google’s bug tracker shows the name of the phone including this bit – “LMP.” Could that be a reference to “Lemon Meringue Pie” suggesting the “Lion” information that has surfaced is just to throw people off the scent?

As far as the changes to the interface spotted in the screenshot, we see:

  1. Toggle – the toggle, or Switch as it is called in the Material Design guidelines, appears much shorter and instead of a thin line uses a fat bar. It is unclear why this would be changed as it seems to take the design backwards. It is possible the effect was caused by some bug or may be intentional in an effort to obfuscate things.
  2. Device icons – at least in the list for connected Bluetooth devices, entries now have an icon associated with them to go with the text entry. It is not clear whether this will be carried over to other parts of the system, but is likely.
  3. Gear icon – the Gear icon for settings has been given color – teal in this case – so that it matches the rest of the user interface. Previously it was just black. Along with the change in color to the icon, a vertical double-line separator that was present before is no longer present.
  4. Bluetooth visibility – this particular change is specific to the Bluetooth function as it appears the two minute limit on being visible to nearby devices has been removed if the lack of a countdown timer is any indication. In addition, the location of the text informing the user of the visibility of the device has been moved to the bottom of the list.
  5. Gmail icon – another very subtle change, the Gmail icon now appears to have a stacked appearance. This may be a change to help indicate that more than one message is unread. This change may not necessary be part of Android L as it could be something included in an upcoming release of the Gmail app.
  6. Signal strength indicators – the final change noted involves the signal strength indicators for WiFi and data. The icons now appear to be a single image without any breaks to indicate steps or levels. This is similar to how the battery icon now appears with the available charge changing freely within the confines of the icon.

Although the changes are small, what do you think of the direction Google appears to be headed in with Android L’s Material Design?

source: Android Police

Come comment on this article: New leaked image of Android L shows possible UI refinements

Nike+ running app to come pre-loaded on Samsung’s Gear S smartwatch

Posted by wicked August - 29 - 2014 - Friday Comments Off

Gear S_Nike

Samsung’s Tizen-based Gear S smartwatch is now official, so it’s up to the company and third-party developers now to begin making apps available for the device.

Samsung recently announced a new partnership with Nike in a press release — Gear S owners will be able to download the Nike+ Running app, which utilizes the device’s GPS and 3G connectivity to track fitness data.

The app comes pre-loaded on the device and can track their runs and record data all while their phone remains at home.

The features appear to be the same as the usual Nike+ Running App, except this is optimized for the Gear S.

Source: Samsung

Come comment on this article: Nike+ running app to come pre-loaded on Samsung’s Gear S smartwatch

Android’s design guidelines: what are they, and why should you care?

Posted by wicked August - 25 - 2014 - Monday Comments Off


These days, there isn’t much left to say about design on Android. There’s a lingering stigma that Android applications are designed for tech enthusiasts, and remain inaccessible for the average user. The platform has many poor first impressions to overcome, but the design team at Google is working hard to clean up their fragmented past.

What Are Design Guidelines?

In some ways Google’s Android Design Guidelines (and similarly Apple’s Human Interface Guidelines) could be called Design Conversation Starters. They are not a coding framework, and they are not a programming language. Instead, they are a collection of thoughts, ideas, and principles that provide a common vernacular for designers and developers.

“What do you think about using an ActionBar?”, “I think a card metaphor is what we’re getting at here”, or “I’m not sure if this scene transition translates well to a larger screen.” These are all potential examples of conversations that product developers are having about the popular applications you use every day.


Provide A Baseline Look And Feel

The guidelines also serve as an example of how basic applications should look and feel. Keep your navigation and actions along the top of the screen, maintain logical navigation hierarchies, avoid touch targets less than 48dp (density-independent pixels) in size, etc. However, these specifically read more like rules than guidelines. It’s preferred that you follow them, but hey, rules were meant to be broken.

Think Of The Users

Above the need for designers and developers to have a language to converse in, the user is paramount to any discussion. Having design guidelines means that users will naturally acquire a lexicon of behaviors that they can bring with them into any new application they encounter. Just like how your users  know that ctrl+z is undo and you can right click for more options, they will also know that pulling to refresh will give them new content, and pressing back will return to their previous view.

Why Have Guidelines At All?

No article on Android Design would be complete without paying homage to its past. A past that I, and all other Android enthusiasts, would prefer to soon forget. A lot of these conversations start out the same way, “Why have guidelines at all? The web doesn’t have guidelines, why does Android?” That’s a whole article in itself, one I’m probably not qualified to write, but I’ll try and shed some light.

There were always design guidelines, but they usually read more as a book of rules rather than a ice breaker for conversations.

Android applications got off to a rocky start. There were always design guidelines, but they usually read more as a book of rules rather than a ice breaker for conversations. I remember one of my proudest moments as a budding designer was making the menu icons for the Android app at my first company. It had a complex set of rules to ensure that they looked like the icons in the rest of the system. In my naive experience, this was the pinnacle of design. Such thought was put into every glowing detail.

Icon Design Guidelines - Android Gingerbread (2.3)

Icon Design Guidelines – Android Gingerbread (2.3) – original slides

Homegrown Gingerbread Icons

My feeble attempt at “design”

The only navigation available in the design documentation were tabs across the top of the screen, and a dashboard pattern (which I like to call the “Six Pack”) used in a twitter app (the source of which I’m still waiting for). There were many navigation needs that were left completely unanswered, and the designers did their best to fill those gaps. Actions would be in tab bars, navigation would be in menu items (from the physical menu button), and screens with actual back buttons baked into them,  to name a few.

None of these design paradigms were inherently wrong in themselves, and they have all worked their way into the modern design framework in different ways. But the platform was evolving quickly, and applications designs were updating too slowly to allow these patterns to figure themselves out on their own volition.


Screen Shot 2014-08-23 at 6.29.27 PM

Quickly realizing the developers’ struggles, and needing a platform for unifying Android 2 and 3, the design team at Google brought us the Holo Design Guidelines with Android 4. Holo catapulted us into the modern application design age. Finally, the tools were available to reliably design applications in a unified style, and justifiable reasons were given as to why other platforms shouldn’t be mimicked.

Android 4 brought us an official ActionBar API, allowing us to easily add action bars across our applications. It also brought us Fragments (a system that enabled creation of views that could be rearranged in different ways to enabling phone and tablet interfaces to use the same components), better notifications, and a plethora of new features that put the platform on track to fostering a successful ecosystem.

Material World

The transformation from Android 4 to Android L is tremendous, and arguably even bigger than the jump from Android 2 to Android 4. Many developers are harkening this as Android design’s golden age, where the creative tools available are among the best in the industry.

Cognitive Context

Material applications are finally going to provide us some much needed cognitive context for many of the transitions designers are expecting us to understand. In Android L, visual components (called Hero Elements) will seamlessly transition from one screen to the next. An avatar from your contacts list will transition to its location on the details screen. An image in a grid will scale to the screens size when touching. It should finally make sense where the data on the screens is actually coming from.

Dynamic Color

I love color, and I love that Android is now treating color as a first class citizen. PocketCasts is a beautiful podcasting application I use on a daily basis, but no longer will it hold a monopoly on color-accented colored user interfaces in the Android ecosystem. With the introduction of Palette (an addition to the support-library with blazing fast algorithms that extract prominent colors from an image), as well as easy image tinting, Android applications are going to start looking more vibrant, and will adapt to the content in which they are displaying.

A New Era Of Card Based Interfaces


Developers have been asking for a card layout since Google+ introduced it almost 2 years ago. They were reluctant to hand it out, presumably because there wasn’t much benefit they could add aside from baking in a few assets for you. This has changed in L: A card widget has been added, but it does more than just provide you a simple card wrapper for your content. It provides simple API’s for specifying the corner’s radius, it masks the corners of content for you, and most of all, it provides shadows for you, even in the support versions, so that your shadows will look identical across all versions of an application.

Floating Action Buttons are the new kids on the block – expect to see more.


We have seen floating action buttons across a handful of apps in the past – Path, Tumblr, and Foursquare (the old one) to name a few, but these buttons have never been considered a design paradigm until now. Like it or not, this Floating Action Button (FAB for brevity) is going to start making an appearance in many of your favorite applications this fall.

Materials Are Platform Independent


Developers and Designers, from Google or not, are striving towards one goal: Make beautiful applications that enrich the lives of those who use them.

The last key aspect of material design, and potentially the most important: Material design is not the new design language for Android. Material design is the new design language for Google, on all fronts. This means that we’ll be seeing Material design invading all of Google’s web properties, like Gmail and Maps. And don’t be surprised when you start seeing shadows making a comeback in your iOS applications.

The Evolution Of Design

The latest iteration of the Android Design Guidelines from the design team at Google is the best yet, and we should all be excited at the innovation it brings to the table. Even more importantly, they leave plenty of room for flexibility and interpretation to ensure that any idea can be represented in the best way possible.

Developers and Designers, from Google or not, are striving towards one goal: Make beautiful applications that enrich the lives of those who use them. Take a closer look at the applications you use everyday. Pay attention to which design patterns they follow, and also which ones they don’t. Every detail in these applications started out as a conversation – “Lets take a look at the guidelines.”

(Imagery taken from

Chrome ADB server released for Nexus 5

Posted by wicked August - 25 - 2014 - Monday Comments Off

ChromeADBIf you’re interested in tinkering with your phone, you know how using ADB requires installing the SDK or using a toolkit (my personal method of action). However, thanks to Koushik Dutta, a prolific Android developer and creator of many apps, there is a public version of an ADB server for Chrome, released today. Unfortunately, it only works with the Nexus 5 at the moment, but we can expect him to add more devices in the future, most likely starting with the rest of the current Nexus devices.

If you have a Nexus 5, try out the process and let us know how it goes in the comment section below.

Source: Google+


Come comment on this article: Chrome ADB server released for Nexus 5

Google Fit now available to developers as a preview SDK

Posted by wicked August - 7 - 2014 - Thursday Comments Off


Google announced Google Fit at Google I/O, which will gives developers the tools to build amazing fitness apps. The set of APIs can store and access data from fitness apps and sensors on Android devices or other wearables. With the user’s permission, apps will now be able to access fitness history data allowing for detailed insights, personalized coaching, recommendations, and more.

The preview SDK is now available so developers can start building apps today. There are three sets of APIs…..

  • Sensors API provides high-level access to sensors from the device and wearables—so with one API your app can talk to sensors, whether on an Android device or a wearable. So if you’re making a running app, you could register it to receive updates from a connected heart rate monitor every 5 seconds during a user’s run and give immediate feedback to the runner on the display.
  • Recording API allows apps to register for battery-efficient, cloud-synced background collection of fitness data. For example, a running app could ask to store user’s location so it can map the run later. Once it registers for these data types, collection is done by Fit in the background with no further work needed by the app.
  • History API allows operations on the data like read, insert and delete. When the exerciser finishes her run, the running app can query the History API for all locations during the run and show a map.

Hit the source link for more information on how to get started.

source: Google Developers

Come comment on this article: Google Fit now available to developers as a preview SDK

ePad 7 Android 4.0 ICS
$162 $100 FREE SHIPPING 

10" Android 4.2 1.2GHz Tablet PC