• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] BACKside ROM (CM7) + Green Machine Theme

I honestly don't know how to resize a boot animation, I'm sure someone does though, just a matter of time before someone answers.

oh and Jerry, another idea for a possible future feature, the ability to choose what the button on a headset (headphones with mic and 1 button) does. Such as what the long press does, such aas 'open custom application' rather than just having it open the music app. It would be nice to long press that button, and having it start the voice app. ;)
 
Some of those files are flashable zip files that contain the bootanimation.zip, so you have to extract it and then put it on your sdcard (there are unzippers available on the market to do this all on your phone). You'll know you have the right zip file when you open it and there are one to three folders named part0 part1 part3 and a description file.

The easiest way to resize all the images is with ImageMagick or Gimp. Both have batch convert methods, you just need to resize the images to 320x480 if they are larger alread (no need to resize if they are smaller, some are 256x256).

@nitestalkr: If I could remap voice, it would be mapped to the voice button already. ;)
 
That's why I suggested the 'custom application' option, that way you can choose whatever app for it to open, rather than having it open only the music app. And, since the voice command app must be installed via market, if you figure out what the voice buttons name is(ex. Button#7 or whatever the 'code name' is for it), couldn't you also make an option to select what long pressing that button does, and have its default be inactive? Such as choosing what long pressing each of the 4 face buttons do, can't you implement that same line of code for the side voice button, and the headphones mic button? Then again, I'm sure if it were that simple, it would have been done by now. :p

With the exception of you already posting on this; http://forums.androidcentral.com/op...hacks/96770-mod-remap-your-hardware-keys.html

In lame mans terms, couldn't you write a code to more or less do this, if key 216 pressed for x amount of time, ask what to do. Or, make an option in a menu reading, 'if voice key long pressed, choose action, custom application ' and then choose whatever application ?

And this is where I stop while I'm ahead. :p
 
I know its been answered before but I can't find it. How do I turn on my phone while its charging
 
That's why I suggested the 'custom application' option, that way you can choose whatever app for it to open, rather than having it open only the music app. And, since the voice command app must be installed via market, if you figure out what the voice buttons name is(ex. Button#7 or whatever the 'code name' is for it), couldn't you also make an option to select what long pressing that button does, and have its default be inactive? Such as choosing what long pressing each of the 4 face buttons do, can't you implement that same line of code for the side voice button, and the headphones mic button? Then again, I'm sure if it were that simple, it would have been done by now. :p

With the exception of you already posting on this; [MOD] Remap your hardware keys - Android Forums at AndroidCentral.com

In lame mans terms, couldn't you write a code to more or less do this, if key 216 pressed for x amount of time, ask what to do. Or, make an option in a menu reading, 'if voice key long pressed, choose action, custom application ' and then choose whatever application ?

And this is where I stop while I'm ahead. :p
The mechanical buttons are tied to the kernel via gpio, which has certain hooks hard coded. Unfortunately, we don't know all the hooks thanks to LG's wondeful source. You could probably achieve this, but it's not something all users would want, and it would be rather difficult at this time to create an option to do both. Both thekraven and I have been attempting to track down the appropriate keycodes and mappings to get Voice Activations working with the voice button, but any change to key mappings requires changes to 8 other files (plus finding the proper intent), any one of which can bork the build. So it's not as easy as it seems. ;)
 
The mechanical buttons are tied to the kernel via gpio, which has certain hooks hard coded. Unfortunately, we don't know all the hooks thanks to LG's wondeful source. You could probably achieve this, but it's not something all users would want, and it would be rather difficult at this time to create an option to do both. Both thekraven and I have been attempting to track down the appropriate keycodes and mappings to get Voice Activations working with the voice button, but any change to key mappings requires changes to 8 other files (plus finding the proper intent), any one of which can bork the build. So it's not as easy as it seems. ;)

i thought so, i sent you a pm regarding a possible fix that worked on the LG optimus S that i stumbled upon in some digging around that i did.
 
The problem is you selected the bootanimation folder and zipped it up, creating a zip with a bootanimation folder inside. Your zip should just have the part0 and desc.txt files. Let me know it this works for you:
 
alright, I checked it out with preview. it went to the prewiew screen, but it was all black. like there was no images. :/ so I figured it was a bug. set it and rebooted. it did the same thing. all black screen. odd. other than that, phone still works fine, in case the black screen comment mislead you at all :D

YOU'VE GOTTA BE KIDDING ME, wow haha common sense just kicked in. I was just roaming through the boot animation folders I downloaded from xda, and turns out I just didn't think to set the boot animation zip that was in that folder. woww, I feel really dumb. haha but I got it working. Jerry, you really are a cool guy for helpin me. thanks alot for takin your time and doing that. :)
 
Jerry, I flashed a theme I made with a different boot animation. Now I can't find your android flasher animation. Is it moved to another location or overwritten?

btw,

You can change it, and there are video tutorials for how, I'll try to find a link when I get home. Search for unpack boot image optimus v. ;)


You may want to hold off for a bit. Blarf just added PNG support to the bootlogo function. I'm going to pull the change in for my next build. ;)
https://github.com/inferiorhumanorg...mmit/10d08bdc705c86e9ad263f1b9db0dd2f90046f10

Blarf is still the man!


So can we use png's now?
 
Remember kids, flashing themes will overwrite the file "bootanimation.zip", so if you like the current one, rename it before flashing. That way you'll still have access to it.
 
I've been running into an issue the past couple of mornings after flashing the newest build where after charging my phone all night, I go to use it and it's only showing the background image and the notification bar. I'm not able to interact with the notification bar and none of the buttons on the phone do anything. If I hold the power button, all the home screen widgets and the launcher will show behind the "Phone Options" dialog, but when I tap the back button to get rid of the dialog, all the widgets and stuff from my home screen disappears again.

Anyone else run into this issue?
 
You can use PNGs now, but you will still have to unpack/repack the boot.img in order to make any changes. Being able to use PNGs mean we can make prettier first bootanimations, but also means more size taken up (prettier means more data). ;)
 
I've been running into an issue the past couple of mornings after flashing the newest build where after charging my phone all night, I go to use it and it's only showing the background image and the notification bar. I'm not able to interact with the notification bar and none of the buttons on the phone do anything. If I hold the power button, all the home screen widgets and the launcher will show behind the "Phone Options" dialog, but when I tap the back button to get rid of the dialog, all the widgets and stuff from my home screen disappears again.

Anyone else run into this issue?
Sounds like a bad flash. Did you verify the md5 checksum?
 
Jerry will you have a new build soon? One of several possibilities screwed up my phone last night and I'm having multiple FC's. I plan to wipe everything and start over.

If you might have a new build soon I'll hold off. If not, I'll just get it over with.
 
Back
Top Bottom