[7.x.x][WEEKLIES] CarbonROM | cr-5.1 [sumire]
- Thread starter Myself5
- Start date
@THE people requesting:
Have you ever tried to build a ROM in yourself own?! Have you ever thought about that devs are spending their spare time and passion in this as their hobby?! That they have to Go to Work in order to pay bills too?!
Stop requesting stuff. Be grateful and show some respect!
Have you ever tried to build a ROM in yourself own?! Have you ever thought about that devs are spending their spare time and passion in this as their hobby?! That they have to Go to Work in order to pay bills too?!
Stop requesting stuff. Be grateful and show some respect!
Bro at least tell us any month
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
This is killing me . No offense you guys are gr8 , but even Xperia z2 got Oreo custom rom
---------- Post added at 01:15 PM ---------- Previous post was at 01:03 PM ----------
If there is no Oreo we can at least I can understand but you guys are giving us a ray of hope . Your hard work is amazing . Even Sony didn't supported this phone these much .I don't want the exact ETA but an estimated time. Plz plz plz .......
---------- Post added at 01:16 PM ---------- Previous post was at 01:15 PM ----------
If there is no Oreo we can at least I can understand but you guys are giving us a ray of hope . Your hard work is amazing . Even Sony didn't supported this phone these much .I don't want the exact ETA but an estimated time. Plz plz plz .......
I too had FM radio issues a while back, and wiping and reinstalling fixed it: https://forum.xda-developers.com/showpost.php?p=75458635&postcount=684
Of course, it could be the build....but it's worth wiping and reinstalling first.
Last edited:
I quoted Myself5 because no one else was answering and I tought he would be the best to help me. Also, if someone is using this latest build and has no problem with the radio, then it's not the build..
Thanks for answering. I'll try to wipe and reinstall now and post the results.
Thanks for answering. I'll try to wipe and reinstall now and post the results.
Any idea why I can't change iso on snap camera app? it is visible and I can change numbers but no difference happen
Also do you have any tips for battery life?
Also do you have any tips for battery life?
Factory Reset
I use this rom for my device, and I have to reset my phone, how can i reset the phone to the factory settings.
I dont want to delete the rom
I use this rom for my device, and I have to reset my phone, how can i reset the phone to the factory settings.
I dont want to delete the rom
i cant believe sumire still has no 6.1 noct build and z3 for example has 4 already... even my odin has oreo at this point
Our device is ignored, I think we should be thankful for getting this rom in the first place!
Sent from my E6633 using Tapatalk
@Myself5 can i suggest quick charge implementation? like the one z2 got from AndroPlus
https://forum.xda-developers.com/xperia-z2/development/sony-secret-revealed-qc-2-0-t3163490
maybe if we are lucky enough we have a chance to get noct soon and if it gets QC... dreams... ik
https://forum.xda-developers.com/xperia-z2/development/sony-secret-revealed-qc-2-0-t3163490
maybe if we are lucky enough we have a chance to get noct soon and if it gets QC... dreams... ik
Trying to get from one phone to another
I have z5 regular, i have carbon rom installed 2018. everything fine on older phone works good but the mic. Made a full backup in TWRP 3.1.1.0.
So i got another new phone same exact kind E6653, TWRP 3.1.1.0. I transferred the backup from the original phone and tried restore it. No go. Got an error on data partition, "extractTarFork() process ended with ERROR: 255".. i tried many things and eventually gave up. So i decided i'll do a new install and titanium backup ill transfer all my data and apps. But after formating the phone and installing newest open gapps for amd64 7.1 standard, my programs start automatically closing, market, phone.. and so on. So i did cache and davlik clear.. no good....
I am out of ideas for tonight, anyone want to shed me some light ?
I have z5 regular, i have carbon rom installed 2018. everything fine on older phone works good but the mic. Made a full backup in TWRP 3.1.1.0.
So i got another new phone same exact kind E6653, TWRP 3.1.1.0. I transferred the backup from the original phone and tried restore it. No go. Got an error on data partition, "extractTarFork() process ended with ERROR: 255".. i tried many things and eventually gave up. So i decided i'll do a new install and titanium backup ill transfer all my data and apps. But after formating the phone and installing newest open gapps for amd64 7.1 standard, my programs start automatically closing, market, phone.. and so on. So i did cache and davlik clear.. no good....
I am out of ideas for tonight, anyone want to shed me some light ?
Wipe literally everything on your new phone and flash stock rom just to get everything working.
After that flash custom roms.
Probably you're flashing the wrong gapps.
Yup. Do what he said! My stock z5 starting weirding out and rebooting randomly and the best way is to do a full wipe. Try search for Flashtool which will do the full wipe and install stock.
Then you can install the custom kernel, then TWRP, and then in TWRP, flash the custom rom and remember to flash the Google Apps (if you are doing so) before booting into the custom rom.
I'm currently running on Lineage OS May 13 build as I gave up on the Sony Stock build due to its instability. Everything works very nicely, including FM radio.
Did you just install the May 13th build right over the previous one? Things *should* work, but when in doubt, I always go to a full wipe. The FM Radio app doesn't need any permissions and there's not a lot of troubleshooting you do. I didn't install anything extra other than Magisk's Sony App Enabler, but that's just to be able to see Sony apps in the play store and I also installed the Sony Music player from Magisk as well. Otherwise, it's a clean Lineage OS May 13 install.
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
65
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 Sony Xperia Z5
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Nightly
Created 2017-01-01
Last Updated 2018-03-1723FPC/DSDS/Generic
I uploaded the build with a working Fingerprint sensor on my private server, you can find it here:
https://dl.myself5.de/sumire/CarbonROM
Said new build I has a new fixing attempt for the DSDS/Generic device unification, SDCard and RIL should work on both devices now. If there are any occuring issues with it, please let me know.
In addition to that, it contains the today-merged dataicon fix (so H and H+ Icons now show properly) and plenty of updates from stock that were previously files and configs from ivy. Also some sound issues should be fixed. Basically, this build includes all of these changes:
https://review.carbonrom.org/#/q/branch:cr-5.1+topic:sumire-test
On top, we reworked the whole ROM sources recently as we came across some reboot issues due to the wrong CAF tag that got merged. We took care of that and so far it seems like its performing better than it was ever before.
This was the reason why Weeklies have been timed out last week BTW.
With that: Happy testing folks.19Idk what do U mean. I just asked a normal question. Many builds of 8.0 have been released so far, what's more, I have one on my old Xperia SP. And I'm just wondering how long will we wait for 8.0 on Z5. If my knowledge is not enough, then educate me a bit, cuz I don't see anything wrong with my question
So heres the deal then:
1) The SP has one of the most dedicated developers I know.
2) The SP can run on AOSP HALs and code.
3) AdrianDC started to work on Oreo almost 3 months ago by working on master.
4) The Z5 needs CAF HALs. That includes various ROM sided changes that will require a lot of work. The msm8994 related caf code has not even been released yet.
5) You ask for a releasedate, like this would be my job. This is a hobby, I do it in my freetime, and asking for ETAs will neither speed up my work, nor motivate me further into working on the Z5. I'm not even running Oreo on my Daily driver, my Google Pixel, yet because I simply don't have the time to do it at the moment, as every free minute is going into the CAF bringup and working on other Carbon things, yet you're here, asking me when it would finally arrive as if I'd just be too lazy to do it.
6) It will come eventually, but I just can not say why, because I havnt even started yet. My main focus at the moment is, along with some Carbon features, getting the Nexus 6 to fully work. After that I'll finally move on to my Pixel, after that the msm8994 caf tags might have been dropped so that I can start working on that. Again: there is no timeframe and no ETA. I neither can, nor want to provide any ETA, because I likely won't be able to hold on to it anyways. Theres always something coming up in between.19First 7.1.2 Testbuild
If someone feels like testing, I just uploaded a new build to https://dl.myself5.de/sumire/CarbonROM/
The version CARBON-CR-5.1-MOO-M5Edition-sumire-20170417-1911 is built from the completely rebased 7.1.2 sources, and contains all sumire specifc fixes we talked about recently.
New official builds will be restarting soon, and we'll return to the "normal" weekly schedule
Happy flashing
P.S.: The video recording and the screenrecorder issues will be looked into later.
EDIT: For 7.1.2 you require 7.1.2 compatible GApps. Working ones are BeansGapps by @BeansTown106 for example.19"Some" Progress
So, I havn't talked much about it recently, as there was nothing progressing.
However that changed in the last few days. @gtpitch jumped in, and together we got some party going.
There is still a lot of polishing needed, as some of the CAF things break some things on other devices, like the Pixel that doesn't even compile due to double definitions of some CAF repos, so don't expect the CAF-Z5 going Weekly in the next few weeks, but here is a little something:
