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
Related
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
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
Will it be MIUI, Cyanogenmod or something else? Share your desires and maybe devs will listen
Definately MIUI.
Using it on my EVO 3D atm, and I loooooove it!
Definitely Cognition Rom
Will be happy to see custom ROMs, but as long as they incorporate the awesome samsung features
I am only looking to put ROMs on this phone that are proven stable - and keep the features of the SGSIII intact. I don't want a phone that needs this workaround to get a feature to work.
I hope BootManager PRO works for this phone because I do like to keep several ROMs at hand at once. I really love the ICS blues and I have seen some amazing things evolve from a stock AOSP 4.0.X ROM over at the GNex forums. So we just need to wait and be amazed with the features that will be introduced to the world of Android via this phone's development section
Kernels on the other hand - this is where I am mostly concerned. We know pretty much NOTHING about the way a quad core kernel should be dealt with... These will be the main subject of my attention as we get into early development stages.
We shall see what some of our amazing developers who have proven they make kernels their bi***es can do with a new kernel. I am also interested in the kernel that Samsung has developed for it and how exactly this works in our favor here at XDA.
The main point is while most ROMs can be considered close... Kernels will be quite different and will be everyone's main focus - making our quad core beasts run with optimal battery life!
Checkrom
Skickat från min GT-I9100 via Tapatalk 2
I'd like to see a CM9 hybrid\tablet mode rom with per-app dpi capabilities that comes with a free high class escort.
I will use any "rooted" rom that is stable enough .... so far we don´t know is it possible to change bootloader.
Cyanogenmod of course
Probably..... stock rom, bloatware removed (will keep all the good stuff), custom kernel and custom themes
Sent using TCP/IP
CheckRom 100% the most popular and best ever ROM for the SGSII no other ROM comes close, i still use it and have used nothing else for a long time, SGSII ICS ROM's still nowhere near as good as CheckRom although i hear CheckRom ICS will be landing shortly for the SGSII although ill be selling my phone and getting the Galaxy S3
Slim ICS, as don't see much need for all the extra stuff apart from eye tracking to keep the screen on, S-Voice functionality goes in one ear and out the other, NFC not for me, Social tagging can leave me alone, shame the screen is sub standard to the SGS2.
Still loving my SGS 1 but am due an upgrade so may as well get this, hopefully the GPS is not as ****e as the SGS is. ended up buying an iPhone 3GS just to use with TomTom.
Now if you could give me TomTom on the SGS3 then you'd be talking.
Definitely checkrom with a new kitchen. And if we can get a siyah kernel then its over!!!!!!!!
cm9
miui
slim
aokp
Hi guys,
can you help me understanding the main pros/cons for going with Samsung JB or an AOSP rom on the Galaxy S3?
I've tried searching the forum but without luck, anyone got a thread link where this is covered?
My first Samsung (S3) phone is on its way by mail, and I'm trying to decide which type of rom to choose.
Off course I see the obvious stuff like:
Open vs Closed source
Stock vs Custom UI
But, except for the above; why should I choose an optimized (de-odexed, de-bloated etc. etc.) Samsung JB rom over an AOSP rom?
From what I can understand custom kernels also exists for both rom types, so that wouldn't be an argument right?
I'm not familiar with the current HW support in AOSP rom's for the S3. Generally this has been where roms for my HTC phones have differed in the past. What's the status with the S3, do AOSP support most of the stuff or is there still some way to go?
Please shed some light for me :fingers-crossed:
And please don't compare specific rom's against each others. I'm trying to understand this at higher level, I will off course test several rom's and make up my own mind about what specific rom release is best suited for me.
Samsung roms will have all the things mentioned in the ads such as direct call, smart stay, multi window etc. Aosp won't have these as they are samsungs additions. Samsung will have touchwiz launcher as default, which comes with a lot of samsung only widgets. Aosp will have vanilla launcher (with some extra functions and tweaks).
Sammy roms generally have better camera than aosp. Aosp is considered to have better battery usage although I can't really tell from my experience of using both types.
Deodexed means it's easier to develop themes for, as the external odex files are repackaged into the apks directly. But it will take a while longer when booting, as odex files are meant to speed up this process. As for the actual usage, not much difference.
Debloated means getting rid of bloatware that come with your phone, sich as chaton, google talk etc. There will be quite a lot of apps that you don't use but will be present and wasting your phone resources. Debloating is done by some developers but you can do most of ot yourself as long as you're rooted.
Hope this clears things. But these are all general, as you wished it to be. Some aosp will have different launcher options etc, so will sammy roms. As for what you go with, I'll leave it up to you.
Sent from my GT-I9300 using xda premium
Thanks
xcly said:
Samsung roms will have ...
Click to expand...
Click to collapse
Thanks a lot xcly, this clears up some stuff for me
You say that Sammy roms have better camera, what about the rest of the HW support on AOSP? The rest of the stuff (GPS, Accel, Gyro etc.) works ok?
From what I can gather from your post (and reading around) the choice boils down to two main points for me
HW support
Kernel (stability and performance, ofwhich battery performance is derived)
I don't care much for the 'Samsung features' (direct call, smart stay, multi window etc.) and the launcher can always be customized.
Additionally my previous experience is that the continious devlopment done on AOSP (with nightlies etc.) gives a nice feeling of continous improvement that you miss from manufacturer roms. For manufacturer roms you're relying on manufacturer relase schedules and leaks. But off course, one can argue that there is continous development through hacking, back-porting and kernel improvements for these roms as well..
Ultimately I think Ill just have to try out the most popular roms of both types before I'm able to decide what type I go with as a daily driver.
As for kernels most of then support both aosp and sammy so don't worry about it too much. Gps wifi and the lot work well on both as well.
Samsung didn't release any source code for its processor so aosp roms can never realise the full potential. Never had any trouble using aosp so I wouldn't say there is a huge difference, but I guess some advanced users will miss the hw side of things..
Sent from my GT-I9300 using xda premium
Simple to say
TouchWiz UI and pure Android UI.
Other things basically are very similar
Sent from my GT-I9300 using xda premium
Haha nice. All my words in a single sentence
Sent from my GT-I9300 using xda premium
Here is some personal feeling about them.
As you can see from my signature that I had Nexus S and Galaxy Nexus before, and after I lost my GNex, I tried to buy a Nexus 4, but it kinda like mission impossible as it's serious outta supply, so I was forced to make compromise and go with Galaxy S III, which is very nice phone through some thing I don't like such as hardware button and soft key (because GNex uses virtual button on screen which is completely customizable ).
I have been using AOSP ROM for over a year (well, it's outta options actually as they are Google's sons but Samsung didn't make a ROM for them even they are manufactured by Samsung , and 3 month with Sammy ROM.
Even I got my S3, the first thing I have done is flash AOSP ROM and get my feeling about GNex back, but unfortunately due to some reasons, I couldn't make it become GNex-like and realize it is something fool, so I tried Sammy stock ROM.
My first feeling about it is a little prettier than AOSP ( through there's countless themes for AOSP, I am just talking about default theme ) and some Sammy features are very interesting and attractive. (IMHO, I'd say it is more user-friendly to users ) which is why I decided to stay with it , but after all these times, I didn't actually use these features much except multi windows and slide to dial...
OK, sorry for my non sense words and my bad English just can exactly express what I trying to say...
Sent from my GT-I9300 using xda premium
FoxHound rom is all you need.
crDroid is the most stable Sammy Tom out there with the option of having an AOSP theme & not installing all the bloatware that Samsung Roms are notorious for.
Sent from my GT-I9300 using xda app-developers app
don't turn this thread into a best rom one
A quick follow up question
Just a quick follow up question regarding HW support:
Whats the status for AOSP roms regarding MHL, does it work?
I recently saw a video where a guy paired his phone with a PS3 controller and played games on his HD TV. Would this possible on non-Sammy roms?
Can't help you much on that. Never tried mhl on my s3, aosp or otherwise. You're better off asking/searching in cm thread. If it works on cm, it'd probably work on other aosp roms too.
Sent from my GT-I9300 using xda premium
Pedro80 said:
Just a quick follow up question regarding HW support:
Whats the status for AOSP roms regarding MHL, does it work?
I recently saw a video where a guy paired his phone with a PS3 controller and played games on his HD TV. Would this possible on non-Sammy roms?
Click to expand...
Click to collapse
You need to read the relevant rom threads or logically ask in those threads .
jje
First off I just need to know the difference of the 2 I've flashed roms for several years now but I've really ever had this ? Answered for me we all known touchwiz roms are much bigger than Aosp roms so is the space that's not being used by Aosp roms is it available to the user Like almost 600mb that's not being used by this rom ?
Sent from my SCH-I605 using XDA Premium HD app
Basically it doesnt have the touchwiz skin at all. Its plain android. It also means no s-pen support (its implemented now in the official nightlies however rudementary).
As far as the usuable space, thats a good question. It may not necessarily use it but I dont think its available to the user.
At one point AOSP was about speed and fluidity (albeit still that way) but with the power of this phone its pretty fluid on Touchwiz or AOSP.
For me its always boiled down to whether or not ill be using the pen. I dont use it often, I flash to AOSP and find myself missing features of touchwiz and flashing back. My best suggestion is to go through that exercise and make the decision for yourself.
Yeah beans 17 gives you just the look of Aosp but the Guts of Touchwiz it would be nice to have a Rom that had the mixture of the 2
Sent from my SCH-I605 using XDA Premium HD app
My concern is the camera app. Samsung does an awesome job with the camera software. I've always heard, and also confirmed this during my brief fling with the Galaxy Nexus. How are photos on the N2 using the AOSP software?
Beans is a good mixture and hes an awesome dev to boot. He listens to users and includes features they want to see.
The camera app in AOSP quite frankly is s**t. Its finicky, doesnt like low light conditions and is prone to force closing (no fault to the devs as they have been given zero information to build from, its incredible theyve even gotten it to where it is). I dont use my camera alot so I forgot about that.
littleguevara said:
Basically it doesnt have the touchwiz skin at all. Its plain android. It also means no s-pen support (its implemented now in the official nightlies however rudementary).
As far as the usuable space, thats a good question. It may not necessarily use it but I dont think its available to the user.
At one point AOSP was about speed and fluidity (albeit still that way) but with the power of this phone its pretty fluid on Touchwiz or AOSP.
For me its always boiled down to whether or not ill be using the pen. I dont use it often, I flash to AOSP and find myself missing features of touchwiz and flashing back. My best suggestion is to go through that exercise and make the decision for yourself.
Click to expand...
Click to collapse
While there is very little S-pen support in AOSP roms people can always get GMD Spen Control from the Play Store and that will give them a lot of the S-pen functionality back.
Sent from my SCH-I605 using XDA Premium HD app
AOSP: pure, straight, unmolested raw Google code. What goes on a Nexus.
TW: Samsung's proprietary skin/software that they build on top of stock android. Hence the size difference. Sense is HTC's version.
Littleguevara is spot on about the camera. That's why I stick with TW. And my battery, GPS and overall stability is better. Now if I had a Nexus 4....
Sent from my SCH-I605 using Tapatalk 4 Beta