[ROM] Dirty Unicorns 6.0.1 {Flounder} (09/09/16)

[NYCHitman1]

I was wondering if anyone else is experiencing a crash when trying to change the screen lock in the security settings. I have DU 10. 1 Official installed w/ the latest Banks GAPPS. I also did a clean install. By default DU is set to swipe, but every time I try to change the screen lock to something more secure, settings crashes.
I'm experiencing this problem on both my N9 and my wife's N9. Any help would be appreciated.
By the way, thank you so much for such an excellent ROM!

Are you using a theme? If so, there's your problem.

 

[ofc123]

Are you using a theme? If so, there's your problem.

No theme. I'm on full stock DU.

 

[NYCHitman1]

No theme. I'm on full stock DU.

So am I (obviously) and I don't have a problem.

Did you clean flash the build? Are you up to date with your vendor.img?

 

[hopscotchjunkie]

Latest weekly (DU_flounder_6.0.1_20160415-2349.v10.1-WEEKLIES.zip) gives an outdated/incorrect vendor image error with the MOB30D vendor.img

build.prop still shows
ro.build.description=flounder-user 6.0.1 MMB29V 2554798 release-keys
ro.build.fingerprint=google/volantis/flounder:6.0.1/MMB29V/2554798:user/release-keys

Should this have been updated by this change (merged a few days prior to build) http://gerrit.dirtyunicorns.com/#/c/28102 or is there something else responsible for the details in build.prop?

 

[NYCHitman1]

Latest weekly (DU_flounder_6.0.1_20160415-2349.v10.1-WEEKLIES.zip) gives an outdated/incorrect vendor image error with the MOB30D vendor.img

build.prop still shows
ro.build.description=flounder-user 6.0.1 MMB29V 2554798 release-keys
ro.build.fingerprint=google/volantis/flounder:6.0.1/MMB29V/2554798:user/release-keys

Should this have been updated by this change (merged a few days prior to build) http://gerrit.dirtyunicorns.com/#/c/28102 or is there something else responsible for the details in build.prop?

For some unknown reason, the weeklies didn't properly sync.

 

[euqilobaid]

Just installed the ROM and there are several system apps (pre-installed) which are almost the same as the ones i install from the Play store. Is there a way to test which apps are safe to remove from the system via Dirty Tweaks => System App Remover?

I'm considering removing: Calendar, Email, Chromium, Gallery, Clock and Documents.
I'm using: Google Calendar, Gmail, Chrome, Pictures, Google Clock and Solid Explorer.

 

[NYCHitman1]

Just installed the ROM and there are several system apps (pre-installed) which are almost the same as the ones i install from the Play store. Is there a way to test which apps are safe to remove from the system via Dirty Tweaks => System App Remover?

I'm considering removing: Calendar, Email, Chromium, Gallery, Clock and Documents.
I'm using: Google Calendar, Gmail, Chrome, Pictures, Google Clock and Solid Explorer.

Don't remove Documents, but you can remove/freeze the rest.

 

[euqilobaid]

I have removed seven items with "System App Remover". Didn't write their exact names, but they were something like: Calendar, Calendar Widgets, DeskClock, Chromium, Email, DocumentsUI and Gallery. I've restarted the tablet and so far everything is working fine. I've made TWRP backup just in case i'll need to roll back the changes. So far the ROM is amazingly smooth and without any issue i was facing on another custom ROM which i was previously using on the Nexus 9.

 

[NYCHitman1]

I have removed seven items with "System App Remover". Didn't write their exact names, but they were something like: Calendar, Calendar Widgets, DeskClock, Chromium, Email, DocumentsUI and Gallery. I've restarted the tablet and so far everything is working fine. I've made TWRP backup just in case i'll need to roll back the changes. So far the ROM is amazingly smooth and without any issue i was facing on another custom ROM which i was previously using on the Nexus 9.

You'll get FC's now when apps call for the DocumentUI view/layout, but it is what it is.

 

[euqilobaid]

Thanks for the heads-up. I reverted to my TWRP backup but for some reason (guess the tablet encryption which is on by default) i can't get past the lock screen. I'm stuck on lock screen prompt Though i'm 100% sure that i'm entering correct password it doesn't unlock. Ah well, guess i'll wipe everything and do a full clean setup

Love that warm g33ky feeling when i learn something new, but also hate the n00b thing in me which forces me to make all those stupid errors

I'll remove Calendar, Calendar Widgets, DeskClock, Chromium, Email and Gallery. I'll leave DocumentsUI intact.

 

[NYCHitman1]

Thanks for the heads-up. I reverted to my TWRP backup but for some reason (guess the tablet encryption which is on by default) i can't get past the lock screen. I'm stuck on lock screen prompt Though i'm 100% sure that i'm entering correct password it doesn't unlock. Ah well, guess i'll wipe everything and do a full clean setup

Love that warm g33ky feeling when i learn something new, but also hate the n00b thing in me which forces me to make all those stupid errors

I'll remove Calendar, Calendar Widgets, DeskClock, Chromium, Email and Gallery. I'll leave DocumentsUI intact.

Encryption isn't forced on DU. Did you decrypt your device?

 

[euqilobaid]

Nope, didn't decrypt the tablet. Guess i should have I'm rather new to Nexus 9 and i never used android encryption before. Guess the TWPR backup is rather useless with device encryption turned on I'm confused since the backup was created on the internal storage and it was accessible from TWPR just fine, but when i booted the tablet i couldn't get past the lock screen with the password and i'm 100% sure i was entering the proper one. I just don't get it :silly:

 

[NYCHitman1]

Nope, didn't decrypt the tablet. Guess i should have I'm rather new to Nexus 9 and i never used android encryption before. Guess the TWPR backup is rather useless with device encryption turned on I'm confused since the backup was created on the internal storage and it was accessible from TWPR just fine, but when i booted the tablet i couldn't get past the lock screen with the password and i'm 100% sure i was entering the proper one. I just don't get it :silly:

That happens when you don't properly clean flash.

 

[euqilobaid]

What do you mean by "properly clean flash"? Before i restored the backup i wiped everything except internal storage.
I am confused since the backup was stored on the internal storage which was accessed by TWRP without any problems (although the device is encrypeted by defalut), but when i booted the device i could not get past the lock screen.

 

[NYCHitman1]

What do you mean by "properly clean flash"? Before i restored the backup i wiped everything except internal storage.
I am confused since the backup was stored on the internal storage which was accessed by TWRP without any problems (although the device is encrypeted by defalut), but when i booted the device i could not get past the lock screen.

You can fix that via recovery, btw. If you go into system/data in TWRP (File Manager) > delete the file called locksettings.db.

 

[jlokos]

You can fix that via recovery, btw. If you go into system/data in TWRP (File Manager) > delete the file called locksettings.db.

This is a more general question. My device is decrypted. I always use a lockscreen pattern or pin. If I dirty flash an existing rom, or clean flash a new one (obviously), I have no issues with the lockscreen. However, if I restore a backup and then dirty flash, I always get the lockscreen error message and have to go into TWRP File Manager and delete the locksettings files. Is this a problem peculiar to Nexus 9? I don't have this issue with my Nexus 6. Thanks for your help and the great dirty builds.

 

[NYCHitman1]

This is a more general question. My device is decrypted. I always use a lockscreen pattern or pin. If I dirty flash an existing rom, or clean flash a new one (obviously), I have no issues with the lockscreen. However, if I restore a backup and then dirty flash, I always get the lockscreen error message and have to go into TWRP File Manager and delete the locksettings files. Is this a problem peculiar to Nexus 9? I don't have this issue with my Nexus 6. Thanks for your help and the great dirty builds.

It's a recovery issue. Doesn't have anything to do with the ROM itself.

 

[jlokos]

It's a recovery issue. Doesn't have anything to do with the ROM itself.

Got it! Thanks very much.

 

[euqilobaid]

You can fix that via recovery, btw. If you go into system/data in TWRP (File Manager) > delete the file called locksettings.db.

LOL, if i knew that yesterday i wouldn't have to go through a 1/2 a day new setup cycle for the tablet Ah well, stupidity and ignorance are a time waster Thank you for the help.

So if i use restore feature in TWRP i should:
1. wipe cache, dalvik and system
2. restore system
3. delete the file
4. enjoy the ROM
?
This will only fix the lock screen issue, but it won't decrypt the tablet? This works with encrypted tablet?

Sorry for the flood of questions, but i want to make sure i understand things right so i don't act as a n00b again

 

[NYCHitman1]

LOL, if i knew that yesterday i wouldn't have to go through a 1/2 a day new setup cycle for the tablet Ah well, stupidity and ignorance are a time waster Thank you for the help.

So if i use restore feature in TWRP i should:
1. wipe cache, dalvik and system
2. restore system
3. delete the file
4. enjoy the ROM
?
This will only fix the lock screen issue, but it won't decrypt the tablet? This works with encrypted tablet?

Sorry for the flood of questions, but i want to make sure i understand things right so i don't act as a n00b again

Doing what I aforementioned, it just removes the current lockscreen settings. You can re-enable it within the ROM, if you desire.

To decrypt, you will need to wipe the data partition in TWRP. If you click on "Wipe" -- you will see the option to "WIPE DATA" which will provide further instructions. Keep in mind that decrypting does wipe your entire storage.