yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Tone_Capone:
The camera app is technically named gallery.apk. Im fairly sure its called gallery3d because of the photosphere feature, having nothing to do with the actual Gallery. Everyone was having camera issues with the original release, so its not just you. I don;t think a wipe will do anything, but suit yourself.

---------- Post added at 12:22 PM ---------- Previous post was at 12:20 PM ----------

A factory reset, whether through the ROM or recovery is the same thing... Your SD will be fine through both.
[Samsung Galaxy Nexus] Tone_Capone:
No problem dude!

Cough... Thanks Button.... Cough...
[Samsung Galaxy Nexus] bostonbassman78:
I got ya lol
[Samsung Galaxy Nexus] mursepaolo:
Is 2.53 based off JB 4.2?

Nvm just read through the pages. Hoping for a fix for the issues soon. So far loving 4.1.2 with 4.2 gapps.
[Samsung Galaxy Nexus] bostonbassman78:
Another release should hopefully be out tonight
[Samsung Galaxy Nexus] MrVJTod:
If you're concerned about stability, wait. 2.99 is still a little shaky and does recommend a full wipe.
[Samsung Galaxy Nexus] bostonbassman78:
I've been on 2.99 since release I love it just no matter what camera app even stock one force closes and it happens with every gapps I use and no video playback either and I did full wipe through twrp I was just thinking if I did it through the phone and not the recovery then reflash it all after that would help but I'm just gonna wait till the next release
[Samsung Galaxy Nexus] xavier86:
For now I'm on mrom 3.1 until the new release here.

Everything works. But I like the PA environment. I won't be flashing probably until Friday because the rom I'm on now proves stable enough to be a daily.
[Samsung Galaxy Nexus] bostonbassman78:
If I'm not mistaken moles just dropped another 2.99+ build

Edit: hoping that 2.99.1 drops for us tonight to ;)
[Samsung Galaxy Nexus] iomthd:
Haha you never know, it is Thanksgiving across the US after all.
[Samsung Galaxy Nexus] bostonbassman78:
This is true
[Samsung Galaxy Nexus] crimson12:
Maybe it's a setting I'm missing, but is there a way to swap the location of the soft keys and the clock when using the tablet mode UI?
[Samsung Galaxy Nexus] jaybob413:
2.99.1 Update Posted

Link to version 2.99.1 posted to OP.

This version is based on AOSP 4.2 instead of CM10. It is still a work in progress.

Please be safe and backup anything you are not willing to lose.

Also make sure you have the latest recovery to avoid sd card/storage issues. We recommend the latest TWRP recovery for your device.
[Samsung Galaxy Nexus] Mills00013:
Status for those waiting: 2.99.1 does fix the issues with the camera and gtalk not functioning on 2.99. Follow updated instructions at the OP and get your flash on.

Make sure to use the newest linked gaaps: http://www.mediafire.com/?usudw50yb1iubme
[Samsung Galaxy Nexus] Tone_Capone:
I'm on the fence about flashing this just because I don't know how much I will miss some CM10 goodies that I've taken for granted.

Honestly, is it worth flashing yet?
[Samsung Galaxy Nexus] bostonbassman78:
Downloading now
[Samsung Galaxy Nexus] Mills00013:
Depends on what you're addicted to. There's no toggles, no display orientation settings, no customization really of any sort. It doesn't have a theme engine or any ability to add or remove softkeys. (Those are a couple of the big ones people usually miss. Know that it's missing a lot more than that compared to a traditional CM10 based build).

But what it does have is crazy AOSP speed and a smooth experience that I haven't seen in a PAD release in quite a while. And it's nice to see PAD working with something not CM based, which should make it much easier to port in the future to other ROMs or devices if the devs choose to embrace that. (Imagine Hybrid settings on CNA, for example). The groundwork is in place for some really great things. I'd view this as the start of most ROMs during a new release: bare bones. Don't view this as a change from CM to AOSP as much as just a new version of Android, which always causes modifications to come out a little later. As soon as the mods are ready for 4.2, I'm sure that Moles will start to integrate them.
[Samsung Galaxy Nexus] LauraSakura:
I use toggles heavily but inability to add or modify the navigation bar softkeys kills it for me. I know I'm whining but I can't stand the default key layout. I guess I got too used to menu-home-back-search on my RAZR, but now it bugs me to use anything else. Still going to check this out though to see the changes
[Samsung Galaxy Nexus] bostonbassman78:
Nice work on this everything seems smooth but am I only one that sees t-cdma64 on the drop down shouldn't that say Verizon wireless
[Samsung Galaxy Nexus] Mills00013:
You're not the only one. AOSP doesn't come with preconfigured eri packages (like the CM10 builds probably do) which is why it was probably never added. The dev needs to configure our eri.xml files to display properly during roaming/non-roaming situations.

You can do this yourself if it really bothers you before moles (or whoever) fixes it. Check out this thread.
[Samsung Galaxy Nexus] crimson12:
Hmm that's odd... Mine says Verizon wireless
[Samsung Galaxy Nexus] bostonbassman78:
Weird on another note is anyone else seeing double tones in ringtones
[Samsung Galaxy Nexus] Mills00013:
Not weird. Normal. The system/etc file spn-conf.xml is used in a regular situation. Your eri.xml file located in the data directory is called when your phone is in a roaming situation. You may or may not actually be roaming. You might be using a tower that Verizon has deemed outside of your normal operating reins (for example if you're a legacy Alltel customer and you're still on an Alltel plan, all Verizon owned towers will show as roaming.) Either way, it doesn't matter. If you're showing T-CDMA64, it's because your phone either doesn't have an eri file or the file is configured incorrectly. Crimson's is working fine because he's probably on a legitimate Verizon rate plan and using Verizon owned and operated towers in a large metropolitan area. You can fix it yourself (checking the thread I linked previously) or you can wait for the devs to fix it.

On another note:

Built in tethering is still linked to checking Verizon provisions. Tethering restrictions need to be removed for the next CDMA build.
[Samsung Galaxy Nexus] bostonbassman78:
I will wait for the dev to fix it and I'm not roaming at all the cell tower by my house is ran by Verizon and Verizon is the only cell carrier that works in my area
[Samsung Galaxy Nexus] neilrl79:
Mine has changed back and forth between "Verizon" and "t-cdma64". Also my signal seems to be weaker than it was before flashing 2.99b2 in the same location.
[Samsung Galaxy Nexus] Mills00013:
Like I said, you may or may not know you're roaming. The term roaming here is used losely to represent a tower that is not set as one of the default towers in your PRL. Your phone's PRL (which is pushed and controlled by Verizon and is based on your provisioning in their system) is telling your phone that you are. Which is why it's checking for the eri.xml file.

In a typical normal everyday setup, you will never see this difference because the eri is usually set to display the default information (eg. Verizon Wireless).

The semantics aren't really important, I'm just hoping that this sorta clears up why you're seeing T-CDMA64. It's nothing you've done wrong. It's just not a completed rom from the development side.
[Samsung Galaxy Nexus] bostonbassman78:
It cleared it up on your first post I'm just being stupid I guess
[Samsung Galaxy Nexus] Mills00013:
Onto something more important: tethering and location services. If the build tree is current on gitbub, it looks like it should be pretty easy to enable tethering and google based location services (so we're not stuck using the nonsense Verizon based ones).

In the toro framework config (location at https://github.com/ParanoidAndroid/...rameworks/base/core/res/res/values/config.xml in PAD's gitbhub), removing lines 51-55 before the next compilation will give us free unprovisioned tethering.

In the same file, adding a simple configuration should give us Google Location services:

<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The standard AOSP fused location provider -->
<item>com.android.location.fused</item>
<!-- The Google Network Location Services location provider -->
<item>com.google.android.location</item>
</string-array>

While you're in the file, line 38 has an extra quotation in it. (As noted by an astute XDA poster here.)

Does anyone know if PAD has a gerrit instance (or similar code dumping) setup yet so I can submit these requests myself without having to request access to the github repo or hope that jaybob/moles will see it?
[Samsung Galaxy Nexus] iomthd:
It's not set up yet. The team said they'd set these up after the case has been stabilized
[Samsung Galaxy Nexus] bostonbassman78:
No I think there not posting anything to github till the ROM is stable
[Samsung Galaxy Nexus] Mills00013:
Jaybob, I went ahead and forked the android_device_samsung_toro tree on github, made the changes, and submitted a pull request back to you for review and merge into the master branch.

Hit me up if you have any questions or concerns!

---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------

Looks like the AOSP code (that we're modifying anyway) was pulled a couple days ago onto their github, so that part at least is current. I'm just not sure if it's the working tree or not for their compilation. Either way, changes are pushed into a pull request so hopefully we can have a couple of goodies in the next build :laugh:
[Samsung Galaxy Nexus] bostonbassman78:
Sweet thanks man
[Samsung Galaxy Nexus] DevinLeFevere:
Could someone post a Multi DPI Play Store?? Thanks
[Samsung Galaxy Nexus] Mills00013:
The regular play store should be multi dpi... I have mine set in tablet mode right now, only after running it in phone all day. What are you trying to do?
[Samsung Galaxy Nexus] DevinLeFevere:
Well, when I went to set the DPI to 230 it starts having issues with the "This App isn't compatible" yada yada.
[Samsung Galaxy Nexus] Mills00013:
Hmm, did you flash the gapps package linked to the first post? Or are you using an older set? The newest one should be dated yesterday.
[Samsung Galaxy Nexus] DevinLeFevere:
I did. I just went thru a HUGE mess of putting my phone back to 4.0.4 and now back to JB :crying:

Anyway, I'm going to try it again and hope it works.
[Samsung Galaxy Nexus] neilrl79:
I bit the bullet this afternoon and flashed beta2 and I'm really impressed with how well it runs. Everything I use seems to be working great.
[Samsung Galaxy Nexus] dodgersrgood:
does this have the quick toggles mod working? and also does it have the per-app-color thing or is that just in the non 4.2 preview builds?
[Samsung Galaxy Nexus] Mills00013:
Not sure which quick toggle mod you're referencing, but the per app color works perfect.
[Samsung Galaxy Nexus] dodgersrgood:
this one http://xdaforums.com/showthread.php?t=1999125 someone was talking about leaving cm10 earlier and another person replied saying there are no toggles, i didnt know if they were talking about the cm10 toggles or no toggles whatsoever
[Samsung Galaxy Nexus] droidgyrl6:
Wow...really luvn this ROM! The per-app color looks AWESOME! Been running it since this morning without issue! If this is just the preview, I can't wait for the full version! Thx a bunch! :)
[Samsung Galaxy Nexus] Marisa:
My quick settings are functioning as toggles
[Samsung Galaxy Nexus] Mills00013:
Ahh, gotcha. Yeah the 4.2 toggle system is built in and working, of course, but any notion of the custom toggles (such as say the LTE on/off switch or torch) are not present.

It should only be a matter of time before the PAD team cherry picks all the good ones out of the CM source tree though.
[Samsung Galaxy Nexus] the258:
Flashed it and have Been using it for about an hour. I really like the new features even found the Dev option in the menu on accident ha.

But so far no bugs, only downside is that the signal is weak. Will flashing a different radio be safe?
[Samsung Galaxy Nexus] crimson12:
Getting random reboots that hang forever until I clear the cache. Any ideas?
[Samsung Galaxy Nexus] bostonbassman78:
Your radios should already be the latest ones unless Verizon adds some new ones when they come out with a official 4.2

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------

The boots are a Google issue happening on stock to
[Samsung Galaxy Nexus] bburkhar:
Does anyone know how to get 5 icons wide on the home screen?
[Samsung Galaxy Nexus] crimson12:
Okay sorry didn't know about that. Anything I can do to help with fixing that, or do we have to wait for el goog on that?
[Samsung Galaxy Nexus] bostonbassman78:
Pretty sure we wait on Google but knowing the pa team they could already have it fixed never know:D
[Samsung Galaxy Nexus] SilentO:
Verizon official 4.2 release lol funny. Good luck waiting
[Samsung Galaxy Nexus] Bstrong9211:
There is an official leak out there.
[Samsung Galaxy Nexus] Mike02z:
I'm running PA 2.99 on my N7 and N10 with no issues. When I tried to run it on my GNEX it worked fro about an hour then went dead. No response so I needed to pull the battery. Ran fine for another hour then did the same thing. Screen went black and would not respond. Did a complete wipe and reinstalled and same thing. I restored my former stuff via TWRP restore and all is fine. Will be glad to try it again when the next release comes out.
[Samsung Galaxy Nexus] crimson12:
I was checking out the Google code logs of the reboot issue. Turns out a lot of people who had HD Widgets installed were getting random reboots, myself included. Not entirely sure why or how this app breaks anything, but since I removes it I haven't had a single reboot.
[Samsung Galaxy Nexus] mursepaolo:
Is there a list of broken things?
[Samsung Galaxy Nexus] droidgyrl6:
I've been running this since Friday and I haven't had any issues, other than not being able to log-in to VVM ... and not staying logged in to My Verizon or my bank app. For me, this ROM had been virtually flawless!
[Samsung Galaxy Nexus] bostonbassman78:
I have to agree been pretty good for me to also moles released another build so we should see it soon
[Samsung Galaxy Nexus] enigmaisdead:
2.99.3 is on Goo.im. Anyone know what's been changed?
[Samsung Galaxy Nexus] jaybob413:
2.99.3 Update posted

Link to 2.99.3 Update added to OP.

This version has CM/T-Mobile Theme Manager, along with other AOSPA updates.
[Samsung Galaxy Nexus] fakieskr8333:
Looks like tethering is still a no go :(
[Samsung Galaxy Nexus] bostonbassman78:
That sucks as I use it a lot
[Samsung Galaxy Nexus] neilrl79:
Tethering worked for me on beta2.
[Samsung Galaxy Nexus] kkeller87:
Hey everyone. Im currently on CM10 and using a leak of the 4.2 gapps. I want to give PA a try. Ive tried downloading the gapps from the OP and it fails every time on my phone. Tried downloading from my PC and it seemed to download fine, but couldnt flash it. Has anyone had success here?

Also, Im at work right now without ADB or anything. Is there a way to put TWRP on without my home computer?

EDIT - I think i've got the TWRP figured out.
[Samsung Galaxy Nexus] Robin2:
Why isn't there a changelog or a list of known issues. We don't get a lot of info with each release.
[Samsung Galaxy Nexus] nyjohn:
Try checking the pa thread off maguro vesion
[Samsung Galaxy Nexus] bburkhar:
I am having location/GPS issues on latest version.
[Samsung Galaxy Nexus] Tone_Capone:
Is there a way to save the backup of my paranoid ui settings so I can restore them after updating to 2.99+?

Where exactly are these backups stored?

---------- Post added at 03:56 PM ---------- Previous post was at 03:48 PM ----------

Try flashing this. It should optimize your gps settings.

http://db.tt/0nB5BLL9
[Samsung Galaxy Nexus] Mills00013:
You should be able to backup in the paranoid settings area. In the main menu there is a backup function and it will tell you where it's backing up to. It saves the file on your memory card. Do the update, then restore the same way, and you should be good to go.
[Samsung Galaxy Nexus] jaybob413:
Forgot this for today's build. Have it on the list for the next version.
[Samsung Galaxy Nexus] neilrl79:
Located system/etc/paranoid
[Samsung Galaxy Nexus] jeff5347:
Running 2.53 right now I'm gonna wait til 3.+ comes out. But I'm curious..I have 2.53 flashed over verizons 4.1.1 , do I need 4.1.2 to get 2.99 or 3.0 or is it OK to be on 4.1.1?
[Samsung Galaxy Nexus] neilrl79:
You're fine where you're at, just make sure to do factory reset in recovery when you do move on to the 4.2 based PA.
[Samsung Galaxy Nexus] Tone_Capone:
The files didn't make it through the factory reset, so that whole "Do the update, then restore the same way, and you should be good to go" thing is a no-go.

On another note, is the new Tablet mode like the old one, or the new phone like UI?
[Samsung Galaxy Nexus] cappiez:
This is awesome. Love it. Haven't ran into any issues in my daily usage at all.

Only question.. Any way I can get my wallpaper to stretch underneath the navbar, so buttons sit on wallpaper with 100% navbar transparency?

As a request, if in previous versions, and hasn't been worked in, and my apologies. But, a possibility for navbar size separate from status bar..
[Samsung Galaxy Nexus] SilentO:
Official leak? Why isn't anyone using it or have it? Don't be stating something that isn't true.
[Samsung Galaxy Nexus] klisp:
Will dark paranoid get an update to 4.2 as well?
[Samsung Galaxy Nexus] bostonbassman78:
Pretty sure daxmax stopped making it

Sent from my Paranoid Android
[Samsung Galaxy Nexus] the258:
Word. Signal seems to have gotten better with 2.99.3.

One thing I would like to see implemented would be the torch. Just to have it on the quick settings. Don't like having to download one and have a widget. That is just me.
[Samsung Galaxy Nexus] Tone_Capone:
Im flashing back to 2.53 until this is more stable. There no way this can be a daily driver for me right now. Like the progress im seeing though!
[Samsung Galaxy Nexus] xxxdroidxxx:
How do you enable the transparent nav bar? Can't find it in settings or I'm just blind
[Samsung Galaxy Nexus] Divadjeon:
will you be adding profiles to this ROM?
[Samsung Galaxy Nexus] droidgyrl6:
If you apply the PA colors, the status bar and nav bar are transparent on the stock launcher. I use Apex...so I just changed the hex values in Paranoid Settings (doesn't work with Nova though).
[Samsung Galaxy Nexus] yakitori2:
Honestly, I havent enjoyed ANY of the 4.2 roms ive flashed. 1. Its featureless as its still new. 2. the sdcard naming is effed...emulated0 or 0 for sdcard along with a regular sdcard is not cutting it for nandroids. 3. lockscreen honestly sucks....at least until the option to add app widgets to lockscreen...screw it. I dont want messaging or gmail or a clock...those options suck. 4. quick settings is slower to access than the notifcation toggles. I dont like it.

Im not bashing development at all...the community is great...just the fact that the "new" features are not better than the "old" ones yet.

One thing that sucks bigtime...for me using CWM recovery...if I flash a 4.2 rom...it renames the sdcard...and if I want to restore my nandroid...I have to flash a 4.1.2 rom...then move all the contents from /0 back to /sdcard and then restore my backup. All that work to me is not enough to see what new features have been added with each incremental release.
[Samsung Galaxy Nexus] vince7:
User profiles are already added
[Samsung Galaxy Nexus] billykxda:
I am not a PA user, but I just came over to see what's happening here. I am on the cusp regarding moving from a very fast/stable 4.1.2 ROM (CNA with Franco r300) with all the features exactly the way I want them, to 4.2 where I hear lots of users saying the same things as the poster above.

It's great to be an early adopter, and it's awesome to futz around with new stuff, but as of this date, it still seems that 4.2 needs to be baked a little longer - particularly to either include the great features of previous versions, or possibly better solutions that take us to another level.
[Samsung Galaxy Nexus] bostonbassman78:
Me personally have had no issues with pa 2.99-3 I'm running it on 2 devices yes some features are missing but pa is working so fast that I bet by today or tomorrow 3+ comes out with some more features

Sent from my Paranoid Android
[Samsung Galaxy Nexus] idkwhothatis123:
For some reason, my gallery won't show any of my photos. I've moved my dcim folder to the right area but still nothing.

Edit: got it. Took a photo and now my gallery shows everything lol. Weird
[Samsung Galaxy Nexus] yakitori2:
the only issue I was having was tether provisioning still in place. That and the lockscreen sucks on 4.2 imo. Other than that...the emulated0 sd card and the /0 sdcard naming...sucks for trying to restore a nandrod on cwm recovery.
[Samsung Galaxy Nexus] mattymo:
This. All my sd files are borked and now I need to go in and move everything from 0 back into sdcard0. Pain in the butt. Glad I can still rely on 2.53 though. All 2.99.3 gave me was no data connection and boot loops.
[Samsung Galaxy Nexus] the258:
Same here. Running smooth with out any bugs. Idk why many are having issues getting it to work, I wonder if they are using the correct recovery.
[Samsung Galaxy Nexus] idkwhothatis123:
No issues here with twrp as far as functions go. Everything is flawless here now that my gallery is recognizing my photos.
[Samsung Galaxy Nexus] Tone_Capone:
I flashed it with TWRP 2.3.2.1 so it wasn't my recovery. My boot times were absolutely retarded. I had to wipe cache and dalvik to get the phone to boot. I also ran into quirkiness in the hybrid engine, especially in tablet mode.

I'm just going to wait to see what the next build brings.
[Samsung Galaxy Nexus] MrVJTod:
Don't use CWM Recovery. TWRP has no problems with 4.2.

I didn't realize GooManager included an option to install TWRP - its hidden under the menu option to "Install OpenRecovery Script"

I had tried to install 4.2 with CWM and had the same problems and ended up back on 4.1 after a long and tedious recovery process. I swore I would not try 4.2 until CWM was updated, but a day later, I replaced CWM with TWRP and I've been happy on 4.2 since.
[Samsung Galaxy Nexus] donnyp1:
I've had almost no issues on any 4.2 rom. I'm not sure what is causing everyones issues. I don't use but a few apps from market, so its no big deal to fully wipe to me before every flash. I also run superwipe after wiping just to make sure. I don't have bt issues with either my moto earpiece, or my lg sound bar at home. Tethering has worked on every 4.2 rom also. I keep it simple, but phone flies and has great battery. Its been a daily for me from the beginning.
[Samsung Galaxy Nexus] jesusice:
2. That is normal 4.2 behavior. Update your recovery, stop moving the **** around and just leave it there.

3. Lockscreen widget is up to app developer to implement. See Unified Remote for example, it does have lockscreen widget support.

4. Your precious notification toggles can be downloaded and installed in as much time as it takes to complain about the stock functionality.

Not bashing you, but what the **** do any of these random complaints of yours have to do with the ROM? Go. Back. To. FaceBook.