Search results

He means if it's installed directly through local upgrade, which it will.

Doesn't work on T-Mobile converted devices. You're gonna have to extract the payload.bin file and flash manually if you want to try this out.

Small correction, T-Mobile is running on Universal Profile 1.0 but they are not connected to Google's Jibe RCS hub, which means cross carrier RCS is not supported. I'm fairly certain the Samsung phones you mentioned don't have RCS working across carriers either. Now if enough people were to...

You don't know the objective of these dev previews. More than to let "flashaholics" test out the latest and greatest in Android, they're meant to help app developers get their apps ready for the new API level before it's made public. Previously, only Google devices received the beta updates...

can you tell me if it works with other ROMs? custom 9.0, not stock.

fixed!

wow I have no idea how that happened, because I didn't change the download link at all. anyway, it's fixed now, thanks for pointing it out.

mea culpa, fixed.

New update pushed! OP and second post updated. Thanks in part to ChriChri on Discord, I have acquired another Z1 and now I'm back with new builds! Let me know what you think! Also, we will be going official soon! As you may already be knowing, Carbon has started rolling out official...

New update is up! Download link is in the first post and changelog in the second. Sorry for the long hiatus. Ideally I would have wanted to fix the camera issue before releasing a new build, which is what I was trying to do. Unfortunately, I have not made any progress in that regard, which is...

Thread reopened at OP's request.

This was a test build not meant for release. If you're using this, don't complain about bugs.

You don't understand...it's impossible without Sony going nuts and releasing their stock sources (which they will never do). They had the Open Devices project which used crippled blobs for the camera and open source HALs working with 3.10, but that wasn't useable for anyone. If you have ever...

Definitely not. Even with kernel 3.10 we had a whole lot of trouble and was not worth the effort. Anything beyond that is pretty much impossible. Maybe the kernel can be upstreamed to the latest 3.4 release (minor version changes) but that would bring little to no changes, so that is not a...

When we go official it will support Delta updates. That should happen Soon™

I just tested it...it does work :confused:

Single HDR shots crash the camera. Non-HDR shots work. The camera app is basic at the moment but that will be taken care of in the next update. Mea culpa, it will be fixed ASAP. EDIT: Fixed!

Ambient display is already present. Settings > Display > Ambient Display.

Oh! I didn't notice the NFC being gone. It will be fixed ASAP.

While I would love to help you out, it is pretty much impossible for me because I am in a country that is not affected by the issue you speak of.

Don't bother. That is based on Sony's Open Devices Project, which was a good concept but did not provide any sort of usability whatsoever for msm8974 devices. Stick to 3.4.x and forget about unification.

Reserved Huge thanks to 0LDST4R for being kind enough to send me a sirius to work on! Looking forward working on this device a lot more in the coming days :) Changelog: 20/04/2019: ⚛ Fix NFC. ⚛ Improve performance and battery life. ⚛ Upstream Carbon updates (a lot of new goodies, check em...

Reserved

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...

IMPORTANT MODERATOR INFORMATION: Thread closed for GPL violation and failure of the OP to address it. It may be reopened in the future if OP decides to comply with the law.

Unsure of how legit that is because it seems like he's got our chipset wrong (SD400 instead of the obscure bcm that we actually have).

Use the latest TWRP (3.2.1 or newer)

Don't really see anything wrong in the logcat, so it could be an SELinux denial. Let me know if your problem is fixed if you set SELinux to permissive. On a side note, I have some news. My honami was unfortunately stolen from me a week ago, and as such I will not be able to continue...

Well, I removed support because during the first Pie bring up, Carbon didn't support f2fs and it broke the build. I never added it back because I didn't use it and didn't think anyone else would either. I will add it back for the next build. Thanks for catching that, fixed now!

I don't know. In general I do not support custom kernels, but I haven't made any significant kernel specific changes in this build so if that kernel worked with Carbon before, it should still work with this build.

Hello everyone! First of all, I'd like to apologize for the lack of communication these last few months. However, I now have a much improved build up for use! Changes include: * Fixed GApps lag (it's blazing fast now!) * SELinux enforcing * Fixed HW acceleration * Improved GPS (it's like Oreo...

Alright, here's the thing. Most of the "infected apks" you've listed are frankly outdated and we don't really need it anymore. Carbon includes them because they're part of AOSP and they're harmless. I can see how another ROM may not include them. I propose this: since our source comes out clean...

A) I am almost 100% sure the virus scanner you're using is not meant to scan system software. There is very little information on the internet about the threats listed, but what I could gather is that these detections are based on the apk's ability to use system-only permissions (such as...

Exciting!

+1. CarbonROM + VoLTE = pure bliss.

That's very weird. I will look into it. Thanks for the report.

Indeed. We also do not have any reference devices to look at, because BCM chips are hugely unpopular. In fact, ours is probably the bcm device with the newest official Android version (MM).

Android Wear is not based on Linux, only the underlying kernel is, and the kernel for the SmartWatch 3 is already open-source on Google's git. Android Wear, like Android itself, is licensed under Apache v2 and does not require the release of modified source code, which is why you don't see the...

Problem #1 is expected. Our device has a 16:9 display and when you set the camera resolution to anything that is 16:9, the black bars appear because of the space taken by the navbar. Unfortunately, that is how the app is designed, and since we're hard at work on Pie, it is unlikely that we would...

We use delta updates, which essentially only contain the files that have changed between your current version and the newest update. More often than not, this zip would be <100MB.

Nope, and we won't be unless we get official treble from OnePlus.

Duplicate --> Serves no purpose --> Closed.

Thread closed at OP's request.

Thread closed at OP's request.

It will not work. It requires a 64bit chipset.

Do you have a lockscreen password? If so, that could be it. If not, try default_password as your password.

Use TWRP 3.2.x

That sounds correct. You're saying you can't update OTA with this setup?

No, it is not. Our hardware does not support this. There might be a custom kernel that contains a hacky workaround though, so you can use that if you wish. You don't need the module to enable it, just kernel adiutor.

This should not be the case. TWRP can decrypt your phone. Have you tried getting an OTA update with Carbon? If it failed, then maybe you're running the wrong version of TWRP.