Try cpu=dynamic

For some (most) application this is simply not working, the Program crashes. No Idea. As dynamic is only working with i386 it is not a really option.
I try to build it with raspberry as mini (DOS)Arcade Cabinet

well that information could have been useful 😀
Anyway there is somewhere been done a dynamic core for ARM and you should also go for the SVN of Dosbox. Also if sluggish, *less* cycles could be of help. If the rpi is struggling (monitor its cpu usage) more cycles means more struggle, not less.

Wh1sper wrote:

Epic Pinball Android for example seems a bit laggy

If you are using Raspberry it may to be slow for DOSBox, so it's good to find builds wich support dynamic core

blocksize=256 - this will reduce response time
cycles=10000 - doubtful Pinball needs more. maybe even less will be enough

to reduce CPU load:
rate=22050
oplemu=fast
oplrate=22050
pcrate=22050

Thank you for the tips.
But I'm still in developing at my Laptop, here is the delay between keypress and action in pinball.
I wonder why this happen. Epic pinball is written in assembly, it should be fast enough in emulation.
Or could it be the keyb gr?
hhm I'm trying

Wh1sper wrote:

Or could it be the keyb gr?

The game's shareware version in Windows DB 0.74 on default settings with cycles=5000 works without noticable delays or other issues. In case your CPU is faster than P3 1000, there should not be problems with performance (with core=dynamic, normal mode is several times slower). You may try other DB port, if the default settings with modifications above will not help.