[Moto G Themes and Apps] xpmule:
The work on the Moto E variants from Motorola's graphics dept is horrendous joke.. and that is coming from myself a pure amateur.

When i looked at my moto E 2015's graphics for the bootloader i was appalled at how sloppy a job they did.

The text in the bootloader was badly misaligned for example.

I noticed tons of other problems as well as.. poorly optimized graphics.

So i have a problem with guy saying earlier his little picture is 16mb large because of a gradient.. that i silly.

And yes INPUT does in fact matter big time.

I don't care if it is encoded after the fact or not.. doesn't change anything.

50% of this topic *SHOULD* be about image optimization.

Problem is most of you don't seem to know anything about it at all.

..you seem to just grab what ever and jam it in then cross your fingers. LOL

It's insane to think you "NEED" 16mb for a simple boot logo.

If you do i think you are doing something wrong.. optimize it and stay under the limit.

Like seriously people a simple Google logo with a black background should NEVER be 16mb or something.

And more about Moto's sloppiness.

I rebuilt their boot-animations and noticed they did a horrible job optimizing those too.

They really don't put much concern into file sizes with things.

I could go on and on.. some of the images on the Moto E's bootlogo.bin's are never used for example.

The features in the menu were removed years ago but the images are still in there wasting space.

Fixing their sloppy work is tiring..

I took apart their Marshmallow Boot animation for the Moto E 2015 frame by frame and converted the background on 300 images one by one with a black background then rebuilt the animation video file and mine had a better quality with far better visual quality (encode settings) with a smaller size and.. i also fixed the timing too.

They really are horrible and sloppy at this type of stuff.

I was expecting professionalism which wasn't there.

Guy earlier said Moto's picture was large.. point is ...... it shouldn't have been in the first place !

So yeah guys..

This is about finding random pictures and jamming them into your phone.

EDIT: which is a good thing :)

So.. half the matter is preparing and optimizing the picture you got.

I gave you all a great tip too.. PNG's (editable vs not)

They are notorious space wasters.. then you get into stuff like JPEG encode settings.

I have setup my own profile for that stuff on Fireworks over a decade ago.

Either learn about that stuff or find another picture.

The reality is there is no good reason a simple static picture of a Google logo etc should be 16mb.

That is simply insane and shows how little Moto cares when they put stock images on your phone that huge.

Larger crap will take longer to load on the phone.. not professional at all.

EDIT:

By the way to continue arguing with guy earlier ;)

I seen the exact source code for image input in this program.

It *READS* the bytes for the size then compares them to a list of max sizes based on the listed phone model number.. then allows you to continue or rejects your image.

So.. encoding afterwards is irrelevant.

If you input your image into the program and it is too large it would never get to the encoding stage anyway.

So that guy earlier doesn't know what he is talking about.

I suggest grabbing the source code to this program and reading it ....like i did ;)

Thanks again to the original dev of this program.

He did a lot of great work to let us have this cool program.

I appreciate his efforts and his willingness to share it with us all.