Develop Bugs

Internal Storage -ARHD & Rom cleaner conflict

Hi, I installed rom cleaner and uninstalled it this morning.At that time I had ARHD 7 installed.
I think it has some how resized my sd-ext partition.
Since then I was not able to install any other rom. (eg AKOP,MIUI, Codefirex)
They all end up with a boot loop. AKOP was partially success but, it showed less internal storage capacity. Hence I could not install any apps.
However I manged to install ARHD again after several tries.
My questions are.
1. Whats the default internal storage size in HTC DHD.
2. Is this because of changing from android 2.3.5 to 4.1+
3. In past I've had no trouble changing roms between miui<->Akop<->viperX

you should search your queries here
regardless, never used rom cleaner, but no app or zip should resize your ext partition. what's important is how you made the partition, round here we recommend 4ext recovery, which is also available for your phone, or gparted.
the sd-ext size will remain at whatever size you pick.
depending on what rom you choose, some will require an sd-ext partition to work at all, others you may need to manually enable it. the rom normally needs some sort of script to be able to see and use the ext partition. details should be searchable in the respective rom threads.
you won't necessarily 'see' you total internal memory read 'internal + sd-ext', but as long as your sd-ext is mainly being used for apps it doesn't really matter. traditionally it's best to use your real internal memory for app data as it's faster than most sd cards.

[Q][FIXED] Playstore error 491 on Paranoid Android 4.2.2

Hey guys,
First my compliments for the beautiful ROM of WoH! I've upgraded my old Desire from Cyanogen 7 to WoH's PA 4.2.2 for my girlfriend and I am jealous.. it looks better than CM 10 on my HTC One!
Problem
But unfortunately, I am running into problems. The problem is that after installing the ROM and switching on a2sd, any download from the play store greets me with 'error 491'.
What I have tried
Usual solutions from Google and this forum are:
- Remove google account (Accounts, google account remove), reboot, readd
- Clear data of Play store, reboot readd, reboot
- Clear user data / factory reset, ad2sd install
- Tried both YourZgapps XS Normal and Multi DPI versions
I have tried these to no avail, the error persists.
What I exactly have done
- Formatted the 4 GB SD into 2 primary partitions, 3073 MB FAT32 and 1023 MB ext4, in windows using MiniTool
- Put the ROM, and GAPPS on the FAT32 partition by SD cardreader
- Boot into recovery, twice performed 'wipe data/factory reset' and 'wipe cache'
- Install from zip, installed ROM and GAPPS
- Reboot, open terminal, did:
su
mount -o rw,remount /system
a2sd install, choose Y -> N -> Y
Click to expand...
Click to collapse
- Reboot
Error when trying to install any app from the Play Store, exact error is '<Appname> “could not be downloaded due to an error 491.”'
Did I make an obvious mistake which I ma failing to see? Any help would be appreciated!

W(!!!!!)oH :laugh:
Install the MediaProvider Fix listed in the ROM thread (post #1 od #2).
Edit:
http://forum.xda-developers.com/showthread.php?p=44389831#post44389831

WoH said:
W(!!!!!)oH :laugh:
Install the MediaProvider Fix listed in the ROM thread (post #1 od #2).
Edit:
http://forum.xda-developers.com/showthread.php?p=44389831#post44389831
Click to expand...
Click to collapse
Thank you for your quick answer, mister WoH! The link points at the MediaProvider package for Android 4.3.2., while the ROM I installed is Android 4.2.2., is this alright? I'll give it a try anyway :good:
Would you say 4.3.2. is better (more stable or so) than 4.2.2.?

Didn't realize you were at 4.2, sorry.
I'd go for 4.3
Edit:
http://forum.xda-developers.com/showthread.php?t=2402514 might help you for 4.2.2

So apparently I installed 4.3 as 4.2.2. ROM (in that thread, the link points to the 4.3! ), so no surprise that GApps didnt work properly.
So, 4.3.. I didn't find instructions in the OP, so I gave it a go:
- Full Wipe
- From Recovery, installed in sequence:
- pa_bravo-3.99-RC2-20131011.zip
- pa_bravo-3.99-RC2-20131011-fix-s.zip
- pa_gapps-full-4.3-20131010-signed.zip
- Reboot
After reboot, internal memory is completely full, even though during the installation PA GApps says it moved GApps to sd-ext.
Terminal su / a2sd tells me:
a2sd=apps dc2sd=dalvik-cache a2sd=appdata
so I guess a2sd should work.
What did I do wrong?
Aaaand btw: Happy Birthday! :beer:

I believe this is your problem:
Dooxed said:
- Formatted the 4 GB SD into 2 primary partitions, 3073 MB FAT32 and 1023 MB ext4, in windows using Paragon Partition Manager
Click to expand...
Click to collapse
Do not use windows software to make linux partitions. It only works on very rare occasions.
My bet is that your partitions are not properly aligned, hence why A2SD doesn't work.
Backup your sd card (just copy the visible FAT32 contents to PC) and repartition with gparted or 4EXT recovery only, nothing else.
Copy stuff back to sd, then full wipe and reinstall ROM again to be on the safe side.

Nice tutorial, will use next time!
So far I just had to execute su | mount -o,rw /system | a2sd install Y N Y, and it works.
Now everything seems to be working, ie. downloading from Play store and the extended memory.
WoH and eddiehk6, thank you for your time!
I have two small and short remaining questions:
- How much memory should be indicated at Settings, Storage, Internal Memory?
Currently it shows something like 170 MB used / 110 MB free, and that with a sd-ext of 1 GB.
- Is 4EXT recovery much better than CWM recovery? Worth the upgrade?
Thanks again!

Dooxed said:
Nice tutorial, will use next time!
So far I just had to execute su | mount -o,rw /system | a2sd install Y N Y, and it works.
Now everything seems to be working, ie. downloading from Play store and the extended memory.
WoH and eddiehk6, thank you for your time!
I have two small and short remaining questions:
- How much memory should be indicated at Settings, Storage, Internal Memory?
Currently it shows something like 170 MB used / 110 MB free, and that with a sd-ext of 1 GB.
- Is 4EXT recovery much better than CWM recovery? Worth the upgrade?
Thanks again!
Click to expand...
Click to collapse
If you are still on stock hboot (which I'm assuming you are) you should have 148mb of internal storage. If you ran the "y,n,y" a2sd configuration, your only your app data will be left on the internal memory. The apks and dalvik will be moved to the ext partition.
And yes 4ext is worth the upgrade from cwm. It does everything that cwm can do and includes some other useful features, plus its touch based so you no longer have to mash your hardware keys.
Sent using xda-developers app

[Q] CyanoMod 007 with A2Ext+: Can't install apps / no free space

Hi, I've installed CyanoMod007 v31 with APPDATA moved to a 2GB ext2-partition on my SD-Card.
Now everything worked fine, except that in the settings, instead of my 2GB memory for apps, it still showed 140MB (though about 350MB are already in use). Still, I had no problems installing apps, so I didn't worry about that too much. But then when I tried to install a large app (150MB), the setup failed after the download completed, and now I can't install or update any app in the play store, because apparently there is not enough free space.
I've already connected the SD card to my notebook to check if it got somehow polluted with temporary data, but the sd-ext partition is fine, 350MB in use of 2GB overall.
So, I'm out of ideas, can someone help me on this?
(Sorry for not posting in the CyanoMod007-thread, but I don't have permission to do so...)

First of all, why ext2? I recommend ext4.
Try doing the partition with 4Ext Recovery.
Also, if it doesn't work I suggest u try Mounts2SD which moves ALL data. (Play Store)

[q] help with htc desire memory

HI
Im new to this forum so please forgice me if my post is in the wrong place.
I have the 2010 htc desire and have it rooted and am running MILDWILD 8.0 which is great on this phone. my question is how do i add extra internal memory using partion ext on sd card. I can partion the sd card with clockword recovery but when i reboot it always hangs on the htc logo. can any one help with this?
Thanks

CWM-made partitions dont cope well with this phone. Reformat the partition using this guide.

I followed the guide but mildwild 8.0 still shows 148 on htc desire internal memory.

That's because you're still on stock hboot, no better than before it was rooted.
- Install DiskUsage, enable root and browse to your /system partition.
- You will see a lot of free space on /system. This is wasted space.
- You can convert this wasted space to extra /data (internal memory) by flashing a different hboot with a smaller /system partition.
(You need to be s-off for the following, if you're not, use 'revolutionary')
- Nandroid backup
- Flash cm7r2 hboot using fastboot
- Full wipe and nandroid restore
- Go again to DiskUsage, your free space on system is greatly reduced :good:, and your /data will go up to 287MB
- This 287MB will be used for app data (e.g. saved game data), and will allow for more apps to be installed.
- You won't see your sd-ext reported in your total internal memory (i.e. it won't read 'internal + sd-ext')
- Keep your apps on 'internal' (don't 'move to sd'), this will trick them automatically to sd-ext.
- If you use DiskUsage to browse to /sd-ext, you'll see apps and dalvik cache there, which means it's working as it should.

do i need to do this? if so can you show me a guide.
also does mild wild 8.0 have built in apps2sd scripts and if so how do i use them.
i have saw videos on youtube with the htc desire internal memory going from 148mb to 1.5gb how can i do this?
thanks

You don't technically need to do to it, but in order to gain more app space you should understand exactly how your memory is being used in the first place.
Apps2sd is already enabled in the ROM by default as stated in the ROM OP. You do not need to do anything extra. Like I said, keep apps on internal and your apps and dalvik cache will be moved to /sd-ext, you should be able to check this now with DiskUsage.
I recommend starting here for fastboot guide, that's the only thing you're missing. Flashing things through fastboot isn't that hard once you get used to it, and can be crucial in certain situations. Once you flash the ROM on cm7r2 hboot, you'll be using your space more efficiently and have a lot more space for apps.
I know 287MB doesn't seem like much more. But this is /data partition is only used for app data. This will still get filled up as you install apps, but much more slowly :good: The apps and dalvik cache which take up much more space go to sd-ext, which is what you want.
You can refer to the same videos if you really want to see 1.5GB internal memory, they likely use a 'data2sd' or equivalent script but in my experience it's not worth it. You would have to remove the current working script, and replace it with something else, which is risky if it's incompatible and untested. Even if you do this, you're not actually gaining anything extra. You have already created the sd-ext partition; it's size is whatever size you set it when you partitioned. It does not change depending on the A2SD script.
I understand that having a 'visible' 1.5GB memory looks better...but once you realise your partition is already there and being used correctly, you don't need to see it.

thanks
i now have 288mb of internal storage with an ext partion sd of 1.4gb,
is that all i need to do now?
so when i install apps the mildwild 8.0 rom will move all to ext4 partion automatically?
also some apps i use to use now say "compatible with your device" is there a way around this so i can install them on my desire?
Thanks

Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?

eddiehk6 said:
Pretty much yes. Keep them on internal as instructed (don't 'move to SD') to trick them to sd-ext.
All you really need is reassurance that your ext partition is actually being used, which is why I always recommend DiskUsage. Have you actually tried it as first recommended?
Browse to your /sd-ext (or similar name) folder, the one which is ~1.4GB in total size. What can you see?
As for incompatible apps. Don't know. Which ones, are they for higher versions of Android? Have you tried sideloading the apks?
Click to expand...
Click to collapse
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.

tronic44522 said:
yes i have tried it as recommended.
when i browse /sd-ext i see 1423mib then the following dalvik-cache 76.7mib, app 66.4mib, system data 104.3 mib and freespace 1175mib
I also liked the guide on fast boot you sent me, as from using tips from it i was able to flash a new splash screen and boot animation. so thank you.
by side loading do you mean installing the apps with the apk file and not through the play store?
if so this works for some apps but now others. the app Im looking to use is the Argos app. before the recent update it worked fine but now when i went to update i get the device is incompatible message in play store. I have read some stuff on the build.prop method but am unsure if this would work.
Click to expand...
Click to collapse
Yep, all good, it's filling up so you have successfully added internal memory :good: plenty more space for apps.
Yeh that guide worked for me which is why I always recommend it. I liked changing the splash screen too (ironically can't be done on Nexus devices as far as I know)
Sideloading is as you described
The Argos app is compatible with Android versions 4.0 and higher as on the play store page, which is why it's incompatible with CM7 which is 2.3.x. The same probably applies to the other apps you're having trouble with. I've never messed with build.prop, probably could work, just make sure you make a nandroid backup before trying any of it.

[Q] [HELP] SM 113 Unable to mount external partition as sd-ext

Initially Titanium Backup's "move to SD" feature looked like a great way to use tools I was already familiar with to make the most of limited internal storage. While searching for answers on how to set up what TB needed, it became clear that pretty much any similar app or solution - e.g. Mounts2SD - would need this partition mounted to function properly.
Problem is I can't seem to get it to work, despite trying EVERYthing that all of xda forums and Google can tell me. And there's a lot of info on this topic.
This is the mount command in Terminal emulator:
Code:
su
busybox mount -t ext4 /dev/block/mmcblk1p2 /sd-ext
(where I've confirmed that /dev/block/mmcblk1p2 is the partition I want to mount, ext4 is replaced by correct filesystem, and /sd-ext exists and is the desired mount point.)
It seems to go fine... I don't get any errors or feedback. But TB doesn't detect the partition even after adding an "app" folder using "mkdir" command.
Here's way more info than necessary about my situation in case it might help...
Device is SM-113, KK 4.4.4. Rooted, stock everything, selectively debloated using Titanium Backup Pro
Recovery is TWRP 3.0.0
Busybox by Stericson from Google Play
This is what I've done, in all possible combinations:
— Have used 3 separate SD cards: 32GB fresh out of the package (largest size officially supported by this tab) and 2 used 64GB (no documentation but it mounted and works fine for regular storage!)
— Used TWRP, AParted (from Play store) and Minitool (on Windows) to create the partitions
— 2nd partition formatted as ext2 & ext4 (read somewhere that ext3 wasn't a good idea...)
— Size of the 2nd partition ranging from less than 10% of SD card size up to 10GB
— Mounting to /sd-ext, /system/sd, and /data/sd (per TB's knowledgebase, linked above )
I've also attempted using a few apps from Google PIay as recommended by various threads on the subject from this forum (don't even remember which but I can look them up if necessary). I've since wiped and restored a nandroid backup so that none of these can potentially get in the way.
This IS working on my (also stock, MM 6.0.1) Galaxy S5 (G900W8) with one of the cards that didnt work on this tab - a 4GB ext4 partition on a 64GB SD card. After TB recognized it I set up init.d support and it happily mounts on every boot.
So it looks like it's something to do with this device, which sadly has extremely limited space that makes me want to cry. Therefore, I hope someone else with the 113 can lend a hand.
If necessary, I'm totally willing to flash stock, re-root, and set everything up again in order to make this work!

Not too sure. I use Aparted and Link2SD on a couple of my older toys...lol. I use ext 3 too. I have a 210, I'll play with it and see if I can figure it out.

Thanks @RealWelder! Don't know if that'll help as it's a different device, but let me know what, if anything, you figure out.
Personally, I'm going to give it another shot using the 'Mounts2SD' app (even though I'd wanted to do this WITHOUT any new apps... oh well, if it works at least I'll have plenty of space!)

I got it to work! *happy dance* Absolutely NO idea exactly what did it, but there was a lot of fiddling with permissions, and rebooting, and painfully typing "mount -t ext4 etc. etc." into terminal, and making adjustments to init.d scripts until finally ... TB recognized it.
Thank you XDA forum!
Sent from my Samsung SM-T113 using XDA Labs