Develop Bugs

[ROM] [Unofficial] [V9.2]Dirty Unicorns 5.0.2 {Honami} [UPDATE] [APR 8 2015]

{
"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"
}
About Us:
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!!​
Kernel Source:
https://github.com/cyanogenmod/android_kernel_sony_msm8974
Flashing Instructions:
- Flash any other kernel which has recovery built in
- Perform a FULL WIPE as described below if coming from another ROM
(A full wipe is when you wipe system/data/cache/internal and/or sdcard)
- 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:
[B]Version 9.0 [/B]- Initial Release of Lollipop
For detailed change log, check [URL="http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z"]http://gerrit.dirtyunicorns.com/#/q/status:merged,n,z[/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
*If we have left someone or some team out, please accept our apologies*
Download Links:
Version 9.0 - https://www.androidfilehost.com/?w=files&flid=25354 --- My AndroidFileHost DU folder
Recommended GAPPS - DU TBO Gapps || Banks Gapps || 64-bit Gapps
Other Links:
G+ community - https://plus.google.com/u/0/communities/109738128866939227235
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
Jira (Bug Report / Feature Request) - http://jira.dirtyunicorns.com/
XDA:DevDB Information
Dirty Unicorns, ROM for the Sony Xperia Z1
Contributors
Saatvik Shukla
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2015-01-28
Last Updated 2015-04-07

Reserved
Screenshots http://forum.xda-developers.com/showpost.php?p=58482662&postcount=2

Reserved

Saatvik Shukla said:
Kernel Source:
https://github.com/cyanogenmod/android_kernel_sony_msm8974
Click to expand...
Click to collapse
The kernel source above is different to the one in your github: https://github.com/saatvik2012/android_kernel_sony_msm8974
which is forked from crdroidandroid
I ask because I was able to compile DU for z3-compact using the CM12 kernel you mentioned but it does not get past the sony logo. I was told that others had the same problem.
Did you come across that problem? Does crdroidandroid kernel fix the issue?
Thank you in advance

m0d said:
The kernel source above is different to the one in your github: https://github.com/saatvik2012/android_kernel_sony_msm8974
which is forked from crdroidandroid
I ask because I was able to compile DU for z3-compact using the CM12 kernel you mentioned but it does not get past the sony logo. I was told that others had the same problem.
Did you come across that problem? Does crdroidandroid kernel fix the issue?
Thank you in advance
Click to expand...
Click to collapse
As what i feel, its because of the Toolchain. I experienced similar thing with the LiquidSmooth build.
Haven't got time to look into the matter yet, but thats what i suspect is.
br
s

Thanks man

Any known bugs in this ROM?

on this rom for close to a day. so far everything works. extremely snappy.

Camera working??
Câmera is working???

everything works afaik. haven't found any bugs YET. much better than the other lollipopo roms i've tried thus far

Can you flash this rom with locked bootloader without any worries?

pin70 said:
Can you flash this rom with locked bootloader without any worries?
Click to expand...
Click to collapse
Nooooooo unlocked bootloader ONLY sorry man

ploopower79 said:
Nooooooo unlocked bootloader ONLY sorry man
Click to expand...
Click to collapse
Hmmm, if i unlock the bootloader, will i be able to easily lock it again so i can install the official lollipop when it comes out?

pin70 said:
Hmmm, if i unlock the bootloader, will i be able to easily lock it again so i can install the official lollipop when it comes out?
Click to expand...
Click to collapse
The process itself is not hard to lock and unlock but the danger is making sure you back up your "TA partition" so when you choose to relock it, you'll retain all the benefits and not lose them forever. But in the end its your call and your phone read, read again, read a third time and just before you unlock your bootloader read it again lol

ploopower79 said:
The process itself is not hard to lock and unlock but the danger is making sure you back up your "TA partition" so when you choose to relock it, you'll retain all the benefits and not lose them forever. But in the end its your call and your phone read, read again, read a third time and just before you unlock your bootloader read it again lol
Click to expand...
Click to collapse
ok, did a TA backup and downloading android SDK as we speak to perform the unlocking of the bootloader c:
looking forward to trying out this ROM

pin70 said:
ok, did a TA backup and downloading android SDK as we speak to perform the unlocking of the bootloader c:
looking forward to trying out this ROM
Click to expand...
Click to collapse
So, i went into recovery, installed the ROM and all the GAPPS, my z1 automatically restarted in infinite loop as expected, because i still haven't found what kernel i should be using, it says in the post to use the crandroid kernel? however all i could find was a 277mb .rar, and afaik a kernel should only be a 16mb~ .img file to flash in flashtool?
could you send a link to the correct kernel that i should flash?
EDIT; Nvm the .img file was inside that .rar file, booting in the ROM now c: eager to test it out
tks for all the support <3

Bug reports, first of all i'd like to mention that this ROM is awesome, i get 1gb free of ram when using it, however, i am struggling to do simple tasks with it, i've noticed some very constant crashes while trying to play music using Google's music app, or soundcloud, or youtube, everything will freeze or simply crash, in some cases causing the cellphone to reboot, i've noticed that a few snapchat videos recorded in portrait are playedback in landscape with everything stretched, also noticed a very low volume on the mic, at least while using whatsapp.
Update, it is crashing after a while with pretty much any app. i`ll try reinstalling everything
Reinstalled, problem persists, apps will freeze from time to time forcing me to close them, snapchat, play store, youtube, etc.
Am i the only one having theses bugs?
thanks! keep up the awesome work

for me too, tried and a lot of fc in apps (apps updated)....

pin70 said:
ok, did a TA backup and downloading android SDK as we speak to perform the unlocking of the bootloader c:
looking forward to trying out this ROM
Click to expand...
Click to collapse
tofclaire said:
for me too, tried and a lot of fc in apps (apps updated)....
Click to expand...
Click to collapse
At least i'm not the only one hmm, hope this gets fixed asap.

pin70 said:
So, i went into recovery, installed the ROM and all the GAPPS, my z1 automatically restarted in infinite loop as expected, because i still haven't found what kernel i should be using, it says in the post to use the crandroid kernel? however all i could find was a 277mb .rar, and afaik a kernel should only be a 16mb~ .img file to flash in flashtool?
could you send a link to the correct kernel that i should flash?
EDIT; Nvm the .img file was inside that .rar file, booting in the ROM now c: eager to test it out
tks for all the support <3
Click to expand...
Click to collapse
could you sent me the boot img cause i didn't manage to find it inside the zip file

[ROM][d2tmo][6.0.1] Team OctOs Oct-M

{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-M.​
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -​
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802​
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes, this is Android 6.0.1
Q: What code is Oct-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12 code. Oct-M is base on CyanogenMod 13.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XXXXXXX feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But XYZ and all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favourite Opengapps package http://opengapps.org/
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock CyanogenMod 13 kernel.
Kraken kernel source code can be found here: https://github.com/Oct-mm
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
OpenGapps
CyanogenMod
OmniROM
LiquidSmooth
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-M, ROM for the T-Mobile Samsung Galaxy S III
Contributors
bthorne79, CjKacz, canodroid15, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Version Information
Status: Stable
Current Stable Version: OCT-M R2
Created 2015-02-17
Last Updated 2016-08-26

Reserved
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP,
NONE REPORTED FROM TESTERS

Thanks OP
downloading now..
:good:

bthorne79 said:
Known Issues
A full list of Known Issues resides on our website. *In order to avoid confusion for people who skimmed the OP, the biggest Known Issue with the Galaxy S3 (d2lte) platform is the Camera. *It could cause Force Close issues. *This is an upstream issue, and we are working to correct it.
Click to expand...
Click to collapse
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.

goldentequila said:
Please put this info and list other bugs in the OP so that people won't be misled. Not everyone reads past OP.
Click to expand...
Click to collapse
Sorry but the inability to read is the users issue. Half the time they don't even read the OP. Go right to the download link. I posted in the 2nd post and there is a link in op to site with bug list and change log
Sent from my SPH-L720 using XDA Free mobile app

Running nicely right now. Had a hard time getting WiFi to connect on first boot but its working now

We put the information on the website because its easier to keep track of across the multiple devices we develop for. We develop the ROM for the simple fact we want to run it, not for you, or anyone else. The ability to be cognizant on what you're doing is a primary requirement for flashing ROMs, and the inability for you to apparently read and comprehend the very simply formatted OP means you are not willing to rise to the level we seek in a user.
It would be better for everyone involved if you don't flash Oct-L. You have many ROMs to choose from, you shouldn't choose ours.
ROM Development is not a service or product industry. You are neither a customer, or a client. Your demands mean exactly nothing and we have better things to do than hold your hand.
Now, if you feel like running what we build, by all means, do so. However, your continued patronage to the thread is directly proportional to your ability to be civil and not condescending.
Enjoy, or not at your leisure, but unless you have something constructive to say, please wander to another ROM.
Toodles!

Running smooth. ^.^

lol bitter much? Don't ruin this for the rest of us who rely on devs like these guys to continue providing up to date software for our aging phones.
I'm definitely trying this ROM out.

From the Moderator
To all in this thread........
Please all remember, the Devs do this for free and out of their love for developing....
....So being rude and poor mannered...... gets you nothing but maybe one less Dev making Roms for your phone
Keep that in mind when you feel like you have some lame commentary or demand to make...
........To the trolls, rather than complaining...... show us your skills and make a ROM for us to critique.......
........oh yeah...... you have no skills other than running yer mouth and making personal demands in a thread.......
~~~ oka1

The strangest thing is him talking about the OP not listing a Buglist. The Rom that he his visiting the most does not either. With that said I'm done. Mod can in and slammed the hammer down on that issue.
Please any one using this rom if you do see anything and and are able to catch a log please report and send log to us.
Thanks for supporting Team OctOS
Sent from my SM-T217S using XDA Free mobile app

Is the nav bar included in this release? Working?

allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
Sure! About the only thing that doesn't work is the camera!?

Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12

anil2653 said:
Installed this Rom and turned on wifi but after login to my account wifi stopped and grayed in off position
Rebooted device and wifi got on but every time failed to login
Again rebooted and it started working correctly
Reached office but again failed to connect to wifi
It is just an information as I read same thing happening with other cm12 build too so this may be with the cm12
Click to expand...
Click to collapse
What firmware is your phone on I've noticed that the newest modems and firmware is needed for lollipop to work correctly. These builds have been in test for quite some time. Our testers have put this build through the ground with not one hick-up just camera which we have been working on getting fixed.
If you can get a log of the WiFi issue you are having we will look at it. My suggestions is to update to the latest modem firmware for d2tmo.
Sent from my SPH-L720 using XDA Free mobile app

allendj81 said:
Is the nav bar included in this release? Working?
Click to expand...
Click to collapse
canodroid15 said:
Sure! About the only thing that doesn't work is the camera!
Click to expand...
Click to collapse
The Navbar will cover the "Clear All Recents" button if you select the lower right or left position. This already has been corrected for the next release.

Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!

vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Our d2tmo user still uses CWM as the team we suggest TWRP only cause CWM is almost a dead recovery and has been know to cause bad flashes..
Sent from my SPH-L720 using XDA Free mobile app

vick007 said:
Thanks a lot for this amazing rom, i´ll install it as soon as it finish downloading, but one question, it´s the same instaling it in cwm? i mean, does it makes a diference like more bugs or things like that, i hope you understand Thanks a lot!
Click to expand...
Click to collapse
Also, CWM has had historical issues with actually wiping the partitions effectively. The "Wipe system, data, cache, dalvik x3" was a reality in the past because of CWM. Those issues don't happen with TWRP.

I noticed a couple of things:
1) When flashing the ROM it takes a while. Compared to other lollipop rom's, this one takes about 3-4 minutes to flash, while others flash in like 15 seconds. Is that normal?
2) Installing apps from the play store are taking a long long time. Each app takes about 2 minutes to install, longer if it's a bigger one like youtube. I've noticed it takes long across all lollipop rom's, but one this one it seems to be longer.
3) Kernel Tweaker crashes when I try to view read-ahead and IO scheduler. This doesn't happen with any other ROM so I'm thinking there's something going on with oct os.
Any thoughts?

[ROM][7.1.2][OFFICIAL] CarbonROM WEEKLIES (armani)

{
"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.
We only support Dynamic (Beans) GApps, reports on force closes with any other packages will be ignored.
Get CarbonROM
GitHub
Gerrit
Device 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!
If you like my work,you can make a donation here -
XDA:DevDB Information
CarbonROM, ROM for the Xiaomi Redmi 1S
Contributors
aniket.lamba
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: A custom recovery (TWRP preferrable),knowledge on how to flash zip files,a brain ofcourse!
Based On: CAF
Version Information
Status: Stable
Created 2017-08-17
Last Updated 2017-08-17

Q n A
Official weeklies are out! Get them from the "Get CarbonROM" link in the OP.
BUGS:
-> You tell me.
CHANGELOGS:
You can visit https://carbonrom.org/changelog to view the changelog.
FAQs (Please read before posting questions):
Q: Does this ROM support OMS?
A: Yes, full OMS7 support is present.
Q: Is the ROM rooted by default?
A: No, please flash your favorite root solution after installing the ROM.
Q: Does the camera work?
A: It does.
Q: Do I need to make a factory reset before installing this ROM?
A: If you're installing it for the first time, YES, a full factory reset is required. If you're moving from an unofficial build to official weeklies, A FULL WIPE IS REQUIRED. Otherwise, dirty flash would work fine. If you have any issues with Google apps crashing, flash your gapps again.
Q: SafetyNet?
A: Sure, if you use Magisk and enable Magisk hide.
Credits:
LineageOS
@kwoktopus
@Myself5
@gtpitch
You can say thanks by donating to CarbonROM, me or any of the contributors. It really helps.

Reserved

Bug: Bluetooth connected but no media audio ( i used speaker Bluetooth). Please fix it, Thanks @aniket.lamba?

Bug: Bluetooth connected but no media audio ( i used speaker Bluetooth). Please fix it, Thanks @aniket.lamba?

lapmv86 said:
Bug: Bluetooth connected but no media audio ( i used speaker Bluetooth). Please fix it, Thanks @aniket.lamba
Click to expand...
Click to collapse
Go to /system/etc/ via a Root browser and replace your audio_policy.conf with this file - audio_policy.conf and set the permissions r-w-r-r.Reboot and see if bluetooth works or not.

aniket.lamba said:
Go to /system/etc/ via a Root browser and replace your audio_policy.conf with this file - audio_policy.conf and set the permissions r-w-r-r.Reboot and see if bluetooth works or not.
Click to expand...
Click to collapse
didn't worked

simuhnck said:
didn't worked
Click to expand...
Click to collapse
Alright can you provide me a logcat? Use Catlog to record the logs.

aniket.lamba said:
Alright can you provide me a logcat? Use Catlog to record the logs.
Click to expand...
Click to collapse
catlog is not working, used alogcat:good:

Screenshots please...
Bro, screenshots please..and tell me if this ROM having apps lock... System app lock...?!

Bro the ROM gave really good battery backup and camera is really good. Btw where is the option to launch dialpad at start of phone app.

simuhnck said:
catlog is not working, used alogcat:good:
Click to expand...
Click to collapse
aniket.lamba said:
Alright can you provide me a logcat? Use Catlog to record the logs.
Click to expand...
Click to collapse
Still same issue with latest build, Mi Bluetooth Speaker not connecting :crying:

Concerned about dynamic gapps
In Redmi 1s anything except open gapps Pico gives error while flashing as bigger files can't be flashed.. are you sure dynamic gapps would work as the mini version is about 210 mb??

not rooted and stuck on boot logo after flashed root file.

anonymousadi said:
In Redmi 1s anything except open gapps Pico gives error while flashing as bigger files can't be flashed.. are you sure dynamic gapps would work as the mini version is about 210 mb??
Click to expand...
Click to collapse
Flash this - https://github.com/opengapps/arm/releases/download/20170817/open_gapps-arm-7.1-pico-20170817.zip gapps package.Other gapps bigger than 80 MB won't work as the /system space is too less.

mvyvahid said:
not rooted and stuck on boot logo after flashed root file.
Click to expand...
Click to collapse
Flash this zip file.

I used open gapps pico bigger than 80mb it's fine until now

aniket.lamba said:
Flash this zip file.
Click to expand...
Click to collapse
Even magisk work fine.
---------- Post added at 05:47 AM ---------- Previous post was at 05:47 AM ----------
qheen said:
I used open gapps pico bigger than 80mb it's fine until now
Click to expand...
Click to collapse
Bean gapps mini work fine.

ROM is smooth, but USB charging is very slow, Can we have fast charge on USB, as right now no custom kernel is available for android 7.1.2

spacexgen said:
ROM is smooth, but USB charging is very slow, Can we have fast charge on USB, as right now no custom kernel is available for android 7.1.2
Click to expand...
Click to collapse
Phantom is there :good:

[8.1.x][OFFICIAL][RELEASE] CarbonROM | cr-6.1 [taimen]

{
"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.
Notice:
In order to install GApps, you must flash the ROM then reboot into TWRP before flashing the recommended MindTheGapps GApps package (as this switches slots).
Also, we know the default wallpaper on is black. We know it's caused by the RRO overlays on vendor and unfortunately we can't change the default (yet?), you can change it manually without complications though.
We know it’s complicated, but it sure is worth it!
Install Instructions:
Flash the newest factory images on both slots
Move your ROM + [GApps] + TWRP.zip to your internal storage
Boot the TWRP.img > Check what Slot you're on (Reboot Menu) ->Wipe Data & Cache -> Flash the ROM as well as the TWRP.zip
Either Reboot to system or, in case you want GApps, reboot to recovery via TWRP (Reboot -> Recovery)
Check and confirm that you are on the opposite slot from Step 3. If not, switch to it and reboot the recovery again (Reboot Menu) -> Flash GApps (and whatever else you want to flash -> Reboot to System -> Enjoy CarbonROM
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 Google Pixel 2 XL
Contributors
Myself5, frap129, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-01-16
Last Updated 2018-09-12

First!!!!!!
Sent from my Pixel 2 XL using Tapatalk

Just made my New Year's! Kudos

You got now listening, but what about active edge? I'm assuming not yet, yeah? Could you share a list of carbonROM features that are working with this build??

Oh man! Super excited for this rom! Thank you for all your hard work!

slothdabski said:
Dl link isn't working for me
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Works fine for me. If @Myself5 is cool with it, here's a direct link: https://dl.myself5.de/taimen/CarbonROM/CARBON-CR-6.1-TBA-UNOFFICIAL-taimen-20180116-1549.zip
MD5: https://dl.myself5.de/taimen/CarbonROM/CARBON-CR-6.1-TBA-UNOFFICIAL-taimen-20180116-1549.zip.md5sum
Yell at me if you want it removed

raynan said:
Works fine for me. If @Myself5 is cool with it, here's a direct link: https://dl.myself5.de/taimen/CarbonROM/CARBON-CR-6.1-TBA-UNOFFICIAL-taimen-20180116-1549.zip
MD5: https://dl.myself5.de/taimen/CarbonROM/CARBON-CR-6.1-TBA-UNOFFICIAL-taimen-20180116-1549.zip.md5sum
Yell at me if you want it removed
Click to expand...
Click to collapse
Thanks a ton
Sent from my Pixel 2 XL using Tapatalk

Screenshots
Sent from my Google Pixel 2 XL using XDA Labs

Thanks for this :good:

TheNightman said:
You got now listening, but what about active edge? I'm assuming not yet, yeah? Could you share a list of carbonROM features that are working with this build??
Click to expand...
Click to collapse
Had to reverse engineer a lot of google code to get Now Listening to work, and now that I know what I'm doing, active edge is up next
Prattham said:
Screenshots
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Screenshot:
"Its based on aosp just look at your phone".jpg

Anxious to try this!

@frap129
Do you happen to know if the rom (in its current state) supports activation of the Project Fi E-sim? I still have my old sim card from my Nexus 6p, but just curious? And if not would that feature come in the future?
Also do you guys have a donation link??

Ericarthurc said:
@frap129
Do you happen to know if the rom (in its current state) supports activation of the Project Fi E-sim? I still have my old sim card from my Nexus 6p, but just curious? And if not would that feature come in the future?
Also do you guys have a donation link??
Click to expand...
Click to collapse
It should, AOSP supports eSim and I didnt see anything specifically about Fi in the stock frameworks.
Edit: Donation link will be added to the OP shortly

Awesome! Thanks for this. Glad To see development taking off.

YUSSSS

frap129 said:
It should, AOSP supports eSim and I didnt see anything specifically about Fi in the stock frameworks.
Edit: Donation link will be added to the OP shortly
Click to expand...
Click to collapse
I believe @Ericarthurc tried with the other ROM and it didn't work. I'm in the same boat as well with Fi.

Just flashed LOS yesterday and it's running perfect. I'll give this a go this weekend. Thank you for releasing this to us. So glad to see development starting to churn. Looking forward to the future of this device!

@JagXK8 So I just installed the ROM and project Fi was "pre activated"? Under sim settings I have my phone number and mobile data is work with e-sim. I even just took a phone call. the weird thing is I installed the project Fi app and it says "error cant activate due to problem with sim"? I am going to try and systemize the project fi app and see if that fixes the issue.
---------- Post added at 11:46 AM ---------- Previous post was at 11:41 AM ----------
So I flashed the rom and project fi was already activated (e-sim). There is no project fi app installed on the device, so I installed it from the app store and it was giving me an activate error in the app, I tried systemizing the app but that didn't change anything. I just uninstalled the project fi app and I am still activated. So I have no idea how its working? But it is?

What about support the Pixel 2??

ApoelEllhnwn said:
What about support the Pixel 2??
Click to expand...
Click to collapse
If we get a maintainer, we will. No blind support though.

[8.1.x][UNOFFICIAL][WEEKLIES] CarbonROM | cr-6.1 [lilac]

{
"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.
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 XZ1 Compact
Contributors
SirSoviet, modpunk, Myself5
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-07-17
Last Updated 2018-07-16

Changelog
July 23, 2018
Upstream changes
Switched to modpunk's kernel due to build failure, difference should be unnoticeable
July 16, 2018
Initial release
https://blog.carbonrom.org/changelog/

Bugs
CAMERA: Enabling stabilization option in camera settings under "Video camera" causes an error message and crash when attempting to record.
[*]APP: Gardenscapes connection error on all yoshino devices. Enable storage permissions for app manually.
CAMERA: Manual focus by tapping while zoomed in crashes the app.
All of these issues are present on modpunk's latest LineageOS build. I'm not a programmer, so please be patient while the issues are resolved!

Nice! Been hoping for a Carbon ROM build for the xz1c. Just flashed and looking good so far. Thanks so much!

I installed it. So far everything is working for me. Will you continue to compile new versions, especially if new patches arrive?

SkyHigh76 said:
I installed it. So far everything is working for me. Will you continue to compile new versions, especially if new patches arrive?
Click to expand...
Click to collapse
I shared my initial version with the intention of releasing new versions.
However, my only practical platforms for compiling my builds on are my laptop, which takes 6 hours to build everything without having compiled anything else and gives me only 20GB of free storage space after building, and Google Cloud Trial which is just a trial, and so it has a limit.
As long as I have access to a build server, new builds will be released for at least a while.

New build! No device-specific bug fixes just upstream changes and a kernel switch

Going on vacation so no builds until around mid-August. Sorry!
While you guys wait, I recommend installing AOSP Phh-Treble with a DRM fix, Magisk, and SELinux permissive patch. The included camera won't work, but Open Camera does and the quality will be as good as stock despite being AOSP.
Also runs noticeably smoother than other AOSP roms like AOSP compiled directly from sonyxperiadev, pretty ironic considering that Treble GSIs aren't tailored to device-specific level.

SirSoviet said:
Going on vacation so no builds until around mid-August. Sorry!
While you guys wait, I recommend installing AOSP Phh-Treble with a DRM fix, Magisk, and SELinux permissive patch. The included camera won't work, but Open Camera does and the quality will be as good as stock despite being AOSP.
Also runs noticeably smoother than other AOSP roms like AOSP compiled directly from sonyxperiadev, pretty ironic considering that Treble GSIs aren't tailored to device-specific level.
Click to expand...
Click to collapse
How did you manage that? I was on Stock rom booted into TWRP. There I did a factory reset and wiped System, Cache, dalvik and data. Then I flashed the System Image from treble project the A partition one vanille Android but it didnt boot. Am I forgetting something?
EDIT: Fixed it. You should not use a Magisk patched ramdisk before flashing or use a patched kernel. A flash after coming from a fresh stock rom worked.

weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*

Tralien said:
weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*
Click to expand...
Click to collapse
Hey man learn to read comments before you say anything, the dev said he is going on vacation and there won't be new updates until he is back, so stfu

Tralien said:
weeklies.....lol....you managed to build 2 !! builds and for about 4 weeks there´s nothing new.....
very interresting that new projects die within 2 weeks *sad*
Click to expand...
Click to collapse
I'm sorry for not committing to this project, but shouldn't you be grateful that I built CarbonROM for lilac and shared it with you and the rest of the community?
You've needlessly pointed out twice that progress on RR for the S9 has halted. And? Developers are humans, just like you (I assume).
I suggest that if you haven't already, you should experience what it's like to build and maintain a custom ROM, before continuing to complain about inactive developers.
I'm back from vacation now, but I really don't have any reason to continue with this project, doesn't help that I would have to share my builds with people like you if I did. Google Cloud credit is running low anyways, and I don't have access to any other solutions.

SirSoviet said:
I'm sorry for not committing to this project, but shouldn't you be grateful that I built CarbonROM for lilac and shared it with you and the rest of the community?
You've needlessly pointed out twice that progress on RR for the S9 has halted. And? Developers are humans, just like you (I assume).
I suggest that if you haven't already, you should experience what it's like to build and maintain a custom ROM, before continuing to complain about inactive developers.
I'm back from vacation now, but I really don't have any reason to continue with this project, doesn't help that I would have to share my builds with people like you if I did. Google Cloud credit is running low anyways, and I don't have access to any other solutions.
Click to expand...
Click to collapse
Anyway, thanks for your work. Some guys here may cant read your post before about your vacation.
May be you will change your opinion about not publishing any future versions.
I think that Carbon was running quite well.

Dang that sucks. I really wanted to see more from CarbonRom.

As I expected...you ask for donations in your first post and now......no more updates
you developers always ask for donation and this is one good example why many people dont donate.

Tralien said:
As I expected...you ask for donations in your first post and now......no more updates
you developers always ask for donation and this is one good example why many people dont donate.
Click to expand...
Click to collapse
Sorry, I've never shared my builds on XDA before, and I was just trying to follow other CarbonROM members' post formats. Please note that I am not a member of the CarbonROM team, these are unofficial builds.
Good news! I now have a dedicated build machine, completely separate from my main computer.
I may post more builds soon, but flashlight, RIL, and camera are currently broken in modpunk's LineageOS I built for myself (my CarbonROM uses his device and kernel trees).
Hopefully I'll be able to revert the changes and bring a build to you guys sooner.

@SirSoviet Pls I'm not being rude or bossy I just wanna ask are we going to get new builds of this rom?

Thread closed at OP request