0

ATT version of Galaxy S3 running cm-10.1.2-d2att.zip

http://download.cyanogenmod.org/?type=stable&device=d2att

I seem to be having a storage issue. I'm guessing it was while I was changing to a new a ROM. I wiped the device and did a fresh install, but used titanium to restore settings.

the 12 gig internal reports having less than 1 gig free, but I can only find ~3 gig of information. (see pic)enter image description here

enter image description here

  • I'm not sure what CM10.1.2 points to: Could it be you switched from Android 4.1 to Android 4.2 with the latest update? If so, it might be the storage location has changed, IMHO from /sdcard to /storage/sdcard0 (I have no reference here, so I cannot check the exact locations). So on the Windows machine, it only shows /storage/sdcard0 now (as a Fuse "drive"), and you don't see the entire storage. Please check directly on the device. – Izzy Aug 12 '13 at 18:36
  • @Izzy IIRC Google changed the layout of system under 4.2, /storage/sdcard0 to /storage/primary/legacy/ - possible driver update/refresh? – t0mm13b Aug 14 '13 at 12:06
  • @t0mm13b That's what I was referring to. I saw the very same issue reported elsewhere (cannot remember the link), being caused by an update from one JB version to the next. During that process, data was duplicated from its original place to the new path (i.e. copied to the new and still left in the old place), which caused free storage to "drop", logically. – Izzy Aug 14 '13 at 12:16
0

How about your internal SD and emulated SD card free space? Sometime your phone has duplicate files on emulated SD and internal SD. Sometime it may be an issue with the setting restore. When you're switching ROM (different android version), it's not recommended restore data using old ROM backup.

  • I'll try this out. Are you saying that when you do a fresh rom install you (re)configure all your apps? – wlraider70 Aug 14 '13 at 16:03
  • Yes definitely, most of the ROM developer mention don't restore data using TB or any other backup apps. – chris Aug 17 '13 at 13:40
0

Try reflashing the Rom with full wipe again but don't restore anything with Titanium Backup.

similar problems usually happen when I used to restore data with Titanium Backup especially if the android upgrade from Rom to another is significant (e.g 4.1 to 4.2).

please try this and tell what happens :)

Edit: added my comment to the answer.

  • What is the idea behind this? Why should this help? Can you give some background, please? – Izzy Aug 14 '13 at 8:56
  • I used to get similar problems when I restored data with TB especially if the upgrade is significant like 4.1 to 4.2 JB.. I'm not very sure of the solution but if i'm wrong please correct me. – Kmelkon Aug 14 '13 at 10:40
  • 2
    I was not arguing the "right or wrong". My asking for background was to understand what idea stands behind it. May I propose you edit your answer and include some more details? Your comment already sheds some light, but might go unnoticed as people tend to feel them "not that important as the answer itself". So even including the facts from your comment would already make your answer more useful :) Thanks for your contribution! – Izzy Aug 14 '13 at 11:46
  • Thanks for the advice. I'll edit my answer, and if you saw that you further edit it after that, please do :) – Kmelkon Aug 15 '13 at 5:16
  • 1
    Maybe you contact Joël (the dev of Titanium) and ask for advice? He's usually quite responsive. If you get an answer that sheds more light, please don't forget to let us know :) – Izzy Aug 15 '13 at 12:24
-1

This usually happens if you have connected to Nokia to you pc via USD cable. Ignore this and continue using you phone. I have been observing this for more than 3 years now where phone drive shows in red and full.

  • 1
    Nokia? What Nokia? This is an Android site. – Izzy Aug 14 '13 at 12:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.