Galaxy Nexus 2 to Debut Running Android 4.1, JellyBean
Samsung and Google have reportedly partnered up once again to create a successor to the wildly popular Samsung Galaxy Nexus.
However, this device will debut running Android 4.1, JellyBean software, according to YouMobile.com.
Last year's Galaxy Nexus made headlines when it introduced the world to the highly anticipated Android 4.0, Ice Cream Sandwich software. Samsung seems to have a handle on creating devices that optimize the Android experience, and the original Galaxy Nexus was a perfect example of this.
Get Our Latest News for FREE
Certain variants of the Galaxy Nexus have already been upgraded to Android 4.1 JellyBean.
Sprint customers who own the smartphone are still waiting for the update to roll out. Samsung issued a minor software upgrade last week in order to bring the carrier's version of the Galaxy Nexus up to speed.
It brought the device's software build version to number L700.FG01, and slightly tweaks its on-screen signal strength indicator, along with adding support for Sprint TV.
The update also changes the default settings on Wi-Fi and LTE making them "on" now that Sprint's LTE network is fully operational.
Galaxy Nexus users who have already upgraded to Android 4.1, JellyBean for the GSM version of the smartphone are currently experiencing issues with its GPS as it does not work, even with several satellites in view.
In order to diagnose the problem, owners of the device can check to see if their GPS has been affected by opening up an app that constantly tracks where they are such as Google Maps and then check the notification shade for a GPS message. If it says "Searching for GPS," and they do not see a flashing icon, then they are not getting a GPS lock and there device has been affected by the bug.
They can also test to see if the bug is present by downloading the GPS Test app and see if they have satellites within view.
Android Central posted a simple fix for the problem. Users can go to the Settings option, choose Location services, uncheck and re-check "Google's location service," and the problem should be corrected, according to the site.
