I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
bbabiuk said:
I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
rootSU said:
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
Click to expand...
Click to collapse
Very thorough. I do have one other question then...
Then AOSP ROMs for Nexus devices should by the nature of the build process have everything working similarly to the stock ROMs. Things like Bluetooth not working quite right or green tints to cameras should not occur.
Sent from my Nexus 5 using XDA Premium 4 mobile app
*should* yes, but not guaranteed. Pure aosp should work immediately after compile. However, new functions are added by developers to the aosp code base to make the roms more functional and these commits can break each other or even existing functionality
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
air2k57 said:
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the update. The nice thing about nexus devices is it is so simple to go back to stock. It was a real pain on my HTC one.
Sent from my Nexus 5 using XDA Premium 4 mobile app
No problem. I had htc one and it was indeed a pain. While I liked sense, I felt a need to root because of annoying apps it came with, or power saver notification that was always there. Not to mention, T-Mobile variant took ages to get updated, and when it did, it was buggy. The whole S-Off thing was a nightmare.
I've always found other devices, even nexus 4, to function better with custom ROMs and kernel. It took me awhile to root n5 though, simply because I was happy with everything. I did like ability to have center clock, or circle battery with %. However, in order to have those, you need aosp or gravity box that doesn't work with art due to xposed. Oh yea, pie I liked too, I like having more screen space.
Other than that, I am very happy stock. I ended up finding a really good mix with purity ROM and elementalx kernel. I liked elemental on HTC one a lot as well. And, it has cooler colors option, I do like the way it makes display look.
Last night I ended up unrooting and going stock to compare. Reason being, I got annoyed with bright back key in landscape and text on quick toggles in portrait ended up being cut off some. Performance wise, I am thinking that lure stock is still A bit quicker. Battery? Not sure yet, I got woken up at 7am by stupid weather alert, ended up unplugging my phone and leaving it on nightstand. It dropped from 99% to 95% in 4 hours idle. So about a % an hour. I remember Franco and elemental having better idea battery life though.
Sent from my Nexus 5 using xda app-developers app
Related
I have a big question that is been floating around in my mind.
We have CM7 which is based on ginngerbread and we got Eagle blood 1.03 which is gingerbread as well.
Why does it seems like eagle blood developers seems to develop way faster and have a more stable rom than CM7?
Is it because they had to port gingerbread to the G2x? If that its the case, wouldn't it be easier to grab the gingerbread leak and develop using that as the source?
eagle blood is from gingerbread leak and cyanogen isn't?
Also does it takes longer for CM7 to develop because they are adding more features to the ROM?
The reason I'm asking is because I had this questions and is nothing against CM7 directly at all, I just want to understand how they are doing it and see the benefits.
Thanks
Sent from my LG-P999 using XDA App
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
regP said:
Eagle Blood is based on the existing gingerbread leak.
Cyanodenmod is build from the ground up using the AOSP source code.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Once they get the device-specific stuff ironed out, feature updates can be added easily across multiple devices.
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
moshe22 said:
That clears up some of my doubts.
So basically they are using a gingerbread AOSP from google?
And what are the advantages of doing it this way instead of just grabbing a leaked ROM and tweak it.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
r4d14n7 said:
For example, if you look at the CM7 changelog the unlabeled changes are to all GB devices and the entries labeled "p999" are changes specific to this device.
Click to expand...
Click to collapse
Oh good to know, thanks
regP said:
Better performance. Manufactures ROMs often end up with bad coding which results in a device suffering from things such as bad battery life, lower performance, etc. Also with official ROMs you can't do much with it until they release the source code. And even then (at least with samsung) some things like driver source never get released which means the devs cant fully optimize the ROM. AOSP means full control over the ROM to make it do what you want it to do the way you want it to be done. It does take much longer to complete though which is why CM has nightly updates. Makes it easier to put out a nightly than to put out a whole new ROM for every bug they fix. I'm sure someone can explain this better than me.
Click to expand...
Click to collapse
Wow, this really answers my question as to why it takes them longer. Thanks
So it means that cyanogen even develop their own drivers?
Sent from my LG-P999 using XDA App
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
I must disagree. I LOVE CM 7 and ran build 11 and 13 and found it rather buggy right now. Sometimes the touch screen didn't recognize touches on the right side(I consider this a significant bug). When you call a number and have to punch in numbers (like a VM password or when dialing an extension) did not work for me(which I consider another significant bug). I also heard there are issues with it sticking APN settings(cant comment because I didnt really check that when I had cm 7 installed) I just dont think cm 7 is stable enough at the moment. Eagle Blood is running pretty well right now. I would say a lot better than cm 7 but that will change once CM gets the bugs worked out
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
Yes, personal experience. Been running eb 1.02 and is been great.
I Just flashed CM7 #15 just to test it out and is buggy for me
-When i receive a call i don't get any sound from the ringer even though is not muted
-Sensors are like in auto brightness even though they are not
-The performance of the whole system isn't the best.
I am sure it will be the best ROM out there but as for now still only and nightly and is buggy
Sent from my LG-P999 using XDA App
One significant difference for me, which is due to the fact that Cyanogen has built their own rom with their different bluetooth stacks (as opposed to LG's custom ones), is that bluetooth controllers actually work with CM7. Useful for using a wiimote on emulators through HDMI
Just something to consider, no bluetooth controllers on EB.
Sent from my LG-P999 using XDA App
regP said:
Eagle Blood is based on the existing gingerbread leak with added tweaks.
Cyanodenmod is build completely from the ground up using the AOSP source code. It has features not found in ROMs released by manufacturers.
It's like modding an engine vs building an engine.
Click to expand...
Click to collapse
Right, and not only that, cyanogen has many different phones he and his dev team have to work on.
Sent from my LG-P999 using Tapatalk
Build #16 is out today and supposedly the TouchTones in the dialer and the backlight is fixed (thank god!)
But yes. Cyanogen builds their own kernel and drivers, which is why it usually is more compatible with stuff like WiiMotes and stuff. But once they get the Kernel working properly (which they are doing now) it is just a matter of updating the core OS then it can be pushed to all devices pretty seamlessly (I guess).
There are lots of benefits of using CM over standard stock Gingerbread. For one, Stock is 2.3.3 where CM7 is 2.3.4 so it supports lots of Googles new apps like Video in Google Talk and the new Cloud Music player.
Also there are tons of tweaks like Notification menu toggles, System Themes, Sound Profiles, Black-List calling, Several Lockscreen types and Widgets with Gesture support, etc the list goes on and on.
Between the Notification Toggles and Themes which you can install from the market, I'm hooked.
Plus it is the only Gingerbread rom that doesn't cause my phone to lockup/reset/Black Screen of Death/whateveryoucallit
MWBehr said:
You mentioned that you feel eaglesblood is more stable than CM7. Is this from personal experience or from reading the forums? In my experience, CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
It has tons of bugs like inaccurate battery readings
Sent from my LG-P999 using Tapatalk
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
MWBehr said:
CM7 as of around nightly #11 has every significant bug worked out.
Click to expand...
Click to collapse
u must be high
jdaclutch said:
my concern is that is the g2x able to do 1080p video recording and high resolution picture like the stock rom? THis is the only reson why I'm still sticking with the stock rom.
Click to expand...
Click to collapse
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
r4d14n7 said:
+1. I take a lot of photos and videos of my kids and would rather stick with 2.2 than have a gimped camera.
Click to expand...
Click to collapse
Yeah, i take alot of pictures and videos too
Sent from my LG-P999 using XDA App
Hi,
I'm relatively new to the whole Android business, coming from the Blackstone running Windows Mobile 6.1, where I did some ROM cooking. So probably I don't have that much of an overview yet.
After looking around in the Android development section for this device, I realized that most (all?) ROMs are based upon the HTC stock ROMs.
However I was wondering whether there are ROMs (or projects) with the goal of bringing the stock Android sources to our devices. I'm not that much of a fan of all these modifications the OEMs are including and would like to have as much of a vanilla Android as possible. As seen with the vulnerability of htclogger, this is a justified request as all added (unneeded) stuff is just another weak point.
I'm pretty sure that the vanilla sources won't be enough to get our devices running and there are a bunch of drivers, which must be added to get (full) functionality.
The ultimate goal would be to get some sort of scripts, which would automatically grab the latest Android sources, add the necessary stuff, which is needed to get full support for our devices, and build a ROM, which then could be the base for custom ROMs using the available tools/kitchens.
So, basically, before starting something, which already exists (but I couldn't find), I would like to ask you if you know of something that suits my taste in any sense? Or am I the only one interested in this way of thinking? Is there anyone who would like to participate in this endeavor when there shouldn't be something similar already?
Thanks in advance for any helpful reference in the right direction.
Best regards,
johnpatcher
There are a lot of roms with no-sense options and you have miui and cm7
xyqtt said:
There are a lot of roms with no-sense options and you have miui and cm7
Click to expand...
Click to collapse
Yeah, but all ROMs I've seen so far are based upon the stock ROMs and removed some of the included HTC stuff. There even seem to be some scripts, which would do just that after flashing such a ROM. I would like to go the bottom-up kind of approach.
As great as MIUI and CM7 are, both of them don't support the Sensation officially yet. Furthermore they try to be an alternative firmware/ROM and add a whole bunch of functionality for themselves.
Without looking into their building process, I could imagine that they are using the Android vanilla sources as a base, which would be the kind of thing I want, although I would have to investigate that further. Does anyone know something about this?
CM7 does officially support the Sensation, albeit in Alpha form.
What you want is someone to compile a ROM from source (AOSP) specifically for the Sensation but it would seem no one has taken up the challenge yet. Surprising really, there were 2-3 on the Desire
We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.
Well, technically Cyanogen Mod is the greatest AOSP ROM out there. As far as I know nobody writes anything from the ground up. At least if I understand how everything all goes together. Now, someone may very well use their base code & do all their own coding for add-ons & customizations but I'm not sure who or which ROM you may be talking about. My wife has a Nexus 4 so I have been browsing their forums but that's the way it seems to me.
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
SEE! I told ya I wasn't sure. LMAO! :laugh:
demkantor said:
Well you wouldn't port an aosp ROM as the base wouldn't be aosp, so it would need to be built from source if you want true aosp. This is of course much more complicated on a phone like this where there is no aosp source other than from the SDK, its doable but would require lots of hard work
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would love to try this, and I've gone far enough to setup everything on my linux box. I got to the point of downloading the source files, and I'm not sure where to go from there. Reason being that I know that most of the phone sensors and components wont work without the proprietary drivers and other required software for the phone. I don't know where to find them, and if I managed to get them, how to integrate them into the source tree. I have looked through the developers reference thread, but not sure whats needed from there to get all the stuff needed.
I think I'm in over my head lol
Fuzi0719 said:
We seem to have a great selection of other ROMs, from CM, AOKP, etc. but I never see just an AOSP ROM for this device. It would be great to compare the "Nexus Experience" for the Doubleshot, I think.
Click to expand...
Click to collapse
I gotta say, I only just got into the ROM bizness. Was running fully stock, locked GB rom on this phone until a few weeks ago. After some research and lots of reading through these forums I settled on the Unofficial CM 10.1 JB rom here, and absolutely love it. I can't believe what amazing crew of dev's we have here that are bringing new life to this great hardware, but unsupported handset!
Suffice to say it's been my ONLY other experience compared to stock, but I'm using it as a daily driver with nearly no issues, and some have even been fixed since my first flash a few weeks ago. Can't thank this forum enough. Now if only I could post in the development forums without having to make 9 more BS posts I'd be a happy camper!
Ok, so I'm not a tech pro. But molding my gadgets is becoming a hobby. I've learned unlocking and rooting.. I've started flashing ROMs and mods to stock roms.
Now I'm wondering, what's the difference between ROMs like pure AOKP vs ROMs based on other original roms like AOKP?
For example, I'm using Smoothrom on my grouper nexus 7 to boost performance/reduce lag/etc. It is a 4.3 Jellybean ROM based on AOKP. What is the difference v the AOKP ROM? added features baked in? Bugs within Aokp fixed?
This is question is just for knowledge sake, so please don't criticize any biases or wrong assumptions apparent in the language of the question. Please do address any inaccuracies or biases/assumptions that you notice. Like I said, this is just for me to better understand the motivation/benefits/risks/purposes behind roms like AOKP v AOKP Based (slimrom).
Sent from my Nexus 7 using Tapatalk
Okay basically everything that's made from scratch or source is pure. Roms that mention they are based on these so called "aosp" "aokp" is pretty much the same thing as the one built from source but its been modified, for example cyanogenmod is built from source, if you download it and modify the ROM, enhance it a bit more, add more features you will have to say it is based on cm as you didn't build it from source or scratch. You used the ROM as a base for your project. Like something you can start from.
Its like a car. A person that owns a car and modifies it, but its based on the original. The original is initially made by scratch. I hope I made sense. Sounded better in my head
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Okay basically everything that's made from scratch or source is pure. Roms that mention they are based on these so called "aosp" "aokp" is pretty much the same thing as the one built from source but its been modified, for example cyanogenmod is built from source, if you download it and modify the ROM, enhance it a bit more, add more features you will have to say it is based on cm as you didn't build it from source or scratch. You used the ROM as a base for your project. Like something you can start from.
Its like a car. A person that owns a car and modifies it, but its based on the original. The original is initially made by scratch. I hope I made sense. Sounded better in my head
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you. Completely makes sense. I guess that's why forums usually have two sections "original development" and Android based development."
Question for anyone:
Are those that are based on something like CM usually and improvement on CM in terms of bugs, etc or is it more just a preference in terms of features?
Sent from my Nexus 5 using Tapatalk
yogi217 said:
Thank you. Completely makes sense. I guess that's why forums usually have two sections "original development" and Android based development."
Question for anyone:
Are those that are based on something like CM usually an improvement on CM in terms of bugs, etc or is it more just a preference in terms of features?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It really depends, some add in more features, some remove features and make is clean. In you way you could say its an improvement but its up to the user as they are the ones that judge it themselves. Some bugs get fixed in the nodded Roms that use cm as base, like I said its all up to the user that mods the ROM. If they want to fix it themselves or wait for a new release.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
It really depends, some add in more features, some remove features and make is clean. In you way you could say its an improvement but its up to the user as they are the ones that judge it themselves. Some bugs get fixed in the nodded Roms that use cm as base, like I said its all up to the user that mods the ROM. If they want to fix it themselves or wait for a new release.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you. That's what I was thinking, but wanted to make sure. I'm digging this culture. I'm a teacher and interested in independent learning and the support of the online community in mobile software modding and development is very interesting from a learning perspective.
Sent from my Nexus 5 using Tapatalk
@yogi217 It actually is quite interesting. I'm sure you'll understand quite a bit about android development in some time. It isn't that hard, just explore and youll come to a point and find out how easy it is. And good luck on your android/mobile development journey!
Sent from my Nexus F...Fi...Fii...Ahem...*clears throat*... Five.
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
v1nsai said:
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
https://android-review.googlesource.com
As far as I know, the stock ROM on the Nexus 5 doesn't use any proprietary binaries so it stays closer to AOSP, which is why it also seems to perform "worse" in benchmarks and makes some people buy other devices because they have "better performance", lol.
the nexus 5 is a nexus, those drivers are made directly for the nexus 5, no hacking needed. other androids are different, they arent nexus.
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
yea, there are better roms than cm, almost all aosp based, not as bloated and much faster.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
If CM thread is quiet, it's being overshadowed by superior ROMs. Unsure why anyone would choose it for a Nexus.
Stock ROM works but has zero options. Couldn't stand it without Xposed. Don't want Xposed because I want ART.
I'm saying flash SlimKat for ROM. Then flash Code_Blue kernel. My opinions are subject to change... several times a month. And TWRP or PhilZ for recovery. Stay away from stock CWM.
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
v1nsai said:
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
Click to expand...
Click to collapse
one and the same in this case