Related
I'm trying to understand why i cannot put a video of > 4GB to /mt/sdcard/video. I had assumed there was some use of vfat filesystem, but after digging into it, it appears not.
The mount table is such that
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
and /sdcard is a soft-link to /mnt/sdcard.
If i look in /data/media/video, which is on the ext4 filesystem, i can put a file > 4GB.
But when i try instead to write this to /mnt/sdcard/video, it fails.
What is the rationale for the fuse mount of the /data/media onto /mnt/sdcard? Is that part of the MTP mounting system for USB?
Is there any reason i cannot just either use the path of /data/media for everything and/or change /sdcard link to point to /data/media instead of /mnt/sdcard?
if i grep around in the *.odex files i find some reference /sdcard, and some reference /mnt/sdcard. What is the rationale for that?
Where is the script that does the fuse mount of /data/media to /mnt/sdcard? It doesn't seem to be /etc/vold.fstab. Is it the /init.p3.rc script? It seems to just run /system/bin/sdcard. Is there a reason i cannot just make that be 'ln -s /data/media /mnt/sdcard' instead of 'service sdcard /system/bin/sdcard /data/media 1023 1023 ' or will i end up with file permission problems?
I have been tryying to get the Nabi 2 to mount micro sd card/sdcard2 as internal storage/sdcard. I have altered the vold file on AN7G3 Arnova 7" tablet so as to have 32 gig internal instead of 4 gig, works really well. Also know many have done this for other devices and works on GB 3.2 and ICS 4.03. Nabi2 has ICS 4.0.3 but can not get them to switch. when i change sdcard and sdcard2 and reboot, device can not reconize micro sdcard/sdcard2 and openning settings/storage on the device cause the storage to force close. ES File Exployer does not reconize sdcard2. Is there a way to achieve this with the vold file or does this have to be done thru adb. If adb could someone help me with the commands. This device IS rooted and Google Play installed. I will include a copy of the vold.fstab as a vold.txt. TIA as several folks need this info and i will relay your info or you can on the Nabi 2 thread.
i don`t see the internal storage defined in the vold.fstab
can you put the output from mount ?
globula_neagra said:
i don`t see the internal storage defined in the vold.fstab
can you put the output from mount ?
Click to expand...
Click to collapse
Not really sure what you want. The internal storage is named sdcard and micro sdcard is named sdcard2. In settings/storage they are listed as internal storage and sdcard. Es File explorer sees them as sdcard and sdcard2. If I know what you need, I will get it for you.Need
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2 (this is the external sd card)
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.0/usb2 (this is the host where you can connect a mouse, etc.)
this what apears in your vold.fstab
so, the line for the internal storage is missing
on my tablet it looks like this
dev_mount sdcard /mnt/sdcard 20 /devices/platform/msm_sdcc.2/mmc_host (internal storage)
dev_mount sdcard1 /mnt/external_sd auto /devices/platform/msm_sdcc.4/mmc_host (external sd)
dev_mount udisk /mnt/udisk auto /devices/platform/msm_hsusb_host.0/usb1 (host for mouse, keyboards, etc)
This is the "mount" in adb shell
C:\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sh-3.2# su
su
sh-3.2# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,d
ata=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,
data=ordered 0 0
/dev/block/mmcblk0p17 /content ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=
1,data=ordered 0 0
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
sh-3.2#
I agree, this vold is different from what I have delt with in my limited experience. Here is a screen shot of mount on terminal emulator. Does this give you the info that you requested.
well, in the mount the internal storage it appears, is strange that it does not appear in the vold.fstab
i think the internal storage is triggered by the boot.img, or a .rc from the /etc
you could have a look on a nexus tablet, or acer iconia110 to see how is defined there the internal storage in vold.fstab. (since all are having tegra 3, you should have a corect image)
globula_neagra said:
well, in the mount the internal storage it appears, is strange that it does not appear in the vold.fstab
i think the internal storage is triggered by the boot.img, or a .rc from the /etc
you could have a look on a nexus tablet, or acer iconia110 to see how is defined there the internal storage in vold.fstab. (since all are having tegra 3, you should have a corect image)
Click to expand...
Click to collapse
That's a good thought as Nabi2 is very close to the nexus 7 . Will try and run those down. Thanks
I have just spent the last 2 hours attempting to mod the Vold file in like 4-5 different ways and nothing worked I took the moded Vold file off my LG Esteem Smart phone which has a moded Vold file that makes my extsdcard the Internal Memory and studied it to find there is only like 2 sets of 2 words and numbers that are switched from one line of code to another and THATS IT!! The rest of the code is letter for letter number for number the same!... So I tried applying the same technique to my Nabi 2's Vold file and no matter what it just makes the extsdcard (sdcard2) appear not there anymore and has the following message in the storage status tab.. "Insert an SD card for mounting" Someone's gotta tackle this!!
It was suggested that I/we as clarkiss run an su file with script manager and alter the vold. We did this and still force close when openning settings/storage. Used original vold and ran script, when opened settings/storage, I see my micro sdcard listed as internal storage and sdcard2. Es File explorer sees micro sdcard as sdcard and sdcard2, nothing sees the internal storage but any programs or games still install to the unseen internal storage.
Anyone have any idea on this? I have included the sdcard_switch.su that we ran with script manager, in hope that with the vold posted above someone might have an idea to help us. There are quite a few folks looking for this and will be more as they by these for christmas.
Thanks.
I figured I would post the original Vold.fstab to see if anyone has any ideas or suggestions... If you need me to post anymore files let me know and I will quickly get posted!! The below code is the entire contents of the Vold.fstab... I also have included a link to download (Hosted by my Box account) the Vold.fstab file at the bottom of this post after the code as well incase anyone wanted to help us play with it :silly: Help with this on any level is more then welcome!!
Contents of Vold.fstab file (Code)
## Vold 2.0 fstab for kai
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard2 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2
dev_mount usbdrive /mnt/usbdrive auto /devices/platform/tegra-ehci.0/usb2
https://www.box.com/s/2az7hod00g9fbenn3j14
If anyone has a vold.fstab from a nexus tablet, or acer iconia110 tablet that they could share. I would like to see them to compare with the nabi 2.
as i said, on you guys, the vold does not trigger the internal storage (have a look here on this lines )
/dev/block/vold/179:97 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow _utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharse
As you can see this line: /dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime, is the internal storage, on your vold, this line is missing
therefore you should start and search when the internal storage is mounted
the line that defines the internal storage is
dev/fuse mnt/sdcard
you should look maybe in the boot.img ?
it should look like this
dev_fuse sdcard /mnt/sdcard fuse
---------- Post added at 02:02 PM ---------- Previous post was at 01:58 PM ----------
this is the vold from HTC one x, tegra version.
## Vold 2.0 fstab for endeavor
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 14 /devices/platform/sdhci-tegra.3/mmc_host/mmc0
As you can see the internal storage is trigered by the vold.
globula_neagra said:
as i said, on you guys, the vold does not trigger the internal storage you should look maybe in the boot.img ?
Click to expand...
Click to collapse
Sounds good...How do I look in the boot.img? Is there a program or something of that sort to use? Could you give me a quick guide on the steps to take to look in the boot.img?
globula_neagra said:
as i said, on you guys,
it should look
As you can see the internal storage is trigered by the vold.
Click to expand...
Click to collapse
I also don't know where to start. Sorry to be so lost but really don't know what to do from here. Any help pointing us to what we need to do would be great. We are learning and follow direction. I have looked for the info but no luck.
We are noob's but trying. Lol
Located the boot.img
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
---------- Post added at 07:23 PM ---------- Previous post was at 07:17 PM ----------
Clarkiss said:
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
Click to expand...
Click to collapse
Scratch that lol its just the god damn boot animation in the beganning damn it!!!!!:crying:
Clarkiss said:
I think I located the boot.img... After reading and jumping from link to link forum to forum I came across "bootanimation.zip" in /system/media. Im going to unpack it and study it via HowTo: Unpack/Edit/Repack Boot Images website
---------- Post added at 07:23 PM ---------- Previous post was at 07:17 PM ----------
Scratch that lol its just the god damn boot animation in the beganning damn it!!!!!:crying:
Click to expand...
Click to collapse
You know, jmztaylor has img files at
http://androidfiles.org/uploads/?dir=Nabi2
I just don't know how to unpack it?
ALD3 said:
You know, jmztaylor has img files at
http://androidfiles.org/uploads/?dir=Nabi2
I just don't know how to unpack it?
Click to expand...
Click to collapse
Ok im starting to get deeper and deeper into this lol I have unpacked the ROM we are running on which of course is from jmz with Android Kitchen/Cygwin and I am looking at Working Folder Information in the Kitchen and I see something I kinda dont like... Of course there is like 10-15 lines of information like Android OS version: 4.0.4 and ROM Name: JmzStockNabi and so on but this is what is bothering me... One of the lines reads as follows.. Apps2SD <Apps to EXT> enabled: NO .... I wonder what would happen if that were changed? anyone have any suggestions?
stripped Nabi 2 ROM
After extracting the BOOT.img and opening the "BOOT- EXTRACTED" folder it created I found another folder in that folder called "boot.img-ramdisk" and inside it was the following:
[folder called] data
[folder called] dev
[folder called] proc
[folder called] sbin
[folder called] sys
[folder called] system
[PROP file called] default.prop
[file called] init
[RC file called] init.goldfish.rc
[RC file called] init.mt799.rc
[RC file called] init.nv_dev_board.usb.rc
[RC file called] init.rc
[RC file called] init.tf.rc
[RC file called] ueventd.goldfish.rc
[RC file called] ueventd.mt799.rc
[RC file called] ueventd.rc
I started studying all the files and the one that looked most interesting to me and what im trying to do is the "init.mt799.rc" file!:laugh: It seemed to reference quite often the sdcard, sdcard2, and external storage so that got me a little happy haha! Seems like I might be starting to get to the bottom of this riddle :fingers-crossed: So I copied and pasted the entire contents of the "init.mt799.rc" file code below to see what you guys think! And if you guys want me to post/attach any one of those other files let me know which and I will immediately
"init.mt799.rc" file contents
#Copyright (c) 2012, NVIDIA CORPORATION. All rights reserved.
import init.nv_dev_board.usb.rc
on early-init
mount debugfs debugfs /sys/kernel/debug
# for backwards compatibility
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE2 /mnt/sdcard2
mkdir /mnt/sdcard 0000 system system
symlink /mnt/sdcard /sdcard
mkdir /forever 0644 system system
mkdir /sct 0644 system system
mkdir /mnt/sdcard2 0000 system system
# create directory for mounting usb drives
mkdir /mnt/usbdrive 0666 system system
symlink /mnt/usbdrive /usbdrive
on fs
# Mount system to allow checkpoint and set NVSI symlink
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system rw
# Create NVSI filter symlink
symlink /data/data/com.nvidia.NvCPLSvc/files/com.nvidia.nvsiutilv1.xml /system/etc/permissions/com.nvidia.nvsiutilv1.xml
# Remount system read-only
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system wait ro remount
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
setprop ro.crypto.umount_sd false
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA /data wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,errors=panic
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC /cache wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,errors=panic
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDD /forever wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc,
#mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/SCT /sct wait noatime nosuid nodev journal_async_commit,data=writeback,nodelalloc
on post-fs-data
mkdir /data/addon_res 0770 system system
mkdir /sct 0644 system system
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
mkdir /data/misc/dhcp 0770 dhcp dhcp
mkdir /data/nvcam 0700 media camera
chown dhcp dhcp /data/misc/dhcp
chown wifi wifi /data/misc/wifi
chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
chown wifi wifi /data/misc/wifi/hostapd.conf
mkdir /data/misc/wminput 0776 system system
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
# Set indication (checked by vold) that we have finished this action
setprop vold.post_fs_data_done 1
chown system system /forever
mkdir /forever/misc 0774 system system
mkdir /forever/misc/dmt 0777 system system
chown system system /sys/class/accelemeter/dmard06/enable_acc
chown system system /sys/class/accelemeter/dmard06/delay_acc
on boot
#reboot_flag
chmod 0666 /dev/block/platform/sdhci-tegra.3/by-name/UDE
# bluetooth
# bluetooth MAC address programming
chown bluetooth bluetooth ro.bt.bdaddr_path
chown bluetooth bluetooth /system/etc/bluetooth
#setprop ro.bt.bdaddr_path "/system/etc/bluetooth/bdaddr"
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
# bluetooth
# bluetooth MAC address programming
chmod 0660 /sys/class/rfkill/rfkill0/state
chmod 0660 /sys/class/rfkill/rfkill0/type
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/state
chown bluetooth bluetooth /sys/class/rfkill/rfkill0/type
# NFC
#setprop ro.nfc.port "I2C"
# backlight
chown system system /sys/class/backlight/pwm-backlight/brightness
# didim
chown system system /sys/class/graphics/fb0/device/smartdimmer/enable
chown system system /sys/class/graphics/fb0/device/smartdimmer/aggressiveness
# power
chown system system /sys/kernel/tegra_cap/core_cap_level
chown system system /sys/kernel/tegra_cap/core_cap_state
chown system system /sys/module/cpu_tegra/parameters/cpu_user_cap
# Power management settings
write /sys/module/cpu_tegra3/parameters/no_lp 0
#write /sys/module/tegra3_emc/parameters/emc_enable 0
#write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 1000000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor conservative
write /sys/devices/system/cpu/cpufreq/conservative/up_threshold 95
write /sys/devices/system/cpu/cpufreq/conservative/down_threshold 75
write /sys/devices/system/cpu/cpufreq/conservative/freq_step 3
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpufreq/interactive/boost_factor 2
write /sys/devices/system/cpu/cpufreq/interactive/sustain_load 80
write /sys/module/cpu_tegra3/parameters/auto_hotplug 1
#write /sys/module/cpuidle_t3/parameters/lp2_0_in_idle 0
write /sys/module/cpuidle/parameters/lp2_in_idle 1
chown system system /sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load
chown system system /sys/devices/system/cpu/cpufreq/interactive/max_boost
# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
write /sys/block/mmcblk1/queue/read_ahead_kb 2048
# Wiimote connect status
write /data/misc/wminput/connected 0
chmod 0666 /data/misc/wminput/connected
# GPS init
#write /sys/class/gpio/export 162
#write /sys/class/gpio/gpio162/value 0
#write /sys/class/gpio/gpio162/direction out
#chown root system /sys/class/gpio/gpio162/value
#chmod 0664 /sys/class/gpio/gpio162/value
#write /sys/class/gpio/export 163
#write /sys/class/gpio/gpio163/direction out
#write /sys/class/gpio/gpio163/value 1
#chown root system /sys/class/gpio/gpio163/value
#chmod 0664 /sys/class/gpio/gpio163/value
# Load WiFi driver
insmod /system/lib/modules/bcmdhd.ko
# BB mapping symbolic name to the logging ttyACM port
symlink /dev/ttyACM2 /dev/log_modem
on property:ro.debuggable=1
# EMC debug interface
chmod 666 /sys/kernel/debug/tegra_emc/eack_state
service wpa_supplicant /system/bin/wpa_supplicant \
-Dnl80211 -puse_p2p_group_interface=1 -e/data/misc/wifi/entropy.bin -dd
# we will start as root and wpa_supplicant will switch to user wifi
# after setting up the capabilities required for WEXT
# user wifi
# group wifi inet keystore
class main
socket wpa_wlan0 dgram 660 wifi wifi
disabled
oneshot
#TI-ST
service uim /system/bin/uim-sysfs
class core
user root
group root
oneshot
service dhcpcd_wlan0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service dhcpcd_p2p /system/bin/dhcpcd -aABKL
class main
disabled
oneshot
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL -f/system/etc/dhcpcd/dhcpcd.conf
class main
disabled
oneshot
service dhcpcd_bnep0 /system/bin/dhcpcd -ABKL
class main
disabled
oneshot
service iprenew_wlan0 /system/bin/dhcpcd -n
class main
disabled
oneshot
service iprenew_p2p /system/bin/dhcpcd -n
class main
disabled
oneshot
service iprenew_eth0 /system/bin/dhcpcd -n
class main
disabled
oneshot
# create virtual SD card at /mnt/sdcard, based on the /data/media directory
# deamon will drop to user/group system/media_rw after initializing
# underlying files in /data/media wil be created with user and group media_rw (1023)
service sdcard /system/bin/sdcard /data/media 1023 1023
class late_start
# bugreport is triggered by the VOLUME-DOWN and VOLUME-UP keys
service bugreport /system/bin/dumpstate -d -v -o /data/storage/bugreports/bugreport
class main
disabled
oneshot
keycodes 115 114
#BCM
service hciattach /system/bin/brcm_patchram_plus --enable_hci --scopcm=0,2,0,0,0,0,0,0,0,0 \
--baudrate 3000000 --patchramdir /etc/firmware --enable_lpm --tosleep=5000 --create_bdaddr /dev/ttyHS2
user bluetooth
group bluetooth net_bt_admin
disabled
# Mount usb drives as /usbdrive. Generally usb drives are formatted with FAT
# filesystem, so we support FAT as of now.
on device-added-/sys/block/sda
mount vfat /dev/block/sda /mnt/usbdrive
on device-removed-/sys/block/sda
umount /mnt/usbdrive
# Prepare TF service
import init.tf.rc
# Enable NvCpuD, and set it to never poll config again
on boot
setprop nvcpud.enabled true
setprop nvcpud.config_refresh_ms -1
service nvcpud /system/bin/nvcpud
class main
user root
group root
#Raydium touch setting
#service rm_ts_service /system/bin/rm_ts_server
# class main
#Synaptics touch, allow low power mode
#on boot
# write /sys/devices/sensor00/fn01/nosleep 0
# create filesystems if necessary
service setup_fs /system/bin/setup_fs \
/dev/block/platform/sdhci-tegra.3/by-name/UDA \
/dev/block/platform/sdhci-tegra.3/by-name/CAC \
/dev/block/platform/sdhci-tegra.3/by-name/UDD
class core
user root
group root
oneshot
service pm_service_check /system/bin/pm_service check
class core
user root
group root
oneshot
service pm_service_clear /system/bin/pm_service clear
user root
group root
disabled
oneshot
on property:sys.kh.addon.mount=true
mount ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDB /data/addon_res wait rw ,data=writeback,nodelalloc
chown system system /data/addon_res
setprop sys.kh.addon.mount_state true
i will have a look on this for you.
you will need dxixda kitchen to unpack the system.img and boot/recovery.img
if someone can tell which is exactly the boot.img and the system.img from here http://androidfiles.org/uploads/?dir=Nabi2
http://androidfiles.org/uploads/?dir=Nabi2/stockimages
what mmblock is the system and boot.
---------- Post added at 12:27 PM ---------- Previous post was at 12:09 PM ----------
till now i noticed the fallowing values
# Default Read Ahead value for sdcards
write /sys/block/mmcblk0/queue/read_ahead_kb 2048
write /sys/block/mmcblk1/queue/read_ahead_kb 2048
# for backwards compatibility
export EXTERNAL_STORAGE /mnt/sdcard
export EXTERNAL_STORAGE2 /mnt/sdcard2
mkdir /mnt/sdcard 0000 system system
symlink /mnt/sdcard /sdcard
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
globula_neagra said:
i will have a look on this for you.
you will need dxixda kitchen to unpack the system.img and boot/recovery.img
if someone can tell which is exactly the boot.img and the system.img from here http://androidfiles.org/uploads/?dir=Nabi2
Click to expand...
Click to collapse
The boot.img (and the system.img i think) is in the jmzrootpackage.zip. Because anyone trying to do what we are would have that boot.img flashed or at least thats the one I have because I used that files contents to gain root access and it has a new boot.img that it flashed to my Nabi 2...
Dear All,
Last night. I try to swap memory internal to SD Card.
First, I try to make same file like basic swap memory and paste to system/etc.
and It Doesn't work.
So I make another ways.
After try and error. The mods i have installed work perfectly.
This is the CODE script to make Internal memory changed to SD Card.
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/secure/asec 1>>$LOG 2>>$LOG
What to do with it?
Hire the step make it work on your Device.
1. Make 1 file *.fstab or Copy from Other device with same extension.
2. Give the file a name vold.fstab
3. Copy and paste the above code to file. and save it.
4. Copy it (vold.fstab) to SD Card.
5. Use your Androind File Manager, Copy file vold.fstab to Directory system/etc/init.d and paste.
6a. Set Permission to rw-r--r-- (0644). or
6b. Set Permission to rwxr-xr-x
7. Reboot your Device.
This another solution for swap memory.
Please Check this page
http://goo.gl/EwKH1x
Now after reboot finish. Your memory device is already swap.
If it helps you. Please click the thanks Botton :good:
Credit:
@nunu_Nugraha
Should it work on another device?
Sent from my LG-P990
I hope so...
ivaneris said:
Should it work on another device?
Sent from my LG-P990
Click to expand...
Click to collapse
I think, it should be work to with another device.
but I'm not sure. Backup before you start.
Do with your own risk.
Thnx..it works with some modification ....use it now..:thumbup:
Sent from my LG-P990
ivaneris said:
Thnx..it works with some modification ....use it now..:thumbup:
Sent from my LG-P990
Click to expand...
Click to collapse
Did you change with another permission?
anyway, glad to hear it worked on your device to.
Elixia said:
Did you change with another permission?
anyway, glad to hear it worked on your device to.
Click to expand...
Click to collapse
No just edit the mount point...
Sent from my LG-P990
Request
ivaneris said:
No just edit the mount point...
Sent from my LG-P990
Click to expand...
Click to collapse
If you don't mine.
can you please, show me and other friends.
The code work on your device?
Elixia said:
If you don't mine.
can you please, show me and other friends.
The code work on your device?
Click to expand...
Click to collapse
Sure..here it is
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:11 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:11 /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /mnt/secure/asec 1>>$LOG 2>>$LOG
Well..if there any other way to swap please tell me my friend..as this work said not as 4.4 standard actually
We just got cm11 almost fully working recently on lg p990...
Sent from my LG-P990
ivaneris said:
Sure..here it is
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:11 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:11 /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:49 /mnt/secure/asec 1>>$LOG 2>>$LOG
Well..if there any other way to swap please tell me my friend..as this work said not as 4.4 standard actually
We just got cm11 almost fully working recently on lg p990...
Sent from my LG-P990
Click to expand...
Click to collapse
Of course mate. I will let you know if i find another way to swap metode.
since my little brother have similar device like you have.
so it's easy to test new swap metode if any.
and thanks for share your swap code. Hope it help anybody in xda.
Tips
Dritza said:
i tried but no effect on Xperia Sola
Click to expand...
Click to collapse
Sorry mate, did you follow it with correct permission?
If it yes and keeped not work on your device. I sugest you to try this.
Change the red and purple text code with "memory read on your own device".
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:14[/COLOR] /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:14[/COLOR] /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /mnt/secure/asec 1>>$LOG 2>>$LOG
How to get your own code number?
Just, run terminals app
tap this text
mount | grep sdcard0
mount | grep sdcard1
Description:
179:97 = Number code for sdcard0 ,and
179:14 = Number code for sdcard1
Hope that work.
Can this work with Xperia P or just with the phones who have SD card?
dinoCRO said:
Can this work with Xperia P or just with the phones who have SD card?
Click to expand...
Click to collapse
It's complicated to apply this metode to device have no sd card.
But I didn't say it's Imposible.
If I find about it, I will share it with you.
for now, you have to be patient. Advantage of the existing first.
Sori typo
need your assist
Elixia said:
Dear All,
Last night. I try to swap memory internal to SD Card.
First, I try to make same file like basic swap memory and paste to system/etc.
and It Doesn't work.
So I make another ways.
After try and error. The mods i have installed work perfectly.
This is the CODE script to make Internal memory changed to SD Card.
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/secure/asec 1>>$LOG 2>>$LOG
What to do with it?
Hire the step make it work on your Device.
1. Make 1 file *.fstab or Copy from Other device with same extension.
2. Give the file a name vold.fstab
3. Copy and paste the above code to file. and save it.
4. Copy it (vold.fstab) to SD Card.
5. Use your Androind File Manager, Copy file vold.fstab to Directory system/etc/init.d and paste.
6a. Set Permission to rw-r--r-- (0644). or
6b. Set Permission to rwxr-xr-x
7. Reboot your Device.
Now after reboot finish. Your memory device is already swap.
If it helps you. Please click the thanks Botton :good:
Credit:
@nunu_Nugraha
Click to expand...
Click to collapse
hi fren, your script compitable for samsung or not because i have try but its not working. i really2 need your help
qaliff said:
hi fren, your script compitable for samsung or not because i have try but its not working. i really2 need your help
Click to expand...
Click to collapse
Sorry mate, this swap script only for xperia go and similar.
if you running on samsung. than you may try this http://forum.xda-developers.com/showthread.php?t=2584862
hope it help and solve your problem.
Elixia said:
Sorry mate, did you follow it with correct permission?
If it yes and keeped not work on your device. I sugest you to try this.
Change the red and purple text code with "memory read on your own device".
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:14[/COLOR] /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:14[/COLOR] /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:97[/COLOR] /mnt/secure/asec 1>>$LOG 2>>$LOG
How to get your own code number?
Just, run terminals app
tap this text
mount | grep sdcard0
mount | grep sdcard1
Description:
179:97 = Number code for sdcard0 ,and
179:14 = Number code for sdcard1
Hope that work.
Click to expand...
Click to collapse
Didn't work
Elixia said:
Dear All,
Last night. I try to swap memory internal to SD Card.
First, I try to make same file like basic swap memory and paste to system/etc.
and It Doesn't work.
So I make another ways.
After try and error. The mods i have installed work perfectly.
This is the CODE script to make Internal memory changed to SD Card.
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:14 /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/179:97 /mnt/secure/asec 1>>$LOG 2>>$LOG
What to do with it?
Hire the step make it work on your Device.
1. Make 1 file *.fstab or Copy from Other device with same extension.
2. Give the file a name vold.fstab
3. Copy and paste the above code to file. and save it.
4. Copy it (vold.fstab) to SD Card.
5. Use your Androind File Manager, Copy file vold.fstab to Directory system/etc/init.d and paste.
6a. Set Permission to rw-r--r-- (0644). or
6b. Set Permission to rwxr-xr-x
7. Reboot your Device.
Now after reboot finish. Your memory device is already swap.
If it helps you. Please click the thanks Botton :good:
Credit:
@nunu_Nugraha
Click to expand...
Click to collapse
on xperia sola not work
Doesn't work..
Hi dude,
Followed everything to the dot, but it doesn't work.. I'm using the CM11 rom by RodgerRules on my Xperia Go.. Please help
Doesn't work on my xperia go running CM11..
Change with this
Hukanawa said:
Hi dude,
Followed everything to the dot, but it doesn't work.. I'm using the CM11 rom by RodgerRules on my Xperia Go.. Please help
Click to expand...
Click to collapse
Einstein69 said:
Doesn't work on my xperia go running CM11..
Click to expand...
Click to collapse
Sorry bro for almost forget it
On attach file below. Put it in to folder system/etc/init.d dan give it permissions rwxr-xr-x
I already test both of them on my xperia go running CM11.
Link : https://docs.google.com/file/d/0B-yslefpNn1hSVNPUmdfQ1RRQkU/edit?pli=1
I'm looking for a smooth way to use symlinks from/to both the emulated sdcard and an ext4 formatted external sdcard in order to easily redirect data between the two.
However the way those file systems are both mounted and linked on various locations in the directory tree isn't very straight forward:
Mount Points
The external sdcard gets mounted natively on /mnt/media_rw/sdcard1 ... and once again virtually with a fuse layer on top on /storage/sdcard1
Code:
[email protected]:/ # mount | grep sdcard1
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type ext4 (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,data=ordered)
/dev/fuse on /storage/sdcard1 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ # df -m | grep sdcard1
/dev/block/vold/179:33 14953 174 14627 1% /mnt/media_rw/sdcard1
/dev/fuse 14953 174 14627 1% /storage/sdcard1
The emulated sdcard (origin: /data/media/*) is virtually fuse mounted on /mnt/shell/emulated (and /storage/emulated/**)
Code:
[email protected]:/ # mount | grep emulated | grep fuse
/dev/fuse on /mnt/shell/emulated type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0 type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/0/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated/legacy/Android/obb type fuse (rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other)
[email protected]:/ # df -m | grep emulated | grep fuse
/dev/fuse 5465 164 5301 3% /mnt/shell/emulated
/dev/fuse 5465 164 5301 3% /storage/emulated/0
/dev/fuse 5465 164 5301 3% /storage/emulated/0/Android/obb
/dev/fuse 5465 164 5301 3% /storage/emulated/legacy
/dev/fuse 5465 164 5301 3% /storage/emulated/legacy/Android/obb
Links
Existing symlinks pointing to sdcards:
Code:
/external_sd -> /storage/sdcard1
/mnt/external_sd -> /storage/sdcard1
/sdcard -> /storage/emulated/legacy
/mnt/sdcard -> /storage/emulated/legacy
/storage/sdcard0 -> /storage/emulated/legacy
/storage/emulated/legacy -> /mnt/shell/emulated/0
Symlink Creation
Fuse mount points don't allow for creation of symlinks:
Code:
[email protected]:/ # ln -s /storage/sdcard0 /storage/sdcard1/link_to_sdcard0
ln: /storage/sdcard1/link_to_sdcard0: Function not implemented
But native mount points do:
Code:
[email protected]:/ # ln -sv /storage/sdcard0 /mnt/media_rw/sdcard1/link_to_sdcard0
'/mnt/media_rw/sdcard1/link_to_sdcard0' -> '/storage/sdcard0'
Permissions
Code:
drwx------ 4 1023 1023 /mnt/media_rw
drwxr-xr-x 4 root root /mnt/media_rw/sdcard1** # when mounted
drwx------ 2 1023 1023 /mnt/media_rw/usbdisk # when unmounted
drwxr-x--x 5 root 1028 /storage
drwxrwx--x 4 root 1028 /storage/sdcard1** # when mounted
drwx------ 2 root root /storage/usbdisk # when unmounted
drwx------ 3 shell shell /mnt/shell
drwxrwx--x 5 root 1028 /mnt/shell/emulated** # only 0 populated (legacy, obb empty)
drwx------ 2 shell shell /mnt/shell/emulated # when unmounted
drwxr-x--x 5 root 1028 /storage
dr-xr-xr-x 2 root root /storage/emulated**
1015=sdcard_rw
1023=media_rw
1028=sdcard_r
After applying these permission fixes to overcome external storage restrictions introduced in 4.4 the link becomes accessible in File Manager, but again only via the native mount point.
Storage Variables
Am I wrong assuming that apps rather use environment variables to determine storage paths than looking in the directory tree!? Well, obviously they point to the unwanted fuse mount points:
Code:
[email protected]:/ # env | grep sdcard1
EXTERNAL_SD=/storage/sdcard1
SECONDARY_STORAGE=/storage/sdcard1:/storage/usbdisk
[email protected]:/ # env | grep emulated
EMULATED_STORAGE_SOURCE=/mnt/shell/emulated
EMULATED_STORAGE_TARGET=/storage/emulated
EXTERNAL_STORAGE=/storage/emulated/legacy
Solution?
Here is some official information on how storage is used: http://source.android.com/devices/tech/storage/config-example.html
I've started messing around building a new ramdisk in order to gain control over the cards. Ideas so far are:
- remove fuse stuff from init.rc --> use bind mounts for the emulated sdcard?
- remove vold stuff from init.rc?
- setting up mount points manually in fstab
- changing variables to the native mount point in case of the external sdcard
Ideas for solutions causing the least headache?
---
Notes:
/etc/init* script
/system/build.prop: persist.fuse_sdcard=false # emulated sdcard does not get mounted at all
I share your pain trying to get your head around how android 4.4 works.
The documentation is definately lacking...
Don't forget also that ALL shares are declared to the os through "framework-res.xml",
and this file is very pedantic with its "strings".
ie: the string-names are built-in. Things break if you change them.
In the end when I eventually got my head around it (sort of), it was easier to use the designed in methods to achieve/share what I wanted,
rather than try to modify android4.4 back to 4.1.
edit2:
as my info cost me dozens of googling hours, and lots of experimentation, i'll add this hoping it will be useful....
Remember you actually can share: emulated storage, other internal storage, and plug-in usb storage, internally, and externally via mtp.
and it does work well.
http://source.android.com/devices/tech/storage/config-example.html
The link you posted above contains nearly everything you need to get shares and mtp working nicely for you...
edit3:
I needed this as well.
export PRIMARY_STORAGE /storage/emulated/legacy # RC note: gets around issues
edit4:
I also had to relax/change the permissions to make it work properly:
mkdir /storage/emulated 0750 media_rw media_rw # RCmod: was 0555 root root
and here as well:
#External storage directories
mkdir /mnt/media_rw/sdcard1 0750 media_rw media_rw
mkdir /mnt/media_rw/sdcard2 0750 media_rw media_rw
mkdir /storage/usbdisk0 0750 media_rw media_rw
there were other things as well but hopefully you can use this as a starting point.
....and then there is Selinux
So I was able to create a symlink to external sdcard on LG g3 running rooted stock kit Kat Rom. I successfully changed Groove's (formerly xboxmusic) offline storage to external sdcard.
The following command was successful in creating a link, but Groove was unable to download music to the directory presumably due to permissions on /mnt
su
cp -rp /data/media/0/Android/data/com.microsoft.xboxmusic /storage/external_sd
rm -r /data/media/0/Android/data/com.microsoft.xboxmusic
ln -s /mnt/media_rw/external_sd/com.microsoft.xboxmusic/ /data/media/0/Android/data
After these commands, Groove was producing errors stating that there was not enough disk space. As said before, I believe this was due to it's lack of permissions to /mnt
Replacing the last command with the following worked and offline music is now downloaded to external sd card
ln -s /storage/external_sd/com.microsoft.xboxmusic/ /data/media/0/Android/data
data
Hope this helps.
monkeyfncoconut said:
So I was able to create a symlink to external sdcard on LG g3 running rooted stock kit Kat Rom. I successfully changed Groove's (formerly xboxmusic) offline storage to external sdcard.
The following command was successful in creating a link, but Groove was unable to download music to the directory presumably due to permissions on /mnt
su
cp -rp /data/media/0/Android/data/com.microsoft.xboxmusic /storage/external_sd
rm -r /data/media/0/Android/data/com.microsoft.xboxmusic
ln -s /mnt/media_rw/external_sd/com.microsoft.xboxmusic/ /data/media/0/Android/data
After these commands, Groove was producing errors stating that there was not enough disk space. As said before, I believe this was due to it's lack of permissions to /mnt
Replacing the last command with the following worked and offline music is now downloaded to external sd card
ln -s /storage/external_sd/com.microsoft.xboxmusic/ /data/media/0/Android/data
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
data
Hope this helps.
Click to expand...
Click to collapse
Is it true that:
symbolic linking
ext4->fuse works
ext4->vfat does not work?
And,
Is it possible fuse->fuse, or fuse->ext4?
Hi, I have a problem, I have the odd situation that the system partition shows 4gb and the /sdcard shows the 54.9gb, but there not linked, can some one guide me how to link them please.
First, I apologize if I am writing a duplicate thread. If so, please link it.
As part of my Android-hobby-experiments with a rooted Sony Xperia Z5 Compact e5823 with Android MarshMallow, I attempted to use a partition of my external microSD card as swap area but ended up in a boot loop after reboot.
I have two partitions on the microSD card. One is fat32 and the other one is linux-swap. Both partitions were made under Debian using GParted, at different timepoints.
If I remember well, I did the following on a terminal emulator:
Code:
$ su
# mkswap /dev/block/mmcblk0p2
# swapon /dev/block/mmcblk0p2
(here I got an error. something like "Invalid argument".)
# free -m
I saw no improvement, so then I did:
Code:
$ su
# mkswap /dev/block/mmcblk0p3
# swapon /dev/block/mmcblk0p3
(here I got the same error.)
# free -m
(no improvement)
# exit
$ exit
Device was working normal after this.
Hours later, I reboot the phone (the camera sometimes crashes/freezes after taking a pic, so I took a pic, screen froze, took a screenshot, and rebooted). Then I reached a boot loop.
The screen showes the Sony Xperia logo, then the screen attempts to load the "powered-by.-ndroid-animation" but instead there is a black screen and a blinking red LED (4 times). The screen is then gray and the show repeats. I turned off the phone by opening it and disconnecting the battery
Then I took the microSD card out and the SIM card aswell. I swiched on the phone and the bootloop continued. :silly:
I can enter fastboot-mode (volume up + USB connection). Which I now use to switch off the phone instead of opening and disconnecting the battery :cyclops:.
Luckily, the device on fastboot-mode is listed the under Debian by the command
Code:
$ fastboot devices -l
, so I believe in hope to fix this boot loop w/o (re)flashing a ROM
It is also possible to run a custom recovery. I have run TWRP3.0 from this post and nilezon's version from this posts using the command
Code:
$ fastboot boot recovery.img
At the very beginning of the console of the recoveries there is an error:
Code:
Updating partition details . . .
Failed to mount '/lta-label' (No such device)
. . . done
Full SELinux support is present.
MTP Enabled
--- Update ---
I used the terminal using TWRP3.0 to read the file
Code:
/etc/fstab
and it looks as follows
Code:
/dev/block/mmcblk0p43 /system ext4 rw 0 0
/dev/block/mmcblk0p42 /data ext4 rw 0 0
/dev/block/mmcblk0p41 /cache ext4 rw 0 0
/external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
/dev/block/mmcblk0p3 /firmware vfat rw 0 0
/dev/block/mmcblk0p38 /appslog ext4 rw 0 0
/dev/block/mmcblk0p40 /oem ext4 rw 0 0
/dev/block/mmcblk0p31 /persist ext4 rw 0 0
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
/dev/block/mmcblk0p39 /diag ext4 rw 0 0
I decided to comment out
Code:
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
and reboot. Boot loop persists in the same way and at the console of the recovery there is still, at the very beginning,
Code:
Failed to mount '/lta-label' (No such device)
I rechecked the
Code:
/etc/fstab
file and my modification was gone.
--- Update 2 ---
Today After connecting the SD card with a microSD-USB-adapter Debian shows the following error:
Code:
Error mounting /dev/sdb1 at /media/user/4C25-AD09: Command-line `mount -t "vfat" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdb1"
"/media/jk/4C25-AD09"' exited with non-zero exit status 32: mount: /dev/sdb1: can't read superblock
Still, both partitions are recognized by GParted. "/dev/sdb1" is the fat32-partition. "/dev/sdb2" is the swap-partition. I can't access the first . . .
so I am stuck. dou you guys have any suggestion about what to try next?