Hello,
Firstly I would like to say that I am coming from Google Nexus S, to Galaxy S3.
The first day I get my Galaxy S3, I immediately noticed that the touch screen is not as responsive as my Nexus S. I can feel the delay while moving icons, scrolling the pages etc. it just can't track my finger that fast.
I tried different roms, kernels, tried everything, and then I started to believe that it is a hardware related issue, UNTIL THE JB ROMS HAVE RELEASED..
I just flashed a JB rom (SuperNexus-B1) and touchscreen is now extremely responsive, like my Nexus S. (Btw, there isn't any problem on Nexus S both ICS and JB roms.)
I enabled the "Show touches" option from developer options, and woww.. It is tracking my finger really fast.
Now, why there is a touchscreen problem on Galaxy S3 with ICS, while not on other devices like Nexus S or Galaxy Nexus.
@Devs: please investigate this issue. Galaxy S3's touchscreen is capable of this, and it is a software related issue.
@Devs: please investigate this issue. Galaxy S3's touchscreen is capable of this, and it is a software related issue.
Suspect they will wait for Samsung JB release pointless fixing something this late in the life of ICS .
Did you update your original firmware ???
jje
Did you try cm9 or just touchwiz ROMs? Maybe it's touchwiz related.
Gesendet von meinem GT-I9300 mit Tapatalk 2
JJEgan said:
@Devs: please investigate this issue. Galaxy S3's touchscreen is capable of this, and it is a software related issue.
Suspect they will wait for Samsung JB release pointless fixing something this late in the life of ICS .
Did you update your original firmware ???
jje
Click to expand...
Click to collapse
They are still releasing new roms, updates, and they fix bugs, release stuff for ICS, so it is not pointless to fix this one too.
I'm on the LG6 firmware.
Tectas said:
Did you try cm9 or just touchwiz ROMs? Maybe it's touchwiz related.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
I'm currently on the AOKP Milestone 6 rom. Same issue here. So it should not be Touchwiz related.
Maybe it is a cpu governor issue?
xmRipper said:
They are still releasing new roms, updates, and they fix bugs, release stuff for ICS, so it is not pointless to fix this one too.
I'm on the LG6 firmware.
Click to expand...
Click to collapse
No issues at all here on stock lg8, the screen is more responsive than my gnexus and much more than my Nexus s.
juliano_q said:
No issues at all here on stock lg8, the screen is more responsive than my gnexus and much more than my Nexus s.
Click to expand...
Click to collapse
I don't think there is any screen related update between lg6 and lg8. You just can't notice that, I can feel the delay. Just move any icon on the screen, I believe you can feel it too.
My friend has a Galaxy S2 and I also noticed same lag on his phone too.
xmRipper said:
I don't think there is any screen related update between lg6 and lg8. You just can't notice that, I can feel the delay. Just move any icon on the screen, I believe you can feel it too.
My friend has a Galaxy S2 and I also noticed same lag on his phone too.
Click to expand...
Click to collapse
I have both the devices here man. I also have a gnexus running JB and my gs3 is more fluid than it.
juliano_q said:
I have both the devices here man. I also have a gnexus running JB and my gs3 is more fluid than it.
Click to expand...
Click to collapse
I have both too. As I said, you just can't notice it. It isn't about being fluid. I am talking about finger tracking.
Watch this video and you will understand what I mean: http://phys.org/news/2012-03-microsoft-finger-1ms-touchscreen-video.html
Edit:
I just installed this multitouch test app to my both phones, and moved my finger on both at the same time, Nexus S' tracking is faster..
xmRipper said:
I have both too. As I said, you just can't notice it. It isn't about being fluid. I am talking about finger tracking.
Watch this video and you will understand what I mean: http://phys.org/news/2012-03-microsoft-finger-1ms-touchscreen-video.html
Edit:
I just installed this multitouch test app to my both phones, and moved my finger on both at the same time, Nexus S' tracking is faster..
Click to expand...
Click to collapse
The same here. The S3 screen on Jelly Bean feels at least 10 times more responsive than on stock LG8 ROM...
Gesendet von meinem GT-I9300 mit Tapatalk 2
xmRipper said:
I just flashed a JB rom (SuperNexus-B1) and touchscreen is now extremely responsive, like my Nexus S. (Btw, there isn't any problem on Nexus S both ICS and JB roms.)
I enabled the "Show touches" option from developer options, and woww.. It is tracking my finger really fast.
Now, why there is a touchscreen problem on Galaxy S3 with ICS, while not on other devices like Nexus S or Galaxy Nexus.
@Devs: please investigate this issue. Galaxy S3's touchscreen is capable of this, and it is a software related issue.
Click to expand...
Click to collapse
Have you asked the dev what he had changed in his Rom? Maybe he is aware of it and can provide a solution. I am also interested in this. Thanks for bringing up this issue.
------
Send from my Galaxy SIII going PARANOID
Thankfully there's a possible fix for this. Probably the only thing that bugs me about the S3. My old S2 on GB felt much better when scrolling. Didn't update it to ICS because it didn't feel as good.
Sent from my GT-I9300 using xda premium
I changed the cpu governor to hotplug, touchscreen feels a lot better now.
I also changed the CFS Tweaks to "Thunderbolt script default" from STweaks, but I don't know if that affects.
how did you change the cpu governor to hotplug?
imfromwales said:
how did you change the cpu governor to hotplug?
Click to expand...
Click to collapse
Firstly you must flash a kernel that supports hotplug governor, I used SiyahKernel.
Then you can use STweaks application to change.
xmRipper said:
I have both too. As I said, you just can't notice it. It isn't about being fluid. I am talking about finger tracking.
Watch this video and you will understand what I mean: http://phys.org/news/2012-03-microsoft-finger-1ms-touchscreen-video.html
Edit:
I just installed this multitouch test app to my both phones, and moved my finger on both at the same time, Nexus S' tracking is faster..
Click to expand...
Click to collapse
what is the latency of the GS3 screen? is it totally hardware governed or can it be changed with software?
imfromwales said:
what is the latency of the GS3 screen? is it totally hardware governed or can it be changed with software?
Click to expand...
Click to collapse
Firstly I thought it is all about hardware limitations, but after flashing a JB rom then I realized that our hardware is capable of.
So no official figures on either ICS or JB? Obviously no official figures for JB as no official firmware yet
Sent from my GT-I9300 using xda app-developers app
Are you not all simply noticing the difference (and improvements) resulting from "Project Butter" in Jelly Bean? It was designed to improve speed and responsiveness - the exact thing I think most of you are complaining about in ICS (compared to JB). So yes, I'd fully expect JB to feel more responsive on identical hardware...
TimmyRaa said:
Are you not all simply noticing the difference (and improvements) resulting from "Project Butter" in Jelly Bean? It was designed to improve speed and responsiveness - the exact thing I think most of you are complaining about in ICS (compared to JB). So yes, I'd fully expect JB to feel more responsive on identical hardware...
Click to expand...
Click to collapse
No because there isn't any issue on other devices, like Nexus S with ICS.
I think the problem is in the Samsung's kernel for S3.
Related
Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Using cm9 and camera I working fine snappy and touchscreen is very nice!
Sent from my GT-I9300 using xda premium
dinan said:
Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
mintvilla said:
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
Click to expand...
Click to collapse
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
dinan said:
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
Click to expand...
Click to collapse
so did you sort out how to feed your finger tracking needs ??
i feel i think exactly like you... id like to keep my crapwiz functionalitues, but i'm crying out for the miss of smoothness here.
since me and u seems to have the same needs on this topic, please let me know if you find out somethig intresting.
c ya
dinan said:
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
Have you tried running a custom stock-based ROM that has the scrolling cache disabled (such as WanamLite) or with a kitchen option to disable this cache (such as Omega)?
I dont understand why the latest jellybean for the s3 lags in all transition animations?
Where is the butter? everyone reporting everythings perfect?
How composer is not completely ready for aosp jb. Hence
《tapatalked from galaxy s3》
Oh, come on !! JB isn't officialy released yet, and you are complaining about laggy animations ?
Just use the search and you will find out that hardware composer isn't fully functional on JB.
jakemog said:
I dont understand why the latest jellybean for the s3 lags in all transition animations?
Where is the butter? everyone reporting everythings perfect?
Click to expand...
Click to collapse
What rom are you on? I've used CM10 and am currently on the latest paranoidandroid and even though hwcomposer isn't completely working, it is quite smooth and I don't get lag at all
Sent from my buttery smooth S3
demondor said:
What rom are you on? I've used CM10 and am currently on the latest paranoidandroid and even though hwcomposer isn't completely working, it is quite smooth and I don't get lag at all
Sent from my buttery smooth S3
Click to expand...
Click to collapse
To be true it is laggy..... The HWComposer is not working on CM10 . On Faryaab's JB is partially working (smoother than CM10).
But to me, none beat the stock rom (LG8) at all actually... With just Siyah 1.4 without those custom roms or whatever crap.
Well wait for Samsung's JB it will be then the true performance of the JB. Nothing is wrong with your phone.
As hw composer doesn't fully work yet, you can set animation scales to off via developer settings. I set all to .5x, there is some micro lag in transition animations but not so bad.
Even though the hardware composer isn't exactly working on CM10, I'm on the latest Paranoid Android as well, and I don't see any noticeable lag?
metzalx said:
Even though the hardware composer isn't exactly working on CM10, I'm on the latest Paranoid Android as well, and I don't see any noticeable lag?
Click to expand...
Click to collapse
CM10 especially on entering System Settings, it is quite noticeable....
Even sammy ics rom do better than that...
tanjiajun_34 said:
CM10 especially on entering System Settings, it is quite noticeable....
Even sammy ics rom do better than that...
Click to expand...
Click to collapse
I believe Samsung has working hwcomposer for their ROMs..
Skickat från min GT-I9300 via Tapatalk 2
**DISCLAIMERS**
This thread has no intention of attempting to complain, diminish, degrade, or criticize any developers on this forum or any of their work, as all of us are nothing but grateful for the amount of free, altruistic, and superior quality code that they provide us with. :good:
This thread has no intention of trying to reiterate the content of the "Butery Smoothness" thread found at http://forum.xda-developers.com/showthread.php?t=1814010 nor to define what "Buttery Smoothness" is, as the previous thread defines it well enough already through the posts and insight of multiple users.
This thread has been created with full knowledge and consideration of the alpha development stage that Android 4.1.1 is currently in and all content discussed in this thread is stated with regard to said knowledge and should only be perceived as an attempt to contribute to at least one of multiple bug fixes to further improve the state of Android 4.1.1 on the SGH-i717 for the good of all users
Purpose
The purpose of this thread is to solve the perceived lack of graphical smoothness and fluidity inside of Android 4.1.1 (Jelly Bean) on the SGH-i717 which has been noticed and reported by many users in multiple ROM's through the collaboration of information, ideas, and solutions between all users and developers.
Background
Many users have reported a significant lack of graphical performance in multiple Jelly Bean ROM's for the SGH-i717 in various scenarios such as home screen navigation, UI animations, and in-app scrolling where there is not only a user-noticeable drop in performance but a quantifiable drop in frame-rate. With Google's Project Butter being a highlight of Jelly Bean, the lack of smoothness in its current state for our device brings not only dismay but logical confusion as other, older devices with lower specifications (such as the Galaxy Nexus for example) perform better graphically than the SGH-i717 with higher specifications. The higher graphical performance in the older Ice Cream Sandwich indicates that the highlighted performance issue in Jelly Bean is not related to hardware incapability but to software utilization of the hardware.
I want to leave as little of my insight in this thread as possible because I want to hear from other users but I'll post some initial information and questions to provoke some response.
Ever since Jelly Bean development began, I've noticed this issue on my device and have even had a replacement device with the same experience so hardware isn't a likely culprit in my opinion. h0tw1r3 was one of the first developers to bring a Jelly Bean ROM to SGH-i717 users and other ROM's were formed briefly after his using it as a base. Until about the third or fourth build ( 8-21 I believe), the performance was sluggishly the same. After this build though, there was a noticeable increase in graphical performance, although still significantly behind ICS. That new standard hasn't changed much since until the latest CM10 nightly builds where I've noticed quite an increase in graphical performance putting it a little closer to ICS performance but still painfully behind such that Dolphin is the only browser that feels smooth enough to use efficiently.
I have also noticed an odd phenomenon where the performance varies from build to build without a noticeably significant change. For example, I remember using DaGr8's AOKP port for a while and finding it smoother than other ROM's at the time but once installing his next build (that only mentioned minor unrelated changes, although some could have been unlisted) the performance was back down again. I have experienced this with multiple different ROM's though which is what is most peculiar that there is so much inconsistency.
Helpful Questions
Have you noticed any of these issues before? If so, which ones?
Do you think the issue is hardware or software/driver related?
How would you compare your best JB experience to stable ICS builds?
Which processes/applications perform the best and the worst for you graphically?
Which ROM's run smooth for you and which ones don't?
Which browsers have you tried in Jelly Bean and which ones do you prefer the most?
Have you noticed graphical performance issues in Chrome consistently at all? If so, in which ROM's or instances have you experienced such?
Do you have any ideas/suggestions as to what is causing or what could fix this issue?
And regardless of the inevitable bugs we are experiencing in alpha software, are you extremely grateful for the developers who have provided us with them? (SAY YES!!)
If any of you would like to add more content or questions to this list (and PLEASE do), just ask them and I'll add them to this OP.
Suggestions and Modifications for Improvement (list will grow over time as new information is presented)
1) Verify that the "debug.mdpcomp.maxlayer" parameter in build.prop is set to the value of 3 and not 2 when you first install a ROM (thanks to NYConex for the tip!). Some developers/ROM chefs (lol) will customize this setting based on their preference. This setting disables (value 2) and enables (value 3) GPU acceleration taking the load off of the CPU. Disabling has fixed the flicker issue that has developed in Jelly Bean for many people but will severely impact performance and graphical smoothness as well as battery life potentially. For flickering, I instead recommend using a live wallpaper which will force the GPU to refresh the screen much more often disabling flicker (in the homescreen at least).
2)**ESSENTIAL FIX FOR SIGNIFICANT IMPROVEMENT** Change the debug.composition.type in /system/build.prop from "dyn" to "gpu" and reboot. This makes a MAJOR difference in ALL areas of performance. The existing string that is entered by default is a "dynamic" setting which alternates putting the graphical load on either the GPU or CPU depending upon resource allocation. Changing the setting to "gpu" will force Android to constantly use the GPU for graphics so you won't notice stutter and lag as Android switches the load from the CPU and GPU. Using this setting also increases overall system speed IMMENSELY as it allows the CPU to do more central tasks like launching applications and communicating with hardware instead of handling the graphics. This "constant GPU setting" plays very nicely with Project Butter in the sense that it uses a constant component of hardware to render graphics along with the constant frame rate that VSync provides. I may try to learn how to make my first ROM sometime soon and when I do, I'll be sure and integrate this into the ROM. Either thank the post or let everyone know if this has helped you!
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
NYConex said:
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
Click to expand...
Click to collapse
Good question. I know there are settings in Developer options that allow you to show GPU status and updates which may provide some insight into GPU/CPU utilization. I don't have an immediate answer for you though. I'll do some research and report back.
With the Liquid ROM, I noticed it to be of the poorest performance as others. Was your experience smooth out of the box or did you have to change the debug.mdcomp.maxlayer from 2 back to 3 first?
**EDIT**
I just tried the Liquid ROM again and realized the debug.mdpcomp.maxlayer setting was set to 2 by default in that ROM and after the changing it, the performance was much better, though about the same as CM10 nightlies.
The mdcomp.maxlayer is always the first thing I check after flashing a ROM. I always set it to 3. But if you go back to liquid try the navbar and you will see what I mean. In not home right now but when I get back I'll mess with it a little.
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
Lol damn right. I'd say its between 14-21 FPS variably.
Which ROM's have worked the best for you so far?
On mobile, had 2 scroll forever to read topic
SayWhat10 said:
On mobile, had 2 scroll forever to read topic
Click to expand...
Click to collapse
Are you saying that my OP is too long which made you scroll forever or are you saying that the lag in Jelly Bean cause you to scroll forever?
andrawer said:
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Do you use Google Chrome? If so, how would you describe its performance in comparison to Ice Cream Sandwich?
The CM10 nightly has been the smoothest this far. So going by experience heres the rankings ATM.
1) Nightly... Smooth but constant flicker.
2) Liquid
2) Paranoid
3) Aokp
4) manualscout4life's rom.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
not sure if i understand.
I use my thumb to initiate the notification bar/drawer pulling down and it's immediate and smooth?? Up/down/up/down/up/down...smooth...just tried it. Not even a hint of lag...and that's with 4 notifications waiting for me to do something.
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
egomezmorales said:
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
So when will we get hardware acceleration? When jb officially comes out for the note?
roloracer said:
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
Click to expand...
Click to collapse
This has been my thought and awareness all along and what I've wanted to work on repairing. Perhaps it's everyone's use of the term "smooth" that is making everything amiss. When people boast that their JB experiences are "incredibly smooth!" and even more specifically "smoother than ICS!" I think they are making very fallible statements because I don't think that my perception of JB being behind ICS in smoothness can be interpreted as just a "difference in opinion or interpretation". It's definitely factual and quantifiable when testing frame rates and comparing them to ICS. Perhaps it's safe to say that "Jelly Bean is remarkably usable right now considering its alpha state", but to say that it is smooth is quite a fallacy. It's really not much better than Gingerbread and Gingerbread lacked HW acceleration altogether.
But if JB lacks hardware acceleration completely, then how is toggling the maxlayer setting and HW overlay setting in developer options clearly affecting performance if HW acceleration isn't even supported at all in the first place? Some sort of acceleration is clearly being enabled for the evident difference in performance to occur.
I am grateful that you recognize JB's current state to be behind and also attribute it to HW acceleration as I initially did. Now we can hopefully gain some momentum on finding the hindrance of bringing HW acceleration to JB!
If there's anything we've learned thus far, it's not to label a ROM officially "smooth" unless you can prove it greater than or equal to stable ICS builds with quantifiable means!
The word "smooth" is beginning to become a profanity for me, which is rather extreme, as there aren't many words I don't say! Lol...
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
So far the smoothest jb rom for me has been dagr8's aokp Sept 1 build.
HW overlays are disabled and cpu at stock frequencies. Running Nova 1.2.2 and have fluid home screen transitions and overall smoothness.
If I were to nitpick, the notification bar is the only thing that seems somewhat sluggish but only when I pull it down on the home screen (I am running a live wallpaper.)
No reboots or sleep of deaths so far, loving this rom at the moment.
yollasho said:
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Really interesting read, thanks for sharing!
Sent from my Nexus 7 using xda premium
---------- Post added at 01:04 PM ---------- Previous post was at 01:04 PM ----------
Fasty12 said:
So when will we get hardware acceleration? When jb officially comes out for the note?
Click to expand...
Click to collapse
Yep, or that a developer taps on how to get HW acceleration
Sent from my Nexus 7 using xda premium
We've had hardware acceleration.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I have been looking at my girlfriends brand new S3 with stock firmware and i have noticed that ICS is actually smoother than every JB leak i have installed and also smoother than my Omega 26 Rom. My Omega 26 Rom has all of the bloat removed and it doesnt make any difference.
In fact i would go as far to say that hers is smoother than mine!
Im starting to think that all this Rooting and Flashing causes more problems than it might solve!
Smoothness doesn't necessarily mean speed though
Eg. Reset transition speeds to 1 if you have them on 0.5 is a good way of demonstrating what I mean
slaphead20 said:
Smoothness doesn't necessarily mean speed though
Eg. Reset transition speeds to 1 if you have them on 0.5 is a good way of demonstrating what I mean
Click to expand...
Click to collapse
Thought I'd find you lurking around here spouting 8ollox.....
Sent from my GT-I9300 using xda premium
irzero said:
I have been looking at my girlfriends brand new S3 with stock firmware and i have noticed that ICS is actually smoother than every JB leak
Click to expand...
Click to collapse
I've noticed the exact opposite. My girlfriend's phone seems so sluggish with stock ICS compared with my JB ROM. I think JB has been really snappy since at least LI6.
irzero said:
I have been looking at my girlfriends brand new S3 with stock firmware and i have noticed that ICS is actually smoother than every JB leak i have installed and also smoother than my Omega 26 Rom. My Omega 26 Rom has all of the bloat removed and it doesnt make any difference.
In fact i would go as far to say that hers is smoother than mine!
Im starting to think that all this Rooting and Flashing causes more problems than it might solve!
Click to expand...
Click to collapse
I kinda get what youre saying. I have 3 devices on which I have the new cm10, dli8 and lh1. LH1 wins in all categories except for jellybean smootness of the dli8 leak. ICS is still king.
remember, these are still leaks, may still be bugs...
No. The jellybean is smoother. And cm10 is waaaay faster
People just have different ideas of smoothness. Some people think the Galaxy Nexus with Jelly Bean is smoother than the GS3 with ICS, not a chance, Some stupid people even think that the Iphone 3Gs is smoother than the GS3, which is just plain retarded. Some people think that the iphone 4 and 4s kill even the high end Androids in smoothness, wrong again. Some people think that sense 4.0 isn't a stuttery mess and that the One X is actually close in performance to the GS3, you guessed it, wrong.
Just go with your eyes.
If i were to hazard a guess. AOSP probably has about 30 frames of animation that just cycle every half a second, locked at 60fps. While touchwiz has like 40 frames of animation or more that is usually locked 60fps but not always like JB. So yeah, during the times that ICS touchwiz is at 60 fps, it should appear smoother.
Basically if ICS doesn't drop below 60fps or have memory que issues then technically we wouldn't see project butter. We don't even technically see it. We only notice it when the system chugs, and if project butter kicks in properly, we won't even see that. lol
Well its subjective, you need to ask yourself what do you mean by smoothness? For me its fast respons when opening apps and having no lag or stutterings. For this JB leak li8 does the job
Sent from my GT-I9300 using xda app-developers app
people keep raving about how smooth the iphone is but it's noticeably slower than android, esp the high end ones.. the smoothness is just there to cover the lags
I have owned 5 iPhone's and I can tell you now that ios strongest point is the consistently fast transitions. You can move around the OS 10x faster than android. Android is filled with loads of pointless animations and transitions that just make it slower.
I found my problem to be a widget called application manager. It caused a stutter in my transition from Page to Page. I minimised this and now it's smooth.
But I'd still argue that there is no difference between my girlfriends ICS and my JB
Sent from my GT-I9300 using Tapatalk 2
I've been an s3 for almost 7 months now. From last few months on touchwiz JB 4.1.2 based ROMs, I feel my phone has become sort of slow (not exactly laggy though), but slow in opening critical phone apps like dialer or contacts, etc Also launcher redraws have become lot frequent now..
I remember when I initially got my phone with ICS, it felt so snappy coming from sgs2 that I didn't move to custom ROM that for few months as I just didn't feel the need. Somehow, its lost that wow now .
Is it because I have gotten used to the speed and craving for something better or was ICS really faster, you guys also feel?
P.S. I don't think its number of apps related as I have roughly the same number of apps now which I was using back then...
I actually feel that it's slightly slower too, but I still prefer jellybean because the lagginess is not very significant and I also use the multiwindow function quite often
disclaimernotice said:
I actually feel that it's slightly slower too, but I still prefer jellybean because the lagginess is not very significant and I also use the multiwindow function quite often
Click to expand...
Click to collapse
I don't see too much difference but is true in some times importante apps such as dialer load not as faster as i like.
This behavior i think is in ICS too, or at lesast i remeber
AW: Was ICS faster than JB on S3
The EMR2-build in combination with locked dialer and contacts by JKAY framework is THE MOST fluent phone I've ever expected. No lag at all, full Touchwiz functionality and complete AOSP look. Guys? We have a winner!
|| Typed with my S4 Octa-Beast or my Note 10.1 ||
Op - Relevance? If this phone could run froyo, some things would be quicker.
Sent from my GT-I9300 using xda premium
Mr Woolf said:
Op - Relevance? If this phone could run froyo, some things would be quicker.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
true that, but ironically JB was supposed to make things faster with project butter and all
anyway I was seriously thinking of reverting back to ICS, the only thing which I'm gonna miss would be the improved notifications, don't use multi-window at all and about google now..its a nice concept but still haven't seen good use for it yet. Not sure what else was changed from ICS to JB transformation.
Though i'm not sure, if I can flash ICS simply, as I have upgraded my modem and camera driver. Is there any precautions/procedures I need to follow ?