If W10M doesn't fix BLANK, It's over..

flowkidd

New member
Oct 29, 2012
12
0
0
Visit site
Hi guys,

I've been messing around with W10M Previews since they came out and I'm losing confidence that my main problem will be resolved.

My main problem is that apps keep resuming, WHY? What is the problem that they can't fix? Even their own apps keep resuming even if we just switch over for a second.

Sure, this is old news since forever but this is a new OS, which means they should've got that fixed FIRST as part of a new OS.

If they don't fix that before the release it's over for them. No one wants to see that screen when iOS and Android don't do that. It will make it seem slow.

What else do they need to fix in order to even compete?
 

barotropic

Member
Mar 25, 2013
79
0
6
Visit site
I wonder...most of us testing W10M are using inexpensive phones equipped with fairly low-powered S400 and S200 SOC's. Is the "resuming" screen as annoying on a Lumia 930 (800 series SOC)? I suspect most Android phones we are seeing for comparison are using 800-series SOC's, or at least 600.

Also, I wonder what part installing apps on a micro SD card plays in the lengthy delay. Guess I should run an experiment.

BTW, I when I compare the general responsiveness of my Lumia 640 with an S600-equipped Android device, I am not concerned. The Android device doesn't hesitate as much during the "resuming" phase, but it is not as smooth and quick in other launches and transitions. Overall, I think the responsiveness is very similar on like hardware.
 

hacer619

New member
Apr 25, 2012
350
0
0
Visit site
That's true for the resuming problem. But for me im using a lumia 920 and I only see it when opening wp8 apps all win10 apps have no resuming problems. There is however a splash screen. windows 10 apps are optimised to have no resuming problems. Im not sure about 512mb ram devices.
 

Paolo Ferrazza

New member
Dec 7, 2014
441
0
0
Visit site
Well, android does not have resuming and drains battery, iOS does not have resuming because it has a super CPU.
In other words just buy a windows phone that costs like an iPhone and you won't see any resuming (I have no resuming on my 930 and it costs half an iPhone anyway) :p
 

theefman

Active member
Nov 14, 2008
3,979
5
38
Visit site
"Resuming" and "Loading" are inherent to WP 8.1 and from all indications thats goimg to carry over to W10M only they'll be hidden by splash screens.
 

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
I hope but shouldn't a technical preview have the core almost finished, cause if you are waiting until the end to fix something that is part of the core of the OS, it's not good planning.

As far as loading/resuming is concerned, I'd be very much surprised if MS were able to remove it entirely. I don't know why this issue, which has been with us since WP7, has persisted for so long, but it seems to be systemic.

Still, the answer to your question is "No". While it's true that some things must be closer to finished than others, these are typically things we as end users never see, and usually have no idea they even exist.

I also dispute that we can know how well MS is planning their work on W10M. For example, the overly lengthy loading/resuming delays (even for WP) some are reporting, could potentially be an issue with firmware. Firmware is always implemented last, and is not part of the core OS, meaning this delay may not be a bug at all, but rather just the consequence of device specific software components not yet existing. We just don't and can't know...

If software were a house, a painter having missed a spot in the kitchen could affect the house in a way as to make it look as if a bomb went off in the basement. This is so completely different from what most people consider intuitive that it makes most judgements of unfinished software by laymen pretty much meaningless. Judging the progress of software development requires you to forget most of what you know about how material products evolve. It's easy to grasp how far along the building of a bridge, sculpture or house has progressed, but that intuitive approach simply doesn't apply to software. None of us can really judge W10M's progress without access to a lot more information than any of us currently have.

An example would be the last preview build. MS stated that they fixed over 2000 issues and bugs. How many in this forum could name even 1% of those addressed issues? That demonstrates that MS's progress or speed is not really the problem people think it is. The real issue is people's inability to see even 1% of the progress being made. That is obviously bound to influence people's perceptions in a negative way.

All of this represents a very large risk in terms of how people perceive MS and the W10M preview. We can see this now in the forums in how some people are starting to doubt MS' software competence, or in threads such as this one. I suppose MS thinks the benefits outweigh the risks.

Anyway, last but not least, it seems a lot of people are expecting to get their final/official W10M update in October. People simply can't imagine how the preview could improve "enough" by then. I doubt anybody with an existing device will have W10M officially by October however. October is when MS will release W10M to OEMs. OEMs, including MS, may still have to build drivers and firmware for their own devices, meaning there may be more time than many of us think.
 

flowkidd

New member
Oct 29, 2012
12
0
0
Visit site
Well, android does not have resuming and drains battery, iOS does not have resuming because it has a super CPU.
In other words just buy a windows phone that costs like an iPhone and you won't see any resuming (I have no resuming on my 930 and it costs half an iPhone anyway) :p

My android (HTC One) lasts more than my L925 with WP8.1 and it doesn't have none of this loading.... or Resuming..... madness. Thanks for the reply.
 

Manmikey

New member
Jun 22, 2015
71
0
0
Visit site
My android (HTC One) lasts more than my L925 with WP8.1 and it doesn't have none of this loading.... or Resuming..... madness. Thanks for the reply.

I'm with you on the resuming............ loading............ I have a lumia 640 so I don't expect it to have flagship performance and accept it on this device but that doesn't mean it isn't frustrating to see it so many times in a day. I got the 640 to try out Windows phone and I am enjoying it after years of android. I now intend to get a 950 when they are out however if these high power flagships have loading and resuming pauses in every day use I will probably reconsider, it is just not acceptable for a state of the art flagship to have a performance issue like this. I look forward to the reviews of the first devices!
 

Paolo Ferrazza

New member
Dec 7, 2014
441
0
0
Visit site
I'm with you on the resuming............ loading............ I have a lumia 640 so I don't expect it to have flagship performance and accept it on this device but that doesn't mean it isn't frustrating to see it so many times in a day. I got the 640 to try out Windows phone and I am enjoying it after years of android. I now intend to get a 950 when they are out however if these high power flagships have loading and resuming pauses in every day use I will probably reconsider, it is just not acceptable for a state of the art flagship to have a performance issue like this. I look forward to the reviews of the first devices!

They won't. The resuming/loading screen depends on how much code the coder puts in the resuming part of the app and how fast the CPU will process operations. An app is composed of background and foreground parts when coding.

The background part runs even if the app is suspended.

The foreground part usually stops running when you change app or go to start. Then when the app is reopened the resuming part of the code is executed, in this code the coder must update the GUI accordingly. For example if a new message arrived while in background or the background thread did something worth showing and so on.

So this is all to say that:
-coders should put just a few lines of code, if there is a long operation like fetching something from the net they should first let the app open and then load missing data
-processor speed and fast memory will both mitigate bad coding (not slow net connection)

The only thing MS can do is to create some strategy to oblige developers to have short resuming times (loading-times when first opened), like "if it takes more than x just reinit the app and if reinitializing the app takes more than y just let the app crash with an error" (maybe this is too aggressive but something should be done so developers will receive bad feedback and change their code and so the blame is not put on the OS itself).

Maybe you all knew this, just wanted to give some insight on the matter to those who didn't.

So just to recap, on a 950 you will only have the resuming on really badly coded apps and so you should complain to the developers via the store review system.
 

colinkiama

New member
Oct 13, 2013
2,842
0
0
Visit site
Every OS has resuming.../loading. It's just that WP devs aren't implementing splash screens during loading/resuming (except in the Facebook app)
 

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
They won't. The resuming/loading screen depends on how much code the coder puts in the resuming part of the app and how fast the CPU will process operations. An app is composed of background and foreground parts when coding.

This is all correct in theory, but in practice you can build an empty WP app that does absolutely nothing in response to the resuming event, and occasionally still be confronted with the resuming screen. As far as I'm concerned, if an app is still in memory and doesn't respond to a resuming event, resuming should be instant, but that's just not the case. Something more is going on here that MS isn't telling us.

I don't see these types of resuming delays on iOS.
 
Last edited:

MDK22

New member
Oct 17, 2013
1,375
0
0
Visit site
has anybody considered it might be the apps, not the OS.

The loading/resuming only happens on certain apps (from what I read), I've had NO issue on my Lumia 1520 - but, I'm still on WinPhone 8.1.

The other (troubling) issue is ... people leave their phone ON for weeks (in some cases, months) - a quick reboot (weekly) will fix myriad issues.

As far as Android comparisons, after six months they ALL lag, it's the nature of the beast.
 

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
has anybody considered it might be the apps, not the OS.

The loading/resuming only happens on certain apps (from what I read), I've had NO issue on my Lumia 1520 - but, I'm still on WinPhone 8.1.

The other (troubling) issue is ... people leave their phone ON for weeks (in some cases, months) - a quick reboot (weekly) will fix myriad issues.

As far as Android comparisons, after six months they ALL lag, it's the nature of the beast.

Read my post directly above yours. Based on my analysis I'd say apps can utterly destroy loading / resuming performance. However, even apps that should theoretically resume instantly sometimes do not. I can't say I've witnessed this on iOS. I'd say WP occasionally engages in processing that leads to a resuming delay which intuitively seems unnecessary, but poorly built apps can make that delay far worse.
 

Jazmac

New member
Jun 20, 2011
4,995
4
0
Visit site
Probably on some devices this remains an issue. I don't see this on my HTC One. What I have discovered about this latest build, I cannot enable the battery saver. Makes the phone freak out completely. But I don't have the resume bug. ::Knock wood::
 

Nabkawe5

New member
Dec 19, 2012
544
0
0
Visit site
Those who say that WM10 is a preview seem to forget that WP8.1 is NOT and it still resumes all the time.
 
Last edited by a moderator:

RaRa85

New member
Nov 2, 2011
613
0
0
Visit site
Those who say that WM10 is a preview seem to forget that WP8.1 is NOT and it still resumes all the time.
Yes I wanted to show a friend some pictures I took on my Lumia 1020 last October before my experimental year with Android and I cannot tell you how embarrassing it was to look at a blank home screen and literally wait for the tiles to fill in before going forward to the photos hub.

Sent from my D6616 using Tapatalk
 
Last edited by a moderator:

Members online

Forum statistics

Threads
323,181
Messages
2,243,392
Members
428,035
Latest member
powerupgo