yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Circaflex:
im not too sure what they are working on but there is always the possibility there are features being worked on behind the scenes in a private repo, like they did with DSB, Peek, PIE, etc

But yes, its mostly just theme engine, a few aosp fixes and app ops. its a really great rom for those looking to stick pretty close to stock but have some extra features.

---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------

This has already been answered many many many times. No one from the team left, the ONE+ deal is no different than PA before when they had other jobs. ONE+ is just their normal working day job, they are still PA and still continue to contribute. You guys need to quit thinking the world is ending because some of the devs were offered a job with ONE+. You aren't the first to wonder this, and its been explicitly stated by many PA members.

---------- Post added at 03:07 PM ---------- Previous post was at 03:04 PM ----------

just flash the normal package, don't mondify anything, stay in TWRP after the flash and be sure to flash a third party kernel that doesn't enforce encryption and youll stay unencrypted; encryption starts when you boot the phone so if you don't reboot after flashing the PA build and flash the third party youll be fine.
[Nexus 6 Android Development] daleski75:
New build uploading now guys.
[Nexus 6 Android Development] daleski75:
Build 06/03

Settings: Abandon the App Ops Template structur

SystemUI: Fix nav button ripple getting stuck

https://www.androidfilehost.com/?fid=95916177934537763

md5 0e0bb7a33c9a3b6611316a424b26b7ad
[Nexus 6 Android Development] blinqipa:
[MENTION=1095206]daleski75[/MENTION] is it possible to integrate PIE controls from the KitKat version of PA?
[Nexus 6 Android Development] puertorecon:
I would love to see what PIE looks like on Lollipop.
[Nexus 6 Android Development] daleski75:
I am just compiling the builds I am not a dev so won't be doing any cherry picks etc sorry guys.
[Nexus 6 Android Development] xReaper7x:
Sorry if I can't see it but I don't see an option to turn of bringing down quick notifications if I swipe from the right? I just don't really like that and wish to turn it off, is there such menu?
[Nexus 6 Android Development] Smallsmx3:
Official alpha 2 up
[Nexus 6 Android Development] sonofevil77:
Oh I've been waiting for this!

Sent from my Nexus 6
[Nexus 6 Android Development] daleski75:
Update.

I keep an eye on the gerrit page each morning so as soon as I see any new commits I will do a build, until then guys enjoy alpha 2
[Nexus 6 Android Development] Linch89:
PA isn't official on n6 correct? I thought there would be a lot more going on in n6 threads! Guess the price is a little too steep. N5 -> n6!
[Nexus 6 Android Development] Smallsmx3:
It's official. There's not an official thread at the moment.
[Nexus 6 Android Development] daleski75:
New build now up and its still 5.0.2 if anyone asks.
[Nexus 6 Android Development] Smallsmx3:
Assuming this is dead? Heard there was some huge blow up and PA bounced off XDA
[Nexus 6 Android Development] daleski75:
Not dead just no new commits.
[Nexus 6 Android Development] jamescable:
dead

They are not dead, but Pa is dying....they have yet to release official 5.0 and even their 4.4.4 ROM is still pretty much stock with no features....and now 5.1?? Consider dead
[Nexus 6 Android Development] daleski75:
[MENTION=2789361]Smallsmx3[/MENTION] Unless they officially state it's dead then it's not dead. [MENTION=3604271]jamescable[/MENTION] They stopped developing for kitkat a while ago and they may have private github repo's with much more up to date code.
[Nexus 6 Android Development] Smallsmx3:
What hole do you live in. Just because there was no thread here on XDA doesn't mean there wasn't an official release.

And I meant this thread being dead. Not the ROM. I'm sure it will still be developed for a little while longer.
[Nexus 6 Android Development] vergilbt:
Any news in git?
[Nexus 6 Android Development] daleski75:
Not checked for a while too be honest very busy with family stuff right now but will check and see if I can find time to do more builds for you guys.
[Nexus 6 Android Development] vergilbt:
Great... Go ahead.
[Nexus 6 Android Development] Circaflex:
nothing really has changed since March 6, unless of course they are using their private gerrit for now. Last i heard they have 5.1 builds semi-working, theme engine was causing some issues. They said they could release without themes and it works fine, or fix the issue with themes. PA has also somewhat taken a break, due to the community and outrage of users they needed time away from development.
[Nexus 6 Android Development] daleski75:
Trying for a week and a half to get a new build out but something is broken with the build process.

Repo sync all works but when I do ./rom_build.sh shamu it comes back with this each and every time.

Your Java version has not been checked and is a candidate for failure. Masquerading.

Building AOSPA 5.0 for shamu

Start time: Mon Apr 20 14:29:06 BST 2015

Setting up the environment

including device/generic/mini-emulator-arm64/vendorsetup.sh

including device/generic/mini-emulator-mips/vendorsetup.sh

including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh

including device/generic/mini-emulator-x86_64/vendorsetup.sh

including device/generic/mini-emulator-x86/vendorsetup.sh

including vendor/pa/vendorsetup.sh

including sdk/bash_completion/adb.bash

Lunching shamu (Including dependencies sync)

build/core/product_config.mk:238: *** _nic.PRODUCTS.[[vendor/pa/products/pa_shamu.mk]]: "device/motorola/shamu/full_shamu.mk" does not exist. Stop.

your device can't be found in device sources...

Traceback (most recent call last):

File "build/tools/roomservice.py", line 317, in <module>

fetch_dependencies(device)

File "build/tools/roomservice.py", line 270, in fetch_dependencies

raise Exception("ERROR: could not find your device "

Exception: ERROR: could not find your device folder location, bailing out

** Don't have a product spec for: 'pa_shamu'

** Do you have the right repo manifest?

Starting compilation

build/core/product_config.mk:242: *** vendor/pa/products/pa_shamu.mk: PRODUCT_NAME must be defined.. Stop.

Total time elapsed: 0 minutes (4.740287344 seconds)

It also wiped my roomservice.xml file as well which didn't help.

I have tried a fresh install of Ubuntu and done a repo sync to both lollipop and lollipop-mr1 and all come back with the same results.

Also there has been very little progress on github publicly so not sure it's worth keeping this thread open.
[Nexus 6 Android Development] daleski75:
Got the builds working again (found an old backup of my roomservice.xml) so doing a build now and will post it later on tonight.
[Nexus 6 Android Development] daleski75:
Spoke too soon looks like the builds are broken so will try a repo sync tomorrow.
[Nexus 6 Android Development] daleski75:
Still no go guys but will keep trying to get a working build out.
[Nexus 6 Android Development] daleski75:
Looks like they updated the branch to 5.1.1 so doing a fresh repo sync and fingers crossed now it will build ok.

The build is getting a lot further however it looks like it's still on LMY47D
[Nexus 6 Android Development] daleski75:
Not sure why I did not think of this but [MENTION=2455860]VECTUS[/MENTION] suggested updating the roomservice.xml to point to 5.1.1_r1 fro 5.0.2_r1 and doing a build now so hopefully this time it will compile ok.
[Nexus 6 Android Development] Smallsmx3:
Sweet! Curious as to how pa is. Thanks for this!
[Nexus 6 Android Development] daleski75:
Still no dice it gets even further but still won't compile yet.
[Nexus 6 Android Development] Smallsmx3:
Oh well. I'm really content with the ROM that in on now. Its just bizarre that CM is the only major player with decent LP builds. Been slow out the gate for 5.0
[Nexus 6 Android Development] daleski75:
Not quite true if you look at the official pa gerrit https://gerrit.paranoidandroid.co/#/q/status:merged there seems to be very little movement however the legacy pa is moving at a very fast rate http://gerrit.aospal.com/#/q/status:merged
[Nexus 6 Android Development] VECTUS:
Yeah I think I figured out my build issue. Building CM right now but I'll try another PA build later today. Pa isn't updating their stuff real well. Makes it a challenge to compile...
[Nexus 6 Android Development] daleski75:
Let me know if you manage to get it to compile ok and also is your build still LMY47D when you do ./rom_build shamu?
[Nexus 6 Android Development] Nickchapstick:
I miss PA :( glad you are working on it. I can't wait to see what this may become.
[Nexus 6 Android Development] VECTUS:
No it doesn't and my builds fail. Tried to fix the .mk file it wanted but when I do that it just goes to another issue... I've never built PA and I'm stumped to be honest...
[Nexus 6 Android Development] daleski75:
I have built PA many times for the nexus and one plus one and hopefully when pa push some new commits it will then build but who knows when that maybe.
[Nexus 6 Android Development] daleski75:
No new commits since the 4th of April so not sure what's going on and because of this the builds I try to do every few days are still failing.

Opinion guys....

Is it worth keeping this thread open considering the glacier pace of development from PA for this phone?
[Nexus 6 Android Development] skhjpz:
I think yes, team have exams so we need to wait
[Nexus 6 Android Development] IVIanuu:
Is it possible to compile a aospal build for our device?
[Nexus 6 Android Development] daleski75:
Hmm let me check that out.
[Nexus 6 Android Development] info[]box1:
Happy to see the N6 got development team for the PA mission. Guys don't stop the great work, keep it going. Even if releasees are weekly, monthly whatever. Stay on the ball. Thanks again.

Yeah and an AOSPAL build be awesome.. :silly:

"Energy and Persistence "
[Nexus 6 Android Development] daleski75:
Trying a build now and I can only assume they have given up on AOSP and gone now to Cyanogenmod and unsure how I feel about that if it's true.

At least it hows 5.1.1 now rather than 5.0.2.

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=5.1.1

PA_VERSION=5.1-20150507

TARGET_PRODUCT=pa_shamu

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=krait

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.16.0-36-generic-x86_64-with-Ubuntu-14.10-utopic

HOST_BUILD_TYPE=release

BUILD_ID=LMY47V
[Nexus 6 Android Development] Smallsmx3:
That blows, CM base? No thanks
[Nexus 6 Android Development] daleski75:
Looks like it yeah they have moved shamu from AOSP to the CM12.x (legacy non-nexus devices)

http://gerrit.aospal.com/#/c/571/

And there is no progress since the 04/04 on https://gerrit.paranoidandroid.co/#/q/status:merged
[Nexus 6 Android Development] vergilbt:
What is it meaning? Different sources for different devices? All nexus on aosp and all legacy devices on cm?
[Nexus 6 Android Development] daleski75:
nexus was aosp but now cm by the looks of it.
[Nexus 6 Android Development] gohabsgo:
On google+ the legacy developers mentioned that all of their builds are CM based. Also, they aren't officially providing a build for Shamu or for that matter Nexus devices. They did however merge the commit on gerrit allowing for a build if somebody wishes to do so, which you are kind enough to do.

All of that being said, once the Nexus developers get back to work, after their study break, I believe the aim is to provide Nexus builds based on AOSP.

So for now, we have kind of a temporary unofficial build based on CM and hopefully we will eventually be able to replace that with an AOSP build at some point in the future.
[Nexus 6 Android Development] daleski75:
I still have the AOSP source code so if they do go back to it then it won't take much to get it building again.
[Nexus 6 Android Development] daleski75:
Neither are building yet will try again tomorrow.
[Nexus 6 Android Development] skhjpz:
Maybe try with this https://gerrit.paranoidandroid.co/#/c/662/
[Nexus 6 Android Development] VECTUS:
Dale, looks like they've done a lot of work on the git the last 3 or 4 days. Shamu is added too...

https://github.com/AOSPA/android_device_motorola_shamu
[Nexus 6 Android Development] daleski75:
Tried to do a compile earlier on and failed on both legacy and aosp. Have you got it to compile yet?
[Nexus 6 Android Development] VECTUS:
Naw I'm at work... I can try tomorrow though if you need me too...
[Nexus 6 Android Development] daleski75:
Trying another build now with the AOSP source
[Nexus 6 Android Development] daleski75:
Trying yet another build guys.... here we go repo sync time :)
[Nexus 6 Android Development] frankymix:
Lets us know when you upload to download and try! Cant wait!
[Nexus 6 Android Development] puertorecon:
Straight up!!
[Nexus 6 Android Development] an21281:
Any progress?
[Nexus 6 Android Development] daleski75:
None yet I am trying to do a build of both legacy and aosp and both fail but rest assured I will post right away if I get any build working.
[Nexus 6 Android Development] skhjpz:
What error you got? Maybe we can help
[Nexus 6 Android Development] daleski75:
From memory there is some files missing pertaining to sepolicy on the aosp build, the legacy build not sure what that fails on.
[Nexus 6 Android Development] Frozt:
[MENTION=1637948]daleski[/MENTION] thanks for all your hard work compiling and putting time into PA when no one else would, I know its just compiling like you said but you gave us that piece of pie we wouldn't have otherwise!

(I'm not currently using PA as a daily)
[Nexus 6 Android Development] ilpolpi65:
first of all sorry about my english,

I was trying to build pa for shamu but I always have the same error [MENTION=1095206]daleski75[/MENTION] post#17, the odd thing is that if you try to build for another device like flo or hammerhead you have the same error....( so I suppose that the problem is not about a specfic device(shamu) but a generic issue

Instead if I build shamu with aospa_L all run ok....
[Nexus 6 Android Development] daleski75:
When did you build the legacy Pa? I tried on Friday but mine failed
[Nexus 6 Android Development] ilpolpi65:
Yesterday 16/05 Saturday (italian time)
[Nexus 6 Android Development] daleski75:
Will do a build tomorrow then and post legacy builds until the AOSP ones start to work and it's nice to know that at least one of them compiles.
[Nexus 6 Android Development] DirtyDroidX:
I've kept a eye on this thread for a long time. Actually, I'm running PAC 5.0.2 still. Anyway, without getting into the "crap" I see brewing; has anyone manually pulled all source or picks and adjust the build manifest to reflect? It's a simple question but little things can cause errors.
[Nexus 6 Android Development] VECTUS:
Dale is working on this pretty hard for you guys. I gave it a go and had issues also (but still more than happy to help Dale when he needs it).

.. I think PA's git is still a WIP and still needs time to come around personally. Your idea sounds good, but in practice its not quite that simple (not being a jerk, just stating my experience). So people are still working on PA for n6, but its slow go... Anyhoo, we all just want to get along for a common goal so no one needs to take any posts to the extreme... There's more to life than Android/cellphones.... Whooaaa, did I just type that??? Meh
[Nexus 6 Android Development] TonyStark R.I.P.:
See this ^^^, this is helpful.

Lets try to stay civil in here please.

If anyone needs to discuss how big there wigwam is, this isn't the place. Bring your indifference to PM.

Leave the Development thread for Development.

It would appear this has been missed ^^^

Please sit tight and either help or don't respond.

Thanks for understanding.

TS out;)
[Nexus 6 Android Development] DirtyDroidX:
I'm not sticking my nose in,up,sideways or anyways in anyway when I say I no my way around a Linux box pretty well ;) I was head Admin of a popular android website and helped a lot of guys/groups out. Life has put this hobby on the back burner over the past few years. As of late I'm having more time to tinker again;thanks to a 2nd divorce,ahh,anyway.

Can you post the manifest you guys are using or link me to what you're pulling down from GIT or wherever else.

I don't have problems with helping and like problem solving build errors. If you guys are OK then good enough. If you need some help just shoot me a PM.

DDX
[Nexus 6 Android Development] skhjpz:
From what I saw in PA community they are working on shamu, try change name of folder Motorola to moto
[Nexus 6 Android Development] daleski75:
I don't think renaming folders will help but thanks for trying.
[Nexus 6 Android Development] daleski75:
Update for everyone.

I am trying to do builds each day and I know of others who have managed to get a legacy build out (although PA running CM feels all kind of wrong lol) however because PA is still very much in a alpha state working builds are going to be few and far between but the second I get a build to work I will post it on the OP right away.
[Nexus 6 Android Development] DirtyDroidX:
Yeah they cloned CALF (CM) make it work. Are you using proprietary blobs to setup the make files? I wouldn't worry about the kernel to much cause the stock AOSP should at least boot. JMO
[Nexus 6 Android Development] daleski75:
I am using the blobs which get downloaded when doing the first run of ./rom_build.sh shamu and the compilation gets pretty much all the way through and fails right at the end.
[Nexus 6 Android Development] skhjpz:
So try clean build
[Nexus 6 Android Development] DirtyDroidX:
What's the build error? Can you paste bin the last 30 lines?

Also I would clear the room service put a new one in then "repo sync -f && make clean" just for kicks.
[Nexus 6 Android Development] daleski75:
Going to try the repo sync -f etc first and see if that compiles and if not will post the error on pastebin.
[Nexus 6 Android Development] TonyStark R.I.P.:
[MENTION=1095206]daleski75[/MENTION]

Thank you sir:good:
[Nexus 6 Android Development] micmars:
Blasphemy...in my home it's Android, and idiotic family members a distant second.

I thought this was one of those universal truths that everyone just accepted, like rabbit's feet and unicorns.
[Nexus 6 Android Development] daleski75:
Did a rm -rf aospal and then did a fresh repo sync etc and get the same error.

www.pastebin.com/dbsuQptC

EDIT

Think I might of cracked it although I could build euphoria and CM on the same VM it looks like PA needs more resources so I have upped the RAM and swapfile to see if this now works.
[Nexus 6 Android Development] DirtyDroidX:
That's all webview stuff. I would cut out all webview from the make cause it can be downloaded on market. Or use a another Roms files that have it working.
[Nexus 6 Android Development] daleski75:
Got the builds working again by ditching Ubuntu had issues with inodes running out (don't ask me how) /tmp filling up and a lot more besides.

Moved over the BBQ Linux and copied across my build folder and voila compiled right away.

Legacy Build is uploading now with a change log and will try the AOSP build later on tonight.
[Nexus 6 Android Development] daleski75:
New build and changelog posted and this is untested as I no longer own a Nexus 6.

Doing a repo sync of PA AOSP now and will see if that compiles.
[Nexus 6 Android Development] an21281:
Downloading now will report back
[Nexus 6 Android Development] Hogyoku:
At first boot i wasnt able to get into the display setting but after flashing a custom kernel in putting selinux in permissive it workd fine.

Thanks for the rom !
[Nexus 6 Android Development] frankymix:
Yes I also got the display setting force close. Will try flash a different kernel.
[Nexus 6 Android Development] daleski75:
Hopefully that will be fixed in a future build and will keep an eye on the commits for this one.
[Nexus 6 Android Development] an21281:
Same here even with flashing custom kernal, will wait for the next update. Thanks for this!
[Nexus 6 Android Development] frankymix:
Tried different kernel but no dice. Other than that everything else seems to be working fine. Good job!
[Nexus 6 Android Development] daleski75:
New build with changelog uploading soon ;)
[Nexus 6 Android Development] skhjpz:
Any word about AOSP build?
[Nexus 6 Android Development] ilpolpi65:
For now as workaround you can use:

http://www.xda-developers.com/easily-change-your-android-selinux-mode/
[Nexus 6 Android Development] Hogyoku:
try elementalX that did the trick for me
[Nexus 6 Android Development] daleski75:
AOSP still fails to build
[Nexus 6 Android Development] DirtyDroidX:
[MENTION=1095206]daleski75[/MENTION] I would add to the OP about jumping from any 5.0.X to 5.1.1 ROM-Doing so you should flash the updated firmware files for bootloader, radio etc etc. These can cause a ton of errors in general.

Info on 5.1.1 updated firmware -- http://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052

Also if people are having problems with display FC, try switching themes and doing a cache wipe.
[Nexus 6 Android Development] skhjpz:
Try cherry pick those commits

https://gerrit.paranoidandroid.co/#/c/670/

https://gerrit.paranoidandroid.co/#/c/669/

https://gerrit.paranoidandroid.co/#/c/677/

https://gerrit.paranoidandroid.co/#/c/683/

They are blobs, device proprietary files and some fixes :)
[Nexus 6 Android Development] DirtyDroidX:
I don't believe he knows how to cmd picks in. Lol I was just looking through those a little bit ago, was going to suggest the same [emoji12]
[Nexus 6 Android Development] daleski75:
Cherry picking is easy but it can also cause issues which is why I don't normally attempt it.
[Nexus 6 Android Development] skhjpz:
I still would give it try, if something go wrong just type repo sync :p
[Nexus 6 Android Development] daleski75:
Not quite as simple as doing another repo sync but I get what you mean and I will consider it but I cannot test it as I no longer own a N6.
[Nexus 6 Android Development] an21281:
I'm available to test any time, also don't mind clean wipes or even factory restores if necessary... Let me know
[Nexus 6 Android Development] frankymix:
As for now I will leave the kernel I have. Battery life is awesome with it. I can live without the display settings as I can adjust everything in kernel adiutor.

Thanks for the suggestion.
[Nexus 6 Android Development] frankymix:
new update

Will you implement the new WiFi calling update the nexus 6 is receiving this weekend?
[Nexus 6 Android Development] seangeezy12:
VoLTE?
[Nexus 6 Android Development] TonyStark R.I.P.:
Bananas in pajamas?
[Nexus 6 Android Development] daleski75:
New Legacy build coming shortly and will try to get the AOSP compiling as well a bit later on.

Legacy build with change log now up on the first post.
[Nexus 6 Android Development] DirtyDroidX:
Are coming down the stairs.
[Nexus 6 Android Development] dirtyjersey856:
Nice! Been running the 22nd build since it was posted and I must say its been awesome with latest Zen kernel. Fantastic battery life, smooth & snappy. Only issue was the Display Settings fc that was already stated, but otherwise a stellar build. Its been nice to finally be able to use Unofficial Paranoid Android Walls/ ParaPaper which I suggest anyone using PA should go and check out on G+
[Nexus 6 Android Development] puertorecon:
Is the settings fc still. I want to flash,....
[Nexus 6 Android Development] puertorecon:
Well I flashed,...running super. Just need the display setting to work. Some how this ROM has a DPI issue. To get it to look stock in the app drawer,..I had to change DPI to 593.
[Nexus 6 Android Development] frankymix:
How do you use PARApaper? Looks pretty awesome.

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

Only bug I've found other than FC display settings will have to be when you connect a head phone or aux cord to listen from them you have to hit the speaker icon. Anybody else having this bug?