What's so great about CynagenMod? - Vibrant Q&A, Help & Troubleshooting

What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App

At the time cyanogen brought a lot of features we now use everyday. Os optimizations apps to sd. Things lf that nature. It is fully opensource and open to anyone to use.
I am fascinated and captivated by the vibrant screen on my epic galaxy s.

Nabeel10 said:
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.

duboi97 said:
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
Click to expand...
Click to collapse
Plus it is a large group of people that work collectively together, they along with a few others are the ones that the leading "cutting edge" devs........ they blazed the trail and now all of us and the current devs benefit from their work.

Yea. Since its built from scratch it is faster than any roms here.
The g1 roms were same speed rooted or not
When cm came it was fast! And then a rom based on cm called super d was even faster and then a european rom was fastest!
So what I'm trying to say is, CM is and will be faster than the ROMs built here overclocked or not because the ROMs found here are based on the Official Froyo made by Samsung not a Vanilla Gingerbread rom built from scratch
So I think something built frrom scratch is better than something just modified and themed
Sent from my SGH-T959 using XDA App

It's built from scratch using the AOSP source, which a lot of ROMs are not (many ROMs are merely modified versions of existing stock ROMs).
It has an extensive amount of customization and flexibility beyond any other ROM I've ever used on an Android device.
I don't mind the ROM I'm running on my Vibrant, but I miss CyanogenMod. Since the CM7 release candidate for the MT4G just hit, I think it's time for me to change it up a bit. I'm tired of my short-range wifi (seriously, less than full bars when I'm only six feet away from my 802.11n router?), non-functional GPS and totally wonky compass, anyway.

I think one of its advantages is the sheer size of the community, if you've ever used various Linux distributions the same concept applies. When your user base expands to the point where you've got dozens if not hundred of loyal users posting guides, reporting bugs, requesting features, and answering new user's questions the community really feeds on itself and builds momentum. Cyanogen is largely responsible for a lot of the momentum in the rom community, and I know it's brought more people to the community than almost any other project.

A lot of things.
The cyanogenmod options alone are worth it - VM Heap, swap, JIT, compcache, et cetera. Granted these things are more relevant to lower end devices. Then there's the native ADW launcher integration. I've never been about to replace the stock launcher with ADW and get the same results.
It's really just its use in practice. Everything works, the interface is very instant/responsive (no jagged animations/scrolling, ever), no force closes, lots of mods/hacks for it from the community, which in general is very scrutinous about performance/stability hangups. Battery life twice what you're use to.
They're the only ROM team I've donated to. I flashed hundreds of roms when I had my Magic (one of the hardware-weakest android phones) but CM is what kept it up to par, giving me an extra generation's life out of it.

I personally love all the features built in, like pulldown menu modifications, as well as pretty much customizing every aspect, NO roms like that exist for our Vibrants..

It is Cyan in color, and mod like the british music scene duh!

hmm... I might have to give cm7 a try once they get it working on the vibrant. They are working on it right? If the manufactures were smart, they would give a pre-release phone to those guys before it's available to the public. Of course, the carriers may not like it. I just purchased my vibrant 3 weeks ago (former iphone 4 user). I tried a few darkyy's roms, then toxic, then finally I stuck with trigger. I'm very satisfied with it - mainly b/c everything works nice and smooth.

I see I'm a bit late but yes, Trigger is awesome. I tried flashing others and I always come back after 2days tops.... For some reason, Trigger runs so much smoother than the other ROMs on my phone... And I have tried 2.2.1(Honestly I dont get the difference) and I am not a fan of the 2.3.3 because most say the GPS doesn't work and I use my GPS at work, yes through my phone(I'm cheap). Plus that is one of my reasons for buying a "smart phone" It has everything at your finger tips, or supposed to at least right. Hope your having fun.,..... BTW, CM is freaking awesome on every device I have seen it on...... I'm actually curious to know why it's not on the Vibrant as an official build but eh..... It will come when it's ready I suppose

Related

(Q) cm7.. why?

It seems that cyanogenmod is very popular with other phone users, and everyone seems to want it for the vibrant as well... but can i just ask what differs cyanogenmod from say trigger bionix or eugebes rom?
It seems like there is a crapton more work involved and that you could possibly brick your phone.
Sent from my SGH-T959 using XDA Premium App
It's a pure aosp rom, that's why people go crazy about it. I ran cm on my g1 back in the day and it made it a completely different phone.
Sent from my GT-I9000 using XDA Premium App
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
How you comparing trigger with cm7... think man, gb 2.3.3 and aosp... builded from scratch... code by code... it dont have a bit of tw. Well it dont even contain 2 frameworks like tw or any other...
Sent From My CM7 HTC Glacier Running @1.401 GHz
**delete **
Sent from my GT-I9000 using XDA Premium App
Because it's a pure AOSP ROM. Build from scratch (well, a base).
Try it if you really want to know, except for GPS issues and not so good battery life, it is AMAZING.
cashyftw said:
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
Click to expand...
Click to collapse
Lol i fount it funny, never knew about that kind of searchs, haha nice...
Sent From My CM7 HTC Glacier Running @1.401 GHz
CM is the granddaddy of AOSP ROMs. Cyanogen and his team are devs cutting actual code, writing their own device drivers and system apps. The entire CM ROM is compiled from customized source code.
Contrast this with the approach taken by ROM chefs who largely assemble their ROMs out of precompiled components borrowed from different releases of the vendor's ROM binary plus some configuration hacking where the odd component has been successfully decompiled.
That's not to belittle the achievements of the top chefs in any way - it's frankly astonishing that this school is viable at all, they seem to be operating mostly blind so it's more art than engineering in some respects.
But both approaches have their strengths. OEMs like HTC with access to detailed specs for their own hardware and low-level API's can produce better drivers and better apps that work closely rough drivers (like the camera app), but at the other extreme, AOSP code can sometimes include features the vendor left out or even implement a completely rethought and altogether superior design.
It's unfortunate that the closed source strategy of vendors with their signed modules often denies us the opportunity to combine the best of both. I'm particularly thinking of how juice defender can only control the toggling between 2G/3G radio on AOSP ROMs because the radio driver will only respond to code signed with the same key as itself. Aint signed code wonderful, eh?
Sent from my Desire HD using Tapatalk
Another reason is quick updates.
CM has updates before any major manufacturer and they're updating phones that manufacturers abandoned a long time ago.
I ran CM on my G1 and I've been seriously considering making the jump with my Vibrant any day now.
for me, it's long term support. once cm adds a phone, then that phone is typically going to be able to easily be upgraded to the newest android os and typically very shortly after it comes out. like many others, i had a g1 and because i cm i was able to get more life out of the device by ocing it and updating it 2.1 and 2.2.
go install cm7 and you will see what's good about it. the only major problem with it right now is no gps. after running cm7 i went back to biwinning and bionix, but that was short lived, i'm back on cm7 because having 2.3.3 > gps, for me.
Yep, CM7 4/21 nightly + cm7 Kang kernel, overclocked to 1.2 GHz + ondemand Governor equals the fastest I have gotten my Vibrant.
I have a Nexus S, right now it's stock 2.3.4 but when Cyanogenmod gets updated to 2.3.4 then for sure I will flash it. Why? When I already have stock? Well have you seen the the things you can do on that thing? You can add a music widget built right into the lockscreen, change themes with ease, change what the search key does, change the lock screen style, and the browser is improved ( incognito mode for one) you also get some fixes that Google almost never fixes, plus stock 2.3.3-2.3.4 disables Facebook sync with your contacts, however Cyanogenmod removes this thing that Google put... basically you can customize the thing like crazy. Plus it still remains stock, but the entire experience can change. I made my Nexus S look like Sense, changed how the notification bar and other aspects of the UI looked, changed the launcher to a themed launcher pro and changed the lockscreen to lense style, boom Sense style completely. Also if your device isn't stock you can install it and you make it stock, a problem with Sense is that a lot of the time the software disables things that some apps might need ( making things like wiimotes not work on it) but if you have Cyanogenmod, it eliminates that.
Sent from my Xoom
How is the battery life when using cm7 on our vibrant?
Too bad it doesnt have gps i actually use it so ill have to wait until gps works on it
Sent from my SGH-T959 using XDA Premium App

Benefits of a Cyanogen 7 or 9 ROM over these already highly tuned custom roms?

Hi,
Could someone please enlighten me to the benefits of a Cyanogen mod over all of these custom ROMS that include a version of Sense (I think that they all do).
I'm referring to Energy, Revolution ROMS.
Would a Cyanogen mod be faster, have more battery life, and be more stable since it is an AOSP (android open source project) based and doesn't have the Sense overhead? Does it have any other secret sauce?
Or are the custom ROMS already pretty much equal to what Cyanogen puts out, with the only difference being Sense?
Thanks!
p.s. Coming from the iphone world, it is interesting that there are no custom ROMs for iOS. There does not appear to be a need since the core OS is pretty stable. While I liked that, I do miss the ability to tweak my phone at the ROM level. In all honesty though, the fact that for the vast majority of Android phones, a custom ROM is a flat out necessity in order to achieve stability and battery life, would probably not fly with most customers. But I'm willing to go through the putting a custom ROM on my phone since it's more like an adventure to me than a hassle.
ICS is ran over AOSP which is the fastest because they include NO bloatware at all.
Sense includes tons of bloatware and Sense just slows down the system.
CyanogenMod is ran over AOSP for the fastest experienced.
Please post your questions in the Q&A section mate, to keep the Development section nice and tidy.
Cheers!
In general, the Cyanogen team added many features to the Android AOSP, in many ways out 'featuring' the cell providers teams. Things like gesture lock are great add-ons that provided functionality with very little in the way of bloat. Additionally, they could tweak things in AOSP that the vendors might not want to touch for fear of breaking thousands upon thousands of users. CM is a boutique ROM.
Apple, to your point, offers no custom ROM's, and this is by design. The whole point of the Apple ecosystem ( and it's success in large part), is due to the fact that they keep it very locked down. This ensures a consistent and predictable environment in which to work, and support costs are kept to a minimum.
Some of us (myself included) don't really enjoy the Sense's of the world, and although they are not all together horrible, I just don't favor some fancy graphics over app functionality. I just generally like the simple clean interfaces. I have to hand it to the Sense team though... there are some pretty nice base apps. BUT, I prefer 3rd party tools most times, and like supporting the little developer if he keeps his project going.
Finally, the computer hacker in me just loves tweaks, optimizations, and tinkering with things. If I can overclock a chip, you can be damn sure I am going to do it!

[Q] Difference between cm9 mods

What is the difference between Neo's Rage CM rom and Project Rachel/CounterShrike? I know that CounterShrike has the bottom status bar mod, but in terms of battery life/speed/performance, what's the difference and which one is better?
If u want to know the differences read all of the ops. Everything else is a matter of opinion. However I use neos rage.
Sent from my Rezound using xda app-developers app
CounterShrike is all about features and options. I'm trying to put as many mods in as I can in the ROM without affecting stability, and I'm trying to bring in some bugfixes along the way. It's otherwise fairly stock...I'm not really taking anything out, and I'm also not doing any tweaks outside of those that come along in the code commits I put in. I leave the tweaks up to end user preference. Neo, on the other hand, is all about minimalism and tweaks. He's bringing some features in, but not nearly as many as me, but he's also heavily debloating the ROM, and tweaking things to try to maximize performance and battery life.
I like Neo and think he does great work. In fact, it's because of him and his mentoring that I'm at the point that I can do what I'm doing with CounterShrike. My personal opinion is that you can't go wrong with either one, but they are two fundamentally different ROM philosophies, and think having them both benefits the community. It really just comes down to what you are looking for.
Spend at least three days running each one, and make sure you've explored every option in the menu before changing to the other one.
Sent from my ADR6425LVW using xda premium
One small difference is that the Counterstrike camera has working live face detection, whereas the one on RAGE currently does not.
I've been researching if the fabled MIUI camera UI can be ported, but in the meantime, Camera JB + from the Play Store is a small but good upgrade over the stock AOSP camera.
Much respect to the both Neo and Shrike for all their hard work.
Sent from my Rezound using Tapatalk 2
Project rachel was my rom that i gave to shrike. So pretty much the same thing. Although I understand he has plans to go further with it

Snappyness

So I've seen this word thrown around a lot since switching to Android from my old iPhail 3G (yes, I actually lived with that horrible laggy device for ~4 years) and in comparisons between Android and iOS (which I'm not trying to get into here). I've also read lots of people saying Jelly Bean was supposed to be 'snappier' compared to ICS. I wasn't sure if they were referring to lag as in fps or a delay in reaction. My Note II is currently stock 4.1.1, but I'm definitely noticing some delay in games, such as Air Hockey, between moving my finger on the screen and the paddle moving in the game, for example. It's quite noticeable in apps like Maps too. I had the Galaxy S III for a short time before I decided I wanted the bigger (and better specs) Note II, but not long enough to make any comparisons. My question is, is there a way to increase the snappyness without doing anything too dramatic, such as flashing a different ROM, etc. Or will a ROM like beanstown106's Jelly Beans help? Or is this a problem that is inherently part of Android operating system/devices? Thanks in advance.
marcmy said:
will a ROM like beanstown106's Jelly Beans help? .
Click to expand...
Click to collapse
I can tell you that flashing beans ROM made absolutely no speed difference whatever over my previous debloated/rooted stock ROM (and I didn't really expect it to)
One thing is, it is noticeably laggy when running the inferno galaxy live wallpaper, but pretty much instant response with regular WP.
The "snappieness" in individual apps is really down to the app itself combined with phone specs.
Poorly coded apps may have lag.
High end apps may push the hardware harder and cause lag.
I would bet its mostly the former when it comes to the Note 2.
Samsung also put touchwiz on these phones, which does affect overall performance to some degree. If we get the ability to remove much of it in favor of AOSP versions, then it should perform a little better overall.
The differences between iPhones and Android... is that Apple focuses on user interaction over all other things. So this means they will sacrifice performance in other areas to ensure that user interactions are kept smooth, or at least keep the appearance of smoothness. For example, iOS will stop loading web pages when you start to scroll the screen, so the CPU can focus on smooth scrolling. This means that the page will never finish loading if you keep scrolling around on the screen. Android does not do this or these kind of things. The new "project butter" implemented in JB is designed to help smooth out the interface and user interactions, without sacrificing performance in other areas. Its not perfect though, and it requires good specs and more power than the iOS way of "one thing at a time".
Great response ty very much. I guess next question is will we be able to get those AOSP versions later on or are we SOL in that department?
Sent from my SCH-I605 using xda app-developers app
Depends on which version you have.
I am on Verizon, so my device is locked down, other versions are not.
This device is also unique in the fact it has a Wacom stylus and functionality, so that must be considered.
Often times, you can swap things out without too much issue. AOSP lockscreen instead of touchwiz lockscreen... AOSP launcher instead of touchwiz launcher... without too much trouble. Problem is, underneath the ROM is still touchwiz... or at least that is how it worked on HTC Sense phones. (this is my first touchwiz device) HTC do a lot of work to the underlying framework which meant wholesale replacement of everything wasn't possible, so it depends on how much Samsung changed Android to put touchwiz on it.
Basically they "DE-Touchwiz" the phone and do some background tweaks for added performance, plus they "de-bloat the ROM. (they remove all the unnecessary crap that the carriers and Samsung put in, that served them some benefit, but not benefit the users) The advantage of this method is that you can keep much of the functionality of the stylus.
Another method is to use a ROM based on stock, but tweaked and de-bloated. This usually retains all the functionality of the device as it came out of the box... but the performance is usually only a little better than stock, and less than one where the AOSP stuff has been put in. This method does allow you to keep most of the stylus functionality.
As far as straight up custom ROMs based on AOSP...
They usually offer the best performance for a given device, having no extra crap, and being tweaked for performance... But you will lose most if not all the stylus functionality. Some ROMs may have limited stylus functionality, but they have to put that in themselves, meaning more work on their part.
As far as performance gains... I can only speak of HTC Sense devices with sureness. Where pure AOSP usually had significant improvements to performance/battery life. (mostly due to how extensive Sense is, touchwiz may be better in this regaurd) "De-sensed" ROMs where they removed all of the Sense stuff they could and replaced with AOSP equivalents, had good performance increases. "De-bloated" and tweaked but otherwise stock ROMs had some improvement.
But as was said, the stylus functionality is something that must be considered when looking at ROMs
After using AOSP ROMs quite extensively in both of my two Galaxy 3s, I have no desire whatever to run those type ROMs in my Note 2 (and lose things like pen functionality).
I could never see any performance difference whatever (except maybe in useless benchmarks) between a completely debloated TW ROM with all the features working perfectly and a buggy AOSP ROM in my G3s (and I tried every G3 ROM available at least twice).
Posters where constantly claiming this ROM is PERFECT when discussing any AOSP ROM but two posts later someone else would post "can anybody get NFL Mobile to work??" The next post would say "that has never worked in AOSP but I never use it anyway so who cares........"
Good call. I'd rather keep most functionality
Sent from my SCH-I605 using xda app-developers app
You could go into a store and try some of those games out on a DNA. Hopefully some are free so you don't have to put your google account in the play store and then clear the data. The DNA's gpu is much faster. It sounds like it's the app coding though. I don't have any input lag with on screen buttons playing GTA or N64oid, and emulators are pretty heavy on the processor.

[Q] Custom rom performances?

With my old tablet the custom roms always meant a performance increase too, but:
I've tried pretty much well every single custom rom available for this tablet by now and i still havent managed to find one that actually increases the performance of the tablet. When im running the stock firmware i get about 7500-7600 on quadrant and my browser is really responsive and stuff. There's not been a single custon rom out there that has even performed better then 5600 on quadrant. Is it just me, or are the custom roms not hat good performance wise?
EDIT: By better performance i mean how snappy the tablet feels, using benchmarks as a secondary frame of reference.
Not sure if quadrant is doing a good job. I also am getting same results as you with 7xxx for stock and 5xxx for all CM based ones. Although the CM roms feel smoother here.
Sent from my SGP311 using XDA Premium HD app
I abstained the vote cause the question does not bear a black and white / yes or no answer anymore these days.
In my humble opinion, and I picked up the smartphone / PDA / mobile device modding bug back about when this site catered to the the original HTC XDA almost exclusively, and Steve Jobs was merely having wet dreams about his iPhone (*1)... nodded RIMs have gotten to a state where they are overvalued. Saying a custom ROM is always way ahead of stock is like saying "one device with a fixed featureless fits everyone perfectly".
Custom ROMs had their deserved heyday when the industry loaded up near every carrier distributed smartphone with scrappy bloatware that made you weep. Depending on the mobile OS at any given time it was nigh impossible to get rid of that stuff, unless you flashed the whole shebang. From there on the custom ROM scene kinda exploded along with the market distribution of smartphones and later on tablets, certainly owed to the introduction of Android over older generation closed source systems, which enabled much more in-depth possibilities of adding novel features, fixing stuff that was basically broken out of the box and integrating all of this nicely.
(For a frame of reference: I tossed my PalmPilot and Nokia phone when the HTC Wallaby (Telekom MDA or so)hit the shelves... Early adopter by nature and I thought combining cellphones and PDAs, bother which I used avidly was the most revolutionary idea since the combustion engine. This was generation Windows Pocket PC, basically a PDA with cellphone feature thrown in as an afterthought (the antenna actually doubles a stylus compartment). Phone integration was a PITA on good days. On bad, long work days it might just happen that your moody battery would jump from 35% to flat out dead within a mere six minute phone call. Yet, no biggie right? Well, it was, the devices had no non volatile storage. Dead battery means go home, pray your last phone backup is recent enough and restore the entire thing. I spent a lot of time fixing this device (windows style - shoehorning in binary OS components from newer PocketPC versions and prodding the registry on the phone (!)...) to a point where it was almost usable as PDA only device, supplementing telephonly with a Nokia.
A while later better devices came out, PocketPc was scrapped for Windows Mobile and in high hopes I got a HTC Charmer. This looked like a more solid platform and indeed proper custom ROMa emerged, adding real functionality and allowing to get rid of carrier branded crap, later even RIMs emerged with Windows Mobile version updates never intended for that phone, some even taking the recent cutting edge HTC front-end, the first incarnation of Sense (I think it was called vanilla). I figured the really bad conceptual problems were fixed and merrily went along. But, as god hates my guts, I drained the battery accidentally, only to find that the phone would still go dead, deaf, dumb and wiped despite a good three or four years of technological progress. I was so confident that I neglected backups with that model and basically lost the majority of my stuff again. The Nokia dumbphone was back in the game, the HTC left a dent in the wall that required plaster and a patch of new wallpaper.
TL;DR: The first gen smartphones (PDA with cell module afterthought were such flawed concepts, badly integrated, that keeping recent backups and maintaining it operational took quite an effort on user side, on that sort of negated the higher productivity of using one altogether. But bear with me now, I am still circling around the point or two I want t. Make.
Because a few months after I abandoned smartphones for good (or so I thought) Apple coughed up their iPhone prototype and a few months later pumped it to market. I was amazed (not because of the technological feat, they were more or less throwing R&D money bricks at existing tech and concepts, however they exactly figured out what went wrong in the early generations, fixed that stuff, added fingerdriven multi-touch in favor of stylus driven displays and, this is the real kicker, in a time and age when the cool cell to have was a Nokia 8 Series or a decent, very small flipphone or clamshell they managed to brainwash their customers into what PDA and smartphone adopters at that time already knew - it's totally worth to dump the train of ever smaller telephony only cells for a much larger, more fragile device because of all the freedom and power those things offer you.
I kept my guard and obviously went for Android devices once I got back on the horse. HTC Desire, a backup Wildfire, Desire HD, Sensation, One S and a few tablets along the way. Now, here is the kicker. The Desire ran much better with a custom. The Wildfire could only be updated to a recent Android version with a custom ROM due to HTCs sometimes appalling quick update discontinuation. The Desire HD ran a basically stock custom ROM! But with lots of lovely icon eyecandy, so I stuck with that too. The Sensation benchmarked equally (give or take 5%) but the ROM added novel features, properly implemented, which I decided to stick with. But frankly, it was because I could. I would not have recommended a newbie to Android flashing to take the plunge. My current HTC One S has a recovery downloader and is rooted cause some essential apps I can't live without need it. Full custom ROM switch. I see no point. Android has come a long way. If today I have bloatware I can go to App Manager and disable them. Icon gone, runtime resource hogging gone. Many features that were the selling points for a custom ROM a while back are now natively incorporated.
This is just how I feel about my Sony SGP311 now. It runs 4.2.2 rooted, no recovery yet. This is planned, maybe at some point a stable, close to stock custom kernel to allow some overclocking on a per app basis for XBMC. But other than that it just Danny works. The Sony skin put over stock Androi. Is not that bad, and more to the point it never gave me the impression of hogging the system. Turn off what is useless to you, Office suite, walkway, etc and be on your merry way. It just comes down to what you do with the device, but as a custom ROM junkie who has just gotten off the habit, for me it makes no sense anymore.
Now, if you made it all the way here, I ran two benchmarks on my 4.2.2 root but stock. Maybe they aid you in your decision.
EDIT: the attachments are garbage. Here are proper links:
http://i.imgur.com/vMFEX1p.png
http://i.imgur.com/IEPVvMS.png
http://i.imgur.com/mB5MKSH.png
Also, none of the above is supposed to rain on the developers parade or something. I admire your skills and dedication over all those years, and there isn't a single custom ROM that went onto my devices withour a PayPal "crate of beer" donation ever. However, the fiddling, time spent reading up on custom ROM choice, issues and unlocking process etc is just not in relation for me anymore. Those thoughts are yours to reject, spindle, mutilate, adopt, oppose or plainly ignore... Just speaking for myself here.
Thanks for this! I was also trying to decide if I should be flashing a custom rom on my XTZ. I am itching to flash but couldn't come up with any strong reason to do so, probably for battery life and stock look?
Will be interesting to hear from another person who is a strong believer of flashing custom rom on XTZ.
Sent from my GT-N7105 using Tapatalk
i got slightly better score using a custom rom. Plus i get themes, expanded desktop and pie control which is a must for this tablet. I hope more xda developers develop for this tablet. Will reward with donations
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
4.3 too bugy for me
im using 4.2.2 cm rom FXP242-cm-10.1-20131021-UNOFFICIAL-pollux_windy.zip
i already sent team a donation hope to keep em motivated
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
Sorry, the post was incomplete. Changed it.
r1ntse said:
Sorry, the post was incomplete. Changed it.
Click to expand...
Click to collapse
I prefer 4.2 ATM. I get close to 30 Mbps download speed on this ROM where on 4.3 roms only 2mbps download? Also video cam recording, screen is squashed on 4.3. Other than that they run great but I personally cant feel a performqnce boost from 4.3 to 4.2. I also installed crossbreader and Supercharger V6 script which addresses screen redraw lags, so if there is a slower issue with 4.2 i would have addressed it with these two mods and may not be able to tell.

Categories

Resources