Discussion in 'Android Devices' started by jakax, Jul 7, 2010.
crash with my galaxo 1.6.3
The process android.process.acore
Download the Forums for Android™ app!
It worked for me. With pure galaxo 188.8.131.52 I had 25FPS in neocore, now with galaxo 184.108.40.206 and JIT I have 30FPS - 5FPS better and I havnt had any FC yet
First I created nandroid backup, than wipe, installed fresh galaxo 220.127.116.11, restored GAPPS, booted just to be sure everithing worked fine, rebooted back in recovery, fixed package permissions, applyed jakax.zip and booted in android
Hope it works for you
@livingcode, thanks it's work for me
With what app made the benchmark
I tried the same thing but than my Galaxo configuration wasnt working any more...
Galaxo config works now...booted before applying jakax.zip...
Neocore - on market
@528 without sound 33.6FPS
@528 with sound 29.0FPS
@614 without sound 33.4FPS
@614 with sound 28.7FPS
@710 without sound 33.6FPS
@710 with sound 28.8FPS
Odd that overclocking doesn't seem to be working.
Is anyone else having strange problems with TetherWifi, since installing JIT?
I tried the Dalvik with jit and it work
I had 4.82 MFLOPS with Linpack ( I didn't try with neocore but the phone is faster )
I used the recovery method after a clean installation ( fix permission after restore gapps, then apply any zip )
but there's a problem if we want to customise our phone after the installation of Dalvik
For ADW it's not a big problem, delete launcher.odex then install ADW
but if we want's to apply a theme like Androw ( from BEAUTY ) it's more difficult
because the theme change some system app like phone.apk
it mean that we have to change the odex file
but if we change an odex we have to rebuild all odex and it's a lots of work
Yes, So am I. It improves the Linpack result, but for the Neocore, it don't have any improvement for it..
how to solve the conflict with the theme...??
you need to rebuild all the odex in system/app and all the odex in system/framework
and it take several time =/
BEAUTY works on an adaptation of his theme, to make it applicable with the Dalvik with jit
By the way, can we do it by myself ( I mean to rebuild it)
yes but I don't know all the step to do it
you need to use baksmali/smali
to de-odex the file et rebuild a classes.dex file
and use dexopt-wrapper to rebuild the odex
but I don't know how to adapt it to the theme
ha ha! you are expert already! anyway, lets wait for BEAUTY to do it. Thanks!
No i'm really not an expert ^^"
I just learned some stuff with Drakaz Jakax and others
I hope that BEAUTY could do the work
Is this hack compatible with the Darksense theme?
Yes and No, It will work but since the theme modified a lot of system packages, all of these dont get improved by the JIT hack.
If only there is a fix for bloody camera so everyone could move to froyo with native JIT...
There's something I don't understand. I thought the Dalvik was the virtual machine, meaning it was the part which is running all the apps. Shouldn't every app be affected by a different Dalvik? Why would the version of, say, phone.apk, matter?
Its not the .apk which matter, it's the .odex
I'am not certain that the provided .odex from the jit hack, are working with a modified .apk
adw is a good example. since ppl deleted the launcher.odex it works without crashing.
odex are optimized dex files (each time you install an application dalvik generate one for your application in /data/dalvik-cache) which directly point to functions in other odex.
These files depend on each other. That means, if you change one odex on which another one depends on, you have to regenerate the odex, its dependencies are no more valid.
The odex files provided here contains the same functions/codes from the ones you already have. But as dalvik internals have changed from donut to froyo, they had be regenerated (old odex are no more compatible with this version of dalvik, of course dex files are).
These odex are framework, so all other odex files must be regenerated. Dalvik did this for all your applications at first boot after you installed this version (from the dex files in apks).
However if you have installed an odex file on your own (that dalvik can't regenerate because there is just an odex file and no dex file), you must regenerate it yourself. This would be the same if you upgraded framework odex with the old dalvik version.
I hope this helps.
Thanks, Jakax, for the very thorough reply. I understand now.
Must themes come with odex files? If the system generates them on it's own, couldn't I install galaxo->JIT->Theme and then wouldn't it create the correct odex files?
It should NOT work because the odex version will be incompatible.
This would work if the theme was provided as an apk or jar file with dex file.
odex files are generated from dex files and dalvik can't regenerate an odex with an odex (however this can be done using smali/baksmali which does: odex to dex and then you take the dex file and regenerate an odex)
Afaik themes are modified odex files from framework, so the author should get the one provided here and apply the modifications and redistribute it.
When you install a theme it change framework-res.apk and service.odex in system/framework, and some apk in system/app
but if an apk is changed you have to rebuild the odex because the odex is based on a sign of the apk
and if you rebuild one odex, you have to rebuild all
of course you can delete the odex, but if you do it Dalvik is useless
The problem with this version of Dalvik, it's a backport from FROYO
so I think that the system is not able to rebuild the odex alone
( I tried and it failed )
you have to do it manually