Related
I have been using a class 2 16 GB SD card that I bought off play.com for a while now, and it worked perfectly in both my Hero and my N1, until recently. Since flashing Froyo, I have been having some issues, for example my mp3 files are not indexed in the music app, so nothing shows up, also my phone was freezing, both when I unplugged it from USB and at other random intervals.
So I decided to try another SD Card to see if it would clear up the music indexing problem. Since then, that has worked, and my N1 does not seem to have frozen at all.
Has anyone else had any issues like this, and could the SD card be causing my phone to freeze? (By freeze I mean it sits with whatever I was doing on the screen, but is completely unresponsive, and sometimes if I wake the phone it sits on the slide to unlock screen with the screen dimmed.
Thanks for any help.
I have a issue like this and I re-formated the the card and all worked for me. I again had the issue with another card I just took all data off the card and all worked so there was a file that had corrupted on the card. Hope this helps
That is definitely useful. Thank you.
Did your problem involve freezing at all?
I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.
nemethb said:
I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.
Click to expand...
Click to collapse
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.
dawgpound6985 said:
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.
Click to expand...
Click to collapse
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).
i believe this is also the cause of my sdcard corruption. ever since i installed froyo, i lost half the sdcard, and now i can't mount it in recovery.
i can't comment yet
still working
have over 400 apps installed
only around 400 MB free in the internal SD everything else consume by Apps and Maps
i keep changing apps frecuently, and installing updates as they appear on Android Market
I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.
Devhux said:
I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.
Click to expand...
Click to collapse
Sorry, but what? Let me get this straight, you tried voodoo lag fix, uninstalled immediately, and yet you still believe it is the lagfix that destroyed the SD card? You think that applying the lagfix mod somehow utterly destroys your SD card even though you've used it for an extremely short amount of time? If that's true then most root users would have bricked their vibrants already.
Seriously, that makes no sense. I stand by my theory that there's a bad batch of SD cards that went into the i9000m production. Bad SD batches happen all the time. Not something uncommon. On top of that, all Voodoo lagfix does is change the file system of the SD card. Would your hard drive die if you formatted it from ntfs to fat32? No. This is not mentioning there are quite a few vibrants that have not used lagfix with dead sd cards.
If it was purely a hardware failure of the flash chips, then it would make sense to have the failures occur randomly. As it is right now, most of the failures seem to happen when people flash the newer Froyo builds (or very soon afterwards).
As far as the lagfix is concerned, I'm by no means implying that this is the only cause of the failures, but if something is going wrong in the conversion of file systems (however minute it may be), it is possible for the file system to become corrupted over time.
I don't think we know for sure whether it's a hardware failure or a software one. This is made even more difficult by the fact that we are generally limited in what recovery options are made available (not like a desktop, where I could boot a Linux distro off a USB stick and directly access the file system to troubleshoot). I do realize some have been able to try and get utilities like GParted to run on the phone's internal memory, but it's still not nearly as convenient as running the same utility on a desktop HDD/SSD.
Feel free to disagree with me, but I know once I get my phone back, I won't be installing a lagfix (or a custom build for that matter).
Hmm.. So i9000m's had a bad batch of memory? interesting. I'll remember that when someone comes asking for problems and see if their device is a i9000m , BTW what is the i9000m ? Captivate?
i9000m = Canada Bell Mobility version of Samsung vibrant
i9000 = international version
nemethb said:
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).
Click to expand...
Click to collapse
I missed this post completely. People are having some MAJOR confirmation bias for WHY the i9000m dying.
Just because you do something, it doesn't always imply causation. There are plenty of vibrants around with dead SDs without ever installing lagfix or froyo. It's purely coincidence, because the SD was going to fail anyway.
Actually, I don't think there is enough evidence to come to any conclusion regardless.. But there is no evidence proving that the lagfix cannot be part of the problem, or no reliable proof. especially since nobody totally understands how the internal hardware works on this phone though. In fact, the "evidence" that wear leveling happens on the hardware controller is based solely on the sentence "computer SSD's do it that way" (ie, no evidence). And a lot of other evidence related to other problems i'm seeing is also based on assumption.
1) First isolate if the problem is faulty hardware or simply a formatting issue..
2) Work out what ROM's and such people were using
3) Work out if they were using a lagfix.
4) CONFIRM that the internal SD is actually dead. Many people here jump to conclusions too quickly.
5) Also, work out if there is an easy way to get "batch numbers".. Maybe it's isolated to a specific hardware batch.
i was on official jh2 rom from bell w/ voodoo lagfix. Never attempted flashing another rom. I noticed one time it crashed so i pulled the battery for an hour and that had fixed the issue (or so i thought). Was working for about a day and it crashed again. Out of desperation i tried flashing other roms like froyo. So the way i see it, its either general faulty hardware or the lagfix...not flashing froyo builds.
My i9000M had never crashed until soon after installing the JPK firmware, and in my case one crash was enough to "break" the SD Card. Again though, the fact it only crashed when I installed Froyo does not mean this was the cause.
Hopefully we can figure it out, because between the 3-button recovery mode issue and this, I'm considering getting another Android device instead.
I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App
I started thinking the same thing actually. Mine did have the 3 button recovery issue as well, and of course I had patched it (using the official Samsung Canada JH2 re-release).
MaestroSeven said:
I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
3 button was working on mine. But I have seen reports on here from people with the same issue where 3 button was not working..
Sent from my GT-I9000M using XDA App
3 button was also working on mine. Like the others, JPK booted correctly but I was getting force errors due to me upgrading from Eclair. Then I decided to wipe/factory reset and it was a no go from then on.
I hope we can figure this out. There has to be a way to get to the internal SDCard and repair it properly.
I have the T-Mobile US Vibrant and I noticed some weird problems with my internal storage too. I have only rooted and lagfixed my phone. I noticed it was taking longer and longer to open photos in my gallery and sometimes they don't open at all. Sometimes the phone will not mount as a storage device on my laptop. In the past 4 days, my phone has crashed hard twice. The first time I had to boot into recovery and wipe personal data and download all my apps and set my email accounts again. This morning my phone lost all the contacts from Facebook, Touchdown (Exchange) and Gmail.
This JUST happened to me like, 5 minutes ago. I browse these forums every day and I had never seen any warnings with regards to Froyo screwing up internal sd cards. It seems many of these cases are Froyo related. Now I probably have to take my phone back.
Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.
Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny
Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks
Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny
Maybe a factory reset (do it in recovery) would help?
I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.
@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?
2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G
UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.
sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)
tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))
I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App
Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App
Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.
related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.
gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine
More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G
have had the device now about 7 months and last week it started randomly freezing and the home button and the 2 capactive buttons didnt work, had to pull the battery to get ti to start and it did it again about 20 minutes later, took out the sd card and it seemed fine for the next few hours use. Now a week later it is happening more and more frequently alot of the time it is freezing on media scanning, it will freeze on usb and sd card so it makes me wonder whether it was the sd card afterall
things i've done :
swapped roms, ive tried stock LC2, stock LC1 both deodexed versions and as a test put darky rom 3.3 earlier and it did it then, mainly when scanning and also once when trying to hook the phone up via the usb cable to transfer files.....have wiped and fomatted the sd card, the internal usb memory is next but id rather leave that as alast resort issue
im running go launcher but that shouldn't really affect the media scanning part and it freezing, the odd thing about a freeze the other night was that i couldnt get the home button or other buttons to work but the youtube video was still playing without any problems, figure that one out!
im thinking it could be that the internal memory is going faulty, is there a way to test bad blocks on the device?
Richy99 said:
have had the device now about 7 months and last week it started randomly freezing and the home button and the 2 capactive buttons didnt work, had to pull the battery to get ti to start and it did it again about 20 minutes later, took out the sd card and it seemed fine for the next few hours use. Now a week later it is happening more and more frequently alot of the time it is freezing on media scanning, it will freeze on usb and sd card so it makes me wonder whether it was the sd card afterall
things i've done :
swapped roms, ive tried stock LC2, stock LC1 both deodexed versions and as a test put darky rom 3.3 earlier and it did it then, mainly when scanning and also once when trying to hook the phone up via the usb cable to transfer files.....have wiped and fomatted the sd card, the internal usb memory is next but id rather leave that as alast resort issue
im running go launcher but that shouldn't really affect the media scanning part and it freezing, the odd thing about a freeze the other night was that i couldnt get the home button or other buttons to work but the youtube video was still playing without any problems, figure that one out!
im thinking it could be that the internal memory is going faulty, is there a way to test bad blocks on the device?
Click to expand...
Click to collapse
What rom were you on originally?
Sent from my GT-N7000 using xda premium
ive tracked it down to it either being go launcher or some anomaly with other go apps as currently on darky iced 3.3 and using the tw interface not a single freeze
was lc2 rooted, started when i went back to lc1, but it was probably something that go updated and started causing it
Richy99 said:
ive tracked it down to it either being go launcher or some anomaly with other go apps as currently on darky iced 3.3 and using the tw interface not a single freeze
was lc2 rooted, started when i went back to lc1, but it was probably something that go updated and started causing it
Click to expand...
Click to collapse
Good to know.
Sent from my GT-N7000 using xda premium
ok scrap that, just had a freeze after deleting a backup from the sd card
Try this eMMC check app from Gplay to see if it give any clues about memory chip condition.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Alright guys this forum is pretty kickass and I was just wondering if anyone else could give me some insight to these weird quirks my Moto Droid4 is giving me.
Issues:
-Many apps that need to access SD card don't save properly i.e. TB gives insufficient storage error on scheduled backups, sometimes photos don't save correctly
-^^ Also related is sometimes when trying to connect as "Mass Storage Mode" via USB to my computer the device will lock up or when I try to write files to the SD card the transfer will lock up and the phone becomes almost unresonsive
-SD card and writing to the card becomes fickle if I ever mount and unmount, to the point where sometimes it won't mount until I reboot the phone
-Sometimes the phone will just become unresponsive altogether and exhibits periods where it will turn on the softkeys but the screen won't turn on. Hitting the hold button then ends up just toggling the softkeys.
I've tried:
-3 Different Roms now, all JB. Two different 4.2.1 and one 4.1
-Checking the SD Card with windows built-in disk checker and sector fixer. Everything "Passed"
-Turning off all CPU overclocking components and apps.
-Making sure newest Busybox and SU app is up to date and allowing all apps.
I think its the SD card but I don't see how the phone not turning its screen on or becoming sluggish could pertain to that.
Thoughts?
Thanks in advance guys :fingers-crossed:
Have you tried to back up all data of the SD card format the card put data back on and try again... my wife's RAZR did this and that fixed it...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
Have you tried to back up all data of the SD card format the card put data back on and try again... my wife's RAZR did this and that fixed it...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
I believe I have, but I will do it again as soon as I'm done with the Disk Checking for the 3rd time. Will post results
Completely nuked my internal storage and SD card, by formatting. It still does lockup everyone now and then and by that I mean it will blink a notification, and sometimes turn on the softkeys when I go to hit the hold button but the screen never comes on. sometimes the softkeys respond to me hitting hold and they go on and off but the screen won't it requires a reboot to fix. Is it the phone at this point?
Changed to a different SD card same model same brand and class and since then I have not experienced any of these problems. And I can rule out bad files on the card because I copied over everything from the other card straight to this one. Its been about 5 days with not one problem. I will give it 10 before I call it.