Out of the blue sky, every time I try to copy and paste a file from one folder to another, I get an error message that says the following:
"Cannot copy (file name here), access is denied. Be certain that there is enough free storage memory, that the destination is not write protected and that the file is not currently in use". I have double checked ALL of the above possible causes of error and NONE of them apply. There is more than enough storage space, there is more than enough free storage memory, and as far as I know, there is no way to actually SET write protection on WM 6.5. I've checked the SD card, and the little switch on the side is NOT set in the "locked" position. Anybody know how to fix this so I can copy and paste files again? The phone I'm using is Siemens SX66 and I'm using WM 6.5, build 212202.
ok, there are several ways to deal with that, the first thing to try is another file manager:
TotalCommander Download (Mirror)
if that shows the same error message, it is not the program, but actually the storage. in that case, try a different sd card or, if it happens in the internal storage as well, try a hard reset or a re-flash, maybe a newer rom would also be nice.
Hi,
I was organising my computer today (ironically in preparation for a backup) and plugged in my phone to copy files and it wouldn't mount or ask for the type of connection. I went to unmount it in Android and it said the size was '00'. I put the card in a card reader and did a check and it seems a few sectors have gone bad (which implies the reserve pool has filled too). That would explain the way it has been pausing for long periods of time when copying files (haven't done that in a month or so).
I've managed to copy all but one of the .apk files in /sd-ext/app and /sd-ext/app-data. If I put these (plus an empty dalvik-cache) on a new partition on a new card will A2SD+ be happy (apart from the one broken app of course)? Does each .apk have special permissions per app or anything? I should probably do a full wipe but I'm trying to hold out for official gingerbread. I tried to do a nandroid backup but clockworkmod says 'cannot stat /sdcard'
I haven't managed to get much of the FAT32 partition as it keeps dying after a few I/O errors and requires me to re-plug it (every sector comes up with I/O errors even when they are fine). I managed to get some files that I have nowhere else using ddrescue on individual files (a full image doesn't work because of the endless errors after a while). I think I may have made things worse as I stupidly didn't mount the drive in read-only mode. Now android mounts the SD card in read-only mode too, where it wasn't doing that earlier today. I did notice a few I/O errors in the android system log when I was trying to figure out the problem.
I'm misisng some (fairly unimportant) photos because the DCIM/100MEDIA folder seems to have lost it's directory listing. Does anyone have any suggestions for tools to recover these? I tried photorec but it only seems to find the thumbnails. I can't get the partition to mount on Windows but it more or less works on linux. According to HD Tune disk scan (chkdsk just freezes), the number of bad blocks is actually fairly small.
I did a whole pile of app updates yesterday which must have pushed it over the edge (many of which failed due to 'insufficient space' on the A2SD partition). The phone still mostly works (since most apk files are readable and the settings are stored on the phone).
Does dalvik-cache get updated much? I'm worried it might hugely shorten the life of a new card.
Thanks
Running Leedroid 2.4 A2SD+
Ok, I've got a new 16GB MicroSD card.
I can't get Android to recognize the apps in the A2SD partition, it regenerates the dalvik cache though. I've tried setting the .apk files to be globally readable and writeable.
Any ideas?
Yay, got it working
It turns out you need to run fix_permissions.sh, as Android does care about apk files and data files having the same permissions. fix_permissions did some strange changes to data permissions but it all seems to work bar needing to re-add most of my widgets to GoLauncher. Leedroid doesn't include fix_permissions but after much hunting (most links I found were broken), I managed to find it on cyanogenmod github.
https://github.com/CyanogenMod/android_vendor_cyanogen/raw/gingerbread/prebuilt/common/bin/fix_permissions
Just copy it to the SD card and run from ADB shell (or a terminal):
Code:
su
chmod +x /mnt/sdcard/fix_permissions
sh /mnt/sdcard/fix_permissions
Note that you must use sh, just ./fix_permissions gives permission denied for some reason.
Edit: seems it didn't correctly fix apps in app-private (of which I only had 2). I just reinstalled them (probably possible to fix them manually by looking at the owner in /data/data and chown the apk).
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
iunlock said:
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
Click to expand...
Click to collapse
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine?
Did you try using a card reader an see if you can access it that way?
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too
Sent from my SM-N900T using Tapatalk 2
Mod, can you move this over to the proper forum. Thanks.
Possible causes / Things I've tried:
I do have some pictures in an App called: KeepSafe, where you have to enter in a pin code to access those pics, so then I was thinking maybe this was causing the problem. So I entered the App and tried connecting, but darn...same old thing. Doesn't work and I keep getting the same error message as the pic I have attached to the original thread.
I have also tried to reboot in Recovery (twrp) and tried to mount the exSD, but still nothing. Here's the message it gave me:
E: Unable to mount '/usbstorage'
This is driving me crazy. Anyone?
cbucz24 said:
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine? - Yes I can access it just fine through ES File Explorer. I've also checked the permissions.
Did you try using a card reader an see if you can access it that way? - I'm sure it'll work fine with a card reader, but that's not my preferred method. It's just frustrating for something to have worked and out of the blue stop.
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too - I've uploaded a screen shot of the message that I'm receiving.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Try moving the KeepSafe files to another directory.
Frank
Update 6/30/14
SUCCESS!
From the gallery on your phone, you can create folders and move (not copy) over pictures/videos and it'll be default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just did it in little batches of 20 here 50 there and made just a few folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple.
Update 6/30/14
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
From the gallery on your phone, you can create folders and move (don't copy) over pictures/videos and it'll by default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just moved about a couple hundred pictures to varies folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ... (Windows wouldn't open it either.)
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple. Hope this helps.
iunlock said:
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Click to expand...
Click to collapse
It is more likely that they thought it very unlikely that there would be more than the old limit of 2,000 files in a directory so they didn't allow for it in the program code.
Frank
Ok so I'm on an H810 and it's rooted. Software version H81010b. Now I have hardly done anything root wise aside from enabling the Hot Spot really. Now for some reason when I take pictures my camera thinks it's saving it to my SD CARD, but when I look, the picture is correct, just shows a strange icon, see attached. It used to work fine. At the same time Titanium backup used to work fine now it says that the directory I'm pointing it to is readonly. !? I have already enabled write access on my SDCARD long ago using the Netxapp fix and if I run it again it says that there's nothing to be done because write access is already set up. When I take a picture, the thumbnail shows up in the small window/circle, but when I touch it to load the image, it shows me a blank image actually. Now if I set the camera to take images on the INTERNAL sd card, then it's fine. I wasn't having any issues with this until a couple days ago... any ideas? Solutions? Thanks!!
OK, think I figured it out. I went into ES File Explorer and went to ROOT EXPLORER and then to MOUNT R/W and it showed the external sd card mounted as read only. If I set it to r/w then my camera and other apps work fine writing to the sd card. If I reboot my phone however, the problem comes back until I LAUNCH ES FILE EXPLORER but I don't have to do anything else, after I launch it everything else can write to the sdcard again. I am guessing this happened because I disabled boot notification/boot startup for es file explorer. My bad. Strange though that this has such a prolific effect on the device since this is a 3rd party app. HOWEVER, I do have root explorer enabled in it so maybe that has something to do with it?
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar? Ans: Apparently yes, it is a "feature", aren't we lucky.
Am I missing some special setting? Ans: No.
Any thoughts on what the issue could be or if there is a fix? Ans: It can be fixed using root magisk.
Are your mount points similar/different? Ans: Guessing not and isn't related to the problem.
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)? Ans: Not the cause of the problem.
Thanks
meltwater.
i thought i was the only one with zero bytes files. and when you transfer them back- all good
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
dvijetrecine said:
i thought i was the only one with zero bytes files. and when you transfer them back- all good
Click to expand...
Click to collapse
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
SUPERUSER said:
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
Click to expand...
Click to collapse
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
meltwater said:
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
Click to expand...
Click to collapse
Magisk is the new "supersu" standard when it comes to root.
So it is the root per say. Yes you need root. But you root your phone by installing Magisk, its kind of a multi-tool.
You need to unlock your bootloader, if not already unlocked if you bought it that way like I did from Tradingshenzhen.
It will say Unlocked on the bootloader mi splash screen when you turn the phone on if the bootloader is unlocked.
And then you need to properly flash TWRP. Other than that you can stay on stock rom and use Magisk
Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ExSDCard Write Access Enabler module thread https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
I see something I did not see before.
In the thread OP mentions:
Since the v3.3 ZIP version, a feature has been added especially for Oreo (Android 8) users, on this Android version, several special permissions can be used by any app.
For exemple, theses specials permissions are used to get access to reading logs, managing the power of the device.
If you want to use this special feature, you just have to follow theses easy steps:
- creating a simple file named "ExSDCard_Oreo_apps" in the module path, so: /sbin/.core/img/ExSDCard/ExSDCard_Oreo_apps (remove any extension).
- Write all the apps package names that require a special permissions, one by line, for exemple:
Click to expand...
Click to collapse
So with this you can apparently create custom rules for apps that don't support selecting the external SD card path.
Maybe you should look in to that and experiment
This bug happened across android 8.0 in various brand.
Since I familiars with ES File Explorer, I solved by root the phone, convert ES File Explorer into System app via Titanium Backup, then everything work perfectly fine. No more 0 bytes copy file.
ES File Explorer still work even I un-root my phone by uninstall Magisk.
If you're really not want to root your phone or any other reason. Just copy file that you want then restart your phone. Copied file will now become usable file.
My bootloader isn't unlocked and for now I'd rather avoid rooting my phone (may well do so later).
Good to know there are work-arounds, and that my device hardware is ok.
Will have an experiment and see if I can live with it until I have a go at rooting. Even if I do the temp fix of ES explorer.
Thanks for the info and tips.
Same **** for me. 1 year to solve this stupid bug and they dont have fix this **** yet
Say thanks to xiaomi[emoji108][emoji867]
Enviado desde mi MI MAX 3 mediante Tapatalk
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Wmateria said:
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Click to expand...
Click to collapse
Yep, looks like it is a solid bug. For now, I'm living with it and use the space I have on internal memory to transfer data to before using a System file manager to transfer to SDcard.
Been trying some app development and now found the "Install via USB" bug.
Again can work around it, but it does spoil debugging with Android Studio.
There are certainly some odd bugs on this phone, I suspect down to Xiaomi going "off plan".
meltwater said:
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar?
Am I missing some special setting?
Any thoughts on what the issue could be or if there is a fix?
Are your mount points simlar/different?
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)?
Thanks
meltwater.
Click to expand...
Click to collapse
no need for this post. erased.
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
jorgeepelos said:
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
Click to expand...
Click to collapse
Get a Mi Mix 2S
Wmateria said:
Get a Mi Mix 2S
Click to expand...
Click to collapse
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk[/QUOTE.
It's people like you who make the community bad when you out your hatred in the forums or is not knowledgeable enough because main post talks about THIRD PARTY FILE MANAGER APPS not 1ST PARTY Xiaomi File Manger APP and thinks it's the end of the world on here and the Xiaomi forums. And trust me there is plenty of you people around pushing Devs and OP here by complaining when other people already stated the fact many times on a thread, and trust me, I hardly take offense. "Read", it works.
Click to expand...
Click to collapse