Hi,
Just Got the 7.7 3g - so far so good. Screen is as good as they say
The extra resolution defn. helps with web browsing.
Not finding any lag really.
7.7 is just about the limit for my two handed use but i would say the original 7" was a wee bit easier to handle but something with time should become more intuitive.
Just a few issues - external sd card is somewhat limited. Might be deliberate by Samsung but does not make sense.
Normal user apps cant access to the external sdcard. Using connect bot, i checked permissions and it seems that it is mounted by the os with system permissions, where as the internal sdcard is mounted as sd_rw.
This can't be correct? The only way to copy stuff to it is to use the samsung system file explorer as it has system permissions So copy to internal first then to external - this sounds like a bug?
I have not rooted this yet - might then chown to sd_rw get rid of this ?? There is a lot of entries in the vold.fstab to make sense of. Not a hacker so just looking around. A bit too early to start soft-bricking
But I take these don't have protected bootloaders so thats why we can root ?
Video playback is v.good but I am not able to throw on a bluray m2ts file (obviously with the sd card issue) and play smoothly. I found Dice player can handle m2ts by renaming it to a ts file. It then can use hardware decoding. Still drops frames but still watchable to a certain degree. For all other files mx player is still best. I have lossy transcoded some "native" blurays clips and seems that it handle high profile h264 1080p at high bitrates very well. Hoping, formatting sd card ext3/ext4 will improve things.
On the whole very impressive device - plus more ics goodies to come soon hopefully.
I've noticed some issues with the external SD card as well. Only the stock file manager can copy files from the internal storage to the external storage. I was able to transfer files to the ext. SD via Dooblou's Wifi Explorer, though. Although that would crap out a few times.
I'm hoping that we see some new ROMs with a different file system at any rate. The 4GB limit is so 1998.
Fix for external sd write issue
I've already posted a fix for this in our original thread?
davp said:
There is a fix for the write to external storage in this thread:
Samsung Galaxy Tab Plus->Galaxy Tab Plus General->unable to write files to external sd card
post #7
Requires root to apply fix.
There is a new permission that older file managers aren't asking for yet. The stock file manager knows to ask for it.
Fix worked for my P6810 wifi.
Click to expand...
Click to collapse
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Rooted and then applied this change.
Can write to ext sdcard !!!!
Cheers
Will apply as soon as i get tad, should be getting it today, cant wait
Sent from my GT-P1000 using XDA App
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
will6316 said:
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Using downloaded apps or the stock File Manager app? Because I formatted the SD card in the Tab and nothing else can write to it. Now, I can drag and drop stuff from my computer via MTP, but that's not the same issue.
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
burhanistan said:
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
Click to expand...
Click to collapse
Thanks Burhanistan. I had this problem too and did what you did to get around it. Now I can read/write to the external SD with any file explorer.
Hello,
I can access the external SD with no problem, only issue is Titanium backup showing 440Mb capacity on the external SD (32Gb card).
Anyone with the same issue? Any fix?
Thanks.
No problem for me
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Things must have changed as i got my P6800 recently did the upgrade from samsung and tried to copy to external sd and no problem for me. I never tried to do it pre upgrade but maybe the upgrade fixed that. Re i can copy and paste to device from my pc when its connected - to both device and sd. I can also copy using the the stock file manager from device to sd card.
No Issues here also
I recieved the tap a week ago. Now my 32GB Sandisk SD is here.
The Tap did at the first startup and using the described 12 MB Android update via internet conn.
Until now there is no issue between writing from/to SD over PC/MTP, copying between internal and external SD. Used preinstalled Filemanager and ES File Ex.
I tried it unrooted and rooted but not before the Android update.
davp said:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Some people are reporting the above procedure is no more needed, however, with several apps (like Titanium backup, and a SAMBA explorer), writing to the sdcard (extstorage/.../sdcard) is still impossible (GT6800 updated to latest samsung firmware).
I have used this procedure and can state that Titanium backup works now with the SD card.
Thanks to many reading within the XDA forum, I have found this simpler procedure :
- download / install the "Root Browser Lite" app from the android market
- add write access to group and other to the following directory: /system, /system/etc, /system/etc/permissions (with root browser Lite, press on the directory name during 3 seconds to get a contextual menu allowing to change the permissions)
- add write access to group and other to the file platform.xml in /system/etc/permissions
- use the editor of "Root Browser Lite" to modify the file platform.xml as described above (you should have two <group gid= ...> lines within the WRITE_EXTERNAL_STORAGE xml block.)
- save the file. Verify that a .bak file has been created and that the date of platform.xml changed.
- remove the write access.
- Turn off the GTAB, then turn it ON.
NB: Titanium backup still reports a erronous free size on the SD card (401MB), but backups on the sdcard work.
can't save the xlm doc
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Hi, I edit the file but when I try to save it I fail because it says original saved as .....xlm.bak, but I can't find that file and the one I find is unchanged, any ideas?
There is an automated installer for the fix here:
http://forum.xda-developers.com/showthread.php?p=21670802
Is for the plus but worked fine for me
Sent from my SCH-I815 using Tapatalk
damm, must forget something, just followed exacty all the steps
still no writing on sd card
the automatic installer failed also
IS there a way to go into the (forgive the incorrect term) "registry" or similar, and have Android re-interpret/understand that instead of looking in "/sdcard"... it should instead look/point programs to "/mnt/sdcard/extstorages/sdcard"...
i heard that it might be called something like a "simlink" or "symbolic link"... maybe this could resolve the application installation issue to the sdcard as well as backups, transfers, etc... right now, not only do i run out of space too fast, can't install apps to the sd card, but as well, if i should run a hard reset... all my data erases! (yes, the internal "SD card" is erased in a hard reset)...
so, for all practical senses, when it says it will erase data, unless you KNOW you have copied ALL you user data to your "Real" SD Card, you will kill your data without even knowing it when you do a hard reset, even if you "thought" you were protected because "I saved my info to the SD card!"
(and yes, this was my experience today, so it's a fact.)
backup programs won't point to the sd card, (app manager, titanium, app list backup, etc)...
so unless you actively move files individually to the card (and know where to look)...
Bottom line... is there a hack/workaround on this that's not just "open up for file transfers" or is someone working on a ROM that might kill the partitioning and allow the /sdcard to actually point to a real external card?
Edited: Nevermind...
acess-rights-hell
hi forum
i would like to use the EzyKernel v1 - 23/02/2012 as in post http://forum.xda-developers.com/showthread.php?t=1513413&highlight=ezykernel
one of the prerequisites is a stock ZSKL firmware.
on the tab is/was XXKL4 AUT/CH
i successfully flashed the ZSKL2 - but that's where the nightmare started: i could not write to sdcard, busybox/superuser don't work properly, as i can't get root via su - which means to me, that there are messed up accessrights also in other places, not just the SD. the funny thing is, that i finally got the overclocking EzyKernel working, but not busybox + superuser.
does that sound familiar to anyone ?
i would really appreciate any ideas about this.
thank you
with best regards from switzerland
roland
could you please explain what "make sure you have mounted the file system r/w" means. And sorry for my noob question, but does this fix allow to install apps on the external sd card or I'm missing something.
To save some people time in searching and asking the same question I had (and for 4.4.2 I think there will be plenty...):
I had severe issues using a brand new SD card in a brand new unrooted Galaxy S5. However, I now found through test that it was not the card.
I tried many things, formatting on my computer, formatting on another phone, etc etc. Nothing worked. I then tried to use the card on other devices, which worked fine! I then tried other cards, none of them seemed to work.
So I thought the S5 was defective. I did some searching online, and found that it actually is not defective. This is a feature of kitkat 4.4.2!
The card is perfectly usable, but under very restrict situations.
For example, reading is perfectly possible, but writing is controlled by kitkat. I found through some websites that Samsung decided to beef up security and at the same time make the use of external storage more clean.
Previously you could use any file browser to manage any file son any external storage, like an SD card. Although this gave great freedom, Samsung also seemed to believe that it is a source of security risk where rogue apps could read/write to folders they didn't create. They also seemed to believe this made management of files on external storage messy. To control this Samsung now allows properly installed apps to generate folders only in internal memory, and those same apps can only access folders they themselves created. The exception to this are factory standard default apps that come preinstalled on the device.
So my mistake was to use ASTRO file manager to move around a file. Once I read the issue online, I tried the same action with Samsung's pre-installed file manager, and to my surprise the file did transfer to the SD card!
To further clarify, I suspect this "feature" is limited to write activities. For example, backup to SD apps will fail to write apps to SD. Similarly, Airdroid cannot copy files from your desktop to the SD card, only to their own folder (and thus you need Samsungs file manager to move those files to the SD card).
What's interesting about this however, is that READ access seems to still be possible. ASTRO file manager can still read files from directories other apps made. Adobe reader can still read files on all kinds of folders.
The criminal spy app can still read and copy your banking files from your bank directory to its own directory for transfer to the criminal mind who will then plunder your account. So no, the security issue Samsung wanted to address has not been addressed.
What is my opinion about this? Well, I think Samsung made a nice attempt to improve security. However, they completely failed to address the biggest security risk, which isn't write access, but read access. And at the same time made it very painful and difficult to store large numbers of music, video and document files to the SD card. Because now you will either need to plug in your memory card into your computer, or move all those files via internal memory to the external SD card using Samsungs file manager, which of course takes much more time.
More info on the feature can be found here:
http://gs4.wonderhowto.com/how-to/b...ns-android-4-4-kitkat-your-galaxy-s4-0152036/
here:
http://support.solidexplorer.pl/responses/kit-kat-442-issue
And here:
http://developer.samsung.com/forum/...Lines=15&startId=zzzzz~&startPage=2&curPage=4
We could all ask Samsung to revert this "feature", but chances that they will, are remote since there are ways around this problem.
Of course, people who use many many apps/games will be out of luck, as they will be restricted to 16/32 GB.
Note to moderators: Can we make this a sticky for kitkat 4.4.2?
Root and you'll be able to R/W on the ext-SD card and try this app SDFix
Samsung has nothing to do with it... It's an Google's android policy.
So, the links I provided make that same statement. I.e. I'm aware of possible fixes. However, I bought my phone in Singapore so I could have a reliable unhacked, unrooted, unmodified phone. Others might also want original phones and not root their phone until their warranty runs out.
This was not my point though. My point was to provide some info that could be turned into a sticky so it is easier for people to find what could cause their memory card issues.
I still hope the original post will help others troubleshoot their memory card issues with their s5.
Hi, My partner has a S5, it is running 4.4.2, as you know google have locked down using file browsers and other SD card apps.
The issue being that I have a Note 3 running STOCK 4.4.2 with no root access and I can use ES File Explorer to move files from my Media server to my External SD card.
Does any one know why this is and how you can do this without rooting the device>?
84DGR said:
Hi, My partner has a S5, it is running 4.4.2, as you know google have locked down using file browsers and other SD card apps.
The issue being that I have a Note 3 running STOCK 4.4.2 with no root access and I can use ES File Explorer to move files from my Media server to my External SD card. Does any one know why this is and how you can do this without rooting the device>?
Click to expand...
Click to collapse
Google tightened up security in Kitkat by restricting third party access to your SD card. Apps now only have permission to work within one folder or area of the card, rather than anywhere. A file explorer, even a non-root version would logically have broader access than most types of apps due to the nature of what a file explorer needs to do.
You can revert the Kitkat changes if you are rooted. I am not aware of any apps or methods to so so without root. Nor can you revert to a pre 4.3 JellyBean firmware as Samsung has blocked reversion to preclude people removing Knox that way. You might be able to downgrade to an earlier Kitkat version that doesn't have the SD permissions change yet. I haven't confirmed that, but it might be possible.
But in practical terms you either need to root and revert the changes, live with the restrictions or seek out updated versions of apps that work better in the new regime.
.
I slowly look there no longer. I have rooted my S3 Neo initially quite normal and provided with CWM as it has been explained in various tutorials. Then I fixed the Android 4.4 write access issue with the "NextApp SDFix" from Android market. With the "ES File Explorer" and "Total Commander" I could normally rename files on the SD card, copy and move.
However, to me the practical effect is associated with all apps, which store data automatically on the SD card very mysterious, because instead of the SD card, they will continue stored internally namely in "/storage/Emulated/0". I tested this with "Dead Trigger 2", which is usually stores the game data in "Android/OBB". In Application Manager I have the opportunity the app to move itself to the correct SD card (.android_secure directory), but just the app itself and not the game data wich stay in the internal, emulated SD-Card.
For my previous smartphone, an Ace 2 NFC (I8160P) there was a fix for it to fit the "vold.fstab" to file: http://forum.xda-developers.com/showthread.php?p=28419837#post28419837
I could find only a tutorial changing the internal memory with the real SD-Card for the normal S3, which, however, is probably not compatible with the S3 Neo: http://android-hilfe.digidip.net/visit?url=http://forum.xda-developers.com/showthread.php?t=2036796 - Or should I try it so anyway?
At first the question: Why the Kitkat-Fix is at all useful, if it does not help in practice and the data continues to be stored internally? The only thing that has been directly accessed files to the correct SD card was the photo app but that's about it.
Update: I just see that it also provides an Android folder on the right SD card as well as in the emulated and actually reside in folders and the installed apps, including "Dead Trigger 2". However, the folder unlike emulated SD card are completely empty. What does that have to mean again?
I hope somebody can help me ans find a solution as I can't use my external SD-Card for most game datas or apps as planned or I will send back my S3 Neo tomorrow.
PLEASE!!! Can somebody help me???
do you use xposed? there are a couple of modules that allows you to use obb files from sdcard. Personally i use "xinternal". those ps apps never worked for me also.
Use Folder Mount
I use a xposed module called "HandleExternalStorage" and it works like a charm! Try it yourself!
Good luck
Ok, I have had many phones and this problem is a little bit weird for me.
I'm using Poweramp as my daily driver for music. I tried deleting some songs I stored on my SD and it said my files were write protected. I then used Root Browser just to see, that most of my music and photos I have on my SD card were not located in /sdcard but in /storage/57EF-B920, a directory I never created. When I put the SD card into my PC, I can see all my files normally and r/w without any issues.
I figured I could only alter files using the stock file browser and gallery app, but why? And why are my SD card stored media files showing up in /storage/57EF-B920 instead of their actual path? Is that a security feature?
My phone is 100% stock and not rooted.
Thanks for your help!
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
hawkerpaul said:
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
Click to expand...
Click to collapse
Sorry for the late reply, but thanks for the explanation! So it's because how MM works vs how Lollipop did and Poweramp not being uptodate with that? I'll try out the permission thing and even if I fail, it's good to know why it won't work. Thank for your help!