{
"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?
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"
}
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
{
"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
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+ with treble support https://forum.xda-developers.com/showpost.php?p=78708796&postcount=2
- backup everything before install including efs partition
- wipe cache and vendor partitions before install
Install:
- Flash zip in compatible TWRP
- Don't forget about gapps (arm 9.0)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Doesn't work:
RIL
Download:
0207 build
T710: https://drive.google.com/open?id=1VScAyyvr8WcAseGAFVmIM4DPd2-Q1Us6
T715: https://drive.google.com/open?id=1q7oHTyV_JJGG3B56h0Wd_QiUsKn6hVzg
Device sources:
https://github.com/bonuzzz
treble-enabled twrp
t710: https://drive.google.com/open?id=1d0YycDthOxo7IM1b5gZbNI7zCdlu2Cix
t715: https://drive.google.com/open?id=1wrZKDMQcosQRrZGDypIG27Oqv-zL6m2G
known issues:
info on data partition is not accessible
Hi, thank you for the build, awesome! I was going to install LOS 15 but now I'll go directly for this one. I'll tell you how it goes
Sent from my Aquaris M5 using Tapatalk
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Hockron said:
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Click to expand...
Click to collapse
Unfortunately it's not so simple. So no new builds for t810/t815 at least in near future (several months). I focus on t710/t715 only.
as usual gr8 job ma8 considering. We got los15.1 stable finally seeing this beta makes me really happy so, keep up the good work...
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
bonuzzz said:
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
Click to expand...
Click to collapse
Its very sad for everyone that you abandoned the rom, but I understand what not having the time and the energy means. Thank you very much for the build. In any case I installed as I said before.
I haven't tested it much but for the time being its running pretty smooth. I installed some apps and no crashes so far. Just an error message at boot saying something happened, after closing it everything OK.
I add some screenshots here.
Ill keep posting issues if I find any. Do you think I could compile your sources in my computer?
{
"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"
}
Sent from my SM-T710 using Tapatalk
what to do when you are sick and staying at home? answer is simple:
new lineage16 builds are uploaded.
all hw stuff has been brought up except ril on t175, so no mobile network support yet. everything else should work.
links are in first post.
How much work should it be done to port this onto T810? And do you know anybody is doing it?
frankieboy1233 said:
How much work should it be done to port this onto T810? And do you know anybody is doing it?
Click to expand...
Click to collapse
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
T815 plzz. I have no knowledge about porting roms, but if by any way I can help u in porting this to T815 plzz let me know...
sweet, i saw your trebel twrp in the other forum, freaking fntastic
#1. Loaded trwp and ROM only no root
Excellent power 97 percent remain after 13 hours
No 5gz WiFi. But because I had nothing else loaded I couldn't see the nvram_net.txt settings.
So I tried to load pico and lineageos add-on su, and had several boot up and setup issues with the play services kept crashing. After bypassing lots of stuff, gave up and reloaded, I was able to see the root permissions in the developer settings, but lineageOS extras shows only arm 15.1 no 16 for root. Thought that was an issue. Silly me I didn't do a logcat. Before I did #2
#2nd try wipe , load, pico and magisk 17 . no magisk 17 in apps.
Did a bypass load apps to get to desktop. Had a couple " this device has errors, please contact manufacturer "
Play store was able to install apps, but I had no access to my paid apps. See #1 I wanted to fix my 5gz WiFi files. And I use es file explorer pro, but since I didn't have root... Well.
Play store recovered my programs am going to try magisk 18 . BRB
Looks nice, a couple of google play store bugs, an actuall desktop black out.
In conclusion, awesome ! Work !
Will fiddle some more. couldn't get a logcat
Downloaded all my gapps, and I found an unofficial root for lineageos 16 in another forum.
Trying again. Cheers
https://androidfilehost.com/?fid=11410963190603875495
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
bonuzzz said:
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
Click to expand...
Click to collapse
i have an 815 to test as well
---------- Post added at 05:35 AM ---------- Previous post was at 05:17 AM ----------
bonuzzz said:
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
Click to expand...
Click to collapse
Same here.
I got 5gz to work . I changed
Code:
ccode=US
regrev=69
Based on several posts over the years, I researched what regrev is in related to the ccode
It relates to what frequencies and I believe power outputs for different countries legal free and open radio frequencies.
The clues are in the driver for the wireless device source code.
Here is a broadcom driver for the 3.10 kernel
https://android.googlesource.com/ke...drivers/net/wireless/bcmdhd/dhd_custom_gpio.c
In there is a small database that should be consulted when you boot up your device and your country code should be selected when the driver is accessed
This has never worked properly for any lineageos based ROM.
Also most stock ROMs do not have this in their correctly.
All the files in /system/vendor/etc/wifi that have nvram in their name ( total 6 files ) need updated manually with an editor with root access.
As soon as I enter codes and reboot, I see all the 5 gz and many other networks that normally are too far away.
Kind of a chore to do this on every reloaded device, but that's what it takes.
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
samw52000 said:
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
Click to expand...
Click to collapse
Same here I cant flash Gapps with out it sticking on Samsung's boot logo
@samw52000 @legojoe8 read the first post carefully, in particular about twrp
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Hello
I have created this rom using the Lineage sources and a fix from the creator of the rom of this page: http://customromz.proboards.com/thread/11/crdroidandroid-9-marlin-v5-zip?page=1&scrollTo=16. I don't have too much knowledge in how the rom is developed so perhaps I won't be able to solve all your questions.
Please let me know if you have any issue.
Regards
SourceTree
LineageOS
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your google pixel, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Install stock rom
2) Copy crDroid zip, gapps zip and twrp zip to your device
3) Boot into Recovery
4) Wipe cache, system, & data (or just cache & system for a dirty flash).
5) Flash ROM
6) Reboot into recovery
7) Flash gapps
8) Boot up
9) when the setup wizard starts execute the following command to allow it to connect to wifi
adb shell pm grant com.google.android.apps.pixelmigrate android.permission.WRITE_SECURE_SETTINGS
10) Open the contacts and phone apps and accept the permissions requests
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
you tell me...
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Joe pacino
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
I might take a look at this, what have you done since the last build in the main thread?
GeTex said:
I might take a look at this, what have you done since the last build in the main thread?
Click to expand...
Click to collapse
Hello
Thanks for your answer. What your are interested in is the process I follow to compile the rom ?. I can post the script I use, that is one I have created from the crdroid sources: https://github.com/crdroidandroid/crdroid_build.
Regards
Why not post this in the Pixel Development forum? Would gain more traction there.
PapaSmurf6768 said:
Why not post this in the Pixel Development forum? Would gain more traction there.
Click to expand...
Click to collapse
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
jontxo said:
Hello
I am not allowed yet to post in the Pixel Development forum because I haven't made enough posts yet.
Regards
Click to expand...
Click to collapse
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
PapaSmurf6768 said:
Oh
Well thanks for your work anyway, has this been running well for you? Might be able to try it, the old crDroid was my favorite ROM.
Click to expand...
Click to collapse
It is the rom that I use in my phone in a daily basis and I haven't found any issue yet.
Are anyone try this rom? How was the performance and battery life? Any problems?
SoKa1993 said:
Are anyone try this rom? How was the performance and battery life? Any problems?
Click to expand...
Click to collapse
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
PapaSmurf6768 said:
I flashed it, all good so far.
Couple things to note, the Stock OpenGapps package said it was too big for system storage, had to move to Mini package.
When going through setup, the adb command given wasn't working until I went through setup a little bit, then came back to the beginning. Not sure exactly how to fix it but it worked eventually, and WiFi connected.
Will put it through its paces over the next couple days, thanks for the build!
Click to expand...
Click to collapse
You are welcome. And thanks for trying it.
Regards
jontxo said:
You are welcome. And thanks for trying it.
Regards
Click to expand...
Click to collapse
Suitable for daily driver? How frequent will it to be update?
SoKa1993 said:
Suitable for daily driver? How frequent will it to be update?
Click to expand...
Click to collapse
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
jontxo said:
I use it as a daily driver for my phone. I will update it whenever a new crdroid version is out.
Regards
Click to expand...
Click to collapse
Thanks. Will try it tonight and give feedback to you.
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
kkjb said:
Good features, like the "past" features. Your kernel has very good sleep mode, and speed stepping. Overnight battery life looking good. I haven't tried cell radio yet, this is the second pixel I use for testing first. I will try a couple of ways to get Google photos app to work Like Pie, before I commit more. Photos device file backups not working correctly, but that might be my device to device transfer process to move master work data to a newly flashed build. THANKS for your time and efforts.
Edit- yep had device transfer problem. Complete wipe / reinstall apps. Photos fine again.
Click to expand...
Click to collapse
I am glad everything is OK.
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
SoKa1993 said:
Everything is ok but the charging speed is quite slow. Max i got just 5.0W. Is it because the rom or the kernel i used? Currently using latest franco kernel. But on others rom it works fine. Other than that, i loved it. Thanks
Click to expand...
Click to collapse
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
After a few days on this I can say this is easily the best Pie ROM I've put on my phone. Features are great and no problems to report in my day to day use.
Couple notes I had; I had to flash the Mini Gapps since the Stock package said it was too large for the partition. After booting, the trick to get WiFi to work during setup didn't work immediately but did work after clicking around a bit. Then Photos was crashing on start so I deleted it as a system app and just installed it from Google Play. That works fine, and I haven't had any other apps do this.
Thanks again OP, will be on this one for a while.
jontxo said:
How have you managed to flash franco kernel. I have this error: new image larger than host partition. Aborting...
Regards
Click to expand...
Click to collapse
I just flash it and it work like usual. Maybe something wrong when u flash the rom file. Did u clean flash it or dirty? Mine clean flash. After flashing the rom, i boot it to system. Then install gapps, magisk. Boot it again. Then franco. Work like a charm. Btw, this rom is smoother than other roms. Love the extra setting on this rom. Thanks for ur work.
New version of crdroid- 5.8
Hello
I have uploaded a new version of the room, the 5.8.
https://androidfilehost.com/user/?w=settings-dev-files&flid=298676
Greetings
{
"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"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.Has a refined Material Design 2 UI crafted by @SKULSHADY.Many useful features that provide a smooth premium experience.Just flash and enjoy...
Founder & Lead Developer:SKULSHADY (Anushek Prasal)DevOPS & Scaling:Irongfly (Sukeerat Singh Goindi)
If you like our work and would like to support this project then please consider donating.
PayPal: https://www.paypal.me/ANUSHEK
UPI: [email protected]
Download ROM: https://havoc-os.com/device#sofiar
About Havoc-OS: https://havoc-os.com
Recovery: Vache's unofficial TWRP
Magisk: https://github.com/topjohnwu/Magisk/releases
FlameGApps: https://flamegapps.github.io/
Official Havoc-OS Telegram Group: https://t.me/havocofficial
Official Rav/Sofia-R-P Havoc-OS Telegram Group: https://t.me/+ioAiJwr1DKZiMjJl
Havoc-OS Announcements Telegram Channel: https://t.me/Havoc_OS
Code Review: https://review.havoc-os.com
1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.
2. Wipe System, Data, Dalvik, Cache.
3. Flash the ROM, GApps (Optional), Magisk (Optional).
4. Reboot and Enjoy.
LineageOS (https://github.com/LineageOS)
Crdroid (https://github.com/crdroidandroid)
Pixel Experience (https://github.com/PixelExperience)
And all the other Developers, Testers, Donators and Users.
https://github.com/Havoc-OS
https://github.com/Havoc-Devices
Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
Havoc-OS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Official
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help
Any plans to fix FM radio?
Leroy_Sparks said:
Any plans to fix FM radio?
Click to expand...
Click to collapse
Yeah I'll attempt a few things to try and fix it, worse case scenario I'll just remove it.
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
xStealth said:
Keeping an eye on your releases. If you manage to fix FM radio I'll be making the jump immediately. Glad to see some development resume for this device!
Click to expand...
Click to collapse
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Funciona no a02s?
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
Yeah, I've been watching the Telegram. I'd been waiting on an update from Beetle but it appears they've stopped development on this device. I'd been using their most recent for over a month when suddenly Android system started using tons and tons of battery for no apparent reason so I shelved the phone and went back to my old one while waiting.
ph4n70m-404 said:
Theres been development just mostly on the telegram, currently FMRadio works on my corvus build but that is also SELinux Permissive, although its not the best solution you can likely get it to work on any rom by setting the rom to SELinux Permissive.
Click to expand...
Click to collapse
I installed Arrow to get FM radio (had been on Beetle's havoc before that). I'd like to have the radio but I do like havoc better. One thing I've encountered on the arrow ROM is a lot of stations have distorted audio (not all), even ones that usually have great reception on an old htc phone. I wonder if the moto radio is maybe not the greatest? Anyone notice similar? (I never tried fm radio while I had oem ROM).
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Thanks dude for ur work! UwU
luke.leheny said:
Thanks for the work on this ROM. I've been using Beetle84's build of Havoc 4.8 and I figured this might be the best place to post about bugs, since the other thread is now labeled "discontinued"? I'll probably post this there too. I'm gonna install your 4.10 build soon regardless. Here are some bugs I found that are possibly still present in your build:
Ambient display is a little buggy. Trying to enter your PIN from the ambient display will suddenly hide the keypad and show the regular lock screen. If you do this quickly, this will all happen and also the screen will turn off (probably because tap to wake/sleep or whatever is enabled too)
Metadata doesn't update normally when listening to audio via Bluetooth. My car will just display the metadata for the first song until it randomly switches to a new song like 10 songs later, and be stuck on that song for a while too.
I put my phone on airplane mode a lot, and sometimes when I take it off, it doesn't receive texts until I enable and disable airplane mode again. Sending texts, using data, and sending/receiving phone calls still all work during this time, as far as I can tell but I haven't tested thoroughly yet. I have US Mobile using Verizon's network if that helps.
When I boot the phone (either cold boot or restart), there is a period between the time the phone is on and the time I've entered my password to "log in". During that time, I technically receive texts, but android deletes them automatically and there's no trace of ever having received them. This is an especially bad bug as it was difficult to even know it was happening. I was told by multiple people that I never responded to a text, when in reality I never saw it. Took forever to figure out what conditions were actually causing me to not receive them. My temporary solution to this is to always put the phone on airplane mode if I ever have to turn it off, because that way I'll have already logged in before I connect to the network.
Hotspot does not work, just immediately turns back off after turning it on
If this isn't the right place to post about bugs, I apologize. I had been using Havoc on this phone for about a month and only made this account to make this post.
Edit: Should probably mention which phone I am using: it's Moto G Power 2020 (sofia)
Click to expand...
Click to collapse
Okay so I've tested your 4.10 build and pretty much all of these bugs are gone. Ambient display is still a little weird when trying to unlock but I tested on another phone and it seems like a Havoc OS bug rather than a bug with this build/phone. Haven't had a chance to check the bluetooth audio one yet. But the last 3 on this list all seem to be resolved by this build.
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
xStealth said:
Decided to give this a go because I was having untold amounts of problems with your Lineage build and getting GApps to work. Zero issues on the first install and everything is good. Other than radio not working, everything else seems to be just fine. I'll be sticking with Havoc.
Click to expand...
Click to collapse
Yeah LOS is having lots of issues with GApps lmao, I've been told a possible fix and i might try doing GApps included builds but im waiting for when I have a decent amount of time to try some of these. I did a Corvus build that has FMRadio fixed but thats only because Corvus is in SELinux Permissive and as i mentioned before you can likely fix FMRadio on every newer rom by setting it to SELinux Permissive via a magisk module.
@ph4n70m-404 I'll be keeping an eye to see if you somehow manage to fix the radio without having to go permissive. While radio isn't the most important of things, it's just a nice thing to have in case service goes down or I'm in the middle of nowhere.
Just wanted to add, overnight I only lost about 1.5% battery during idle (GApps version on 2.4GHz WiFi) in around 10 hours. That's absolutely astounding! Beetle's build did that to begin with, but after a few months Android System began to chew through battery nonstop. Excellent work!
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
jhford said:
I have a Moto G8 Power 2020 (XT02041-4), and I flashed Beetle84's Havoc ROM the day I received it. I've used it for several months. Initially, the battery life was great, but I recently found that I was getting slightly more than one day. Some on this forum associate it with Android apps, but I've had essentially the same apps installed from day 1.
So, I decided to install a new ROM and selected LineageOS 18.1 (LOS18), with which I'm very familiar. However, I couldn't install GAPPS regardless of the GAPPS I selected. Also, something weird troubled me. I was running TWRP 3.5.0_10-0 and tried to flash TWRP-3.5.0-0-rav-sofia.img which the OP of the LOS18 suggested. I flashed it in TWRP seemingly successfully, but TWRP 3.5.0_10-0 was still installed .when I rebooted Recovery. I thought I had screwed everything up and used the Lenovo Rescue Tool to flash the stock ROM.
But then I discovered this thread, and decided to go back to Havoc by flashing this ROM. However, although the OP suggests initially wiping System, Data, Dalvik, Cache, System is not available when I do an Advanced Wipe. So, I used the Lenovo Rescue Tool and flashed the stock ROM again.
That's where I am, and I'd appreciate some guidance with this. Much appreciated. Thanks
Click to expand...
Click to collapse
I'm the same builder as los one, the twrp image is just the same vache one everyone recommends so you just reinstalled the same twrp, los has been weird with getting gapps working so I've been trying to resolve that. The install instructions are just the ones the rom provides for their template and should really just be loosely followed, the only reason i dont change those is because i would probably write way too much about the install process and possible fixes to issues like the fact you should be on stock a10 before flashing when i and others provide far better support on telegram.
My advice is to use the vache moto flash tool, grab the firmware from lolinet, and flash back to stock a10, then after you make sure stock is working and everything install the twrp, wipe the data using wipe - format data on twrp, then proceed to just flash the rom via twrp.
JPutz said:
Any chance this will go to version 5.x? Would be nice to keep this going, but I don't now if Havoc is planning on putting A12 on this device.
Click to expand...
Click to collapse
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
ph4n70m-404 said:
No clue on Havocs plans for a12, this isn't official so it isn't havoc's decision if it gets put on this device or not, after there is a good a12 tree for this device that's stable and havoc releases stable 12 then yes most likely.
Click to expand...
Click to collapse
That's cool. I am happy where I am at. Rock stable and works flawlessly. I just think it is cool that I have a phone this old and it has recent updates on a custom rom.
I still say this should be stock. I had to redo my phone back to factory (flashed the update to the wrong slot. Oops!) and the stock rom was so annoying. I though I just hated iOS and the Samsung roms.