Related
I can imagine this may have been asked before, yet I can't find any definitive answers, to what are the benefits to running ICS over Gingerbread at this time?
I dont really think there is much right at this moment, due to the ICS being out is so buggy, but i read alot of positive about CM9 which is running ICS - though one major drawback for me is the USB mount doesn't work.
But after playing around with my dads Galaxy Nexus, the diffrence aint gamebreaking. Surely its optimised in other ways, better interface imo - but again, Gingerbread is really great, and i will surely stick to this untill ROM chefs starts to cook roms on stable ICS releases.
Eventually check out my thread where some people are talking about ICS and the benefits from it compared to Gingerbread
right, ics is still buggy. but check out some of the very good custom ics roms in the development forum. some of them now are more stable than they previously do. i mean, stable enough for daily use.
apparently ICS has a lot of benefit over GB:
some of the good points:
- smoother ui animation (you'll feel more smoother than GB, also there are more transition animation added)
- improved google apps (gmail, calendar, maps, phone, sms have been redesigned and feels better than current version in GB)
- voice dictation (different from the one in GB, instead of "press-speak-press-speak", now you can keep speaking and the word will come out as you speak)
- face unlock (no need to introduce)
- options to encrypt the phone memory (forget if GB has it)
- some new widgets (some of the custom roms use AOSP apps instead of the samsung one, e.g. the calendar widget looks much better now)
- camera app seems to open faster
some problems:
- usb mass storage not working (may get fixed in the future, but now you can use MTP instead, if you are using windows or mac. linux users can have some problem with that)
- some apps don't work with ICS (most apps work, for the rest we need to wait for update to support ics)
- battery drain issue (there have been several report for battery drain on "Android OS" process, google seems to fix it in 4.0.4, so we just need to wait. currently mine can last over 10h with moderate use)
- remember it's still in alpha/beta stage, so backup your data!
if you are really interested, make a full backup using CWM and try to flash some of the roms. you can always go back to ginger bread by recovering the backup. hope this helps
I tried one of the cyanogenmod alpha builds from codeworkx and i had the impression that the menu is cleanear and more tidied up all in all. dont know if thats an ics or a cyanogenmod thing though.
my wireless lan seemed to work better, too
THUDUK said:
I can imagine this may have been asked before, yet I can't find any definitive answers, to what are the benefits to running ICS over Gingerbread at this time?
Click to expand...
Click to collapse
After being on ICS Remix 8.6 by Westcrip, I "feel" the browsing, the sliding and most of the navigation on the phone is happening a lot faster.
Before February I felt like my old Gingerbread-thingy by Eskimo i belive... was the nuts. Now its like playing in a other league.
My SG2 feels generally Smoooottthheeeer
My 3 cents
The taste is better
BigMrB said:
The taste is better
Click to expand...
Click to collapse
More for hot weather, really.
**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
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
Searched and I was surprised there was no main thread comparing and discussing the differences between Sense and AOSP roms like a lot of other device sub forums have. I've been running a Sense 5 rom since I got my DNA a few months ago but have been itching to switch to AOSP. However I have a few questions.
In my past experience with other devices, native ROMs (in this case Sense based) usually work a little better in terms of things like battery life, signal, and stability. Is this the same for the DNA?
Other things I'm concerned about
-Camera: IMO the Sense camera is way better than the AOSP. I can deal with the loss of software features, but is the picture quality still as good?
-Sound: Beats is mostly just an equalizer gimmick, but the DNA is loud and overall sounds great. I briefly ran an AOSP rom and the first thing I noticed was the sounds was distorted at high levels. I also found this thread which echos my problem. Is this still an issue?
I'd say in my opinion you are spot on with the sense vs aosp in the aspect of aosp issues! Just MY OPINION AND PERSONAL FINDINGS! I love Aosp but I do think it lacked some of the "stock, supposed to be there" kind of feeling I get with sense.. I have been running the CM 11 nightlies for quite a while now. I don't know about pic quality for sure. If there is a difference it's not noticeable to me. I do think I get better battery on sense but signal and stability are basically equal..
Sent from my HTC6435LVW using Tapatalk
I haven't run an AOSP rom since I first flashed NOS Google Play Edition. No matter how strong the temptation to try KitKat, the lower external speaker volume on the AOSP roms that I tried, combined with the inability to use Google Sound Search, Soundhound, or Shazam, ultimately made me stick with a rom using the Sense kernel. But, since I can't stand Sense, I'm sticking with GPE Roms, no matter how delayed they may be.
Sent from my DLX using xda app-developers app
I've just been on CM11 today after only using sense 5. I can say I already miss blinkfeed, and can already assume the battery will be worse, but everything else seems the same. It's worth trying. I'm rather fond of the Google integration.
Watercycle said:
I've just been on CM11 today after only using sense 5. I can say I already miss blinkfeed, and can already assume the battery will be worse, but everything else seems the same. It's worth trying. I'm rather fond of the Google integration.
Click to expand...
Click to collapse
The battery is way better when the screen is off, but probably worse than sense when the screen is on. I don't usually have more than 2 and a half hours of screen time in a day, but I typically get about 18 hours of battery on crpalmer's cm11 kernel. Also as far as cameras go, I love camera jb+. Stock aosp camera with some extra features, my favorite being the 6mp setting because it gives me full screen 16:9 pictures. Focal is great too and shows a lot if potential, but it's really unstable.
Sent from my Droid DNA using Tapatalk Pro
The only problem I have with CM based roms is the low volume when recording videos. Otherwise no problems. Battery, signal, speaker volume, etc are are on par or better than Sense plus the snappiness and customizability are great. There may be a couple apps that don't work well with CM ROMs but I don't use those particular apps so it's not a problem for me.
I've been running Carbon 4.3 for the last two months. I have not tried a KK ROM since all the features have not been implemented yet.
orangechoochoo said:
The only problem I have with CM based roms is the low volume when recording videos. Otherwise no problems. Battery, signal, speaker volume, etc are are on par or better than Sense plus the snappiness and customizability are great. There may be a couple apps that don't work well with CM ROMs but I don't use those particular apps so it's not a problem for me.
I've been running Carbon 4.3 for the last two months. I have not tried a KK ROM since all the features have not been implemented yet.
Click to expand...
Click to collapse
FYI, the camcorder volume should be much better for any kit-kat ROM build with the 12/12 or later CM device tree.
Free txs for you choo.cho take er ez
Æaa\../
crpalmer said:
FYI, the camcorder volume should be much better for any kit-kat ROM build with the 12/12 or later CM device tree.
Click to expand...
Click to collapse
Could you make that change to the 4.3 kernel?
orangechoochoo said:
Could you make that change to the 4.3 kernel?
Click to expand...
Click to collapse
It's a change in the CM device tree. Gimme a kit-kat? Aka, time to bit the bullet and update?
crpalmer said:
It's a change in the CM device tree. Gimme a kit-kat? Aka, time to bit the bullet and update?
Click to expand...
Click to collapse
I spent the first two-thirds of the year playing with alpha and beta ROMs, right now I'm just holding steady with the full-featured versions of 4.3. Plus there's nothing compelling about KK ROMs except for the fact it's new. It has ART but it's still too new and some devs suggest against using it for now.
In my experience sense obviously has a better camera and also better sound even with beats off and viper audio sense sound is just better.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
orangechoochoo said:
I spent the first two-thirds of the year playing with alpha and beta ROMs, right now I'm just holding steady with the full-featured versions of 4.3. Plus there's nothing compelling about KK ROMs except for the fact it's new. It has ART but it's still too new and some devs suggest against using it for now.
Click to expand...
Click to collapse
I've made the jump and I'm on the latest CM 4.4.2 (12-17 build) and it is sooooo much faster and smoother than 4.3. I was scared to make the jump but this thing really flies. Battery life is about the same.
HTC DNA
d08speed3 said:
I've made the jump and I'm on the latest CM 4.4.2 (12-17 build) and it is sooooo much faster and smoother than 4.3. I was scared to make the jump but this thing really flies. Battery life is about the same.
HTC DNA
Click to expand...
Click to collapse
Even compared to 4.3 with your build.prop tweaks?
orangechoochoo said:
Even compared to 4.3 with your build.prop tweaks?
Click to expand...
Click to collapse
Yup. I've applied my same tweaks to 4.4.2 and it flies man. Its really stable. To odeox the ROM use this flashable zip I found in this thread. Download the "ARMEABI" (That's for our device). I'm really happy with kitkat.
http://forum.xda-developers.com/showthread.php?p=47462548
HTC DNA
Thanks for all the input so far. Still a little worried about the sound issues but I'll probably give an AOSP rom a try, can always revert back to my nandroid
detonation said:
Thanks for all the input so far. Still a little worried about the sound issues but I'll probably give an AOSP rom a try, can always revert back to my nandroid
Click to expand...
Click to collapse
Def give it a try it's fun I do it all the time but inevitably always go back to sense
Sent from my HTC6435LVW using XDA Premium 4 mobile app
d08speed3 said:
Yup. I've applied my same tweaks to 4.4.2 and it flies man. Its really stable. To odeox the ROM use this flashable zip I found in this thread. Download the "ARMEABI" (That's for our device). I'm really happy with kitkat.
http://forum.xda-developers.com/showthread.php?p=47462548
HTC DNA
Click to expand...
Click to collapse
I tried KK today, what annoys me is:
1. The browser, which I use a lot, doesn't have text reflow, incognito mode, and working full screen mode (hide nav bar). I do not like other browsers.
2. The dialer sucks.
With the tweaks it doesn't seem much faster than 4.3.
orangechoochoo said:
I tried KK today, what annoys me is:
1. The browser, which I use a lot, doesn't have text reflow, incognito mode, and working full screen mode (hide nav bar). I do not like other browsers.
2. The dialer sucks.
With the tweaks it doesn't seem much faster than 4.3.
Click to expand...
Click to collapse
Weird. Ive flashed back and forth between 4.3 and 4.4....4.4 feels way smoother
HTC DNA
I don't care for smoothness, I want it to be responsive and fast. If I flick up or down I don't want a delay to make it feel smooth, I want it to instantly move fast. That's just me, I have all animations and various frills turned off. I replicated the same setup on 4.4 and it just wasn't the same.
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