yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] drakenabarion:
For me, each version is improving. This is the 23rd July build, and the previous build was very laggy on input, but this currently is instantaneous when I touch the screen. Its no longer a case that I touch the screen with no response for several seconds before all my input displays on screen withing a few hundred milliseconds. Nope now its instant, even more so than cm9. Probably an aspect of project butter which is far more than just vsync.

Loading apps is still a bit laggy. System can get unresponsive while loading various apps such as gtalk, gmail but most especially Facebook. However it is much improved, albeit not perfect, in today's build.

One fault that still exists is Google now. Its slow at the moment but on top of that, once it has been launched, it causes the whole system to become very laggy even after exit. Actually the only way to really exit is reboot.

As for launcher lag, I haven't had this outside of playstore updating an app in the background, or the issue with Google now.

This release the biggest aspect for me is the keyboard input. I don't even think it was like this in Froyo. Hopefully it wont regress.
[Galaxy S I9000 Android Development] elitevet:
It's bad taste to compare an RC to an alpha anyhow, tigerpants. STFU & GTFO.

Go watch the desktops change on your smooth phone or something.

Maybe even jerk off to it. Don't forget the baby oil, or else it won't be SMOOTH.

Punk.
[Galaxy S I9000 Android Development] mikandlotta:
Which part of [ALPHA] do you not understand?

This is an EARLY testing ROM, pretty darn good in my opinion, and an awful lot better than what Samsung is prepared to give us - naturally they want to maximise cashflow and sell new and 'better' phones.

The devs here have worked hard to prove that the SGS still has life in it and can actually 'do' what Samsung said was not possible.

If you do not like to risk your precious time with ALPHA roms, then please go somewhere else and find another sandbox to play in.

If you are willing to be constructive, detail quirks and problems in a way that will help the community, please stick around!
[Galaxy S I9000 Android Development] pmos69:
You are obviously free to try or not try what you want. Nobody is even making recommendations or comparisons. People usually report their own experiences and that's all.

What he did was call a lot of people liars, just because he had a different experience (no doubt because of something that didn't go well with is installation or testing method).
[Galaxy S I9000 Android Development] fatino:
Usually peoples experience is overrated because of whole new awesome JB 4.1 rom thing. You guys know its true. I just like to see things how they are. Alpha not alpha. As I said devs have a lot of time to make things better. I dont ***** about that. I just dont get why you have to insult him because his experience was worse than on cm9 which is true. And it was confirmed by a bunch of people. Jeez guys relax.

Wysyłane z mojego GT-I9000 za pomocą Tapatalk 2
[Galaxy S I9000 Android Development] groksteady:
You know what actually sucks? Waking up and reading several pages of people complaining, instead of specific points to what is improved or now buggy. The whole point of community, most especially for the non-devs in this subforum, is to offer help. Help as in the zero-cost updates you're getting for your aging, abandoned device, or help as in documenting a specific problem so a real-ass dev can look into it and make it better for all of us.

I'm sorry if I got rattled by mere trolls, but this is a fairly exciting time in the DIY development of the SGS, and it blows to see people crab on that this free buffet isn't perfect. Say something useful. And I hope this useless, venting post gets deleted, too, whenever a mod cleans things up.

sent from a telephonic device
[Galaxy S I9000 Android Development] AlexandreT:
Maybe your phone is one of those that really needs datadata. Why don't you try DerTeufel's rom based on CM10 but retaining datadata?
[Galaxy S I9000 Android Development] bohdans:
People need to realize that not all SGS are created equal!

I have an early model SGS, and it has the slower NAND than the new ones, It is nearly unusable in CM10 even on 20120723.

but I have also NEVER had a GPS issue, it locks in any ROM I have tried in 30 seconds everytime.

Because I don't have the GPS issue does that mean everyone else is lying? Of course not its a well known issue.

Just because YOUR SGS runs fast without datadata it does not mean that everyones will.
[Galaxy S I9000 Android Development] emli_:
This is freaking amazing, THANK YOU DEV TEAM!
[Galaxy S I9000 Android Development] AndroidBR:
And that's the reason why, just a few days ago I stopped by and made sure to register my happiness about the release of JB 4.1.1 OTA for the Samsung Nexus S.

I am very anxious to try CM10, but since this is my only phone and I have to rely on it for work, I can't afford to be wiping it every time I try out a new ROM that does not "meet my own standards, needs and expectations".

I'm also using common sense by avoiding making comparisons of two very different beasts: the official RC2+ CM9 and this "unofficial" Alpha CM10.

How many builds have been made for CM9? Hundreds? [It's worth mentioning that only one of those messed up my phone. And it was quickly removed from the download page.]

There's been like 3 or 4 builds for CM10...!

To the ones unhappy with today's CM10 performance on your i9000, you can try or go back to CM9 or just come back in a month or two from now.

And most importantly, be grateful for the hard work and the hours these kind developers/geniuses are putting in.

How do you do that?

You hit that "Thank you" button and support them by paying them a couple of beers.

My 2¢.
[Galaxy S I9000 Android Development] schafoO:
Got so me random reboots @ 0720 using semaphore a1&2. Clean flash. 0723 runs stable so far. Tyvm. It's a great ROM in alpha. Will be awesome as soon as it's "final"
[Galaxy S I9000 Android Development] TigerCourage:
@elitevet

Get a life man. I'd rather jerk off on a smooth rom than on a laggy one and I bet more people agree. Alpha or not, I'm not blaming the dev for the laggy performance because it will get fixed in time. I blame enthusiasmed people like you claiming it's super smooth compared to CM9 and give people high hopes to flash it right away.

I didn't mess with any of you so I'd appreciate if you're also not gonna mess with me. It's just a personal opinion wich I think I'm free to express.

Ontopic:

Rom is very stable if it wasn't for the lags in the app drawer. I think most of us use ICS mostly because of the beautiful launcher and hw accelerated interface
[Galaxy S I9000 Android Development] jacobuscuracao:
you can use Nova or Holo, nobody's going to hold it against you. Nova is doing a great job for me

BTW I think I feel a thread cleaning coming on ........ let's stay on topic guys: bugs and bug fixes
[Galaxy S I9000 Android Development] TigerCourage:
Tried both Apex and Nova. And it lags. When I go through the widgets, the widgets just redraw (that's a problem for me on ICS also but on JB the widgets take longer to redraw wich creates the frame drops)
[Galaxy S I9000 Android Development] Abyv:
Strange never had any random reboots. Not yet on cm10. Smoother than any other JB ROM. May be its my sgs is getting old. 1500mah battery seems to run out just in 24 hours.
[Galaxy S I9000 Android Development] jacobuscuracao:
well, I guess 'lag' is a kind of subjective. However, redraws should leave evidence (I have a couple of widgets but don't see redraws, or I don't notice them).

Now, when I open a logcat app, I get nothing. Is logging turned off? I'm on stock kernel, but not getting any (logs)
[Galaxy S I9000 Android Development] pmos69:
The lags in the app drawer are a common issue after installation.

This ROM, in its current state can take quite a while to "stabilise".

After that the experience is usually very smooth.

There are also issues with the media scanner dying/restarting at times, and that has a huge impact on performance when it happens.

The building/rebuilding of each application's data at the beginning, added to the fact this ROM is no longer using a dedicated partition for that mounted on the faster oneNAND also makes it slow for some time.

(You can find a cm10 based ROM that still uses the datadata partition).

Add these issues with all the initial syncs and you can understand why you have to wait some time to be able to perceive how things behave normally.

There are additional issues that can affect how things run, like Google+ miss behaving and stuff like that, but those don't affect everybody all the time.

This is not a perfect ROM. It's a little soon for that :)

All these issues and many others have been reported in this thread. Have a read.
[Galaxy S I9000 Android Development] pmos69:
Change the io scheduler to noop.

Set the governor to ondemand.

Use something link ram manager and lock the launcher in memory.

Set kernel samepage merging.

Set max CPU freq to 1200Mhz
[Galaxy S I9000 Android Development] abitzsong:
I have no specific lag on apex.

I mean there are lags but it's just as or better than ICS.

No random reboots either.
[Galaxy S I9000 Android Development] pmos69:
Only way I've been able produce random reboots is if I underclock it.

Can do it even in latest version - just set max speed to 400Mhz.
[Galaxy S I9000 Android Development] drakenabarion:
On 23rd July build. Just connected phone to pc for transferring a few files.

Several apps disappeared from app drawer but also my keyboard disappeared. Restart without phone connected to pc brought them back. Since this, several of my ringtones from sdcard don't show up in the list of ringtones. Some of the apps were not stored on sdcard but they all seemed to be purchased apps which disappeared.

Also I couldn't access the external sdcard from pc. The drive was displayed but trying to access was like trying to access an empty drive.

Also, but possibly unrelated, Google now provided weather cards when I rebooted. New feature caused by connecting to pc? :)
[Galaxy S I9000 Android Development] groksteady:
I had similar problems with derteufel's v5. Just now noticed on 0723 that rebooting while AC charging, the startup takes longer to prepare sdcard, then my custom ringtones (saved in sdcard) are wiped to unknown and are unavailable in the ringtone list. Also, Gallery is empty. Unplug the charger, and ringtones, sound settings and Gallery folders come back after several minutes. Reboot while not charging, and settings stick and everything shows up much quicker.

sent from a telephonic device
[Galaxy S I9000 Android Development] warhead1978:
Am i the only one ?

did a factory/reset and format /system before install ROM and gapps...

Gesendet von meinen "This device will be not supported" CM10 4.1.1 auf SGS i9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] LukeSP:
You're not the only one.
[Galaxy S I9000 Android Development] abellimz:
Hey guys i just flashed 0723,why is the ui so laggy? Apps load faster than previous build but now UI is unresponsive and laggy.

I dont see anyone talking about this, why is that so??
[Galaxy S I9000 Android Development] bohdans:
Stop re-posting your own posts and maybe read the thread. You might even find your answer which has been mentioned on almost every page.
[Galaxy S I9000 Android Development] sazinas:
It is so "laggy" because its is an ALPHA build. If you don't know what that means google it. Also stop reposting your posts to get attention!

Keep up the good work guys!:good:
[Galaxy S I9000 Android Development] warhead1978:
no one said "yes the position is not correct" no one said similar only last 15 pages lag butter vsync custom kernel settings in RAM management easter eggs...

so I wait and repost my screen in the morning (here) and wait for help full answers in a discussion thread ... sry for this ...

Gesendet von meinen "This device will be not supported" CM10 4.1.1 auf SGS i9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] bohdans:
Lots of people are having lag, others are not,

Some are using custom launchers, killing media scanning service or changing vmheap sizes to get less lag.

Some of these things work, others may not,

Since this is still an alpha and under development you best bet is to read through, and try some of the answers yourself and see what helps your lag issues.

The Lockscreen moved has been posted a few times, looks like its a bug that should be fixed "upstream" that is, by the CM team not pawtip as he is only looking after the device.
[Galaxy S I9000 Android Development] DROCSID:
I know how you feel, CM9 is great imho, but even with a modded CM9 (other

kernel etc) the stock CM10 is great for an Alpha and again I will use the magic

word 'smooth' and lagfree (for me).

Notice that this is an Alpha build and not every phone is the same, but you

HAVE to try the things here above mentioned:

- Clean flash (you'd already did so?)

- Install another modem (which works good for you)

- Let the ROM stabilize for more than a day

- Install Ram Manager Free (https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree&hl=nl)

and enable 'balanced', set LOCK LAUNCHER IN MEMORY and heapsize 64

- Set governor to deadline (I find n00p so much more laggy) from settings

- Disable any animation / haptic feedback (just a suggestion) from settings too

- Set CPU to 1200 Mhz (not necessary but I always like) again from settings

Now report back what you've mentioned on the above issue's. Better or worse?

It really should go better than you've experienced before on JB.

Ohw and I did NOT set kernel samepage merging, why should I do it? For better

benchmarking results? It's won't help imho (only when apps support it which they

don't now).

As a final word:
[Galaxy S I9000 Android Development] warhead1978:
I only post one screen not more... and it is the only one here in this thread ... I never said an other thing ...

Gesendet von meinen "This device will be not supported" CM10 4.1.1 auf SGS i9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] bohdans:
Thank you RATBORG for a nice list of things to try to reduce lag! We need to point this post out to all "my phone is laggy" posts :D

Might not fix it for everyone, but its a good start to get people trying themselves.

---------- Post added at 03:38 PM ---------- Previous post was at 03:36 PM ----------

Sorry warhead1978 I was aiming more at abellimz's post (laggy phone) not yours.
[Galaxy S I9000 Android Development] DROCSID:
Sure, it helped here too :D
[Galaxy S I9000 Android Development] Vogie:
I try all JBs exept this ROM

Dose this one fixed media issue?

Can i see my pics n music in gallery and music player?

Sorry for my low bandwidth and limitations for download and try by own.
[Galaxy S I9000 Android Development] abellimz:
No the point is not how laggy it is... im talking about how different my experience is from eveyone else on the same build, so anyone care to help? Its not just the usual "not smooth" UI complaint... im getting a severe UI lag, I'm just curious as to whether its just me.

Stop assuming every questions on lag is a criticism of this rom, Im smart enough to understand that this is alpha.

I just want to know if im the only one facing the ui lag problem which didnt exist in 0720...

In this case its actually about smoothness, not lag. Damn it.

Or do I have to wait for the vsync to settle? I waited a few hours btw.

Nowadays people on XDA only knows how to criticise others for being rude without realizing that they misunderstood others. Sometimes they themselves are rude also without realizing it. Stop feeling self-righteous about it, its a terrible culture. Sighs.
[Galaxy S I9000 Android Development] Ogix:
try Semaphore JB kernel, it is a lot smoother for me without any mods.
[Galaxy S I9000 Android Development] pmos69:
Yes, in 0723 the UI animations seem less smooth and a bit more jerky to me than in 0720.

It's a bit strange because the overall response from applications seems to have improved.

Or maybe I'm just imagining stuff. It's quite possible.
[Galaxy S I9000 Android Development] purpleraintoxicity:
For me apps seems to stuck one in a while.

While animation seems smoother
[Galaxy S I9000 Android Development] burakgon:
Buy a tank or helicopter, if you find that laggy. Compared with SGS3 ICS and owned everyway.
[Galaxy S I9000 Android Development] p!rate:
Thanks dev's, love it :)
[Galaxy S I9000 Android Development] pmos69:
That must show how subjective our evaluations must be :)

Have you tweaked the heapsizes?
[Galaxy S I9000 Android Development] riggnix:
20120723 running very smooth.

Using Devil Kernel 1.0.2

dalvik.vm.heapstart size = 8m

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=128m

SmartassV2 100-1000MHz

Deep Idle ON

Devil Idle Auto

Battery life is great already too...

Working better than CM9. Thank you!

Only issue is having to turn on/off flight mode after reboot for data connection. But that's minor ;)
[Galaxy S I9000 Android Development] Milkman12:
This friend of mine just installed the rom but before entering in the system it requires a password. He doesn't have a pin code, he tried a few solutions, but nothing. What could be the solution?
[Galaxy S I9000 Android Development] thestudent00:
It happend for others sometimes too. Just reflash the rom. Perhaps wipe again before flashing

Sent from my GT-I9000 with UNOFFICIAL cm10 JB
[Galaxy S I9000 Android Development] abellimz:
No guys! I'm not talking about slight UI lag. Its that the whole thing is unresponsive and scrolling lags, go launcher lags and everything lags! Seriously nobody facing this issue?

I did a clean install.

When I first boot up the rom it runs smoothly but after a few minutes the whole phone has severe UI lag. Yea. Hope some one can help me.
[Galaxy S I9000 Android Development] bohdans:
Try what tips others have posted, but you may have an older version with the slower NAND chip like me :(
[Galaxy S I9000 Android Development] gmhafiz:
I upgraded from 20 to 23, google now worked partially - it did not speak back.

So I wiped everything, flashed 23 and gapps-19. Google Now works including TTS.
[Galaxy S I9000 Android Development] pmos69:
Testing it now (On a train, using a PC - wifi AP over 3G - writing this), and it's working perfectly with "stock" cm10 kernel.

Scratch one more. :)
[Galaxy S I9000 Android Development] mermigas:
I dont know if is the right place to post but I have no guidance voice with GPS application IgoMyWay (Primo).

With Copilot and Navigon all is OK
[Galaxy S I9000 Android Development] 99x:
Slight OT, but how much fast onenand does the galaxy S have (in comparison to the Nexus S, which I believe has 512MB?) This might help people understand why the Nexus S is better with JB.
[Galaxy S I9000 Android Development] Kurre:
I'm not sure are you asking about performance (fast) or capacity (512MB), but oneNAND is the faster and smaller one (moviNAND is 8/16GB).

Performance can't be easily tested on oneNAND AFAIK (and it probably ain't the issue afterall (over 100MB/s), but the size). And I think that SGS has same size chip as Nexus S (if it have's that 512MB chip as you mentioned).
[Galaxy S I9000 Android Development] riggnix:
AFAIK I also have the slow, old NAND. My phone was bought in June 2010, that has to be one of the first batches.

0723 still running very smooth here. try flashing again, maybe wiping everything will help, the install script isn't perfect yet... also you might wanna try Devil Kernel (make sure you use the JB version).

Editing your heap settings in build.prop could also help, find my settings a few posts back, they're working pretty great.
[Galaxy S I9000 Android Development] 99x:
Sorry, was talking about capacity - as nexus S doesn't have the datadata issues AFAIK
[Galaxy S I9000 Android Development] riggnix:
that's correct I think.

the problem is, that Galaxy S (at least the very old ones) have a slower moviNAND chip than Nexus S. the /data partition is located in moviNAND, so a slow moviNAND slows app startup and so on...

that's why with CM9 /datadata was invented. this was on the fast oneNAND, and tried to store performance critical files. But with Jellybean, the /system partition has to be bigger than with ICS, leaving no place for /datadata.

also, pawitp said (and i agree) that /datadata was only a workaround and we should think of something else we could actually do to fix this issue.
[Galaxy S I9000 Android Development] strickyy:
Where can I see, which chip does my phone have?
[Galaxy S I9000 Android Development] 99x:
Ah, thanks that makes sense. I also read somewhere that the Nexus S stores /system on moviNAND, does Galaxy S store this on oneNAND instead?
[Galaxy S I9000 Android Development] riggnix:
i really don't think that Nexus S stores /system on moviNAND. the whole point of oneNAND is to hold /system...

putting /system on moviNAND would really slow down the phone.
[Galaxy S I9000 Android Development] Alberto96:
Why dont make a system for partitions with ram cache? As FancyCache for windows do? It would be much better. For example we have 388 mb of ram. 64 mb or 100 mb for the cache ( i know that would reduce ram but can increase performance) and its solved. See : http://www.romexsoftware.com/en-us/fancy-cache/index.html
[Galaxy S I9000 Android Development] riggnix:
I don't think there is a way to do this. The newer the phone, the more likely it is to have the newer chip.
[Galaxy S I9000 Android Development] bhu1:
U can Google to see if their is any old news article about the chip. When did Samsung started using the new, from exactly which batch. Then see the manufacturing date on or phone's box. Mine was manufactured in February 2011 so I am pretty sure its new.
[Galaxy S I9000 Android Development] 99x:
Apparently the Nexus S has 1GB Rom so I was probably wrong when I said it had 512MB.

MCP - 8Gb (1GB) MLC Flex-OneNAND + 4Gb (512MB) Mobile DDR + 1Gb (~125MB) OneDRAM, PoP (Estimated)
[Galaxy S I9000 Android Development] oliva94:
@pawitp Please add to the OP that there are two kinds of moviNAND and those who have the old one will have app load slowdowns.

That would have stopped the previous ~100 posts of flamewar.
[Galaxy S I9000 Android Development] pmos69:
Ram is even more precious than the onenand.
[Galaxy S I9000 Android Development] Alberto96:
We have enough ram, 64 mb of ram for the cache i think that are not so important. After we should have 324 mb of ram and for me are enough. And for people that wants a major boost 128 mb of cache = 260 mb ram. Or we can use bigmem option and we have more ram free. ( cache not the partition /cache )
[Galaxy S I9000 Android Development] 99x:
If we can get the large ram kernels (with support for HD video decoding) then there will be even more free ram. Perhaps we can just increase the /cache partition size, now that we don't have /datadata or has the free space been consumed by /system?
[Galaxy S I9000 Android Development] NamNamNom:
Hey guys...

First i wan't to say thanks to all the devs that are working hard and free to keep an old phone alive. It's a great rom.

Secondly, please people, don't complain about how laggy or "unsmooth" the rom is. IT'S AN ALPHA! Mods and other things aren't fully functional in the rom yet. It was almost exactly the same thing with ics. The difference is that JB is harder to get working.

Instead of complaining do something useful. Report bugs, so the devs can see what to do in the next build.

Pawit gives you jellybean without any need to pay for a GNEX or Nexus S, and that's why i think you should be grateful.

Hope you guys read this before posting anything...