Difference between 4.1.1 and 4.1.2 - Verizon Samsung Galaxy Note II

I keep reading posters claiming that CleanROM is better than Beans because you get "all the new features" of 4.1.2 android.
After trying both ROMs (they are both awesome) I always end up going back to my red/black themed Beans setup as I like all the Beans custom options that are not available in CleanROM.
My question is however, what features am I missing out on by running 4.1.1 instead of the newer version?? After running them back to back, I could barely remember which was which. The two seemed exactly the same to me, what did I miss here??

Not a whole lot.
Touchwiz sees some minor updates, like autocorrect on the keyboard. Some other things, we already had, like the ink effect on the lockscreen.
As for base Android, nothing you would care about or notice is in 4.1.2. Most users think that a version number higher means its faster, more stable, better on battery life, and many other things.
At the end of the day, its simply not true.
4.1.2 came out when it did (instead of being included in 4.2) because the Nexus 7 required it for the new hardware revision (power management hardware change). It wouldn't run on 4.1.1.
Take a look:
http://www.androidpolice.com/2012/1...4-1-2-at-the-low-level-developer-commit-logs/

adrynalyne said:
Not a whole lot.
Touchwiz sees some minor updates, like autocorrect on the keyboard. Some other things, we already had, like the ink effect on the lockscreen.
As for base Android, nothing you would care about or notice is in 4.1.2. Most users think that a version number higher means its faster, more stable, better on battery life, and many other things.
At the end of the day, its simply not true.
http://www.androidpolice.com/2012/1...4-1-2-at-the-low-level-developer-commit-logs/
Click to expand...
Click to collapse
Thanks for the reply, that's exactly what I figured.
I saw no advantage whatever when I tried both versions back to back but I thought maybe I missed something.
I already had an auto-correct KB and 4.1.1 is certainly just as fast/stable etc.
My battery life with beans ROM and the perseus kernel is amazing also.

4.1.2 is faster then 4.1.1 benchmarks proves it
On 4.1.1 on quadrant I'll score like 6100 but on 4.1.2 I'll hit 7000

winco209 said:
On 4.1.1 on quadrant I'll score like 6100 but on 4.1.2 I'll hit 7000
Click to expand...
Click to collapse
adrynalyne said:
Most users think that a version number higher means its faster, more stable, better on battery life, and many other things.
At the end of the day, its simply not true.
Click to expand...
Click to collapse
I rest my case.

adrynalyne said:
I rest my case.
Click to expand...
Click to collapse
LOL, exactly.......
I laughed so hard when I saw your reply I almost choked on some ice tea I was drinking!!

So far, it seems to me that the biggest difference is that auto brightness on 4.1.2 is a lot brighter that on 4.1.1. It almost seems to not be working when you come from 4.1.1 because it keeps the screen much brighter on average. So much so that it seems that it isn't auto dimming.

Kamar234 said:
So far, it seems to me that the biggest difference is that auto brightness on 4.1.2 is a lot brighter that on 4.1.1. It almost seems to not be working when you come from 4.1.1 because it keeps the screen much brighter on average. So much so that it seems that it isn't auto dimming.
Click to expand...
Click to collapse
It depends. it is my understanding that auto brightness works differently on 4.1.2 since you can set a "notch" that you want auto brightness to work around. e.g. auto brightness on and set at 100%, auto brightness will either dim slightly under 100 or slightly over 100. while 4.1 uses the intervals between 0-100% and dims accordingly to location. e.g. you are in a dark area, and it sets your brightness at 20% down from 100%.
that is why 4.1.2 seems slightly dimmer, or slightly brighter depending on the situation
to me FW updates mean one of two things, security, feature, or compatibility updates. it doesn't mean it is faster. i also don't see why anyone even cares about quadrant scores after it has been debunked that the paid version gives you +1000 points.

Yeah, that's how it's been explained to me too. It seems from reviews that Samsung cranked up the max brightness as well. I honestly don't like it. It makes the screen burn more power as it's not as flexible. I guess they did this because people have complained about their screens being too dim since the Galaxy Nexus. If I'm in a dark room I need to turn it down to not blind myself, and when I go outside, I have to turn it up to see. Kind of defeats the purpose of auto brightness. I agree, the whole benchmark thing is useless. This phone kicks butt, but there are certain triangle fill tests that it does very poorly on in comparison to other chips. However, it doesn't effect it in game play at all. I'll take that over pretty scores any day.

Related

my note seems a bit "laggy"

I'm coming from the uk galaxy s2 and this phone seems a bit choppy .. like when typring it takes a bit to catch up? Any way to speed it up? Should I turn something on or off?
The Samsung keyboard is very slow. I've had the best luck with smart keyboard. I still get the occasional hiccup once and a while tho.
I'm suprised I haven't seen any build.prop tweaks yet
Sent from my SAMSUNG-SGH-I717 using xda premium
I use A.I keyboard, its always been great..
I mean the over all system, I'm really thinking of returning it for the Skyrocket, this bothers me. I'm guessing ICS will be more intensive, and if it's already chocking on Gingerbread well, heck the phone will really have a tough time with ICS! Any thoughts on this?
Thremix said:
I use A.I keyboard, its always been great..
I mean the over all system, I'm really thinking of returning it for the Skyrocket, this bothers me. I'm guessing ICS will be more intensive, and if it's already chocking on Gingerbread well, heck the phone will really have a tough time with ICS! Any thoughts on this?
Click to expand...
Click to collapse
ICS optimizes performance, based on the performance of the Gnex atleast. It has a weaker 4430 TI cpu, and a slightly lower resolution screen.
I'm not sure what you mean by choppiness, even with system powersaving and battery saver on, it's not choppy for me. Android 3.0... now that was choppy!
You might try the OC kernel, that should help your performance, even at stock.
spykerv said:
ICS optimizes performance, based on the performance of the Gnex atleast. It has a weaker 4430 TI cpu, and a slightly lower resolution screen.
I'm not sure what you mean by choppiness, even with system powersaving and battery saver on, it's not choppy for me. Android 3.0... now that was choppy!
You might try the OC kernel, that should help your performance, even at stock.
Click to expand...
Click to collapse
The Galaxy Nexus has an OMAP 4460..
Sorry, I think I was thinking of the Droid Razr (which afaik has that).
Well, the 4460 has comparable performance no? Look at the Gnex on ICS, its fantastic! There are many optimization, if anything, it will run much faster once ICS rolls around.
I had a Skyrocket and my stock, rooted Note is every bit as fast.
Huh.. I might try a factory reset, think this would help? Or maybe I got something running taking up the ram? How should I go about this investigation?
ICS will do so much better on this phone than most phones currently on the market and if Samsung and At&t dont bloat it too much, most likely better the the Gnex, the specs are just better on this phone
Sent from my SAMSUNG-SGH-I717 using XDA
Use this ICS themed keyboard in the market.
https://market.android.com/details?...sMSwyLDEsImlucHV0bWV0aG9kLmxhdGluLnBvcnRlZCJd

ice cream & lag.

i have a valid question for you guys. every ice cream rom ive tried has given me significant lag/choppiness and heats up my rezound. now today i played with both a gnexus at verizon and a htc one x at at&t and it was smooth as butter. is our issues because of no ota or kernel source? just curious as to what you guys think?
thanks!
fix-this! said:
i have a valid question for you guys. every ice cream rom ive tried has given me significant lag/choppiness and heats up my rezound. now today i played with both a gnexus at verizon and a htc one x at at&t and it was smooth as butter. is our issues because of no ota or kernel source? just curious as to what you guys think?
thanks!
Click to expand...
Click to collapse
Both I would take a very educated guess in saying. no OTA means it is a work in progress and no kernel source means that the kernels aren't really tweaked out for the ROMs they are running....
my guess is sense bogs us down a good bit. also ics is coded for the gnex.
Without kernel source, we're stuck with what the leak has. From what I've read, that is not good.
I'm sticking with GB until we have source...GB flies for me!
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
tspderek said:
my guess is sense bogs us down a good bit. also ics is coded for the gnex.
Click to expand...
Click to collapse
Yeah, Sense 3.5/.6 are steaming piles of laggy crap, but 4.0 seems really nice.
I have official ics on my unrooted galaxy tab 2. It has the touchwiz overlay but is still superfast. I was worried too that ICS was slow until I got this. I think the omap processor is a better performer on average than a qualcomm too, but not by much.
If you are running the gb kernel and firmware it is hit or miss with ics roms for the rezound. GB will always be faster if running gb firmware and kernel. I hope that the ics kernel is fixed when we get the official ics update and that sense doesnt bog things down. We really need htc to release kernel source and firmware in order to have a solid base for ics roms imo. I love Rez Rom Sense 3.6 ICS though, runs pretty good even on old firmware.
sent from my galaxy tab 2
LunaticSerenade said:
I'm sticking with GB until we have source...GB flies for me!
-5
Click to expand...
Click to collapse
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
tekhna said:
Yeah, Sense 3.5/.6 are steaming piles of laggy crap, but 4.0 seems really nice.
Click to expand...
Click to collapse
Actually for me all of the sense 4.0 ports were super laggy. I can say gb seems more fluid but the battery life still stinks on my rezound. That one x is really a nice device but im thinking this may be my last htc. I havent had good luck with the brand.
Thanks for the responses guys.
ICS doesn't lag for me ever, but I dig the Senseless roms for the looks, and indeed, Sense 4.0 isn't optimized for us yet.
jmorton10 said:
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
Click to expand...
Click to collapse
when i went from a sense rom to an aosp rom on my inc2 i noticed a big difference in speed. sense definitely affects things.
ics runs great for me on 3.5/3.6 and on 4.0 its great as well... i have no problems at all
I don't get all these people who have all the battery and heating problems. I think it is user error. I have better battery and better signal since I upgraded to ICS CleanROM.
GrayTheWolf said:
I don't get all these people who have all the battery and heating problems. I think it is user error. I have better battery and better signal since I upgraded to ICS CleanROM.
Click to expand...
Click to collapse
Agreed, if there were such a range in hardware that some overheated while others were great, I'd expect that HTC's quality control was so bad that half the units that were produced wouldn't even power up. Always get a kick out reading about someone who has warrantied a couple of phones then in the next breath says "I'm running "xyz" kernel and OC'd...
Anyway, would you mind sharing your setup Gray? It might help others to know what a working ICS setup is. What Kernel, Radios and other specifics are you running.
What I find is interesting is that with my first rezound I had a horrible experience when I flashed the ICS leak. Extreme overheating, even worse battery life, but it was nothing that I could have done. It was the radios on some hardware that cause this issue. I sent it back, got another, and reran the leak. Haven't looked back since. It's also worth noting that I have a way better experience with ICS then I did with GB. GB scrolling was always choppy and just overall sluggish. ICS fixed all that along with giving me a battery life ranging from 11-17 hours depending on usage.
nolimit78 said:
What I find is interesting is that with my first rezound I had a horrible experience when I flashed the ICS leak. Extreme overheating, even worse battery life, but it was nothing that I could have done. It was the radios on some hardware that cause this issue. I sent it back, got another, and reran the leak. Haven't looked back since. It's also worth noting that I have a way better experience with ICS then I did with GB. GB scrolling was always choppy and just overall sluggish. ICS fixed all that along with giving me a battery life ranging from 11-17 hours depending on usage.
Click to expand...
Click to collapse
I also have a better user experience, as in runs faster, smoother, and less lag along with better battery life on ice cream sandwich than I did on gingerbread. I think a lot of it has to do with how it's set up and configured. And I understand that some people have genuine hardware problems but it seems that it's causing a lot of people to quickly attribute their issues to hardware and not spend the time to chase down the problem and solve it. Regardless another leaked kernel or an official OTA base will definitely be welcomed and help this beast run even better.
bwthor20 said:
Agreed, if there were such a range in hardware that some overheated while others were great, I'd expect that HTC's quality control was so bad that half the units that were produced wouldn't even power up. Always get a kick out reading about someone who has warrantied a couple of phones then in the next breath says "I'm running "xyz" kernel and OC'd...
Anyway, would you mind sharing your setup Gray? It might help others to know what a working ICS setup is. What Kernel, Radios and other specifics are you running.
Click to expand...
Click to collapse
CleanROM Developer 1.2, overclocked 1.8ghz kernel, AmonRa recovery, new ICS radio, juopuntbear boot, S-Off.
Extremely smooth and no problems at all.
Ill put it in my sig too.
jmorton10 said:
GB flies for me too, even running a sense ROM.
I always chuckle when people post how "slow and laggy" sense is.
I get absolutely zero lag running sense 3.5 and figure those posters are probably clueless on how to correctly set up their system.......
Click to expand...
Click to collapse
I don't get any "lag" persay with any Rom I've used. What drives me a little nuts is the stuttery and choppy scrolling in a LOT of apps I use daily. The text and the pictures chop, even though the scrolling motion is smooth. Facebook, zynga apps, internet (if its more than text) messaging app, contacts, reddit news... There are some that don't stutter though. Twicca, tapatalk, menu scrolling, root explorer...
platinumrims said:
I don't get any "lag" persay with any Rom I've used. What drives me a little nuts is the stuttery and choppy scrolling in a LOT of apps I use daily. The text and the pictures chop, even though the scrolling motion is smooth. Facebook, zynga apps, internet (if its more than text) messaging app, contacts, reddit news... There are some that don't stutter though. Twicca, tapatalk, menu scrolling, root explorer...
Click to expand...
Click to collapse
That annoyed me about GB (stock and CleanROM 1.7.5). Even on ICS, Facebook scrolling is choppy, unless you enable Force GPU rendering. Running ICS with Force GPU rendering is an incredibly smooth experience, and I haven't run into any bugs. I'm surprised it's not enabled by default in all ROMs.
I think that people having a better experience on a hacked(nicely mind you), sense 4.0 rom must have set up Gingerbread wrong. See how easy it is to make a statement like that. I have experienced both ics, and gb, and have always had a smoother experience on gb. I hated how ics scrolling in the browser, xda app, tapatalk, and others was jittery at best. I love some of the elements of ics, but the trade off was too much for me. My phone ran about 11 degrees different between ics, and gb. Also, if you go back to around Christmas, overheating was an issue then. On stock. So apparently, this phone can have heat issues. Don't get me wrong, I love this phone, and I appreciate all the work that goes into making roms. I have been following these developers for quite a while. They are all really good. We are blessed to have them.
Sent from my ADR6425LVW using XDA
destro158 said:
That annoyed me about GB (stock and CleanROM 1.7.5). Even on ICS, Facebook scrolling is choppy, unless you enable Force GPU rendering. Running ICS with Force GPU rendering is an incredibly smooth experience, and I haven't run into any bugs. I'm surprised it's not enabled by default in all ROMs.
Click to expand...
Click to collapse
So it is the GPU that's the problem as I thought.... But thankfully it isnt because its not good enough. Lol. It's just because its more limited c

Why did Samsung have to mess with a good thing? (finger tracking)

Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Using cm9 and camera I working fine snappy and touchscreen is very nice!
Sent from my GT-I9300 using xda premium
dinan said:
Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
mintvilla said:
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
Click to expand...
Click to collapse
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
dinan said:
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
Click to expand...
Click to collapse
so did you sort out how to feed your finger tracking needs ??
i feel i think exactly like you... id like to keep my crapwiz functionalitues, but i'm crying out for the miss of smoothness here.
since me and u seems to have the same needs on this topic, please let me know if you find out somethig intresting.
c ya
dinan said:
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
Have you tried running a custom stock-based ROM that has the scrolling cache disabled (such as WanamLite) or with a kitchen option to disable this cache (such as Omega)?

Jelly Bean Smoothness

**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

Let's go back to Jelly Bean

Whoa, Did I really say that?
I remember posting in the KitKat thread daily and looking at various LG sources for the newest update. I got excited when I saw how much faster and smoother KitKat was in this video: http://www.youtube.com/watch?v=_UcvB4aD0KA
When I first tried KitKat I was really impressed. Maybe it was placebo. But it felt smoother and nicer. And I got Immersive mode too! Then I noticed that the battery drained faster, but I learned to accept that. Recently; I was barely able to reach 4h 30 min of SOT on kitkat. The standby times were awful, too, and without root, you have no way of checking what's eating your battery.
It all culminated with the 20D update, that rendered VOIP useless and impossible. I then decided I wanted to return to JB.
I had almost forgotten how GOOD Jelly Bean was. Sure, there's lockscreen lag, occasional scroll animation lag and no immersive mode, but apart from that, I barely notice any major drawbacks. Battery life is so much better, wakelock detectors function perfectly and VOIP works!
So for those of you who have had this thought in your mind for long, just do it. The process of going back to jelly bean took me about 5 minutes and I'm happy with my decision, at least for now.
Have you had a similar experience then please share it!
Guide for going back to JB: http://forum.xda-developers.com/showthread.php?t=2432476
I bought my G2 before KK was released for it. Initially, I was only delaying the upgrade because Swiftkey wouldn't work for kitkat on the G2. I am staying on Jellybean now. Everyone I know with this phone complains of issues now after going to KK.
donm76 said:
I bought my G2 before KK was released for it. Initially, I was only delaying the upgrade because Swiftkey wouldn't work for kitkat on the G2. I am staying on Jellybean now. Everyone I know with this phone complains of issues now after going to KK.
Click to expand...
Click to collapse
I have zero issues on kitkat. Then again im running aosp.
Jellybean was trash for the vs980 because of reboots, and sod's on aosp.
I will agree on stock jellybean I had better battery life, but if you need better than a day off charge with 5-7 hours sot, you have issues.
I'll pass.
Sent from my Vs980 running SlimKat 4.4.4
T-mobile D801 here, latest KK.
absolutely zero issues here. the battery life is actually better, the performance across the board is way better, the extra features are great and worth it. the only issue i was concerned with before the upgrade was the audio hiss / distortion but as it turned out D801 has never suffered from it and on latest KK the sound is as good as with JB for me.
Agree... Except the camera was unbearable!!
Still, I think it's excellent we can go back. Subscribed.
Sent from my LG-D802 using XDA Premium HD app
It will be nice if we have a flashable stock jb+root and maybe latest camera mod for jb build in..
Kk aosp...
Sent from my LG G2 D802
might be nice to use kk ondemand settings on jb.. make it a bit snappier
also the advantage of using aosp browser properly is a big plus.. with webview intact
donm76 said:
I bought my G2 before KK was released for it. Initially, I was only delaying the upgrade because Swiftkey wouldn't work for kitkat on the G2. I am staying on Jellybean now. Everyone I know with this phone complains of issues now after going to KK.
Click to expand...
Click to collapse
SwiftKey worked on Kitkat since day one. You would just get a popup that gapps stopped working once you turned the phone on but that was all.
Lawlrus said:
Jellybean was trash for the vs980 because of reboots, and sod's on aosp.
I will agree on stock jellybean I had better battery life, but if you need better than a day off charge with 5-7 hours sot, you have issues.
I'll pass.
Sent from my Vs980 running SlimKat 4.4.4
Click to expand...
Click to collapse
You are more than free to pass, but the thing is - on kitkat, I was barely able to get four hours of SOT on a regular basis. And since I'm an unrooted user, I have NO ways of checking what's draining my battery at all. Sure Jelly Bean is not flawless, but battery life is very important to me and seems more stable all around.
mannequin said:
T-mobile D801 here, latest KK.
absolutely zero issues here. the battery life is actually better, the performance across the board is way better, the extra features are great and worth it. the only issue i was concerned with before the upgrade was the audio hiss / distortion but as it turned out D801 has never suffered from it and on latest KK the sound is as good as with JB for me.
Click to expand...
Click to collapse
My device never had the hissing problem with KitKat, and the perfomance was generally much snappier. But the international KitKat didn't seem to be refined at all, so maybe TMo did their job!
meangreenie said:
might be nice to use kk ondemand settings on jb.. make it a bit snappier
also the advantage of using aosp browser properly is a big plus.. with webview intact
Click to expand...
Click to collapse
I agree. But I actually figured that the phone runs much cooler on Jelly Bean BECAUSE the speed doesn't jump to 2.26Ghz instantly. I also think that the refined ondemand is what's taking a toll on the battery =)
JB had HORRIBLE bluetooth drivers on stock for my device in my Honda Civic. The static in the background was borderline unbearable. KK update fixed it so I'm sticking with KK. Battery life could be better though, I do agree. Something I've always noticed about all devices I've owned is that the shipping OS is always the most stable.
Ascertion said:
JB had HORRIBLE bluetooth drivers on stock for my device in my Honda Civic. The static in the background was borderline unbearable. KK update fixed it so I'm sticking with KK. Battery life could be better though, I do agree. Something I've always noticed about all devices I've owned is that the shipping OS is always the most stable.
Click to expand...
Click to collapse
Now that you remind me - I occasionally played music from my phone in my dad's car through bluetooth. I only have lossless music on my G2 (.FLAC), so the music quality of the files is generally very good. On kitkat, however, I would start hearing background noises at higher volumes. That's not a problem on Jelly Bean at all.
I guess you're right about your observation, although instead of going back to the 10A which my phone shipped with, I downgraded to 10F (a version of the software, which I never got). The only major difference I feel between 10A and 10F (and keep in mind it's over 4 months since I last used JB) is, that knock on is much faster on 10F and very comparable to KitKat. The only thing I really miss, however, is the CPU jumping up to an adequate frequency to prevent lockscreen lag.
I do agree with the fact JB had stellar battery life compared to KK, although i feel like if i go back to JB, mentally thinking i feel outdated compare to the other phones out there, but thats just me haha, i never had any lags when i first got my G2 out of the box, highly disappointed the fact KK did the opposite in terms of battery life. Honestly i cant really complain, this battery still beats all the devices ive owned or came across and tried for a few days, M7, S4 etc
I guess the kk battery is also more bad because like you guys said it is fast and smoother then the jb stock and jb stock is cooler so yh... Their kernel. Kk stock users must just use dorimanx kernel its better and safer then the stock one
Why stop there? Maybe we can get gingerbread ported over...smh
Sent from my LG-D802 using XDA Premium HD app
stoney73 said:
Why stop there? Maybe we can get gingerbread ported over...smh
Sent from my LG-D802 using XDA Premium HD app
Click to expand...
Click to collapse
I thought CupCake was way betttttter
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
@OP
"I had almost forgotten how GOOD Jelly Bean was."
R u sure you meant "GOOD" and not "BAD"???
You can always go back to JB and then months later, you could say the same thing "I had almost forgotten how GOOD Kit Kat was."
C'mon, m8, move forward.
I have seen too many people eager to get the new update (that many people usually do curse mfg. for slow update) then demand to go back.
Same exact reaction with Windows OS.
I personally have no issue with KK.
Im going to 4.4.4 cm11 to see what its like and if its cack ill be going back to jb i think.

Categories

Resources