Root [ROM][ALPHA][5.1.1] Dirty Unicorns 4/29/2015

[starkraving]

Maybe that's not what's causing reboots, I've only noticed random reboots with screen off and charger connected. What log do I need to grab for play store force closes?

I updated to B07 via Spock's fully stock ROM if that could possibly cause conflicts.

Play force closes could be something as simple as the gapps package your using.
I recommend these, smaller than standard but fix some force close issues as well as any sync issues.
https://www.androidfilehost.com/?fid=23991606952599848

I see a lot of permission issues still...
Try this from terminal...
su
fix_permissions

If you get this error...
"cat: can't open '/data/system/packages.xml': No such file or directory"

That means there's no symlink...

As far as the reboot on sleep while charging I see you're using kernel auditor, what's your settings?(I'd advise running the ROM with the stock kernel settings and see if you have the same issues.) Also as point of curiosity does this ROM have offline charging fixed?
Let me know what happens.

**Edit**
I was doing some reading and if SELinux is enforcing and permissions are wrong there could be some issues. Do you guys have the option to toggle between Enforcing and Permissive? Just brainstorming lol.

 

[DsyMnapTic]

I am using the GApps package you provided specifically for their size. I'm also on the 5/02 version of phenoms release of this ROM

This is what I got in terminal emulator:
u0_a75@android:/ $ su
root@android:/ # fix_permissions
tmp-mksh: fix_permissions: not found
127|root@android:/ #

I am using kernel audiutor. My settings are:
486min
1728max
Interactive governor
I/O: fiops, 1920kb read ahead for internal
I/O: noop 1024kb read ahead for external
....I haven't changed anything else in that app

Also, I don't believe offline charging is fixed in this one, though I have yet to check.

 

[starkraving]

I am using the GApps package you provided specifically for their size. I'm also on the 5/02 version of phenoms release of this ROM

This is what I got in terminal emulator:
u0_a75@android:/ $ su
root@android:/ # fix_permissions
tmp-mksh: fix_permissions: not found
127|root@android:/ #

I am using kernel audiutor. My settings are:
486min
1728max
Interactive governor
I/O: fiops, 1920kb read ahead for internal
I/O: noop 1024kb read ahead for external
....I haven't changed anything else in that app

Also, I don't believe offline charging is fixed in this one, though I have yet to check.

Yeah its not included in bin now...which I guess makes sense with the SELinux issues that could happen. I'll keep digging through your logs...Nobody else seems to be chiming in with the same problem. So the answers in the log somewhere lol.

 

[roadkill42]

Yeah its not included in bin now...which I guess makes sense with the SELinux issues that could happen. I'll keep digging through your logs...Nobody else seems to be chiming in with the same problem. So the answers in the log somewhere lol.

The off line charging still not working I did what u said formated internal SD and all the other wipes I had no ishues yet over 13 hours running

 

[starkraving]

The off line charging still not working I did what u said formated internal SD and all the other wipes I had no ishues yet over 13 hours running

Interesting, what build are you running?

 

[roadkill42]

Interesting, what build are you running?

The second build and gapps u provided

 

[devilschild26]

The second build and gapps u provided

U on cm 12.1 5.1

 

[DsyMnapTic]

The off line charging still not working I did what u said formated internal SD and all the other wipes I had no ishues yet over 13 hours running

@roadkill42
This should not have anything to do with OFFLINE charging, I feel like you're getting my recent conversation about having problems with SCREEN OFF charging mixed up with a remedy to "treat" the OFFLINE charging problems. Offline needs to be fixed by the devs in the source code somewhere, you can't simply wipe things to get it working. Starkraving was just troubleshooting permission issues I was having. So I do believe offline charging is still nonoperational in any build that is currently available. Screen-off charging is a different issue.

 

[DsyMnapTic]

**Edit**
I was doing some reading and if SELinux is enforcing and permissions are wrong there could be some issues. Do you guys have the option to toggle between Enforcing and Permissive? Just brainstorming lol.

@starkraving
I've tried in the only basic way I would know how and I am unable to toggle from enforcing to permissive. Is it possible you could change it in the build prop or through terminal somehow?

... I've noticed it differs from ROM to ROM, some are enforcing and others are permissive.

 

[devilschild26]

@starkraving
I've tried in the only basic way I would know how and I am unable to toggle from enforcing to permissive. Is it possible you could change it in the build prop or through terminal somehow?

Thought SEL was set permissive

 

[roadkill42]

@roadkill42
This should not have anything to do with OFFLINE charging, I feel like you're getting my recent conversation about having problems with SCREEN OFF charging mixed up with a remedy to "treat" the OFFLINE charging problems. Offline needs to be fixed by the devs in the source code somewhere, you can't simply wipe things to get it working. Starkraving was just troubleshooting permission issues I was having. So I do believe offline charging is still nonoperational in any build that is currently available. Screen-off charging is a different issue.

I was saying what I did and no issues and answering question about off line charging not working and I'm on second build of dirty unicorn

 

[roadkill42]

U on cm 12.1 5.1

Dirty unicorn

 

[devilschild26]

I was saying what I did and no issues and answering question about off line charging not working and I'm on second build of dirty unicorn

So ur on the one that rils crash cause that's the second build

 

[DsyMnapTic]

Thought SEL was set permissive

It is in this ROM

I was saying what I did and no issues and answering question about off line charging not working and I'm on second build of dirty unicorn

Gotcha, it was just the way you typed it that confused me.
So are you having reboots while charging with your screen off too?

 

[roadkill42]

So ur on the one that rils crash cause that's the second build

I had no crashed at all now since I formatted internal SD card I did it last night around 1130pm Eastern time till now haven't had problem yet

 

[devilschild26]

It is in this ROM



Gotcha, it was just the way you typed it that confused me.
So are you having reboots while charging with your screen off too?

Enforcing is only on kitkats

 

[roadkill42]

It is in this ROM



Gotcha, it was just the way you typed it that confused me.
So are you having reboots while charging with your screen off too?

Not on this build my wife is she is still on first build I got the log just haven't had time to post she is always on the phone

 

[roadkill42]

Enforcing is only on kitkats

So what's the difference with enforcing versus permisv?

 

[DsyMnapTic]

So ur on the one that rils crash cause that's the second build

Edit*
Actually, what is the build date on the 4/29 build for those of you running it? Or the original 4/28 CM 12.1?

 

[starkraving]

I'd do a complete new fresh install with no kernel tweaks, no restoration from any backup source(if you have...saw a lot of TiB errors in your logcat) and just restore apps from play store or SD card if they're downloaded apks... There's definitely something squirrely with your permissions but I'm not even sure if that's what's causing the reboot. Hopefully if enough people look at these issues we can figure out if its ROM or user related.

 

[DsyMnapTic]

Do the titanium back up permission issues have anything to do with super user? I always get the "blah blah blah*mount namespace could cause issues*blah blah" message. Lol

 

[DsyMnapTic]

Well here's an app (links to xda) that changes your SELinux mode.
However after some reading, I'm under the impression that it's good that we're running permissive on this ROM, because enforcing employs extra security in the system and only allows for root privileges to run limitedly.
www.gammerson.com/2015/04/how-to-change-lollipops-to-selinux-to.html?m=1

 

[DsyMnapTic]

I'd do a complete new fresh install with no kernel tweaks, no restoration from any backup source(if you have...saw a lot of TiB errors in your logcat) and just restore apps from play store or SD card if they're downloaded apks... There's definitely something squirrely with your permissions but I'm not even sure if that's what's causing the reboot. Hopefully if enough people look at these issues we can figure out if its ROM or user related.

I'll get back to you when I get the time to do this

 

[roadkill42]

How this

 

[DsyMnapTic]

Here you go, fully and completely cleanly reflashed with a wipe of everything including internal SD (data media) .... Still got the reboot during screen-off charging, no user apps installed except syslog to grab the logs. The reboot doesn't seem random however as it usually occurs after the same amount of time every time.