I've been working on getting jit working in the hero, but have hit a wall... I can get my legend ROM to boot and run the setup wizard fine, except that as soon as sense comes along, the entire phone crashes
I'm using the libdvm.so from the g1 thread (the one called something to do with donuts )
I've tried this on my own ROM, benhaam's legendary alpha and RaiderX303's Rom. So I've tried an odexed and unodexed ROM, but both behave the same...
I know the cdma guys got this working, anyone got any suggestions on what I've missed?
I just tried this on vanillain some weeks ago and it was working out of the box, but never got it working on any senseroms
Got it working on HeroDroid 0.3, but it force closes on unlocking by sliding (double-hitting menu button works) and on screen switching, again, by sliding (works if you use pinch-to-zoom out, then selecting the screen you want). Everything else works smooth and fast, but these two problems are an extreme pain in the ass
I've made a JIT build, but there are still too many stability issues to use it in production (everyday use).
Thanks all. Guess this is one for my vanilla roms in future...
Anyone heard any more about dalvik turbo (the commercial product)?
Supposedly, it is for OEMs and manufacturers. I expect the company wants their product licensed by phone manufacturers such as HTC and Motorola (that would be a simple means of collecting recurring revenue). Although it would be nice if they offered it in the Marketplace.
Let me say that the library could work on many ROMs on many Android Devices that use similar processors.
This library may or may not work, I didn't compile it only figured out that it works on CyanogenMOD based on 1.6. since you are able to get booted it seems you are good to go.
Since the update of CyanogenMOD 4.2.15.x the library loops FCs, checking further revealed that some dex files of /data/dalvik-cache were relocated to /cache/dalvik-cache (you can check his wiki page on moving dalvik-cache).
Haven't found where the script is doing this yet and haven't asked either but we have a work around that basically moves the dex files to either /data/dalvik-cache or /system/sd/dalvik-cache (for apps2sd users) remove the /cache/dalvik-cache folder and create a symbolic link there instead.
Code:
ln -s /data/dalvik-cache /cache/dalvik-cache
or
Code:
ln -s /system/sd/dalvik-cache /cache/dalvik-cache
or both
Code:
ln -s /system/sd/dalvik-cache /data/dalvik-cache
ln -s /system/sd/dalvik-cache /cache/dalvik-cache
replace /data/dalvik-cache with /system/sd/dalvic-cache or vice versa (you really just want to get them in one location where ever your dex files are located should be your target.)
FYI, clearing your dex files seems to resolve stability issues.
Good luck, let me know if it works via a PM.
BTW the hack is called "Dusted Donuts"
anon2122 said:
the one called something to do with donuts
Click to expand...
Click to collapse
The cause (I think) is that binding /cache/dalvik-cache to /data/dalvik-cache or to /dev/block/mmcblock4 is failling with this library or apps2sd is causing it.
anon2122 said:
I've been working on getting jit working in the hero, but have hit a wall... I can get my legend ROM to boot and run the setup wizard fine, except that as soon as sense comes along, the entire phone crashes
I'm using the libdvm.so from the g1 thread (the one called something to do with donuts )
I've tried this on my own ROM, benhaam's legendary alpha and RaiderX303's Rom. So I've tried an odexed and unodexed ROM, but both behave the same...
I know the cdma guys got this working, anyone got any suggestions on what I've missed?
Click to expand...
Click to collapse
licknuts said:
Let me say that the library could work on many ROMs on many Android Devices that use similar processors.
This library may or may not work, I didn't compile it only figured out that it works on CyanogenMOD based on 1.6. since you are able to get booted it seems you are good to go.
Since the update of CyanogenMOD 4.2.15.x the library loops FCs, checking further revealed that some dex files of /data/dalvik-cache were relocated to /cache/dalvik-cache (you can check his wiki page on moving dalvik-cache).
Haven't found where the script is doing this yet and haven't asked either but we have a work around that basically moves the dex files to either /data/dalvik-cache or /system/sd/dalvik-cache (for apps2sd users) remove the /cache/dalvik-cache folder and create a symbolic link there instead.
Code:
ln -s /data/dalvik-cache /cache/dalvik-cache
or
Code:
ln -s /system/sd/dalvik-cache /cache/dalvik-cache
or both
Code:
ln -s /system/sd/dalvik-cache /data/dalvik-cache
ln -s /system/sd/dalvik-cache /cache/dalvik-cache
replace /data/dalvik-cache with /system/sd/dalvic-cache or vice versa (you really just want to get them in one location where ever your dex files are located should be your target.)
FYI, clearing your dex files seems to resolve stability issues.
Good luck, let me know if it works via a PM.
BTW the hack is called "Dusted Donuts"
The cause (I think) is that binding /cache/dalvik-cache to /data/dalvik-cache or to /dev/block/mmcblock4 is failling with this library or apps2sd is causing it.
Click to expand...
Click to collapse
Cheers for the info. I will take a look tonight on a build without A2SD (I've got one handy for this kind of thing...)
So, to confirm, I could quickly test this by pushing the libdvm.so file to the usual place (on a ROM with no A2SD) immediately after flashing it (ie. not booted after installing the ROM)
That should then, as far as I understand, do it. I take it that if I wipe dalvik cache before the install of the test ROM, there is no need to re-wipe the dalvik cache (no dex files should have been created)?
Then, I do 'ln -s /data/dalvik-cache /cache/dalvik-cache' to pop a redirect on the data folder?
Please let me know if I'm reading this right before I go and try it again, as I'd hate to try it and find out I was doing it wrong...
Cheers
just wanted to say, would be nice if you could keep the updates coming to this thread, as i am following it as well. just because of the reference to pm. thanks
kendong2 said:
just wanted to say, would be nice if you could keep the updates coming to this thread, as i am following it as well. just because of the reference to pm. thanks
Click to expand...
Click to collapse
No worries. I'll post anything on here, as I'm sure it's not just us that want to know if it works. I'm not doing anything hero related tonight, but maybe friday...
Must do some other work
It's Sense that's making issues..
rolle3k said:
It's Sense that's making issues..
Click to expand...
Click to collapse
Yup. I've not got time to flash tonight, but have you looked at some of the stuff posted by 'licknuts' on page 1? He suggests a couple of commands that should keep the optimised dex files in the right place using symlinks.
anon2122 said:
Yup. I've not got time to flash tonight, but have you looked at some of the stuff posted by 'licknuts' on page 1? He suggests a couple of commands that should keep the optimised dex files in the right place using symlinks.
Click to expand...
Click to collapse
Well, I was experimenting with that dalvik library on my own. Of course you have to clear the dalvik cache, it's just Sense that does not like to operate with jit enabled.
You can use jit without problems if you disable Sense and use androids default lockscreen, which is in my opinion much cooler anyway.
Interesting. How is it, stability-wise in vanilla config?
(I am considering releasing an 'add-on' unofficial update.zip for a couple of roms to make them vanilla with jit, but only if its really stable. I was thinking villain 3.4 and legendary 1.2
As small incremental updates that just remove the rosie & lockscreen and push the new libdvm.
Open question @all:
Any views in this? Would you want this as an add-on to existing roms if stable? Would you usr it? Suggestions welcome. Obviously this is just an idea. Would need to test and consult devs first...
anon2122 said:
Interesting. How is it, stability-wise in vanilla config?
(I am considering releasing an 'add-on' unofficial update.zip for a couple of roms to make them vanilla with jit, but only if its really stable. I was thinking villain 3.4 and legendary 1.2
As small incremental updates that just remove the rosie & lockscreen and push the new libdvm.
Open question @all:
Any views in this? Would you want this as an add-on to existing roms if stable? Would you usr it? Suggestions welcome. Obviously this is just an idea. Would need to test and consult devs first...
Click to expand...
Click to collapse
I would def. use it. I was playing around with it (managed it to open some applications/browse) and it was very fast. You can feel how much better it works.
the work around I posted is really catered specifically for CyanogenMOD 4.2.15.x based with Android 1.6 with some eclair bits thrown in but could work on older Android versions. Our work around was to deal with dex files being in two locations and it seemed that binding the two directories would break caused by the library or apps2sd script.
If you know where you dex files are for a particular ROM are located , easiest to try and put them in one location IF THEY ARE SPLIT up and create a symbolic link pointing to the single location, it might not be needed at all, I just don't have a Hero to test with and our Hero ROMs are brutal to run run with our G1s because of lack of memeory.
As for a Hero ROM if the dex files are in one location I think it should be good. Set the permissions, owner and group on the file.
##back up your original file incase it don't workout
cp /system/lib/libdvm.so /sdcard/dusted-donuts/bak/
## install from where ever you extracted from
cp -f /sdcard/dusted-donuts/lib/libdvm.so /system/lib/
## set owner permissions
chown 0:0 /system/lib/libdvm.so
chmod 644 /system/lib/libdvm.so
##only make a symbolic link if you had to move dex files from a different location..
ln -s /data/dalvik-cache /sdcard/sd/dalvik-cache
just an example.
This may be your best option for older Android builds.
Grab the vmlibs.zip extract the files and don't use the build.prop and copy the additional files as so back up your original files first incase it don't work.
assuming you extracted the files to a newly created /sdcard/vmlibs directory
cp -f /sdcard/vmlibs/bin/dalvikvm /system/bin/
cp -f /sdcard/vmlibs/libdvm.so /system/lib/
cp -f /sdcard/vmlibs/libdhelper.so /system/lib/
rm -f /data/dalvik-cache/*
Booting is slow like 5-10 minutes and if previously your tried the libdvm.so file and got the device to but and FCs, you may just need to find and additional work around.
these commands are for recovery console and terminal. might be a typos in there.
anon2122 said:
Cheers for the info. I will take a look tonight on a build without A2SD (I've got one handy for this kind of thing...)
So, to confirm, I could quickly test this by pushing the libdvm.so file to the usual place (on a ROM with no A2SD) immediately after flashing it (ie. not booted after installing the ROM)
That should then, as far as I understand, do it. I take it that if I wipe dalvik cache before the install of the test ROM, there is no need to re-wipe the dalvik cache (no dex files should have been created)?
Then, I do 'ln -s /data/dalvik-cache /cache/dalvik-cache' to pop a redirect on the data folder?
Please let me know if I'm reading this right before I go and try it again, as I'd hate to try it and find out I was doing it wrong...
Cheers
Click to expand...
Click to collapse
Been playing around with it now.
I had to remove the Hero Lockscreen by doing the following
Code:
# adb remount
# adb shell rm system/app/HtcLockScreen.apk
And I also had to disable Sense.
Once you did that, you can use JIT altho you will lack of the Sense Home screen.
Hmm, nice job. Give this this a try for the screen lock, have had similar issues with varrying apps and this seems to fix them especially when trying various Launcher.apk replacements. Really looking to clear the app settings found in /data/data somewhere the name does not have to match the app name so you may need to hunt for it in /data/data.
mount data for read write and backup your HtcLockScreen.apk to sdcard somwhere.
Code:
******optional**********
killall android.process.acore
***********************
rm -f /system/app/HtcLockScreen.apk
rm -f /data/dalvik-cache/*HtcLockScreen*
rm -fr /data/data/*HtcLockScreen*
cp -f /sdcard/backup/app/HtcLockScreen.apk /system/app/
chown 0:0 /system/app/HtcLockScreen.apk
chmod 644 /system/app/HtcLockScreen.apk
reboot
/sdcard/backup/app (replace the path with the location of a backup of the file.)
rolle3k said:
Been playing around with it now.
I had to remove the Hero Lockscreen by doing the following
Code:
# adb remount
# adb shell rm system/app/HtcLockScreen.apk
And I also had to disable Sense.
Once you did that, you can use JIT altho you will lack of the Sense Home screen.
Click to expand...
Click to collapse
Installed libdvm.so on aHero 0.4, a vanilla rom, everything works fine.
UPDATE: Another good news!! I'm currently testing an odexed version and so far it's holding very well with reboots, battery pulls and resets...I think this is because less data is written to dalvik-cache when it is odexed LOOKS LIKE WE ARE GETTING CLOSER TO A SOLUTION
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I've got some good news! It seems like I got the solution for data corruption on restarts, reboot and resets...I've done 5 reboots, 2 resets and I have not lost a single app on my Launcher. Not a single FC. This is with installation of System and Data on NAND with my data loaded with apps and widgets full on every screen (with pics, music, youtube, etc). I am also using l1q1d 11-27 kernel with my All Language ROM.
Here is my solution.
Since l1q1d put the cache on RAM, opening logcat shows that data written to our NAND is done more by "dalvik-cache" so I decided to move the "dalvik-cache to SD card with the following commands steps. Before I begin, I'll warn you that all your apps should be installed and updated coz if you do this you won't be able to install or update your any of your apps. Here it is:
Open up terminal
1. Type su
2. mkdir /sdcard/dalvik-cache
3. chmod 777 /sdcard/dalvik-cache
4. cp /data/dalvik-cache/* /sdcard/dalvik-cache
5. rm -rf /data/dalvik-cache
6 ln -s /sdcard/dalvik-cache /data/dalvik-cache
7. echo x > /data/.dalvikcache
LMK how it goes for you.
I am using l1q1d's latest kernel 11-27 with my All Language ROM.
Make that 5 reboots and 5 resets and 2 battery pull...still going strong but need to sleep now..
I don't doubt that this will help as it is the main directory which gets written to on the /data partition and can cause cycling and reboots if it gets corrupted or the phone is reset whilst it is still being written to but putting it on the sd card isn't an ideal solution for me. The reason i have data and system on NAND is so that i can unmount my sd card and have the phe unning as fast as possible wthout the bottlenecks caused by the card. I'm not sure there is much more benefit to this then just putting data on SD to start with, however, it will be worth looking into dalvik-cache and trying to get it more stable on NAND so good work
scooter1556 said:
I don't doubt that this will help as it is the main directory which gets written to on the /data partition and can cause cycling and reboots if it gets corrupted or the phone is reset whilst it is still being written to but putting it on the sd card isn't an ideal solution for me. The reason i have data and system on NAND is so that i can unmount my sd card and have the phe unning as fast as possible wthout the bottlenecks caused by the card. I'm not sure there is much more benefit to this then just putting data on SD to start with, however, it will be worth looking into dalvik-cache and trying to get it more stable on NAND so good work
Click to expand...
Click to collapse
Indeed..Looks like the inability to install and update makes data install to SD a better option. Regarding speed, I didn't notice any difference while having the dalvik-cache on SD, but I have a class 6 SD so that could be why. Looks like simply deleting dalvik-cache fixes everything for now. Re: making dalvik-cache more stable on NAND, do you think this is better done via kernel?
BTW, you think an Odex build would be better?
clemsyn said:
Indeed..Looks like the inability to install and update makes data install to SD a better option. Regarding speed, I didn't notice any difference while having the dalvik-cache on SD, but I have a class 6 SD so that could be why. Looks like simply deleting dalvik-cache fixes everything for now. Re: making dalvik-cache more stable on NAND, do you think this is better done via kernel?
BTW, you think an Odex build would be better?
Click to expand...
Click to collapse
How about... uhm....
mount a file for the dalvik cache like we used to mount a ext2 file ?
-o loop iirc..
BTW!!! chown 777 or chmod 777 ??
daedric said:
How about... uhm....
mount a file for the dalvik cache like we used to mount a ext2 file ?
-o loop iirc..
BTW!!! chown 777 or chmod 777 ??
Click to expand...
Click to collapse
It's chmod 777...Oopps looks like I made a typo. Thanks Daedric
I think I got a better solution that this. So far I have 5 reboots and 3 battery pulls and so far no FC. It seems like an ODEX'ed version is better. I think with the odex, there are less data written to dalvik-cache so it's more stable on reboots or resets... I'll continue testing but with a non-odex, I would get errors with loaded data and widgets. So far so good with odex'd. Looks like we are getting closer
I have been having an issue with not being able to update the Maps app (insuficient space error) in another thread but after trying a few options have now managed to kill the market !
After trying to clear data cache etc I reflashed the ROM (Redux 1.2) to no avail.
I read about a possible cure through terminal monitor of moving the market cache to SD via terminal which I followed using :-
mount -o remount,rw /
rmdir /cache
mkdir -p /mnt/sdcard/cache
ln -sf /mnt/sdcard/cache
mount -o remount,ro /
This failed ( I didnt note the error message unfortunately) & now when accessing the market Downloading an app fails midway through the process.
Does anyone know how I can reverse this process ?
I don't know if this will help at all, but I was having a problem with the Market as well. I had just installed a new rom, but was getting error messages saying there wasn't enough space to install. I just ended up backing up my SD card, formatting it, and starting over. That solved my problem, I don't know if it'll help you with yours.
Sent from my HTC Desire CDMA using XDA App
Try downloading marketfix from the Android market. Had the same problem, this fixed it.
Sent from my HTC Desire using xda premium
A solution similar to your attempt:
http://forums.miuiandroid.com/showt...e-to-install-large-apps-like-MAPS-from-market
I know it's for MIUI, but it works for other roms as well.
Hello there,
i want to install Miui on my Desire.
I want to use the Oxygen Hboot table because i think its faster than installing any app2sd script.
I deleted some apps and stuff i dont need so that the rom fits in the Hboot Table.
Everything works right now,
but i have one big Problem:
I can not install any big app from the Market. (larger than 4gb)
I read somewhere, that i have to move the Download cache to SD card.
So i installed the app s2e and moved the cache.
But it still does not work?
Can anyone help me?
Thx
Open your terminal app
su
mkdir /mnt/sdcard/oxygen/market-cache
cd /cache
mv download download.bak
ln -s /mnt/sdcard/oxygen/market-cache download
ls -ahl
Click to expand...
Click to collapse
Now try and install the apps via market again and it should now be working.
Thank you so much!
It worked.
You only have to change line2 with line1
justnils said:
Thank you so much!
It worked.
You only have to change line2 with line1
Click to expand...
Click to collapse
My bad, ftfy
Hi, I'm a noob not only to Android but to Linux either. I'm aware this is probably a very old question, but I can't find a topic in wich is explained how to do this manually.
I'm using amarullz a2sd on Sandvold ICS beta 0.6.1.1, and it works fine, like most of you know, is magic works this way:
- system apps and data on nand
- apps and data on ext4
- all dalvik on nand.
So I get lot of space and very little lag.
The problem is: dalvik grows, and grows very fast, and worst of all, the system can't understand why at some point the internal memory have lot of space but it can't ever save the temp install file, or create the dalvik for a new app.
All this problems flush into the famigerate "invalid package file" error, for whose everyone has a different solution.
So we get: dalvik saturate nand = Android go crazy = users go crazy and make any sort of assertion on how to solve this (someone suggest a full wipe everytime this happen XD ).
The solution may be simple and obvious to all of you, but I'm a noob so let's pretend this is a great step for humanity: insert manually a script to put the dalvik too on ext4, on top of the pre-esistent amarullz one.
I googled some time and I come to this script that to me seems the best way:
Code:
su
cp -pr /data/dalvik-cache /system/sd
rm -r /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
(Ok I'm aware the cp is not necessary, but this way I have not to bother about rains of FC until I reboot and system recreate dex files).
That seems to do the magic... but here my two questions:
1) Simple matter: how to make this permanent on reboot? I have to insert it in a text file in init.d? the number on the file name count for the order of execution in respect to other scripts?
2) Not so simple (for me): why "/system/sd" ? I thought the path to the ext4 is "/sd-ext", so the correct dir is not something like "/sd-ext/my-dalvik" ??
If this is right, the correct script must be this way:
Code:
su
cp -pr /data/dalvik-cache /sd-ext/my-dalvik
rm -r /data/dalvik-cache
ln -s /sd-ext/my-dalvik /data/dalvik-cache
(Clearly the cp and rm parts will not be present in the boot script).
Am I right?
DISCLAIMER:
- I'm not discussing if amarullz is good or bad, every post on this subject will be ignored. I like it, I just want to change this thing.
- Posts that invite me to not install tons of apps and live a life of abnegation will be ignored as well.
- Sorry for my english
- Sorry if I'm verbose: I just want to be clear on the explanation.