After messing around with a certain tweak, here's what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Neocore and Quadrant were run at 1.8 GHz / performance.
Fps2d at 1.2 GHz / smartassV2.
Probably slightly lower FPS on 1 GHz if not equal.
If there's enough people interested, I'll upload it in the dev section.
Credits to zdzihu since he found this first
EDIT: It's not as good as you think.
KalleD said:
“I know there’s been a lot of discussions regarding framerate caps, and let me assure you, it’s all to improve the user-experience.
Disabling the framerate cap will degrade the visual appearance, introducing tearing artifacts, and stuttering when navigating lists, etc.
However, assuming you just want higher figures when benchmarking, and care less about the experience, here’s the general steps:
1. You need to set the system property “debug.gr.swapinterval” to 0. A typical command for this would be:
adb shell setprop debug.gr.swapinterval 0
2. For this to take effect, you will need to restart the system-server. You could do this with:
adb shell
stop zygote
start zygote
Also, please note that this setting is not “persistent”, meaning that the next time you reboot your device, the setting will reset to 1 unless you’ve modified your initrd to do this at every boot.”
Click to expand...
Click to collapse
The SE Developer told we might degrade the visual appearance, introducing tearing artifacts, and stuttering when navigating lists, etc
Did you notice any of these?
ShyamSasi said:
The SE Developer told we might degrade the visual appearance, introducing tearing artifacts, and stuttering when navigating lists, etc
Did you notice any of these?
Click to expand...
Click to collapse
Yes, but this is not debug.gr.swapinterval. It's totally different. The tearing and stuttering are there but it's not as bad.
Related
Would anyone care to list the best settings to use for TCPMP on the Jasjar/Universal?
What is the best video driver, what should be buffer sizes, microdrive?, preload at underrun etc etc...I have tried playing around with them, but not really sure what I'm doing, so would appreciate some help here.
Thanks in advance.
You don't have a microdrive - that's the old IBM (I think) Compact flash hardrives.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Otherwise, I think the graphics should be set for xscale, and most of the other stuff is to personal taste I think. I've never fiddled to much with it and it works well enough.
Preload and buffering are again for loading up a certain amount of data to RAM before playing media. I've never needed to play with the settings.
What kinds of things are you (potentially?) having troubles with?
V
The usual slightly jerky video replay on files. Even WMV files that play perfectly in WMP on the Jasjar, seem to struggle a bit in TCPMP. I thought I might be able to reduce some of the jerkiness by tweaking the settings, but being the plank that I am, I don't really know or understand what they do.
I think the video accelerator option being set to xscale is pretty much the best you can do.
Try playing with lower sound quality to check.
Try increasing the "normal buffer" slightly, I keep mine at 2400k; too high and it may hinder performance because the system will be fighting for resources.
Ignore microdrive.
In advanced you can try "prefer less buffering", but I don't use it and have no problems.
"lookup tables over arithmetic" should help, but again, I don't use it.
On xscale I tick all three.
What resultion/bitrate are the files?
V
The only setting I have played with is in the advanced menu is the "Manual A/V offset +/-" . I have selected -130ms in order to get the lip sync right.
I read on another site some chap thats done alot of testing of TCPMP, and im sure the best gfx performance was when on RAW. summut like 40% better performance over the rest.
Just making sure that everyone knows there's a new version of TCPMP available - Version 0.70
Any major changes?
Not that I can see...a new plugin for speex or something that I've never heard of...
http://tcpmp.corecodec.org/changelog
I was playing around with class based programming stuff, and the Diamond GSensor, and some physics (I'll pretend it's relevant to my A levels ) and wrote a little game to experiment...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What it is is a field of balls that are affected by gravity. If they collide, they should bounce off each other in a vaguely realistic way.
The number of balls can be adjusted via the up/down keys up to a maximum of 100 (the performance isn't great with that many though...)
The size of balls can be adjusted using the left/right buttons - there's no minimum or maximum size.
Hitting the centre button will pause everything.
You can click and drag the balls, and sometimes a "flick" makes them move, I need to fix that though.
Tilting the device will accelerate all the balls.
The colour and position of each ball is random.
Should work on Diamond, Raphael, Blackstone, Rhodium and Topaz.
This isn't meant to have a real reason, it's just something fun and physicsy!
Changelog:
0.7 - fixes a touch screen related bug...
0.6 - reduces sensor polling time making it more reliable, some graphical speed ups as well.
0.5 Initial public release
Looks good.. Let me try this..
This is a pretty fun and simple game! Would u consider open sourcing it?
gobmonster said:
This is a pretty fun and simple game! Would u consider open sourcing it?
Click to expand...
Click to collapse
I probably will when I've cleaned up the code and tried to make it faster...
New release fixes a few things...
Get it from the first post.
hey i was wondering if you still have the source code for this?
I'm looking for something to get of started on programming apps for my diamond and its sensors... and this seems to be a pretty cool place to start as i have a few ideas of how this could be improved..
Thanks,
-David
Seems to have got lost *kicks to the top*
I've gotten this message about three times so far while playing Sims 3:
"Heap 2 out of memory" allocating 40 bytes but only 128 available (36 LFB). Increase icf setting . . ."
Anyone else get anything like that?
Ive gotten this warning several times i have been doin research on how to increase icf setting and it said it was sum advanced stuff and it sed it cood ruin your rom but it wasnt necessarily for the vibrant i think it was more of a computer thing idk but i want to increase memory so i can play more soon
Here's a pic and video of the crash from the Tmo forums:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.youtube.com/watch?v=sG2e8941fNc
I pretty much can't buy/move anything without this happening so it's rendered the game practically unplayable. Hopefully a dev here can tell us what we need to tweak.
I think the above poster is trying to promote a site, its not even fully up and running, and i see nothing as to a fix for anything on the site, unless someone else see's something I dont
Inat said:
Here's a pic and video of the crash from the Tmo forums:
http://www.youtube.com/watch?v=sG2e8941fNc
I pretty much can't buy/move anything without this happening so it's rendered the game practically unplayable. Hopefully a dev here can tell us what we need to tweak.
Click to expand...
Click to collapse
The one thing i have done is every-time i buy something, or move something i save my game, for me it usually happens if it try to buy 3 things in a row, so i now buy, save and buy,save...and when it crashes at-least my last save has the prior thing i bought. Its not a great way to play, but its all i can figure out until someone smarter than me comes up with a fix.
I haven't event installed the game yet so sorry I am of no help. Though I still find it funny that they promote a game that does not work.
Sent from my Samsung Vibrant using XDA app
How to run GTA: Vice City and other heavy games pretty fast and smother with the Xperia Play
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video Settings
Resolution: 100%
Distance Detail: 28
Visual Effects: Medium(No notable differences with high)
Dynamic Shadows: OFF
Frame Limiter: OFF
Roms that GTA Vice City liked:
(Performance is very close in this roms)
Can work with other roms.
Kernel
LuPus GB v8 or v9 at 1.6GH with Virtuous and Sio. Virtuous is definitely the best governor and safe more battery.
Important thing: leave at least 150 MB free on your internal memory for play without lags.
Advanced tweaks for full speed
Access Lupus Menu via Terminal and choose: Option 5 [Tweak Options]
- Set Option [2] <SQLITE3 Optimization>.
- Set Option [8] <Micro SDcard speed tweak>. Put read cache at 1024 and save setting for apply it in every boot.
Game Version Tested: 1.02
After all, reboot and enjoy!
Screenshots with FPS Meter
Average FPS: 20
Note
In certain parts of the map may occur lags in game, that are not related with the power of the device, but by the bad Android port. The Android version is not developed by Rockstar Games, for that, was bad optimized.
20 fps well flawless means something different for me. 30 fps should be the absolute minimum to play really fluid.
GTA: SAN ANDREAS is locked at 25fps, and is very smoother. 20 is not perfect, but for me, is good enough. For Xplay, more than it, only reduce the resolution. However in various moments the game can get at 25FPS or more.
I am far from being an Android power user. I don't use mods, skins or launchers and prefer to stick to stock ROMs.
The farthest I go is to root my device, given the fact that some apps I need either work better with it or won't work at all without it.
So you have an idea, just the other day I posted I couldn't figure what "Greenify" was good for since, as I understood it, If we have to enter the app to hibernate/de-hibernate the target apps we might as well just launch and kill them, as needed, only to be kindly enlightened by another user about the fact of life that some apps do still run in the background, even after we've killed them.
...Pretty "tech challanged", right?
...but, coming from this "restricted" background, I do have a tip to share with you guys after having tried some online suggestions to deal with the relative "sluggishseness" and low Quadrant benchmarks I was faced with, after having migrated to JB XSP.
Apps took up to 3 seconds to launch and I was having this kind of values in Quadrant:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried a bunch of stuff to improve things up. I removed a series of apps I rarely used, even some system ones, using SystemApp Remover and inhibited others like MacroDroid. Still, no improvements.
Until...
Today, acting on tip read online, I went to "Settings" ---> "Developer Options" ---> (Activate) ---> "Drawing" and changed "Window animation Scale", "Transition Animation Scale" and "Animation Duration Scale" from the default values to 0.5x.
I got definite improvement in launch response, general "sluggishseness" with Quadrant values jumping to this:
Happy Puppy now
Hope this helps!
XK
I tried your suggestion and here are my results
Before change
4488
After change
3446
Restored to original settings
4146
Sorry for lack of images but I am unable to attach them.
In my case those settings did not improved the performance it actually decreased it. This might be on a case by case scenario but a good tip nonetheless
Sent from my GT-P6800 using xda premium
Note the huge jump in the I/O score. Seems out of character with the other devices.
"media" app. is consuming too much battery n running constantly even after force stopped. How to solve this issue..?
aries8 said:
"media" app. is consuming too much battery n running constantly even after force stopped. How to solve this issue..?
Click to expand...
Click to collapse
use this https://play.google.com/store/apps/...SwxLDEsImNvbS5hZGR6Lm1lZGlhc2Nhbm5lcnJvb3QiXQ..
or
https://play.google.com/store/apps/details?id=com.addz.mediascanner&feature=more_from_developer
to stop the media scanner