Database Info

[INFO] ICS Performance Tweaks

Wanted to share some info on ICS tweaking/tuning based on the following page.
http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/
I've implemented all of them and my ROM is super smooth and fast. Would be interested to see how others do with them.
Extract from site...
Here are just a couple of tweaks to smoothen one's UI experience in Android 4.0 Ice Cream Sandwich. (Remember these changes won't apply without a reboot and you will need a rooted device).
Improve UI frame rate and touch response:
On dual core devices:
In build.prop (found in/system/) set (It's probably already there under #Common Display Settings, just increase the value):
Code:
windowsmgr.max_events_per_sec=240
On single core devices either of the following are recommended:
Code:
windowsmgr.max_events_per_sec=120
or
Code:
windowsmgr.max_events_per_sec=150
240 seems to work fine on single core devices as well. You should probably try different values and see which one works best.
Disable kernel error logging:
Add this anywhere in build.prop -
Code:
ro.kernel.android.checkjni=0
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
Enable tile rendering:
(does not apply to Galaxy Nexus)
Whether this will work largely depends on the device and the chip it is using. If you are using a Snapdragon/Adreno based device, as far as I know, tile rendering has not been fixed yet.
For others, you might as well give it a shot (either that or it's already enabled like it is on the Galaxy Nexus.) The worst that can happen is messed up homescreen icon/widget rendering, which can be fixed easily by reverting the change. Tile rendering is a more efficient form of GPU composition, and boosts performance since each frame is split into tiles.
Add or change the following in build.prop:
Code:
debug.enabletr=true
Qualcomm specific tweaks:
Many recent ROMs will already have these but the following settings are recommended under #Qualcomm display settings in build.prop.
Code:
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
com.qc.hardware=true
Improve Scrolling FPS:
I don't actually know the best value for this, I guess try anything from 4000-8000 and see what happens. However, it adjusts how SurfaceFlinger handles scrolling input and can potentially improve FPS:
Add or adjust the following in build.prop
Code:
ro.max.fling_velocity=4000

Really Really Nice Find.
I implemented these into the build prop of MHX Superlite and now it runs even faster then before.
Would definitely recommend developers implement these if they haven't already.

I had most of the these build.prop edits since the release of my ROM! Its great too see an article! But ya i have those!
tehee said:
Really Really Nice Find.
I implemented these into the build prop of MHX Superlite and now it runs even faster then before.
Would definitely recommend developers implement these if they haven't already.
Click to expand...
Click to collapse

Instead of many different flavors of ROMs, this is really something I would like to see.

+1 to this and stuff like this into MHX's rom.
I have seen a few other tweaks and stuff but honestly I'm usually too lazy or incompitent to go in and bother to apply them myself. but I'd really like to see this in 4.3 of mhxs rom.

One thing I've noticed time and time again is that a lot of the scripts included in custom ROMs don't actually work. I'm not pointing fingers or anything. One thing I always do is read the scripts in init.d and then try to run them from an adb shell. You'll see errors and what-not if binaries are missing, directories don't exist, or worse yet multiple scripts with the same stuff, or even conflicts between scripts, etc. Makes my head spin from a troubleshooting perspective. Check build.prop for dupe entries as well. Sometimes you might think you set something only to have something towards the end supersede it.
Regardless, these tweaks make my launcher (Nova) ultra smooth. The EGL mod, I noticed, is exactly how Qualcomm packed their binaries. e.g. no CPU-level rendering.

appdroid said:
I had most of the these build.prop edits since the release of my ROM! Its great too see an article! But ya i have those!
Click to expand...
Click to collapse
I can see that, Antutu was showing me 6500! Not too shabby!!

. If you are using a Snapdragon/Adreno based device, as far as I know, tile rendering has not been fixed yet.
Does this mean this tweak wont work on the skyrocket? or it isnt yet on the skyrocket and i should do it?

InstigatorX said:
Improve UI frame rate and touch response:
On dual core devices:
In build.prop (found in/system/) set (It's probably already there under #Common Display Settings, just increase the value):
Code:
windowsmgr.max_events_per_sec=240
On single core devices either of the following are recommended:
Code:
windowsmgr.max_events_per_sec=120
or
Code:
windowsmgr.max_events_per_sec=150
240 seems to work fine on single core devices as well. You should probably try different values and see which one works best.
Click to expand...
Click to collapse
None of that is in my build.prop file...

If it's not in my system, can I safely add it ? I'm running Smooth ICE v3.1.

Yes
Sent from my SAMSUNG-SGH-I727 using xda premium

bdbx18 said:
If it's not in my system, can I safely add it ? I'm running Smooth ICE v3.1.
Click to expand...
Click to collapse
Yes. Sorry for the double post. Fat fingers.
Sent from my SAMSUNG-SGH-I727 using xda premium

check out this thread. i wonder if any of these can be added as well?
http://forum.xda-developers.com/showthread.php?t=1563239
---------- Post added at 09:27 PM ---------- Previous post was at 09:07 PM ----------
so i tried some of these. must have done an edit wrong in the build.prop. i added another qualcomm specific string i found and things went bad quickly.
phone reboots past the splash screen, but the screen goes dark and does not turn on, even though adb can still see it
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
pushing the original build.prop does nothing
clearing everything from the phone did not work, and after that it would hang at the spash screen and adb would not recognize.
now it will no longer charge from the kernel, the battery icon pops up for a second and immediately disappears and the screen stays black. the only sign of life is a series of 4-5 buzzes when holding down the power button. button recovery no longer works. download mode does though if you get lucky with the right timing.
---------- Post added at 10:04 PM ---------- Previous post was at 09:30 PM ----------
i dont know what i did, but i really messed something up. got lucky and odin'd back to ICS leak.
i guess just be careful when messing around with this. i thought just pushing the original build.prop back to the device would work, but I was wrong.

orlandoxpolice said:
check out this thread. i wonder if any of these can be added as well?
http://forum.xda-developers.com/showthread.php?t=1563239
---------- Post added at 09:27 PM ---------- Previous post was at 09:07 PM ----------
so i tried some of these. must have done an edit wrong in the build.prop. i added another qualcomm specific string i found and things went bad quickly.
phone reboots past the splash screen, but the screen goes dark and does not turn on, even though adb can still see it
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
pushing the original build.prop does nothing
clearing everything from the phone did not work, and after that it would hang at the spash screen and adb would not recognize.
now it will no longer charge from the kernel, the battery icon pops up for a second and immediately disappears and the screen stays black. the only sign of life is a series of 4-5 buzzes when holding down the power button. button recovery no longer works. download mode does though if you get lucky with the right timing.
---------- Post added at 10:04 PM ---------- Previous post was at 09:30 PM ----------
i dont know what i did, but i really messed something up. got lucky and odin'd back to ICS leak.
i guess just be careful when messing around with this. i thought just pushing the original build.prop back to the device would work, but I was wrong.
Click to expand...
Click to collapse
Yeah, editing the build.prop can be tricky. Never had what happened to you specifically, though. Here's link to my build.prop if u want use. Works well for me.
https://www.sugarsync.com/pf/D7693548_724_777039871
Sent from my SAMSUNG-SGH-I727 using xda premium

How come android doesn't have a registry? Something like how wm used to have.
[ ICS-Leak 4.0.3] SkYrOcKeT

WhatzinyourphonE said:
How come android doesn't have a registry? Something like how wm used to have.
[ ICS-Leak 4.0.3] SkYrOcKeT
Click to expand...
Click to collapse
Linux doesn't have registry by design so that's why android doesn't have it. They will never have it, it's the way that the OS is designed, everything is in files inside.
Sent from my SAMSUNG-SGH-I727 using Tapatalk

I added a debug.qc.hardware=true line as well as defining a min and max surface flinger and I'm pretty sure that effed it up.
Sent from my SAMSUNG-SGH-I727 using xda premium

not to sound stupid.
What do I add the the build.prop if these fields are not there?

tjsooley said:
not to sound stupid.
What do I add the the build.prop if these fields are not there?
Click to expand...
Click to collapse
If you open up build.prop you will see lines of code like these:
windowsmgr.max_events_per_sec=120
You change the value (true/false or number) so that it works differently or add a new line.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1236732

Presbycusis said:
If you open up build.prop you will see lines of code like these:
windowsmgr.max_events_per_sec=120
You change the value (true/false or number) so that it works differently or add a new line.
Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1236732
Click to expand...
Click to collapse
the thing is I dont have any of the lines in my build prop

[WIDGET][2.1+] MicroNotes

MicroNotes​Android 2.1+​
Hello people!
I am new to XDA so first i would like to say Hi.
MicroNotes is my first android app/widget that i have made and so i would like some feedback.
DESCRIPTION
From planing out your daily schedule to writing a to do list for the day, MicroNotes for Android is your #1 Notepad app for your Android device.
FEATURES
-Multiple line notes, good for making lists
-Works on android Gingerbread(2.1) - android Ice-cream Sandwich(4.0.4)
-Updated almost daily
-Looks good on all types of devices (Android 2.1 - 4.1)
-No bugs
-Simple
-Dose not need a internet connection
Lots more to come!
Check out my portfolio at: http://besieger.ensocms.com
INFORMATION
This is a widget not an app, when you place the widget on your screen you will be taken to a app like screen where you can type your note and save it.
Should you need to edit your note simple tap the existing note on the screen and edit then press save to save the changes.
Any one interested in trying it here is a link: Link
If there is anything wrong with my post please let me know so i can change it
Thanks for your times guys,Josh

"wrighting" should be spelled writing.
I'd like to know more: when you click the widget, does it open the main app or does the keyboard appear on the launcher screen?
Also, is there a main app in the first place (since you're just saying "widget")?
---------- Post added at 11:48 PM ---------- Previous post was at 11:37 PM ----------
Ok, installed it. It's only a widget (make sure it's installed to the phone memory). Simple to use, simple interface, non existent loading times. Clicking the widget opens a screen where you can change the note. Some themes/transparency would be nice, other than that, it does what it says it does.

GermainZ said:
"wrighting" should be spelled writing.
I'd like to know more: when you click the widget, does it open the main app or does the keyboard appear on the launcher screen?
Also, is there a main app in the first place (since you're just saying "widget")?
---------- Post added at 11:48 PM ---------- Previous post was at 11:37 PM ----------
Ok, installed it. It's only a widget (make sure it's installed to the phone memory). Simple to use, simple interface, non existent loading times. Clicking the widget opens a screen where you can change the note. Some themes/transparency would be nice, other than that, it does what it says it does.
Click to expand...
Click to collapse
thanks for looking at my app, what do you mean by add themes?

besieger1 said:
thanks for looking at my app, what do you mean by add themes?
Click to expand...
Click to collapse
Different background/text colors, perhaps optional rounded corners, etc.

[APP][2.2+]Yet Another Auto Brightness

Yet Another Auto Brightness (YAAB)
A small open source application designed to enhance user control over screen brightness. Initially it was developed to make the screen as dim as possible to save battery on old devices. AND to provide a simplest possible user interface without any complicated calibration procedures and so on.
It is Beta version now. It has ascetic interface and very simple in use.
Source code, issue tracker and latest APKs are available here: http://bitbucket.org/gyrussolutions/yaab/
Google Play link: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Any feedback is highly appreciated, especially from other Android developers

Tester initial impressions
A nice small download and a simple and clean interface. Started service and it immediately started dimming my brightness. A few points to begin with:
The manual slider does not seem to work as there was no change in the brightness.
It doesn't seem to alter the brightness in different lighting (unsure if it is supposed to do this or not from documentation).
It is making my screen too dim, I have a GT-I9300 and the auto brightness on it is excellent and always keeps my screen at the good readable and useable settings.
Will run for an hour or so now and update this with further thoughts then.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Ok it's keeping my screen to dim to be usable so have had to uninstall for now. A few further points though:
Application Force Closes when you stop the serverce.
The manual slider does not work.
Handset - GT-I9300
ROM - Paranoid Android 2.51
OK log wouldn't upload, here's a link for it on dropbox.
https://www.dropbox.com/s/mbyfz33b7audtxz/2012-11-02-17-10-36.txt

Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.

andrvo said:
Good report, thanks a lot.
Looks like the app incorrectly reads light sensor data on your device and thus brings brightness to minimum.
I'm working on the issue now.
Click to expand...
Click to collapse
Let me know when you have a new version and will test again for you.

Hi!
IIIIkoolaidIIII said:
Let me know when you have a new version and will test again for you.
Click to expand...
Click to collapse
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.

andrvo said:
Hi!
I did some research tonight and found out that many people have concerns about light sensor behaviour in your ROM.
I wrote a very simple app that shows sensor parameters on the screen and displays all subsequent updates received from the sensor.
APK is here: https://bitbucket.org/gyrussolutions/lightreader/downloads (sources are available there also)
It doesn't require changing settings and it will not attempt to change screen parameters also. Minimal discomfort
Could you please run it on your device and post here its output in a dark room and under strong light?
Thanks.
Click to expand...
Click to collapse
Details bellow, Sensor name - CM36651 Light sensor
Darkened Room:
Accuracy 3, MAX 121240, last 0.0
Bright light:
Accuracy 3, MAX 121240, last 3700.0 (fluctuating around this point)
I've not read much in relation to sensor issues on this ROM, will do some digging myself now. Hope this information is useful to you.
B
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
I have just done some digging and found no Liight sensor issues mention in the CM10 threads or known bug list. There was a light sensor issues back in September for Paranoid Android but this was fixed back then. Where have you seen the information about peoples concerns with the light sensor?
I have attached a link to the CM10 known issues bellow.
http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-I9300:Nightly:Known_issues

I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.

andrvo said:
I saw several mentiones of light sensor problems here on the forum, like this: http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862 or this http://forum.xda-developers.com/showpost.php?p=31801837&postcount=2862
Some other mentiones on other forums/blogs.
But anyway your readings are very good, so the sensor isn't a culprit any longer.
I just had to make sure that the app has valid input data and the problem is somewhere in the algorythms. Because in the log file you submitted yesterday contains very strange values.
Thanks again. I'm going on with my investigation.
Click to expand...
Click to collapse
Yeah those were two months ago and the bug was fixed in a few days, there have been about 10 version updates since then as well.
Let me know when you're new version is available and will test again.
B

Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.

HTC Wildfire S (Marvel)
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
I'm curently on custom SENSE 2.1 rom but I switch often so will test this one on them too.
Tnx,

GermainZ said:
Maybe you should restrict app installation to devices that have a light sensor? Because Google Play allows me to install it even tho I don't have one.
Click to expand...
Click to collapse
Will be done, thanks. I don't know how could I have missed that

kobredabre said:
Works as intended on HTC Wildfire S (Marvel) 510e.
Brightness is applied 1/2 secconds after screen is on and with correct levels acording to the external light and manual adjusment seting.
I like the simplicity (pls don't change that) and, so far, I didn't noticed any bad impact on battery life.
Click to expand...
Click to collapse
Thanks for the update.
We are working on automatic/manual "night reading" mode and manual range adjustments now, but we intend to keep the main screen and the defaults in this way, so most of the users would not even need to open menus and dig deeper into the settings.

IIIIkoolaidIIII said:
Let me know when you're new version is available and will test again.
Click to expand...
Click to collapse
I've uploaded current version to the downloads section: https://bitbucket.org/gyrussolutions/yaab/downloads
Check this one please when you have time.
To be honest I still don't know why did it set brightness to minimum on your phone and didn't ever rise it again.
But your log revealed a number of thread synchronization issues that I fixed in this version. I believe there could be connection between these issues and your dark screen.
UI is a bit different, it is my current development version. But start/stop buttons still do the same.
Don't wait long, 10-15 seconds is enough, if it doesn't track ambient light changes right from the beginning - it will not start after some minutes.
Thanks.

Hi andrvo,
Yaab works on my Nexus 7. It is also very easy to use. But I have two remarks.
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.

Thanks, checking it out...

benkxda said:
First the app starts in portrait and I only use me tablet in horizontal view. The app not only starts in portrait, it does also not change to horizontal. This would be nice, if the app would start with mentioning the position.
Click to expand...
Click to collapse
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
benkxda said:
The other point is, that it only needs one more option in my case. There is automatic and manual brightness. If I can use the manual slider in the automatic mode to set a basic brightness, this would be handy. Hope you know what I mean.
Click to expand...
Click to collapse
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
benkxda said:
Thanks for your work. Would be nice to find Yaab on Google Play to get updates automatically.
Click to expand...
Click to collapse
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab

Test it on Galaxy Note 2
Everything looks working. Closing the sensor with my hand causing the screen light dim.
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.

andrvo said:
Yes, it is my fault. I didn't have enough time to test those layouts on tablets.
I plan creating layouts for tablets from scatch since existing were designed mostly for phones.
Well, it works almost as you describe. "Manual adjustment" actually set the base line for the automatic brightness formula.
I'm preparing new release right now, will be available today or tomorrow. New version also allows to limit top and bottom values of brightness, maybe it will fit your need
It is here: https://play.google.com/store/apps/details?id=biz.gyrus.yaab
Click to expand...
Click to collapse
That new release I get then via Play, thanks for that. Delighted me.

jimmod said:
Test it on Galaxy Note 2
Not sure what idea I can give though, probably you can check 'smart stay' feature at Samsung S3/Note 2. Although it's not a screen auto-brightness thing but it have same objective about saving battery from screen consumption.
Click to expand...
Click to collapse
Ok, I'll check it, thanks.

Version 1.6 is rolling out to the Play store.
What's new:
night mode, manual and automatic. The latter will work only on new devices with high quality sensors which are able to provide accurate values in the lower part of the range. Manual works on any device.
range controls added. Now it is possible to shrink the actual range of automatic brightness values.
bugfix (of course)
Beta testing is still going on, all testers are welcome.
Fresh APK is also available here: https://bitbucket.org/gyrussolutions/yaab/downloads

[Q] Bluestacks no phone/large phone view mode?

Bluestacks landscape/portrait only tablet view mode. Where are others?
As soon as the bluestacks have been progressing it has been deleting most of the crucial elements from it. Now the appsettings app doesn't contain the phone and large phone view mode only the tablet and default mode. Because of this most of the apps doesn't work fine and creates problem unless fiddled with the registry. As appsettings is an app and previously built bluestacks had these options can someone post them here as most of the games do not work with the default and tablet mode resolutions. Also some apps automatically changes resolution too, it's okay to change the orientation but instead of changing the app's orientation the bluestacks orientation is changed which is mind wobbling.
Do anyone else is having this problem?

Hiiii ... when I use blue stack my first word for this app is blue sh!t ...!!! he never my any I download
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
everyone having problem by using bulestacks in my opinion

any webbrowser with dark mode? (white text, black background)?

Hello
is there any browser which is designed like
-only white text
-only dark background
(if possible not many wide white fields)
Ideally I couild also specify the color, but that's not really needed.
I hope you have suggestions, as I cant really use stock Firefox/e.g cause of some eye problems

Hi
UC browser is the only one which works flawlessly for me (ive tried a ton of browsers) BUT dont use night mode !!!
You have to put your own dark (black) image as a global background, and select white text on black bg in the menu.
dwa4321 said:
Hello
is there any browser which is designed like
-only white text
-only dark background
(if possible not many wide white fields)
Ideally I couild also specify the color, but that's not really needed.
I hope you have suggestions, as I cant really use stock Firefox/e.g cause of some eye problems
Click to expand...
Click to collapse

Where can I select the bqckground image?

dwa4321 said:
Hello
is there any browser which is designed like
-only white text
-only dark background
(if possible not many wide white fields)
Ideally I couild also specify the color, but that's not really needed.
I hope you have suggestions, as I cant really use stock Firefox/e.g cause of some eye problems
Click to expand...
Click to collapse
There are add-ons for Firefox that do this. I forgot the name but you can search for it.
Another browser which can do invert colors is Pyrope Browser. You can download it from play store if you have android 5+.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
dwa4321 said:
Hello
is there any browser which is designed like
-only white text
-only dark background
(if possible not many wide white fields)
Ideally I couild also specify the color, but that's not really needed.
I hope you have suggestions, as I cant really use stock Firefox/e.g cause of some eye problems
Click to expand...
Click to collapse
There are Firefox add-ons that can do invert colors :
https://addons.mozilla.org/en-GB/android/addon/dark-background-light-text/?src=search
https://addons.mozilla.org/en-GB/android/addon/dark-mode-night-reader/?src=search
https://addons.mozilla.org/en-GB/android/addon/invert-image/?src=search

Thanks - checked them out. Works, but while launching a site its that annoying white screen.
+firefox isnt good for 3g/portable use.
ideal would be an dsrk opera mobile

dwa4321 said:
Hello
is there any browser which is designed like
-only white text
-only dark background
(if possible not many wide white fields)
Ideally I couild also specify the color, but that's not really needed.
I hope you have suggestions, as I cant really use stock Firefox/e.g cause of some eye problems
Click to expand...
Click to collapse
dwa4321 said:
Thanks - checked them out. Works, but while launching a site its that annoying white screen.
+firefox isnt good for 3g/portable use.
ideal would be an dsrk opera mobile
Click to expand...
Click to collapse
Have you try Pyrope browser? It's gello/chromium based browser that can do invert colors for Android 5+.
And you might like this browser :
https://play.google.com/store/apps/details?id=com.urysoft.darknessreader
It's lagging in my machine but for you it may be different.

im still in kitkat, so I cant install perupe.
The latter one looks good, will play around it for now