Hey,
I'm considering WP7 and one thing that really concerns me is the apparently painfully slow load times associated with running third party apps.
I've seen reviewers commenting on the huge difference between first and third party software on WP7, but I haven't been able to experience it in the stores because most phones there aren't connected to marketplace.
Anyway, YouTube videos of the Facebook app show incredibly jagged scrolling and a looong load time. This directly contrasts the amazingly smooth and quick UI.
Have you guys experienced this disconnect between first and third party? Are load times really that bad? As I'm switching from an Android device most things load instantaneously, so it'd be a shame to switch to something slow.
Opinions would be greatly valued.
Thanks heaps
yeah, I put alot of it down to devs trying to rush things out the door to get into the market place
That and the type of memory storage used. I personally would recommend one of the samsung or lg phones as their use of NAND storage really helps load times on apps. In the end though, it doesn't make a huge difference, and really like others have said, if devs take the time, it shouldn't take an app too long to load.
Believe me when I say it's not down to the phones/os, but rather hurried coding on the dev's side of things. In general though, everything is crazily fast, minus the few poorly coded apps that I tend to avoid anyway
Alex
Yeah it really comes down to apps on an individual basis. My RSS Reader and Weather Channel apps load fast, but facebook takes about 10-15 seconds to completely load everything. Shazam is pretty fast too but the "painfully long" load times are going to be graphic intensive 3D games. Those can take a minute to get from tapping the icon to actually playing.
Not Slow
jennan88 said:
Hey,
I'm considering WP7 and one thing that really concerns me is the apparently painfully slow load times associated with running third party apps.
I've seen reviewers commenting on the huge difference between first and third party software on WP7, but I haven't been able to experience it in the stores because most phones there aren't connected to marketplace.
Anyway, YouTube videos of the Facebook app show incredibly jagged scrolling and a looong load time. This directly contrasts the amazingly smooth and quick UI.
Have you guys experienced this disconnect between first and third party? Are load times really that bad? As I'm switching from an Android device most things load instantaneously, so it'd be a shame to switch to something slow.
Opinions would be greatly valued.
Thanks heaps
Click to expand...
Click to collapse
Had my Focus since Nov 8. All of my apps have installed very quickly via Zune and Marketplace.
They all load very quickly, as well - MUCH faster than any app on my TP2. Almost all of them have been updated by the devs, though, since thier releases.
I haven't had the same sort of experience to be honest. In terms of loading times everything seems to be fine as far as the apps I've tried. I've heard this stuff as well but it just hasn't been true in my experience.
Yes, I am working on a very intensive 2D game with advanced AIs and animations that will eventually go multi-player after socket support and my startup time is about 2-3 seconds, even with a boatload of sprites and a BIG uncompressed wave file. In addition, it runs absolutely smoothly, as I programmed it in XNA, and I was glad to see that the phone ran my code FAR better than the PC emulator (to the point of perfection).
The storage speed is not THAT bad on MicroSDs. It is bad, compared to other things, but horrible initializations and bad code will simply result in long startup times. I haven't even cleaned my code up yet and I am doing it with a partner, so it needs a lot of cleaning up.
Regardless, devs also need to realize that they cannot continue to re-allocate continuously like they do on PCs, as the bytecode interpreter does a clean-up of all the memory on the phone whenever new space is needed. It is sad that developers can't get these things through their thick skulls.
Honestly, I don't know why these programs have such long startup times. I can imagine with a MicroSD and a 3D game with lots of data to load, like Assassin's Creed, there could be a long load, but for some reason simple apps like Facebook and such aren't living up to even mediocre load and run speeds.
water911 said:
Yes, I am working on a very intensive 2D game with advanced AIs and animations that will eventually go multi-player after socket support and my startup time is about 2-3 seconds, even with a boatload of sprites and a BIG uncompressed wave file. In addition, it runs absolutely smoothly, as I programmed it in XNA, and I was glad to see that the phone ran my code FAR better than the PC emulator (to the point of perfection).
The storage speed is not THAT bad on MicroSDs. It is bad, compared to other things, but horrible initializations and bad code will simply result in long startup times. I haven't even cleaned my code up yet and I am doing it with a partner, so it needs a lot of cleaning up.
Regardless, devs also need to realize that they cannot continue to re-allocate continuously like they do on PCs, as the bytecode interpreter does a clean-up of all the memory on the phone whenever new space is needed. It is sad that developers can't get these things through their thick skulls.
Honestly, I don't know why these programs have such long startup times. I can imagine with a MicroSD and a 3D game with lots of data to load, like Assassin's Creed, there could be a long load, but for some reason simple apps like Facebook and such aren't living up to even mediocre load and run speeds.
Click to expand...
Click to collapse
Yeah, my application also loads completely in about 2 seconds, and in general, most of the apps I have used have been pretty quick. Facebook is probably the biggest exception.
Agree with everyone else, it's due to the devs not knowing what they are doing - which in turn is down to the platform still being new (lots of devs still do not have a device and use only the emulator for testing). I've seen vast improvekents as apps have been updated though, so wouldnt worry about it.
In regards to what some people have been saying about Nand vs MicroSD, is there actually that big of a difference?
I'm tossing up between Trophy, HD7 or Omnia 7, so I'd like to know if I'm shooting myself in the foot by buying HTC because I prefer LCD to AMOLED
jennan88 said:
Hey,
I'm considering WP7 and one thing that really concerns me is the apparently painfully slow load times associated with running third party apps.
I've seen reviewers commenting on the huge difference between first and third party software on WP7, but I haven't been able to experience it in the stores because most phones there aren't connected to marketplace.
Anyway, YouTube videos of the Facebook app show incredibly jagged scrolling and a looong load time. This directly contrasts the amazingly smooth and quick UI.
Have you guys experienced this disconnect between first and third party? Are load times really that bad? As I'm switching from an Android device most things load instantaneously, so it'd be a shame to switch to something slow.
Opinions would be greatly valued.
Thanks heaps
Click to expand...
Click to collapse
from my experience, they aren't slow to load (except for games), but they are very slow to resume. If you try to navigate back to one using the back button, or if your screen locks while a third party app is open, it takes quite a while for the app to "resume" to where you left off
This a main concern of mine. Apps that would run smoothly on Android like Facebook, IMDB, Last.fm, etc. run slow as molasses on WP7. Hopefully MS starts putting these devs in order or else I'm walking.
zukа said:
In regards to what some people have been saying about Nand vs MicroSD, is there actually that big of a difference?
I'm tossing up between Trophy, HD7 or Omnia 7, so I'd like to know if I'm shooting myself in the foot by buying HTC because I prefer LCD to AMOLED
Click to expand...
Click to collapse
Out of curiosity, why do you prefer LCD over AMOLED?
People talk about how high contrast AMOLED is, and that's true - it is. But I find it's oversaturated to a point where nothing looks natural - a photo that displays perfectly well on LCD will look like a horribly photoshopped nightmare on AMOLED.
The main problem for me, though, is color banding.
http://www.mobiletechworld.com/2010/11/17/the-problem-with-super-amoled-screens-nasty-color-banding/
I can't stand it
I am sure that it is third party most of the time, Weave (the RSS reader that I use) actually loads up rather quickly and it just went through an update a couple days ago. The update also made the resume time pretty quickly.
Moral of the short story, it depends on the developer most of the time. The quick apps are usually the ones that have been updated recently while the slow ones, haven't. Not the OS problem.
Although, games sometimes load up rather slow based on my experience. Hoping the update improves load times for games by a large margin.
manny84 said:
This a main concern of mine. Apps that would run smoothly on Android like Facebook, IMDB, Last.fm, etc. run slow as molasses on WP7. Hopefully MS starts putting these devs in order or else I'm walking.
Click to expand...
Click to collapse
Out of those three apps, the only one running slow is Facebook - which is completely due to the way it's written.
In general, apps are fairly fast both to load and resume now (recently released or updated ones that is). Also, the "January" update comes with memory optimization which further shortens load times (although mostly for games).
Just my $0.02, but coming from a Touch Pro 2 ALL the load times seem fast, even Facebook and games. I also have an iPod Touch 4G and my WP7 load times are on par with that.
Related
I love my Desire and I cannot envisage swapping it for any other phone (except maybe a similar model with a keyboard!). It's obviously one of, if not THE best phone around at the moment.
The only thing I'm slightly envious of is the smooth scrolling of the iPhone. When I scroll through my "All programs" screen it's ever so slightly choppy. Same if I scroll through a long text message conversation. Hardly noticeable unless you put it next to an iPhone.
My question is this: since the Desire has so much horsepower, is it possible to optimise the interface so it's perfectly smooth like iPhone? I don't know anything about development, and suspect this is something that could only be changed by the Android designers, but is there any way a talented dev could do this in a ROM? Anyone care to explain to me yes/no, and why?
Thanks!
I tried out home++ beta yesterday, unfortunately it's not optimised for the desire yet (lots of icons missing) but the app list is silky smooth. I think its poor implementation on gooogle/htc's part rather than the phone being at fault.
Also I'm using handcent for text messaging, its smooth aswell, didnt notice any problems with stock messages app though.
I noticed the choppy scrolling on older Android phones, but I have not had that issue with the Desire yet. It's as smooth scrolling as possible. Even when I put my Desire next to an iPhone 3gs it is fast and smooth. The Desire is even a bit more responsive then the iPhone, which is very noticeable when typing.
-------------------------------------
Sent from my HTC Desire
I would say my Desire is definitely fast, but not so smooth. When lists scroll or things open and close on the iPhone it is a definite, measured type of action - it happens at consistent speed from the beginning to the end of the action/animation. No jerking or choppyness at ALL. Whereas on my Desire, despite it's 1gig processor, it doesn't achieve that same effect in all places.
I don't know how else to describe it. It's one of the only places Desire falls down compared to iPhone (oh, apart from the lousy video playback, poor camera recording framerate, cheap touchscreen and poor screen performance in sunlight!).
setspeed said:
I would say my Desire is definitely fast, but not so smooth. When lists scroll or things open and close on the iPhone it is a definite, measured type of action - it happens at consistent speed from the beginning to the end of the action/animation. No jerking or choppyness at ALL. Whereas on my Desire, despite it's 1gig processor, it doesn't achieve that same effect in all places.
I don't know how else to describe it. It's one of the only places Desire falls down compared to iPhone (oh, apart from the lousy video playback, poor camera recording framerate, cheap touchscreen and poor screen performance in sunlight!).
Click to expand...
Click to collapse
I noticed that too.
Menu scrolling isn't what i'd call choppy but it's just not AS smooth as the iPhone. This is especially apparent near the end of any menu for some reason.
An example of perfect scrolling speed on the Desire would be the settings menu. That is perfect, no choppiness, no lag, just perfect. Things like the app drawer and sometimes even the homescreens appear to drop a few frames from time to time.
I agree with you, is not smooth like iphone, even being faster than it. Maybe google needs to improve the ui of android to optimize it.
-------------------------------------
Sent via the XDA Tapatalk App
I think it's rather HTC's fault, cause in the stock Android apps everything is perfectly smooth here. Only the HTC apps sometimes stutter while scrolling.
I'm on an htc hero and notice the same thing. This is something htc needs to release a fix for
-------------------------------------
Sent via the XDA Tapatalk App
Check the clock when you scroll back to it - if an earlier time you see it for a microsecond when you scroll
yeah its definitely not anywhere as smooth as the iphone, scrolling through most lists is incredibly choppy, even my years old 1st generation ipod touch is silky smooth (even when scrolling through a list of albums with album artwork on each one)
but as someone has said, it seems to be only htc stuff thats like this (the messages app, the app drawer) other areas such as the settings scroll smoothly.
Not anywhere as smooth? Come on, don't exaggerate. It's almost the same as the iPhone, actually.
If you've ever used a Windows Mobile phone, you know what "not anywhere as smooth" means!
But still, of course, any improvement is welcomed...
shaundalglish said:
If you've ever used a Windows Mobile phone, you know what "not anywhere as smooth" means!
Click to expand...
Click to collapse
LMAO!!!!
+1
yeah, but using live wallpapers will definitely slowdown the scrolling in the homescreen. It's not much, but noticable. Without using live wallpapers, the scrolling is as smooth as it should be.
iphone scrolls page to page, of course this is smoother. Iphone can't handle scrolling over the entire page/apps.
And an Iphone is a dump of icons, doesnt sound like a smartphone to me
Remember the iPhone screen resolution is only 480x320 as well, significantly less than the Desire. Much less screen estate to move around.
Yep, +1
I mainly see this when scrolling to the bottom of the All Program menu.
There are others with this too:
URL blocked by XDA - Search for "lag program menu htc desire" another post in XDA by other users
I emailed HTC about the small amount of lag but they said to return my phone for an exchange! Slightly unnecessary.
Hopefully more people post their lag issues here, HTC see it and do something about it for their 2.2 release.
I've tried various things to try and resolve - made sure no other programs are running, no live wallpapers, no wallpaper at all
Its not a massive problem, but there is no noticeable lag in the stock 2.1 Android Apps drawer - so we know it shouldnt be an issue.
It does stutter a bit done it on all android phones i had from htc, if you use Helixlauncher 2 though that has a much nicer scroll menu and its as smooth as butter, i would love if they could add this style into the Sense system as it looks far better.
iPhone sucks man, if you like it why don't you buy one and you'll have your A LA iPhone smooth scrolling... Jeez, i don't understand soome people.... You have a Desire and still wanting an iPhone... SUCKS!
Using MCR (Modaco Custom Rom) here, without SenseUI. Then decided to install ADWLauncher, and to be honest the scrolling on the main screen/app drawer is super smooth now. So I'd say that this probably is HTC's 'bad' programming on the SenseUI.
phunkycow said:
Using MCR (Modaco Custom Rom) here, without SenseUI. Then decided to install ADWLauncher, and to be honest the scrolling on the main screen/app drawer is super smooth now. So I'd say that this probably is HTC's 'bad' programming on the SenseUI.
Click to expand...
Click to collapse
that looks cool, I think SensUI is starting to get useless since google implemented many Sense-features into standard android too. The only thing that keeps me having SenseUI is the HTC-clock. I don't like the standard Android-clock widgets. Other than that, I think Sense is starting to get more and more useless. Last year, with android 1.5, Sense was pretty usable.
About 3 months ago (end of march?) I upgraded from my old trusty Hero to the new HTC Desire, and as everyone who has had the joy of owning one I've been very happy with it, specially after (with the unvaluable help of XDA) I managed to iron out some of its quirks.
My only issue with it is that lately I keep getting the annoyng taskbar icon and message that says that there's no more space available on my phone and that I should delete some more apps to free some more space.
I constantly kept reducing the number of my apps every few days, renouncing to some I was quite fond of, and eliminating all double functions even though I liked to have the possibility to choose, but the space keeps getting smaller and smaller, not because I install more apps , but only because I update the apps I already have.
Every time I update my apps the newer versions apparently take more space than the ones they substitute, so that nearly every time I update I am forced to erase at least one of my apps.
Soon I'll have space for only one super-updated app !
I have noticed that the "no more space" icon & message pops up every time the free space goes under 10% and after the latest updates I have only 9% ( 13 mb) left.
The problem is that now I have just the absolutely necessary apps, those I feel I just can't do without.
All in all , including all the original apps and programs that came with the phone and that it's impossible to erase, I've got 128 icons on my menu.
Is that many?
I'm pretty sure that I had more in my old Hero.
On my other phone , an HTC HD2, I have found a very useful app (for win mob 6.5) that frees memory and even speeds up the phone, does anyone knows of an equivalent program for Android 2.1?
Or maybe of some way to get some free space by some other method, like moving something to the mem card, or getting rid of some useless stuff?
Please?
This thing is getting relly frustrating.
No way to solve this issue barr flashing a FroYo rom or installing APPS2SD
Easier to install a FroYo rom but they are still buggy.
PlexusXXX said:
About 3 months ago (end of march?) I upgraded from my old trusty Hero to the new HTC Desire, and as everyone who has had the joy of owning one I've been very happy with it, specially after (with the unvaluable help of XDA) I managed to iron out some of its quirks.
My only issue with it is that lately I keep getting the annoyng taskbar icon and message that says that there's no more space available on my phone and that I should delete some more apps to free some more space.
I constantly kept reducing the number of my apps every few days, renouncing to some I was quite fond of, and eliminating all double functions even though I liked to have the possibility to choose, but the space keeps getting smaller and smaller, not because I install more apps , but only because I update the apps I already have.
Every time I update my apps the newer versions apparently take more space than the ones they substitute, so that nearly every time I update I am forced to erase at least one of my apps.
Soon I'll have space for only one super-updated app !
I have noticed that the "no more space" icon & message pops up every time the free space goes under 10% and after the latest updates I have only 9% ( 13 mb) left.
The problem is that now I have just the absolutely necessary apps, those I feel I just can't do without.
All in all , including all the original apps and programs that came with the phone and that it's impossible to erase, I've got 128 icons on my menu.
Is that many?
I'm pretty sure that I had more in my old Hero.
On my other phone , an HTC HD2, I have found a very useful app (for win mob 6.5) that frees memory and even speeds up the phone, does anyone knows of an equivalent program for Android 2.1?
Or maybe of some way to get some free space by some other method, like moving something to the mem card, or getting rid of some useless stuff?
Please?
This thing is getting relly frustrating.
Click to expand...
Click to collapse
Wait until 23 June.. I got some info.. Froyo for HTC Desire will coming
PlexusXXX said:
...On my other phone , an HTC HD2, I have found a very useful app (for win mob 6.5)
Click to expand...
Click to collapse
OT: how do you like your Desire compared to the HD2?
I have the HD2 and I think the phone hardware is great, love the screen and the RAM and ROM. So far the best phone I have ever had, and I have had a lot.
I would love to try Android (would love to have it on a phone with the HD2 specs - and ATT )
...On my other phone , an HTC HD2, I have found a very useful app (for win mob 6.5)
Click to expand...
Click to collapse
OT: how do you like your Desire compared to the HD2?
I have the HD2 and I think the phone hardware is great, love the screen and the RAM and ROM. So far the best phone I have ever had, and I have had a lot.
I would love to try Android (would love to have it on a phone with the HD2 specs - and ATT )
Click to expand...
Click to collapse
I came from HD2 as well and I have to agree that HD2 hardware is far more superior than the Desire. The build quality is good, large screen is gorgeous.
However, I prefer Android so much more than Winmo. Glad that I made the switch.
Sent from my HTC Desire
myth1001 said:
I came from HD2 as well and I have to agree that HD2 hardware is far more superior than the Desire. The build quality is good, large screen is gorgeous.
However, I prefer Android so much more than Winmo. Glad that I made the switch.
Sent from my HTC Desire
Click to expand...
Click to collapse
it seems to be THE OS everyone is going to. I will wait until 2.2 gets on a phone that I can use with ATT, and that might only be a month away.
This is a known issue, I've had it but it seems to have gone. While I have no 100% sure cure I will try to give you some advice, hopefully it will solve the problem.
Question (please reply) : does your phone take a lot (I mean A LOT) of time to power down? I ask this because I feel there's a problem with the Desire's shutdown routine, it should clear some cache and old/obsolete data during shutdown but sometimes it fails.
Back to your problem, you have 2 options: try to force the phone to do the right thing and reclaim space OR restore to factory default and reinstall everything. Of course, second option is a little bit painful but as you have already been forced to uninstall most of the apps you'll have less to reinstall after a full wipe.
As for first option:
- try to power down / reboot your phone several times in a row; be patient, let it do it's thing, don't pull the battery out.
- power down your phone then power up by keeping MENU key pressed until it boots up: this will force it into safe mode (it only loads apps installed in the ROM, not the ones you added later). Can't really tell you why/how this helps but it solved my problem and it doesn't hurt to try. After booting into safe mode check the amount of space you have: should be OK now. Power down the phone and power up normally.
- check your apps (Settings, applications, manage applications) to see which ones take so much space. Maybe it's the browser cache, maybe Gmail storage or whatever. After taking care of one or more of them (e.g. clear browser cache) reboot your phone (power it down as it should, not by pulling battery out, to allow it to do it's shutdown routine).
I really hope this helps, I know how frustrating it can be. Froyo can't come soon enough! Or some real/safe root method.
I have been experiencing similar problems (although far less extreme), I tried starting in safe mode, clearing the browser cache and restarting, my free memory went from 74Mb to 105Mb but this change only showed up after the restart.
Thanx for the the prompt answers and the suggestions which I am trying right now.
I did'nt think about emptying the the browsers' caches because I thought that this kind of data would be kept in my capacious 16GB sd card.
I'm gonna do it right away because I use 3 browsers: Opera as default, but also Xscope and Dolphin which are really great to watch flash videos and I love watching long BBC documentaries in my spare time.
Besides I just noticed that Xscope automatically clears its cache on exit (if the option is activated) and Dolphin stores it on the memo card (also if the option is checked).
As for your questions.
1) No, my Droid switches off (and on ) very fast, much faster than my old Hero or my old N97, or my old Omnia, faster than my old HTC HD, and even slightly faster than my (actual) HTC HD2.
I guess it's thanks of the snappy Snapdragon CPU.
2) I do feel a bit silly having 2 phones but after having tried a Hero I just had to buy one and once I did I immediatly became a true Android convert.
I use Gmail, Gdocs, Gcalendar as my basic programs and iGoogle is my startpage , moreover the choice of free apps on Android market is without equal (i know because my wife insists on using iPhone 3GS, and now she even bought a 27" iMac hoping to get the same seamless sync'ing I get with my google apps on PC and my Android phone).
But no matter how much I love Android, the HD2 ,( which I had since september 2009) is just too good to let it go.
Forget about all the great Android Apps, but to watch pics, vids, to read e books and downloaded PDF pages, and also to listen to music it has no equal (in my opinion).
The camera and videocam (after applying the latest firmware and the fixes found here on XDA) are better than those on the Desire.
The voice dialing for the HD2 just works (thanx to dutty's work) also via BT headset and headphones, while the Desire's best voice dialing app (choice dialer) still tends to suck and the lack of a dedicated "call" button makes things even worse .
For one like me, who spends most of his waking time driving a car , voice dialing is a must; and the one Dutty fixed for the HD2 is just great.
Last but not least I bought that beautiful HD2 active holder for table and car (which does not fit the Desire) and I also bought CoPilot sat nav for the HD2 which works perfectly too.
As an excuse for having 2 phones usually I say that I need one for business and one for private use and maybe sometimes it's true too.
I usually keep the Desire in my pocket and the HD2 in my car or briefcase.
In any case because of my job, most of the time (nearly always actually) I am obliged to find space in my briefcase for a good bridge camera, a little vidocam, a dictaphone, and my netbook with accessories and peripherals, plus assorted gizmos according to the specific situation at hand, so the HD2 doesn't really change much in terms of weight.
Unfortunately the only phone that maybe would be able to substitute both my phones would probably be the HTC EVO but it seems like this beauty will never make it to our decadent european continent.
So I look forward to be able to buy the Dell Streak (mini5) and I really hope that next month , once hopefully I'll finally manage to wrap my fingers around it, I will not end up carrying 3 phones.
What do you think?
I'm a desperate case?
OF course not, you are like me and other Desire users... I'm not sorry i bought the phone and even thought that i wouldn't mind having such little space for apps, but really - we have so many apps and can't installed it because of the limited space...
This is also HTC fault because they have to win money, but for what we pay for the Desire and others, we really shuld have bigger internal space (1GB was enough for now).
Froyo will surely solve our main problems, and i also have 2 phones...
I will replace my simple Nokia when WP7 will be released at the end of the year, since i will never have an Apple device bought my me.
The i will have the two best: Android and WP7 - and i know that WP7 won't suffer from another annoying thing on Android: platform fragmentation. I'm sure that all WP7 devices will be automatically updated to latest versions of the OS which not occur with Android phones.
W7 looks poised to be a winner, however in my opinion Sense UI and the changes that HTC made to win mobile 6.5 for the HD2 , are so good that I really don't thik that this particular device needs a different OS.
HTC managed the incredible feat of making win 6.5 good, easy and a plasure to use.
In fact probably when (if) an upgrade for the HD2 will become available , I don't think that I will rush to install w7, which (as all new OSs) will probably see the light burdened with all sorts of bugs, glitches, and childhood diseases, while the newest ROM for HD2 coupled with Sense UI is eminentely stable, and just... good.
What win would need to compete with android is the so called "ecosystem" or "environment" : apps (specially free apps) and integration with cloud services, like Android does with Gmail, Gmaps (with sat nav), Gdocs, Gtalk, Gcalendar, Gtranslate, etc. etc.
I mean, have you seen the Windows marketplace? It's pathetic.
Even OVI market for my old N97 was better than this and I remember that it relly sucked.
They even removed the few free apps there used to be.
As good as W7 will turn out to be, one thing no OS can do is fixing this kind of structural weaknesses in the win "ecosystem".
I think it's for HTC's own good to update the Desire as soon as possible since potential buyers could go out to buy a Nexus if they wait too long.
With the Hero-update, it's another story I think because there were some issues and I think performance was one of them. And that way, HTC managed Hero users to go out and buy the Desire.
But this time, they can't do that move since the Desire is their top-device and the Nexus is a rival although they created the device. HTC would rather people buy the Desire than the Nexus of course.
PlexusXXX said:
W7 looks poised to be a winner, however in my opinion Sense UI and the changes that HTC made to win mobile 6.5 for the HD2 , are so good that I really don't thik that this particular device needs a different OS.
HTC managed the incredible feat of making win 6.5 good, easy and a plasure to use.
In fact probably when (if) an upgrade for the HD2 will become available , I don't think that I will rush to install w7, which (as all new OSs) will probably see the light burdened with all sorts of bugs, glitches, and childhood diseases, while the newest ROM for HD2 coupled with Sense UI is eminentely stable, and just... good.
What win would need to compete with android is the so called "ecosystem" or "environment" : apps (specially free apps) and integration with cloud services, like Android does with Gmail, Gmaps (with sat nav), Gdocs, Gtalk, Gcalendar, Gtranslate, etc. etc.
I mean, have you seen the Windows marketplace? It's pathetic.
Even OVI market for my old N97 was better than this and I remember that it relly sucked.
They even removed the few free apps there used to be.
As good as W7 will turn out to be, one thing no OS can do is fixing this kind of structural weaknesses in the win "ecosystem".
Click to expand...
Click to collapse
Well its been a long time since I have played with any winmo device, but I believe ms will make things right with wp7. They already announced new live wave 4 and hotmail support for POP3 and a lot of new techs. Also the so called ecosystem is going great, wp7 will have Xmas and xbox games on it (you will be able to play the very same games on mobile, xbox and pc). The new demos I have seen are amazing and done in very little time, and this is great for developers. One thing that I should expect is, although I like the new OS aspect, they intend that all devices should look the same. This is good for the final user, but for me, an enthusiastic user, I would want to make it more customized. Maybe latter on we will see this happening, but I will bet wp7 will rock! If only Nokia would put all their potential in making great phones with Android and wp7, that would be also great! Fingers crossed
Necroman_AI said:
Well its been a long time since I have played with any winmo device, but I believe ms will make things right with wp7. They already announced new live wave 4 and hotmail support for POP3 and a lot of new techs. Also the so called ecosystem is going great, wp7 will have Xmas and xbox games on it (you will be able to play the very same games on mobile, xbox and pc). The new demos I have seen are amazing and done in very little time, and this is great for developers. One thing that I should expect is, although I like the new OS aspect, they intend that all devices should look the same. This is good for the final user, but for me, an enthusiastic user, I would want to make it more customized. Maybe latter on we will see this happening, but I will bet wp7 will rock! If only Nokia would put all their potential in making great phones with Android and wp7, that would be also great! Fingers crossed
Click to expand...
Click to collapse
MeeGo/Maemo > Android > Windows Phone 7
I cant complain TOO much, seeing how my work pays for the service...but these TP2 with WM 6.5 are sooooo buggy and sluggish and doggy.....i ran out of other words for slow.....
We got them because they run a program that we use @ work....even the program sucks on this phone.
From all ive read..the only good thing about these phones...are the fact that you can make them look and feel like other phones that suck less....(android)
so......
short of a hard reset....how the hell do you make these phones "fast"
it seems like I spend most of my time waiting for the phone to react to the task that I just asked it to do.
I clear ram, I delete SMS/MMS.....nothin.
I wanna spike it like a football and poop on It's carcass
6.1 Titanium. It's fast, ugly, and not functional at all. Basically WinMo slightly sped up.
It's an older phone, pretty good for its day but fairly underpowered compared to today's phones.
That being said, it is absolutely packed full of features, which is why I love it.
arrrghhh said:
6.1 Titanium. It's fast, ugly, and not functional at all. Basically WinMo slightly sped up.
Click to expand...
Click to collapse
say what? Actually comparing titanium to SPB mobile shell, I have to say the latter is faster, at least compared to energy rom titanium 6.1.
As for the functionality I find it better because you can get twice as much done while the stupid sense interface is busy loading/freezing up.
I'm not happy with the speed of the phone, even running slimmed down roms its still slow and will never open anything instantly. But as has been mentioned, the functionality is 2nd to none. I honestly think for a 'business' phone, i.e. replacing a laptop, windows mobile is the best OS by far. And the slide out keyboard is almost mandatory to make it work properly
Things such as mapping fn+c = ctrl+c/copy. fn+z = ctrl+z/undo, shift+SMS = escape key. fn+up/down/left/right = pgup/pgdown/home/end. These are not possible with an onscreen touch pad, nor do I believe they are natively supported in android or ios. If you ever want to essentially use a desktop in the field then it's fantastic having native support for just about every windows' basic function straight out of the box. Even if you have to custom map keys at least you don't need to write software to perform those functions.
I've tried using things such as remote desktop connections on android phones and I lack the ability to do certain things on the fly, such as if I want to move a file, I have to use the crappy right click shortcut (usually 2 finger tap or something like that) and do it that way. Whereas because this is a windows environment I simply hit fn+x / fn+v. Syncing files, reading files and handling the file system is up to 'me', not up to the hopeless proprietary software i.e. itunes/apple
As I've noticed that most (if not all) Android phones I've ever tried have been suffering from the "non-fluid" issue. The homescreen and apps experience might be fast but they're not fluid like ones found on iOS or Windows Phone and I'm guessing that it's because previous Android phones doesn't have the 2D gpu acceleration. ICS has added the feature and I'd like to ask those owner out there if the experience is now as fluid as iOS or WP7? watching video review doesnt help because videos are formatted into 30fps. Even GS2 doesn't appear to be fluid (aka I dont think it's running at 60fps)
The home screen and app launcher are very fluid if you have a static wallpaper. With a live wallpaper there is considerable slow down. Some wallpapers are less CPU intensive than others though.
Sent from my Galaxy Nexus using XDA App
Android's fluidity is actually due to more than just Hardware acceleration. Most Gingerbread phones come out of the box very quick (Nexus S) and really glide without any apps installed. Hardware [was] acceleration is a big problem, as you were throwing efficiency out the window in order to run on everything. Now with it HW Acceleration, the slickness of the OS has multiplied exponentially giving you an experience on par with iOS (Joshua Topolsky, The Verge)
Now, here comes the real problem, apps. Android apps have the most freedom in the developer sense, and are also the most lax on what is allowed in the market. While iOS dev kit requires a stringent agreement and agreement to an app review process before getting your license, Google's Android Market is nothing like that. If you can pony up $25 (a requirement only recently), you can publish whatever the hell you have made, no matter how ugly, useless, or inefficient it is. Google's toolbox for Devs is great, even greater in terms of options in app making, but enforces no standards or required templates. This is why iOS apps all have the same look and feel while Android's app range from great to complete ****. This makes a lot of sense though as Android started late in the game, so they needed to bring up the app numbers, no matter how many were ugly soundboards or battery hog games.
With ICS, Google is taking a step in the right direction by offering the HOLO hook for developers, which will allow apps to be "prettied up" for ICS instantly. Also, more efficient protocols have been added to keep battery life and smoothness up, such as a revised Garbage Collector (actually, I think they removed it entirely) and allowed apps to share information with each other. The Garbage Collection is what make your phone lag, as it is recycling the unused code on the apps you're running in the background. The new location hook allows apps to now constantly turn on your GPS to pull your location, as they can simply request it from other apps if they don't need the most up-to-date info or if you just recently used your location on another app. The OS should be as fast as any other on the stock level, and as soon as the Apps become ICS friendly and more efficient, Android will truly have people falling in love with it
Chrono_Tata said:
With a live wallpaper there is considerable slow down. Some wallpapers are less CPU intensive than others though.
Click to expand...
Click to collapse
This is particularly annoying. My last Android (Nexus One) was pretty smooth on almost all live wallpapers - certainly on the stock ones. The Galaxy Nexus lags like hell (slow juttery screen swiping) on all of them except one of them. Very, very disappointing and hope it gets fixed somehow.
Live Wallpaper
Thank you everyone, I'm now ordering one for myself and hopefully there won't be a let down on the UI experience!
rikbrown said:
This is particularly annoying. My last Android (Nexus One) was pretty smooth on almost all live wallpapers - certainly on the stock ones. The Galaxy Nexus lags like hell (slow juttery screen swiping) on all of them except one of them. Very, very disappointing and hope it gets fixed somehow.
Click to expand...
Click to collapse
Strange, I owned Nexus One too and live wallpaper (stock one) isn't running at acceptable frame rate at all....it's laggy and sluggish (i changed from iPhone 3G and that might explain why)
May be you can try changing live wallpaper on Galaxy Nexus cuz the one u'r using might not be that optimized?
PS. One more question, how u guys find the battery life?
dnlsmy said:
Also, more efficient protocols have been added to keep battery life and smoothness up, such as a revised Garbage Collector (actually, I think they removed it entirely) and allowed apps to share information with each other.
Click to expand...
Click to collapse
No, they most certainly did not remove the garbage collector but they implemented a more modern algoritm for it and it now makes sure to run on a different CPU core as to not take CPU cycles from the app. A garbage collector is part of the Java platform and could never just be removed since that would result in constant memory leaks that would result in a crash as soon as you filled up all the memory.
When will the stuttering laggy UI experience be addressed?
I'm tired of all the mis-information. There's a pattern: Google is about to release a new handset, they don't show the handset scrolling in any of their ads, or if they do, it's super-imposed. A handful of 'mainstream' bloggers praise the handset calling it quick and responsive and lag free. You buy into it, buy the handset, and the basic UI is anything but CONSISTENTLY fluid and responsive.
I stupidly bought the Galaxy Nexus, really wish I hadn't. Here's just one example of the issue: I have an SMS thread with a mere 27 SMS messages between a friend and myself. When I scroll the up or down the thread, it's embarrassingly choppy (stuttery - don't know what word to use for it). It's extremely unpleasant, and completely ruins the end-user experience.
What annoys me is that Romain Guy closed Android Issue 6914, claiming that it was implemented in ICS. Now ICS is here, and the Android phone is still plagued with the stutters and non-fluidness Android is renowned for. Thankfully someone else has opened a new issue (Android Issue 20278), and hopefully this time Google will FULLY address the issue.
Understandably, it annoys some people more than others. Any user who has experienced a mobile UI that is buttery smooth and fluid (free from 'jitters' and 'stutters'), and where a page or menu sticks to your finger like a magnet when you scroll, would not be able to put up with what Samsung and Google have produced. It's what the kids today would call an 'epic fail'.
---------- Post added at 10:17 PM ---------- Previous post was at 10:11 PM ----------
I'm tired of all the mis-information. There's a pattern: Google around about to release a new handset, they don't show the handset scrolling in any of their ads, or if they do, it's super-imposed. A handful of 'mainstream' bloggers praise the handset calling it quick and responsive and lag free. You buy into it, buy the handset, and the basic UI is anything but CONSISTENTLY fluid and responsive.
I stupidly bought the Galaxy Nexus, really wish I hadn't. Here's just one example of the issue: I have an SMS thread with a mere 27 SMS messages between a friend and myself. When I scroll the up or down the thread, it's embarrassingly choppy (stuttery - don't know what word to use for it). It's extremely unpleasant, and completely ruins the end-user experience.
Understandably, it annoys some people more than others. Any user who has experienced a mobile UI that is buttery smooth and fluid (free from 'jitters' and 'stutters'), and where a page or menu sticks to your finger like a magnet when you scroll, would not be able to put up with what Samsung and Google have produced. It's what the kids today would call an 'epic fail'.
scott.deagan said:
I'm tired of all the mis-information. There's a pattern: Google is about to release a new handset, they don't show the handset scrolling in any of their ads, or if they do, it's super-imposed. A handful of 'mainstream' bloggers praise the handset calling it quick and responsive and lag free. You buy into it, buy the handset, and the basic UI is anything but CONSISTENTLY fluid and responsive.
Click to expand...
Click to collapse
I find this to be untrue, the experience for me has been really good so far. Not perfect but its close. They have come a long way, it'll only get better.
And if you think any of the ads including apple are using true device operation in their advertising you are fooling yourself.
Sent from my Galaxy Nexus using Tapatalk
Can one of you guys post some video footage of said lag? I just ordered a Galaxy Nexus and can still cancel it. Thanks!
Yea there is an iPhone YouTube video performing the exact same steps they show in the commercials and it takes a LOT longer in real life.
Oh well.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
serialtoon said:
Can one of you guys post some video footage of said lag? I just ordered a Galaxy Nexus and can still cancel it. Thanks!
Click to expand...
Click to collapse
Not something worth canceling your order for, it's barely noticeable.
Nexcellent said:
Not something worth canceling your order for, it's barely noticeable.
Click to expand...
Click to collapse
Its the main reason i left Android. Hoping that one day they will use GPU rendering to assist with UI fluidity. If that is present, its enough for me to cancel an order. Ive been a long time Android enthusiast, but the UI sloppiness is what has kept me from keeping an Android phone for too long.
As a fellow UI lag hater I can tell you it's still there in some places. The problem is, although the base of ICS supports and uses GPU acceleration, 3rd party apps dont yet, and even if you "force" it in the developer settings, it isn't compatible with some apps, and will sometimes cause crashes.
That said, it is ages ahead of Gingerbread, but still not as smooth and fluid as iOS and WP7; not even the GPU accelerated parts.
ICS is a big improvement over gingerbread in terms of fluidity.. but it's not on the same level as iOS and WP 7 yet.
UI lag is one of the things I always hated about Android.. and I feel better about ICS than previous versions.. but they still need to improve it if they want to be on the same level as Apple and Microsoft.
FWIW, I bought the phone having read in several reviews that the phone still suffered (albeit much less) from the usual android-lag. It now compares favorably to iOS and the windows mobile platform, just doesn't match or pass them in fluidity and smoothness.
In my experience, many aspects of the UI are "buttery-smooth" and whatever else reviewers usually say. However, there are still a good amount of moments where lag and hangups are present. The difference is, I'm ok with that. I've accepted the phone for it's plusses, despite it's minuses.
To be clear though, it does lag and hang from time to time. Rebooting once a day helps and I believe forcing GPU rendering under developer settings generally helps.
Sent from my GNex
Dont forget that Andoid does much more in the background and foreground compare to iOS or WP7.
Think multitasking, customization, widgets, etc.
It is understandable Android cannot be as smooth as those iOS and WP7.
And for me, it is more than good enough. I wont ditch Android because it might lag a little bit, because the advantages are much more valuable.
---------- Post added at 11:58 AM ---------- Previous post was at 11:48 AM ----------
Here, this just in ... a thorough explanation from Google Developer about Android graphics:
https://plus.google.com/u/0/105051985738280261832/posts/2FXDCz8x93s
I copied the text here:
How about some Android graphics true facts?
I get tired of seeing so much misinformation posted and repeated all over the place about how graphics rendering works on Android. Here is some truth:
• Android has always used some hardware accelerated drawing. Since before 1.0 all window compositing to the display has been done with hardware.
• This means that many of the animations you see have always been hardware accelerated: menus being shown, sliding the notification shade, transitions between activities, pop-ups and dialogs showing and hiding, etc.
• Android did historically use software to render the contents of each window. For example in a UI like http://www.simplemobilereview.com/wp-content/uploads/2010/12/2-home-menu.png there are four windows: the status bar, the wallpaper, the launcher on top of the wallpaper, and the menu. If one of the windows updates its contents, such as highlighting a menu item, then (prior to 3.0) software is used to draw the new contents of that window; however none of the other windows are redrawn at all, and the re-composition of the windows is done in hardware. Likewise, any movement of the windows such as the menu going up and down is all hardware rendering.
• Looking at drawing inside of a window, you don’t necessarily need to do this in hardware to achieve full 60fps rendering. This depends very much on the number of pixels in your display and the speed of your CPU. For example, Nexus S has no trouble doing 60fps rendering of all the normal stuff you see in the Android UI like scrolling lists on its 800x480 screen. The original Droid however struggled with a similar screen resolution.
• "Full" hardware accelerated drawing within a window was added in Android 3.0. The implementation in Android 4.0 is not any more full than in 3.0. Starting with 3.0, if you set the flag in your app saying that hardware accelerated drawing is allowed, then all drawing to the application’s windows will be done with the GPU. The main change in this regard in Android 4.0 is that now apps that are explicitly targeting 4.0 or higher will have acceleration enabled by default rather than having to put android:handwareAccelerated="true" in their manifest. (And the reason this isn’t just turned on for all existing applications is that some types of drawing operations can’t be supported well in hardware and it also impacts the behavior when an application asks to have a part of its UI updated. Forcing hardware accelerated drawing upon existing apps will break a significant number of them, from subtly to significantly.)
• Hardware accelerated drawing is not all full of win. For example on the PVR drivers of devices like the Nexus S and Galaxy Nexus, simply starting to use OpenGL in a process eats about 8MB of RAM. Given that our process overhead is about 2MB, this is pretty huge. That RAM takes away from other things, such as the number of background processes that can be kept running, potentially slowing down things like app switching.
• Because of the overhead of OpenGL, one may very well not want to use it for drawing. For example some of the work we are doing to make Android 4.0 run well on the Nexus S has involved turning off hardware accelerated drawing in parts of the UI so we don’t lose 8MB of RAM in the system process, another 8MB in the phone process, another 8MB in the system UI process, etc. Trust me, you won’t notice -- there is just no benefit on that device in using OpenGL to draw something like the status bar, even with fancy animations going on in there.
• Hardware accelerated drawing is not a magical silver bullet to butter-smooth UI. There are many different efforts that have been going on towards this, such as improved scheduling of foreground vs. background threads in 1.6, rewriting the input system in 2.3, strict mode, concurrent garbage collection, loaders, etc. If you want to achieve 60fps, you have 20 milliseconds to handle each frame. This is not a lot of time. Just touching the flash storage system in the thread that is running the UI can in some cases introduce a delay that puts you out of that timing window, especially if you are writing to storage.
• A recent example of the kinds of interesting things that impact UI smoothness: we noticed that ICS on Nexus S was actually less smooth when scrolling through lists than it was on Gingerbread. It turned out that the reason for this was due to subtle changes in timing, so that sometimes in ICS as the app was retrieving touch events and drawing the screen, it would go to get the next event slightly before it was ready, causing it to visibly miss a frame while tracking the finger even though it was drawing the screen at a solid 60fps.
• When people have historically compared web browser scrolling between Android and iOS, most of the differences they are seeing are not due to hardware accelerated drawing. Originally Android went a different route for its web page rendering and made different compromises: the web page is turned in to a display list, which is continually rendered to the screen, instead of using tiles. This has the benefit that scrolling and zooming never have artifacts of tiles that haven’t yet been drawn. Its downside is that as the graphics on the web page get more complicated to draw the frame rate goes down. As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom, with the negative of having artifacts when newly needed tiles can’t be rendered quickly enough. The tiles themselves are rendered in software, which I believe is the case for iOS as well. (And this tile-based approach could be used prior to 3.0 without hardware accelerated drawing; as mentioned previously, the Nexus S CPU can easily draw the tiles to the window at 60fps.)
• Hardware accleration does not magically make drawing performance problems disappear. There is still a limit to how much the GPU can do. A recent interesting example of this is tablets built with Tegra 2 -- that GPU can touch every pixel of a 1024x800 screen about 2.5 times at 60fps. Now consider the Android 3.0 tablet home screen where you are switching to the all apps list: you need to draw the background (1x all pixels), then the layer of shortcuts and widgets (let’s be nice and say this is .5x all pixels), then the black background of all apps (1x all pixels), and the icons and labels of all apps (.5x all pixels). We’ve already blown our per-pixel budget, and we haven’t even composited the separate windows to the final display yet. To get 60fps animation, Android 3.0 and later use a number of tricks. A big one is that it tries to put all windows into overlays instead of having to copy them to the framebuffer with the GPU. In the case here even with that we are still over-budget, but we have another trick: because the wallpaper on Android is in a separate window, we can make this window larger than the screen to hold the entire bitmap. Now, as you scroll, the movement of the background doesn’t require any drawing, just moving its window... and because this window is in an overlay, it doesn’t even need to be composited to the screen with the GPU.
• As device screen resolution goes up, achieving a 60fps UI is closely related to GPU speed and especially the GPU’s memory bus bandwidth. In fact, if you want to get an idea of the performance of a piece of hardware, always pay close attention to the memory bus bandwidth. There are plenty of times where the CPU (especially with those wonderful NEON instructions) can go a lot faster than the memory bus.
Click to expand...
Click to collapse
you saying iOS has no stutter lag..
My iPad stutters all the time. Its no where close to smooth!
Sent from my Galaxy Nexus using Tapatalk
There was some suggestion in this thread that any acceleration is currently software based only, and that the hardware acceleration has yet to be enabled.
I don't know how accurate that is, and there doesn't seem to be a definite answer in that thread.
Perhaps in the 4.1 update?
Evostance said:
you saying iOS has no stutter lag..
My iPad stutters all the time. Its no where close to smooth!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus using xda premium
I've had the Tab S 10.5 for about a month now and the lag while using everyday apps is driving me crazy. My top three offenders are:
1. Chrome
2. Play Newsstand
3. Play Store
I've done the following to help improve things:
- Changed launcher to Nova.
- Disabled bloatware (everything I can without rooting).
- Installed Chrome Samsung support library.
3D heavy games seem to run fine. My last tablet was a HP touchpad running CM11 so I am used to dealing with a few quirks. I stepped up to the Tab S to get away from some of that though. I know Android is infamous for scroll stutter, but it seems to me that a flagship tablet should easily beat out a bootleg touchpad.
Is this on par? Also, does anyone else's tab s get really hot around the touch screen near the Samsung logo? Maybe the Nexus 9 is worth another look. :silly:
Thanks for your comments.
Edit: I've read similar posts on lag. It seems like the argument boils down to: 1. Personal perception or 2. A mysterious "bad batch" of hardware.
i did the same steps,my tab is full of apps and games but i have 0 lag and the browsing is also fcking smooth. In the settings i also turned of features like dual window.
Are you sure you turned off fully power saving mode? About heating,if i play a game like gta or hearthstone i can also feel a warm area under samsung logo but is not hot and pretty common if you play games.
edith and use chrome beta instead of the standard chrome
Chrome lags on the tab s. Happens to most people. To fix over heating i installed a custom kernel that would optimise and prevent heating. Some big games do lag aswell.
thomasovics said:
i did the same steps,my tab is full of apps and games but i have 0 lag and the browsing is also fcking smooth. In the settings i also turned of features like dual window.
Are you sure you turned off fully power saving mode? About heating,if i play a game like gta or hearthstone i can also feel a warm area under samsung logo but is not hot and pretty common if you play games.
edith and use chrome beta instead of the standard chrome
Click to expand...
Click to collapse
I am already using chrome beta. The stock broswer is smoother.
can you upload a video to see the lag we are talking about?
I want to buy this tablet, and Ive read many posts about lag... but actually, is it very annoying? is there any video to see it?
Latiosman said:
can you upload a video to see the lag we are talking about?
I want to buy this tablet, and Ive read many posts about lag... but actually, is it very annoying? is there any video to see it?
Click to expand...
Click to collapse
Only on certain apps. Chrome and a few others. On some games it just lags on loading screen but not during gameplay. Watch a veiw reviews on youtube. Theres some videos talking about the lag. Touchwiz launcher also has lag but can be fixed.
Latiosman said:
can you upload a video to see the lag we are talking about?
I want to buy this tablet, and Ive read many posts about lag... but actually, is it very annoying? is there any video to see it?
Click to expand...
Click to collapse
I think it depends on your perception of lag and what apps you mainly use. In my case, Chrome and Newsstand are always up so I see the lag constantly. I wish I had a Nexus 9 side by side for comparison. If I get a chance I'll take a video, but it might be hard to see. I played with a demo model at Best Buy and it seemed faster than mine as well.
I came from a iPad mini 2 (last year's model) to this tablet. As smooth as my iPad was I have to say I have very little if any lag on mine. It's runs beautifully for me. I'm OCD, any bit of lag would drive me up the wall. I really don't notice hardly anything. I'm still running bone stock everything minus using Nova launcher. Don't even feel like I need to root or flash anything. Although I'm going to once there is a root released for my model. Maybe I'm just lucky I don't know. Have had zero issues.
I'm used to an overloaded gs3 so this looks ultra smooth to me [emoji3]
It lags more with multiple user logged in, always reboot of you don't need the additional user
Ripx88 said:
I came from a iPad mini 2 (last year's model) to this tablet. As smooth as my iPad was I have to say I have very little if any lag on mine. It's runs beautifully for me. I'm OCD, any bit of lag would drive me up the wall. I really don't notice hardly anything. I'm still running bone stock everything minus using Nova launcher. Don't even feel like I need to root or flash anything. Although I'm going to once there is a root released for my model. Maybe I'm just lucky I don't know. Have had zero issues.
Click to expand...
Click to collapse
For example, this thread's website lags a great deal in chrome beta when scrolling. Other sites aren't too bad. Newsstand is the worst though. Are you using the stock broswer?
This site does lag a little when scrolling. That I do have to admit. For whatever reason it doesn't really bother me however. I've never noticed any scroll stutter on stock android so I attribute it to touchwiz. This thing debloated or running a custom rom probably flys. I imagine any scroll stutter would be gone at that point.
I use the stock browser. I was never a fan of chrome. I know that on touchwiz your going to get the best performance from the stock browser unless there's a fix I'm unaware of which could be a possibility. Newsstand I actually haven't used so I can't speak for it. TouchWiz is just eating up so much ram. I'm like always at 1.5 to 2 gigs of ram with nothing running (other then the tons of unnecessary system apps I can't terminate) That is pretty ridiculous to me. Is touchwiz smooth as stock android? Definitely not. But I really have little to no lag other then scroll stutter on certain sites. I'm still going to root and debloat this thing when it's available for my model so I can truly experience the power of this tablet.
Lol, chrome sucks
It's about time Samsung optimised their flagship device. Had 3 since July and they all lag, stutter when scrolling and render pics poorly. Nova didnt fix the problems and changing some apps like using chrome beta marginally helped.
About time they fixed this via an update rather than just forget about the device and launch more/different models. Samsung will always fail unless it focuses on a core product set and spend the time making the hardware work properly with the software.
I was attacked when I first got my first device for stating lag. Whether an first time user or someone who doesn't want to root (glad I didn't after having 3 replacements), I shouldn't have to kill apps, install different roms and root.
Certain other OS fix problems like these quickly. Where's support from Samsung??
I have the note 4, their es8000 led TV, fridge freezer and various other bits so I'm not a Samsung hater by any means, just someone who expects upgrades to fix problems.
It's hard to determine how much lag is there until you run the same apps side by side with another tablet.
Over Xmas I got a chance to do just that. Ran S 10.5 side by side with my sister's nexus 7 2013. Both running kit kat (hers is 4.4.3 instead of 4.4.2).
Play Store and chrome both run smoother on hers, less jerking and stopping when scrolling. Tapatalk about same. She has Google now launcher, feels faster and smoother than nova launcher on mine. Overall, every thing just feels a little smoother and more fluid.
Granted, the nexus is 1920x1200 so it's pushing fewer pixels around, but the nexus is one year older and I paid $179 for it vs $379 for the S.
I think Samsung slapped on the OLED display and said heh, good enough. Which is true because I bought it
Custom Rom?
I made a rom that is all stock, just a few optimisations. Better performance, better batterylife and so on, here you go:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
I'd use only stock browser, if it had a full screen option and some gestures, but nope.
My alternative browser is maxthon pioneer, it has everything but stutters a lot
I've had my S 10 since August....I don't like chrome, never have, but after reading all this I opened chrome and came to this forum and I see no issues at all. NONE, other than I don't like chrome
I'm stock not rooted or ROMed. I have Apex launcher installed since day one and disabled all the Samsung and google bloat I could disable.
I have no issues with this tablet other than posting on some forums is a little quirky but that's just the way things are. I normally use Dolphin with the Jetpack or Boat Browser for tablet.
I love this tablet! Sure beats the stuffing out of my Asus TF700T! What a total POC that is!
Joker87 said:
I'd use only stock browser, if it had a full screen option and some gestures, but nope.
My alternative browser is maxthon pioneer, it has everything but stutters a lot
Click to expand...
Click to collapse
I just throw in a wipe cache once every few days, and stock browser experience is very smooth, even with the second account logged on, with Facebook, dropbox, carousel and plenty other services in background
Don't worry about the Lag
This lag on Tab S is only temporarily, the Android 5.0 will get rid of 90% of the lag. I know this for fact because I have Note 3 with Touch-wiz it lags often, after installing Android 5.0 I have NOT ONCE run into lag after 1 month of using it.
As of now, the Tab S is supporting android 5.0 cm 12 which there should definitely be no lag but again its unofficial ROM as of now, there are still things they are working on. Samsung's android 5.0 will get rid significant amount of lag, because Android 5.0 have 60 fps animation smoothness, and efficient RAM usage.
I've also heard rumors Samsung is working to refreshing their Touchwiz Interface with slim amount of lag. So, the future is promising.
As of now, if you really can't stand the lag, Install the Android 5.0 ROM for Cm 12, there are afew things not working in their such as Camera, NFC or something else, but the usage should show NO LAG!!!
[email protected] said:
As of now, if you really can't stand the lag, Install the Android 5.0 ROM for Cm 12, there are afew things not working in their such as Camera, NFC or something else, but the usage should show NO LAG!!!
Click to expand...
Click to collapse
Cyanogenmod for Galaxy tab S??