Ah OK cool. Thanks.
in your battery stats, what processes are listed as using your battery?
Ah OK cool. Thanks.
It's good! It's a stylish, solid phone and has plenty of power. Jellybean is very smooth on it. Its only weakness in my opinion is the one day of battery, but I don't mind it because I have plenty of time in my day near a plug.My Droid X is getting long in the tooth and is slightly broken. I was looking for a non-$200 ICS phone. Nexus (Verizon) for $49 from Amazon looks like a good deal. Is this a good or bad idea?
I downloaded CPU spy but the only thing I can tell is that my phone wasn't going into deep sleep. So I found an app that seemed to be the problem. But what does the 1200, 700, and the 350 MHz represent? Not really sure what that's supposed to tell me. 700 MHz is 60% of the last hour and 15 minutes.
Screen 39%in your battery stats, what processes are listed as using your battery?
Is your phone rooted? If so, get better battery stats from here. Reset the timers and let the phone sit for ~2 hours, then post a screenshot of your partial wakelocks.
Amazing. I just came in here to ask if anyone heard where the OTA was.
If you’ve got a Galaxy Nexus HSPA+ device, you will receive a prompt alerting you to the update over the next several days. Up next for Jelly Bean: all Galaxy Nexus, Nexus S, Motorola Xoom and of course, Nexus 7, which will ship with Jelly Bean later this month.
Update: A Google spokesperson has informed us that the company has not pushed out any changes to search functionality in connection with the Jelly Bean update.
I'm so ready to pull the trigger and get myself a Nexus phone. Problem is, I want to stay on Verizon and I can't trust them to get JB pushed to phones in a timely manner. Apparently, it took 4-5 months for them to push out the ICS 4.04 update.
I guess the bright side is that I can continue to keep my eyes and ears out for news of a new Nexus phone in Q4 while I monitor how Verizon handles the JB update. (And to get out ahead of the argument: I want to avoid having to go through the "trouble" of rootin' 'n' romin'.)
Screen 39%
Android OS 37%
Phone idle 7%
Cell standby 6%
Browser 4%
Voice calls 3%
Android system 2%
Would take and post a screenshot but I'm at work.
Haven't rooted it yet.
Anyone on the dev preview of Jelly Bean...firstly fuck you, secondly here's your OTA link to update to final version of Jelly Bean http://android.clients.google.com/p....signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
Apparently the Verizon version was just inaugurated into the AOSP Nexus family, meaning that starting with Jelly Bean it should be in lock-step with the rest of the Nexii. In any case, I highly doubt anything like the 4.0.4 fiasco will happen again, and even if it does, the Verizon GN is still #2 in update speed and is head and shoulders above every other handset except the GN HSPA+.
Time to start clearing data for Google Services Framework and spamming check now...
So is there a rock solid, stable AOSP rom for Verizon Nexus yet?
Latest version of Jelly Belly seems to have a million issues.
And what kernel should I use? Keep on with leankernel?
Looks like our main man coco was the dude to break it at XDA. Hope he isn't banned here too long.
Also thanks for the links! Flashed it via temp CWM.
Still don't like how you have to use other things to flash updates unlike the N1
wowLooks like our main man coco was the dude to break it at XDA. Hope he isn't banned here too long.
Also thanks for the links! Flashed it via temp CWM.
Still don't like how you have to use other things to flash updates unlike the N1
It's cool guys, I made bail
takju (Play Store) 4.0.4 IMM76I to final 4.1.1 (JRO03C) OTA link http://android.clients.google.com/p....signed-takju-JRO03C-from-IMM76I.5c416e9c.zip
How exactly do you apply this? I downloaded and unzipped it.
lol, you could show him the galaxy nexus toolkit
Really? I'm running 2.6 and haven't noticed any problems. I'm using whatever kernel it comes with by default. But to answer your question, I haven't seen an AOSP ROM that's 100% good to go yet.
That things freaks me out more than fastboot for some reason.
/#su
How exactly do you apply this? I downloaded and unzipped it.
Method 1 - CWM recovery installed
1) Download the correct update for your build on to your computer;
2) Open the archive and delete the recovery folder;
3) Copy the file to /sdcard on your device;
4) Reboot into CWM;
5) Select "install zip from sdcard";
6) Select "choose zip from sdcard";
7) Select the update the you just copied to your device;
8) Wait until it completes. Reboot. Done.
Method 2 - Stock recovery installed, Unlocked bootloader
1) Download the correct update for your build on to your computer;
2) Copy the file to /sdcard on your device;
3) Download CWM from here and place it on your computer in the same directory as your fastboot binary. For CDMA/LTE devices, use this version;
4) Rename the CWM image to cwm.img
5) Reboot into fastboot mode;
6) Open a command prompt in the same directory;
7) Type fastboot devices to make sure your device is recognized;
8) Type fastboot boot cwm.img
9) Select "install zip from sdcard";
10) Select "choose zip from sdcard";
11) Select the update the you just copied to your device;
12) Wait until it completes. Reboot. Done.
Method 3a - Stock recovery installed, Locked bootloader, with root;
1) Download the correct update for your build and place it in /sdcard;
2) Open a command prompt in the same directory as your ADB binary;
3) Type adb devices to make sure that your device is recognized;
4) Type adb shell
5) Type su
6) Type cat /sdcard/name-of-zip-here.zip > /cache/name-of-zip-here.zip
7) Type exit
8) Type exit
9) Reboot into recovery;
10) Hold the volume up key and press the power button;
11) Select apply update or whatever the menu item is (I don't have a stock recovery installed, but it should be easy to identify);
12) Wait until it completes. Reboot. Done.
Method 3b - Stock recovery installed, Locked bootloader, with root (use this method only if you have to -- use 3a or 3c first);
1) Download the correct update for your build and place it in /sdcard;
2) Download CWM from here (CDMA/LTE devices, use this version) and place it in /sdcard;
3) Rename the CWM image to cwm.img;
4) Open a command prompt in the same directory as your ADB binary;
5) Type adb devices to make sure that your device is recognized;
6) Type adb shell
8) Type su
9) Type dd if=/data/media/cwm.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
10) Type exit
11) Type exit
12) Reboot into recovery;
13) Select "install zip from sdcard";
14) Select "choose zip from sdcard";
15) Select the update the you just copied to your device;
16) Wait until it completes. Reboot. Done.
Method 3c - Stock recovery installed, Locked bootloader, with root;
1) Install ROM Manager from the market;
2) Flash CWM using ROM Manager;
3) Reboot into CWM;
4) Select "install zip from sdcard";
5) Select "choose zip from sdcard";
6) Select the update the you just copied to your device;
7) Wait until it completes. Reboot. Done.
Method 4 - Stock recovery installed, Locked bootloader, no root;
You need to either: 1) root or 2) unlock your bootloader or 3) wait until you get the update pushed to you OTA
Okay so mine was a factory unlocked phone. Will i still automatically get 4.1?
I am finally back on stock Jelly Bean 4.1 and patiently waiting for the 4.1.1 OTA. All the custom ROMs so far are a waste of time.
I was toying with the idea of going back to the iPhone for the time being but for some reason I couldn't do it. Weird how that works.
When Apple releases an iOS update, is that a roll-out too or does everyone immediately get a notification?
Update anxiety.
You'll probably be on the iPhone and with no thought of switching to android a couple of weeks before iOS6 hits.
Everyone immediately, worldwide.
Did you get a jelly bean beta in several iterations weeks before final release?And Google can't do this with their own devices, because ...?