yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] Mentalmuso:
I'm going to give you guys a SystemUI.apk to try. You will have to replace the SystemUI.apk in /system/priv-app/SystemUI folder with it, then chmod 755 it. This can all be done in twrp.

Encryption must not like a modified SystemUI.apk, and there may be one thing I changed in the stock apk, I can't remember. So below is the stock deodexed one

Failing that, we can try a bone stock framework-res.apk also, though I doubt that would cause a ui crash

Also..... try flashing the stock Vendor.img AFTER the rom has flashed. This way if it's vendor related that should fix it up, and I'd know which direction to look then..

https://drive.google.com/file/d/0ByUAe3vAX9jSZlYzRFlVV09CQ00/view?usp=drivesdk

Of course. Then there is the question. Are you needing your SD card to be encrypted? Flashing stock before my rom then letting it boot creates an encrypted sdcard. If you don't care to be encrypted, flash stock, but don't let it boot, then flash WETA, the kernel in WETA has encryption disabled. So when you boot into WETA you have the choice to encrypt your phone after. Maybe you could try encrypting that way instead if you need it.

?--->
[Nexus 6P Android Development] kouklo:
im rooting right now. When that is done ill install your rom and before I reboot ill put that file in the proper location. Is that right?
[Nexus 6P Android Development] Mentalmuso:
Are you needing encryption?

Of course wiping your sdcard to become decrypted isn't ideal

The systemui.apk can be placed after the WETA rom has flashed. If I was home I'd make you a zip to flash

?--->
[Nexus 6P Android Development] Mentalmuso:
Did you say earlier that you were running V2.1 fine with encryption?

?--->
[Nexus 6P Android Development] kouklo:
I truly don't care about Encryption, I can take it or leave it. from everything I have read, there is really no major pulse or minus if its encrypted or not. I just want to get your rom to work. LOL.

For the life of me I cant find /system/priv-app/SystemUI anywhere. any ideas? Maybe I should try a different way?

Yes I was running 2.1 with no problems, I never really looked to see if it was encrypted or not

---------- Post added at 12:21 AM ---------- Previous post was at 12:06 AM ----------

so /system/priv-app/SystemUI doesn't exist. It took me a bit but I figured out how to create a folder in TWRP for the SystemUI.apk. I just rebooted, wish me luck! LOL

---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------

still the same thing..........I feel like you guys didnt wish me luck. LOL

any idea what I should do next?
[Nexus 6P Android Development] kouklo:
another update- I was doing some research on how to decrypt the phone. I found this site. http://www.droidorigin.com/decrypt-nexus-6p/ he has MTC19V that's not encrypted. I flash stock again then I flashed that IMG. I rebooted 2 times just to make sure it was still good. LOL. I tried flashing your rom again and the same thing happened.

TL;DR LOL both encrypted and decrypted make no difference.
[Nexus 6P Android Development] Mentalmuso:
I have no other advice except formatting your data partition and starting from scratch. And as for there being no systemui, your phone won't boot without it, so maybe you haven't mounted system in twrp.

Keep in mind if you flash back to stock to try again, don't let stock boot up, if it does, then it will encrypt your data partition automatically. You don't want that.

?--->
[Nexus 6P Android Development] Jammol:
Yes v2.1 was working with encryption.
[Nexus 6P Android Development] Mentalmuso:
Here is a flashable zip of a bone stock system ui. If you haven't tried it already.

https://drive.google.com/file/d/0ByUAe3vAX9jSZVFYb3N3cnQ0ZVk/view?usp=drivesdk

?--->
[Nexus 6P Android Development] Mentalmuso:
I really thank all the testing you have done for this. I have only one other idea if that systemui.apk zip doesn't work. And that is to start from scratch with a V3.1. I'm currently deodexing stock rom. Then I'm going to test it out myself. I'll post here so you can test also if you still feel up to it. But just in case you don't, I want to make sure I'm doing the same thing as you...

This is what I'll do to test..

Flash stock images.

Boot into stock rom letting it encrypt?

Flash twrp

Flash WETA rom

Boot into WETA and see if it crashes.

I want to see this crash for myself and my sdcard doesn't have any data on it I don't mind losing.

?--->
[Nexus 6P Android Development] kouklo:
ya thats exactly what I do.

I wont get a chance to try your zip until tomorrow, but ill let you know once its done.
[Nexus 6P Android Development] Jammol:
Correct. That's exactly what I'm doing. Also make sure you setup fingerprint with pin.

It's no biggie testing for me. Great way to help troubleshoot.

I'm starting to think it's SuperSU. The reason why is I tried the new PA build and its not rooted. However once you flash SuperSU and reboot, system ui error at the pin entrance screen during boot. This is very odd that all of a sudden there's issues with all the versions down to v2.65. It's definitely not a June build issue because PA latest build on the site is off the May update.

Update: Wow so I think I just solved the issue in the most noobish way. I'm on PA right now and decided what the heck, let me flash SuperSU v2.65 and see what happens. Device is encrypted of course and have it setup and all that. So I flashed su and wiped cache and dal and rebooted. Pin entry came up, entered it, it rebooted (normal?) And pin entry again, finished booting, I'm now on rooted encrypted PA. WTF?!

About to try this same thing on META and will report back.

Btw, the system.ui zip you provided didn't do the trip.
[Nexus 6P Android Development] Mgrev:
Yes, PA has the CM theme engine, and with the limited testing i've had with bluetooth, it seemed to be just fine

---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------

it's at www.aospa.co
[Nexus 6P Android Development] spuri78:
thanks for your response. I was on pure nexus. Yep, advanced wipe. everything except internal. Using stock kernel as well.

Maybe I will flash again and this time won't flash the latest vendor image. Will report back.
[Nexus 6P Android Development] Mentalmuso:
Thanks. Ill test that out later. Everything tested fine for me, i must have missed something. Lucky its a first build huh. Im allowed mistakes on v1 haha

?-->
[Nexus 6P Android Development] Reuben_skelz92:
Had this ROM on my s6 and it was very good
[Nexus 6P Android Development] Mentalmuso:
WETA V1.0.1

Fixed Center Clock FC

Added 480dpi option

Download Page

--->
[Nexus 6P Android Development] razrlover:
Had force close on atmos and viper drivers not installed. Tried stk kernel then custom us permissive.

Then flashed guitardedhero viper dolby 4.8 over it and everything works now.

Thanks
[Nexus 6P Android Development] Mentalmuso:
Did you flash vendor after installing the rom?

?-->
[Nexus 6P Android Development] Mentalmuso:
Thanks, root didnt even stick for me this time around. Eish, does that guitarded mod work on enforcing?

?-->
[Nexus 6P Android Development] razrlover:
I'm not sure, your should pm him. From nexus 6 app and themes thread
[Nexus 6P Android Development] prestige2:
I love ROMs that focusing on the sound quality

Definitely will try this one.
[Nexus 6P Android Development] tweeny80:
Kia ora

NZ represent !!
[Nexus 6P Android Development] Mentalmuso:
I have fixed it, I will be uploading another update later tonight.
[Nexus 6P Android Development] Mentalmuso:
Chur bro
[Nexus 6P Android Development] Mentalmuso:
WETA V1.0.2

Fixed SuperSU and busybox install

Should have fixed v4a and Dolby

Added keep existing/flash nothing in kernel options

Download Page

?--->
[Nexus 6P Android Development] Mentalmuso:
How is this build working for people? Just wanting to make sure supersu and busybox are installed properly, and that v4a and dolby are working.

--->
[Nexus 6P Android Development] kaos80:
Thank you for sharing with us your rom.Una single question: Busybox is preinstalled or I'll have to install it manually?

Inviato dal mio Nexus 6P utilizzando Tapatalk
[Nexus 6P Android Development] Swamphound:
Thank you so much for sharing your build. Very sleek and had no trouble using Android Pay in two stores yesterday using your initial release. That's a first for me having it work without needing to make any changes. I've also learned what a wetapunga is!
[Nexus 6P Android Development] Mentalmuso:
Busybox is pre installed

?--->
[Nexus 6P Android Development] Mentalmuso:
I'll be making another update tonight with the new April security patches.

?--->
[Nexus 6P Android Development] xReaper7x:
Fantastic! I am patiently waiting for the new build :)
[Nexus 6P Android Development] razrlover:
Haven't had time to flash latest update with fixes. Looking forward to April update will test when its cooked and ready.
[Nexus 6P Android Development] phillymade:
OK, I'll be the one to ask...why are we talking about PA ROM on this ROM's thread? This is a fantastic ROM.

Just saying....bash away now....
[Nexus 6P Android Development] Mentalmuso:
Haha, ok well let me know how you go, I'm glad you found something

?--->
[Nexus 6P Android Development] davey89:
Just jumping in to say I've been having the exact same issue as Jammol.. Can't add anything of value that he hasn't already said, but I'm happy to help with any testing :)
[Nexus 6P Android Development] Jammol:
Saying bash away now looks as if you want to start something. Also it just shows that you have an idea of what the outcome response will be, so why even say anything when you post originally started off innocent. Just saying.

PA came up because it's the only other aosp/stock based ROM that isn't rooted already (that I know of). I used that ROM to see if I could cause the same issue to occur. This is the only stock ROM with a mod that was updated to the June patch (that I know of). Instead of being that way, you really could help the situation but meh, it's whatever.

[MENTION=4553200]Mentalmuso[/MENTION] did not work. I have clue where to dig now for ideas of what it could be. Maybe the fact that it's rooted before first boot of the ROM itself? That doesn't even make sense because v2.1 was totally fine being encrypted.

The ROM is definitely still functional though, it's just annoying if a reboot is needed, lol. Takes about 15 minutes of rapid tapping to enter the pin code. ?
[Nexus 6P Android Development] kouklo:
I can do some testing too. is there something in particular you want to try? keep in mind that I have nothing on my SD card, I can wipe everything.
[Nexus 6P Android Development] theellucidone:
So I have a rookie issue. I cannot get adb to authorize me. Plug phone in and just keep getting unauthorized. I'm trying to update to 3.0.1 but can't flash vendor or radio files. Can anyone please help me here. Phone folder /data/misc/adb is empty. I've cleared adb from laptop and restarted server. Ive reinstalled drivers. Nothing is working. Anyone have any ideas?
[Nexus 6P Android Development] KLit75:
Anyone flash this to secondary with multirom? I flash the vendor.zip, ROM and everything flashes fine but when it boots up I can't connect to WiFi for the initial setup. WiFi never turns on.
[Nexus 6P Android Development] Jammol:
Did you enable debugging under developer options? You have to enable that first while the phone is disconnected from the computer, once on make sure verification for usb connections is on(2-3 options below debug option), once you connect the device and you run an adb command, it should ask you to accept commands from the source on the phone itself.
[Nexus 6P Android Development] theellucidone:
Yes it is enabled. Still a no go. Where is the revoke authorizations option? Cannot find it
[Nexus 6P Android Development] trapharder4844:
Anyone flashed xposed?
[Nexus 6P Android Development] KLit75:
Think this was answered very early in the thread and its a yes. xposed was working. No reason to think there's issues now.
[Nexus 6P Android Development] Mentalmuso:
Yes, I tested the latest build a couple of days ago

?--->
[Nexus 6P Android Development] A.R.I.S.E. Sound Systems:
Might want to update the OP with the ARISE version being used, I'm glad you like it enough to use it in your ROM :good:
[Nexus 6P Android Development] trapharder4844:
Could you post the link
[Nexus 6P Android Development] Mentalmuso:
Nice, will do. Is exodus out of beta yet?

?--->
[Nexus 6P Android Development] Mentalmuso:
Everything you need is in here, http://xdaforums.com/showthread.php?t=3034811

?--->
[Nexus 6P Android Development] mackster248:
Thanks for the update! Out of curiosity, why did you remove the battery percentage from there lock screen and notification pull down? Is it to save a little battery?
[Nexus 6P Android Development] Mentalmuso:
It was bugging me and another user. 3minit battery has percentage so it was doubling up in some cases. But I have realized, like a dummy, I modded the stock systemui as well when I shouldn't have. It'll be back for stock in the next update.

?--->
[Nexus 6P Android Development] rndchef:
For the life of me, I cannot get this rom to boot again. I was able to get it to boot up once but the keyboard issue prevented me from moving forward. Thought it was an overlay issue. Have tried three times with a clean install and still the system ui crash every time. Can't figure out how I got it to boot the first time. I am encrypted and using the vendor image correctly. I have read over and over and can't seem to figure it out. As a flashaholic, this is very troubling! :crying: I can't get any sound mods to work on this phone. Tried Dolby and Viper.
[Nexus 6P Android Development] Mentalmuso:
I have to ask.. wipe dalvik?

?--->
[Nexus 6P Android Development] rndchef:
Tried that as well. I wipe dalvik, system, data and cache. Flash vendor image and rom. Then wipe dalvik. Still system crash and have to restore twrp.
[Nexus 6P Android Development] kouklo:
Its the exact same thing that happened to me mdchef. I flashed it 7 or 8 times. I tried dirty/clean I even tried nexus root tool kit. I managed to get in to the phone 2 times, but like you, no keyboard or on screen buttons. I eventually gave up and went back to 2.1
[Nexus 6P Android Development] Jammol:
Read my post that's two pages back. You have to tap on the pin entry space right after getting the FC notification to disappear. You have to be really quick.

Turn screen off and then on again, you should see the keyboard.

Tap ok then quickly the first number for your code

Tap code entry space quickly for keyboard to show up again.

Continue this process until code is entered and phone boots up.
[Nexus 6P Android Development] KLit75:
Finally was able to flash this as a secondary with multirom (needed to flash vendor with fastboot.)

Excellent so far. Only thing I miss is sweep2wake. Is there anyway to do this with this kernel? Thanks
[Nexus 6P Android Development] Mentalmuso:
Im glad you found a method. I did some testing this morning, i booted it up in stock to encrypt data partition. Then i flashed a bone stock but deodexed mtc19v rom. Pin screen came up, i entered the pin, and phone would just reboot.

My initial thought after that was maybe, going into twrp and backup data, transferring the backup to your pc. Then flashing userdata.img in bootloader to format data partition.

Boot into weta go to settings and setup encrytion, may take a while. Then after you are encrypted try rebooting and see if there are the same issues. If not, then restore your twrp data backup to newly encryted partition.

Also if any of you have tried another stock img based rom that has encryption working fine, let me know and i will have a chat to the dev.

--->
[Nexus 6P Android Development] Jammol:
That's what I did to get the pin screen to work without issues.

I've ran this with encryption from boot.

http://xdaforums.com/showthread.php?t=3372600
[Nexus 6P Android Development] rndchef:
I read that but all I get is System FC box over and over with a black screen behind it before it is supposed to boot. What pin? Never used a pin just swipe and fingerprints but nothing is setup on a clean flash. Thanks for responding. I suppose giving up until the rom is more stable to install. Thanks for responses!
[Nexus 6P Android Development] Jammol:
When you use fingerprint security at setup or anytime after, you are required to use either a pattern(swipe pattern), pin(numbers only) or passcode(letters and numbers). Once that is set, a pin pad will show up on every single boot because the device is then encrypted with that pin instead of the internal system default.

The only way to get to not being encrypted is to wipe the actual storage of the phone by choosing to format Data and then typing Yes. This will then enable unencrypted usage of the device.

The ROM is perfectly stable, there's just an issue with the way SuperSU is dealing with the encryption.

If you want to use this ROM without errors do this:

Save whatever you need to

Full wipe including Format Data

Flash the ROM and let it boot

You shouldn't be met with any pin entry whatsoever as we just wiped it above.

Setup your device without any security (just swipe)

Reboot to see if it gives you System FC.

If that's good to go, head to settings>security and setup encryption. It should force you to also setup either fingerprint, pin, pattern, or passcode. Encryption can take over an hour and requires constant charging of the device.

Once encryption is done, you should now have the device as if it was encrypted already (coming from stock), and simply flashed the ROM.
[Nexus 6P Android Development] Mentalmuso:
Having forced encryption by default is really a dumb idea for Nexus. Did you say that SuperSU 2.65 worked ok with encryption? Or is it all messed up now?

?--->
[Nexus 6P Android Development] Mentalmuso:
I just read in that link to stock rom you posted a few back, that you need to format user data and reencrypt. I think you already figured that out for everyone. If reassures me that it isn't my rom though we should work out the procedures and I'll put it in the op.

?--->
[Nexus 6P Android Development] Jammol:
I didn't follow those procedures. My internal was already encrypted from stock though. I just flashed the ROM and left it encrypted. Didn't have any issues with pin entry even though I'm flashing both Roms the exact same way. I'm really thinking it has to do with SuperSU.

---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------

Did not matter what version of SuperSU I used, it would still give the error at pin entry on boot.
[Nexus 6P Android Development] Mentalmuso:
It's either that or deodexing. I noticed that rom is left forced. This is usually because deodexing stock Google apps can be troublesome. It changes with every update too. The May update all I had to do was replace webview with one from a gapps package. This time around there was even more.. I can't help but think this is part of the issue. I'm thinking an odexed version may be on the cards. This way all the Google apps stay as angler.

... I'm also wondering and did so last month, whether it's even worth deodexing any more. You can run android now with only a deodexed systemui if you wanted systemui mods. Franework-res.apk is already deodexed stock. That's all I ever mod... I'm going to build one and you can try it out

?--->
[Nexus 6P Android Development] Jammol:
Well thank you Google for switching things up month to month eh?!

I'll be glad to test it to see what happens. I don't blame you for questioning the point of deodexing. I gave up on it a few Android builds back because I always end up just running stock rooted, lol.

It's whatever though, I don't dev anymore so I sleep better at night. :P
[Nexus 6P Android Development] Mentalmuso:
I just wiped and flashed to stock

Flashed stock odexed rom zip

rooted

and still the same issue.

Im giving up at this point, i think some security features have come through from Android N. They have the same issue there also.

--->
[Nexus 6P Android Development] Mentalmuso:
Op updated with new install mothod for Encrypteeees

Please correct me if im wrong below, i am not an encrypter of my device, and rely on users for help here. You only need to re encrypt your device if you need it.

ENCRYPTED DEVICES - If you have your data partition encrypted, you are going to have issues unless you do the following..

1. Make a Nandroid backup of your data partition, and copy it to your PC.

2. Copy WETA zip to PC

3. Now making sure your backup is on your PC... go into TWRP and Format your data partition.

4. reboot TWRP, then copy WETA zip onto device

5. Copy vendor.img onto device

6. Flash vendor.img

7. Flash WETA.zip

8. Boot

9. Once setup, reboot into recovery, copy your backup back onto your device and restore Data.

10. Boot up, and go to settings and encrypt device if needed.

--->
[Nexus 6P Android Development] rndchef:
Tried exactly as listed and continue to get the same System ui crash upon startup and can't get past it so have to restore a nandroid. the only question is should I not allow system partition to be modified in TWRP? That is the only thing that came up on TWRP before flashing vendor image that wasn't addressed. I did allow it.
[Nexus 6P Android Development] Mentalmuso:
You need to allow system modification for the rom to flash.

Are you saying you are getting a systemui crash after you restore your backup? Or after you have encrypted everything through settings?

?--->
[Nexus 6P Android Development] rndchef:
Ok. I allowed the modification. I get Systemui crash the moment it attempts to boot up after clean install of Vendor & Rom. Could it be one of the modifications I am choosing in the Aroma? I am choosing permissive kernel, smaller navi bar dpi, increased volume and ad removal. that is the only possible issue after data format. It must be one of the mods.
[Nexus 6P Android Development] Mentalmuso:
Are you encrypted and did you format your data partition? In twrp selecting format data and typing yes to confirm? Basically you can't flash WETA over the top of an encrypted data partition. It'll crash.

?--->
[Nexus 6P Android Development] rndchef:
I followed the instructions completely and formatted the data partition which clean wiped everything. Should have worked.
[Nexus 6P Android Development] Mentalmuso:
Did you restore your data or try booting it clean? This rom works perfectly with a non encrypted data partition. Did you flash back to stock at all? Do that then try again

?--->
[Nexus 6P Android Development] Randomsmack:
Arise( Exodus RC1) sound mod is out of beta
[Nexus 6P Android Development] Mentalmuso:
OK after hours of testing. I have been running encrypted for a while and have found that having a pin setup on device startup is not going to work. You can still have an encrypted device, though I would recommend disabling the pin on startup option, this then let's everything work as it should, using the stock SystemUI with device startup pin will work as normal in the next update but this method will have to be used if you want status bar mods.

To do this go into settings/security/screen lock

Setup a pin but when prompted select to not use on device startup. Now you won't have the ui crashes.

(You can get past the pin if you are quick, pressing on on the ui crash popup and activating keyboard then pressing the pin in. One by one. It's an art but can be done)

Another way is to flash to stock IMG. Boot up letting it encrypt data, at setup make sure not to select pin on device startup. Now when you flash weta you won't get any issues if you select a modded SystemUI option like 3minit. All other mods like 40dpi navbar and system dpi can still be used normally without problems.