Database Info

stock android ROM, AOSP rom, CM9

All,
looking for insight regarding currently available ROM's that would offer the closest thing to CM9 (from what I’ve read CM9 is only available on Tegra3 handsets)? Looking for a 'stock android experience' or AOSP based build... your suggestions are much appreciated.
currently unlocked, running 1.85FW, with CWT recovery...
many thanx,

The closest thing available right now would probably be CleanROM Dev edition 2.0. Check it out in the development section.

CleanROM DE 2 is what I'm running and it's great. It's pretty clean.

Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?

100%digital said:
Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?
Click to expand...
Click to collapse
Clean ROM DE is different from what you are running. Check the dev section. As for an AOSP ROM...who knows. There are a lot of factors involved.
Rabble rabble rabble.

If I understand correctly, you'll have to wait until we get S-Off so we can flash boot.img. Once that's achieved, it will be possible to flash full ROM's. But there are still a lot of things that need to be figured out, like getting the camera working, Wifi, GPS, data, etc.
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.

jmattp said:
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.
Click to expand...
Click to collapse
You know that never happens =)

jmattp said:
If I understand correctly, you'll have to wait until we get S-Off so we can flash boot.img. Once that's achieved, it will be possible to flash full ROM's. But there are still a lot of things that need to be figured out, like getting the camera working, Wifi, GPS, data, etc.
Maybe the Cyanogenmod developers will get lucky and it'll work out of the box.
Click to expand...
Click to collapse
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.

I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium

eraste said:
I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Because the only device running stock Android 4.0 is the Galaxy Nexus. I've gone through several of them and they all had the same purple tint, weird crosshatch pattern visible on white images, distortion/noise at low brightness, and other issues related to the Pentile SAMOLED display. Besides that, I can't think of any other device that runs stock Android.
I especially can't think of any Android phones that look as nice as the One X. I like its unibody construction, machined earpiece grill, soft-touch case (the black one anyway, not sure if the white is glossy), the way the glass is slightly above the case like old iPod Nano, and the display itself is really good.
Before Ice Cream Sandiwch, we had maybe the Motorola Droid, the Nexus One, and then the Nexus S. I hate physical keyboards, the Droid was out. Currently, there aren't many choices if you want a vanilla Android device. Actually... there's only one, and the display is a disappointment to me.
In my opinion, the best Android phone available right now is the One X. Knowing that developers are always making custom ROM's for the majority of Android devices, I know that I don't need to let the software dictate my purchasing decision.

eraste said:
I've never understood that rationale, buy an HTC phone that you know will be packed with sense etc then go back in time to bare bones android. Why not save your money and buy something like a Samsung, Motorola, LG, etc. With a barebones android os? Lol my rant
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You realize those manufacturers slap their own crap on top of stock android too, right? Samsung - TouchWiz, Moto - Blur, LG - Whatever the heck they do. Unless you're buying a Nexus device then you're getting a manufacturer skin.
Personally, I buy for the hardware. Though, the stock software has to be tolerable enough to last me until custom roms start coming out.

pside15 said:
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.
Click to expand...
Click to collapse
so without nand access the One X isn't going to see any AOSP builds? I’m not sure I entirely understand how nand is that important... I mean if you can boot a your own ROM, who cares.
Does HTC typically release the source for their phones as ‘pside15’ indicated that is an important factor in creating ROMs?
Seems like the Cyanogenmod team already has AOSP build for the Tegra handset. HTC One X (with Tegra) source isn’t released…

pside15 said:
That's not correct. We can flash boot images just fine through fastboot now. Just need s-off to flash kernels through recovery. Once HTC releases the source for our phone more ROMs will follow, including AOSP ROMs I'm sure. Source is needed to help create custom kernels.
Click to expand...
Click to collapse
Thanks for the correction.

100%digital said:
Thanks for the input, been running CleanRom v2.2 since yesterday afternoon, and I must say not very impressive at all... guess I’ll just need to keep waiting for that true android experience I crave so badly.
The change log listed for CleanRom v2.2. does not give any indication that carrierIQ has been removed (which is another huge disappointment for this ROM)
any idea how long we're looking at for a decent AOSP ROM to be released? month? two months?
Click to expand...
Click to collapse
qft.
I LOVE the htc one x for the hardware and its physical appeal, but i also cant wait for some stock android ROMs. The aroma one thats out gets pretty darn close, but its no CM9. Im hoping that in the next two weeks with our new freedom with the unlocked bootloader etc etc.. that we will get more than 2 roms... thats ALL I see currently in the dev section. I shouldnt complain though because obviously I'm no dev.
I feel like the AT&T version was a waste of my money though :/ it just doesnt have enough attention. The only reason I have it instead of the tegra 3 is because of the battery and lte. Otherwise there is literally no other reason I should keep this phone. Does anyone know if the battery life has been improved at all for the international version?

dufort said:
qft.
I LOVE the htc one x for the hardware and its physical appeal, but i also cant wait for some stock android ROMs. The aroma one thats out gets pretty darn close, but its no CM9. Im hoping that in the next two weeks with our new freedom with the unlocked bootloader etc etc.. that we will get more than 2 roms... thats ALL I see currently in the dev section. I shouldnt complain though because obviously I'm no dev.
I feel like the AT&T version was a waste of my money though :/ it just doesnt have enough attention. The only reason I have it instead of the tegra 3 is because of the battery and lte. Otherwise there is literally no other reason I should keep this phone. Does anyone know if the battery life has been improved at all for the international version?
Click to expand...
Click to collapse
I'm working on one myself....but because I do not want to release trash and because I have been limited on time over the last week or two...I have not released yet. Sit tight and chill out. Phone hasnt even been out for a month yet...
Sent from my HTC One X using XDA

Good to see you h8 I liked your stuff on the infuse you taught me a lot
Sent from my HTC One X using xda premium

h8rift said:
I'm working on one myself....but because I do not want to release trash and because I have been limited on time over the last week or two...I have not released yet. Sit tight and chill out. Phone hasnt even been out for a month yet...
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Oh I'm sitting tight, stoked to see what the future is with this device. Just had to vent a bit :banghead:
Sent from my HTC One X using xda premium

100%digital said:
so without nand access the One X isn't going to see any AOSP builds? I’m not sure I entirely understand how nand is that important... I mean if you can boot a your own ROM, who cares.
Does HTC typically release the source for their phones as ‘pside15’ indicated that is an important factor in creating ROMs?
Seems like the Cyanogenmod team already has AOSP build for the Tegra handset. HTC One X (with Tegra) source isn’t released…
Click to expand...
Click to collapse
Source has been released for one x tegra...
Sent from my HTC One X using XDA

There are only so many ways you can debloat the stock roms lol.
Things will pick up once the source is released and devs can start going crazy.

+1
jmattp said:
Because the only device running stock Android 4.0 is the Galaxy Nexus. I've gone through several of them and they all had the same purple tint, weird crosshatch pattern visible on white images, distortion/noise at low brightness, and other issues related to the Pentile SAMOLED display. Besides that, I can't think of any other device that runs stock Android.
I especially can't think of any Android phones that look as nice as the One X. I like its unibody construction, machined earpiece grill, soft-touch case (the black one anyway, not sure if the white is glossy), the way the glass is slightly above the case like old iPod Nano, and the display itself is really good.
Before Ice Cream Sandiwch, we had maybe the Motorola Droid, the Nexus One, and then the Nexus S. I hate physical keyboards, the Droid was out. Currently, there aren't many choices if you want a vanilla Android device. Actually... there's only one, and the display is a disappointment to me.
In my opinion, the best Android phone available right now is the One X. Knowing that developers are always making custom ROM's for the majority of Android devices, I know that I don't need to let the software dictate my purchasing decision.
Click to expand...
Click to collapse
Exactly!

htc one x- kitkat thread

I thought it would be good to start a threat about kitkat anticipation and also when a ROM is spotted we would have a place to talk about it. A lot of people are porting the HTC one ROMs to the one x and there is some CM kitkat ROMs already on the HTC one. So maybe we can find someone to port it soon. Its already apparent that the sense versions are behind . the HTC one has 4.3 and sense 5.5.. Pure android seems like it will be the only way for new ROMs

I feel as though we should leave kitkat alone and mainly focus on the roms at hand, but I definately would not mind a nice piece of chocolate if you catch my drift
Sent from my HTC One XL using XDA Premium 4 mobile app

nlsolja123 said:
Pure android seems like it will be the only way for new ROMs
Click to expand...
Click to collapse
I'm not sure why you see that. There were at least 2 or 3 devs that ported Sense 5 over from the M7 to the EVITA (before HTC released Sense 5 for us officially). As long as there is interest by devs, I don't see why they wouldn't do the same again for KitKat and Sense 5.5. True, the hardware hurdles will be an issue. But AOSP ROMs will experience their share, as well.

redpoint73 said:
I'm not sure why you see that. There were at least 2 or 3 devs that ported Sense 5 over from the M7 to the EVITA (before HTC released Sense 5 for us officially). As long as there is interest by devs, I don't see why they wouldn't do the same again for KitKat and Sense 5.5. True, the hardware hurdles will be an issue. But AOSP ROMs will experience their share, as well.
Click to expand...
Click to collapse
Team Venom has released the Viper ROM for the HTC One. They released ViperXL for ours. Seems like they have all the necessary talent and tools to put together a new ViperXL release with 4.3/Sense5.5

I am pretty sure Kit Kat is going to be a while. It would be really cool to get a 4.3 Rom good enough to be a daily driver. They are getting there. We still have a healthy Dev community.
Sent from my HTC One XL using Tapatalk

As far as 4.3 being a daily driver, I'm running PAC 4.3.1 with touched 6.1 kernel with no problems, I use it as a daily driver. I've been on 4.3 maybe a month with little to no problems. So I think 4.4 is looking good for our phones
Sent from my One X using xda app-developers app

While you're having success with that ROM there have been several problems plaguing 4.3 ROMs, that's what's being referred to.
Sent from my Evita

Well here's the first kitkat rom:
http://forum.xda-developers.com/showthread.php?t=2535315

Also saw in some other thread a screenshot of Evita running CM11 (H8's screenshot, I think), so yeah. :good:

4.4 Kit-Kat is officially coming to The HTC One in January of 2014 So hopefully we see a nice port come to our One X/L

Unfortunately it's pretty difficult to port from the One due to the different chipsets and resolution, it just doesn't work properly. A port would need to come from a similar device, like maybe the One Mini.
Sent from my Evita

HTC releases their updates on time. Blame your carrier for the delays
Sent from my VENOMized HoxL

I've read in many places that Evita is going to get even an Android 5 update, so "Why so disappointed?"...
After all, it has been a flagship phone for several months and is still a powerful one in the markets

I seriously doubt this phone will ever get Android 5.0 as an official update, I'd put money on it. I'm not sure where you read that but it's highly unlikely. We're probably not even going to officially see 4.3 or 4.4.
Sent from my Evita

Scozzar said:
I'm fairly certain that the Evita is done for updates. Also, HTC has a horrendous record of keeping their promises when it comes to release dates. Remember that update we were supposed to get at the end of November? Remember how it wasn't released until march nearly 5 months later? I do. That's when I rooted my phone.
Click to expand...
Click to collapse
That was the carriers fault. Adding all that bloatwear takes time dontcha-know.
And I was talking about a Port from the One by our devs here to the One X.
arashtarafar said:
I've read in many places that Evita is going to get even an Android 5 update, so "Why so disappointed?"...
After all, it has been a flagship phone for several months and is still a powerful one in the markets
Click to expand...
Click to collapse
No we are supposedly getting a Sense 5 Update (Android 4.2 from Android 4.1.1 I think) But AT&T won't get it till next November probably

You're not quite right about that. HTC push their own non-carrier updates to their non branded/Asian models and they do have a terrible record of keeping promises and getting them out on time, if at all.
Sent from my Evita

Hey guys I have the international version but both versions seem to be abandoned by HTC but there is a glimmer of hope as Google want 4.4 pushing out to all devices capable of running it so hopefully HTC will update all the one series phones eventually.

Google can't even get their own nexus (galaxy) updated. What makes you think they can make HTC do it. This phone won't get any more updates. The next HTC one will be out soon and all focus will go for that.
Sent from my HTC One X using xda app-developers app

shoredroid
anyone here running shoredroid 4.4 on their at&t one x?
just flashed mine last night after unlock/root/s-off/ and I can't believe how much more smooth and fast my phone feels.
now I just have to order a new screen to replace this cracked junk!
guess thats what I get for an $80 craigslist phone huh?

undivide said:
anyone here running shoredroid 4.4 on their at&t one x?
just flashed mine last night after unlock/root/s-off/ and I can't believe how much more smooth and fast my phone feels.
now I just have to order a new screen to replace this cracked junk!
guess thats what I get for an $80 craigslist phone huh?
Click to expand...
Click to collapse
All of the kitkat roms are pretty darn smooth. I had some SD card/signal loss/reboot problems on shoredroid so I moved to the CM 11 nightlies. Latest nightly working perfectly so far *crosses fingers*

Sense vs GPE

Has anyone tried running both Sense and the GPE ROM for any length of time? Any deal breakers with the GPE ROM. I have read through most of the forum over there, but I'm not allowed to post in development forums so I wanted to see if anyone could provide any feedback on the GPE ROM. I used to have the Thunderbolt but grew sour of Sense after a while. Now I'm pretty much over any manufacturer UIs like Blur, TouchWiz, Sense, etc. I'm looking for the pure android experience I get with my Nexus 7, but Nexus isn't available on Verizon so a GPE version of the HTC One M8 seems like about the best thing to try. Any thoughts on how this ROM works?

bradwatson said:
Has anyone tried running both Sense and the GPE ROM for any length of time? Any deal breakers with the GPE ROM. I have read through most of the forum over there, but I'm not allowed to post in development forums so I wanted to see if anyone could provide any feedback on the GPE ROM. I used to have the Thunderbolt but grew sour of Sense after a while. Now I'm pretty much over any manufacturer UIs like Blur, TouchWiz, Sense, etc. I'm looking for the pure android experience I get with my Nexus 7, but Nexus isn't available on Verizon so a GPE version of the HTC One M8 seems like about the best thing to try. Any thoughts on how this ROM works?
Click to expand...
Click to collapse
GPE is essentially pure AOSP. just comes with google apps etc. I personally love it, I just came over from the galaxy s4 a few days ago where I was running the GPE rom there and it was my favorite rom ive ever ran on any phone. I haven't used sense in so long im enjoying it right now, still running stock rooted s-off with xposed, but when I do start roming ill prolly just go straight to GPE.

I'll stick with sense IMO, many more features, very fast , and unparalleled functionality.
Sent from my HTC6525LVW using XDA Free mobile app

I've used the GPE rom for a few days and the sense based roms as well. In my experience it seems the GPE needs a custom kernel because there are a few things not working properly, the camera for example, and the overall experience is sluggish compared to the sense based roms. Stick with anything sense based right now, run a different launcher, and use xposed, that combo is killer and you get all the speed you can handle. Give the GPE a few more weeks and it'll probably be in full working order, at which time I'll definitely be going to it. So nice having a clean rom that was explicitly made for this phone from the manufacturer.

GPE isnt as good as some ASOP roms IMO. I typically run SlimKat, but there are many more out there.

Kernel Development?

how come we are not seeing much development on kernels for the M8, especially Verizon?

Just came from the G2, which has a locked b/l and it has 2 compatible vzw kernels plus some Rom devs that build their own. What gives?
Sent from my HTC6525LVW using Tapatalk

Quadrider10 said:
how come we are not seeing much development on kernels for the M8, especially Verizon?
Click to expand...
Click to collapse
It depends on how many DEVs pick it up and how far along CM is on it usually. Youll see more probably once CM gets more stable on the M8 as CM is multi-device compatible so one kernel to rule them all sort of thing from what I know. The Regular M8 has plenty of work, its just that for around 6 months the carrier specific ones tend to see less work till someone puts in the work to unify everything.

yea, was just curious. I saw that the original M8 had a lot more dev then verizon.

Snapdragon 820 = AOSP?

Quite simply, from what I'm reading about S6, and Exynos, the main reason for lack of major AOSP ROMS (CM13 has been finally ported), is the idea that Exynos is not documented so coding for it is difficult.
Knowing now that Snapdragon 820 is a Qualcom chip, which apparently is the most common SoC used for phones, should we expect to see a lot of AOSP based ROMs?
I am very used to Vanilla Android, and I don't think I could deal with TouchWiz, I like CM Theme Engine, and RRO Layers, so the big reason for my question is based on the hope that the probability of non-TouchWiz ROMs is high.
Also, I had a moto x 2014 and I've come to fall in love with AMOLED, and would like to stick to a small form factor 5 to 5.1 inches, combined with healthy ROM community, I'm kind of hoping S7 with SD820 might be the phone for me.
Please don't say "If you like Stock don't buy a Samsung", I get it, but it looks like maybe that stigma might not hold up soon if the ROM cookers are supportive.
Thanks!

I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.

geoff5093 said:
I'm not sure on the international versions, but I know most carrier versions of the Note 4, S6, Note 5, etc. never got unlocked bootloaders in the first place, let alone custom ROMs. Knox is killer.
Click to expand...
Click to collapse
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.

I don't do carrier contracts so I'd most likely look/hope for a developer/pure edition of the S7.
The Edge does not really interest me, unless they figured out some cool things to do with the curved screen that are actually useful.
I'd much rather have a fingerprint reader, and front sensors like the Moto's, I love waving my hand in front of the display to have it wake up and tell me the time.
People go... you are a Jedi!?

Airtioteclint said:
Tmobile variants of all the phones you listed are bootloader unlocked. Knox has never stopped anything.
@Shemploo yes more than likely AOSP roms will be available for the snapdragons. I'm betting even exynos variants will get it although probably a little later.
Click to expand...
Click to collapse
I know AT&T and Verizon are different stories, good to know it works for T-Mobile though.

Most if not all Sprint phones have unlocked bootloaders too. At least last time I checked!

Yes. However you got something wrong there. The reason why Qualcomm has all the fancy AOSP based ROMs (I say fancy because most people consider non aosp roms boring) is because of this. This is where QCOM releases their soruce code for the platforms. This makes fixing easier because you actually have the code. However exynos and all the other ones don't give a crap about the small percentage of their users that actually flash roms etc. Infact, they only want money. And guess what? ROMs = Longer device lifespan. That's why they don't release it. Thankfully enough there are some geniuses here on XDA that still are able to do the job for exynos! However, QCOM has allot better optimization with CM in terms of performance than with any other chipset. I live in the EU, which means Exynos. After already owning 2 exynos devices, I'm tired of the work that has to be done for them. I was lucky enough that both of them had Exynos chipsets that already had allot of devs mainly from other devices which made building possible for me.

@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.

Shemploo said:
@CTXz I suppose the closest thing to AOSP on Samsung devices QCom, or Exynos, is going to be Cyanogen right?
Would I be right to assume Cyanogen would be the first (possibly only) AOSP to build for Samsung?
In other words, would/could anyone build true AOSP based on Google's source code?
I understand both are considered AOSP, I'm asking cause from general experience with ROMs, when ROM is built on CM, they usually just build in the CM Theme Manager, and only the ROMs based on Google's code do things like RRO Layer support.
Click to expand...
Click to collapse
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.

..

CTXz said:
Ofcourse, infact that is up to the devs, however CyanogenMod is usually recommended over pure AOSP due it's great documentation, common updates, it's optimizations and tweaks above stock AOSP. It's also the simplest to get the hands on.
EDIT: It's also important to know that CM isn't just AOSP with a few apps. While CM is based on AOSP, it still has it's own community and is still a different ROM than AOSP mainly when it comes to the internal changes.
Click to expand...
Click to collapse
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.

knitler said:
After Cm started trying to push that you make an acct with them I will never use CM again. I know that people say Inc has no relation to... whatever non-Inc calls themselves, but I no longer trust any of them and would rather buy a Windows phone or iPhone before I run them on any phone of mine again.
Click to expand...
Click to collapse
Um... CM =/= Cyanogen Inc
CM is a completely separate group that is not affected in any way. It's like XDA and GOogle. XDA is for developing and still both work on android. I know some people in the official CM group, all of them very friendly and none of it is affected by Cyanogen Inc. You're making yourself lies that aren't true. It's like blaming the entire CyanogenMod team because one dev for a specific device didn't fix the issue yet.

If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk

barondebxl said:
If CM is the main like, why not just get a Nexus and get it over with? You'll get CM right away.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
Because some people don't want a nexus

CTXz said:
Because some people don't want a nexus
Click to expand...
Click to collapse
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk

barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
And cripple it with bad, forever-beta, with half the functionally misssing software.

Sure hope we get aosp!
Sent from my SM-N920T using Tapatalk

I thought it was primarily due to the 64 bit architecture that was the hold up with aosp on the s6. Buy I could be wrong. Been a while since I went looking.

barondebxl said:
But if CM is what you look for, isn't a Nexus your best bet? Unless you want the S7 hardware.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?

CTXz said:
That is a good argument, however many people DO actually go for the look/hardware and with that said. Afterall xda wouldn't be this big if you could use the word nexus for all excuses, right ?
Click to expand...
Click to collapse
Might want to get used to it as sooner or later it will only be nexus devices that are worked on.
Also what's the point of getting the device fore the hardware when aosp doesn't take advantage of the hardware? Aosp drivers don't compare to the stock ones.