Monday, 16 September 2013

[Poll] The 'Recently Updated' Section Of The Play Store App Has Changed From 7 To 3 Days – Is That Better?



A recent Play Store update to 4.3.10 cleaned up some rough edges and added a few minor features. Although, one of those features was contentious to say the least. The Recently Updated section of the My Apps page listed everything updated for the last week, which could be a long list for users with a lot of apps. It's not seven days anymore, though. Now it's more like three.
nexusae0_thumbnail8 2013-09-16 15.50.01
The Play Store now only considers apps updated in the last three days (give or take a little) to be recent. This means the list will be much shorter, and frankly, fits the definition of "recent" better. Users with a few apps might not have much of anything in the Recently Updated list, though.
We spoke to a Googler who confirmed the limit is currently set at about 3 days, but it's not set in stone. It could go back up or be lowered even more. So how do you feel about this change? Our last poll resulted in a whopping 59% of you saying the amount of time should be shorter.
Is 3 days the right length of time for apps to show up in the "Recently Updated" section of the Play Store?
View Results

Google Just Bought Touch-To-Transfer App Company 'Bump'

You guys remember Bump? It's been a while since we've had a reason to discuss the app, but that changes today; Google just bought the company. For those who may not be familiar with Bump, it's an app that allows files, images, apps, and the like to be transferred from device to device by touching the two together. It was actually pretty popular a few years ago, before NFC and Android Beam (which, honestly, still doesn't work correctly half the time) came along.
1
The thing that makes Bump a more compelling option over NFC, however, is that it's cross platform – as long as both parties have the Bump app installed, it makes transferring information from Android to iOS incredibly easy.
The acquisition was announced today on the Bump blog, though details are basically non-existent at the time. Bump's CEO and co-founder David Lieb penned a short entry that announced the company's joining with Google, but also confirmed that "Bump and Flock will continue to work as they always have for now" (emphasis mine), which alludes to possible changes in the future.
At this point, it's unclear what Google wants with Bump – maybe they'll put the team on fixing the way Android Beam works (read: making it actually work).
Time will tell.
Bump

Sprint Expands 4G LTE Availability To 34 New Markets, Brings Nationwide Coverage Up To 185

Compared to Verizon and AT&T, Sprint's network leaves much to be desired in terms of both data speeds and coverage. This isn't the result of a lack of effort, though, as the Kansas-based company has steadily rolled out LTE to new markets throughout the summer. Today the company has announced the availability of 4G LTE in 34 new markets, bringing the total number from 151 up to 185. Sprint customers throughout the South, Midwest, North Carolina, Oregon, and Pennsylvania should now have a new reason to smile.
Sprint's 34 new markets:
  • Anniston/Oxford, AL
  • Montgomery, AL
  • Macon, GA
  • Alexandria, LA
  • Houma/Bayou Cane/Thibodaux, LA    
  • Lake Charles, LA
  • Ruston, LA
  • Allegan, MI
  • Bay City, MI
  • Monroe, MI
  • Greenville, MS
  • Kinston, NC
  • Lumberton, NC
  • Lawton, OK
  • Muskogee, OK
  • Enid, OK
  • Oklahoma City, OK
  • Stillwater, OK
  • Salem, OR
  • Bedford, PA
  • Juniata and Mifflin counties, PA
  • Amarillo, TX
  • Beaumont/Port Arthur, TX
  • Corpus Christi, TX
  • Del Rio, TX
  • Longview, TX
  • Lufkin, TX
  • Midland, TX
  • San Angelo, TX
  • Victoria, TX
  • Fort Atkinson, WI
  • Marshfield/Wisconsin Rapids, WI
  • Sheboygan, WI
  • Whitewater, WI
The full list of markets with 4G LTE coverage is available here. If your location still isn't up there, I feel your pain. Pittsburgh, too, remains nowhere to be found.
Source: Sprint

[APK/Website Teardown] Next Up For Android Device Manager: Remote Password Changing And Device Locking

When Google launched the Android Device Manager in early August, I applauded the initiative because we finally got a much-needed security solution that was built into every Android devices that ships with Google's services. Rather, it was a good start, since the functionality was so limited: location, remote wipe, and alarm.
For the last two days, I've been digging around the new Google Play Services APK 3.2.64 that started rolling out to Android devices everywhere. If you remember, Google Play Services is the company's secret weapon to combat lack of device updates, as Google can push new functionality to everyone without the need for OS patches. Think of it as a collection of services and libraries that other apps can use.
Last time, such an update allowed us to detect the advent of the Android Device Manager four days early - the APK was detected around August 3rd while the Device Manager was launched on August 7th. This time, I suspect the same thing will happen, and we're on the verge of seeing a new much-needed feature: remote password changing and device locking.
After finding the changes in the APK, I switched my attention to the Android Device Manager's site and was able to dig up the messaging for the new functionality. Furthermore, I was able to roughly figure out the look for the new prompt. I'll start with that:
wm_9-15-2013-5-20-16-PM
This makes the Device Manager instantly 100% more useful. Before, if your device was stolen, all you could do was attempt to track it or wipe all the data - there was no middle ground. Remote locking with a new password is the missing command you can issue immediately, while attempting to figure out exactly what happened. It would suck to wipe your device and then find out that your significant other borrowed it, wouldn't it? But at the same time, it's an added peace of mind to have while scrambling to collect your thoughts.
Oh, and you won't have to do anything to the Device Administrator functionality since, as we saw when Android Device Manager was launched, it already requested access to remote device locking and password resets:
Screenshot_2013-08-03-12-47-26 Screenshot_2013-08-03-12-47-19

APK/Website teardown

Here are some instances of the new locking functionality in the APK and the website.
These strings gained the "lock" parts in Google Play Services 3.2.64:
<string name="mdm_reminder_notification_text">Set up remote lock and factory reset</string>
<string name="mdm_settings_wipe_title">Allow remote lock and factory reset</string>
Under MdmDispatcherService, we now have new code that fires the lockNow() and resetPassword() functions, as long as the new password satisfies the password policies on the device (min number of characters, symbols, numbers, upper case letters, etc). Otherwise, an error is returned and the minimum requirements listed so you can adjust the new password accordingly.
if(!((DevicePolicyManager)dpm).resetPassword(str, 0)) {
  // figure out what failed
} else {
  ((DevicePolicyManager)dpm).lockNow();
}
Some code from the website:
Yj="We could not lock your device. Please try again."
Zj="We successfully reset your password and locked your device."
ak="We successfully sent a lock request to your device."
df='<div class="password-req"><div class="req-preamble">Your new password was not strong enough.  Your device has the following password requirements:</div><ul class="password-req-list">'
ef='<div class="pwd-dialog-container"><div class="pwd-dialog-text">Your device will be locked with a new password. You should reset this password after your device is found. Do not reuse your Google Account password.</div><input class="dialog-input" id="pwd-dialog-in1" name="pwd-dialog-in1" type="password" placeholder="Enter new password"><input class="dialog-input" id="pwd-dialog-in2" name="pwd-dialog-in2" type="password" placeholder="Confirm password"><div id="pwd-error" style="display: none;"><div id="pwd-error-text"></div></div></div>'
I just love when all the pieces come together. I fully expect Google to announce and launch remote password changing and device locking as early as tomorrow or sometime later in the week.

APK Download

Google Play Services updates roll out silently, so chances are you already have this update. If you don't and want to download the new Google Play Services APK 3.2.64 (the previous version was 3.2.25), you can do so below:
Google Play Services
Download Google Play Services from Google Play
QR code for https://play.google.com/store/apps/details?id=com.google.android.gms
500,000,000+ downloads
166101 ratings (3.3 avg)

 
Design by Free WordPress Themes | Bloggerized by Lasantha - Premium Blogger Themes | cheap international calls