OK I spent eight hours yesterday figuring out how to root my phone.... Success... I was finally able to figure it out.. Thanks for all the tutorials and posts that helped me do it...
I would love some direction in how to find some cool and neat and SAFE AND STABLE Roms to flash.. Is there a site with roms to choose from?? Any help or suggestions is appreciated....
Thank you again everybody
Just look in the android development section in the international forums. Viper rom is really nice, so is Arhd.
Sent from my HTC One
I second ARHD. It depends whether you like sense and want to keep it without all the bloatware, or try something more pure android. I know Google edition ROM is out now, but I like sense too much to try it. Heres some links to arhd and ge.
http://forum.xda-developers.com/showthread.php?t=2183023
http://forum.xda-developers.com/showthread.php?t=2356654
Ok great thanks for the help.... I just got home from work and can't wait to spend the rest of the day flashing different roms.. Lol. What fun! This is a thousand times better than jail breaking... I was never able to flash different firm wares on an iPhone... This is a thousand times better
Pro tip: almost all roms on here are stable and safe unless they have alpha or beta in the title
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
Pro tip: almost all roms on here are stable and safe unless they have alpha or beta in the title
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the "pro tip." I love this place.. I'm running a GPE rom and having fun... I think I want to flash something I can theme with a lot of choices... I'll look around and see if I can find a rom around here that people are theming... Thanks again
OJsakila said:
Thank you for the "pro tip." I love this place.. I'm running a GPE rom and having fun... I think I want to flash something I can theme with a lot of choices... I'll look around and see if I can find a rom around here that people are theming... Thanks again
Click to expand...
Click to collapse
For maximum themeing capabilities you can go with any of the AOSP (Android Open Source Project) based roms like Cyanogenmod (CM) AOKP, Vanilla rootbox, Slimbean, etc. They all support custom theming with hundreds uf not thousands of downloadable comaptible theme files in the Google Play store.
They are much more customizable than the GPe roms as well. But be warned, what you gain in customizability and cool factor you may tradeoff in optimal function of the phone features itself, namely camera, sound, call audio quality and BT call/streaming audio reliability.
The reason is because GPe and vanilla android 4.2.2 may look identical on the surface, but are different underneath. The GPe of the One runs on a stock Sense OS heavily modified to look and work like vanilla Android IU, but the underlying OS framework works best with the HTC hardware. While AOSP roms have hardware compatibility issues. You'll see this is a regular issue on those threads. I was using CM until the GPe roms were released. I loved the user options on CM and AOKP but was frustrated by terrible call quality and unstable BT connections. I switched to one of the GPe based roms and I gave up some cool features, but my phone works too well as a phone now to switch back.
Most people using GPe based roms are hoping the developers will adopt and incorporate the cool custom ideas from CM based roms like UI options, themes, adjustable control tile toggles, navigation bar mods, etc.
Sent from my Nexus 7 using Tapatalk 2
kayone73 said:
For maximum themeing capabilities you can go with any of the AOSP (Android Open Source Project) based roms like Cyanogenmod (CM) AOKP, Vanilla rootbox, Slimbean, etc. They all support custom theming with hundreds uf not thousands of downloadable comaptible theme files in the Google Play store.
They are much more customizable than the GPe roms as well. But be warned, what you gain in customizability and cool factor you may tradeoff in optimal function of the phone features itself, namely camera, sound, call audio quality and BT call/streaming audio reliability.
The reason is because GPe and vanilla android 4.2.2 may look identical on the surface, but are different underneath. The GPe of the One runs on a stock Sense OS heavily modified to look and work like vanilla Android IU, but the underlying OS framework works best with the HTC hardware. While AOSP roms have hardware compatibility issues. You'll see this is a regular issue on those threads. I was using CM until the GPe roms were released. I loved the user options on CM and AOKP but was frustrated by terrible call quality and unstable BT connections. I switched to one of the GPe based roms and I gave up some cool features, but my phone works too well as a phone now to switch back.
Most people using GPe based roms are hoping the developers will adopt and incorporate the cool custom ideas from CM based roms like UI options, themes, adjustable control tile toggles, navigation bar mods, etc.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The Sense version isn't heavily modified to look like Vanilla, its heavily modified to look like Sense. All carriers start with vanilla.
As for the features--because there's a Google Play Edition (GPE). The GPE devices run vanilla android--what we call AOSP, after the Android Open Source Project...which is the project Google created in order to "Open Source" Android, make it available to everyone, and provide for a "Google Experience".
The Google Experience" comes stock on the Google Play Edition devices, and guarantees that the device comes the way Android is/was intended to be, and is designed far better in terms of functionality and usability than the Firmware(s) created by Samsung, HTC, and other manufacturers, which add additional software to run on top of the Google Experience software in order to differentiate themselves from one another, and be able to say that their phones are better. In reality their software might look better and have a few extra features, but it's slower, can take years to update, and in the end, is often more restrictive.
Because these devices require Google certification, all features are required to be in working order. And because Android is so modular, you're guaranteed to have all the drivers, libraries, etc. you need to use all the base hardware available on the device. This means that beats audio, Wifi , Bluetooth, GPS, 3d, Sound, etc. Will all work. The only thing that won't work is the IR blaster on top of the device (for turning your device into a universal remote control to change channels with on your TV, blue ray player, etc. ), and since updates come from the manufacturer and not Google, it's believed that an update may enable this in the future.
By the way, Engadget did a side by side during their review, and stated that picture quality wasn't any better on the Sense version---which means that you'll get great photos on both devices.
That's the reality. Some have made some wild speculations, and have come to some wild conclusions (entirely subjective and disproved), but this all comes from extremely authoritative reviewers...people who are given devices and whos career depends on spending a ton of time analysing these devices, and getting it right.
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
The Sense version isn't heavily modified to look like Vanilla, its heavily modified to look like Sense. All carriers start with vanilla.
As for the features--because there's a Google Play Edition (GPE). The GPE devices run vanilla android--what we call AOSP, after the Android Open Source Project...which is the project Google created in order to "Open Source" Android, make it available to everyone, and provide for a "Google Experience".
Click to expand...
Click to collapse
Thanks but you're misinterpreting what I was saying.
Sent from my Nexus 7 using Tapatalk 2
CleanROM 3.0 <stock look and feel with added performance and perks
Just so I understand this correctly, if we need to get S-OFF to flash ROMs such as Viper due to it being 1.28, correct?
Sent from my HTC One using Tapatalk 2
nope s-off is not needed. If you still can, obtain the unlock key from HTCDEV.com and use that to unlock your bootloader (this will wipe your phone completely), install a custom recovery such as CWM or TWRP, then install either superuser or supersu for the root
Then flash away
1. http://www.youtube.com/watch?v=QU7vi388dMk
2. http://www.youtube.com/watch?v=rRkAHw_GmIs
Thank you so much! So what exactly does S-OFF allow you to do besides customizing the bootloader?
Sent from my HTC One using Tapatalk 2
tanner4137 said:
Thank you so much! So what exactly does S-OFF allow you to do besides customizing the bootloader?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Restore your phone completely back to pre-rooted stock condition with the stock Sense ruu. Just like when you got it from the store.
Also is required if you want to reflash/update the phone firmware (which will completely wipe out phone data just like unlocking the bootloader).
Sent from my Nexus 7 using Tapatalk 2
kayone73 said:
Restore your phone completely back to pre-rooted stock condition with the stock Sense ruu. Just like when you got it from the store.
Also is required if you want to reflash/update the phone firmware (which will completely wipe out phone data just like unlocking the bootloader).
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
And do we need to update the firmware to install any of these ROMs?
Sent from my HTC One using Tapatalk 2
tanner4137 said:
And do we need to update the firmware to install any of these ROMs?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
NO.
Stop being so fixated on updating your firmware. Read more and ask fewer questions.
Sent from my HTC One
Related
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
Hi. I wa going to start testing the cm nightly but I still think ol' sammy has done some good stuff in their android release so... yeah I would like to keep stuff like "put phone to ear when smsing " and other stuff.
Now to my q. Wasn't there a project somewhere trying to port all apps from different manufacturer's so they could be included in aosp roms? Though it had something to do with cyanogenmod but Im maybe wrong...
Skickat från min GT-I9300 via Tapatalk 2
Not sure about that but they will all rely on frameworks from each specific device so I don't see that project being feasible.
I won't be going to aosp just yet. The unused touchwiz overhead is not so much that I want to lose Samsung features
Sent from my GT-I9300 using Tapatalk 2
A search would have told you no. It is not going to happen. CM only uses open source coded apps and non of the Samsung apps are. So if you want an AOSP based rom you will have to be willing to lose the Samsung apps and features.
Sent from my Inspire 4G using Tapatalk 2
Check out this thread, its a sgs3 pack for the galaxy nexus.
http://forum.xda-developers.com/showthread.php?t=1669190
Tried it, works quite fine, however some strange rendering with touchwiz (think cause its targeted for the nexus, which has on screen navigation buttons)
I think you mean the openDESIGN project which aims to rewrite popular features from scratch to unify great features from different manufacturers in Cyanogenmod.
Sent from my GT-I9300
I think its a bit of a waste to goto CM9 only to put back all the bloatware.. And there ate still issues with CM9 for the s3
I persoanlly have gone for one of the other roms, that is deodexed etc, so that it can be modified to an extent, whilst keeping a lot of its usefulness
It runs a little better than stock, seem to have slightly better battery life, and some custom mods that i want
I am itching to try cm9.. I did install paranoid rom, but i think its a little early yet for someone that needs some things to work right.. Cm7 on the nexus s was good.. When cm9 is that good it will get installed on my phone
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
Hi my name is Rob and I'm a flashaholic I have to admit with every new phone I get I probably flash every custom ROM made for it I'm not much for stock based roms but I got my lg g2 about a month ago and have flashed to try out just about every ROM built for it so far and I can't wait to see more kitkat ROMs
I pretty much like to flash the latest versions of android to just waiting on more kit kat ROMs
Over the past two days I've flashed 6 different ROMs but keep coming back to ose even though it's not that stable it has all the features I'm looking for
What about you
Figured I'd start a thread for fun let's hear your confessions
am afraid its a completely normal condition bought on by a very complicated organism designated lgg2 i'm afraid the prognosis is not good as the disease is very fast and progressive with episodes of high euphoria followed by intervals of extreme anxiousness- we can only hope that the research into this worrying condition will be continued
and that maybe in the distant future there may be a cure.
I myself find I've been able to avoid the flashaholism by knowing how I like my phone
I'm on pa currently awaiting cm to finish fixing the lte issues.
But I my self know I like a build of the latest cm, stripped down, debloated to it's bare minimum, with a good kernel, and a few tweaks
Sent from my LG-G2 using XDA Premium 4 mobile app
I wanna flash g flex Rom but I'm afraid to **** **** up
Sent from my LG-D802 using xda app-developers app
Hello, flashaholic here as well.
Love the g2, Flashed cm, PA rom, slimkat and others. Unfortunately I'm soft-bricked at the moment. Hoping to find a resolution.
However with that being said I love the flexibility and the customization.
Sent from my SCH-R970 using xda app-developers app
I am in the same boat. Always looking to see if my circle or ROMS have updated versions. At this point I cannot go back to stock I think I like the latest 4.4.2 performance. Stock just feels slow to me though it's been a while. Maybe ill check out the Flex..
Using PA Houstonn's 4.4.2, Beanstalk 4.4.2, PacMan 4.3 nightlies, and 4.4.2 SlimKat weeklies.
Good luck with your addiction.
Robshr said:
Hi my name is Rob and I'm a flashaholic I have to admit with every new phone I get I probably flash every custom ROM made for it I'm not much for stock based roms but I got my lg g2 about a month ago and have flashed to try out just about every ROM built for it so far and I can't wait to see more kitkat ROMs
I pretty much like to flash the latest versions of android to just waiting on more kit kat ROMs
What about you
Figured I'd start a thread for fun let's hear your confessions
Click to expand...
Click to collapse
me too, this week i flash my first stock rom, and no good, aosp is way faster, if you think in test more there is carbom rom now!
I've always been a flashaholic. This is the first phone I've been completely satisfied with just root. I couldn't care less about flashing now, and its pretty sweet not having to set my accounts up and restore backups once a day.
Yes I like this subject since it reflects my internal war
I'm gonna copy a reply I wrote due days ago on similar topic to avoid writing the whole essay :
"My friend THIS is my biggest issue currently!
I'm gonna be THOROUGH so BEWARE 
I come from many phones history (see signature) where I always flashed PA or CM especially on touchwiz phones.
However on the G2, I liked stock at first and kept using it for around 2 months.
Then, having ORD decease (  see signature again) I kept my eye on PA and tried it on Christmas vacation. It caused me such a big confusion to the extent where I went between stock and PA like 5 times confused on which is BETTER and which I LIKE most.
Currently I returned 2 days ago to stock but still thinking about PA... 
Yes stock is nice with all features and stability, but I just HATE the nonconformity in design (even when using Xposed heavily to stabilize things and theme others).
-Also PA gave me such a smooth experience (much faster) with a lot more RAM and great simple looks. About RAM I greenified most system and installed apps that hogs RAM and still barely have about 500mb of free RAM while I have around 900mb on AOSP roms without any greenifying.
-Most importantly I had crazy battery life on PA while it's lower on stock even when nearly disabling every feature (except knock on of course).
-The thing that made me return to stock, believe it or not, was mainly camera (I know there's a mod for stock camera on AOSP but it's not that functional) and non-intrusive call notification which is a life saver when playing games. I tried "call heads", "call popout" from playstore but none worked nicely all the time.
Even when Omni gives that feature, I cannot install Halo (via Xhalo xposed module) on this ROM bcz it conflicts heavily with multiwindow feature in their rom which I cannot care less about it.
-I hate stock lockscreen and I love AOSP lockscreen.
-I hate AOSP camera and I like stock camera.
-I love AOSP calendar which options of colouring the events but hate its lack of features. I love stock calendar and its widget and snooze option while I hate its lack of colouring events feature.
-Although stock launcher is great it keeps redrawing (reloading) when quitting apps (heavy ones) which is annoying. AOSP laucher doesn't but lack features.
-Sound quality TILL NOW is better on stock.
-Immersive mode and the ability to always see notification bar even when in heavy games is awesome on AOSP.
-Quick memo is awesome for screenshots and editing on the run and sharing. I still couldn't find an app that does all that, that simple and quick on AOSP.
-Call voice recorder (G2 tweakbox) gives amazing sound and recording quality while call recorders on AOSP suck.
-NO FM radio on AOSP till now (maybe spirit fm will change that eventually).
Although most times I think that I don't need all those "useless" features on stock and that I need the quickness, smoothness of AOSP. I end up thinking that I did not pay 650$ (yes in my country) for a 32GB G2 to dump all those and run AOSP on it. If so, it would have been smarter ( and cheaper) if I kept my nexus 4 (or get a cheaper nexus 5 rather a G2). However I really like the feel and looks of AOSP. However  it's those small/silly/gimmick/nice cool features that stock ROM gives you that make you feel that you own a SMARTphone and not any simple phone. It's the fact that you know that they are THERE when you need them that makes you feel satisfied even when you really rarely use them.
As you can see, it's a REALLY very TOUGH decision which always makes me feel confused. One day I wanna use AOSP, the other stock.
I really hate that phone for that.  On samsung phones I really didn't give a thought about it.
Regards,"
Sent from my LG-D802 using XDA Premium 4 mobile app
damn found another rom
Well found another ROM that looks interesting downloading and flashing now beanstalk 4.4.2
Update: right now I'm torn between beanstalk and slimkat have them both on my phone and I keep switching back and fourth but I think beanstalk is winning so many customizations think in gonna stick with it for awhile
Well found my new ROM beanstalk ROM has just about everything you'll want
App Compatibility?
All those on AOSP ROMs, What about apps. I have read that most of the apps specially games don't work on AOSP on lg g2. You have that problem?