yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] fairct:
New nightly is up! I copied a changelog from molesarecoming:

aosp dalvik optimizations

cm's mms & calculator

2g/3g toggle

quicksettings up to date

backlight settings up to date

aokp's patch against resetting wallpaper when restarting sysUI

several rom scene patches against this and that android leak

dependencies (superusers, etc.)

Also has the LTE toggle of course :)

Get it now! http://d-h.st/508
[Samsung Galaxy Nexus] EvilDobe:
Sweet titties! Thanks for this.
[Samsung Galaxy Nexus] Droidlovinyogi:
Well alright! Looking forward to this! Thanks.
[Samsung Galaxy Nexus] parkson:
Not seeing the LTE toggle in 4-16 build
[Samsung Galaxy Nexus] fairct:
Sigh. Yeah, it isn't there. I dirty-flashed, and it is still on mine. If I go to the Quick Settings settings section, it isn't though. There was a lot of refactoring done on this build to that part of the code, and I had a whale of a time getting those pieces merged back in. I'll take a look.

EDIT: Looking through the code before breakfast (nerd alert!) and it looks like it's missing from the settings side, especially since my phone still shows it. So... at least it isn't missing from the framework. I should be able to provide a new Settings.apk/new build and that'll fix it. You can just dirty flash the new build.
[Samsung Galaxy Nexus] fairct:
Here's a zip to flash to fix my Settings.apk goof. I have a build going, but it won't be done until after I'm at work. I'll get it posted once I get home, but you can flash my previous build, then this zip, and be just fine.

http://d-h.st/9U6 Credit to EvilDobe for fixing my derped zip file!
[Samsung Galaxy Nexus] EvilDobe:
Good news/bad news....

Good news is that your file works. Bad news is that your have a folder nested in your zip so it won't flash. Good news is I fixed it for you & it now flashes correctly. Bad news is that Settings crashes right after you add the LTE toggle. Good news is that it shows up & works.
[Samsung Galaxy Nexus] simonbarsinistr:
No matter what, you're a righteous dude for trying to get us a new build Fair!
[Samsung Galaxy Nexus] fairct:
You mind if I take yours and put it on d-h? I'm TERRIBLE at making flashable zips lol. And... I got some force-closes too with Settings, but it appears to work correctly. A logcat showed mine were NPEs (NullPointerExceptions) in a section that removes tiles that are unnecessary. So... no biggie. I have a full build running and I'll post that after work... with luck, that'll fix it. Otherwise, I'll go digging tonight/this weekend.
[Samsung Galaxy Nexus] EvilDobe:
Go right ahead. It's your file. I just fixed it for you since you got a life & are too good to us with your builds.
[Samsung Galaxy Nexus] fairct:
Thank you kindly, sir. New file is here: http://d-h.st/9U6 Wanted to move it to d-h to keep traffic from crashing your googles.
[Samsung Galaxy Nexus] foxdog66:
Why do I have a sprint system updates option in the settings?
[Samsung Galaxy Nexus] fairct:
Because I supplied a Settings.apk file from toroplus. Easter eggs! :silly:

All joking aside, once I get home from work I'll post the proper build with the correct Settings.apk.
[Samsung Galaxy Nexus] foxdog66:
O ok. Not to question your skills or anything but I started wondering what I was really running. With my full account hooked to these roms I think it's important to be careful you know. And the other day, I swapped batteries and when it booted up it acted like it was going to send off a text message on it's own :what:
[Samsung Galaxy Nexus] fairct:
It was because I had just built toroplus and could make the modifications quickly. Feel free to question my skills lol, I'm a total noob at this
[Samsung Galaxy Nexus] foxdog66:
I wouldn't say total noob :p considering you are compiling and sharing :)

I'm guessing the lte toggle is a cherry pick, from cm or aokp? I read somewhere that pa was based off cm's source but rewritten from aosp (or maby that hasn't happened yet) I haven't tried the official PA builds so I'm not sure of the differences.

It's been a while sense I've done any compiling. I screwed up my local source some time ago and before fixing it I got a chromebook and haven't really turned on my Linux machine lol
[Samsung Galaxy Nexus] fairct:
Yep, cherry-pick from CM. PA has a lot of AOSP components, but they're also using quite a few CM-pieces as well, like MMS and Calculator from CM were added into the build yesterday.

New nightly posted. I dirty-flashed and it seems fine. Did get an odd number for the post-dalvik flash "Optimizing apps" or whatever the message is... like 20-something instead of 100+. So... make a backup.
[Samsung Galaxy Nexus] fairct:
Is anyone getting weird behavior out of this build? I did a clean flash and I'm having a ridiculous amount of freezes, SoDs, etc. It could be kernels, but I flashed to a kernel that worked previously and it still acts funny...

I'm pulling down a new repo, and I'll have a clean build up tomorrow sometime. It won't have the LTE toggle until I can spend a bit more time and make sure I do it right. Sorry if it gives others these issues.
[Samsung Galaxy Nexus] foxdog66:
I'm not having any problems after a dirty flash. It rebuilt all the cache for me as well.
[Samsung Galaxy Nexus] simonbarsinistr:
I'm laying off til the new commits settle down again :) my phone runs so nice on the last build before the new stuff was added, I don't want to risk it!
[Samsung Galaxy Nexus] fairct:
Totally understandable. From what I'm hearing from the toroplus side, it appears to be either on my end or the clean flash. EvilDobe had issues on a previous recent build with a clean flash, so I think maybe something is getting left out... I'm just kicking off a clean build from a fresh repo, so I guess I'll know soon!

Thanks for the input guys. I don't intend to make you my guinea pigs... but sometimes it comes out that way. It's my goal to give you a nice, stable product, and I hate releasing something that isn't 100% correct. I MIGHT be a perfectionist :silly:
[Samsung Galaxy Nexus] Nephilim:
Gonna try your 4/17 build right now and if then your new one today when it's up. :)
[Samsung Galaxy Nexus] fairct:
It was running fine, but now... Lightflow doesn't open. Just hangs. And... I was able to open Trickster and set some kernel params (not set on boot), and then it now crashes. Can't get it to open for the life of me, with variations of uninstall, clearing data, etc. Tried flashing a previous AK (99), but that didn't help. No idea what's going on :eek:
[Samsung Galaxy Nexus] terminal13:
Fairct, which kernel do you include in the nightlies?

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] fairct:
The one I build from the staging branch from PA. The main branch kernel doesn't work correctly. I have made no changes to it, however.
[Samsung Galaxy Nexus] terminal13:
Got ya..

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] Nephilim:
Was this off of a clean flash or a dirty one? I'm wondering because I always dirty flash. Maybe once every couple months if I notice lag I might do a fresh install but not normally.
[Samsung Galaxy Nexus] fairct:
Clean flash. I haven't blown away the data partition in a while, though.
[Samsung Galaxy Nexus] Nephilim:
Cool, I have a nandroid already done and I'm gonna test it via dirty flash. I'll flash your clean build today regardless though.

Report back on this one in a little while. ;)
[Samsung Galaxy Nexus] fairct:
Fun story: my clean build from today doesn't boot on my phone. Just sits. My phone go boom, apparently.
[Samsung Galaxy Nexus] Nephilim:
I'm sure you'll figure it out, you do a great job compiling these and I prefer your builds over Jaybob. Keep up the good work! :good:
[Samsung Galaxy Nexus] fairct:
I think my issue was TWRP wasn't actually wiping everything, and just being buggy in general. I wiped ALL data from my device, and flashed the 17th build with newest GAPPS, and AK 108. Everything seems to be working just fine. I also flashed newest CWM just because I was pissed at TWRP :angel:
[Samsung Galaxy Nexus] Nephilim:
17th build is working absolutely fine off of dirty flash for me. No issues and everything rebuilt 100% on first boot. Using the most recent twrp btw. :)

Sent from my AK Diamond powered AOSPA 3.15 Galaxy Nexus
[Samsung Galaxy Nexus] fairct:
Mine's working flawlessly now. Getting good battery life too. I'll stand by my previous statement of WTF? :confused:
[Samsung Galaxy Nexus] dirtsky:
On the 16th build I'm having trouble trying to get exchange email to work. Any ideas?
[Samsung Galaxy Nexus] Nephilim:
Agreed lol.

---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------

Flash the 17th build?
[Samsung Galaxy Nexus] dirtsky:
I'm going to later. I'm at work at the moment. :p
[Samsung Galaxy Nexus] blckngldhwk:
Anybody else have ongoing issues trying to download the rom from the host? I constantly get 'download unsuccessful'.
[Samsung Galaxy Nexus] simonbarsinistr:
Just to comment on your earlier statement fair; we're all guinea pigs here!
[Samsung Galaxy Nexus] foxdog66:
I just noticed that messaging has disappeared from the share menu... :confused:
[Samsung Galaxy Nexus] Kazba1626:
Me too can't share tweets using messaging app.
[Samsung Galaxy Nexus] error629:
I've been using this mms apk. But when I reboot or do a battery swap it reverts back to the default. This has been an on going issue through several builds. I'm not complaining, love the rom. It's no big deal to just run the apk over.

Fairct, just curious, but why is your 4g button in quick settings not in every build?

Also, do you have a donation link? Neph, I think you deserve a donation also why all your great input. I don't think just hitting a thanks button is enough.

---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------

Sorry I forgot to mention it was the blackbean (?) Mms apk
[Samsung Galaxy Nexus] fairct:
In the most recent build PA switched to using CM's mms.apk, so I suppose that option must be missing from it. If it was a feature you need, you can pull the apk from one of the previous nightlies.
[Samsung Galaxy Nexus] fairct:
The mms.apk gets replaced every boot? That's pretty wild; don't really know what's going on there. I only recently added the lte toggle because I was originally just providing a stock PA experience. As far as donations... Those should go to the PA team, not me. The credit for the hard work should go to them!
[Samsung Galaxy Nexus] NeverSeparate:
I thanked you just cause that's a cool attitude to have :) so thanks for that.

Sent from my Carbonated Gnex
[Samsung Galaxy Nexus] Wade-0:
I'm glad someone else noticed this too. I thought it was just me. I was trying to share a link from the browser and had to use the Clipboard share target instead. Was hoping this wasn't "the new way" to share via SMS/MMS now. I did notice, however, that it's available when sharing a picture from the gallery.
[Samsung Galaxy Nexus] b33zy682:
Can we get a new nightly tho???
[Samsung Galaxy Nexus] cmoG530:
Lol. Are you aware of where you are? No ETA's and if you followed PA, you'd know that they're busy trying to finish the new hybrid engine. Pie2 is now on hold, until Jesus finishes his exams, Lord willing. So, for right now, there's no reason for an update. Moles did say that, there may be updates, but just to keep things up to date. That and KLP is due in three weeks Lord willing, so every ROM will be starting from scratch again.

So...for now I say this is a time to experiment with different ROMs, because there won't be much going on. Especially when Android v5 is out.
[Samsung Galaxy Nexus] b33zy682:
When did i ask for an ETA. i just wanted to see some progress. i dont have a google+ to follow them on so i didnt know. and v5 might not even drop at google i/o. all i wanted was an update to keep things out of date. this would of been a perfect answer if you would of left the first sentence out. but whatevs
[Samsung Galaxy Nexus] fairct:
I don't mind you asking. No commits of note have happened to the PA code though. There has been a little bit going on with CM, so I'll probably have a build up toward the end of the week if nothing big happens sooner. I should probably change the title of the thread away from nightly since this certainly isn't a nightly :P
[Samsung Galaxy Nexus] Nephilim:
Asking for ETA's is a no-no. Also, it's been said on this thread many many times that fairct only updates when something worthwhile is introduced to the git.
[Samsung Galaxy Nexus] MrVJTod:
Of you make a new build for him from the 4/17 base, I promise to praise how much faster and smoother it is than the current build.
[Samsung Galaxy Nexus] jmileti:
What? Really. Did you just say that.
[Samsung Galaxy Nexus] fairct:
I'll just leave this here... https://plus.google.com/107979589566958860409/posts/RAjdXZRSiZz

Anyone excited? :good:
[Samsung Galaxy Nexus] TemplesOfSyrinx:
Oh Baby!!!

The anticipation is killing me!:silly:
[Samsung Galaxy Nexus] Droidlovinyogi:
Yes definitely excited. Sounds like it's going to be big!
[Samsung Galaxy Nexus] fairct:
dude.... dude. DUDE! https://plus.google.com/107979589566958860409/posts/LWir38gJnSH

Now I'm stoked.
[Samsung Galaxy Nexus] tattedupboy:
That would be freakin awesome! What I've got to know though, is if this will be implemented into Android 4.2.2 and carried over into 4.3, or if we'll be waiting until the source code for 4.3 is released.
[Samsung Galaxy Nexus] Wade-0:
Weird... The GOO.IM app just notified me there was an update available for my ROM, which is currently this one. Neither this one nor the official have been updated, not sure what that was about. Got me all excited for nothing ;)
[Samsung Galaxy Nexus] EvilDobe:
Goo was having issues before. Probably just a side effect.
[Samsung Galaxy Nexus] Droidlovinyogi:
I hope everyone is keeping their eye on the progress of the new PA project. There's major stuff in the works:

https://plus.google.com/u/0/107979589566958860409/posts
[Samsung Galaxy Nexus] fairct:
I'm checking their G+ and github multiple times per day lol.
[Samsung Galaxy Nexus] Droidlovinyogi:
Good to hear that you're on top of the git. I appreciate your ability to understand and work with it, and that you share your builds with us. I don't understand it and absolutely don't have time to learn how. In fact I've just found time at this moment to flash your current 4/17 build. I'm looking forward to running it. It'll hold me over until the next time their git warrants that you use your skills.

In the meantime I'm refreshing their G+ many times per day, looking for the inevitable update and reading new comments. I enjoy reading the comments, the level of anticipation and enthusiasm feeds my own excitement about what's to come and adds to the fun of it.
[Samsung Galaxy Nexus] fairct:
I come from a Java background, so Android has a lot of common pieces. I was a CS major in school, so I picked up a lot of the Linux pieces there. I'm a born tinkerer though, and I love doing things for the sake of 'seeing if I can do them.' I plan to post a build in the next day or so, just so we can get to the updated CM pieces.
[Samsung Galaxy Nexus] Droidlovinyogi:
That sounds great...looking forward to it. BTW what are the CM pieces?
[Samsung Galaxy Nexus] fairct:
After checking the manifest, looks like MMS, Calculator, superuser, file manager, and I'm not sure what others... I would like to pull in the CM Clock if it isn't already in use... They added a 'sleep cycle' setting for alarms that seems pretty cool, or so I recall seeing.
[Samsung Galaxy Nexus] Nephilim:
Nice set of small additions. Seriously cannot wait for the windowed apps though!!!!!!!!!!!! Gonna be soooooo useful! :good:
[Samsung Galaxy Nexus] fairct:
Those things are actually already pulled in. That was my list of things from CM that I know are already in PA... there are probably others. A build would pull in any updates to those, and I wanted to get CM's clock because of the fancy new alarm (if it got committed).

And... me too. SO EAGER.
[Samsung Galaxy Nexus] fairct:
New nightly posted! Couple caveats with this one.

All of the new stuff is from CM, basically. Couple updates to FileManager, MMS, etc. I pulled in CM's DeskClock, but that alarm feature I mentioned hasn't been merged yet. I DID pull in CM's Camera, because they recently added in a 'take picture by saying certain words' feature, as well as a timer. It also has HDR, which I've heard of but don't know really anything about.

The caveats are: you have to use a modified GAPPS to get this to work. PA's GAPPS overwrite the camera (Gallery2.apk) with one of their own. I've posted a stripped down GAPPS in the OP for use if you want CM's camera, or if you're tired of all those extra Google apps normally in PA's. It basically only has Talk, the Play Store, and a couple other required pieces.

Rom: http://www.d-h.st/PWA

GAPPS: http://www.d-h.st/emL
[Samsung Galaxy Nexus] LancerV:
Does anyone know if this uses AK Kernal? For what ever reason I can never uninstall AK kernal
[Samsung Galaxy Nexus] fairct:
Nope, the kernel is built.
[Samsung Galaxy Nexus] EvilDobe:
Damn you! I got bored & just finished flashing the latest Liquid nightly & getting it setup. Guess I'll have to flash THIS now. Thanks, fair.
[Samsung Galaxy Nexus] fairct:
Ahaha! I laugh at your misfortune. :laugh:

I got bored too, hence pulling in CM apks.
[Samsung Galaxy Nexus] Nephilim:
So minus the FileManager, MMS, Deskclock and Camera this build is no different than the last or was there bugfixes and other things besides that under the hood?
[Samsung Galaxy Nexus] fairct:
I don't believe there were any core PA changes. Mostly just CM APKs. You see the newest G+ post? https://plus.google.com/107979589566958860409/posts

WHY ISN'T THIS COMMITTED YET?!
[Samsung Galaxy Nexus] Nephilim:
Can't f*cking wait! This is going to be amazing!!

Sent from my AK Skull powered AOSPA 3.15 Galaxy Nexus
[Samsung Galaxy Nexus] dirtsky:
Oh hell yeah! Sweetness!
[Samsung Galaxy Nexus] jmileti:
I just drooled all over myself. Anyone got a towel?
[Samsung Galaxy Nexus] iomthd:
Anyone else getting an fc when sending an mms?
[Samsung Galaxy Nexus] fairct:
I haven't sent an mms recently... Normal texts work fine though
[Samsung Galaxy Nexus] tcs.computergeek:
Same here. MMS is fc'ing

I did a dirty flash of the new update and slim gapps. So its probably my fault.

Edit:

Rebooted to recovery and wiped cache and dalvic cache and fixed permissions and MMS went through. Hope this helps.
[Samsung Galaxy Nexus] bigbear6708:
New aospa user here... About to flash for first time... Want to subscribe to this thread to see updates... that multi window has me pumped
[Samsung Galaxy Nexus] pitokellie:
camera f/c

can someone hepl me .my camera f/c i did everything i could reflash april 29 rom gapps 4/16
[Samsung Galaxy Nexus] lurch81:
Is this good to go? See some posting MMS fc'ing..
[Samsung Galaxy Nexus] lurch81:
Flashed the "slim" gapps to have cm's camera but I have no HDR or voice activation etc did I do something wrong?
[Samsung Galaxy Nexus] fairct:
Did you flash it with the new ROM? The slim gapps just keeps from overwriting the one in the ROM.
[Samsung Galaxy Nexus] TemplesOfSyrinx:
I dirty flashed and ended up not having the new CM camera. So I did a clean flash and now everything works.
[Samsung Galaxy Nexus] lurch81:
No I came from different rom so did clean install, even tried flashing the rom again without gapps over the top like I used to to with cm to get it to work but that didn't work with this build
[Samsung Galaxy Nexus] TemplesOfSyrinx:
Are you restoring anything with Tibu or another app? I have tried to recreate what you are saying, but I have no problems. If you do a full wipe, Flash the rom and the proper gapps it works. I have done it several times.
[Samsung Galaxy Nexus] tokuzumi:
Do the separate ringer/notification volume settings work? I did a wipe of system, data, cache, and dalvik before installing the rom, but I can't have different volume settings, even with the link volume check mark not selected.
[Samsung Galaxy Nexus] joqsan:
Does anyone know when or if there is an option in this ROM to center the clock?
[Samsung Galaxy Nexus] dodgersrgood:
has that new pop-up window thing been added to the nightly builds yet?
[Samsung Galaxy Nexus] cmoG530:
Lol. When it does, I'm sure you'll hear about it. It's still in the early stages. You can stay up to date via their Google plus.
[Samsung Galaxy Nexus] bigbear6708:
Just flashed this bad boy. Like it so far. Love how it is not bogged down with options and the feature included work very well. Can someone with aospa exp tell me if the paranoid settings. Conf backup file will get saved after each wipe and flash... Don't think I could keep setting up my per app settings. Also, is there a way to get different battery icons, saw some contest on pa website. The mole guy one looked sweet. Thanks
[Samsung Galaxy Nexus] Nephilim:
Yes, paprefs are saved to sdcard so they stay upon each wipe as long as you don't wipe SD. :)

Sent from my AK Skull powered AOSPA 3.15 Galaxy Nexus
[Samsung Galaxy Nexus] cambunch:
The new CM additions are great. One bug I have noticed is that the Power Shutter in the camera doesn't work perfectly - it takes a picture when you hold it down but also pops up the Power Menu. Not a big issue and I'm sure it will be fixed soon.
[Samsung Galaxy Nexus] jmileti:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/02/12]

I don't flash gapps when i dirty flash. Wipe dalvik and cache. That's it.
[Samsung Galaxy Nexus] jeffcavicchi:
Re: [ROM] [4.2.2] AOSPA 3.x TORO (SEMI)NIGHTLIES [03/02/12]

I just ended up flashing gapps anyway. I have it on my sd card, so it just seemed easier.

Love having Superuser integrated into the ROM!
[Samsung Galaxy Nexus] Nephilim:
Yep, superuser built in is slick. Remember to uninstall supersu though, it is still there. Not sure if it causes issue or not because I removed it right away.
[Samsung Galaxy Nexus] fairct:
Yeah, I did a clean-flash just to avoid any wonkiness with it.
[Samsung Galaxy Nexus] Tone_Capone:
So these builds use Super User instead of SuperSU? Why the change?
[Samsung Galaxy Nexus] fairct:
Ask the PA team :) I have no idea; I just build the source haha
[Samsung Galaxy Nexus] Nephilim:
Hey fairct, I asked before but you might of missed it. This new build you compile, did it include the full 4.2.2 AOSP code that was released yesterday?
[Samsung Galaxy Nexus] fairct:
I saw your question and forgot. From what I can tell looking at the manifest, it looks like all the pieces that get pulled from AOSP are indeed now using 4.2.2. I missed that commit! I'll update the OP. I'm still prodding around the kernel issue. I don't like when something stumps me...
[Samsung Galaxy Nexus] Nephilim:
Thanks for the info. Glad to hear it.

Btw, did you see this yet? http://xdaforums.com/showthread.php?p=38678944#post38678944
[Samsung Galaxy Nexus] fairct:
I did not! Fantastic! Thanks for the heads up. I was just moping that toro got left out in the cold again :p
[Samsung Galaxy Nexus] Nephilim:
All I really want from that is the radios. ;)
[Samsung Galaxy Nexus] fairct:
Yeah... starting to wonder if we need to flash back to the Feb. 27th nightly to prevent any issues...
[Samsung Galaxy Nexus] Nephilim:
This looks to say that devices with updated bootloaders and radios will be the ones affected. I'm not sure if Toro will be since we have not gotten either yet.

https://plus.google.com/107979589566958860409/posts
[Samsung Galaxy Nexus] jeffcavicchi:
I haven't tried making a call yet since flashing the latest nightly, but everything else seems to be working OK - I am a little bit confused about needing to flash the latest radios. Can anyone shed light on this? Nephilim or fairct?
[Samsung Galaxy Nexus] Nephilim:
I'm keeping an eye on this right now over on G+. As far as I can tell this is more important to the GSM devices and the ones that google has released updated bootloaders/basebands for. I have had no issues with anything including calls, sms, gps, mms etc so we are fine as of now with the fully integrated 4.2.2 code. There is a thread over in the General section about a person that received a Test build of 4.2.2 for Toro Gnex today and they are going to try and pull the Radios. Oddly the bootloader is the same.