Database Develop

G1 not working very well anymore?

okay, so i've had my G1 for about a year. i have played around with it a lot and as recently as a month or so it has been very snappy and responsive with SuperD rom as well as older (4.x) Cyanogen roms. i have flashed cyanogen 5 test-something (-2 maybe?) and didn't really like it, so i tried a couple of the other newer roms. now, it seems like no matter what rom i flash, it has serious lag and responsiveness problems. i have done complete wipes (partitioning the SD card to fat/fat32 only, wiping it completely with a disk wiping utility, re-partitioning with amon ra recovery, and wiping from amon ra recovery), i have installed both new and old roms, i have flashed old and new radios (i have had danger spl for a while), and nothing seems to help! i am getting the HTC Evo on Friday so i guess this doesnt really matter that much, but i am concerned that other people might be having this problem and if i give this phone to a family member or friend i would like it to be functioning as smoothly as possible. it seems like since my hardware hasnt changed, i should be able to wipe, flash my old setup and have nice snappy response time like i had before. right now it's like i open the web browser and load a page and then press the home hardware key and it takes about 5 seconds for the homescreen to load, even though all i have is four icons, the default background, and the power control widget. there used to be no lag at all with this same configuration (an older Super D rom). any suggestions?

i'll just say amen to that. my G1 just isn't what it used to be anymore. I just recently did a complete wipe including completely clearing and repartitioning the SD card and I didn't even bother reinstalling all my apps, i'm just reinstalling them as I find I need them... don't have a lot of widgets... things just aren't what they used to be anymore. i wish i could figure out why. and i'm in contract until NEXT july... so i'm gonna have to figure this out sooner than later.

Same here, but it got a lot faster as soon as I added overclock and removed beautiful widgets!

Agree with the others posted. I do not use beautiful widgets. So that was not the issue with me.
I have also noticed that my internet speeds with t-mobile have dropped in half for the last few months. They (t-mobile) do not provide any real help on that issue. I remember back in '08 a post being made that they will put people on low internet if they exceed the 1Gig download in a month. Has anyone every ran into that one?

I'm not that tech savvy or anything, but you guys do know that just about everything you flash to your phone says "Caution not responsible this will put your phone under major stress... wear and tear... blah blah blah"...
Mine did the exact same thing. I always just assumed that after trying to push it to it's very limit for so long it finally just gave up and couldnt go that far anymore.

This is true. My G1 is having weird problems. I have overclocked before, but not anymore. I think these problems started after I overclocked, or after I flashed the latest radio for the G1.
Developers just write that their ROMs will put the phone under stress just to warn people that their not at fault for their phone screwing up miserably somehow (like with the catastrophic Haykuro SPL... oooo ****, what a mess that was)
When the Haykuro SPL came out, I didn't immediately flash, even though I had the required radio already. I made a few posts in XDA verifying the steps so that I wouldn't **** my G1.
And clocking the G1 to 528 Mhz ISN'T OVERCLOCKING.... the processor was made to go up to that spec, HTC just kept the maximum clock in Android to 384 Mhz to save battery and prevent complaining customers.
The G1 should be able to write it's NAND over a thousand times... it's a flash memory chip, it was made for read/write. It won't get slower unless you really screw the crap out of it, for example, by applying more voltage to the damn thing.
Maybe I should re-flash the radio, the SPL, and erase and flash the recovery and everything else. Or maybe return it to complete stock and bring it back to rooted-ness... that can solve some small little mistake I possible made a while back, in the first months of G1 rooting...

AustinAce said:
Same here, but it got a lot faster as soon as I added overclock and removed beautiful widgets!
Click to expand...
Click to collapse
Overclocking is great
But the G1 should still have the same performance as it did when it was manufactured. The CPU is the same, everything is the same. I don't know why it seems like the G1's performance is diminishing... maybe it's just our exposure to superior Android phones like the Motorola Droid or Nexus One?

For all of those that are complaining about their slow G1 devices on Cyan's 5.0.7 turn off swap and compcache. Confirm it with adb shell and type "free" to confirm that it's reading 0 for swap. Adjustments have been made so that you shouldn't need it anymore. Cyan has said himself that you would be digging a "swap grave" if you did. Also, I find it funny how a lot of people b!tch that the G1 won't be upgraded beyond Donut but clearly we can all see why. My suggestion is to turn off swap and compcache. Not good enough? Go back to stock or whatever you were happy with and stop complaining!
For the record I (like thousands of others) have 5.0.7 on my G1 (without swap or compcache) and it's been running fine. Overclocked and all. Using ADW Launcher with 7 screens filled with widgets and shortcuts. I was running it for 3 days straight with heavy usage before it rebooted on me. So I think that it's something that you're doing.

Everytime my G1 has acted up and no amount of recovery and sd card wiping seemed to help. What did help me out though was wiping from fastboot using the
fastboot erase boot
fastboot erase cache
fastboot erase userdata
fastboot erase system
commands. This will wipe everything in the phone (outside of the sd card).
It should actually perform the same wipe functions as the recovery program does, but I have had luck with this in the past.
BTW, I fried one of my older G1s overclocking it when Cyanogens roms first came on the scene. It just became completely unstable and would shut off randomly and frequently. Unless you've done some hardware damage due to stress or clumsiness, your G1 should be rock solid as Binary says.

Why does my G1 seem to get slower and slower
T-mobile G1 32B Bronze "PVT Dream"
Extended Life Battery and Cover
16 GB Class 6 Card, ext4 1024MB, linux-swap 512MB, remainder fat32, No Compcache, Apps2SD - "before GAPPS"
Cannon202 2.2.1 build, 2.1 firmware, 2.22.23.02, Tried w/wo cpu oc app and Cannon's original build is Superior, would not rec installing oc app at all. The clocking used in this builds kernel is smoking fast, yet made to be unstable imo in my tests against this build with the cpu overclocking app, customizable yet much slower, flakier, and noticeably unfavorable temp increase just holding it ...
My G1 is smoking fast, Great Signal Strength, Excellent wifi and 3G speeds. Things I've noticed in my journey into the "Custom Rom Universe."
1. All it takes is one file,app, or architectural flaw (ext234,Linux-swap,corrupted partitions, faulty cache etc...) - even slight - to destroy the Harmonious bond between software and hardware on any device.
2. Most new phones are coming with Class 2 removable storage from the OEM. A Class 4 card may suffice, but a Class 6 Card is mandatory. If there were faster I would say go even faster on the transfer rate. depending on the application, the Android OS will bounce to and from the SD Card a bunch and more often as more apps are installed (updates), cache, partitions, etc the faster the card the less the phone has to compensate against the slower transfer rates, thus better performance ...
3. Heat/Battery - I tied these together why? Heat from Over-clocking or even just Summer weather or the combination of the 2, kills batteries overall life and output. Not to mention the affect on all electronics from heat, the cooler the better I would assume. If your phone has a custom Rom another factor to take in consideration is the it's going to require more juice from the battery and the change in the amount of load across the board on the phone as it does any pc/mac or any other form of computing device is pull more power which can weaken, damage, or even kill the battery all together. It's amazing how much the integrity of the battery affects the overall performance.
("IMO") - I just thought I might add my 2 cents. The performance on my phone is outstanding and very stable and I have changed the architecture so many times ... I would be embarrassed and damn near ashamed to venture a guess and disclose that information . So like it says "In my opinion" it's alright to disagree . The point is to argue, not to be argumentative , but I thought this information might help someone. Sorry for the long post.

Have you tried putting a new class 6 MicroSD card in? That might be the problem. SD cards only last so long.

[Q] Problems with Nookie Froyo and CM7

like namely, neither one will boot.
Grabed the Nookie Froyo boot image, wrote it onto a card (8Gig AData Class 6 card) with my linux box then watched as whole lot of nothing happened.
Saw a "Loading..." screen for a bit then "ANDROID.." and it stops there.
Somewhat similar problem with CM7. The installer version never could finish. Froze just past the mkfs the first time, second time got past the extract process, third time it said it made it and to restart. Never made it past that and actually booted.
Found a pre-done CM7 image, just sat at the logo screen for a long time before I shut it off. (like ~15 minutes)
The honeycomb preview image I found also didn't work...
I've tried both ones I have avaliable right now. (they're both identical from a different (failed) project involving a PSP and a Mem Stick Pro Duo adapter)
Technically I do have a 4Gig Class 4 in my MP3 player but i'd rather avoid using it. (it's near full right now and i'd have to copy everything off of it)
Right now i'm just wondering what's going on?

ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.

Fnord12 said:
ok, just tried the Kingston 4gb class 4 card
Used the win32 disk imager program to write the nookie froyo image to the sd card.
Works fine, if a bit sluggish (class 4 card, ~15MB/sec read, ~5-6 writes, what do I expect here)
so i'll make an assumption that the Adata cards aren't suitable for use? Really sucks if this is true, was hoping to avoid spending any more money on this.
Now my only problem is that SoftKeys is misbehaving "Unable to execute as root"
Should I just tough it out on 2.1 until the "official" 2.2 or CM7 comes out? (heard something about how sleep is broken)
Sorta sucks a little as there's a 2.2 only app I rather wanted to run.
Click to expand...
Click to collapse
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything

johnmagoo said:
Is softkeys the only app that cant get root privileges? I guess you could try to fix permisions in rom manager, it wont hurt anything
Click to expand...
Click to collapse
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.

Fnord12 said:
I didn't play around with it much given it's somewhat sluggishness. I did see the superuser prompt for softkeys but it apparently didn't work. Not sure what you mean by "rom manager" though?
Am getting ready to try out CM7 RC4 though. Wondering what that's like. Launcher Pro on 2.1 is nice-ish but it's clearly made for a phone given the wide spacing between buttons on the NC's screen.
Click to expand...
Click to collapse
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.

johnmagoo said:
Rom Manager is in settings, its part of CWM for flashing roms and stuff.
I am personally running Nookie Comb with no problems. For me it runs super smooth, wireless does not loop, and all my apps work just fine. I think I will probably switch to CM7 once the actual release is out, I am just having a really hard time switching to it now because Nookie Comb is working flawlessly for me.
Click to expand...
Click to collapse
Well, so far CM7 is running better off the card than Nookie Froyo did.
app downloads are slow as hell though, no clue why.
once CM7 is out and if the odd wireless issue is solved then I may install it to the internal memory.

[Q/Problem] Seems to happen with Every Rom.

I would like to keep this short and sweet so...
Basically heres the low down: I got a G1 almost a year ago, got into Rooting/flashing 7 months ago. I noticed in the beginning almost every rom was giving me a problem, Freezing up, hanging for long periods of time, etc. I eventually found a very nice, stable rom thats been lasting me for about 6 months but as of late was being horrible. Force Closing everytime I got a text message, REALLY Hanging for long periods of time, freezing up. Etc.
So I finally got FED UP, and decide it was time for a change, so I grabbed MLIGN 3.3v having seen so many good reviews and what not, thinking it would be the remedy to my poison. I cried. So in short, here is whats going on:
1. It seems to only wanna cooperate when Plugged into the USB, which, isn't too practical.
2. When not plugged in, it is NOT sluggish, but when loading into apps I've noticed it will hang for quiet awhile or completely lock up to the point only popping out the battery will work.
3. I haven't noticed it yet, but on the old ROM it would randomly shut off during phone calls; which leads me too....
4. When ever I shut the screen off (by pushing endcall) it seems to freeze and lock up and eventually either SHUTOFF or REBOOT into a SHUTOFF of the phone and refuse to turn back on until it has been plugged into the USB, or enough time has passed for it to 'forgive me' and by that, I mean randomly work again.
5: Various other things I cant think of right now.
So, basically thats almost everything. Whenever its plugged into USB though, it works like a charm (for the most part).
Would a problem with my Battery be the case? Which, would be awkward but a possibility.
Or did I just do something wrong?
I made sure to factory wipe the phone twice, even 3 times on the last go, I updated the ENG.SPL and Radio every time I tried to reflash just to make sure.
I partitioned my SD Card for 32MB Swap; 512EXT2 (and 7xxEXT2 I forget what it was) and I also upgraded it to EXT3, which showed some improvement... I believe.
So, I just would like to have my phone working, in a peaceful, obedient manner xD.
Forgive me for the block of text, and all help will be appreciated. Thank you guys... I await sound advice

Try different ROM? See which one works best.
Like me, I found that SuperAosp is best suit for me (see my sig for DEV Site and Download, if you want to try it). It had been running fast and I had no issue, what so ever. Occasionally when I loaded apps that hogged the power usage it gets lags, but still good. FCs are at minimal to none (that's just because of the way I handle the apps). Once in a while I noticed that it reboot, when I tried to use the apps that hogged the memory (maybe that was the apps issue).
Only other thing I recommed is to download a different launcher, because the build-in ADW Launcher does not work too well in my opinion.
Another thing, if you wish to keep the ROM you had. I would suggest to change the partition size. (IE: Catch [128MB]/Ext 2 or EXT 3 [1024MB]/ FAT32[the rest]) Now I know other people might say that it's overkill, but to me my G1 performance it great.

I've tried multiple roms as of late, and the one I like the most does happen to be MLIGNs... everything seems to be working correctly for the most part with the exception of what I listed above... Now on the like, 23rd reboot most of the sluggishness that was there before is gone, and everything is pretty much being cooperative, with the exception of like the weather, which isn't updating properly but I can live with that. What I cant live with is the fact that this ROM when not plugged in, will freeze up when in the lock screen, a few minutes after it has darkened and gone black and wont respond at all. Or I'll unplug it and just do a test, swipe left, right for a good minute or two, go into apps and It'll just SHUT OFF. Maybe it really is the battery? I'm unsure. When I look at the battery it does look quiet bloated... I am unsure...
I'm gonna try to set it to what you recommended, and see if that works...

I don't think it's the battery.
Have you tried reformat/partion your SD card (be sure to backup your data first). See my last comment on sizes recommendation for each partition.
Also check on the swappiness setting.

Mhm... so I went back and followed everything you told me to do, including repartitioning to the exact file sizes you told me. (Also I'm guessing Cache meant Swap) So I set everything up and its really blazing fast and stable.... until I remove the USB cord. Then it shuts off, freezes at lock screen when the screen is dimmed to black, and will just randomly shut off while doing things (especially when trying to get into messages)
Also if it helps, I have a Class 2 8Gig SD card, and my Recovery is Ra 1.5.x(I forget.) I'm completely confused... I dunno what to do... I would really like this to just work and stop being a hassle D:

Hmmm, Try reading this thread, http://forum.xda-developers.com/showthread.php?t=1010932
See if it helps.

Nothing :/ Its okay... I'm gonna go play around with other roms, completely re do my phone, make sure everything is updated etc. Then go from there.
Thank you anyways, you were a big help, reguardless of my phones triumphing retardism

[Q] Phone freezes randomly / needs hard reboot - 2.3.3 and 2.3.4 custom ROM's

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

[Q] I rooted Captivate w/Froyo 2.2 - Now lots of problems

I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T

My vote is to go with a custom ROM. It will solve all of these problems. Cognition is the most similar to stock and is quite easy to flash. As for the problems you are having, I don't know what to tell you.
Try Cognition 4.5.3. You won't be disappointed.

Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?

Well, not busy tonight. Watching pre-season football.
Flashing a Froyo rom is not too bad. Since you have stock 2.2 it will be a little more tricky than if you were still on 2.1.
First, what is your build number? look on the sticker under your battery to see a four digit number beginning with either 10 or 11.
I will private message you with more.

taltal13 said:
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Click to expand...
Click to collapse
Make sure you READ EVERY LINE OF THE OP. When you think you got it, read it again, then give it a shot. For the time being just factory reset your phone, should clear up some of your issues. Good luck
sent from long ago, in a Galaxy far, far away.

^^^ he's right. READ, READ, READ... until you're sick of it. It will pay off and keep you from bricking. Sorry I didn't mention that. But I will be glad to help you if you need.

and if (or when) you manage to brick it do not panic,, go back and read some more,, seems that almost everything an idiot like me can do is fixable,, and most normal people are pretty safe,, they are not going to kill their phone,,,,if they read and follow instructions,,,not doing those two have found my phone in some pretty unresponsive states,, but I am running mosaic VI now and loving it,,but have been on so many I had to go look,,and have finally I hope learned the value of reading ( and those other people probably do know more than me so I should not think I know better ,,,yet)

taltal13 said:
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
Click to expand...
Click to collapse
Not sure how much of knowledge you have gained before doing these attempts of changing some values to enable side-loading...
I would suggest to do factory reset since you are still on FROYO and see if this does the magic.
If it gets locked back to AT&T, I suggest just talk to AT&T rep to unlock & side-enabling. Once all is well, you can do rooting as you did before. Hope this helps to solve your problem.
For any other help, we have XDA here and get some time to go through forums. As others suggested, please read, understand and act.

A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal

taltal13 said:
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
Click to expand...
Click to collapse
Just for a bit of encouragement ive been using Cognition 4.5.3 as my daily driver for the past 4-5 months and have never had a single issue with great battery life. Ive tried numerous other roms on this forum and always have run into a boot loop, force close, or other random issue that makes my phone unstable but with Cognition I experience what my phone was meant to be like.