Join now - be part of our community!

Z3 compact data issue

ManilaDave
Visitor

Z3 compact data issue

Hi I'm ManilaDave in Ireland. I have the Xperia Z3 Compact.

I joined the Forum because of an issue with my new Z3 Compact. I have a large electronic reference library that I downloaded to my phone and transferred to the 64 gig MicroSD card. (I transferred the app before downloading the books). The information on the app was that the app itself and the data - running to almost 9 gigs - were actually on the MicroSD card with almost nothing on the Device Memory, but the internal memory was also reading 95% full. I had no option but to delete the data from the app. As soon as I did that the internal memory on the device freed up giving me 8 gigs of available space. It is clear that the data is not transferring properly from internal memory to MicroSD. 

It seems then that the data is not completely transferring and leaving a "footprint" on the internal memory as large as that on the SD card. When I went to the "Transfer data to SD card" control it showed no data available to transfer even though the internal memory was reading 95% full. Then when data was deleted both SD and Internal memory were increased substantially. 

Anyone got any idea what is happening here and how to fix it? Why doesn't the data download directly to the SD card when the app is located there?

2 REPLIES 2
peter58home
Visitor

Hello

i agree with you

kind regards peter58home/

ManilaDave
Visitor

Hi Peter!

I've since discovered that the problem is with the app itself rather than with my Z3 Compact which I love. The app developers have not developed a "work around" the issue and the data will automatically download to the internal memory. This seems crazy from the developer of a library app who would know better than anyone that the digital resources (books) they sell take a lot of space and will quickly clog up the internal memory on modern phones / tablets. This has something to do with Google policies but other developers have developed "work around" solutions to the problem. I've requested the developer of the library app to look at the issue and it seems I'm not alone in being frustrated by this.