Database Users

Making the Leap - Stock - > Cyanogen: Let's discuss

Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!

DownloaderZ said:
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
Click to expand...
Click to collapse
I love it right now.. before it was bloated and totally incomplete and now they got it working pretty darn good you asked at a good time! but for some users.. still causing issues. For some like myself it is perfect right now absolutely no problems I took a while to stick with GB because of all the problems with CM7 I had an htc magic which was pretty similar to the dream and I understand most the problems you probably faced. I've tried a bajillion cooked rooms myself and ever since I moved to the nexus one I just stick with a few (I tried so many on the magic it was my first android and wasted so much time -_-) I would suggest you give this one a try it still has extra features but most of which I find useful

It makes it noticeably snappier and battery life is better. 99% win (wireless LAN reception is a bit worse). I went from stock 2.3.4 to CM7 and am kicking myself for not doing it 16 months ago lol. Maybe there were issues with cooked Roms earlier but the n1 is a mature platform and I haven't noticed any major issues with cyanogen 7.03, of course YMMV
Sent from my GT-P1000 using Tapatalk

I have been running the nightlies for weeks and they have been very stable for me. I have not had any significant problems and really like using them. #85 put the permissions blocking in yesterday and I tried it with a few apps. Seems to work fine. I liked stock rom, but personally could not do without trackball wake and lots of other wonderful features in cm.

Once you go custom you wont ever go back to stock.
Make sure you understand how to flash a custom recovery and how to get to it first.

he said he had cm on his hero so he must now about custom roms..
i think it is currently very stable and good apart from the wonk issue.

CM7 Nightlies have been gold for me. Except couple bootloops. I'm on #83 now with data throttle removed. I love my Dinc
Sent from my ADR6300 using XDA App

I have been running CM7 since shortly after the official Froyo was released from Google. I had to send my phone back for the powerbutton and so I rooted it right before and tried out one of the CM6 nightlies. It was amazing. The features in every subsequent version have only built on the quality of CyanogenMod. I have been a nightly user ever since (although I only flash nightlies every week or so).
It has been extremely stable for me and I have converted a few friends (most recently a friend with the Desire HD) and they don't know how they dealt with the stock crap for so long.
So in short, give it a shot. Do a nandroid beforehand if you are worried, as then you can go right back if you don't like it.

You can only control the permissions on cm7 nightlies. That feature isn't available in the stable release I believe.
Sent from my Xoom using XDA Premium App

cyanogen 7 starting at nightly #74 has introduced some new bug fixes which greatly improve standby battery life, so that now idle current with screen off is 3-4mA. its so good now, that you can leave your phone unplugged over night for 8 hours and only lose like 3% battery. and this is WITH wifi and email accounts turned on and syncing.
this makes the nexus one like a brand new phone and turned it into a proper normal device in the sense that you can now rely on superb battery life. you know that when you arent using it and the screen is off, when you come back to it you will have the same battery percentage as when you left it.
its a no brainer to use the nightly just because of this alone.

Ever since the 2.3.4, I've been happy with the battery life and fixes with the GPS. Currently my uptime is 190+ hours without the usual sluggish response that requires a restart.
Running CM7 I found more random issues from the call quality being distorted and random reboots, to other random bugs that I need something stable.
Sent from my Nexus One

i often go 550 hours between reboots on cyanogen.

Holy Cow!!!

Up until this point I've been using the EOS Stable Release 2, more because I liked the idea of "stability" over bells & whistles. On a whim last night I installed the EOS Nightly 117 build and I can't believe how fast it is. Screamin' fast! Plus it seems very stable.
How often do you nightly folks update? Every day? Every few days? When a new feature is installed? So far I'd say it's worth the time to update every day. I'm sold.

I usually only update when I am really bored or when I see a feature I really want!
I also updated to JB and it is -like you said- crazy fast! I absolutely love it. Now let's hope the addition of extra features doesn't slow down the performance

Its wicked fast and super stable. Loving it. Having no problems except the usual android apps toothing problems, not playing nicely with jb, but only encountered 2 so far.
Sent from my Xoom using XDA Premium HD app

holly crap

Yep that's Jelly Bean for you =)
The nightlies are generally very stable, it's once in awhile you will encounter issues, but so far I haven't been getting any issues at all. On another note I believe when TeamEOS implement Linaro optimisations on JB, the XOOM will be blazing fast.

Unless there is major change or fix in the nightlies i dont flash..
But do have a question with 117. I cant seem to get Video chat in google talk to work. It just goes black screen and closes. The normal IM'ing works.. just cant video. Both from and rear camera seem to work with the camera app.
Any Ideas?
Thanks!

R1150GSA said:
Up until this point I've been using the EOS Stable Release 2, more because I liked the idea of "stability" over bells & whistles. On a whim last night I installed the EOS Nightly 117 build and I can't believe how fast it is. Screamin' fast! Plus it seems very stable.
How often do you nightly folks update? Every day? Every few days? When a new feature is installed? So far I'd say it's worth the time to update every day. I'm sold.
Click to expand...
Click to collapse
Re: nightlies...I flash them as soon as they come out...works for me.
You see a big change, in part because you're now on a whole new operating system (Jellybean) that has a number of fundamental improvements. TeamEOS will be applying all of their own improvements from here on in, so it's really worthwhile to stay on the bleeding edge with these nightly builds.
Also, flash #118 and the newest eos gapps for Jellybean: 7/13. Your issues should be resolved. If not, there may be something in the Moto propriatary binaries that will be released when the OTA comes out that can fix video chat.

Sweeeeeet jelly bean
Sent from my Xoom using xda app-developers app

The speed increase your seing in Nightly 117 is due to what Google calls "Project Butter" which is a key new feature of jelly Bean and increases performance and screen draws significantly.
As to how often do I flash a new nightly, I usually skip about 10-20 nightlies unless one comes out that is reported to have very few issues and good enough for a release candidate.
Other times I will go off that if a particular bug I have been having is showed to be fixed but it really makes little to no sense for anyone but someone acting as a beta tester (and even then) to flash every nightly that comes down the pipe.
First off if you want to help squash bugs you need to use the device a lot and put it through it's paces which you can'y do if most of your day is spent flashing the newest.
And remember you bought the device to use it not flash it (although some would say otherwise LOL)
If you follow the project it's pretty easy to find the happy medium and know when to flash.
Anyone on the 1.0, 2.0 or pre 117 Nightly should really consider updating and getting all that Jelly Bean and Buttery goodness!
Not to mention Google Now which is pretty damn cool!
And just a warning to anyone on V2.0 or pre-Nightly 96 you will need to flash a new radio as well. Read the direction carefully as on;y Rogue Touch recovery can flash the radio and you need to flash that first before the rom. There is also a new Gapps for jelly Bean as well so read the instruction carefully.
But I'm running the jelly bean now and it is far superior to the older stuff and they haven't even started tweaking it yet they are just creating their base!

Back to ICS for me....

For the meantime at least...
I skipped ICS and went straight from GB to jelly bean, to be more exact, helly bean..
Now helly bean did run fairly slick for me, but the other night there I was bored, so decided to flash a couple of ROMs just for something to do, and since I skipped ICS, I thought I'd try slimICS with semaphore kernel.
My phone is totally instantaneous now, running even nicer than it was, also, I now have 220MB of free ram compared to the 80 or something I had on JB, which can only be good.
Considering I had the Google now disabled on JB before, I can't even think of any features of jb that I miss not having, and it looks pretty much the same too. I just can't warrant losing 150MB nearly of ram, and my phone running a little slower, even if its barely noticeable.
Also, battery life is a lot better in ICS compared to JB, and I did go through correct procedure to try and improve it in JB.
So for now I'm gonna stick with slimICS, at least until the next time I'm bored
I may end up going back to JB, but right now I'm kinda thinking that mainly because of ram constraints, that the trusty old i9000s are better off on ICS.. or am I wrong??
Would be interested to hear of others views or experiences... Cheers...
Sent from my GT-I9000 using Tapatalk 2

Latest GNexus release has 150 - 200mb of free ram too. It also includes a task manager to kill unneeded processes. For me it is the best Rom right now (I upgraded from slimics). I feel the butter of jb with triple buffering now
maybe your bad experiences are caused by devil kernel and/or different sd partition of heallybean Rom?
For me heallybean Rom lagged too. So I switched to semaphore which gained my device more speed and stability
Sent from my GT-I9000 using Tapatalk 2

I'll maybe give GNexus JB with semaphore a try next time I decide to flash a rom then.
How do you find your battery life is with it? Cos I really am noticing a big improvement in my sema/slimICS compared to my old devil/hellybean. Just got 19 hours out of a charge when I was used to about 11, not scientific I know but I use my phone a very similar amount each day. Definitely a lot better.
If I could get back to JB, with as much free ram as I have now, and a similar battery life I'd be a happy person.
Sent from my GT-I9000 using Tapatalk 2

Now I am not a power user but I second the GNexus rom.
Using the default Semaphore kernel it seems to use 2 to 3% an hour. This is just sitting in my pocket with wifi on.
I haven't run it below 50% so I don't know if the 2 to 3% is lineair since I have a charger in the car and at work.
About the free memory, well it all depends. I also have a S2 which I use for data (S uses a company paid sim but has very limited data) and I don't think the S2 is alot faster. The only thing I really notice is that the camera is faster, but what do you want.
This rom is smooth and does all I need it for.
I would suggest to give it a go without looking at the memory etc.

Same as first post for me, right now I don´t have enough time to try all the differents rom around but decided to install CM10 and the impressions were not so good, including fast battery drain. Surely gonna give it another try, but now I´m back with old good CM9.

I also loved Slim ICS 4.2. But now, slim bean 2.3 makes me forget about slim ics.
Together with semaphore is as stable and maybe faster then slim ics.
And 2.4 is almost out
Sent from my SlimBean powered GT I9000 using Tapatalk

JB
Try MIUI 2.8.31b Multi ..Android 4.1.1 Mackay Kernel , you will never search for another rom!

agree
I have to agree that ICS and SlimICS in particular is better than any JB rom out there now. Especially if you take advantage of the "Power Saver" feature in ASS, then it is definitely a keeper.

I'm currently on HellyBean, but I will try SlimBean

I got bored again lol
I've put on slimbean/semaphore with inverted gapps etc, and I must admit, I'm definitely feeling the JB butter
Bit less free ram than I had on ICS but if its gonna run this sweet I don't care. Its all good in the 'hood so far
Hopefully it will last.
Sent from my GT-I9000 using Tapatalk 2

Am I the only one who finds ICS & JB unbearably slow on Nexus S?

Seriously, it's like treacle! I'm about ready to root and install gingerbread.
Dialler takes forever to come up, when I tap the search button it takes many seconds for the keyboard to appear.
No-one else seems to mention this problem?
I have very few apps installed, and certainly no bloatware like task killers, etc.

No, you aren't the only one. Our phone is just a bit too old. All we can do now is bear with it until we upgrade.
Sent from my Nexus S using Tapatalk 2

Jelly bean is slow as **** for me. I guess most of the people just can't notice that jb's animations and reaction time when touching the screen is just delayed.
I've been frustrated with my nexus not acting fast untill i tried one combination. I'm i9023 user and this combo is just perfect for my phone. No input lag whatsoever, no animation lag, everything is just fast and instantly responsive. Give it a try and tell me what you think.
Cm9.1 stable:
http://get.cm/get/3F6
Air kernel 4.4:
https://www.dropbox.com/s/lfonudtw9ngerwf/Air_Kernel_v4.4_65fps+blue.zip
Gapps:
http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip
Use it with apex launcher, because trebuchet may lag when opening app drawer. To avoid dialler lag, i suggest using exdialer, it's downloadable from the market.
Please try that and let me know if I'm the only one who sees the difference
Even the keyboard is just faster than on jb. Scrolling, switching between windows, statusbar is more responsive. Try and tell me what you think.
Sometime I wonder how come poeple say jelly bean is faster than ics. First impressions are good, but after very short time of usage jelly bean is full of slow ****. Every rom based on jb is just slower than this combo.
Sent from my Nexus S

Nope. No problems here. Phone is fast and stable, although a little struggling with battery life, but like I said before somewhere in these forums, life is full of tradeoffs.

Yes this thing is slow. Its actually kept me from being involved with the phone. I don't add different ROMs or anything anymore because they all feel to heavy for this phone.
I'm just counting down the days until the next Nexus is released.
Sent from my Nexus S 4G using Tapatalk 2

"Am I the only one who finds ICS & JB unbearably slow on Nexus S?"
Pretty much, no problems here.

Xperia ROM
Hi,
For all of you who are not happy with the speed of Nexus S, try using this rom -
http://forum.xda-developers.com/showthread.php?t=1827071&highlight=xperia
I can assure it is definitely much faster than the stock ICS or jellybean ROMs. If you have been using the stock Nexus S ROMS, you will see noticeable difference in the colours. They are much better on this Xperia ROM and does not have that yellow shade. I love the ROM and believe me I have tried almost every ROM available on XDA for for Nexus S.
Though there are 2 issues, for which I haven't found any solution, it blocks the calls coming from unknown numbers and you do not even see a missed call. And you can't use the default screen locks. But apart from these, the ROM is rock solid, never crashes or hangs, everything works fine and it is ultra smooth.
If you think your phone is running slow, I highly recommend this ROM. Everyone should give this ROM at least a try.
Let me know if I helped by clicking Thanks

Mines seems fast but battery life is terrible getting a galaxy nexus next week
Sent from my Nexus 7 using xda premium

I don't really notice a difference speedwise between ICS and JB. They are both a little slower than GB was, but not unbearable. The added features of ICS/JB are well worth it IMO.
Overclocking a little bit can help, although it can hurt battery performance a bit.

muldy said:
"Am I the only one who finds ICS & JB unbearably slow on Nexus S?"
Pretty much, no problems here.
Click to expand...
Click to collapse
Agreed. Current combo keeps up with wife's combo. Don't know what the OP is talking about. See sig for both setups.

I agree with jellybean being kinda slow. However, i dont know if it's just the rom's were installing on our device, cause i kinda remember stock JB being pretty fluid which is kinda making wanna go back to stock again

GB was stale, solid, and best battery life.
I miss having a flashlight app that worked and better battery life.
ICS and JB have been ok up until I started having power button issues last week.
JRO03L update seems to have fixed the majority of freezes, crashes, and power button issue.
After the reality has set in, I would have stick with GB

no problems here. aokp jb build 2 and beladus marmite 4.4 kernel combo is running smooth on mine.
Sent from my Nexus S using xda premium

Slow? My phone is faster than ever. The fact though that your phone is not rooted explains your struggle.
Sent from my Nexus S

kwibis said:
Slow? My phone is faster than ever. The fact though that your phone is not rooted explains your struggle.
Sent from my Nexus S
Click to expand...
Click to collapse
Are you implying that every end-user of android phones should learn to root or install custom roms/kernel to get a DECENT experience? While I'm content to see Google supporting a device almost 2 years after its release (Apple does that as well btw), I'm kind of feeling disgusted about the overall user experience, laggyness, crashes, random reboots and decreased battery life. I wish Google released a FINISHED product/operating system and not leave its customers in a sort of beta-testing fog.

I'd suggest backing up your data and wipe your whole device like a madman. Format.
And start from scratch with the rom of your choice
Might be that time for your ol' precious Nexus S.
I did. And its very worth it :thumbup:
And for the others.. like the previous post..
Jump on the apple train. Yes, There os is stable... but stale
Dive in!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Memory management is the problem...
I think the problem has to do with the way memory is managed in ICS/JB... I still can't find found a recent ROM that will keep the launcher in memory no matter what. That's terrible for user experience! None of the task or memory manager apps in the Google Play Store seem to help either.

_
slow??? my NS is lightning fast! with slim bean ROM and bedalus kernel

DMardroid said:
I'd suggest backing up your data and wipe your whole device like a madman. Format.
And start from scratch with the rom of your choice
Might be that time for your ol' precious Nexus S.
I did. And its very worth it :thumbup:
Click to expand...
Click to collapse
^ this. I was having a bad experience with JB as well until I formatted my sdcard. And I'm not talking about wiping from CWM. I'm talking about mounting it as USB storage and formatting from a PC.
Sent from my Nexus S 4G using Tapatalk 2

Highway 55 said:
^ this. I was having a bad experience with JB as well until I formatted my sdcard. And I'm not talking about wiping from CWM. I'm talking about mounting it as USB storage and formatting from a PC.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

i9000, most unstable device to use custom roms

I had 2 android devices before this one and this one is by far the most unstable device for custom roms. I had a motorola milestone and nexus one and i rarely get bootloops and never get broken recovery. With i9000 its atleast once a week and for no apparant reason. My battery was low so i turned off my phone and replace the battery and then BOOM broken recovery and bootloop and im stuck with this **** in school....

Hey!
I have not tested other devices yet, but if i think about what i did to my I9000 and always got it restored, and also overclocking (up to 1200 mhz) runs stable as hell. I tested AOKP ICS Milestone 6 and the X-Bean 2.0 (JellyBean). Everything stable as hell.
But i think this differs from phone to phone.
I am a happy camper with my I9000 :highfive:

quick question regarding how unstable the i9000 is.
I bought my i9000 from a friend a few weeks ago as i desperately needed an android phone after drowning my Desire S on holiday. It was in great condition for a 2 year old phone.
I am on my 5th ICS ROM and every single one of them has been lagging like crazy after i install all my apps. ie. it takes about 2 or 3 seconds for the touch to respond on the screen sometimes.
When i go back to the homescreen using Go Launcher it looks like it reloads the whole thing. It feels like the phone is constantly loading apps freshly every single time you use them. They always load eventually but takes a good few seconds. I never use Task Killers.
Is it possible the actual ROM chips are dying in the phone? Crappy quality chips to keep costs down perhaps.
It lags constantly no matter what you're trying to do. No matter what app i'm trying to load up. And this has happened on every single ROM i've tried.
Any ideas if the actual hardware is simply dying?
ps. the Desire S ran ICS custom ROMS perfectly with only the occasional lag when you were doing too much. So the hardware in the i9000 is defo capable.

My experience is that sometimes a "RESET" is needed to make the phone act like brand new.
That means, wipe everything on the phone.
Install an Gingerbread ROM (JW4 for example). Flash the right CF Root Kernel.. Wipe Again (Data/Cache/Dalvik).
Then install one of the stable ICS Roms (I had AOKP Milestone 6) and i am currently on JB (X-Bean 2.0).
Both are stable as hell, and it feels like i am on a Samsung Galaxy S3 sometimes, i never had any lag, its fast as hell after some tweaking.
I would also recommend using Devil Kernel on your phone, had the best performance/battery with those.
But again, every phone differs.
For the record, my phone is also 2 years old and is used every day (almost heavy use).
Good Luck

yes that is right it is so unstable in ics and jb ....so laggy,many fc s

Then you're probably doing it wrong. No above mentioned problems here. I'm running CM10 latest nightly (all stock) since day one. Latest nightly is super fast and responsive and it's been like that since 5 nightlies ago.

Either your phone is crap, your rom is crap or your installation is crap. I'am on my 3rd Rom and never had Bootloops, lags or any other Problems.
Gesendet von meinem GT-I9000
----------------------------------------------
ROM: | ICS333 2.0.1 |
Kernel: | Semaphore ICS 1.3.0s |
----------------------------------------------

You got unlucky with your phone. My friend has this issue to, and I never had.
Sent from my GT-I9000 using xda premium

No way! I9000 is perfect for testing ROMS. I've tested many custom ROMS and now on CM10 latest nightly, the phone is amazing!

Tsipo said:
No way! I9000 is perfect for testing ROMS. I've tested many custom ROMS and now on CM10 latest nightly, the phone is amazing!
Click to expand...
Click to collapse
+1

Overclocking should do the trick. I have about 90apps on my i9000 running ICS AOKP rom milestone 6. I've overclocked my phone to 1.4ghz and it runs smooth with an ocassional lag which is not bad but most of the time its smooth. Battery life is ok.
Sent from my GT-I9000 using xda app-developers app

Ive never had the problems you mention but that doesn't mean ive ever been satisfied using a Jelly Bean ROM. In fact, the one I have now has been installed for less than 24 hours and I'm umming and arring about removing it. Just the little things Im afraid.

AlwaysDroid said:
You got unlucky with your phone. My friend has this issue to, and I never had.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I think you guys are right, my phone is just faulty. Need to find a replacement asap then.
Even installed V6 Supercharger and Maximum Overdrive and phone still lags like hell after a few hours use. Its fine after a reboot for a while but then the lag kicks in and can take up to 10 seconds for the screen to respond. Rebooting every few hours ain't much fun lol

I've been using my SGSI9000 with custom ROM's for more than a year now. It always ran smooth, I never soft bricked it nor had any boot loops while installing ROM's. I've been using several flavors of DarkyROM, then CM since version 7 I think, to 9 and now 10 (including alpha's and beta's) and I almost install the daily as it is released (almost daily ROM installs) and still the phone does great, battery is still good (more than 1 day of usage) and everything works ok (have lag from time to time, but nothing major).

You should always start by something "clean", then test if it is laggy, buggy, etc.
Either start with the latest official rom with a clean system or with something reputed, like CM9/10.
Don't forget to start from a clean rom, IE: Format user data, cache, /system, etc.
Then, if it is still unstable, you might have a defective device.
I've had this devices since about 2 years, and I have installed numerous rom and I can tell you the ones available currently are rock solid!

Locke der Boss said:
Either your phone is crap, your rom is crap or your installation is crap. I'am on my 3rd Rom and never had Bootloops, lags or any other Problems.
Gesendet von meinem GT-I9000
----------------------------------------------
ROM: | ICS333 2.0.1 |
Kernel: | Semaphore ICS 1.3.0s |
----------------------------------------------
Click to expand...
Click to collapse
+1
Also, to one of the guys who was complaining, get go launcher off your phone for a start, it uses a huge amount of ram compared to other launchers. I'm running JB on my phone and its super slick and stable with tons of apps installed.
Maybe its something you're doing wrong, or a poor choice of kernel, or maybe you've not set it up well, because I have seen none of the issues that you speak of.
Sent from my GT-I9000 using Tapatalk 2

Like i said i'm on my 6th or so ROM some ICS, some JB and even ran the stock GB ROM and they are all FUBAR after a few hours use. Currently its running RemICS UX. And as i said before its slick as hell for 2 hours then grinds to a halt.
I'm not a n00b, i've been on XDA since Nov 2010 and have had 2 HTC devices which ran all ROMS solidly so i know how to install a ROM with all the proper wiping etc.
I just wanted to confirm that having a Samsung device is a bit of a lottery, u might get a good one or a duff one. I can accept that the one i got is duff. Not a problem, just need to seek out my next phone.

kennyhkw said:
I just wanted to confirm that having a Samsung device is a bit of a lottery, u might get a good one or a duff one. I can accept that the one i got is duff. Not a problem, just need to seek out my next phone.
Click to expand...
Click to collapse
I wouldn't generalize to all Samsung devices, it is fact that there were 2 types of I9000 hardware produced. To quote:
MoneyFace =p said:
Our beloved Galaxy S has 2 storage chips:
512MB Samsung OneNAND and 16GB Samsung moviNAND (or SanDisk iNAND for newer batches)
OneNAND is a SLC NAND which writes much faster more suitable for contaning app data so your apps runs faster as it can write faster.
moviNAND is a MLC eMMC NAND which writes slower, more suitable for app and personal data storage.
Click to expand...
Click to collapse
So there is 512MB fast storage and 16GB of other storage. The 16GB has two versions, slow moviNAND on the early batches and faster iNAND on the later ones. The problem is that with newer ROMs that take more space it is a juggle what to put on the fast storage and what to put on the slower storage. Inevitably something has to go on the 16GB chip, which will be moviNAND or iNAND depending on how new your hardware is. If it is moviNAND, like my unit that I bought the week it launched here over 2 years ago, there is going to be worse lag depending on how the developer has arranged things. (That post goes into detail about how that particular ROM, Helly Bean which I run, uses the flash chips. CM10 has switched to this as well.
This quote says how you can tell which chip your unit has:
fishears said:
So, Is this ROM right for me?
If you have the fast iNand then, yes, because you'll get more data storage space with no loss of speed If you have the MoviNand then maybe yes, maybe no. My advice is "Try both".
To see which Nand you have look at the following file in a text viewer:
/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/name
If the content starts with "S" then you have iNand. If it starts with "M" then you have MoviNand.
Click to expand...
Click to collapse
In summary it's not some vague Samsung thing, it's a specific performance issue with the early hardware versions of the I9000 that they improved in later versions. Some ICS/Jelly Bean ROMs do a better job of managing this, the theory is that CM10 and Helly Bean are as good as it gets, but it is still not going to be perfect. I also think there are issues with RAM management on pretty much all ICS/JB ROMs for this phone (leaks) but that's another matter entirely.

OK, the only unstable thing I find about Jelly Bean (after a few days use) is flashing multiple .zips before a restart. On GB, I could flash, 2, 3, 4, 10, zip files via recovery and it would reboot fine. I find that Jelly Bean runs the optimizer then stops at 'Starting apps', I'd only flashed about 4 zip files. Maybe I didn't leave it long enough but after a few hard resets and what not JB came back but touchwiz was ****ed. It kept artefact'ing lol. However, when I flashed the 4 zips individually separated by restarts it was fine.

no problems here
hey,
well i have been flashing different roms, kernels, patches... for more than a year and never had issues on my galaxy s
could be something u're doing wrong, like no proper wiping maybe or partition problems...