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.
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
Forgive me if this has been posted elsewhere but I couldnt find it.
Q1. Has anyone experienced clicking the Home button from another app or from the app drawer and seeing just the wallpaper for a few moments until the home screen widgets, folder and shortcuts are redrawn?
Q2. Also, Has anyone noticed lag when scrolling between home screens if a Live Wallpaper is used? I notice some live wallpapers make scrolling worse than some others.
If this has been posted, let me know?
Yes to Q1.
Also had lock up in gallery with a spinning circle and nothing happening.
Yes to Q2. All of the live wallpapers except one cause lag. Quite disappointing.
Yes I've noticed this which is quite disappointing considering everything is meant to be GPU accelerated and butter smooth in an iPhone-esque manner, general navigation doesn't seem any different to my HD2. Hopefully software updates can overcome these issues.
It's good to know I don't have a faulty handset but its a shame that its not as smooth as the early reviews lead me to believe (although it is very smooth once in the app drawer and other places).
Does anyone know any impressive Live Wallpapers that have little or no detrimental effect on Home Screen lag? I find Koi Free quite impressive without causing much noticeable lag (but its a bit old hat now, so I'd like something different).
Yeah I find it very hard to work out how The Verge could've given it such a high score, software in particular, and called it "blazing fast".
It's good, but it doesn't feel very fast to me.
I'm very disappointed by the live wallpaper lag, i thought ICS completely diminished any lag in the OS
all the live wallpapers make the scrolling look historic except for the one: PHASE BEAM
that one is as smooth as a picture wallpaper
anyone else? hopefully its easily fixable in a future general maintenece OTA or some custom roms
if you guys are using third party wallpapers then they probably were never updated to enable the hardware exceleration.
if your using the built in, then thats totally unacceptable IMO and is very upsetting since i was looking forward to having a device that will actually be able to run LWPs.
neok44 said:
if you guys are using third party wallpapers then they probably were never updated to enable the hardware exceleration.
if your using the built in, then thats totally unacceptable IMO and is very upsetting since i was looking forward to having a device that will actually be able to run LWPs.
Click to expand...
Click to collapse
I have tryed the ones that came with with phone and sadly it is not smooth also.
Sent from my Galaxy Nexus using XDA App
It feels like my Sensation with a 3rd party launcher. =(
Still love the phone but this wasn't supposed to happen.
i read in the endaget review that not all live wallpapers are HW accelerated - as of right now only "Phase Beam" (the default) one is.
Which is why you should notice theres no lag on the Phase Beam Live wallpaper (at least not for me), whereas stuff like "Nexus" live wallpaper will seem to lag
This is the paragraph i read:
"Not all the live wallpapers are fully optimized (for example, Phase Beam is, but Water isn't). Developers have to add a single line of code to their apps to take advantage of 2D hardware acceleration -- you're able to enable this as the default for all apps by checking "Force GPU rendering" in the Developer Options."
So apparently its just one line of code that devs need to add in for their apps - granted, these are GOOGLE wallpapers so im not sure why they just didnt add it in themselves.
But this also adds to the Developer options of "Force 2D rendering" - although im not sure if this will help the unoptimized live wallpaper lag
just my 2cents
1. Yes
2. Yes
I also sometimes get lag when launching the app drawer.
Scrolling widgets also seems so stutter slightly as well.
Glad to know its not just my handset, but dissapointed as well. My GS2 was buttery smooth everywhere
Well, this is disappointing. It's a pretty basic part of the user experience, one that you'd think Google would spend a lot of time on. My GS1 running 2.3.4 suffers from refilling the launcher when I return to the home screen. I was hoping the SGN with ICS would end that experience. You guys running a lot of apps? Maybe there's something in common between those affected that isn't experienced by everyone. Will be watching this thread.
Noticed it straight after first boot, amount of apps has nothing to do with it, at least for me.
Anyone tried different launchers. Different launchers play a big role in Android user experience and smoothness. I don't think any custom launcher has hardware acceleration enabled yet, but it would be worth a shot.
It is also unacceptable that the default stock Live Wallpapers from Google weren't updated to utilize the hardware acceleration. HWA is the main feature of ICS that everyone was waiting for. EVERYTHING on the Galaxy Nexus should be setup for HWA. No excuses.
On a side note, all of my phones lagged a little when using LWPs. Even my fast G2x. The SGS2 had hardware acceleration enabled... so it could just be the launcher.
adw launcher FTW.
enable 2d doesnt fix it
has this been opened as an issue in the google aosp page
Hmm. This reminds me of the first time I took my Nexus S out of the box..
Just wait for some custom roms and such, google are apparantly horrible at optimizing performance.
I have a feeling that using GPU acceleration to certain wallpapers would cause the phone to become unstable or something, like how forcing GPU acceleration has been reported to cause instability. Google probably disabled it while they quietly work on the issue.
Sent from my Galaxy Nexus using XDA App
perhaps
but the one live wallpaper works WONDERFULLY
A problem I always had with the Xperia S is that the whole thing feels extremely choppy and clunky. I have extremely low tolerance for choppyness, and this phone has always felt really clunky for me, it's hard to pretend the choppyness isn't there. There is nothing that makes me feel good about a device than silky smoothness, and even though the phone is still very fast and reactive, the slow framerate and microstutters are extremely noticeable, especially if you ever used a smooth device before (such as my good old Xperia Ray on gingerbread which was smooth like an iPhone, and when I upgraded it to ICS I couldn't stand it anymore because it became horrendously stuttery).
I was wondering, since Project Butter promises fully accelerated UI and elimination of the persistent lag that all android phones have, do you think this will finally resolve the slugginess of this phone's stock rom?
Is PB an OS features that all phones running JB have, or do the developers (in this case Sony's) have to implement it on their own?
Also, regarding the current stock ICS, there is nothing that helped with the constant lag and choppyness in the UI, the only thing that DOES make a difference is enabling "force GPU rendering", it's found under "developer options" and disabled by default. Once you enable it, scrolling lists (such as the settings menu) will become silky smooth (you have to go back to home and then back to settings menu to notice the difference). With this disabled, scrolling every list menu is embarassingly choppy. It doesn't cause any battery drain so I recommend everyone to enable it if you haven't already.
I seriously hope JB will resolve the constant choppyness of this phone's UI.
MarkMRL said:
A problem I always had with the Xperia S is that the whole thing feels extremely choppy and clunky. I have extremely low tolerance for choppyness, and this phone has always felt really clunky for me, it's hard to pretend the choppyness isn't there. There is nothing that makes me feel good about a device than silky smoothness, and even though the phone is still very fast and reactive, the slow framerate and microstutters are extremely noticeable, especially if you ever used a smooth device before (such as my good old Xperia Ray on gingerbread which was smooth like an iPhone, and when I upgraded it to ICS I couldn't stand it anymore because it became horrendously stuttery).
I was wondering, since Project Butter promises fully accelerated UI and elimination of the persistent lag that all android phones have, do you think this will finally resolve the slugginess of this phone's stock rom?
Is PB an OS features that all phones running JB have, or do the developers (in this case Sony's) have to implement it on their own?
Also, regarding the current stock ICS, there is nothing that helped with the constant lag and choppyness in the UI, the only thing that DOES make a difference is enabling "force GPU rendering", it's found under "developer options" and disabled by default. Once you enable it, scrolling lists (such as the settings menu) will become silky smooth (you have to go back to home and then back to settings menu to notice the difference). With this disabled, scrolling every list menu is embarassingly choppy. It doesn't cause any battery drain so I recommend everyone to enable it if you haven't already.
I seriously hope JB will resolve the constant choppyness of this phone's UI.
Click to expand...
Click to collapse
If you're really curious you could flash the test version DoomlorD posted. There's also this video on Youtube:
http://www.youtube.com/watch?v=kNLODO3YOnA
Looks like it is more fluent, as was expected, but ofcourse that's a nearly empty firmware. Some 3rd party apps can make your phone a lot slower, even when they're supposedly not running. A clean installation of ICS is also quite fluent compared to the lags I've had caused by some apps before I removed or restricted them.
Redstarr1 said:
If you're really curious you could flash the test version DoomlorD posted. There's also this video on Youtube:
http://www.youtube.com/watch?v=kNLODO3YOnA
Looks like it is more fluent, as was expected, but ofcourse that's a nearly empty firmware. Some 3rd party apps can make your phone a lot slower, even when they're supposedly not running. A clean installation of ICS is also quite fluent compared to the lags I've had caused by some apps before I removed or restricted them.
Click to expand...
Click to collapse
I can't flash it because I'm not unlocking my BL. Also, which apps do you think are the most resource hungry? I already disabled facebook and all social network related stuff, most services like sony select, etc. No difference at all.
My Xperia S and my Nexus 4 feel as smooth as each other using go launcher and obviously one has project butter and one doesn't
A simple solution would be to set a background process limit to 3 or less (developer options-resets on reboot so take care of that)
Also decrease the transition and animation from 1 to .5(dev options again)
If u are rooted(which am expecting u are)
Use romtoolbox or any utility capable of profiling ur cpu...set two profiles..screen off->governer-ondemand-low frequency(will save battery)
And one as screen on->governer-performance-max frequency(reduce ur lag)
If u have too many apps..use greenify or some app with same functionality
These basic settings have kept my ion lagfree all the while
Sent from my Xperia ion
Hit a thanks when someone helps
for what it's worth, i just came to the xperia S from the original galaxy S. i was running JB on that, which has nowhere near the specs of the xperia S, and JB was smooth as silk there, so it does seem to make a noticeable difference. moreso on 4.2 than 4.1, however.
unfortunately i've been hit with the bootloader unlock = no , so the wait for jb again begins..
MarkMRL said:
I can't flash it because I'm not unlocking my BL. Also, which apps do you think are the most resource hungry? I already disabled facebook and all social network related stuff, most services like sony select, etc. No difference at all.
Click to expand...
Click to collapse
That's why I posted the link to the Youtube video so you could get a glimpse that way .
I'd also disable Google+ and Google Talk if you're not using those. And some apps that you installed yourself from the Play Store can make your phone sluggish as well. I used Greenify to force my games and some apps to hibernate (Angry Birds, Dropbox, Google Drive etc), saved over 100mb in available memory. That has made my phone a lot less laggy. I usually don't encourage using app killers but Greenify is doing a good job with no errors for the past 3 days.
absolutely yes
jb leaked is the smoothest thing i have ever seen
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??