Database Info

samsung s5230 whit android : it's possible?

i have samsung s5230 whit so samsung and it has a 200 mhz processor
and 144 mb memory and can i install android on this cell?

You know about games for PCs - they have minimum requirements. If your PC is slower than minimum requirements, game will work, but very slow. Android too will work with slower devices than requirements, but very slow. Your device is really too slow.
For Android minimum requirements:
1. ROM - at least 512 MB (now possible to boot from SD or any card);
2. CPU - at least 528 MHz;
3. RAM - at least 256 MB;
4. Internal memory - at least 130 MB;

Actually it is possible(anything is ).....but this feat would require extensive coding and a way to flash android.....also even if it boots...it will be a heck lot slow and would be just for show

[Q] are WM apps capped from using 25mb+ RAM?

hey fellow XDA WM devs and users and forum people,
Greetings,
so I am asking whether not WM devices are capped on using 25+mb of RAM for each app...
If so, can I assume that this is the reason why we cannot have stunning graphic games just like the other compatitor platforms (iOS, Android) ??
also, a reply tweet from one of my favourite game dev:
http://twitter.com/Isotope244/status/16152606483
any comments or answers are greatly apprerciated
Kind Regards

Processes in winmo can only access 32 mb of virtual memory (with a max of 32 processes). There's normally at least 7 mb or so of memory allocated to dll's for all processes (sometimes more). 32-7=25 mb. I think that's what the developer is talking about. This is changing with WP7, where all process will have full access to 1 GB of virtual memory (limited by the amount of availabe RAM).

Farmer Ted said:
Processes in winmo can only access 32 mb of virtual memory (with a max of 32 processes). There's normally at least 7 mb or so of memory allocated to dll's for all processes (sometimes more). 32-7=25 mb. I think that's what the developer is talking about. This is changing with WP7, where all process will have full access to 1 GB of virtual memory (limited by the amount of availabe RAM).
Click to expand...
Click to collapse
thanks farmer tad for your reply....
now its all clear to me
thanks.
(oh lol... then what's thhe point of phones having all those extra RAM while the OS cannot use them, at all?)

[Q] RAM management - Swap, Compcache, Memory Manager

I did a cursory search of the forum, but did not really find anything that answered my questions to my satisfaction. Anywho, I would like to gauge other users' opinions of how they run their particular memory management on their phones. From what I've gathered so far between the xda forums and cyanogenmod wiki, the hierarchy of how memory space is managed by the OS is as follows:
1. Compcache (if using compcache & backing swap)
2. Swap
3. Memory Manager (MM)
In any use-case scenario, I believe that once Compcache and/or Swap are exhausted, MM steps in and kills off processes with high OOMs. Frequency of Compcache/Swap is regulated by "swappiness", which can be set to a value [0-100] (lower values correspond to less paging out by the OS, and visa-versa). What I am still concerned/confused about is the following:
A. To what extent does the scaling of swappiness affect paging? Is there a ratio between swappiness and the number of pages stored/retrieved per tick?
B. If the above hierarchy is valid, then when is the MM activated to kill processes? Does this only occur if the worst-case is reached (RAM and Compcache/Swap partition are filled)?
C. My handset (HTC Hero CDMA) has 195204 KiB of RAM. A quick browse of that phone's forum has shown me that most users keep their swap partitions between 32-64 MiB. A number of users within that forum have also mentioned that raising swap size beyond those values can lead to performance degradation. Is that due to how the Android kernel functions? I know that in a desktop OS environment (Windows/OS X/Linux), swap partitions can be as large as users want them to be, and that there is no performance degradation (with respect to swappiness, that is).
Well, I guess that's all of my lingering concerns/questions. Any input will be greatly appreciated. Thanks.

[INFO][SHARE] What is zRam in Kernel?

Some budding devs like me and some others have asked this question and got this answer!
Firstly I want to thanks all who supported me!
My Parents for buying me an Android Device and Supporting
-CALIBAN666- for his thread
franciscofranco for his definition on zRam
abhisahara
Sniper Killer
And all those whom I have forgotten to mention!
Originally posted by Wikipedia
Q: What is zRam?
A: zRam is a module of the Linux kernel, previously called "compcache". zRam increases performance by avoiding paging on disk and instead uses a compressed block device in RAM in which paging takes place until it is necessary to use the swap space on the hard disk drive. Since using RAM is faster than using disks, zRam allows Linux to make more use of RAM when swapping/paging is required, especially on older computers with less RAM installed.
Google has also said to enable zRam as default for Chrome OS Devices!
Click to expand...
Click to collapse
Originally posted by franciscofranco
The zram module creates RAM based block devices: /dev/ramX (X = 0, 1, ...).
Pages written to these disks are compressed and stored in memory itself.
These disks allow very fast I/O and compression provides good amounts of
memory savings.
Basically is for storing swapped pages into compressed memory ram.
Click to expand...
Click to collapse
-CALIBAN666- said:
I think its better to Post this here,when its not better,than sorry!!!
-----------------------------------------------------------------
Once a brief statement for those who are not traveling so long in the Android scene:
ZRAM = ramzswap = Compcache
In order to explain more precisely ZRAM first need other terms are more clearly defined:
Swap can be compared with the swap file on Windows. If the memory (RAM) to complete the PC the data that are being used not actively outsource (eg background applications) so as to re-evacuate RAM free. To this data is written to a hard disk. If required, this data is then read back from there easily. Even the fastest SSD is slower than the RAM. On Android, there is no swap!
In ZRAM unnecessary storage resources are compressed and then moved to a reserved area in the fixed RAM (ZRAM). So a kind of swap in memory.
This Ram is more free because the data then only about 1/4 of the former storage requirements have. However, the CPU has to work in more because they compress the data has (or unpack again when they are needed). The advantage clearly lies in the speed. Since the swap partition in RAM is much faster than this is a swap partition on a hard drive.
In itself a great thing. But Android does not have a swap partition, and therefore brings Android ZRAM under no performance gain as would be the case with a normal PC.
In normal PC would look like this:
Swap = swap file (on disk) -> Slow
ZRAM (swap in RAM) -> Faster than swap
RAM -> Quick
With Android, there is no swap partition, and therefore brings ZRAM also no performance boost.
The only thing that brings ZRAM is "more" RAM. Compressed by the "enlarged" so to speak of the available memory. That's on devices with little RAM (<256MB) also pretty useful. The S2 has 1GB but the rich, and more than. There must not be artificially pushed up to 1.5 GB.
After you activate the ZRAM also has 2 disadvantages. The encoding and decoding using CPU time, which in turn has higher power consumption.
Roughly one can say (For devices with more than 512MB RAM):
Without ZRAM: + CPU Performance | + Battery | RAM
With ZRAM: CPU Performance |-Battery | + RAM
For devices with too little RAM so it makes perfect sense. But who shoots the S2 already be fully complete RAM and then still need more?
Check whether you can ZRAM runs in the terminal with
free or cat / proc / meminfo
I hope it helps to understand zRam!!!!
Click to expand...
Click to collapse
So basically zRam module in kernel increases and optimizes performance!
I didn't write all this information, I just compiled it together in one thread for ease :fingers-crossed:

But making it work is an headache.. you have to add LZO(Lempel–Ziv–Oberhumer) compression through menuconfig and then run zRam scripts through init.d and what not..

robowarrior1377 said:
But making it work is an headache.. you have to add LZO(Lempel–Ziv–Oberhumer) compression through menuconfig and then run zRam scripts through init.d and what not..
Click to expand...
Click to collapse
This thread is a information share thread
It is not a thread in how to enable it in your kernel -_-

Thanks for the info
Sent from my GT-N8000 using xda premium

Zram = extravagant battery
so it makes wasteful battery zram?
excuse me if my English is poorly

gj man thanks for info very helpful :good:

Change the first line of the thread.

[DEV][ROM] Help with Building Vanilla Android 13 GSI with 16GB RAM and 24GB Swap!!

Hey XDA community!
(I wasn't sure what tags to type and where to post pardon me. I had read the posting guides...)
I'm reaching out to you all for help with building Vanilla Android 13 GSI on a system with limited RAM. Unfortunately, I'm unable to upgrade my RAM due to various constraints. Here's a breakdown of the issue I'm facing:
Memory Consumption and Terminal Closure: When I start the build process, everything seems to work fine initially. However, after approximately 3 minutes, the terminal abruptly closes itself. During this time, the memory consumption reaches its peak, utilizing nearly all available RAM. Next the terminal to close unexpectedly.
High RAM and CPU Usage: Throughout the brief duration that the build process runs, the RAM and CPU usage remain consistently high. This behavior contributes to the subsequent closure of the terminal.
Limited Swap Usage: Despite having a sizable swap space of 24GB, the swap usage remains within 7.5GB limit. It doesn't exceed this threshold and the terminal closure occurs.
Given the constraints preventing me from upgrading the RAM, I'm seeking your expertise to find alternative solutions or workarounds for this issue. I'm open to suggestions, such as optimizing the build environment, modifying specific configuration parameters, or implementing any strategies to stabilize the build process within the limited resources available.
Your valuable insights, experiences, and troubleshooting suggestions would be greatly appreciated. Together, let's explore different avenues and find a way to successfully build the Vanilla Android 13 GSI on this system configuration and if its useful to know I'm on Ubuntu 23.04 LTS and 8GBx2 DDR4 2400Mhz RAM.
Thank you for your support and contributions!
Best regards,
FiniteCode