Database Develop

[Q] GUESTE'S 2.2 final ext4 - gallery - SOLVED!

Hello everybody!
As per title I am opening gallery and it sees only items installed in the internal sd, how can I let gallery look at .jpg files registered on the EXT SD ? I am not used to this filesystem. For example linking through USB to the car audio system let you listen only to songs installed on the internal SD.
ALL other considerations on the ROM are: perfect, particularly regarding battery life. Didn't find options for my SIP number account, using Sipdroid flawlessly .
Regards.
Alessandro

Try to force media files check. Go in Settings , Sdcard and memory, and unmount/remount sdcard.

Thanks for your reply, tried also folders rescan in dev tools, seems it scans EXT EMMC also but no results . Must look into some older thread in Acer Liquid, I remember smthg regarding a COOLIRIS.MEDIA file in sdcard in order to let device look into specific media for the type of files.
Will come back with results .
Regards , Alessandro.
So, I found that msg., but it regarded an old 2.2 version of Android for the Acer Liquid, and it said to cancel file in Android/data/, all the files in Cooliris.media, and reboot; maybe System remounts files in the SD when scanning for media and rebiults this file properlY ( it seems now untouched from the 23 of December ). Turning to EXT 4 as I am now maybe left EXT Sdcard unchanged: even if I set photos to be recorded in the external, photo is actually recorded only in internal SD ( which is a bit ..... full now, with nandroid etc. ) .
Need help.
Regards
Alessandro

solved
Found I had from 5/1/2012 a .NOMEDIA file in the root of External SD: deleted it and ... problem solved.

How to move apps from external sd to internal sd

So I have four partitions in my galaxy mini :
System rom 216mb (21.4mb free)
Internal 479mb(447mb free)
Sd card 15.3gb(13.5gb free)
Sd card(a2sd) 187mb(8.54mb free)
When I try to move my apps to sd card using the default move it moves to sd card(a2sd) and not to sd card .
So how do I do that ? + Is their a way I can move stuff from my system rom to other partitions ?

im abcd said:
So I have four partitions in my galaxy mini :
System rom 216mb (21.4mb free)
Internal 479mb(447mb free)
Sd card 15.3gb(13.5gb free)
Sd card(a2sd) 187mb(8.54mb free)
When I try to move my apps to sd card using the default move it moves to sd card(a2sd) and not to sd card .
So how do I do that ? + Is their a way I can move stuff from my system rom to other partitions ?
Click to expand...
Click to collapse
First Search in Google Then Post......
P.S.=Don't Spam please

pratyush369 said:
First Search in Google Then Post......
P.S.=Don't Spam please
Click to expand...
Click to collapse
Sorry to not meet upto your expectations but nowhere in google did I find the desired result and In no way do I feel that I have spamed xda forums .
Maybe you can help me to recognize in what way I have spammed ?

Bump , no help ? :/

sdcard, external_sd
a2sd is moving apps to your other partitions. the 16 gig card you got has to be the one where you got to move apps. all apps are stored in your internal memory. the system rom is read only, so you wont be able to move or erase it. its permanent, programmed at the factory. so forget rom. if you formatted your sdcards correctly, then you must be able to delete partitions, or reformat them. i recommend deleting the partition after uninstalling all apps on that partition. remember, you are rooted, so if you have root access apps on that partition, then you first have to undo everything the apps did. eg: if you have chainfire, then you got to remove all plugins(qualcomm, nvidia, powervr if installed) the cf3d plugin with egl if installed, then uninstall cf. connect your mobile via usb cord, or get your sdcard in a memory card reader, connect to pc. use "device manager" in your pc to see all partitions of your hard drives. look for your sdcard drive, and you will see all types of data divided in it, that is, formatted data, raw data, etc. if you see raw data, then you have to format it, and its likely that you will be done there. but i f you see formatted data, then just delete the 8 mb partition, and then its possible that you may succeed. this is dangerous, and your data can sort of "vanish", but it will only be the 8mb data according to me. its also possible that you may not be able to delete the partition after all, as this usually works for hard drives. if so, you may use hp format tool to format your device to NTFS and try again. this also can make your data vanish by what you say. the simplest would be to try and delete the partition from your mini itself. the app which you used to partition must allow you to remove partitions also, so look for it. and if this particular app is in the sdcard(a2sd), then you would better move tit to phone memory first. remember, uninstall ALL apps on the partition, and undo ALL the changes they made to your device before trying this out. this may horribly go wrong, so beware! (i havent tried it yet, so. and someone gifted me an ipod 5g, which i tried to partition, but was unsuccessful.) just hit thanks if you find this helpful!
---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------
Link2SD is an application that makes it easy for Android 1.6+ users with root privileges on their phone to move applications to the SD card.
The idea behind is same with apps2sd scripts, linking applications to SD card's second partition but differs in two ways.
One, instead of linking /data/app folder (that means moving all applications), you can select applications that you want to move.
Two, it's an application which means has a user interface. You can manage your applications with few clicks.
It also provides native apps2sd features on Android 2.2 and higher. It can move any non-protected user apps to SD card (force move), with batch moving capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).
Features:
- Create and remove link for apk, dex and lib files of the applications you select
- Automatically link newly installed apps (optional)
- Move any user apps to SD even though the app does not support moving to SD (a.k.a. "force move", for Android 2.2 and higher)
- Shows the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- Set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- Batch link, unlink, reinstall, uninstall, "move to SD", "move to phone" functions (multi-select mode)
- Uninstall system applications (bloatware removal)
- Freeze and un-freeze system and users applications
- Convert system apps into user apps
- Convert user apps into system apps
- Integrate "Updated" system apps into system (ROM)
- Clear data and cache of the application
- Clear all apps cache at once (1-tap cache cleaner without being root)
- List applications, show detailed size information and link status
- Sort and filter applications
- Search applications by name
- Display available space information of internal storage, SD card and SD card 2nd partition
What you need:
- root permission.
- a second partition on your SD card.
You should have two partitions on SD card and both should be primary.
The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4 or FAT32.
Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need ext2.ko or ext3.ko modules and even some additional modules to be able to mount. Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones.
Link2SD does not create the second partition, you need to create it yourself. You can use any partition manager such as Minitool, Paragon, Easeus etc. for this.
How it works:
Link2SD mounts the second partition of your SD card and makes OS mounts it at boot time.
When you press "Create Link" button Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's 2nd partition and creates symbolic links in original directories.
Note: On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if you move the apk file.
You can remove the links and put application files back to phone. Just click on "Remove Link" button.
Some points
- System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
- When you connect your phone to PC as mass storage, Android unmounts the first FAT partition but the second partition remains mounted. Therefore linked applications are not affected and can be run without problems.
- Link2SD does not move application's private data files; it moves apk, dex (dalvik-cache) and lib files.
DISCLAIMER: It is made available for use at your own risk with no warranty of any kind.
you may try this before everything else!

To move apps to sdcard, use link2sd and long press the desired app & select "Move to sdcard"(if u have root).
Sent Via XDA™ Premium

[Q] internal_sd is swapped with external_sd by phone

Greetings to all,
I have a Galaxy S GT-I9000 which I bought last year.
I had no problem flashing any firmware with odin and every flash I made was successful.
I never had an external_sd card ever since I bought the phone.
Now my problem started when a couple of months ago I flashed ICS 4.03 from CWM from
an external_sd card.
As strange as it may sound, all apps and media files where installed on the external_sd
card. I found out about this after the phone booted up successfully and by checking the contents
of both the internal_sd & the external_sd cards. I wasnt bothered by this as long as the phone
boots up normaly and storages mount.
Now I wanted to flash XXJW4, I did everything by the book. (i.e factory reset, clear cache, clear delvik)
and flashed successfully.
The phone entered into an endless bootloop.
Taking out external_sd card and booting to recovery 3e results in /sdcard & /data mounting problems
Inserting external_sd card and booting to recovery 3e produces no mounting problems. in fact I can
clear cache and factory reset.
So my guess is that: the phone identifies the external_sd card as internal_sd and mounts it to search
for booting parameters but fails to find it, because the card is formatted and has no os.
Creating three partitions for fat32, ext2 or ext3 or ext4 and a linux-swap and flashing any firmware results
in the phone booting up normally with out any problems.
My question is: how is it possible to change where the phone looks up for boot sectors (If I may use windows terms )

According to this wonderful post h t t p : / / python . ca / nas / log /201204 /by Neil Schemenauer's Web Log
the phone internally has two built in flash memory devices:
- NAND device (8 or 16GB)
- Flash memory for (BML or MTD schemes) used by the ROM
Now the problem might have been created by the ROM's flash memory, it ignore the NAND device
and tries to boot up from the extended memory (external sd) which results in a boot loop if it doesnt
find the OS that's looking for (in our case Android).
ANY ONE PLEASE give me any idea or hypothesis if you like, as to how to go around this problem.
A complete boot up process for the device would be very help full. I understand most Galaxy I9000 phones
are having these problems.... Lets SOLVE THIS

So I'm I the only one having this problem...... STRANGE.!!!!

One week after my first post,... No one had dared to post any idea.
It seems sda developers rarely visit the Q & A.
Any ways I managed to solve the problem, it was a faulty jumper
on the main board.
This thread is closed

I might have a similar issue....some application settings/data etc are being installed on the external card and the "external SD" folder leads to nothing (no files there - while using the emmc folder in the root directory does access the external card. So, it appears the system is messed up (but still working).
Unfortunately, I can't help you solving your problems but I found out that flashing some old stock rom (GingerBread 2.3.6 JW4 or JW7) brings things back to normal - at this stage I'm experimenting with new custom roms and as long as my external card is accessible I'm not bothered if the messed up folders....still, a neat solution would be very much appreciated.

Thank you xelaris for your post,....
In my previous post I had mentioned flashing JW4 and that didn't work.
Installing the ROM on the external_sd card with at least two partitions one ext2 or ext3 or ext4 (for data) and vfat or fat32(for usb storage)
most certainly work. But performance will be reduced dramatically as the external sd requires more time for read/write operations.

[Q] KitKat Partitioning Issue

At the risk of sounding like a complete n00b, I come to you all with an issue I'm experiencing. I know it's an operator error, so bear with me;
I just recently flashed Milaq's KK build. I increased the /system partition using the new CWM w/ data/media to 512 mbs. Everything is running well, but all the apps I install are installed to the internal memory, which maxes out around 1.4 gbs. My question is, how do I make the default install location the virtual ext SD card?
I hope this makes a bit of sense to you all - because I'm about to pull my hair out here.
Thanks for any/all input on my current situation.

I understood the partition/directory structure in my previous CM7/CM9 installs.
But with the new datamedia storage configuration I'm confused to all the various labels for the memory storage areas.
I've read the document at http://teamw.in/DataMedia
but the situation is still not very transparent.
• Under Android settings I see "Internal Storage" and "SD Card" and "USB Storage".
• In ES File Explorer I observe:
/sdcard ->
/external_sd -> /storage/sdcard1
/usbdisk -> /storage/usbdisk
/storage/emulated
/storage/sdcard0 ->
/storage/sdcard1
/storage/usbdisk
• In X-plore I also observe:
/storage/0
/storage/legacy
• CM File Manager app top level directory is labeled as "0":
It appears there is various crossover in directory mappings. Is there a definitive guide as to the partitions, directory structures/mappings and symlinks that apply to the above memory areas. There is already enough contradictory posts in various development threads on this so not asking for assumptions/presumptions. Hoping to hear from an expert/developer who knows this stuff on back of their thumb.
And what controls/manages where new apps are installed?

Good Question I also would like to know

While looking around the internet, I found this as a potential option;
In terminal;
su
pm set-install-location 2
I attempted it, but haven't noticed any difference.
/bangshead/

Stryeguy said:
While looking around the internet, I found this as a potential option;
In terminal;
su
pm set-install-location 2
I attempted it, but haven't noticed any difference.
/bangshead/
Click to expand...
Click to collapse
I think you are looking at this wrong. Instead of making Android use the external storage by default, you just need to make the data partition bigger and use that as your default storage. Milaq himself suggested this partition layout:
system - 600mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)
If you are going to go with Milaqs builds, The best way to do it is to move all your stuff from your sd card to your computer, wipe your sd card, use tailor in webOS to repartition to match what Milaq suggested and move all your stuff back onto your device in, I think, the sdcard0 folder (which should now have the majority of the space).

jsgraphicart said:
I think you are looking at this wrong. Instead of making Android use the external storage by default, you just need to make the data partition bigger and use that as your default storage. Milaq himself suggested this partition layout:
system - 600mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)
If you are going to go with Milaqs builds, The best way to do it is to move all your stuff from your sd card to your computer, wipe your sd card, use tailor in webOS to repartition to match what Milaq suggested and move all your stuff back onto your device in, I think, the sdcard0 folder (which should now have the majority of the space).
Click to expand...
Click to collapse
Thank you for your response - it was exactly what I was looking for. I knew I was overlooking a step.
I'll get around to doing that tonight.
Again, thanks so much.
:cheers:

I had the same question. But I just used tailor to resize the partitions. If it says file system error, let it fix it. As long as there are free space, all your files will stay.

Just posting a follow up;
Installed Tailor and repartitioned as per Milaq's instructions, and everything is working as it should be.
Thanks for the help, guys. Glad to know it was just my reading skills that were lacking.

Marshmallow Unused Partitions Small \data possible solutions

Hi everybody.
I flashed CM13 with success inside the Unsued Partitions (aka Safe Slot), along with the OC kernel.
I tried then to see if I was able to actually use the phone day to day. I was immediately faced the issue of the small /data partition, which, with the pico gapps, starts with nearly 700MB used (first boot), more than half of the available storage.
The built-in "move to sd" option (only for some apps) doesn't move the biggest files to the external storage.
Is it possible to use the "adoptable storage" option for Marshmallow on the Droid 4? (obviously with a suitable sd card).
Will it encrypt the sd card partition by default?
Thank you very much for your help,
sweetsuicide

Bump

Bump

Ok,
I found the time to test it out myself. Adoptable storage is indeed available in cm13, but it actually is of limited help: most apps WON'T move to sd. Is this the intended behavior or am I doing aometinf wrong?