Does anyone know if it's possible to change the settings of the image viewer so that when you edit (and crop) an image, it does not also re-scale the image size.
For instance, I take a picture at 3264x1836.
I then crop (using the default image viewer (gallery)) a section covering approx 80% of the image and the image that gets saved is 702x367.
Unscaled this should have been something like 2800x1400 (or similar).
I want (and need) to be able to control this scaling myself. The reduction in size is so severe in the default editor is pretty much useless for me.
I tried several other photo editors, and they behaved in a similar way. The closest I've got is Resize-Lite - but even that one scales down to 720p settings.
Any ideas?
Just installed MIUI and having the same issue...
never had with cyanogen or sense...
any ideas?
I finally made my own Boot animation.
The original idea was made by others (BIOS boot up) I never did figure out where I got my first one (the Galaxy Nexus one)
I typed in every single letter in every single image of this boot anim except the grey letters at the bottom I added Volume Down and left it as it was.
I have an avatar live wallpaper. I got ahold of the author and he told me how to get the images out of it. I used those for the second portion.
I found some zebra wallpaper and recolored and scaled it for the background.
DEEP respect to people who make these things. its an insane amount of work having to do each and every frame individually. I think I have 9-10 hours into this total ! not counting photoshop research to make life easier with some semi automation with recorded shortcuts. and I HAD A TEMPLATE to work from !!
took me forever to figure out how to automate a copy paste to overlay the stripes under the text without it MOVING the "pasted" content (centering) during the paste operation (that is why each frame has that white square at the bottom
I am thinking of making another with an android icon instead of the avatar movie sequence where I "avatarize" the android robot
maybe
its 16mb so I am hosting it and linking here. does anyone know how to reduce png image size without killing quality?
Enjoy let me know what you think.
I am also attaching my SII Bios one with no avatar theming. the second half the android matrix thing I did not make I left that in from the template I used to make this one (the galaxy nexus bios boot anim) that is not my work.
the first half is all mine.
Here is the Avatarized one
http://www.mylittlemouse.com/other/bootanimation(Avatar).zip
Here is a Video of it booting up. The sound file is a Mixture and Edit of the Old School computer disk spin up I found on a youtube video from here on the forums (on another SII bios anim) that I clipped parts out of and merged with the windows boot sound.
http://www.youtube.com/watch?v=IZri21-NvdQ
if anyone knows who made that original (original to me at least) Google Nexus Bios boot anime let me know so I can credit them as the source for the idea for this.
Hi,I Just Made A Guide To Support My Other Thread On How To Create Bootanimations So It Is Easier For People To Understand And Grasp The Concept.
CONTENTS
The Basics
Inside the bootanimation.zip file
Featured Boot Animations
The Android boot animation is contained within a an uncompressed zip file called bootanimation.zip that can be found in the media folder of the system partition i.e. /system/media on the internal memory of the device. This single file contains all the information required to play the boot animation, and is loaded automatically when the device boots. Thus, customizing or changing the boot animation is simply the process of editing or replacing this file.
Inside The Bootanimation.Zip File
This section is for those interested in finding out how the Android boot animation works. If you just want to install one without bothering yourself about what’s in the file, feel free to move on to the next section, as this one will get a little technical. Though it should be easy and simple enough for anyone to grasp.
While the Android boot animation might appear to be in a video format during playback, it is in fact a little different. If you extract the contents of the bootanimation.zip file to your computer, you will see:
A desc.txt file
A part0 folder (Contains PNG images named in incremental numbers)
More part1, part2 etc. folders (May or may not be present)
As you can see, bootanimation.zip merely contains one text file and one or more folders with PNG images. The animation is played simply by displaying the images in a sequence, and the text file defines how they are to be played. In essence, first the PNG files in the part0 folder are displayed one after the other and afterwards, those in the part1 file – if it exists – are displayed, again one after the other, and so on. All of this is defined in the desc.txt file.
Let’s see how it works in a little detail by taking a closer look at the contents of the file.
The folders
These contain PNG images named in numbers, starting from something like 0000.jpg or 00001.jpg and proceeding with increments of 1. There has to be at least one folder, and there is no known upper limit to the number of folders.
The desc.txt file
This file defines how the images in the folder(s) are displayed during the boot animation, in the following format:
Width Height Frame-rate
p Loop Pause Folder1
p Loop Pause Folder2
An example of a desc.txt file is:
480 800 30
p 1 0 part0
p 0 0 part1
As you can see, in the first line, 480 and 800 define the width and height of the boot animation in pixels for this example. This must be the same as the screen resolution of your device for the boot animation to properly play in full screen. 30 is the frame rate in fps (frames per second) i.e. number of images to display per second.
The second and third lines have a same format, start with p, which stands for a part of the animation and end in part0 or part1, which denotes the folder in which the images for that part are present.
The number after ‘p’ defines how many times this part will loop (repeat playback) before switching to the next part (if present). Specifying 0 would make the part loop indefinitely till the phone has fully booted.
The next number is for the pause, and is expressed in the number of frames, which can be translated into time by dividing it by the frame rate. A pause of 15 for example, would mean pausing for the time it takes 15 frames to play and since the frame rate is 30 frames per second, 15 frames would take half a second.
Translating all of this in case of the above example, the boot animation will play at a resolution of 480 by 800 pixels, at a frame rate of 30 fps, starting with the contents of part0 folder and after playing them in one loop, switching to contents of part1 folder and playing them continuously till the device fully boots.
A note on resolution: Most high-end Android devices with large screens have a resolution of 480 x 800 pixels, and are referred to as HDPI. Some mid-range devices have a resolution of 320 x 480 pixels and are called MDPI. Lastly, the screen resolution of some low-end devices is 340 x 320 pixels and these are called LDPI, though these are either the really old Android phones or the cheapest Chinese models.
As a rule, a boot animation made for a lower resolution device will run fine on a high resolution one but it will be centered on the screen, with the extra screen space around it not being used. Using a high resolution boot animation on a low resolution device will result in the boot animation not fully displaying on the screen, with its outer parts being cut off due to being outside the screen’s bounds.
IF YOU WISH TO MAKE A BOOTANIMATION NOW THEN GO HERE AND FOLLOW MY GUIDE: http://forum.xda-developers.com/showthread.php?p=27059237#post27059237
unreserved
thanks
thanks for the info , ill try to make my bootanimation and ill post it here if it works lol, one small question, if i do something wrong in the .zip, can the phone get a brick?
edit..
hhmmm part1 folder doesnt show up, could you tell me why?
Tuner420 said:
thanks for the info , ill try to make my bootanimation and ill post it here if it works lol, one small question, if i do something wrong in the .zip, can the phone get a brick?
edit..
hhmmm part1 folder doesnt show up, could you tell me why?
Click to expand...
Click to collapse
No fn will not brick just a blck screen in startup dont worri ... keep up ur work
Sent from my GT-I9300 using xda app-developers app
Thanks for the guide
I am on stock lp7 rom but I have no boot animation.zip file in my media folder.
Instead I have bootSamsung. Qmg and bootSamsungloop. Qmg files?
Can I still make a boot animation?
Thanks for your help
nice guide..i'll try soon
I created a GIF using Photoshop CS2.
When I open the GIF using Internet Explorer, it looks great.
But when I use Boot Animation Factory to create the bootanimation.zip, it ends up looking very choppy and the text part of the GIF comes & goes. Looks terrible, lower resolution and not at all like my GIF. I've attached both the GIF and the animation I created. If anyone can fix it, or tell me how to fix it... I would really appreciate it. :good:
EDIT: I gave up on trying to create the GIF from a GIF. So I created the boot animation from individual slides in a part01 folder (after resizing to 720x1280 in Paint) and it worked great.
I was wondering if it was possible to change the boot logo (NOT the boot animation).
I managed to extract two identical files from my phone's oeminfo that seem to contain the boot logo.
However, I can't figure out the format.
The file has no header and is approximately the right size to be a 1080 x 1920 24bpp bitmap. So I wrote a little program to open it as if it was a 24bpp bitmap and convert it to PNG so I could get a look, and got some nonsense (I'd post it here but I can't because I'm a new user).
It was... clearly the right file but not quite the right format. I could see the Huawei logo but it had wavy horizontal distortions as if the number of bytes per line was variable, and many horizontal streaks on the Huawei flower where the brightness was correct but the hue was wrong. Oddly, the "Powered by Android" at the bottom of the image is pixel perfect, so I know at least that part is a normal 24bpp bitmap.
Any thoughts?