Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags
Downloads:
HTC One Global Unlocked (All GSM Variants)
Important Links:
We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash SuperSU zip
Reboot
Thank you for choosing codefireXperiment.
Ohai guys! Just FYI, I have the T-Mobile variant and this project is my daily driver. I think you will come to find this build is sick fast and it's benchmarks will blow any other AOSP build clear out the water. Personally, I've never experienced speed like this. There's a lot of great stuff in the pipeline so stay tuned and stay updated.
If you come across any bugs, please let me know. Since the last couple builds, I can't find any. But if any issues, concerns, or requests pop up, post up.
Great to see you hear. I still remember you from the Evo 3D days
May I ask what "OPENMASTER" is referring to?
LiquidSolstice said:
Great to see you hear. I still remember you from the Evo 3D days
May I ask what "OPENMASTER" is referring to?
Click to expand...
Click to collapse
Oh snaps, sup LiquidSolstice! Our project is based on AOSP Master branch, not release. There's been upside and downside to this stategy. We had to hunt down some bugs here and there, but afaik they all got squashed as of the last couple builds.
bigrushdog said:
Oh snaps, sup LiquidSolstice! Our project is based on AOSP Master branch, not release. There's been upside and downside to this stategy. We had to hunt down some bugs here and there, but afaik they all got squashed as of the last couple builds.
Click to expand...
Click to collapse
Fascinating. I didn't realize there were multiple branches. I guess that does put you more on the cutting edge level than most other ROMs here?
Oh shiz. The last few devices I've owned and ran CFX were consistently the fastest each device has ever been. You couldn't slap the smile off my face when I seen this thread
If I have an att one and converted to GE, does it matter which download I choose
Sent from my One using Tapatalk 2
InflatedTitan said:
Oh shiz. The last few devices I've owned and ran CFX were consistently the fastest each device has ever been. You couldn't slap the smile off my face when I seen this thread
If I have an att one and converted to GE, does it matter which download I choose
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Honestly, I'm not sure. That's why we build them all. I know the tmo variant has different proprietary radio libs, likely for additional spectrum support. But I'd bet the UL and att builds are pretty much the same, except for device fingerprint.
Synergy, me, and a couple of other guys make up the core team. I'm having a blast with m7 man! I got some sick ideas in store to fully harness the power of this beast.
bigrushdog said:
Honestly, I'm not sure. That's why we build them all. I know the tmo variant has different proprietary radio libs, likely for additional spectrum support. But I'd bet the UL and att builds are pretty much the same, except for device fingerprint.
Synergy, me, and a couple of other guys make up the core team. I'm having a blast with m7 man! I got some sick ideas in store to fully harness the power of this beast.
Click to expand...
Click to collapse
I have never flashed a tmo-specific m7 build on my T-MO branded phone and I don't think I've ever had a problem with signal.
LiquidSolstice said:
I have never flashed a tmo-specific m7 build on my T-MO branded phone and I don't think I've ever had a problem with signal.
Click to expand...
Click to collapse
Heck, if that's the case I'll look and see if I can get away with a single build. That would make life simpler.
bigrushdog said:
Heck, if that's the case I'll look and see if I can get away with a single build. That would make life simpler.
Click to expand...
Click to collapse
Same here. Notice the att one forum is dead. I don't think I've ever flashed an att specific ROM. International is fine and service is awesome.
Sent from my One using Tapatalk 2
InflatedTitan said:
Same here. Notice the att one forum is dead. I don't think I've ever flashed an att specific ROM. International is fine and service is awesome.
Sent from my One using Tapatalk 2
Click to expand...
Click to collapse
Ya the tmo board was a ghost town. Ok, lemme run a UL build and see if my m7 likes it. Gotta test things personally first. Keeps me out of trouble.
bigrushdog said:
Ya the tmo board was a ghost town. Ok, lemme run a UL build and see if my m7 likes it. Gotta test things personally first. Keeps me out of trouble.
Click to expand...
Click to collapse
Hi, good to see your ROM here too Running it on my N7
Welcome
btw sense ROMs work universally for all GSM devices
poondog said:
Hi, good to see your ROM here too Running it on my N7
Welcome
btw sense ROMs work universally for all GSM devices
Click to expand...
Click to collapse
I'm still getting my feet wet in GSM land. I got kicked off Sprint for violating their roaming policy. Of course, it was intentional to get out of buying my contract :angel:
bigrushdog said:
I'm still getting my feet wet in GSM land. I got kicked off Sprint for violating their roaming policy. Of course, it was intentional to get out of buying my contract :angel:
Click to expand...
Click to collapse
haha, maybe put some crocs on mate
That's nice of them... oh well good excuse to get a GSM device cause they're waaaaaaay better
Oh wow man!sounds like a lot of work has been put into it..downloading and testing now!!
Sent from my HTC One using Tapatalk 2
aamitabh28 said:
Oh wow man!sounds like a lot of work has been put into it..downloading and testing now!!
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Quite a complete ROM already as its been in development on this device for a while already and other devices months
Download stopped a couple of times already .. on dolphin..any ideas mate?
Sent from my HTC One using Tapatalk 2
aamitabh28 said:
Download stopped a couple of times already .. on dolphin..any ideas mate?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I just downloaded from the server (another build) on my computer all fine
Nice to see another rom thanks for the work !
As soon as our IT guy get the backend right, I'll write an updater for easy updates. Couple things I think would be nice. Native xvid support and native dts audio. I have mx player pro with a custom libffmpeg that does all that but native is always good. Thoughts?
Related
Alright ladies and gentlemen, I am glad to finally bring you the Evervolv series of ROM's. This is an alpha build, however most, if not all items should be working. I'm going to keep this post vague and update it when the rom becomes beta worthy.
This rom would not be possible without the CM team, so i give them props any time i can.
Click to expand...
Click to collapse
The current team of Evervolv constists of:
preludedrew - Droid Incredible, Evo 4G, Evo Shift 4G & Nexus one maintainer; overall support & development
cocide - Evo 4G; Web; Linux and overall support & development
milesje - Evo 4G; java and overall support & development
Adhvanit - Graphics and Droid Incredible support.
RyteSyde - web and graphics development; Evo Shift 4G support
TpyoKnig - Web support and hosting.
Contributors
Exxodium - Wallpaper graphics
Deck - What does deck do?
Click to expand...
Click to collapse
Everything should be working as of now (with the small except to the Brightness widget, it's functionality is there... but the UI updating is not just yet). The Nexus One i have has no sim card, so i can't test everything. However English is the main supported language, if google hasn't added the language support, i haven't either. This means certain apps will have no support at all (i.e. Evervolv Settings). If there is someone that would like to contribue the efforts to languages, we'd be more than happy to have you aboard.
Screenshots of the ROM in action can be seen Here - Screenshots
Download the latest from from Evervolv.com
Make sure to do a full wipe, even if you're coming from an older build, just to make sure. Also, flash Google Apps that are also on that download page.
Evervolv's Github. Click Me
Evervolv's current kernel. Click Me
Click to expand...
Click to collapse
Q&A
Is this CM7?
No, this is a build that started from AOSP. However, some of the fixes and few features have been derived from the CyanogenMod Team, including the CM kernel.
How social is the evervolv team?
You can join us on IRC, irc.freenode.net #evervolv. Or follow myself and the status of Evervolv @preludedrew on twitter.
Reserved...
One more....
What changes baby been made to this rom? How does it compare to cm7?
Sent from my Nexus One using Tapatalk
Nice, I am flashing now and will check it out.
Looks good and feels good aswell, but trackballwake is needed.
Why not. I haven't tried anything Gingerbread yet (been faithful to Rod's MIUI the last few months).
I'll download and check it out!
uoY_redruM said:
Why not. I haven't tried anything Gingerbread yet (been faithful to Rod's MIUI the last few months).
I'll download and check it out!
Click to expand...
Click to collapse
Giving up already?
I may give this a shot too. I have ORD - I need serious help!
Disclaimer: By help, I mean moooooaaarrrr ROMMMMM's!!!!!
Axefield said:
Looks good and feels good aswell, but trackballwake is needed.
Click to expand...
Click to collapse
agree with this... this rom already support app2sd??
Liking so far. Its a breath of fresh air. Just something nice and new, really smooth and responsive.
It appears a2sd is not there? Maybe I'm wrong but under settings it said ext (unavailable).
Also, its a little eh that I can't change the dock settings (I know I can use LauncherPro and I probably will but I was trying to avoid that) because I use Chomp and DolphinHD so those dock shortcuts are useless.
Screen off animation is SWEET and boot animation is stellar.
Overall, seems very solid for a first release. I'll stick with it for now, assuming camera and camcorder work (I'm headed out to Sea World with the wife and son today/tomorrow so I need a functioning camera).
Great job and great release. I'll report back more Monday night when I get home and have used it for a few days.
Does this rom have the "wonk" problem? With nightly Rom I still have lots of problems
Nick3d said:
Does this rom have the "wonk" problem? With nightly Rom I still have lots of problems
Click to expand...
Click to collapse
yeah does it?
i havent had many problems with pure google though
but this looks nice i may try
A smooth & responsive ROM on the first release, nice.
Good Website design, too
Looking forward for more.
Axefield said:
Looks good and feels good aswell, but trackballwake is needed.
Click to expand...
Click to collapse
This was added yesterday along with the ability to change the left and right launcher buttons. I'll keep ya'all up 2 date. Best place for nightlies is my Twitter: @preludedrew. If you like to test things and just like to hang out with people... catch us on IRC, irc.freenode.net #evervolv.
preludedrew said:
This was added yesterday along with the ability to change the left and right launcher buttons. I'll keep ya'all up 2 date. Best place for nightlies is my Twitter: @preludedrew. If you like to test things and just like to hang out with people... catch us on IRC, irc.freenode.net #evervolv.
Click to expand...
Click to collapse
Hi,
You say you've added trackball wake etc, but there is no new download link?
Have you just updated the file but not renamed?
bryanchapman9999 said:
Hi,
You say you've added trackball wake etc, but there is no new download link?
Have you just updated the file but not renamed?
Click to expand...
Click to collapse
No, i will need to compile a new build. Should have a new build out soon.
preludedrew said:
No, i will need to compile a new build. Should have a new build out soon.
Click to expand...
Click to collapse
OK many thanks.
I would communicate that as its a bit missleading
Also the capacitive buttons do not light up on mine. Full wiped twiced and same issue.
Sent from my Nexus One using XDA Premium App
Great rom. I love the font and bootanimation. Wish the rom had a2sd.
Sent from my Nexus One using XDA App
OK, so after a few days use I'm noticing a few things.
Battery life seems to be average, nothing special. I hardly used it at all as I was on a small vacation (didn't make any phone calls, hardly text at all, didn't take pictures, surfed the web very very lightly) and my battery would very quickly drop to the 80's in % and beyond. Although, this could possibly be associated to my next thing.
When charging, light on top is green (fully charged) when it hits 90% battery. It does continue charging to 100% but I found that very odd that it turns green to indicate full when its at 90%...
As stated, the font is very nice too. Everything overall seems smooth, especially for a first release. I'd be nice to see new releases soon, of course with a change log etc.
Looking forward to see what is to come.
Good Morning to you all!
Sorry if this has already been posted but I couldn't find much of anything on this topic. Does a "Google Edition" Rom exist for the EVO 4G LTE? I know we have the AOSP and AOKP roms but this is something I've wanted to ask for a while. I love the pure Google experience and I just have to wait about a year until i can upgrade to a new phone like a Nexus.
Thank you again for taking the the time to read this and for all the awesome work all you Developers put in for making this awesome phone even better.
Sent from my EVO using xda app-developers app
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
I'm with you on that one. Not sure why anyone with knowledge of rooting (who doesn't mind a voided warranty) would want to buy a GE phone.
______________________________
HTC Evo 4G LTE
I don't have any problem with any AOSP Rom other than signal and connectivity issues. But its really just curiosity for me and I'm a big fan of Google so the idea of having a Google Editon EVO sounds cool to me.
Sent from my EVO using xda app-developers app
Well it won't happen.
And aosp is just as much Google as a GE would be.
Sent from my Nexus 7 using xda premium
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
scottspa74 said:
Imagine having a GE ROM that had added functionality and customizations. Then, go download one of our CM/AOKP/DU ROMs. - imagination realized.
Or, put another way, take one of our AOSP ROMs, strip away functionality and customization, and you have a GE ROM.
Is that what you're looking for?
Not trying to sound smart ass, totally sincere.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
ZamoraDC said:
What do you think would be a good solid AOSP Rom to either behave like a GE Rom or better I've only tried the CM Rom and the Xlyon Rom back and forth and couldn't get the feel I was looking for.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You could always try Evervolv. That's probably the closest to AOSP, that is, with the least customization.
Captain_Throwback said:
No. But the AOSP ROMs we have work fine. What's wrong with flashing one of them? They are essentially the same thing, except, well, better .
Click to expand...
Click to collapse
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
How difficult is this to do?
Sent from my EVO using xda app-developers app
ZamoraDC said:
How difficult is this to do?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I can't say.
For the DNA it was extremely simple (but zarboz is a boss so he would've gotten it anyway) since the two devices are almost identical (One and DNA).
But the fact that you guys have a 3.4.x official HTC kernel should help.
hacked together using core binaries from other devices when necessary.
Click to expand...
Click to collapse
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
If you think about it, this site probably wouldn't even exist if OEMs made good software. They often do have access to proprietary drivers and documentation, but most of that is slowly getting open sourced anyway.
That type of reasoning is a fallacy because more often then not OEMs are just too plain cheap to do things properly. They just need to hit their deadlines. So your only real options are to either buy a nexus device, or invest a little time in helping fix any issues that you may find.
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
CNexus said:
Not true. Not trying to insult any devs in any way, but AOSP roms for anything other than a Nexus are hacked together using core binaries from other devices when necessary. There is never such a thing as a bug free AOSP Rom, except for a Google device and/or Google edition.
The Google edition roms on the other hand, were compiled by HTC for a device that they know in and out. Unfortunately, this is one of those times when "the vendor knows best", simply because of sheer resources and hardware documentation.
It would be possible to port the GE roms if you guys ported the GPE kernel and used that to port the rom, like Zarboz and newtoroot did for the DNA.
Click to expand...
Click to collapse
Have you ever used one of the IRC builds of cm10 or cm10.1? They're more stable and are more feature rich than the stock ROM that shipped with this device or any of the updates that they were gracious enough to let sense users download over the air. The 3.0 kernel was seriously stable, but the 3.4 kernel is (nearly as) stable _and_ leaves more RAM for your silly animation effects and whatever. It's based on the reference kernel for the chip set, if I'm not making an arse of myself. So pick a build. I know 1/16 was an awesome cm10, and like I said in another topic I had 191 hours uptime on the 7/23 cm10.1 before I rebooted to rule out the ROM when I was having data issues(it was the network) </rant>
Sent from my EVO using xda app-developers app
xHausx said:
You would be surprised at what shortcuts OEMs take too.
Just because they have the resources doesn't necessarily mean it's cost effective, or that their software engineers have the time, to redo everything from scratch for each device. It's usually much easier to make it for one and then adapt that copy for use on other devices. I actually found this site thanks to htc's sloppy implementation of hdmi on the original evo. According to them it was impossible to fix until Toastcfh and Netarchy did just that and rewrote their kernel from scratch (iirc).
Click to expand...
Click to collapse
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
xHausx said:
Someone please correct me if I'm thinking of the wrong device, but I believe it was the htc TyTN2 where htc didn't even bother to include a fully functional display driver because they didn't want to pay the license for it.
http://forum.xda-developers.com/showthread.php?t=359534
Click to expand...
Click to collapse
Ha! That was my first smartphone! I first signed up on xda (under a different name) when that phone launched (I got it as the att tilt) so that I could run manila and then android on it! That display driver issue was so frustrating. Sorry for ot, but I haven't thought about that in ages.
CNexus said:
Not saying they are perfect and neither am I taking sides. But the fact of the matter is that AOSP is ported using binaries made for other devices and other hacks and so is nearly impossible to make it 100% compared to vanilla nexus roms. Issues are inevitable. And those same exact shortcuts you stated apply to and are no exception with AOSP ports like CM or evervolv. They also commonize (not a word, I know) as much as possible. They group devices like all the d2 and all the jflte, or even by processor like s4_common, etc under one common branch to make it easier for themselves to maintain.
I know I'm not gonna win here because of several things, namely being that I'm taking the "wrong" stance from the majority's point of view. But I just felt adding my 0.02 would help with the OP's original question.
Click to expand...
Click to collapse
It's not accurate to say the binaries are made for other devices when the devices are all basically the same. The MSM8960, for example, has it's own binaries, but the same chip is used in a range of devices from the Evo LTE, Blackberry Z10, One X (LTE), One XL, Windows Phone 8X, LG Mach, Moto Droid Razr M, Droid Razr, Razr Max, Atrix HD, Incredible HD, Xperia GX TL SX & V, Galaxy S III... the list goes on
The binaries all of those devices use were developed for the Qualcomm devkit I've linked below.
When you're working with a sense ROM versus an AOSP ROM there are many differences in not only appearance but the framework as well, but once you start getting down to the kernel level the hardware is all basically the same. Where we have the advantage over OEMs is that most companies know it's counterproductive and a waste of money to go after enthusiasts who borrow their binaries from one device to use on something else. If an OEM did that they would be sued in a heartbeat.
https://developer.qualcomm.com/mobile-development/development-devices/snapdragon-s4-msm8960-mdps
edit: probably actually this instead, but same difference: http://shop.intrinsyc.com/products/dragonboard-members-only
To digress back to the OP's original question though, the google edition One is basically just the one with AOSP on it. If you can find a pure AOSP ROM it'll be the exact same thing.
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
ZamoraDC said:
Thanks for the info I'm really thinking of seeing if i can try and make my own ROM and plus I've always wanted to do so hopefully it all goes well. I just don't wanna brick my phone in the process hahaha. Do you guys think trying to build off of the HTC One GE rom and convert it over to the EVO or use an EVO based AOSP ROM? Thanks again for all the help.
Sent from my Evo 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Why don't you just build AOSP? You can use the CM kernel and pull the relevant vendor files from an existing AOSP ROM (or find an up-to-date github with them).
That way you don't have to worry about having the extra customizations, but you'll still have a kernel built from Qualcomm source along with the ROM.
asop aokp cm
I have tried a lot of ROMs and I find these devs do a much better job than stock ROMs yes you have some bugs in some but the always work them out cudos to the devs I'm just glad they still support my device and having gabe up on it
It's popular, so I thought I'd try bringing Carbon back to the DNA- all credit goes to Team Carbon and everybody who helped bring AOSP to the DNA, including but not limited to- chad0989, flyhalf205, crpalmer, invisiblek, pio_masaki...
DISCLAIMER: Flash this ROM at your own risk- I am not responsible for voided warranties, bricked hardware, explosions, bugs, frustration, etc.
See 2nd post for information on diagnosing and reporting bugs. It includes a link to my detailed guide, including radio/reception info
CarbonRom is an aftermarket firmware based on the Android Open Source Project.
We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy. Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here.
Click to expand...
Click to collapse
Features:
-Android 4.3.1
-PIE
-Halo
-Active Display
-AOKP Ribbons
-More that haven't even been mentioned, and more to come!
---Feature infographics courtesy of reddit user wamen_noodles
Flashing Instructions:
-Download ROM and gapps
-Reboot into recovery- wipe cache, dalvik, data, and system
-Flash ROM, gapps and reboot
---I don't recommend dirty flashing, but if you do please do not report any bugs until you do a clean flash. For thorough details, see the link in my signature or in Reporting a Bug below.
Download:
CDMA: AFH
GSM: Just flash the GSM Patch over the CDMA build.*
Gapps: Official or Slim for dark UI support. Carbon states most gapps should work though.
Crpalmer's kernel version 4.7.4 should work fine, but please don't report bugs unless you're on the included kernel (you can just dirty flash the ROM to restore the stock kernel). I recommend the OndemandCRP governor and ROW I/O scheduler.
Old Builds:
CDMA ONLY 10/28: AFH
GSM ONLY 10/28: AFH
Source:
Carbon
Device tree
Vendor files
Kernel
*Flyhalf205's GSM Patch was modified to reflect recent changes and set Network Mode to GSM/WCDMA Preferred.
XDA:DevDB Information
[ROM][4.3.1][Carbon][Unofficial], a ROM for the HTC Droid DNA
Contributors
pyroguysf
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2013-10-27
Last Updated 2013-11-05
Reserved
Known Bugs:
-All CM 10.2 bugs: please search the CM thread before posting.
-Carbon Fibers occasionally FCs on boot
-Two seemingly identical phone apps to choose from when using a dialer link
-Turning off quick settings causes repeated System UI FC
-You tell me
So far everything has been minor and hasn't noticeably affected the performance, stability or features of the ROM. Don't expect this to move past what I'd consider "beta" because I don't have the know how to really fix any of these, so it's up to Team Carbon's changes since I know at least some of these aren't specific to us anyway. If there's any major problems, I'll try to make an attempt to work with Team Carbon or another more knowledgeable dev to sort things out.
Reporting a Bug:
Generally, only report a ROM bug if it can be replicated after a clean flash without any 3rd party kernels or apps. See this guide for more details. If it's apparent you didn't follow at least some of these instructions or use search, I will probably only laugh and make fun of you- guides and search boxes exist for a reason.
first
munchy_cool said:
first
Click to expand...
Click to collapse
I know you're going to say something about it so I'll just get it out of the way- No the hand waving isn't enabled for active display and no I don't know how to include it, lol.
pyroguysf said:
I know you're going to say something about it so I'll just get it out of the way- No the hand waving isn't enabled for active display and no I don't know how to include it, lol.
Click to expand...
Click to collapse
ha ha ..actually there is no option for that ..that's what active display is supposed to do.I will try and download the rom once am home and test it. If it works i'll post and if it doesn't i shall remain quiet
Maybe we're both wrong? Looks like I spoke too soon because I just turned on pocket mode and it catches the hand wave no problem (other ROMs I've tried, pocket mode was extremely hard for me to trigger by any means). Either that or Carbon just tweaked it to their liking.
Edit: @munchy_cool From our avatars, you'd think we were in a Mustang forum... haha
I hate to sound like a moron... and I'm going to but, do any of the CM based roms (non-sense roms) utilize the headphone amp / beats audio?
I have been using Newts GPE rom for a few months now so I don't know if this had been implemented and I did look around for a while but honestly it would be easier if one person saw my post and replied to me lol
The headphone amp is a big deciding feature for me with roms, and I love CM alot too :/
Thank you
x70xchallengerx said:
I hate to sound like a moron... and I'm going to but, do any of the CM based roms (non-sense roms) utilize the headphone amp / beats audio?
I have been using Newts GPE rom for a few months now so I don't know if this had been implemented and I did look around for a while but honestly it would be easier if one person saw my post and replied to me lol
The headphone amp is a big deciding feature for me with roms, and I love CM alot too :/
Thank you
Click to expand...
Click to collapse
Beats is strictly a Sense thing- DSP Manager would be the AOSP equivalent. As far as I know the headphone amp is working and speaker amp is partially working, but both are 99% up to par with Sense IMO.
pyroguysf said:
Beats is strictly a Sense thing- DSP Manager would be the AOSP equivalent. As far as I know the headphone amp is working and speaker amp is partially working, but both are 99% up to par with Sense IMO.
Click to expand...
Click to collapse
Great! Thanks for the quick reply!
Gotta give this a try! :beer:
Edit: well it didn't like me as a gsm user, oh well.
Excellent
Æaa\../
pio_masaki said:
Gotta give this a try! :beer:
Edit: well it didn't like me as a gsm user, oh well.
Click to expand...
Click to collapse
Aww man, sorry. You'd know more about fixing that than I would, so do you think it might just be this line in the makefile? $(call inherit-product, vendor/carbon/config/common_cdma.mk)
I don't know if it'd like me including the GSM one in addition to CDMA, but I can try doing just a GSM one for you.
pyroguysf said:
Aww man, sorry. You'd know more about fixing that than I would, so do you think it might just be this line in the makefile? $(call inherit-product, vendor/carbon/config/common_cdma.mk)
I don't know if it'd like me including the GSM one in addition to CDMA, but I can try doing just a GSM one for you.
Click to expand...
Click to collapse
You'll want to call the gsm version and block the CDMA version. You'll also want to use the gsm M7 build.prop stuff concerning the radio, I kept two sets of those, one for CDMA and one for gsm and named each system.prop as I needed that version, then blocked the gsm or CDMA line for which ever build I wasn't doing. Messy but it worked for me.
That aside, don't worry about it as far as being for me, my DNA is sold tomorrow I think , just wanted one last hoorah with it and Carbon :thumbup:
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
You'll want to call the gsm version and block the CDMA version. You'll also want to use the gsm M7 build.prop stuff concerning the radio, I kept two sets of those, one for CDMA and one for gsm and named each system.prop as I needed that version, then blocked the gsm or CDMA line for which ever build I wasn't doing. Messy but it worked for me.
That aside, don't worry about it as far as being for me, my DNA is sold tomorrow I think , just wanted one last hoorah with it and Carbon :thumbup:
Click to expand...
Click to collapse
Well, I'd like to be able to include GSM users too, and with you as one of the more actively knowledgeable people, I'll take any tips while I can still get them. Even better if I can help you with that last hoorah. Tried my best to make those changes (the GSM m7 system.prop is like 5 lines versus 50 on the dlx- I was a little confused, lol), and provided I didn't create any errors, I should hopefully have a GSM build up in an hour.
@pio_masaki and any other GSM users can give this a shot if you want and let me know how it goes- http://www.androidfilehost.com/?fid=23196940996969845
Edit: Also posted a new CDMA build since yesterday's DNA and Carbon changes seems to have stopped the Carbon Fibers FC and restored accurate signal text- http://www.androidfilehost.com/?fid=23196940996969853
Flashed and played with this Rom it's bad ass can't wait for the amp to be fixed my phone always sounds like there is a blown speaker. There are no real issues though thanks for bringing carbon back to life brother!!!
Sent from my dlx using Tapatalk
coachcrey said:
Flashed and played with this Rom it's bad ass can't wait for the amp to be fixed my phone always sounds like there is a blown speaker. There are no real issues though thanks for bringing carbon back to life brother!!!
Click to expand...
Click to collapse
Yeah, the loudness is back, but I usually have to tweak DSP Manager to get it sounding right, although it varies from build to build.
Welp, flashed it last night around 1:30am, so far so good!!
Everything seems 100% perf! (VZW) Amp is working loud and actually louder/clearer than on sense
I flashed crpalmers 4.7.4 kernel though and i get system ui crashes every 5 seconds or so xD so I guess I will flash the original boot img
x70xchallengerx said:
Welp, flashed it last night around 1:30am, so far so good!!
Everything seems 100% perf! (VZW) Amp is working loud and actually louder/clearer than on sense
I flashed crpalmers 4.7.4 kernel though and i get system ui crashes every 5 seconds or so xD so I guess I will flash the original boot img
Click to expand...
Click to collapse
I've know for certain myself and at least have been running crpalmer 4.7.4 without problems, so I'm not sure what to say. Did you wipe dalvik/cache after flashing the kernel?
pyroguysf said:
I've know for certain myself and at least have been running crpalmer 4.7.4 without problems, so I'm not sure what to say. Did you wipe dalvik/cache after flashing the kernel?
Click to expand...
Click to collapse
Yes I did actually it's very odd, I flashed the original boot img and wiped cache/dalvik and rebooted and still said system ui crashes, then wiped caches again, flashed rom over again to refresh, sys ui still crashing, then wiped caches and system, and reflashed rom, still sys ui crashes xD
so I wiped everything, caches, data and system, and flashed rom again and now its fine... so its something in the data partition :/
I've noticed that CM12.1 is already out for many devices, do we have a developer with the Cyanogenmod team working with Hima?
Man I been wondering the same thing I'm so ready to flash lol
There's been zero mentioning of it so far. What with hima being so easy to make roms for, I wanted to see if any devs might let us know. I'm also curious if we'll see the phone get clocked back to 2ghz.
I would love to see this as well.
dmcgrath009 said:
I would love to see this as well.
Click to expand...
Click to collapse
I will second (or third or fourth) this motion!
It's easy to compile for this device if any of you want to learn how and release a ROM for CM12.
orangekid said:
It's easy to compile for this device if any of you want to learn how and release a ROM for CM12.
Click to expand...
Click to collapse
I would attempt it, but I have quite a few questions. I've done it for the M7 before with no problems (even had a thread with nightly builds etc.), but with the M9 being rather new, a lot of things are still up in the air:
No proprietary blobs (usually I would use TheMuppets, but they haven't updated blobs for M9...yet) I could probably pull these using another extract-files.sh from GitHub for the M9, but are all proprietary blobs the same between all M9 variations?
No MSM8994 AOSP kernel (that I can find)
Sprint hasn't released kernel source yet so there goes that option
Everything else is pretty self-explanatory though
orangekid said:
It's easy to compile for this device if any of you want to learn how and release a ROM for CM12.
Click to expand...
Click to collapse
Yeah, def. But is it even supported for cm12 yet?
calebcabob said:
Yeah, def. But is it even supported for cm12 yet?
Click to expand...
Click to collapse
It even makes me wonder was the m9 that bad of a review? The s6 has cm12 and it launched on the same day as the m9 . we should have had something by now Idk *Shrugs*
trev23sks said:
It even makes me wonder was the m9 that bad of a review? The s6 has cm12 and it launched on the same day as the m9 . we should have had something by now Idk *Shrugs*
Click to expand...
Click to collapse
Has nothing to do with that. Has to do with Verizon being asshoIes...locking their devices down like 17th century princesses in chastity belts. That's why GSM already has source available, and we don't
calebcabob said:
Has nothing to do with that. Has to do with Verizon being asshoIes...locking their devices down like 17th century princesses in chastity belts. That's why GSM already has source available, and we don't
Click to expand...
Click to collapse
This is the sprint section... Nothing to do with Verizon...
Sent from my 0PJA2 using XDA Free mobile app
cstrife999 said:
This is the sprint section... Nothing to do with Verizon...
Sent from my 0PJA2 using XDA Free mobile app
Click to expand...
Click to collapse
Haha! How the...?? That's funny - no idea how I ended up in here. I'm out.
calebcabob said:
Haha! How the...?? That's funny - no idea how I ended up in here. I'm out.
Click to expand...
Click to collapse
make the switch! then come back!
on a side note and since we are off topic now ^^ lol jk bud
I have cm 12.1 on my m8 and it runs so beautifully... I even activated it for a day just to use it and see what I was missing.. (thats right.. missing from an older generation phone). I will say that cm12.1 was a real treat but the data issues that plagued mine (and pretty much all of us m9 owners in b41 areas) were still there on the m8. Let me be clear that b41 worked better but i still had data drops and data inconsistencies. Plus single strength was equal to the m9. I really do believe sprint has (at least started to) fix their data provisioning issues on their end for the m9 because my data service has been much better.
deakelem said:
make the switch! then come back!
on a side note and since we are off topic now ^^ lol jk bud
I have cm 12.1 on my m8 and it runs so beautifully... I even activated it for a day just to use it and see what I was missing.. (thats right.. missing from an older generation phone). I will say that cm12.1 was a real treat but the data issues that plagued mine (and pretty much all of us m9 owners in b41 areas) were still there on the m8. Let me be clear that b41 worked better but i still had data drops and data inconsistencies. Plus single strength was equal to the m9. I really do believe sprint has (at least started to) fix their data provisioning issues on their end for the m9 because my data service has been much better.
Click to expand...
Click to collapse
Not surprising to hear...seeing how we're both running CDMA data. Booo...CM12 + CDMA = Very shaky data imo
calebcabob said:
Not surprising to hear...seeing how we're both running CDMA data. Booo...CM12 + CDMA = Very shaky data imo
Click to expand...
Click to collapse
Yea this was the first time I had/noticed the issue on cm12 with my m8. But i did run it stock for a few hours just after re-activating it so i could get the latest profile and prl, etc and I had unexplained data issues on stock too. It could just be my locations and the issues were not enough to drive you nuts really.
Now my N5 on sprint was bad a lot of times haha.. I loved the phone but it had its first triband growing pains. Still not as bad as users i know with the n5 on gsm network specifically tmo.. That wast truly bad.
Anyways, sorry about the OT. Back on topic now
It's coming!!!!!! https://github.com/Hima-Dev/android_device_htc_hima-common
Cm12 is in the works. About another month or so until it's really ready for daily use, though I can't say for sure what kind of luck we'll have with a sprint build.
A lot of the other devices are much easier to work on because htc released a ton of kernel sources for a lot of the international and Asian devices, but ZILCH for Sprint. That means we're unlikely to see a rom without sense for a while.
Well, that's not exactly true... With working RIL, we'll probably get a build not terribly long after everyone else, but let's just say my hopes aren't terribly high with htc seemingly being jerks about releasing a damn bit of useful code for the Sprint m9 (or any CDMA m9 for that matter)
I'd be happy with some decent radios, honestly. Struggling to get even a tiny bit of LTE signal in an area where my LG G2 was full LTE all the time after flashing a new radio makes this a little irritating...But that's a topic for another thread.
The first beta is here!!! Sprint version coming soon
http://forum.xda-developers.com/one-m9/orig-development/rom-cyanogenmod-12-1-beta-1-t3150777
Most of it is broken, and apparently they have to make a version separate from the cdma versions. Hopefully we'll have the same as the M8 where one build supports all devices. Still, cannot wait for nightlies.
asacado said:
Most of it is broken, and apparently they have to make a version separate from the cdma versions. Hopefully we'll have the same as the M8 where one build supports all devices. Still, cannot wait for nightlies.
Click to expand...
Click to collapse
I remember cm saying that were going to make a unified build for all versions of the phone when the started dev on the m8.. it would be strange for them to change their mind so hopefully we do get the same thing as the m8. I would also love to get the same amount of attention as the m8 does those builds are perfect.
No offense to OMJ. I am just suprised we have no other ROMS for this phone.
wytecaztle said:
No offense to OMJ. I am just suprised we have no other ROMS for this phone.
Click to expand...
Click to collapse
there's ViperOne, LeeDroid, and Insertcoin.
Aldo101t said:
there's ViperOne, LeeDroid, and Insertcoin.
Click to expand...
Click to collapse
For the Sprint version?
wytecaztle said:
For the Sprint version?
Click to expand...
Click to collapse
yep, right now the only one that supports sprint yet is ViperONE, because of the resent firmware update, we haven't got yet, but the first ones they put out prior to the update have sprint support, go to international thread and read up on it.
wytecaztle said:
For the Sprint version?
Click to expand...
Click to collapse
Aldo101t said:
yep, right now the only one that supports sprint yet is ViperONE, because of the resent firmware update, we haven't got yet, but the first ones they put out prior to the update have sprint support, go to international thread and read up on it.
Click to expand...
Click to collapse
LeeDROID v7.6.0 also supports sprint.
Why aren't these roms present in the Sprint section I wonder? Seems odd as nobody would think to check the international forums.
cstrife999 said:
Why aren't these roms present in the Sprint section I wonder? Seems odd as nobody would think to check the international forums.
Click to expand...
Click to collapse
easier for the devs to monitor one thread than a bunch.
Well they can do what Viper did and create a small thread with links then lock it
I blame htc lol
these forums are dead because of 2 reasons:
1) the M9 was not much of a upgrade from the M8
2) overheating issues
HTC took it on the chin w/ this one...
OMJ said:
these forums are dead because of 2 reasons:
1) the M9 was not much of a upgrade from the M8
2) overheating issues
HTC took it on the chin w/ this one...
Click to expand...
Click to collapse
yup...I think a lot of people didn't see the M9 as a real upgrade to the M8 and only for those who didn't jump from M7 to M8 combined with the horrible press about the overheating (I've yet to experience) and camera (love the camera updates for what I use it for) and whining about it not being 4k (seriously, who needs that on a phone?) means it's not been a very popular device.
Screw 'em...I think it's a huge upgrade from the M7, especially the camera (even in it's original iteration).
Many thanks to @OMJ @benny3 and @chas123 for supporting this device.
OMJ said:
these forums are dead because of 2 reasons:
1) the M9 was not much of a upgrade from the M8
2) overheating issues
HTC took it on the chin w/ this one...
Click to expand...
Click to collapse
This maybe true but another thing to point out is that this phone is so complete that there is hardly anything left to mod or add. I'm mean the only thing left for you to add to the phone is to add the 5.1 update to your ROM. Other then that your ROM is so complete its been on REV 24 for over a month with nothing else to add or tweak. Of course there is the point you already made that this phone being so close to the M8 that your ROM was already matured through the M8 days.
barleysoda said:
This maybe true but another thing to point out is that this phone is so complete that there is hardly anything left to mod or add. I'm mean the only thing left for you to add to the phone is to add the 5.1 update to your ROM. Other then that your ROM is so complete its been on REV 24 for over a month with nothing else to add or tweak. Of course there is the point you already made that this phone being so close to the M8 that your ROM was already matured through the M8 days.
Click to expand...
Click to collapse
I could agree, but I'm still looking for a CM/AOSP flavor to rock on mine... And not to mention before the latest updates, we could still flash all those feature loaded ROMs. But lately, I'm hesitant to flash anything other than BadBoyz.
Sent from my HTC1(M9)
barleysoda said:
This maybe true but another thing to point out is that this phone is so complete that there is hardly anything left to mod or add. I'm mean the only thing left for you to add to the phone is to add the 5.1 update to your ROM. Other then that your ROM is so complete its been on REV 24 for over a month with nothing else to add or tweak. Of course there is the point you already made that this phone being so close to the M8 that your ROM was already matured through the M8 days.
Click to expand...
Click to collapse
This is especially true when it comes to theming. You pretty much can theme it the way you want very easy. Im not a big themer or theme design, this latest Android 5.1 is very difficult to theme. Since its still new quite a bunch of apks are not compiling correctly and im not that skilled yet or have the time lately to figure out why, LOL. Other then the Viper Theming threads not much Theming has been going on throughout all HTC M9 versions.
You are better running badboyz for sprint, our firmware is extremely sensitive and with so many international versions using their base, our lte issues arrise of we aren't using a rom that supports our phone properly.
asacado said:
You are better running badboyz for sprint, our firmware is extremely sensitive and with so many international versions using their base, our lte issues arrise of we aren't using a rom that supports our phone properly.
Click to expand...
Click to collapse
Traded my flex2 for a HTC One m9, rooted it, unlocked it, and then I installed badboyz the very first day. Love it. I'm so used to having cm/aosp on all my devices and I customize the crap out of them but I have to say that I have hardly seen any lag or performance issues on this phone. The phone gets pretty warm when doing heavy tasks like playing a game and what not but I don't find it any different then other devices doing the same tasks.
Either way, I love the m9. It's a well built solid device. I jumped at the chance to trade haha. Their loss
Sent from my 0PJA2 using Tapatalk
I will say this is probably the least active forum I have seen out of all the HTC's I have own which is every flagship for Sprint since the evo 4G (even going back to TP1 & TP2). That being said, OMJ's badboyz is awesome I have been using it since I got the phone. There is also no red text hboot and custom splash screens just like my M8 had. I like this phone, while really not much different from my M8 besides the camera it's not as big of fail as people make it out to be. I'm hoping the M10 is a nice refresh and hopefully HTC is done with trying camera gimmicks. I would like to see higher resolution screen next year & wireless charging.
Sim-X said:
I will say this is probably the least active forum I have seen out of all the HTC's I have own which is every flagship for Sprint since the evo 4G (even going back to TP1 & TP2). That being said, OMJ's badboyz is awesome I have been using it since I got the phone. There is also no red text hboot and custom splash screens just like my M8 had. I like this phone, while really not much different from my M8 besides the camera it's not as big of fail as people make it out to be. I'm hoping the M10 is a nice refresh and hopefully HTC is done with trying camera gimmicks. I would like to see higher resolution screen next year & wireless charging.
Click to expand...
Click to collapse
The majority goes on in the overall m9 forum and not sprint as I guess devs don't want to check multiple forums.
Sent from my 0PJA2 using XDA Free mobile app
I really don't see where development is lacking. As many have said there are quite a few roms in the main m9 forum that offer sprint support. If you look at the cm development device tree sprint support is added. What's missing?
LeeDroid, and Insertcoin drains horrible.......... lol any suggestion?