These days, it seems like everybody is trying to make Android more secure. As usual, rooting and modding are often casualties of this effort. Just over a month ago Android 4.3 broke the existing model for root, forcing updates to existing methods, and now Samsung is rolling out updated Android 4.2.2 firmwares for the Galaxy S 4 which fully enable the company's heavily secured KNOX environment. Fortunately, Chainfire is already on top of it and has updated his popular root software, SuperSU, to be compatible with the new system.
Every version of Android has launched with at least one headlining feature. As any true fan would know, the 4.2 camera brought with it a very cool new mode called Photospheres. While the initial hype has dropped off, the popularity of photospheres still continues to grow, thanks in part to improvements in image quality and the addition of a Maps-based community designated for sharing the immersive images. We don't always want a location attached to our regular pictures, but it's pretty rare when we don't want our photospheres to be geotagged.
Updates are rolling out to Nexus devices as we speak, but the public changelogs seem to only call for improvements to "Security." However, the latest round of commits just went up on the Android Open Source Project, bringing everything up to date with both JWR66Y (4.3_r1.1), which is going out to most Nexus devices, and JSS15Q (4.3_r2.2), which is destined for the 2013 Nexus 7. Thanks to Google's gracious sharing of the source code, we can comb through each and every little detail of what's new.
If you sprang for an HTC One Developer Edition back when the phone was launched and have been patiently waiting for your Jelly Bean 4.2.2 update, you might as well stop waiting. But that's a good thing! According to a Twitter post from HTC's Global Sales President and Head of America Jason Mackenzie, the Developer Edition will skip right over the incremental 4.2.2 update and go straight to 4.3.
@jmwein we definitely care and want you to have great experience.
If there is one thing we all eventually rely on with mobile devices, it's having a sturdy Wi-Fi connection. Whether it's because of a low data cap, you live or work somewhere with a weak cell signal, or like me, the local cellular technology is stuck in the stone age, you probably have a few wireless networks saved on your phone or tablet. While you probably take it for granted that your devices will automatically connect to these networks when they are in range, some people are finding that feature hasn't been working as expected since upgrading to Android 4.3.
Little things can add a lot of otherwise unnoticed polish to the apps we use and the games we play on a daily basis. Thanks to animations, sound effects, music, and custom graphics, our software tends to feel more responsive and engaging. But sometimes a bug comes along and breaks a part of that experience. Today, we're going to take a look at one of the more user-facing bugs to sneak out with Android 4.3: automatically looping sounds are broken in numerous apps.
Update: The Nexus 7 2013 build (codename "Flo") has now been posted. It's the first official CM build for the new Nexus 7.
ROM addicts, the time has come. The CyanogenMod team has been working diligently on version 10.2 of the popular ROM family, the Android Jelly Bean 4.3 update. Tonight the first batch of nightlies are being posted to the download page, Get.CM. There are only a few devices with updated builds at the moment, but that should change as the night progresses.
The great Nexus 7 ordeal of 2013 is now over after Qualcomm apparently agreed to the release of the factory image and all necessary drivers, only a day after lots of hubbub had been made about this touchy and unpleasant situation. Awesome, so now we have access to the factory image, meaning we can restore the tablet back to stock no matter what happens to the software on it.
Say, you had a bad flash and are now boot-looping.
We're all happy to see Android 4.3 finally make its appearance, especially as it brings some pretty important and positive low-level improvements like Bluetooth Low Energy and TRIM support. Unfortunately, new versions often introduce new bugs that slip by even the most diligent testers. Jelly Bean 4.2 had its fair share of issues, including an almost comically bad oversight: the total annihilation of December in the stock Contacts app. This is why each major release is often followed by a couple of bug fix OTAs in the following weeks.
Update: Looks like we were right.
ROM developers and Android tinkering enthusiasts alike have probably noticed at this point that the new iteration of the Nexus 7, unveiled two weeks ago, does not yet have factory images or driver binaries posted on the appropriate Google Developers page. A similar issue plagued the Nexus 4 in its early days, though eventually images were posted. At the time, legal issues were speculated as a possible reason for the delay, and Android build maintainer JBQ - largely responsible for the images / binaries - said only this in response: "I can't comment."
With the new Nexus 7, JBQ has not outright said that legal problems with Qualcomm are preventing the factory images (and possibly the driver binaries) from being published, but a quick look at the relevant evidence makes it pretty duh-obvious that's what's going on.