• 5,810,319
    REGISTERED
  • 53,422
    ONLINE NOW

Posts Tagged: Samsung Galaxy Nexus

vzw galaxy nexus update

Not too long ago we talked about a test build of the Verizon Galaxy Nexus appearing on Google’s servers, and now it would seem Verizon has finally decided to roll this out to the masses. The update is available via OTA push, which can be initiated manually via Menu > Settings > About Phone > System Updates. If you prefer to wait for the automatic push, you should begin to receive a notification on your device shortly.

You can find the update instructions and information from Verizon or visit the Official VZW Jelly Bean Update thread to discuss the OTA.

SMS Error

Most consider Jelly Bean to be the greatest version of Android released thus far. It’s fast, smooth, it has Google Now, and all sorts of other features that not many people have complained about. There are a few things here and there, however, that may annoy certain users. One example is a text limit that will give you the pictured warning if you send too many texts in a short time.

While the rate limit there to prevent malicious apps from hijacking your text messaging, some think that it’s set too low. Now there’s a fix. According to XDA Senior Member erishasnobattery, who posted the fixes:

JRO03H had a limit set of 100 messages in 30 minutes, which probably kept all but the most avid texters in the clear. However, when we merged to JRO03L last week, it had dropped to 30 in 30 minutes. Personally, I think it was a typo and should have been 300, but either way, it triggered on me so I set out to fix it.

If you couldn’t tell from the update names, this is aimed at the Samsung Galaxy Nexus. Not only has erishasnobattery fixed the issue on the ROM he maintains, but has created fixes for some other popular Gnex ROMs, such as BAMF, AOSP, and a special one for CM10.

If you’d like to get rid of the warning, check out the original thread. However, keep in mind that with the new limit set to 500 messages in 30 minutes, there is a little more room for malicious activity.

Advertisment
SprintLTE

It’s pretty bad that Sprint is slated to be the last of the four major US carriers to give their customers nationwide 4G. (Though some may call into question the “4G” aspirations of certain carriers.) It doesn’t make it any better that their 3G, which the majority of customers are still using, needs a dramatic makeover. Is there anything that could make it worse? How about if your device was set to only use the most stable signal, thus preventing it from receiving 4G data signals. Turns out, that’s actually happening. Samsung Galaxy Nexus owners on Sprint who are fortunate enough to live in a 4G area may still not be receiving 4G, and now there may be an answer as to why.

According to XDA Senior Member Jimlarck:

If you live in an LTE area and you still aren’t getting LTE its maybe because your 3G signal is stronger than your 4G signal. Toroplus Galaxy Nexus were programmed to only stick with the most stable connection.

If you seem to have LTE Coverage and you aren’t getting 4G LTE then it may be because of your 3G.

The methods to fix the problem also create new problems, but thankfully they’re both quite easy to roll back from. The easiest one is simply changing the Preferred Network Mode to LTE Only. However, this was found to kill phone and text capabilities. The other method requires requires the use of dialer codes, and editing your MSL using a tool by XDA Recognized Developer -viperboy-.

For more info, check out the original thread.

boot 2 gecko

When we brought you news of the Motorola Defy running Boot to Gecko, it was brought to our attention that the Samsung Galaxy Nexus was already doing so. Upon closer inspection, it was found that not only was the GSM Galaxy Nexus indeed had a Boot To Gecko port running, but that the Verizon variant very recently got its own B2G working as well.

XDA Senior Member Axel2033 is working on the build for the GSM model, and XDA Forum Member jellybellys is working on the Verizon port. The Verizon B2G has a lot of things working, but also a lot of things not working, which include:

Cell service (1x, 3g, and 4g)
screenshot
camera only sometimes works
no softkeys
All resources are designed for hdpi, so everything’s a bit small

This is by no means a daily driver. However it is still an excellent opportunity for anyone who wants to see what B2G is all about. While there isn’t a working / not working list for the GSM version, Axel2033 has said in no uncertain terms that it’s a highly experimental build, so that means the GSM Nexus version isn’t daily driver material yet either. Even so, it’s really cool to see B2G making its way around the forums.

For more info, check out either the Verizon Nexus B2G thread or the GSM Nexus B2G thread.

nexus-one-boot-screen

As we’ve discussed before, the allure of the Google Nexus devices are their timely updates to the latest and greatest versions of Android. However, that has hardly been the case for the CDMA Nexus devices. With the Verizon Galaxy Nexus receiving test builds of Jelly Bean, Sprint users have been wondering when their official Jelly Bean update would be coming for the Samsung Nexus S 4G and the Galaxy Nexus. After the OTA update was put on hold last week, Sprint is now officially rewarding their customer’s patience.

According to Sprint, the Galaxy Nexus update brings:

Nexus Software Update – L700.FH05

Enhancements/Fixes:

Operating system upgrade Android 4.1 Jelly Bean.  Below is a list of a few changes:
– Notification Bar – Expanded view of emails
– Meeting Makers – more information to notification bar.  Provides the ability to snooze and dismiss meetings from the notification bar.
– Addition of Google Now (online search):

  • Voice search
  • Integrated approach to search features within Google services

And the Nexus S 4G update brings:

Nexus S Software Update – JRO03R

Enhancements/Fixes:

Operating system upgrade Android 4.1 Jelly Bean.  Below is a list of a few changes:

– Notification Bar: Expanded view of emails
– Meeting Makers: more information to notification bar.  Provides the ability to snooze and dismiss meetings from the notification bar.
– Addition of Google Now (online search):

  • Voice search
  • Integrated approach to search features within Google services

As always, applying the update will remove root. So if that is important to you, make sure to watch for a rooted update from one of XDA’s talented developers.

ADA

Around here, many users enjoy various AOSP-derived ROMs. There are quite a few options, including such well known ROMs as CyanogenMod, AOKP, and ParanoidAndroid. There are many more options as well, which is great because the more the merrier.

Now, the Android Developer Alliance development team has released the AffinitySERIES ROM to various devices. Their missions statement is pretty simple, as explained by ADA member, and XDA Recognized Developer, blueHarford:

One of our biggest things is No Drama, no secrets, BIG on communication which i think alot of other teams lack. We are not the best we will not boast ourselves or ever use the word kang. We feel like one of the first teams to start AOSP project to where it truley is part of the open source community. Were not out for recognition were out to make good products.

The initial release includes the Verizon and GSM Galaxy Nexus and the Nexus 7. These new ROMs bring some old favorites, like Theme Chooser, but also bring a number of features including:

Fast, Responsive, Intuitive & Professional UI
GLaDOS v2.1 Power Kernel Built In
First of its kind Customized Toggle Icons
Custom Awesome Popup SMS Features
Facebook Contacts Support
Custom Power Widget
4 Way Reboot Menu
Exclusive ADA Wallpapers
5 Way Lock Screen Targets
Beautiful Weather Lock Screen
Quiet Hours
Voice & Data (SVDO)
T9 dialer
SuperSU
BusyBox
Customized Navbar Settings
Statusbar Customizations
Modified Navigation Bar Options
Clock Modifications – Left, Center, and Right Clock AM/PM Weekday Abbreviation
Battery Options 6 Styles to Choose
Theme Chooser
Many, many more…!

Users are reporting that the ROM works well and has very few issues. Most are reporting no issues at all, which is great for a Jelly Bean ROM. Now that the initial release is out of the way, the team is looking forward to the host of other devices they plan on supporting in their second round of releeases. The official list includes:

Asus Transformer TF101
Asus Transformer Infinity TF700
Samsung Galaxy Tab2
Droid RAZR/RAZR MAXX
Samsung Galaxy Nexus (toroplus)
Samsung Galaxy Note
Samsung Galaxy SII and SIII

If you’d like to learn more, check out either the Verizon Galaxy Nexus thread or the GSM Galaxy Nexus thread, both posted by XDA Senior Member purian23.

Galaxy Nexus

When most users tear down their devices, it’s to fix something. That is, unless you’re XDA Elite Recognized Developer AdamOutler, who just does it for fun. When tearing down a device, users usually need a guide of some sort and, of course, the replacement parts necessary to make the fix. Now, Samsung Galaxy Nexus users have a tear down and fix tutorial that’ll help them get into the device, fix what they need to fix, and back out without damaging anything.

The video and tutorial was created by XDA Forum Member armanatz, who originally wrote it up to help those who need to fix their power button. However, since that involves taking the device mostly apart, this method could also be used for the replacement of other basic parts. However, it’s probably not the best option if you need to use it to replace the mobo or other core components.

With the appropriate tools, you can get it taken apart and put back together in about 20 minutes as shown in the video provided. Also, don’t forget that messing around with the phone’s hardware is potentially risky if you don’t know what you’re doing. So if you decide to do it, you do so at your own risk. To learn more, hit up the teardown thread.

galaxy nexus

Since the unveiling of the original Nexus device, Google has made it a point to state that owning a Nexus device means you’ll be on the fast track to new OS updates. However, this has not been the case for owners of the CDMA variants of the Galaxy Nexus.

At Google I/O 2012, the GSM Galaxy Nexus received Jelly Bean. Around that time, the bookies and odds makers in Vegas began taking bets on when the CDMA versions would be as lucky. It’s been three months now, and neither the Sprint nor Verizon Galaxy Nexus have been updated. But maybe that is changing.

As of last night, reports began coming in about an update notice that began appearing for certain Verizon Galaxy Nexus owners. After investigation, XDA Senior Member oldblue910 determined that it is test build JRO03O, and requires a lengthy process to be able to apply the update, which requires you to first return to the IMM76Q update, flash to IMM76K, and finally apply the JRO03O update. You will need to be unrooted and stock in order to apply the update, but if you are so inclined feel free to download the update directly from Google’s servers.

Samsung-Logo

When flashing an AOSP ROM on a CDMA phone, it’s a win-some lose-some affair. You gain the functionality that comes with a pure Android experience. However, you traditionally lose USB Modem and Diagnosis Mode on your device. For those who are unaware, USB Mode and Diagnosis Mode are accessed via codes you enter into the dialer. This is not only required to activate the phone on some networks, but also helpful in alleviating some problems like restoring your IMEI using QPST. However, for many Samsung devices, that is no longer a problem. Now, you can get all this functionality back without flashing back to a stock ROM.

XDA Senior Member autoprime has put a thread that not only gives a profound amount of information but also provides a script to make it all easier. The suggested way is to use a script manager application to apply the script. As autoprime explains:

Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed. You may or may not have to unplug/plugin the usb cable after new mode is set.

Also provided is a plethora of instructions. This is a huge step for the supported devices, which include:

The Epic 4G Touch was having some troubles with the script, but autoprime managed to fix it in short order. Additionally, this method will soon support other devices. So if you’ve had to flash back and forth between AOSP and stock just to use these codes and your phone is supported, it’s time for some celebration.

 

To learn more, head over to the original thread.

 

Update: Given the abuse, the link to the thread has been removed. We apologize for any inconvenience.

CyanogenMod-10-CM10-Jelly-Bean

We recently told you about the CyanogenMod team beginning work on CM10. Now, a significant milestone has been reached: CM10 Nightlies have appeared for select devices. For those who aren’t familiar, a nightly build is an automatic build incorporating the latest changes in CM source for a device. Yesterday, CyanogenMod released the list of those devices that would be getting the first round of nightlies:

# The US SGS3 variants (AT&T, T-Mobile, Sprint)
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (VibrantCaptivateInternational, and i9000b)
# The SGS2 i9100g
P3 and P5 tablets

That list will grow as other devices become ready and receive the blessing from their maintainers to begin nightlies. Be sure to keep your eyes open for when your device joins the list.

Update: We’ve received various reports from XDA Forum Member Scotto70 and others that the Nexus 7 build is currently nonfunctional. So if you’ve got a N7, we recommend that you hold off for the time being!

Slim Bean Android ROM

With the release of the Jelly Bean source code to AOSP last month, we are seeing more and more of Jelly Bean ROMs ported to various Android devices. Slim Bean is the Jelly Bean variant of the popular Slim ICS ROM, and it is now available for several devices including the Samsung Vibrant, Nexus S, Galaxy Nexus (Verizon, sprint, and GSM variants), Samsung Captivate, and Samsung Galaxy S I9000.

Slim Bean’s predecessor Slim ICS has been quite popular as a very lightweight and fast AOSP-based ICS ROM, with just the right amount of tweaks and mods added to it, including some by the ROM developer and others from AOKP and CyanogenMod. With Slim Bean, XDA Recognized Contributor krarvind aims to bring the same features to Jelly Bean, while still keeping it fast and lean in the tradition of his previous work.

You can download all variants of Slim Bean ROMs from the Slim ROMs website. Below are the links to the device-specific threads for Slim Bean where you can find more details and join the discussion:

Nexus VIA

We have guides for just about anything here on XDA. If you need to fix a soft brick, reflash stock firmware, root your device, unlock your bootloader, or use a custom recovery, there’s tutorials all over the site for it. So, what about radio chip set repairs and reprogramming? Those are a little harder to find, as they are a bit more complicated than flashing stock firmware. Such guides do exist though, including one that was written for the VIA chipset found in most newer Samsung phones. This includes, among others, the CDMA/LTE Samsung Galaxy Nexus on Verizon and Sprint.

XDA Senior Member autoprime has released a guide that will help anyone looking to repair or reprogram their VIA chipset devices. The guide is quite extensive and includes a number of methods, fixes, explanations, processes. In short, if you have a VIA chipset device (specifically the CBP7, CBP7.x, or CBP7+), this is a thread worth reading.

There is quite a bit of information to digest. Users can find anything from PRLs to an ETS Mode tutorial, from MSL acquisition to EVDO reprogramming. One could even repair their MEID and ESN. However, it should be noted that cloning ESNs is definitely not allowed. If any info regarding that shows up, the post will be immediately deleted, and the user will get into some trouble. Educational purposes only.

For additional information, check out the original thread.

15dknif

As those of us lucky enough to be running Jelly Bean have found out, Adobe Flash isn’t officially supported. While many no longer care about the dying technology, quite a few of us still have use for it.

XDA Recognized Contributor stempox has found that by simply side-loading the APK, users are able to view media content as always through the native Android browser app. From there, users simply have to enable plugins in the browser settings, as was done in previous versions of Android.

Naturally, this will not work with Chrome Browser, which doesn’t support plugins and has supposedly replaced Browser as the default web browser on the platform. However, since Browser still comes as the default browser on the Galaxy Nexus and (presumably the Nexus S), this still has the potential to help quite a few.

For those running the Google Nexus 7, which does not come preloaded with Browser, you must manually install Browser. Luckily, this is also possible, thanks to a guide written by XDA Forum Member Censura_Umbra. In order to accomplish this, users need to copy over Browser.apk to /system/app using a root-enabled file manager and modify its permissions accordingly. Afterward, users have to remove or rename a couple of files that would otherwise cause issues with the app. What about Flash? According to XDA Forum Member NeoMagus, Flash content works just fine when installing Browser this way. Alternatively, users have reported that side-loading the latest version of Firefox browser works as well.

To get started, head over to the Adobe Flash and Nexus 7 Browser installation threads.

Advertisement

XDA TV: Most Recent Video

Buy/Sell on Swappa

  • Nexus 5 (Unlocked) buy | sell
  • Galaxy Note 3 (T-Mobile) buy | sell
  • HTC One M7 (Verizon) buy | sell
  • Galaxy S 5 (Unlocked) buy | sell
  • Nexus 7 2013 buy | sell
  • Swappa is the official marketplace of XDA