I created a boot animation, but the first stage, it was as if he was going to slow down, poets take a look? Thanks
Up
Sent from my GT-I9000 using Tapatalk
It Looks good.
That tends to happen sometimes with very large Bootanimations.
so I can not avoid the initial slowdown?
velenoso84 said:
so I can not avoid the initial slowdown?
Click to expand...
Click to collapse
If your images are larger than around 480x480 then you will get some slowdown as the files are buffered into ram. Maybe try testing a couple of different sizes until the slowdown is minimised... or start the animation "small" so you don't notice it so much, then by the time the action starts all the images will be in ram. Just an idea.
Also be sure to optimize the pngs with e.g. PNGOptimizer.
Hello, I tried searching around but couldn't find any similar problem.
I've created my own bootanimation.zip which can be downloaded here http://www.megaupload.com/?d=576GF823 Its Red Wings Related, showing the Center Ice at Joe Louis Arena, then an awesome goal by zetterberg, then loops center ice again. That all works great.
The problem I've run into is that the first time it plays any of the animations they are slow. and when I'm only playing the goal once it goes in slow mo, if i loop it, the 2nd time it plays fast as it should. Is there anyway to fix this? I originally was just doing the goal, then the center ice on loop. I tried putting 1 center ice first, hoping it would take the lag and allow the goal to play full speed, but it doesn't.
Any help is appreciated.
The first playback is slow because it has to load every frame into memory while simultaneously performing the boot process. After all frames are cached, there's no more fighting other processes for access to the system partition.
I'm not 100% on this, but I don't think you can do anything to pause the boot sequence for that first load of the animation.
HTC Vision (G2) - CM7 B62 w/AUS radio
Yeah, I just ran into this same issue making my own. :/
I wish there was a way to pre-cache the boot animation, if it ran full framerate then I'd actually get to see the whole clip when the phone boots.
Mine has no loop though, it's one continuous clip.
crater said:
Hello, I tried searching around but couldn't find any similar problem.
I've created my own bootanimation.zip which can be downloaded here Its Red Wings Related, showing the Center Ice at Joe Louis Arena, then an awesome goal by zetterberg, then loops center ice again. That all works great.
The problem I've run into is that the first time it plays any of the animations they are slow. and when I'm only playing the goal once it goes in slow mo, if i loop it, the 2nd time it plays fast as it should. Is there anyway to fix this? I originally was just doing the goal, then the center ice on loop. I tried putting 1 center ice first, hoping it would take the lag and allow the goal to play full speed, but it doesn't.
Any help is appreciated.
Click to expand...
Click to collapse
Not sure what application you used to make you're bootanimation, but I made mine in After Effects and this is what I did to fix the issue. When rendering I made the dimensions half of the actual screen dimensions (this ended up being 960x600 for my tf700t), then I set the frame rate to 10fps. I then modified the desc.txt file accordingly:
1920 1200 18
p 1 0 part0
p 0 0 part1
(don't copy/paste that, can't remember if you need spaces or not).
Basically I used smaller, less demanding files (and by modifying the export framerate, fewer of them) and then had the tablet just blow them up to fit the screen. No discernible loss in quality. Hopefully this helps someone out there.
Hi everyone
I'm in the process of making my own boot animation which I am sure you will all like
However, I am using LeeDroid's boot animation as a base and my soundtrack that goes along with the animation is twice as long as the LeeDroid one. Will it still all play when the phone turns on or will it stop after a certain point?
EDIT: Also, even after using PNGCrush on the frames I am still getting file sizes like 125Kb at the beginning. I read that they aren't really supposed to be over 35Kb. Any way I can reduce these file sizes?
Sorry I have so little to go on, I've done a lot of experimenting with ROMs in the last month and I lost track of my daily use ROM.
The main thing I can recall is the boot screen was of Lloyd the Android mascot -- it was just a still image but a 3D rendering of him, I believe.
Well, I think that was the right one...
There was also one with a green glowing sort of swirly star particle effect animation for the boot screen. That one may have been it, actually.
Hi guys !
Here is the thing. I used to change the resolution of my G3 (D855 - 16GB) on stock to 1080P, and it was amazing.
Since Marshmallow, there's a few problem if you do that. Let me explain :
I managed to lower the resolution of the rom with ADB to 1080p, everything was right, but the DPI was too big, obviously ! So i lowered it to 540, the limit of LG apps, and everything was fine, but the problem is, it's still too big. It's one of the problems of the G3 that i can't stand. The DPI is too big, even in stock 1440P. I tried different things, to lower the DPI under 540, and here is the results :
1 ) Lower the DPI of the rom under 540 : Force close on LG Apps
2) Lower the DPI of the rom under 540 and use App Settings to put all the LG Apps at 540 DPI, it somehow worked but there was a lot of incompatibilites that were not in Lollipop. That was what i used to do on my Lollipop Rom.
3) Leave the DPI to 540 but change all the daily used apps to a DPI under 540 : It worked too, but the System UI was still too big.
4) Same as 3, but change the DPI of SystemUI under 540 : It worked too, but everytime i call was received, i couldn't answer because of force closes.
So here's my question. Can someone help me to figure how to lower the DPI of SystemUI and getting the phone to still work ? Or share with me another method to do it, ideas that i can try, etc, i'm open to suggestions !
Thanks !
Actually, I used to go through the same steps as you described, on Lollipop. I got everything to work, with 1080p and dpi around 440 I believe. My experience was, that App Settings would pretty much fix any misbehaving app after the dpi change, including the call/message apps. The only thing that continued being weird was the default LG home screen, which still had blank, broken icons and widgets so I had to replace it with Nova Launcher, which worked like a charm. This was about half a year ago, and when I done it on my phone, I repeated the same process on my friend's G3 (same ROM, same process).
My G3 would work fine for a while, but eventually, at some point during the 3rd or 4th system restart, it would always get bricked, stuck on the LG logo while booting. Always had to restore my backup., try again, but to no avail.
My friend's G3, on the other hand worked just fine ever since, which I can't quite wrap my head around, since it's the same phone, with the same ROM and the same procedure.
So I would also like to know if it's possible to create a stable 1080p system with MM now. As to your call problem, does it force close even though you applied the fix to it in App Settings?
I also replaced my launcher by Nova Launcher, on stock or modified, i prefer Nova Launcher, a lot more options to customize it.
I'm actually using a modified 1080P Marhsmallow Rom, but it's not stock, it is on AICP (based on CM13 MM i think), and it is working fine, but it's not stock. The camera is not as good as stock.
I dont know why your phone had this problem though, i never had this on mine.
I'll try again the same steps that i described, on the fulmics marhsmallow rom, that is eventually coming in a few days.
For the phone force close problem, i tried multiple things, and it didn't work with a custom DPI set with app settings on the phone APP. That's why i tried to put the whole system at 540 DPI and my personal apps at 400. And as described in my first post, it worked good, but systemUI was too big.
Maybe i can try differents xposed modules to customize the SystemUI to make it smaller without modidyfing the DPI of the whole app?...
Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.
Lymnoreia said:
Bump... Is really no one interested by downgrading the resolution of the G3?... You should at least try, it is good for gaming and fluidity.
Click to expand...
Click to collapse
If you put "Game optimizer" setting ON, then all games are run in 1080p.
You can find it under "Battery & power saving" option.
Therefore, there is no reason to downscale resolution on Marshmallow
Same here. Just flashed Fulmics 3.1.... Set my DPI to 540 but still find the UI too big unlike when I was on Ti-x lollipop. I browse facebook regularly and the chatheads are way too big for a 540 DPI, heck, it's even smaller when I was on lollipop with the same DPI. It's kinda annoying considering how big the G3's screen is... big UI just waste space. I'm loving the new marshmallow rom but this one is really a nuisance.