Root Multiple questions directly and indirectly related to updating to JB

[shyFluttershy]

Hello, everyone. As I said in the title, I have a bunch of questions that relate one way or another to the whole process of updating to JellyBean.

1.
A few months ago, I followed this tutorial to the letter to format my external SD card. I made my larger partition FAT32 and my smaller partition ext2, because I was using stock ICS. I can't remember which thread it was anymore, but somewhere in these forums someone said that for JB, the SD card should be ext3. How important is this? If it's no big deal, then good: It's one less thing to worry about. But if it matters, what's the proper order of operations here? I imagine pulling the card before I update, re-formating it, and then putting it back after I update would be the most prudent thing to do.

1a.
I assume that after all is said and done, I'll be able to re-root one way or another and once again be able to use Link2SD? (I really, really hope that this will fix my problem with the external SD card spontaneously un-mounting!)

2.
Given the issues people are reporting with the JB update, what's the better way to go about this: Do I do the OTA update? Do I use Kies and hope it's got JB in the pipeline? Do I flash a JB ROM someone posted here?

3.
Given the issues people are reporting with the JB update, would it be feasible to give Cyanogen Mod a whirl? Is it compatible with VM's SGR?

4.
In the event I end up starting from scratch, how much will I hate Google Hangouts?

Thank you!

 

[bkttk2]

Hello, everyone. As I said in the title, I have a bunch of questions that relate one way or another to the whole process of updating to JellyBean.

1.
A few months ago, I followed this tutorial to the letter to format my external SD card. I made my larger partition FAT32 and my smaller partition ext2, because I was using stock ICS. I can't remember which thread it was anymore, but somewhere in these forums someone said that for JB, the SD card should be ext3. How important is this? If it's no big deal, then good: It's one less thing to worry about. But if it matters, what's the proper order of operations here? I imagine pulling the card before I update, re-formating it, and then putting it back after I update would be the most prudent thing to do.

1a.
I assume that after all is said and done, I'll be able to re-root one way or another and once again be able to use Link2SD? (I really, really hope that this will fix my problem with the external SD card spontaneously un-mounting!)

2.
Given the issues people are reporting with the JB update, what's the better way to go about this: Do I do the OTA update? Do I use Kies and hope it's got JB in the pipeline? Do I flash a JB ROM someone posted here?

3.
Given the issues people are reporting with the JB update, would it be feasible to give Cyanogen Mod a whirl? Is it compatible with VM's SGR?

4.
In the event I end up starting from scratch, how much will I hate Google Hangouts?

Thank you!

Hopefully I can answer some of this.

1. After you are rooted just see how link2sd reacts. I know that I use ext3 but that is just something I had chosen. Not sure if it is required. If you did standard OTA and then rooted from there then you should be able to select link2sd - recreate mount scripts choosing your ext2 partition. Once you reboot all your previous links should be intact.
(At least this is how it should work)

2. I do not know if JB is currently available via KIES. If it is then that might be the most successful option. Just remember to back-up any data as the KIES update will wipe everything.

It does not work for everyone but I accepted the OTA update and then after backing up files I selected the factory reset and just started fresh from there. I applied some of the recommended settings for lock screen freezes (etc) and things seem to be running smoothly.

3. Unless you find a Cyanogen Mod rom that states it is specifically for the Galaxy Reverb and is confirmed by others to be working do not try to flash it. I think currently there are only two custom JB Roms available at this time, Party Time JB and Fusion JB

4. I do not use Hangouts so I can not comment on that one.

 

[sanjuro77]

I don't mind Hangouts at all.

 

[shyFluttershy]

I don't mind Hangouts at all.

How would you compare Hangouts to Talk? Is it anything like the GMail app update, which I'm not very fond of? (Dangit, Google, it wasn't broken! Why did you try to "fix" it?)

Thanks.

 

[sanjuro77]

Hangouts has a somewhat different interface, just like anything else new, that takes a bit of getting used to, but it's fairly intuitive and I didn't have any difficulty picking it up. I used to use it a lot, too, my old house did not get great cell reception but we had satellite internet, so I basically used Hangouts/talk as my primary form of communication for quite a while.

 

[shyFluttershy]

Hangouts has a somewhat different interface, just like anything else new, that takes a bit of getting used to, but it's fairly intuitive and I didn't have any difficulty picking it up. I used to use it a lot, too, my old house did not get great cell reception but we had satellite internet, so I basically used Hangouts/talk as my primary form of communication for quite a while.

I use Talk for chat/texting. (I have a low-minutes plan, so I've asked my co-workers to text me instead of calling me if they need to tell me anything.) The screenshots of Hangouts on the Google Play Store page make it look a lot more cluttered than Talk is. And considering that the SGR is kind of slender, well...

Thanks.

 

[shyFluttershy]

I found /system/app/Talk.apk and uploaded it to my Dropbox -- does this mean I can have my gTalk back if I find myself wiping clean and starting fresh?

(yay...?)

Thanks.

 

[sanjuro77]

Theoretically, yes, but personally I've had problems in the past trying to install system apks (which doesn't necessarily mean you will have the same issue)

I found a Google Talk apk, install-able, over at xda though!

http://forum.xda-developers.com/showthread.php?t=2281290

 

[shyFluttershy]

Theoretically, yes, but personally I've had problems in the past trying to install system apks (which doesn't necessarily mean you will have the same issue)

I found a Google Talk apk, install-able, over at xda though!

http://forum.xda-developers.com/showthread.php?t=2281290

Cool. Because I also un-did the GMail update and backed up that apk, too. :dalek:

Interesting how the Talk.apk from xda is 1.2 MB while the Talk.apk I backed up from my /system/app/ directory is 2.1 MB.

Thanks.

 

[shyFluttershy]

2. I do not know if JB is currently available via KIES. If it is then that might be the most successful option. Just remember to back-up any data as the KIES update will wipe everything.

It does not work for everyone but I accepted the OTA update and then after backing up files I selected the factory reset and just started fresh from there. I applied some of the recommended settings for lock screen freezes (etc) and things seem to be running smoothly.

I tried going the Kies route, but it hangs after it finishes downloading the firmware components. Fortunately, my phone seems completely oblivious to this miserably failed attempt. Looks like I'll be doing the OTA followed by a factory reset as soon as I can get to a place with wi-fi.

Thanks.

 

[shyFluttershy]

Everything I care about is backed up, and with luck I didn't forget anything. Thanks to sanjuro77, I have an installable .apk of gTalk. My backed up older version of the gMail .apk may or may not work, but I can live with it if it doesn't.

I'm as ready as I'll ever be for the factory reset. From there will be re-rooting and greenifying ... or should that be greenifying, then re-rooting? Or does it matter?

Fingers crossed, breath held!

Thanks.

ETA: OMG so full of win! JB came with the older versions of gTalk and gMail, and with auto-update turned off, I'm good to go with respect to this! (yay...!)

 

[sanjuro77]

Sweet, glad you finally got everything worked out!