{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who's back? We're back.
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, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
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.
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.
Downloads:
Get CarbonROM
GitHub
Gerrit
Kernel source
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
CarbonROM, ROM for the Google Pixel
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Nightly
Created 2017-01-01
Last Updated 2018-03-17
Very nice! Ask and you shall receive, right?
quangtran1 said:
Very nice! Ask and you shall receive, right?
Click to expand...
Click to collapse
Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.
Myself5 said:
Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.
Click to expand...
Click to collapse
Thank you! Happy '17! I've always liked Carbon ROM.
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
aholeinthewor1d said:
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
Click to expand...
Click to collapse
gApps have always been problematic with every additional security layer added. With different slots, but shared data, I can envision it's getting more complicated.
Downloading.... It's like Christmas all over again. Thanks @Myself5!
quangtran1 said:
Downloading.... It's like Christmas all over again. Thanks @Myself5!
Click to expand...
Click to collapse
What's up with the Gapps thing. Do we flash after or are they built in.
@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!
This is rather nice to see. Thanks for your hard work.
aholeinthewor1d said:
Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.
Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.
Thanks!
Click to expand...
Click to collapse
They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.
I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.
quangtran1 said:
@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!
Click to expand...
Click to collapse
1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).
A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so
Regards
Myself5 said:
They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.
I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.
1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).
A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so
Regards
Click to expand...
Click to collapse
Thank you!
Carbon....No way
So we install it and then it boots the opposite slot? Is that what I'm understanding?
wow I thought carbon was dead. used to be my fav rom, thanks.
instructions on how to install?
Simer03 said:
Carbon....No way
So we install it and then it boots the opposite slot? Is that what I'm understanding?
Click to expand...
Click to collapse
It's installed in both slots. And yes, it boots into the slot that was not previously active. At this time, as the dev responded above, there's no GApps yet.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
fix-this! said:
wow I thought carbon was dead. used to be my fav rom, thanks.
instructions on how to install?
Click to expand...
Click to collapse
You install it like you'd install any ROM in a recovery such as twrp. Then install gApps. There's no gApps available yet.
So it installs to both slots does that mean it uses double storage space
dantexaiver said:
So it installs to both slots does that mean it uses double storage space
Click to expand...
Click to collapse
It's the same setup you have now being stock. There are 2 of a few different folders including /system which is where the software is stored. No difference
It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.
1) Does this have Slim Recents? I didn't see it listed on the features page.
2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
Myself5 said:
Pixel related info: Due to yet to be fixed issues, manually flashing GApps on the Pixel builds is not working on all ROMs. The GApps will be gone after booting. I'll might release an unofficial build with GApps included soon.
Click to expand...
Click to collapse
Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.
CZ Eddie said:
It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.
1) Does this have Slim Recents? I didn't see it listed on the features page.
2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
1) No.
2) The feature page is outdated, but will be updated later this day.
The ROM is having full substratum support, you only need to root and install substratum.
Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.
Click to expand...
Click to collapse
Will provide a build in the next days.
Flashing GApps "worked" after some dirty hacks to the installer Well... "working" as far as "it was there and then dissapeared after the boot" can be defined
Are there "legal" reasons Gapps can't be built in or something? Just curious because I've always wondered how it's OK to release some builds with them built in
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Standard Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you
Click to expand...
Click to collapse
(This is a Copy and Paste from a Official Tread)
Brief Discription and History of the Team:
Dirty Unicorns is a project that started out with no name. It was a project that was first created based off AOKP back in the early days of Jelly Bean because of curiosity. In the early days, it was just a one man show on one device (EVO 3D). However, many others have joined the project since and it has grown a lot. We have seen a wide variety of talent contribute to this project of ours and many of our contributors have gone on to help other projects, and that is ultimately why we do what we do.
Once Jelly Bean was over, we decided in Kitkat to move to a new base, which was OmniROM. While AOKP was fun, OmniROM proved to be even more exciting because it challenged us to see what we could with something different.
With Lollipop, we have moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. With that said, it has been an awesome learning experience and it's still not over! We are still learning every day and continue to move forward.
Few more things we will say is that we don't accept nor ask for donations. We don't believe in that. Everything that is necessary to keep this project going is out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc.....
All we do ask is that you search, read and try to enjoy the process with us!!
Flashing Instructions:
For xt907 users= Must be running the 183.46.10 or 183.46.15 Stock KKBL
--Have to have booted the .10 or .15 at lease once to insure sensors are active.
--Verify that you're using the latest version of TWRP 2.8.5.0 or newer
--Perform a FULL WIPE as described below if coming from another ROM
(A full wipe is when you wipe system/data/cache and Dalvik)
--Flash the latest version of this ROM
--Flash recommended GAPPS linked below
--Reboot and ENJOY!!
**If you fail to follow these instructions, don't bother reporting any bugs**
**If coming from a previous lollipop version, wipe system and cache**
Change Log:
Code:
Version 9.3
- Update to Android 5.1.1
- Materialize DSPManager
- Fix SysUI FC for Themes with QS mods
- Change checkboxes to switches
- Remove Voice Dialer
- Fix for Play Services deep sleeping
- Fix various Theme Engine issues
- Add back notification LED settings backend
- Fix NavRing FC
- Expose values for our applications to be themed
- Hide lights settings if device doesn't support them
- Don't set preferred APN's automatically
- Fix battery and notification lights
- Various translations
For detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]gerrit.dirtyunicorns.com[/URL]
Credit and Thanks:
We would like to give thanks to everyone that contributes to the Android community, small or big because every bit counts. Although we can't list each and every contributor within the Android community, we would like to highlight some of the teams and individuals that have made it possible NOT only with just this version of DU but throughout the years because we don't ever want to forget where we came from.
That said, on behalf of the DU team we say THANKS to....
JMZ Software
Baby Jesus
Code Aurora Forum
Omni ROM
Android Open Kang Project (AOKP)
Android Ice Cold Project (AICP)
XDA-Developers
SlimROMs
Preludedrew
Max Weninger
Team Black Out
CyanogenMod
David Hacker
*If we have left someone or some team out, please accept our apologies*
Links to Stop by and check in..
-- G+ community
-- ROM Source
-- Gerrit
Kernel Source:
-- My Github
Download Links:
xt907-ROM
DU_xt907_5.1.1_20150525-1824.v9.3-UNOFFICIAL
Suggested Gapps
Pick Your Poison
Extra Audio enhancements.....
DSP 2 ViperAudio TWRP installer
I don't normally ask for Donations and I will not start now,
I didn't do anything but synced in the source and made the build...
Flash and Enjoy....
Mine
Mine Too
At last!!!!
Enjoyed this on my Moto X. Now it's time to get dirty with Razr M. Downloading it.... Will report you with my findings.
i try this rom just now. Its Good...
one thing weird is,
i installed AdAway app, make it enable and download necessary data file. then after some times, it disable by it self....
can you look up about it?
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i try this rom just now. Its Good...
one thing weird is,
i installed AdAway app, make it enable and download necessary data file. then after some times, it disable by it self....
can you look up about it?
Liking this ROM so far
dark.blue said:
i try this rom just now. Its Good...
one thing weird is,
i installed AdAway app, make it enable and download necessary data file. then after some times, it disable by it self....
can you look up about it?
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
i try this rom just now. Its Good...
one thing weird is,
i installed AdAway app, make it enable and download necessary data file. then after some times, it disable by it self....
can you look up about it?
Click to expand...
Click to collapse
I too installed DU, and liking it very much so far. Everything seems to work, and snappier than earlier versions of CM12.1
I'm not sure this has anything to do with your AdAway app problem, but FYI, this ROM has a built-in Ad Blocker. It's under settings, Dirty Tweaks, System.
beeewell said:
I too installed DU, and liking it very much so far. Everything seems to work, and snappier than earlier versions of CM12.1
I'm not sure this has anything to do with your AdAway app problem, but FYI, this ROM has a built-in Ad Blocker. It's under settings, Dirty Tweaks, System.
Click to expand...
Click to collapse
i know about it... but the build it Ad Blocker, always failed to Update Host file....
thats why i use another app...
is it at yours the AdBlocker works just fine? it able to download data and update host file?
You are correct. The built in app hosts update fails.
AdAway works, but is disabled after a reboot.
beeewell said:
You are correct. The built in app hosts update fails.
AdAway works, but is disabled after a reboot.
Click to expand...
Click to collapse
hmm so whats wrong?
its happend in LuquidSmooth too...
but works well in cm12.
Guys this issue has been brought up on G+ and Alex replied back that the reason it is failing is to many people are trying to update at one time. Try again later and it will update. Adaway tries to apply the host files but yeah it don't stick because this ROM has its own. So if you use this feature use the built in one.
Sent from my LG-VS980
Kick ass ROM man. Thanks!
I'm having lockscreen issues that are making this barely usable. Whenever I turn the screen on to the lock screen, it is unresponsive. I can turn it off and back on and the lock screen is translucent, then off and back on again, and the lockscreen is responsive again. However, about every other time, the lockscreen will become unresponsive again, and will restart the system UI, which takes around 30-40 seconds. Other than that, the ROM is mostly good. It is a bit choppy on mine at times (I am on KKBL), but usable. Is there any future for incorporating kernel controls into this ROM? I have setCPU, which has allowed me to change some parameters that made it a bit smoother (it was VERY choppy at the beginning), but this is a very difficult daily driver for me at this point.
slapshot2286 said:
I'm having lockscreen issues that are making this barely usable. Whenever I turn the screen on to the lock screen, it is unresponsive. I can turn it off and back on and the lock screen is translucent, then off and back on again, and the lockscreen is responsive again. However, about every other time, the lockscreen will become unresponsive again, and will restart the system UI, which takes around 30-40 seconds. Other than that, the ROM is mostly good. It is a bit choppy on mine at times (I am on KKBL), but usable. Is there any future for incorporating kernel controls into this ROM? I have setCPU, which has allowed me to change some parameters that made it a bit smoother (it was VERY choppy at the beginning), but this is a very difficult daily driver for me at this point.
Click to expand...
Click to collapse
I will have to play with my xt926 a bit more to see if I can duplicate your lockscreen issue... As far as CPU control. I use Kernel Auditor from the PlayStore. Well worth the donate version,
Sent from my VS980 4G
XT907 kk unlocked bootloaer, twrp 2.8.6.0 . after flash, reboot and stuck in the DU logo
kcuongh said:
XT907 kk unlocked bootloaer, twrp 2.8.6.0 . after flash, reboot and stuck in the DU logo
Click to expand...
Click to collapse
Same here on all counts.
kcuongh said:
XT907 kk unlocked bootloaer, twrp 2.8.6.0 . after flash, reboot and stuck in the DU logo
Click to expand...
Click to collapse
I fixed mine by installing CM 11 first. Wiping, then installing DU.
nobe1976 said:
I will have to play with my xt926 a bit more to see if I can duplicate your lockscreen issue... As far as CPU control. I use Kernel Auditor from the PlayStore. Well worth the donate version,
Sent from my VS980 4G
Click to expand...
Click to collapse
I've been running it a couple of days, and I've experienced some delays with the lock screen opening as well.
Not quite as bad. Just locks up for a second.
GPS isn't working.
eta: not ROM related
Thread search fail (XDA contact form fails too?..)
(.. So posting thread draft fail here?)
Pretty simple "Adaway" keyword search in a thread ..
http://forum.xda-developers.com/droid-razr-m/development/rom-dirty-unicorns-5-1-1-t3118112
.. Keeps implying bad link?
https://drive.google.com/file/d/1NOOI5CdfbGXIds8i_XczCEKtgVS4n4klXw/view?usp=docslist_api
THANKS HEROES for all you do..
.
.
.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICPAndroid Ice Cold Project
AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, Rom has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CM when it comes to hardware, drivers and some features.
If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!
.
.
.
.
.
In the beginning we would like to thank:
CM team
maxwen
Thoemy
SlimBean rom team
ParanoidAndroid team
CarbonRom team
LiquidSmooth rom team
Omni rom team
DU team
teemodk
audahadi
Community
@LorD ClockaN
@zipsnet
@n3ocort3x
@semdoc
@eyosen
@alienmind
@Chezbel
@Drgravy
@eboye
.
.
.
We are now paying for servers that build nightlies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 10
Downloads:
AndroidFileHost
BasketBuild
((I've automated the builds but haven't updated this mirror in a while, when I find time I'll update it))
Mirror by @cajunflavoredbob: Files
Recommended Gapps: (ARM64/6.0)OpenGapps
Full Changelog link: Complete change log by the download link
Torch is spotty
SEPolicy is a WIP, set SELinux to permissive for best performance
ROMS should contain everything you need to enjoy Marshmallow. You are not required to install any Add Ons, simply download the latest ROM, gapps, flash it, and go!
You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup - these can cause stability issues that are very hard to debug. If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience strange behavior.
How to flash:
Don't do it if you don't know it
Full wipe, flash rom, flash gapps, boot
ROM has gapps persistance in between dirty flashes
To update to M, you must flash the M modem and perform a full wipe
KERNEL:
Kernel in this rom follows CM source with custom additions.
Kernel has support for primary MultiROM ROM (includes kexec hardboot support)
PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed.
You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. Zip gets saved under AICP_ota folder on your internal SDcard.
If you want to contribute to the AICP or wanna see what is being worked on/merge feel free to visit our gerrit, link is at the bottom!!!
IceColdJelly AICP G+ community
kernel github
device tree github
rom github
rom gerrit
You want to see a normal night at the DEV office, click here!!
XDA:DevDB Information
AICP for h811, ROM for the LG G4 (T-Mobile)
Contributors
superfes
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2016-03-08
Last Updated 2016-04-19
You beautiful, beautiful human! I'll be flashing immediately! Thank you sooooo much!
Downloading now will report back on how it is
Edit: Running amazingly right now smooth in general but like many ROMs recently there's a little bit of a notification area lag. I know Devs are working on a fix so overall great ROM.
TacoTuco said:
Downloading now will report back on how it is
Edit: Running amazingly right now smooth in general but like many ROMs recently there's a little bit of a notification area lag. I know Devs are working on a fix so overall great ROM.
Click to expand...
Click to collapse
Awesome, I hadn't tested this one personally ^_^
The only issue I've encountered since flashing last night is during one phone call, the screen did not light up when I moved it away from my face. I made another call right after that, and it worked fine, so perhaps it was just a fluke.
Loving the customizations. I've missed using a good non-stock ROM. Is there a dark mode built in or just CM themes for that?
CM theme engine
Rock on Superfes! Thanks man
First of, this is my favorite ROM yet! So many customizations! And that awesome boot screen! Thank you for building/sharing.
I gave this a go yesterday on the 3/8 nightly. Google now crashed after doing the ok Google thing consistently, and system ui crashed a couple times. I'm giving it another go today. This is too good not to keep playing with, I'm downloading the 3/9 right now, I'll leave some notes after a days use.
Thanks again!
How is the cell signal on this rom??? I want a cm rom with good signal strength. I'm tired of a lot of cm based roms having the cell drop issue
mrbox23 said:
First of, this is my favorite ROM yet! So many customizations! And that awesome boot screen! Thank you for building/sharing.
I gave this a go yesterday on the 3/8 nightly. Google now crashed after doing the ok Google thing consistently, and system ui crashed a couple times. I'm giving it another go today. This is too good not to keep playing with, I'm downloading the 3/9 right now, I'll leave some notes after a days use.
Thanks again!
Click to expand...
Click to collapse
So after using this today, I get the same lag with notifications shade, recents, and lockscreen. Google now still crashing with ok Google commands using latest open gapps nano. Google now does the voice commands just fine, I wouldn't know if I didn't get the little sorry Google now crashed message.
Same story I had with AOKP pretty much.
Overall I love both the ROMs, I'm looking forward to improvements with the lag stuff. Being nightlies I hope that comes around.
---------- Post added at 10:47 PM ---------- Previous post was at 10:44 PM ----------
Eddiekool12 said:
How is the cell signal on this rom??? I want a cm rom with good signal strength. I'm tired of a lot of cm based roms having the cell drop issue
Click to expand...
Click to collapse
Works fine for me
Eddiekool12 said:
How is the cell signal on this rom??? I want a cm rom with good signal strength. I'm tired of a lot of cm based roms having the cell drop issue
Click to expand...
Click to collapse
Slightly worse than stock, but not by much. Maybe a 10-15db difference.
mrbox23 said:
So after using this today, I get the same lag with notifications shade, recents, and lockscreen. Google now still crashing with ok Google commands using latest open gapps nano. Google now does the voice commands just fine, I wouldn't know if I didn't get the little sorry Google now crashed message.
Same story I had with AOKP pretty much.
Overall I love both the ROMs, I'm looking forward to improvements with the lag stuff. Being nightlies I hope that comes around.
Click to expand...
Click to collapse
I've got the same issue. It only happens for me with Google on Tap. If I'm in the Google app, then it seems to work fine.
There's a little bit of lag, other than that, good rom
I've updated to the 09 March ROM. When I choose to "Hide sensitive notifications" on the Lockscreen, my notifications are also hidden while I'm unlocked. If I "Show all notifications" then it shows them again while unlocked. This did not happen on the 08 March ROM.
EDIT: After another short, 2 minute, phone call, the screen did not turn back on after moving it away from my face. I used the power button to turn it back on and end the call. I made another call after that, also under 2 minutes, and it worked fine.
I have one issue with this. The lock screen has a lot of lag. Not sure if I'm missing something but its super laggy and sometimes not responsive.
Sent from my LG-H811 using Tapatalk
@superfes
I have two thoughts for you. First, I would like to ask you to please make a post or something when you update the ROM, that way, those of us subscribed to this thread will get a notification about it. Secondly, I'm glad to see you drop dev-host from your mirrors. I will offer you the option to use my personal site for mirroring, if you'd like. It's a very fast server with no bandwidth or storage limit or ads. Let me know what you think.
cajunflavoredbob said:
@superfes
I have two thoughts for you. First, I would like to ask you to please make a post or something when you update the ROM, that way, those of us subscribed to this thread will get a notification about it. Secondly, I'm glad to see you drop dev-host from your mirrors. I will offer you the option to use my personal site for mirroring, if you'd like. It's a very fast server with no bandwidth or storage limit or ads. Let me know what you think.
Click to expand...
Click to collapse
I'll add the date to the subject ^_^
What's your site?
superfes said:
I'll add the date to the subject ^_^
What's your site?
Click to expand...
Click to collapse
http://mirror.cajunflavoredbob.com/superfes/index.html
Whipped this up in about 10 minutes. There's room for screenshots in the header. Download speed is pretty zippy right now.
EDIT: I can't check for a title change everyday. Either make a post or PM me when there's an update, and I'll add it to the mirror, or I'll update it whenever I notice it.
cajunflavoredbob said:
http://mirror.cajunflavoredbob.com/superfes/index.html
Whipped this up in about 10 minutes. There's room for screenshots in the header. Download speed is pretty zippy right now.
EDIT: I can't check for a title change everyday. Either make a post or PM me when there's an update, and I'll add it to the mirror, or I'll update it whenever I notice it.
Click to expand...
Click to collapse
Cool, I'll throw this up in the main if that's okay with you.
I can probably post on updates sometimes, just don't wanna get annoying with it ^_^
superfes said:
Cool, I'll throw this up in the main if that's okay with you.
I can probably post on updates sometimes, just don't wanna get annoying with it ^_^
Click to expand...
Click to collapse
That's fine with me.
Thank you Fester! It's almost there with the lags, huge improvement. I'm going to hold off for a couple more builds, soon hopefully it will be as smooth as cm13
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTALLATION
* Download ROM and the latest GAPPs (Pico).
* Full wipe and format is ALWAYS suggested to avoid odd issues.
* Flash ROM, GAPPs.
* SUPERSU INSTALLATION
* Wipe cache & dalvik cache
* Reboot
CREDITS
@monster1612 @Hashcode @transi1
Contributors:
@alexander_32
Version Information
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.101+
Status: Release Candidate
Current Version: M4B30X
SOURCE
local_manifest
jem
bowser-common
omap4-common
kernel
proprietary
Want to support development? You can consider donating, my email is [email protected]. I spent countless of hours with this
DISCLAIMER:
Code:
Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
KNOWN ISSUES
You tell me
TWRP BUILDS
Created 2016-10-17
Last Updated 2016-10-23
Last build was made using @r3t3ch ' s (THIS TOXIC TEENAGER IS NOT WELCOMED HERE AND MY OTHER THREADS) repositories. You'll not see his builds anymore
FEEL FREE TO USE MY SOURCE AND POST BUILDS HERE
My laptop is too slow, I don't have jem (so I can't test it) and I don't have time for that.
Here's is original thread for tate.
THANKS FOR UNDERSTANDING.
@ rat3ch will not bring new builds here. He's a disgrace.
login/passwd requested
Hi Alexander
Thanks a lot for your work bringing high quality ROMs to us jem users.
When I click on the ROM download link above, I get a login/passwd request? Is this normal?
Also, I don't understand how this new ROM differs from the previous one linked on the other thread (2016_10_13)?
Could you explain a bit?
Thanks in advance.
What's the change from previous build?
Thanks
bapi28 said:
Hi Alexander
Thanks a lot for your work bringing high quality ROMs to us jem users.
When I click on the ROM download link above, I get a login/passwd request? Is this normal?
Also, I don't understand how this new ROM differs from the previous one linked on the other thread (2016_10_13)?
Could you explain a bit?
Thanks in advance.
Click to expand...
Click to collapse
My bad, it was a link for me. It's fixed now. The last build was made by one inadequate guy, who went too far and screwed up video and audio streaming with his commits. It wasn't made using my source, which is posted in the description. You should use a previous one for now. Or BeanStalk (probably the best release) or just go try what works best for you.
My source is better, there is no issues with YouTube (it sometimes glitches on 720p, but it's not embarrassing like patchy sound in last build). I'm talking about tate version, off course. But it must also affect jem as well.
You can use this source and make a new updated build. Honestly, I have no time for this and I can't even test it.
redhonker said:
What's the change from previous build?
Thanks
Click to expand...
Click to collapse
Please, read my explanation to @bapi28. Thanks.
Thanks
OK thanks a lot for the clarifications.
Actually I was about to try the 2016_10_13 CM build, but I understand this is the one that got garbled with inappropriate sources, so I'll skip this one and wait for the next. Reading your OP, I initially thought that there was another 2016_10_17 "clean" build released somewhere, but couldn't find where to download it. Unfortunately I don't have the knowledge and toolchains to build it myself, so I'll have to wait for somebody to do it for the community. However, I am definitely willing to test if you need a jem owner to test-ride new experimental builds.
I'm a long time lurker here but I don't post very often, so let me use this opportunity to thank all the developers and say that I am quite impressed (to say the least) by the outstanding work you guys are achieving to support this old machine (almost 4 years old already), including providing the latest TWRP btw. I have been a long time user of hashcode's unofficial CM10 releases and then official CM10.2 (I skipped the alpha CM11 and CM12 entirely). Currently I am using transi1's Revolution Remix v5.7..4 ROM (2016_09_21), which was released about the same timeframe as the previous CM13 (2016_09_17) and Beanstalk (2016_09_20). It runs extremely smooth and responsive, apart from somewhat long bootup times (which is no big deal really because it is rock stable for me, I only needed to reboot it twice in a month).
Note: I'm probably not a "power user" so I don't know the actual differences and distinctive features between flavours CM, Beanstalk, Resurrection,... That's why I intend to try them all to check for myself. But I'd be grateful if anybody can point me to a detailed feature comparison.
bapi28 said:
OK thanks a lot for the clarifications.
Actually I was about to try the 2016_10_13 CM build, but I understand this is the one that got garbled with inappropriate sources, so I'll skip this one and wait for the next. Reading your OP, I initially thought that there was another 2016_10_17 "clean" build released somewhere, but couldn't find where to download it. Unfortunately I don't have the knowledge and toolchains to build it myself, so I'll have to wait for somebody to do it for the community. However, I am definitely willing to test if you need a jem owner to test-ride new experimental builds.
I'm a long time lurker here but I don't post very often, so let me use this opportunity to thank all the developers and say that I am quite impressed (to say the least) by the outstanding work you guys are achieving to support this old machine (almost 4 years old already), including providing the latest TWRP btw. I have been a long time user of hashcode's unofficial CM10 releases and then official CM10.2 (I skipped the alpha CM11 and CM12 entirely). Currently I am using transi1's Revolution Remix v5.7..4 ROM (2016_09_21), which was released about the same timeframe as the previous CM13 (2016_09_17) and Beanstalk (2016_09_20). It runs extremely smooth and responsive, apart from somewhat long bootup times (which is no big deal really because it is rock stable for me, I only needed to reboot it twice in a month).
Note: I'm probably not a "power user" so I don't know the actual differences and distinctive features between flavours CM, Beanstalk, Resurrection,... That's why I intend to try them all to check for myself. But I'd be grateful if anybody can point me to a detailed feature comparison.
Click to expand...
Click to collapse
You actually don't need knowledge to make a build. I can tell you exactly what to do, all you need is Ubuntu 14.04+ (or Linux 17.3), 100Gb+ free space, 2+ cores and 4+ GB of RAM. You just need to type some commands and download the source.
OK so let's try to learn how to build this thing
I am under Linux OpenSuSE 42.1, have approx. 200 GB free HD space left, 8 GB RAM, 4 core intel Haswell 4570s.
If you can give me the detailed instructions, I will try to build it.
Thanks.
bapi28 said:
I am under Linux OpenSuSE 42.1, have approx. 200 GB free HD space left, 8 GB RAM, 4 core intel Haswell 4570s.
If you can give me the detailed instructions, I will try to build it.
Thanks.
Click to expand...
Click to collapse
I've left you a PM.
PLEASE REDOWNLOAD THE BUILD
https://www.androidfilehost.com/?fid=457095661767103968
Installation: Full wipe/Flash ROM + OpenGApps
Previous garbage was removed.
Big thanks to @bapi28 for the help.
Also, I strongly recommend you to disable Snap Camera or better delete it (I always delete system Camera app)
alexander_32 said:
FEEL FREE TO USE MY SOURCE AND POST BUILDS HERE
My laptop is too slow, I don't have jem (so I can't test it) and I don't have time for that.
Here's is original thread for tate.
THANKS FOR UNDERSTANDING.
@ rat3ch will not bring new builds here. He's a disgrace.
Click to expand...
Click to collapse
I can help building cm13 for jem. Here is the build 20160103 uploaded, it's built with alexander_32's sources and the last upstream changes. I'm going to upload the builds here.
manu3193 said:
I can help building cm13 for jem. Here is the build 20160103 uploaded, it's built with alexander_32's sources and the last upstream changes. I'm going to upload the builds here.
Click to expand...
Click to collapse
Thanks
alexander_32 said:
Thanks
Click to expand...
Click to collapse
I've been using the ROM in the last days and it's very smooth and stable, i've noticed some SELinux denials, but is good for daily use.. I'm gonna get some logs and check what's going on when i'll have free time.
I think it runs perfectly. Start up is quite quick, and the update process only took 1 minute. Amazing!
manu3193 said:
I can help building cm13 for jem. Here is the build 20160103 uploaded, it's built with alexander_32's sources and the last upstream changes. I'm going to upload the builds here.
Click to expand...
Click to collapse
New build: 20161107 here
Thanks for all the great work and info here. It has been a while since I have messed around with TWRP and updating my jem. I'm currently on CM11 and looking forward to trying this out. I was hoping for a few pointers so I don't mess something up. I have updated TWRP to 3.0 in preparation for this. I downloaded the latest rom, the Gaaps pico arm 6.0, the UPDATE-SuperSU-v2.76-SYSTEMMODE.zip.
For the "Full Wipe", do I just wipe the Data, Cache, and Dalvik that is pre-selected, or do I need to do an advanced wipe and check extra boxes (Internal Storage, System)?
And the Format that is recommended, will that leave any folders untouched? Where do I put the rom etc, so they will be there when it is time to flash?
Then I install the rom, then Gaaps, then SuperSU, and then wipe the cache and dalvik and reboot.
Thanks for any info you can offer.
brotherhaslip said:
Thanks for all the great work and info here. It has been a while since I have messed around with TWRP and updating my jem. I'm currently on CM11 and looking forward to trying this out. I was hoping for a few pointers so I don't mess something up. I have updated TWRP to 3.0 in preparation for this. I downloaded the latest rom, the Gaaps pico arm 6.0, the UPDATE-SuperSU-v2.76-SYSTEMMODE.zip.
For the "Full Wipe", do I just wipe the Data, Cache, and Dalvik that is pre-selected, or do I need to do an advanced wipe and check extra boxes (Internal Storage, System)?
And the Format that is recommended, will that leave any folders untouched? Where do I put the rom etc, so they will be there when it is time to flash?
Then I install the rom, then Gaaps, then SuperSU, and then wipe the cache and dalvik and reboot.
Thanks for any info you can offer.
Click to expand...
Click to collapse
Yes, you need to go to advanced wipe and check everything. Then connect jem to your PC copy all the files and
Then I install the rom, then Gaaps, then SuperSU, and then wipe the cache and dalvik and reboot.
Click to expand...
Click to collapse
Everything should be fine.
alexander_32 said:
You actually don't need knowledge to make a build. I can tell you exactly what to do, all you need is Ubuntu 14.04+ (or Linux 17.3), 100Gb+ free space, 2+ cores and 4+ GB of RAM. You just need to type some commands and download the source.
Click to expand...
Click to collapse
My primary machine would fit all the requirements you've laid out. Please point me to the build instructions, I'd like to get my feet wet in this wonderful world The most I've done with Android customization is playing with Android Kitchen tool (the ROM failed miserably, that is another matter)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
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!
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) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
For this ROM to work you need to use the latest ODM Images. If you need additional guidance on how to do that, please refer to Sonys Guide on how to flash an ODM Image.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
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
CarbonROM, ROM for the Sony Xperia XZ
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2018-03-31
Last Updated 2018-07-19
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
LuthfiKun said:
No one tried this rom yet? I have a problem over here. It keeps asking for password after the CarbonROM logo even though I wipe everything clear, any ideas? What I was doing was flash 41.3.A.2.99 with everything wiped, flash ODM, flash TWRP, flash the rom and then Pico OpenGapps. Something wrong with my procedure? Thanks in advance.
EDIT1 : Oh yeah, forgot to mention my device is F8332, it isn't supported?
Click to expand...
Click to collapse
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Dual sim support?
Myself5 said:
Use the "format data" option in TWRP to get rid of encryption, wipe doesn't clear encryption. If coming from stock, thats necessary unfortunately due to differences in the encryption used. Otherwise (if coming from AOSP) the password its asking for would be the one you used before.
Click to expand...
Click to collapse
Alright format it is.
agentsandy007 said:
Dual sim support?
Click to expand...
Click to collapse
No it isn't. At least out of the box. You can find a patch on Sony AOSP Build thread.
Volte Supported??
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Klaus N. said:
First of all, thanks alot @Myself5 and all other devs, who are working hard to bring this to our XZ :good:
My experiences after 1 day:
- rom is very smooth and snappy.
- root via Magisk v16 & Xposed 90.1-beta3 (systemless) works flawlessly
- the fp sensor always works, but it's not as sensitive as with stock
- night light worked - until I've installed Substratum and a Substratum theme, but after that it doesn't work anymore (even after deactivating, uninstalling the theme, a system restart and deinstalling the Substratum app it sill doesn't work). Also a dirty flash of the rom.zip didn't help to get it working again.
- the build-in camera takes acceptable pics (not as well as the stock camera, but acceptable); also focussing is a little slower than stock. Another thing is, it's not possible to chance the location to save the pics to the ext. sdcard.
- formatted as a portable storage, the ext. sdcard item on the left of the status bar can't be removed (see attachement)
- the battery consumption is a bit high (from 100 % to 98 % in 1 h - without doing anything)
But in the whole, it's really promising for th 1st official build :good::good::good:
Click to expand...
Click to collapse
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Can you upload screen recording of rom from home to settings and other functions.
I plan on flashing this soon, but I figured I'd tell you, your link to the Carbon FAQ is broken.
ilininja said:
Hello, is the battery life when used good ? As good as stock ?
And does it have that bug when if you record video the result will be green ?
Click to expand...
Click to collapse
The battery consumption while in use is ok. But my device doesn't go into deepsleep while the screen is off. So I had lost about 23 % in 10 hrs - leaving the device untouched!
Video recording works; I haven't noticed that bug.
Saroj11488 said:
Can you upload screen recording of rom from home to settings and other functions.
Click to expand...
Click to collapse
Sorry, I went back to stock for now, as there's a new stock fw (41.3.A.2.107).
I have a few bugs to report. First, the fingerprint sensor is extremely slow, about half or even one third of the speed compared to stock. Second, could you guys please fix the deepsleep? That one is not working for now. And third, Night Light does not work at all...
Thank you for updating the XZ to Android 8.1 I am glad to see carbon rom on this device although it is not that stable for now.
Really nice ROM and I'm looking forward to make this my daily driver, I tried it for two days and these are the bugs I found:
1: GPU performance is really bad with 2d games and google maps lagging all the time when they never do on stock
2: CPU performance is inferior compared to stock, especially single threaded
3: enabling 120 hz display won't do anything and the settings or UI will crash when leaving the page
4: fingerprint seems to be sometimes less responsive, usable but can be improved
Camera is not so bad and the modded google camera works well, hopefully this will become the first proper AOSP based platform for this device that has only seen failures until now, keep up the good work.
Can I dirty flash this rom for just update?
I use Carbon Rom 3/31 version, but I can't use delta update because my device cannot receive the stock script.
I must change the rom script with Notepad+.
So...can I use dirty flash or....could you manage it?
Thanks for continously updating this rom and thank you for fixing the bug with the fingerprint sensor.
I'm not sure if deepsleep has been fixed but there is a big problem with playing music. I can't even play any music track at all...
Hello, looking forward to make this my daily driver, is it possible ?
What I would want is decent battery life and camera.
Hello. I tried to listen to music after installing the ROM, but the earphones are disconnected as soon as they are connected to the smartphone.
The earbuds pfe 132 and are made up of earphones with an iphone microphone.
L'ily said:
Clean flashed the 10th build along with Rytekk's dual-SIM patch, Pico Open GApps and Magisk 16.3 to my F8332 and other than that annoying SD notification (which can be banished to the notification drawer by making System UI notifications low priority) and Night Light not working, the only other major issue raised ITT of the CPUs not entering Deep Sleep is fixed according to Adiutor.
Great stuff. I haven't been able to standardise on one ROM since the CM days (interesting side note, it looks like you built the kernel for the NOCT build on my Z2 tablet).
I recommend this to anyone for daily use. Also, lower your expectations to realistic levels guise. I remember when XDA threads were for flagging major broken functionality, not complaining that a few amateur enthusiasts weren't putting out work that competed on every indicator against the finished product of a multibillion-dollar for-profit international conglomerate.
Sent from my Sony Xperia XZ using XDA Labs
Click to expand...
Click to collapse
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Hello, with the 10th build I have a problem with the installation, it keeps telling me that Google services framework stopped.
Any help ?
(V11 vendor image odm, formated data)
BigMixman said:
Could you please give a link to that dual SIM patch?I have flashed this ROM on my F8332 successfully but none of my SIM cards works
Click to expand...
Click to collapse
Add these lines in build.prop, and reboot.
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
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! As always, make sure to do backups.
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) 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.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
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!
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?