Database Develop

Heads Up For Devs (Next big thing)?

Now that the lag fixes have made strong progress and Froyo's source is almost here, there's one final thing that can be fixed about the SGS: compared to other phones, it's got quite a bit of less USABLE RAM.
Luckily, a cool dev in the i9000 forum has been messing with the kernel and figuring out how to free up more RAM. He's at 356 MB freed up (non-stable) thus far, and about 340 MB stable. This is up from 304 MB by default!!
Take a look if you haven't already. http://forum.xda-developers.com/showthread.php?t=816229
Thanks to all devs for their hard-work, and I hope this helps you out in some way.

this requires board configuration files which are only available in source, not useful to us until we have source.

has anyone figured out if the 200 some odd megs of missing RAM are used by the GPU? Or does it have its own dedicated RAM?

Kaik541 said:
this requires board configuration files which are only available in source, not useful to us until we have source.
Click to expand...
Click to collapse
So you're saying we need the Captivate source files specifically? Because it works just fine for i9000 SGS.
gunnyman said:
has anyone figured out if the 200 some odd megs of missing RAM are used by the GPU? Or does it have its own dedicated RAM?
Click to expand...
Click to collapse
The thread details some of it. Apparently Samsung's programmers were lazy and it dedicates quite a bit of RAM for GPU purposes (but doesn't dynamically allocate it based on usage... so that RAM just sits there useless when you're not doing video-intensive applications) and some of it is also for the radio/modem.

Disgustipated said:
So you're saying we need the Captivate source files specifically? Because it works just fine for i9000 SGS.
Click to expand...
Click to collapse
yes, unless you know how to make a captivate froyo kernel without sources and aren't sharing (don't point to xcalibur's kernel, that's an i9000 kernel, not a captivate one)

Still interesting stuff though. Looks like we'll be able to recover at least 20-30 MB of RAM from the GPU. Perhaps more once it gets sorted where each and every drop of that original 512 MB is going.

Would be cool if that is what CM6 was waiting for....
that would yield huge performance increases i'd imagine.

iamamp3pimp said:
Would be cool if that is what CM6 was waiting for....
that would yield huge performance increases i'd imagine.
Click to expand...
Click to collapse
No it would not, having 140-150MB up from 120-130MB free RAM while sitting on your home screen and running your applications will NOT give your a huge or otherwise performance increase. FREE RAM means it's not being used! this is not a desktop where it uses a lot of swap when running on a low RAM system. the hardware on these devices NEED the alloted RAM to operate correctly. Samsung was not simply "lazy" mess around with the kernel and free up a few more MB RAM and you might find a few VERY RAM intensive applications that perhaps run smoother or what ever but then you are reducing performance of all the hardware features that make your device so nice, I.E the Camera, Radios, GPU. the effort is not worth any possible tiny free RAM boost you might get. why does everyone care so much about the free RAM anyway. I know a LOT of folks are going to jump in here now and ramble on about how it's a big deal and how samsung screwed it up or whatnot, but making those hardware features dynamicly allot RAM would mean that the kernel would have to some VERY efficient prioritizing of hardware/software RAM usage in order to have the device run currently in whole. It makes more sense to me to just do what they did and lock the amount of RAM to those hardware features that would allow them to best operate without your phone radio not working right or your camera not being able to record in 720 because you forgot you had some application open in the background and RAM prioritizing isn't as perfect as it should be. the device runs FINE! Also so this isn't confusing to anyone who might think that I think we want to make the RAM dynamic, I understand it'sstatic thing but the same things apply, those hardware features would just be stock without the correct ammount of RAM all the time.

ICS on 512MB a problem?

Just wondering... is 512MB going to be a problem with ICS?
(It's a simple question I know)

Scougar said:
Just wondering... is 512MB going to be a problem with ICS?
(It's a simple question I know)
Click to expand...
Click to collapse
I'm writing this from CM9 ICS alpha and runs perfect, don't worry for that
Enviado desde mi LG-P990 usando Tapatalk

No, it shouldn't be a problem.
But please post such things in the ICS discussion thread!

Flix123 said:
No, it shouldn't be a problem.
But please post such things in the ICS discussion thread!
Click to expand...
Click to collapse
Thanks and apologies. I had wondered if getting a 1GB model phone would have been a significant advantage.
(Mod feel free to move the question to a post in the discussion thread).

Scougar said:
Thanks and apologies. I had wondered if getting a 1GB model phone would have been a significant advantage.
(Mod feel free to move the question to a post in the discussion thread).
Click to expand...
Click to collapse
You can almost guarantee that a 1GB model will be better. The Optimus 2X does struggle with it's 512 mb, because 128mb is attributed to the GPU. Lukily, some kernels, like IronKrnl free some of that memory up and give it back to the CPU, but it's still losing 80mb.
Also, it's worth noting that, if you want to run ICS, if you look at the phones out that have 1gb of ram, you'll see they're all actually better phones- especially what Samsung make.
So, while the O2X is a cheap dual-core device. The best experience will come with something with 1gb of RAM, as it's much more likely to also get ICS. (Due in part because most 1gb phones have already had an announcement, and for it to be soon)

ICS is very hungry in memory. On my Asus Tablet running official, my 1GB RAM is fully used, as usual in Linux but at a higher level than in GB.
To run ICS correctly on O2X, you must use IronKrnl, the 48mb ramhack version is correct (means it steals 48MB to GPU, leaving only 80MB to it), and modifying memory killer values to a sort of aggressive profile.

Yea right, so this is why I had less free memory on GB. And now I have CM kernel on ICS. I doubt you actually tried CM9 alpha on O2X if you are talking crap like this about performance.
Sent from my LG-P990 using Tapatalk

The browser in ICS works better even though we have 512MB. It always returned to where I had left. 512 and less is enough for full desktop environments on PC even.

Ph4nt0m_ said:
Yea right, so this is why I had less free memory on GB. And now I have CM kernel on ICS. I doubt you actually tried CM9 alpha on O2X if you are talking crap like this about performance.
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
See my sig and stop arguing. I run CM9 since first day Ricardo published SK0, and now running SK2 with latest Ironkrnl. Setiron himself admitted on Google+that ICS is a memory eater.

Dont know how much free memory we're talking about here but I'm on SK2 with original CM9 kernel. Using Adv.Task Killer from time to time and I always have around 200-240 Mb free memory. Just sharing my experience

Running CM9 aswell and its sooooo smooth, faster than any rom ive tried

OK, so what happens when you want to run Tegra games? (like Dungeon Defenders for example). A shame you cannot dynamically set the ram hack :-(

Scougar said:
OK, so what happens when you want to run Tegra games? (like Dungeon Defenders for example). A shame you cannot dynamically set the ram hack :-(
Click to expand...
Click to collapse
That's the real question... Free memory when phone is idle means nothing. Plus you have to consider the lowmemkiller values you have set, I personnally use aggressive values: 16 24 32 90 100 110 to free the most possible memory.
Many users report freezes with games that run perfectly on GB. The problem or ramhack is choosing the right value for gaming, it seems 48mb version is the best compromise. A 'on the fly' feature was not planned for the moment by Setiron in one of his G+ posts.

Mjuksel said:
Running CM9 aswell and its sooooo smooth, faster than any rom ive tried
Click to expand...
Click to collapse
That has no direct link with OP. But it's true it's smooth lol.

Striatum_bdr said:
That has no direct link with OP. But it's true it's smooth lol.
Click to expand...
Click to collapse
It does. In low memory situations ICS seems to keep running better and smoother compared to GB. If you get under 40mb free on GB everythings gets very slow, with ICS it seems to handle it a bit more elegantly from a user experience.

Please don't think I'm pesimistic here, I'm just going off the comments: Given that OEM releases tend to be bloated and memory wasteful, it's not looking great for an LG ICS release that is 'fully' working. If they pull it off and allow tegra games to run, then I'll be impressed

the official release from LG should be more efficient, and once you remove bloatwares, it should be quite a charm

Hi,
The Google Nexus S also has only 512Mb, and a certain amount of those allocated to GPU (though I don't remember how many), and ICS works like a charm on it... So I think it shouldn't be a problem on our O2X! :-D

hearoy said:
Hi,
The Google Nexus S also has only 512Mb, and a certain amount of those allocated to GPU (though I don't remember how many), and ICS works like a charm on it... So I think it shouldn't be a problem on our O2X! :-D
Click to expand...
Click to collapse
It has the same config (128 for the GPU, 384 of available RAM) and works really fine.
Obviously a full gigabyte would be awesome.
Cheers!

Im typing using my optimus one running icss.
NOTE: my phone can only be over clocked till 729mhz.
So for our 2x it will be no prob.
Just need propriety files.
Sent from my LG-P500 using Tapatalk

The Dar Knight Rises lagging excessively on Optimus 2X?!

The graphics are exceptional but the lag is so bad that it hinders my gameplay significantly.
I don't understand why this is happening. The game runs perfectly smooth on an ipod toucb 4th generation; sure I know that apple has a way of making their devices run apps smoothly. I also know that optimus 2x's tegra 2 gpu chipset isn't the most powerful but it's certainly not a low end GPU either. As a result coupled with a dual core processor surely it should play very smoothly, when a device like an ipod touch with its mere 1ghz can even execute it fine.

Beplexor said:
The graphics are exceptional but the lag is so bad that it hinders my gameplay significantly.
I don't understand why this is happening. The game runs perfectly smooth on an ipod toucb 4th generation; sure I know that apple has a way of making their devices run apps smoothly. I also know that optimus 2x's tegra 2 gpu chipset isn't the most powerful but it's certainly not a low end GPU either. As a result coupled with a dual core processor surely it should play very smoothly, when a device like an ipod touch with its mere 1ghz can even execute it fine.
Click to expand...
Click to collapse
Which android version/rom are you using?
ICS is known for using a lot of memory. So, there is a chance that the 512Mb of our device is not enough for using the android system + game.
If you're in ICS, I suggest you to downgrade to a rock solid CM7 GB rom. (temasek's unnoficial cm7 is just AWESOME).
I am really sad to say it, but i think our device is not capable of running ICS in a heavy use profile.

I think we need hwa driver to run those new games out there smoothly
Sent from my Optimus 2X using xda premium

cool.guy said:
Which android version/rom are you using?
ICS is known for using a lot of memory. So, there is a chance that the 512Mb of our device is not enough for using the android system + game.
If you're in ICS, I suggest you to downgrade to a rock solid CM7 GB rom. (temasek's unnoficial cm7 is just AWESOME).
I am really sad to say it, but i think our device is not capable of running ICS in a heavy use profile.
Click to expand...
Click to collapse
That's depressing, because i'm currently using temasek's unofficial cm7 ROM
On a side note, based on the Play Store reviews for Dark Knight Rises it looks like high end phones like the Galaxy S2, Galaxy Nexus and even the galaxy S3 experience occasional lag. Therefore i'm not entirely giving up hope of being able to play this game...
Also you say that our device has too little RAM. Once again i'll refer to the ipod touch 4th gen. It only has 256 MB of RAM and a 1gHz processor, yet my friends have shown me how TDKR runs quite smoothly on their device. I'd like to know how this is possible.
I know about smartphones' inferior gaming quality compared to portable consoles like PSP which only have 64MB of RAM and a 222mHz processor, because PSP's are specifically designed for gaming and don't have other processes that interfere with their performance. I don't think the same analogy can apply to ipod touches and android phones, because ipods are essentially mobile devices without the texting and calling capabilities. So I REALLY can't see why our phones are incapable of playing this game.

Use ramhack to have some more RAM available, overclock your processor and use the highest OTF value for the GPU if you use the Etana Kernel. You could also kill all running processes before running the game. Just make sure to have enough RAM free for the game.
Sent from my Optimus 2X using xda premium

Just saying, PSP has 333 MHz
Sent from my SGH-T989 using xda app-developers app

333 mhz since 3.5 firmware.

Blazing angel said:
Just saying, PSP has 333 MHz
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well that's nice to know. Still frustrated about this game.

mybe is the rom problem instead of ICS laggy,
i had no issue while i m in ICS, but not with the game you mention

jackn3o said:
mybe is the rom problem instead of ICS laggy,
i had no issue while i m in ICS, but not with the game you mention
Click to expand...
Click to collapse
I'm sorry but I have no idea what you just said...are you suggesting that I use an ICS ROM?

Beplexor said:
That's depressing, because i'm currently using temasek's unofficial cm7 ROM
On a side note, based on the Play Store reviews for Dark Knight Rises it looks like high end phones like the Galaxy S2, Galaxy Nexus and even the galaxy S3 experience occasional lag. Therefore i'm not entirely giving up hope of being able to play this game...
Also you say that our device has too little RAM. Once again i'll refer to the ipod touch 4th gen. It only has 256 MB of RAM and a 1gHz processor, yet my friends have shown me how TDKR runs quite smoothly on their device. I'd like to know how this is possible.
I know about smartphones' inferior gaming quality compared to portable consoles like PSP which only have 64MB of RAM and a 222mHz processor, because PSP's are specifically designed for gaming and don't have other processes that interfere with their performance. I don't think the same analogy can apply to ipod touches and android phones, because ipods are essentially mobile devices without the texting and calling capabilities. So I REALLY can't see why our phones are incapable of playing this game.
Click to expand...
Click to collapse
That it don't work good on the O2X can only be because of 3 things.
1. The developer have made the game primary for newer phones with more power.
2. The software on your phone don't make good use of the hardware.
3. Poorly written/bad code in the game-
That it runs fine on the PSP you seem to have a good understanding for. Good thing to mention about the PSP is that the resolution is really small compared to phones now days. But you miss the similarity to the iPod? Sure the iPod runs the "same" firmware as the iPhones. Only that when it's installed to the devices it leaves out all phone stuff(things thats ALWAYS on and use RAM).
This is also a common thing that it's nothing that people can deny. Most apps runs better on iOS then their counterpart on Android. Why? Because its easier to program for iOS. Not easier in the mean of writing the code but testing it and making sure that it runs on every or at least those devices you want. Without the need of posting a minimal requirement list like on PC's. Also goes for the PSP and every other game console, maybe I didn't need to mention that.
O yea for the record don't try ICS rom it will be a waste of time since it don't have any HW-acceleration.

lintz said:
That it don't work good on the O2X can only be because of 3 things.
1. The developer have made the game primary for newer phones with more power.
2. The software on your phone don't make good use of the hardware.
3. Poorly written/bad code in the game-
That it runs fine on the PSP you seem to have a good understanding for. Good thing to mention about the PSP is that the resolution is really small compared to phones now days. But you miss the similarity to the iPod? Sure the iPod runs the "same" firmware as the iPhones. Only that when it's installed to the devices it leaves out all phone stuff(things thats ALWAYS on and use RAM).
This is also a common thing that it's nothing that people can deny. Most apps runs better on iOS then their counterpart on Android. Why? Because its easier to program for iOS. Not easier in the mean of writing the code but testing it and making sure that it runs on every or at least those devices you want. Without the need of posting a minimal requirement list like on PC's. Also goes for the PSP and every other game console, maybe I didn't need to mention that.
O yea for the record don't try ICS rom it will be a waste of time since it don't have any HW-acceleration.
Click to expand...
Click to collapse
I see...so ipod touches don't multitask either. Well that actually makes perfect sense seeing as it's iOS.
And yeah I know about the lack of HW acceleration. LG has to release ICS officially so we can get the drivers...but the hopes of getting ICS on our phone are getting dimmer by the day especially with LG canada confirming no ICS for their phones -.-
*Edit: I'm going to be bold and deny the fact O2X is not powerful enough. I just saw 2 reviews in the newest reviews for TDKR on playstore, one using HTC One X and the other Nexus 7 both complaining about horrible constant lag. If some quad core devices experience this lag, then surely it must be the dev's problem?

Beplexor said:
I see...so ipod touches don't multitask either. Well that actually makes perfect sense seeing as it's iOS.
And yeah I know about the lack of HW acceleration. LG has to release ICS officially so we can get the drivers...but the hopes of getting ICS on our phone are getting dimmer by the day especially with LG canada confirming no ICS for their phones -.-
*Edit: I'm going to be bold and deny the fact O2X is not powerful enough. I just saw 2 reviews in the newest reviews for TDKR on playstore, one using HTC One X and the other Nexus 7 both complaining about horrible constant lag. If some quad core devices experience this lag, then surely it must be the dev's problem?
Click to expand...
Click to collapse
The 3D hardware acceleration is working perfectly fine on ics. So there shouldn't be a difference between ics and gb in games. Except some that are caused by less free memory in ics.
Sent from my LG-P990 using xda app-developers app

I have CM9 Nova HD - ICS, along with Chainfire 3d with all the drivers. Still the laggy performance of TDKR.
Guess they have not made the game accordingly.
tonyp said:
The 3D hardware acceleration is working perfectly fine on ics. So there shouldn't be a difference between ics and gb in games. Except some that are caused by less free memory in ics.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse

KLP Custom ROM for our SGSA...?

Will we have a Key Lime Pie Custom ROM for SGSA once its released? Just very curious about it
I am putting this thread here because I think this should be a general discussion where everyone could share their thoughts/development plans.

Don't get your hopes too high,If 4.3 Jelly Bean can be ported as a custom ROM because of similarity,I don't think KLP will ever be on this device,only if STE releases the sources,which is improbable.

It will be possible only if STE release sources. Now we have their pre-built binaries from our stock jb and devs have difficulties making them to work on aosp 4.2. Almost no chances in making them working on KLP because our libs where made for 4.1 and we don't have their sources to modify them according to newer versions of android.
*generic signature*

The reason why we don't get 4.2.2 is because RAM consumption, even with CM, that uses way less ram than stock rom. Now, if CM10.1 uses less RAM, and the consumption is still high... Imagine on stock...
Sent from my gt-i9070 using xda app-developers app

AnMotass said:
The reason why we don't get 4.2.2 is because RAM consumption, even with CM, that uses way less ram than stock rom. Now, if CM10.1 uses less RAM, and the consumption is still high... Imagine on stock...
Sent from my gt-i9070 using xda app-developers app
Click to expand...
Click to collapse
What are you talking about? Now with the buggy settings app, which takes up 60mb+ ram, there's still 380mb ram free. Without any app killing, or "ram freeing" what you would do on a stock rom. Stop talking nonsense. And btw, cm10.1's ram management is completely different than a 4.1.2 stock rom's... you won't run out of ram, except if you run an app which requires 600mb ram..
Edit: After opening: dialer, messaging, browser, clock, and camera, there's still 368mb ram free (in the settings, so count that in..). So what are you talking about?

tesztelem said:
What are you talking about? Now with the buggy settings app, which takes up 60mb+ ram, there's still 380mb ram free. Without any app killing, or "ram freeing" what you would do on a stock rom. Stop talking nonsense. And btw, cm10.1's ram management is completely different than a 4.1.2 stock rom's... you won't run out of ram, except if you run an app which requires 600mb ram..
Edit: After opening: dialer, messaging, browser, clock, and camera, there's still 368mb ram free (in the settings, so count that in..). So what are you talking about?
Click to expand...
Click to collapse
cool man..LOL

AnMotass said:
The reason why we don't get 4.2.2 is because RAM consumption, even with CM, that uses way less ram than stock rom. Now, if CM10.1 uses less RAM, and the consumption is still high... Imagine on stock...
Click to expand...
Click to collapse
I think RAM is not the real problem on our device. There's plenty of free RAM even when multitasking, and also Android can instantly clear RAM when needed in order to open a new app.
Some rumors I heard say that Key lime pie will a quite light OS, so it will be able to run even on devices without a big hardware.
The real problem IMHO is ST Ericsson not releasing source codes. Samsung will likely not release official 5.0 for our device, and we should rely on developers, but I imagine it's hard for them to port a 5.0 based rom from other devices without source codes.

KLP=Android KITKAT=CM11
Just search the cm 10.2 thread of team canjica's for cm 11 and there will be a post by the developer about CM 11 being under construction.
Also the Android KitKat is considered to be able to run on older devices with atleast 512 mb ram and 1 ghz dual core and having met the requirements by s advance,maybe samsung will release stock 4.4(KitKat) by next year but we could taste it with CM 11 being ready by january(IF).
I am bad at smileys.

cm 11 :good:

4.4 and RAM

Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app

butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
I think so, the spare RAM should make the ROM about 3 times more spare RAM, and quite fast.

butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Short answer.. your way off..
Long Answer..
The big change is that the system now degrades gracefully on low resource devices.. so things like animations and textures are reduced to maintain the systems overall performance even on low resource devices.. versus say jellybean and ICS which simply tried to run regardless even on the original G1.. bringing the entire system down to a crawl (this is a vastly oversimplified version of a portion of what is going on in 4.4 and is not meant to be exhaustive explanation)
The second part of your question is why I want to strangle every marketing person from the beginning of time.. just because the system CAN operate with less ram does NOT mean that it is not USING all of the ram in your device.. the system will invariably use up as much as it can get its hands on (and still try to grab some more!)

OK, I think I get it! Thanks for the help
Sent from my HTC Desire C using xda app-developers app

Improved memory management should (in theory) also help the Tegra 3 chip since it has slow single-channel ram.