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
will add thread in Index Thread..
in college after 5 hr's
Sent from my SM-N900 using Tapatalk
Tried this out and my kernel speeds were stuck at 96/384. I tried a few apps to change them but nothing worked.
matt1313 said:
Tried this out and my kernel speeds were stuck at 96/384. I tried a few apps to change them but nothing worked.
Click to expand...
Click to collapse
Hm, I am using the stock CM kernel - did you flash anything different, or just what is provided in this thread?
What was provided a and then your kernel. Both would not change values
Sent from my XT926
matt1313 said:
What was provided a and then your kernel. Both would not change values
Sent from my XT926
Click to expand...
Click to collapse
If you're using multiple apps to control it DON'T.
They are more than likely conflicting. NoFrills was the one recommended to me that I found was able to 'lock' the frequencies in the best.
arrrghhh said:
If you're using multiple apps to control it DON'T.
They are more than likely conflicting. NoFrills was the one recommended to me that I found was able to 'lock' the frequencies in the best.
Click to expand...
Click to collapse
I agree with you and I singled them all out, none worked, Not the built in performance, no frills or ROM tool box.
matt1313 said:
I agree with you and I singled them all out, none worked, Not the built in performance, no frills or ROM tool box.
Click to expand...
Click to collapse
Also, to be clear - you are using only ONE at a time, right? You aren't setting the built-in performance settings and NoFrills right? Once you install NoFrills, you should disable built in performance... etc...
No I'm doing correctly
Sent from my XT926
matt1313 said:
No I'm doing correctly
Sent from my XT926
Click to expand...
Click to collapse
I just reflashed the latest official clean (which is a few days behind for my device) and min 384, max 1512 in the built-in performance settings...
Not sure what to recommend at this point.
I didn't notice looking back through the posts if you mentioned you were flashing clean or dirty... I might have assumed poorly, you are clean flashing this?
The 2/2 nightly killed the bluetooth audio info for my car, going to see if 2/4 fixed it. I still have the occasional RAM problems/app killing but I've learned to live with it.
jldr said:
The 2/2 nightly killed the bluetooth audio info for my car, going to see if 2/4 fixed it. I still have the occasional RAM problems/app killing but I've learned to live with it.
Click to expand...
Click to collapse
I saw some people talking about AVRCP or w/e that protocol is on the CM gerrit... I think it's an upstream issue.
arrrghhh said:
I saw some people talking about AVRCP or w/e that protocol is on the CM gerrit... I think it's an upstream issue.
Click to expand...
Click to collapse
Do you know which version of AVCRP they are planning to implement? I haven't lost hope for someone to do 1.5, so we can finally browse files and playlists...
Sent from my XT925 using Tapatalk
StefanGA said:
Do you know which version of AVCRP they are planning to implement? I haven't lost hope for someone to do 1.5, so we can finally browse files and playlists...
Sent from my XT925 using Tapatalk
Click to expand...
Click to collapse
Isn't that something that can be only done at the level of the OS? We didn't have AVCRP1.3 until 4.3... I mean it would be awesome to see though!
jldr said:
Isn't that something that can be only done at the level of the OS? We didn't have AVCRP1.3 until 4.3... I mean it would be awesome to see though!
Click to expand...
Click to collapse
Indeed, this is an upstream issue.
I don't have any devices which use AVRCP, so I apologize I cannot test it at all.
I'm going to give this another try. Can I use your CM11 kernel as I enjoy the higher processing power?
matt1313 said:
I'm going to give this another try. Can I use your CM11 kernel as I enjoy the higher processing power?
Click to expand...
Click to collapse
Yes indeed!
Anybody able to type using swipe?
Im on the latest nightly.
Once i start to make a trail. The keyboards goes down and im not able to make it go back up, unless i go to another app.
Sent from my XT925 using Tapatalk
Related
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
nicholaschw said:
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
Click to expand...
Click to collapse
Again?? Aren't you tired? You went over it but people from the forum certainly not. I absolutely don't wanna argue with you but yesterday Jarred aka Universal SS droped the ARM thread and today you are back.And you are not the same person. Certainly not. You are like bad news,they never fail.
nicholaschw said:
After much practice into linux, i went for a C coding workshop for android. Basically i doubled, maybe even tripled my skill level. I finally am able to promise you something not pointless to this society which feels great hatred on me. I already got over this. I hope such releases can ease the scams in may.
The new kernel, based on ARM.'s vanilla kernel common, will be a 3.4.11 kernel. It features full tweaks to all over the source. Expect little features on initial release. The releases in the front will be focused entirely on fixing the kernel sources itself. The major merge all the way to the latest kernel version might have caused bugs to appear
Click to expand...
Click to collapse
Good for you. Hope it works out better this time and test thoroughly before release and after changes.
might is a understatement. It almost certainly will cause bugs to appear (the most common bug is it not booting when major changes are made to the kernel base). Also allot of the bugs from the kernel don't show symtoms they just go wrong and use a few more KB of memory or that bit restarts and causes a slight slowdown or it takes a few milliseconds longer to complete its task etc.
Edvin73 said:
Again?? Aren't you tired? You went over it but people from the forum certainly not. I absolutely don't wanna argue with you but yesterday Jarred aka Universal SS droped the ARM thread and today you are back.And you are not the same person. Certainly not. You are like bad news,they never fail.
Click to expand...
Click to collapse
Your comments (although highly entertaining) don't do much, at least he's trying. Your right though: some information is contradictory.
EDIT: Have a taco
xonar_ said:
Good for you. Hope it works out better this time and test thoroughly before release and after changes.
might is a understatement. It almost certainly will cause bugs to appear (the most common bug is it not booting when major changes are made to the kernel base). Also allot of the bugs from the kernel don't show symtoms they just go wrong and use a few more KB of memory or that bit restarts and causes a slight slowdown or it takes a few milliseconds longer to complete its task etc.
Your comments (although highly entertaining) don't do much, at least he's trying. Your right though: some information is contradictory.
EDIT: Have a taco
Click to expand...
Click to collapse
I don't get it
First it was Nicholas who said he's handing it to a new maintainer, who is Jared, right? And Jared mentioned it has been dropped support
http://forum.xda-developers.com/showthread.php?t=2034227&page=10
Good news for everyone!ARM. will drop support for the LG optimus black!Hope everyone is happy and have a nice day.(I'll still be in the forums though)Moderators please lock this thread
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
And now ARM Project's back?
Yes. He is fed up of this community. So, he turned over to support HTC. I give him my support for DNA. Now, i comeback to finish off what is destroyed, complete whats junk, and make it into something like a useful book into a library. Thanks xonar. I still have one last lesson. I did not learn drivers. edv, as said above, thats my motive. And, the reason why i comeback is the value of my life. You rather change an enemy into a friend rather than gaining more opposition.
nicholas for f--k sake !!! , once you have the kernel going post the topic and flatter yourself ,, you never learn do you
If this is going to turn into a flame war then I'll close it as that's not needed here but as it's posted in General, you should be here to discuss the topic. It's been explained why the other one was dropped but if nicholaschw wants to try develop something out of it let him and just ignore this thread if you don't have anything productive to add to it. This wasn't posted in Development so he's not expected to have the kernel ready to post so discussion is allowed here.
Thanks
AvRS
ARM Project TEAM.
To get away our doubt to you, may I ask you something about your ARM Project?
You have many thread there,
Optimus Black
Optimus 2X
Xperia Arc
HTC Droid DNA
Samsung Galaxy S3; and
Google Nexus 4.
And I got this post,
nicholaschw said:
We are an non-profit organisation alike cyanogenmod, but only focusing on creating a global aftermarket kernel for the Android OS, specifically to remove the major setbacks of linux.
Click to expand...
Click to collapse
So you're involved with (kind of) non-profit organization (alike CyanogenMod), can we know who's the members of your team? AFAIK, you don't own the phone in personal. So you (might) develop those kernel alone by yourself, or how many developers in your team?
I read your ARM. Project Recruitment, and it seems no one interested, so this non-profit organization doesn't existed yet, or you already have your own internal team?
redy2006 said:
To get away our doubt to you, may I ask you something about your ARM Project?
You have many thread there,
Optimus Black
Optimus 2X
Xperia Arc
HTC Droid DNA
Samsung Galaxy S3; and
Google Nexus 4.
And I got this post,
So you're involved with (kind of) non-profit organization (alike CyanogenMod), can we know who's the members of your team? AFAIK, you don't own the phone in personal. So you (might) develop those kernel alone by yourself, or how many developers in your team?
I read your ARM. Project Recruitment, and it seems no one interested, so this non-profit organization doesn't existed yet, or you already have your own internal team?
Click to expand...
Click to collapse
We currently are five-membered. Xperia is full, me, jared and pidozz. Two more are under evaluation. See ARM.'s git
Good Luck with whatever you're doing, I hope you learn someday.
My better half made me a delicious taco and while eating I read the comments.
It was not my intent to flame, neither argue with anyone. I will rather get drunk and party till morning. Good year everyone.
Sent from my LG-P970 using xda premium
Edvin73 said:
My better half made me a delicious taco and while eating I read the comments.
It was not my intent to flame, neither argue with anyone. I will rather get drunk and party till morning. Good year everyone.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Off topic but good year to you too,here they don't serve tacos
Sent from my LG-P970 using xda premium
hmm, 80% of repos are forked from already good kernels from such devs like gokhanmoral, CM, garwedgess, coolya, etc.
it's like forking Diana kernel then adding a little touch.
Even your "bproj repo" is a clone from huexxx https://github.com/ARMP/bproj-black/blob/master/Makefile#L198 yet you pushed it as initial commit. I understand, maybe you're shy to fork it repo to repo.
Your Makefile on the repo shows:
export KBUILD_BUILDHOST := $(SUBARCH)
#ARCH ?= $(SUBARCH)
ARCH ?= arm
#CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
CROSS_COMPILE ?= /home/huexxx/android/arm-2010q1/bin/arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Lol. He gets owned pretty much doesnt he?
In the Nexus 4 forums he told us that he works for google btw.
realfelix said:
Lol. He gets owned pretty much doesnt he?
In the Nexus 4 forums he told us that he works for google btw.
Click to expand...
Click to collapse
if i am, i would be in the newspapers. I'm so young. And go look at the post. FATHER. One more thing, this post is useless as gab himself is more capable to give this community a kernel
Thread closed as per OP request.
Guys any word on aosp for our device..?..dying to try one..come on give me some info or i will need to learn java..lol...
Prm593 said:
Guys any word on aosp for our device..?..dying to try one..come on give me some info or i will need to learn java..lol...
Click to expand...
Click to collapse
It was on forum many times, use search
Few users on this forum just start working on AOSP and i think CM, but it's just begining...
cheers
Mayex said:
It was on forum many times, use search
Few users on this forum just start working on AOSP and i think CM, but it's just begining...
cheers
Click to expand...
Click to collapse
sorry..but thnks
Prm593 said:
sorry..but thnks
Click to expand...
Click to collapse
Its not about only JAVA here you see. Building for a completely new device needs much more. If you are really keen to learn, then go ahead and pick up a book on Embedded Linux so that you can learn how a device tree is created, how it has to be edited and what sources are necessary to pull it off!
Cheers!
sarkar1990 said:
Its not about only JAVA here you see. Building for a completely new device needs much more. If you are really keen to learn, then go ahead and pick up a book on Embedded Linux so that you can learn how a device tree is created, how it has to be edited and what sources are necessary to pull it off!
Cheers!
Click to expand...
Click to collapse
ok bro thnks...but any luck with the aosp.?
I have idea. :silly:
We can post here any progress in building AOSP.
Could anyone who knows something post here that how looks work on AOSP? Any progress?
Calm down, guys. Don't get hyperexcited.
Developing a device tree is a hard and long process, as most of the things don't work and need proprietary files.
Give us some time. I'm sure that in the near future the development section will be full of ROMs
Sent from my C5303 using XDA Premium 4 mobile app
eagleeyetom said:
Calm down, guys. Don't get hyperexcited.
Developing a device tree is a hard and long process, as most of the things don't work and need proprietary files.
Give us some time. I'm sure that in the near future the development section will be full of ROMs
Sent from my C5303 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I couldn't say this better myself. First we need something that will boot atleast! Only then can the actual debugging start.
EagleEye, are you developing anything yet?
Cheers
sarkar1990 said:
I couldn't say this better myself. First we need something that will boot atleast! Only then can the actual debugging start.
EagleEye, are you developing anything yet?
Cheers
Click to expand...
Click to collapse
My thesis at the moment. I have a deadline on Wednesday.
I need to wait for my ISP to sort my connection out (probably tomorrow), set up a Linux on my ultra fast Pentium 4 beast :silly: (build server saves my ass) and I will start working on CM.
I'll create an IRC channel, so interested people can help me out.
Stay tuned
eagleeyetom said:
My thesis at the moment. I have a deadline on Wednesday.
I need to wait for my ISP to sort my connection out (probably tomorrow), set up a Linux on my ultra fast Pentium 4 beast :silly: (build server saves my ass) and I will start working on CM.
I'll create an IRC channel, so interested people can help me out.
Stay tuned
Click to expand...
Click to collapse
Awesome man! Send me the link to the channel... Build server :good:
Sent from my C5302 using Tapatalk 4
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
peters. said:
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
Click to expand...
Click to collapse
some hope's have come up..
cheer's guys
peters. said:
Just curious. Is Sony releasing kernel with proprietary drivers? (they say they are very open-source friendly) Coming from HTC device, HTC did provide the kernel sources, but heavily modified, which caused AOSP not working. I finally went for Sony for their attitude towards community, I saw some build files on their web, but not sure what exactly they are.
Click to expand...
Click to collapse
All kernels have proprietary drivers, every single vendor does it because the companies that manufacture CPU/GPU/wifi/nfc/telephony/bluetooth/etc chips don't want to release every bit of source code, so they release sources that should make the chip work easily on different builds of android, keeping a lot of code on precompiled binary files
Check the sony developer portal, they released the open-source pack for our devices...
I'd be interested to see a list of the main developers involved in this
So far I've seen
(excuse my spelling)
Pulsar_g2
Chainfire
Eespen
Entropy512
XpLoDWilD
Rebellos
Apologies to the people I missed, give me some names below to add to the list!
Who are the rest?
t0ph0id said:
I'd be interested to see a list of the main developers involved in this
So far I've seen
(excuse my spelling)
Pulsar_g2
Chainfire
Eespen
Entropy512
XpLoDWilD
Who are the rest?
Click to expand...
Click to collapse
There isn't a list at present, for the simple reason that this is a community project, and it's more important to have community involvement than to celebrate some big names that are involved.
There are a few more people than that though
I guess we can get together a list later on, but I'll have to make sure I don't miss anyone - this is why people lists are tricky to maintain
Going forward though, omni is intended to be something anyone can contribute into, be it translating, testing (once builds are being made officially), developing features, giving devices support, or helping out in forums.
pulser_g2 said:
There isn't a list at present, for the simple reason that this is a community project, and it's more important to have community involvement than to celebrate some big names that are involved.
There are a few more people than that though
I guess we can get together a list later on, but I'll have to make sure I don't miss anyone - this is why people lists are tricky to maintain
Going forward though, omni is intended to be something anyone can contribute into, be it translating, testing (once builds are being made officially), developing features, giving devices support, or helping out in forums.
Click to expand...
Click to collapse
Thanks for the response, I should have known something like that was coming.
:cyclops:
t0ph0id said:
I'd be interested to see a list of the main developers involved in this
So far I've seen
(excuse my spelling)
Pulsar_g2
Chainfire
Eespen
Entropy512
XpLoDWilD
Who are the rest?
Click to expand...
Click to collapse
That list gives me goosebumps.
You can add Rebellos to the list!
Just names
And as pulser said the term "lead developers" is misleading. We see ourselves not as that.
Sent from my Find 5 using xda app-developers app
maxwen said:
Just names
And as pulser said the term "lead developers" is misleading. We see ourselves not as that.
Sent from my Find 5 using xda app-developers app
Click to expand...
Click to collapse
Nice to see you, and the others, here
I think there will probably always be a need for leads/senior developers (e.g. those with global +2) just to prevent something from descending to chaos - however, I want to try and minimize the distinction between leads and others, and only have overriding happen when there's a really good reason to do so, as opposed to something getting -2ed because a maintainer just doesn't like it.
Most importantly, if something is rejected, it's going to have to have a detailed explanation from multiple people of why.
pulser_g2 said:
There isn't a list at present, for the simple reason that this is a community project, and it's more important to have community involvement than to celebrate some big names that are involved.
There are a few more people than that though
I guess we can get together a list later on, but I'll have to make sure I don't miss anyone - this is why people lists are tricky to maintain
Going forward though, omni is intended to be something anyone can contribute into, be it translating, testing (once builds are being made officially), developing features, giving devices support, or helping out in forums.
Click to expand...
Click to collapse
Don't forget me.. like you forgot to add my ssh key when you switched domains (btw, can you fix that?)
Entropy512 said:
I think there will probably always be a need for leads/senior developers (e.g. those with global +2) just to prevent something from descending to chaos - however, I want to try and minimize the distinction between leads and others, and only have overriding happen when there's a really good reason to do so, as opposed to something getting -2ed because a maintainer just doesn't like it.
Most importantly, if something is rejected, it's going to have to have a detailed explanation from multiple people of why.
Click to expand...
Click to collapse
Maybe the term "project overseers" is more appropriate
maxwen said:
Maybe the term "project overseers" is more appropriate
Click to expand...
Click to collapse
I would prefer "dark overlords" personally.
Entropy512 said:
I would prefer "dark overlords" personally.
Click to expand...
Click to collapse
Master Blaster
Sent from my Find 5 using xda app-developers app
I'm only sharing to you. All credits is to Bpear/Luster
Info+download:
http://www.gizmoluster.com/2013/12/paranoid-android-4-0-beta-unofficial-luster-builds-kitkat-4-4-2/
[]s
VW
I want those per app dpi features. They're so awesome!
Sent from my Nexus 5 using Tapatalk
victorwalter said:
I'm only sharing to you. All credits is to Bpear/Luster
Info+download:
http://www.gizmoluster.com/2013/12/paranoid-android-4-0-beta-unofficial-luster-builds-kitkat-4-4-2/
[]s
VW
Click to expand...
Click to collapse
Paranoid android specifically asked that no builds are shared at this early stage and previous threads have been locked. Do you have their permission to share this?
FuMMoD said:
I want those per app dpi features. They're so awesome!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Although the pa ui is simple to use, the xposed module "app settings" is very good at delivering per app dpi and tablet ui
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Paranoid android specifically asked that no builds are shared at this early stage and previous threads have been locked. Do you have their permission to share this?
Click to expand...
Click to collapse
nor does he need any permission to share. they themselves put it out, it got picked up by that site, and he shared that site. if they do not want anyone to share, then they should not put it out. that is how it works.
simms22 said:
nor does he need any permission to share. they themselves put it out, it got picked up by that site, and he shared that site. if they do not want anyone to share, then they should not put it out. that is how it works.
Click to expand...
Click to collapse
That is not how it worked here:
http://forum.xda-developers.com/showthread.php?t=2558519
They said you can build it for yourself, but do not share publicly. That's why it suggests to me that permission should be gained. Not only out of courtesy and respect (as is often the case here on XDA - as well it should) but also as they explicitly came here and requested things not be shared.
The fact it is on github does not mean they want it to be shared. Github is a collaboration tool first and foremost. To say they cannot use the collaboration tool within their own team otherwise it's fair game for people disrespecting there wishes is unfair. Sure. they may now want the build to be shared publicly, and if that is the case, perhaps this thread should be locked as a duplicate and the original re-opened, but I haven't seen any official statement here yet that public sharing is now accepted.
I think perhaps we should ask @ApriliaM3 for comment as the moderator locking the last thread at PA's request
rootSU said:
That is not how it worked here:
http://forum.xda-developers.com/showthread.php?t=2558519
They said you can build it for yourself, but do not share publicly. That's why it suggests to me that permission should be gained. Not only out of courtesy and respect (as is often the case here on XDA - as well it should) but also as they explicitly came here and requested things not be shared.
The fact it is on github does not mean they want it to be shared. Github is a collaboration tool first and foremost. To say they cannot use the collaboration tool within their own team otherwise it's fair game for people disrespecting there wishes is unfair. Sure. they may now want the build to be shared publicly, and if that is the case, perhaps this thread should be locked as a duplicate and the original re-opened, but I haven't seen any official statement here yet that public sharing is now accepted.
I think perhaps we should ask @ApriliaM3 for comment as the moderator locking the last thread at PA's request
Click to expand...
Click to collapse
i didn't know it.. sorry for that.
mod please close this.
victorwalter said:
i didn't know it.. sorry for that.
mod please close this.
Click to expand...
Click to collapse
Well, lets at least see what is to be said. The staff here may know newer information than I have. I just wanted to ask the question
rootSU said:
That is not how it worked here:
http://forum.xda-developers.com/showthread.php?t=2558519
They said you can build it for yourself, but do not share publicly. That's why it suggests to me that permission should be gained. Not only out of courtesy and respect (as is often the case here on XDA - as well it should) but also as they explicitly came here and requested things not be shared.
The fact it is on github does not mean they want it to be shared. Github is a collaboration tool first and foremost. To say they cannot use the collaboration tool within their own team otherwise it's fair game for people disrespecting there wishes is unfair. Sure. they may now want the build to be shared publicly, and if that is the case, perhaps this thread should be locked as a duplicate and the original re-opened, but I haven't seen any official statement here yet that public sharing is now accepted.
I think perhaps we should ask @ApriliaM3 for comment as the moderator locking the last thread at PA's request
Click to expand...
Click to collapse
again, they shared it publicly. if they share it publicly, then whoever wants can share it. their permission is not needed. and, on top of that, since they shared it publicly, they also need to provide the kernel source. if not, then they are violating gpl.
simms22 said:
again, they shared it publicly. if they share it publicly, then whoever wants can share it. their permission is not needed. and, on top of that, since they shared it publicly, they also need to provide the kernel source. if not, then they are violating gpl.
Click to expand...
Click to collapse
So what you're saying is that the original thread was locked in error. Meaning this thread should be locked and the original re-opened.
rootSU said:
So what you're saying is that the original thread was locked in error. Meaning this thread should be locked and the original re-opened.
Click to expand...
Click to collapse
no. they have every right to close an xda thread if they want, it it might never be opened, if they dont want. they have that right. but xda isnt the only public website. they shared it publicly, not in private, on another website. since it was shared publicly, it is public now. and anyone who grabs it has the right to reshare it. dont get me wrong, i do not use PA, nor do i want to try it. but, as a rom that is shared publicly by them, they lose the right to say that no one can share it. while it was not public, in a private testing group, they can say it. but cant say it about a publicly shared rom. this thread isnt opened by them, and shares what they share in public on a different site.
simms22 said:
no. they have every right to close an xda thread if they want, it it might never be opened, if they dont want. they have that right. but xda isnt the only public website. they shared it publicly, not in private, on another website. since it was shared publicly, it is public now. and anyone who grabs it has the right to reshare it. dont get me wrong, i do not use PA, nor do i want to try it. but, as a rom that is shared publicly by them, they lose the right to say that no one can share it. while it was not public, in a private testing group, they can say it. but cant say it about a publicly shared rom.
Click to expand...
Click to collapse
Thats just it though, they didnt share it on or to the other website. At least I cannot see anywhere on the site linked in the OP that PA shared a build. Its a quote from a G+ post (and link back) that had no builds then 5 unofficial builds added. So nothing has changed since the last lock. The site in question appears to have done the same as the OP of the last thread which was locked.
rootSU said:
Thats just it though, they didnt share it on or to the other website. At least I cannot see anywhere on the site linked in the OP that PA shared a build. Its a quote from a G+ post (and link back) that had no builds then 5 unofficial builds added. So nothing has changed since the last lock. The site in question appears to have done the same as the OP of the last thread which was locked.
Click to expand...
Click to collapse
that is also a possibility. if that site shared it without permission, than these builds are still public, unfortunately. whoever is the spokesperson for pa will have to take care of it. they can also ask a mod to remove it from here, then a mod will decide if its appropriate to remove or leave(most likely they would remove it). but it is up to them to ask to remove it.
All OP has to do is just point to the Google plus community group page and tell us to download the betas through there. I'm sure they allow linking to their community page at least.
https://plus.google.com/+ParanoidAndroidCorner/posts
FuMMoD said:
All OP has to do is just point to the Google plus community group page and tell us to download the betas through there. I'm sure they allow linking to their community page at least.
https://plus.google.com/+ParanoidAndroidCorner/posts
Click to expand...
Click to collapse
So is it just me who cant find any official betas on there?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
So is it just me who cant find any official betas on there?
Click to expand...
Click to collapse
I can't either. You know, they had planned to release something last weekend but the host of their gerrit went down so they couldn't. Do you guys really want a release of PA without Hybrid? without PIE? without Halo?. I mean, they'll give it to us anyways but frankly I don't see the point. Why not use one of the 100 other ROMS with the same features in each while you wait? I mean just look at the ROMS out for hammerhead right now, they're all remarkably similar. Granted if you look at that feature list of the "beta" there are a few standout features but other than that why do you guys want a ROM that won't have what makes PA unique? You've waited 1.5+ months you can't wait a little longer? lol.
zxyz said:
Do you guys really want a release of PA without Hybrid? without PIE? without Halo?
Click to expand...
Click to collapse
No not at all..
I looked also and didn't see any.
You could make a build yourself and cherry pick those things but don't be surprised if it won't boot or if it does you get lots of bugs.
The stripped PA is only while it's in beta. From what I understand, hybrid still has an issue with DPI right now and they're working on combining halo and pie. Plus the hosting issues with their gerrit. I don't think normal PA builds will be too far behind the betas. At least hopefully.
Just check out their gerrit. A crap load got merged on the 18th now that they're back up and there's some cool stuff up for review too. ParanoidOTA, Knock Knock to sleep, battery light, something about voiceplus. Who knows what will and won't get merged but the PA guys are hard at work. They recently switched up their hosting too so now that that's all taken care of, the ball is finally rolling.
Sent from my Nexus 5 using Tapatalk
Oh I have to give this a try! I have been waiting for paranoid.
All the sweet features like halo and hybrid have been broken by kitkat. That's why they haven't released anything official yet.
Sent from my Nexus 5 using Tapatalk
FuMMoD said:
All the sweet features like halo and hybrid have been broken by kitkat. That's why they haven't released anything official yet.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
They may have been broken by KitKat I have no clue. But PA themselves said that they have build a brand new clean base for 4.4 and are building off of that. So they are making sure everything works great with the new base then the features will be added. I've been using PA 4.0 since that site posted the beta and I can say its fast and smooth just like stock and the immersive mode is great.
>^.^< Sent From Meow nexus5
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!
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [d800/d801/d802], ROM for the LG G2
Contributors
CarbonDev, BigShotRob22
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-04
Last Updated 2014-06-07
Reserved
Reserved
Could you please add support for the d803. This is my fav rom . thnx
Will there be a separate thread for vs980?
Sent from my g2 using Tapatalk
Lol vs980 is in the nightlies. So yes. We has support. Maybe add in title?
Sent from my LG-VS980 using Tapatalk
Yeah LS980 is supported too. I'm running it now haha.
Been running the vs980 version since release. Runs great I have only caught on sod. Everything is running really smooth. I appreciate the sound output for aux is just about stock levels too
Sent from my LG-VS980 using Tapatalk
Loving this rom! Got it on my G2, N5, and my N7 flo and it is the best of the best!
Sent from my LG-D800 using Tapatalk
Also been running this since it dropped...loved it on my Gnex...love it even more on my G2. Thanks Carbon Team!
Sent from my VS980 using Xparent Skyblue Tapatalk 2
That's good to hear because it seems the d803 is like the unwanted child ..
So, I'm on the d800, am I the only one not getting a working keyboard? I touch a text field, the cursor pops up, but no keyboard. I tried it with aosp and SwiftKey set as default with no luck
bps119 said:
So, I'm on the d800, am I the only one not getting a working keyboard? I touch a text field, the cursor pops up, but no keyboard. I tried it with aosp and SwiftKey set as default with no luck
Click to expand...
Click to collapse
Yea I think its just u bro lol what gapps are u using?
Sent from my LG-D800 using Tapatalk
monkboy24 said:
Yea I think its just u bro lol what gapps are u using?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
PA gapps, modular micro package from 1/23. No worries, I'll eyelash with banks gapps and see if the issue persists. Thanks for the response.
bps119 said:
PA gapps, modular micro package from 1/23. No worries, I'll eyelash with banks gapps and see if the issue persists. Thanks for the response.
Click to expand...
Click to collapse
i flash banks core with all my roms and never ran into any issues
Testing out now! Good to see this up.
Sent from my LG-D801 using XDA Premium 4 mobile app
I don't have an access to a charged for the next 9 hours so I really don't feel like flashing this just to test these: Could somebody tell me if halo and pie (probably not) are implemented yet?
Sent from my LG D802
Bluetooth watch
Just a quick question, anyone know why with the previous unofficial Carbon my Sony Smartwatch was working and now it is isn't. I have tried using different kernel's and still no luck. I know the watch is out of date and everything, but I have reasons for still using it. Anything you can recommend to try would be helpful. Thanks!
Makrilli said:
I don't have an access to a charged for the next 9 hours so I really don't feel like flashing this just to test these: Could somebody tell me if halo and pie (probably not) are implemented yet?
Sent from my LG D802
Click to expand...
Click to collapse
No it is not. Halo is in review on our gerrit tho
Sent from my LG-VS980 using xda app-developers app
I can't download the rom, the site is too slow
Ps. Now is ok. Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk