MicroSD Card Not Accessable & Won't Unmount

This is a discussion on MicroSD Card Not Accessable & Won't Unmount within the Nexus One forums, part of the Google Phones category; HI, I've started getting some weird problem with my Nexus One & MicroSDHC cards. I have an 8gb class 4 MicroSDHC card, which was working ...

Results 1 to 7 of 7

Thread: MicroSD Card Not Accessable & Won't Unmount

  1. #1
    Junior Member bjblackmore's Avatar
    Join Date
    Sep 2010
    Posts
    12

    Question MicroSD Card Not Accessable & Won't Unmount

    HI,

    I've started getting some weird problem with my Nexus One & MicroSDHC cards. I have an 8gb class 4 MicroSDHC card, which was working perfectly a week or so ago, however I've started to notice that after booting the N1 up, some of the icons on my desktop are not displaying correctly, and are the basic android default icons. When I try to launch the applications it tells me its unable to launch. If I go into Settings > SD Cards & Phone Storage, and try to unmount the SD card, the phone seems to hang, and I can't get out of that screen, until a warning mesaage pops up telling me the SD card & phone storage app is not responding, and do I want to Force Close, Wait or Report. I've also found I can't access the SD card via USB.

    I can get the card to read OK, but I have to format it, then copy stuff back on. If it's just data, the card seems OK, but the moment I start moving applications on to the SD, it seems to cause problems. I can also fix the problem by deleting the last installed/moved application off of the card, currently that's MSN & Armored Defense Lite.

    I've also tried mounting the SD card in Windows 7, and running chkdsk /f, which does find some trunkated files/folders, and apparently fixes the problems. But when I put it back in the N1, I get the same problem!

    Has anyone else experienced this? Anyone know what might be causing it, or how to fix it?

    I'm using a non-rooted N1, Froyo 2.2, FRF91

    Any help would be appreciated

    Ben

  2. Android.net is the premier Android Forum. Registered users do not see these ads. .

  3. #2
    Android Lurker DudeRandom21's Avatar
    Join Date
    Aug 2011
    Posts
    0
    Do you still have the original 4gb sd card that came with the phone(or any other sd card). If yes does it work on that card if yes then it has to be your sd card.

  4. #3
    Junior Member bjblackmore's Avatar
    Join Date
    Sep 2010
    Posts
    12
    I'll give it a try. I have tried another 8gb class 4 card, and that was having the same problems. The 4gb sandisk card that came with it, is only a class 2, which is why I was using the class 4 8gb. I've also ordered a new 8gb class 6 card for 15, to see if that fixes it.

    I seem to have improved the problem, slightly, by formatting again, and loading stuff on 1 app at a time. The phone doesn't seem to mount the card properly on boot up, as no apps load after initial boot, even though the 'SD cards & phone storage' settings manager says it's mounted.

    However, I can now unmount the card, and remount it, without the 'sd card & phone storage' app hanging, and the apps will open correctly. If I could just figure out why the card isn't mounting correctly at boot up, it would be sorted!

  5. #4
    Junior Member bjblackmore's Avatar
    Join Date
    Sep 2010
    Posts
    12
    UPDATE: I don't think it's the card, I copied everything on the 8gb onto the 4gb that came with the phone, and it still won't mount the SD card.

    I 'think' it might be something to do with an APP called Blow Up Lite. It seems that everytime I move this to the SD card, the SD card won't mount. I'll have to do more testing, it might just be coincidence that everytime I move that app, I then reboot to test!

  6. #5
    Junior Member bjblackmore's Avatar
    Join Date
    Sep 2010
    Posts
    12
    When trying to unmount the SD card and it hangs, I get the following error in Dalvik Debug:

    11-05 10:52:25.875: INFO/ActivityManager(82): Displayed activity com.android.settings/.Settings: 291 ms (total 291 ms)
    11-05 10:52:27.445: INFO/ActivityManager(82): Starting activity: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.deviceinfo.Memory }
    11-05 10:52:27.825: INFO/ActivityManager(82): Displayed activity com.android.settings/.deviceinfo.Memory: 363 ms (total 363 ms)
    11-05 10:52:56.571: WARN/WindowManager(82): Key dispatching timed out sending to com.android.settings/com.android.settings.deviceinfo.Memory
    11-05 10:52:56.571: WARN/WindowManager(82): Previous dispatch state: {{KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=72} to Window{44e4c768 com.metago.astro/com.metago.astro.FileManagerActivity paused=false} @ 1288954267295 lw=Window{44e4c768 com.metago.astro/com.metago.astro.FileManagerActivity paused=false} lb=android.os.BinderProxy@44edd490 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{44e4c768 com.metago.astro/com.metago.astro.FileManagerActivity paused=false}}}
    11-05 10:52:56.571: WARN/WindowManager(82): Current dispatch state: {{null to Window{45011b80 com.android.settings/com.android.settings.deviceinfo.Memory paused=false} @ 1288954376573 lw=Window{45011b80 com.android.settings/com.android.settings.deviceinfo.Memory paused=false} lb=android.os.BinderProxy@44ead310 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{45011b80 com.android.settings/com.android.settings.deviceinfo.Memory paused=false}}}
    11-05 10:52:56.956: INFO/Process(82): Sending signal. PID: 4044 SIG: 3
    11-05 10:52:56.956: INFO/dalvikvm(4044): threadid=3: reacting to signal 3
    11-05 10:52:57.015: INFO/dalvikvm(4044): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.125: INFO/Process(82): Sending signal. PID: 82 SIG: 3
    11-05 10:52:57.125: INFO/dalvikvm(82): threadid=3: reacting to signal 3
    11-05 10:52:57.325: INFO/Process(82): Sending signal. PID: 155 SIG: 3
    11-05 10:52:57.325: INFO/dalvikvm(155): threadid=3: reacting to signal 3
    11-05 10:52:57.525: INFO/Process(82): Sending signal. PID: 157 SIG: 3
    11-05 10:52:57.525: INFO/dalvikvm(157): threadid=3: reacting to signal 3
    11-05 10:52:57.725: INFO/Process(82): Sending signal. PID: 2023 SIG: 3
    11-05 10:52:57.725: INFO/dalvikvm(2023): threadid=3: reacting to signal 3
    11-05 10:52:57.865: INFO/dalvikvm(155): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.865: INFO/dalvikvm(82): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.905: INFO/Process(82): Sending signal. PID: 169 SIG: 3
    11-05 10:52:57.905: INFO/dalvikvm(169): threadid=3: reacting to signal 3
    11-05 10:52:57.915: INFO/Process(82): Sending signal. PID: 4036 SIG: 3
    11-05 10:52:57.915: INFO/dalvikvm(4036): threadid=3: reacting to signal 3
    11-05 10:52:57.915: INFO/dalvikvm(157): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.915: INFO/Process(82): Sending signal. PID: 171 SIG: 3
    11-05 10:52:57.925: INFO/dalvikvm(2023): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.925: INFO/Process(82): Sending signal. PID: 3601 SIG: 3
    11-05 10:52:57.925: INFO/dalvikvm(171): threadid=3: reacting to signal 3
    11-05 10:52:57.925: INFO/dalvikvm(3601): threadid=3: reacting to signal 3
    11-05 10:52:57.925: INFO/dalvikvm(169): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.935: INFO/Process(82): Sending signal. PID: 4025 SIG: 3
    11-05 10:52:57.935: INFO/dalvikvm(4025): threadid=3: reacting to signal 3
    11-05 10:52:57.945: INFO/dalvikvm(4036): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.945: INFO/dalvikvm(4025): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.945: INFO/Process(82): Sending signal. PID: 3609 SIG: 3
    11-05 10:52:57.945: INFO/dalvikvm(3609): threadid=3: reacting to signal 3
    11-05 10:52:57.955: INFO/Process(82): Sending signal. PID: 3592 SIG: 3
    11-05 10:52:57.955: INFO/dalvikvm(3592): threadid=3: reacting to signal 3
    11-05 10:52:57.955: INFO/dalvikvm(171): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.975: INFO/dalvikvm(3601): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.975: INFO/Process(82): Sending signal. PID: 4014 SIG: 3
    11-05 10:52:57.975: INFO/dalvikvm(4014): threadid=3: reacting to signal 3
    11-05 10:52:57.975: INFO/Process(82): Sending signal. PID: 3557 SIG: 3
    11-05 10:52:57.975: INFO/dalvikvm(3557): threadid=3: reacting to signal 3
    11-05 10:52:57.975: INFO/dalvikvm(3592): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.975: INFO/dalvikvm(3609): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.986: INFO/Process(82): Sending signal. PID: 1334 SIG: 3
    11-05 10:52:57.986: INFO/dalvikvm(1334): threadid=3: reacting to signal 3
    11-05 10:52:57.986: INFO/Process(82): Sending signal. PID: 3585 SIG: 3
    11-05 10:52:57.986: INFO/dalvikvm(3585): threadid=3: reacting to signal 3
    11-05 10:52:57.986: INFO/dalvikvm(4014): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.986: INFO/dalvikvm(1334): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.986: INFO/dalvikvm(3585): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:57.995: INFO/Process(82): Sending signal. PID: 197 SIG: 3
    11-05 10:52:57.995: INFO/Process(82): Sending signal. PID: 3977 SIG: 3
    11-05 10:52:57.995: INFO/dalvikvm(197): threadid=3: reacting to signal 3
    11-05 10:52:57.995: INFO/Process(82): Sending signal. PID: 3949 SIG: 3
    11-05 10:52:57.995: INFO/dalvikvm(3977): threadid=3: reacting to signal 3
    11-05 10:52:57.995: INFO/dalvikvm(3949): threadid=3: reacting to signal 3
    11-05 10:52:58.005: INFO/dalvikvm(3557): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.015: INFO/Process(82): Sending signal. PID: 2018 SIG: 3
    11-05 10:52:58.015: INFO/dalvikvm(2018): threadid=3: reacting to signal 3
    11-05 10:52:58.015: INFO/dalvikvm(3949): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.015: INFO/Process(82): Sending signal. PID: 3714 SIG: 3
    11-05 10:52:58.015: INFO/dalvikvm(3714): threadid=3: reacting to signal 3
    11-05 10:52:58.026: INFO/dalvikvm(3977): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.026: INFO/Process(82): Sending signal. PID: 3723 SIG: 3
    11-05 10:52:58.026: INFO/dalvikvm(3723): threadid=3: reacting to signal 3
    11-05 10:52:58.035: INFO/dalvikvm(197): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.035: INFO/Process(82): Sending signal. PID: 3740 SIG: 3
    11-05 10:52:58.035: INFO/dalvikvm(3740): threadid=3: reacting to signal 3
    11-05 10:52:58.035: INFO/dalvikvm(2018): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.045: INFO/dalvikvm(3714): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.045: INFO/Process(82): Sending signal. PID: 3733 SIG: 3
    11-05 10:52:58.045: INFO/dalvikvm(3733): threadid=3: reacting to signal 3
    11-05 10:52:58.045: INFO/Process(82): Sending signal. PID: 3667 SIG: 3
    11-05 10:52:58.045: INFO/dalvikvm(3667): threadid=3: reacting to signal 3
    11-05 10:52:58.045: INFO/dalvikvm(3723): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.045: INFO/dalvikvm(3740): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.055: INFO/Process(82): Sending signal. PID: 3654 SIG: 3
    11-05 10:52:58.055: INFO/dalvikvm(3654): threadid=3: reacting to signal 3
    11-05 10:52:58.055: INFO/Process(82): Sending signal. PID: 3660 SIG: 3
    11-05 10:52:58.055: INFO/dalvikvm(3660): threadid=3: reacting to signal 3
    11-05 10:52:58.055: INFO/dalvikvm(3733): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.055: INFO/Process(82): Sending signal. PID: 3641 SIG: 3
    11-05 10:52:58.055: INFO/dalvikvm(3641): threadid=3: reacting to signal 3
    11-05 10:52:58.095: INFO/dalvikvm(3654): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.095: INFO/dalvikvm(3660): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.095: INFO/dalvikvm(3667): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.095: INFO/Process(82): Sending signal. PID: 3495 SIG: 3
    11-05 10:52:58.095: INFO/dalvikvm(3495): threadid=3: reacting to signal 3
    11-05 10:52:58.095: INFO/Process(82): Sending signal. PID: 628 SIG: 3
    11-05 10:52:58.095: INFO/dalvikvm(628): threadid=3: reacting to signal 3
    11-05 10:52:58.105: INFO/dalvikvm(3641): Wrote stack traces to '/data/anr/traces.txt'
    11-05 10:52:58.165: ERROR/ActivityManager(82): ANR in com.android.settings (com.android.settings/.deviceinfo.Memory)
    11-05 10:52:58.165: ERROR/ActivityManager(82): Reason: keyDispatchingTimedOut
    11-05 10:52:58.165: ERROR/ActivityManager(82): Load: 1.35 / 1.62 / 1.49
    11-05 10:52:58.165: ERROR/ActivityManager(82): CPU usage from 73238ms to 61ms ago:
    11-05 10:52:58.165: ERROR/ActivityManager(82): system_server: 4% = 3% user + 1% kernel / faults: 2960 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): om.metago.astro: 2% = 2% user + 0% kernel / faults: 24 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): akmd: 1% = 0% user + 1% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): d.process.acore: 0% = 0% user + 0% kernel / faults: 173 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): d.process.acore: 0% = 0% user + 0% kernel / faults: 144 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): zygote: 0% = 0% user + 0% kernel / faults: 336 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): d.apps.uploader: 0% = 0% user + 0% kernel / faults: 64 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): adbd: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): cOrganizer.lite: 0% = 0% user + 0% kernel / faults: 64 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): synaptics_wq: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): ksoftirqd/0: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): m.android.phone: 0% = 0% user + 0% kernel / faults: 22 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): usb_mass_storag: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): ds2784-battery: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): m.dasur.slideit: 0% = 0% user + 0% kernel / faults: 73 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): d.process.acore: 0% = 0% user + 0% kernel / faults: 41 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): logcat: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): droid.gallery3d: 0% = 0% user + 0% kernel / faults: 36 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): nie.geniewidget: 0% = 0% user + 0% kernel / faults: 11 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): nt.android.mail: 0% = 0% user + 0% kernel / faults: 30 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): le.android.talk: 0% = 0% user + 0% kernel / faults: 12 minor
    11-05 10:52:58.165: ERROR/ActivityManager(82): +ools.stockalert: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): +ndroid.settings: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): -ndroid.settings: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): -flush-31:0: 0% = 0% user + 0% kernel
    11-05 10:52:58.165: ERROR/ActivityManager(82): TOTAL: 11% = 8% user + 3% kernel + 0% irq
    11-05 10:52:58.185: INFO/dalvikvm(3495): Wrote stack traces to '/data/anr/traces.txt'

  7. #6
    Senior Member FlyingsCool's Avatar
    Join Date
    Feb 2010
    Posts
    369
    So what the heck is Blow Up Lite? Do you really need it? Sounds like problem solved.

    "Doc, every time I take a drink from my glass with a spoon in it, I get this pain in my eye" Doc: "Maybe you should consider taking the spoon out first?"

  8. #7
    Junior Member bjblackmore's Avatar
    Join Date
    Sep 2010
    Posts
    12
    Tried that, works OK until you reboot the phone, then none of the desktop icons load properly, and when you try to launch them it says 'could not launch selected activity', and you have to unmount then re-mount the SD card, or the SD card process hangs when you try to unmount.

    I received my brand new 8GB Class 6 MicroSD card in the post this morning, so I'm going to try that, formatting it first int he N1, then copying everything on to it via the N1 USB storage access, rather than removing it, and using a USB card reader in a PC!

    P.S. Blow Up Lite is a cool little game, based on physics, where you have to blow up a structre by planting TNT around it.

Remove Ads

http://www.scramblerducati.org/

Sponsored Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Search tags for this page

activity sd card and phone storage settings is not responding

,

activity settings (in application settings) is not responding. wont allow sd card to mount

,

activity storage settings is not responding

,
android sd card unable to launch app
,
android sd card won't unmount
,

android won't unmount sd card

,

can't unmount sd card android

,
inable to unmount sd card not highlighted
,
micro sd card won't unmount
,

sd card won't unmount

,

sd card wont unmount

,
unable to unmount sd card
,

unable to unmount sd card android

,
unable to unmount sd card on android phone
,
unmounting sd card on android kernel
Click on a term to search our sites for related topics.
Android Forum