Jellybean Information

[akash3656]

High-res contact pics do sync.
I repeat: HIGH-RES CONTACT PHOTOS SYNC SERVER-SIDE ON JB

(Confirmed by using updated hexsync to get 720x720 pics and a full wipe)

Good to hear. However other people have reported that we have to reupload the pictures as they were initially stored in low resolution.

Sent from my Galaxy Nexus using Tapatalk 2

 

[ArmanUV]

Good to hear. However other people have reported that we have to reupload the pictures as they were initially stored in low resolution.

Sent from my Galaxy Nexus using Tapatalk 2

yes that's true. You have to reupload.

 

[CubicTom]

Couldn't you just push these files back to folder and reboot and have stock recovery when ota arrives then flash it protect root with ota rootkeeper then reinstall cwm recovery
/system/recovery-from-boot.p
/system/etc/install-recovery.sh

Yes.

Sent from my Galaxy Nexus using Tapatalk 2

Interesting. Think I am going to do that, too.

When making CWM permanent, I just renamed the recovery-from-boot.p and kept it in the folder. Thus, I could just rename it again and OTA should install fine, right?

However, I did not do anything to the install-recovery.sh before or after I installed CWM (should I?). Just checked the folder and a file named like that is there, sized 559 Bytes and dated 01 Aug 2008, 14:00. Is this already the one I need?

Moreover, do I need any further steps of uninstalling CWM or anything when the OTA comes around? When answering this, please take my signature information into account.

Thanks very much for the support!

Cheers :beer:
CT

Sent from my Galaxy Nexus using xda app-developers app

 

[NCguy]

Can you provide a market link?

Edit: Found it, but it claims its not compatible with my ROM version

Sent from my Galaxy Nexus using Tapatalk

Does the app developer have to explicitly add the new rom version or is it just a black list? If it has to be added then aren't all non-Installed apps going to show initially as incompatible until the developer adds them whether or not they are in fact not compatible?

 

[fnd66]

Jelly Bean looks great hope for a better battery live

 

[Nick_Stylz]

Jellybean

For some reason on my Gnex running 4.1, it doesnt have the Set Mobile Data On/Off slider?? Which means that credit will just be taken off my phone when I leave Wi-Fi range. Please help

Thanks

 

[Jezz_X]

For some reason on my Gnex running 4.1, it doesnt have the Set Mobile Data On/Off slider?? Which means that credit will just be taken off my phone when I leave Wi-Fi range. Please help

Thanks

try "settings\data usage" its in there at the top

 

[jjc_01]

High-res contact pics do sync.
I repeat: HIGH-RES CONTACT PHOTOS SYNC SERVER-SIDE ON JB

(Confirmed by using updated hexsync to get 720x720 pics and a full wipe)

When you say "hexsync" do you mean HaxSync? Because I have bought that app but haven't given it a try in JB. If it finalyl shows up in HD on my HD AMOLED screen I Would be so happy!

 

[navodwickra]

When you say "hexsync" do you mean HaxSync? Because I have bought that app but haven't given it a try in JB. If it finalyl shows up in HD on my HD AMOLED screen I Would be so happy!

I found this app works better than HaxSync :good:

 

[jjc_01]

I found this app works better than HaxSync :good:

And its free? Sounds like its too good to be true! I'll have to test it out.

 

[navodwickra]

And its free? Sounds like its too good to be true! I'll have to test it out.

it's free and it joins your contacts too.

 

[Stretlow]

So let me get this right, if I reupload my pictures to google contacts on my pc through the gmail site, then re-sync my contacts I should have high res pictures on the phone?

 

[derPianist]

So let me get this right, if I reupload my pictures to google contacts on my pc through the gmail site, then re-sync my contacts I should have high res pictures on the phone?

Right!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2

 

[fnd66]

how do you get a better battery life.. its really bad :crying:

 

[CubicTom]

how do you get a better battery life.. its really bad :crying:

First of all, this is a really general question and also doesn't give us much information about what you have tried already and _how bad exactly_ it is. I shall nevertheless give it a try:

Maybe the battery needs to be recalibrated, which is a common issue after flashing a new ROM.

To do so, charge your phone to 100% without interruption, then unplug the charger and leave the phone running without recharging it until the battery is completely empty such that it turns itself off.

Repeat this procedure twice.

After that, battery statistics should again reflect your battery's full capacity.

If battery life is still bad after that, you should check under settings -> battery, if there is any particular process eating up all the power.

Also, if you want to temporarily increase your battery life above its usual level, say for outdoorsy activities, you can use an app like SetCPU to reduce the processor speed available. However, you need to be rooted to do that and the CPU settings need to be handled with care!

Apart from all this, turning off Bluetooth, NFC and WiFi whenever it isn't needed and reducing your screen's brightness can help extend your battery life. Also, if you are somewhere without any mobile signal reception, you will save heaps of capacity by entering flight mode, since the network search is quite energy intensive.

Sent from my Galaxy Nexus using xda app-developers app

 

[kristovaher]

I am not sure if this was already here in 4.0.4 (it wasn't in 4.0.1), but I am glad to see that it is possible to set phone lock timeout again. Back when I used HTC Desire I had a PIN code on my phone for casual security, but since at times I switched the screen off and soon after on again (like when in a store to look at something) I didn't want to enter the PIN all the time. So I had a time lock set for it, that it only asked for PIN if I didn't use the phone for five minutes.

This was not an option in Android 4.0. If you used PIN security then every time you turned off the screen and back on again, it asked for a PIN. Especially horrible when it timed out. It became an annoyance enough that I ended up using Slide Lock only.

Now it's possible again to set the timeout forphone lock, making sure that your phone is locked only after X amount of time. I love it! It even has an option to check if power button instantly locks or not.

 

[CubicTom]

I am not sure if this was already here in 4.0.4 (it wasn't in 4.0.1), but I am glad to see that it is possible to set phone lock timeout again. Back when I used HTC Desire I had a PIN code on my phone for casual security, but since at times I switched the screen off and soon after on again (like when in a store to look at something) I didn't want to enter the PIN all the time. So I had a time lock set for it, that it only asked for PIN if I didn't use the phone for five minutes.

This was not an option in Android 4.0. If you used PIN security then every time you turned off the screen and back on again, it asked for a PIN. Especially horrible when it timed out. It became an annoyance enough that I ended up using Slide Lock only.

Now it's possible again to set the timeout forphone lock, making sure that your phone is locked only after X amount of time. I love it! It even has an option to check if power button instantly locks or not.

As far as I remember, this has also been a feature in 4.0.4 already.

Sent from my Galaxy Nexus using xda app-developers app

 

[efrant]

[snip]

When making CWM permanent, I just renamed the recovery-from-boot.p and kept it in the folder. Thus, I could just rename it again and OTA should install fine, right?

Right.

However, I did not do anything to the install-recovery.sh before or after I installed CWM (should I?).

There are two files place on your system (by OTA updates) that cause the recovery partition to be re-flashed on every re-boot. install-recovery.sh is the script that flashes recovery-from-boot.p to your recovery partition. Deleting or renaming one or both will prevent this from happening.

Moreover, do I need any further steps of uninstalling CWM or anything when the OTA comes around? When answering this, please take my signature information into account.

No. (Although I have seen people having issues with Stericson's busybox installed.)

 

[CubicTom]

Thanks efrant, for your useful reply which helped extend my understanding!

[Snip]
I have seen people having issues with Stericson's busybox installed.

Can you recommend any other busybox version which is not expected to cause such problems?

Cheers
CT

Sent from my Galaxy Nexus using xda app-developers app

 

[efrant]

Thanks efrant, for your useful reply which helped extend my understanding!

Can you recommend any other busybox version which is not expected to cause such problems?

Cheers
CT

Sent from my Galaxy Nexus using xda app-developers app

I use Busybox Installer, and I have it install the latest version of busybox in /system//xbin