![]() I've just swipe closed all those few recent apps and the widget for free RAM instantly changed to: 25% 214mb free. But although how this function works is open to much interpretation, I have done some reading and tested it a few times.įor example, I've just used some regular apps like camera, phone dailer, photos etc etc and my free memory widget is reading: 21% 187mb free. Now, I just thought that swiping away the recent apps was simply that. It is like fighting a losing battle using task killers that are automatic or manual and hasnt helped me at all.Īlso, its not worth going into the setting and apps to manually 'stop' the apps as that doesnt seem to help much either as apps still restart and some cant be stopped at all. I have tested alot of things and one thing is for certain, using a task or app killer is pointless as alot of apps just restart even without being used. The recent apps listing wont help though surely? The main thing I have found however is to swipe closed all the apps in your recent apps listing. I don't use other apps whilst logging tracks and I certainly don't browse the internet. I've now downloaded a new music app which is easier on the RAM and have a widget called Free Memory Plus on my homescreen all the time so I can constantly see what RAM is free. So how do you actually minimize your chances of Locus crashing? Tell me. But as for Cheetah browser, well I simply don't use it whilst Locus is open as that too gobbles up about 50mb and for a lightweight simple browser is quite heavy on RAM use. I obviously cant help that Locus Pro is using alot of RAM and despite Nova using about 50mb I use that launcher as it is a vast improvement over stock. The 3 main culprits of high RAM use are Locus Pro, Nova Launcher and Cheetah Browser. On my phone, the background services and everything else use about 75% of the RAM leaving about 210mb free it seems (approx). So I have been monitoring things very carefully. Apart from that I only have Locus running although the way the Android system works - there is alot of RAM constantly being taken up at the same time When out walking/hiking I have been listening to Google Music app on Android and every so often check the internet for a moment using Cheetah Browser. Surely you have RAM heavy apps running that shouldnt be? But because it restarted itself and would immediately find a GPS signal it would beep and I'd suddenly know it had crashed and restarted at which point I would unpause the track recording and all would be fine without missing any of the track recording. Now, what used to happen on this and other phones was that Locus would crash but would then instantly restart with the track recording paused. I have a beep set in Locus that happens when it obtains a GPS signal. You say unlike previous Locus versions, what do you mean? Not so, I don't have the best Android phone but the Moto G has enough free storage space on it and with 1 GB of RAM that should be fine too. Over the past few weeks I've had Locus crash a few times whilst I have been tracking recording, and unlike previously Locus is not restarting itself (as a service or not as a service) and so if remained unchecked I lose a huge amount of tracked walking - much to my anger. ![]()
0 Comments
Leave a Reply. |