Develop Bugs

[Q] Pros and Cons of sd-ext?

Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
blahbl4hblah said:
Having sd-ext partition on your sdcard will always be benefical, the phone will run so much better believe me
Click to expand...
Click to collapse
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?

ArmedandDangerous said:
Hi!
Just would like to know the pros and cons of formatting into ext4 on my SD.
As far as I can find :
Pros : Supports files larger than 4GB as Fat32 cannot
That's about it I think...
Cons : Windows cannot natively detect such a partition
Why I ask this is I just saw a this post
I'm ready to go ext4 if there's any performance gain, who wouldn't? But what gain is there, and what would I lose in return?
Click to expand...
Click to collapse
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App

OriginalGabriel said:
You're mixing things up here a bit I think. Sd-ext referrs to having a partition on your sdcard to allow support for Apps2SD (basically being able to move apps to your SD card and run them from there in order to free up space); you'd basically repartition the card so that there's an ext3/4 partition for apps and a FAT32 partition for data.
As for the ext4 filesystem, it does allow for larger file sizes and is also a bit faster but you're correct in the fact that you won't be able to natively mount it on a Windows system.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?

ArmedandDangerous said:
But don't we already have Apps2SD in GB, + all the apps that do it for you. How is this different, apart from some apps that can't natively be moved? And why is it faster? Internal memory should always load faster, should it not?
Click to expand...
Click to collapse
GB has the ability to do Apps2SD but it requires the partitioning as, I believe, a symlink is set up so that partition on the sdcard acts as a part of the devices internal storage.
As for speed, just moving apps to your sdcard won't speed up your phone; what that poster you quoted was talking about (most likely, I'd have to see the original thread) was converting your devices partitions (/system, /data, /cache, etc.) from ext3 to ext4. ext4 is a bit faster however some ROMs do not fully support it.
Sent from my T-Mobile G2 using XDA App

Ok, let's clear this up. GB has Apps2FAT32 (a2sd) natively. A2EXT is completely different but none of that is the point of the OP's question.
When it comes to our phones - there is almost no notable performance gain when using EXT4 over any other EXT format. Our phones don't utilize FAT32 internally - just on the sdcard. EXT4 is designed for use with massive file systems. A couple Gigs really doesn't access it's full potential.
While the question is interesting, I'm not really sure what you're planning on doing. Don't format your sdcard entirely in EXT format, and don't attempt to format your phones partitions as FAT32. The result would be... just don't do it.

Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
This has two main advantages: larger sized data partition and more speed as EXT is inherently faster for I/O purposes.
Click to expand...
Click to collapse
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up

ArmedandDangerous said:
Just read this on the portal
http://www.xda-developers.com/andro...hd2-data-successfully-moved-to-ext-partition/
How do I go about formatting a section of my SD into ext4, with existing SD data intact.
And how do I move apps that area already in my phone's internal memory to the ext4 partition? I know there's an option in ROM Manager and CWM, but just don't want to mess anything up
Click to expand...
Click to collapse
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.

blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
Thankfully I am already using meXdroid~ Guess I'll just wait for the new version in the next few days to do the formatting. Can I backup all my apps with Titanium Backup, flash ROM (wipe data/cache and dalvik cache), restore with Titanium.
Or would I have to reinstall every app again so that it goes into the ext4 partition?

blackknightavalon said:
As far as I know, only two ROMs actually support the real A2SD: PyroMod and MexDroid. It's recommended you format the EXT partition to EXT4 before you actually flash either of those ROMs, and you have to rename MexDroid in order to get A2SD working.
Click to expand...
Click to collapse
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).

KCRic said:
There's a script to accomplish this on pretty much any ROM. It *should* work on current ROMs too. It's called 'darktremor a2sd'. Still find it amazing people forget about that one when this question comes up because it's one oldest methods of obtaining a2sd.
I'm still not understanding the OP's question. Are you wanting to do this for an IO performance gain or for space? I can understand doing it for space if you have a ton of apps but if you're doing it for performance it's a waste of your time. You're internal partitions should already be in EXT4 format (use 4EXT Recovery if they're not).
Click to expand...
Click to collapse
I'm doing it for the performance. Have been using 4EXT for a few days and loving it. Already converted internal memory to ext4 from ext3. If further partitioning my SD card for performance is really not noticeable, then I guess I've got nothing to worry about

[Q] a2sd problems on ICS

Hey,
I've been using ICS (beta 0.4.2.1 now, beta 0.3.9 previously) and none of the a2sd scripts seem to be working. I tried to use the one you have to activate through adb, and today when I updated to 0.4.2.1 I chose another one from the installer. My phone still reports 148 MB of internal storage...
I've had a thorough search of similar threads, but you know how difficult it is to find any meaningful information on this forum; can someone please point me in the right direction? Thank you!

I flashed ICS and installed the bundled a2sd script and it worked like the script on Insertcoin. That is the system still displayed the data partition size of my hboot but the SD ext4 partition was utilised for apps. If you have titanium backup you can see the data usage on the home screen.
I also flashed amarullz script. This script did change the reported internal memory to my SD card partition size. I did not use it long so I can't comment on how it runs on s class 4 SD card.
Sent from my HTC Desire using XDA

You did not understand how A2SD works. It moves all apps (with A2SD+ also dalvik-cache) you install automatically to an EXT-partition (some of their data still remain in internal memory). But it does not increase / decrease the size of internal memory.
If you want to change the size of internal memory, you have to use a script which moves the whole /data-partition to an EXT-partition. The size of this partition is then the size of your internal memory. The name of this scripts is DATA2SD / DATA2EXT.
Sent from my HTC Desire using Tapatalk

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

Did you ever get a fix for your problem?
I have something similar. Was running 0.3.9. and decided for a couple days ago to upgrade to a newer edition. Wiped data/factory reset, wiped cached and dalvik-cache, and installed the new version.
Used stock everything, activated a2sd and tried to start and install some apps from google play. Got a message that it was not sufficient space.
Did get titanium installed, and that reports the different "drives" correctly, but I still don't get it to work as it should. If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Anyone got any ideas?

Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used

arsvendg said:
If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Click to expand...
Click to collapse
Same problem here. I tried to wipe caches and even recreated the partitions but still no luck with the stock a2sd.

robla1000 said:
Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used
Click to expand...
Click to collapse
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?

arsvendg said:
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?
Click to expand...
Click to collapse
App and appdata are different things:
The App it's the "core" and are loaded in the RAM when you start them, so if you move them to sdcard you get a slowdown only on the boot of the app itself
The Appdata it's the data created and used by the program to run, likes databases and so; if you move it to the sdcard you get a slowdown 'cause the program continuosly try to access it.
someone correct me if I'm wrong, i'm still learning the stuff
Long story short: normal A2SD+ methods (like DarkTremor or m2sd) only move a part of /data, linking the files; you will NOT see the increased space but your Apps will occupy less memory.
Data2sd method like data2sd or Amarullz A2SDX will "swap" the ext space with the internal data memory, giving you a visible increase in your internal space.
TL;DR if you have a fast SD card you can go for the latter, else stick to m2sd wich is a new and good method to move application!
For partitioning, I suggest you to use 4ext touch recovery, you can install it on your phone from 4ext.net and flash your new recovery directly from your phone (you need to have S-OFF!); after you have your new recovery flashed:
make a backup of your SD card data (you have to format it)
Reboot in recovery
Go to "Tools"
"partition sd card ->"
"Remove all partitions and start from scratch"
Now you have to set, in order, you primary ext dimension, your secondary ext dimension and the swap dimension
I usually go for - 1st ext: 1024 -2nd ext: 0 - swap: 0
Select ext4 for your first ext partition
Now you are ready to use wathever a2sd method you want.
Hope this will help you!
Regards,
Ryther

Ahh I'm just going to leave this here.
All the ICS Devs have done a great job - Kudos to them.
But if you want a bugfree ROM which works well, for now - GIVE UP on ICS.
Go back to CM7 - it'll do you good.

Don't give up on ICS because SOME people have issues. I've ran an ICS build with a2sd working just fine no bugs whatsoever. I have not tried a data2ext script on an ICS build though so I don't know about that.

[Q] Arc's /cache partition

Hey,
I've got Arconium ICS rom installed on my Xperia Arc. I'm running low on internal memory, and while trying to find more space on the device I've found this:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock2 225.0M 1.1M 223.9M 1% /cache
So my question is - what is the cache partition used for on ICS? How big should it be? I found this in the description of some Nexus HD ICS rom:
Cache partition (/dev/block/mtdblock4) is only used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
Click to expand...
Click to collapse
Of course partitions path varies, but the info seems to be relevant.
And a final question - fdisk doesn't seem to work (getting "fdisk: can't read from" error) - how do I go about changing partition table?

To my knowledge (based mostly on HTC phones), in normal use the cache partition is used for downloading apps prior to installing, and for downloading OTA updates (which is why it's so big).
If youre running custom ROMs then this partition doesnt need to be anything like this size, because youre not going to be installing OTA updates. HTC desire owners resize this down to as little as 5meg (though this seems low to me, IMO it should be at least as big as the biggest app youre ever likely to install, so i'd say 25-50 meg is a safer bet.
Now, i have no idea how CWM works, so if this is using the partition to perform installs or nandroid backups or something then your probably wouldnt want to make it much smaller.
There is also a lot of space which could be freed up on the system partition, particularly if youre using a stripped down ROM.
All of the above is all well and good, if there is a way of changing the Arc's partition table. I have no idea how this is done, or if it is even possible. So would love someone who knows about this stuff to respond. BUT: i very much doubt FDISK (you mean windows fdisk?!?!?) is the answer - at the very least i'd expect that you'd need a specially modified kernel in order to boot with a modified partition table. The fact that it fdisk with an error instead of giving it a try is probably the only reason your phone still boots.

[Tool][Port][Blackhole Nullifier & Wipe][1.5a][6.3.12] Discontinued

I've been working on this port for personal use, but I figured others may find this useful.
What is it?
It's a script flashed through recovery, same as when you flash a ROM, that wipes for you in one simple step!
What does it do? (Wipe)
Depending on which version you choose, it calls on mke2fs and e2fsk to format /cache /data /system, then check the partition afterwards.
It will wipe /cache for the cache only, or system, cache and data for the full wipe. It does not do the external SD card, but it WILL FORMAT INTERNAL SD!
What does it do?(Nullify)
Same as the wipe, however this first calls on DD to zero out the partition, leaving NO DATA behind. Its a full overwrite of all data in the partition, with no way to salvage after running. The chances of anyone being able to recover any data after this is run is pretty slim outside of extreme power users and like..the CIA or something. Even then the data would be so corrupted I doubt anything usable could be rebuilt. Best used when bugs come up regardless of wiping multiple times, or prepping the tab for sale, no personal data can be retrieved from the internal SD.
How do I use it?
This is assuming you run a custom recovery!
System Wipe:
Reboot into recovery (this has been tested on my personal device with CWM and TWRP).
Make a full backup.
Install from SD, pick the system wipe zip.
Install the zip.
Wait a bit, it should take a minute for full wipe.
You can either restore a backup or flash a new ROM zip.
OPTIONAL: Fix permissions
Reboot system
NOTE even on a restore first boot will take longer then normal.
Cache Wipe:
Reboot into recovery.
Make a full backup, just in case.
Install from SD, pick Cache Wipe zip.
It'll take a second.
OPTIONAL: Fix permissions
Reboot system
NOTE boot will take a little longer then normal.
Nullifier:
Make sure you have at LEAST 50% battery or are plugged in.
Copy all information and files you want to save from Internal SD to PC or external SD card (the slot one).
Reboot into recovery.
Make a nandroid backup.
Install zip from SD, pick the nullifier zip you want to run.
Cache nullify takes about 9 minutes, full system takes about 35-40.
Check if you can mount /system /data and /cache, if you can, proceed, if not, reboot recovery (recovery not system!)
Install from zip, pick your ROM zip, or restore a nandroid.
Reboot system, and do whatever the DEV suggests.
NOTE Boot will take longer then usual.
What's this ported from?
This is based on work by Volk's Nullifier script for the G2x, and based directly on the Hellfire Nullifier. It's no longer really even close, but the concept and work is still based on their work.
What does each version do?
Cache Wipe: Formats /cache and deletes /data/dalvik-cache.
System Wipe: Formats /cache /system and /data. Recovery mounts INTERNAL SD to /data/media, so THIS DELETES INTERNAL SD!
Please backup your INTERNAL SD before running this or you will lose everything on it!
Cache Nullify: Nullifies /cache and deletes Dalvik-cache.
System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!
Cache Wipe\Nullify is meant for cleaning up when things get buggy.
System Wipe is meant to format everything for a new rom install or nandroid backup restore. The recovery will remove directories around /media, not format, this will format /data completely in preparation for new data.
System Nullify is meant to destroy all data in /system /cache /data, including your internal SD, by zeroing out the partitions. In other words, writes 0s from start to end.
Who should we thank?
Volk, who created the initial concept and script Nullifier, which this is based roughly on.
x0hell0x who ported it to the Hellfire Kindle Series, which this is based directly on.
da-pharoah, who helped me through the process and dealing with different device IDs in different recoveries. If it weren't for him I'd have given up and made seperate zips for each recovery.
What's coming up?
Right now I think this is complete! I'm unsure of how it handles CWM, so I may need to create CWM versions.
Things to note! READ THIS!
This is intended to run on the Acer Iconia Tab A100 ONLY! I have not set this up to run on any other device, and doing so may result in a brick! This wipes partitions, and could wipe boot, recovery, or any number of other partitions if run on a different device!
This was created and tested on my personal device using TWRP recovery! Using any other recovery may or may not prevent the script from running correctly! System wipe\nullify erases internal SD please backup data and ensure your ROMs and Nandroids are stored on EXTERNAL SD CARD!
The wipes are meant for every flash, the nullifiers are NOT meant for every flash! They are meant for changes from one ROM to another rom, or every few flashes, say 10. Otherwise use manual wipes or my wipe scripts!
Porting:
I'll consider porting to other devices if I have time, please PM me if interested.
I am not responsible for any damage that may occur from use of this script! If you choose to use this, that is your choice. As with anything else, flashing can cause problems including data loss, hair loss, bricking, brick laying, and magical fairies cracking your screen.
Changelog:
5.25.12 v0.1
Initial attempt at porting over, full of fail.
5.26.12 V1.0
Wipe Cache only version completed and successfully run on my device in CWM and TWRP.
5.27.12 V1.0a
Minor changes to the script for cache only version.
5.28.12 V1.1
More changes, changed handling of device ID from recovery to handle both types of recovery reporting (thanks da-pharoah)
Adjusted the status bar indicator to better reflect where in the operation the script is (thanks da-pharoah)
5.30.12 V1.1a
Created post, minor clean up of spelling errors.
5.30.12 V1.3
System Wipe finished after some major changes to command arguments. Cache wipe getting updated as well to 1.3 with a fix to rm argument.
6.1.12 V1.4
Cleaned up an error with the cache being formatted and throwing errors. Updated and cleaned up Cache Nullifier, all scripts updated to 1.4.
6.1.12 V1.5a
I made a mistake and updated the wrong script versions, resulting in nothing being formatted due to the system not unmounting before carrying on with the script. My apologies, I hadn't noticed the issue until I attempted to use it today for a rom install. For now, use only 1.5a versions, updating them all now with the fix. Slight changes to output to help see what it's saying. Working on getting the status bar timing correct.
6.3.12 V1.5a Final
Rechecked each script, and should ALL now be FULLY working in TWRP. CWM may or may not handle the script correctly, if you run into issues like it not working, send me a PM or Email with /cache/recovery/last_log and if there dmesg. System Nullifier added finally!
Please bear with me, I'm finishing my High School course and only have limited time on any given day, and it mostly goes to schoolwork, I will update when I can, and I really hope to have the full wipe completed within a few days. Nullifier may take longer as I'm not sure why DD hangs.
Downloads: These are on my drop box for now, it's small so it shouldn't cause issues.
Blackhole System Wipe 1.5a A100
Blackhole Cache Wipe 1.5a A100
Blackhole Cache Nullifier 1.5a A100
Blackhole System Nullifier 1.5a A100

does this actually "wipe" data so that is can not be recovered? or just erase it?

joeyjojojjjjjj said:
does this actually "wipe" data so that is can not be recovered? or just erase it?
Click to expand...
Click to collapse
Right now all it does is format, or wipe, with mke2fs to whatever FS that partition uses, EXT4 or EXT3. Its not much different from using CWM wipe/format commands, just does it all for you. Once I figure out why DD hangs, it will then Nullify the partitions, complete and utter destruction of data by overwriting the partitions with 0s, leaving no traces behind at all. I'm currently hammering out the full system wipe script, which will do /cache /system /data and /data/dalvik-cache, the /cache/dalvik is done when /cache is formatted. The problem I ran into is for some strange reason, internal SD is mounted to /data/media in recovery, meaning formatting /data directly will erase the internal SD card as well. The recovery gets around this by deleting directories around it, but never formats it, which IMO can lead to issues and bugs down the line. I have only 1 method of dealing with this, and that's moving /data/media to the external SD card (SDC), formatting (or nullifying) then moving it back. As this can mean moving up to 8 GB, its not a liable method as it will take a LONG time to move it there and back.
I'm hoping to have the first full system wipe available tonight, however it WILL erase the internal SD, this is only to be used if you don't care what's there, or are having alot of bugs, and copy your stuff off before running. I can't test it since the wife is using the tab now, and I'm not gonna put it online without testing it first.
TL;DNR: It just erases it.

Updates
1.4 versions are up.
Now includes Cache only Nullifier! This is the wiping that I think joeyjojojjjjjj was looking for. Unrecoverable data destruction. Currently DDs /cache, then formats and checks, then deletes dalvik-cache. Overwrites the partition with 0s from beginning to end, leaving nothing but ZERO behind, hence blackhole nullifier.
Hoping to finish up System Nullifier tonight some time.

1.5a Final is done
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.

pio_masaki said:
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.
Click to expand...
Click to collapse
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it

da-pharoah said:
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it
Click to expand...
Click to collapse
It works lol it's based on your work after all

pio_masaki said:
It works lol it's based on your work after all
Click to expand...
Click to collapse
Lol I know but still u got it rockin for the a100 so that's what I meant..
Sent from my LG-P999 using xda premium

Wipes with Crossix Memory Swap?
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!

conorkickass said:
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!
Click to expand...
Click to collapse
Internal SD only. It will never touch your external SD card. And the reason is....
The crossix mount swap is only active when android runs from /system. This is run from recovery, so any system mods don't affect anything running in recovery.
So you're safe, only the included internal SD is wiped, regardless of crossix's mount swap.
Tapatalked from my Galaxy S II.

This is sick. Nice work.
Sent from my SGH-I777 using xda premium

could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645

Presko said:
could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645
Click to expand...
Click to collapse
This has nothing to do with these tools lol.
Anyways I can port it but its useless without the sbk, so not really a point until Acer releases it.
Sent from my Nexus 7 using Tapatalk 2

Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Btw I have contacted the Russian author via 4pda and he says to give a straight shot and to send him a screen shot
Tomorrow at work will have time to try
Is there something specific to put in the start command at prima vista ?

Presko said:
Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Click to expand...
Click to collapse
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well that's a chance to ps my post while you aswer it
btw is there a petition or something that I can contribute with ?

Presko said:
well that's a chance to ps my post while you aswer it
Click to expand...
Click to collapse
Huh?
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Huh?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
not again I will stop editing previous posts

Presko said:
not again I will stop editing previous posts
Click to expand...
Click to collapse
Oh OK I didn't see the edits.
Anything using nvflash or apx mode needs the sbk, no way around it. It may yet be cracked like the a500s, but so far no.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] plants vs zombies2 install problem

I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?

HandyBesitzer said:
I wanted to install p. vs z 2 but it has 168 MB. And our Desire 151MB system partitionn :crying:
Of cause i have an ext partition. There are 754 free Mb of 1,41 GB. (quick system info)
But my intern memory just have 33,44MB of 151 free.
Click to expand...
Click to collapse
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
So on the ext i could install it 4 times but the store first download to intern. Is there a way to install? Maybe if someone uploads the apk and i flash it in the recovery directly to ext4?
Click to expand...
Click to collapse
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
An other question. When i startet my phone there where just 5,6MB free. When moves the a2sd script things to the partition and when moves it it back?
Click to expand...
Click to collapse
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.

eddiehk6 said:
Your /data partition is 151MB, not your /system partition. Your /system partition is 250MB as you are on stock hboot.
When installing apps, as far as I know it doesn't actually install it to internal (/data), and then move it to ext4. It should install it directly to ext4.
However, depending on the ROM, it needs to see the available space on the internal. The apk is then tricked to your ext4 partition.
One way to install it which might work (not tried it)
- Find and download the apk
- Copy and paste it to your /sd-ext partition using a file browser
- Change file permissions to match your other apps
- Reboot
What ROM are you using, and are you using the built in A2SD script or something else? Any A2SD script should move apps (and maybe dalvik cache) automatically to your ext4 partition. I does not move it to internal and back to ext4.
It looks like your memory usage is not very efficient. You may benefit from changing hboot if your ROM /system size is a lot smaller than 250MB. Your dalvik cache might also be on internal, when you could move it to sd-ext where there is plenty of free space.
Click to expand...
Click to collapse
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??

HandyBesitzer said:
i'm using RSK Sattelite ROM.
but if the apps are installed to ext how comes that the data sometimes has about 10MB free and after i installed an update there are 15MB free??
Click to expand...
Click to collapse
It depends a bit on how your script works. Reading the ROM OP it has some sort of "a2sdx" built it, I'm not familiar with exactly how it works. You need to understand this script first before wondering about anything internal memory related.
Think about it logically though...the script is meant to move things to the ext. That's its purpose. Generally they move at least the whole app apk to ext.
So
- If you have an app installed, it should already be on the ext.
- When you update the app, it will overwrite the existing apk on ext.
- There are other things along with an app such as app libs, app data and dalvik cache, which may be on internal or ext depending on the script. These can change on app updates as well.
Have a look at an app like 'DiskUsage', use it to browse your /data partition. See what's using the space. Often you may have some stray /system apps on /data, and you need to move them back to /system.