There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Perhaps you could try one of the lollipop versions. They (both aosp and Omni) are really stable. If you however need 3G I would suggest the aosp rom.
There's no harm in trying them out. If you still feel that they lag to much you can always go back to stock.
I've been running the aosp rom on my wifi tab for some time now and it performs pretty great actually.
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Lior84 said:
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Yes, responsive. I did overclock it to 1400mhz but it's running stable. Only youtube is sometimes not the best when running 720p videos.
Not responsive :/
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Mast3rC22 said:
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Click to expand...
Click to collapse
I can only speak from my experience with the aosp rom but scrolling in Chrome is smooth, I'm also using Nova Launcher and it is overclocked to 1400 mhz. Please don't expect miracles from this old device that samsung gave up on one ago. It runs 5.1.1 as smooth as it can. Also don't expect any hard core gaming and youtube will sometimes have issues. If all these things are deal-breakers then stay with whatever you have now. I wrote this from my own experience with my own tab. My father has the same one else only that one is bone stock. Touch wiz and everything with only a handful of apps installed. And yes it runs smooth and has less "issues" but it's running 4.0.4... I hope my explanation helps you make an informed decision.
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I was considering the same. I was on 4.4 omni, seemed laggy. Flashed stock ICS, which did seem snappy but still bloated. I thought I'd give AOSP 5.1 a go. Haven't over clocked anything and its definitely smoother than 4.4 omni. Very compact ROM, I installed gapps and that only set google play. Currently tested WiFi and GPS and they're working. Chrome is smooth and running flash smoothly. Auto detected resolution on YouTube.com is smooth. Haven't tried YouTube app as yet. I normally use tubemate anyway. This tab will always have trouble playing 1080p vid. Max I go now is 720. Tried and its working fine using mxplayer. 5.1 is still in social testing but the bugs are slowly being fixed. I was on ICS for a long time as it performed well. Having experienced the same with 4.4 and now upgrading to this rom , I'm happy with how smooth and responsive it is. Ticks the boxes.
My main concern is lags. I run omni 4.4 on with nova and the response is disappointing.
Most of the time, my son use it to watch movies, YouTube and some games but nothing really hard. When I take it to do some stuff on it, the lags just giving me crazy. I know that the main problem is lack of RAM but hey, with 4.0.4 it works OK.
Sent from my Nexus 5 using xda premium
Going back does mean stability. The way I look at it though is you can only put so much into a mini, but it will always be a mini, not a Ferrari. Lollipop seems to work OK but its stretching the capability of this tab. For me with minor tweaks its going OK. A goto software always on all my droids is Greenify. It kills all the apps lingering in the background and stops them from opening again unless I open them. Try it out, you need all the ram you can get outta these older tabs. With the paid version it also kills system apps like google play services which is a big ram hog. I guess the only way you'll make your mind up is give ICS a go for a few days then try LP and see what you think.
A lollipop ROM might be smoother, if there would be the "Performance" menu in the settings app (like CM12).
If anyone has got any cyanogenmod ROM, i suggest these settings:
CPU governor:
• Intellidemand/ondemand: The CPU will increase the frequency when needed. It's default in many kernels. I really suggest that, because the device will be very stable (and smooth) and the battery life will be quite good :good: ;
• Performance: The CPU frequency will be set to max setting;
• Powersave: The CPU frequency will be set to minimum setting.
CPU min frequency: 150mhz (max. 200mhz)
CPU max frequency: overclock to 1400Mhz (do not overclock to 1.5 or 1.6ghz, the cpu will freeze and might be damaged)
I/O scheduler: deadline
zRam: 18%
Resources clean: on
KSM: on
PS: Enable "Set on boot" to each menu.
Sorry for the worst english ever.
I like decatf's 5.1 AOSP rom. He put a lot of work into creating a wrapper for hwcomposer which does a better job translating some of the newer rendering apis to work with the ancient ics binary Nvidia video driver blobs. That's why videos and animations are much smoother on his rom than the alternatives and why you don't get that weird "lightning bolt" rendering effect that's been around since pershoot's cyanogen jelly bean roms. He also implemented an audio driver wrapper as well in the same vein. And if you use his TWRP version, you can format /cache and /data to use f2fs, which definitely helps with disk I/O. He even ported over Multirom so you can dual-boot, but alas, it doesn't boot Ice Cream Sandwich roms at the moment.
It's the best modern rom thus far for the original Tab 10.1. Other than proper modern and native Nvidia drivers updated for Lollipop, the only thing really holding back the original 10.1 at this point is the Tegra 2's lack of NEON support. But there's nothing decatf can do about that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Related
**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
Ok right now I have a US 4.0 player and I'm currently running the stock rom. It runs fairly smoothly and I get a Quadrant score of just 1264. Previously I have successfully rooted it, installed Terrasilent kernel 1.3.5. I then installed EtherealRom 2.4. But I noticed that the player did not run smoothly at all, even though I got a slightly higher Quadrant score of 1330ish. I then went back to stock and things again ran smoothly even at the lower Quadrant score. So I rooted it again and installed Terrasilent kernel again. I then installed the Icy Fusion V2.3 rom. Again the player really lagged even through I was getting a higher Quadrant score than stock. When playing music through Poweramp doing anything else at all makes it stutter like crazy. And I tried other music players with the same result. Even scrolling through the screens get's all laggy when nothing is running. All I really use my player for is music, gps, surfing the web and reading rss articles. I don't play any games on it. I have tried switching to Ext4 and that didn't help either. Does anyone have any idea why using a custom kernel and rom makes it run so much crappier than stock? I know other people are getting it to run good with the custom rom and kernel. I'm just not sure what to try to get the same results as others.
I'm no expert on ROMs but remember stock has everything working like HW acceleration so that might be it. And also ICS is more demanding the 2.3 so it could be that. For me stock wasn't smooth at all.
Karim.younus said:
I'm no expert on ROMs but remember stock has everything working like HW acceleration so that might be it. And also ICS is more demanding the 2.3 so it could be that. For me stock wasn't smooth at all.
Click to expand...
Click to collapse
Thanks for the response, but I'm pretty sure that both the roms I tried are both 2.3 variants, not ICS.
I tried flashing Terrasilent and Icy Fusion again and kept it overnight to see if anything needed time to process in the background. But as of today it is still running as before, very laggy and choppy.
Hanthesolo has some i9000 ports to the galaxy player 4 that worked very good for me.
Sent from my YP-G1 using Tapatalk 2
Most of the time ROMs don't run as smooth as the original stock one. However, I used both Ethereal and IcyFusion and I haven't seen much lag on either. You should try bumping up the min clock speed to 400mhz or 800mhz, and keeping the max clock speed at 1000mhz. Also I listen to PowerAmp, while using Voodoo Amplifier, DSP Manager, and emulating genesis/snes games at a clock speed of 800mhz to 1000 mhz and I only see micro lag at best. Sometimes you might have too many background apps running on the player, so I would go to task manager and if you see that is 300mb or more for ram usage then that's why the player is lagging.
I use icy fusion along with terrasilent and had same results until I installed autokiller memory optimizer. I have it set to extreme. Smooth as butter now. I also have min set to 400 and max set to 1000 using set CPU.
Sent from my YP-G1 using Tapatalk 2
I just tried out alpha 4 of CM10 on my player 5.0
I did not overclock that
but it is quite smooth for UI animations/transitions.
Maybe because it is Jelly Bean
5.0 and 4.0 has the same hardware, why is it that 5.0 is smoother than 4.0?
Thanks for the tips guys! It was a memory issue I guess. Not sure why stock handled it better, but once I installed a task killer things smoothed right out in the Ethereal rom.
I will switch to an ICS rom once they get that camera figured out. I know the 4.0 camera isn't great, but I use it a lot.
My friend told me that it is best to stick with CM7 because it does not have ad many bugs as CM9 or CM10
Sent from my YP-G1 using xda app-developers app
I use daily on GP 5.0 chip rom with adw launcher on 1.5 ghz and V6 supercharged...its so much smoother than stock that cant compare.
Sent from my YP-G70 using xda app-developers app
Also I just wanted to add that I've tried every launcher available on the market and the best running one for me is launcher pro. Everyone said its old and outdated but hands down, its been the best launcher in terms of performance. The only thing that has come close is the new smart launcher. But it needs a few things added in features for me to use it every day. Good luck.
Sent from my YP-G1 using Tapatalk 2
mwclark7 said:
Also I just wanted to add that I've tried every launcher available on the market and the best running one for me is launcher pro. Everyone said its old and outdated but hands down, its been the best launcher in terms of performance. The only thing that has come close is the new smart launcher. But it needs a few things added in features for me to use it every day. Good luck.
Sent from my YP-G1 using Tapatalk 2
Click to expand...
Click to collapse
tru new adw launcher ex ..its fast and awsome..i even use it on nexus 6
Sent from my YP-G70 using xda app-developers app
Gaideran said:
Ok right now I have a US 4.0 player and I'm currently running the stock rom. It runs fairly smoothly and I get a Quadrant score of just 1264. Previously I have successfully rooted it, installed Terrasilent kernel 1.3.5. I then installed EtherealRom 2.4. But I noticed that the player did not run smoothly at all, even though I got a slightly higher Quadrant score of 1330ish. I then went back to stock and things again ran smoothly even at the lower Quadrant score. So I rooted it again and installed Terrasilent kernel again. I then installed the Icy Fusion V2.3 rom. Again the player really lagged even through I was getting a higher Quadrant score than stock. When playing music through Poweramp doing anything else at all makes it stutter like crazy. And I tried other music players with the same result. Even scrolling through the screens get's all laggy when nothing is running. All I really use my player for is music, gps, surfing the web and reading rss articles. I don't play any games on it. I have tried switching to Ext4 and that didn't help either. Does anyone have any idea why using a custom kernel and rom makes it run so much crappier than stock? I know other people are getting it to run good with the custom rom and kernel. I'm just not sure what to try to get the same results as others.
Click to expand...
Click to collapse
I noticed that the stock rom on 5.0 runs better than the custom gingerbread rom we have.
You should try an ICS rom. Yes, the camera doesn't work, but you have a Turbocharged device with amazing battery life.
The camera on the 5.0 is pretty ****ty, so i don't care about it.
Also, in Gingerbead, transitions and animations are done by the CPU, while in ICS, GPU does the job. Thats why ICS is 1000000x smoother than Ginberbread on Player 5.0
And with ICS, i don't lose any battery percentage at night, basically you have 5x standby time.
And the RAM managment on ICS is much better, i never noticed any jaggies or lag on my player since i put RemICS on it. :good:
Hey guys I just got NFS: Most Wanted on the ATT Note. The gameplay and the controls are great but the game sort runs in slowmo. Anybody else getting different performance in other ROMS?
I'm running flapjaxx's AOSP ICS rom W/ GPU OC and CPU OC. I assume the slowness is due to the Note's large resolution and it's not quite as optimized as it could be for our phones. It is smooth but just terribly slow.
UPDATE
OOOOKAY guys I am back with some interesting results!
I continued to try more roms and see the performance with Need for Speed Most Wanted. I first tried Flapjaxx's stock ICS rom with touchwiz with an overclock kernel and gpu OC. That ran better than any of the AOSP but still had some slowness to it.
Seeing as the stock roms tended to give more performance, I tried another stock rom. This one: http://forum.xda-developers.com/showthread.php?t=1766933. No OC kernel, everything stock pretty much. Here is what happened:
1. I restored NFS from titanium
2. NFS says this android is not compatible
3. I uninstall NFS and install it from the Playstore and redownload the SD data
4. Ran the game and observed that there was little to no lag! Well I'm sure it could be a bit better, the frame rate was totally playable and it actually felt speedy!
Now i'm not sure what is happening here. Either 1. the game downloaded a new SD data with lower graphics requirements, 2. the game recognized the device as a different device and choose the graphics setting accordingly, OR 3. the device just performs better @ mostly stock. Now can anybody inform me on how the SD Data actually works that would be great so I can pinpoint what it is.
My next test will be using the above rom that yielded good performance with flapjaxx's OC/GPU kernel to see if it speeds up the frames anymore.
UPDATE 2
After a bit more testing I see that without the OC kernel and using the kernel from 'better stock' ROM above, the road actually is missing some water and effects which is probably leading to the smoother gameplay! If anybody else is testing this let me know what your results are!
UPDATE 3
Trying out flappjaxx's Jelly Bean rom with his GPUOC and CPUOC. No surprise there, graphics got bumped up.
What I did notice is that there is almost NO DIFFERENCE in frames (from what I could see) from Stock rom + AOSP/JB roms with OC kernel in BUMPER CAMERA MODE despite the higher graphics. To be clear, those of you on AOSP that are already using bumper mode will not get higher frames in bumper mode on something like a stock rom. There is little to no difference in bumper modes. Should be all that I can test now. I will be sticking with this Jellybeanie and playing NFS in bumper camera mode myself (in car view).
EA, give us graphic options. That is all.
UPDATE 4
In conclusion:
Game is somehow determining the graphics through the kernel
SD Data downloaded is the same on every rom, don't have to download new SD Data.
Some roms perform better than others. I had a lot of luck with Jelly Bean roms on stock kernel, no need to overclock.
Figured I'd give you guys a ranking list from roms. Going from best to worst
1. Latest Jelly Bean Nightly 11/21 Stock Kernel - Great out of car and even faster in car - graphics medium
2. Flapjaxx's FJ Stock Rom Mod - OCGPU/CPU best performance (in car view only) - graphics high
3. Electro's Stock Rom - Stock Kernel with no OC Okay performance in both out of car view and in car view - graphics medium
im running AOPK milestone 1, You can kinda play the game....but all the cars are black the buildings are black and the road is black....Not really sure what is going on! but I do get the slowmo at first but after I go to the menu and go back to playing the game it starts to run smoothly....in black that is!
I noticed the slowness as well, I switched to the in car view and it runs much better. Give that a try...
Sounds like u downloaded the wrong SD data
Sent from my SAMSUNG-SGH-I717 using xda premium
ksprelude01 said:
im running AOPK milestone 1, You can kinda play the game....but all the cars are black the buildings are black and the road is black....Not really sure what is going on! but I do get the slowmo at first but after I go to the menu and go back to playing the game it starts to run smoothly....in black that is!
Click to expand...
Click to collapse
That's jelly bean right? I had some problems running games and with graphical glitches in jelly bean until I turned off HW overlay and that stopped my problems.
omniphil said:
I noticed the slowness as well, I switched to the in car view and it runs much better. Give that a try...
Click to expand...
Click to collapse
Wow, yeah running in that camera mode is a lot better. Hopefully the fix the issues completely. Thanks for the tip!
geeksquadryder said:
Sounds like u downloaded the wrong SD data
Click to expand...
Click to collapse
What do you mean?
Seems to run a little laggy on mine, and it's a real battery hog as well
Sent from my SAMSUNG-SGH-I717 using xda premium
Tomdg07 said:
Seems to run a little laggy on mine, and it's a real battery hog as well
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Ditto, switching to in-car view is definitely a lot smoother, has decent graphics but looks like the limit of S3 Adreno 225 chip has been reached, this (and other games of similar graphic quality) may be enough reason for me to upgrade to note 2 later. I also have slow down problem with NBA 2K13.
No real graphic glitch however, if you see missing textures it has to be wrong sd data, remember we are Snapdragon NOT Mali.
Im on liquid RC7 with KK.12 kernel no overclocking and the game seems to run fine for me with no lags..however Tomdg07 is right its a battery hog which quite frankly isnt a surprise. I just got off a 30 minute subway ride and I was playing it the entire time..used up exactly 20% of the battery.
kingofkings11 said:
Im on liquid RC7 with KK.12 kernel no overclocking and the game seems to run fine for me with no lags..however Tomdg07 is right its a battery hog which quite frankly isnt a surprise. I just got off a 30 minute subway ride and I was playing it the entire time..used up exactly 20% of the battery.
Click to expand...
Click to collapse
Really? No lag? Hmm, what's that ROM? Is it one of the Jellybeanies? Have you tried in car view to see if it is even faster than out car?
Metsuna said:
Really? No lag? Hmm, what's that ROM? Is it one of the Jellybeanies? Have you tried in car view to see if it is even faster than out car?
Click to expand...
Click to collapse
Yes indeed no lag at all - Liquid is a jellybeanie you can find it in the original development thread. To be honest I havent had the need to try in car view because the out car view has been working fine.
I should mention though that whilst I have not over clocked I am using several build prop tweaks some of which Im sure optimize graphics and what not.
kingofkings11 said:
Yes indeed no lag at all - Liquid is a jellybeanie you can find it in the original development thread. To be honest I havent had the need to try in car view because the out car view has been working fine.
I should mention though that whilst I have not over clocked I am using several build prop tweaks some of which Im sure optimize graphics and what not.
Click to expand...
Click to collapse
Just tried NFS Most Wanted on Liquid with KK Kernel and no luck. I even tried some build prop tweaks. It just feels too slow. Weird.
Going to try deleting it and redownloading the SD Data instead of restoring it from Titanium. Will report back with results.
EDIT: No go either. Still low frame rates. On a good note however, Liquid Jellybean Rom is probably the most stable of the Jellybeanies.
OOOOKAY guys I am back with some interesting results!
I continued to try more roms and see the performance with Need for Speed Most Wanted. I first tried Flapjaxx's stock ICS rom with touchwiz with an overclock kernel and gpu OC. That ran better than any of the AOSP but still had some slowness to it.
Seeing as the stock roms tended to give more performance, I tried another stock rom. This one: http://forum.xda-developers.com/showthread.php?t=1766933. No OC kernel, everything stock pretty much. Here is what happened:
1. I restored NFS from titanium
2. NFS says this android is not compatible
3. I uninstall NFS and install it from the Playstore and redownload the SD data
4. Ran the game and observed that there was little to no lag! Well I'm sure it could be a bit better, the frame rate was totally playable and it actually felt speedy!
Now i'm not sure what is happening here. Either 1. the game downloaded a new SD data with lower graphics requirements, 2. the game recognized the device as a different device and choose the graphics setting accordingly, OR 3. the device just performs better @ mostly stock. Now can anybody inform me on how the SD Data actually works that would be great so I can pinpoint what it is.
My next test will be using the above rom that yielded good performance with flapjaxx's OC/GPU kernel to see if it speeds up the frames anymore.
UPDATE
Tried the OC Kernel on the stock ROM which lead it to being slow again! I'm not sure now what to think. Going to wipe and go back to the 'better stock' kernel not the 'pure stock'.
After a bit more testing I see that without the OC kernel, the road actually is missing some water and effects which is probably leading to the smoother gameplay! If anybody else is testing this let me know what your results are!
I really just wish there was an in-game settings option to reduce the graphics quality...... (if there is and I'm missing it please fill me in)
Sent from my SAMSUNG-SGH-I717 using xda premium
Tomdg07 said:
I really just wish there was an in-game settings option to reduce the graphics quality...... (if there is and I'm missing it please fill me in)
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Agreed. Right now there is no way to change graphics quality. Certainly would save me trouble. What I think is happening is that with some Roms and Kernels the game thinks we have higher hardware and cranks up the graphic quality thus slowing down the performance of the game.
What I found is every time I used an OC kernel of some type, the game slows. So it might be a kernel issue.
I just cant comprehend why despite having the same phone and same setup (i.e. rom, kernel etc) we get totally different results.
PS> Tomdg07 props to your state for pushing obama over the 270 he needed to win. Americans totally made up for giving dubya two terms.
I was testing some more Roms yesterday including Black IV and Electro's stock debloated Rom. Black IV had flapjaxx's kernel with the ability to OC and on the Electro was not OCable.
My results were the same. Something about flapjaxx's kernel or kernels with the ability to OC makes the game bump up in graphics thus making it slower. The game must be scanning the clockspeed or something or maybe it's something deeper than that. If I can I want to test out AOSP roms again to see if its the kernel or both the kernel + the rom.
Trying out flappjaxx's Jelly Bean rom with his GPUOC and CPUOC. No surprise there, graphics got bumped up.
What I did notice is that there is almost NO DIFFERENCE in frames (from what I could see) from Stock rom + AOSP/JB roms with OC kernel in BUMPER CAMERA MODE despite the higher graphics. To be clear, those of you on AOSP that are already using bumper mode will not get higher frames in bumper mode on something like a stock rom. There is little to no difference in bumper modes. Should be all that I can test now. I will be sticking with this Jellybeanie and playing NFS in bumper camera mode myself (in car view).
EA, give us graphic options. That is all.
UPDATE: Those of you that are finding this page and reading this post. Look on the front page for what roms are the best for this game.
Got an alert to update the game when opening it, after updating it won't even open, anyone else issues after update?
Sent from my SAMSUNG-SGH-I717 using xda premium
Tomdg07 said:
Got an alert to update the game when opening it, after updating it won't even open, anyone else issues after update?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Same issue. Luckily I had a backup of the SD data on my hard drive so I can revert back. But yeah something messed up in that download messed up the game for us.
Metsuna said:
Same issue. Luckily I had a backup of the SD data on my hard drive so I can revert back. But yeah something messed up in that download messed up the game for us.
Click to expand...
Click to collapse
Only form of a backup I have is in the nandroid backup I did before flashing cm10, I suppose I could dig it out of there somehow, but I'll give them a day or two to fix it first
Sent from my SAMSUNG-SGH-I717 using xda premium
So had my nexus 10 for a few days now and im confused about the general stuttery performance issues. my galaxy s3 running cm10 runs android rather buttery and smooth. the nexus 10 seems to be lacking butter. ive tried the nexus 4 and it's a great buttery performance but the 10 lags and stutters alot, is this just because of the screen resolution or is a fault of android? ive tried cm10 and others nexus 10 roms but still seems kinda stuttery. is over clocking the answer? it's only really 2d performance where the 10 seems to be lacking and i expected more from a 1.7 dual core proc.
something i have noticed is that as long as i keep my finger on the screen, it does not lag, however if i fling and then remove my figure it lags and stutters.
i want to hear other peoples opinions on nexus 10 performance because so far, i fail to see the butter.
moonytoonyking said:
i want to hear other peoples opinions on nexus 10 performance because so far, i fail to see the butter.
Click to expand...
Click to collapse
If there are performance problems, the reason they never get fixed is that people insist on posting subjective experience with "lag" on xda instead of objective, useful bug reports on the AOSP bug tracker..
In my experience, though, it's always a ****ty app hogging the UI thread in a service or some other noob developer move causing lag.
My N10 is smooth and stock.
The idea behind Project Butter, I believe, is that when you have your finger on the screen, then the governor automatically ramps up the speed to whatever the max has been set to. This is the reason why interactive is now the most common governor of choice for AOSP. I suppose you could root and flash a different kernel with other specialised governors like KToonses, which comes with PegasusQ, KToonsertive and others. Or even on stock you could change to other kernels and see if that helps out. I haven't really been noticing much problem with the stutter even on interactive tbh. Animations are fine, so could be that you do have some cpu intensive app causing the lag.
Sent from my HTC One X using xda premium
I use both daily, cm 10.1 on my d2vzw and can tell you my N10 doesn't lag/stutter, both are comparable speed wise in daily use here. As others have suggested I would check your installed apps for irregular behavior
Sent from my SCH-I535 using XDA
I have a nexus 10 and a 9300i too, and my nexus 10 is much much faster!
Actually thinking about it 1 app runs better on my S3, google chrome. I use the AOSP browser instead on my N10, for this as well as flash support.
Think i found the problem
it would appear that having google currents syncing in the background causes lag. tablet is super fast after disabling.
No lag here whatsoever. Running cm10.1 nightlies.
I haven't had a single hint of lag since day one. Seriously, literally as smooth as smooth can be as far as 2D desktop experience goes. If you're suffering noticeable lag I'd honestly think you have a faulty tablet. This thing is BUTTER.
moonytoonyking said:
it would appear that having google currents syncing in the background causes lag. tablet is super fast after disabling.
Click to expand...
Click to collapse
I believe the thread you're referring to is here:
http://forum.xda-developers.com/showthread.php?t=2012756
bamboosensei said:
The idea behind Project Butter, I believe, is that when you have your finger on the screen, then the governor automatically ramps up the speed to whatever the max has been set to. This is the reason why interactive is now the most common governor of choice for AOSP. I suppose you could root and flash a different kernel with other specialised governors like KToonses, which comes with PegasusQ, KToonsertive and others. Or even on stock you could change to other kernels and see if that helps out. I haven't really been noticing much problem with the stutter even on interactive tbh. Animations are fine, so could be that you do have some cpu intensive app causing the lag.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
The other aspects of project butter such as the vsync made a much bigger difference than the ramping up CPU. Prior to jellybean if a toast notification came up all the animations would become really choppy. Even with the CPU at low speeds the animations stay smooth as they are rendered by the GPU.
Sent from my Nexus 7 using xda premium
blackhand1001 said:
The other aspects of project butter such as the vsync made a much bigger difference than the ramping up CPU. Prior to jellybean if a toast notification came up all the animations would become really choppy. Even with the CPU at low speeds the animations stay smooth as they are rendered by the GPU.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I agree but the TC stated that it didn't lag when he kept his finger on the screen so I assumed it was due to that particular part of Project Butter that made a difference.
Sent from my HTC One X using xda premium
Found a thread with the trick to getting Tegra 4 graphics on our Note 3's. Our device is more than capable of running this so it's BS that Madfinger and other devs do this crap. Give thanks to "lm that guy" in the original thread linked below.
Tegra 4 Graphics: http://forum.xda-developers.com/showthread.php?t=2496204
Dead Trigger 2 Download: https://play.google.com/store/apps/details?id=com.madfingergames.deadtrigger2
Enjoy!!!!
nolimit06 said:
Found a thread with the trick to getting Tegra 4 graphics on our Note 3's. Our device is more than capable of running this so it's BS that Madfinger and other devs do this crap. Give thanks to "lm that guy" in the original thread linked below.
Tegra 4 Graphics: http://forum.xda-developers.com/showthread.php?t=2496204
Dead Trigger 2 Download: https://play.google.com/store/apps/details?id=com.madfingergames.deadtrigger2
Enjoy!!!!
Click to expand...
Click to collapse
I tried this on the Nexus 7 Grouper and it was almost perfect. You can notice very tiny lag when looking at the reflective water, so I expect that any other device out there such as the Galaxy S4 and Note 2 can run it no problems.
Crossvxm said:
I tried this on the Nexus 7 Grouper and it was almost perfect. You can notice very tiny lag when looking at the reflective water, so I expect that any other device out there such as the Galaxy S4 and Note 2 can run it no problems.
Click to expand...
Click to collapse
It was unplayable laggy on my Grouper, might have been the level I was on. The N7 ROMs based on CM are a mess and don't allow custom kernels without what I consider major problems. Not sure what's going on there.
nolimit06 said:
It was unplayable laggy on my Grouper, might have been the level I was on. The N7 ROMs based on CM are a mess and don't allow custom kernels without what I consider major problems. Not sure what's going on there.
Click to expand...
Click to collapse
Yup you were right depends on the level. First level plays pretty stable. Indoor levels are a disaster. The game is pretty damn optimized if it stays as stable as it does. It is playable on mine, just unpleasant to play, not a dramatic lag. I'm pretty pissed i waited all summer for this game, never released then, and now that it is it requires you to be connected to some sort of internet all the time to play. Groupers depend on wifi, i live in NYC where the best time to play is while on the buses. Buses don't have wifi?!?! How am I to play lol. And my Nexus 7 is mint but the wifi is pretty crappy compared to my girls which has some wear, so here at home even with a good connection i encounter issues playing and the loading also depends on internet believe it or not.
As for roms for the Nexus 7, go with SmoothRom 5.2. Its AOKP based instead of CM. If you've done your homework, AOKP is claimed to be glitchy, but that really doesnt apply to the Nexus 7. And SmoothRom is 99% stable, no crashes, no "Unfortunately BlaBlaBla has stopped working," no fluttering graphical glitches. The 1% instability goes to the fact that at times the stock AOSP browser's Back/Forward/Refresh buttons dissapear. Its stable for daily use. I have it installed on mine and my girls. Only con is that its still stuck on 4.2.2 but the preformance IMO exceeds 4.3 with the tweaks it has.
Kernel-wise, I use M-Kernel to reach the crazy 1.6GHz although I never really clock it that high except when testing preformance differences (it can reach 1.7GHz, the secret is it must be on a single core as NVIDIA points out on their Tegra 3). Franco Kernel gives nice battery life, but theres occasional slowdowns on the entire rom and freezes, at times complete system crashes (not sure if thats only with this rom, i know the latest updates to that kernel suddenly brought that).
So if your looking for a stable, fast, reaponsive rom for the Grouper, think SmoothRom. Kernel is up to you.
I will look in to that ROM, thanks for the heads up.
Sick graphics
Sent from my SM-N900P using XDA Premium HD app
nolimit06 said:
I will look in to that ROM, thanks for the heads up.
Click to expand...
Click to collapse
No problem! You wont regret it let me know how it works out! I'm now testing this on the LG Optimus G...wish me luck!
I'm using the Root Browser in Rom Toolbox. I can edit the value in the XML, and it says it's saving, but when I go back in to the file my edit is reverted back to the original.
How can I tell visually if the ultra high graphics are actually enabled?