yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DieGo316:
ye i know people now are trying to compile the ROMS by themself instead of waiting for the dev to have time on his own that is pretty good for our android community :laugh::good:
[Samsung Galaxy Nexus] Garner:
3.1? Have i missed something lol
[Samsung Galaxy Nexus] Nephilim:
Not available on Maguro yet. ;)
[Samsung Galaxy Nexus] qu4nd:
AW: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

It's out for toro :(

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Been using it since yesterday. :p

Sent from my AK Pirates Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] ssvijay:
May be we will get it with today's changes

https://plus.google.com/107979589566958860409/posts/8L2875ep3Zs

PS: Just Kidding
[Samsung Galaxy Nexus] Garner:
Ahhh and how is it compared to 3.0?
[Samsung Galaxy Nexus] Nephilim:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Speed and battery very much improved in my opinion. At least paired with AK Pirates Kernel.

Sent from my AK Pirates Powered AOSPA 3.1 Galaxy Nexus
[Samsung Galaxy Nexus] Garner:
Mint! cant wait now :)
[Samsung Galaxy Nexus] pompatello:
Will it be possible in the next releases to expand notifications with the expanded desktop active?
[Samsung Galaxy Nexus] szucsgf:
This is a feature I would appreciate as well.
[Samsung Galaxy Nexus] Jtlaraia:
No, Im running Toroplus not maguro so I didn't have to compile my own Rom, I've been using mine since yesterday too. I enjoy my rare chances at rubbing it in. It was my mistake thinking 02Ranger was running toro. I think im going to switch over to AK kernel though, Franco seems to have its bugs. How is your voice text working? Mine just won't.
[Samsung Galaxy Nexus] Nephilim:
Dirty flashed from 3.0 to 3.1 with no issues whatsoever. My settings are linked in my signature and as always, I use AK Kernels. :D
[Samsung Galaxy Nexus] okanb3:
When will release PA 3.1 version for maguro? Its already released for toro etc.
[Samsung Galaxy Nexus] ssvijay:
Please fellas take all you 3.1 discussions to your respective threads

(Not kidding this time- completely jealous)

---------- Post added at 02:05 AM ---------- Previous post was at 02:05 AM ----------

I am sure you are new here in XDA, we dont ask for ETAs around in here.
[Samsung Galaxy Nexus] okanb3:
Okey, sorry. Just my excitement.
[Samsung Galaxy Nexus] Jtlaraia:
I dirty flashed as well, its all been pretty smooth but i've been putting it through its paces for sure. Like I mentioned earlier, the only problem i've had is my voice text not working but maybe I messed something up, I haven't played with GPS but everything else is great. Thanks for pointing out your settings, I'll try out AK pirate.

BTW guys, 3.1 is awesome...:laugh:
[Samsung Galaxy Nexus] slayr76:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Why do people keep mentioning 3.1 pa toro in a maguro pa gnex thread, this thread needs to be cleaned by mod once again, when gnex marguro gets google update lime pie before toro i will be sure to let you toro users know how good it is :D
[Samsung Galaxy Nexus] Nephilim:
It really is. :D
[Samsung Galaxy Nexus] aiinjylls:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Does anyone know the transparency value for the lock screen? I want to set transparent status bar, but I want it to match the lock screen
[Samsung Galaxy Nexus] marhensa:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

um because some maguro user already tried it too..

some people already build it from github.

you know man..

you can build for yourself if you want.

---

Sent from Android Device
[Samsung Galaxy Nexus] Nephilim:
Not to mention some Maguro users where asking how it runs. ;)
[Samsung Galaxy Nexus] Loureiro:
Still a no-go for that, AFAIK
[Samsung Galaxy Nexus] dictionary:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

3.1 for Maguro runs awesome! Hah! Take that toro users! Lol.
[Samsung Galaxy Nexus] slayr76:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Really dude I never knew that lol, an its not released for maguro officially so what's your point, should I start posting about how awesome n4 runs pa an somehow correlate that to this thread.
[Samsung Galaxy Nexus] Garner:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

I can feel a Moderator coming :rolleyes:
[Samsung Galaxy Nexus] Nephilim:
Nah, you should rather just stop posting all together because everything you say to people is rude and condescending.

How bout you tell me more about how little you know when it comes to the IT industry. ;)

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Very nice to hear, do you have any issues with deep sleep. 3.1 has a big that keeps the device from deep sleep for some people including myself but you can work around it by opening Google Maps and then allowing it to get a GPS lock. After that deep sleep works perfect until you reboot, then you just repeat the cycle. :)
[Samsung Galaxy Nexus] szucsgf:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Actually I appreciate Toro users giving me a preview of what my Maguro can expect.
[Samsung Galaxy Nexus] Nephilim:
I feel the same about Maguro users. Since you guys most of the time are the ones to get the updates first I usually come to this thread to read about bugs, battery life, new features etc. It's great because when we over at Toro get the update I already know what to expect a little more. :D
[Samsung Galaxy Nexus] Jtlaraia:
Glad you got Maguro working^^ and chill with being so upset, yes I use Toroplus, yes I and posting on this forum. They are Both Samsung Galaxy Nexi are they not? So even though we are joking around isn't it nice to hear from us as guinea pigs so that when you go to flash your copy you know what you may or may not have to do to have the best possible outcome. Please dissipate all of the hate.

Also, I swapped to AK pirate and i'll see how that works. Thanks for the settings/color settings Neph, I tweaked to the cpu speeds a bit because I like big numbers. I just can't help it. I may sound inept here but why does the GPU get so buggy when OC'd to 512? I need to go look up the original specs on that....
[Samsung Galaxy Nexus] Nephilim:
I think you forgot to quote the other people you are talking too lol.

Anyway, I'm glad my settings helped. If you want to run 512gpu smoothly just turn off "CORE" in the Smartreflex section of Trickstermod. ;)
[Samsung Galaxy Nexus] szucsgf:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

For example we already know to expect a GPS wakelock. Thank you Toro users. Collaboration at its best.
[Samsung Galaxy Nexus] Nephilim:
The GPSwakelock seems to happen to some but not to others, it's strange. I did relay the info on the PA G+ page though, hopefully they look into it if it becomes a big problem.
[Samsung Galaxy Nexus] szucsgf:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1
[Samsung Galaxy Nexus] Piemo:
R: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Played a bit ago on AOKP with navbar and statusbar transparency. If I remember right the value was between 40-50%. Don't remember exactly, but if I have to decide, zi'll say 50% was my value for having statusbar, navbar and lockscreen with same transparency.

Sent from my Paranoid'd Galaxy Nexus swyping with my nose.
[Samsung Galaxy Nexus] Loureiro:
AOSPA Team implemented lockscreen statusbar and navbar transparency?
[Samsung Galaxy Nexus] pixel2tech:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Same here did same thing for some reason other kernals seem to slow it down now AK pirates makes it fly.
[Samsung Galaxy Nexus] haxor:
Need Help :( I was updating my apps from playstore suddenly my phone restart it self after to it my phone goes restart it self after google logo not able to boot what should i do :confused:
[Samsung Galaxy Nexus] aaronpoweruser:
just uploaded a new build to the dev folder, i dont have a gnex so i have no idea how if it will boot
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Does it have 4.2.2 kernel?

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] haxor:
yup it have franco #365 now i too scared too lose my data please help me !
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Sorry bro i meant new rom update aaronpoweruser just put up, wanted to be sure if i need to flash kernel too. Do you have a recent recovery? Will lose you some data but at least it should boot. Had similar prob few days ago but did battery pull and it came good. If you got adb turned on on ya phone you might be able to adb pull files and data to your desktop in download mode? Or adb push a fresh rom download, gapps and kernel ( in case originals were corrupted) and reflash, that should get you going with data preserved i think, barring hardware issues. Forgive me if i am wrong i am inexperienced.

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] haxor:
Never had this problem before yup i have TWRP recovery and i am able to enter in it what should i do will you tell me and how can i get my data ?
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Do you have a backup? If so try restore it, will lose some data from time you backed up until now, but if it works you will be up and running, i use cwm so not familiar with twrp menu but i gather they are similar. You could also reflash rom gapps and kernel zips if you still got them on ya sd, might get you going for long enough to transfer your data to a desktop, i would flash rom then gapps then wipe cache partition and dalviks then flash kernel and reboot. Fingas xd for ya bro let me know how ya go, if it dont work looks like adb pull, not expert with adb but one of the thread regulars might be able to advise

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] Kocai:
What in the hell this thread has become into. Toro users discussing their ROMs in here. Seriously, if you want to help other users, it's fine regardless of what device you're using but if it's unrelated to PA Maguro, don't post it here. If you're using unofficial build, don't post your settings and problems here too. Use your common sense.
[Samsung Galaxy Nexus] Nephilim:
I'm in no way being arrogant or bashing anyone. I have helped quite a lot of people on this site. All you ever do is downtalk everyone with some sort of unjustified sense of entitlement. You bashed me like you even have a clue about IT work, you go from thread to thread badmouthing everything. I suggest you have some respect for the people on this site. I have yet to see you say one polite or helpful thing to anyone without a condescending attitude about it.

Grow up, this site is a community, a community made to help one and other, you do nothing of the sort with your terrible commentary.
[Samsung Galaxy Nexus] ranasrule:
whats new in pa_maguro-3.00-26FEB2013-004559.zip ??
[Samsung Galaxy Nexus] tegezan:
go to paranoid android google plus for changelog..
[Samsung Galaxy Nexus] ranasrule:
cant seem to find anything there about this build :confused:
[Samsung Galaxy Nexus] Nephilim:
https://plus.google.com/107979589566958860409/posts

The Feb 25th and the Feb 23rd posts are relevant to what will be new to you in todays update. ;)
[Samsung Galaxy Nexus] marhensa:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

this.

love you man.

---

Sent from Android Device
[Samsung Galaxy Nexus] aaronpoweruser:
does the rom work?
[Samsung Galaxy Nexus] 02ranger:
Honestly, I appreciate all the comments about how the Toro 3.1 version is working. It's a nice view into what's waiting for us Maguro users when we get a 3.1 build (like the GPS bug), which I assume is what aaron just posted. It's not like you guys came in and were bragging and putting down the Maguro users, you brought answers to questions that WE posed, and I never got the impression that any of you with a Toro were doing it in a condescending manner, so thank you! Like you said before, we usually end up with the updates first, so I'm sure it was nice to have the shoe on the other foot this time, and I think you guys handled that situation well. I don't think a lot of the Maguro users here could do the same without being jerks about it, thought to be fair a lot could.

Lastly, you're absolutely right about the trolls and noobs. They're gonna show up with needless questions regardless of where you look or what's going on in that thread. I really don't believe the Toro users contributed very much to those posts.........

---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------

I don't know yet, I go on break in a little over 10 minutes, gonna download and flash then....... lol

I'll post back if nobody else has by then.
[Samsung Galaxy Nexus] Nephilim:
Hey aaron, I posted over on the G+ about a possible GPSwakelock issue. Not everyone on the Gnex has it but a decent amount experienced it. The problem is GPS/Maps is somehow keeping some people from reaching deep sleep. If you turn launch Google Maps, allow it to get a GPSlock and then exit you can reach deep sleep as normal again until a reboot. Then you have to repeat the cycle. This has only been pointed out by AOSPA users as far as I have seen and only on the newest updates. (3.1)
[Samsung Galaxy Nexus] aaronpoweruser:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

That's a common thing with maps, nothing we can do about it. Try opening Google now and let that get a lock to see if it helps
[Samsung Galaxy Nexus] Nephilim:
Thanks for the tip, I'll keep that in mind.

I take it this is a 4.2.2 issue? Because I never had it on AOSPA 4.2.1 3.0
[Samsung Galaxy Nexus] The-Captain:
Thread Cleaned.

The arguing doesn't belong here. On the topic of the argument. Until the PA devs say one way or the other, this should be left for them to decide. Not anyone else. Assuming there are fine the way it is, then it will stay that way. Please keep argument out of here as it really adds nothing to the progress of this thread. Thanks.

~ The-Captain
[Samsung Galaxy Nexus] Nephilim:
Thank you.
[Samsung Galaxy Nexus] Rotary Heart:
Well I have to say that this new build is clean smooth. I really love it. I don't event care about new features. I just want it to be more cleaner :good::highfive: devs
[Samsung Galaxy Nexus] jackpham:
pa_maguro-3.00-26FEB2013-004559

http://goo.im/devs/paranoidandroid/roms/maguro/dev/pa_maguro-3.00-26FEB2013-004559.zip
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Just flashed latest update (26/2), got stuck at google boot, so flashed a 4.2.2 kernel (ak purity23) and it rebooted fine, all working well now, prob good idea to have a kernel zip on sd just in case. Thankyou @aaronpoweruser you made my day:D

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] ppog:
You sure about that? I might have dreamed it but I'm pretty sure I remember MBQ talking about this issue in another thread aaaaaaages ago
[Samsung Galaxy Nexus] marhensa:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

will try and report here.

still downloading..

but seems the post above me confirms it works but with custom kernel flashed.

thank you aaron..

:D

---

Sent from Android Device
[Samsung Galaxy Nexus] aamadorj:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

I confirm newest PA build (named Feb. 26th) boots and it's working fine on my GN. I didn't try it with stock kernel, because right after flashing this ROM I installed latest AK Pirates kernel available to public.

By the way, I like new PIE. :)
[Samsung Galaxy Nexus] 02ranger:
I'm flashing it now, but I'm at work so I don't wanna risk flashing without a kernel, so I'm flashing Pirates 704 with it. About to wipe cache and dalvik and restart........ :)

Edit: Everything looks good so far on it. Thanks!
[Samsung Galaxy Nexus] neerajvd:
Working great

I flashed the new build with AK 704 Pirates. And its is working super smooth. :victory:

Loved the PIE animations when on Expanded Desktop.

Also the gap between the screen and the PIE has been removed. :( Will take some time to get used to the new alignment now.

PIE rotation is a nice new addition. I will somehow prefer it unchecked. :)

The misalignment when unchecking the Search button is still there :(

Didnt try flashing with default kernel.

Edit: I flashed the Zenith softkeys and the gap between PIE and screen has returned. :)
[Samsung Galaxy Nexus] DoesntPostAThing:
Come home from a long day and new build of AOSPA to flash :good: I think it will go well with AK Purity 23.
[Samsung Galaxy Nexus] jesfreak:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

On last build I'm having FC of playstore i can't even open it, i flashed gapps again and the problem persists :confused:
[Samsung Galaxy Nexus] neerajvd:
Did you use the 9th Feb Gapps? They are working fine for me.

In Settings -> Apps, try and uninstall the updates of Play Store and let it get updated automatically.

Current version of Play Store is 3.10.14
[Samsung Galaxy Nexus] slayr76:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Anyone else get paranoid android app setup on recents after every reboot an when u touch it nothing happens I just have to keep clearing it from recents tab on new 26FEB2013 build, I have pro version of PA I think it has something to do with that.
[Samsung Galaxy Nexus] melloyellowkc:
flashed the previous 20th and now 26th's build and i was stuck on the google logo. tried so many times so i went back to the last working one which was the 15th. thank god. :(

is there a way to add files to your GNEX when you're in the recovery?
[Samsung Galaxy Nexus] nikei:
have you try to flash custom kernel?
[Samsung Galaxy Nexus] jesfreak:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Did you flashed a custom kernel??
[Samsung Galaxy Nexus] neerajvd:
Having the same issue. And I haven't installed the Pro version.

P.S. I have purchased the pro version, but not installed it since the last clean flash.
[Samsung Galaxy Nexus] jesfreak:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Thanks!! That worked!! :D
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Had same issue, got pro paprefs, kept appearing in recents, after another reboot or two to flash some other mods (gnex xlouder) it stopped doing it, now everything working well and its not appearing in recents. So maybe worth trying coupla reboots?

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] trigaum:
So, i made my per-app-color in some apps that not comes default in PA 3+ and i want to flash the 20feb release.

So i need to know if there´s a way to save PA Colors preferences and restore it at my new release.

(I always do a clean install when flashing new release.

Thankyou guys!
[Samsung Galaxy Nexus] 02ranger:
I've got the same problem, and I don't have PA Prefs Pro yet. Have never purchased it. :( I dirty flashed the 26th build on top of the 20th build, just for information's sake...........
[Samsung Galaxy Nexus] Rotary Heart:
I did and it seems to be working great.
[Samsung Galaxy Nexus] neerajvd:
Thanks. Will try rebooting a few times and check.

Also, if anyone didn't know this, but there's an app from the PA team on Play Store.

The current features are not much apart from adding a Properties tab in the PAPrefs. Hopefully new will be added soon. :fingers-crossed:

Its a great way of supporting the awesome developers. Do try it out.

https://play.google.com/store/apps/details?id=com.paranoid.preferences.pro

Keep up the fantastic work PA team.
[Samsung Galaxy Nexus] Kocai:
Copy the properties.conf and one of your backup files (the newest) and put it in your /sdcard before you wipe.

First method: Make a backup of the "new" properties.conf and copy the previous properties.conf back into /system/etc/paranoid and give the correct permission -rw-r--r-- and make sure the owner and group is system before rebooting the phone.

Second method: using file explorer apps like Solid Explorer, delete the content of the "new" properties.conf, copy the content of the old properties.conf into the new one, save and reboot. I personally use this method since I believe it's the safest one.

I believe he wants to do a clean flash and are afraid of losing his per app colors setting.
[Samsung Galaxy Nexus] 02ranger:
You can go into the PA Prefs app, go to Tools, then choose the Backup option. Then use a file explorer, navigate to /data/data/com.paranoid.preferences/files/backup and there should be a .conf file for each time you have hit backup. Copy these files and paste them somewhere safe on your sdcard that will survive a wipe. After clean installing the new ROM, paste your backup file in the same location (I had to create a backup in the PA Prefs app to get the folders created), then you can restore the backup. It's actually a lot simpler than it sounds, :p

Edit: Got beat to it. lol

Also, I didn't know about the properties.conf file. I think I just forgot about it. What's in that file?
[Samsung Galaxy Nexus] sgtkwol:
Can't get last 2 builds to boot. I was using Franco r364 with PA 15Feb, without a problem. I tried flashing last 2 builds with same kernel and can't get past Google screen. Am I missing something?
[Samsung Galaxy Nexus] Khizar:
kocai if you dont mind can i use your answer in my Paranoid 101 thread?

yup its been out for a while

it has ALL your properties in it..

if i am not mistaken r364 is a 4.2.1 kenrel and you are trying to flash a 4.2.1 kernel on a 4.2.2 rom... thats the problem ;)

Edit- the 15-Feb build wasnt fully 4.2.2 thats why ONLY 4.2.1 kernel worked on it and 4.2.2 kenrel only worked after flashing the 4.2.2 GPL zip but the 20/26-Feb builds are fully 4.2.2
[Samsung Galaxy Nexus] dandemonic:
Re: [ROM][AOSPA 4.2.2] PARANOIDANDROID 3.0 (Feb15) | Release candidate | R1

Anyone tried flashing without custom kernel? Just curious coz when i did it wouldnt boot, so flashed kernel too, just wanted to see if its a rom issue or just my gnex having an andy moment? I guess if its rom issue this thread is gonna get more 'stuck at boot please help' questions like after last update was released.

sent via xda from my noozxoide'd xlouder PA v3+ AK purity23 gnex pro
[Samsung Galaxy Nexus] Kocai:
The first time I made a clean flash I did it like you and I got a lot of SystemUI crash. Possibly a conflict or something. I dunno. So I figured out a way that so far has never failed me.

Look at the content yourself. It's basically your hybrid settings. All of them. Configuration, colors, layout etc.
[Samsung Galaxy Nexus] sgtkwol:
Thanks, that's the problem. Now how was it working with 15Feb, which is 4.2.2 based? Nothing like some stuff that isn't supposed to work, actually working...
[Samsung Galaxy Nexus] trigaum:
Thankyou @02ranger and @Kocai for help!

I´ll try it as soon as my Gnex gets full charged battery!

Thankyou so much!
[Samsung Galaxy Nexus] Khizar:
actually i also do what 02ranger said and never had any issues.. the only different thing i do is set the permission after pushing the backup

yup stock kenrel still wont boot.. so i flashed AK kernel and it booted fine

the 15-Feb build wasnt fully 4.2.2 thats why ONLY 4.2.1 kernel worked on it and 4.2.2 kenrel only worked after flashing the 4.2.2 GPL zip but the 20/26-Feb builds are fully 4.2.2