Related
Ok, I have the task killer app, but not sure how to determine what apps are ok to have running in the background and not suck up juice...
Seems odd to me that all the apps, even some that have an 'exit' menu item still linger after closing.
I searched about this forum (and wiki), but did not see similar questions.
It's probably so obvious that it doesn't register...
Thx!
Don't kill things like Alarm Clock, Messages, Touch Input, etc. Background apps only suck juice and use data if the app's themselves connect to the internet or use background data, if you aren't using background data, then disable it (there are third-party apps to toggle it mobile data and GPS on and off through widgets).
Personally, I used a task-killer and thought it would extend my batter but your battery life doesn't go down any faster killing tasks. My phone runs faster and smoother with it uninstalled and my battery was mostly draining because I had mobile networking on. Turn that off when you aren't using it (including GPS) and your battery life will increase two-fold. Not as much to do with background apps as you think.
Ok, thanks!
I have to Rogers too, but in my readings, everyone has said use the task killer, so I thought that was standard operating procedure. Then surprised a stock system didn't have anything like that installed.
I had left wifi and gps enabled on my Pure (Topaz) and battery life wasn't that bad. Would turn off when not in use. Does this one just stay on all the time?
-P
It will stay on all the time unless you turn it off via Settings or a third-party widget installed through the marketplace. As said in a few topics, Android is a Linux based OS meaning it's meant to handle the loads of apps running at the same time, it's how Linux handles RAM that makes Android fast. Running background apps do not mean they are literally running in the background, like in windows when you open 18 different windows and minimize a few, the programs are still running full capacity. Linux saves the applications settings and puts the application on 'idle' or a 'sleep' mode that allows the application to run in the background without it affecting battery life much. (I believe that's how it works.)
Don't worry about the task managers and just get some third-party toggle widgets installed from the market place.
I should have been more clear in my original question, sorry.
I'm quite familiar with *IX, been using / running / admin since 86.
I was mostly concerned with misbehaving apps (apps in background that continue to chew cycles), or devices that do not go idle when not in use. Generally unusual stuff that will drain the battery, not necessarily the obvious.
My experience with Android prior to this phone with with Android 2.0 as a work in progress on the HTC Topaz (which I am selling), and I constantly used task killer. I'm using it as a bad reference, I know it was in early stages of devel, but it was hard to tell what was draining the battery (and it got very warm).
I just unlocked my Sapphire last night and so far am very happy with it.
One thing that I wondered: is the expectation that if it gets slow, or if memory/swap starts to run low/out, you should reboot it? I guess that is why there is no task killer initially installed?
hi,
having a discussion with my friend about our phones and why hero is better than his.
I have a friend, he has iphone 3GS. Says that he can Multi-task on it. He can play music in the background, make a call on bluetooth, and surf the net; all at the same time.
This sounds like multi-tasking to me.
SO.. what am I missing? please enlighten me.
PS.. I love my hero!!!
You can do certain multitasking on an unjailbroken iPhone, but can't run multiple apps at once. ie. you can't have an RSS app running in the background looking for updates, a twitter client waiting for messages and something else in the foreground.
AFAIK. But if it's jailbroken then I believe you can multitask.
listening to music on the background is not multitasking if you ask me.
oh.. yes.. he is jailbroken...
Why would he want to listen to music while making a phone call?
I have a 3GS and use pro switcher. This is multitasking that causes me no
lag or battery drain. more here http://www.youtube.com/watch?v=x9C0oFj40Ms&feature=related
rdgut said:
listening to music on the background is not multitasking if you ask me.
Click to expand...
Click to collapse
Having owned a 2g/3g/3gs and Android phones I can tell you for certain 3gs is not multitasking, although it makes up for it very well.
Its a bad example I know but the moment you press the home button on the iphone it will either quit the app completely, or suspend it. When its suspended the app cannot carry out other tasks, Tomtom passes a junction you should have turned at, you've missed it because the phone isnt multi tasking. Wheras your android phone tells you to "Please turn Left in 300yds"
A good example of iphone os's made up "multi tasking" is the ability for you to exit certain apps (the stock apps are best) and resume as if you were multitasking - Contacts for example, opening a contact then hitting home, openning your emails, hitting home again, then going back to contacts, and it maintains the same view, as if you've never left that screen. Its a simple thing but works really well.
Phones I've had in the last 12 months include the G1, HTC Diamond, HTC Touch, iPhone 2g, 3g, 3gs (all size variants), HD2 leo, + a few others that I cant remember, and soon a Hero so I've tried pretty much every smartphone available.
Oh.. and my 3gs is jailbroken for that very reason I need true multi tasking on a couple of apps rather than push notifications Backgrounder to the rescue
ldavies83 said:
A good example of iphone os's made up "multi tasking" is the ability for you to exit certain apps (the stock apps are best) and resume as if you were multitasking - Contacts for example, opening a contact then hitting home, openning your emails, hitting home again, then going back to contacts, and it maintains the same view, as if you've never left that screen. Its a simple thing but works really well.
Click to expand...
Click to collapse
Android does this too, as well as allowing true multi-tasking.
Regards,
Dave
Raptor-21 said:
Why would he want to listen to music while making a phone call?
Click to expand...
Click to collapse
Hahahahahaha Nice one
Raptor-21 said:
Why would he want to listen to music while making a phone call?
Click to expand...
Click to collapse
joking aside...
It was just an example...
anyways, can anyone..
give me a better way to show me and my friend, how to confirm that the iphone can not multi-task???
Dan330 said:
give me a better way to show me and my friend, how to confirm that the iphone can not multi-task???
Click to expand...
Click to collapse
Well, Spotify is a good example. Stream some music and then switch away from the app to do something else - the music will stop. This doesn't happen with the Android version.
Of course, if he's jailbroken and running Backgrounder, this won't apply, as he could use Backgrounder to stick Spotify into the background but it does highlight the issue for most iPhone users.
It should really be stressed though that the iPhones lack of multi-tasking is not a technical issue with the OS - the OS is perfectly capable of multi-tasking, and indeed many of Apples own apps are permitted to multi-task.
The issue is that Apple specifically disallow 3rd party apps from multi-tasking as they believe this "improves" the user experience. This may well be true for the vast majority of iPhone users, but personally I'd prefer the choice without having to resort to jailbreaking the phone.
I fully expect Apple to relent in the very near future, and a future OS version will allow apps to run in the background. This will be quite ironic if they do so, because apparently Windows Phone 7 is purported to disallow multi-tasking too!
Regards,
Dave
Dan330 said:
give me a better way to show me and my friend, how to confirm that the iphone can not multi-task???
Click to expand...
Click to collapse
I am a addict of moutain walk. I am use to record my tracks on google earth with my phone. Some applications in Android/Iphone OS do that)
With an iphone i cannot do anything else! With android i can listen webradio music, send a picture of the landscape by email to friends, look landscape infos and historical informations on the web, tweet, use google buzz, etc.. while always recording my tracks.
It's impossible to do that with an Iphone! I have to stop the recording that is really stupid!
Locale is the example I often use. Runs in the background and changes phone settings based on location, etc.
a simple test would be entering a url in the browser, hitting enter and immediately going back to the home screen. then wait a minute or so and go back to the browser.
on the iphone the browser will have stopped loading the page and will have to reload. on android the page will have loaded in the background and will be fully rendered.
although the iphone can support multitasking when jailbroken with apps like backgrounder, i find it a hassle i can happily live without on my hero
Locale would be my example as well -- love the app to death <3
As much as this pains me to say...
Palm Pre/Pixi = True Multitasking
klbjr said:
As much as this pains me to say...
Palm Pre/Pixi = True Multitasking
Click to expand...
Click to collapse
Not sure what this is supposed to mean when Android supports "true multitasking".
Regards,
Dave
Full multitasking with every app's UI being constantly updated is a flawed concept, especially on restrictive environments such as smartphones. After all, we can only see one app at a time on these small screens of ours.
The key element here is background services. Android has support for background services, meaning anyone can write a music player and have it play music in background. iPhone does not allow that; only the stock music player can run a background service to play music.
The example applies no only to music players, but to IM apps, to email, etc. A prime example would be browsing the web with an IM app running in background. Impossible on iPhone, and done by many on Android.
iPhone tries to remedy the situation by offering push notifications, but they rely on external servers sending notifications to the phone, and we all know how pleasant it is to get a popup in our face while we're playing a game. Besides, push notifications don't address the problem of background services that do things other than sending notifications, such as the music player.
Android's multitasking model is a good example of how background services should work on phones. It separates the UI from the service, so that the UI can be suspended or even killed while the service still does its job.
On a sidenote, I'm quite sure Windows Phone 7 will have support for background services. Their main point is how most apps will be directly integrated into their UI, though. I like the concept.
foxmeister said:
Not sure what this is supposed to mean when Android supports "true multitasking".
Regards,
Dave
Click to expand...
Click to collapse
Well maybe I should have clarified. Yes the Hero allows for background apps to continue to run when you switch away from it to another app. It's the whole process of switching between the different apps that to me encompasses "true multitasking". The Pre/Pixi just handles the whole process much more smoothly and fluid. Better than any phone currently on the market. That is the only reason why I haven't gotten rid of mine as of yet. Even after having the TP2, Moment and now Hero, I still find myself using my Pre for most daily tasks. For me, I can do things twice as fast on my Pre than any other phone I have had and they are without question the Multitasking King/Queen of the market.
just to note.. i'm not a troll i love my x10..
i just had a chance to play around with my friend's iphone4 today
i didn't like the small screen, and it wasn't like.. that much more crystal clear than my x10.. and i still love my x10's design.. i think ip4 is so ugly..
BUT!!
my x10 was kinda laggy when i first bought it and now it's gotten much better after the firmware upgrade to 026.. but even then it gets laggy with lots of programs running, so i sometimes have to use the task manager to close the apps and then it doesn't lag..
on the other hand.. this ip4 was so smooth! like.. with my x10, when i move the screen or something there's like.. a little bit (maybe like a milisecond but still noticeable) delay before it registers my touch and moves.. but with ip4, there was no delay in registering my touch.. and also when i open a game or something, it would just pop up instantly...whereas my x10.. i open timescape, other apps, etc.etc. and there's like a second delay with black screen....
so what's the difference??? there's still more things i like about x10 than i won't switch over to another phone for another year or so, but it'd be great if my x10 could be less laggy......
is it because of the difference in os?? like... android has 'real mutitasking'.. is that why? or will the 2.1 firmware fix the problems?? (when i open my app.. or time/mediascape.. it stops for like a second at black screen and then the app loads... ) i have never used any other android phone.. so i can't really tell if it's an android problem or x10 problem...
The OS is certainly a part of it...the iPhone just has icons and folders; there's no widgets, or true multi-tasking, or anything like that. Lag should be a lot less with 2.1, even though now, I only see it for like a second after coming out of the lock screen, and that's it.
Also, I believe the processor on the iPhone is slightly faster (in actual processing power, not clock speed), which would make a difference.
I think it is mostly the os. The nexus one doesn't lag and out has very similar specs.
Sent from my X10i using XDA App
Ios don't multitasking? Are you kidding? It multitask very very well....
Sent from my X10i using XDA App
its true. mostly because of the OS design. iOS 4.0 does not allow true multi-tasking in programmer sense. If you do programming with iOS 4.0 you will be amazed on how complicated how to make your app do some work on background. Most of the apps you closed and running in background is actually really in paused stated.
second is the email and all the rest of the notification, they all is done on the server, then the server send you a push notification on the phone, then only that time, the phone will download the notification like email or facebook.
Android doesn't have a centralized server because they basically just selling the OS, not service. So the phone must do all the work to pull all notification from the server.
then like the post above, iOS does not have widget means no background process that supporting the widget.
so basically Android is slower because they do a lot of thing in the same time with single core processor, while iPhone do one thing at one time. I tried a China Android Table with dual core 1+1 Ghz processor, running 1.6 OS. That one is really really fast.
xeviro, you're not entirely correct with e-mail. Gmail app supports push so the phone doesn't have to do everything. Once it receives push notifications, it receives e-mail. but E-mail app doesn't have push capability, there you have to manually or periodically check.
I have mine set up as such -
ADW as the home launcher
Scrolling - horizontal instead of vertical (samsung like)
No wallpaper - black screen
"Advanced task killer" running - security level low; auto kill level safe/aggressive
No widgets running except time
Although it's boring, I have virtually no lag.
At the end of the day it is an android thing cause basically its java runing on top of a linux kernal.
basically the android os is doing a hell of a lot more at the same time than ios4. and on top of that doing it using java running atop linux, whereas if im not mistaken, IOsSapps are 'native', kinda like PDK apps on the Pre and what will be called android NDK apps in the future.
if uve run a java app on ur pc ull know what we mean.
ales85 said:
xeviro, you're not entirely correct with e-mail. Gmail app supports push so the phone doesn't have to do everything. Once it receives push notifications, it receives e-mail. but E-mail app doesn't have push capability, there you have to manually or periodically check.
Click to expand...
Click to collapse
Some email client on droid suport IMAP IDLE, the build-in Gmail app have it. But the email client for Timescape is not (see that you need to set duration), and Timescape doesn't talk with Gmail apps contents
lt iibad said:
basically the android os is doing a hell of a lot more at the same time than ios4. and on top of that doing it using java running atop linux, whereas if im not mistaken, IOsSapps are 'native', kinda like PDK apps on the Pre and what will be called android NDK apps in the future.
if uve run a java app on ur pc ull know what we mean.
Click to expand...
Click to collapse
because i happen to be a project manager for my company, making something for Android as well for iOS so i can tell you that apps in Android running in wilds, all program may run in background, some even can stay resident for god now how long and eat our battery the Android 2.1 and above is more strict about background apps. While iOS is like running in zoo full with bureaucrats, everything must be done in order so its much more stable but harder for us the programmers.
you are right about iOS application is native, and Android is bytecode that's need to be intepret to run. The problem with Android 1.5, 1.6 and 2.1, they don't have Just In Time compiler that converts this bytecode into native code on the run. Android 2.2 have it, that is why Nexus One is very-very fast.
lol, now we are talking about this, i really wish that our 2.1 delayed, because SE devs is actually rewriting all Timescape and Mediascape using NDK. then X10 basic apps (Timscape and Mediascape) would be very fast without waiting for 2.2
There seems to be an issue with the stock browser not remaining idle in memory after I press the home button
This seems to happen when multiple pages are loaded. In idle, the stock browser continues using CPU!
Anyone experiencing this?
How do you know it continues using CPU ?
By looking at the stock task manager!
The CPU usage ticks away for the browser
So close it with Task Manager, what's the problem? Stock browser doesn't have an exit option.
The problem is, why would I keep monitoring the program to see if it is using CPU power if it is supposed to be idle?
Well if you stop from Task Manager it will not be idle.
Android task killing is not recommended, so what gives?!
Now what does that mean? You have to exit it from Task Manger when you don't need it, pressing home button will never close it.
I know... but I was under the impression that manual monitoring of apps that are supposed to be in idle is unnecessary as people who advise against using task killers say that it is actually better for the operation of the Android OS as a whole, and killing apps is bad, since when home button is pressed, the apps actually lie dormant and do nothing
The issue now is I noticed the internet browser is still using CPU power, when it is supposed to be dormant. Of course I know the task manager can kill it, but I try not to kill the program!
Mate I am amazed by your thought. Some users say that don't use ATK or 3rd party Task Killer apps, but they NEVER say don't use the in built Task Manager. Jeez man, you don't wanna Exit an app because of some technical comment, unbelievable.
Regards.
The point being I don't wanna keep checking the task manager to see if the stock browser is using CPU power, that's the whole point of how Android is supposed to work, that is, if the app is in the background, it is supposed to idle and not consume power!
Just wondering why is it the stock browser is consuming power when it's supposed to be dormant
Well .. try to have the browser in background overnight .. and then check the battery statistics how much battery it did consumed over time ..
If you have background downloading set to ON in Android settings, and if the browser is on a site that's set to auto-refresh, it'll keep working in the background. That's by design and completely normal.
If you don't want this, make sure no auto-refreshing site is active in the browser before you send it to the background, or simply disable background downloading.
ithehappy said:
Mate I am amazed by your thought. Some users say that don't use ATK or 3rd party Task Killer apps, but they NEVER say don't use the in built Task Manager. Jeez man, you don't wanna Exit an app because of some technical comment, unbelievable.
Regards.
Click to expand...
Click to collapse
A lot of people advice against killing applications with task manager for good reasons, except for ill-behaving applications of course. How have you managed to miss those threads?
Killing an application prevents the "exit"-routine in the application from running so it cannot do want it wants to do when it shuts down (maybe storing settings/data to flash etc). Killing applications with task manager in Android is like killing applications in Windows with the task manager, something you shouldn't need to do.
So the question is if the stock browser is ill-behaving or if this is a normal behaviour. If this is just for a short while and then the browser stops using CPU then this isn't a problem.
If an application won't exit correctly when stopped from task manager, it most probably won't exit correctly when the phone is being turned off. Does it mean you can't turn the phone off ?
This is actually true for windows too.
tjtj4444 said:
Killing applications with task manager in Android is like killing applications in Windows with the task manager, something you shouldn't need to do.
Click to expand...
Click to collapse
Well buddy I really can't take the comparison between a PC and a Mobile phone. A PC never has a battery problem, neither RAM problem, if 1000+ apps are running on background, which exists on Mobile phone. I listen to Music while playing Crysis 2. GS II is a powerful device, a damn powerful one, but comparing it or it's Task Manager with a PC is kiddish IMO.
Anyway, I just meant to OP that he/she should press the 'Exit' option in Task Manager after it gets minimized to completely close the Browser.
Regards.
rantzzz said:
The point being I don't wanna keep checking the task manager to see if the stock browser is using CPU power, that's the whole point of how Android is supposed to work, that is, if the app is in the background, it is supposed to idle and not consume power!
Just wondering why is it the stock browser is consuming power when it's supposed to be dormant
Click to expand...
Click to collapse
agreed! would be very interesting to see how much does it consume overnight!
ithehappy said:
Well buddy I really can't take the comparison between a PC and a Mobile phone. A PC never has a battery problem, neither RAM problem, if 1000+ apps are running on background, which exists on Mobile phone. I listen to Music while playing Crysis 2. GS II is a powerful device, a damn powerful one, but comparing it or it's Task Manager with a PC is kiddish IMO.
Anyway, I just meant to OP that he/she should press the 'Exit' option in Task Manager after it gets minimized to completely close the Browser.
Regards.
Click to expand...
Click to collapse
Sorry, but the task manager in Android and Windows are very similar in more or less every way. And regarding "A PC never has battery problem" makes me laugh, have you heard about laptops and netbooks? With a CPU with 35W TDP in a standard laptop it is pretty important with well behaved applications in a PC as well.
I remember when I had problems with Word on my PC and often had to kill Word, I got tons of backup files laying around in my folders, and I often had to deal with the annoying document recovery at startup, you get similar unexpected issues with Android applications. It is easy to get corrupt files and end up in strange applications states if applications aren't able to shutdown properly.
Killing the stock browser is an ugly work-around, better than doing nothing if it drains the battery a lot though.
So my point is that this is an interesting thing to investigate, this is after all XDA, we should understand if the stock browser drains the battery or not, and also understand why (for some reason Flash comes to mind...).
on nexus phones when i minimize the browser with multiple windows open, then monitor CPU usage, it is dead flat using zero cpu. so there is definitely a problem if the SGS2 browser is doing something. dont listen to anyone saying to just kill it with a task manager. that's not the point. are you supposed to kill the browser 30 times a day everytime you are done doing something with it? of course not, that's insanity.
my suggestion is to monitor the browser 5 minutes after you minimized it and see if it still continues to burn CPU. my hunch is that after a few minutes it should go to zero usage.
aydc said:
If you have background downloading set to ON in Android settings, and if the browser is on a site that's set to auto-refresh, it'll keep working in the background. That's by design and completely normal.
If you don't want this, make sure no auto-refreshing site is active in the browser before you send it to the background, or simply disable background downloading.
Click to expand...
Click to collapse
this is completely wrong. the stock browser will NOT auto refresh in the background. it is specifically coded such that if you are loading a webpage and switch to the homescreen in the middle of loading, the web page will finish loading and then the browser will remain frozen and not do anything until the next time the user returns to the browser. this is well documented.
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...