Related
I have noticed that occasionally browser closes itself while reading news and I'm being back to reloading news app. I thought perhaps it's my fingers touching back button. But after installing Tasker it gave me warnings, pointing to limited memory. My investigation shows that browser can take up to 150MB with few tabs open, depending how you exit the browser. With 370MB total on this phone it creates low memory condition and results in system killing all foreground processes to reclaim memory. So that's me being kicked out of my news :-l
I did factory reset thinking perhaps it's due to rooting but it's not it. I have a few apps but not that many.
Now the phone was marketed as gaming device. Do we know if the gpu memory 140MB is used at all for graphics by regular apps? Also is every game using it or is it utilized only by Tegra specific games?
I'm starting to think that 512MB is real issue, affecting phone's normal use. Even if you have your active app running ok often you may notice that your previous app was removed since system tries to clean background processes first. In my case news needs re-downloading and then I have to navigate to the place I left.
I just hope gingerbread will address the issue, to some extend.
For screenshot go to: tapatalk.com/mu/d0365549-2325-0bdd.jpg
Sent from my LG-P999 using XDA App
Have you frozen the Tmobile bloat? I got one memory error message before I rooted & froze. I haven't got any since & that is running a custom home (Go Launcher EX or SPB 3D) with Lookout, Watchdog, Wifi calling, Noom & a ton of custom live widgets.
Is this with the stock browser? I used Skyfire & it was a bit buggy so I use the stock but I keep my tab count to a minimum - usually less than 3 at a time because I have Flash enabled. In fact Flash could be your issue. Try disabling Flash and see what happens.
Bloatware was first thing axed. it's on stock browser. just checked dolphin browser with flash disabled and received low memory notification from tasker when browsing on three tabs. So it's not browser or flash specific. Can somebody confirm that browser can allocate 100 or more MB when using it actively? I was bit shocked seeing this.
Sent from my LG-P999 using XDA App
This never happened to me. I just checked my available memory when watching a flash video in the browser and it was still showing 137mb left. While playing pocket legends it is telling me I have 111mb left.
Sometimes certain apps that are coded wrong will suck up a ton of memory. This happened to me when I downloaded the NFL mobile app.
I can't speak for a g2x, but since my g2 has the same ram, I can say on stock browser regardless of the amount of ram I have available which always seems to be around 50 to 70, browsing has never been an issue for me. I only get insuffcient memory issues when installing apps from the market on rare occassions, redownload and it usually works. Not sure if this helps, but a phone with same memory specs just chiming in. I'm running cm7, a few widgets mostly utilities stuff.
Sent from my HTC Vision using XDA App
So, I've heard the new update 2.21.401.10 still has the well known limited multitasking issues (see YT videos for One X, it's the same for us: http://www.youtube.com/results?sear...0.0.0.119.352.3j1.4.0...0.0...1ac.R68YKWQ8QnE )?? Is it true? How can we persuade HTC to keep standard Android multitasking?
I've also heard the audio issues (crackles, trashed sounds, some micro-stutters sound-related. You can easily notice this with games, f.e. Pinball Arcade or Mame4Droid etc. Won't hear these problems on GS2 and other Android phones) are still there too, so the audio driver is still the same.
Should I go back to GS2? Multitasking problem is very important for me...
I don't have issues with sound now, never have. A lot of games ether aren't compatible completely (gta 3), and others are just trash audio. If you want to test audio run a GOOD mp3 file, if it crackles its your phone....
Sent from my HTC One S running Axiom S
the multitasking of the one X and S isnt' bugged, it is in this way for a choice of HTC. Basically the system doesn't left completly open apps but it freeze them which is almost the same of restart the app from zero more or less. This is because HTC want to keep some resources free to have a more fluid sense experience.
Anyway if you have an unlocked device you can flash this script http://forum.xda-developers.com/showthread.php?p=27318828#post27318828 that should give you real multitasking and leave the cool HTC interface ( the task manager ) to swith from an app to another. I would try it but I don't want to unlock my device at the moment.
none of the scripts work. wait till developers will fix it on kernel level. no other solutions here.
HTC One S via XDA
hexaae said:
So, I've heard the new update 2.21.401.10 still has the well known limited multitasking issues (see YT videos for One X, it's the same for us: )?? Is it true? How can we persuade HTC to keep standard Android multitasking?
I've also heard the audio issues (crackles, trashed sounds, some micro-stutters sound-related. You can easily notice this with games, f.e. Pinball Arcade or Mame4Droid etc. Won't hear these problems on GS2 and other Android phones) are still there too, so the audio driver is still the same.
Should I go back to GS2? Multitasking problem is very important for me...
Click to expand...
Click to collapse
I agree with hexaae. It's worth nothing having a super-fluid UI if it means killing your opened browser when you try to live it in background. You just can't browse between browser and email: how is this supposed to be called multitasking??
I really believe this choice of HTC's is senseless... On a smartphone with 1GB of RAM...
Edit1: by the way, what is the "background processes limit" option in "development options" supposed to do? Possible values are 0, 1, 2, 3, 4, default.
Edit2: would it be an idea to make a poll and see how many people would be interested in this?
mannequin said:
none of the scripts work. wait till developers will fix it on kernel level. no other solutions here.
HTC One S via XDA
Click to expand...
Click to collapse
why do you say that it doesn't work? On the thread some guys has reported that it works!
light_n_roses said:
why do you say that it doesn't work? On the thread some guys has reported that it works!
Click to expand...
Click to collapse
It worked for me, problem was the battery started draining like crazy. Which got me thinking, the reason HTC did this was battery life. Nothing else. Sense was still just as smooth for me, but apps would multi task like I used to, but my battery would last less than half as long. So I went back to stock and am getting decent battle life again.
Sent from my H1S using XDA Premium.
MadJoe said:
It worked for me, problem was the battery started draining like crazy. Which got me thinking, the reason HTC did this was battery life. Nothing else. Sense was still just as smooth for me, but apps would multi task like I used to, but my battery would last less than half as long. So I went back to stock and am getting decent battle life again.
Sent from my H1S using XDA Premium.
Click to expand...
Click to collapse
Well this is quite natural, you should manually clear everything once that you put the phone on stand-by ( and here the cool HTC task manager interface lack of a " close all" button ) or if you don't want to do this you can put task killer widget on the home that kill everything by a tap. Anyway this would kill also the background process not started by you which is not good so HTC should really put a "close everything" button on task manager interface so we can kill just recent apps opened by the user and not from the system.
Sent from my HTC One S using xda app-developers app
it works for about "10 minutes". all script "fixes" are nothing more than a placebo.
mannequin said:
it works for about "10 minutes". all script "fixes" are nothing more than a placebo.
Click to expand...
Click to collapse
That is not true. Yes, the multitasking is not stock quality... but the scripts do have a noticeable effect that improves performance (assuming you have enough free memory).
mannequin said:
it works for about "10 minutes". all script "fixes" are nothing more than a placebo.
Click to expand...
Click to collapse
this shouldn't be a script ment to improove performance, this should be something that it works or not, an off/on ...
light_n_roses said:
Well this is quite natural, you should manually clear everything once that you put the phone on stand-by ( and here the cool HTC task manager interface lack of a " close all" button ) or if you don't want to do this you can put task killer widget on the home that kill everything by a tap. Anyway this would kill also the background process not started by you which is not good so HTC should really put a "close everything" button on task manager interface so we can kill just recent apps opened by the user and not from the system.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It lacks the close all option because it is not needed. You dont have to close any apps unless they are something that need to be operating all the time like music player when it is playing songs or navigator and stuff like that. There is no difference for your batterylife whether you clear the "recent apps" list or not. And its called "recent apps" for a reason because it means that it has nothing to do with the fact is that application actually running or not. It has always being like that in android. It just makes it easier to jump between apps.
Using task killers and such only increases battery usage since the app it has closed needs to be loaded again when you use it the next time instead of it being just unfreezed from the memory.
HTC has set the automatic killer which kills apps on the background when running out of memory way too aggressive when you compare that to how it works on vanilla ICS or even older HTC phones running android 2.2 or 2.3.
However the latest update made multitask way better for One S. And Iam talking about the one which updatet android version to 4.0.4. Now you can jump between many apps without the fear of them closing immediately so Iam very happy with that now and it works as its should be.
Paqu1 said:
However the latest update made multitask way better for One S. And Iam talking about the one which updatet android version to 4.0.4. Now you can jump between many apps without the fear of them closing immediately so Iam very happy with that now and it works as its should be.
Click to expand...
Click to collapse
I've read comments by users who installed latest update and still have the limited multitasking issue (I'm waiting for the OTA update in Italy). Are you saying instead this has been "fixed"...?
Moved To Q&A
Please post all questions in the Q&A section
hexaae said:
I've read comments by users who installed latest update and still have the limited multitasking issue (I'm waiting for the OTA update in Italy). Are you saying instead this has been "fixed"...?
Click to expand...
Click to collapse
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.
Paqu1 said:
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.
Click to expand...
Click to collapse
Actually I still don't know because I do not have the last updated, I'm waiting that it goes online on automatic update.....
Hope you are right!
Paqu1 said:
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.
Click to expand...
Click to collapse
Please can you test this?
Open Google in the stock browser and type in something to search (but don't start searching!)... then switch between other apps and finally go back to the browser. Does it still reload and delete your input text?
I'm going to test the script now. Available memory is not an issue for me, as I removed Sense and am running Nova Launcher. My available memory usually sits around +230, ranging from 170-270. Haven't seen it drop below that. As for battery life, as long as you actually use the HTC multitask button and kill the apps that you don't want to go back to, the battery shouldn't really be affected, or at least the only effect will be a result of the apps that you actually want running, so it's a trade off, right? Keep in mind that means not killing the processes that will be automatically restarted by Android (ie using an auto task killer, or some pre Froyo type apps), only user apps that you recently launched and are now killing.
tgtoys said:
As for battery life, as long as you actually use the HTC multitask button and kill the apps that you don't want to go back to, the battery shouldn't really be affected, or at least the only effect will be a result of the apps that you actually want running, so it's a trade off, right? Keep in mind that means not killing the processes that will be automatically restarted by Android (ie using an auto task killer, or some pre Froyo type apps), only user apps that you recently launched and are now killing.
Click to expand...
Click to collapse
Oh god, didn't I just explained this few post earlier? You dont have to do any of that since it DOESNT have any impact to your battery life. Go ahead and test it if you dont believe me.
hexaae said:
Please can you test this?
Open Google in the stock browser and type in something to search (but don't start searching!)... then switch between other apps and finally go back to the browser. Does it still reload and delete your input text?
Click to expand...
Click to collapse
Ok, I just did what you asked. After doing that with the default browser I was able to jump between Dolphin HD which had two tabs open, youtube app and chrome without any of them closing. And I even went to home screen between them. I think thats pretty good compared how it worked previously. Because then often it was enough if I just jumped to homescreen and then right back the previous app to make it close.
Confirmed.
Official stock ROM, via OTA, ver. 2.31.401.5... and there IS multitasking, finally! Task manager is much more conservative (around 70-80% of cases) with executed apps in the multitasking-history-menu...
Yes, also the browser now won't reload pages if you switch to the mail app for a moment and go back...
~200MB free mem.
This is my first post on XDA and although i'm not new to the android scene having owned a lot of devices in previous years but I never came down to post queries of my own cause everything used to go real smooth!
I recently got a Nexus S i9020t from a friend and tried flashing a Jelly Bean rom on my device.
No issues so far with everything working with every rom that i've tried...
The only thing that bugs me is the ram.
I've tried several kernels on top of different roms (Matrix, Air (Big-Mem version), Marmite etc.) designed for Jelly Bean but I never to seem get any greater ram than about 150-170 mb even on first boot with no applications installed and when I restore about 50 of my apps through titanium it goes down to 120-150 at max.
I have tried rebooting my device every now and then but the ram leak doesn't get any better.
That way most apps that I run crash my device (im a big fan of chrome on android but the lack of availability of free ram degrades performance)
I've been looking into using different free task managers on the play store but of no use.
Simply put, my question relates to the free ram this device can generate!
Can anyone give me an explanation as to the lack of free ram and what kernel, tips and tricks I could follow to improve it?
You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.
chronophase1 said:
You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.
Click to expand...
Click to collapse
Yeah so like you said I did try the Big Mem versions of Air Kernel and Matrix but it was never really of much use. Matrix gives me about 180 mb of ram when the device has no foreground apps running (except the system processes of course) and Air goes to about 140-160 not more.
The thing that I don't get is that this other friend runs Jelly Bean on his Galaxy S with Devil Kernel or something and his free ram is above 190-ish.
Technically both sport the same hardware with a few extras on Nexus S (led flash, lack of gorila glass, NFC etc.) but it really doesn't make sense.
And about those Launcher redraws. Yeah, they've been going really frequent now that I installed and use chrome as my daily browser.
Overall, in my experience I'd say Matrix Kernel would be perfect if it weren't for that Voodoo Colour Mod. It gives a weird hue to my display orangy in nature but Air comes around well in that department.
We all understand what you're experiencing. Basically, our Nexus S devices just are not able to keep up with the ever increasing size of electronic files. Even though it's nice to be able to run JB, it really stretches the Nexus to it's limits. I too am torn, because I love the smoothness of 4.1.1, but to be honest, the phone can handle GB much easier. One other thing, Chrome is a huge consumer of ram ... really too much for the NS. As much as I love my Nexus, the handwriting is on the wall, if I really want to continue to enjoy all the new stuff coming our way.
The colors can be adjusted to your liking. Some kernels have a setting that's not the factory norm(ie Trinity). You also have to keep in mind some of that RAM has to be dedicated to the OS itself. You're gonna have to deal with the fact the phone has a memory limitation on 4.1. Sucks, but there's really not much else you can really do about it.
I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium
[email protected] said:
I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those auto triggers you talk of what software do you use to counter those cause I just looked at the cached processes inside the stock Application Manager and it showed a few that always show up when my phone boots. Of those that I usually encounter is Titanium, Maps, Google Search and a two or three more. Killing them doesn't make much of a difference though. Either the ram display at the bottom is screwed or the ram just doesn't go up when I abort any one of them and after a while they again show up. How do I deal with them?
Some general points.
Yes we want more ram. But we want it to use it. Free ram is wasted ram.
Task managers suck. All of them.
Low ram should not crash your device.
Stop worrying about how me free ram you have
Chrome sucks. It sucks on all devices. Sucks on n7. AOSP just runs better.
Want to keep a little more free ram because your device lags when its low on ram. Go to developer options and limit background processes
I'm with al. No point in over-obsessing about it. Cached processes aren't doing anything. They're there for when you want to switch apps for quicker access, which part of the way Android operates. You can limit what starts on startup to increase boot time(probably not even worth it), which I do even though I just said it probably doesn't help much, with a startup manager.
I to am no fan of task killers. I've heard that they can sometimes consume more ram since some of the killed apps will try to start again.
I found the autostarts app very useful. I have disabled around 50% of all auto starts. Mainly for installed apps but also a bunch of system apps. Another useful tool is Auto Memory Manager which sets the ram level where the system kills apps according to their category (e.g. Foregroud, visible, hidden etc). I use the "mild" manager with the level for empty apps raised. I manage to get around 80 MB free when running nothing. However I have a performance ROM which might affect that number.
My Nexus S has been retired a long time now.. I'm currently using the GS3 with lots of rams so it's not an issue for me anymore dealing with low rams... However, same symptoms on the GS3 or any Android phone, the less available rams means more processes are running which can cause slow app responsiveness. Also, some app even runs in the background hogging load of cpu usage, that definitely slows down your phone. I use task manager to kill off those high cpu apps when they go wild. OS Monitor is a good app for monitoring cpu usage... GO SMS Pro is an example app that sometimes persistently consumes 30% - 50% cpu, killling it off makes the phone smooth again.
S-beamed from my GSIII via xda premium
Ive noticed that the ram usage has almost double from GB to ICS (almost the same apps running in both versions).will this cause the mobil to slowdown .
Sent from my MB865 using xda premium
NatsuIgneel said:
Ive noticed that the ram usage has almost double from GB to ICS (almost the same apps running in both versions).will this cause the mobil to slowdown .
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Albeit GB software was/is very stable and has great performance, ICS is more intensive; for example, in terms of resource usage. As smartphones become more capable, our own applications, as well as the Google Mobile Services (GMS) applications, are becoming more advanced, which means that they require more CPU power, run more network activities and use more RAM, and full hardware acceleration also results in a need to load additional graphic libraries for certain apps, which makes them use even more RAM.
Another effect of the hardware acceleration is that it can make the battery drain faster in some cases. An example of this is video playback, where the hardware acceleration requires every video frame to be run through the GPU, thus making the system use more power than it would have without HW acceleration.
In regards to your 'available' RAM, about a third is used for functions that require a dedicated memory allotment to operate fast enough. For example, this is the case for certain multimedia functions. The remaining space, is reserved for the Android OS. Within the Android OS, functions like the activity manager and Home screen app are running.
When running low on RAM, typically with less than approximately 40MB left, the activity manager will start to close processes according to priority. At first, idle background activities are killed. The last thing to be closed down is the foreground activity.
Processes that are closed will obviously have to be restarted when the user enters the app again, which takes time and slows the system down. For example, when running a heavy game that uses all available RAM, the activity manager will be forced to kill all processes running in the background. This might include vital functions like the dialer and even the Home screen application. When you exit your game, there is a risk that the phone is perceived as slow, since the Home screen app will have to be restarted, just like every other activity you access afterwards.
Another interesting thing is that many apps use slightly more RAM in ICS. For example, the web browser is quite intensive, and uses 20-30MB more in ICS compared to GB. All in all, there are a lot of changes that together result in greater RAM requirements, and resource usage in ICS is heavier on the system compared to GB. However, there should be no cause for concern that this is in fact now the case...
Response from the ace! Its my day .thanks for the explanation sir
Sent from my MB865 using xda premium
NatsuIgneel said:
Response from the ace! Its my day .thanks for the explanation sir
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You're very welcome, hope that clears things up a bit for you. Also, battery life on ICS is all relative, meaning that nobody's definition of "normal" usage is static or comparable. ICS battery life is great, along with it's ability to cope with RAM usgae, etc. Experiment with it, try different settings, explore your posibilities to make the phone work for you, not the other way around. I'd be happy to help you with any further concerns or questions...
This clears one of my queries about RAM supposed to be 1GB (which should have realized being allocated as dedicated system RAM just as storage of 4GB reserved by system for storage memory).
You mentioned "Full hardware acceleration", question is, is this enabled by default on ICS? cause under "developer options" there is a option for "Force GPU rendering - 2D hardware acceleration" which is disabled by default & has an option to be selected by the user.
Also I have seen under running programs certain apps like "Astrid", "Hotspot VPN" appear (individually as a program) simultaneously in two rows as 1 process & 1 service but with varying RAM footprints, thoughts??
RAD7 said:
This clears one of my queries about RAM supposed to be 1GB (which should have realized being allocated as dedicated system RAM just as storage of 4GB reserved by system for storage memory).
You mentioned "Full hardware acceleration", question is, is this enabled by default on ICS? cause under "developer options" there is a option for "Force GPU rendering - 2D hardware acceleration" which is disabled by default & has an option to be selected by the user.
Also I have seen under running programs certain apps like "Astrid", "Hotspot VPN" appear (individually as a program) simultaneously in two rows as 1 process & 1 service but with varying RAM footprints, thoughts??
Click to expand...
Click to collapse
The objective here is let the CPU to do general OS related processing while GPU is doing specific graphic related processing. If you are an Android developer you know that Software development Kit (SDK) is letting you specify whether your app should use GPU if available.
Force GPU rendering is always using GPU to render application graphics regardless of above mention developer options. Even if developers disable GPU rendering for a specific app, still it will use it if you have 'enabled Force GPU rendering' and freed up CPU to do other important work.
As far as the duplicate (but dissimilar) RAM "footprints", I'm not sure why there would be more than one, when typically the two (services and processes) are shown on the same entry. I will see what I can find out about this.
Side note: I received an email from Motorola saying that they have shipped my replacement of my Atrix 2, after bricking from leak #2 testing, so I will be more of a service to this community once I get back the device. Sorry for the side step, just excited...
Apex_Strider said:
The objective here is let the CPU to do general OS related processing while GPU is doing specific graphic related processing. If you are an Android developer you know that Software development Kit (SDK) is letting you specify whether your app should use GPU if available.
Force GPU rendering is always using GPU to render application graphics regardless of above mention developer options. Even if developers disable GPU rendering for a specific app, still it will use it if you have 'enabled Force GPU rendering' and freed up CPU to do other important work.
As far as the duplicate (but dissimilar) RAM "footprints", I'm not sure why there would be more than one, when typically the two (services and processes) are shown on the same entry. I will see what I can find out about this.
Side note: I received an email from Motorola saying that they have shipped my replacement of my Atrix 2, after bricking from leak #2 testing, so I will be more of a service to this community once I get back the device. Sorry for the side step, just excited...
Click to expand...
Click to collapse
Noted the response on the first query.
See attached screenshot for the dual (dissimilar) RAM footprints (in this case it's just the "VPN" app.
:good: on the side note
The other thing that has not been noted in here, is that the kernel takes around 200 mb of ram right away on boot. That is why with almost nothing running you only see 800+ mb of "available" ram.
Sent from my Xoom using xda premium
Apex_Strider said:
Processes that are closed will obviously have to be restarted when the user enters the app again, which takes time and slows the system down. For example, when running a heavy game that uses all available RAM, the activity manager will be forced to kill all processes running in the background. This might include vital functions like the dialer and even the Home screen application. When you exit your game, there is a risk that the phone is perceived as slow, since the Home screen app will have to be restarted, just like every other activity you access afterwards.
Click to expand...
Click to collapse
Hi I am on PA atm. I had a horrid experience last night. I was playing Asphalt 7, in middle of an intense race, and then I received a call. but it stayed in game so I paused and then it got frozen of a sort to the tune that I missed the call. this is where I miss the good ol call receive/end keys..
So is there anyway to make sure that the calling function (Dialer?) doesn't get killed at all??
I recently noticed that the CPU on my rooted, stock rom Nexus 5 was running at levels of 70*% on all 4 cores. It came to my attention because this really slowed down the phone and made apps run very slow.
I asked about it and investigated but got no satisfactory responses. Finally I came across this
http://androidcommunity.com/nexus-5-camera-and-cpu-usage-bug-acknowledged-20140305/
I uninstalled the camera updates and the CPU usage immediately dropped to normal with only 2 cores being used most of the time.
So, if your phone has been running slow lately, it might be because of the latest camera update. Uninstalling the update might be the answer for you too.
the camera daemon was an issue way before the new camera came out. many many many have been experiencing it with the old camera. its not the camera itself btw, its a service your phone runs when taking photos(using the cam). and there are 2 temporary fixes for it.. 1. reboot your device, 2. use a free memory app to kill your services. as you can see that article was written way before the new camera app came out.
Which service should I kill? The battery app said it was "Android os" that was hogging it. Would disabling the camera app and using a different app make a difference?
Here's the difference I saw.
i use an app called FMR Memory Cleaner. i open it, press the button to run it(kill everything), and it frees my ram memory up. as a side effect, it kills that camera daemon service running. so it stops the high cpu usage/battery loss right after. basically, right after i stop using my camera, i run it.
btw, i used to work for androidcommunity.com(and actually get paid for it). i used to head and run their forums. and if you search simms22 in their search, a whole bunch of their news articles will pop up with me in them
Thanks. I thought task killers were useless because Android just reloads what it needs, but maybe it doesn't reload the camera daemon until the user calls it again. I don't use the camera much which is possibly why I had not noticed this till now.
Wonder if a boot manager could selectively prevent the camera and similar daemons from loading till actually called. But I don't know much about the inner workings of android.
Anderson2 said:
Thanks. I thought task killers were useless because Android just reloads what it needs, but maybe it doesn't reload the camera daemon until the user calls it again. I don't use the camera much which is possibly why I had not noticed this till now.
Click to expand...
Click to collapse
its a matter of opinion. sure, android does the job. personally i dont like how android does it. ive been using a few free ram/fast reboot type memory freers apps for the past 5 years, and am very selective of which i use, as some are just junk. anyways, it keeps me happier in the end, and thats whats important. isnt it?
simms22 said:
its a matter of opinion. sure, android does the job. personally i dont like how android does it. ive been using a few free ram/fast reboot type memory freers apps for the past 5 years, and am very selective of which i use, as some are just junk. anyways, it keeps me happier in the end, and thats whats important. isnt it?
Click to expand...
Click to collapse
Yes it is what's important.
And thank you for your help.