Hi, I recently switched to the extreme , I’m using lock screen, the free version was so light-the extreme getting…
Hi, I recently switched to the extreme , I’m using lock screen, the free version was so light-the extreme getting up to 40 mb of ram running even I did setup to not running in background.Is that normal background process?
]]>
« I’ve been through the scripting tutorial etc and had a look at what methods and properties are available but what… (Previous Post)
(Next Post) Title »
D5 Creation
< ![CDATA[
Yup, because of the lock screen IIRC
]]>
< ![CDATA[
Cheers mate, such a shame đ that’s really killing my little Xperia u
]]>
< ![CDATA[
Does it make much difference if you disable the lockscreen? I remember there was a thread about it a while ago.
]]>
< ![CDATA[
Jay M if i recall coorectly there were 3 threads on this topic. llx doesnt exactly use all that ram by itself if im correct. it depends on your widgets, your number of home screens, all your other apps , the lockscreen, whats being placed on the lockscreen…… the list goes on. i have 1gb ram yet my system is running all but 350 of it on a good day. it was talked about at least 2 or 3 different times on different threads.
]]>
< ![CDATA[
I’m running only two despots witch is the the second one is the lock screen, on lock screen I’ve placed only the dynamic text for time and date plus dynamic text for missed calls and missed sms and gestures that’s all, after I disconnected the lock screen launcher get in cached process in normal consumption, .
]]>
< ![CDATA[
it also depends on the device. the last time we discussed this i had more widgets on just 1 screen than jay did on 3 yet he was using more ram from llx than i was. but then there were a few like you J Mis who only had 1 screen with maybe 3 widgets and they had more ram used than me AND jay combined.
]]>
< ![CDATA[
LL has an option to minimize ram usage, maybe you could try that out
]]>
< ![CDATA[
Is already on, us nothing I can do apart of turn the screen lock off đ on the post I said up to40mb but last night cached 53,imagine :), but the most curious thing from all of it is that phone still works even on 2mb of ram left đ
]]>
< ![CDATA[
For some time now I’ve noticed that LLX eats up a lot of it’s available memory quite quickly, often resulting LLX restarting itself on the background (and then being slow to open the app drawer) or widgets losing their data (zooper: can’t load or something like that; restart brings everything back though).
When I restart LLX then heap free is just under 50MB, locking and unlocking (yes, I use the lockscreen) takes ~20MB away and when I now opened the app drawer I’m left with 5MB (and the icons in the app drawer aren’t themed properly – because there wasn’t enough memory).
Also the lockscreen gets very laggy becasue of the memory issue and I get frequent crash notices.
I have 3 widgets (2 are full page and the third is larger – for the lockscreen), 2 panels and a bunch of app icons (because using the app drawer is usually a pain).
I was going to uninstall everything and recreate a fresh setup to rule out something reminicent eating up the memory, but then I saw this post =D
I just haven’t had the time to get this sorted, hopefully in a feew weeks, when the exams are over.
Anyone know from where does LLX take it’s heap max size? I know it’s device specific. I’ve often wondered why it isn’t bigger as this isn’t the first time I’ve run into problems like this!~
Sorry for the lengthy post! =D
]]>
< ![CDATA[
I think if the developer Will add the option to set the lock screen using one of the empty pages from the main desktop that Will sorted the ram problem, I think, maybe I’m wrong
]]>
< ![CDATA[
I have a lot of widgets and apps, as well as some desktops for testing.
I don’t have lock screen enabled. And I disabled the ‘save ram’ settings.
On average, in the process screen of the android settings: 120MB
Is it too much? Maybe.
]]>
< ![CDATA[
Taavo Allik funny you should mention all that because my llx has always been slow to open and it oftentimes restarts itself. everyday this has been going on. i always thought my problem was device specific (toshiba is a piece of trash).
]]>
< ![CDATA[
Curtis Sylvester Jr. Probably won’t help much but disable Animations in developer settings
]]>
< ![CDATA[
Guys the screen locker is the issue, without that launcher is soooo light
]]>
< ![CDATA[
seems to have sped up thanks Jay M. now to see if it restats by itselfï»ż yup still restarts
]]>
< ![CDATA[
It will restart itself if you run outta ram i think. All disabling the system animations does is makes switching to other Activity’s instant. Why wait if you don’t have to right? lol
]]>
< ![CDATA[
ikr Jay M it did speed things up. now if i can stop this device bug from resetting llx lol. i use the launcher loader to force llx as my default home and now half the time when i hit the back button it loads the loaders stupid menu. smh
]]>
< ![CDATA[
Curtis Sylvester Jr. You were suggested to use a different one…I don’t remember who but it was a post in this community. Search for it if you want.ï»ż
(I’m talking about the launcher loader)ï»ż
]]>
< ![CDATA[
TrianguloY i thought i did but somehow could have lost it….. now i cant find it in any posts or in the playstore. im looking right now
]]>
< ![CDATA[
http://market.android.com/details?id=vn.mobilepro.market.laucherswitcher here we go this one seems to work great TrianguloY
]]>
< ![CDATA[
There is virtually no difference in memory consumption and CPU use between LL and LLX if both version display the same desktops and items.
If figures are not roughly the same then you need to find the difference in the app usage. Widgets, icons and wallpapers are the biggest RAM consumer.
There is no background process: there is a service, but it does not run in another process. Anyway, don’t let the 53MB figure fool you: the app is using more… Other apps too.
]]>
< ![CDATA[
Pierre HĂ©bert where have i read that comment before? oh thats right you said that same thing at least 2 other times hehe :p btw TrianguloY that app was a bust.
]]>
< ![CDATA[
Pierre HĂ©bert all is true what you are saying, i agree than are no difference in consumption of cpu between LL and LLX  without running the LOCK SCREEN . Now, if the Lock Screen is turned on the LLX is turning in to the monster hand to hand with Facebook (73) and swype(32) producing death of less powerful devices like my Xperia U –  i think that is massive thumb down for that brilliant app  like LLX –Â
You should add some description on Play store about it. Â
]]>
< ![CDATA[
But maybe it is linked with what you have on the lockscreen ?
The lockscreen in itself is a desktop, it doesn’t matter whether is it displayed as another desktop or as a lockscreen, but its content really matter.
]]>
< ![CDATA[
Pierre HĂ©bert i tried even without anything (only gesture to unlock) automatically increasing the ram -normally is running very nicely  in cached process (about 11) with lock screen up to 57 (not in cached process ).  Â
]]>
< ![CDATA[
So my guess is that these figures are misleading. If you see a cached process, then it may mean that the app has been stopped but its process has been kept because the system has enough memory to do so.
]]>
< ![CDATA[
Pierre HĂ©bert thanksÂ
]]>