Hi,
first, I know that RAM is separated to several parts, one for Android OS + apps and other for low level hardware, RIL, GPU, hardware acceleration, camera etc. No need for that kind of answers here, thank you
So, I know that on some kernels (on other devices) there is way to map more RAM to user by reducing GPU RAM, freeing some memory banks from camera etc.
In that case it is possible to have more available RAM for user and applications in trade for possible HD video stutter, worse 3D performanse and/or no HD video recording. Also, it doesn't mean that only GPU RAM banks can be decreased, maybe something other can be modified to free more RAM.
For example, HTC Sensation ROM has that kernel with more RAM but no FullHD recording.
Similar thing is with Optimus 2x ROM that gives 64MB of RAM more than stock values.
Xperia Ray (with ICS kernel in this case) also has 15 MB of RAM more than usual. Not a big improvement but still it is possible.
There are numberous cases with such modifications and tweaks (from Galaxy W, Galaxy S Plus, to Motorola Atrix, Galaxy S and so on...)
Our Xperias have 1GB of RAM from which 685MB is available on JB ROMs (on @letama 's 4.3 ROM is 622MB), where with 3.0 kernel some ROMs have 715MB of user available RAM.) From one older (ICS for Xperia 2011), but still relevant Xperia blog entry there is one quote that somewhat explains one bit of that:
Increased RAM usage
In general, it can be said that the RAM is the working memory in the phone, used by running processes in contrast to the flash memory, which is mainly used to store things. As you might understand, this is a simplified explanation and might not be entirely true in all cases. However, it can serve as a help to understand the difference between the RAM and the flash memory of the phone. To see how much RAM is currently used, go to Applications in the Settings app of your Xperia™ phone.
Now, let’s look at how the RAM is used. Out of our 512MB RAM, about a third is used for functions that require a dedicated memory slot to operate fast enough. For example, this is the case for certain multimedia functions. The remaining space, which is at least 340MB, is reserved for the Linux user space, as required in the Android Compatibility Definition Document (CDD). Within the Linux user space, functions like the activity manager and Home screen app are running.
Click to expand...
Click to collapse
Also relevant:
Hardware acceleration means that the GPU is used to render graphics, which enables a smooth user interface. However, it also results in at need to load additional graphic libraries for certain apps, which makes them use even more RAM.
Click to expand...
Click to collapse
Additional info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Because on CM based ROMs there is no Bravia Engine, some specific Walkman album and/or video features and big chunk of users (like myself) don't need fastest 3D performance nor 1080p (which is still lagging, well until .96 source code arrives. Minding that, is it possible that in .200 builds wrong memory mapping led to FullHD stutter?) but additional RAM would be precious for multitasking and having more apps open at the same time.
Unfortunately I am out of luck regarding some tutorials or explanation how to set up kernel and tweak its memory map (because I lack of Android development knoledge) but I hope someone out there like letama, RaymanFX, DoomLord etc. can help. It doesn't meant that they must do it but maybe give us "noobs" some directions how can we start and try to do it ourselves.
Sorry for long post, I didn't want it to became "another RAM thread" because it isn't. The more explanation provided the less confusion is present Thank you for reading it until end
Regards,
switzerland92
First of all - good topic
It's obvious there is a way to increase available RAM if you look OS version on one device with same hardware but just different OS.
In Gingerbread, ICS and then in JB.
If you just compare 211 and 96 firmware there's big change.
HD video (1080p) recording is great..
So I guess it's RAM mapping which should fix in custom ROM's
But for me it's not so important how many RAM I have free, I want my RAM to be occupied and fully working to get best performance.
But in some ROMs we could see 70MB of RAM free and terrible performances.
To close this - I think Sony did a great job with 96 firmware and that's good.
Only question stays for custom ROMs
It's question for developers who really built ROMs from the beginning and do everything alone.
We have few great guys here but I doubt they will join this conversation
Sent from my LT26i using Tapatalk 4
Maybe our master @letama knows something. Really interesting topic.
Gesendet von meinem LT26i mit Tapatalk 4
Well, I don't have all the answers for this, but let me give you some hints:
In recent kernels (JB), memory allocation is handled by ion. ion is managing pools that are dedicated to specific tasks. Memory dedicated to each pool is defined by kernel, in board file for our XS (arch/arm/mach-msm/board-semc_fuji.c)
Here is what I have for mine:
#define MSM_ION_HOLE_SIZE SZ_128K /* (128KB) */
#define MSM_MM_FW_SIZE (0x200000 - MSM_ION_HOLE_SIZE) /*(2MB-128KB)*/
#define MSM_ION_MM_SIZE 0x3E00000 /* (62MB) */
#define MSM_ION_MFC_SIZE SZ_8K
#define MSM_ION_SF_SIZE 0x9000000 /* 112MB -> 144MB */
#define MSM_ION_CAMERA_SIZE 0x7000000 /* 80MB -> 112MB */
#define MSM_ION_WB_SIZE 0xC00000 /* 12MB */
#define MSM_ION_QSECOM_SIZE 0x300000 /* (3MB) */
...
Which are sony JB values except for SF and CAMERA that I had to increase for 3.4 (new drivers, consuming a bit more).
This is where you can play to try to get more free ram, but it will be difficult without impairing a function.
Regarding the 1080p issue, this has nothing to do with ram. With my same kernel and same memory allocation, issue is fixed with new sony camera blobs.
Thank you for your answer, it really helped me a lot
Is there any article or explanation for e.g. that is MSM_ION_SF_SIZE etc.? I realized for some stuff from context but most of that is unknown.
switzerland92 said:
Thank you for your answer, it really helped me a lot
Is there any article or explanation for e.g. that is MSM_ION_SF_SIZE etc.? I realized for some stuff from context but most of that is unknown.
Click to expand...
Click to collapse
SF is Surface Flinger, display driver...
letama said:
Well, I don't have all the answers for this, but let me give you some hints:
In recent kernels (JB), memory allocation is handled by ion. ion is managing pools that are dedicated to specific tasks. Memory dedicated to each pool is defined by kernel, in board file for our XS (arch/arm/mach-msm/board-semc_fuji.c)
Here is what I have for mine:
#define MSM_ION_HOLE_SIZE SZ_128K /* (128KB) */
#define MSM_MM_FW_SIZE (0x200000 - MSM_ION_HOLE_SIZE) /*(2MB-128KB)*/
#define MSM_ION_MM_SIZE 0x3E00000 /* (62MB) */
#define MSM_ION_MFC_SIZE SZ_8K
#define MSM_ION_SF_SIZE 0x9000000 /* 112MB -> 144MB */
#define MSM_ION_CAMERA_SIZE 0x7000000 /* 80MB -> 112MB */
#define MSM_ION_WB_SIZE 0xC00000 /* 12MB */
#define MSM_ION_QSECOM_SIZE 0x300000 /* (3MB) */
...
Which are sony JB values except for SF and CAMERA that I had to increase for 3.4 (new drivers, consuming a bit more).
This is where you can play to try to get more free ram, but it will be difficult without impairing a function.
Regarding the 1080p issue, this has nothing to do with ram. With my same kernel and same memory allocation, issue is fixed with new sony camera blobs.
Click to expand...
Click to collapse
Nice hex seems alot of bytes. Btw. How do I increase the bytes? Of those.. Because its hex
Sent from my LT26ii using xda app-developers app
I use native Windows calculator, when you set it on "programmer" than you can convert units (HEX, OCT, DEC, BIN).
Related
Hermes WM Roms Benchmarks
My Hermes is dead.. this isnt going to get updated again, im so sorry
One of the MOST common questions we get, is, what's the lites rom? And what's the fastest rom?
How to make your rom faster
A new program called WMRegOptimizer, which you can get here, has had noticed improvements on the speed of my phone and others.
For more detailed info and a few helpfull recommendations.
My Methods:
I take the rom, fresh from the chef, and flash it, that's it, no UC, no changes, nothing!
I run the tests unplugged, and before connecting to activesync.
All i install is my battery drain tool, and my benchmarking tool.
I dont change the Pagepool, or the cache settings, for the main benchmarks.
Below there will also be benchmarks of the rom i use, and other members of XDA, post yours up as well!
Also, attached you will find a XML you can import with Advanced config, or use in your UC, this is cache tweaks, and i will post benchmarks to show how they help.
I know that My benchmark suit isnt the best around, i chucked it together in 5min, but, as im using the same on all roms you can compare without worrying to much!
If there was any "odd" readings, aka something much higher/lower, I re benchmarked, re flashed, until I was sure its not an error I can do anything about.
About each section :
Rom name: name of the rom
Rom build: The build of the rom
idle power consumption (mA): This is the power it was draining in mA (milliamp) sitting in the power consumption tool with the backlight (at rom default), the device was not allowed to turn off ect. And i left it for 2-5min to average.
Integer: How quickly the phone performed Integer calucations, see here for more info
floating point: How quickly the phone performed floating point calucations, see here for more info
RAM Access: How quickly the phone could access the RAM
Draw Bitmaps: How quickly the phone could redraw bitmaps on the screen (graphical performance)
Main Storage read/write: How quickly the phone could read/write to the main storage.
Higher is better apart from for idle power consumption, where lower is better.
Power consumption is VERY MUCH affected by screen brightness, I should have standardised this.. but it still give an idea..
My conclusions
RBS roms are faster than Non BS
Compressed roms are slower and use more power in idle for the most part
Some roms are faster but use more idle power, and different roms have there strengths and weaknesses!
.zip has all the benchmarks so far, along with graphs.
Pagepoll tests
I decided to take 3 roms and test 6v8meg PP, the results are in the .zip
For the most part, the 8meg PP roms where faster, but has less ram (duh). I would do more tests, but it would take far to much time..
Graphs
These are out of date compared to the .zip, I will update them asap.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There ALL in the .zip, they would take up to much room to post here.
Performance XML
This file can be run with UC, or imported with advanced config.
What this does is fine tune the cache sizes to what I think gives the best performance.
Updated on 25th August
Added Power management tweaks to the XML
Updated the Cache settings.
Added tweak to remove the delay when taking pictures.
Examples:
CRCv12.9 BS naked 8meg PP pre XML benchmarks. (See that the higher pp is faster than the 6meg one in the main benchmark tests)
Integer: 181.9167
Floating Point: 5.779
Draw Bitmaps: 710
RAM Access: 1620
Main storage (write): 710.62
Main Storage (read): 3690.09
CRCv12.9 BS naked 8meg PP post XML benchmarks.
Integer:184.3587
Floating Point: 5.783
RAM Access1632
Draw Bitmaps: 726
Main storage (write)710.37
Main Storage (read)3685.66
Performance settings if you dont want to use the XML:
File system cache: Enabled
File system cache size: 2megs
File system filter cache: 8192 sectors
Glyph Cache: 128KB
What to benchmark your own rom? See this post for the program I use!
Notes: None of the tweaks in the XML is my work, apart from making it and posting it here, im just trying to make it easier for the newbies to get the most from there device!
WM 6 roms
This thread here by KarhU has benchmarks for most WM6 roms
Todo:
*Add links to rom thread in the spreadsheet.
*Work out why there is the MASSIVE increase in main memory speed on CRCv12.7 and roms based on it. (seems to be some due to some tweaks in the rom!)
If this has helped you, or you like what I do, maybe consider a small donation, anything is very gratefully received!
I'm shaking
In my chair, waiting for the results, ..... half an hour too long, get your a into g
zocster said:
In my chair, waiting for the results, ..... half an hour too long, get your a into g
Click to expand...
Click to collapse
It takes 10min per rom And i keep having to text/call mid power usage test ;/
Bravo
Awesome work, ...
Excellent job, thanks a lot !!
That all the current roms done, Ill try to make it easer for you to see what everything means tomorrow, right now I need to get working, get my Hermes back to how I like it, and do some work
Any feedback? Any roms you want me to do? any graphs? Just say!
Impressive..simply impressive..
blackout128 said:
Impressive..simply impressive..
Click to expand...
Click to collapse
Thanks you!
Now, to get the ball rolling, lets see your benchmarks!
Heres mine: CRCV12.9BC-naked 8meg PP
Integer: 181.1740
Floating point: 5.773
Ram Access: 1637
Draw bitmap: 721
Main Storage (write): 708.24
Main Storage (read): 3683.45
veyka said:
Thanks you!
Now, to get the ball rolling, lets see your benchmarks!
Heres mine: CRCV12.9BC-naked 8meg PP
Integer: 181.1740
Floating point: 5.773
Ram Access: 1637
Draw bitmap: 721
Main Storage (write): 708.24
Main Storage (read): 3683.45
Click to expand...
Click to collapse
Mine fully loaded, with MSN pushing mail, and activesync on 2003 OWA sync.
integer: 178.6745
floating pt: 5.751
RAM Access: 1600
Draw bitmaps: 565
Main Storage Write: 614.46
Main Storage Read 3723.64
Heres mine: PDACorner NRBSN V20 8 Meg PP
Integer: 176.8177
Floating point: 5.746
Ram Access:1626
Draw bitmap: 716
Main Storage (write):631.45
Main Storage (read): 3453.63
@ veyka!
idle power consumption higher is better or lower is better ?
dvha79_ddt said:
Dear peyka!
idle power consumption higher is better or lower is better ?
Click to expand...
Click to collapse
Lower is better! Wooops! Ill correct that in my first post. Thanks
veyka said:
Lower is better! Wooops! Ill correct that in my first post. Thanks
Click to expand...
Click to collapse
Thank you for your fast reply, This topic is real mean.
Good luck!
dvha79_ddt said:
Thank you for your fast reply, This topic is real mean.
Good luck!
Click to expand...
Click to collapse
Thanks again! Im just benchmarking another 4roms! update asap.
5 roms added! New better graphs planned for later today!
Awesome work!
Keep it up!
Any Schap's 4.40 Beta benchmark??
Nico
thank, man - you do a nice work
Thanks man very useful, I'm still on WinMo6.0 deciding where to go.
colombia7 said:
Any Schap's 4.40 Beta benchmark??
Nico
Click to expand...
Click to collapse
I can do! Ill look into getting a non locked copy!
And thanks everyone
I ran out of steam last night But ill finish off the updates for today.
So I was seeing all these ROM's now that the world is unlocked for the WFS.
"This is the fastest ROM around!", etc, etc...
Talk is just that so we decided to have a little fun.
This is just a straight up 1/4 mile race lads and lassies!!!
I don't have much to say much about aesthetics, logical placement of things, or other details although I did spend some time on each ROM and was familiar with a few to begin with. Again. It's a drag race by the clock only!
I proposed and carried out the following:
-I intended to make the field level as the foundation of a house my good ol' man himself would build.
- The ROM's got tested out of the box. No additional flashing of this or that to improve this or that.
- I used the same Wildfire S GSM A510e, and CLEAN formatted Adata Class 10 16 GB SD card to perform both Antutu and Quadrant Standard benchmarks on all ROM's. Consistant SD r/w results are part of what makes a ROM smoke. Especially using DATA2SD, LINK2SD, A2SD, etc. This card was formatted in the following manner:
Partition 1 - Primary/Active FAT32 - 13.5 GB
Partition 2 - Primary - Ext2 - 1.0 GB
Partition 3 - Primary - Linux Swap - 512 MB
- I ran each test three times and choose the highest score in both the Antutu and Quadrant tests.
- No software was added to the ROM's by myself other than a file manager if I needed one to install Antutu and Quadrant Standard. [/I]
-This was a speed and performance test only and only within the confines of the testing platforms at hand.
-I clocked all ROM's at 806mHz/806mHz with performance governor and just let them run flat out.
-I tested all equally and didn't put one in just to be impartial, not that I stood a chance.
The ROMs and their Developers:
HenseMod4 By Henry_01
A slick HTC Sense based ROM heavily modified and updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.sense 1.0 By benjamingwynn
A clean well thought out Sense based ROM with updates galore.
m1ndh4x8r EU GB 2.3.5 By m1ndh4x8r
The standard for HTC Sense based ROM's. A Story I don't need to retell.
TurboFire Beta 9 By DJPC
A stripped down drag racer. This ROM weighs in as the smallest of the HTC Sense based ROMs.
Unofficial CyanogenMod7.2.0 Port By Alquez
The standard for Non-Sense based ROMs. This is the smallest sized ROM in the field and it again doesn't need it's story told.
The Results:
HenseMod4 By Henry_01
.sense 1.0 By benjamingwynn
m1ndh4x8r EU GB 2.3.5 By m1ndh4x8r
TurboFire Beta 9 By DJPC
Unofficial CyanogenMod7.2.0 Port By Alquez
Not surprisingly the lightest weight ROM came out on top by a hair in the Antutu Benchmark and by quite a bit in the Quadrant Standard score.
Second going to m1ndh4x0r's ROM, the kernel of which was used in all the other HTC Sense based ROMs. I guess if it's your game you might as well be the best at it if only by a hair over Henry_01 and his third place HenseMod4.
The other three ROM's came in really really close and at the end of the day, aside from the standout Quadrant score by Alquez, the pack was tight right to the end.
Kudo's to our three newest developers BenjaminGwenn, Henry_01, and DJPC (who might I add doesn't even own a Wildfire S and developed his ROM using the eyes and ears, and logcat files of testers alone!).
That's it folks. I'm ROM'ed out, typed out and seeing triple from this.
The drag race is over for another year.
Hope you enjoyed yourself and will give all these ROM's a run for their money and pick which one is best for you. They all deserve a serious look.
PS If you are a developer or end user who liked the idea of me spending the time and resources to perform these tests please do click thanks!
Great idea mate.
I'm well looking forward to the results
Hope all the devs get involved.
It will be good to know how each rom performs
Sent via Tapatalk
Contest entries extended until Sunday, January 22'nd at 11:59 pm GMT-5 (EST)!!!
Will the roms be tested at their stock clocks or will they be clocked to the same frequency?
I ask because i clock mine to 600MHz because some people have had issues with the often 800MHz default clock used in other roms
djpc said:
Will the roms be tested at their stock clocks or will they be clocked to the same frequency?
I ask because i clock mine to 600MHz because some people have had issues with the often 800MHz default clock used in other roms
Click to expand...
Click to collapse
Good poing that I forgot to enter in the criteria.
Clocks will all be set to 806/806 Performance.
Thanks DJPC
We need a way to thank from the XDA app... Thanks anyway DS. Looking forward to the results.
HTC Wildfire S | CyanogenMod 7.2
Sent from XDA app
drsjlazar said:
We need a way to thank from the XDA app... Thanks anyway DS. Looking forward to the results.
HTC Wildfire S | CyanogenMod 7.2
Sent from XDA app
Click to expand...
Click to collapse
Just use tapatalk app instead, the thanks button works on that app.
Sent via Tapatalk
I am looking forward to see the results...
I am using latest m1ndh4x8r's Rom and I am quite satisfied, but I want to see how other roms perform, in compares with the one I use...
good idea mate... keep up...
Today is the day! Let's get ready to rumble!!!
Time to start testing some ROMs
Everyone else. Just sit back and watch the results!
Awesome!
*supports cm7*
Haha great! Looking forward the results
The results are in!...
Come on up to the first post and see the results of this years ROM Drag Race!
Please don't forget to click thanks and also thanks for the developers who put in so much of their time and energy to come up with these ROM's!
Here it is...The results!!!
Read post #24
THIS POST IS JUNK. SEE POST #24 WITH MY CONCLUSIONS BASED ON A BETTER UNDERSTANDING OF THE DATA.
Going by the Antutu total score results, there is no reason to chose one ROM over another based on performance. The standard deviation is +/-1%. But, looking at Antutu category-by-category is a different story. Here are the lowlights/highlights:
* HenseMod4 -20% in SD card write
* .sense 1.0 -13% & -14% respectively in Database IO & SD card write
* m1ndh4x8r is as average as could be in all categories
* TurboFire +16% in SD card write
* CM7 +13% in RAM and +18% in SD card write
So, the big story here is variation between the ROMs in SD card write speed. There is a cumulative ~35% improvement in SD card write speed to be gained with the non-Sense ROMs.
Quadrant shows significant variation from mean:
* HenseMod4 -13%
* .sense 1.0 -5%
* m1ndh4x8r -3%
* TurboFire -1%
* Cyanogen7 +23%!!!!!
Now I'm even more glad to be running CM7. Thanks, again d33ps1x and Alquez!
Hehe you spelt me name wrong
Sent from my HTC Wildfire S A510e using xda premium
I knew the boss would win, what I supported! Love ya CM n' Alquez!
benjamingwynn said:
Hehe you spelt me name wrong
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Hey I lost my screenshots too!
Can you send me your lock screen and main screen?
Thanks dude.
BTW Name fixed!
CafeKampuchia said:
Going by the Antutu total score results, there is no reason to chose one ROM over another based on performance. The standard deviation is +/-1%. But, looking at Antutu category-by-category is a different story. Here are the lowlights/highlights:
* HenseMod4 -20% in SD card write
* .sense 1.0 -13% & -14% respectively in Database IO & SD card write
* m1ndh4x8r is as average as could be in all categories
* TurboFire +16% in SD card write
* CM7 +13% in RAM and +18% in SD card write
So, the big story here is variation between the ROMs in SD card write speed. There is a cumulative ~35% improvement in SD card write speed to be gained with the non-Sense ROMs.
Quadrant shows significant variation from mean:
* HenseMod4 -13%
* .sense 1.0 -5%
* m1ndh4x8r -3%
* TurboFire -1%
* Cyanogen7 +23%!!!!!
Now I'm even more glad to be running CM7. Thanks, again d33ps1x and Alquez!
Click to expand...
Click to collapse
You know. I love waking up in the morning crying and wearing my wasted dragon costume and seeing something like this! (Follow another thread for inside joke)
Thanks. Great breakdown.
Damn, well done to the other devs on their roms. As a tip to those whose roms are suffing on sd card performance, the read ahead values make a huge difference to performance, but leave them as init.d scripts not init.rc as I have had some users reporting issues with higher values.
Looks like I need to get some more tweaks into the rom yet, unfortunately I ran out of time trying to get a wifi fix and could not get some last minute optimization in.
Post a picture of the dragon costume?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your phone’s RAM is a very essential component which plays a vital role in the speed and the performance. if you have more RAM, it means the processor have more storage capacity to process more and more temporary functioning files, and hence it can freely work which ensures the device is fast enough. But if your RAM is low, the processing power of the device is affected. Like if you have a low RAM< you won’t be able to play high end games on your Android Smartphone, or even ti might lag while doing simple tasks such as seeing a video, typing a text etc. So if you are suffering from low RAM, and want to get rid, you are at the right place. By reading this post you will be able to know how could I increase the RAM
ROEHSOFT RAM EXPANDER :
This RAM expander app is one of the best app available in the play store which allows you to easily increase the RAM of your Android smartphone. So let’s begin with the process toincrease RAM using ROEHSOFT RAM EXPANDER. Have a look at some of the features of this app to increase RAM of your device.
Swap memory file upto 4 GB ( In simple words it can increase ram by 4 GB depending on your device and memory card too)
Widget for PNP swap
Detailed analysis of your memory and details about it
Swappiness kernel parameter already set.
Very easy to use and create swap file and really simple interface
It will work with most of the Android devices.
Pre-requisites :[/COLOR]
Here is a list of things we will need before starting the process to increase RAM.
A rooted android phone, so if you haven’t yet rooted your phone first root your device as this method only works with root access to your device.
ROEHSOFT RAM EXPANDER app, you can get this app from play store but you need to know that this is not a free app. (though you can number of apk files for this app but most of them won’t work due to license issues but you can try them, if they worked it will be your luck ).
An external memory SD card installed on your phone.
How to Use ROEHSOFT RAM Expander :
So file the steps below to increase the RAM of your Android smartphone now.
Install the app on nokia x to increase RAM
Now after installing the app choose your default language.
Now to increase RAM create a SWAP file by clicking on the SWAP Active and enabling it
After the process is finished just click on the grey colored box and activate the swap file created.
Congratulations you have successfully increased the RAM of your Android smartphone.
This increased ram will not show in the task manager but you can feel the change with the overall performance of the device which seems to be boost up. If you already have a decent ram them got might need to run some very heavy game to know the difference in performance. So I hope this post helped you in increasing the RAM of your Android smartphone.
http://forum.xda-developers.com/attachment.php?attachmentid=2778001&stc=1&d=1401793417
Click to expand...
Click to collapse
why is this here it should be in nokia x forum
gurram prashanth said:
why is this here it should be in nokia x forum
Click to expand...
Click to collapse
It is now....
justmpm said:
It is now....
Click to expand...
Click to collapse
thanks man
gurram prashanth said:
thanks man
Click to expand...
Click to collapse
I followed this and got my device hard bricked......please do not swap....u'll get your device bricked(hard bricked).....the one who posted this must be punished....
Why people not clarifying it as someone already bricked his device on following this thread.
Just tried this with a 512 MB swap file on a rooted Nokia X with Gapps and Google Now Launcher.
Feels a bit smoother now. Had no real issues. Only SuperSU seems not to be 100% reliable when temproary setting the app to allow root access. Changed it to be permanently root. Now works fine.
My tab s 8.4 eat a lot or ram always 2gb in use wile their is no app is running? Why is that?
a lot of apps running on background
1 GB is also reserved for vnswap
vnswap what that mean?
It's just caching.This is a part of efficient memory management and not a problem. People who think it is don't understand usually. For common tasks, storing info in RAM is more efficient. System doesn't need to get it from SD which takes longer and uses more power.
That's a pretty simplistic way to put it but you should let your OS manage memory and use that 3GB to its fullest.
texaspledge said:
It's just caching.This is a part of efficient memory management and not a problem. People who think it is don't understand usually. For common tasks, storing info in RAM is more efficient. System doesn't need to get it from SD which takes longer and uses more power.
That's a pretty simplistic way to put it but you should let your OS manage memory and use that 3GB to its fullest.
Click to expand...
Click to collapse
Well, Android is and was always using "empty" RAM as a file cache. How is this different and less efficient than Samsung's approach?
UpInTheAir said:
1 GB is also reserved for vnswap
Click to expand...
Click to collapse
Reducing the amount of VNSWAP via Synapse in your kernel to 1 doesn't seem to do anything to the amount of RAM in use. So, do I something wrong or do I still don't get it?
EDIT: Sorry if my posting reads a bit harsh, it is certainly not meant that way Language barrier and stuff...
TheGoD said:
Reducing the amount of VNSWAP via Synapse in your kernel to 1 doesn't seem to do anything to the amount of RAM in use. So, do I something wrong or do I still don't get it?
EDIT: Sorry if my posting reads a bit harsh, it is certainly not meant that way Language barrier and stuff...
Click to expand...
Click to collapse
It's not supposed to.
Reading from v1.4 Change-log
synapse: Memory: VNSWAP control (1>1024 MB - Unable to disable (reset) / set size to 0 yet)
Click to expand...
Click to collapse
It does change the size of the VNSWAP but doesn't reclaim the reserved RAM yet. Need to find a way as I quoted. I don't want to disable it fully in compile, i want to have tweakable options
Anyway, is OT from OP question and instead kernel development related.
rowihel2012 said:
My tab s 8.4 eat a lot or ram always 2gb in use wile their is no app is running? Why is that?
Click to expand...
Click to collapse
I think it's probably some rogue app.. Go to Settings --> Application Manager and "Running Application" to see what's running int he background. But if it does not slow down your tablet, it should be fine. Just like my Mac, it uses tons of memory but OSX have such great memory management that my Mac still runs well.
TheGoD said:
Well, Android is and was always using "empty" RAM as a file cache. How is this different and less efficient than Samsung's approach?
Click to expand...
Click to collapse
Huh? That doesn't make sense at all. Android doesn't do that, it's probably more of rogue app. See https://developer.android.com/tools/debugging/debugging-memory.html
great,now my tablet plays rogue on its own...lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
texaspledge said:
It's just caching.This is a part of efficient memory management and not a problem. People who think it is don't understand usually. For common tasks, storing info in RAM is more efficient. System doesn't need to get it from SD which takes longer and uses more power.
That's a pretty simplistic way to put it but you should let your OS manage memory and use that 3GB to its fullest.
Click to expand...
Click to collapse
What he said. Every android device I get has a thread with people complain about ram usage. Android is based on Linux. Unlike Windows, Linux uses as much ram as possible all of the time to run smoother.
http://www.linuxatemyram.com/
pretty much as the title.
i dont like the 1.3ghz clock speed and would like to change it to 1.5, tried SetCPU but it couldnt change anything.
so anyone got a way that works?
For this to work, we would need to compile a new kernel with added frequencies and voltages. But from what I've read this is not so simple on MTK devices.
Skickat från min Elephone P8000 via Tapatalk
Yes, overclocking is pretty hard on MTK kernels. sometimes even when you successfuly up the voltages and clocks and it shows on userspace too (cpu-z etc.) it still works at older freqs under the hood.
pitrus- said:
For this to work, we would need to compile a new kernel with added frequencies and voltages. But from what I've read this is not so simple on MTK devices.
Skickat från min Elephone P8000 via Tapatalk
Click to expand...
Click to collapse
It would be the only way to turn the weak MT6753 into the much more powerful MT6752 (overclocking from 1.3GHz to 1.7Ghz) though... If a kernel dev is ever to concern himself with this device ... it would be very interesting indeed...
Stevethegreat said:
It would be the only way to turn the weak MT6753 into the much more powerful MT6752 (overclocking from 1.3GHz to 1.7Ghz) though... If a kernel dev is ever to concern himself with this device ... it would be very interesting indeed...
Click to expand...
Click to collapse
As far as I can see
#define CPU_DVFS_FREQ0 (1495000) /* KHz */
#define CPU_DVFS_FREQ1 (1300000) /* KHz */
#define CPU_DVFS_FREQ2 (1235000) /* KHz */
#define CPU_DVFS_FREQ3 (1170000) /* KHz */
#define CPU_DVFS_FREQ3_1 (1144000) /* KHz (for 6753 FY)*/
#define CPU_DVFS_FREQ4 (1040000) /* KHz */
#define CPU_DVFS_FREQ5 (819000) /* KHz */
#define CPU_DVFS_FREQ6 (598000) /* KHz */
#define CPU_DVFS_FREQ7 (442000) /* KHz */
#define CPU_DVFS_FREQ8 (299000) /* KHz */
1,5 Ghz shouldn't be a problem. As soon as I get CWM running (it actually already compiles but I'm still facing some issues) I'll start working on CM and on a custom kernel.
BlueFlame4 said:
As far as I can see
#define CPU_DVFS_FREQ0 (1495000) /* KHz */
#define CPU_DVFS_FREQ1 (1300000) /* KHz */
#define CPU_DVFS_FREQ2 (1235000) /* KHz */
#define CPU_DVFS_FREQ3 (1170000) /* KHz */
#define CPU_DVFS_FREQ3_1 (1144000) /* KHz (for 6753 FY)*/
#define CPU_DVFS_FREQ4 (1040000) /* KHz */
#define CPU_DVFS_FREQ5 (819000) /* KHz */
#define CPU_DVFS_FREQ6 (598000) /* KHz */
#define CPU_DVFS_FREQ7 (442000) /* KHz */
#define CPU_DVFS_FREQ8 (299000) /* KHz */
1,5 Ghz shouldn't be a problem. As soon as I get CWM running (it actually already compiles but I'm still facing some issues) I'll start working on CM and on a custom kernel.
Click to expand...
Click to collapse
Great! i follow!
Inviato dal mio ZP998 utilizzando Tapatalk
1.5ghz is, originally, a default frequency already present in kernel which only was cut off by elephone, so it shouldn't be a real problem to re-enable it
viel erfolg, blueflame4
seadersn said:
1.5ghz is, originally, a default frequency already present in kernel which only was cut off by elephone, so it shouldn't be a real problem to re-enable it
viel erfolg, blueflame4
Click to expand...
Click to collapse
Finally!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And you know what? It was just a motherf typo that screwed my Board Config!
yay!! everything working (for recovery), incl. adb support?? nice, just nice respect and thx
ahh, "it are the small things in life"
seadersn said:
yay!! everything working (for recovery), incl. adb support?? nice, just nice respect and thx
ahh, "it are the small things in life"
Click to expand...
Click to collapse
Thanks! ADB works as well as all keys. Mountpoints are not created yet but that's easy to fix.
If everything goes well I'm sure I can release tomorrow!
Luckily the SoC supports fastboot so it's a breeze to test new builds.
BlueFlame4 said:
Thanks! ADB works as well as all keys. Mountpoints are not created yet but that's easy to fix.
If everything goes well I'm sure I can release tomorrow!
Luckily the SoC supports fastboot so it's a breeze to test new builds.
Click to expand...
Click to collapse
Question: wouldn't it have been easier/faster to use the CWM offered on Elephone forums?
sure, but it's an stone age old version. it's always good to have options and a choice.
where would we be when there wouldn't be people like him, giving their valuable time for developing new stuff, for others?
Stevethegreat said:
Question: wouldn't it have been easier/faster to use the CWM offered on Elephone forums?
Click to expand...
Click to collapse
My ultimate goal is to compile a fully working CM12.1 from source and in order to do that I have to configure the device tree properly. CWM is more or less just a by-product and not the end result.
BTW feel free to contribute if you have spare time! https://github.com/visi0nary/android_device_alps_k05ts_a
seadersn said:
sure, but it's an stone age old version. it's always good to have options and a choice.
where would we be when there wouldn't be people like him, giving their valuable time for developing new stuff, for others?
Click to expand...
Click to collapse
Yeah I understand that point. I mostly asked of it as a way to save time. Still I'm glad that there are people working on it.
@BlueFlame4 : Thanks for posting the device tree, always useful to have it public so that many can contribute.
Hi, guys!
Any news on this? Could anyone do it?
I was really excited with the possibility of overclocking the P8000, however, I am not familiar on how to develop such things...
Thanks.
Rizera said:
Hi, guys!
Any news on this? Could anyone do it?
I was really excited with the possibility of overclocking the P8000, however, I am not familiar on how to develop such things...
Thanks.
Click to expand...
Click to collapse
I'd call this perfect timing. There are news but not (yet) regarding overclocking. My CM build just compiled without errors. I'm still using the precompiled kernel though and will flash it when I'm home tonight. Don't want to give out ETAs though. So if it boots, I'll make the kernel build from source as well but I don't expect it to boot to be honest since this is the very first build
Edit: Well, it doesn't boot but I have an idea what might be the problem...
Edit2: Okay, I fixed some errors but it still doesn't boot. Gonna look into it within the next days. Good night
Good luck and we'll be following your progress!
charliepie said:
Good luck and we'll be following your progress!
Click to expand...
Click to collapse
Thanks, it's always a pleasure to get feedback!
BlueFlame4 said:
I'd call this perfect timing. There are news but not (yet) regarding overclocking. My CM build just compiled without errors. I'm still using the precompiled kernel though and will flash it when I'm home tonight. Don't want to give out ETAs though. So if it boots, I'll make the kernel build from source as well but I don't expect it to boot to be honest since this is the very first build
Edit: Well, it doesn't boot but I have an idea what might be the problem...
Edit2: Okay, I fixed some errors but it still doesn't boot. Gonna look into it within the next days. Good night
Click to expand...
Click to collapse
Are you able to activate touch at Kernel to use touch recovery? Nice to hear that you are working on cyanogen mod good luck!
mark2410 said:
pretty much as the title.
i dont like the 1.3ghz clock speed and would like to change it to 1.5, tried SetCPU but it couldnt change anything.
so anyone got a way that works?
Click to expand...
Click to collapse
http://forum.xda-developers.com/ele...ernel-visi0narys-kernel-t3226081/post63318857 :highfive:
alfredxyz said:
Are you able to activate touch at Kernel to use touch recovery? Nice to hear that you are working on cyanogen mod good luck!
Click to expand...
Click to collapse
Will have a look at it soon.