[ROM][AOSP][Nightly/Release] CarbonRom KitKat [jflteatt/jflteusc] - AT&T Samsung Galaxy S 4 Android Development

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [jflteatt/jflteusc] - AT&T Samsung Galaxy S 4 Android Development

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 [jflteatt/jflteusc], ROM for the AT&T Samsung Galaxy S 4
Contributors
CarbonDev, PatrickC
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-09
Last Updated 2014-05-09

Reserved

Reserved

Edited: download link works now.
I look forward to downloading and flashing this, Carbon was easily my favorite 4.3 rom.

Anyway there'll be a jfltecan release down the road, or at least a workaround with the jflteatt to work for the Canadian variant? I know there's lots of interest! :fingers-crossed:

finneginsfast said:
Anyway there'll be a jfltecan release down the road, or at least a workaround with the jflteatt to work for the Canadian variant? I know there's lots of interest! :fingers-crossed:
Click to expand...
Click to collapse
As far as I know, they will not be supporting the CAN version... However, there is a workaround that you can do...
(They will not install unless you do this)...
Download the jfltetmo file (The att version may work as well, I haven't tried it)
Two changes to make.
1.
In CARBON-KK-NIGHTLY-20140209-0238-jfltetmo\META-INF\com\google\android -> updater-script
Change the first line from:
assert(getprop("ro.product.device") == "jfltetmo" || getprop("ro.build.product") == "jfltetmo" || abort
to:
assert(getprop("ro.product.device") == "jfltecan" || getprop("ro.build.product") == "jfltecan" || abort
2.
In CARBON-KK-NIGHTLY-20140209-0238-jfltetmo\system -> build.prop
Change:
ro.product.model=SGH-M919
ro.product.brand=samsung
ro.product.name=jfltetmo
ro.product.device=jfltetmo
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=jfltetmo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=jfltetmo-user 4.3 JSS15J M919UVUEMK2 release-keys
ro.build.fingerprint=samsung/jfltetmo/jfltetmo:4.3/JSS15J/M919UVUEMK2:user/release-keys
ro.build.characteristics=default
ro.carbon.device=jfltetmo
# end build properties
#
# from device/samsung/jfltetmo/system.prop
#
# system.prop for SGH-M919
#
to:
ro.product.model=SGH-M919
ro.product.brand=samsung
ro.product.name=jfltetmo
ro.product.device=jfltetmo
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=jfltecan
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=jfltecan-user 4.3 JSS15J I337MVLUEMK6 release-keys
ro.build.fingerprint=samsung/jfltecan/jfltecan:4.3/JSS15J/I337MVLUEMK6:user/release-keys
ro.build.characteristics=default
ro.carbon.device=jfltecan
# end build properties
#
# from device/samsung/jfltecan/system.prop
#
# system.prop for SGH-I337M
#
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
Thanx Carbon for the great ROM!!
I did find one issue with the theme compatibility though...
The quicktiles and MMS app don't seem to theme...
Just thought I'd let you know.
Thanx again!!

Carbon back in business I see. I just flashed and so far so good.
Sent from my SGH-I337 using XDA Premium 4 mobile app

wow running smoothly with ktoonsez kernel. Hope fully this cures my flasholicalism

Just tried to flash 2-16 Nightly. Wiped system, cache, and dalvik, flashed ROM and GApps, and on reboot, I got the "Unauthorized software" message and it wouldn't boot. Anyone else having this issue? I'm back on 2-12 now and it flashed fine.

energyracing said:
Just tried to flash 2-16 Nightly. Wiped system, cache, and dalvik, flashed ROM and GApps, and on reboot, I got the "Unauthorized software" message and it wouldn't boot. Anyone else having this issue? I'm back on 2-12 now and it flashed fine.
Click to expand...
Click to collapse
Try it again and flash loki doki. You could also flash a lokied kernel after flashing the Rom.
Sent from my SGH-I337 using Tapatalk

geomax45 said:
Try it again and flash loki doki. You could also flash a lokied kernel after flashing the Rom.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Will do. Didn't even think of that, actually. Thanks. But what could have changed in the builds to stop Loki-ing the ROMs? I'm using TWRP 2.6.3.1, which auto-Lokis everything anyway, so I'm a little confused as to what has changed.

energyracing said:
Will do. Didn't even think of that, actually. Thanks. But what could have changed in the builds to stop Loki-ing the ROMs? I'm using TWRP 2.6.3.1, which auto-Lokis everything anyway, so I'm a little confused as to what has changed.
Click to expand...
Click to collapse
Read about CM merging all devices for the S4 under the same build tree.

Any support for jfltecan
I'm currently running carbon rom (unofficial 01/31/2014) which was posted in another thread which supports jfltecan. I know carbon isn't supporting this model but can someone help on how I can get the latest version running on my phone.

kdot25 said:
I'm currently running carbon rom (unofficial 01/31/2014) which was posted in another thread which supports jfltecan. I know carbon isn't supporting this model but can someone help on how I can get the latest version running on my phone.
Click to expand...
Click to collapse
Did you get it from this thread?
http://forum.xda-developers.com/showthread.php?t=2568699
[ROM] Unofficial Carbon Kitkat [4.4.2][jflteatt/jfltecan] 02/19
Cuz it was just updated.

swatty43 said:
Did you get it from this thread?
http://forum.xda-developers.com/showthread.php?t=2568699
[ROM] Unofficial Carbon Kitkat [4.4.2][jflteatt/jfltecan] 02/19
Cuz it was just updated.
Click to expand...
Click to collapse
Thanks alot, I tought everything was getting moved to this thread.

Thread closed. Please check it out in its new home Samsung Galaxy S4 Unified Development here

Related

[ROM][Nightly][ICS] Team Eos WiFi Nightlies (Wingray/MZ604)

Team EOS XOOMICS 4.0.4 Wingray MZ604NIGHTLIES
Welcome to the evolution of TiamatXOOM.
With the AOSP release of Android 4.0 begins the next dawn of the Android operating system. And with this release comes Team EOS, the natural evolution of the TiamatXOOM development team.
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. The launching point for this development effort is the Motorola XOOM.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated once every 24 hours and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS Xoom is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Xoom Nightly builds: http://goo-inside.me/devs/teameos/roms/nightlies/wingray/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Use the latest available gapps package available from http://goo.im/gapps
*Note - You will need to re-flash G-Apps after you flash an updated nightly build. You can do this before you reboot after the installation of a new nightly.
Also note that if you are coming from an earlier G-Apps package you will need to wipe prior to installation of this package in order to avoid FC issues.
--
Current Known Issues:
This builds is only for the MZ604 Wingray (WiFi XOOM) It does not support data on any GSM or 3G only Xoom
Features:
Because these are nightly builds the included features are constantly evolving. Change logs are generally generated on a daily basis.
Change logs can be viewed at http://nightlies.teameos.org/changelogs/
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Tiamat ICS Xoom kernel
Support for OC;Under/Overvolt
Governors: lagfree, interactive, conservative, ondemand, userspace, performance
Kernel Note: In compliance with GPL kernel source can be found at: http://git.tiamat-dev.com/tegra2/tiamat-xoom/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery (Solarnz R4c, Rogue, Clockwork)
Perform a full wipe (read Factory Reset) prior to installing this over ANY Honeycomb based rom (this includes all Tiamat roms)
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
FEATURE REQUESTS!
We need YOU, yes YOU to help us build the best AOSP rom out there. Have an idea for a feature you want to see implemented then let us know!
Team EOS Feature Request
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
EOS Motorola Xoom Boot Splash
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
Welcome to the XOOM evolved. Welcome to Team EOS.

For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
Also a note on 3G/4G Xooms- You can infact flash and install this rom on 3G/4G xooms. You will not however be able to use the 3G/4G radio. There are new basebands that are needed in order for the 3G/4G radios to be able to communicate with the RIL and until these updated basebands are released we are in a holding pattern for radio connectivity.
Also there are sporadic reports of HDMI partly functioning. Full HDMI functionality is dependent on additional proprietary binaries that Google has not been able to release yet due to licensing issues.
Also, please note that while the current builds are proving to be very stable, and for users that do not use their cellular radio they can be used as a daily driver these are still nightly builds and are subject to constant development. If you find strange or otherwise unexplained errors logcats are greatly appreciated as it makes it much easier to track down issues.
Thank you all for your support!
*Updated G-Apps Package*
The developers working on CM9 have released an updated G-Apps package for 4.0.3 AOSP based builds
New version is 4.0.3 V8
A Special Thanks goes out to gpstar this G-Apps build
Download: http://www.multiupload.com/54DD4VIXZ6
MD5: 4a6a7543b025a17f9536eccc4e5afc17
*Note - Because of changes made to the G-Apps package a wipe will be required if installing this version of G-Apps over a previous G-Apps package in order to avoid FC issues. This version of G-Apps appears to address some of the communications issues that have been plaguing Google services on AOSP builds.
Bug Reporting:
As you test out the platform and you discover bugs please report them to:
https://bugs.teameos.org/
A couple of notes about bug reporting. If it is an application issue (IE a particular game generates FC errors) please do not report it. There is nothing that we can do about specific application issues.
If you do report an error please, Please, PLEASE include logcats showing the errors. It is often time difficult if not impossible to replicate errors and logcats make resolving issues much much easier. Please feel free to add the logcats as attachments to the bug report.
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
Eos Motorola Xoom Boot Splash
Thank you again for your continued support of Team EOS!

I can say from personal experience that this ICS Rom is working beautifully. Yes, there are a few bits missing but it's clear that this is taking the Xoom to another level, altogether.
Cudos to Team EOS for taking this step. I can't wait for the next nightly.

Do we need to do a full wipe and reset if coming from razorbladex's rom?

double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't. Just wiped cache.

double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
Since I have no idea what rom that is the answer is yes. The only time you do not need a wipe is if you are coming from a factory OTA. Generally speaking all custom roms will require a wipe prior to install.

Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Nusince said:
Since I have no idea what rom that is
Click to expand...
Click to collapse
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.

Again, since I have no way of knowing anything about razorbladex's ICS rom as I have never flashed it my inclination is to tell you to wipe first to ensure there are no residual or unforeseen conflicts. With that said, what you choose to do is up to you.
When you flash a new rom /system gets overwritten which includes the su binary so this is a non-issue. This build includes the latest changes to the su binary.
double1 said:
Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.
Click to expand...
Click to collapse

That first part of my question was for okantomi, sorry I should have quoted him since he stated that he had flashed this over that rom.

double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't wipe anything coming from his rom, just flashed the rom then flashed gapps and everything is fine, really quick and smooth

Is it possible to update the first post with a list of broken stuff so that it's easier to keep track?
Sent from my Galaxy Nexus using XDA App

Can anyone comment on HD youtube and netflix working ?

I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?

rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
Because you clearly have no cell network signal! Mine has it too. Give it a while: ICS roms are new and have yet to be extensively tweaked for little details like this.

bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse
Both play content. Navigating Netflix isn't the smoothest.

It's because these builds are essentially ready for 3G/4G connectivity. However for the time being the cellular radio icon will show regardless of if you have a stingray(3g/4g) or wingray(wifi) board. This will be addressed once we have the necessary components to bring life to the cellular radios.
rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
---------- Post added at 04:59 PM ---------- Previous post was at 04:40 PM ----------
HD content in Youtube works fine. Don't know about netflix.
bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse

Very interesting. On the other rom HDMI worked but calendar didn't. Now on this rom calendar works but HDMI don't lol. Small trade off but I find this very interesting.
James

Netflix works fine for me

cant wait to flash this, just downloaded it and will be flashing when I get home, good work guys!

Can we assume that further updates will be flashable over this ROM without wiping ?

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [endeavoru]

XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [endeavoru], ROM for the AT&T HTC One X
Contributors
CarbonDev, mattmanwrx
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

Don't think this is for our device...???
Sent from my Transformer Prime TF201 using XDA Premium 4 mobile app

What a tease...
Sent from my Transformer Prime TF201 using XDA Premium 4 mobile app

Going through the downloads and this is definitely NOT for our device. @CarbonDev.
There are a few links to Evita Roms but they are all 2013.
Edit - Asked to have this moved to the proper Forum.

There is no devDB thread available for the international HTC One X (endeavoru) so I had to put in the ATT One X forum

CarbonDev said:
There is no devDB thread available for the international HTC One X (endeavoru) so I had to put in the ATT One X forum
Click to expand...
Click to collapse
great thinking. Imma just wait here with this popcorn and watch the reaction to all the n0obs that flash this on an Evita handset. :silly:

yeeeeeahbuddy said:
great thinking. Imma just wait here with this popcorn and watch the reaction to all the n0obs that flash this on an Evita handset. :silly:
Click to expand...
Click to collapse
They can flash our 4.3 rom for evita if they like

CarbonDev said:
There is no devDB thread available for the international HTC One X (endeavoru) so I had to put in the ATT One X forum
Click to expand...
Click to collapse
Yes it's on XDA. Here is the link:
http://forum.xda-developers.com/htc-one-x
Just ask to have it moved there

Moved to the Endeavor forum.
@op if you have any devDB issues, report your thread or PM me and we will help sort it out. :highfive:

I don't quite understand why is this called "[ROM][AOSP][Nightly/Release] CarbonRom KitKat [endeavoru]" if this is for the AT&T's US "HTC Evita" NOT for the Tegra 3 "HTC Endeavor"...

karlis1989 said:
I don't quite understand why is this called "[ROM][AOSP][Nightly/Release] CarbonRom KitKat [endeavoru]" if this is for the AT&T's US "HTC Evita" NOT for the Tegra 3 "HTC Endeavor"...
Click to expand...
Click to collapse
Its for endeavoru,
Downloading latest nightly CARBON-KK-NIGHTLY-20140204-0041-endeavoru.zip, Good to see Carbon KK.

Just installed the rom, but the icons seem massive
Update:
Camera doesn't seem to work, crashes straight away

sthbr82 said:
Its for endeavoru,
Downloading latest nightly CARBON-KK-NIGHTLY-20140204-0041-endeavoru.zip, Good to see Carbon KK.
Click to expand...
Click to collapse
So it is - didn't see it on the BOTTOM of the ROM list

Just updated the repos with the latest cm fixes.. Ran another nightly, check our download site in around an hour for the complete download.
Mounting SD card should be fixed - credits cm
Sent from my SM-N9000 using XDA Premium 4 mobile app

mattmanwrx said:
Just updated the repos with the latest cm fixes.. Ran another nightly, check our download site in around an hour for the complete download.
Mounting SD card should be fixed - credits cm
Sent from my SM-N9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Still no luck, SDCARD is unreachable :crying:

modest.young said:
Still no luck, SDCARD is unreachable :crying:
Click to expand...
Click to collapse
try with changing the kernel...maybe another kernel can solve it...like next aosp ep4...there is also a beta kernel which is more stable then the version in OP ...just look in the last 5 pages or so for the download link...also repack it

One of the screenshots says that it's 4.3, and OP says it's 4.4
One of these needs to be corrected.

so i've just installed the rom. on the first boot. sdcard cannot be read and the camera forced closed when i open it.
but then i reboot to change to another room, flash aicp boot img and reboot. apparently my camera an sdcard problems is fixed.
update : immersive mode is not working

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [toro]

XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [toro], ROM for the Samsung Galaxy Nexus
Contributors
CarbonDev, winner00
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

Thanks
sent from the DOG pound

Awesome, thanks. Can't wait to see this ROM developed and released as a stable. Thank you guys for all your hard work
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2

Maybe you can get Derek to lock the old thread.

Everything running well on my end! Good work guys

so far it's been worth the wait.
** Great Job **
is there anything in the works to add the slider before unlock?
Sent from my Galaxy Nexus using Tapatalk

Webpage crashes on dolphin and stock... Want to flash.
Sent from my Galaxy Nexus using Tapatalk

gorillabiscuit said:
Webpage crashes on dolphin and stock... Want to flash.
Sent from my Galaxy Nexus/QUOTE]
Same here but am getting by using Firefox for now.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse

I'm getting android.process.acore force closes. Can't do anything without getting the error. Clean install and PA GAPPS.
Trying to download the GAPPS linked on the Carbon site but the download keeps failing.
Sent from my Galaxy Nexus using XDA Premium HD app

Lte does not work. Also when trying to swipe the keyboard hides. Doesn't fc just hides. The back button seems not to work every time.

LTE works, you just need to restart the phone prior to setting up GAPPS.
Sent from my Galaxy Nexus using Tapatalk

So glad carbon is back. No problems so far, clean install, pa-gapps, mpokang 1080, #BAUSE! :thumbup:
Sent from my Nexus 7 using xda app-developers app

Browsers keeps fc on carbons download page. Anyone have a mirror to the latest update?

grandzu said:
Browsers keeps fc on carbons download page. Anyone have a mirror to the latest update?
Click to expand...
Click to collapse
I was going to try downloading from the app but get a 404 error. I had read a few days ago on Twitter that they are having to do some work to their servers because so many people are downloading the ROM. I wished I could help you out with a link I would like to try the newest myself.
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2

So excited to see kitkat Carbon for my Galaxy Nexus. I downloaded the KK nightly toro, and did a factory reset, and a format / system but when I flash the rom I get an error:
set_metadata_recursive: some changes failed E: Error in /CARBON_KK NIGHTLY_20140207-0521-toro.zip (Status 7) Installation aborted.
Can anyone tell me what I am doing wrong? I tried a different nightly, same error.
fortunately, restoring my nandroid worked, back to carbon jb

Wolfkmann said:
So excited to see kitkat Carbon for my Galaxy Nexus. I downloaded the KK nightly toro, and did a factory reset, and a format / system but when I flash the rom I get an error:
set_metadata_recursive: some changes failed E: Error in /CARBON_KK NIGHTLY_20140207-0521-toro.zip (Status 7) Installation aborted.
Can anyone tell me what I am doing wrong? I tried a different nightly, same error.
fortunately, restoring my nandroid worked, back to carbon jb
Click to expand...
Click to collapse
one thing you didn't mention is if you was using the latest CWM or TWRP
Sent from my Galaxy Nexus

lesclark said:
one thing you didn't mention is if you was using the latest CWM or TWRP
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Probably not the latest CWM. Is that my problem? I think I have CWM touch 6.0.2.3.

I believe the latest is 6.0.4.3
there have been issues if your not on the latest
Sent from my GT-P3113 using Tapatalk

[ROM][AOSP][Unofficial] CarbonRom KitKat [m7vzw]

UPDATE 6/2/14: The M7VZW is now officially supported! Download link is now pointing to the official downloads to avoid downloading one of my unofficial builds. I'm not the official build maintainer however.
-----------------------------------------
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 addressed 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!
Contributors
CarbonDev, daxmax
ROM OS Version: 4.4.x KitKat
Based On: AOSP
-----------------------------------------
-----------------------------------------
Source:
CarbonROM: https://github.com/CarbonDev
Cyanogenmod: https://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod

ART supported?
Via Nexus S7ven

[ROM][AOSP][Unofficial] CarbonRom KitKat [m7vzw] 2-24-14
fullmetal509 said:
ART supported?
Via Nexus S7ven
Click to expand...
Click to collapse
It never occurred to me to check to see if there was something I needed to add in to the device files to support changing the runtime.
EDIT: I'll check to see if the lines are in the build target. I always err on the side of caution and ART wasn't a concern since this was a build for me.
EDIT 2: Testing ART support now.
EDIT 3: Seems to be working just fine. I'll run ART on my phone for now and test.

Thanks for the birthday present pal, I've been hoping to see this ROM for a while now!
Sent from my HTC6500LVW using Tapatalk

TheAppleAndroidGuy said:
Thanks for the birthday present pal, I've been hoping to see this ROM for a while now!
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Nice. Happy birthday.

ART support
Just a quick update on ART support. After enabling it in developer options and rebooting, things seem to be fine so far. It took a bit after switching the runtime the first reboot but after the 'upgrade' finished there were no FC's and the phone seems to be functioning normally. Any apps that have issues with ART will still have issues though obviously. Having said that, so far so good.

Yesssssss, mmuzzy. We new more mmuzzy in our lives.
Sent from my One using XDA Premium 4 mobile app

Hey mmuzzy! Good to see you around in these parts, I ran your rom for my nexus 7 2012 a while back. You beat me to the unofficial Carbon-rom haha.

skiman10 said:
Hey mmuzzy! Good to see you around in these parts, I ran your rom for my nexus 7 2012 a while back. You beat me to the unofficial Carbon-rom haha.
Click to expand...
Click to collapse
Thanks. Ah, sorry about that. I didn't see that.

mmuzzy said:
Thanks. Ah, sorry about that. I didn't see that.
Click to expand...
Click to collapse
Its alright. My first unofficial port of a ROM so it is taking some time.
Sent from my HTC6500LVW using Tapatalk

skiman10 said:
Its alright. My first unofficial port of a ROM so it is taking some time.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Check your PM.

mmuzzy said:
Hey guys,
Here is an unofficial build of the CarbonROM I made for myself and I thought I'd share since it seems to be working pretty well for me. Your mileage may vary though so please nandroid as you normally would when crack flashing. If one of the normal devs was already working on CarbonROM this wasn't me trying to step on toes. I don't intend to do this nightly, or at all if an official build is in the works.
In the meantime, enjoy.
ROM: http://goo.im/devs/mmuzzy/m7vzw/carbon//CARBON-KK-UNOFFICIAL-20140224-1729-m7vzw.zip
GAPPs: http://goo.im/gapps/gapps-kk-20140105-signed.zip
I've linked the 'standard' GAPPs but I've also had good luck with PA and Banks versions of GAPPs.
Sources:
CarbonROM: https://github.com/CarbonDev
Cyanogenmod: https://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod
Thanks to CarbonROM, Cyanogenmod, Flyhalf205, santod040, buckmarble, and everyone else who give us all these great ROMs to chose from.
Click to expand...
Click to collapse
Hell yes. Finally. Props to you, sir!
Is this running the unified CM kernel, or something else? Not that it matters too much, I'm gonna flash it anyway...

Can you post in the OP any bugs or things not working? How is battery life on this?

123421342 said:
Can you post in the OP any bugs or things not working? How is battery life on this?
Click to expand...
Click to collapse
I haven't found anything glaringly broken yet. Battery life is decent. I have hours of deep sleep overnight.
Sent from my One using Tapatalk
thedrizzle said:
Hell yes. Finally. Props to you, sir!
Is this running the unified CM kernel, or something else? Not that it matters too much, I'm gonna flash it anyway...
Click to expand...
Click to collapse
I was viewing on my phone and missed the question. Sorry about that. It's running the CM kernel which seems to be running smoothly as of yesterday.

Tried to download gapps. Says "404 not found"
Sent from my HTC6500LVW using Tapatalk

pita said:
Tried to download gapps. Says "404 not found"
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Yup. Not sure why that is. I linked from the GAPPs page on Goo.im but even clicking on the link from http://goo.im/gapps gives the same results.
Alternative GAPPs downloads:
Cyanogenmod: http://wiki.cyanogenmod.org/w/Google_Apps
BaNkS: http://forum.xda-developers.com/showthread.php?t=2012857
OP updated with alternatives also. Thanks for pointing it out.

I guess it's just my phone but every time I install this my phone starts roaming until I factory reset it
Sent from my HTC6500LVW using Tapatalk

jtj1825 said:
I guess it's just my phone but every time I install this my phone starts roaming until I factory reset it
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I didn't run into that at all. If you dirty flashed I probably would have recommended wiping anyway.

mmuzzy said:
I was viewing on my phone and missed the question. Sorry about that. It's running the CM kernel which seems to be running smoothly as of yesterday.
Click to expand...
Click to collapse
No worries...thanks for the reply. I may flash the EliteLunar kernel since it has a few nice features that the CM kernel doesn't, but I'll agree that the CM kernel does run nice and smooth. Thanks again for the port...I hope we can keep this going until Carbon either devs for the m7 or lets someone be an official maintainer. Carbon has been my favorite ROM since its inception.

thedrizzle said:
No worries...thanks for the reply. I may flash the EliteLunar kernel since it has a few nice features that the CM kernel doesn't, but I'll agree that the CM kernel does run nice and smooth. Thanks again for the port...I hope we can keep this going until Carbon either devs for the m7 or lets someone be an official maintainer. Carbon has been my favorite ROM since its inception.
Click to expand...
Click to collapse
I'll keep my eyes on the changelog. Now that I've got everything set up it's no big deal to build a ROM now and again when the changes warrant it until an official port.

[ROM][SGH-T889 / T0LTETMO][4.4.4][UNOFFICIAL] CyanogenMod 11 - Builds of opportunity

As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the T-Mobile Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided us with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward.
My product is no more than a straight source built t0ltetmo build as the CM11 spec is drawn up for the t0ltetmo on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
cm-11-20150322-COUGMADE-t0ltetmo.zip
cm-11-20150313-COUGMADE-t0ltetmo.zip
cm-11-20150222-COUGMADE-t0ltetmo.zip
cm-11-20150206-COUGMADE-t0ltetmo.zip
cm-11-20150116-COUGMADE-t0ltetmo.zip
cm-11-20150107-COUGMADE-t0ltetmo.zip
cm-11-20150101-COUGMADE-t0ltetmo.zip
cm-11-20141220-COUGMADE-t0ltetmo.zip
cm-11-20141216-COUGMADE-t0ltetmo.zip
cm-11-20141212-COUGMADE-t0ltetmo.zip
cm-11-20141209-COUGMADE-t0ltetmo.zip
cm-11-20141206-COUGMADE-t0ltetmo.zip
cm-11-20141201-COUGMADE-t0ltetmo.zip
cm-11-20141126-COUGMADE-t0ltetmo.zip
cm-11-20141027-COUGMADE-t0ltetmo.zip
cm-11-20141020-COUGMADE-t0ltetmo.zip
cm-11-20141011-UNOFFICIAL-t0ltetmo.zip
cm-11-20141002-UNOFFICIAL-t0ltetmo.zip
cm-11-20140921-UNOFFICIAL-t0ltetmo.zip
cm-11-20140914-UNOFFICIAL-t0ltetmo.zip
cm-11-20140906-UNOFFICIAL-t0ltetmo.zip
cm-11-20140831-UNOFFICIAL-t0ltetmo.zip
cm-11-20140826-UNOFFICIAL-t0ltetmo.zip
cm-11-20140818-UNOFFICIAL-t0ltetmo.zip
cm-11-20140810-UNOFFICIAL-t0ltetmo.zip
cm-11-20140806-UNOFFICIAL-t0ltetmo.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.

Mine

Gimme

How is it so far?

Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!

carlz28 said:
Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!
Click to expand...
Click to collapse
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).

nice!

Coug76 said:
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).
Click to expand...
Click to collapse
No worries! Its one of those OCD things that bugs me on any ROM/device. Wish I could help narrow down the issue but I have no coding/devving/ROM building skills.
2 days running now and no other issues. Definitely a DD build!

New build is up.

Coug76 said:
New build is up.
Click to expand...
Click to collapse
still couldn't figured out how to change the network name?

zain0300 said:
still couldn't figured out how to change the network name?
Click to expand...
Click to collapse
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.

Coug76 said:
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.
Click to expand...
Click to collapse
i never asked when are you gonna fix it

What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app

sipher26 said:
What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
What did you get to work? I am hoping to trip over something soon. I have been mucking around in the .conf files for a while now.

I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app

sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the build.prop. If you let me know I can try it out as I have a nandroid sitting on my SD card all the time.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=cm_t0ltetmo-userdebug 4.4.4 KTU84Q bd05cc81b5 test-keys
ro.build.version.incremental=bd05cc81b5
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Sat Aug 9 22:04:17 PDT 2014
ro.build.date.utc=1407647057
ro.build.type=userdebug
ro.build.user=cougatron
ro.build.host=cougatron-MS-7793
ro.build.tags=test-keys
ro.product.brand=samsung
ro.product.name=t0ltetmo
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=t0ltetmo
ro.product.model=SGH-T889
ro.product.device=t0ltetmo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t0ltetmo-user 4.1.2 JZO54K T889UVBMB4 release-keys
ro.build.fingerprint=samsung/t0ltetmo/t0ltetmo:4.1.2/JZO54K/T889UVBMB4:user/release-keys
ro.build.characteristics=default
ro.cm.device=t0ltetmo
# end build properties
#
# from device/samsung/t0ltetmo/system.prop
#
#
# system.prop for t0ltetmo
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/ttyS0
ro.telephony.default_network=9
telephony.lteOnGsmDevice=1
ro.sf.lcd_density=320
ro.lcd_min_brightness=20
# System property ril adb log on
persist.radio.adb_log_on=1
# For sys info indication
persist.radio.add_power_save=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dalvik.multithread=false
persist.sys.dun.override=0
persist.sys.root_access=1
ro.cm.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.cm.releasetype=UNOFFICIAL
ro.modversion=11-20140810-UNOFFICIAL-t0ltetmo
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
persist.sys.recovery_update=false
ro.cm.display.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.ringtone=Orion.ogg
ro.carrier=unknown
ro.telephony.ril_class=SamsungQualcommRIL
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.zygote.disable_gl_preload=1
ro.opengles.version=131072
ro.bq.gpu_to_cpu_unsupported=1
debug.hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Any luck?

New build up.

looks to me that it is showing your region.local instead of your service provider

mattlowry said:
looks to me that it is showing your region.local instead of your service provider
Click to expand...
Click to collapse
I'm trying to figure out how to fix it and am getting frustrated with it. That same behavior is present in the official builds of CM and Omni. I have been digging through the source git for AOKP to see if I can tell how they are making it work. I can only work on it after the kids are in bed but before I sleep. My eyes are starting to cross...

Develop Bugs

welcome