The clever two sided, e-ink backed YotaPhone 2 is in fact not coming to the USA. This morning YotaPhone canceled their ($300,000!) Indiegogo campaign and will offer either an international model or a refund to backers. YotaPhone has stated they will have a new manufacturing partner for the next model.
In our Helpful Guide to Music Streaming Services, we mentioned several different services that offer ways to stream catalogs of music directly to your device. While each service has their benefits and drawbacks, the common theme among them is to give you access to a vast library of music without the need to store your own, and charge you a monthly fee for the privilege. But what if you already had access to your own catalog of music? Sure, there are many music locker services out there that allow you to upload and stream your own files. Google Play Music allows you to upload up to 50,000 tracks at no cost, and Amazon Music can even store them for you automatically when you purchase music on a physical medium. But what if you wanted to bypass the re-encoding that these services do to your files? What if you wanted to use the cloud storage services you already pay for? Enter CloudPlayer, the newest app from developer doubleTwist.
Simply stated, doubleTwist’s CloudPlayer allows you build your own music streaming service from the files you already have, using the cloud storage services you already use. The app links to your Dropbox, OneDrive, and Google Drive accounts, as well as pulls from local storage, and scans each for compatible media. Then, it builds from all available sources to create a database, and organizes it into one music library, complete with album art, tags, and metadata. It supports MP3, AAC, OGG, M4A, WAV, and WMA files, and as of version 1.0.4, also supports FLAC files, including those at higher resolutions (up to 24-bit, 192kHz audio). This is probably the biggest reason to use CloudPlayer over other digital music locker services, as most others re-encode lossless or high-resolution files to some type of lossy format. At any time, you can make any file or playlist available for offline playback, and restrict the data needed for streaming to WiFi networks only. There is Chromecast and Apple AirPlay support, and Last.FM scrobbling is built-in.
CloudPlayer is a free download from the Google Play Store, however a one time in-app purchase of $4.99 is needed to unlock the most desirable features, including the cloud storage functionality itself, Chromecast and AirPlay support, and the equalizer and other sound processing features. Upon first opening the app, you are greeted with this information, and can proceed with a 7-day free trial of these “premium” features by logging in with your Google account.
The app itself borrows a lot of visual and operational cues from Google Play Music, which isn’t a bad thing. It offers Material design, and revolves around a gesture-based interface for navigating around your music library. The hamburger menu pops out and allows quick and easy access to sorting options, such as Albums, Artists, Playlists, Songs, Genres, and Composers. From here, you can also show only tracks you’ve downloaded for offline playback and have stored locally, as well as access the settings menu. From the settings menu, you can link to or re-scan your cloud storage services, which include Dropbox, OneDrive, and Google Drive, toggle the use of cellular data on or off, change the default sorting option, set up Last.fm scrobbling, or reset the music database.
Once you connect your cloud storage accounts and allow CloudPlayer to access them, a database is built and organized using track metadata and album art. While browsing the library, overflow menus can be used to make tracks or selections available offline, added to an existing or new playlist, added to the play queue, or deleted. Selecting something for playback will take you to the Now Playing screen, or you can slide it up from the bottom to access it from anywhere within the app. This screen is nicely laid out and functional, and includes high quality album art, play/previous/next buttons, shuffle and repeat controls, a scrolling title bar in ‘track name-artist name’ format, and elapsed/remaining track times. You can swipe left and right on the album art to quickly advance through the playlist, or tap the album art to be able to rate the currently playing track. The bottom of the Now Playing screen houses an ‘Up Next’ section, allowing you to view and quickly jump around the entire playlist. The overflow menu button brings up the 10-band equalizer, SuperSound settings (simulated surround sound settings for headphones), browse currently playing artist, browse currently playing album, and clear play queue options.
The app supports lock screen controls, displaying the album artwork fullscreen, and also has a persistent notification with quick controls. Also available are three home screen widgets: A full 4×4 widget, and two 4×1 widgets: a dark-themed widget, and a lighter-themed one.
Performance is fluid and fast, with no detectable stuttering or dropped frames while navigating through the app. I had no issues getting playback to start with both MP3 and FLAC formatted files from any of the supported cloud storage services, but do keep in mind that there is a very slight delay of a second or two while streaming from them, as the app accesses the track and buffers it. The only time I noticed any significant amounts of delay is when I quickly skipped around a song numerous times, forcing it to re-buffer entirely, but this should not be an issue for most.
There are some notable features which are missing, such as the lack of crossfade or gapless playback support, the lack of ChromeCast support for music that is stored on Google Drive, the inability to add or edit track metadata or album art, and the inability to upload music from your device to the cloud from directly within the app. These features, however, are all listed as coming soon in the Play Store description. One missing feature that I would have liked to see is the ability to view any sort of file information, such as the type of audio file, bitrate, sample rate, and bit depth information. As it stands now, If you have mixed file types or qualities in your music library, you will not be able to differentiate between them. CloudPlayer is a relatively new app, however, so we can be sure that doubleTwist is working on adding features and keeping the app well-supported for the foreseeable future.
Despite the missing features and a $4.99 price, CloudPlayer greatly excels at what it sets out to accomplish. The benefit of being able to connect to multiple cloud storage services means that one could have the space to support a pretty large music library using only the free storage provided by each of the three services, without having to pay for monthly storage from just one of them. And while Google Play Music and Amazon Music are great services on their own, you won’t get the ability to stream lossless audio tracks from them, as both re-encode uploads to lossy file formats. doubleTwist has released a very competent, well-designed, and great performing music player here, and their take on music streaming is one that a lot of people would be quite pleased with.
You can grab doubleTwist’s CloudPlayer from the Play Store.
You can also learn more about CloudPlayer from doubleTwist’s product page.
Have you tried CloudPlayer, or any other music locker service? Let us know your impressions in the comments!
Battery life is an important aspect of your smartphone, especially if you use it for more than just calls on the go. Since you’re on XDA, you probably do and want to get the most out of your battery. Now, you can’t magically expand its size but no matter how much its capacity is, you should make sure it’s not draining faster than it should be.
Your phone’s processor runs at different frequencies when you’re using the device. The CPU frequency it runs at is chosen by the “governor” in a smart manner, usually based on current usage. In other words, your CPU will run at a high speed when you’re gaming, but at a much lower speed if you’re reading an eBook. Again, you can’t do much here assuming the governor is doing its job. What matters the most is what happens when you’re not using the device. In that scenario, battery drain would be ideally minimal as your CPU goes into a special state called “deep sleep”, which consumes a minimal amount of power.
Everything seems fine, then — at least ideally. However, applications can request wake locks which keep your device awake, and are later released as soon as possible. While this makes sense for (and is properly used in) many cases, some applications and developers tend to abuse it due to bugs, oversights or ignorance. If your device is heating when the screen’s off, or if your battery doesn’t last as long as it should, that’s probably the main culprit.
This is where CPU and wake lock monitors, such as CPU Spy Reloaded by XDA Forum Member royale1223, come into play. Inspired by classic apps that share the same goal, it boasts an up to date, material design along with the features you’d expect. You can view neatly graphed CPU state statistics along with the time and percentage of each, wake lock statistics as well as general information about your CPU, GPU and battery. You’ll need to be rooted to view wake lock statistics, but everything else can be used on unrooted devices as well.
CPU statistics come in two forms: a scrollable and zoomable bar chart, and a pie chart. Timers can be reset or restored, allowing you to monitor your device over a more precise period instead of seeing all statistics since startup.
But that’s not everything! Some planned features are the ability to reset timers automatically when the battery is full, resetting wake lock times and detecting big.LITTLE and HMP CPUs. The developer is also happy to listen to any suggestions you might have.
The XDA App Translators also deserve a mention for their help with translating this app to various languages. If you want to join their efforts, or if you’re a developer who needs help with translating your app, make sure to check their thread out.
CPU Spy Reloaded is free, free of ads and comes with minimal permissions. If you’d like to support the developer, you can buy the pro version to unlock the light theme. Head over to the CPU Spy Reloaded Forum Thread to get started!
We are very close to entering the last third of 2015, and we have now seen many of the biggest flagship lines issue their latest iterations. Phones like the LG G4 and Galaxy S6 were some of the most anticipated devices in smartphone history, and the hype surrounding the M9 and OnePlus 2 had us discussing for weeks. But for the most part, the awe has vanished.
There is a feeling that virtually all of us at the XDA office couldn’t shake off after each and every phone unveiling, something which can loosely be described as “cool, but not enough”. Mind you, by this we mean “I wouldn’t upgrade to it”, and I am sure many of you have felt the same. We’ve discussed each phone in-depth, and arrived at the conclusion that it is not because they are bad phones, and certainly not because they are worse phones than the ones before, but because most of them don’t offer a no-compromise, thorough upgrade.
The global context at large is most likely a culprit. We’ve seen the rise of the affordable phone with the original Moto G, but now the trend has moved into the premium space by the increasingly powerful influence of Chinese OEMs like Xiaomi and Huawei, and start-up companies like OnePlus. Some manufacturers like Motorola have given into the pressure and revised their pricing, and others are reportedly considering cutting prices as well. As we approach the saturation point in the biggest markets, the industry is shifting towards emerging economies that see increased sales of affordable devices.
Balancing out hardware advancements, the desire consumers have for “premium smartphones” and competition with the low-end is not an easy task. While 2015 phones have seen clear-cut upgrades on many fronts, we are left feeling that there were compromises and half-measures in their development. This wouldn’t be so bad if the companies themselves wouldn’t try to market their phones as a “no compromise” flagship. Case in point, the OnePlus 2. In this editorial, I will dig into why the OnePlus 2 has failed to meet the hype it set itself up for, and why these compromises ultimately lead to user discontent.
OnePlus had a hit last year with their One flagship, and its bang-per-buck ratio trumped plenty of competitive offerings. The hardware was great, the pricing was excellent, and the phone’s software was good as well. However, the company did meet plenty of controversy over their invite system, quality control issues and very shoddy consumer support. They promised that they would improve upon all of this, and in some ways they did. The OnePlus 2 has been hyped for months and months on end, and with each little tease, the fandom the OnePlus One developed had higher and higher expectations. This week we saw the end result, and while it is a good product, OnePlus made some nonsensical decisions and claims. Is this really the “2016 flagship killer”?
Battery life is something the OnePlus One surprised all of us with, so we were expecting greatness out of its successor. Shortly before the launch, we heard confirmation of a 3,300 mAh battery, which instantly got many excited. I remained skeptical because we had learned (through AMAs) that the OnePlus 2 would not feature a removable battery, nor wireless charging. When the company announced the USB Type C standard, I saw myself having to ground my friends’ expectations, because USB Type C does not inherently mean higher charging speed. And it turns out I was right: OnePlus opted for a standard USB 2.0, and to make things worse, it has no Quick Charge. We now know it can take around 3 hours to get a full charge, through a port that is not widely adopted, without wireless charging and without the option to change batteries. What’s more, MKBHD’s battery benchmark and real-world usage suggest a regression in battery life (although it is still too early to make conclusive statements).
On to NFC: the company decided to leave out NFC support from their new flagship, because apparently “OnePlus One users were not using it”. This is something that I’ve heard before in my interview with Fairphone, and it shows that OnePlus did not project into the future: Android Pay will hit many markets soon, and expand to many stores. Alibaba is also popularizing mobile payments in China, one of OnePlus’ most important markets. This gives NFC the possibility of the widespread use it has not had since its introduction. OnePlus decided to incorporate a fingerprint scanner, but now it is mostly relegated to unlocking the phone, not mobile payments. What’s more puzzling is that Carl Pei himself had suggested an emphasis on biometrics for mobile payments, just not the close-contact kind which will expand with Android Pay, Samsung Pay, Alipay in China and Apple Pay (really original names, by the way) hitting more and more stores.
Finally, we have the screen. OnePlus had a very impressive screen with their previous phone, and this one does not look bad either. I am not the kind of user who is crazy about 1440p screens – in fact, I run my Note 4 at 1080p – but OnePlus once again showed nonsense: they have been advertising their Virtual Reality launch since it was announced, and they kept saying that Virtual Reality is the future. They even shipped out free VR Cardboards! Now, if there is a practical reason to have a high-resolution screen, that is VR. The fact that OnePlus has been pushing for VR while making their device a much less appealing option for VR is as retrograde as it gets. We had a feature on why VR can justify QHD and UHD displays, which we suggest you read in case you are out of the loop. You will see that QHD does have a noticeable effect on VR, and other manufacturers know this (which is why Samsung began its push for it with the Note 4).
This is not the only phone to promise too much and delivered too little. The M9, for example, had many issues which we discussed time and time again — and not all were due to the Snapdragon 810. But this infamous SoC did put most OEMs in a troubling spot. LG and Moto opted for the less powerful but more stable 808, which is one of the few ways to avoid the flak the number “810” carries with it as well as possible performance inconsistencies. Rumors say that the 820 might come before we expected it to, around the last quarter of 2015. Hopefully this is the case so that other highly-anticipated devices (like new Nexus phones) can make use of a more powerful and more stable chipset. But the problem with the sales of 2015 smartphones, which didn’t meet expectations even for Samsung, is too complex to blame simply on hot chips or failed hype.
So far, the “no compromise” phones have had compromises here or there. Some are big, some are not, but more often than not they are found in key areas of a phone. Regressing in something as important as the camera or battery life is not something anyone wants out of their precious and expensive upgrades. Now that flagships are powerful enough to last years (especially with good software or developer support from OEMs or XDA), there is less of a reason to upgrade. The market knows this, OEMs know this. Motorola has now split their flagship model into two, and the Moto X Pure is just $399. It features amazing specifications for that price. The Chinese giants are entering the West, and many first-world markets are beginning to show signs of saturation. Developing markets are more important than ever. In this context, balancing out every aspect while focusing on keeping a low price is a hard task.
The OnePlus 2 is not a 2016 flagship killer, because in many areas it cannot even kill 2014 flagships. But soon enough, there might be nothing left to kill: the high-end is beginning to merge with the middle-range. When most OEMs catch-up to the new model the market favors, OnePlus’ niche will go away. If Motorola is anything to go by, then it might just happen sooner than we expect.
Those of us eagerly awaiting the next developer preview of Android M will unfortunately be waiting a little longer for the upcoming third build. Googler Wojtek Kaliciński took to Google+ earlier to break the bad news about the “near final” release, and declined to comment on speculation regarding an ETA.
The OnePlus 2 has been officially released. 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 a serious security vulnerability on Android and be sure to check out the article talking about how easy it is to make your one Xposed Module. 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 NetStrength. Then Jordan reviews the ASUS Lolliflash and ZenPower. Also, TK showed us how to root the LG G4. 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
More and more phones are featuring fingerprint scanners, and with many promising developments and it being natively supported on Android M, we can soon expect to see them on smartphones everywhere. If done right, it is a useful feature that allows for quick unlocking and authorization. There are concerns regarding security, but nonetheless the industry seems to be embracing it with open arms. What do you think?
