Task Manager 1.10.5 release note

V.1.10.5
*User can set "LONG UPDATE CYCLE"(>2 secs) to save battery

* FIXED BUGS

By default, this AP use 2 seconds timer to monitor cpu and memory, battery usage. Now you can input your desired monitoring cycle from 2 to 99 seconds, that can save battery power.

Fixed bugs: improve monitoring efficiency, prevent high cpu usage occasional and more smooth for ListView scrolling.

Task Manager 1.10.4 Release note

* CHANGE CPU % to BLACK/WHITE COLOR

* ADD CPU Usage calculation from power on

* Fixed expection happen when user terminate application.

Comment:
The icon of status bar in Android only can assigned by fixed resource id, so I must be add many icon files to support different color of CPU % on status bar, it's why the Task Manager became to bigger than before. If you know the way to solve this issue, I will appreciate your advice, thank you!

Task Manager 1.10.3 Release note

V.1.10.3
* Add BATTERY % option on status Bar

* Change % Color to BLUE for Hero black background

ORIGIN function
* STOP, SWITCH to Task or Process

* provide ONE CLICK STOP or MULTIPLE STOP

welcome suggestion to wingtseng123@msn.com
and visit http://wingsandroid.blogspot.com/ to see more information of this AP, or try my AP PaintWallpaper.

PaintWallpaper 2.0.2 release note

V2.0.2
*ADD: User can RESIZE browser view

NOTICE

1. You can touch the RED line then move to your desired size, then touch up to end the resize operation.
2. Browser view size will never bigger than the rectange area of my application

V2.0.1
*Localized to: ja, de, fr, es, zh_CN, zh_TW

*ADD Browser view on wallpaper

PaintWallpaper 2.0.0 release note

*ADD Browser view let you can add browser view on wallpaper
scroll web page then press "Record", the view in red rectange will be paint on wallpaper

*DON'T paint by minute when add Browser view, it will kill your battery

*ADD Calendar/Date/Clock/Note on wallpaper

Known issues
1. Some times exception because memory is not enough for bigger web page

2. For some web pages, the capture location may be incorrect