This is the Thread for discussion about Cm12.1 for Atrix HD
As you can see, it is official cm12.1 and i am just a person who maintains this thread.
The following people are maintainers for this device : @epinter
The following people and/or organizations have contributed to this device: @Hashcode0f, @dhacker29, @Skrilax_CZ, @kabaldan
Code:
/*
* ~ Please READ ME ~
*
* I do not guarantee any successful flashing. I am not responsible
* for bricked devices, dead SD cards, or a broken device. YOU are
* choosing to make these modifications, and if you point the finger
* at me for messing up your device, I will laugh at you. But I will try
* my best to explain all the necessities, so you won't mess up your Device.
*
* ~ END OF AGREEMENT ~
*/
Instructions:
! Download the zip file
! Make sure you have atleast 50% battery left
! Make sure you have backed up your current rom
! factory reset your device, erase delvik cache and format /system (if you are using philz recovery, use clean to install new rom)
! flash the ROM zip, GApps zip
! reboot device
! First boot takes around 10 - 15 minutes. Its normal.
For More details, please visit Cyanogen wiki page of Atrix HD
Download cm12.1 from here
Download GApps from here
Click here for changelog
Plz keep us posted
i using rom cm12.1 very fast but ahau times reboot buil5/5/2015
I'm using 2/5 build.. Can you confirm if Facebook is installing? I tried installing it but after soo much time in 'installing' it gives unknown error app cannot be installed..
Sent from my ATRIX HD using XDA Free mobile app
Does anyone use the dynamic gapps by banks? I wanted to flash cm12.1 but i noticed that the link doesnt show minimal gapps anymore so im kind of hesitant about where to get my gapps
chococomaxim said:
Does anyone use the dynamic gapps by banks? I wanted to flash cm12.1 but i noticed that the link doesnt show minimal gapps anymore so im kind of hesitant about where to get my gapps
Click to expand...
Click to collapse
You can also search Android file host
Sent from my MB886
Phone never goes to deep sleep... Is it just me or is it a common cm 12.1 bug?
Edit: it happens even if gapps are not flashed!
Sent from my ATRIX HD using XDA Free mobile app
There is a problem playing movies videos etc. It will get to the point of freezing until it reboot itself.
It's a shame about this rom...it has much potential.. Sigh
Sent from my MB886 using Tapatalk
Aingaran said:
This is the Thread for discussion about Cm12.1 for Atrix HD
As you can see, it is official cm12.1 and i am just a person who maintains this thread.
The following people are maintainers for this device : @epinter
The following people and/or organizations have contributed to this device: @Hashcode0f, @dhacker29, @skrilax, @nadlabak
Click to expand...
Click to collapse
Does this thread help or dilute help for AHD users?
Just a consideration about the possible downside of having a separate thread for AHD/CM12.1. As I mention here http://forum.xda-developers.com/showpost.php?p=60552125&postcount=3118 "As to a dedicated MB886 thread; it would be nice but our cohort (MB886 users actively testing CM12.1) is small and if we did that we would be less able to pick the brains of the more experienced Devs/hobbyists who are tweaking similar ROMs from the same phone family. At least we have kabaldan and others working on issues related to our phone that were reported here and through Jira.".
Unless the Devs prefer a separate thread we might be better off in the shared thread - since those more experienced and greater in # users wont come here to help us we'll have to monitor that thread anyhow. Food for thought.
Also, some minor corrections and cleanup suggested for OP;
- skrilax should be Skrilax_CZ (which may be why the mention link is broken and pointing to different user named skri. In any event you don't want the mention system referring to wrong user.
- nadlabak mention link also seems to be broken and sending contact to wrong user, in this case one named nad. I know nadlabak is the reference used in the old CM11 thread but he has been posting lately as his palindromic doppelganger "kabaldan". Using kabaldan might straighten out that broken mention link.
IronTechmonkey said:
Does this thread help or dilute help for AHD users?
Just a consideration about the possible downside of having a separate thread for AHD/CM12.1. As I mention here http://forum.xda-developers.com/showpost.php?p=60552125&postcount=3118 "As to a dedicated MB886 thread; it would be nice but our cohort (MB886 users actively testing CM12.1) is small and if we did that we would be less able to pick the brains of the more experienced Devs/hobbyists who are tweaking similar ROMs from the same phone family. At least we have kabaldan and others working on issues related to our phone that were reported here and through Jira.".
Unless the Devs prefer a separate thread we might be better off in the shared thread - since those more experienced and greater in # users wont come here to help us we'll have to monitor that thread anyhow. Food for thought.
Also, some minor corrections and cleanup suggested for OP;
- skrilax should be Skrilax_CZ (which may be why the mention link is broken and pointing to different user named skri. In any event you don't want the mention system referring to wrong user.
- nadlabak mention link also seems to be broken and sending contact to wrong user, in this case one named nad. I know nadlabak is the reference used in the old CM11 thread but he has been posting lately as his palindromic doppelganger "kabaldan". Using kabaldan might straighten out that broken mention link.
Click to expand...
Click to collapse
OP updated
Reviewing posts I realize my last one came off more critical than was intended so I've returned to adjust the tone.
It's not like I don't appreciate the thread. In fact there are notable benefits of having a thread that is device and ROM specific. It was just that with only about 4 or 5 AHD users regularly dipping in to test CM12.1 and report in these threads I was concerned that an additional thread would water us down, but the opposite may be happening. It seems that some AHD/CM12.1 users that were not participating in the other thread have found this thread. Even if we have to follow 2 threads to track bugs and issues, if this thread keeps bringing new AHD users into the conversation that is great. so Thanks!
What I'll start doing is posting test results in both this thread and in the the other one http://forum.xda-developers.com/droid-razr-hd/development/lollipop-5-0-runs-msm8960s-kkbl-t2939832
IronTechmonkey said:
Reviewing posts I realize my last one came off more critical than was intended so I've returned to adjust the tone.
It's not like I don't appreciate the thread. In fact there are notable benefits of having a thread that is device and ROM specific. It was just that with only about 4 or 5 AHD users regularly dipping in to test CM12.1 and report in these threads I was concerned that an additional thread would water us down, but the opposite may be happening. It seems that some AHD/CM12.1 users that were not participating in the other thread have found this thread. Even if we have to follow 2 threads to track bugs and issues, if this thread keeps bringing new AHD users into the conversation that is great. so Thanks!
What I'll start doing is posting test results in both this thread and in the the other one http://forum.xda-developers.com/droid-razr-hd/development/lollipop-5-0-runs-msm8960s-kkbl-t2939832
Click to expand...
Click to collapse
I know what you mean..it is kinda frustrating to not have a dedicated thread for our device
Sent from my MB886 using Tapatalk
Just for your interest:
1st May build seems to be completely stable for me.
I have no reboots at all, descent battery life, nearly no bugs. But I should say, I am not a heavy user.
The only one bug that I have is that sometimes the screen does not power up at incoming call, and I have to press power several times to turn it on. But I have had this bug on pretty all custom roms for AHD.
So, I think that I will stay on this build.
Legza said:
Just for your interest:
1st May build seems to be completely stable for me.
I have no reboots at all, descent battery life, nearly no bugs. But I should say, I am not a heavy user.
The only one bug that I have is that sometimes the screen does not power up at incoming call, and I have to press power several times to turn it on. But I have had this bug on pretty all custom roms for AHD.
So, I think that I will stay on this build.
Click to expand...
Click to collapse
Same for me, I was having the screen-on issue with Blisspop too.
What's the word ppl? Any comments on recent build?
On 6-4 nightly...and on a reboot said no sim card. So I rebooted and issue was gone
marknoll said:
On 6-4 nightly...and on a reboot said no sim card. So I rebooted and issue was gone
Click to expand...
Click to collapse
Across both CM11 and CM12 it is not uncommon to have media sync issues immediately after installation. Normally I've experienced this as ringtones that are absent until after an additional reboot. Maybe this was a similar issue.
[EDIT] Forehead slap. I thought you wrote SD rather than SIM, so these issues might not be related but, for what it is worth I did recently see someone else report about something similar where the SIM was not detected for a while (forget where).
installed CM12.1 ver 5.1.1 in Atrix HD with Gapps and not work Play Store, Then download Play Store in: http://forum.xda-developers.com/showthread.php?t=1996995 and not work ???
Any can help
Edit: Not have the gapps "Google Play Services", solution; download and install this apk, after working Play Store, also install other apk that you need
I was told that I should've recvd about ten texts and I never got them. So I did a hard reboot then all of a sudden they showed up. It went through the "android is upgrading" Wth?
Sent from my ATRIX HD using Tapatalk
Related
These are UNOFFICIAL nightlies of CM9 for the Droid Incredible
drk_hd has thrown together an awesome rom here: http://forum.xda-developers.com/showthread.php?t=1558923
But all of the same bugs still exist since its based off the same code.
I've done is scripted his build instructions posted here: https://github.com/drkhd/android_device_htc_inc/blob/ics/README.md
Also have added a few tweaks here and there
Follow the twitter feed here which should link you to the latest successful build after it is done: http://www.twitter.com/invisiblek_cm
Or check out this link to find the latest 'successful' build: http://goo.im/devs/invisiblek/dinc/cm9.unofficial.nightlies
goo.im sometimes take a few minutes (up to a half hour sometimes) to actually replicate the files that are uploaded. Please be patient.
Latest gapps here: http://goo.im/gapps
All the necessary rules apply here: I offer official no support here nor take no responsibility for you, your phone or who you may injure by throwing your phone in a fit of rage.
NANDROID FIRST!!! These are extremely experimental!
Major thanks to:
cyanogen and his awesome team for all their work
the evervolv team (MongooseHelix and drewis) for their device tree and many other things that made this possible
drk_hd for mashing this stuff up and putting together a guide on how to build it
cayniarb for the kernel and all the work he does for our devices
s0up and all the goo.im guys
many others i'm sure i'm missing...
ISSUES
Code:
[SIZE="4"]
- Camcorder doesn't work
(apparently there's a 3rd party market app that will work)
- Some people are experiencing freezes when unplugging
Please track that issue here: [url]http://tinyw.in/JUIb [/url]
- Others??
[/SIZE]
CHANGELOG
Code:
[SIZE="4"]
6-21-12
- back to the inline kernel. compiled with -O3 but using the old toolchain
6-20-12
- using a prebuilt kernel now. built with linaro gcc 4.7
6-18-12
- tweaked sd/emmc read_ahead: [url]http://tinyw.in/czFp[/url]
6-17-12
- MMS fixed upstream: [url]http://review.cyanogenmod.com/#/c/17822/[/url]
5-30-12
- another fix due to an overlay that disabled some pretty effects
commit here: [url]http://bit.ly/L3bFF2[/url] [B](thanks mamarley!)[/B]
5-28-12
- updated adreno drivers from CAF
- notification power widget LED flashlight now enabled
5-27-12
- applied a fix for the gpu regression detailed here: [B](thanks mamarley!)[/B]
[url]http://review.cyanogenmod.com/#/c/16028/[/url]
- enabled torch.apk (still not in notification power widget)
5-26-12
- added a slightly modified kernel that contains several cpu governors
5-24-12
- fixed sensors (prox, brightness, accelerometer, etc)
was using drk.hd's old device tree
- goo'ified the rom so it shows in goo-manager
[/SIZE]
Quick Links
Code:
[SIZE="4"]
Twitter feed for builds: [url]http://www.twitter.com/invisiblekcm9ka[/url]
Links to all nightlies: [url]http://goo.im/devs/invisiblek/dinc/cm9.unofficial.nightlies[/url]
Gapps: [url]http://goo.im/gapps[/url]
My github: [url]http://www.github.com/invisiblek[/url]
Unofficial changelog: [url]http://cm-kang.appspot.com/inc/ics[/url]
[/SIZE]
Thank you! I was hoping someone would do this. Crackflasher's gotta get his fix ya know
nice to see this, Thanks for your contribution .
Crackflashers will be able to leave rehab now, nicely done!
Sounds good I've been eager for a cm9 update, I'm going to flash this soon
Sent from my ADR6300 using Tapatalk 2
Accelerometer doesn't rotate screen on latest.
xport said:
Accelerometer doesn't rotate screen on latest.
Click to expand...
Click to collapse
+1 I can confirm that also.
xport said:
Accelerometer doesn't rotate screen on latest.
Click to expand...
Click to collapse
yep and the LED isn't working here
Can someone clarify - is "official" CM implementation of ICS for DInc being worked on? Or has DInc been dropped from the list of official CM targets for ICS due to some reasons (obsolete/lack of driver binaries/etc)?
It's not supported mostly because there's no maintainer to submit patches to the CM team The same for other older phones like Evo. Now there may be other reasons but this is the primary one.
Woah, let's not start rumors. http://forum.xda-developers.com/showthread.php?p=24081082 read that one, as well as mine on the two pages before that.
In essence, we have one maintainer, CUViper, and he's busy with work. Once it settles down, he'll try and get us up and running. Drk.hd is doing his best to get as much up as possible for CUViper to look at through Gerrit. Meanwhile, I'm just helping out where I can, mainly by troubleshooting and answering questions like these. Not much else I can do with no computer.
Tl;Dr yes it's being worked on. Eta: none. Promises for getting official CM9 on the Inc: see answer for eta.
Editorial side note @invisblek: since you got this at goo.im, why don't you make it Goo Manager compatabile (or ROM Manager compatible)?
Happy to have some sort of Cm9 than none. Weather or not it gets supported.
Sent from my ADR6300 using Tapatalk 2
Looks like proximity sensor (turning screen on and off during calls when moved away and close to face) is not working either.
Great work, glad to see this thread open up and hope that things progress.
new build coming up
sensors fixed (i was using drk.hd's old build method)
prox, brightness, accelerometer, etc
goo-inside.me'ified too
With the builds previous to the one you just mentioned I've been having force restarts. Besides that and the rotation issue, it's beatiful.
Great work!
@invisiblek, you don't have to upload the md5 file at goo, since it automagically creates and displays it. Goo Manager app actually checks and compares them, too.
warpurlgis said:
With the builds previous to the one you just mentioned I've been having force restarts. Besides that and the rotation issue, it's beatiful.
Great work!
Click to expand...
Click to collapse
Does it reboot all the way to your bootloader or just the cm boot screen?
If the former, I'd be interested in seeing your /proc/last_kmsg after one of these reboots. The latter, I'd recommend a data wipe.
PonsAsinorem said:
@invisiblek, you don't have to upload the md5 file at goo, since it automagically creates and displays it. Goo Manager app actually checks and compares them, too.
Click to expand...
Click to collapse
Long gone are the days of doing things manually I suppose.... thanks Pons
Invisiblek my God you have been gone so long that I don't think a lot of people remember you were a legend here when it came to dinc kernel development and a tie for the best with Chad's so let me first say I am stoked to see tour return. Second I just finished downloading your first nightly and I'm gonna report back to you about it after I flash. Lastly a question for ya and I'm sure is on all the minds of anyone that ever uses your gb kernels....any chance of you taking stab at updating your work and making an ics kernel for us dinc users. I mean dude I'd be happy honestly if you just did a couple of betas just to get the bugs out and then made one final release. I'd be like a giddy school boy on the night before Christmas. You shouldn't of seen my eyes when I was reading pons reply and he said your name I was like huh that can't be him and then I went back to op and checked out your profile and long behold it was you. Anyway ty for all your work now and in the past in my eyes your a legend with dinc development.
Sent from my ADR6300 using xda premium
wetbo529 said:
Invisiblek my God you have been gone so long that I don't think a lot of people remember you were a legend here when it came to dinc kernel development and a tie for the best with Chad's so let me first say I am stoked to see tour return. Second I just finished downloading your first nightly and I'm gonna report back to you about it after I flash. Lastly a question for ya and I'm sure is on all the minds of anyone that ever uses your gb kernels....any chance of you taking stab at updating your work and making an ics kernel for us dinc users. I mean dude I'd be happy honestly if you just did a couple of betas just to get the bugs out and then made one final release. I'd be like a giddy school boy on the night before Christmas. You shouldn't of seen my eyes when I was reading pons reply and he said your name I was like huh that can't be him and then I went back to op and checked out your profile and long behold it was you. Anyway ty for all your work now and in the past in my eyes your a legend with dinc development.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Haha thanks. I'll be honest though, much of the work I did on kernels was kanging other peoples' code though.
I've been planning to roll a kernel one of these days...
Is there a ICS kernel we can run with this? I tried the incredkernel ics and as soon as the boot screen loaded phone went blank.
Sent from my ADR6300 using xda premium
Okay, I got a couple PM's asking me to open an own thread, as the old CM 10.1 Bug Thread isn't updated anymore and the OP hasn't been online since February 2nd.
So here you go.
For logcats, development-related questions (e.g. implementation discussions) continue to use the thread in the dev discussioin section.
In this thread there won't be any posting restrictions.
Update: I've released a CM10.1 ROM which should fix most of the apparent issues.
More details in the thread: http://forum.xda-developers.com/showthread.php?t=2265329
Edit: this post isn't needed anymore.
You'll find the known bugs and fixes in the second post of the thread linked above.
I would like to test it. But I'm on old bootloader
Sent from my LG-P990 using xda premium
Okay guys, I think I fixed the call rejecting issue, at least it now works for me now.
Download: http://tonyp.hopto.org/cm-10.1-20130416-UNOFFICIAL-p990.zip
I need to make sure that I didn't break it for other Basebands, so please test if you can reject calls and report with your baseband.
If it doesn't work for you on this build please try the yesterdays one to see if there's any difference.
Desticus said:
I would like to test it. But I'm on old bootloader
Click to expand...
Click to collapse
Yes, I'm sorry but I can't build everything for both bootloaders right now.
All that stuff takes lots of time, and I need to focus on my own test builds, I hope you understand.
I am positive that I'll release a stable build, soon.
-----------------------------------
Hello TonyP:
I tried the testbuild, day 16.
And apparently the red frame, to completely gone or so I think.
Can you confirm that?.
As for gapps:
use the usual:
http://goo.im/gapps/gapps-jb-20121212-signed.zip
or showing us the goomanager:
gapps-jb-20130301-signed.zip
Thank you for your progress in the ROM.
Greetings.
tonyp said:
Okay guys, I think I fixed the call rejecting issue, at least it now works for me now.
Download: http://tonyp.hopto.org/cm-10.1-20130416-UNOFFICIAL-p990.zip
I need to make sure that I didn't break it for other Basebands, so please test if you can reject calls and report with your baseband.
If it doesn't work for you on this build please try the yesterdays one to see if there's any difference.
Yes, I'm sorry but I can't build everything for both bootloaders right now.
All that stuff takes lots of time, and I need to focus on my own test builds, I hope you understand.
I am positive that I'll release a stable build, soon.
-----------------------------------
Click to expand...
Click to collapse
Hey Tony Thanks for the great work, I have used your previous build, call rejecting is working fine with the first build. Downloading the current 2nd build.
Just a note: When on call if the speaker is activated, the opposite person voice seems to echo for them, this was an issue on cm10 with pengus rom also, not sure if others have reported.
Baseband- v30a
Ril- Default.
kekks said:
Hey Tony Thanks for the great work, I have used your previous build, call rejecting is working fine with the first build. Downloading the current 2nd build.
Just a note: When on call if the speaker is activated, the opposite person voice seems to echo for them, this was an issue on cm10 with pengus rom also, not sure if others have reported.
Baseband- v30a
Ril- Default.
Click to expand...
Click to collapse
Just wanted 2 say Tony that i'am testing your latest build of cm10.1 and it works helluva smooth
Everything works as it should,smoothest rom so far :good:
Tony,
Do you think HDMI output can also be corrected?
Just flashed it. No problems so far.
tonyp which kowalski kernel do you use? i don't see the kowalski manager. can I flash the latest exp?
Guys, I especially asked you to test call rejecting and post the result with your baseband - and there's not a single reply regarding that.
I do not care if it's smooth or the best or whatever, I wanna make progress with fixing the bugs as long as I got some spare time.
If no one helps in fixing bugs I'll pull the public testbuilds and we do it in a closed testing circle (which will take longer) - that's up to you.
chp2 said:
Tony,
Do you think HDMI output can also be corrected?
Click to expand...
Click to collapse
It can, yes. But it's a mess, unless we get the decompiler by a friends of pengus I doubt we will look further into it.
More details in the dev discussion section.
optimusG said:
Just flashed it. No problems so far.
tonyp which kowalski kernel do you use? i don't see the kowalski manager. can I flash the latest exp?
Click to expand...
Click to collapse
Oh yes, this is important:
Flash the latest pengus kernel on top of this ROM if you want to use it as a daily driver!
There's just a testkernel included.
Just to be sure - it'll need the ICS-bootloader/partition table, correct ? I'm gonna hijack my son's p990 in 6-7 hours so I can test on it all night. If I remember correctly its on v10a BB.
These typos came from my Nexus 7
Reptilez_DK said:
Just to be sure - it'll need the ICS-bootloader/partition table, correct ? I'm gonna hijack my son's p990 in 6-7 hours so I can test on it all night. If I remember correctly its on v10a BB.
These typos came from my Nexus 7
Click to expand...
Click to collapse
Downloading the testbuild too, will flash it soon running V30A BB.. But call rejecting... Am I right if this is what you mean by it:
- Make someone call
- Reject the call
If so, I can have it tested and brought you the results within the next hour...
PS: Good thing this isn't in the development section = noobs allowed here yaaay
Before to annoy Tony, anyone experience very slow UMS mode file transferts in both ways (read & write to flash) on CM10.1?.
I can't write at more than 6MB/s and read at 10MB on my class10 SD (no matter of I/O scheduler). The same SD does 15MB write on ICS and 10MB on CM10.
Okaaaay, flashed it over full wipe, as mentioned with V30A BB. Called up my phone from another phone, rejected it and it went well. If that was a proper test: Success
PS: For heavens sake, with the final CM10.1 release, please do make an option to disable that CRT animation. Every time I see that animation I am seconds away from throwing the phone out the window. Makes me crazy every time
Edit: This is impossible to become a daily driver. Why? Go outside. Stand in the sun. Pick up your phone. Turn it on. Good luck guessing where the icons are on your screen. Brightness goes so low, that I can barely see anything while indoors, imagine outside then.
PA CM10 will always shine on my phone and thats what I'm going to let it do for a long time, a very long time. Bye-bye CM10.1
I can confirm it works with V30A as well.
Natalya, give it is some time, wait till the final product has arrived. That brightness thing was a fail by Google, nothing to do about it.
I have dual boot on my phone, PA11 as the main and CM10.1 testbuilds as secondary. Honestly, I am having difficulties seeing a CM10.1 ROM becoming my daily driver too, but penguins can make a lot of things change, we all know that
I just checked it on V30A as well with the build from post #4, and I can say that call reject works flawlessly.
I know that this isn't the purpose of this testing build, but I just wanted to say that automatic NITZ fix doesn't work for me and even though it detects that my timezone is GMT +3 the time itself is GMT. (I don't even know if that fix is already implemented here so if it isn't, my bad )
And anyways great work Tony!
Call reject on V30a working flawlessly here too
guys a question.
red frame is displayed? In the version of day 16.
by that I do not appear.
with 15 if. that was experimental as tonyp said
greetings and thanks.
clashman90 said:
guys a question.
red frame is displayed? In the version of day 16.
by that I do not appear.
with 15 if. that was experimental as tonyp said
greetings and thanks.
Click to expand...
Click to collapse
Disabled on version of the 16th
Is it just me or by setting the phone to automatic brightness, the low brightness bug disappers.
Sent from my LG-P990 using xda premium
About Carbon
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. and on our Gerrit CarbonDev Gerrit.
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, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
****************** All links below this are UNOFFICIAL builds ******************
GAPPS
CWM 6.0.4.4 w/ swipe - Heimdall
TWRP 2.6.3.0 touch recovery w/ working AROMA touch (N5110)
ROM Downloads:
Initial Release
Changes:
-Initial Release
Jan 26th
Changes:
-Fix interface crashing
-Fix back camera freezing
Feb 2nd
Changes:
-Fixed electron beam screen off animation
-Upstream Sync
Feb 7th
Changes:
-Upstream Sync
-Fully working camera
Sources:
Rom Sources
My GitHub
Kernel Sources
Device Tree
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [N5110], a ROM for the Samsung Galaxy Note 8.0
Contributors
ryukiri
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Created 2014-01-24
Last Updated 2014-02-23
Reserved
How to Build this ROM
1) Setup Your Computer
Stop at
Code:
$ mkdir ~/android
$ cd ~/android
2) Download Source and Compile!
Code:
$ mkdir Carbon4.4
$ cd Carbon4.4
$ repo init -u https://github.com/CarbonDev/android.git -b kk
$ repo sync
$ . build/envsetup.sh
$ lunch (then select device from the list)
$ make carbon
3) Wait till it finishes and grab the zip from the out directory.
*Note: Syncing the repo will take a long time (downloads about 15 gbs of source), depending on your internet speed.
Reserved
Yes! Will flash and report right away!
Update: Took my time to test it, restore my apps, test them and mess a little with the options.
Update 2: After spending even more time with the newest release, this is practically a 0 issues ROM. I'll update my review along with new releases.
My micro SD 32gb works perfectly, if you have a 64gb card I would recommend to be formatted as "exFAT".
Smooth ROM and good RAM usage.
Packed with awesome features and I know there's more to come, CarbonRoms has A LOT of features. From changing status bar colors(and it's icons) to edit the menu and back buttons lights duration and remap the buttons(love it), see screenshots in the OP to have an idea.
No issues at all restoring my apps with Titanium Backup.
Stylus is working perfectly and this ROM has the Buttons settings for our device.
Camera is now working perfectly and more features are being added!
*Remember to do a full wipe clean install.*
Two things I want to mention, they're not annoying and they do not break the ROM at all.
*Interface option under Carbon Fibers crash, however given the fact that you guys are still merging those nice features I think it's kinda obvious. That's why I don't consider this annoying, nor ROM breaking, is just a work in progress. I thought I could mention this so no one get scare about it.
*This one is not even an issue is just a question, I use this device in landscape mode all the time, and every time I turn off the screen it rapidly rotates the screen before shutting down. There's no option for the effect to select or to turn it off, my question is: Is that one of the features to be added later within carbon fibers interface? I apologize, I used Carbon a lot with my N7 flo but I can't remember where that option was located.
*Both fixed on newest release*
NekroWolfen said:
Yes! Will flash and report right away!
Update: Took my time to test it, restore my apps, test them and mess a little with the options:
1.My micro SD 32gb works perfectly.
2.Smooth ROM and good RAM usage.
3.Packed with awesome features and I know there's more to come, CarbonRoms has A LOT of features.
4.No issues at all restoring my apps with Titanium Backup.
5.Stylus is working perfectly and this ROM has the Buttons settings for our device.
Two things I want to mention, they're not annoying and they do not break the ROM at all.
*Interface option under Carbon Fibers crash, however given the fact that you guys are still merging those nice features I think it's kinda obvious. That's why I don't consider this annoying, nor ROM breaking, is just a work in progress. I thought I could mention this so no one get scare about it.
*This one is not even an issue is just a question, I use this device in landscape mode all the time, and every time I turn off the screen it rapidly rotates the screen before shutting down. There's no option for the effect to select or to turn it off, my question is: Is that one of the features to be added later within carbon fibers interface? I apologize, I used Carbon a lot with my N7 flo but I can't remember where that option was located.
Click to expand...
Click to collapse
I found out about that crash during my 2 minutes with this rom..I'm assuming its because of them not finished merging stuff yet. I also see multiwindow and halo both on their gerrit so I'm guessing they'll merge those when its stable
I'm not sure since I've never used Carbon before, but I think what you are talking about is describing the bug thats in all of our roms. Its just the animation right? if you turn the screen back on, it stays in landscape mode? Can't test it because I'm not using this rom right now
And also, not sure if you noticed yet, but the back camera doesn't take photos..I'm almost 100% sure CM broke something in the common device tree because the back camera works in omni, so right now I'm figuring that out and transferring all the files to our own common device tree instead of using the one shared by all the smdk devices.
Edit: Confirmed interface crash is due to a recent commit. Should be fixed soon.
ryukiri said:
I found out about that crash during my 2 minutes with this rom..I'm assuming its because of them not finished merging stuff yet. I also see multiwindow and halo both on their gerrit so I'm guessing they'll merge those when its stable
I'm not sure since I've never used Carbon before, but I think what you are talking about is describing the bug thats in all of our roms. Its just the animation right? if you turn the screen back on, it stays in landscape mode? Can't test it because I'm not using this rom right now
And also, not sure if you noticed yet, but the back camera doesn't take photos..I'm almost 100% sure CM broke something in the common device tree because the back camera works in omni, so right now I'm figuring that out and transferring all the files to our own common device tree instead of using the one shared by all the smdk devices.
Click to expand...
Click to collapse
Yeah is the animation, I was just curious about it, it doesn't bother. The camera thing actually it doesn't bother me either because I can take pictures with any camera app from the app store.
It may be a work in progress, but for a initial release of this beta is pretty darn good. I'm still using it and I think I'm gonna keep it, I've been a huge fan of Carbon for awhile.
NekroWolfen said:
Yeah is the animation, I was just curious about it, it doesn't bother. The camera thing actually it doesn't bother me either because I can take pictures with any camera app from the app store.
It may be a work in progress, but for a initial release of this beta is pretty darn good. I'm still using it and I think I'm gonna keep it, I've been a huge fan of Carbon for awhile.
Click to expand...
Click to collapse
Oh okay btw, can you provide some (maybe 4 or so) good screenshots that I can put in the OP that show some of the carbon options / settings and stuff?
EDIT: Screenshots added.
Sent from my GT-N5110 using Tapatalk
A N5100 version would be very nice
redukt said:
A N5100 version would be very nice
Click to expand...
Click to collapse
I believe @tejkkarani will be taking care of that...if any unexpected things occur then he'll contact me and i will release it.
ryukiri said:
I believe @tejkkarani will be taking care of that...if any unexpected things occur then he'll contact me and i will release it.
Click to expand...
Click to collapse
Great! Great! Grat! :laugh:
New build is up with some relatively big fixes.
ROM is running great and yes it fixed the Carbon fibers, the camera still freezing thou(the ones on the playstore works btw).
NekroWolfen said:
ROM is running great and yes it fixed the Carbon fibers, the camera still freezing thou(the ones on the playstore works btw).
Click to expand...
Click to collapse
Really? For me the back camera doesn't freeze anymore..only the front.
Sent from my GT-N5110 using Tapatalk
ryukiri said:
Really? For me the back camera doesn't freeze anymore..only the front.
Click to expand...
Click to collapse
Rear camera & interface settings are working fine for me on the second release.
Nackler said:
Rear camera & interface settings are working fine for me on the second release.
Click to expand...
Click to collapse
ryukiri said:
Really? For me the back camera doesn't freeze anymore..only the front.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply, yes I too can confirm the camera works, I dirty flashed(just cache and dalvik)the update. Later on I did a full wipe clean install to make sure and voila. So now we can surely say there's no issues on this ROM.
NekroWolfen said:
Sorry for the late reply, yes I too can confirm the camera works, I dirty flashed(just cache and dalvik)the update. Later on I did a full wipe clean install to make sure and voila. So now we can surely say there's no issues on this ROM.
Click to expand...
Click to collapse
Both rear and front cameras working?
hermeticist said:
Both rear and front cameras working?
Click to expand...
Click to collapse
For me, only both cameras work in snapchat, hangouts video, oovoo, and skype...so far (same as the apps that worked in omni)
hermeticist said:
Both rear and front cameras working?
Click to expand...
Click to collapse
Yes sir, all working good, I really recommend this ROM, is the one I'm using.
NekroWolfen said:
Yes sir, all working good, I really recommend this ROM, is the one I'm using.
Click to expand...
Click to collapse
I can also confirm that we'll get official support since one of the devs have a note 8. I think he'll make a new thread when its ready..
ryukiri said:
I can also confirm that we'll get official support since one of the devs have a note 8. I think he'll make a new thread when its ready..
Click to expand...
Click to collapse
Nice! I'm noticing a lot of movement in the gerrit, those are good news. Carbon was my one of my favorite with the Nexus 7 flo, and I'm still surprised by how well and smooth it is on the Note 8, to be honest I wasn't expecting this ROM here, hence why I'm so excited.
About Carbon
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. and on our Gerrit CarbonDev Gerrit.
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, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Reserved
Also Reserved
Great work! Will try it out once finished modding it for XT905.
PS: Why not add it to DevDB?
levizx said:
Great work! Will try it out once finished modding it for XT905.
PS: Why not add it to DevDB?
Click to expand...
Click to collapse
I was told none of these moto's have DevDB. I've never used it myself, might be why haha.
arrrghhh said:
I was told none of these moto's have DevDB. I've never used it myself, might be why haha.
Click to expand...
Click to collapse
Yeah, maybe that
Quick question: I'm noticing quite apparent banding on my screen, especially on white background. And occational white noise splash while turning screen on, is it normal or just because I'm using it on XT905? Seems to be kernel related. I'm actually testing out both Gummy and Carbon, both have the same problem.
levizx said:
Yeah, maybe that
Quick question: I'm noticing quite apparent banding on my screen, especially on white background. And occational white noise splash while turning screen on, is it normal or just because I'm using it on XT905? Seems to be kernel related. I'm actually testing out both Gummy and Carbon, both have the same problem.
Click to expand...
Click to collapse
This is not made for xt905, so I'm not sure... Do you know how that device differs? I'm not aware of any forum for that device...
Edit - just checked, seems CM doesn't support it either? How does CM run?
arrrghhh said:
This is not made for xt905, so I'm not sure... Do you know how that device differs? I'm not aware of any forum for that device...
Edit - just checked, seems CM doesn't support it either? How does CM run?
Click to expand...
Click to collapse
Should be almost the same since this is just the GSM version of XT907. By apparent I actually mean noticable by human eyes (on while background). It's has to have something to do with the buffer or refresh rate.
Actually all ROMs with minor modification works fine. Not as smooth as I'd hope ie not smoother than debloated stock 4.1, but all things work, sans the occasional white-noise splash while turning screen on and the annoying band morie pattern.
Another question, do you have any plans ditching the emulated sdcard? It's quite pointless with just about 4GB after a full wipe and you have to share the space with apps.
I can't find out the download package of the xt907, is that true? I love carbon team, the black theme looks really nice
allen_ho said:
I can't find out the download package of the xt907, is that true? I love carbon team, the black theme looks really nice
Click to expand...
Click to collapse
We are working on migrating to a new download site + mirror... as our infrastructure was not up to the task (downloads were REALLY slow).
Hopefully the new setup can handle the load! I'll upload the last build to a mirror.
The banding issue affects all 4.4 roms. I don't know the technical details but it seems 3D acceleration is about 50% slower than 4.2 roms. Since nearly everything is composted in the GPU now, everything seems to suffer from poor frame rates and other graphical anomalies.
which is going to be better as a daily driver this one, or the JB?
allenrb2 said:
which is going to be better as a daily driver this one, or the JB?
Click to expand...
Click to collapse
Personally I would not recommend anything above 4.2.2/CM10.1 at this stage.
It's fine if you want a test drive, and it's stable enough to be a daily driver.
But it's not as fast and feature-complete. Unless you desperately want the new things (ART etc),
you might have to wait for a while (after official kk for RAZR M/HD) before KitKat roms really take off.
levizx said:
Personally I would not recommend anything above 4.2.2/CM10.1 at this stage.
It's fine if you want a test drive, and it's stable enough to be a daily driver.
But it's not as fast and feature-complete. Unless you desperately want the new things (ART etc),
you might have to wait for a while (after official kk for RAZR M/HD) before KitKat roms really take off.
Click to expand...
Click to collapse
I don't know, I prefer the 4.4 ROMs over 4.2. Personally faster for me. It's just right now if people want a lot of features there aren't going to be as many in 4.4 as there are for 4.2, though that will change. It's only because obviously JB has been out longer, but honestly feature-wise things are catching up.
flashing kitkat, because jb was force close city, hopefully its stable
motoroid7 said:
I don't know, I prefer the 4.4 ROMs over 4.2. Personally faster for me. It's just right now if people want a lot of features there aren't going to be as many in 4.4 as there are for 4.2, though that will change. It's only because obviously JB has been out longer, but honestly feature-wise things are catching up.
Click to expand...
Click to collapse
KitKat is buggier than JB4.2 with our dated kernel/driver, that's a fact. For me the banding issue is a showstopper, period. Feature-wise, I do agree it's getting better, but we live in the moment don't we? Like I said, it's cool if you use it just to test it out, you might even be of help to the devs in identifying bugs.
But if you are asking the question "should I use this as my daily driver", the answer is probably no, otherwise you wouldn't be asking the question in the first place.
the kitkat rom seems to be running ok so far
arrrghhh said:
We are working on migrating to a new download site + mirror... as our infrastructure was not up to the task (downloads were REALLY slow).
Hopefully the new setup can handle the load! I'll upload the last build to a mirror.
Click to expand...
Click to collapse
I found the KK nightly as the same path on GOO.im for JB, is it the same team working on?
http://goo.im/devs/carbon/xt907/nightly/
allen_ho said:
I found the KK nightly as the same path on GOO.im for JB, is it the same team working on?
http://goo.im/devs/carbon/xt907/nightly/
Click to expand...
Click to collapse
We are no longer using goo.im. I might've missed a nightly job, I'll doublecheck.
Edit - perhaps someone already fixed it... uploads are going to our new mirror.
Is there an error with the reported signal in the battery options? Cell standby shows very high percentage time without signal, upwards of %50. On stock based roms I have never seen more than %1 time without signal.
Dear XDA Community,
dear Demetris,
This Thread is about http://forum.xda-developers.com/showthread.php?t=2760771
Unfortunately it's not allowed to me to post anything in the official thread, cause I'm new here on the board. BTW: This hard rule makes it almost impossible to take part or give feedback to the developers. As well it's not allowed to send a direct message to anyone. I could imagine that many users actually would like to help to make things better, but that they gave up due to this hard restriction.
Okay, back to Topic.
I tested a lot ROMs for the P880 and the "LiquidSmooth v3.1" from Demetris ist the best for me. It has all this kind of stuff what I need. Pie control (customizable), Halo and it runs really smooth and fast. I would like to say big thanks for this nice ROM to Demetris! Great work, please keep going.
Some questions / minor bugs:
Battery
If the WiFi Module is activate it's not possible to charge the battery. That means I lose more energy as the charger can put in.
(Without WiFi) I'm not able to charge over 95% if the phone is on (Power on but screen is off).
Question
The thread title is saying that's about a official ROM. Is there I reason why I can't find this ROM at the official http://liquidsmooth.net page?
Do you plan to update / maintain this nice ROM in the near future? It would be really nice.
It would be nice if someone could point / link Dimitri to this Thread. My fear is, that he will not notice it.
Best & Thanks,
HDSteff
Official means @Demetris compiled it using official CyanogenMod sources and he is our maintainer on this project AFAIK he maintains liquidsmooth too... But I can be wrong...
Hey gerciolisz,
Thank you very much for your answers!
Maybe Demitris will find a minute to take a look into my thread.
Best,
HDSteff
1. You cant find a rom on official page because looks like they are stuck at v3.0 http://liquidsmooth.net/?page_id=12
2. Updates will come but as Liquidsmooth dont have an autobuild system i need to manually build the rom myself but doing that i lost 2 hdd's thus far due to heat & extreme usage
Im thinking about take back my P880 and try this rom
Sent from my Xperia Arc using xda-developers.com, powered by appyet.com
Hey Demetris,
Thanks a lot for your time & Feedback!
Best,
Steff
Could you post how many files do you have in Android folder. I have 46168 files / 917 folder for a grand total of 850.76MB. I'm wondering is it normal to have so many files, or did I miss something while flashing?
Edit: Nevermind, ES Explorer finally managed to count which folder it was. Apparently an old VLC installation had most of those files. I finally managed to delete all of it.
Go on.
Signal los / RIL issue
Hello,
I am running the Liquidsmooth version 3.2-2014-07-21, kernel 3.1.10-cm+ september 2 2014 and I have this issue. Im loosing network signal in "3G only" mode and it doesnt recovers (it frezes). If i use device in "2G only mode" mobile data connection only, the signal does not crash, and signal almost never goes down(2 times in week).
Devs any solution on this? RIL issue?
Regards and sorry for bad english.