Can't access Internal Storage

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Run File Manager on Android
2.Clik on home and then on storage "folder"
3.It shows home screen, instead of Internal Storage.

What is the expected output? What do you see instead?
It shows home screen, instead of Internal Storage.

What version of the product are you using? On what operating system?
I'm using Froyo 1st beta on my Omnia II.

Please provide any additional information below.
Internal storage works on WinMO fine and access on Sd card from both systems 
works too.

Sorry for my bad English.

Original issue reported on code.google.com by lukas.je...@gmail.com on 14 May 2011 at 12:47

[GoogleCodeExporter]

Because you run android on you're sd card, you cant acces you're (winmo) 
internal memory. Unless you run android on internal memory. This is not een 
issue, its normal.

Original comment by JJasperd...@gmail.com on 23 May 2011 at 3:37

[GoogleCodeExporter]

JJasperd..please dont give wrong information here..just dont answer it if u 
dont know..

btw..you must edit your init.rc to mount internal storage to correct partition 
number..
for testing download terminal emulator from market then type

su
mount -t vfat /dev/block/mmcblk0p1 /storage
(change to mmcblk0p5 if you have extended partition)

then check your /storage folder via file manager..

TIPS : To check available partition in your phone..type this in terminal

cat /proc/partitions

then u'll have a list of current available partitions..

Original comment by boemye...@gmail.com on 23 May 2011 at 3:59

[GoogleCodeExporter]

Thank you very much. I'll try it!

Original comment by lukas.je...@gmail.com on 23 May 2011 at 6:21

[GoogleCodeExporter]

I can mount the partition but when I check it with file manager, the file 
manager fail. I think that it could be a permission problem. Could you help me?

Original comment by jjrom...@gmail.com on 2 Sep 2011 at 3:38

[GoogleCodeExporter]

I can mount the partition but when I check it with file manager, the file 
manager fail. I think that it could be a permission problem. Could you help me?

Original comment by jjrom...@gmail.com on 2 Sep 2011 at 3:39

[GoogleCodeExporter]

can you post the output of cat /proc/partitions in Android terminal emulator?
(In froyo it is in settings -> dev tools)

Original comment by erikcas1972@gmail.com on 2 Sep 2011 at 4:00

[GoogleCodeExporter]

This is the output:

# cat /proc/partitions
major minor  #blocks  name

179        0    8028160 mmcblk0
179        1          1 mmcblk0p1
179        5    7503872 mmcblk0p5
179        6     524286 mmcblk0p6
179        8    1921024 mmcblk1
179        9          1 mmcblk1p1
179       13     872439 mmcblk1p5
179       14    1048576 mmcblk1p6

In the terminal I can see the storage directory with its files but with File 
Manager cannot.

thanks.

Original comment by jjrom...@gmail.com on 2 Sep 2011 at 4:19

[GoogleCodeExporter]

which one do you mount in terminal?

Original comment by erikcas1972@gmail.com on 2 Sep 2011 at 4:30

[GoogleCodeExporter]

I mount mmcblk0p5

Original comment by jjrom...@gmail.com on 2 Sep 2011 at 7:42

[GoogleCodeExporter]

can't reproduce it. Do you use official dev install, or some bundle/iso?

Original comment by erikcas1972@gmail.com on 3 Sep 2011 at 10:24

[GoogleCodeExporter]

I use this page in order to install it: http://o2droid.phj.hu/index_en.php

Original comment by jjro...@focosistemas.com on 4 Sep 2011 at 1:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Did you by any chance encrypt your "My Storage"? I know that WM users in my 
company who receive company-email on their phone have their storage to be 
encrypted. Just tried this on a collegues'B7610. My Storage does indeed NOT 
show up in File Manager, even when mounted manually 

Original comment by erikcas1972@gmail.com on 4 Sep 2011 at 2:58

[GoogleCodeExporter]

Really, I don't know, I have not done anything in order to encrypt "My Storage" 
but I don't know if it is an "automatic option", How do I know it?

Original comment by jjro...@focosistemas.com on 4 Sep 2011 at 4:13

[GoogleCodeExporter]

I had the same error and i have a possible workaround, I probe deleting (make 
backup first) some files I think cause this problem and then work fine.

I think it´s a problem whith a long for the name of files or similar. If i 
have more information, i´ll post here.

Sorry for my English.

Original comment by axterixs...@gmail.com on 14 Nov 2011 at 8:39

[GoogleCodeExporter]

OK, i have a folder named Memorándum in storage root. Deleting this folder(and 
other similar) dont have this problem.

Maybe the problem was the special character. 

Original comment by axterixs...@gmail.com on 14 Nov 2011 at 9:41