• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Official Carbon KitKat Nightlies Are Here!!

Additionally, USB tethering and camera freezes are known issues for a lot of ROM's currently based off of what CM is doing. I am currently searching XDA for a camera .apk which I know I saw at some point which is supposed to work in place of the stock camera .apk. Will post if I find it. Since I am not the developer of Carbon ROM, I have no reason to be offended if something isn't working, and as I said, mentioning that I don't use a certain feature is just a reference point indicating that I have no first-hand knowledge of the issue.
 
Upvote 0
Do you need me to holler at decimalman to contact you? He sounds like he is getting super frustrated with his options for file hosting. And by the way, please amend your previous post, your word choice is specifically listed as being inappropriate in the Forum Rules.

I'll have to get some things set up, but if you or him or whatever could use it and it would be helpful, i'd be happy to assist
 
Upvote 0
I'll have to get some things set up, but if you or him or whatever could use it and it would be helpful, i'd be happy to assist

Cool. And agreed, XDA definitely has its pros and cons! I post way more over here, but I find that XDA is a good place to glean information from, once you sift through the BS, arrogance, half-truths, misinformation, etc.!
 
Upvote 0
Struckn, you're a cheerleader for the rom. It's how I became familiar with and why I use Carbon. I follow the rom and the nightly s. I modify the asserts base on your tutorial. Thank you.


At worst a cheerleader won't acknowledge serious flaws in a rom. I have a Motorola Triumph dead on the shelf after flashing CM ICS when it was bleeding-edge. Everyone raved how smooth it was but not so much concern was expressed for how hot the battery became.


As to the USB tethering issue: Activating tethering actually establishes a connection however data is unable to be accessed on the desktop. The 2-05 nightly works. Within the rom, contained in the change-log txt file, there was a commit, on 2-06, which mentions tethering. The name of the guy who made the change is Dave Daynard, he doesn't appear to be part of the Carbon dev team. I don't know who to contact.


Struckn, kick some ass for me will you?
 
Upvote 0
Struckn, you're a cheerleader for the rom. It's how I became familiar with and why I use Carbon. I follow the rom and the nightly s. I modify the asserts base on your tutorial. Thank you.


At worst a cheerleader won't acknowledge serious flaws in a rom. I have a Motorola Triumph dead on the shelf after flashing CM ICS when it was bleeding-edge. Everyone raved how smooth it was but not so much concern was expressed for how hot the battery became.


As to the USB tethering issue: Activating tethering actually establishes a connection however data is unable to be accessed on the desktop. The 2-05 nightly works. Within the rom, contained in the change-log txt file, there was a commit, on 2-06, which mentions tethering. The name of the guy who made the change is Dave Daynard, he doesn't appear to be part of the Carbon dev team. I don't know who to contact.


Struckn, kick some ass for me will you?

I hear you loud and clear buddy! Won't deny the cheerleader role for sure. I guess I'm also lucky that I use my phone in a more basic manner than a lot of people, so the things I need or use frequently aren't usually the ones that are broken. I think I may have a camera fix coming, I am about to extract an .apk that worked earlier in the month for fixing the camera issue, it is the camera from Vanir ROM, and apparently it was incorporated into the Beanstalk ROM as well, so I am downloading both to see what I can do. Will dig into the tethering issue next!
 
Upvote 0
Hello! The camera started to freeze and after rebooting the camera doesnt last long until it crashesa again. Any idea whats going on?

OK people, here is a working .apk file for the camera issue, I extracted it from the 2/3/2014 build of Vanir ROM and used it to replace the one that came with the latest build of Carbon. Did a clean install and took a bunch of pictures, switched to video, back to camera mode, switched back and forth from rear camera to front camera, back to video, then back to camera, both front and rear. You get the point. No freezes or crashing. Hopefully there are no issues after prolonged usage, but I think I gave it a fair initial shakedown. Download this .apk file to your desktop, then open your zip of Carbon ROM, navigate to system folder, then app folder, and just drag and drop this .apk in, it will ask you about replacing the current one (don't rename anything or this won't work, it needs to be camera2.apk), accept the changes and then close the zip file. Happy flashing!

Camera2.apk
 
Upvote 0
OK people, Carbon is now doing the universal ROM thing as well, so look for d2lte to be the new download folder. These will still contain a device check in the asserts which will need to be removed, as d2vmu does not show as one of the approved devices (will update if this changes, don't have time to download the newest one right now).
 
Upvote 0
OK people, Carbon is now doing the universal ROM thing as well, so look for d2lte to be the new download folder. These will still contain a device check in the asserts which will need to be removed, as d2vmu does not show as one of the approved devices (will update if this changes, don't have time to download the newest one right now).

Downloading D2LTE 2/16 nightly right now. I'll edit post with more info

edit:
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att" ||
getprop("ro.product.device") == "d2spr" || getprop("ro.build.product") == "d2spr" ||
getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo" ||
getprop("ro.product.device") == "d2cri" || getprop("ro.build.product") == "d2cri" ||
getprop("ro.product.device") == "d2mtr" || getprop("ro.build.product") == "d2mtr" ||
getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" ||
getprop("ro.product.device") == "d2vzw" || getprop("ro.build.product") == "d2vzw" ||
getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || abort("This package is for \"d2att,d2spr,d2tmo,d2cri,d2mtr,d2usc,d2vzw,d2lte\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
is the new assert checks, d2vmu still not included

edit2: removed asserts, went with full wipe/factory reset and dalvik wipe, flashed rom, flashed apn fix, flashed gapps, rebooted, booted fine.
 
  • Like
Reactions: struckn
Upvote 0
The Carbon Team changed the updater-script file in the changeover from the D2SPR builds and the latest D2LTE (universal D2) build. There are no bootloader/device-specific script lines. Seeing this, I flashed 2/16 Carbon D2LTE without modifying the updater-script file. So far, so good.

I dirty flashed (over 2/13 D2SPR Carbon KitKat)
--wiped cache and Dalvik, then flashed (using Phil's):
1.) Carbon ROM, 2/16 (D2LTE)
2.) PA 0-day 2/13 Mini-Modular Android 4.4.2 GAPPS (I just wanted to update my GAPPS)
3.) DKP D2 Kernel, 2/13
4.) Optimized Dalvik
5.) Moped's APN fix #3

Re-wiped cache and Dalvik, rebooted.
Phone, MMS, WiFi, 4G LTE, 3G, and camera are all working well 3 hours in.

Perhaps we can look forward to being able to flash newer universal D2 roms intended to work for Sprint, without having to make any ROM updater-script file modifications.
 
  • Like
Reactions: upconvert
Upvote 0
Upvote 0
Upvote 0
Not sure what that means. Is there something different about carbon that it won't work with my mk5? CyanogenMOD works perfectly

PRL and Profile update are something you should be familiar with regardless, it is knowledge that should be somewhat mandatory for users of the SGS3, no matter which carrier you are on. From any TW ROM, you dial ##72786# on the dialer, and let the phone reset and reboot (the reboot will happen twice before the process is finished). This helps to fix a lot of weird signal/connectivity/data issues.
 
  • Like
Reactions: ssethv
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones