Doing well for a device with an OS with practically no market history in smartphones, Samsung has revealed that it has sold 1 million Z1 devices in less than 6 months of sales. The company has revealed that a Gold variant of this successful device is planned, along with more entry level handsets on its home brewn Tizen OS.
The post Samsung Sold 1 Million Tizen-based Z1 In 6 Months appeared first on xda-developers.
Facebook has officially launched its “Lite” app for users in India and Philippines, targeting users in emerging markets with unreliable 2G connections. The app is designed to use less data, and supports push notifications and messaging, and even installs in less than 1MB of space.
The post Facebook Lite appeared first on xda-developers.
Xposed Framework is an extremely popular modification platform for Android, so much so that we included it in our Best of XDA series. Creator rovo89 has just updated the package to v65, reportedly including a host of bugfixes, more complete logs and a simpler naming scheme.
The post Xposed Framework Updated to v65 appeared first on xda-developers.
The Meizu MX5 has been leaked. That and much more news is covered by Jordan when he reviews all the important stories from this week. Included in this week’s news is the announcement of Amazon releasing the Alexa SDK and be sure to check out the article talking about the Sony E5663 specification leak. That’s not all that’s covered in today’s video!
Jordan talks about the other videos released this week on XDA TV. XDA TV Producer TK released an Xposed Tuesday video covering XHangouts. Then TK reviewed the Montar Car Mount. Also, TK gave us an app review of MRU Widget. Pull up a chair and check out this video.
Be sure to check out other great XDA TV Videos
Check out Jordan’s YouTube Channel and Jordan’s Gaming YouTube Channel
The post Meizu MX5 Leaks, Oukitel’s 10,000 mAh Phone – XDA TV appeared first on xda-developers.
Chromium Dev François Beaufort has given us a little insight into how the the Chrome OS team measures end-to-end latency. The team uses a robot built by Finnish company OptoFidelity to measure this on Android and Chrome OS devices. There’s also a video demoing how a line is actually drawn on a screen.
The post Chrome OS Team Uses Robot To Measure Latency appeared first on xda-developers.
Join us in a fun Sunday Debate on Notifications. Come with your opinions and feel free to read some of our thoughts, then pick your side or play devil’s advocate to get your voice heard and engage in friendly discussion. You can read our food-for-thought or jump straight into the fray below!
Notifications are a huge part of Android, and Lollipop brought with it a redesign of the age-old notification ticker. The “heads up” system is loved by some, and detested by others — not unlike many changes each version brings, yet in a particularly polarizing way. The main issue with Lollipop’s implementation is that it was not properly worked out for the initial versions. That is, there was no built-in way to disable it, nor revert the system, and once a notification hits your screen during use, your only option is to swipe it away and dismiss the notification from your list. This last bit was addressed in later builds, but many users are still stuck in 5.0.x and left to fix the issues through other means.
Now that many months went by, we have more than a few options at our disposal to address this issue. First of all, KitKat users can enjoy heads up notifications through Xposed modules and app options like HeadsUp and others. Lollipop users that want to be able to hide the heads up notifications instead of dismiss them can use Heads Up Hide for Xposed, and now we also have options to restore the notification ticker like XDA Forum Member Productigeeky’s Ticklr. In short, users can now enjoy heads up notifications or the ticker on both Lollipop and KitKat.
But given that most people tend to choose one over the other, we want to ask you the following: Which one is more efficient? Which one do you prefer, and why? Should we incorporate both? For which use-cases? Can their functionality be expanded, and if so, how? This debate can be considered rather opinionated, but we also want you to touch on the matter of usefulness for various use-cases. As always, feel free to skip our food-for-thought and go straight to the discussion in the comments.
The premise of heads up notifications is to bring you the information within a tidy presentation, allowing you to read it in full before deciding what to do with the message. While we were teased with quick replies and the like, we are left waiting for Google or developers to implement such a system. The notification can, however, be rather spacious, particularly in landscape mode where it can interrupt a movie. The fact that it is so obtrusive can make media consumption a pain when you are getting blasted with random messages, especially on early implementations where you can only dismiss these. These notifications are in tune with Material Design and can be quick and pleasant, but not all the time. However, a virtue that the heads up system has over the ticker is that you are only one click away of the app.
The ticker is an age-old system which many Android fans love for a very good reason: it’s unobtrusive. The ticker presents messages in your status bar, allowing you to almost completely ignore the notification unless you do want to pay attention to it. Moreover, ignoring it is a passive process (no need to swipe anywhere) and you can rest easy knowing that the notification will be there for you to access later. However, problems quickly arise with this system: in certain contexts where one must pay careful attention to the text, this one can switch to the next line too fast for one to fully grasp the important bits of the message (luckily there are ways to tweak the scroll speed). Since it’s a preview, it’s usually not too important, but Heads Up notifications do give you more control over the processing of the preview’s information. Long messages can also be split awkwardly and distort the flow of the message, which can also be detrimental in certain cases.
Why not both? It is clear that both the ticker and the heads up solution have their inherent strengths and weaknesses depending on what the context is. Ultimately it seems to be a conflict between how intrusive and manageable or unobtrusive and uncontrollable you want the notification preview to be. A black/white list for which apps can send ticker or heads up notifications is not enough, however. Rather, one would need a list for the apps in which you can receive one or the other. This way, media consumption apps like Youtube could, for example, only display the ticker.
One one hand, heads up notifications offer you better control over your notification, at the expense of being intrusive. You can, however, quickly take care of the message by directly accessing the app. The ticker is different altogether, and while unobtrusive, it has its downsides as it can lead to a less efficient experience in many contexts where precise intelligibility or quick input are needed. A hybrid system can benefit both options, but you might find said system pointless or overkill if you clearly prefer one over the other. So we ask you the following:
The post Sunday Debate: Heads Up Notifications vs. Ticker appeared first on xda-developers.
In a move that was predicted since Android Studio was launched back in 2013, Google has announced that they will be ending official support for Eclipse at the end of this year. This specifically includes the Eclipse ADT (Android Developer Tools) plugin and the Android Ant build system.
Over the past few years, our team has focused on improving the development experience for building Android apps with Android Studio. Since the launch of Android Studio, we have been impressed with the excitement and positive feedback. As the official Android IDE, Android Studio gives you access to a powerful and comprehensive suite of tools to evolve your app across Android platforms, whether it’s on the phone, wrist, car or TV.
Back when it was released, Android Studio had drawn mixed reactions. You either loved the new features and polish that it promised to bring along, or you still preferred to remain with Eclipse and the extensive troubleshooting documentation that it had accumulated from the community. However, Google has indeed delivered on its promise of providing a robust development platform for app developers, with Android Studio having matured into a stable and reliable tool. What’s more, Google will be migrating the rest of the standalone performance tools like DDMS and Trace Viewer to Android Studio, along with building additional support for the Android NDK, so little reason will remain to still continue on using Eclipse over Android Studio.
If you are an Eclipse die-hard, you can still continue on using it even after support ends.
Android tools inside Eclipse will continue to live on in the open source community via the Eclipse Foundation. Check out the latest Eclipse Andmore project if you are interested in contributing or learning more.
As a suggestion, it is better to make the switch to Android Studio as soon as you can.
Also, if you want to contribute to Android Studio, you can also check out the project source code. To follow all the updates on Android Studio, join our Google+ community.
The post Google Set To End Support For ADT In Eclipse appeared first on xda-developers.
