Database Develop

[q] sd interal/external

when i go to the shell of my devices, i put mount; and show me this:
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
what is mi internal and external memory?
thank you for you answers!!!

damn thats confusing lol
what exactly are you looking for ?? What do you want to know about your internal / external memory
im a little confused

Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O

i have the two memorys bricked, internal and external, and when i run the command try to find /dev/block/mmcblk0 to execute the parted /dev/block/mmcblk0 , no exist...
i find the external sd in /dev/block/vold/179:9, but i could find the internal memory! to fixit

blubxd said:
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
Click to expand...
Click to collapse
okey the external is /dev/block/vold/179:9
but the internal?!

Can you help mw please??? I send this mesg from my i9000 but i cant use the sd internal and external. Any solution to this?

CM10 - Issue with /data partiton

After installing the latest CM10 Nightly 20121002 it would appear that the /datadata partition is back however my apps are still trying to install themselves to /data which has been reduced to ~80MB and as a result I get a messsage soon after the market restore begins that space is low.
I went back to CM10-20120919 and I have 422MB available in the /data partition as expected.
I tried to post to the CM10 Nightly thread but I'm still less than 10 posts old on XDA, I posted the partition layout in 20121002 on the Cyanogen forums, can't post links, too noobish for XDA yet again.
Is this expected behaviour in CM10? Do we now how to put everything on the SD card?

Hi,
I'm on CM10 1002 and I have 1G free in /data (and 472M used). In /datadata I have 218M free and 203M used.
All my apps are on the phone, i didn't moved anything on sd card.
I think it was something wrong with your install, you should try flashing it again.

Aviatoru said:
Hi,
I'm on CM10 1002 and I have 1G free in /data (and 472M used). In /datadata I have 218M free and 203M used.
All my apps are on the phone, i didn't moved anything on sd card.
I think it was something wrong with your install, you should try flashing it again.
Click to expand...
Click to collapse
I have downloaded the latest nightly 20121003 and I still have the same issue.
Here is what I see in ADB:
1|[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 184M 48K 184M 4096
/mnt/asec 184M 0K 184M 4096
/mnt/obb 184M 0K 184M 4096
/cache 17M 2M 14M 4096
/radio 16M 15M 760K 4096
/datadata 422M 17M 404M 4096
/system 393M 229M 164M 4096
/data 81M 46M 35M 4096
/efs 12M 5M 6M 4096
/storage/sdcard1 7G 822M 6G 32768
/storage/sdcard0 14G 11G 3G 8192
/mnt/secure/asec 14G 11G 3G 8192
[email protected]:/ # 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,n
omblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch:angel:
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
Everything checks out except the /data LV, it's only been created as 81MB!
Something has gone wrong in LVM:
--- Volume group ---
VG Name lvpool
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 484.00 MiB
PE Size 4.00 MiB
Total PE 121
Alloc PE / Size 121 / 484.00 MiB
Free PE / Size 0 / 0
VG UUID buUfFr-wHCP-0WaI-theX-LYHJ-WIB3-CvBIW0
--- Logical volume ---
LV Path /dev/lvpool/system
LV Name system
VG Name lvpool
LV UUID KyabDe-sf7A-eVsT-S0ay-XenC-Yvyk-QuStAC
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 400.00 MiB
Current LE 100
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/lvpool/userdata
LV Name userdata
VG Name lvpool
LV UUID zIQCKS-O3sA-QqJa-6FCb-dw0A-mvSV-5nAcH0
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 84.00 MiB
Current LE 21
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
[EDIT]
Partition list on mmcblk0
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
255 heads, 63 sectors/track, 1945 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1868 15004678+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 1869 1931 500173 83 Linux
/dev/block/mmcblk0p3 1931 1946 125453 82 Linux swap
Anybody know how to fix this?

infecticide said:
I have downloaded the latest nightly 20121003 and I still have the same issue.
Here is what I see in ADB:
1|[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 184M 48K 184M 4096
/mnt/asec 184M 0K 184M 4096
/mnt/obb 184M 0K 184M 4096
/cache 17M 2M 14M 4096
/radio 16M 15M 760K 4096
/datadata 422M 17M 404M 4096
/system 393M 229M 164M 4096
/data 81M 46M 35M 4096
/efs 12M 5M 6M 4096
/storage/sdcard1 7G 822M 6G 32768
/storage/sdcard0 14G 11G 3G 8192
/mnt/secure/asec 14G 11G 3G 8192
[email protected]:/ # 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,n
omblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:9 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch:angel:
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ #
Everything checks out except the /data LV, it's only been created as 81MB!
Something has gone wrong in LVM:
--- Volume group ---
VG Name lvpool
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 484.00 MiB
PE Size 4.00 MiB
Total PE 121
Alloc PE / Size 121 / 484.00 MiB
Free PE / Size 0 / 0
VG UUID buUfFr-wHCP-0WaI-theX-LYHJ-WIB3-CvBIW0
--- Logical volume ---
LV Path /dev/lvpool/system
LV Name system
VG Name lvpool
LV UUID KyabDe-sf7A-eVsT-S0ay-XenC-Yvyk-QuStAC
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 400.00 MiB
Current LE 100
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/lvpool/userdata
LV Name userdata
VG Name lvpool
LV UUID zIQCKS-O3sA-QqJa-6FCb-dw0A-mvSV-5nAcH0
LV Write Access read/write
LV Creation host, time localhost, 2012-10-05 19:18:17 +0000
LV Status available
# open 1
LV Size 84.00 MiB
Current LE 21
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
[EDIT]
Partition list on mmcblk0
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16005464064 bytes
255 heads, 63 sectors/track, 1945 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1868 15004678+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 1869 1931 500173 83 Linux
/dev/block/mmcblk0p3 1931 1946 125453 82 Linux swap
Anybody know how to fix this?
Click to expand...
Click to collapse
So I think I found the problem and, possibly, the solution.
I noticed on my internal SD card that there is a swap parititon that wasn't being used, as confirmed by 'free' in ADB. Swap shouldn't be there so I deleted it Reflashed, hoping it would recreate the internal partitioning to right size. Nope, same issue.
Deleted the linux partition (mmcblk0p2) hoping that during the reflash it would recreate it. Nope, almost bricked the phone until I discovered that ADB is available in recovery.
Re-created said partition with remaining space, I now have ~360MB of "internal storage". So it would appear that the internal card is partitioned wrong.
Could the helpful person from before, go into ADB shell and run fdisk -l /dev/block/mmcblk0 and post the results so I can see what I should have for unit numbers?
Thanks!

[Q] Internal SD card doesn't mount on boot.

Hello everyone,
I am using CM10.1 on my Samsung Galaxy S i9000. I have a strange problem since I swithed to CM10 about a month ago. If I boot to revocery I can reach, read and write to all partitions including sdcard and internalsd (and data, system etc.) However, If I boot to normal system, the boot screen SGS/Cyanogen mod image lasts on the screen for too long and then system stats.
When system starts, I end up with external sd mounted but not internal sd. If I connect my phone to a computer at this time, computer only sees external sd card, and says "insert disk" when I click internal sd from Explorer. However, when I removed by sdcard from computer, my phone says "preparing sd card" and than mounts internal sd. Now, external sd is unmounted magically. This time I can use internal sd (read, write everything) but external sd card is not mounted. If I go to System -> Storage to mount external sd card, "Insert sdcard to mount" appears, and it can't be mountable.
I also ran mount command before connecting to PC (when external sd was mounted) and after disconnected from PC (this time internal sd was mounted) These are the outputs:
before connecting to pc
Code:
[email protected]:/ # 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/secure tmpfs rw,relatime,mode=700 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:25 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
last lines differ
after connecting to pc
Code:
[email protected]:/ # 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/secure tmpfs rw,relatime,mode=700 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/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
How can I fix this? Btw, I can't report this to CM10.1 page because my post count is too low.
If I could'nt write and read to internalsdcard properly on recovery or after disconnecting to pc I'd thought that it was broken on hardware level but this seems like a software issue to me? What do you think?

By using which shell command, I can try to manually mount my internal sdcard, after the phone booted?

If I run these commands manually after turning on my phone, I can mount my internal sd card to /storage/sdcard successfully. However, I can't mount sdcard to multiple locations (such as mnt/sdcard and /sdcard) so programs don't run properly.
Code:
mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard0;
setprop EXTERNAL_STORAGE_STATE mounted;
am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d file:///storage/sdcard0;
However if I try to mount vold/179:0 i get the following error:
Code:
[email protected]:/ # mount -t vfat /dev/block/vold/179\:0 /storage/sdcard0;
mount: Device or resource busy
Any thoughts?

What is vold and what is the difference between mounting
/dev/block/vold/179:0 and /dev/block/mmcblk0p1 ?
If both points to internal storage, why can't I mount one, but do mount another?

Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.

gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse
Probably, problem is "clockworkmod" folder into external SD card!
When you make backup, you must choise "tar format" instead "dup format"!!

almost there
Man!
That´s exactly my case!! SGS Vibrant T959, with CyanogenMod v10.1.2. I noticed that I was not accessing the internal sdcard. I tried to plug in the computer and enable the usb mass storage but it wouldn´t mount the internal sdcard. Then I rebooted in recovery mode (CWM recovery) and went to mount & storage -> mount sdcard. Rebooted and nothing. Went back to CWM recovery, mounted sdcard, and to browser it I went to 'install zip' just to see. I was able to see my old files.
Then I googled it and found this!
Thank you very much for your hint!
Funny thing is, this happened just after I installed this version (10.1.2). I was using v10.0 and it was just all fine (with 32 Gb external sdcard).
1) I removed it, and boot and there was my internal sdcard with all my files and backups!! ooohoooo
2) plugged my 32 gb sdcard back and it mounted .
3) reboot
4) and my internal SDcard was not mounted again .
So for now, everytime I boot I have to remove my 32gb external sdcard first, and plug it again after boot is finished.
Does anyone know how to def fix it ?!
Thanks!
gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse

portisheadbr said:
Does anyone know how to def fix it ?! Thanks!
Click to expand...
Click to collapse
just a thought, Android might have issues when the SD card is not formatted using Android. Its advisable to format Sd cards in a PC and after that again in your Android Phone.
Not sure , if this would solve your problem, but worth a try, if its not too difficult to do.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

[DEV][WIP] CM12 for tsubasa/mint - Looking for Xperia T testers!

Hey people!
As some of you might already know, with the help of @updateing I have been able to compile CM12 for Xperia V.
However, there are two remaining issues that are really annoying and make the rom completely unsuitable for daily usage:
Internal storage doesn't mount and mobile data shows the 2G/3G connection icon, but the browser always redirects to the "Error: Name not resolved" page. APN settings are confirmed not to be the reason for this behavior.
Perhaps some other devs that are working on porting Android L to tsubasa/mint/hayabusa might want to join this discussion and help me figure out what's wrong. If we share our progress and work together, we might get this to work.
Just for general information, I have used the device repos and vendor files in updateing's git, as well as slightly modified CM12 kernel source to build the rom.
Selinux is already disabled in cmdline.txt and thus cannot be responsible for the issues. (It re-enables somewhen during boot, however.)
I have already tried mounting the internal storage via init.rc, working around vold. But only root can read/write files if I do. So that's no option.
Now, I'm running out of ideas.
I'm really grateful for any suggestions or hints. Thanks in advance, everyone.
In attachments you'll find some logs that might be helpful.
Also, the following, older log shows the mounting issues before I started experimenting with init.rc.
Code:
Line 1289: I/SystemServer( 726): Mount Service
Line 1291: D/MountService( 726): got storage path: /storage/sdcard0 description: Interner Speicher primary: true removable: false emulated: false mtpReserve: 0 allowMassStorage: false maxFileSize: 0
Line 1293: D/MountService( 726): addVolumeLocked() StorageVolume:
Line 1295: D/MountService( 726): mStorageId=0 mPath=/storage/sdcard0 mDescriptionId=17040836 mPrimary=true
Line 1297: D/MountService( 726): mRemovable=false mEmulated=false mMtpReserveSpace=0
Line 1299: D/MountService( 726): mAllowMassStorage=false mMaxFileSize=0 mOwner=null mUuid=null
Line 1301: D/MountService( 726): mUserLabel=null mState=null
Line 1303: D/MountService( 726): got storage path: /storage/sdcard1 description: SD-Karte primary: false removable: true emulated: false mtpReserve: 0 allowMassStorage: false maxFileSize: 0
Line 1305: D/MountService( 726): addVolumeLocked() StorageVolume:
Line 1307: D/MountService( 726): mStorageId=0 mPath=/storage/sdcard1 mDescriptionId=17040837 mPrimary=false
Line 1309: D/MountService( 726): mRemovable=true mEmulated=false mMtpReserveSpace=0 mAllowMassStorage=false
Line 1311: D/MountService( 726): mMaxFileSize=0 mOwner=null mUuid=null mUserLabel=null mState=null
Line 1313: D/MountService( 726): got storage path: /storage/usbdisk description: USB-Speicher primary: false removable: true emulated: false mtpReserve: 0 allowMassStorage: false maxFileSize: 0
Line 1315: D/MountService( 726): addVolumeLocked() StorageVolume:
Line 1317: D/MountService( 726): mStorageId=0 mPath=/storage/usbdisk mDescriptionId=17040838 mPrimary=false
Line 1319: D/MountService( 726): mRemovable=true mEmulated=false mMtpReserveSpace=0 mAllowMassStorage=false
Line 1321: D/MountService( 726): mMaxFileSize=0 mOwner=null mUuid=null mUserLabel=null mState=null
Line 1331: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard0
Line 1331: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard0
Line 1331: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard0
Line 1333: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard1
Line 1333: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard1
Line 1333: W/MountService( 726): Duplicate state transition (unmounted -> unmounted) for /storage/sdcard1
Line 1335: D/MountService( 726): volume state changed for /storage/usbdisk (unmounted -> removed)
Line 1335: D/MountService( 726): volume state changed for /storage/usbdisk (unmounted -> removed)
Line 1339: W/MountService( 726): getSecureContainerList() called when storage not mounted
Line 1339: W/MountService( 726): getSecureContainerList() called when storage not mounted
Line 1447: W/MountService( 726): getSecureContainerList() called when storage not mounted
Line 1447: W/MountService( 726): getSecureContainerList() called when storage not mounted
Line 1953: D/Vold ( 259): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)
Line 1959: D/MountService( 726): volume state changed for /storage/sdcard0 (unmounted -> checking)
Line 1959: D/MountService( 726): volume state changed for /storage/sdcard0 (unmounted -> checking)
Line 1961: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard0 flg=0x4000000 (has extras) } to UserHandle{-1}
[COLOR="Red"][B]Line 2005: E/Vold ( 259): /dev/block/vold/179:15 failed to mount via EXT4 (Permission denied)[/B][/COLOR]
Line 2007: E/Vold ( 259): Volume sdcard0 found no suitable devices for mounting :(
Line 2009: D/Vold ( 259): Volume sdcard0 state changing 3 (Checking) -> 1 (Idle-Unmounted)
Line 2013: D/MountService( 726): volume state changed for /storage/sdcard0 (checking -> unmounted)
Line 2013: D/MountService( 726): volume state changed for /storage/sdcard0 (checking -> unmounted)
Line 2015: I/PackageManager( 726): Updating external media status from unmounted to unmounted
Line 2015: I/PackageManager( 726): Updating external media status from unmounted to unmounted
Line 2017: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///storage/sdcard0 flg=0x4000000 (has extras) } to UserHandle{-1}
Line 2017: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///storage/sdcard0 flg=0x4000000 (has extras) } to UserHandle{-1}
Line 2019: E/VoldConnector( 726): NDC Command {5 volume mount /storage/sdcard0} took too long (879ms)
Line 2021: E/MountService( 726): Boot-time mount failed (-1)
Line 2021: E/MountService( 726): Boot-time mount failed (-1)
Line 2025: D/Vold ( 259): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
Line 2029: D/MountService( 726): volume state changed for /storage/sdcard1 (unmounted -> checking)
Line 2029: D/MountService( 726): volume state changed for /storage/sdcard1 (unmounted -> checking)
Line 2031: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard1 flg=0x4000000 (has extras) } to UserHandle{-1}
Line 3051: D/Vold ( 259): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)
Line 3053: D/MountService( 726): volume state changed for /storage/sdcard1 (checking -> mounted)
Line 3053: D/MountService( 726): volume state changed for /storage/sdcard1 (checking -> mounted)
Line 3055: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/sdcard1 flg=0x4000000 (has extras) } to UserHandle{-1}
Line 3055: D/MountService( 726): sendStorageIntent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/sdcard1 flg=0x4000000 (has extras) } to UserHandle{-1}
Line 3057: E/VoldConnector( 726): NDC Command {6 volume mount /storage/sdcard1} took too long (1373ms)
Line 4307: I/ActivityManager( 726): Start proc com.android.externalstorage for broadcast com.android.externalstorage/.MountReceiver: pid=1524 uid=10008 gids={50008, 9997, 1028, 1015, 1023} abi=armeabi-v7a
Line 4377: D/MediaScannerReceiver( 838): action: android.intent.action.MEDIA_UNMOUNTED path: /storage/sdcard0
Line 5473: D/Vold ( 259): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)
Line 5481: D/Vold ( 259): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)

Considering "name not resolved": did you properly set DNS addresses?

tajimura said:
Considering "name not resolved": did you properly set DNS addresses?
Click to expand...
Click to collapse
Not sure. Didn't change anything related to DNS.
On other roms, mobile network worked out of the box for me, that's why I didn't try changing settings like that.
I'm currently trying to replace the CM12 kernel source with updateing's kernel-msm repo. Noticed some differences in mobile data driver.
We'll see how it goes.

How is it going so far mate?

PeterGeorgiou said:
How is it going so far mate?
Click to expand...
Click to collapse
No progress yet. But I had to stop the work because of some friends' visit.
Had some compile error right before. I'll have a look at it later. :good:

Good news.. Most stuff is fixed.
There is one annoying graphic glitch left, which I'll have a look at tomorrow. :good:
Also I need to add a recovery to the kernel.

WhiteNeo said:
Good news.. Most stuff is fixed.
There is one annoying graphic glitch left, which I'll have a look at tomorrow. :good:
Also I need to add a recovery to the kernel.
Click to expand...
Click to collapse
Good news [emoji4]
BTW, it will be fine if kernel supports FOTA Recovery.

This is only for the Xperia V or it is also for the T's?

moliverac8 said:
This is only for the Xperia V or it is also for the T's?
Click to expand...
Click to collapse
I can't debug XT.
Especially with an alpha rom like CM12, decent developer support is important. But without the phone, I can't do so..
I am confident one of your awesome devs is going to release CM12 soon. If not, I might provide a flashable zip here - just for testing.

WhiteNeo said:
I can't debug XT.
Especially with an alpha rom like CM12, decent developer support is important. But without the phone, I can't do so..
I am confident one of your awesome devs is going to release CM12 soon. If not, I might provide a flashable zip here - just for testing.
Click to expand...
Click to collapse
I have a T that I'm willing to test your builds on, but I have no developer knowledge or experience. Can I be of use to you, with my phone?

The same here.
Theonewithideas said:
I have a T that I'm willing to test your builds on, but I have no developer knowledge or experience. Can I be of use to you, with my phone?
Click to expand...
Click to collapse

Theonewithideas said:
I have a T that I'm willing to test your builds on, but I have no developer knowledge or experience. Can I be of use to you, with my phone?
Click to expand...
Click to collapse
DS-1 said:
The same here.
Click to expand...
Click to collapse
I don't know. Development would take much longer that way. Also there would be a risk of bricked phones. :/

WhiteNeo said:
I don't know. Development would take much longer that way. Also there would be a risk of bricked phones. :/
Click to expand...
Click to collapse
But Xperia V and Xperia T are so much similar, won't it work on T if it already works on V? Besides, if something doesn't work out, can we just flash working CM11 ROM, and go back to normal? How big is the risk?

Theonewithideas said:
But Xperia V and Xperia T are so much similar, won't it work on T if it already works on V? Besides, if something doesn't work out, can we just flash working CM11 ROM, and go back to normal? How big is the risk?
Click to expand...
Click to collapse
Well. If there is no other dev that actually owns the device, I might provide one or the other build for mint.
The problem is that as soon as I release CM12, people expect me to fix bugs that I can't find or track down.
Give your developers some time. I am sure there are already people working on this.

It's really NOT recommended to cross-flash ROMs between T, TX and V... Though the hardware is almost the same, drivers in kernel are still different. For example, if T's ROM is flashed into TX, the screen will be screwed up once the phone is powered on.(I have made several threads about this) And according to some users, if T's ROM is flashed into V, the screen will stop working completely, not just upside down. This is because T's display panel driver contains NV recovery system, which will break any panel other than T's, while TX's does not contain such thing. So flashing TX on T won't cause damage to the panel (but how does it work correctly?). However, this is no guarantee that TX ROM will work on V, or in the way round.

Just noticed that there are daily builds of CM12 by FXP for Sirius, Leo, Aries etc. Seems we are dropped now

I'm having the same problem, now my phone won't even start(some problem with offline charging), i screwed my college finals, so I'm busy fixing that instead of phone

Alright, Xperia T owners.. Christmas present incoming.
I have found the time to merge my Xperia V changes to Xperia T sources and compile a test build of CM12.
However, I do not know if the rom boots, but if it does, it should be pretty much fully working.
That's why I'm looking for testers - Please pm me if you're interested.
In case the build boots - fine. You'll receive weekly builds just like Xperia V owners.
But in case it doesn't boot, I cannot afford the time to debug this thing.
Still, the rom might serve as a decent base to fix the current vibrator/camera issues.
Anyway, stay tuned people!
I'll keep you updated when I have some feedback from one or two testers.

WhiteNeo said:
Alright, Xperia T owners.. Christmas present incoming.
I have found the time to merge my Xperia V changes to Xperia T sources and compile a test build of CM12.
However, I do not know if the rom boots, but if it does, it should be pretty much fully working.
That's why I'm looking for testers - Please pm me if you're interested.
In case the build boots - fine. You'll receive weekly builds just like Xperia V owners.
But in case it doesn't boot, I cannot afford the time to debug this thing.
Still, the rom might serve as a decent base to fix the current vibrator/camera issues.
Anyway, stay tuned people!
I'll keep you updated when I have some feedback from one or two testers.
Click to expand...
Click to collapse
Just want to be tester,

Send me the link im ready for testing!!! good job bro! and happy christmas!

internal storage not mounting

hi everyone, i have a problem:
i factory reset the phone and flashed a cm12, latest nightly i think. however the problem is there's not a sdcard0 anymore. when i go there from file manager, pc or adb shell there is just an empty folder. any way to restore it? this doesn't allow me to do anything: downloads, photos ecc.ecc.
i have inquired more and i finally found the core problem: the internal storage it's not mounting, here's what i found from adb logcat
I/Vold ( 271): /dev/block/vold/4095:1048575 being considered for volume sdcard0
D/Vold ( 271): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 271): Trying to get filesystem type for /dev/block/vold/4095:1048575
E/Vold ( 271): None or unknown filesystem on /dev/block/vold/4095:1048575
D/Vold ( 271): Volume sdcard0 state changing 3 (Checking) -> 1 (Idle-Unmounted)
W/Vold ( 271): Returning OperationFailed - no handler for errno 0
D/MountService( 696): volume state changed for /storage/sdcard0 (unmounted -> checking)
D/MountService( 696): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/
flg=0x4000000 (has extras) } to UserHandle{-1}
D/MountService( 696): volume state changed for /storage/sdcard0 (checking -> unmounted)
I/PackageManager( 696): Updating external media status from unmounted to unmounted
D/MountService( 696): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///storage/sdcard0 flg=0x4000000 (has extras) } to UserHandle{-1}
E/MountService( 696): Boot-time mount failed (-1)
and here's what ls show from the /dev/block/folder
[email protected]:/dev/block/vold # ls
179:0
179:1
179:10
179:11
179:12
179:13
179:14
179:2
179:3
179:32
179:33
179:4
179:5
179:6
179:7
179:8
179:9

I have te same problem, do you fix it?

Same here! Anyone can help??
Στάλθηκε από το SM-N920C μου χρησιμοποιώντας Tapatalk