[Q] Thinking about performance - Hero, G2 Touch General

I was thinking about performance on my HTC Hero. For example, there is quite a noticeble time to load first-need app after reboot or memkilling:
I/ActivityManager( 522): Displayed activity com.google.android.gm/.HtmlConversationActivity: 5531 ms (total 6088 ms),
I/ActivityManager( 522): Displayed activity eir.dialer/.FastDialer: 2412 ms (total 2412 ms),
I/ActivityManager( 522): Displayed activity com.jb.mms/.ui.ConversationList: 1477 ms (total 1477 ms)).
There is two ways to reach less loadtime:
1. Optimize ActivityManager and other time-consuming processes of app loading.
2. Lock such apps (home, sms|mms, dialer, caller id) in memory.
First way can be choosen by developers, not mine.
So... how to lock any app in memory?)

Locking them in memory is found in CM extras.
Sent from my Hero using XDA App

thats presuming its the messaging or home app he wants locked in memory AND he's using cm7

Yes, homescreen and messaging app can be locked in memory in cm-extras. And what about dialer or _any_ other app?

No idea, I guess there comes a point when you'll run out of memory on the Hero ... unless you use YouLu dialer which is the messaging and dialer app all in one

As for now, I have such solution: don't use "back" button Only "Home". I think I could take a look at the CM-parts source code and make some "proof of concept" apk for locking any app in memory. I'm not a java coder, but .NET ))

Well if you dont use a CM rom it is kinda hard to try and look for CMoptions.

rdejager said:
Well if you dont use a CM rom it is kinda hard to try and look for CMoptions.
Click to expand...
Click to collapse
Who says I don't? Hm. Can you tell your dialer and sms loading time?

Related

Anyone got a stable task manager that WORKS?

I have a TMobile MDA that has the newest Tmobile rom installed. I have tried GSPmagic and Magic Button and both suck. GSPmagic cant close the phone or active sync, and locks the system sometimes if you dont use close All which closes everything , what a buggy piece of crap. Magic Button seemed to hog my resources and it had problem closing things as well. Is this a commmon problem or does anyone here have a solid task manager and it would be a plus to put the device lock on the task bar too. I DONT ASK FOR MUCH JUST SIMPLE AND SOLID.
thanks
Charles :x
Try InClose
Much better
Thanks Mark, that is ALOT better. uses half the system memory as well. Now I just need to figure out how to get the phone lock in my launcher or on the task bar.
Task Manager
I haven't tried InClose, but I use Truetoolbar and SmartSkey.
After having used allmost all available taskmanagers, i just assigned "Running Programs" to a hardware button. One click and u can manage your tasks. No loss in memmory or performance.
:lol:
If you want to put the phonelock in the tray, you can use VJTrayLaunch with VJDeviceLock.
For a task closer, I use VJOkButt. But it purposely doesn't close the Phone or ActiveSync since they could be necessary files. To close those, use VJTaskKiller or VJPhoneToggle.
V
Phone can *not* be closed by *any* task manager. The phone all can only be closed by killing the cprog.exe process but that results a) instant soft reset b) freezed device c) flight mode turns on (depends of the device which happens, but one will surely do).
KTamas: I don't think closing cprog.exe will always have that effect.
I've done it quite safely on my Magician, except for one bug: trying to dial a contact from Contacts causes a crash.
On my Mio A701, closing cprog.exe will put the phone into flight mode.
V
mach2005 said:
After having used allmost all available taskmanagers, i just assigned "Running Programs" to a hardware button. One click and u can manage your tasks. No loss in memmory or performance.
:lol:
Click to expand...
Click to collapse
how do you do that? I can't figure it out.
ILauncher v3.0 has a task manager that will close the phone pad which frees up program memory. It also has a traylauch. Ilauncher uses less memory than pocket plus.
Anyways here is another free taskmanager, install to phone the execute. It will allow you to see the process riunning and allows you to kill any process you want.
Inclose
Just downloaded and using Inclose. Magic Button was fine unti I upgraded the ROM. Then it went berserk. Never closed the phone pad had to soft reset. Let us see how Inclose behaves.... until now it is.
I use SmartTask with the Cingular 8125 and it is absolutely perfect:
http://www.freewareppc.com/utilities/smarttask.shtml
(ok, a few exceptions, like you can't quit the Phone application or else the phone resets. but otherwise perfect.)
mach2005 said:
After having used allmost all available taskmanagers, i just assigned "Running Programs" to a hardware button. One click and u can manage your tasks. No loss in memmory or performance.
:lol:
Click to expand...
Click to collapse
Umm... How do I do this? Can't see that option in "Buttons" in settings.
Magic Button hogging memory?
Sorry, but you don't know what you're talking about...
Magic Button's exe only uses 4kb of memory! :shock:
If you wanna talk about a memory hog, we can talk about Voice Command porking up a whopping 4477kb of memory :shock:
As for a good task manager style app though (like the windows task manager), I suggest ITaskMgr:
http://www.iaccarino.de/silvio/ppcstuff.htm
Excellant task manager and it is free! It also minimizes to the phone's tray. Very cool app.
http://buzzdev.net/content/view/86/1/ I currently use that one and I'm liking it.
masr1979 said:
http://buzzdev.net/content/view/86/1/ I currently use that one and I'm liking it.
Click to expand...
Click to collapse
Yes, this Task Manager is great. Improved functionality on v1.5 - check the above link. And it appears to be very stable, I haven't had any issues with it at all.
herzzreh said:
mach2005 said:
After having used allmost all available taskmanagers, i just assigned "Running Programs" to a hardware button. One click and u can manage your tasks. No loss in memmory or performance.
:lol:
Click to expand...
Click to collapse
Umm... How do I do this? Can't see that option in "Buttons" in settings.
Click to expand...
Click to collapse
Sorry, I forgot to mention that you need a lttle program to make it work.
Just install the cab and you have got the option in the 'buttons"menu.
^that's wonderful, I've been looking for that all along, nothing fancy, does what i want perfectly I can't stand all those task manager progs, thank you.
markmcrobie said:
Try InClose
Click to expand...
Click to collapse
Thanks for your suggestion. I have this installed and it works sooooo much better than magic button.
It has a lot of useful features, like to rotate the screen. I can now rotate my screen to landscape when I'm using PIE without opening my keyboard. Also, if you want to minimize instead of close, you just press and hold the close icon and select minimize from the drop-down menu.
GldRush98 said:
Magic Button hogging memory?
Sorry, but you don't know what you're talking about...
Magic Button's exe only uses 4kb of memory! :shock:
Click to expand...
Click to collapse
It DOES cause some CPU usage. I'll publish some more exact CPU usage benchmarks; when I tested, it caused some 1-2% CPU usage, unlike most other (decent) task manager tools. This doesn't mean, however, that it'll always cause that much CPU usage. Will definitely publish a big roundup of all these apps, along with their CPU and memory usage.

[APP][21/11/2008] NoTSR - A very little tool to restore memory

Hi.
When using my Diamond I noticed some processes don't disappear when they should. They fill up memory. Either you kill 'em with some Task Manager, or you soft reset.
Don't wanna SR or kill processes manually? Let my thing do it for you!
NoTSR is a very very simple program which kills some predefined processes, based on my experience with Diamond.
Source code (eVC++ 4) is for you to use and modify whatever you want. However, it would be nice if you gave me some credit if using it!
Have fun!
p. s. Sorry for the icon.
If anyone is wondering, this is what it kills off (copied straight from the source code):
"Opera9.exe", // everything still loads well
"OperaPreL.exe", // after killing them
"pword.exe", // for some reason Pocket Word leaves its process even after leaving
"CommManager.exe", // other Office apps seem to be fixed
"AudioManager_eng.exe", // last ones are opened by manila for quicker loading of tabs.
"AlbumSearcher.exe" // killing AudioManager stops music and rewinds current track.
I keep getting a "Can't list processes" dialog box when I launch the app. I tried placing the NoTSR.exe within in the extracted NoTSR subdirectory and also outside the subdirectory.
JNGold said:
I keep getting a "Can't list processes" dialog box when I launch the app. I tried placing the NoTSR.exe within in the extracted NoTSR subdirectory and also outside the subdirectory.
Click to expand...
Click to collapse
I can confirm that.
What did we wrong? Do we have to place it in a special folder, like windows?
It worked for me, but my phone was very sluggish after running the app and I had to soft reset to bring it back to par.
Thanks for starting this development, there is definitely a gap to be filled by it, I use oxios hibernate and a task manager to finish off opera .exe, this is much easier to use and your icons not so bad either!
uniqueboy said:
It worked for me, but my phone was very sluggish after running the app and I had to soft reset to bring it back to par.
Thanks for starting this development, there is definitely a gap to be filled by it, I use oxios hibernate and a task manager to finish off opera .exe, this is much easier to use and your icons not so bad either!
Click to expand...
Click to collapse
Thanks for positive feedback. I wonder why th sluggish reaction. Loading of opera as well as some TF3D tabs will for sure be slower, but whole phone is weird. After all, it just kills and leaves (see src if unsure). I use NoTSR myself and I got no problems at all. Maybe you could test it again and if it slows down show the list of processes?
@others: try using the app with rest closed. It should work in any folder; I keep it in my docs and launch via Start.
Thanks again for interest!
same error message for me. sprint touch pro with jd6.1 rom
I can't reproduce that error to analyze and fix it, so I post new version which tells you what went wrong. Try with it.
trying now
kosherpig said:
Thanks for positive feedback. I wonder why th sluggish reaction. Loading of opera as well as some TF3D tabs will for sure be slower, but whole phone is weird. After all, it just kills and leaves (see src if unsure). I use NoTSR myself and I got no problems at all. Maybe you could test it again and if it slows down show the list of processes?
@others: try using the app with rest closed. It should work in any folder; I keep it in my docs and launch via Start.
Thanks again for interest!
Click to expand...
Click to collapse
OK, so I've been using the NoTSR app for a couple of days and I can't reproduce the lag that I had when I first ran it, odd. I think it may be something to do with the fact that when I first ran it it was from within file explorer, after using it I could not get explorer to open up again properly. Now I have put a shortcut in my windows/start up/programs folder and I am running it from my start menu everything seems just fine and is all working as it should with no sluggish side effect, so thanks again kosherpig for the very useful app.
SKTools Lite (free) comes with a small program called "Free up ram." During SKTools Lite install, it will tell you something about your windows version, just click through that and let it install.
Once it's installed, go to your programs page and you'll see it there: "Free Up RAM". Just run it once. It will look like nothing is opening, but its because it's working in the background. You'll get a message box very shortly telling you how much ram (in KB) you freed up.
http://s-k-tools.com/index.html?sktools/m_lite.html
I use it all the time. Brings me from 45 -50 down to 35-40. Lowest I've seen was 32%.
Our programs are slightly different. My one doesn't free RAM by itself; it closes processes which won't close by a "close all" command. And NoTSR is not resident (after all its name is No Terminate-Stay-Resident ). Its goal is to be as small as possible, also in term of occupied disk space (~9kB now). Maybe this SKTools and NoTSR could be used in conjunction to free up even more RAM?
And, I also got the error message 2 times.
1st when I was running FM radio.
2nd when I was at the Music tab.
I solved them:
1st by closing FM radio and invoking NoTSR. Everything went OK.
2nd switched to the Home tab. NoTSR failed again. Waited some seconds, ran again. OK now.
Solution: fails? Shut everything using the HTC task manager, go to today/home screen, and invoke NoTSR after some time. I can say the behavior is really weird, since my code doesn't depend on running apps.
However, I run NoTSR everytime after using Opera. I got that error 2 times in my whole usage.
Anyways. Thanks for all responses
I find "Oxios Hibernate" frees up more ram than sk tools "free up ram" does, it is also free, but must be run manually, a useful addition to any start menu.
I'm getting about 10 mb back with NoTSR after opera browsing, "free up ram" or "hibernate" practically nothing back after opera browsing. Basically if you use opera then this is a "must have".
A small update.
If you know when Oxios Hibernate works and NoTSR fails, check this exe out. I tried to contain the Hibernate in it.
This version is bugged.
Please use version from 1st post.
If you ran this version already perform a soft reset.
Sorry for inconvinience.
chronster said:
SKTools Lite (free) comes with a small program called "Free up ram." During SKTools Lite install, it will tell you something about your windows version, just click through that and let it install.
Once it's installed, go to your programs page and you'll see it there: "Free Up RAM". Just run it once. It will look like nothing is opening, but its because it's working in the background. You'll get a message box very shortly telling you how much ram (in KB) you freed up.
http://s-k-tools.com/index.html?sktools/m_lite.html
I use it all the time. Brings me from 45 -50 down to 35-40. Lowest I've seen was 32%.
Click to expand...
Click to collapse
it lowers your memory usage by 10%???
To me it goes from 63% to 61%...
On my Diamond
thats frustrating...
Hi there, trying to use this app I'm getting the same error as others...
"Can't list processes: The parameter is incorrect. (#0)"
Task Manager is empty, I've tried leaving it on the home screen for 20 secs and running it but still the same problem.
Any ideas? I'd really like to get this working as Dutty 3.1 does appear to suffer from this memory problem.
EDIT.... OK, did a reset and it's working fine. I'll play with it over the next day or so, and fingers crossed Dutty 3.1 will be good enough for me as I don't need YouTube.
EDIT2... Worked for a while, now has the same problem as earlier.
Are you using the version form 1st post?
If not, please use it.
By the way, something is really wrong... AFAIK "Invalid parameter" has error code 87, 0 is "success". I've looked at program code to see where I could mess up memory, but I saw no such places. Help with finding this bug (you've got the source) would be very appreciated.
hi kosherpig
can you add a settings file where we can put our personal process to stop?
I've try to modify the source but I'm not able to compile it
kosherpig said:
Are you using the version form 1st post?
If not, please use it.
By the way, something is really wrong... AFAIK "Invalid parameter" has error code 87, 0 is "success". I've looked at program code to see where I could mess up memory, but I saw no such places. Help with finding this bug (you've got the source) would be very appreciated.
Click to expand...
Click to collapse
Hi Kosherpig, I am using the version from the 1st post.
I'm happy to help finding the bug, but not sure what to do here! I THINK it stopped working after I used TomTom7, but can't be sure.
It's only 1635 and it's down to 16% battery already (I think this is a problem with Dutty 3.1), so I don't want to do lots of tests. However, when I'm home and charging it, I'll try each app individually until I pin point which one "causes" the problem.
Does this help? Anything else you want me to try?
Hi kosherpig, getting on great with NoTSR now, I just have one small idea that it would be nice to show the memory stats in the pop up dialogue in a similar way to oxios hibernate. Unless of course this would significantly affect the size and speed of the app, in that case I think it is easy enough to check on the memory usage other ways with a couple of quick taps.

What is with certain background processes?

I noticed certain background processes like 'Email' and 'Gallery' kept coming back.
Even after I killed them with 'Advanced Task Killer', they kept popping back up and I want to know how to stop them? I don't want them to run automatically unless I need them.
Why is 'Gallery' kept popping up? I haven't checked any pictures lately.
Good question bro. This should be put to Google's Android forum.
Sent from my GT-I9100 using XDA Premium App
MrRoberts69 said:
I noticed certain background processes like 'Email' and 'Gallery' kept coming back.
Even after I killed them with 'Advanced Task Killer', they kept popping back up and I want to know how to stop them? I don't want them to run automatically unless I need them.
Why is 'Gallery' kept popping up? I haven't checked any pictures lately.
Click to expand...
Click to collapse
Out of interest, why are you bothered about it?
MrRoberts69 said:
I noticed certain background processes like 'Email' and 'Gallery' kept coming back.
Even after I killed them with 'Advanced Task Killer', they kept popping back up and I want to know how to stop them? I don't want them to run automatically unless I need them.
Why is 'Gallery' kept popping up? I haven't checked any pictures lately.
Click to expand...
Click to collapse
Please spend some time to read up on how linux works, specifically how memory is used, and then you will understand how Android works and why these applications keep "coming back".
I cringe everytime I read people talking about taskkiller applications.
kitch9 said:
Out of interest, why are you bothered about it?
Click to expand...
Click to collapse
I like to know how things tick and there is a REASON why the 'Gallery' kept popping back up.
MrRoberts69 said:
I like to know how things tick and there is a REASON why the 'Gallery' kept popping back up.
Click to expand...
Click to collapse
Because this is how android OS works. It loads processes for faster use when needed. There is nothing you can do to stop it, its based on android and its process management method, etc. These apps should be frozen in an idle state using zero resources. Use system panel to confirm gallery is not using any CPU.
They should make the system clever by having it learn what each person uses/doesn't use and only load the processes accordingly . I just find it irritating that it loads stuff that I am never going to use... I don't care that it doesn't use resouces, I just find untidy
I agree, i dont like things to start without me using them first neither! This is just stupid. Also some things should never been shown to users in my opinion. If something is in the kernel and not for me to mess with it should be hidden.
ps. as a user i dont want to spend reading tons of pages on how the OS works in detail, it should be easy to use and dont make the user confused. this is one aspect i hope Android improves in the future.
vampyren said:
I agree, i dont like things to start without me using them first neither! This is just stupid. Also some things should never been shown to users in my opinion. If something is in the kernel and not for me to mess with it should be hidden.
ps. as a user i dont want to spend reading tons of pages on how the OS works in detail, it should be easy to use and dont make the user confused. this is one aspect i hope Android improves in the future.
Click to expand...
Click to collapse
Buy an iphone
Sent from my GT-I9100 using XDA App
First of all starting some processes also start others in anticipation of their use. What is happening is that apps you are using are calling for those to start for quicker launch and there are dependencies that are not immediately obvious that will sometimes start a seemingly unrelated process. Memory management on android is very good and typically with task killers you often work against the built in memory management. I'm going to do a cut an paste here with a few basics....
By default, every application runs in its own Linux process. Android starts the process when any of the application's code needs to be executed, and shuts down the process when it's no longer needed and system resources are required by other applications.
A content provider is active only while it's responding to a request from a ContentResolver. And a broadcast receiver is active only while it's responding to a broadcast message. So there's no need to explicitly shut down these components.
Activities, on the other hand, provide the user interface. They're in a long-running conversation with the user and may remain active, even when idle, as long as the conversation continues. Similarly, services may also remain running for a long time. So Android has methods to shut down activities and services in an orderly way:
An activity can be shut down by calling its finish() method. One activity can shut down another activity (one it started with startActivityForResult()) by calling finishActivity().
A service can be stopped by calling its stopSelf() method, or by calling Context.stopService().
Components might also be shut down by the system when they are no longer being used or when Android must reclaim memory for more active components.
If the user leaves a task for a long time, the system clears the task of all activities except the root activity. When the user returns to the task again, it's as the user left it, except that only the initial activity is present. The idea is that, after a time, users will likely have abandoned what they were doing before and are returning to the task to begin something new.
An activity has essentially three states:
It is active or running when it is in the foreground of the screen (at the top of the activity stack for the current task). This is the activity that is the focus for the user's actions.
It is paused if it has lost focus but is still visible to the user. That is, another activity lies on top of it and that activity either is transparent or doesn't cover the full screen, so some of the paused activity can show through. A paused activity is completely alive (it maintains all state and member information and remains attached to the window manager), but can be killed by the system in extreme low memory situations.
It is stopped if it is completely obscured by another activity. It still retains all state and member information. However, it is no longer visible to the user so its window is hidden and it will often be killed by the system when memory is needed elsewhere.
If an activity is paused or stopped, the system can drop it from memory either by asking it to finish (calling its finish() method), or simply killing its process. When it is displayed again to the user, it must be completely restarted and restored to its previous state.
The foreground lifetime of an activity happens between a call to onResume() until a corresponding call to onPause(). During this time, the activity is in front of all other activities on screen and is interacting with the user. An activity can frequently transition between the resumed and paused states - for example, onPause() is called when the device goes to sleep or when a new activity is started, onResume() is called when an activity result or a new intent is delivered. Therefore, the code in these two methods should be fairly lightweight.
A few conclusions.....
Android is hard coded to automatically kill a task when more memory is needed.
Android is hard coded to automatically kill a task when it's done doing what it needs to do.
Android is hard coded to automatically kill a task when you haven't returned to it in a long time.
Most services (while possibly running in the background) use very little memory when not actively doing something.
A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
Killing a process when it isn't ready only causes it to have to reload itself and start from scratch when it's needed again.
Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
Most applications will exit themselves if you get out of it by hitting "back" until it closes rather than hitting the "home" button. But even with hitting home, Android will eventually kill it once it's been in the background for a while.
krabman, thanks mate now your post really helped me a lot to understand these processes

How to minimize applications

I was wondering if i could minimize applications on my phone and make them run as there are running normally . So that when i return to them they do not have to reload or anything . Something like the backgroundr application on iphone . Is something like that available on android ?
Sent from my HTC Vision using XDA App
hah are you kidding me? You're about to start a flame war lol.
Android has proper multitasking. When you hit the home button in an app, the app continues to run. Effectively "minimizing" the app. The only reason why it would close is to open up memory for a newer app that demands it. Switching between apps is as easy as holding down the 'home' button to see a recent apps list, and selecting which you want.
The iPhone is the one that actually doesn't do true multitasking. For most apps on iOS, they freeze the app rather than letting it continue to run. Things like streaming music, etc. will continue to play, but minimizing an app like a game etc. something will freeze the app till you return to it.
Some light reading on the subject that may give you a little insight: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
After you understand that, I find this video explains it as well: http://developer.android.com/videos/index.html#v=fL6gSd4ugSI (from a developer POV, but still shows how it works).
+1, home button to "minimize" the app, and longpress home to return to it.
Well I was gonna say, just hit home and it stays running but his post is epic lol.
Okay thanks and sorry for the dumb question but i still have a few inquisitions .. if i am browsing the web and i go to the messaging app to send a text then when i go back to the internet browser the web page reloads . As i have a slow mobile internet connection that annoys me . Secondly if i am watching a video and again have to send a text when i go back to the video it starts from the beginning . Is tht how its suppose to be or am i doing something wrong ?
Sent from my HTC Vision using XDA App
talha92 said:
Okay thanks and sorry for the dumb question but i still have a few inquisitions .. if i am browsing the web and i go to the messaging app to send a text then when i go back to the internet browser the web page reloads . As i have a slow mobile internet connection that annoys me . Secondly if i am watching a video and again have to send a text when i go back to the video it starts from the beginning . Is tht how its suppose to be or am i doing something wrong ?
Click to expand...
Click to collapse
it more than likely means there wasn't enough free RAM available to run both applications (along with all other background applications) so it closes the previous app so that the current one can operate freely.
So what I'm expressing is that Android isn't closing the app because you switched apps, its closing in order to keep the other apps running properly when the system is low on RAM, rather than the phone freezing up.
Are you running stock HTC Sense? Because on MIUI I just loaded a page, then read a text, followed a link to the youtube app, watched a video, then toggled back to the browser and the page was still there...
If you're on stock HTC Sense I'm assuming thats why you're having RAM problems.
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Sent from my HTC Vision using XDA App
I just checked 'running services' in the phone settings under applications . There the free ram.is ranging from 185mb to 165mb . :s
Sent from my HTC Vision using XDA App
Do you have a ''how-to'' to disable or uninstall services that we dont need?
In the same way as msconfig on windows.
talha92 said:
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This "Task Manager" you have running. Is it some app that kills other apps? If so, uninstall it. It is causing your problems and making your phone run poorly.
If you search around (maybe even on the Unity thread, if my memory serves me correctly . . . which it often doesn't!) there are some tweaks posted that are claimed to help memory management by slightly adjusting the parameters by which Android kills processes. I haven't personally tried them, so make a nandroid before changing anything, just in case.
talha92 said:
I like the htc sense look on my phone so i am using virtuous unity v1.31 that has sense 3.0 ..And i have the task manager application installed i have never seen my phones free ram lower then 65 mb . Its usually around 70-75.. so i wonder why my phone is closing apps by itself . :s
Click to expand...
Click to collapse
What 'task manager application' do you have running? If its killing processes prematurely then that can be a problem...
GinoAMelone said:
This "Task Manager" you have running. Is it some app that kills other apps? If so, uninstall it. It is causing your problems and making your phone run poorly.
Click to expand...
Click to collapse
the task manager app is the app already installed in the virtuous unity rom .. and i cant seem to uninstall it . and i dont think it would cause problems as it is packaged in the rom. would it ? .
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
redpoint73 said:
If you search around (maybe even on the Unity thread, if my memory serves me correctly . . . which it often doesn't!) there are some tweaks posted that are claimed to help memory management by slightly adjusting the parameters by which Android kills processes. I haven't personally tried them, so make a nandroid before changing anything, just in case.
Click to expand...
Click to collapse
thanks i am going to search for it in the virtuous unity thread and see if i am able to solve the problem .recently i noticed if i am playing music in the background and i open the messaging app or a big site like the desktop version of facebook on my browser the music application crashes so there is definately an issue with memory management in my phone
The main issue is that Sense 3.0 is not really meant to run on our phone, due to lack of memory. Sense 3.0 takes a huge chunk of memory, so it doesn't take much more to push the system over the edge. The tweaks I've read about won't be a huge change in memory management. But people on here swear they are helpful.
redpoint73 said:
The main issue is that Sense 3.0 is not really meant to run on our phone, due to lack of memory. Sense 3.0 takes a huge chunk of memory, so it doesn't take much more to push the system over the edge. The tweaks I've read about won't be a huge change in memory management. But people on here swear they are helpful.
Click to expand...
Click to collapse
With the new virtuous unity 2.37.0 (sense 3.0) I have an average of 130 mb of free memory. I use temp+cpu widget to monitoring.
Is it not enough?
I read an article about memory managing (auto killer apps) on GB roms, an apparently it wont give a faster speed or better battery life.
oVeRdOsE. said:
With the new virtuous unity 2.37.0 (sense 3.0) I have an average of 130 mb of free memory. I use temp+cpu widget to monitoring.
Is it not enough?
I read an article about memory managing (auto killer apps) on GB roms, an apparently it wont give a faster speed or better battery life.
Click to expand...
Click to collapse
If the latest version of Unity uses less memory, updating to that version might help the OP with his particular issue. I'm personally on 1.29. I tried every version after that (with the exception of 2.37), and they all resulted in my battery life being cut in half, so I'm back on 1.29.
The memory management tweaks I spoke of are simply adjustments to the parameters by which Android's built-in task manager kills tasks when memory is needed, not a separate auto killer app. Android inherently kills idle tasks when memory gets low. The adjustment I've seen, if I remember properly, actually raises the threshold for how full memory is before it starts killing tasks.
I agree that 3rd party auto killer apps will not increase performance, except in pretty isolated cases (like a rogue app, badly coded app with a memory leak).
Yes i was thinking of updating to v 2.37 nd see if tht solves my problem . And i was wondering if there was a simple way to stop android automatically closing applications till its down to more like 20-25mbs . But it will never go tht low will it ?
Sent from my HTC Vision using XDA App

[Q] Task switch in WP8, is it still slow?

I just want to know from anyone who had tried WP8 if the task switch is still slow for 3rd party apps, like in WP7.5?
Especially for messaging apps like Whatsapp or Viber. In WP7.5, it is very slow to resume.
That is because the apps are poorly written. My game has np resuming.
No, messenger apps run in background, so do location apps and no aps can resume from the start screen
Sent from my Lumia 900 using Board Express
I guess this should answer the question. As you can see, the app resumes at the state where you left it. It is really nice to see that. So these damn annoying loading times (except for first loading) are now a thing from the past.
Loading times / fast app resuming
Thanks for the answer. I will choose WP8 for my upcoming phone then.
I'm currently have WP 7.5 phone and also sick with loading times when switching apps.
You know you can switch between apps without having to re-load them...right?
Yes I know, using arrow button right?. But sometimes when we receive toast message (for me, mostly from whatsapp), I just press the toast message and it will launch the apps from beginning and it is very slow to show the message compare with similar condition in Android or iPhone.
morpheuszg said:
I guess this should answer the question. As you can see, the app resumes at the state where you left it. It is really nice to see that. So these damn annoying loading times (except for first loading) are now a thing from the past.
Loading times / fast app resuming
Click to expand...
Click to collapse
but the app resume its only if the app is one of the 8 "multi-tasking" right? If you have an app (for instance facebook) opened on the day before without rebooting the phone and opening for instance 30 diferent apps in the between that app wont be fast right? It has to "slow load" again, right?
Instant app resume has to be coded into the apps by the devs for WP8 it doesn't happen automatically. A lot of the current apps do not currently support this.
Sent from my HTC Titan using Board Express
tfouto said:
but the app resume its only if the app is one of the 8 "multi-tasking" right? If you have an app (for instance facebook) opened on the day before without rebooting the phone and opening for instance 30 diferent apps in the between that app wont be fast right? It has to "slow load" again, right?
Click to expand...
Click to collapse
As I and several others have said, the app needs to be coded to support this feature.
morpheuszg said:
I guess this should answer the question. As you can see, the app resumes at the state where you left it. It is really nice to see that. So these damn annoying loading times (except for first loading) are now a thing from the past.
Loading times / fast app resuming
Click to expand...
Click to collapse
mcosmin222 said:
As I and several others have said, the app needs to be coded to support this feature.
Click to expand...
Click to collapse
yes i know that. But windows 7.5 already had instant resume. Is this new functionality only when pressing the tile again instead of going via task-switcher?
tfouto said:
yes i know that. But windows 7.5 already had instant resume. Is this new functionality only when pressing the tile again instead of going via task-switcher?
Click to expand...
Click to collapse
Task-Switcher is still there for all Apps. Some Apps can now be fast-resumed from the Tile. Aside from that App startup times have improved because of several things:
Faster Hardware (obviously)
Pre-Compilation of MSIL to Machine Code in the Cloud
Faster network stack (especially for Apps like Facebook that do remote calls on startup)
Just tried this with the new FB app that is optimized for WP8. So I opened FB, and went to the home screen and then opened nearly every app on the phone and made sure that it wasn't in the "deck of cards" multitasking. I then hit the FB tile on my home screen and sure enough it opened right away to where I was at. There wasn't a "resuming" screen or anything.
So like the others have said, if the app is optimized for it (like FB) then it works without a hitch.
Though I must say even on apps not optimized the "resuming" or "loading" screen is soooo short that you barely have the time to even read it.
Overall, I have an LG Nitro HD running CM10 and I have an HTC 8x. The 8x is WAY faster opening apps and just overall speed. Not to mention battery life. ( I know, off subject )
tfouto said:
yes i know that. But windows 7.5 already had instant resume. Is this new functionality only when pressing the tile again instead of going via task-switcher?
Click to expand...
Click to collapse
It can be both, depending on how you code the app.
You can see the loading screen for a split second, then go right where you were if the developer so decides to. In fact, the developer can even show you po*n while it loads, so you can't really say if the app did or did not instantly load.
You can also use the task switcher.
Anyway, reload times should be fast even if you go through the loading screen. The only problem would be at first run, when the MSIL code has to be turned into machine code. After that the app should be significantly faster.
mcosmin222 said:
It can be both, depending on how you code the app.
You can see the loading screen for a split second, then go right where you were if the developer so decides to. In fact, the developer can even show you po*n while it loads, so you can't really say if the app did or did not instantly load.
You can also use the task switcher.
Anyway, reload times should be fast even if you go through the loading screen. The only problem would be at first run, when the MSIL code has to be turned into machine code. After that the app should be significantly faster.
Click to expand...
Click to collapse
Well lets hope developers from now on will just start making wp8 native code apps...
Microsoft does the MSIL => JIT compilation now in the Store, so it deploys precompiled Assemblys to the phone. There are actually articles out there that explain how you can enable/disable that behavior when working with the emulator to see the difference.
Still native code will be faster and "more predictable" in it's runtime behavior, due to lots of checks not being implemented (Out of Bounds at every array access, Garbage Collection, etc.) The downside is that native apps tend to be more error prone (mainly because you can do many things the CLR would not allow for good reason).
StevieBallz said:
Microsoft does the MSIL => JIT compilation now in the Store, so it deploys precompiled Assemblys to the phone. There are actually articles out there that explain how you can enable/disable that behavior when working with the emulator to see the difference.
Still native code will be faster and "more predictable" in it's runtime behavior, due to lots of checks not being implemented (Out of Bounds at every array access, Garbage Collection, etc.) The downside is that native apps tend to be more error prone (mainly because you can do many things the CLR would not allow for good reason).
Click to expand...
Click to collapse
You can still avoid many CLR exception checks if your code your app properly.
I don't think C++ will phase out C# as far as windows phone is concerned. C# is way more viable and stable and a few nanoseconds here and there won't be as annoying as an app crashing in the middle of your work, without any apparent reason.
mcosmin222 said:
You can still avoid many CLR exception checks if your code your app properly.
I don't think C++ will phase out C# as far as windows phone is concerned. C# is way more viable and stable and a few nanoseconds here and there won't be as annoying as an app crashing in the middle of your work, without any apparent reason.
Click to expand...
Click to collapse
well is it really only a few nanoseconds? IPhone 5 especially apps loading are blazing fast. WP apps are "slow" by comparisation... Maybe when all windows phones are quad-core loading times are no longer a issue, and C# its ok then...
Yes, it is just a few nanoseconds.
Trust me, if an app is well written, the startup time shouldn't be more than 2-3 seconds.
And if it is bad written, it doesn't matter how much C++ you use in it, it won't make any difference.
well on iphone5 it usually 1-2 seconds... Maybe it's a faster processor...

Categories

Resources