7yl4r / avatarwallpaper Goto Github PK

on phones with multiple 'external storage' devices (increasingly common), we end up with the 'first time setup' run multiple times and multiple versions of the dataLog.txt file.

Not sure how to deal with this. I had to remove something from my desktop so that I could see the avatar.

Though will introduce many dependencies and potentially seriously reduce performance.

it's overkill at this point, but worth considering if complexity grows.

Here's a nice listing of android game engines

The offset created by switching homescreens left/right currently does nothing. The code to access this offset (named mOffset here) is commented out in wallpaper.avatarWallpaper.java. (search for mOffset & onOffsetChanged)

Many wallpapers scroll a bit based on this value, and I think we could include some effect based on this offset as well. Simple scrolling seems boring though, so I'm not sure what exactly this offset should do.

I think the app is holding a wakelock, which keeps the screen on indefinitely. This significantly affects battery life.

In the initial setup a sample avatar image is shown on the face choosing screen. On smaller screens the head is constrained to the given head box, but is not re-sized, so the lower right side of the head image is cut off.

Observed on Android 2.2. Each time you do it the body shrinks a little bit more, so you can make it reeeeealy tiny if you keep at it.

on first run wallpaper is stuck on 'standing', and the FFT display does not change.

when changing wallpapers and then returning, the app crashed. 2nd try at it seems to work fine.

create a separate class which can be called from the main application class to setup/run/draw various displays showcasing the functionality of the sprite/animation/entity class and scene handler.

If battery runs out with the wallpaper on, images do not properly load from the SDcard after power returns.

More frames should be added to add a delay between channel changes.

"external storage" is not actually external. It can go lots of places, and this makes getting the data off of the sdcard much more difficult. It also seems to break some things such as the photo face setup. It appears to work, but the image never gets saved or retrieved properly because it was all coded assuming that we knew exactly where it would be.

unreproduceable crash leaves the avatar app only a black screen. Subject reports no recent power problems or USB connections which are more typical causes of this kind of error. States only that it failed after connecting to a new wifi network.

should display splash screen or something?

looks very similar to issue #43

sprites load when the app is first run, if they get deleted, nothing is done and this is skipped. Instead, perhaps it should :

• Notify the user that the app is not working
• re-load the images from assets

This can be done by creating a method in the sprite/animation/entity class (currently residing in edu.usf.eng.pie.avatars4change.avatar) which is called when this case is encountered and attempts to reload the sprite. Reloading the images can be done by using the existing load() method of each class.

or mongoDB will complain about the collection name in on the server.

illegalArgumentException is thrown by Surface.unlockCanvasAndPost in wallpaper.avatarWallpaper

It looks like this has something to do with the surface changing unexpectedly. For now, just be careful not to rotate the phone when you are setting up the wallpaper.

sprites need to have frame # in common so that the location changes line up with one another.

Finding the exact location to align the sprites is difficult. There must be a better way to do this...

'Press to reset' is better than 'press to turn on reset flag for next program initialization'

If something goes wrong during initial setup (like camera failure), I don't get another chance to take a picture, select picture from the gallery, provide a unique name, etc.

A button could be added to the settings dialog to restart initial setup. Alternatively, everything in initial setup could be added into the current settings screen.

on v1.2. Probably this change does not show until the sceneBehavior update is called, which is only 1/hr for the proteus version...

it just shows "loading wallpaper". It will show if the screen blanks and comes back or something of that nature though...

Current workaround is to use the 'Xperia Gallery', which works for some reason.

rather than having each sprite collection in a folder, the sprites could be read from a sprite sheet containing all sprites for a given animation, avatar state, or avatar body part and retrieved by location in the sheet.

This may be difficult to code, but may improve the performance of the app by allowing the app to load images less frequently.

However, this may also cause the app to use more memory, leading to a difficulty staying under the maximum memory usage requirements for live wallpapers.

By updating only what was changed since the last draw, we can possibly optimize drawing. In this case, care must be taken to erase the old objects, since they will not simply be drawn over as they are currently. This might increase our max framerate from the ~30fps it sits at currently.

a 2d sprite-based gaming library could be used to make life a lot easier in coding the sprite arrangements. But now... which to use?

Sensor service does not work unless another accelerometer-using application is run. (I think) Tested using Luis' original activity monitor.

Observed on Xperia ST18a, 4.0.4.

It's good that there is no crash, but a notification or toast should be shown as well.

Using v1.2

The only way I've found to correct it is a re-install.

I don't know where all these bugs are coming from in the study, and I'm unable to reproduce them. More information about the phone needs to be recorded. Things which might help:

• Battery log
• timed file write check 'ping'
• add a crash-handler which logs info on crashes

I think it is printing the numerical id from the R file rather than the actual string value.

My Samsung Galaxy S3 has a 1280x720 display and the avatar looks pretty tiny. We should do our best to keep the size of the avatar the same across all phones, independent of screen resolution. This should be possible using resolution-independent units (inches?).

the com.droid4you face choosing application crashes when a relatively large face is selected, but not for smaller ones. This could indicate a memory leak, but I don't know that code well enough to find it. Observed primarily on the HTC magic Android 2.2.

or when the sdcard is in use via usb.

sprites could have a rotation member which allows for the sprite to be rotated. (especially useful for sleeping & biking)

When looking through the phone gallery the images show up, allowing users to easily (accidentally) delete or modify them, resulting in a broken wallpaper.

I believe that a restart of the wallpaper will fix it, but ideally, I think these images ought to be a bit more hidden from the user.

The viewLogger (in avatarWallapaper) responds to onVisibilityChanged() and then prints the time viewed along with the current animation, it is assumed that the animation at end of view time is the animation which was present the whole time. An example of when this breaks: I turn on phone screen, animation is running, while I'm looking at it the animation changes to sleeping. Now when I turn off the screen, the logger records that I viewed 'sleeping' for the full duration of my use.

This is probably not a big deal, since animation changes occur infrequently and view times are short, so the chance of seeing a change is rare.

In order to fix this, the logging should be broken out into a function which can then be easily called from within the timed scene changer as well as onVisibilityChanged.

The values which first show up are incorrect, and the value must be changed in the settings in order to be applied to the avatar.

animations are possibly too big...

This includes any logged data as well as the hidden sprites folder all of which is stored in the /MirrorMe/ directory.

to keep subjects from changing them. A simple required password entry would be fine. I think the way to do this would be to allow for users to have some settings, and one of the settings is a 'admin settings' button which starts an activity. The activity can then prompt for password and change settings.

Using RAZR HD there is no 'menu' button to press to pull up the sub-options menu from the settings screen. On this phone typically a '...' button will appear to allow access to more options, but there is not one here. Perhaps a fix is to make these options accessible via a button, since the current 'press settings then menu' is a bit strange anyway...

Each sprite/animation in an entity needs to line up at certain connection points with the other objects in the entity. (for example the head sprite needs to always be on the body's neck). Currently, these points are determined by guess-and-checking the locations which are hard-coded. A better approach for allowing the alignment of sprites/animations in an entity is needed.

Should be 12am, right?

You get to the choose image screen just fine, but when the image is chosen the default smiley face is shown for you to crop rather than the image selected.

DROIDX using Android 2.3.4

It was fine for at least an hour, and then this started happening. Maybe it has something to do with the change from one animation to the next.