I've ordered a used Asus c101 with 16gb of storage. I think 16gb will likely be enough. However, I'd like to get android applications moved to the sdcard.
I know this isn't officially supported but a linux based system should be capable of it. In Ubuntu I would simply remount the apps directory (whatever that is) to a different partition in the fstab file. I know ChromeOS doesn't support fstab, but there are a couple start scripts in /etc/init that look very similar.
As far as I can tell, I'd have to be in Dev mode to edit these files. Is there a root option without Dev?
Has anyone attempted this?
Related
I'm seeing almost every app (except for CWM recovery) thinks the
/mnt/sdcard directory is the external card (which is true in most
android devices). So they are looking in and placing files in the wrong
place. Smarter apps allow me to set a virtual root for it to start with,
but Kindle and Nook insist on looking in /mnt/sdcard/<appname>
for the stored books.
Does anyone know a workaround to repoint /mn/sdcard/<appname>
to /mnt/sdcard/ext_sd/<appname>.
Personally, I think the idea to change the meaning of
the /mnt/sdcard, (from the uSD card to part of the on
board flash memory), was not thought out well.
Yeah its a head scratcher. I assume that HTC decided after putting out a $600 tablet they could save money by not including a $7 SD card in the ext. slot and just defaulted everything to the internal SD. I'm sure someone could write a script to change the mount points on rooted ROMs, but not sure what might fail if you change cards.
hmm as a temp workaround I guess I can run a script to copy the
/sdcard/ext_sd/nook and /sdcard/ext_sd/kindle directories
to the corresponding places on the internal 'sdcard'?
Does android have an rc.local like file to run after the system mounts the two devices, and one to run at shutdown, to do the copies?
being vfat, I can't softlink the directories to point to the real sdcard
is there a way to overlay mount the 2 directories from the real sdcard
to the internal flash sdcard?
While doing some internal storage cleanup, I came across a bunch of junk files in the Opera cache. I'm guessing I had Opera running at some point when my phone died not so gracefully, corrupting whatever it was doing at the time. The immediate problem is that I can't delete these files. The file system utilities cannot find the files, but the file names are still in the FAT somewhere:
Code:
/mnt/sdcard/Android/data/com.opera.browser/cache/cache/g_0027 # ls
ls: ./[email protected]Â¥a»â©âª./â¤â¬: No such file or directory
ls: ./â¤cr[âÏ
.âb.: No such file or directory
ls: ./º4ô/.áuâ*: No such file or directory
ls: .±gy/â*B.âÎü: No such file or directory
ls: ./òú)â©â§+.â/ü: No such file or directory
ls: ./±Ï=%âid
.âµ/: No such file or directory
ls: ./iaòêâ*·âñ.â/w: No such file or directory
My first question (although less important) is can I delete these files using some unconventional method (not including formatting the space)?
My larger question, and the one hinted at by the subject, is this: is it possible to format the internal SD space as ext4? From what I understand after doing some Googling, the stock kernel (and perhaps Android in general) is designed around the idea that your non data space would be formatted as VFAT (it's built into the /init.rc inside the zImage according to one thread in the i9100 forums). Is this also the status of CM7/9? I did find an entry in the CM forums from last October where somebody just did it on a whim and ran into issues, to which others replied that apps2sd can use the space when set up for it...but no solution for actually using the space as regular storage.
I know enough about coding to really muck stuff up (I took a real basic C++ course way back in high school, know very little java, and a decent amount of scripting languages, but that's about it...I can stumble through reading code, but it'd be a mess trying to change it), so I'm not exactly inclined to dig into this that far, but I wouldn't mind assisting in some way if someone else was interested (I'll be happy to be a guinea pig, and don't mind trying to figure out some of the code stuff...I just wouldn't know what to do with it all if I did figure something out). I rarely connect to my phone via USB anymore, even more rarely do I mount the SD as mass storage to a PC, and yet more rarely still do I connect to a Windows PC via USB and mount as mass storage. Unless there's a good, solid argument for why the space uses VFAT besides compatibility with Windows, I'd love to be able to switch to a journaled file system.
I have a 128 GB microsd and I do not want FAT32 on it. I have MIUI 8 (Android 5.1.1) with 3.10.49 kernel, TWRP 3 and root. For some reason mount doesn't work at all, it always produces error "Invalid argument". I tried replacing it with one from BusyBox but it didn't help. Some forum guys told me that I should add the card to fstab (which AFAIK is located inside boot.img), and edit the config of vold (which is located I have no idea where). Also this. All I understood from there is that there is some storage_list.xml and I should edit it. Again, searching through forums led me to this path framework-res.apk\res\xml\storage_list.xml.
But still! I have no idea where this framework-res.apk is located and how do I unpack-repack it.
All info that I'm desperately trying to extract from google is outdated or related purely to cyanogen >_< Please give some instructions
You wrote you don't want FAT32. Other filesystem than that isn't supported by MIUI which is why you won't succeed to show your card content by editing anything. You need a 3rd party libs with your filesystem support.
See here, worked for me http://forum.xda-developers.com/showthread.php?p=61142640
or install a custom app with your filesystem support (eg. Paragon NTFS).It works either.
Sent from my phone by Tapatalk
Dude, that's the f$#@ed up part, you see.
> If you use KitKat
And I'm using 5.1.1 which is technically lollipop.
I'm seeking for a support as close to native as it can be, so I'm not involving any "mounting" crapware, especially Paragon's products, I'm fed up with their ext4 4 windows driver which gave me countless BSODs and corrupted files.
You said that MIUI doesn't support anything but FAT32, but that's not 100% true. It by default supports only FAT32 for external storage. But at the same time it mounts internal storage (which is of course in ext4) no problem. So I guess it's not *unable* to use ext4 (or f2fs, which is AFAIK supported by any kernel after 3.10.*) for external storage, it's just not enabled by default, and the question is how do I properly use that ability of android to mount ext4 (and/or f2fs)
UPD: I have to apologize for posting "also this" in the initial post w/o actually giving the link, here it is.
This is what seems actually related, but I'm too noob to understand what am I supposed to do to mount the damn card
First, the ROM and/or (especially) kernel should have F2FS support, then ramdisk should be modified with fstab edited so it could mount F2FS partitions at boot.
Other than that, it's impossible.
Sent from my ASUS_Z00A using XDA Labs
Hi folks,
I'll keep this short and sweet. New to Android dev but am a software engineer by trade.
Assuming I have a custom kernel with F2FS baked in to support AOSP/CM. I've modified my vold.fstab on my ramdisk to support F2FS on /data and /cache. Some of this was trial and error, looking at similar ramdisks on GitHub, etc.
Despite all that, it seems Android won't accept that alone for microSD. I still get "SD card is corrupt" when setting the SD card as "Portable storage".
I'm able to su mount -t f2fs /dev/block/mmcblk1p0 /mnt/randomdir no problem. However that is not "native" support and only propagates to the root user.
Any tips in the right direction? Hopefully the question is generic enough to be a general AOSP case, but if it matters I am working with Samsung Galaxy Note 3 right now (HLTE).
Thanks,
Sam
Greetings!
I have an LG V60 which is carrier unlocked, though it is the T-mobile variant and it just so happens that T-mobile is my service provider.
When I purchased my V60, Android 10 came installed and within a few weeks the Android 11 push had started. I have a ton of apps on my phone and a bunch of data, so I bought the largest SD card available at the time, which was a SanDisk 1 TB SD card. I immediately configured adoptable storage without any issues whatsoever. I enabled the option under developer options to allow apps to be installed on external storage even if the manifest file says otherwise. My upgrade to Android 11 was a piece of cake, and life was pretty good.
Fast forward to two days ago. T-Mobile started putting pressure on me to in install Android 12, so I cleaned up my V60 and let it rip.
My phone booted up with Android 12 and the only glitch I noticed was a warning about my SD card being ejected and that I should insert it again if I wanted to use it. It was still installed, so I physically ejected the card and reinserted it. The system remounted the 600GB partition I use for general storage, but I noticed some very important apos seemed missing.
After hunting around a bit, I realized that the mount point for the adoptable storage partition was not shown. I then used Termix to get to a shell and tried to run sm to figure out what was going on. Much to my disappointment, I can't locate the sm utility after issuing a find command from Termix. Note that my device is not rooted.
I ask pretty much at a loss about what to do. I don't know enough about how all this stuff works internally, so I'm reluctant to copy sm from an earlier version of Android and just see if it works.
Aside from reverting back to Android 11, which I'm pretty sure is doable, but by using the firehose driver, an engineering bootloader, and QPST, I am at a loss about what to do.
I just can't believe that LG/T-mobile could be so inconsiderate as to not identify adoptable storage configurations before proceeding with the installation of Android 12. I am locked out of many of my most important apps, the most noticeable loss is AquaMail, which I rely on heavily to manage several email accounts.
Any thoughts on how to proceed? I really hope there's a silver bullet that will get me out of this logjam.
I would be grateful if anyone out there who understands this stuff better than I do (which isn't saying much because I know just enough to be dangerous, it seems) can help me out of this bind.
Thank you!
Here's some additional information that I learned since I posted my issue yesterday.
Adoptable storage, or at least the "sm" utility used to manage it, *IS* actually present on my device. I forgot how tightly the file systems have been locked down, so the 'sm' until is only accessible from a shell started by adb. So, the fact that I couldn't manipulate adoptable storage from Termux is not really an issue at all; it's expected.
That said, I am still having trouble with adoptable storage. Here's what I know:
sm list-disks shows disk:179,0. This is consistent with other installations.
sm list-volumes shows, among other things, private:179,3 unmountable. Previously it showed private:179,3 mounted 8hex-4hex-4hex-4hex-12hex, and that gnarly file name corresponded to the mountpoint /mnt/expand/8hex-4hex-4hex-4hex-12hex. The filesysyem was ext4 and it was /dev/block/dm-3. That is where my adopted storage was located. Now the device can't seem to access that filesystem at all.
Any thoughts? I really hope there's a stupid-easy fix to this, or I'm going to lose a ton of data.
Thanks!
Just thinking out loud, but have you tried the card in a PC so see if you can backup the data before you do anything.
I would go so far as to say, you DEFINETLY CAN back up the data. Use dd to make an image of the card. If you are tight on space you can pipe it into gzip but I would recomend just leaving it uncompressed as its easier to access the files in the image if you need to later. I run zfs with compression so it doesnt save much space anyway. Allways make two copies. I dont mean make one image and copy it. I mean, image it twice. If your REALLY paranoid or its really really important to you (like it contains all the blackmail pictures on your boss, your bitcoin and those videos you made with your really hot ex-gf), you image it twice on different computers.
You can find the procedure on google. If you dont have a pc with linux you can find a recovery disk or live cd distribution.
Greetings,
Sorry for taking so long to respond. I can mount the SD card on my PC, but what's visible is my 800GB encrypted exFAT partition which normally mounts on my V60 as /storage/abcd-wxzy. What's not visible is the ext4 partition that normally mounts on my V60 as /mnt/expand/8hex-4hex-... My PC has software on it to automatically mount ext4 partitions (Linux Filesystems for Windows by Paragaon Software) and it works fine. When I examined the partition in a sector editor, it shares nothing in common with other ext4 filesystems, which leads me to believe that it is encrypted.
So basically the upgrade from Android 11 to Android 12 seems to have made my adopted storage volume completely inaccessible. I have tried unsuccessfully to downgrade from Android 12 to Android 11, but that was a complete disaster. I am not sure if there is a proper method to downgrade from Android 12 to Android 11. I'm sure LG tries to prevent downgrades, but I have seen examples of operating system downgrades previously, just not from Android 12 to Android 11 on the LG V60, specifically.
I am at a loss. I fear my data on the adopted partition is lost, which would be horrible.
By the way, I can and have imaged the physical partition on my SD card that contains the ext4 partition that is used as adoptable storage, but I can't do anything with it because it is completely unrecognizable. I'm still going with the theory that it's encrypted.
I beg anyone who has any insight on how to get past this to please share what they know. I'm getting desperate. I can't possibly believe an upgrade from Android 11 to Android 12 would kill my adoptable storage volume. That just doesn't make any sense :-(
Thanks!
pqcracker2 said:
so I cleaned up my V60 and let it rip.
Click to expand...
Click to collapse
do you mean factory reset? if yes your data is 100% gone
the encryption keys are all stored in the userdata partition so if that partition got formatted somehow (be it bootloader unlock or sth else) they are lost, and even if they are not lost itll be hard/impossible to get to them as android 11/12 locks down read access to the userdata partition extremely