Related
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.
Hey Devs,
As you may have noticed, I recently released a ROM with 276 MB free space on /data.
I accomplished this by using the MTD hack discovered by firerat and lbcoder.
It changes the kernel cmdline and includes addresses where the partitions are located.
This way, we are able to change the sizes.
That's exactly what I did.
The bad thing is that you need a recovery with a cmdline, which matches the ROM's boot.img's one!
So, a user needs to flash a recovery first and can then flash the ROM after a reboot into the new recovery.
Now, if the user wants to change his ROM to something else, he will need to revert the recovery.
It would be a lot easier if some other developers here would be interested in the MTD hack, so there is no need to revert.
I hope that some other developers will jump on the bandwagon now.
Here is the command I use for creating boot.img's, with modified partition sizes:
Code:
mkbootimg --kernel kernel --ramdisk ramdisk --cmdline 'mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)' -o boot.img --base 0x19200000
This reduces the /cache partition to 4 MB and makes /data as big as possible (the space which is left).
Now, the Market would normally fail to download huge APKs, because /cache is so small.
The problem can be easily solved by symlinking /cache to /data/cache and mounting the native cache partition on /dev/cache.
This can be done even without modifying the ramdisk, just do it in a script which runs before the Android frameworks start, like a2sd scripts.
Here are the necessary commands:
Code:
mount -o rw,remount /
umount /cache
rm -rf /cache
mkdir /data/cache
ln -s /data/cache /cache
mkdir /dev/cache
mount /dev/block/mtdblock4 /dev/cache
chmod 777 /data/cache
mount -o ro,remount /
Regarding the recovery:
Klothius from the Sapphire section created an update.zip which automatically patches the current recovery to use the provided cmdline.
You can find it here and include it in your instructions:
http://www.megaupload.com/?d=FY6CBAEE
I hope this little documentation will help you and will make you interested in doing this for your ROM.
Nice work. We'll look at implementing this into the next FroydVillain release. My only reservation would be keeping a wee bit more space on /cache than 4MB since our OTA app uses it. We could always hack it to use a dir on /data I suppose.
Hacre said:
Nice work. We'll look at implementing this into the next FroydVillain release. My only reservation would be keeping a wee bit more space on /cache than 4MB since our OTA app uses it. We could always hack it to use a dir on /data I suppose.
Click to expand...
Click to collapse
Yea, that would be better.. The whole purpose of this thread is to make things more compatible, means same cmdline Also you wll need to write the instructions for the recovery to /dev/cache then, keep that in mind
I will also add the RecoveryMod and an explanation in the documentation now.
I think the limitation of needing to switch recovery when changing ROMs is quite bothersome. Is there anyway we can get a recovery which supports both modes?
erasmux said:
I think the limitation of needing to switch recovery when changing ROMs is quite bothersome. Is there anyway we can get a recovery which supports both modes?
Click to expand...
Click to collapse
Sure, it can be done, but that would take a looot of work!
maxisma said:
Sure, it can be done, but that would take a looot of work!
Click to expand...
Click to collapse
More than I think it would be worth, to be honest. It'd make more sense for all the ROM developers to pull together on this and just make it a fact that we're giving more space to data, since it also eliminates the need to create fancy hacks moving dalvik to cache or to sdcard or splitting it between 2-3 file systems to cater for people who like to have the entire Android Market on their phone.
This has my/Villain's full support Maxisma, it makes perfect sense. Might I suggest you PM the other ROM developers here, or at least the popular ones like Fusion etc, and refer them to this thread so we can all work together on it.
Now that it's safe to assume that HTC have pretty much ditched the Hero, it makes sense for us to fix/improve -everything- including partition layout. There is a lot of wasted space in /cache that only gets used if a ROM developer starts fudging about with where dalvik lives, but /cache isn't quite big enough to completely migrate dalvik cache to for people who like to have a lot of apps.
Is there any more work on this? :d
shinyfong said:
Is there any more work on this? :d
Click to expand...
Click to collapse
I believe maxisma stopped work on it due to it breaking something or causing something not to work. I think he mentioned it in his Rom thread...
pulser_g2 said:
I believe maxisma stopped work on it due to it breaking something or causing something not to work. I think he mentioned it in his Rom thread...
Click to expand...
Click to collapse
It was me who broke it ;-) I accdidentally booted with a different mtd layout and thus killed all my data.
This method is perfectly fine though.
But I switched to a Nexus and I don't have a Hero anymore.
In a lot of the custom roms threads I see that people are always asking the cooks to update the system apps as soon as a new one is released.
Rather than us users constantly hassling the cooks to do this, could somebody post an 'idiots' guide how to update the system apps ourselves?
I have seen a few threads about how to remove apps using adb, but none on how to update them.
Any help would be appreciated, not just by the users, but probably by the overworked cooks too
Cheers.
EDIT: by this I mean a way to update the apk in the system folder rather than the date to save space on the phones memory.
One way is to open the market and click on the 'downloads' link at the top and it will give you a list of installed apps and the ones highlighted in red have updates.
Another way is to search the market or a free app called 'aTrackDog' which will check all your apps for updates.
Thanks, but that is not what I meant. I should have made it clearer in my question.
What I want is this: a way to update the applications so that the updated apk goes into the system folder rather than the data folder. That way the update doesn't take up any more of the precious space on my phone.
I'll edit the OP to show this.
But thanks anyway for your help.
Don't you mean the fact that certain apps included in roms cant be updated. Only possible by flashing an updated version of that rom.
Wrong section.
prodygee said:
Don't you mean the fact that certain apps included in roms cant be updated. Only possible by flashing an updated version of that rom.
Click to expand...
Click to collapse
No, that's not true. Often when a cook produces their own rom they will release an "Update pack" when a system app has been updated (such as Flash or Maps). For an example, see here under 'updated system apps':
http://forum.xda-developers.com/showthread.php?t=773997
What I am asking for is if anybody knows how to use adb to update apps on the system partition. When updating from the market a the update takes place on the data folder, not the system one.
Ta.
scutworker said:
No, that's not true. Often when a cook produces their own rom they will release an "Update pack" when a system app has been updated (such as Flash or Maps). For an example, see here under 'updated system apps':
http://forum.xda-developers.com/showthread.php?t=773997
What I am asking for is if anybody knows how to use adb to update apps on the system partition. When updating from the market a the update takes place on the data folder, not the system one.
Ta.
Click to expand...
Click to collapse
do you mean by example
Code:
adb push Vending.apk /system/app
adb reboot
TomLeeDesire said:
do you mean by example
Code:
adb push Vending.apk /system/app
adb reboot
Click to expand...
Click to collapse
That is something like it. What I want is a guide to what to do to update these apps when an update is out in the market place. Something like being able to update the app from the market, but then move the new apk to the system folder so to save space on data.
Thing is, if you're using a cooked ROM you're likely to be using A2SD+ which makes the need to not have system updates redundant as you've got your EXT partition. The other way would just be to edit the original ZIP file and reflash the ROM without a wipe
EddyOS said:
Thing is, if you're using a cooked ROM you're likely to be using A2SD+ which makes the need to not have system updates redundant as you've got your EXT partition. The other way would just be to edit the original ZIP file and reflash the ROM without a wipe
Click to expand...
Click to collapse
That is not entirely true, even though I sport A2SD+ (and it's 1/3 free) my /data is always begging for room... I'm always at the 15MB-free-limit.
Then you've either got a LOT of apps storing data or something's not right
Small dirty 0.1beta guide
I'll use teppic's update zip as example (hope he doesn't mind), sample of his updateapps.zip can be found in this thread -> http://forum.xda-developers.com/showthread.php?t=773997
1. Install the update from Market, then open Appmonster and backup it on SD. After that, uninstall the update, to free up space.
2. Open the update.zip with WinRar (don't unpack it), you'll see 2 folders
META-INF
system
Open the inside of META-INF till you get to update-script and open it for editing, here's the example:
Code:
show_progress 0.1 0
delete SYSTEM:app/YouTube.apk
delete SYSTEM:app/YouTube.odex
delete SYSTEM:app/Facebook.apk
delete SYSTEM:app/Facebook.odex
delete_recursive DATA:data/com.android.vending
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
Replace/add/remove .apk's (you can add .apk without .odex) in this list, as those commands will delete existing apps from /system/app on phone
The rest of the script will copy the content of the other folder you saw before (system with subfolder app), so you want to add/remove apk's you like to there. Remember to use WinRar's function to add the file to archive, everything done here's is inside of the archive. When you're done, save the update-script, check everything again and close WinRar.
3. Flash the zip ;]
or do it manually:
h_ttp://forum.cyanogenmod.com/topic/8067-how-to-manually-update-system-apps/
EddyOS said:
Then you've either got a LOT of apps storing data or something's not right
Click to expand...
Click to collapse
I do think A LOT fits (about 300 apps installed)...
That's exactly what I wanted.
Thanks for the help, everybody.
Does this work on a Rooted (Unrevoked) phone with HTC's Original Froyo?
- I've been following teppic74's thread for some time now, and for every app that get an updated I get closer to flashing his ROM... but if I can just update my apps I wouldn't have to go through the process of reinstalling everything else after...
gosa said:
Does this work on a Rooted (Unrevoked) phone with HTC's Original Froyo?
- I've been following teppic74's thread for some time now, and for every app that get an updated I get closer to flashing his ROM... but if I can just update my apps I wouldn't have to go through the process of reinstalling everything else after...
Click to expand...
Click to collapse
Sure thing.
thed0g said:
Sure thing.
Click to expand...
Click to collapse
Nice!
That means my weekend is saved, I 'm gonna give myself some updates!
- Thanks!
One thing...if using the push and pull commands in adb to move the apk files to the system partition, what happens to the .odex files? Do you move them as well?
scutworker said:
One thing...if using the push and pull commands in adb to move the apk files to the system partition, what happens to the .odex files? Do you move them as well?
Click to expand...
Click to collapse
.odex files are only on some custom rom's, you probably dont have them.
Hello again...
I kind of never got around to doing this last weekend - both because lack of time but also because the more I read the more worries I have. (Don't know when I lost my "gung ho" attitude, but age seems to turn me into a chicken...)
Anyway - I wanted to ask one important question.
How do I keep an eye on the space I have available for updating my apps? What if the updates are so much larger than the apps I'm replacing, what will happen then?
I read in teppic74's thread that he recommended some adjustments to save space, but how do I know what I have to "play" with? Is there a good app to read available space in "system"?
Thanks in advance,
gosa
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
The past few days I've been having problems with the past store, wonder if anyone can help, google search and xda search not turning up much help...
I had an update for Sygic, first it gave that it couldn't load to SD or USB storage, then it would download and hang without installing. Sygic support recommends deleting some settings files from the app, still awaiting confirmation on one point.
In several attempts to download and update various other apps I am getting insufficient storage space (app2SD should be working... ran through the installation procedures again last night, and left it overnight) and download that just hang and won't install. Erased play data to no effect, uninstall FB app to try and work around it, now I can't download it, just hangs.... there goes my social life
Ready to factory reset if needed, any help before I do?
Sent from my HTC Desire using xda premium
Re: App2SD, play store, problems..
App 2 sd probably is working, but I'm guessing your dalvik cache is still on the phone and needs moving to the card.
Sent from my HTC Desire using Tapatalk 2
Re: App2SD, play store, problems..
Do I need to move dalvick with recovery, or a script?
edit- another search led me to S2E, but if i look for it on play, its not compatible.... still dont know if i could download it anyway......
Sent from my HTC Desire using xda premium
How to move the data folder or dalvik-cache:
Sometimes this is also described by the term "A2SD+". Some Custom ROMs support it (e.g. MoDaCo Custom Froyo, according to the comparison table). So if you use MoDaCo Custom Froyo and have A2SD enabled (by having created the ext2 partition on the sd card as explained in section A), then also the dalvik-cache will be moved to the sd card.
However you also can do it by yourself if you already have A2SD enabled (this is necessary, as well as root access).
start the terminal and type (without |):
in order to move /data/data:
| su
| cp -pr /data/data /system/sd
| rm -r /data/data
| ln -s /system/sd/data /data/data
Be careful! you will loose all your application data if this fails. however usually the default data can be restored by android using the .apk file. I recommend creating a Titanium Backup before doing this (as well as an nandroid backup).
and in order to move dalvik-cache:
| su
| cp -pr /data/dalvik-cache /system/sd
| rm -r /data/dalvik-cache
| ln -s /system/sd/dalvik-cache /data/dalvik-cache
If the dalvik-cache should get lost, it's not such a problem because it will be easily recreated on reboot (taking some minutes the first time). However, the dir /data/dalvik-cache should exist and be accessible for the system (or the according symlinked dir).
Caution! If you do this, most of the apps or even the whole system won't work if the whole SD card is ejected / unmounted!
this any use? not sure i like the last line though......
http://forum.xda-developers.com/showthread.php?t=1342387
found this will post on his thread later and await reply, still dont understand why the downloads are hanging though, anyone?
you can use int2ext
https://play.google.com/store/apps/details?id=eu.codlab.int2ext
this app or script via te?
edit- wiping data now, enabling app2sd on JV-JB, and when activating one permission is to move dalvik, getting confused now....
SOLVED- kinda complete wipe and re-flash.........
Skivit said:
SOLVED- kinda complete wipe and re-flash.........
Click to expand...
Click to collapse
That was my first thought
Aye, was trying to avoid it, maybe learn something in the meantime, but I was going round in circles. Funny that when I tried mount2sd, it gave a warning, must have been something with the script. Seems to have settled down, just wondering why Play store was acting up too...
Sent from my HTC Desire using xda premium
Skivit said:
Aye, was trying to avoid it, maybe learn something in the meantime, but I was going round in circles. Funny that when I tried mount2sd, it gave a warning, must have been something with the script. Seems to have settled down, just wondering why Play store was acting up too...
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Dunno what kind of update they did back in september, but since then many people noticed that something is wrong. Must be that OAuth2 they implement.
I'll Google that one later
Sent from my HTC Desire using xda premium