Root [ROM] Dirty Unicorns 5.1.1 {HAMMERHEAD} (4/26/15)

[Hook]

After a few distractions, I finally got around to the new official build tonight. I did a clean install just because I like to every so often, though dirty flashes almost always work for me.

As usual, I'm really loving it. Thanks for all the hard work to NYCHitman and the rest of the Dirty Crew. This is really such a fantastic ROM.

 

[Brian706]

Will probably flash tomorrow. Just got back into town and too tired for a clean flash.

 

[NYCHitman1]

For those experiencing force closes, please get me a log of them. That's really the only way I can help you.

 

[thisISjoel]

For those experiencing force closes, please get me a log of them. That's really the only way I can help you.

How can I get logs of this kind of thing?

 

[Brian706]

How can I get logs of this kind of thing?

Easiest way: https://play.google.com/store/apps/details?id=org.jtb.alogcat

 

[NYCHitman1]

On a side note, I updated the OP to reflect all the latest changes to our template + added changelog, etc..

 

[thisISjoel]

Does this mean anything to anyone?

--------- beginning of /dev/log/main
I/System.out(26924): tainted command part 0: logcat
I/System.out(26924): tainted command part 1: -v
I/System.out(26924): tainted command part 2: brief
I/System.out(26924): tainted command part 3: *:V
I/System.out(26924): tainted command part 0: logcat
I/System.out(26924): tainted command part 1: -v
I/System.out(26924): tainted command part 2: brief
I/System.out(26924): tainted command part 3: *:V
D/Instrumentation(26924): PDroid:Instrumentation:execStartActivity: execStartActivity for org.jtb.alogcat
W/ContextImpl(26924): PDroid:ContextImpl: ContextImpl being created but already has sOuterContext
W/ContextImpl(26924): PDroid:ContextImpl: ContextImpl being created but already has sOuterContext
D/dalvikvm(26924): GC_CONCURRENT freed 10449K, 45% free 16590K/30028K, paused 3ms+3ms, total 28ms
D/Instrumentation(26924): PDroid:Instrumentation:execStartActivity: execStartActivity for android
I/System.out(26924): tainted command part 0: logcat
I/System.out(26924): tainted command part 1: -v
I/System.out(26924): tainted command part 2: brief
I/System.out(26924): tainted command part 3: *:V
D/Instrumentation(26924): PDroid:Instrumentation:execStartActivity: execStartActivity for org.jtb.alogcat
W/ContextImpl(26924): PDroid:ContextImpl: ContextImpl being created but already has sOuterContext
W/ContextImpl(26924): PDroid:ContextImpl: ContextImpl being created but already has sOuterContext
D/dalvikvm(26924): GC_CONCURRENT freed 606K, 41% free 16901K/28244K, paused 2ms+6ms, total 37ms
D/dalvikvm(26924): GC_CONCURRENT freed 1547K, 43% free 16334K/28244K, paused 2ms+2ms, total 16ms
I/System.out(26924): tainted command part 0: logcat
I/System.out(26924): tainted command part 1: -v
I/System.out(26924): tainted command part 2: brief
I/System.out(26924): tainted command part 3: *:V

I should probably just try a clean flash to see if that fixes my wallpaper issues, yeah?

 

[Hook]

Does this mean anything to anyone?

It will to a developer.

I should probably just try a clean flash to see if that fixes my wallpaper issues, yeah?

No, the wallpapers are not working, even with a clean flash. I suspect it may be as simple as the server link for the wallpapers needs to be updated. Not sure why they aren't just included in the ROM, but probably a low priority.

 

[thisISjoel]

It will to a developer.



No, the wallpapers are not working, even with a clean flash. I suspect it may be as simple as the server link for the wallpapers needs to be updated. Not sure why they aren't just included in the ROM, but probably a low priority.

Thanks I may still clean flash since I just did a nandroid backup anyway so may as well give it a swing.

EDIT: I used TWRP to do a factory reset and when it was done the phone booted straight into the welcome to DU screen, I didn't have to flash it. Is this still a clean flash or have I muffed up somewhere?

 

[Hunter5]

Thanks I may still clean flash since I just did a nandroid backup anyway so may as well give it a swing.

EDIT: I used TWRP to do a factory reset and when it was done the phone booted straight into the welcome to DU screen, I didn't have to flash it. Is this still a clean flash or have I muffed up somewhere?

Same thing happened to me so I went back to recovery and did a full wipe and tried again, this time I had to input all my info just like I had a new phone. You'll probably be ok but if you're like me I always do a clean install, just gives me piece of mind and I don't mind doing it.

Been 3 days now and everything is running perfect.

 

[Hook]

Thanks I may still clean flash since I just did a nandroid backup anyway so may as well give it a swing.

EDIT: I used TWRP to do a factory reset and when it was done the phone booted straight into the welcome to DU screen, I didn't have to flash it. Is this still a clean flash or have I muffed up somewhere?

I'm a little confused by your description. First, TWRP shouldn't reboot unless you tell it to. Second, the standard wipe does do a factory reset, which does reflash the current ROM, as any factory reset does, but since you have wiped data, it should make you go through all the pick language and set up account stuff even if you boot back into it without flashing. Reflashing the ROM wipes the system and boot partitions, which is why TWRP says "Most Of The Time This Is The Only Wipe You Need"-- you don't want the old data hanging around.

However, if you reboot from a factory reset, yes, I am assuming you would reboot into whatever was last flashed but without data (data here does not refer to internal storage-- I never wipe that). I guess if setup info is in the system or boot partitions, you might not have to do that.

I would do the standard wipe and then reflash the new DU to make sure there isn't stuff in the system and boot partitions you would rather not have.

Hopefully someone who really understands all this stuff better will comment because I think I just lead myself around in circles.

 

[Incakola]

Is anyone experiencing the dialer app fcing when looking up a contact?

 

[Hook]

Is anyone experiencing the dialer app fcing when looking up a contact?

I'm not. Searching, lookup, select from dialing all work fine.

 

[Incakola]

I'm not. Searching, lookup, select from dialing all work fine.

Which gapps did you use? Also does the volume rocker work for you?

 

[Hook]

Which gapps did you use? Also does the volume rocker work for you?

I'm using DU_TBO_Gapps_04-11.zip.

And I suspect you aren't asking me whether the volume rocker changes volume (it does) . I think I remember some setting to get it to do something else, but i don't use it. Tell me exactly what to try and I'll test it.

 

[xdrc45]

Is anyone experiencing the dialer app fcing when looking up a contact?

My dialer app is working fine here too.
I initially used the Micro gapps when I flashed the new build, but then I wanted to try out the DU TBO gapps and switched. Dialer app was working fine on both versions.

The only other thing I've noticed with the new build is that if I hold down the power button to long or after the "Power Menu" opens, the phone will perform a soft reboot.

 

[Hook]

The only other thing I've noticed with the new build is that if I hold down the power button to long or after the "Power Menu" opens, the phone will perform a soft reboot.

That's normal stock Android. It is indeed a soft reset that actually simulates a battery pull and is very useful when things go a little wonky.

 

[xdrc45]

That's normal stock Android. It is indeed a soft reset that actually simulates a battery pull and is very useful when things go a little wonky.

I figured as much... It just seemed like it was really easy to perform now, than it did before. I've done it like 3 times now just opening the Power Menu.
Thinking about it now, I bet the problem may be my spigen slim armour case... I just switched back to using it from different one and the buttons are a pretty tight fit. I've captured a few bug reports also just pressing the power button and with out even pushing the volume button Lol. I guess it still needs to be broke in.

 

[Incakola]

I'm using DU_TBO_Gapps_04-11.zip.

And I suspect you aren't asking me whether the volume rocker changes volume (it does) . I think I remember some setting to get it to do something else, but i don't use it. Tell me exactly what to try and I'll test it.

Oh, I meant the feature where the volume rockers change the music track while the screen is off. Just dirty flashed with the du gapps and dailer is functional again

 

[Hook]

Oh, I meant the feature where the volume rockers change the music track while the screen is off. Just dirty flashed with the du gapps and dailer is functional again

Ah, no, that doesn't work.

 

[Incakola]

Also is it safe to update busybox to 1.22.1?

 

[Hook]

Also is it safe to update busybox to 1.22.1?

Someone else will have to answer that. I don't have Busybox. Never been entirely sure what it is for. Everything works fine without it.

 

[Rxpert83]

Someone else will have to answer that. I don't have Busybox. Never been entirely sure what it is for. Everything works fine without it.

It works because im pretty sure most Roms already have it baked in

 

[Hook]

It works because im pretty sure most Roms already have it baked in

Makes sense. When I first rooted, I know WUGs added it and I used to update it on stock ROM. But then, somewhere in there, going to Cataclysm and then DU, it disappeared and I never bothered to reinstall. I think I still have a backup in TB. As I said, I don't really know what it is for. ;-)

 

[xdrc45]

Also is it safe to update busybox to 1.22.1?

Yes it is safe to update your BusyBox to 1.22.1

Makes sense. When I first rooted, I know WUGs added it and I used to update it on stock ROM. But then, somewhere in there, going to Cataclysm and then DU, it disappeared and I never bothered to reinstall. I think I still have a backup in TB. As I said, I don't really know what it is for. ;-)

I'll try to make this short, easily understandable and hopefully not to boring lol.
BusyBox basically is a collection or library of powerful command-line tools in a single binary executable app, that can run Linux commands on your phone. A lot of Android apps that require root privileges use BusyBox from the command-line extensively. So Busybox gives this function of additional commands to your phone, which it normally doesn't have. Apps like Titanium Backup, Terminal Emulator and etc, require busybox to perform the functions of the said app. Without busybox installed your phone is much more limited in what it can do. Such as the ability to write data directly to partitions on your device.
Rxpert83 is correct... Many ROMs such as DU and like CM use BusyBox extensively and already have it pre-built into the ROM. If I remember correctly DU has BusyBox v1.21.1 JB pre-installed.