yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Not fixed. It started doing it again yesterday, and so far today it's frozen up twice already. I'm switching to another GB ROM and if that doesn't do it I'll go back to Froyo.

I can even tell when it's about to happen because the phone starts to get these little lag spikes. And even changing pages in the Kindle app is sometimes very jerky.

This is f**ing annoying as hell.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Shoot!

I went back to Froyo also (Darky 9.5). I was just downloading gingerreal to try GB again but now I am hesitant.

Froyo though is no problem at all without any reformat or disk scanning of the problem SD card (mine is 32gb, class 4).

It is annoying as hell but man is the power management better in GB than Froyo. Otherwise I would stick with Froyo but right now I am lasting about 12-14 hours (albeit I have my knock off battery in right now as I forgot the stock in the wall charger at work). I would get at least 24 in GB.

Sigh... Let us know how it goes. I think this must be driving some others nuts too. And your right about the warning signs. First its lags, then freezing.

Still think that faster media scanner might have had something to do with it.

BTW when I flashed froyo I had to do it like a dozen times as I kept getting the can't mount dev/block/st110 error on my stock roms (i9000m) and boot loops on others. Still can't seem to get into 3 button recovery (download was fine) but I can get there from SGS tools and extended power menu so haven't tried that hard.

Leads me to think that the internal memory was also corrupted by whatever did the external SD. Of course I have the i9000m which has an internal SD that just likes to fry (this is my second handset) so it could have been that too.

Not much help for troubleshooting am I!

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Yes I'm convinced it has something to do with the SD storage. I'm on Criskelo ROM at the moment because like you, I'm really happy with the battery life on GB, and wanted to stick with it. Cris's ROM is currently based on 2.3.4 and let me tell you, it's *FAST*. Way faster than darky's. And it has awesome animations. I'm not a big fan of some of the visual customizations (some of the icons) Cris did, but in general it's very nice. If it proves stable after 5 days I'm definitely sticking with it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Keep us posted. I'll even spring for another (smaller 16gb) card if I thought that would work. Still no issues on froyo.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
BTW Is that Criskelo rom jvq?

Just wondering if the root problem might get addressed in one on the stock roms as it obviously isn't an issue in froyo.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
No, it's jvp. And I have a 16gb sd card, and it's not that (its size, I mean). Because one of the times I was testing this, I had the sd card out for several days until it started freezing again. One thing is for sure, it seems this is a bug that starts degrading the storage over 4-5 days and that's when it starts giving problems. So until I hit the 5 day mark with Criskelo's ROM I won't be satisfied that it's fixed.

I'll let you all know how it goes.
[Galaxy S I9000 Q&A, Help & Troubleshooting] agent86:
I am getting the freezing problem on 9.5 black screen but if hold power down for long press it reboots. 9.5 has been great so I have stuck with it until now. It works fine for about 5 - 10 hours. Never seen it freeze or slow down while actually using it. Any clues as this ROM seems to work reliably for most people.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Well this thread is for gb issues but maybe you have a kernel that is underclocking when on standby?

I think I've read that can cause issues when waking up. Otherwise maybe try a reflash?

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Quick update:

5 days in (yesterday) phone locked up twice already. This problem is so rare that none of the ROM developers have any clue it even exists, so no way to be sure if it's related to the SD. I'm giving it a few more days and then I'll give up and go back to Froyo, which although it's not as fast, at least it's stable.

yes, pressing the power button forces a reboot but that's just ridiculous. I want stable and reliable more than i want flashy and nice.

I wish some of the developers could give some hints on how to debug using adb. I'd be more than willing to plug it in, get in with db and check what processes are stuck. I used to use Linux so I can use the commands...just need to know what to look for and how.

EDIT: Can you guys post which kernel you're running? In fact, please write:

- What kernel (who made it, version)

- Lagfix status (don't think it's the cause but just need to establish if there's a pattern)

- If you have BLN on or off

I'll start:

Kernel Dark Core 2.7.1

No lagfix enabled (RFS compatibility)

BLN support in kernel but not active
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
I was on darkcore kernel with gingerreal and dark 10.1 but I don't recall what kernel I had in F1. Likely what ever it was packaged with.

Usually ext4.

Never used BLN.

Froyo Darky 9.5 still chugging along. Some reboots when toggling wifi or bluetooth but I am sure that is unrelated.

But now I want skype 2 with video which is gb only! Might try again on the weekend.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Well I'm reinstalling stock GB. Only modification will be CF-Root's kernel. I might put in Voodoo since it is the closest one to stock there is. If on stock GB everything goes nicely, I'll then flash in Darky's or Criskelo's with a different kernel than Dark Core. I'll let you know what happens, but you'll have to wait for 5 days :rolleyes:
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
I am seeing some similar reports on some of the rom pages too so I think it's starting to happen to a few more people now. I'll wait patiently...

Thanks

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Really? That's good news, sorta.... can you tell me which ones? I've got *yet* another theory and I'd like to see what's common with those ROM's.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sundazetoo:
@ferparedes I tried the "F1 Galaxy S2 V6" ROM and that seem to have bugs and was not as smooth.

So I went back to Darky's 10.1 but when I flashed the zip via CWM I got into a boot loop. Anyways I realised that theres 2 version of Darky's 10.1 one for CWM and one for ODIN. I tried the ODIN version because of the boot loop and it flashed fine, and I noticed that it seems cleaner as there's minor tweaks and less bloatware (mind you there's a few missing Samsung apps that I use). After missing some samsung apps like AllShare I reflashed via CWM and it worked this time.

I would recommend that you try Darky's 10.1 Resurrection (ODIN) http://www.darkyrom.com/community/index.php?threads/odin-darkys-resurrection-edition-10-1-gt-i9000-only-for-now.3237/

Darkys 10.1 Extreme Edition JVH

Kernel: Dark Core 2.4

Not sure about BLN as I don't have any settings in CWM.

Voodoo Enabled
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Can't recall. I follow gingerreal most often but it might have been juwes or &F1.

What's your theory?
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
The Dark Core kernel. It's the same one that's included in Darkys, Criskelo and F1 roms. And from reading Darky's forums they are in the beta section and considered "unstable" .

So this is what I'm going to do:

Right now I'm running stock JVP (except for CF-root for root)

If it goes OK for more than 5 days I'll flash Voodoo's kernel. Test for another 5 days.

After that I'll flash either Criskelo or Darky but keeping the voodoo kernel. If that goes well, then it will definitely supercurio's kernel.

What do you think?
[Galaxy S I9000 Q&A, Help & Troubleshooting] hansjeg:
Happens on repaired SGS with stock XWJVH as well...

My Samsung Galaxy S has been repaired. Actually, it's brand new now with a new main board in it. The repair center put XWJVH on it and as the reason for having it repaired had to do with me flashing all the time (lost my IMEI :eek:), I decided to stick with stock ROM for a while and see how it goes. After a couple of days, it froze for the first time and I had to remove the battery. When it happened again after a few more days, I did a factory reset and installed all apps I frequently use again, but this time I left out 'suspicious' software like LauncherPro and WidgetLocker. So here I am: basically a new SGS with stock XWJVH and TouchWiz, only a few apps on it, all massively downloaded stuff from the market, and yesterday, only two days after factory reset, my phone hung again. Where the first two times it happened when I was using it, yesterday it just happened when it was in my pocket. It was extremely hot, it didn't respond at all and again I had to remove the battery to be able to boot it again.

So, don't blame any of the custom ROM's or kernels. I guess this is something in Samsung's 2.3.3 firmware. And I would gladly know what so that I can deal with it...!

Hans.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
That's interesting. Although mine has never frozen "on it's own" like yours. Its always when doing something, giving it some input that it freezes. Also,mine has never gotten hot at all. In fact, after it freezes I've left it there for up to 15 minutes and its never gotten hot at all. I don't think its the same problem, but we'll see after 4 more days.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Hmmm seems my Darky 9.5 still likes to blow up every 2 weeks or so... had wipe and reflash and restore.... how's the stock and cf root combo going?
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
I'm afraid I don't have great news. It's frozen twice already, didn't even make it to the 5 day mark! I'm going back to one of Criskelo's Froyo-based ROM's today.

What about yours? Is the behavior the same as with the GB ROMs?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Oh no. Its way worse and way less often and affects the internal sd. Basically I get a soft reboot and force close for all user apps.

Its weird though as everything seems to be on the user portion. It like one of the partitions where user apps are stored unmounts but I don't know enough Linux to fix it or confirm that.

Too bad about gb not working might try insanity froyo now.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
What you're describing sounds like a different problem from what we're experiencing with the GB build. I just hope it's not that our phones are nuked (their nvram or something).

I'm flashing Froyo tonight and crossing my fingers everything will go back to normal. When GB 2.3.5 or something comes out I might try that again.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Well I always worry because I have the infamous i9000m which had a bad run of motherboards. But this happened even once it was repaired. I might try a stock rom with a rooted kernel to see if that helps but when it only happens every 2 weeks to a month you kind of forget how much it sucks.

Let me know of you do get similar but I doubt it.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] mission92:
It's the Tw4 Issues. I'm sure that now Tw4 is not stable in i9000.

I tried many roms and kernel have the same issues.

The more apps you have installed, the easier it freezes. Especially palying huge games like PvZ and Asphalt 6.

So you should change back to Tw3 or try another launcher.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Hawkeye3:
Just to chime in here: I get this with the standard ROM. No launcher modifications, no lagfixes, ... the only mod is that I rooted the phone. Not sure if I had the problem in 2.3.3 but both 2.3.4 ROMs have had it. It happens most frequently when I use search (to find and launch an app) or run Google Maps.

The phone does sometimes recover from a hang (after several minutes) but usually I end up having to hold the power button to force a reboot.

I have not tried formatting internal or external storage, but from what I'm reading here I have little hope that that fixes anything anyway. This looks to be a bug in the stock ROM, and everybody else is inheriting it from there.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
It's not TW4. I've never used TW4 and it's not included in the stock ROM.

I'm back on Froyo, Darky 9.5 to be exact. Running fine, third day.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Yup, that seems to be the case. Apparently something wrong with Samsung's GB build and *some* phones only. That's a reason why I have little hope that they will fix it at all.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Yeah I thought about going to cm7 and still might but last nights attempt did not go so well.

Lost imei (temp just in cm7) abd ext sd not recognized properly. Camera also looked horrid though it was 3am in low light....

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lunchbox115:
Let me guess: you did not have Froyo before installing?

Sent from hell to take your soul
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
No, I was on Froyo. Darky 9.3, to be exact.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
I think he was asking me regarding CM7 install issues. But yes I did go back to Froyo several times... I have a post in q/a that outlines what I did and how I might change it.

Though now that I remember TV out is not supported in CM7 I am less interested (as my kids are watching a feed right now on the TV while I am on vacation - its useful for that!).

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Just a quick update. 4 days now since going back to Froyo and the phone's rock solid, so far. No slow downs, no hiccups and no lag.

Battery life is maybe 90% of what it was with Gingerbread and the phone is almost as fast (with ext4 lagfix).

I'm going to miss having access to the new ROMs, new themes and such but at least I'll have a stable phone. When 2.3.5 comes out I'll try that again.

If phone starts with an attitude again I'll let you know. If not, then you were right in that it is something with Samsung's GB build.

BTW I installed Darky 9.5.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lunchbox115:
Exactly, most problems come from flashing CM7 directly from Gingerbread. ;)

Sent from hell to take your soul
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
@gfacer - How's your phone doing so far? Is it finally stable on Froyo?

Mine is still ticking away fine, now on the 5th day. Installed a Gingerbread modem (XXJVE) and battery life is pretty good.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Well I've gone back to stock rom 2.2 (the latest for Canada) with only a custom kernel. Tired of rebuilding my homepages and lack of sleep in general. Also apparently Canada will be getting a specific GB build shortly so I'll try that when it comes. Then at least I can blame Samsung properly (and I still have 4.5 months on warrenty).

I'll know more in a few weeks as that is how often Darky's 9.5 went south on me but so far just some odd ominous vibrations but they were not followed by a crash or freeze.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Well I hope I don't run into the same problems you did on Darky 9.5. Before the GB snafu, the version I was running -very stably I should say- was 9.3. Never went to 9.5 because I didn't see that much advantage and the update required a wipe...and like you said, rebuilding the desktop and entering username/passwords everywhere is a chore.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Well yeah you won't have an issue...

Just did it on stock/speedmod combo. my device or an app seems to corrupt my db_data partition frequently. Trying just a rooted stock kernel with stock firmware but no real tweaky apps like mem killers or juice defender etc. Then I will add them in slowly.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Well I'm now ln third week since I went back to Darky 9.5. Everything's perfect so far. I do miss some of the GB specific things but not too much. I'm going to give GB another try when something newer than JVQ comes out.
[Galaxy S I9000 Q&A, Help & Troubleshooting] fritzz75:
i had the same problem and it seems the tw4 is to blame-if you put to many widget or shorcuts on home panels the phone will freeze.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
No, its not that. I never used TW4.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ptbrudy:
I think i have the same problem as you. The mobile freezes every time the screen locks, and I can't unlock, I've read all the thread, and I've seen that you only have gone back to Froyo. But now I have Froyo 2.2 and still happening the problems. I've flashed to 2.2.1 and 2.3.3 and the problem persited (all oficial versions) now I'm on 2.2 because I'm thinking of sending the mobile to SAT.

Sorry for my english.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Your English is just fine :D

And I think you have a different problem. Probably a bad motherboard. Our problems specifically are hung phones after 4-5 days of use with Gingerbread, apparently caused by an increasing USB storage (internal phone storage) corruption by the OS. The result is random phone freezing, while doing just about anything -not only when phone is locked-

In my case, at least, the problem went away by going back to Froyo (Darky 9.5).
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
2.3.4 JVR out today.

Jvp and jvq were beta versions. Jvr is supposed to be final, so it might been more stable. I'm gong to try it but you're welcome to do so also and see if this problem is fixed.

Q: did any of you guys try MIUI or CM7?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
I tried to try cm7 but install wiped my imei settings and external sd was not recognized so I gave up.

Let me know about jvr, I'll try again. I think my froyo issues might be juicedefender related it's one of my longest lasting most invasive application and no problem in last 2 weeks so far. Could still be a kernel issue but I think it would be more common then.
[Galaxy S I9000 Q&A, Help & Troubleshooting] bhu1:
i don't know why it happens but it happens to me too i don't have an custom rom s i just have the out of box froyo and it hapens a lot literally a lot i factory reseted it in recovery mode but still it happened once i thought it is a touch wiz 3 prob. earlier but now i think something else is wrong or are these devices defective?
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Well with me its happened only on the currently available gingerbread ROMs. My phone came originally with eclair, and I've flashed several froyo-based ROMs and at least 2 of them were stock, and also Darky ROMs. It was only after I flashed gingerbread that I started getting these problems.

In your case, if you're on your factory stock OS and you're getting these freezes I'd say that your particular unit is defective. Take it back for a replacement.

UDPDATE: Installed *Stock* JVR today (rooted with CF-Root only) . Should either fail or pass by Sunday. Will update as I know.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Don't try it. 2 lockups already and not even made it to day 4. I'm on Galnet miui currently. If I don't like it I'm going back to Early 9.5 and staying there.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
Thanks for the update. I am waiting on the Bell gb update to 2.3 (. 3 or. 4 not sure) sometime this month. I hope it's not an issue for that stock rom.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] GreenSGS:
bump.I was wondering that it's my phone freezing randomly but it seems like an issue on all stock 2.3.3 roms and so on custom. 2.3.4 JVQ is came out officially and so this bug issue going to stay there.I feel like regreting buying this phone. one problem solved and next is in, for example started with lag in 2.1,then missing settings(yeah do factory reset but my phone still forget screen timeout now and then) and now hanging phone and force close.List can be longer.

We just keep solving problem,when can we use this phone with peace of mind.A stable CM7 is last hope.

I am going to write to Samsung tomorrow.This is f**king annoying.
[Galaxy S I9000 Q&A, Help & Troubleshooting] nhokonline2010:
-Hardcore's speedmod Kernel [k15H-T23] no use vs room cook Chebon.why? i no speak EN
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Try Darky 9.5. Rock solid and no lag. Both CM7 and MIUI are smooth and beautiful but they have battery issues. I'm not convinced of MIUI yet.
[Galaxy S I9000 Q&A, Help & Troubleshooting] eman:
We need to try to find what we have in common - causing the crash/freeze.

My phone is stock but rooted using CF-Root

EDIT: Also Noticed that the phone works more stable if No Lock is not switched on- I use an app called No Lock that prevents the phone from locking. I think it also prevents it from sleeping,
[Galaxy S I9000 Q&A, Help & Troubleshooting] DroidSamster:
Maybe flashing to a base 2.3.3 might help?

If just using factory reset isn't working...
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
All for it, but we've already tried to catch whatever's causing the freezes. I have over 106 apps installed and there's too few of us to get enough data. What is almost clear for us is that it's somehow related to the internal phone storage or the sdcars getting corrupted over time, by the os itself. Haven't figured out what's causing it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
I tried with a stock GB install with nothing except root. Same thing happened.
[Galaxy S I9000 Q&A, Help & Troubleshooting] bhu1:
U need something more stable ,forst install android 2.3.4 from samfirmware.com then root it using cf root (at your own risk,obviously) then install miui which is pretty stable or jetpack v3.1 which is super stable! and if nthng works for you then obviously go for cm7 which has bad battery life!

(all of this process is at your own risk)
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
Yeah, did that! I lived with MIUI for about 2 weeks. It is stable, but it's too iPhone-y and the battery life sucks horribly.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
So I am now on the Bell KG3 rom (2.3.3) and though it sort of sucks generally (bad battery - and stock so no bells and whistles) I haven't had the sd card corruption issue.

Of course no custom kernel works for this rom right now (just a rooted stock kernel)

When you flashed the stock roms were the de-odexed ones from Ramad's list or odexed ones from samfirmware.

G
[Galaxy S I9000 Q&A, Help & Troubleshooting] ferparedes:
KG3? 2.3.3? how can it be 2.3.3 and be KG3. 2.3.4 is JVP and up...

Anyway I'm not sure, but I think they were deodexed, so not 100% stock, there. No idea how I could get an odexed one.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lgsshedden:
these are common problems but different phones and different rom and kernel combinations. So, what does that tell you? The issue is residue from past installs and flashes of firmware interfering with whatever final program you wish to install. The only solution is to do a clean install, which means flashing a stock froyo firmware, using recovery to clean the system and reformat the sd card, then flashing a stock gingerbread, cleaning davlik cache and cache, and then worrying about the custom kernel and rom once you have a clean stock system in place again. Factory reset does not remove stuff from your internal sd card and without complete clean (including reformat of sd card and the repartition when you flash froyo) vestiges of past firmware can and do affect your later installs.

Doubtless someone will follow after and argue with what I have just posted. Fair enough. Just be aware that you can flash any kernel or rom, but without a clean install sooner or later, you will have issues which will impair your performance.