Related
Hi Everyone!
I've lurked in the xda-forum awhile. I had a HTC Touch HD ("Blackstone" I think it was) about 4 years ago, rommed it with forum help but still wound up not liking the device so I got rid of it shortly thereafter and went back to simple candybar phone. Got an international/unlocked Galaxy S3 about three weeks ago and it is my first smartphone since then and my first Android phone! Very happy so far but I have several questions so far for some minor irks.
1. Memory management - I am using the GO task manager and my memory usage is regularly between 70%-90%. It's also annoying that the device has 1gb of RAM but it shows up as 779m. Is this high usage normal? I'm guessing it is due to a lot of stock boatware which leads me to my next point.
2. Startup app management - I have tried several apps that promise to manage startup applications but nothing seems to work very well. The best one I've seen so far is Startup Cleaner 2.0 but still things like Google Talk, TripIt and some games still start even though I select them to be disabled on startup. Is there a better utility or is this a weird thing with Android or ICS?
3. Bloatware - Is there a way to uninstall the stock bloatware I don't use like Google Talk, Google+ or ChatON?
4. SD card - I purchased a Sandisk 64gb Micro Ultra SDXC memory card and slapped it in. It shows up when I connect the phone to my PC and I have been transferring files and storing camera pics with it successfully. However, the one thing I can't seem to do is move any apps to it. It seems any program that is supposed to move apps to the SD card doesn't recognize it. For example, in "App 2 SD" it states: "The Device does not have a real primary external storage, or the primary external storage is emulated. Moving app to SD function may not be supported by this device."
5. ROMs - I did some poking around and it sounds like the Omega might be best for an Android n00b. Does this strip out a lot of the bloatware? Any significant pros/cons of using this over the stock ROM?
6. Gorilla Glass 2.0 - Is this the stuff they invented in Star Trek IV because it is crazy durable!
7. Security applications - I am using Lookout free version. Is anything else recommended more (Avast) or should I supplement Lookout with something else?
I appreciate any and all help and my deepest thanks in advance. Sorry if my questions are of the n00b variety but I'm new to Android smartphones!
- LaptopFTW
LaptopFTW said:
Hi Everyone!
I've lurked in the xda-forum awhile. I had a HTC Touch HD ("Blackstone" I think it was) about 4 years ago, rommed it with forum help but still wound up not liking the device so I got rid of it shortly thereafter and went back to simple candybar phone. Got an international/unlocked Galaxy S3 about three weeks ago and it is my first smartphone since then and my first Android phone! Very happy so far but I have several questions so far for some minor irks.
1. Memory management - I am using the GO task manager and my memory usage is regularly between 70%-90%. It's also annoying that the device has 1gb of RAM but it shows up as 779m. Is this high usage normal? I'm guessing it is due to a lot of stock boatware which leads me to my next point.
Never use task manager, let RAM work for you
2. Startup app management - I have tried several apps that promise to manage startup applications but nothing seems to work very well. The best one I've seen so far is Startup Cleaner 2.0 but still things like Google Talk, TripIt and some games still start even though I select them to be disabled on startup. Is there a better utility or is this a weird thing with Android or ICS?
Freeze with Titanium Backup
3. Bloatware - Is there a way to uninstall the stock bloatware I don't use like Google Talk, Google+ or ChatON?
For easy way, use custom ROM, best CheckROMv2
4. SD card - I purchased a Sandisk 64gb Micro Ultra SDXC memory card and slapped it in. It shows up when I connect the phone to my PC and I have been transferring files and storing camera pics with it successfully. However, the one thing I can't seem to do is move any apps to it. It seems any program that is supposed to move apps to the SD card doesn't recognize it. For example, in "App 2 SD" it states: "The Device does not have a real primary external storage, or the primary external storage is emulated. Moving app to SD function may not be supported by this device."
Can't move any apps to external anymore,as far I know, you can Bind it data only
5. ROMs - I did some poking around and it sounds like the Omega might be best for an Android n00b. Does this strip out a lot of the bloatware? Any significant pros/cons of using this over the stock ROM?
Best striped ROM is CheckROMv2, any stock apps you need can download from kitchen.
6. Gorilla Glass 2.0 - Is this the stuff they invented in Star Trek IV because it is crazy durable!
Yes durable enough, my screen still naked, not have any hair line yet
7. Security applications - I am using Lookout free version. Is anything else recommended more (Avast) or should I supplement Lookout with something else?
Use Samsung drive, no need anti virus
I appreciate any and all help and my deepest thanks in advance. Sorry if my questions are of the n00b variety but I'm new to Android smartphones!
- LaptopFTW
Click to expand...
Click to collapse
My answer below your question ^o^
Sent from my GT-I9300 using Tapatalk 2
Think the last guy covered most things but a couple of thing to add.
You don't need titanium backup or even root to remove apps as Ice Cream Sandwich allows you to disable unwanted apps right from the application management menu. The only system apps you aren't allowed to disable are ones which will break your phone, so you can safely freeze unwanted crapware without worrying about breaking anything.
I'm not entirely sure it's a good idea to start with custom roms straight away, maybe you should spend a week or two on stock and playing with what I mentioned above to learn a bit about Android before you dive into the world of root.
Also never listen to anyone when they say this, that or the other Rom is best. There are many great developers on xda and what suits him or me may not suit you.
At any rate my experience with past androids is that performance and battery life aren't all that different between the roms, it's usually only small tweaks here and there which are visible to the user. For example some will remove certain apps or the boot sound. The exceptions would be roms built from source like Cyanogenmod, Aokp and Miui. These feel very different to the Galaxy S stock Rom, although Cyanogenmod and Aokp feel quite similar to each other.
Sent from my GT-I9300 using Tapatalk 2
Yup, you're right, but I think I answer as best I could. Yeah many good ROM out there, CheckROMv2 is only my suggestions.
About stock Galaxy S3, yeah good enough for casual users. Some user didn't like bloatware, many can't be deleted and need permission to do that. Peace.. ^_^
Sent from my GT-I9300 using Tapatalk 2
apisfires said:
Yup, you're right, but I think I answer as best I could. Yeah many good ROM out there, CheckROMv2 is only my suggestions.
About stock Galaxy S3, yeah good enough for casual users. Some user didn't like bloatware, many can't be deleted and need permission to do that. Peace.. ^_^
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
That's right you can't delete them but a new feature of ice cream sandwich is that you can freeze them. It's basically the same thing titanium backup does but it works on stock unrooted devices.
Sent from my GT-I9300 using Tapatalk 2
If you ignore the various themed components of custom roms then after my tests their is no real diffrence between any of the custom roms as they basically all have the same inside . Advantage over stock almost nil .
Of course custom roms and custom kernels are at a very early stage of development for the SGS3 so far .
jje
Thanks, everyone for the advice and replies. I'm loving the phone so far but am always looking for ways to tweak and customize.
It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stopped
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
stempox said:
It 'just a habit of many displaying applications in the background to go on the Android Market and install a task killer for fear that some application in the background throughout the battery consumption and slow down the phone memory consuming.
First Step
Android is the son of Linux and not Windows, Windows programs make sense that clean and optimize your memory, not in linux and behaves the same way if you have 10 or 100MB of free memory.
How to manage Android applications
Android applications and processes have defined 3 stages:
1) Running
2) Break In
3) Stoppati
Each application runs in its own process when Android starts the process need to be made and ends when no longer needed, it lives in its own world and its code running is isolated from the rest with a Virtual own machine, it is assigned an ID whose permissions are visible to the user and 'application.
If an application needs to share files with another application creates a unique ID to save memory with a single Virtual Machine she shared.
Services are active as long as they need as well as activities that require the data connection and every process of Android. To understand whether an application or any process needs to connect and see if there are updates that it is active so that makes this operation.
It is not good or terminate these operations because the process will start all over again immediately active or when we are going to open an application it will take longer to open.
All processes are terminated when there is no longer needed or when the memory required by other processes.
If a user leaves a task for a long time, the system deletes all activities except the root, and when the user returns to the task it is like you had left.
An application is running when in fact you're running and is the first system plan
When it is no longer at the center of the 'attention but can still be visible is paused and can be killata by the system in case of need for extreme lack of memory
Finally, the application is blocked, but retains all the information is no longer visible on the screen and is in the background, can be killata from Android for any other activity that requires memory.
Summing Android is designed to kill the tasks when
You need more memory
They finished their work
Are not used for a long time
Kill process "by hand" can lead to side effects such as non-receipt of messages, slowdowns, crashes, etc. widget
The majority of applications closes with the BACK button and in any case by pressing the HOME Android close the task after it has been in the background for a certain period of time.
The majority of services running in the background using very little memory when they are not doing something so all other processes (reporting, etc.)
Domada: But why do I open google maps, facebook etc. mail.
These programs are not actually "open" if you notice are all programs that need a network connection, when you turn on the phone they do nothing but check for updates and notifications and then close.
If these activities killiamo happens that most of them will re-open to start all over again or take longer to open when we need them, or worse, will not give us accurate and up to date or will not work properly as well as make a lot more processor.
Click to expand...
Click to collapse
I know I'm likely to get criticised by some for saying this but some of us have to use task killers.
My phone has an average of 140 mb free after it boots up. Add to that apps that stay in ram even when you close them and you can have as little as thirty or fourty mb free.
I've seen apps such as facebook and tapatalk, and even some games, taking up ram even though I don't want them used once I exit from them...and when my phone gets to around fifty mb free or less it can get slow and unresponsive.
A quick kill of un needed apps makes the os perform as it should again.
It's nice to say android clears up ram as needed, and it does, but try playing a decent hd game when your ram is low and, unless you kill some apps first, you're left with a black frozen screen while it tries clearing some ram. In some cases your phone can be unusable for a while, on mine when this happens the capacitive buttons stop responding to keypresses.
Now on ics with 1 gb ram this isn't an issue but for those of us with less ram and / or an older os it is.
Ideally we could configure non system apps so that if we don't want them in ram when finished with them then they cannot auto restart.
It is a simple fact that two identical phones will perform differently if one has lots of free ram and one has most ram in use, I use an on demand task killer so that apps that stay around on exit can be stopped from eating ram and slowing my phone down so for me a task killer is not pointless specifically because it frees up ram so that something memory intensive can be run without slowing my system while android tries to make room for it.
So while I agree with the theory, in practice task killers can be useful or at least on demand ones can.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I agree with how Linux handles its applications. I switch between WinXP and Ubuntu and the overall way tasks are utilized are similar, but linux does a better job at handling running applications. On windows i have Chrome open and with 9 tabs open im hitting 1.5 gb ram used. Same situation on linux i find myself hitting around 500mb of ram used. Im sure this applies to android as well.
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
gruntparty said:
On a side note i find that people who "Kill Tasks" are just running them because they can and are usually fixated on seeing a large amount of ram free. It just adds another reason to stay on their device. Just my opinion.
Click to expand...
Click to collapse
I use one to make sure my phones already low ram does not drop so low my phone becomes slow, which it does when you get to even just fifty mb free ram left. And to kill those applications which do not exit properly.
On an android phone that has 512 mb ram if ram gets eaten up the phone goes slow, and I know it is not just me because other users with similar setups have same issues. So I think it is too general an assumption to say we all use task killers for say a cosmetic rather than practical reason though I'm sure some do.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Unfortunately this only stops apps auto starting at boot and once you have used an app and exited it, a lot stay in ram.
Some restart when killed some don't but when your phone is on permanently as many are, having low ram can quickly be a problem.
I think part of that is the phone manufacturer as 512 mb ram, with just 140 mb free at boot, is rubbish on a dual core 3D phone but whatever the cause I find killing tasks helps make phone run better.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
lewymaro said:
I used to kill tasks when i was on Android 2.1 an 2.3, but since 4.0 i feel my phone gone strangely fast, and i don't need to use task killers anymore. Phone is LG GT540, so...
Click to expand...
Click to collapse
I used to love my gt540. Didn't know you could run ics on it though, good phone for the price but didn't like the resistive screen though the phone itself can take some serious punishment and still keep working.
I love lg for their build quality, pretty hard to break them with dropping etc, but unfortunately they do bad with the software side.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk 2
Good topic, I don't like the task killer!
Sent from my GT-I9100 using Tapatalk 2
In general, yes task killers are bad. But occasionally it IS necessary to kill an app. Sometimes an app will freeze. Then it needs to be killed to be able to use it again. But you can easily just go into Settings > Applications > Manage Applications, find the app and then Force Stop it. So there's no real need to have a task killer. Although I do like to have Watchdog on my phone, as it shows the amount of available CPU cycles being taken up by each app, so you can make sure background apps aren't using too much CPU. (It does also show RAM usage, but it sorts apps by CPU usage, by default at least).
Linux has nothing to do with the management of an application, the applications under Android are sandboxed in java and there is this dalvik machine that takes care of everything.
I don't get why people keep mentioning this kernel over and over, also for the biggest part of its history Android did not use a real linux kernel with vanilla flavour, only recently the Android kernel was merged with the linux kernel mainline.
This is one of the very first Google video about Android http://www.youtube.com/watch?v=Mm6Ju0xhUW8
edit: In this series of videos there are also references to memory management and app management.
Markuzy said:
An alternative to task killers for rooted devices are apps that blocks app from running at triggers so nothing is killed at all; the apps don't run.
Eg: the autostarts app.
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
You are right
I do the same thing
In cm9 you can enable auto close apps with long press back button
So I don't need a task killer
Sent from my LG-P500 using xda premium
I was wondering if there is a way to always keep commonly used apps preloaded into memory for instant access. (sms, contacts, browser)
xemi1 said:
I was wondering if there is a way to always keep commonly used apps preloaded into memory for instant access. (sms, contacts, browser)
Click to expand...
Click to collapse
Start them once, and they will be remaining in memory until Android OS decides the memory is better needed elsewhere.
What you describes is not The Android Way. Primary memory is the most critical resource in Android, lacking virtual memory. Due to this fact, an app may be killed by the OS if more memory is needed for other needs. On the other hand, an app often used, is very likely to reside in memory, giving you this "instant access" you want. If you'd be able to lock an app and its memory, the phone would get out-of-memory not being able to release it when you try stating Angry Birds.
This said, some devices have "Don't keep activities", "Background limit: no processes" or so much bloatware installed, leaving an app gets it more or less instant killed, causing the next start of it to be considerably slower. In this case, the solution is to adjust those parameters, not forcing your apps active.
Read this thread. It might give you some light. Specially the " bulletproof " thing.
The only reason I'm needing this is because of the buggy dialer/contacts that comes with the stock sgs s3 ics 404, where if they go out of the memory they take like 1 sec to load, whereas different dialers and any other stuff is pretty much instant.
It's annoying to experience that delay whenever you need to make a call on a flagship smartphone.
And other market dialers are ugly and/or need the stock dialer to open for them to work.
I would like to avoid rooting g and losing my warranty as well.
Not sure if it is wrong, just would like to get some explanation of this. Phone has bit less than 1GB ram available for apps and default behavior of Androuid should be to use it all for caching recently run proceses, because there is no difference if memory is free or taken - it uses same power.
I have Viper ROM 1.06 and using Nik3r kernel, tested with and without dataswap mod (128MB). Even tried to tweak Viper settings for minfree setting, using Multitasking ultimate profile. And still the same behavior. When I check available memory, it always sits around 750 used out of 980MB. Regardless what and how many apps I run.
Problem is, that when phone is not used for some time I see almost every time apps starting instead of fast switching from memory. Its mainly visible for me on FBReader, which I use to read ebooks every time I have little spare time. I pull phone from pocket, start FBReader and voila, it is starting from scratch loading book. Its 2-3s, but still. its relatively small app, shouldnt be killed most of the time thanks to system policies on free ram.
When I try to play with phone and run as many apps (start FBReader, home and run Chrome+load 2 tabs, run Camera, run Viber, run Tapatalk and back to FBReader) to force it to close my FBreader from memory, everything works fine and it swaps back in immediately. Even though checking Apps tab in settings shows memory usage about 750-800/980, not fully stuffed with cached apps (think its not showing correct numbers? Or not showing memory taken by apps in empty state?). But anyway. I give up, turn off my phone and let it be for some time. Then I check for example for SMS and would like to continue reading my book. And FBReader is loading as if it was closed. Why?
Seems to me like phone does cleaning of cached stuff in memory after some time when it is not used? Cant say precise when it happens, it just annoys me to see that system shows all the time around 750/980MB used and still is unable to keep my app in memory for longer period when it works fine if I test it directly.
Any ideas/tips/explanation?
Hi, I have the same issue with the fb messenger (chat heads)
I
Android still shut down and it doesn't restart...
Any idea ?
Sent from my ARCHOS 80 COBALT using xda app-developers app
How do I free up RAM for my Samsung Note II LTE GT-N7105 on stock Android 4.3, rooted?
I am an Android retarded user looking for a patient teacher who will walk me through the Android RAM mysteries and answer a few question and, in exchnage, I can teach about the secret world of Traditional Neapolitan coffee infusion: home roasting, grinding, preparation and... savouring or, alternatively, Home Theatre! Your pick!
Smiles!
On average, at startup,
- Clean Master shows:
> 50% RAM
> 70% Device Storage
> 20% SDcard External Storage.
- Titanium Back shows:
> 500MB free RAM (of 2.11GB)
> 4GB free Internal+Media (of 10.9GB)
> 50GB free ExtSDcard (of 63.8GB)
Starting with these numbers, the device freezes after a bit of usage of the Swipe (Nuance) App. But I recently played with a 78 year old banker's GT-N7105, which was 20 times faster than mine, while running the same Swipe keyboard App: "My nephew geeks around a forum called xda-developers!"
1. In general, what's the relationship between installed Apps and RAM usage? Sometimes when I kill an app it frees up a bit of RAM, sometimes a lot and sometimes nothing at all.
2. Do installed (but not opened) Apps take up RAM space just by sitting in my Apps drawer? Should I uninstall all the Apps which I downloaded because "one day I might need it" and never used them or are they harmless (RAM wise) if I don't open them?
3. Do Apps which have been launched and now sit in the background take up RAM (as in Windows)?
4. Is there any difference between "fereezing" and "un-installing" an app as far as device operation speed is concerned?
5. Do I need to make sure that Apps don't start up if I don't need them (Google Play Services, Google Play Store, Goggle Translation, YouTube, Video Player, S Voice, Picasa Uploader, Nearby Service, Nearby Devices, SNS)?
6. If they eat up RAM, how do I make sure that they don't self start? Android Assistant App?
7. If background open Apps eat up RAM, is there a way to kill them automatically once I open a new one without loosing the cahced data which i might be using?
Thanks in advance for your time and expertise.
ascanio1 said:
How do I free up RAM for my Samsung Note II LTE GT-N7105 on stock Android 4.3, rooted?
I am an Android retarded user looking for a patient teacher who will walk me through the Android RAM mysteries and answer a few question and, in exchnage, I can teach about the secret world of Traditional Neapolitan coffee infusion: home roasting, grinding, preparation and... savouring or, alternatively, Home Theatre! Your pick!
Smiles!
On average, at startup,
- Clean Master shows:
> 50% RAM
> 70% Device Storage
> 20% SDcard External Storage.
- Titanium Back shows:
> 500MB free RAM (of 2.11GB)
> 4GB free Internal+Media (of 10.9GB)
> 50GB free ExtSDcard (of 63.8GB)
Starting with these numbers, the device freezes after a bit of usage of the Swipe (Nuance) App. But I recently played with a 78 year old banker's GT-N7105, which was 20 times faster than mine, while running the same Swipe keyboard App: "My nephew geeks around a forum called xda-developers!"
1. In general, what's the relationship between installed Apps and RAM usage? Sometimes when I kill an app it frees up a bit of RAM, sometimes a lot and sometimes nothing at all.
2. Do installed (but not opened) Apps take up RAM space just by sitting in my Apps drawer? Should I uninstall all the Apps which I downloaded because "one day I might need it" and never used them or are they harmless (RAM wise) if I don't open them?
3. Do Apps which have been launched and now sit in the background take up RAM (as in Windows)?
4. Is there any difference between "fereezing" and "un-installing" an app as far as device operation speed is concerned?
5. Do I need to make sure that Apps don't start up if I don't need them (Google Play Services, Google Play Store, Goggle Translation, YouTube, Video Player, S Voice, Picasa Uploader, Nearby Service, Nearby Devices, SNS)?
6. If they eat up RAM, how do I make sure that they don't self start? Android Assistant App?
7. If background open Apps eat up RAM, is there a way to kill them automatically once I open a new one without loosing the cahced data which i might be using?
Thanks in advance for your time and expertise.
Click to expand...
Click to collapse
Ugggg I hate this app lately! Just spent ten minuets answering all your points fully and it gave me stupid permission error! Even wrote a nice analogy about ram and libraries...forgive me if I'm brief now
Sum it up
Poorly made apps or ones that need to stay in the background to operate fully or spy on you stay in ram, many don't, dump bad and seldom used apps, stay away from task killers, if you need one use watchdog, see what's actually using cpu, better battery stats or cpu spy can help too. Freezing is fine, v6supercharger can help you, setting background process limit in developer settings can help
You have a nice snappy phone, get rid of junk and use nice roms and you'll have no issues
Secret world of traditional neapolitan coffee infusion sounds intriguing
Sent from my SGH-T699 using XDA Premium 4 mobile app
i would suggest installing and using greenify, since u already rooted.
post #3 of that thread is worth reading, probably will answer most, if not all of your question regarding android ram usage
@an0nym0us_
Cool advice, thanks! I installed and I will try it now.
@an0nym0us_
Cool advice, thanks! I installed and I will try it now.
@demkantor
I only got the jist of it but I didn't really understand... any chance to try again, when you have more time on your hands?
There are 3 aspects that make up coffee flavour: the beans' quality, roasting and preparation.
Beans (origin, ripeness, homogeneity, dryness) and roasting (tempreature, duration) are, for now, out of your reach. But preparation isn't.
Most infusion's preparation depends on 3 basic parameters:
- temperature
- time
- contact surface.
Threfore brewing time and temperature and the beans' grind size (and also the grinding method) will influence the coffee taste: the greater the time, temperature (up to 95°C) and surface the greater the organoleptic proprieties' transfer will occurr. Which does not necessarily mean the better taste... more on that in the next lesson.
Organoleptic properties are the aspects of food or other substances as experienced by the senses, including taste, sight, smell, and touch, in cases where dryness, moisture, and stale-fresh factors are to be considered.