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)?
Related
hey, i was just trying to get some feed back on what differences are there in gb that would be a good reason to leave froyo. the reason i ask is because i put a gingerbread rom on my vibrant for about a day and did not see a deference. everything pretty much looks the same. maybe someone can give me a strong argument for switching because at this point i just don't get it.
I was on GB for a couple weeks to try it out but with all of the bugs and non working GPS its just not worth it til there are more stable roms. People will argue that the GB roms are stable but I've had several problems on GB roms, nothing big but little bugs that just get annoying after a while. I would stick with froyo
Dont switch. They just drain your battery and have loads of bugs, like not beeing able to charge when off.(CM7)
Sent from my SGH-T959 using XDA App
New user interface design with new themes (Black themes save power)
Extra Large Screen Size supported
SIP Communication Supported (SIP Video and Audio Calling, In an operator point of view, this is feature will decrease their voice calling revenue where as user can call each other for lower rates or even free if they have good data connection)
Supports for NFC (High Frequency High Speech Data Transfer in short range)
Support for WebM/VP8 video playback, and AAC audio encoding
New audio effects such as reverb, equalization, headphone virtualization, and bass boost
Improved Copy and Paste functionality
Redesigned Multi Touch Software Keyboard
Audio, graphical, and input enhancements for game developers
New sensors support (i.e gyroscope)
Download manager for long running HTTP downloads
Enhanced support for native code
Improved power management and application control
Support for multiple cameras
there's your list of differences from froyo to GB
I switched because cm7 is just lightyears faster than froyo or anything eelse on our phones ... games that wouldnt work on other roms in n64oid now run smoothly
Sent from a cell tower to the XDA server to you.
It is definitely not worth switching until we get an official leak, although at this point it may be worth facing up to the fact that there will not ever be an official GB rom. The ports are too buggy and unstable to make it worth your time.. you will just uninstall it.
I think it is matter of opinion. Some will highlight the builds being buggy and others on it being faster.
vicky_ag said:
I think it is matter of opinion. Some will highlight the builds being buggy and others on it being faster.
Click to expand...
Click to collapse
+1 to that! ive been running cm7 since nightly #4 and there up past #65 so ive been on it awhile. Havent gone back since and im loving it! I like the Built in theme chooser any day i feel like changing my mood just change theme and built in theme chooser does the rest, 10 sec process. Its way so much faster then Froyo thats like comparing apples to oranges of course its faster it should be if it wasnt google wouldnt be doing a very good job! I could go on with all the cool features and specs but theres no use everyone has there own opinion. Heres the true fact of the matter it says in CM7 op cm7 isnt for the noob rom flasher so it may be buggy on ur phone due a bad flash or not wiping data or wiping dalvik. But with cm7 now having gps its as stable as its ever gonna get. Plus make sure ur reading the instructions carefully!!!
Heres what atinm from cm7 has said about vibrant running cm7 and this is so very true!!
All releases are planned to be free of all bugs. Reality forces us to accept what we can do and our hands are tied on things that we don't have code for, nor documentation for and so no, it will not be free of all bugs/limitations. If the code is stable, if the release is usable as a daily driver for most people, it will get the "stable" designation. We will continue to fix bugs that we can fix.
so its wht it is
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.
Currently running pershoots cm9 ics 03.02.2012 version. There have been plenty of nightlies posted since but is there much to gain? I also see Lang versions but still don't know what that means.
This runs better than anything I've used before,but its the only ics rom I've tried.
There's Romans one which is stable and constantly updated before a fortnight, might want to check it out, his thread has the milestone 4, which is the currently stable version
Sent from my GT - I9003 in the bathroom
Any notable improvements? Netflix and pulse run laggy and the browser needs to be open and closed or stops working at times on pershoots. Those are my main complaints.
Well ICS has been built to support the user's needs, only camera doesn't work since Samsung hasn't given us the driver's for those yet, but everything else has been tailored to performance.
Netflix still lags only because of horribly failed ARM mobile flash port which drains more battery and isn't that optimized for Tegra2 devices. It's a common thing on most, don't worry about it, I assume HTML5 would rectify this.
I'm sorry but what is Pulse? These apps are only for the land of milk and honey
Misledz said:
Well ICS has been built to support the user's needs, only camera doesn't work since Samsung hasn't given us the driver's for those yet, but everything else has been tailored to performance.
Netflix still lags only because of horribly failed ARM mobile flash port which drains more battery and isn't that optimized for Tegra2 devices. It's a common thing on most, don't worry about it, I assume HTML5 would rectify this.
I'm sorry but what is Pulse? These apps are only for the land of milk and honey
Click to expand...
Click to collapse
Pulse is a fairly graphic intensive news reader: https://play.google.com/store/apps/details?id=com.alphonso.pulse&hl=en
The time warner cable app is also very laggy.
It's not that theyre unusable, but when in the hell are apps going to run as smooth on Android as they do on an ipad? I like everything about Android platform over ios, but it never runs apps as well. Use flipboard on an ipad and every app on the tab seems choppy and clumsy. Pulse is an excellent reader, and fine replacement, but I just want a smooth responsive scrolling experience.
Thing is android and IOS packages are built differently, where as apple sdk package already has everything needed to make a stable generic app for all IOS devices, the android version has to balance itself in terms of graphics and performance, what's built on an S2 and tested on one will differ on the 10.1, It's sad 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
Hi all,
I'm sort of new here, so I hope I'm abiding by all the rules... I believe I am :angel:
I've only recently rooted my Samsung Galaxy S3 (international) and have been using Omega for a while now and I'm running 33.3 atm. So not the one based on CM10, but the one based on the stock rom.
I've now reached a point where I'm feeling that I've been there and done that. So I'd like to try a new fresh solution. I've been looking at CM10 and ParanoidAndroid, as these seem to have the largest user base, based on the number of posts here in XDA Developers forums in their threads. However I'm unsure if either of these are right for me.
I believe I read about CM10 having added a feature where you inside the OS could search for and download new versions directly on the phone, like you can with new software on iOS. Is this possible on both CM10 and ParanoidAndroid?
I'm looking for something that is both rock stable and yet constantly adds new gizmos and features, so I have something to play with. I'd like for it to be very easy for me to upgrade to newer versions. On Omega you downloaded via torrents, transferred to the SD card and then just rebooted into CWM and installed from zip. It automatically wiped cache, dalvik and such. So you didn't really have to do much yourself. But if CM10 could do it evern better and also download directly to the Phone, then that's a big plus for me.
I'm also a bit curious about why people change so much stuff on their phones. I often hear people talk about different kernels. From what I understand the kernel is sort of the drivers that bridges the gap between the OS and the hardware. Why is this so important? On Omega the default seemed to work perfectly... so what do you actually get by swapping? if the answer is 0.5% extra batterylife, then that's just not enough for me.
Casper[DK] said:
rock stable.
Click to expand...
Click to collapse
CM10 builds are nightlies, and PA is based off of CM10. So if you want rock stable - go stock
Casper[DK] said:
Hi all,
I'm sort of new here, so I hope I'm abiding by all the rules... I believe I am :angel:
I'm looking for something that is both rock stable and yet constantly adds new gizmos and features, so I have something to play with. I'd like for it to be very easy for me to upgrade to newer versions.
I'm also a bit curious about why people change so much stuff on their phones. I often hear people talk about different kernels. From what I understand the kernel is sort of the drivers that bridges the gap between the OS and the hardware. Why is this so important? .
Click to expand...
Click to collapse
Well first of all, kernel is not only your "drivers". It manages your governors, your I/O schedulers, CPU freq etc. That means when you are flashing a new kernel you are either looking for some improvements in responsiveness of the device, deep-sleep state improvements, WiFi patches (muticast f.e.), modules (like mali gpu), ko's (lets say for xbox controller or openvpn support), better RAM management OR you simply wanna sound smart to your friends :cyclops:
There are couple of articles you should take a look by droidphile, first one is Kernel Stuff and the second one is Governors, Modules, etc
Regarding the ROM, it pretty much depends on what you would like to do with it. If you wanna have working radio, call recording, "smart stay" and other things which are specific to TW based ROM's than you should stick with Samsung TW based ones.
CM is awesome! Very clean and nice experience. Couple of glitches here and there but no deal breaker.
PA is my daily driver. I'm very happy with it and I can't recommend enough. Highly customizable, tons of options, custom led lights, different DPI settings for each app, different layouts, on screen nav bar so on and so forth.
Although PA is based off of CM they are now migrating to AOSP. The main difference between them is code bloat. CM has own settings and codes to support them, which makes it a little bit slower than AOSP but that doesn't mean its worst.
You should start experimenting and see for yourself. XDA is full of information and although the search function is not working for the moment it will work and you can find all your answers.
bnbasarir said:
Well first of all, kernel is not only your "drivers". It manages your governors, your I/O schedulers, CPU freq etc. That means when you are flashing a new kernel you are either looking for some improvements in responsiveness of the device, deep-sleep state improvements, WiFi patches (muticast f.e.), modules (like mali gpu), ko's (lets say for xbox controller or openvpn support), better RAM management OR you simply wanna sound smart to your friends :cyclops:
There are couple of articles you should take a look by droidphile, first one is Kernel Stuff and the second one is Governors, Modules, etc
Regarding the ROM, it pretty much depends on what you would like to do with it. If you wanna have working radio, call recording, "smart stay" and other things which are specific to TW based ROM's than you should stick with Samsung TW based ones.
CM is awesome! Very clean and nice experience. Couple of glitches here and there but no deal breaker.
PA is my daily driver. I'm very happy with it and I can't recommend enough. Highly customizable, tons of options, custom led lights, different DPI settings for each app, different layouts, on screen nav bar so on and so forth.
Although PA is based off of CM they are now migrating to AOSP. The main difference between them is code bloat. CM has own settings and codes to support them, which makes it a little bit slower than AOSP but that doesn't mean its worst.
You should start experimenting and see for yourself. XDA is full of information and although the search function is not working for the moment it will work and you can find all your answers.
Click to expand...
Click to collapse
Thanks a lot for your answer, I greatly appreciate it