So I have to reboot my Galaxy S about 10-20 times a day -- every day -- because it disappears all the time. I have an external card in there too - but that too goes missing.
Anyone know how to fix this ?
no one knows why this happens ?
no one has EVER had their SD card disappear randomly and have to reboot ?
I don't buy that.
Apparently the 51 viewers as of this post haven't had this problem.
I certainly haven't.
Maybe someone that has, will show up.
It's just super annoying
Funkadelick said:
It's just super annoying
Click to expand...
Click to collapse
Might help to know what firmware and apps you are running.
maybe you need to format the card inside the phone using the built in format app. Maybe you have a fake card. Maybe you have bad phone, in that case get it looked at
happened to me for a few days too.
Went uninstalling everything (tried a bunch of podcast/rss readers trying to find something that could handle passworded podcast feeds) as well as the games I was trying out and a few apps.
Hasn't happened since so one of them had to be the culprit.
- Completely vanilla sgs-i9000m from Bell, just unlocked. Not even rooted.
my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.
Before you do, you could try to root and check the logs for anything suspicious (logcat and kmesg). Also you could try to install custom ROM and see if the problem still exists.
If it doesn't help - you should contact HTC.
EErez said:
my stock nexus one becomes highly unstable after booting up. im running strock 2.2.1, and this issue started apearing recently (after 2.2.1 update). the phone has never had any problems in the past.
whenever i turn the phone on, if i touch it it becomes really laggy and freezes, requiring me to pull the battery. however, if i let it sit for 15-20 minutes and then play with it it works fine, until the next time i shut id down (which can be days). i have performed a factory reset without reinstalling all of my old applications, i have formatted my sd card, and i have checked all the applications that start on boot up, but none of them seam to be the issue (when there was nothing on the phone it still reacted this way)
any suggestions? should i contact htc? this is really annoying.
Click to expand...
Click to collapse
Factory reset with formatted card? Has to be something wrong with the phone.
Go to recovery, wipe cache and dalvik cache, and try to boot phone again, often that helps.
tried wiping everything i can through recovery, yet my phone still freezes soon after start up. any chance htc will fix this? i dont want a refurb
Because when system has just booted up, it needs to check SD card and mounts all App2SD applications.
Try to boot your phone without SD and SIM card, see if it solves the issue.
tried removing sim and microsd and all th possible combinations.
it runs great without the microsd, so im guessing that was the issue. ill try another microsd to make sure its not a hardware/software bug related to sds in general but rather an issue with my specific microsd (which isnt the stock one).
thanks for the suggestion. i was very close to sending my phone in to htc (already had a ticket open and a fedex label)
that sounds good perhaps your SD card was corrupted. Connect it to your computer using a card reader, and do a disk check in Windows, see if it can fix any problem. Also try to degragment your SD card.
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
So where do I start?
I rebooted my droid bionic, UNROOTED, pretty much stock.
When it booted back up, I noticed that some shortcuts on my home screen weren't working.
When I went to run them from the app draw, they weren't there either.
I seen this same problem on my D2G when I was running a class 10 SD card with apps saved to the SD card. The diffidence here though was that apps were saved to the internal storage vice the SD card.
When I went to manage apps, my hunch was correct. It was only affecting programs which were moved to the internal storage.
When rebooted again. It would affect other programs and sometimes even recognize the programs it failed to on the last boot.
I did a factory (hard) reset and that still didn't fix the issue.
I then brought the phone to Verizon and gave them a demonstration.
They then tried it on their phones in the store and came to the decision that this is something affection all droid bionics.
If anyone else is having this issue please feel free to come forward. There weren't any bug reports on this yet, so make sure you let your local store know to put it in their forums so this can be addressed quickly.
http://forum.xda-developers.com/showthread.php?t=1255778
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