yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jthompson0019:
This ROM has made my phone awesome for many months now. Of the many android phones and tablets I've ROM'd this ROM was the very best. Good luck to the whole Sourcery Team and thanks for your work and dedication.
[Samsung Galaxy Nexus] Droid0351:
So what is future hold for the sourcery team and what plans are for there next phone?
[Samsung Galaxy Nexus] NeverSeparate:
Thanks for the work you guys put in.
[Samsung Galaxy Nexus] carpenter311:
The white app gallery doesn't have picasa photo sync?
[Samsung Galaxy Nexus] jesssiii:
Flash the 4.2 Camera zip from mods, you will have Picasa sync.

Toro GNex

Sourcery 5.3 Final
[Samsung Galaxy Nexus] jakmayhopher:
I just want to say thank you to Eagle, and everyone else that helped with this ROM. It was my very first ROM I downloaded when I learned how to root, I will miss you guys. This is my favorite, and I will always support. Thank you guys.
[Samsung Galaxy Nexus] gohamstergo:
only ROM ive ever had on my GNex since i got it. maybe ill move to whatever phone yall go to next!

also, change log for 5.3? doesn't seem youve updated your change log page yet. :)
[Samsung Galaxy Nexus] boomerbsg:
Wow.. I didn't see this coming lol. My GF will be bummed as she's got a rock solid 4.5 install on her Nexus, and was waiting for me to update hers to 5.x I had lost my back ups of my 4.5's by my own hand. and had decided to just try out AOKP until 5.3 was done since I just could not get a satisfying install of the 5.x versions as of yet.

When I picked up my GNEX for vzw, this was the first Rom i tried, and LOVED it. truly no other like it. While other ROM's aren't bad, they are no sourcery ;)

I'm due for an my upgrade in July, and I wasn't going to use it, but I'm gonna take this as a sign, been eying the Note 2 for quite some time now.

Good luck to all the Dev's involved with sourcery, and look forward to seeing y'all on other devices/phones I hope.

And now I get to flash the final JBS :crying:

cheers
[Samsung Galaxy Nexus] 93fuelslut:
I'm lost. Isn't this a aokp based ROM? My aokp backup app doesn't recognize therom and a aokp version themed MMS isn't compatible with this rom.
[Samsung Galaxy Nexus] tdevaughn:
no, it is not aokp based.....
[Samsung Galaxy Nexus] thechainrule:
Is Apex launcher laggy as hell for anyone else?
[Samsung Galaxy Nexus] jonstrong:
No - both Apex and Nova have been great. Slightly different feel, but either is a fantastic choice, and both seem totally fine with the ROM. Never an issue here.

One thought -- did you find it laggy in the first minute or so after boot? If so - give the phone a minute or two for all the processes to get initialized and to settle down (including your launcher). If still laggy, I suspect you'll want to do more homework and see what processes are active when you're having this issue.
[Samsung Galaxy Nexus] jediman:
I'm not sure if it's APEX or just the rom in general...or hell my phone.

I've found the last two iterations of Sourcery very laggy after a few hours. Everything on 'stock' as far as the rom goes, each time with a full wipe and reload and no apps installed.

Again it could be my phone. It's very picky these days and due for an upgrade I think.
[Samsung Galaxy Nexus] jonstrong:
What recovery do you have installed?

What steps did you follow before flashing?

I've found that, in general, the vast majority of devices behave the same if scrupulous attention is paid to the steps involved in wiping and flashing.

First, although TWRP is very appealing, and some are reportedly very happy with it, I would suggest CWM for this at the moment. I'm using PhilZ Touch version of CWM, and it works quite well, while offering more features and a better UI than stock CWM.

Wipe VERY thoroughly. Seems that many suffer weird behavior from insufficient pre-flashing wiping. Whichever commands you execute, be sure that the steps they perform include:

- wipe system

- wipe data

- wipe Cache

- wipe Dalvik cache

You may even want to Fix Permissions after flashing, although that shouldn't be necessary.

Once you've booted, make sure to account for background processes that can slow down the device, such as auto upload of pictures, social network apps looking for checkins and updating the world on every move you make.

One more thought - some kernels install their own ram drive, and installation of another kernel doesn't necessarily remove this. If you search the forum for frankenkernel you'll find the topic. Might be relevant, might not. But you should be aware of a possibility.

When I've been careful to do an extremely thorough scrub down before flashing, I just about never have an issue with a mature ROM like this.
[Samsung Galaxy Nexus] jakmayhopher:
Q

Is there a way to make the pull down background more transparent?
[Samsung Galaxy Nexus] KeithLing1115:
Small issue. I flashed the 4.2 test animation in the JBS tools and it wipes out the lock ring and lights. I tried to re-flash another couple different lock rings but they won't show. I even tried another animation and then lock ring but still no good. I went back to my nandroid and tried again in case it was a bad download but it happened again. There were a few other animations I tried that didn't do this but I love the 4.2 test. Is there Any way I can fix this manually or something. If not I can live without the lock ring but would be nice if there was a way to fix it. I've been on this rom since I've had my nexus and I'm sad to see you go. Best rom ever. No one can touch the mods in this rom.
[Samsung Galaxy Nexus] Alton (Halo 2):
Woah? this is his last update to this ROM ?
[Samsung Galaxy Nexus] justen7723:
Correct

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] 93fuelslut:
I'm lost. I thought aokp roms have the most options, and aosp Roms have little options like Cm.
[Samsung Galaxy Nexus] nordy420:
That is where sourcery was different :) no ROM touched it
[Samsung Galaxy Nexus] tdevaughn:
This is a mis-guided observation. Many aosp roms are feature packed
[Samsung Galaxy Nexus] taz1458:
Other then this one little issue rom is awesome. I I set the short cut on the clock to alarms and then hit the clock it restarts the phone. Other then that love this rom.
[Samsung Galaxy Nexus] twillet50:
Anyone else not receiving calls since going to 5.3? Don't know if it has anything to do with the rom or not.
[Samsung Galaxy Nexus] jonstrong:
Nope. Calls are fine here.
[Samsung Galaxy Nexus] anonymously:
Hey no big deal but I recently tried reactivating my nexus while I await a replacement note. After dialing *228 the dialer disappears making it impossible to press 1 to activate it. I'm not even sure what build this is. I restored this real quick after miui did the same thing. I assumed it was a miui thing. Don't know if anyone has came across it?
[Samsung Galaxy Nexus] jesssiii:
Not seeing either if these issues.

And, to the poster above me, my understanding is you're not supposed to dial that (*228) on a 4g phone. Try calling Verizon to activate your Nexus.

Toro GNex

Sourcery 5.3 Final
[Samsung Galaxy Nexus] jonstrong:
Sadly, the idea of dialing "*228" to update the PRL (preferred roaming list) on your Verizon Wireless phone is largely obsolete. The misinformation that's been circulating for the past couple of years about this is amazing. One story has it that doing so will fry your SIM -- this is NOT true. The other issue, that your post raises, is that dialing *228 only makes sense for a handful of 3G phones only -- it was never implemented for 4G / LGE phones on Verizon, and as a matter of fact, if you do this and it does manage to trigger a PRL update on your phone, you'll find that you wound up receiving a PRL optimized for 3G phones -- not 4G/LTE phones. Again - this is NOT permanent damage. PRL's are designed to be easily updated, and simply help the phone determine which towers to prefer over others when you're moving around.

If you can manage to get a knowledge VzW CSR on the phone, you'll learn that:

1) Verizon periodically pushes updated PRL's to 4G/LTE phones

2) The easiest way to force a PRL update on a VzW 4G phone is to power down completely and restart. On a Galaxy Nexus, this would mean a battery pull. I don't have one of the sealed phones with non-removable battery (like the HTC One), but I imagine there's an option to force a complete shut down and restart (i.e., cold boot).
[Samsung Galaxy Nexus] notoriousB:
Loaded 5.3 tonight and so far so good! Maybe a stupid question but is there a way to change the background color of the message input box in mms? I've adjusted everything else but can't seem to figure out how to do that. The send message "button" is all white on white. Not a big deal but it's bugging my ocd. lol

Sad to see this rom coming to an end. Thanks for all the efforts devs!
[Samsung Galaxy Nexus] jonstrong:
Yup - as I note above, *228 is pointless on a 4G/LTE Verizon phone. If you only need a new PRL, then a battery pull is sufficient. If you need your phone activated, call VzW. Make sure you have the "device ID" - ID (MEID, IMSI or IMEI) handy -- the CSR will need this to uniquely identify your phone and associate it with your account. With and the phone in hand, and a call to Verizon, you can be connected within 10 minutes.

Alternatively, look at the following page, and make sure you click the drop down and select "Android":

http://www.verizonwireless.com/b2c/nso/enterDeviceId.do
[Samsung Galaxy Nexus] gohamstergo:
Anybody having strange LCD density issues in misc 3rd party apps? One app I have ran fine in 5.2, but then I upgraded to 5.3 and now its buttons and text are huge and overlapping. The app hasn't changed at all. Installed it fresh (no data) from market a couple times and no luck. How do apps go about getting the LCD density info and how could they be getting the wrong info? Also tried changing the density away from and back to default, didn't help.
[Samsung Galaxy Nexus] Big Cam:
Where do you get this touch version of CWM? Is this one of the options when donating, or is this technically a separate recovery?
[Samsung Galaxy Nexus] justen7723:
Cwm touch

http://d-h.st/SBU

The recovery.img Is available at clockwork website. I took the liberty of putting it in a flashable zip.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Big Cam:
Thank you!
[Samsung Galaxy Nexus] justen7723:
No problem. :D

http://xdaforums.com/showthread.php?t=2131538

[74 lock mods/18 glowdots/Nav keys/searchlights 5/25/13][25 sound mods 5/6/13]
[Samsung Galaxy Nexus] jonstrong:
As well as the official CWM version of touch, see this - PhilZ Touch:

http://xdaforums.com/showthread.php?t=2201860

I've been using this on both my GNex (toro) and Nexus 10 (manta) for several weeks. The UI is definitely a step up from the official CWM UI's, on both touch and regular. Philz also has more features -- but is all built around the core CWM code. It's essentially CWM with a much improved wrapper / UI. Highly recommended.

If you DO check it out, read the whole main thread, then follow the link for the device-specific version to download the right one...
[Samsung Galaxy Nexus] justen7723:
+1 on that. Been using it a few weeks now.

Philz touch toro

http://d-h.st/iyT

http://xdaforums.com/showthread.php?t=2131538

[74 lock mods/18 glowdots/Nav keys/searchlights 5/25/13][25 sound mods 5/6/13]
[Samsung Galaxy Nexus] jesssiii:
Can ROM manager work with the Philz version?

Toro GNex on

Sourcery 5.3 Final

with a very Fancy kernel!
[Samsung Galaxy Nexus] taz1458:
For some reason my wallpaper disappears and won't come back up til a reboot. Any idea?
[Samsung Galaxy Nexus] jonstrong:
ROM Manager doesn't know about it for downloading...I haven't tried queuing up an install from ROM Manager so that it boots into recovery and runs the commands automatically with Philz Touch. Might work -- I think Philz is consistent with the way CWM uses an open recovery script, and if they both look at the root of the SD card for the script, all should be good.

If your thought is re: what you'd flash it with...there are some nice alternatives that let you flash it directly from within Android without having to go into recovery to flash...

---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------

What kind of themes do you have installed? Theme Manager? Launcher theme? these apps can both manage the wallpaper...maybe some kind of conflict?
[Samsung Galaxy Nexus] taz1458:
Have none installed. Didn't have this issue with 5.2. I'm assuming it's some kind of default wallpaper. It's about 3/4 of the page with just a light blue grainy circle almost the whole way up or something.
[Samsung Galaxy Nexus] jonstrong:
That is, indeed, the default wallpaper. Not sure if it still happens under 5.3, but there were a couple of mods that would require a reboot, and end up with the default wallpaper being displayed after reboot. I was pretty sure that this had been resolved in one of the last couple of versions. I've done a done of mods using the ROMs features, and haven't seen the default wallpaper reappear at all so far.

What recovery are you using? How did you prep your device (i.e., wipe) before install? There were enough changes in 5.3 to warrant a clean flash.
[Samsung Galaxy Nexus] taz1458:
I did install the no sound mod. Not sure if that's the reason? I use cwr. I did a full wipe and let the store recover and all that.
[Samsung Galaxy Nexus] jonstrong:
Odd... I haven't installed that particular mod, but I *have* use several of the other sound mods. Pretty sure they're doing essentially the same thing, swapping in different sound files to replace the standard named sound files. So far, I haven't seen a return to the default wallpaper in the last couple of builds.

Although eagle is focusing on other things now, there are a few folks left who were on the team who might be able to help out or recognize what's going on. I'd suggest trying the Sourcery forum itself at the teamsourcery.com site. Also - even faster - try Sourcery on IRC - some of the team still gather there daily. Best shot at getting an informed answer. (if you haven't use their IRC channel yet, there's a web interface to it here: http://teamsourcery.com/team-sourcery-irc/), or you can use a standard IRC client).
[Samsung Galaxy Nexus] notoriousB:
I had the wallpaper thing happen yesterday and I installed nothing to the phone all day. Halfway through the day the blue circle wallpaper showed up and even if I tried to set another photo instead of it it did not change until I rebooted the phone. Weird.
[Samsung Galaxy Nexus] tdevaughn:
Is the picture you used for the wallpaper in your gallery or in the cloud?
[Samsung Galaxy Nexus] jonstrong:
ahhh...good question! So, are you really asking, "when the ROM tries to reestablish the chosen wallpaper are SystemUI restarts, is it no longer available, forcing the system to leave the wallpaper at the default (which IS local to the ROM)?"...or something like that?
[Samsung Galaxy Nexus] tdevaughn:
Yes, that is where I was headed with this line of questioning
[Samsung Galaxy Nexus] notoriousB:
Mine are from the gallery.
[Samsung Galaxy Nexus] taz1458:
Mine too. Still having the problem.
[Samsung Galaxy Nexus] Stoney 666:
Back in ICS Sourcery, there was a "incoming message" notification tone... anyone still have that?
[Samsung Galaxy Nexus] johnnyb15613:
BeanPicker release date has been pushed back...

It is being reworked to coincide with White/Black Magic

This will take some work, as I'm trying to leave White completely stock and Black will be BP.

I'm sure it will take some tinkering, so please be patient and remember it will be supported until there are no more users!!
[Samsung Galaxy Nexus] gohamstergo:
Anyone else getting constant FCs of SystemUI?
[Samsung Galaxy Nexus] jonstrong:
Not a single one...
[Samsung Galaxy Nexus] gohamstergo:
Not sure if you're being sarcastic, but I read back a ways in the thread to try and find something similar, but couldn't..?

If you've really never heard of anyone with this issue, maybe I have to do another fresh install :\
[Samsung Galaxy Nexus] jonstrong:
No sarcasm! Maybe some misunderstanding though? A number of the UI mods will require restarting SystemUI. You'll see this, for example, when you change the lock screen glow dots or searchlight. I'm most of these cases, the Sourcery tools can successfully restart it. In some, a reboot will be necessary.

Are these the kind of issues you're seeing? When do you experience FCs?

...beamed to your puny "phone" by my Galaxy Nexus Avatar...
[Samsung Galaxy Nexus] jesssiii:
Only after I once did a dirty flash.

Toro GNex
[Samsung Galaxy Nexus] wtherrell:
Yes. & Loses wallpaper and nav buttons. Sometimes reboot fixes it, sometimes not. 5.2 doesn't do this. I have wiped & reinstalled several times. Wondering if perhaps some app update may have caused it
[Samsung Galaxy Nexus] jonstrong:
[MENTION=3547811]jessii[/MENTION]i -- I saw this out of context and did a double-take... :D
[Samsung Galaxy Nexus] wtherrell:
I can work around the nav button problem with button savior but it also loses status bar and notifications. If there were a "notification savior" app or some way to recover them I could stay on 5.3. If not, then it's back to 5.2
[Samsung Galaxy Nexus] mfinlay04:
Which recovery did you use to install the ROM? Don't use TWRP as it has some issues wiping system correctly. Also try and fix permissions via CWM recovery or Philz recovery. I got some systemUI FC but only when playing with sourcery tools and changing stuff. Hopefully that helps
[Samsung Galaxy Nexus] eagle1967:
The Final Call

OP Updated
[Samsung Galaxy Nexus] gohamstergo:
Not, restarts, FCs. Seems to kill itself a LOT when screen is off. I turn on screen and the "SystemUI has crashed" (or whatever) window is showing.

Good point, I already have switched to Philz but the install of 5.3 was with twrp. Now that the "last call" version has been released, I'll do a complete wipe and install via Philz and we'll see how that goes.

Side note about Encore version:

"6)reverted dpi to old way-this fixes some apps being oversized cutting off options and such"

YESSSSSSS

Side Note #2: I don't remember reading this, but does anyone know what phone the Sourcery Team is moving to?
[Samsung Galaxy Nexus] twillet50:
A couple of issues on 5.4. Voice dialer keeps FC'ing and maps will not install. Yes it was a clean install.
[Samsung Galaxy Nexus] jesssiii:
Maps was already installed using black magic gapps, doesn't show up in installed apps on play cause it's modded, but you should see it under all section and it works great for me. What gapps did you use?

The voice search gave me the same problem, finally had to delete with root explorer, reboot, then install the one from play. Then I was able to install one of the inverted Google Nows floating around and it worked.

Toro GNex
[Samsung Galaxy Nexus] twillet50:
I used the new black for 5.4. Kept saying that maps was not installed.
[Samsung Galaxy Nexus] twillet50:
I redownloaded rewiped and reinstalled. Maps works now but still no voice dialer or voice search.
[Samsung Galaxy Nexus] NeverSeparate:
Did you update Google search in market? Try that if you haven't.
[Samsung Galaxy Nexus] twillet50:
No update.
[Samsung Galaxy Nexus] NeverSeparate:
Uninstall then reinstall. Maybe something is wrong with the file. Or maybe try a different gapps.
[Samsung Galaxy Nexus] jesssiii:
Yes, delete the quicksearchbox apk THEN REBOOT, then install google search from play or one of the blacked out Google Now apks out there.

Toro GNex
[Samsung Galaxy Nexus] jthompson0019:
Been on last 2 builds and battery life been really bad. Don't think it is the ROM I think it is the phone. Upper back and upper part of screen gets super hot, almost can't handle the phone. Any ideas?

Also should add happens when screen is on and doing almost any task. Doesn't have to been using data the phone is burning up. I am a big music stream and happens all the time when streaming. A lot of times I'll be charging the phone.
[Samsung Galaxy Nexus] justen7723:
Try a different kernel.

↓LOCKS/GLOWDOTS/CALL MODS↓

http://xdaforums.com/showthread.php?p=37541594
[Samsung Galaxy Nexus] jonstrong:
Agree with this, plus some add'l thoughts:

1) back up your current kernel and try a different one. I'm finding leanKernel to be excellent -- been my goto kernel for some time now -- never disappointed in it. Franco kernel updater makes it easy to back up current one and install lean.

2) are you definitely on the latest radios? should be FK01 / FK02

3) was this a truly clean install? if you used TWRP, did you also run the SuperWipe script before installing? If not, know that there are some anomalies associated with use of TWRP.

4) have you reviewed all your background data transfer / syncing settings? Be sure you don't have a ton of attempted activity when / if you don't have a good signal, otherwise your phone will crank up the power output attempting to make and hold a good connection. If you're in an area with borderline 4G but good 3G, you may want to switch 4G off while in that area.
[Samsung Galaxy Nexus] jthompson0019:
Answers.

1. Have tried lk and still had same issues.

2. Yes on the newest radios

3. Last night switched to touch cwm (Pete's or Paul's version) and flashed clean.

4. Yes. Have 4g almost everywhere. On the ride home I hit 3g bit it is strong.

Thx for your thoughts and trying clean install and deleting some apps that where constantly running in background to see of it helps. Today by 12 noon had horrible battery. Deleted apps and feel I am seeing better battery. Will watch tomorrow.
[Samsung Galaxy Nexus] taz1458:
Still getting the disappearing wallpaper issue.......
[Samsung Galaxy Nexus] jonstrong:
Persistent unexplained battery drain issues generally call for a bit of detective work if you want to avoid endless trial and error. I've used BetterBatteryStats - and still recommend it, and there are other apps with similar battery usage tracking functions available. Worth doing a bit of a search, read and comparing. Then - select and install one, and set it up. This usually involves setting up baseline measurements and you making some choice re: configuration. Then - let it loose, and run your phone for a few days. It may be best to get a full charge, then unplug - and after you run the battery down (or mostly down), check all the info you can get re: activity / battery use since your last time on charger.

You should have a number of options, e.g.,

- show apps / processes that consumed the most battery -- sort these for view in descending order, so you can see the worst culprits right up top

- see if you can display items such as kernel and partial wakelocks, alarms, processes, cpu states

- if these are unfamiliar to you, a quick google search will let you come up to speed on the concepts quickly

After a couple of days, there's a good chance you will be able to know pretty accurately where your battery drain is occurring, and whether there's an easy solution.
[Samsung Galaxy Nexus] jthompson0019:
I started using greenify and had 2 apps running in background causing multiple wakes. One was an app you version bible and something else. I took them both off and today as been better. Thx to those who chimed in. If anything else with my battery happens I'll speak up.
[Samsung Galaxy Nexus] gohamstergo:
Ok so fresh install of 5.4 using Philz, same problem with systemui crashing. The most i can seem to narrow it down is it crashes 75% of the time going FROM landscape TO portrait.
[Samsung Galaxy Nexus] taz1458:
Anyone else still getting the disappearing wallpaper? I think I'm going to go back to 5.2. Way less Buggy