SeePU Changelog
v0.8.6beta:- workaround for stupid Cupcake incompatibility
- support all screen sizes
v0.8.5beta:
- tentative Cupcake-FC fix
v0.8.4beta:
- moved the service to its own low-priority thread
- fix FC in CM5.0.x (and possibly others)
v0.8.3beta:
- the 'system' process is now filtered in the History Graph
v0.8.2beta:
- the 'freeze' issue, y'know? Fixed! (thanks Nitin!) - from my good old Magic's POV, though, nothing changed :)
v0.8.1beta:
- another try at solving the freeze issue that never once occurred on my good old Magic (and it's been running constantly for weeks now) - if you notice any difference (for better or worse) please contact me
- as per requests, light text color in the notification pane for those with dark themes - long press any 'history' checkbox to choose
v0.7.6beta:
- quickly fixed the first little bump in the future-proof plan of v0.7 (a problem with ++)
v0.7.5beta:
- some very cool new features! (++ only)
- historical plot of CPU, RAM and/or network usage in the notification pane
- one-click-kill of the app that's stuck in an infinite loop of 100% CPU usage, pain, regret and sorrow (yes, it's the humane thing to do, and I'd rather do it quickly)
v0.7beta:
- optimized the hell out of it - one day I'll write another post about my uberleet low-level byte-mangling skillz
- prepared a future-proof plan for upgrade routes with the upcoming paid addon
- some minor bug fixes
v0.6.1beta:
- fixed FC introduced in v0.6 :/
v0.6beta:
- added network usage graph! (for *all* network interfaces combined)
- UI tweaks
v0.5beta:
- decided it was after all better for consistency to include caches in the available RAM
- UI tweaks
v0.4beta:
- come again? You are what? Legend?
v0.3beta:
- fixed some more the occasional messing up of the icon update - will auto-restart now (good, but why bother by the way? It happens once a day at most...)
v0.2beta:
- fixed (perhaps) the occasional messing up of the icon update
- some performance tweaks
- some UI tweaks
v0.1beta:
- ongoing notification
v0.0.0.0half/beta:
- first public release, EXPERIMENTAL
ShareThis
Posts
15 comments:
Thanks cool app
the best cpu monitoring app !!! beatiful look !
I'm still having freezing issues with the latest version of seepu. Updates start again once I pull down the notification bar and click on SeePU graph, but stop after a while (Mostly after waking up the phone from sleep mode).
You could try changing the app to a Visible process instead of running it as a Secondary server process, although I think that would be at the expense of battery life.
Running on Motorola Droid, btw.
!@$@!#%$# One user reported it was better, I had hoped I finally nailed it :(((((
How do you know it's seen as a secondary server process? In theory it shouldn't, as it has notification icons. I'm afraid Eclair requires explicit use of the new API... Too bad that a) I can't use it, not even through reflection, without making Cupcake/Donut incompatible and b) Google won't allow different binaries for different Android versions.
Once more: %@#$%%!!
Well, I use an app to monitor all my running applications and SeePU shows up as a secondary server process. There's actually a very similar app that uses notification icons to display status - it's called Screebl.
I'm not sure if you're aware off the app, but it shows a notification icon on the bar which changes color depending on the phone's orientation. I've never had it freeze on me and this app shows up as a Visible process.
Also, I changed the OOM priority of SeePU to a very low value, and I haven't noticed any freezes for a while. I believe the OS is automatically terminating the update service when I'm low on memory, and I'm low on memory a lot!
I'm no developer and am not really sure of any of this, it's just my theory!
Sorry to say lowne, but freeze-issue is still there on my Milestone (2.0.1 rooted). Though it seems to happen less often since update to 0.8.1.
:/
Well I can confirm that the update service is being automatically terminated. I checked a list of running services right after SeePU stopped updating, and the service vanished! I don't use any task managers, so I'm pretty sure it's the OS doing it.
I should also mention that I have a pretty cluttered homescreen with a load of widgets and random crap, so this issue probably only pops up for people like me. Wish I had an N1, ha!
@Nitin: you're 100% right - you nailed it from the start and kept hammering on it over and over, I'm finally convinced by the huge amount of proof :D
If there was a 'betatester of the week' award, it'd be definitely yours ;)
(also: lol @ 'load of random crap')
Ok, so if someone can make their apps "Visible", I can do it too (for SeePU at least). As soon as I figure it out, I'll push an update.
Yay, SeePU shows up as a visible process now! Will test and see if it ever stops updating again.
After about two hours of extensive web browsing and youtube, SeePU is still going strong. Pretty sure I've been real low on memory too.
Good job Lowne!
Sorry about the triple post, but here's one last suggestion before I head out for the night:
Enabling the option to kill the process that uses up the most CPU time has an issue - it's almost always system. As you know, you can't and shouldn't really end that process (logcat says process not found) so it's sort of redundant. A solution would be to filter out system, and only kill user processes.
Say I have a rogue application sitting in the background trying to divide by zero. Instead of melting my omap chip, you could just end it! I believe this is a much more efficient method, what do you think?
@Nitin: yeah, turns out I was wrong - you *can* do anything through reflection (well, almost, but it's another story).
About "system": I agree it's kind of useless; but if a process (call it com.evil) that is the root cause of an infinite loop causes system (as opposed to com.evil itself) to get stuck in 100% usage, there's a chance that the 2nd top-consuming process is *not* going to be com.evil, but some innocent bystander idly minding its own business.
So the question (for everyone): how often do you see "system" stuck in 100% CPU usage?
You're right Lowne. I'll just go back to wearing my thinking hat. I will be back with more suggestions/bug reports though!
@Nitin: I decided I'll give it a try after all (the filtering) - it's going to be featured in the new SeePU private beta group, so I can get some early feedback about the possible problem I described (it *does* happen, but perhaps not often enough to be worried about it).
And by all means keep your reports/suggestions coming! Your thinking hat seems to be particularly effective :)
Awesome app but... !Doesn´t work in Cyano 5.0.7 (Eclair 2.1)¡
Post a Comment
Note: Only a member of this blog may post a comment.