I have flashed these patches for ICS on my nook(at least I think I have). Is there a way to verify that they have been flashed?
Well, for the boot animation fix, does the boot animation fill the screen or is it cut off on top and bottom (in portrait)? If it is full screen, you're good.
Sent from my DROID BIONIC using Tapatalk
bootanimation etc patches
Thanks for reply. bootanimation does fill screen, so patches must have applied.
Related
Just a little curious...
I have a i9000m from Bell, and somewhere between applying some lag fixes, overclocking, a trying to get into recovery via buttons (fail, only adb works), my boot logo now changes from "GT-i9000m" to "GT-i9000" ("m" disappears) during boot. I assume that's from applying things that are made around a i9000? And also I have no more boot/off animation. Guessing both of these things are from doing Mimocan's lag fix? I since then undid his and changed to RyanZA's one click v1 (update.zip version), but it all remains.
Wondering if anybody out there has some wisdom to share
I'm not too too worried about these things, but Its kinda lame with no animation If anything, I would remove the startup sound, but only when I get my animation back.
My boot animation also doesnt show up anymore But you can hear the swoooosh sounds and so on...
not sure if this applies to your problem.
I had a similar issue after lag fix, noticed that playlogos1 and playlogosnow files were exactly the same. I got the original playlogos1 file from another galaxy and renamed to playlogosnow, then replaced the dodgy playlogosnow from my phone.... that fixed it for me. (files are located in \system\bin\)
The way I understand it, the lag fix renames the original startup animation from playlogos1 to playlogosnow, then copies a script called playlogos1 in its place which ensure the fix is applied after reboot, the script also calls the animation "playlogosnow".... in my case I screwed up and ran the lag fix twice, which resulted in both files being exactly the same and the original animation getting wiped.
Hope that makes sense.
The poster above me is spot on. Just flash more roms to fix it i guest
Sent from my GT-I9000 using Tapatalk
playlogos1 is the boot logo, the mount on boot script for lagfix renames the boot logo to playlogosnow.
Somewhere along the line one of the devs may have included a logo that is used instead of your stock one, specially when reverting. ( Prevents problems if you try reverting without actually doing the lag fix. )
Old thread bump
I have similar behavior to OP.
My boot screen shows GT-I9000M for a few seconds, then it turns to GT-I9000 before going to the animation (the M disappears).
I first noticed this about a week ago when i started using Doc's roms, currently I'm running Docs' JPA v7 with no lagfixes.
I'd like to get the correct boot screen back with the "M", is it just a matter of getting an original copy of a bell bootlogos1 file and dropping it into /system/bin (overwriting the current one)?
Doesnt OCLF have the option to restore boot animation\logo??
alferret said:
Doesnt OCLF have the option to restore boot animation\logo??
Click to expand...
Click to collapse
I'm not sure if OCLF had that option, ive only ever played with the lagfix options in Clockwork Manager. I don't see any options to restore boot ani/logos there.
First I flashed the new JK6 and then I flashed Eugenes latest kernel over this and it seems to run just fine except for now I have the standard samsung galaxy boot annimation but also flashing android logo on top of it. Anyone know whats going on there and how to get it back to only showing the Samsung animation? Im sure this is an easy fix so hopefully someone knows what is causing it.
I think that most custom roms support boot animation.zip try to put one of those in there if your using one click lag fix try to push the restore boot animation button see if that helps
Still flashing , thanks to odin & tw
the kernel is looking at a bootanimation file (there is no extension) while the other samsung stuff is booting the normal bootanimation files. you'll need to delete the
bootsamsung.qmg
bootsamsungloop.qmg
from your /system/media/ folder to get the dueling boot animations to stop.
geoffcorey said:
the kernel is looking at a bootanimation file (there is no extension) while the other samsung stuff is booting the normal bootanimation files. you'll need to delete the
bootsamsung.qmg
bootsamsungloop.qmg
from your /system/media/ folder to get the dueling boot animations to stop.
Click to expand...
Click to collapse
Ok this worked as far as not having 2 at once but is there a way to get the stock animation from the galaxy s? Right now I have the standard boring android logo. That means I would have to keep the bootsamsung.qmg right? If I could find android boot somewhere in the system maybe i could delete that instead? I thought it would be in system/media somewhere but its not.
Is there a bootanimation.zip of the stock galaxy s bootup? If not there should be.
since you flashed one of eugene's kernels, i think you've flashed the one that dosn't support .qmg booting, but only supports bootanimation.zip. so youre kinda sol.
Hi Everybody
Just wanted to share my boot animation. It's the autobot and decepticon logo from the movie transforming back and forth. Enjoy!
Edit: added the gif it's based on
looks very cool! thx for this one!
No problem, I might tweak it a little so that the emblems stay for a shorter amount of time.
Excuse my ignorance, but how do we install this? Simply flash via Clockwork?
It can be installed to a location that I can't remember via ABD for a permanent install or you can use Root Manager or Super Manager with R/W access to the root and drop the zip in /data/local. The second way will revert back to a different boot animation if you flash a new ROM.
Nice work goochj. Haven't seen you in a while. Def gonna try
This out. Hope your well. Esk0
Thanks esk02k! Yeah haven't been around much, just poke in once in a while. Been planning a wedding
Sent from my HTC Desire using XDA App
So I was messing around with changing the boot animation on my Droid X, ( i wanted to try the Bionic animation), then I switched to one I made myself, but it was too small, so I removed it. I put back the stock Droid X animation, but now whenever I boot it just has the Stock Android boot anim (the word "Android" with the sheen). Anyone know how I can get back to using custom anims or even the stock DX?
NVM just SBFed back to stock.
Ok, I'm still a noob when it comes to Android.
I have a rooted Sprint S4 on the OTA MJA update and TWRP Recovery 2.6.3.0.
I want to know how to get ROM Toolbox to perform the randomly selected boot animations I have downloaded from ROM Toolbox application itself.
What do I need to do get the random boot animations to work when the phone reboots because it is still showing the same Samsung/Sprint boot animations?
Cookbook instructions please.
TIA
I thought xda was supposed to be the place to go for help, even for noobs, guess I was wrong...not a single reply. :'(
mrrsquared1979 said:
I thought xda was supposed to be the place to go for help, even for noobs, guess I was wrong...not a single reply. :'(
Click to expand...
Click to collapse
XDA favors those who search. It's NOT a support/help site. Though most go out of their way to help those that help themselves.
Okay </preach>
So you can try starting here. This enabled me to use my cutom boot animation zips. One thing to make sure is that you have the right screen size on any images (1080 1920) you are planning on using for this device - wrong screen size can send you into a bootloop that requires a nandroid restore.
And here.
With the stock (Odexed) ROMs it is often more difficult to use custom boot animations they might not always work (or you'll have to delete the qmg files first)
leaderbuilder said:
XDA favors those who search. It's NOT a support/help site. Though most go out of their way to help those that help themselves.
Okay </preach>
So you can try starting here. This enabled me to use my cutom boot animation zips. One thing to make sure is that you have the right screen size on any images (1080 1920) you are planning on using for this device - wrong screen size can send you into a bootloop that requires a nandroid restore.
And here.
With the stock (Odexed) ROMs it is often more difficult to use custom boot animations they might not always work (or you'll have to delete the qmg files first)
Click to expand...
Click to collapse
Seems I am getting farther down the rabbit hole, now running TriForceROM 5.0 and that has proved to have an improved battery life.
mrrsquared1979 said:
Seems I am getting farther down the rabbit hole, now running TriForceROM 5.0 and that has proved to have an improved battery life.
Click to expand...
Click to collapse
You may need the ktoonsez kernel from the TF5.0 aroma. Then download the boot animation you want from your Rom Manager then install through your recovery, wipe cache and dalvik and fix permissions, reboot.
Haven't done this yet on TF5.0 but that's exactly how I did it on the last release. Went with the golden skull and bones. Not sure if you can get it to toss up a random one on each reboot though on the S4. Think RM was focused on a different set of phones altogether so maybe all the options in it won't play nice with the S4, just thinking out loud.
Or do what leaderbuilder said
I'm still trying to make my own, have to make time though. A lot of it.
Sent from my SPH-L720 using xda app-developers app
I seem to really like the one where the android is urinating on the Apple.