Related
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Actually, there is. The dalvik-cache doesn't move to your FAT32 partition, so you will still eat up storage space with it.
Also, this program offers other features, such as Low Memory Killer tweaking and heap size adjustments.
Some people also reported that the apps run faster when they are placed on an EXT partition rather than using Froyo's FAT32 implemetation. Personally, I haven't really benchmarked it, so I can't tell you from personal experience if it is faster or not.
I guess it's a personal preference.
stoneyjonez said:
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Click to expand...
Click to collapse
That may be true right now, but apps are getting bigger in the Android market. I know for other phones, it can be a necessity.
As I said in the previous post...it's more of a preference.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Depends on who built it.
I have users that say this works perfectly with CM7. During my testing using CM7, I didn't get it to work because the build I had didn't have EXT support (which is needed for Darktremor to work).
So, I would say do a backup of your phone and try it. If you can't get it working, you are more than welcome to send me the logs at [email protected] and I'll see what happened (logs are located on /data directory: files are dta2sd.log, dta2sd.lg1, dta2sd.lg2)
ajaxchen said:
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Click to expand...
Click to collapse
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
That could be an issue. I'm not familiar with that recovery, but if it has a repair function, you should try to run it.
If you don't have that option or the repair was unsuccessful, I would offload the contents of your FAT32 partition on a computer and repartition the card.
ajaxchen said:
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
Click to expand...
Click to collapse
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
I added a new command in Beta 03 that should make it easier to convert EXT2 to EXT3:
a2sd convert-ext3
Killbynature said:
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Well there are people who like games and seeing that some of the games in marketplace are 80mb each and some even reach over 100. I filled my 500mb internal storage because i like to game on my phone.
It's in the planning stages. The goal is to build an interface so an average user can interact with it. Sadly, I'm not very good at Java yet and I haven't found a programmer to assist me in this quest. But it's still being planned and will happen eventually.
agriff said:
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
Click to expand...
Click to collapse
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Card speed is important when writing. For dalvik-cache and apps, not that much. For moving /data/data to the SD card, it may make a difference.
Read speed is dependent on the quality of the card you are using.
As for performance, I only notice the speed difference when things like dalvik-cache is getting rebuilt. Normal operation...I don't notice the difference.
MuF123 said:
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Click to expand...
Click to collapse
What's the use? We've got plenty of internal storage space.
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Part Four said:
What's the use? We've got plenty of internal storage space.
Click to expand...
Click to collapse
tkirton said:
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Click to expand...
Click to collapse
Not really.
tried working on desire hd stock rom but its not working gets installed successfully but a2sd commands dont work!
Hey all. Can't post in the development forum therefore I'll post here.
I have a Leedroid 2.5 A2SD+ rom but this should apply to all A2SD roms.
What I want to do is to force install the software onto the internal memory. I've tried googling and playing around with it myself without any luck. I've ran ADB in recovery and I can't even push the app into "/data/app" since it directs it to "system/sd/app" which is my ext partition.
Is there anyway to do this or I am out of luck ? The reason behind this is that my Handcent is glitching and there is a delay in notifications (vibrate > sound> LED) This started only after I install LeeDroid A2SD+ rom so I have a feeling that my SD card is slowing things down.
Hopefully someone has an idea about this.
Have you tried spareparts, install it, you'll have an option where to install apps, then set it on internal, may work..
I do have Spareparts, it already comes with LeeDroid but I can't see any options that relate to what you've mentioned.
http://forum.xda-developers.com/showthread.php?t=702997
There are 2 SpareParts, use the one in the link. The second option is app2sd, click on it and choose internal.
Hey, I've tried it but it doesnt seem to work.It still installs onto the SDcard. Hmm...i am stumped, cuz there is gotta be a way to force install an app onto internal memory..
hi,
there is some commando would managed this
=> adb shell pm setInstallLocation 1
more info into leedroid wiki =>
http://leedroid.com/bravo-wiki/prevent-any-all-apks-from-installing-to-sd-card
hope this help
Grrr.... Can't figure it out.
Nothing seems to work. I've tried the guide on the Leedroid Wiki with no luck, I've tried Titanium Backup thing that you have mentioned in the other thread. Doesn't work either. The only thing I don't get is how to remount the sd-ext partition, because in the comments of the Leedroid Wiki, that's what made it work for one of the users. I've tried remounting in CWM(ClockWorksMod) but that didn't work.
SpareParts essentially does that command setInstallLocation 1 but in GUI mod. I am lost.
I've tried using that "pm" command to install onto internal flash since there are commands that apparently allow you too but it still installs onto the SDcard. I am just wondering, is there anyway to temproraly disable App2SD script ?
hi,
if you can't get sorted like this, maybe Darktremor app2sd script wil help you, never tried as i m using data++ rom but here is the complete thread... hope for you that will help.
therez a long explication of how it s working and how to apply this on your current rom.
be sure to get root rights
http://forum.xda-developers.com/showthread.php?t=715116
hoep this help
Thanks for your help. I took a different route by pushing the APK onto the /system partition. I had 20mb left so it was enough for an app.
Thanks for all the help))
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!
Hello, everyone.
I'm a big fan of MildWild's roms, specially of the Oxygen-based 5.0. A superb work of art!
However, always looking for ways to get the most from my fast-aging Desire, I've tried the V6 Supercharger scripts. I've got a rather mixed-up feeling from those, though. I think what they promise is *very* exciting, but in order to get they fully working a lot of work and experimentation is needed. Which is fine… up to a certain point.
So, to the point: does anybody here have a working, optimized, configuration for V6, which works nicely for MildWild 5.0? I'm asking, because there have been times in which, after carefully choosing the "right/best" options during configuration, I got even disappearing applications!
Any light that can be shed on this matter will be appreciated. Thanks in advance.
I tried V6 supercharger on an older version of mildwild oxygen with mixed results
Not sure how much of an effect it actually had. My main issue with it was that it seemed to forget which was my home launcher and choose a different /system app which defeated the point of the script. Ended up removing it and default kernel with Go launcher was ok, though might have performed better with a lighter launcher.
Make sure it says 100% supercharged at least, play around with a few of the options, read the documentation to get an idea of what to pick. Best place to ask would be in the V6 thread itself if it doesn't work.
As for disappearing apps, not sure how much that is due to the script. Are you using the zipalign option? You may be conflicting with the ROM's own zipalign script if it has one. If so, don't zipalign with V6
Also how is your ROM currently set up?
- Which hboot (think cm7r2 is recommended)?
- How did you partition your sd card (gparted or 4EXT recovery recomended, not minitool or clockworkmod recovery)
- Using default A2SD script? Keep you apps on 'internal' to trick to sd-ext, no need to 'move to SD'
eddiehk6 said:
Make sure it says 100% supercharged at least, play around with a few of the options, read the documentation to get an idea of what to pick. Best place to ask would be in the V6 thread itself if it doesn't work.
As for disappearing apps, not sure how much that is due to the script. Are you using the zipalign option? You may be conflicting with the ROM's own zipalign script if it has one. If so, don't zipalign with V6
Also how is your ROM currently set up?
- Which hboot (think cm7r2 is recommended)?
- How did you partition your sd card (gparted or 4EXT recovery recomended, not minitool or clockworkmod recovery)
- Using default A2SD script? Keep you apps on 'internal' to trick to sd-ext, no need to 'move to SD'
Click to expand...
Click to collapse
Thanks for answering!
To begin with, getting to the desired 100% supercharged took a lot of time, reading and experimentation. Sometimes, the very same set of settings led me to different results!
As to your questions:
My current rom is MildWild 5.0, with an Oxygen-R2 HBOOT (as you incidentally have suggested in http://forum.xda-developers.com/showpost.php?p=46278979&postcount=306).
My sd card has a 1 GB ext partition, created with gparted.
I'm using the default A2SD script that MildWild included. Never before have I run into any sort of problem with it.
To be honest, right now, the zip aligning hint you're giving seems the most promising exploration route to me. I will be trying it next weekend.
Thank for the advice!
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
parsifal968 said:
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
Click to expand...
Click to collapse
If you search throught the forums you will find this answered many times over.
For the sake of simplicity I will do so again here.
Yes, you will want to root your device in order to use the apps for underclocking.
Custom recovery is recommended. TWRP is your starter flavor.
You may use apps like link2sd and app2sd if you have your micro sdcard formatted to fat32 w/ two separate partitions, at least for link2sd.
Gamma has been corrected using a custom kernel on the Google Play Edition of the tablet. If you didn't buy it through the Google Play store, It's not the Google Play Edition.
There are (hopefully) some people working on a gamma corrected kernel for the 500, but as of now it has not been released. There is a thread in the development section on compiling your own kernel should you wish to give it a go. Regards,
parsifal968 said:
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
Click to expand...
Click to collapse
- Once rooted, get this app - CPU Tuner
- Like sleekmason mentioned above, no kernel for the v500 version. However you can get this app without root - Screen Adjuster
- Yes you can move apps to microsd. Follow these instructions - Prep SD Card for moving apps
Make sure to only take a maximum of 20% of the SD Card as a partition, e.g. 32GB should have max 6GB for partition.
Once you've done that, follow these steps to Link the apps to sd card - How to use Link2SD
Pman1342 said:
- Once rooted, get this app - CPU Tuner
- Like sleekmason mentioned above, no kernel for the v500 version. However you can get this app without root - Screen Adjuster
- Yes you can move apps to microsd. Follow these instructions - Prep SD Card for moving apps
Make sure to only take a maximum of 20% of the SD Card as a partition, e.g. 32GB should have max 6GB for partition.
Once you've done that, follow these steps to Link the apps to sd card - How to use Link2SD
Click to expand...
Click to collapse
thanks for the usefull reply...
and now:
1) it's better than setcpu? they underclock also the Gpu?
2) i will do a check.
3) why only 20% max? hour gpad support ext4 or i stick with ext2?
parsifal968 said:
thanks for the usefull reply...
and now:
1) it's better than setcpu? they underclock also the Gpu?
2) i will do a check.
3) why only 20% max? hour gpad support ext4 or i stick with ext2?
Click to expand...
Click to collapse
No probs.
1. Not sure about underclocking the GPU, what I do now is that it has profiles similar to setcpu. I would have recommended setcpu, but depends if you want to pay the £1.50 or not. There's plenty more on Playstore, check out the "similar apps" for cputuner/setcpu.
3. I saw it a few times here and there to only use no more than 20%. I think it's the optimal amount for Links2SD to work and with no loss of speed. Also anymore could cause stability issues to the partition and the unallocated space. To be fair, with a 32GB card, 6GB is more than enough space, I have that on my phone and only used 1.5gb with 100+ apps and some system apps on there too. Works great and faster to load apps than on internal.
For the partition, I've used ext4 on my phone, I haven't tried it yet on my g pad (not needed it). Try ext4 first, if the pad doesn't recognise it, then re-partition to ext2.
Pman1342 said:
No probs.
1. Not sure about underclocking the GPU, what I do now is that it has profiles similar to setcpu. I would have recommended setcpu, but depends if you want to pay the £1.50 or not. There's plenty more on Playstore, check out the "similar apps" for cputuner/setcpu.
3. I saw it a few times here and there to only use no more than 20%. I think it's the optimal amount for Links2SD to work and with no loss of speed. Also anymore could cause stability issues to the partition and the unallocated space. To be fair, with a 32GB card, 6GB is more than enough space, I have that on my phone and only used 1.5gb with 100+ apps and some system apps on there too. Works great and faster to load apps than on internal.
For the partition, I've used ext4 on my phone, I haven't tried it yet on my g pad (not needed it). Try ext4 first, if the pad doesn't recognise it, then re-partition to ext2.
Click to expand...
Click to collapse
Neither ext4 or ext2 were allowed for patitions on the sdcard on my device. This is the gpe which may be different in that, LG may allow for those types.
FAT32 works fine though. I am still working on whats required to allow ext2. Wouldn't think it would be so difficult. I know some of the roms allow for it.
sleekmason said:
Neither ext4 or ext2 were allowed for patitions on the sdcard on my device. This is the gpe which may be different in that, LG may allow for those types.
FAT32 works fine though. I am still working on whats required to allow ext2. Wouldn't think it would be so difficult. I know some of the roms allow for it.
Click to expand...
Click to collapse
Hmm that's strange, I haven't tried so can't tell you if it works or not on v500. There maybe a kernel for the GPE which would allow it, I believe there'es a few in the android development area mostly for GPE (v510).
Edit: Just found this thread, supposedly there's a permission issue on GPE versions, there's a fix though through this post:
http://forum.xda-developers.com/showpost.php?p=48635344
Pman1342 said:
Hmm that's strange, I haven't tried so can't tell you if it works or not on v500. There maybe a kernel for the GPE which would allow it, I believe there'es a few in the android development area mostly for GPE (v510).
Edit: Just found this thread, supposedly there's a permission issue on GPE versions, there's a fix though through this post:
http://forum.xda-developers.com/showpost.php?p=48635344
Click to expand...
Click to collapse
Heh, I'm am a kernel developer for the 510. In signature.
No, it's not a kernel issue as such. well, maybe, sorta. It is a permissions/fstab problem as far as I can tell. I haven't really messed with that yet. The kernel itself DOES allow for both ext4 and ext2, and if somebody wants it, I'll enable ntfs for the kernel as well.
I will need to rip apart a rom that allows it and see what is on file. That won't happen anytime soon as I am working on other items at the moment.
The link you posted is just to get rw permissions for the sd card. nothing to do with the format thereof.
sleekmason said:
Heh, I'm am a kernel developer for the 510. In signature.
No, it's not a kernel issue as such. well, maybe, sorta. It is a permissions/fstab problem as far as I can tell. I haven't really messed with that yet. The kernel itself DOES allow for both ext4 and ext2, and if somebody wants it, I'll enable ntfs for the kernel as well.
I will need to rip apart a rom that allows it and see what is on file. That won't happen anytime soon as I am working on other items at the moment.
The link you posted is just to get rw permissions for the sd card. nothing to do with the format thereof.
Click to expand...
Click to collapse
Interesting, didn't know that. I've got the 500 but not tried an sdcard yet (only had tab for couple of weeks). Do you know if the permissions is a problem for the 500 too?
Wasn't sure if it was the tab that wasn't reading the ext2/4 formats.
P.s. I'm new, didn't realise you are the kernel god for the LG v510. Apologies
Pman1342 said:
Interesting, didn't know that. I've got the 500 but not tried an sdcard yet (only had tab for couple of weeks). Do you know if the permissions is a problem for the 500 too?
Wasn't sure if it was the tab that wasn't reading the ext2/4 formats.
P.s. I'm new, didn't realise you are the kernel god for the LG v510. Apologies
Click to expand...
Click to collapse
Lol. It is a google problem as far as the permissions go. They saw a potential for abuse and removed the auto access as such. I don't know if lg left it the same or does what Samsung does and has their own fix.
In the development section under the kernel compile thread, if you read the last page or two you will see where muiriddin is working on a kernel for the 500 that should take care of the gamma issues and such. I believe he has a test kernel compiled and is working on getting it into a useable zip file for your device. There are still a few mysteries to work out
Anyway, there is a thread on these forums (gpad) that discusses the problem and the same fix you found.
sleekmason said:
Lol. It is a google problem as far as the permissions go. They saw a potential for abuse and removed the auto access as such. I don't know if lg left it the same or does what Samsung does and has their own fix.
In the development section under the kernel compile thread, if you read the last page or two you will see where muiriddin is working on a kernel for the 500 that should take care of the gamma issues and such. I believe he has a test kernel compiled and is working on getting it into a useable zip file for your device. There are still a few mysteries to work out
Anyway, there is a thread on these forums (gpad) that discusses the problem and the same fix you found.
Click to expand...
Click to collapse
Naughty Google!
Oh nice, you have many big threads, nice to be speaking to a clever person! Well i'll be happy to test the kernel out for muiriddin when it's up and ready, sound exciting.
Pman1342 said:
Naughty Google!
Oh nice, you have many big threads, nice to be speaking to a clever person! Well i'll be happy to test the kernel out for muiriddin when it's up and ready, sound exciting.
Click to expand...
Click to collapse
Good Day! Thought you, or whoever else has an interest may like to see this article by chainfire (lead developer),
and this one about android device specific configurations. ( I keep looking at this like there might be some magic there
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
http://source.android.com/devices/tech/storage/config.html
apparently, the so-so work around for us was initiated by Samsung, and is a dirty hack that they still implement.
I was looking into the init.rc file for the 510 and found:
Code:
mkdir /storage 0751 root sdcard_r
I changed the above to rw thinking I found the golden calf, recompiled the kernel with the adjusted ramdisk and tested it to no avail.
I do however think I'm on the right track.
I dont think the problem is getting the device to user the sdcard(1), as a symlink maybe could do the trick, I think the problem is making it visible to programs like Dolphin when you want to download something, and then getting a request to do so, meaning programs can't arbitrarily write to the sdcard without our explicit permission (root or question).
Update...
Rooted my gpad and tryed almost all setcpu apps for underclock but no lucky.
At start only core0 seem to do the freq i set (1.2 for example) and others 3 core runs at 1.7 but after some seconds all 4 cores return to 1.7
Tested with perfmon app active and running antutu.
Someone help me!
Sent from my LG-V500 using xda app-developers app