In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
While I think having snapshot, replication, 100% consistency, and dedup capability would be the coolest thing on a phone, I think the ZIL would burn up the sd quicker and the resource utilization would eat battery and memory for the transactional caches to make it practical
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
My only thought is: "why?". I have every app I want installed and still have 102MB available. Given just how much more memory this has than the G1's of yore, I don't really see much of a reason for AppstoSD, especially since Google is releasing their own implementation *soon*.
I was already down to 29 Meg on my internal memory.
I'll be happy when Google implements a2sd. I can't see it being any different than what a2sd us doing though.
Just make sure you have a class 6 card.
Down to fairly minimal memory as well, here.
as to 'why' over conventional a2sd ... the in-built memory is faster than even a class 6 card. A hybrid zpool will allow the faster memory to cache the slower memory (normally, a hybrid zpool combines a SSD with a hard drive pool).
Ah, didn't realize people were having problems with it. Even so, Google has announced that they're working on it themselves and since it will be an actual part of the Android OS, rather than something hacked on, I imagine it'll be a better implementation that whatever we can do. I'll be waiting for that up and coming android release.
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Click to expand...
Click to collapse
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Which memory are we talking about, primary or storage memory? If memory serves me correctly, the current os can only 256MB of primary memory but that will be increased to the full 512 in a later OTA update. I thought I saw some thread flying around here about that.
Amdathlonuk said:
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Click to expand...
Click to collapse
You almost proved his point. 33MB is a ****ty size for a theme - get a better Themerto follow. Hell, most themes for Windows aren't that big.
-bZj
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
How on earth can you possibly make this judgment? Have you ever hear of cache? What about app data? Not to tout my own app (see sig), but the reason I created it was because my myTouch, with all of its storage, would run very low the regular basis. Besides, I like to download apps, both free and paid. Why should I be limited? Personally, I never even came close to filling up my 500MB ext partition on my myTouch but could easily have 50-100MB of cache in just a few days. I think having a GB of internal would suffice. It would allow me to comfortably add as many apps as I please and at the same time, not think about cache and data on the daily basis. $575 and I'm still going to have to hack a2sd on to this. I hate that. I'd much rather use internal storage.
Personally, I'm all for it. If nothing else, it would be one hell of a proof of concept and would likely be useful especially to those who like to run their devices lean and fast. There are too many nice things to say about ZFS, so I'll just say this: it's only a matter of time and what better time than now?
But I don't think it would happen, for the same reason ZFS hasn't been ported to linux, incompatible licenses.
http://zfs-fuse.net/
Can we get the ball rolling on this?
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
kingklick said:
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
Click to expand...
Click to collapse
So what's the Kingnexus kernel have?
cyanogen said:
So what's the Kingnexus kernel have?
Click to expand...
Click to collapse
+1 .... and how does it relate to ZFS (y on earth) and apps2sd?
~enom~
lmao you pissed of cyanogen ! xD
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
Ever hear of games? Seriously, making a statement like this is just plain ridiculous. Homerun Battle 3D is over 30MB in and of itself. Yes, believe it or not, people actually use their nearly $600 3.7" screen for something other than reading email, of which I do plenty. So yes, I hacked apps2sd onto my Cyan ROM and it runs beautifully. I can't even tell the difference between this and internal it's so smooth. By the time Google releases a viable apps2sd the N1 will be yesterday's news. Internal storage and capacitive buttons = fail on the N1. Otherwise, kick ass device.
I never touched the kernal on alpha7 just added a s.d>placeholder in system int.d folder got apps2sd and the rest was set. Did not know kernal was part.
Hope the kernal is good.
Related
I'm way out on a limb right now checking out a few different things for v0.30. A lot has been learned with v0.20 and will be applied.
So my question is:
If I can find a way to eliminate Extended Rom and turn it into either Storage Memory or Program Memory (or both) which is preferred?
BTW, I've already been able to increase Storage Memory to over 60MB (See attached Image)...
kyphur said:
I'm way out on a limb right now checking out a few different things for v0.30. A lot has been learned with v0.20 and will be applied.
So my question is:
If I can find a way to eliminate Extended Rom and turn it into either Storage Memory or Program Memory (or both) which is preferred?
Click to expand...
Click to collapse
Program memory is sufficient; go for Storage
Olipro said:
Program memory is sufficient; go for Storage
Click to expand...
Click to collapse
I agree, I always run short on Storage and have enough program
Storage is the first to run low.. same as the above.
-mix
I don't agree with all of you Storage can be buyed but program memory is limited. Who knows the memory requirements in future WM6 programas.
My vote for program memory!
I'm with Viva. Low on storage? Move programs over to the card. Low on RAM? You're screwed. I say move it over to Program memory. That seems to be the most logical.
TaurusBullba said:
I'm with Viva. Low on storage? Move programs over to the card. Low on RAM? You're screwed. I say move it over to Program memory. That seems to be the most logical.
Click to expand...
Click to collapse
Many are having problems running programs from Storage Card too, some think this is the root of some sleep lockups too. How many people ever runout of Program Memory? Maybe we should do that poll. I have a hard time keeping more tan 7MB free in storage., but I have at least 15-19MB free in Program.
Hi kyphur,
i think an additional 10mb of storage memory wont be sinifcant as the 60mb you have achieved in wm6 is suffice. if we need additional storage memory we have the sd cards to take care of it.
10mb of PROGRAM MEMORY is significant as we only have under 30mb free on a fresh hard reset and after a day of use this drops to about 24mb or less. the extra 10mb will allow us to run, well in my case, many apps with ample program memory and not worry about bogging down the system.
Therefore my vote goes to program memory.
But I have one concern with using ROM storage as program memory. RAM and ROM differ signifcantly in terms of technology and the ROM has much slower access rates than RAM. Would this have a signicant impact on performance?
Nonetheless, id still prefer it to be program memory.
Alot of programs run better from internal storage than from a storage card.
As already mentioned I havent run out of progam memory yet. But there again I have never run out of storage space either.
So my vote is for two thirds storage one third programs as apposed to half and half just to be different.
By the way keep up the good work kyphur, it is much appreciated.
kyphur said:
BTW, I've already been able to increase Storage Memory to over 60MB (See attached Image)...
Click to expand...
Click to collapse
I suggest you max out that storage to see if it actually is valid or not.
Olipro said:
I suggest you max out that storage to see if it actually is valid or not.
Click to expand...
Click to collapse
That is true too, if there are any doubts as to reliabilty, stability then go with storage as well.
50 - 50 Split for everyone.
I have an Ultra 1 Gb SD Memory card Fitted (Faster than std SD) and I have Not loaded any programs on the Phone. (Everything is on the SD) but I am starting to see that my Program memory is getting Low. So I would benefit from more program memory.
I don't know if the Ultra Card makes a difference but I have very few if any Lock ups / Freezes.
I do agree with most on max the storage to see how stable it is...., but I would like both. An option to do either on the fly would be even better.
kyphur, lots of thanks for the great Roms you're cooking and developing! one question though, if Extended Rom gets eliminated in the next version, then will there be some way left to make programs like theft alert survive hard resets?
no no... I mean fill the storage up completely and then soft-reset the PDA to see if it's actually *real* space.
Program seems to make the most sense to me
Program is a good idea so is storage so that is why i vote 50/50. I am running out of both of them anyway.
I know I can use an SD card but it is not the same. SD installed apps causes the device to lock up at times.
Thank's a lot kyphur.
I'm democratic so 50 & 50 but, how wrote Olipro, before real test.
Well,split it even might be logical as few apps need to be installed in phone memory for better performance...........
My vote will be to :: release 2 ROMs ,one with more program memory and one with more storage memory and the users will decide which one to vote ...(will it be too much work releasing 2 ROMs??,if yes then Program memory wins!!)
Kyphur,
if you build two different ROMS, one with maxxed out program memory and one with maxxed out storage id like to run SPB benchmark and post the results for a better polling result....
edit... i would like more storage but dont want to lessen the performance...
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
reserved for space
flak0 said:
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
Click to expand...
Click to collapse
it's really only a matter of time on this ... once the 2.6.3x kernel is perfected for the mahimahi HW ... we'll get it. Think tank not really necessary ... as it's in the works.
~enom~
Ummmm. I thought that was the goal here:
http://forum.xda-developers.com/showthread.php?t=616383
Doubt we need the 2nd thread.
That is correct that is the goal however, until the .32 kernel is perfected is there a way to hack the current Kernel like it was done for the Dream to get the extra memory back. I am just making a suggestion. I know the only issue with the .32 kernel is the proximity sensor fails from what I have read. Can this be confirmed?
All sensors work fine with 2.6.32. Google put the sensor code in git a few days ago. I am having issues with the camera, but another person in the kernel thread said he got it working, but I can't confirm it yet.
As for the memory hack, I do not know how to do it, but the memory map and allocation are in <kernel dir>/arch/arm/mach-msm and the two files are line 959 in board-mahimahi.c and board-mahimahi.h has the memory map table breakdown.
Edit: I just got the camera working
Wont enabling that ram for program use affect the GPU(Like on the G1)?
~~Tito~~ said:
Wont enabling that ram for program use affect the GPU(Like on the G1)?
Click to expand...
Click to collapse
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
staulkor said:
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
Click to expand...
Click to collapse
Thats a bug google said would be fixed and more ram would be avail for the Nexus.
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
swetland said:
Roughly 220MB is available to userspace in the shipping build (ERD79).
Quite a lot of memory is dedicated to the radio firmware (41MB), dsp firmware (32MB), display surfaces (32MB), gpu (3MB), camera (8MB), a/v buffers (41MB), and dsp buffers. Much of this needs to be set aside for these specific tasks due to hardware requirements of very large physically contiguous buffers which can be difficult or impossible to obtain after boot once the physical memory space gets fragmented.
The big limitation though is that the Linux kernel needs to do a 1:1 physical:virtual map of general purpose memory used by the kernel and userspace (which excludes the special purpose stuff described above). This eats into the available kernel virtual address space, which is also needed for cross process shared memory used by the binder, etc. Run out of virtual memory and things get unhappy.
In 2.6.32, HIGHMEM support for ARM will allow us to avoid this requirement for a 1:1 mapping which will allow us to increase memory available to userspace without running the system out of virtual memory adddress space.
Click to expand...
Click to collapse
bofslime said:
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
Click to expand...
Click to collapse
Thanks for the details. I wasn't aware of what was causing the problem before reading this. This makes a lot of sense.
I know we have a way to move our apps to the internal nand memory, and that it's faster that way, but it seems like my class 6 sd card would be faster than the built-in sd. Is it possible to move our apps to the sd card (physical sd, not internal) so we do not bog down the system memory? It would just seem to make sense, until someone figures out how to make the internal sd respond faster.
My phone is just so...VIBRANT
We have 2 gigz of application memory.. No need for apps2sd... Not sure of the transfer rate on it tho... But apps2sd won't be as stable or fast... In my past experience...
Sent from my SGH-T959 using XDA App
junkdruggler said:
We have 2 gigz of application memory.. No need for apps2sd... Not sure of the transfer rate on it tho... But apps2sd won't be as stable or fast... In my past experience...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yea who needs apps2sd with 2 gb of application storage...
temperbad said:
Yea who needs apps2sd with 2 gb of application storage...
Click to expand...
Click to collapse
^ Vibrant pretty much as its own dedicated space for apps.
The data storage is slow, and laggy. I don't think it transfers as fast as a class 6 sd card. I currently have my apps in my /system, but space there is limited. (did the stalling fix)
I'm thinking that my sdcard is faster than the internal sd. Maybe not as fast as the nand, but still.
My phone is just so...VIBRANT
bryon13 said:
The data storage is slow, and laggy. I don't think it transfers as fast as a class 6 sd card. I currently have my apps in my /system, but space there is limited. (did the stalling fix)
I'm thinking that my sdcard is faster than the internal sd. Maybe not as fast as the nand, but still.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
umm?
I'm quite sure that the internal transfer rate is probably way above the capability of a class 6 for a whole lot of reasons, barring any manufacturing defects. If you are thinking that a memory card is magically going to speed up a phone that can basically do without one, then go get a UHS card to feel better.. . I'd rather just have a 16GB class 6 for storing crap and peace of mind but that's it.
bryon13 said:
The data storage is slow, and laggy. I don't think it transfers as fast as a class 6 sd card. I currently have my apps in my /system, but space there is limited. (did the stalling fix)
I'm thinking that my sdcard is faster than the internal sd. Maybe not as fast as the nand, but still.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
NAND is faster than your class 6 card, easily... the lag is not due to the internal storage...
check this post. Maybe it will clear up what I mean about the speed vs space limitations.
http://forum.xda-developers.com/showthread.php?t=727279
I've used method 1, and noticed a HUGE difference in speed. If course, my sd card isn't going to be as fast as the nand, but in past experience (g1, mt3g) the sd card was faster than the built in memory was.
My phone is just so...VIBRANT
bryon13 said:
The data storage is slow, and laggy. I don't think it transfers as fast as a class 6 sd card. I currently have my apps in my /system, but space there is limited. (did the stalling fix)
I'm thinking that my sdcard is faster than the internal sd. Maybe not as fast as the nand, but still.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
I did a test on my Vibrant internal SDCARD and it shows as a class 6....
I set CPU to 1000/1000 very little differences in battery drain yet did help a little with "lag" I also deleted most of the bloat-ware, startup and shutdown files...NOW ALL MOST NO LAG except as listed below...
When from 230 to 90 mb free after 1st boot up (without starting anything manually) to 230 to 120 mb free after 1st boot up...
So much Samsung has running at boot up so that extra 30mb and going down to 100MHz causes the"lag" - BTW, I did not do the "Lag fix" posted just to see if I could get it faster without going that.
The only two issue I currently have is:
While speednet app loads fast it will not start for about 45 secs - is forced to goto Washington State server, whereas all my other Android Phones goto CA...shows CA 1,123 miles away from phone
The double - "Press power button" and "then swipe screen" to use the phone is VERY "$$##%" ME OFF
I have used Titanium Backup to remove the bloatware, but I haven't tried permanently clocking to 1000. I saw no real difference in startup lag in my apps, until I used the "stalling issue" fix. What format is the data partition? That could have something to do with it? Would it make sense to add a swap partition to the internal sd? I'm really wondering if there are things we can do to tweak the built-in storage to make it more flexible, and functional? I would think 16 gig would give us PLENTY of space to play with...
My phone is just so...VIBRANT
Are you serious? I have well over 700 apks saved to my sdcard (almost 800mb) as backups... Theres no way you could throw that on an sd ext4 and it not lag.. Even a class 6... We can't even get apps2sd stable up to 2gigz... Like I said before the way it comes stock is faster and more stable than any hack we can come up with right now..
Sent from my SGH-T959 using XDA App
Nevermind. Found a thread on apps to sd. It's already being done. I'll go check that thread. They don't see it as a pointless effort.
Thank you all.
My phone is just so...VIBRANT
I'm currently running the devil kernel on my phone, using the new devil app to control settings but I really don't know a couple settings though. First what I'd zram and is it better than swap? And what's the best value to set the zram at? I have it on 150mb.
Also what's better zram or swap?
Dude look @ the op
Sent from my SGH-T959 using Tapatalk 2
No info about what it is in the op U_U
well, based on my reading...(Basically meaning take this with a grain of salt because I may not perfectly re-present the information, but this is how I've come to understand it lol )
zram basically compresses unused apps within the system RAM. This allows the system to swap less needed processes to the zram partition for faster access at a later time, instead of killing them. This does take up some of your ram though, so I imagine that the value you are setting is determining exactly what percentage of your ram that the zram partition is allotted.
Swap instead uses a small portion of the SDcard like RAM. The phone will attempt to keep as much within the ram as possible until fill, and then begin using the swap partition on the SDcard. At that point, the phone will begin moving inactive blocks of memory to the SD, freeing up RAM for active processes. If one of the pages on the SD needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the SD ('swapped').
Swap files don't restrict available RAM but writing to the sdcard impacts the speed of opening apps.
Now, which is better? No idea ^^ Lol
Holly crap I'm enabling swap lol. Do I need to repartition my SD card for swap?
I wouldn't enable swap, you don't need it, zram us nifty but also not need. Your system can handle memory just fine without you. Just let it to its thing and you will be fine.
Sent from my Galaxy Nexus using Tapatalk 2
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Woodrube said:
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Exactly, Android is designed for low Memory systems. It can handle out of Memory situations on its own, and will kill unneeded apps as is necessary to free ram for running apps. Don't worry about how much "free" ram you have because it doesn't matter. You want more free ram learn to set the ram usage settings to be more aggressive at killing idle apps. It'll and up using more battery, but if free ram is what you want then that's how to do it.
Sent from my Galaxy Nexus using Tapatalk 2
Woody said:
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Good old g1 and mytouch days
No signature for you!
Woody said:
There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Actually, yes. There are certain apps, like Facebook, Whatsapp, Skype and probably more, that have their background services running even if you close the app. Those services are for sending notification, but they are slowing down this device very much (Even if only the Facebook service is running). So I do feel the device does not handle memory so good. And I can't blame it, since it has a limited memory, but I do wish I had more RAM.
Don't enable zram or swap unless you have the EU bug or like your shizz lag like a mo'fo'. If your phone is playing nicely, then disable both. Allow Purging of Assets also.Set it to two processes in Dev Section.
Sent from a Beaner
Like the SIG D'fresh!
Sent from my SCH-I535 using xda premium
Dougfresh said:
... Set it to two processes in Dev Section.
Sent from a Beaner
Click to expand...
Click to collapse
By this do you mean the "Background Process Limits"?
Sent from my SGH-T959 using xda app-developers app
scottPilgrim said:
hey devil, got a question for you...
any particular reason why you removed zRAM from your kernel? i was wondering if you could elaborate a little bit on why it isn't necessary on this device.
Thanks man
Click to expand...
Click to collapse
Xenoism said:
zram basically compresses unused apps within the system RAM. This allows the system to swap less needed processes to the zram partition for faster access at a later time, instead of killing them. This does take up some of your ram though, so I imagine that the value you are setting is determining exactly what percentage of your ram that the zram partition is allotted.
Click to expand...
Click to collapse
Not really needed on our device that have 2gb of ram memory.
Have ever been in a situation where you have been out of free ram? Neither have I.
Sent from my GT-N7100 using Tapatalk 2
Our devices don't have 2gb ram memory. They have 512mb ram memory
Sent from my SGH-T959 using xda app-developers app
cannondaleV2000 said:
Our devices don't have 2gb ram memory. They have 512mb ram memory
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
1+
So has anyone tried swap on this device?
I was thinking that we might be able to increase ram operation if there was a swap partition.
I'm not exactly sure if it will work....
If anyone see's this thread and has a class 10 micro sd card and they want to try it please let me know how it affects the benchmarking results.
(I'd do it, but I have a crappy class 4)
Darin_Ram said:
So has anyone tried swap on this device?
I was thinking that we might be able to increase ram operation if there was a swap partition.
I'm not exactly sure if it will work....
If anyone see's this thread and has a class 10 micro sd card and they want to try it please let me know how it affects the benchmarking results.
(I'd do it, but I have a crappy class 4)
Click to expand...
Click to collapse
I tried using swap for awhile on my old HD2 which only had .5gb, but not here. The question I have to ask is why? In most of the current ROMs developers have already added scripts that kill dormant processes to free up real memory. Even when I've got a dozen apps open I've got plenty of RAM available. What kind of out of memory issues are you experiencing where you think swap would help?
Odysseus1962 said:
I tried using swap for awhile on my old HD2 which only had .5gb, but not here. The question I have to ask is why? In most of the current ROMs developers have already added scripts that kill dormant processes to free up real memory. Even when I've got a dozen apps open I've got plenty of RAM available. What kind of out of memory issues are you experiencing where you think swap would help?
Click to expand...
Click to collapse
Well it's not exactly a out of memory problem. I just wanted to see if the performance would be affected if a linux swap partition for ram would increase or decrease the ram operation.
I know we don't have the most high end device out there, but the specs are supposed to be better than an S2, yet it surpasses ours. It has a slower processor and less 3d graphics than the amaze and still it beats it.
Ram operation on the S2 according to Antutu: 705
Ram operation on the Amaze according to Antutu: 356
That's about half!!!!!
And I'm pretty sure if we found a way to increase the ram operation it'd help with all the other results.
I don't know why this is the case, but probably has more to do with the software running on the devices than the components. Sense is a lot of things most of which are good, but one thing for sure is it's s resource hog.
Odysseus1962 said:
I don't know why this is the case, but probably has more to do with the software running on the devices than the components. Sense is a lot of things most of which are good, but one thing for sure is it's s resource hog.
Click to expand...
Click to collapse
I believe my rom is senseless, cause I'm on the Xperia Z Ultra by shubham211995