Lose the SAMSUNG splash screen?

[mwshows]

That's a weird interaction. Anyway, what counts is you put things right and, I suspect, had a reminder about getting permissions right. [/smile]

I have switched to using FX File explorer for damn near every operation I need to perform root wise.

Aside from just being a great app...

It will automatically assign permissions based on where the file is located or placed.

Meaning I've no longer had to worry about getting permissions right in any folder.

If you want to try it out, don't forget to also grab the root add on app.... And the Kit Kat SD card fix app.

Sent From The Darkside of My N3

 

[kprice8]

This was [music] Easy like Sunday Morning, yeahhhhhhhhh[/music]

 

[RBEmerson]

I have switched to using FX File explorer for damn near every operation I need to perform root wise.

Aside from just being a great app...

It will automatically assign permissions based on where the file is located or placed.

Meaning I've no longer had to worry about getting permissions right in any folder.

If you want to try it out, don't forget to also grab the root add on app.... And the Kit Kat SD card fix app.

Sent From The Darkside of My N3

WTDT. ES Explorer, by comparison, seemed clunky and uncooperative.

 

[RBEmerson]

Well, this doesn't work.

First I downloaded the animation I wanted from the thread. I went to system\media and located the files I would be replacing. I copied them over to my sd card. I then replaced them with the ones from the zip file in system\media. Rebooted the phone. No boot animation. And now my power button no longer turns off the screen and my brightness defaults to the lowest setting. I quickly replaced the original files, but it did not change anything.

I thought about this problem a little more. I'm left wondering if getting the permissions wrong caused the startup process to end prematurely or at least reach a state where the support for the power button and some other things (e.g., screen brightness) wasn't installed. That's just a guess, but a slightly educated guess. I've messed with Linux systems (mainly openSUSE) and see startups do silly things on occasion. I can see a botched splash screen attempt causing problems. It's not the splash screen files, per se, that do it, but their failure to run. I think. Maybe. Not?

 

[PuffJr2]

I thought about this problem a little more. I'm left wondering if getting the permissions wrong caused the startup process to end prematurely or at least reach a state where the support for the power button and some other things (e.g., screen brightness) wasn't installed. That's just a guess, but a slightly educated guess. I've messed with Linux systems (mainly openSUSE) and see startups do silly things on occasion. I can see a botched splash screen attempt causing problems. It's not the splash screen files, per se, that do it, but their failure to run. I think. Maybe. Not?

I don't belive it would cause any issues like that, since it's just images usually.
The system boots at its own pace, and the boot process is not governed by the boot animation.

 

[RBEmerson]

IIRC, getting the permissions on the .qrm files wrong stopped the power switch and dimmed the screen. Correcting the permissions fixed the problem. Either the permission error broke startup or running with bad permissions somehow smoked brightness and the power switch. I can't imagine a link between files that have bad permissions (and therefore probably won't execute) and a non-op switch and dim display. Occam's Razor favors the broken startup. At least that's my guess. [/smile]