yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jcmm11:
I just installed 1.3 using twrp with no issues. What I do with each upgrade:

1) download Rom and verify md5 to make sure I got a good download.

2) make sure my titanium backup is up to date. Backup all data for user apps plus selected system data (accounts, sms/mms store, and I just added a few more. But those 2 are the primary ones I'm worried about.

3) nandroid backup

4) full sdcard backup to pc. This includes nandroid's and titanium files, just in case.

5) boot into recovery

6) wipe caches plus system. Do NOT wipe data.

7) install new Rom plus any kernel and mods

8) reboot system.

9) re-add any init.d scripts plus add any manually installed system apps (nova and apex in my case)

10) Reboot

11) run titanium and restore all data (only)

12) reboot and you should be all set with your system back except for newer Rom
[Samsung Galaxy Nexus] mwalt2:
The assert failed:get prop ("ro.product.device) makes me think you're flashing it to the wrong device. Are you with Verizon using the Galaxy Nexus?
[Samsung Galaxy Nexus] stillthisguy:
I am on 1.2 and all the GAPPS show installed in the Play Store for me.
[Samsung Galaxy Nexus] Sveke:
Bet you a million bucks vicious borked your partitions.

Anyone I've seen run into problems with recovery run vicious at some point or screwed things up with tibu.
[Samsung Galaxy Nexus] MarkGbe:
guys, any ideas why after a fresh flash to 1.3, fill wipe... My phone does not appear under "my devices"on the play store website?

FIXED... it showed up on its own. :)
[Samsung Galaxy Nexus] veloslave:
Hi Walt

Just wondering... I am on v1.2 and everything seems happy with no problems (that I know of) so I am wondering if you recommend v1.3? Definitely not a problem if so... all of your ROM/updates have been like butta. Just the same, and thank you in advance for your time in providing this awesome ROM and follow up care... I appreciate your opinion.

If you ever decide to start taking "thank you's" in the form of $... I would love to be the first to donate.
[Samsung Galaxy Nexus] mmidgley:
Lock before unlock mod

mwalt2, I realize you've been busy with 1.2* and 1.3... but I was curious about the status of the lock before unlock mod--any plan for this mod to be uploaded again? thanks!

i've been so busy i'm still on 1.1 but plan to flash the latest 1.3 rsn.

m.
[Samsung Galaxy Nexus] Txwolf1980:
I got that coming from v1.1 of this ROM to vicious. Had to redownload it, and it worked fine. Came back to thus ROM via a nandroid restore. But, I would advise redownliading the file from the minus mirror, and see if that helps

Sent from my jellied up mROM v1.1
[Samsung Galaxy Nexus] Sheetzie03:
Yes Verizon
[Samsung Galaxy Nexus] Sheetzie03:
Well I actually did download a 2nd time with the same result. I thought about trying the mirror instead of the devhost download but when I clicked on the mirror it brought me to a page asking me to sign up so I just redownloaded the devhost link.

I'll try messing with it again tonight, if nothing else works, the one response said Vicious may have borked my partitions, so if nothing else works and this does happen to be the problem, what fixes it? Partitioning the SD?

Quick side note-i did flash the JB bootloader recently, wanted to make sure mentioned it just in case.
[Samsung Galaxy Nexus] Txwolf1980:
I just flashed 1.3 fine, off of the dev host site. Do you have a pre vicious nandroid of 1.1 handy? If so, maybe restore to that, then try flashing? I don't think the bootloader would be the issue, since that is below the recovery kernel. I could be wrong. But, that's my guess.

---------- Post added at 01:51 PM ---------- Previous post was at 01:45 PM ----------

OK, mWalt. Just jumped from 1.1 to 1.3, full wipe. So far, everything is perfect. Wallet is the primary reason I updated. So, thank you.'

I'm officially on board with the donations. Slap a link on.
[Samsung Galaxy Nexus] Sheetzie03:
Sorry to say I don't have a backup of 1.1. The only backup I have is of Vicious 4.1.1v1. I wonder if I tried 1.2 of this rom.Also, what if instead of downloading from my phone, I DL from my PC. Just trying to think of anything.

Edit: tried flashing 1.1 with same result.
[Samsung Galaxy Nexus] Sheetzie03:
So I tried to install 1.1 to see if I would give me the same error it does with 1.3 and it did. Can I get some advice on what to do? I tried to redownload, same thing, was going to try from the mirror but its not there. What should my next move be?
[Samsung Galaxy Nexus] hidden_dragon:
I ran into the same problem of the "failed" install. I fixed it by downloading the flashable version of CWM and replaced TWRP. Flashed v1.3 and all is well. Booting into v1.3 now! Good luck...
[Samsung Galaxy Nexus] Sheetzie03:
I will def. Try this now! Ty what link did you use for CWM?
[Samsung Galaxy Nexus] hidden_dragon:
This one: http://xdaforums.com/showthread.php?t=1777949

I flashed this differently. Instead of going into TWRP recovery, I flashed CWM through GooManager (free app). It downloaded an img file to the root of the internal SD. After that, it flashed CWM and rebooted. From there, boot into CWM recovery and flash away.
[Samsung Galaxy Nexus] Sheetzie03:
Hey, yeah I use goo manager as well, great app!

Any you were right as soon as I went to CWM from twrp, it worked right away. Why wouldn't this ROM work with twrp? Weird.

But thanks to you and everyone else who are responded. Much appreciated

Last question, from recently following this thread, the best kernel for battery life looks like faux or trinity? Is this about right? If so, which trinity kernel(looks like there is 2) and is the faux Kernel mentioned a few pages back the correct one to use? Thanks a lot
[Samsung Galaxy Nexus] ethanhunt123:
Thanks so much for this ROM. Awesome! :victory:
[Samsung Galaxy Nexus] hidden_dragon:
I think kernels are a matter of preference. I always liked Faux's kernels. You should try both and see if there are differences. Give each trial at least a few days...you really won't see any differences in a day.
[Samsung Galaxy Nexus] stkiswr:
Does anyone know any basic themes that work with this rom
[Samsung Galaxy Nexus] UniqueNate:
So I had this ROM running for days now and everything worked just fine. No hiccups or anything. I went downstairs to eat dinner with my family and come back up here to get on XDA from the app. It just stayed at the loading screen. I thought it was the app. So I uninstalled it a few times and tried again. It didn't work. Then I tried data related things. It just stayed at the loading screen. I turned the phone off and rebooted. It stays at the Google screen for about 5 minutes. I took out the battery. I then went into recovery from holding down the up and down volume and the power button. wiped everything and rebooted. Stayed on the google screen for more then 5 minutes. I took the battery out. I then restored my back up. rebooted. stayed at the google screen for about 5 minutes and finally played the boot animation of the trinity kernel for another 5 minutes. Finally reached the setup wizard. Weird?
[Samsung Galaxy Nexus] mwalt2:
Any AOSP based theme would probably work. I haven't modified the apk's from how they are output from AOSP.

That seems to be about par for the course with the jelly bean roms for toro (at least in my limited experience flashing this and a couple other ones). I've never had it not get past the Google screen, so probably just being patient and not worrying about pulling the battery would work. It would be nice to find out why this happens, but it may not be totally fixed until we get a Verizon JB rom with new radios, etc.
[Samsung Galaxy Nexus] mmidgley:
I installed 1.3 "dirty" over 1.1 using cwm. I only cleared cache and dalvik first. I also applied the tether zip after letting the rom boot once. Everything seems to be working fine. I do notice that my Google backup still says local debug. Is this still broken, or is it because I upgraded "dirty"? (that saved me a lot of time, maybe enough time to not worry about Google backup for now). I do have nandroid and titanium backups, but I like not having to use them...

m.
[Samsung Galaxy Nexus] Shamrock13:
Is it safe to flash from 1.1 to 1.3 after a cache/dalvik wipe or would it be safer to do a full wipe?
[Samsung Galaxy Nexus] mwalt2:
I personally think it's always best to do a full wipe. However, if you aren't having any trouble and do not use google backup and restore, you'll probably be fine. The local debug is fixed if you do a full wipe, but again isn't really important if you don't use that feature. As far as I know, it will not hurt anything else (it's how it gets built from AOSP by default).
[Samsung Galaxy Nexus] Shamrock13:
Flashed it. Its pretty good so far. I'll let you know tomorrow if its any different.

Also, do you know how I can get Google Wallet?

And this ROM does run slow when its plugged in to charge. I didn't notice that till right now.
[Samsung Galaxy Nexus] keith7120:
Running very smooth. I did a clean install from ICS 4.04 to JB 1.2 I did a dirty intall from JB 1.2 to JB 1.3. I'm using the battery mod, tether mod and the extended power mod. listed on the OP. I did have issues with HBO to GO, Discover Card and Goggle Wallet. I restored those items from Titanium Backup and they all work as expected. I used Goggle Wallet at 7 Eleven to be sure it worked. I'm also using the latest Stable Faux Kernel. JELLY BEAN Rocks!!!
[Samsung Galaxy Nexus] mwalt2:
There's a thread in the nexus software forum that you can find Google wallet. If you've ever had it installed, it should show up in your app list from a PC and maybe your phone.
[Samsung Galaxy Nexus] jedil1c1ous:
not as smooth as the rest

Is it just me or is this the least smooth of all the 4.1 roms? I started with the Vicious GSM port and it seemed very smooth, then I went to the AOSP version and it seemed the same. I flashed mROM and it seemed less fluid when scrolling in multiple places so I went back to the Vicious AOSP and it did seem more smooth again... the only reason why i came back again to mROM is because I wanted more stock... but it seems a little glitchy on scrolling sometimes. Is it just me?

I've done a full data wipe before flashing and I only have the battery mod on it right now.
[Samsung Galaxy Nexus] imablackhat:
I personally do not notice any lag. I was on vicious v3 and have been on mrom cuz I like the stock ness since he released v1

Could possibly be the kernel you are using.

I use trinity with any rom.
[Samsung Galaxy Nexus] jedil1c1ous:
Hmm... I'll try trinity... I don't like Faux because it seems to make my phone get even more hot (then usual) when using 4G.

EDIT: Using the Trinity kernel appears to have improved the scrolling for me... but I hate the 'color tuning' that he added... makes everything look dark, blue, and bad. Ugh.
[Samsung Galaxy Nexus] UniqueNate:
First time I experienced it with any jelly bean Rom. I know the first boot after any kernel flash or Rom flash takes a sec, but this was simply turning the phone off & back on because nothing would open after just using the phone a few minutes before. I had the Rom running flawlessly for days, and the Google screen was stuck for almost 10 min. That's not normal for just powering on your phone. A fresh first boot Rom didn't even take that long past the Google screen. Boot animation, maybe for the first time. But like you said, it could be a Toro thing.
[Samsung Galaxy Nexus] glacius48:
owner info

anyone having problems getting their owner info to show on their lock screen?

-----UPDATE

Owner's info does work. The information is masked by "charging" or "Charged" when hooked up to battery.
[Samsung Galaxy Nexus] djp952:
I found this little gem of a command to fix Google Backup without having to wipe data. I wish I knew the original source so I could give them credit:

bmgr transport com.google.android.backup/.BackupTransportService

Turn off backup completely in settings (uncheck both checkboxes), then run that command. It should magically switch to the gmail backup account, but you might have to reboot.

bmgr is actually kinda cool once I looked into it. Another related cool command I learned is dumpsys backup. This will dump the status of the backup service, including how many things are pending. It appears backup doesn't work on wifi (could be wrong), so when I was playing around I switched to 4G, executed bmgr run, and watched with dumpsys backup until everything was pushed.
[Samsung Galaxy Nexus] fclifton:
Does not show up on mine.
[Samsung Galaxy Nexus] mwalt2:
It shows up fine for me (see screenshot...was trying to type 'test' but auto-corrected to "rest" :)). Make sure you aren't charging when you're trying to look at it. If you aren't charging and still don't see it, you might see what mods you've installed.
[Samsung Galaxy Nexus] SwampNutz:
I'm still waiting for a glitch to happen. This phone is sooo smooth now, switching between applications, and finally typing is super smooth. My only beef is with the apparent increase in battery consumption but I'm waiting a few more days to see if things change in that dept.
[Samsung Galaxy Nexus] fclifton:
Ah, I was charging! When I am not charging it does show up.
[Samsung Galaxy Nexus] mwalt2:
I can't seem to get the lockbeforeunlock mod to work correctly. It launches the camera or google now, but you still have to swipe to the unlock button to get the pattern or keypad to show to secure unlock. The power menu mods linked in post 1 will work fine with this rom and only modify android.policy.jar, so it will not interfere with the tethering mod and they can be flashed in any order.
[Samsung Galaxy Nexus] jfriend33:
If you install the trinity control you can adjust the display...
[Samsung Galaxy Nexus] jfriend33:
Now all the sudden after flashing cwm touch and job boot loader my GPS won't lock yet latitude works and battery is burning quickly...

Think I'm gonna start from scratch on 1.3. BC my life was phenomenal before.
[Samsung Galaxy Nexus] BMWPower06:
is this rom Deodexed?
[Samsung Galaxy Nexus] mmidgley:
I haven't had a chance to use this mod yet (i'm ready to!) but I thought this is how it is supposed to work:

Turn on pattern or pin lock. Power off. [assume its now locked] Power on. Regular unlock is displayed first. Swipe to unlock and then pattern or pin security unlock is displayed. Unlock and use.

Power off. Power on. Regular unlock is displayed. Swipe to use camera or gnow. After using camera or gnow, either power off or press back to be presented with security unlock screen. (are you saying that the issue is that at this point you have to swipe to unlock before getting the security unlock screen? if so, i could live with that!)

Did I describe the desired behavior correctly? I'm in a situation that requires the security unlock to be used, but

I can't wait to be able to access camera faster!

thanks!

m.
[Samsung Galaxy Nexus] mwalt2:
It used to be you just slide to the camera and it presents the pattern/pin lock. Once entered, the camera opens. What is happening now is slide to camera, screen stutters, then you have to slide to unlock, enter pattern/pin, and then camera opens.

Yes
[Samsung Galaxy Nexus] johnhimm:
Coming from JellyBelly ROM. Love the pure stock feel of this ROM.
[Samsung Galaxy Nexus] NinJustin:
This is the only Jelly Bean Rom I've installed and I was seeing some serious problems sending Google Voice Texts. They would queue up and never send or send but also display as queued and not send newer messages.

I seemed to be reciving texts fine but sending them it randomly queues them up.

I reinstalled clean and was still having issues. I also reinstalled the app a few times as well before and after reflashing. I'm back using Cyanogen 9 for now and don't have any problem even here at my office where I get hardly any signal. If It does queue up it sends out shortly there after properly. I've not seen anything like it in any other older rom either.

I know the issue is in both 1.2 and 1.3
[Samsung Galaxy Nexus] stillthisguy:
The only issue I have seen so far on 1.3 is that when sending a picture message, the message just sits on sending. One did finally send, about 2 hours.
[Samsung Galaxy Nexus] mmidgley:
I went ahead and did a full wipe so I could get Google Backup going. Indeed, it came up fine after a full wipe and install. However, I noticed that it broke (meaning reverted to local backup) after I had attempted a titanium restore for just apps/data and flashed the tether mod. I'm not sure which messed it up (thought I didn't do any system stuff with the titanium restore). I ran the bmgr transport command line suggested by djp952 and was back to using my google account for backup. (prior to doing the full wipe install, when I was on a dirty install I did not have the 'com.google.android.backup/.BackupTransportService' transport installed and bmgr always seg faulted when run with any parameters).

m.
[Samsung Galaxy Nexus] johnhimm:
Google Voice Text messages are working for me. I'm on 4G at the moment.
[Samsung Galaxy Nexus] stillthisguy:
Same
[Samsung Galaxy Nexus] johnhimm:
What are people using as a Kernel? I care more about battery life than lightning speed.
[Samsung Galaxy Nexus] Txwolf1980:
I'm on faux. 1350, and I'm getting just as good as stock, totally smooth. I'm thinking about trying trinity, just to compare. But, faux 19b9 is very stable.

Sent from my jellied up mROM v1.3
[Samsung Galaxy Nexus] Hungry Man:
Are you using the SmartReflex edition or just the Ultimate Edition?
[Samsung Galaxy Nexus] johnhimm:
20B2 is out, downloading it now.
[Samsung Galaxy Nexus] Txwolf1980:
According to the thread, ultimate+ smartflex. Apparently all of his beta covers both.

Sent from my jellied up mROM v1.3
[Samsung Galaxy Nexus] NeoMagus:
Also not having any issue at all with Google Voice texts. Only slight quirk I've noticed twice after pulling it off the charger overnight the screen completely locked up when I went into settings to force close maps and required a battery pull. Other than that its been golden
[Samsung Galaxy Nexus] Sparky977:
I'm loving this ROM for the most part. However, I am having a couple issues. When I take a picture, they don't get saved. They have the new animation but then just disappear.

Another problem is that I can't delete some folders from the interior sdcard. Audible started acting up, and the only way to fix it was to erase and reinstall, but then it wouldn't recognize the files saved. When I try to delete the Audible folder through Root Explorer, it keeps telling me "Delete failed". I can rename it but not delete it.

Lastly, the notification drop down says "T-CDMA 64" I stead of Verizon.
[Samsung Galaxy Nexus] Hotstuff5964:
Any way to get drop down toggles?
[Samsung Galaxy Nexus] rsxtypes72:
Try power controls
[Samsung Galaxy Nexus] slayer621:
(deleted, wrong thread)
[Samsung Galaxy Nexus] redstar427:
Should I upgrade mROM from v1.1 to 1.3?

I am still running v1.1 of mROM, and it seems to work just fine.

I edited build.prop, and fixed Google Wallet and MyVerizon myself.

I installed the latest JB bootloader, PRIMELC03.

I can see Hulu Plus in the market.

I don't restore apps automatically, when I wipe, I use it as an opportunity to change the design of my home screens and groups. :)

I don't use VZW Backup Assistant.

Maps and the compass feature works, and I have no close friends to test Latitude.

As far as I can tell the Gapps in the Play Store, are still ICS versions so the JB versions would not update yet anyway.

Is there anything I am missing?

I am not opposed to flashing 1.3, but don't see a need just yet.

Also, at the moment, I like the included kernel.

I tried the faux kernel, at 1200 and 1800, and also Franco JB kernel and could not tell even a little difference in performance.

Again, mwalt2, thanks for your work on this rom, and everyone else who helps with testing and posts. :good:
[Samsung Galaxy Nexus] Shamrock13:
Sadly, I'm having an issue with this ROM. I have my phone on half brightness and WiFi/Bluetooth off. I have 3G/4G and my phone drops 10% by the hour.

Its been off the charged for 2 hours and has a screen time on of 11 min and its at 79 percent. I don't know why this is happening. Anyone recommend a good performing battery saving kernel?

I did do an install of 1.3 over 1.1 so that could be it.

Let me know what you think please.
[Samsung Galaxy Nexus] Hotstuff5964:
:good:
[Samsung Galaxy Nexus] impulse101:
You can flash CM10, it has toggles and is the fastest rom and least issues of all jb roms
[Samsung Galaxy Nexus] veloslave:
I keep looking...

So many ROM's... so many features, I look at them all and read all of the threads (and that's a lot of reading) but so far I have not found a reason to move from this rock solid ROM. I am still running V1.2 with no additional kernel, and EVERYTHING works perfect including GAPPs updates. I run Nova as my Launcher and ExDialer for, yeah, dialing. After getting rid of an exchange account I didn't need any longer I am getting 12 to 16 hours (on a standard batt) of solid use as my daily driver.

I have added a softkey & battery mod found here

http://rootzwiki.com/topic/29153-mod-411-jelly-bean-soft-key-mods-with-menu-and-search-stockbb/

Power menu reboot recovery mod here

http://filetram.com/mediafire/powermenurebootrecovery-zip-8930795455

I also use the battery mod and the native tethering hack that mwalt has posted in the OP.

BTW, my scrolling owners info is working correctly.

Thanks again mwalt... appreciate your time and support here on such an awesome ROM.
[Samsung Galaxy Nexus] SwampNutz:
Tried to download the reboot/recovery mod but the file has been yanked due to some sort of violation :crying:
[Samsung Galaxy Nexus] stillthisguy:
Here is the one I have always used for this ROM. https://www.box.com/s/a8beb8091841375df886
[Samsung Galaxy Nexus] jpntaka:
I'm not sure if anyone else is having this issue, but my gmail doesn't sync automatically.

I tried unlinking the gmail account and then relinking it, which would fix it for a while. However, the problem occurs again after a few days.

I know I have my gmail to automatically sync.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joshtb86:
im flashing it now, but does anyone know if the tcdma64 bug means anything? or is it just a bug?

Thanks!
[Samsung Galaxy Nexus] Txwolf1980:
Just a bug.

Sent from my jellied up mROM v1.3
[Samsung Galaxy Nexus] joshtb86:
thanks wolf...

flashed the bootloader, rom, gapps and native tethering and stuck in a loop.

im going to rewipe, then just flash ROM. anyone else have bootloop problems?
[Samsung Galaxy Nexus] mwalt2:
This rom has gapps, so that could have been you're problem. When I first put it together, a separate gapps package wasn't readily available.
[Samsung Galaxy Nexus] Txwolf1980:
Also, I'd just flash one thing at a time. Rom + mods all in one recovery session can easily cause a loop

Sent from my jellied up mROM v1.3
[Samsung Galaxy Nexus] joshtb86:
i think it was gapps + multi flashes. all good now. thanksj!
[Samsung Galaxy Nexus] SwampNutz:
I've been running this ROM for a few days now and I haven't had any major issues. Battery usage is getting better as it was a fast drain for the first couple of days losing about 10% every 40 min or so, but now things are starting to return to normal. I'm using an extended battery btw. I took the phone off the charger at about 6:30am this morning and it's now 4:26pm and I have 74% battery left and I never placed this on the charger. This is with WiFi, GPS, background sync, BT and 4G turned on.

I REALLY love this phone since putting 4.1.1 on it!
[Samsung Galaxy Nexus] stillthisguy:
Check out these two pictures I took on the ROM v1.3 clean install. Barely different angles, but yellow on one but not the other. Thought this issue was resolved?
[Samsung Galaxy Nexus] stillthisguy:
Here is a thread to help correct the issue.

http://xdaforums.com/showthread.php?t=1739839
[Samsung Galaxy Nexus] mwalt2:
The camera is OK now I think. The yellow tint before happened with every single picture. That looks like the whit balance could just be off in the first one. Are you seeing it in a lot of pictures?