Database Develop

Teeter Game

Hi,
this game is quality...
I've finished the 32 levels of this game and i want MORE
Is it possible to add new levels to this game??
Are there any better sensor games out there?
Raf

No there are currently no gyro-driven games, but wait a few months-:
Steering a car, flying a plane all with Gsen support , like a mini-WII
Why not taking the advantage , now that you created a thread anyway, to post some scores , just for fun
Rule: Post your score after finishing your FIRST TIME finalized 32 levels.
I got a 21 min 35 sec with +18 attempts in total from which 7 were on a same level

unfortunately i didnt make a note of my score after completion and upgraded to a new ROM....

rafter_01 said:
Hi,
this game is quality...
I've finished the 32 levels of this game and i want MORE
Is it possible to add new levels to this game??
Are there any better sensor games out there?
Raf
Click to expand...
Click to collapse
I don't know if you can add levels, but you can edit (and than distibute) them.
The levels are described in files 1.txt - 32.txt in de windows folder.
You can edit these (e.g. with Total Commander) to edit the levels.
The syntax is straight forward:
"B" with two params determines begin position.
"E" with two params determines end position.
"W" with four params determines walls.
"H" with two params determines holes.
See attached file for a new level (replacing the old 1st level)
Just replace the file in the windows folder (after making a backup of the original of coarse)

coolio
thanks for that

more games
i am not sure about this:
while cooking my ROM i discovered these files belonging the teeter:
\windows\1.txt, 2.txt, 3.txt, etc.
i think these are the chellenges. simple txt files
i think we could examine them and make new challenges.

Patrickw_mdav said:
I don't know if you can add levels, but you can edit (and than distibute) them.
The levels are described in files 1.txt - 32.txt in de windows folder.
You can edit these (e.g. with Total Commander) to edit the levels.
The syntax is straight forward:
"B" with two params determines begin position.
"E" with two params determines end position.
"W" with four params determines walls.
"H" with two params determines holes.
See attached file for a new level (replacing the old 1st level)
Just replace the file in the windows folder (after making a backup of the original of coarse)
Click to expand...
Click to collapse
faster than flash

ykat said:
faster than flash
Click to expand...
Click to collapse
Looser makes a new level
I'm waiting

Like the idea, but how do you replce the .txt file, as they're protected, and you can't edit the propeties.

How about adding a 33.txt, anybody know if that adds another level?

bobajob14 said:
Like the idea, but how do you replce the .txt file, as they're protected, and you can't edit the propeties.
Click to expand...
Click to collapse
Did you try edit the properties in Total Commander ?
I'm not sure wether I changed them or not. But I was able to replace the file, and play this new level.

Yes - but whenever I change the attributes, it doesn't save and just reverts back to "read only".

bobajob14 said:
Yes - but whenever I change the attributes, it doesn't save and just reverts back to "read only".
Click to expand...
Click to collapse
mmh.. stange behaviour. In Total Command, you can File->Edit these files and save changes.
Maybe afterwards, you can make changes, at least I can.

Great - I was opening, editing, then saving, which doesn't work.
Going File, edit, save works a treat.
Nice level by the way!

glacieruk said:
How about adding a 33.txt, anybody know if that adds another level?
Click to expand...
Click to collapse
I can confirm that just adding a 33.txt file to the windows directory does NOT add a 33rd level.

Can't see any point in adding more levels when you can alter the levels anyway.
It reminds me of changing the levels on jet Set Willy!!!!

So what are the setting for the later levels? With the uneven floors?
Can we perhaps have 2 instances of teeter
put it in its own folder, /teeter2/ or whatever, copy all the files across from the orginal version.
Then, edit the original files, so we have an all new version of the teeter game.
If someone can group all the needed files, graphics, txt files etc, il work on editing all 32 levels and producing a new version.

dzign-it said:
So what are the setting for the later levels? With the uneven floors?
Click to expand...
Click to collapse
Including a line with :
Code:
D 0
Does the trick..

Has anyone got any further with this?
In the mean time I have found a way to have another 32 levels with editing anything.
Lye on your back and hold your diamond above you, screen towards you (of course).
Then try the 32 levels again. It is very difficult.
Pete

best thing would be to make a level-editor for the game
just drag the holes and walls and press export

Noob needs help....

I found this website: http://www.androidonhtc.com
and i can't remember how. Has anyone tried this yet or is everyone using the stimulator that's available on xda?!
Ugh... so I installed it, figured that the default.txt was configured wrong. fixed what I needed and I keep loading it hoping it will work.
It gets stuck at the "HTC/HERO" page and I'm getting annoyed by the little green perp that keeps popping up with the "hero" words.
If you've tried this and gotten it to work, can you PLEASE help me?! Haha I'm so lost and it's a "stock ATT Tilt. The only thing I've installed other than this Android thing is the speed up keyboard thing.
Here is the info I can give you:
I have no idea what rom I'm running. =( I haven't done anything to it like i said above.
The phone IS unlocked, so I'm running on the Tmobile carrier
I have no idea what radio is either. so therefore..... like i said, i'm a total noob!
Right, please help?

You need to change your default.txt (or startup.txt) to look like this:
Code:
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htckaiser.panel_type=2 ppp.apn=internet ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=320 mddi.height=480 lcd.density=160 no_console_suspend board-kaiser-keypad.atttilt=1"
boot
The mddi.width, mddi.height, and LCD.density parameters are probably where your default.txt (or startup.txt) went wrong, so ensure those are set to the values I've provided above.
And since you're new, I would recommend reading the Kaiser and Tilt wiki articles to better understand your device, and to answer common questions you might have.

What bothers me is that i'm seeing so many different "results" with my search. one says,
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"
set cmdline "pm.sleep_mode=4 board-htcvogue.panel_type=0 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend"
boot
Click to expand...
Click to collapse
which is completely different from what you're showing me.
with your config, i can see the right side of the android, but the HTC/HERO thing is still in the way
when i change the values of the height and width to the kaiser specs on the andoirdonhtc.com page, i can't see it at all...

The reason for the different default.txt files floating around is because the necessary parameters may differ between android versions, sources, etc. For example, the reason you need to set the screen resolution to 320x480 in default.txt is because the Hero image was designed to run on a 320x480 screen. So a default.txt made for another distribution may not work with a different distribution without tweaking. The defaut.txt you just posted looks to be from another distribution, one that appears to be incompatible.
And when you say:
with your config, i can see the right side of the android, but the HTC/HERO thing is still in the way
Click to expand...
Click to collapse
What do you mean exactly? Do you mean that you do not progress past the black splash screen which displays "Hero" and "HTC" interchangably, even when using my default.txt? I don't quite follow
EDIT: If you haven't already, try deleting the "Media" folder off your SD card, deleting data.img, and running an error check on the card from a desktop machine (From Windows Explorer, right click on the card, choose properties, then the tools tab, then error checking). After doing that, put my configuration file that is posted above on your card, and name it startup.txt. Also, ensure that you're using the correct basefiles for your version of Kaiser-Hero if they weren't included in the same package (unlikely but possible).

DaveTheTytnIIGuy said:
And when you say: What do you mean exactly? Do you mean that you do not progress past the black splash screen which displays "Hero" and "HTC" interchangably, even when using my default.txt? I don't quite follow
Click to expand...
Click to collapse
Yes... at one point, with your configuration, i was able to see PART of the Android screen (I saw the time clock, battery life, and I think my reception bars....) but the hero/HTC signs were blocking the rest of the screen! I'll try again and do as you've instructed. I'll get back to you. Thanks Dave for being patient haha
edit: now..... i've done everything you've said... and it's been stuck on the splash screen with the "hero" and "HTC" interchanging.... for about.....10 minutes...
How long is it supposed to sit...?! (May I mention, I haven't touched any keys, am I supposed to?)
boot try #2: alright so we'll try this again... haha...... it's stuck on the splash screen, minus the splashing. the HTC just remains on the screen. When I hit the "end call" button, the screen goes black, as if to put the phone on lock. It wakes back up when I hit the same button again...
boot try #3: i left it there, and i actually forgot about it while I was packing so when I was cehcking to see if there were any messages recieved.... I noticed it said HTC. I can see.... half of the screen? but the HTC splash is still on the remaining half...
Any clue why it keeps doing this?

That's very strange.
Try this:
Delete all the files related to Android. This includes default.txt, data.img, initrd.gz, system.sqsh (if there is one), zImage, data.gz (if there is one), HaRET.exe, calibration (if it exists), the "Media" Folder, etc.
After completing that, download, unzip, and place this Hero build on your SD. It includes basefiles and everything else that's needed. Supposedly it's faster and more stable, but I can't test that since I use a Touch Pro2 instead of a Tilt now.
Boot it
Hopefully the problem will be solved by starting from scratch with a newer version.
And FYI: It's competely normal for the first boot to take a while. Just leave it alone for ~5-10 minutes and it will usually finish.

Ok, so I got it to work but it's slow and I'm having a hard time adjusting to the buttons and what not. Thanks a bunch dave! I really really appreciate the help!!!

No problem, I'm always happy to help

Custom Boot Animation

How exactly do I do this? I've googled it a few times. and I've seen tons of video's of different peoples boot animations.
I also checked CM6.0's new boot animation. (really cool) and it has 111 files or something in the zip.
I have a little like 6 second GIF that I'd like to use as my boot animation. would I just need to put the same file in there multiple times so it's long enough to keep going the entire time the phone boots? or does it have to be a PNG?
Any help would be great. Thanks!

xguntherc said:
How exactly do I do this? I've googled it a few times. and I've seen tons of video's of different peoples boot animations.
I also checked CM6.0's new boot animation. (really cool) and it has 111 files or something in the zip.
I have a little like 6 second GIF that I'd like to use as my boot animation. would I just need to put the same file in there multiple times so it's long enough to keep going the entire time the phone boots? or does it have to be a PNG?
Any help would be great. Thanks!
Click to expand...
Click to collapse
The boot animation must be constructed out of PNG images. You would have to pull every frame out of that gif and convert it to PNG.
The bootanimation generally consists of a series of number PNG images (0001.png, 0002.png, 0003.png ...) in two folders, "part0" and "part1". part0 contains any portion of the boot animation that does not loop, and part1 will contain the loop that will be played over and over until the phone finally boots. You then also need a "desc.txt" file outside of those two directories, which will contain information on the image sizes and which order to play the folders in. This all then gets packaged up into a "bootanimation.zip" file, which will be placed in /system/media/ or /data/local/ on your android phone.
Best way to figure it out is to take an existing bootanimation.zip (you can adb pull the default from /system/media/bootanimation.zip) and pull it apart to see how it's built.

Yea, Thanks for the info. Thats exactly what I did, sort of. I pulled Cyan's new bootanimation with the Cyan Droid skating inside the N1's boot logo.. I unpacked that and looked at how it was built. I replaced all the part 1 with multiples of what I want, but not frame by frame. lol. obviously it wouldn't work cuz it wasn't done right.
Does it need to be sized correct also? like if to large will it not show at all?
Everyone likes Jessica Alba right? I mean how can you not!
Here's what I was thinking of using for a boot animation. I'll let everyone see it, maybe someone will come up with something cool. I'm sure I have better ones, this is just the sexy Jessica Alba. It was the first thing that came to mind.

How about this one I attached? It is just the clip playing in the middle of the screen.
Flash it through recovery or take out the bootamination.zip and adb push it.
You can't put a .gif in the folder you have to pull all the frames.
When you create the zip-file with the folder(s) and the desc.txt you should use "add to archive", select .zip format (obviously :b ) and as compression method select "store". (Not 100% sure about if it's called "add to archive" and "store" cause I use Swedish language in Windows :b )
The desc.txt file in this case contains the following:
Code:
480 260 14
p 0 0 part0
480 260 is how big you want the picture to be (480 is suitable in this case since that's the width of the screen and 260 to get the correct ratio.)
14 is the frames per second. (don't know if it's possible to use a decimale, haven't bothered to try)
part0 is the folder and I guess 0 0 mean that it should keep repeating.
For example if having two folders and you want the fist one to play once and the other to keep repeating until the boot is done it should look something like this:
Code:
480 480 30
p 1 0 part0
p 0 0 part1
Hope that helped a little.

oh wow, Thanks. is that fullscreen? Lets give it a try.
whats the steps for flashing it in recovery. Just put on root of SD and flash in Amon's or is there more to it? I've never changed my boot animation.
Can't I just move it with root explorer to data/local? and reboot

No it's not full screen, then you'd have to hold the phone on the side. The animation takes up about 1/3 of the screen and is placed in the middle.
Yeah, just boot up the recovery menu and there's an option to flash zip-files that's on the root of you SD.
It should work to move it with Root explorer too. But remember if you use Root explorer you first have to open up the zip-file I've attached an take out the bootanimation.zip inside. It's that file you will put in the folder with Root explorer.
Edit: The update.zip I made will replace the original boot animation in /system/media/
So if you want to keep the original you better take a backup or as you said, place it in /data/local/ with Root explorer or: adb push bootanimation.zip /local/data/

xguntherc said:
Yea, Thanks for the info. Thats exactly what I did, sort of. I pulled Cyan's new bootanimation with the Cyan Droid skating inside the N1's boot logo.. I unpacked that and looked at how it was built. I replaced all the part 1 with multiples of what I want, but not frame by frame. lol. obviously it wouldn't work cuz it wasn't done right.
Does it need to be sized correct also? like if to large will it not show at all?
Everyone likes Jessica Alba right? I mean how can you not!
Here's what I was thinking of using for a boot animation. I'll let everyone see it, maybe someone will come up with something cool. I'm sure I have better ones, this is just the sexy Jessica Alba. It was the first thing that came to mind.
Click to expand...
Click to collapse
lol! I flashed that exact animation as my live wallpaper on to my Eclipse head unit in my car a while ago. Never gets old
And to do so I had to convert each frame that I wanted as well.

I know, she's so bangin. I wish it was a longer clip. lol.
Thanks. I'll try it tomorrow

what if we wanted to add a sound clip to the bootanimation on the Nexus One? what folder do we add that in? I have tried just about every folder and way with no luck.

Take a look at this:
oc3rulz said:
what if we wanted to add a sound clip to the bootanimation on the Nexus One? what folder do we add that in? I have tried just about every folder and way with no luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=710204

everythingisround said:
http://forum.xda-developers.com/showthread.php?t=710204
Click to expand...
Click to collapse
I tried that, I have added the audio file to just about every folder on the phone and nothing. I even changed the .mp3 to .ogg Nothing has worked so far, not even adding the file to system/media/audio

[Q] initlogo.rle format

Following instructions from here I pulled the boot ramdisk (uRamdisk) off the first partition of the internal mmc of my NC and unpacked it.
Inside I found initlogo.rle. This is a bootsplash that appears before the boot animation.
I want to see what this is an image of. There seems to be two screens before the boot animation and I was wondering which one this is. (I'm guessing the grey 'n', but I want to confirm that.)
I found this thread on creating a new initlogo.rle and this thread on converting initlogo.rle to png. I went through the steps and the end result was a garbage image file. I double-checked that my process was correct by running it on the user-created initlogo.rle in this thread and it worked perfectly.
My question is does anyone have any idea or perhaps could point me in a direction about what format the initlogo.rle that comes with the NC could possibly be?
If I hexdump the user-created initlogo.rle it's very obviously an rle as hexdump displays data in 2-byte columns. The first and every other column after is usually a small number (the count) while the second and every other after is some larger value (the RGB value). If I hexdump the NC's initlogo.rle it's obviously not in the same format.
There's no obvious header in the file (which is how this type of RLE should be) so I'm assuming it hasn't been compressed with something like gzip and the first four bytes look correct; 0xffff 0x0000, meaning 65535 black pixels which is what you'd expect for an image with a black background.
I know this is an incredibly insignificant issue, but it's nagging me.
Thanks for any help.

I don't have a NC and this is likely a really oversimplified / stupid thought. However, I'll throw it out there anyway. Since Windows BMP are often RLE encoded, what happens to the file if you rename it BMP and then try to open with an image viewer?

epakrat75 said:
I don't have a NC and this is likely a really oversimplified / stupid thought. However, I'll throw it out there anyway. Since Windows BMP are often RLE encoded, what happens to the file if you rename it BMP and then try to open with an image viewer?
Click to expand...
Click to collapse
It doesn't work.
Whether I open it up in MS Paint or Gimp the file is reported as corrupted or broken. The reason probably being the lack of a proper BMP header in the file. Also my understanding is there are different flavors of RLE and the BMP header, in part, defines what flavor of RLE it is.
And you might then think that maybe the NC's initlogo.rle is a different flavor RLE as well. The problem there is there's no header on these files, so whatever application is decoding the image to then display it must assume what format the file is in.
Maybe there's a command somewhere in init.rc or elsewhere that passes some kind of parameter to define what type of format the initlogo.rle is. I'll have to go digging.

Did some investigating as I'm trying to add a boot logo to CM7 for the Nook Color.
The stock initlogo.rle is 600x1024, with the format:
Short, little endian: number of pixels with the following color
Byte: red value, 0-255
Byte: green value, 0-255
Byte: blue value, 0-255
(repeats until end of file)
Pixels are filled starting at the top right, moving by columns down and to the left. The resulting image is attached.

[Q] Need Help with Boot Animation

Hi, I need help with a boot animation I am making. I followed all the instructions for it and its still not working. I just get a black screen during boot where the animation was supposed to happen.
This is for my Nexus 1 btw running CM 6.1.1. the boot animation is basically a siege tank from Starcraft 2 setting up and then packing up again.
I placed the zip in /system/media
Each png is 180x135.
Can someone please look at the zip and see what I am doing wrong? it would REAAAAAALLY help.

More than likely your missing an empty line at the end of your desc.txt, common problem.

Added extra line , didn't work
I added the extra line at the end of desc.txt and its still the same result. Ugh.... I have uploaded the new revised zip.

One problem that i had run into is that i was not zipping them in the least compressed format. make sure that you use fast(minimal) compression.

Compression
Yeah, I tried it both ways with WinRar and 7-Zip and made sure it was set to "Store" as the minimal to no compression option.

Here is my suggestion. This is the desc.txt file i use for all mine and it works fine. Change the resolution in the file and try using that one.
Desc

heres the bootanimation.zip with a changed desc.txt file

YES!!!!!!!!!! ^.^
ianreecej said:
Here is my suggestion. This is the desc.txt file i use for all mine and it works fine. Change the resolution in the file and try using that one.
Click to expand...
Click to collapse
OMG Thank You!!!! It works perfectly now. I don't know what happened before. Now I am going to try to mess with the resolutions to see if I can get everything bigger and cleaner.
Do you by chance know if there is a limit to the size of the boot animation? I made it 8mb because I wanted to keep it lean and fast. If its around 25 mb, will that affect performance?

demoneyes905 said:
OMG Thank You!!!! It works perfectly now. I don't know what happened before. Now I am going to try to mess with the resolutions to see if I can get everything bigger and cleaner.
Do you by chance know if there is a limit to the size of the boot animation? I made it 8mb because I wanted to keep it lean and fast. If its around 25 mb, will that affect performance?
Click to expand...
Click to collapse
No Problem. The limit is really the space on your internal memory as far as i know. If you can fit it on there it should be fine. I know for myself with a droid incredible i can go to about 20 megabytes but that is only again due to my limited internal memory. If you were to move some apps to the sd card etc you can probably free more space.
Drop me a PM if you have questions or need a hand anytime.

Just had a look at your desc.txt and the problem was that all the info was on one line instead of seperate lines for each string of info
-RES +FPS
-NUMBER OF PLAYS + NAME OF FILE ( EACH FILE NEEDS ITS OWN LINE AND PLAY COMMAND)
-EMPTY LINE
Hope this helps you shed some light where you had your hiccup.
Also I found its the fps and image size that affects the animation.
If you have a high quality animation (KB/MB not res size) and a high fps it will struggle to render the images and result in sluggish playback. Try optimizing your images to squeeze that little bit extra out.

dully79 said:
Just had a look at your desc.txt and the problem was that all the info was on one line instead of seperate lines for each string of info
-RES +FPS
-NUMBER OF PLAYS + NAME OF FILE ( EACH FILE NEEDS ITS OWN LINE AND PLAY COMMAND)
-EMPTY LINE
Hope this helps you shed some light where you had your hiccup.
Also I found its the fps and image size that affects the animation.
If you have a high quality animation (KB/MB not res size) and a high fps it will struggle to render the images and result in sluggish playback. Try optimizing your images to squeeze that little bit extra out.
Click to expand...
Click to collapse
Thanks bro for your advice. I had the same problem.