Related
Like the title says, does damageless' sprintupdate2.zip have apps2sd enabled? I flashed it and all my apps appear to be installing on the device memory. What am I missing here? I wiped everything before flashing and partitioned my SD card.
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Kcarpenter said:
I think sprintupdate2.zip was strictly the sprint update + root + busybox - some bloatware.
I wouldn't think he enabled apps2sd on it.
Click to expand...
Click to collapse
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
chapaj said:
Okay, follow up question: what's the best method for enabling apps2sd on Hero 2.1?
Click to expand...
Click to collapse
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Kcarpenter said:
Well, most roms have it built in to the boot up scripts....
You would have to pull that script from one of the roms and put it on yours.
Then you would have to have your SDcard setup with an EXT2/3 partition. This can be done from recovery.
Click to expand...
Click to collapse
I've got the partitions ready to go. I just don't know how to pull the script. Does anyone have a guide on how to do this?
Konikub said:
Bust open Damage 2.08.1 and grab his Boot.img and his a2sd script in /system/bin.....then put them in the ROM you are using.
Click to expand...
Click to collapse
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
chapaj said:
Okay, I've added those the sprintupdate2.zip that I'm using. I can then flash that over my existing ROM without wiping?
Click to expand...
Click to collapse
Shouldn't hurt.
Kcarpenter said:
Shouldn't hurt.
Click to expand...
Click to collapse
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
chapaj said:
That didn't work. I get:
E:Wrong digest:
boot.img
E:Verification failed
Installation aborted.
Click to expand...
Click to collapse
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Kcarpenter said:
Did you resign the zip after you modified it?
use fresh kitchen or avabox
Click to expand...
Click to collapse
I had no idea i had to do that. I'm researching how to do that now. I don't suppose anyone could do it and throw up here as an attachment?
Post it up.
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
tkirton said:
The first SprintUpdate that Damage released, I put the A2SD add-ons in it. If anyone wants me to do it again, let me know and I'll go do it.
EDIT: That was the SprintUpdate2 that I put the add-ons to. http://www.darktremor.info/files/2.1/sprintstock-21-a2sd-signed.zip
Click to expand...
Click to collapse
I dl'd tkirktons darktremor and followed steps in his discussion thread posted above and worked perfectly. Thanks tkirkton!
Quick question. Can the New OC kernel be added to the damageless sprint leaked rom?
just wondering what everyone on here is doing? im on the new cwm.
musclehead84 said:
just wondering what everyone on here is doing? im on the new cwm.
Click to expand...
Click to collapse
your title is conflictual because edify are just the scripts which is what gingerbread and all newer phones will use to install packages. the scripts before were called amend scripts. then ext 4 and i guess you mean stock rfs are the file systems. so all devs SHOULD be developing with edify going forward..........no as far with the ext 4 goes they will probably stay with that unless their is some critical reason not to.
All current clockworks support edify. Clockwork 3 removed amend support like google did with the gingerbread recovery.
Currently, I'm on ext4 with cwm 2.5.1.0 and 2.5.1.2. I don't have a need to move to the new clockwork, yet.
I know all cwm supports Edify scripts. I was just seeing what everyone was doing. Your reading into it to much. I know some people are staying with Rfs, some did the ext4 and then some flashed the new cwm.I guess I could have worded it differently. Thanks for your responses though.
NOTE: This is a work in progress. Please send remarks/comments with additional information you want to see added to this thread.
So what is root exactly?
In the unix/linux world root is the super user that can do anything on the system. In the windows world the user is called Administrator. See here for a more detailed explanation.
Why should I need/want it?
This is a more difficult question than many people think. In the android world every app runs in its own sandbox, meaning every app can access it's own data and call the system to provide access to system resources but it can't access data from another app. This provides a very good protection against malware etc.....BUT it has disadvantages.
The first disadvantage that comes to mind is the possibility to backup the settings and private data of an app.
The second disadvantage is that for app A to be able to use the data from app B the app B must publish a programmers interface to it's data so the app A can access the data.
Both disadvantages can be overcome with root access.
root access can also overcome some limitations that are build in by the company (in this case Archos) that provided the software that runs on your device.
Read below for examples of what can be done.
Is it dangerous to have root?
The answer to that question is yes if you don't know what you are doing.
If you use root to execute command think twice before executing it. If you are following instructions always try to follow instructions to the letter. If you are not sure about something ask someone who knows about the subject.
If you use apps that require root always read the instructions and if you're not sure try to read about the program in question.
PS: Even the competent root user can make mistakes. I've nuke a few systems in my early years and will never make that mistake twice.
What is su and SuperUser.apk and how do they work?
The su binary is used by other apps to get root access. The SuperUser.apk is a front end to give the user some control over what app can have root.
Whenever the su binary is used by an app it will call upon the SuperUser.apk to pop up a question to Allow/Deny access to that app.
How do I root my gen8 device?
Good now we can get our hands dirty and go to work rooting our device.
At the moment there are 3 different ways to root your device with different levels of control and possibilities
Archangel one-click (temporary) root
chulri's root
UrukDroid
Archangel one-click (temporary) root for firmware 2.0.71, 2.1.02, 2.1.03, 2.1.04, 2.1.08
This method is a simple app that can be installed through the normal method of app installation and provides a temporary root (root will disappear after reboot) There is also an option called Permanent root (Should be named Reacquire root after reboot)
The rooting is applied after the OS has booted completely so there is no effective way to change system files/apps. Also the file-system is still read-only so modification can only be done in a difficult way. For more information about how to do that go see here.
chulri's root
This method requires the installation of the SDE (Special Developer Edition) of Archos and the installation of the extracted kernel and modified initramfs of the stock firmware.
chulri has provided 2 different sets for each firmware version.
The first is with a temporary read-write file-system. So with the tmproot version you can experiment with making changes to the file-system and if they don't work out you can simply reboot to revert to the original state.
If you are confident about making changes you can install the rw sysroot version where the changes you make are permanent.
At the moment there are no changes done to the partitioning of the data and storage area. chulri is working on that now so that the /data space can be enlarged.
UrukDroid
This method requires the installation of the SDE (Special Developer Edition) of Archos and a full custom build kernel and file-system.
For more information about UrukDroid please read here.
What can I do when I have root?
Good now that you have rooted your device here are some cool things you can do with it.
Every app or modification you can do with root will have the above rooting methods indicated with the following colors.
Green Can be done.
Red Can NOT be done.
Blue Build-In.
Orange In development.
Apps
Titanium Backup ★ root Archangel, chulri's root, UrukDroid
FBSync for FBReader ** Root ** Archangel, chulri's root, UrukDroid
CifsManager Archangel here, chulri's root (Module download), UrukDroid
Swapper 2 (for Root users) Archangel*, chulri's root*, UrukDroid (* Internal Swap needs to be disabled)
Scripter Archangel, chulri's root, UrukDroid
LCD Density Changer Archangel (free version only), chulri's root, UrukDroid
SetCPU $ Archangel, chulri's root, UrukDroid
Root Explorer (File Manager) $ Archangel, chulri's root, UrukDroid
System apps
AppWidgetPicker Archangel, chulri's root, UrukDroid
Enabling Facebook sync Archangel, chulri's root, UrukDroid
Notion Ink Adam apps Archangel, chulri's root, Urukdroid
themed Market apks Archangel, chulri's root, Urukdroid
Modifications
full Market Protected App access Archangel, chulri's root, UrukDroid
Disable swap for 2.1.02-2.1.08 Archangel, chulri's root, UrukDroid
DVB USB stick support for Live TV Archangel, chulri's root, UrukDroid
Increase of System Storage Archangel, chulri's root (Coming soon), UrukDroid
Enable hidden settings Archangel, chulri's root, UrukDroid
un-mirror the camera image Archangel, chulri's root, UrukDroid
Move Soft Buttons to Notification Area Archangel, chulri's root, UrukDroid
IPV6 Support Archangel, chulri's root, UrukDroid (This is specific to the chulri's root)
Blackberry tethering Archangel, chulri's root, UrukDroid For Archangel users look here.
Ad-Hoc Wifi and AR-DRONE Archangel, chulri's root, UrukDroid (Only changes in /data/ are needed so Archangel should work)
Remap Hardware Buttons Archangel, chulri's root, UrukDroid
Custom framework-res (Theming)
[THEME] Fisha21 custom framework and apps Archangel, chulri's root, Urukdroid
[THEME] LithiumMod Blueberry port Archangel, chulri's root, Urukdroid
[MOD] Battery Icon Mod for gen8 Archangel, chulri's root, Urukdroid
Custom boot animation Archangel, chulri's root, Urukdroid
Reserved for future use
A huge "thumbs up!" for you! This is an awesome information thread
chulri said:
A huge "thumbs up!" for you! This is an awesome information thread
Click to expand...
Click to collapse
Thx just having some fun and I need to increase my thanks meter some more
If you have some suggestions they are always welcome.
chulri said:
A huge "thumbs up!" for you! This is an awesome information thread
Click to expand...
Click to collapse
I strongly agree with chulri, this thread is very useful and clearly information.
Really useful stuff, as a newbie to Android and to tablets I have been umming and ahhing over whether to root or not and will continue to monitor this thread for more information to help me decide.
thank you for this, very useful.
Added a bit of explanation about su and SuperUser.apk in the first post.
Any remarks/additions are always welcome.
Many many thanx for this post!!!
This is an excellent thread, thanks for taking the time to write it.
Just had some suggestions for the "Modifications" section:
custom frameworks: mine, p0rk burn's and your battery mod. Archangel, chulri's root, Urukdroid
Notion Ink Adam apps Archangel, chulri's root, Urukdroid
themed Market apks Archangel, chulri's root, Urukdroid
Ok added them made a special section for THEMES and MODS
fisha21 said:
Notion Ink Adam apps Archangel, chulri's root, Urukdroid
themed Market apks Archangel, chulri's root, Urukdroid
Click to expand...
Click to collapse
Both of these probably are possible with the archangel root.
All the Notion Ink Adam apps except for the browser are probably installable as normal apps.
The Vending.apk can be copied to the /data/test/froyo/system/app.
wdl1908 said:
Ok added them made a special section for THEMES and MODS
Both of these probably are possible with the archangel root.
All the Notion Ink Adam apps except for the browser are probably installable as normal apps.
The Vending.apk can be copied to the /data/test/froyo/system/app.
Click to expand...
Click to collapse
Thanks. I've no experience with the Archangel root, so wasn't sure. Perhaps if anyone else can confirm they work?
Great Jobs!
I like the post 3, hope you keep update^^
nice indeed!
i think we need a sticky!!
Awesome post...Wow.
wdl1908,
You've been a great contributor to helping Archos users. I really congratulates you. Thanks for all of your help. I know you do put much time into this.
Now my suggestion is to add one important thing ...Archos is still not adressing as of today: Blackberry Tethering. Dervari found the fix in their scripts. But they implmented the "if" statement fix but did not comment the "novj" parameter. Which still prevent Archos tabs to tether to BB.
With Chulri's and UrukDroid, you can do that simple edit and be able to tether to your BB. You can't do that with Archangel since the change need to stick.
For this and this alone a lot of people have decided to root. I guess it's a big one to mention.
nashi20002003 said:
wdl1908,
You've been a great contributor to helping Archos users. I really congratulates you. Thanks for all of your help. I know you do put much time into this.
Now my suggestion is to add one important thing ...Archos is still not adressing as of today: Blackberry Tethering. Dervari found the fix in their scripts. But they implmented the "if" statement fix but did not comment the "novj" parameter. Which still prevent Archos tabs to tether to BB.
With Chulri's and UrukDroid, you can do that simple edit and be able to tether to your BB. You can't do that with Archangel since the change need to stick.
For this and this alone a lot of people have decided to root. I guess it's a big one to mention.
Click to expand...
Click to collapse
Can you give me the link to thread that addresses the problem. I'll add it then.
Added custom boot animations to the list.
Here's the link
http://forum.xda-developers.com/showthread.php?t=862884
Note: I consider this obsolete and recommend rusmod
Bugfix v3
Here's the latest bugfix for Dexter's 1.3 aka stock221v13. This includes everything from Bugfix v2 and adds:
Extended power menu that adds "Reboot" and "Recovery" (see thumbnail below for a screenshot)
Include conservative governor (c19932, nadlabak)
Tweak to improve SD card read performance (reverendkjr)
DO NOT APPLY THIS TO XAVWANTED'S OR KHALPOWERS ROMS
The extended power menu requires extensive modifications to the framework. This patch includes Dexter's 1.3 framework. Don't hose your phone! I can help port the menu to the other ROMs, but this can and will bork your stuff if you're not running stock221v3 (+bugfix updates are OK).
Instructions:
Read all the instructions
Save stock221v3-bugfix-3.zip to OpenRecovery/updates/stock221v3-bugfix-3.zip
Boot to OpenRecovery
OR menu > nandroid > backup > system > backup selected
OR menu > nandroid > restore > stock221v13 > system > restore selected
OR menu > apply update > stock221v3-bugfix-3.zip
OR menu > wipe dalvik cache
OR menu > reboot system
Download:
http://www.multiupload.com/MTCIACFSJN
More details:
https://github.com/downloads/Mioze7Ae/XT720-patch
Experimental patches for bugfix v3
Experimental patches are minimally tested.
Metamorph compatibility fix
Volume-down boot to enter fastboot
Bugfix v2
Summary:
Graphics/OpenGL performance tweak (xavwanted)
Media library tweaks (xavwanted)
memhack (khalpowers) moves dalvik-cache to either /cache or /sd-ext
By default moves dalvik-cache to /cache
Will use /sd-ext/dalvik-cache instead if it exists (see also "User control of /sd-ext" below)
minfree memory parameters tweaked
Parameters from AutoKiller Memory Optimizer database
http://andrs.w3pla.net/autokiller/list/currentType/378
http://andrs.w3pla.net/autokiller/list/currentType/591
Fix milestone overclock persistence
Autodetects ext2/3 (kousik)
ext2/3 partition is checked and possibly repaired on boot
Disable automatic apps2ext. Native Froyo App2SD is not affected.
See also "User control of /sd-ext" below
apps2ext used to be called app2sd before native Froyo App2SD (apps2fat) existed. Confusing!
Add support for Link2SD
See also "User control of /sd-ext" below
Adds Maps.apk and updates YouTube.apk
User control of /sd-ext through manual creation of directories
/sd-ext/app (move /data/app to /sd-ext [apps2ext])
/sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
/sd-ext/app-private (move /data/app-private to /sd-ext)
/sd-ext/link2sd (enable Link2SD 1.5.1 support)
apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Replaces /system/oc with modular scripts in /system/etc/init.c
See the README on github for more details. https://github.com/Mioze7Ae/XT720-patch
Installation
Download and copy stock221v13-bugfix-2_signed.zip to the /sdcard/OpenRecovery/updates directory
Reboot into OpenRecovery
"Nandroid > Restore" Dexter's stock221v13 system (restoring boot not necessary)*
"Apply update" and select stock221v13-bugfix-2_signed.zip
Wipe data / factory reset*
*Advanced users: If you've been running Dexter's 1.3 (stock221v13) with the previous stock221v13-bugfix-1.zip, then it should be possible to apply bugfix-2 cleanly over stock221v13-bugfix-1.zip without first restoring system if you haven't made incompatible customizations to /system. You can also probably just clear the dalvik-cache instead of wiping, but I recommend doing that manually if you've moved it to sd-ext.
Download
http://www.multiupload.com/E7NJ9H2F9C
https://github.com/downloads/Mioze7Ae/XT720-patch/stock221v13-bugfix-2_signed.zip
Experimental patches for bugfix v2
Experimental patches are minimally tested.
Conservative governor suggested by c19932 module from nadlabak (included in bugfix-3)
reserved
this post intentionally left not blank
Disable automatic apps2ext. Native Froyo App2SD is affected.
Click to expand...
Click to collapse
Do you mean unaffected or is Froyo Native Apps2SD not working?
3rdstring said:
Do you mean unaffected or is Froyo Native Apps2SD not working?
Click to expand...
Click to collapse
Yes. You are correct native Apps2SD is NOT affected by disabling the automatic apps2ext. Thanks for catching that quickly!
tried to apply over last 1.3 bugfix patch.... "installation aborted".
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
c_urbanek said:
tried to apply over last 1.3 bugfix patch.... "installation aborted".
Click to expand...
Click to collapse
It's kind of a Hail Mary. It did work in my testing and I just tried it again with success. One thing is the new patch is signed so it could also be that your zip got corrupted in download. I've gotten installation aborted messages when the zip was corrupt, but there are probably other ways for it to fail. The md5sum should be
Code:
a93cfa1d6ea73a4ee8ff6ec4afc72baa stock221v13-bugfix-2_signed.zip
smoki3 said:
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
Click to expand...
Click to collapse
If you can see a /system/etc/init.d/00_memfree file on your phone, the update was applied.
App2ext moves all apps to the ext partition. Link2SD lets you do it selectively. This isn't a tremendous gain on Froyo, because we have the native move to SD. One difference is that using app2ext apps will be available while the sdcard is being accessed over USB. Also widgets should work for app2ext. At one point I unscientifically convinced myself that app2ext was faster at loading apps than the native move. That said, I'm not currently using either app2ext or link2sd except when testing. I did a big app purge recently and combined with the memhack I'm not running out of space (yet )
Okay the patch works very good! I have more memory now and it seems like it is very fast now! Great work
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Tavinsky said:
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Click to expand...
Click to collapse
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
If you did move dalvik-cache to sd-ext, then OpenRecovery doesn't know how to wipe dalvik-cache correctly, so you'd have to do that manually. If you set up dalvik-cache on sd-ext, then you probably already know how ways to do that.
It should not affect any apps that are on SD.
If I was really clever I would figure out how to make the update clear dalvik-cache on install... hmmmm.
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
It should not affect any apps that are on SD.
Click to expand...
Click to collapse
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Tavinsky said:
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Click to expand...
Click to collapse
It should move automatically. You don't have to do anything
Tavinsky said:
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Click to expand...
Click to collapse
That sounds right. I can't remember exactly which ones can't be backed up. To undo trying the patch you need to restore System, Data, Cache (maybe), SD Data (possibly, if you have one). It doesn't hurt to get more. Just read the nandroid output carefully to make sure no errors happened.
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
c19932 said:
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
Click to expand...
Click to collapse
Thanks. Maybe I should break the changelog into subsystems. That might make it easier to scan.
The main non-memory improvements over bugfix-1 is xav's egl.cfg which really does help speed up the interface considerably and is the secret sauce of the recent themed ROMs here. We discussed it on the main thread just after bugfix-1 was released and a lot of us adopted it, but it seemed too experimental to push out as a default at the time. I've been running it since then without a problem and forgot that not everyone has it. Since khal and xav have been including it in all their ROMs, I decided it was probably time.
I also get a little annoyed at having to dig out these basic improvements from mostly theme and app-choice packages, but it does hone my understanding of android . I try to not push these things immediately out of respect to khal and xav. There was enough complaining yesterday about how to remove a theme get a "fast" stock ROM, that I decided it was probably time. There really hasn't been too much innovation lately between the ROMs, it's mostly been theming. It's sad xav's selling his phone.
The big problem still remains RAM use. Tweaking the minfree parameters seems more of a band-aid than a fix. That seems to be universal across all the froyo ROMs. Something isn't right. Maybe now that the Milestone froyo is finally released we can get to the heart of the problem.
* /sd-ext/app (move /data/app to /sd-ext [apps2ext])
* /sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
* /sd-ext/app-private (move /data/app-private to /sd-ext)
* /sd-ext/link2sd (enable Link2SD 1.5.1 support)
* apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
hellmonger said:
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
Click to expand...
Click to collapse
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
fwals said:
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
Click to expand...
Click to collapse
I think you are asking: Is it OK to apply stock221v13-bugfix-2_signed.zip on top of stock221v13-bugfix-1.zip? I'm 95% confident it is OK.
Mioze7Ae said:
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
Click to expand...
Click to collapse
No no sorry to bother you you trully rock!!!!!!!
I installed lasted mur4ik os 2.3.7 and i wanted to install LG IME from 2.1 version but when i go to recovery this is the message that i have :
Installing: /sdcard/LG_IME.zip
Finding update package...
Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Plese switch to Edify scripting (update-script and update-binary) to create working update zip packages.
Installation aborted.
Help ?
reD. said:
I installed lasted mur4ik os 2.3.7 and i wanted to install LG IME from 2.1 version but when i go to recovery this is the message that i have :
Installing: /sdcard/LG_IME.zip
Finding update package...
Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Plese switch to Edify scripting (update-script and update-binary) to create working update zip packages.
Installation aborted.
Help ?
Click to expand...
Click to collapse
Try recovery 2.x.x.x
Sent from my LG GT540 Swift
Thanks for reply,i founded some other version made for this os,and it works.