yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] mhb92:
so archi why do we need this new feature as most of them maybe all of them are taken care from kernel flashing ??

is it an option for those who choose stock kernel??

cant really get the point of adding this

though its nice to have also this in aroma..i remember my self setting this all by myself on old phones... though without zram :D
[Galaxy S III Android Development] JustArchi:
First of all, we don't need this, it's optional addition, the same as 90% of ArchiDroid. You can use it, but you don't have to. Also, show me the kernel which implements Hardswap ;). Only Yank has released a similar thing, his hardswap mode, but nobody else.

So why is it here? To provide you with a selection how many additional free megabytes of memory you want.
[Galaxy S III Android Development] Redscorpian:
Read it enough. What's the point of "you shouldn't enable it in the first place"? Clearly I have, clearly I want it removed, clearly I don't need telling that - how's that helpful? Maybe you need to feel superior by stating the blindingly obvious and showing I shouldn't have done something, maybe you don't but that's definitely not helpful.
[Galaxy S III Android Development] Orel1996:
Thanks for the explanation :)

Now, say I give 512mb to swap, and I want it back the way it was. Can I do that and how?
[Galaxy S III Android Development] JustArchi:
You reflash with "0 MB" option. Or you remove /PATH/ArchiDroid.swp manually through recovery, where PATH is /cache /preload /storage/sdcard1, based on your choice.

If you didn't want something, then you shouldn't enable it. Quite logical, isn't it? But okay, you applied something you don't want and you want to remove it, so I told you it's in build.prop, yet you for whatever reason think that I'm rude and unhelpful, OK mate. Sorry if I was rude and unhelpful, from now on please full wipe and reflash in case you'll want to change anything, it's easier to say full wipe rather than pointing exact location for an addition and being called rude and unhelpful.
[Galaxy S III Android Development] Orel1996:
Thanks :)

Although, how can I remove a file through recovery? Can CWM do that? Will a root file explorer such as ES File Explorer be able to do that function? :)
[Galaxy S III Android Development] Redscorpian:
Alternatively you could just give a relevant answer to a simple question without highlighting anything that's completely unnecessary. Simple really.
[Galaxy S III Android Development] JustArchi:
You won't be able to do so from running system, as if you enable hardswap, ArchiDroid's backend will activate it and Android will use it. Have you even tried removing your physical RAM memory from running PC? This is exactly what happens :D.

However, ArchiDroid gives you magic Aroma File Manager after installation. If you double-tap in PhilZ Touch Recovery, it'll pop up. You can also flash it as any typical ROM by going to /data/media/0/clockworkmod/aromafm directory and installing "aromafm.zip".

So basically you have three ways of getting rid of previously enabled hardswap:

1) Reflash with choosing no hardswap, this is the easiest, yet expensive way (time)

2) Open Aroma File Manager, find proper file and remove it, a bit more difficult, yet fastest way

3) Format /cache /preload or /storage/sdcard1 from your recovery, this will remove ArchiDroid's swap file as well.

Up to you.
[Galaxy S III Android Development] Orel1996:
Awesome, thanks for the detailed answer ;)

I'm currently on SlimKat and I really like the Real Dark Slim feature it has that other ROMs seem to implement. Does this ROM have it, and if not, do you plan on adding it?
[Galaxy S III Android Development] JustArchi:
I told you mate, it's not a kindergarten. This is xda-developers site, the main purpose here is sharing knowledge, eventually sharing final effect of somebody's free time combined. Let me quote you user named kyphur:

I told you where you can turn off your navigation bar, I even pointed one single file for doing so, yet you call me rude and unhelpful. Ok then, just please don't expect answers from me in the future, as I can't see a point of writing them if they're rude and unhelpful. Thanks.
[Galaxy S III Android Development] Redscorpian:
Such a lot of time spent trying to prove you're right after trying to show I shouldn't have done something I already know. Helps with your ego problem no doubt. Good luck, you've obviously too much time on your hands.
[Galaxy S III Android Development] mhb92:
mate u should know that in forums almost everyone talks as they know everything and as you said.."rude" though archi does a lot of work "for free" so having all people asking him same things everyday it's something that it shouldn't happen as u can see there is a search button..

although its a forum... u can ask everything :D and because its xda developers it doesnt make it more serious !! :D hehe its hilarious.. :p

real developers are few people in here..

and one thing that is true is that archi's rom is one of the best in here..

and rom isnt developing by itself..

and android developing is a HOBBY!! :D
[Galaxy S III Android Development] Guihardrock:
uoahhh amazin archi i understand everything except one word I/O what´s I/O? sorry for the noobest question ever hahaha :silly:

and thankyou for this amazing rom i will never get tired to say that :cool::cool::cool:

idea: could you add the explatnation in the aroma? for those who didnt read your reply :)
[Galaxy S III Android Development] tokariew:
Simple saying is about performance of reading memory, espacially small files

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] JustArchi:
I/O usually means Input/Output speed. The fully "right" definiton is IOPS - http://en.wikipedia.org/wiki/IOPS. This is a number, which determines how fast hard drive (by hard drive I mean permanent memory) is able to serve requests. We're in "good" situation, because flash memory is relatively much faster than pure hard drive, therefore swap does't hit "that much". It's something between HDD and SSD in terms of speed.
[Galaxy S III Android Development] Guihardrock:
SAD NEWS http://www.sammobile.com/2014/05/08...-galaxy-s-iii-gt-i9300-and-galaxy-s-iii-mini/ :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
[Galaxy S III Android Development] higstar:
Are we likely to hit wire cycle limit of flash?
[Galaxy S III Android Development] JustArchi:
I was wondering about that and come to such conclusion:

a) The most overheaded and overused partition is obviously /data, as this is the ONLY partition with constant reads/writes, plus /system partition, reads only, apart from flashing ROM.

b) Our i9300 has several unused Sammy partitions, such as /cache or /preload. These are nearly never used, as nobody writes anything to them. Dalvik cache is in /data, right now they're pretty much empty with no use.

c) I didn't even include an option to make a swap file on /data, because I know that it'll hurt. Instead, I included three places - /cache, /preload and your external /storage/sdcard1.

Theoritcally, blocks have "fixed size" in our partition layout. This means that TRIM utility or similar can't free /data block and use a block from /cache instead, and vice versa, broken /cache block can't be replaced by working /data block.

So in theory, if you're wondering about a lifecycle of specific blocks, trust me that your /data will be first to die, because /cache and /preload is never used. The only thing which you may want to consider is overall health of eMMC, the question is if we need to worry about it? If you consider life of whole eMMC as one thing, the chance of ending it's life is pretty much the same as you have right now. The "brick" situation comes when all required blocks are dead and we have no free blocks for replacing. But, partition layout specifies fixed size, so eMMC doesn't have freedom of being able to use whole eMMC, only blocks from specific fixed size.

Therefore, I'm pretty sure that chance of decreasing eMMC life is none, as long as you won't put your swapfile on /data, and ArchiDroid doesn't effer offer that because /data is overused already. In worst case you'd need to totally kill all /cache and/or /preload blocks, the question is how much time will it take if these partitions are nearly totally clean and unused? How many ROMs have you flashed in the past to /system partition, how many apps and data you stored on your internal sd card, including /data partition? And it's still alive, alright? So You'd at least need to duplicate the ratio on /cache and /preload to get similar "used" status.

Unless somebody can prove me wrong, maybe [MENTION=2033478]Yank555[/MENTION], as he's the master when it comes to hardswap.
[Galaxy S III Android Development] vldesco:
I agree with JustArchi, for sure We will change our smartphone before the eMMC can be totally damaged (if it gets damaged at any time). I used my Galaxy Ace for 3 months using a kernel that converted the /data partition in a whole swap area, and /data was mounted to external SDCard partition, I know, it was slow, but with more "internal" memory :D...After that, I changed to another ROM/Kernel with swap in external SDCard, and all went fine for 7 months until I lost my Ace :crying:
[Galaxy S III Android Development] JustArchi:
The most important fact is that I'm not even using potentially overused /data. I'm using Sammy's leftovers such as /cache or /preload, so I'm pretty sure that your /data will end it's life earlier than swap on /cache or /preload :D.
[Galaxy S III Android Development] higstar:
Thanks, for the breakdown, all makes perfect sense.

I have dumped a whole bunch of roms into eMMC but I'm sure it is nothing compared to the stuff written to /data

Cheers
[Galaxy S III Android Development] vyp54:
Is there a difference (theoretically) in loss of I/O speed depending the size of memory you choose for hardswap? Like more lag if you hit 512MB instead of 256MB?

Also, this memory will be used after you fill up your RAM or it's always used in combination with RAM memory?
[Galaxy S III Android Development] Redscorpian:
Yeah, I appreciate how you put that and apologise if I've been rude. I must say that I tried the forum search, found I "need to look in settings" and that option no longer works or exists - even Gravity Box KK didn't help so I posted a question which I felt was reasonable. I've used these search options before and found I'd asked the wrong question - afterwards - but I only learned that after finding the answer. I only pointed out that hindsight has never been a good answer as everyone's aware of that. I started by showing my admiration and pleasure with this ROM, which still remains. Thanks for the help, don't be angry, try to remember I didn't deliberately not know what to do.
[Galaxy S III Android Development] Boldizzle:
I have to say, this rom is running near perfect without the cherry picks. Any issues I ever had are completely gone ever since the update to 2.4.4.

Thanks so much for an amazing rom.
[Galaxy S III Android Development] KOLJACK:
Hello JustArchi, Devs, Testers...

I know that Camera is just a gadget. But..

My observation is that Camera (no matter what apk I use, stock, ProCapture, Snap Camera, Camera FV-5, etc...)

has some strange behaviour...

Focusing is not working properly. First shot, autofocus aims correctly, then next shots are taken before AutoFocus finishes focusing...

To bypass above issue I have to point on screen to focus on target and then take shot...

Another observation is that during recording - preview is laggy, and film itself is laggy too.

I decided to check it on latest pure nightly CM11 - and... WOW ! Camera works perfectly and fluidly...

Recording preview is smooth and movie as well... even in 1080p...

Is this Omni to work harder on Camera, or I should dig into AD v2.4.4 much deeper to get same effect... :)
[Galaxy S III Android Development] HD2kty.:
I have exactly the same problem as him.

I also tried other Camera apps as Pro Capture, Google Camera, PowerCam etc. but they all have the same issue.
[Galaxy S III Android Development] Tyrigi:
As Archi said, we can't have 100% working camera on AOSP, but yes in cm 11 is all fixed... so we need to hope that omni will fix it. :rolleyes:

---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------

Archi we should choose only 1 of these folder , or multiple like in cache and preload and extsdcard? Which you suggest?
[Galaxy S III Android Development] JustArchi:
The more you swap, the less IOPS are available for the rest of the system. However size itself doesn't matter, the thing which matters is how many megabytes you'll use from this size. As we want some "control" over things that are swapped, I decided that 128-256 are "OK" sizes to keep balance and not make it lag, while I also added one more step in each direction - 64 MB and 512 MB.

The "likeness" of system to use swap is defined in "swappiness" value, yes, the one which is also available in Boeffla app. I'm currently testing this with various options, the fact is that we should use values from 80-100 range, as others are simply ineffective because LMK kicks in before Android will even have a chance to swap something out.

You should contact with Omni for that. As far as I know, CM lately decided to go back to camera blob from stock Sammy, while Omni still uses opensource camera driver.

Camera is one of the things which will always work much worse compared to stock ROMs, so we can only improve it a little by trying a number of ways.
[Galaxy S III Android Development] JustArchi:
You can use any combination you like. The best "performance" combination is using swap on /cache or /preload, and one on /storage/sdcard1. This way you have two swaps located on two different flash memories, and this helps to keep good amount of IOPS because swapped memory is divided into two independent places.
[Galaxy S III Android Development] Mousman:
So 2.4.4 is much more stable then 2.4.3 but today it frozze on me, it could be bad flash so i might do clean reflash on Sunday.
[Galaxy S III Android Development] Yank555:
You called ?? ;)

I quote your whole post, so there's no need to search for it when reading my comments ;)

Well unfortunately, I'm afraid I will have to prove you wrong on this ... :angel:

The reason is very simple in fact, because between the logical adresses the OS sees (kernel in this case), and actual physical location inside the eMMC is

not

hardlinked at all.

The idea being, each time a write operation is imposed on the eMMC, no matter where the logical data is located (/data, /system, /cache...), the eMMC controller (this happens in electronic inside the eMMC) will decide to use the physical location which at that moment has been the least used so far.

And the eMMC will keep a correspondance table to know where a logical data is physically stored, and this will change each time you made a change to one of such data.

So editing for example build.prop will make the new build.prop to be physically located elsewhere on the eMMC (at least part of it, it depends on the file-size).

The technique is called wear leveling.

So using the "internal SD" for swap (swapfile) is not a good idea in general, as it will wear off each and every single bit of the eMMC eventually, as each write operation will use a new physical location inside the eMMC.

Now on the other hand, most of us likely won't use a device long enough to reach the life limit of the eMMC, but well, who knows ... only time will tell.

That is why I used to only offer hardswap, as in "swap partition on external SD", which is a lot slower, and will give you occasional lags (especially on powerful devices, so about any current device), but is cheap and easily replaced.

So if you want, I am ok to take the risk to brick a microSD card, but not to brick my phone.

I've stopped using it alltogether as phones have just gotten so fast, that external SD swap causes way too much lag. I rather either use zram (only when used with cleancache and zcache) or zswap (on the Note 3). It is limited in size (as opposed to swapfile/-partition), as it will use up RAM to give you swap, but since the swapped data is compressed, it will use less RAM than the swap size it will give you, so it's kind of an equilibrated thing. When you reach saturation, well, that will be as far as your device will be able to go.

I went for the Note 3, because it has 3Gb of RAM, as that's something I really am fond of, there's nothing better than RAM, except

more

RAM :D And yes, even there I use zswap, but it's hardly used to be honest, so it's more for fun than anything else ;)

Even though I'm fed up with Samsung, and the Note 3 is most likely my last Samsung, at least for the time being...

JP.
[Galaxy S III Android Development] JustArchi:
Thanks Yank! :)

Actually I'm rather happy to know that eMMC uses all it's blocks apart from only a few from fixed size, so by proving me wrong you actually made me even more happy :D.

Still, as you noted, probably noone will hit eMMC life, I haven't heard about such situation, SSDs are dated for more than 10 years of active use, and our OSes use swap (so called virtual memory on windows) anyway. For example my OCZ Vertex 3 right now has 12532 ON hours, total of 15,1 TB written and 13,7 TB read. Still, smart shows that I have 98% SSD life left. Definitely swapfile will shorten potential life of eMMC, no doubts in that, but I'm wondering if we can hit any limit if device has less than two years and we're not reading/writing that much anyway.

So, well. I'm going to put big red letters on hardswap page in my aroma and that's it :). Thanks Yank once again for your explanation!
[Galaxy S III Android Development] JustArchi:
Final clash of O3 vs. O2.

Objective: Compile all targets with O3 instead of current O2 and see if it's worth it.

Conclusion:

1. Kernel compiled with O2 has 4902 KB, with O3 4944 KB, so O3 is 42 KB bigger, "OK"

2. ROM compiled with O3 is 3 MB larger than O2 after zip compression. Fast overview: 97 binaries in /system/bin and 2 binaries in /system/xbin + 283 libraries in /system/lib and other files, about 400 files in total. 3 MB / 400 = 7,5 KB per file size increase, "OK"

3. No issues whatsoever, at least so far, "OK"

So yeah, O3 in experimental. I could prove that O2 gives 3x improvement over default android's Os. I can't prove that O3 gives any improvement over O2, but also I can't prove that it decreased performance in any way, so I'm keeping it :).

(Also, fixed MMS FC)
[Galaxy S III Android Development] marcero:
;)

Dont't know why its only 200k. Selected 512 MB in AROMA. Maybe because its just experimental ;)
[Galaxy S III Android Development] JustArchi:
It's not fully working (yet).
[Galaxy S III Android Development] nelsonw:
What about SDcard lifetime? Some people says that you can reduce and create big problems... //

ALREADY ANSWERED, didn't read till the end. Sorry.
[Galaxy S III Android Development] JustArchi:
Have you even read what Yank said? ;)
[Galaxy S III Android Development] nelsonw:
Sorry, asked too soon. Was reading a few pages back, sorry. Didn't read to the end before quoting, won't happen again... Lol
[Galaxy S III Android Development] JustArchi:
Always read everything :).
[Galaxy S III Android Development] striked0wn:
hehehe.. know that from somewhere..:D

deleted edit.. already answered on archis github..
[Galaxy S III Android Development] darkchronicle:
Greetings, currently I'm using [27/04/14] ArchiDroid V1.7.15 <--- (based on S5 themes)

So now I wanted to use this [05/05/14] ArchiDroid V2.4.4 <--

Can I perform update mode or using full wipe? Thanks :D
[Galaxy S III Android Development] coto39:
No, you can't. 1.7.15 is based on sammy stock and this is based on Omnirom. Two completely different bases. You MUST perform a full wipe. Good luck.
[Galaxy S III Android Development] darkchronicle:
Thanks my friend :D

Backing up data now!
[Galaxy S III Android Development] mhb92:
guys i have a lot of wifi drops when playing online games.. fcs on heavy games sometimes..okay the last one is happening on every 4.4.2 roms..though wifi drops is happening lately..

i play arcane legends and almost every ten minutes of playing i lose signal wifi drops..so ? does anyone have this issue?
[Galaxy S III Android Development] pradeepb:
guys, need help. I have installed both ROMs (Archi's) using dual boot method. I wanted to know how to use Whatsapp on both ROMs. Please help. whenver i boot the each rom, it asks me to verify each time :( :( Sorry for the OT
[Galaxy S III Android Development] Mostafa Wael:
So archi i am curious to know if O3 will give any improvements on O2 or not,

What will show us if O3 is better than O2 or not?

I just need to help :) :angel:

And so far the ROM is great,

But i just wanted to know if hardswap is going to give any improvements to speed, multitasking, or heavy games.?? :confused:

What do you recommend for a heavy gamer/speed lover?

I know that is a bit nooby but...

*Feel Free to ignore if you feel that this post is going to let you angry :D *

Thank you!

I hope that this wonderful project gets featured on XDA Portal one day :)
[Galaxy S III Android Development] JustArchi:
You won't know if it gives any boost because there's no trustworthy way to determine it.

By default kernel is compiled with O2 and Android with Os.

In latest AD 2.X stable kernel is compiled with O2 and Android with O2.

In latest AD 2.X experimental kernel is compiled with O3 and Android with O3.

The fact is:

O2: GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff

Os: Enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.

O3: Turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.

In short:

1. Some people claim that Os may be faster than O2 because of CPU cache and smaller code size. While this may be true for loading and launching, definitely it slows down already running binaries, such as dalvik. That's the reason why after switching to O2 everybody noticed that dalvik is actually faster than ART and whole Android is far more responsive.

2. O3 always increases code size compared to O2, and it may or may not increase performance.

Os slows down "pure performance" up to 3 times compared to O2. Even if in some cases it may be faster, this is definitely not a right choice for ArchiDroid.

The battle is between O2 and O3. O2 is "just right" choice because it gives best size:speed ratio, while O3 may increase performance for cost of the code size, but it also may increase code size while not giving any benefits compared to O2.
[Galaxy S III Android Development] coolnand:
Hey.. I have a small doubt.. Currently I'm running 2.4,4.. When I was on 2,4.3, when I cleared the recent apps memory, I could actually see 400mb + free ram.. Now usually my free ram is between 100 and 200. And when I clear, sometimes (actually not much) comes to near 300. I don't have any extra apps installed actually when compare to 2.4.3. And I did a full wipe too.. Any ideas?

---------- Post added at 07:45 PM ---------- Previous post was at 07:37 PM ----------

Just see the attachment.. After clearing all apps except Tapatalk, the free ram is around 183 or something. Is it normal? Or should u be getting more free ram? Just asking cause I used to see around 400mb+ free ram whenever I used to close all apps in 2.4.3. And I flashed both 2.4.3 and 2.4.4 in default settings.
[Galaxy S III Android Development] Guihardrock:
My free ram in 2.4.4 :cool: with normal apk installed
[Galaxy S III Android Development] coolnand:
Woah!! What's wrong with mine?? :( :( :'( someone pls help.... And I don't have that ram bar in recent. Dint see anywhere to activate it. :(
[Galaxy S III Android Development] coolnand:
this is my recent apps space. No ram bar!! :( should I use gravity box? Or it should actually come along with the ROM?