{
"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.
5) Please keep bugreports to this thread or Discord. Do NOT create a Jira ticket. This is still in early development so we don't accept any bugreports yet.
Install Instructions:
Flash the newest factory image
Move your ROM + [GApps] to internal storage
Reboot to TWRP
Wipe Data, Dalvik/ART Cache, and cache
Flash the ROM + [GApps]
Reboot to System -> Enjoy CarbonROM
Get CarbonROM
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 CR 7.0 OPAL, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
ROM OS Version: 9.x Pie
Version Information
Status: Stable
Created 2019-04-19
Last Updated 2019-07-04
A few notes before you proceed:
Before going straight to the download section there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Installation Instructions:
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Peripherals:
FBE Recovery: TWRP
WHAT?!!!! ???????????????????????????????????? I'm really impressed with your HARD WORK ??????? Its amazing the effort you are doing to keep this machine alive. Thank you PixelBoot ?
wow @PixelBoot another ROM from yourself! :good:
Great efforts
You're keeping the Nexus 6P alive
Can i dirty flash this ROM over Pixel Experience?
sufy1000 said:
wow @PixelBoot another ROM from yourself! :good:
Great efforts
You're keeping the Nexus 6P alive
Can i dirty flash this ROM over Pixel Experience?
Click to expand...
Click to collapse
Sadly, a clean flash has to be done.
Thanks for the support! :fingers-crossed:
God daaam another one! :victory: :victory:
You're the best PixelBoot
Thanks from Dominican Republic!
Has been on this rom for a day. Look good and solid. Though I have moved to AOSP Extended because I want a bit more customization.
I am on this ROM since the release, no problems whatsoever
thanks a ton dev
It's very snappy
How did I not notice this! Thanks @PixelBoot
very nice
Installed it, gonna take it for a spin. Just enough additional options, really like the agrresive battery options. So will see how will it pan out. So far so good.
sage of six paths said:
Installed it, gonna take it for a spin. Just enough additional options, really like the agrresive battery options. So will see how will it pan out. So far so good.
Click to expand...
Click to collapse
What kind of settings are there in aggressive options?
sufy1000 said:
What kind of settings are there in aggressive options?
Click to expand...
Click to collapse
Theres agrresive idle and standby ( just toggle on or off ) options in the carbon fibre settings. My phone is still charging to full, but it'll take a day or two till the rom and nfs settle and then i'll have an sot measure. This is kinda the middle point between no extras, and not having too much customization and i like it.
just installing now.
look nice, what kernel for more performance? let me know
I'm not using any kernel per se, i'm using nfs and that's it. However whom ever made the rom made an excellent job since right now after first full charge rom is at 50% battery 2h and 50 mins of sot. So will likely get over 5h of sot for my use which is awesome, and it might even improve slightly in the coming days till the rom and nfs settle properly.
sage of six paths said:
I'm not using any kernel per se, i'm using nfs and that's it. However whom ever made the rom made an excellent job since right now after first full charge rom is at 50% battery 2h and 50 mins of sot. So will likely get over 5h of sot for my use which is awesome, and it might even improve slightly in the coming days till the rom and nfs settle properly.
Click to expand...
Click to collapse
When did you replace your battery?
Sorry for the bonehead questions I'm about to ask, but I need some help here. I tried to find the Carbon FAQ on the website beforehand, but there's like no link to it whatsoever so this is the only place I can ask.
Now mind you I'm no novice at flashing roms, but I've been out of the scene for a long time now. Right now I have an old stock rom on this phone and it's running like absolute crap so I want to erase everything and take a new rom out for a spin in hopes to make things more snappy. This one caught my eye.
Question 1) In the install instructions 1 says to flash the newest factory image. Is this an absolute must? I'm on stock 8.1.0, unlocked bootloader, TWRP installed. I'm sure there's probably nothing newer for this phone than 8.1. Can I just download the rom + gapps, format it all in TWRP, and then install or am I going to royally screw anything up?
Question 2) Can anyone point me to the correct Gapps to use. With so many options these days I really don't want to make the wrong choice, then find the right ones, and have to reinstall.
Thank you in advance.
Raverrevolution said:
Sorry for the bonehead questions I'm about to ask, but I need some help here. I tried to find the Carbon FAQ on the website beforehand, but there's like no link to it whatsoever so this is the only place I can ask.
Now mind you I'm no novice at flashing roms, but I've been out of the scene for a long time now. Right now I have an old stock rom on this phone and it's running like absolute crap so I want to erase everything and take a new rom out for a spin in hopes to make things more snappy. This one caught my eye.
Question 1) In the install instructions 1 says to flash the newest factory image. Is this an absolute must? I'm on stock 8.1.0, unlocked bootloader, TWRP installed. I'm sure there's probably nothing newer for this phone than 8.1. Can I just download the rom + gapps, format it all in TWRP, and then install or am I going to royally screw anything up?
Question 2) Can anyone point me to the correct Gapps to use. With so many options these days I really don't want to make the wrong choice, then find the right ones, and have to reinstall.
Thank you in advance.
Click to expand...
Click to collapse
If your 8.1 is on the december update your good to go, if not flash that one.
If it is you need the fbe recovery for this rom, and all the roms form pixelboot. Aslo for latest lineage 16.
Flash that recovery over the one you have and reboot to recovery, flash rom and gapps, i always have the delete cache and dalvik cache ticked.
After that i go to fastboot and type fastboot -w to delete data, it's probably fine to do the factory format from within twrp.
After that boots i return to twrp to flash magisk, and then download the magisk manager, some roms don't need it, some do.
To use the correct gapps you can just go to open gapps website and pick arm64 9.0 and then the flavour you wish nano, pico or higher.
Make sure you flash open gapps right after rom and then reboot otherwise you might have problems. Just pick the ones with the latest security patch. Thats about it.
You can find an fbe recovery in the pixel experience rom thread, 3rd or 4th post below.
---------- Post added at 09:30 PM ---------- Previous post was at 09:08 PM ----------
sufy1000 said:
When did you replace your battery?
Click to expand...
Click to collapse
Maybe a month ago, two at the very most. In the end after first charge the battery life will round at about 4.30h which is about the same i get on aosp right now.
Related
As usual, pointing to the post concerning this ROM from its main team HERE
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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 at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
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.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-We've fixed PIE! It no longer decides to be invisible from time to time.
-We fixed the battery charge light! None of us use it but apparently you guys are just nuts for it!
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-3.4 kernel on D2xxx devices. It's finally stable enough where we're comfortable with this - remember to only flash other 3.4 kernels or it will not boot as there are rom-level dependencies.
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
Screenshots
{
"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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
Carbon change log HERE
6.02.13 -
Initial release "nightly" build
Fixed Camera
Fixed GPS
6.09.13 -
Synced to Chad0989's trees
Synced sources
Uses chad's -chad branch not fb branch kernel, crpalmer's kernel may work with this build.
6.11.13 -
HALO implemented
6.30.13
Code:
Synced back up with chad's trees
Synced with Carbon source
-Removed for space, post is to long
7.15.13
Code:
Device tree:
Updated with *SOME* of chad/flyhalf/crpalmer's recent work:
https://github.com/CM10DNA/android_device_htc_dlx/commit/b18cbc01baf535de447b44675727ca91b7548bea - cleanup more inline with cm *note* not all changes were done, it was causing issues with Carbon.
https://github.com/CM10DNA/android_device_htc_dlx/commit/9a01d0428755502b17cd2d5854fd293da9b6f143 - updates from m7
Kernel:
To many to list one by one, however visit here https://github.com/CM10DNA/android_kernel_htc_dlx/commits/cm-10.1-chad
And look back to june 30th which was my last pull.
Change log removed for space reasons (post is to long now)
8.06.13:
Tried out the BT fixes from Chad's CM10.2 stuff, so it may or may not work.
Current sources, should be the same as the 8.1.13 final stable releases for Nexus devices.
Change Log 8.06.13
The post is to big for XDA posts now, so instead I'll include a link to the changelog itself!
From here on ONLY use 4.3 gapps, I don't want to see any reports of broken cameras, keyboards or locking up if you are on anything besides a 4.3 gapps!
8.09.13
Fully updated to 4.3 Jellybean source
Fully updated to chad and crew's latest work on kernel/vendor/device
Use only the included kernel for now, crpalmer's 3.1.2 kernel is not fully compatible and will cause display and camera glitching.
Use only gapps for 4.3
A complete revamp of Carbon, they're starting over from the ground up so you may notice a lot of features missing, such as halo, expect these to return soon. What you can also expect is a smooth fast ROM with a solid foundation to build upon!
8.12.13
Updated source
BlueTooth now turns on (how well it works I can't test)
Single build, for now GSM is at least somewhat working on the CDMA build, so for now, pending further investigation, only a single "unified" version is available.
8.19.13
Updated souce
Updated with Chad and company's latest awesomeness
Features are beginning to trickle back in, Halo is back, etc.
Compatible with crpalmer's latest kernel (and .torrented's should also work)
Change Log 8.19.13
8.26.13
Updated Carbon source (ribbons?)
Updated with chad and groups work:
Device:
- Use correct mic for Google Search and other voice apps (bottom, not the top)
- Change back to HTCQualcommRil (from HTCCDMAQualcommRil) * CDMA build only
- Custom recovery graphics
- Sim hotswap will no longer prompt for reboot
- Everything from the 17th to today
https://github.com/CM10DNA/android_d...ommits/cm-10.2
Kernel:
- Hardware VSync support
- Missing clocks added
- ROW Scheduler added
- Everything done for the 14th to today, I'm not typing that all out
https://github.com/CM10DNA/android_k...ommits/cm-10.2
ROM:
- Carbon Fibers updated with a new swype style
- Ribbons returns from AOKP
- See change log on the site as usual
8.29.13
- Updated source
- Removed default showing of the overflow menu button, most hardware key map this and prefer to save the screen space.
- GSM Only: Changed default to WCDMA preferred from GSM/LTE: Should help with initial issues with calling/sms/mms maybe not working on some networks.
- Device, Kernel, Vendor trees otherwise untouched from last build.
- Listview Animations and Interpolator (Carbon Fibers > Interface)
9.13.13
- Updated source
- Built against the M7 kernel
- Includes everything done up to a couple of hours ago.
- NOT Global, CDMA and GSM versions will be needed still.
- CM's enhanced NFC added, I can't test it so any reports would be appreciated.
- MUST CLEAN FLASH THIS NO MATTER WHAT
- Compatible with crpalmer's 4.x.x kernels as far as I know.
9.13.13- B2
Removed qcom keystore to prevent hot reboot on display off.
9.13.13- CDMA B3
Correct issue causing bootlooping on the CDMA build, GSM didn't have it.
9.15.13
Updated source build:
Halo updates from PA
Add color support to text only battery
Fix network speed statusbar indicator traffic color on reboot
Fix reboot menu not being themed
Minor changes
9.16.13
Updated Carbon source:
Small stuff
Corrected QCOM keystore issue (thanks crpalmer)
9.23.13- Part Deux
Update 9.23.13
Updated Carbon source
All updates for the device/kernel sources.
Things that were messed with include the GPS HAL, some display stuff, camera stuff, and more. If you're interested in the details...
Device:
dlx: Import GPS HAL from jf
dlx: HTC camera expects insecure MM heap
dlx: enable option to set button brightness
Kernel:
Large amount, so I'll post the commits from last update, not each one. Not all concern the dna directly. Quite a few concerning bcmdhd, kgsl, msm_fb and other goodies
FROM HERE
TO HERE
Apparently the blank display was due to changes Carbon made to msm8960-common that I hadn't thought to look in on, and it changes quite a few things concerning the display. For now I have reverted to the CM common tree to correct the display issue.
12.5.13:
Initial bringup to KitKat 4.4
UNTESTED, CDMA Version only for now.
New folder for the 4.4 ROM here http://pio-masaki.com/DroidDNA/Carbon-KK
Please use an updated 4.4 GApps package!
Please CLEAN FLASH this only!
Please flash this with the latest 4.4 compatible recovery!
12.10.13:
CDMA only
Updated source and trees
I still can't test so those who had pervious issues (data, MMS) please give this a try and report when you have time.
1.22.14:
CDMA only, may be Global.
Updated build, untested as I lack the device now, please report any issues!
1.29.14:
Updated sources
Camera should work now
Please see if the Settings>Carbon Fibers> Interface FC still occurs.
As usual use the 4.4 GApps that has worked for you so far.
Not on pio-masaki.com yet, you can nab it now here http://d-h.st/Zsj
2.2.14:
Updated sources.
Camera and Interface FCs were corrected last build, should also be alright here.
4.4 GApps that you usually use.
Available on pio-masaki.com
2.5.14:
Updated sources.
Check that the carrier, date/day/whatever is proper and that the data connection icons are correct (IE no more roaming in 3G etc)
For those with speed issues, a report on that would be appreciated.
4.4 GApps that you used last time.
Available on pio-masaki.com
2.9.14:
Updated sources
Built because I was already on my 8th build of the day, why not?
4.4 GApps that you used last time.
Available on pio-masaki.com
2.20.14:
Updated sources
Built because my wife hates me and the couch sucks
4.4 GApps as usual
Available on pio-masaki.com
3.8.14:
Updated sources
Built because why not, its been awhile.
4.4 GApps as usual
Available on pio-masaki.com
4.7.14:
Updated sources
Built because its been a damn month, that's why!
4.4 GApps as usual
Available on pio-masaki.com
6.23.14:
4.4.4
Updated sources
JustArchi optimizations implemented
FULL 100% -03 built ROM, not just portions
Linaro 4.8 toolchain
Built as user instead of userdebug, odexes the ROM and disables some of the background logging
Updated Adreno candies
Peek
Available on pio-masaki.com in the usual place, however look in the SS folder as this is no longer just Carbon.
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
If you are not S-OFF you will need to extract the boot.img and flash it separately, either flashGUI or fastboot, your choice, needs done.
S-OFF:
Download the ROM for your needs, CDMA or GSM.
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup phone as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your phone in settings.
CDMA version: for use with Verizon, NOT for any other network.
GSM version: for use with GSM carriers, NOT for Verizon.
Global verison: for use with BOTH Verizon and GSM, no different build required
FAQS
If you didn't read the bugs list in the first post, go back up and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, that's basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. For now you can use the existing CM tree and build it that way. Any further help can be asked as needed.
Q. Can I use -insert kernel name here-?
A. No. Well ok you can, but please don't report any issues while running anything besides what came with the ROM.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyourass.zip"
Q. Can we do random bantering and good natured fun poking in your thread?
A. Sure, feel free to go OT on occasion, I'm all for having FUN on xda, even if some are not. I would like users to feel completely comfortable in my thread with no worries of me coming down on any thing not ROM or development related, I don't run a strict thread as many know by now. What I don't want is flame wars, though. Please keep a limiter on what is good natured fun as we all know things can get out of hand quickly. If someone is taking offense to something going on and its made known, please end it there with no hard feelings.
Bugs:
None specific to Carbon
Downloads:
Please visit pio-masaki.com for all my ROM builds
Kernel source used:
https://github.com/CyanogenMod/android_kernel_htc_m7
Whoop!!!! I heard rumors! I'm about to no sleep and flash this tonight...thanks so much for your hard work!
I downloaded this from your server and running it now. Seems very smooth and I like the breathing effect of notifications. You need to rest!
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Didn't notice the placeholder post? I was still making the posts lol
And yes, generally it will have whatever issues CM currently has.
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Goto www.pio-masaki.com and download from there
@pio,
Really nice work man.
Using it for the last 2 days and I can say that its the smoothest ROM out there. Paired with crpalmers kernel its SWEEEEEEEEEEET.
Tapatalked from TF300T with AOKP goodness
Pio is a ROM building machine! He probably dreams about code and bug fixes...lol
Websites going down at 3am CST for update and backup...only be down about 20 mins
Updates and backup done. Websites up.
Sent from my Nexus 7 using Tapatalk 2
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Epic 4g said:
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Click to expand...
Click to collapse
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
uppon2 said:
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
Click to expand...
Click to collapse
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Epic 4g said:
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Click to expand...
Click to collapse
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
diesburg said:
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK I will rename it "something.zip" as you said with out the quotations marks & flash. Thank you for the heads up. You are the man! :good:
Awesome going to flash this now! Does this include the halo framework or is that not released yet?
My head is spinning! Which way to I turn? Thanks pio!!
Sent from my HTC6435LVW using Tapatalk 2
I added the index.php issue to the FAQs last night.
Personally I use crpalmers kernel with this ROM, its great, by all means use it.
Personally I use carbon because I don't use PA features. Second is ReVolt, then PAC, though since the recent apps fix in PAC its a little harder to say lol
No halo in this, its in the works, though. The carbon team has released a special halo version for some devices a couple weeks ago, so it may happen once halo matures a little more.
Tapatalked from my HTC DNA - Carbon
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
coachcrey said:
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
Click to expand...
Click to collapse
It was fixed, also if you flash crpalmers kernel wifi will work as well.
Budwise said:
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
Click to expand...
Click to collapse
Its in /data/media, this is discussed numerous times in various threads so I won't get into much detail, but copy from /data/media to /0 and it'll work fine in 4.2 ROMs. To go back to a sense ROM move back from /0 to /data/media. After you can delete /0 but don't they to delete /data/media, just what may be in it as that's your internal SD card.
Tapatalked from my HTC DNA - Carbon
{
"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 XL
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-08
Last Updated 2018-03-17
Nice to have you around!
Sent from my Pixel XL using Tapatalk
I have e to ask...What all pixel exclusive feature are in carbon now? I used to use carbon back on my sgs3 an missed it in your absence
I'm still using carbon rom on my nexus 5. I'm so happy to see this on Marlin. Can't wait to flash!
I just get "No SIM-Card". Did somebody else tried this ROM?
I haven't tried this rom yet, but thank you so much!!! We had 3 roms drop in less than 24 hours so it will take me a day or two to test.
Nic888 said:
I just get "No SIM-Card". Did somebody else tried this ROM?
Click to expand...
Click to collapse
Hi Nice,
I have been getting that on different roms after flashing, I usually reboot to recovery again, factory reset quickly in twrp, and then reflash the rom, flash twrp again, then from twrp reboot to recovery again, then once you're back in recovery reboot to the system or rom. Hope this helps.
Where are the installation instructions? FAQ section on carbon website is not working. Thanks
I had no clue carbon was about to drop for the pixel xl. This has always been my favorite rom ever. Appreciate the CARBON MARLIN LOVE!
---------- Post added at 07:18 AM ---------- Previous post was at 07:11 AM ----------
dablitzkrieg said:
Where are the download instructions? FAQ section on carbon website is not working. Thanks
Click to expand...
Click to collapse
Download instructions??? Tap "Get CarbonRom" and download for your device. But honestly if you need instructions on how to download a ROM, I would hold off on trying to learn to flash a ROM
skulldreamz said:
I had no clue carbon was about to drop for the pixel xl. This has always been my favorite rom ever. Appreciate the CARBON MARLIN LOVE!
---------- Post added at 07:18 AM ---------- Previous post was at 07:11 AM ----------
Download instructions??? Tap "Get CarbonRom" and download for your device. But honestly if you need instructions on how to download a ROM, I would hold off on trying to learn to flash a ROM
Click to expand...
Click to collapse
Lol, I meant installation instructions
Flashed carbon one of my favorites of all time.
But problems ensued after.
no radio,no clear instructions for gapps.
replaced twrp with carbon recovery in very small font,too small for me to see,no signal etc.
but its a work in progress thanks,will flash again when it gets a little more stable
Restoring from factory image now latest google stock then ill retry.
And before anyone goes on a rant,yes this ROM is free i realize that just saving you some trouble.
Right now its not fully functional in my case ymmv.
Carbon Marlin........ One of my regular dual boots on S3 Great to see support for this device from you guys!
I'm very much looking forward to trying this when I can!
TechBSwift said:
I haven't tried this rom yet, but thank you so much!!! We had 3 roms drop in less than 24 hours so it will take me a day or two to test.
Click to expand...
Click to collapse
That almost screams for the need for MultiROM, huh?
humdrum2009 said:
Flashed carbon one of my favorites of all time.
But problems ensued after.
no radio,no clear instructions for gapps.
replaced twrp with carbon recovery in very small font,too small for me to see,no signal etc.
but its a work in progress thanks,will flash again when it gets a little more stable
Restoring from factory image now latest google stock then ill retry.
And before anyone goes on a rant,yes this ROM is free i realize that just saving you some trouble.
Right now its not fully functional in my case ymmv.
Click to expand...
Click to collapse
Ok, lets see.
I experienced some trouble with the vendor blobs I was using in the past, I made a build overnight with different vendorblob setup, maybe you could test it.
It also includes GApps, as these still have trouble on the Pixel devices. We (the Carbon team) don't want to release builds with included GApps for various reasons, so I will release unofficial builds with included GApps until the GApps issues are solved.
The unofficial builds with GApps can be found here:
https://dl.myself5.de/marlin/CarbonROM/
The TWPR thing is caused by the Recovery setup itself. Recovery is built into the Kernel. This means you need to flash the TWRP installer zip again after flashing a ROM.
@Myself5
Dl in progress. Will test it for you shortly
Flashing in progress
Booting. Didn't saw this animation for a long time
Flashed like this
Rom and twrp
Reboot to twrp
Flashed vendor V
Reboot system
Reboot recovery
Flashed latest su
Reboot system
All fine.
TB is running
Flashed MVK kernel and all fine
Fantastic release for a comeback
Will leave it on for tomorrow to test normal daily usage. So I could say something about battery and overall feeling.
mikaole said:
@Myself5
Dl in progress. Will test it for you shortly
Flashing in progress
Booting. Didn't saw this animation for a long time
Flashed like this
Rom and twrp
Reboot to twrp
Flashed vendor V
Reboot system
Reboot recovery
Flashed latest su
Reboot system
All fine.
TB is running
Flashed MVK kernel and all fine
Fantastic release for a comeback
Will leave it on for tomorrow to test normal daily usage. So I could say something about battery and overall feeling.
Click to expand...
Click to collapse
May I ask what the mvk kernel is?
It's the kernel from the velocity dev. Not on xda. He left xda about 4 years ago.
So one normal day in use and I must say it's damn nice. Battery is fantastic.
All works as it should. Bluetooth, Wlan, mobile etc.
Not one bug comes through my way Fantastic job.
Thx again.
Nice to see you guys back... Now don't leave again.. High5 guys!
Hey guys, I'm one of the core developers of CarbonROM...
...and there is something I would like to address:
I would like to keep our threads clean, and strictly about development and/or related topics. XDA is the place to be helping one another, sharing ideas, bringing each other up in this developer community through contributions. Because of the impulse of certain users, I want to follow a strict policy for postings.
The general idea of what should/should not be posted here is outlined in the XDA forum rules.
MikeChannon said:
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Click to expand...
Click to collapse
Things like...
I love your rom, running great! But, battery life is not as good as XXX rom, please add XXX into the rom.
Click to expand...
Click to collapse
...should not be posted here.
Things like...
"I love your rom, but I'm getting memory issues that are not present in XXX rom that affect battery drainage. XXX rom has a the patch on their gerrit that may potentially solve the memory leak. I'll send a push to your gerrit review server so you guys can check it out!"
Click to expand...
Click to collapse
...are welcomed with open arms (and maybe even kisses, too!)
The only off-topic posts that may happen here may come from a CarbonROM core developer announcing or asking for a certain opinion on XXX feature. Thanks for understanding, this is the way development threads were meant to be in these forums. I invite everyone to stay vigilant to report posts that do not follow the summary by MikeChannon in the XDA rules about what should not be posted. Do not engage users if they don't follow the XDA rules, Forum Moderators exist for the purpose of handling such users . Long live the report button!
Myself5 said:
That almost screams for the need for MultiROM, huh?
Ok, lets see.
I experienced some trouble with the vendor blobs I was using in the past, I made a build overnight with different vendorblob setup, maybe you could test it.
It also includes GApps, as these still have trouble on the Pixel devices. We (the Carbon team) don't want to release builds with included GApps for various reasons, so I will release unofficial builds with included GApps until the GApps issues are solved.
The unofficial builds with GApps can be found here:
https://dl.myself5.de/marlin/CarbonROM/
The TWPR thing is caused by the Recovery setup itself. Recovery is built into the Kernel. This means you need to flash the TWRP installer zip again after flashing a ROM.
Click to expand...
Click to collapse
I get the error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Click to expand...
Click to collapse
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the re-brand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.0
Download link: Preview-AICP-berkeley
Full Changelog link: http://dwnld.aicp-rom.com/
VoLTE
IR Blaster
Let me know if you see any more
FAQ:]
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see, if your device is build on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them (as long as they are LOS based), but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet available for Oreo.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, Gapps (only needed if you wipe the system), your preferred root solution and reboot. Or you might just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again if you don't want to loose root, and then reboot.
A2. if it's a flashable ZIP You can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder on the internal storage.
Q I keep losing root with Magisk, how do I fix it?
A Check this out, if that doesn't work for you ask for help in this thread, read or ask in the Magisk thread on XDA or just flash Magisk again!
Q I'm having issues with WhatsApp, how do I fix it?
A Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the root section in the AICP Extras menu.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device
2. Boot to recovery (TWRP recommended)
3. Wipe system, Cache, data and ART/Dalvik cache
4. Flash ROM Zipfile
5. Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot to system
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported Root Solutions:
[COLOR="Dark Red"]Currently SuperSU and Magisk cause the device to reboot every so often.[/COLOR]
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
PLEASE NOTE OTAS ARE CURRENTLY NOT AVAILABLE FOR AICP FOR BERKELEY
ROM & Additional links:
Gerrit Code Review
Github
IceColdJelly AICP G+ community
Contributors
@DarkExistence
LuK1337 (Initial Berkeley tree)
Flex (Fixing fingerprint)
The rest of the Honor Open Source dev community!
And everybody else who contributed to the tree!
You want to see a normal night at the "DEV office", click here!!
XDA:DevDB Information
AICP for Honor View 10, ROM for the Honor View 10
Contributors
DarkExistence
Source Code: https://github.com/AICP
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2018-04-28
Last Updated 2018-04-28
Please note:
- This a flashable zip that must be flashed in TWRP. This is not a GSI
- GAPPS aren't included
- This can only be used on the Honor View 10
Reserved.
This too
One more because why not
are you using unofficial or official twrp?
IcipherPT said:
are you using unofficial or official twrp?
Click to expand...
Click to collapse
Unofficial
Rommco05 said:
FPS gestures like on EMUI are included?
Click to expand...
Click to collapse
Not at the moment, no
DarkExistence said:
Unofficial
Click to expand...
Click to collapse
You can enter recovery mode again after flash your rom?
IcipherPT said:
You can enter recovery mode again after flash your rom?
Click to expand...
Click to collapse
Yeah, I can anyway, but YMMV. Either through the advanced reboot settings in Dev options or from ADB reboot bootloader. Or just from start up without USB cable plugged in.
DarkExistence said:
Yeah, I can anyway, but YMMV. Either through the advanced reboot settings in Dev options or from ADB reboot bootloader. Or just from start up without USB cable plugged in.
Click to expand...
Click to collapse
Yours is a L09 or L04?
@DarkExistence
the next question is, were you able to decrypt your phone with unofficial twrp and aicp on board?
IcipherPT said:
Yours is a L09 or L04?
Click to expand...
Click to collapse
Part of the developer program so L04 . Also on the latest software.
kurvenmeister said:
@DarkExistence
the next question is, were you able to decrypt your phone with unofficial twrp and aicp on board?
Click to expand...
Click to collapse
Yes I could , just had to enter in my screen lock pin and it decrypted. Again though YMMV so if it works for me doesn't necessarily mean it works for you, I'm not a TWRP expert don't see why it wouldn't though
@DarkExistence
thank you for your quick reply. will try it out soon.
you came from stock, flashed twrp, then aicp and then decrypted your device? could you tell me your way? decrypting right after flashing twrp or after flashing aicp?
I think there is a problem with the L09 variant, after flash a custom rom (anyone) I cannot enter anymore in TWRP. I'm not the only one reporting this If I'm not wrong
EDIT: I got an infinite bootloop to enter to recovery xD Had to wait until the eRecovery said "failed to install software"
IcipherPT said:
I think there is a problem with the L09 variant, after flash a custom rom (anyone) I cannot enter anymore in TWRP. I'm not the only one reporting this If I'm not wrong
EDIT: I got an infinite bootloop to enter to recovery xD Had to wait until the eRecovery said "failed to install software"
Click to expand...
Click to collapse
Did you ask in the TWRP thread? Seems more like an issue there vs the actual ROM itself. Hope you get it sorted though , I had a similar issue after updating to the latest stock emui build.
As said in the OP AICP is based on Lineage which from reading the thread you seemed to have issues with before? Most likely a similar case here. Have you tried official twrp maybe?
kurvenmeister said:
@DarkExistence
thank you for your quick reply. will try it out soon.
you came from stock, flashed twrp, then aicp and then decrypted your device? could you tell me your way? decrypting right after flashing twrp or after flashing aicp?
Click to expand...
Click to collapse
I actually came from stock , flashed the unofficial TWRP image, flashed the old lineage system.img (before they switched to the .zip) and then rebooted to TWRP from there and was able to decrypt and flash etc. Waiting for the official TWRP to be updated and will be switching to that then. That's what worked for me anyway but I had glitched my phone with a bad attempt at updating official emui.
DarkExistence said:
Did you ask in the TWRP thread? Seems more like an issue there vs the actual ROM itself. Hope you get it sorted though , I had a similar issue after updating to the latest stock emui build.
As said in the OP AICP is based on Lineage which from reading the thread you seemed to have issues with before? Most likely a similar case here. Have you tried official twrp maybe?
Click to expand...
Click to collapse
Yes ofc, I'm testing as much as I can trying to help every developer, I was asking you to get as much info as I can
I didn't try with offical version because of the encryption =\ (That issue that you are talking about was my fault: frp lock xD)
IcipherPT said:
Yes ofc, I'm testing as much as I can trying to help every developer, I was asking you to get as much info as I can
I didn't try with offical version because of the encryption =\ (That issue that you are talking about was my fault: frp lock xD)
Click to expand...
Click to collapse
Ah, When I was using the official version (unable too now because of my emui version), I used the RemoveEncryption.zip file and it worked pretty well for me, incase you wanted to try it out Just no MTP gotta adb push
DarkExistence said:
Ah, When I was using the official version (unable too now because of my emui version), I used the RemoveEncryption.zip file and it worked pretty well for me, incase you wanted to try it out Just no MTP gotta adb push
Click to expand...
Click to collapse
Not a problem for me! I will test it if you want!
{
"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...
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! These builds are experimental and can contain Bugs (as listed above). 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 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 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.
Download
Join the CarbonROM Discord server
Meet us on Telegram
Homepage
GitHub
Kernel source
Special thanks to @derf elot and @modpunk for most of the work on the yoshino platform.
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
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2019-08-24
Last Updated 2019-08-28
Does it work on poplar dsds?
How to flash it ?
Can you guide me step to step ?
And we need install gapps at the same time with rom ?
wow!awsome!
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
haiha2001 said:
How to flash it ?
Can you guide me step to step ?
And we need install gapps at the same time with rom ?
Click to expand...
Click to collapse
1.backup your data
2.unlock the bootloader
3.flash the recovery---TWRP
4.format the data partition
5.wipe your device
6.push the rom to your device
7.flash the rom
8.reboot&enjoy
LuxferreX said:
wow!awsome!
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
1.backup your data
2.unlock the bootloader
3.flash the recovery---TWRP
4.format the data partition
5.wipe your device
6.push the rom to your device
7.flash the rom
8.reboot&enjoy
Click to expand...
Click to collapse
Which version of TWRP you have used to flash rom ?
We don't need gapps ?
haiha2001 said:
Which version of TWRP you have used to flash rom ?
We don't need gapps ?
Click to expand...
Click to collapse
Edit : if i have dual sim, i can you this twrp for popular dsds to flash this rom : https://androidfilehost.com/?fid=6006931924117921380
haiha2001 said:
Edit : if i have dual sim, i can you this twrp for popular dsds to flash this rom : https://androidfilehost.com/?fid=6006931924117921380
Click to expand...
Click to collapse
U can't use it u have to use the twrp for single sim
I tried it on xz1 dual but it doesn't detect sim card I think it's for single sim only
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
Myself5 said:
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...
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! These builds are experimental and can contain Bugs (as listed above). 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 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.
5) Please keep bugreports to this thread or Discord. Do NOT create a Jira ticket. This is still in early development so we don't accept any bugreports yet.
Download
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Special thanks to @derf elot and @modpunk for most of the work on the yoshino platform.
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
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2019-08-24
Last Updated 2019-08-23
Click to expand...
Click to collapse
Thanks so much for this wonderful ROM but please make a version for dsds
haiha2001 said:
Edit : if i have dual sim, i can you this twrp for popular dsds to flash this rom : https://androidfilehost.com/?fid=6006931924117921380
Click to expand...
Click to collapse
1.yeah,you need to flash gapps
2.this one worked on my device https://androidfilehost.com/?fid=6006931924117921380 ,for the dual sim
LuxferreX said:
1.yeah,you need to flash gapps
2.this one worked on my device https://androidfilehost.com/?fid=6006931924117921380 ,for the dual sim
Click to expand...
Click to collapse
This rom have supported for dual sim ? And which variant of gapps you have used ? ( Stock, micro, pico ... )
hsheemi said:
U can't use it u have to use the twrp for single sim
I tried it on xz1 dual but it doesn't detect sim card I think it's for single sim only
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
Thanks so much for this wonderful ROM but please make a version for dsds
Click to expand...
Click to collapse
No logs, no detailed descriptions, no support. I've asked for someone to test the build on the DualSIM variant a few days ago. You were among those who answered but didn't provide any feedback. So i went ahead and released a version that is tested on the SingleSIM Variant and now there's 4 people complaining about DualSIM support?
less than 12 Hours of creating this thread I already regret touching Sony devices again...
Also, did you really have to quote all of the OP...?
Myself5 said:
No logs, no detailed descriptions, no support. I've asked for someone to test the build on the DualSIM variant a few days ago. You were among those who answered but didn't provide any feedback. So i went ahead and released a version that is tested on the SingleSIM Variant and now there's 4 people complaining about DualSIM support?
less than 12 Hours of creating this thread I already regret touching Sony devices again...
Also, did you really have to quote all of the OP...?
Click to expand...
Click to collapse
It was 3 days ago and all you ask was how did it work regarding the dual sim, in your other thread, but with all do respect not to many are willing to or for that matter going to down grade to Android 8 , I guess that's the last version to test something that is a bit vague in detail.. so that alone pretty much kill your lack of feedback..
Now take a second and look at where most of your so called issues and questions are coming from ..our newer members due to many a lack of details on how to flash, which gapps to use ect.
which to be honest should be in the op but mainly their lack of experience and an allergic reaction to the search button..
Sony may have it's faults and nobody here twisted your are to release the rom but your lack of information is more than likely the reason for half ass answers and or problems.
Myself5 said:
No logs, no detailed descriptions, no support. I've asked for someone to test the build on the DualSIM variant a few days ago. You were among those who answered but didn't provide any feedback. So i went ahead and released a version that is tested on the SingleSIM Variant and now there's 4 people complaining about DualSIM support?
less than 12 Hours of creating this thread I already regret touching Sony devices again...
Also, did you really have to quote all of the OP...?
Click to expand...
Click to collapse
sorry man if i bothered you but i really dont know how to take logs
lilbrat said:
It was 3 days ago and all you ask was how did it work regarding the dual sim, in your other thread, but with all do respect not to many are willing to or for that matter going to down grade to Android 8 , I guess that's the last version to test something that is a bit vague in detail.. so that alone pretty much kill your lack of feedback..
Now take a second and look at where most of your so called issues and questions are coming from ..our newer members due to many a lack of details on how to flash, which gapps to use ect.
which to be honest should be in the op but mainly their lack of experience and an allergic reaction to the search button..
Sony may have it's faults and nobody here twisted your are to release the rom but your lack of information is more than likely the reason for half ass answers and or problems.
Click to expand...
Click to collapse
Your post is an in depth explanation of what is wrong with the Sony community. The OP design is the exact same used on ALL CarbonROM XDA Threads, yet the Xperia XZ Premium and XZ1 community are the ONLY people complaining about it. Surely this is a me issue. Perfectly outlined by your assumption that the builds I released were Oreo. Heck, I even attached a picture of the XZ1 and XZP running those VERY builds I linked that said Android 9. I'm not obliged to do anything. I release those builds because it's a fun hobby. Constantly spoon feeding people because they refuse to do their research is not on that list.
There is no such thing as "which gapps to use". Ever. On any device. Go to any stupid GApps website and download the GApps that match YOUR taste. If you need advice on arm vs arm64 and which android version then you're wrong in this forum.
less than 24 hours into the thread creation and I consider closing it again. Thats gotta be a new high.
hsheemi said:
sorry man if i bothered you but i really dont know how to take logs
Click to expand...
Click to collapse
Check out https://www.xda-developers.com/how-to-take-logs-in-android/.
Though, you could've found that with a Google search. First link when looking for "xda get logs".
Also can you check which device name is shown in Settings? G8341 or G8342?
Myself5 said:
Your post is an in depth explanation of what is wrong with the Sony community. The OP design is the exact same used on ALL CarbonROM XDA Threads, yet the Xperia XZ Premium and XZ1 community are the ONLY people complaining about it. Surely this is a me issue. Perfectly outlined by your assumption that the builds I released were Oreo. Heck, I even attached a picture of the XZ1 and XZP running those VERY builds I linked that said Android 9. I'm not obliged to do anything. I release those builds because it's a fun hobby. Constantly spoon feeding people because they refuse to do their research is not on that list.
There is no such thing as "which gapps to use". Ever. On any device. Go to any stupid GApps website and download the GApps that match YOUR taste. If you need advice on arm vs arm64 and which android version then you're wrong in this forum.
less than 24 hours into the thread creation and I consider closing it again. Thats gotta be a new high.
Check out https://www.xda-developers.com/how-to-take-logs-in-android/.
Though, you could've found that with a Google search. First link when looking for "xda get logs".
Also can you check which device name is shown in Settings? G8341 or G8342?
Click to expand...
Click to collapse
Pictures.. where as there aren't any posted on the but the logo for the rom on the lab app.. I personally haven't look at the rom on other various devices but have glanced at it here, as you said and posted the format is the same simple copy and paste, no screenshots, no flashing instructions no mention of a bug list if there are any.. so maybe the format may need a tweak or two for us slow xz1 and xz premium folks..and if the lack of info in the op causes a few questions to be asked ..then feel to take you ball and go home..
lilbrat said:
Pictures.. were as there aren't any posted on the but the logo for the rom on the lab app.. I personally haven't look at the rom on other various devices but have glanced at it here, as you said and posted the format is the same simple copy and paste, no screenshots, no flashing instructions no mention of a bug list if there are any.. so maybe the format may need a tweak or two for us slow xz1 and xz premium folks..and if the lack of info in the op causes a few questions to be asked ..then feel to take you ball and go home..
Click to expand...
Click to collapse
Yah I believe lack of info cause some issues. Like if you came from lineage 16 dsds and have the dsds twrp you can't flash this rom. You need to flash the single sim xz1twrp in the lineage16 thread.
pattriccio said:
Yah I believe lack of info cause some issues. Like if you came from lineage 16 dsds and have the dsds twrp you can't flash this rom. You need to flash the single sim xz1twrp in the lineage16 thread.
Click to expand...
Click to collapse
It's not only this one, but in my case I run a stock rom with existenz patch, with one twrp, then to flash beetle84 ( excuse the spelling) add on, I need the aroma trwp version , then to flash j4nn's kernel you need to flash the DS twrp.. but that's another story.. but the only.point I was trying to get across lack of info in the op , your going to get questions...
Myself5 said:
Your post is an in depth explanation of what is wrong with the Sony community. The OP design is the exact same used on ALL CarbonROM XDA Threads, yet the Xperia XZ Premium and XZ1 community are the ONLY people complaining about it. Surely this is a me issue. Perfectly outlined by your assumption that the builds I released were Oreo. Heck, I even attached a picture of the XZ1 and XZP running those VERY builds I linked that said Android 9. I'm not obliged to do anything. I release those builds because it's a fun hobby. Constantly spoon feeding people because they refuse to do their research is not on that list.
There is no such thing as "which gapps to use". Ever. On any device. Go to any stupid GApps website and download the GApps that match YOUR taste. If you need advice on arm vs arm64 and which android version then you're wrong in this forum.
less than 24 hours into the thread creation and I consider closing it again. Thats gotta be a new high.
Check out https://www.xda-developers.com/how-to-take-logs-in-android/.
Though, you could've found that with a Google search. First link when looking for "xda get logs".
Also can you check which device name is shown in Settings? G8341 or G8342?
Click to expand...
Click to collapse
Please don't close it
lilbrat said:
Pictures.. where as there aren't any posted on the but the logo for the rom on the lab app.. I personally haven't look at the rom on other various devices but have glanced at it here, as you said and posted the format is the same simple copy and paste, no screenshots, no flashing instructions no mention of a bug list if there are any.. so maybe the format may need a tweak or two for us slow xz1 and xz premium folks..and if the lack of info in the op causes a few questions to be asked ..then feel to take you ball and go home..
Click to expand...
Click to collapse
Screenshots can be found on our website on this thing called Gallery. Cool huh?
Theres no buglist because theres no need for any. Our official builds have to pass fairly strong criteria before going official and are tested on the devices before going official. I never announced or claimed the Dual SIM variant would be supported.
As for flash instructions I expect users to be capable enough to use Google and do their research. If they are unable to do that, they shouldn't bother messing with Custom ROMs to begin with.
Literally the first Google result for the query "flash Android ROM" is a detailed guide from XDA which would work just fine.
However, thanks for pointing out yet again how fitting your username is. Seeing you're not interested in using Carbon nor are using it right now I'd kindly ask you to refrain from further posts in this thread.
Thanks.
pattriccio said:
Yah I believe lack of info cause some issues. Like if you came from lineage 16 dsds and have the dsds twrp you can't flash this rom. You need to flash the single sim xz1twrp in the lineage16 thread.
Click to expand...
Click to collapse
Here's a random thought. What if a zip that doesn't install on the Dual SIM TWRP with an error saying its for the Single SIM variant, is actually for the Single SIM variant?
My offer still stands. I'm willing to look into Dual SIM support of someone with a Dual SIM device volunteers testing. Until then and from now on I'm either going to ignore each and every complaint about the Dual SIM support or value it with some kind of sarcastic reply depending on how I feel.
I spent countless hours working on these devices in my own free time using my own Money to pay for PC Hardware and other expenses. Yet, instead of some kind of appreciation, even if its just the simplest "thank you" post, I get people like @lilbrat *****ing at me for not spoon-feeding people with results from Google queries or worse. Too sad the Sony community hasn't changed in the last two years.
Thankfully, due to multiple reasons, the XZ1 and XZP were my last Sony phones ever, with the community being one of the biggest factors. Shame how the old Sony community turned into this.
I knew I should've left the phones in that dusty corner on my desk instead of putting any time into it.
Thanks so much for your efforts and remember you are here in xda to develop and help each other and others not to debate or criticize or show muscles. thanks again and i think carbon rom is one if the best so don't close the thread and keep up the good work
Myself5 said:
Screenshots can be found on our website on this thing called Gallery. Cool huh?
Theres no buglist because theres no need for any. Our official builds have to pass fairly strong criteria before going official and are tested on the devices before going official. I never announced or claimed the Dual SIM variant would be supported.
As for flash instructions I expect users to be capable enough to use Google and do their research. If they are unable to do that, they shouldn't bother messing with Custom ROMs to begin with.
Literally the first Google result for the query "flash Android ROM" is a detailed guide from XDA which would work just fine.
However, thanks for pointing out yet again how fitting your username is. Seeing you're not interested in using Carbon nor are using it right now I'd kindly ask you to refrain from further posts in this thread.
Thanks.
Here's a random thought. What if a zip that doesn't install on the Dual SIM TWRP with an error saying its for the Single SIM variant, is actually for the Single SIM variant?
My offer still stands. I'm willing to look into Dual SIM support of someone with a Dual SIM device volunteers testing. Until then and from now on I'm either going to ignore each and every complaint about the Dual SIM support or value it with some kind of sarcastic reply depending on how I feel.
I spent countless hours working on these devices in my own free time using my own Money to pay for PC Hardware and other expenses. Yet, instead of some kind of appreciation, even if its just the simplest "thank you" post, I get people like @lilbrat *****ing at me for not spoon-feeding people with results from Google queries or worse. Too sad the Sony community hasn't changed in the last two years.
Thankfully, due to multiple reasons, the XZ1 and XZP were my last Sony phones ever, with the community being one of the biggest factors. Shame how the old Sony community turned into this.
I knew I should've left the phones in that dusty corner on my desk instead of putting any time into it.
Click to expand...
Click to collapse
I have a Dual Sim device and i can volunteer to testing ?
Just found a link of a absolutely usable ROM for the N6P - here's the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry!
(Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...)
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually, it offers perfect support...
Suggestion from my side:
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com
Sorry if I did wrong posting this, it's just pure happiness for the community of N6P users!!!
I flashed dirty on RROS 10 with great results! (Edit: flashed clean later on, just to be sure)
My appreciation for this stable 11 build! Let's hope for more good stuff being on the way!
Thanks
Looks great and luv the name Ravioli! Cheers
Sam Nakamura said:
Just found a link of a absolutely usable link for the Android Open Sources illusion Projects's latest build (not my work!) which I couldn't find anywhere else, nor any discussion about it.
Posting this only reflects only my deepest appreciation about this work!
If I was blind to not see the corresponding thread I'm sorry! Then go ahead and please delete this if any concerns arise, just happy to see work on this almost forgotten devices...
AOSiP-11-Ravioli-angler-20210311-1938.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Enjoy!
GAPPS can be easily found for 11 via Google, I found a nice project on XDA actually...
Sorry if I did wrong, it's just pure happiness for the community of N6P users, I flashed dirty on RROS 10 with great results!
My appreciation for this stable 11 build! Thanks
Click to expand...
Click to collapse
Love this ROM, thanks to @voidz777 for building "THE ONLY STABLE ANDROID 11 ROM" for 6p at the moment, looking forward to updates on it.
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Aditya kukreti said:
Rom is good but not 100% stable..it has minor bugs such as hotspot is turning off within 10-15 minutes everytime and also phone is charging very slowly..other than that it's stable
Click to expand...
Click to collapse
I don't use hotspot that much, but for charging issue what i did is i managed to lower down some clock cores and it works just fine without any isse with less heat
New update is up! Thanks @voidz777 for fresh stable update
Works nicely
A few hickups here and there. Did anyone get the smart controls to work?
I am missing the option to add controls, not sure if that is an ASOP thing or something else.
as @Ata Ur Rehman already said, there has been a new update (May 26th), which can be found here:
AOSiP-11-Ravioli-angler-20210526-0638.zip | by voidz-maguro for Nexus 6P
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also here is the .txt file with a message from @voidz777 (or voidz-maguro):
"I have been interested in other hobbies since March and left 6P alone.
In Japan, the rainy season starts in June and I can only work at home.
Probably I will play with angler for a while.
For the time being, I synced to the May source of aosip.
Device modification corresponds to drm (L3).
selinux is parmissive without change. Because it is very time-consuming to make it enforce. It will take a little longer.
Camera fix? I can't. Find a camera app that you can use without problems.
Even with this, I will spend a lot of time trying in my own way.
Is English strange? It's because of Google Translate.
I want to spend more time on other things than spending time translating into English."
Click to expand...
Click to collapse
本当にありがとうございます (Thanks a lot)
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
voidz777 said:
There are admins who make me stupid on the Telegram channel, so I'm not motivated to do anything about angler. Please ask developers other than me that you like to develop angler.
I also gave the device to a friend.
From now on, I'm not involved with angler anymore.
Click to expand...
Click to collapse
I am sorry to hear that. And everybody does what they can ^^
I am only temporarily (hopefully) using angler, and for that your ROM is more than awesome to use.
Thanks again and much success on whatever else you are doing.
Amazing job keeping the Angler alive with this ROM. Been using this for a few weeks now.
Ata Ur Rehman said:
"THE ONLY STABLE ANDROID 11 ROM" for 6p
Click to expand...
Click to collapse
Is this still the case or have more options appeared by now?
Sorry, I haven't been following the scene for a while.
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
tonyfierros said:
I have the problem when I try to flash the ROM , it send the error (Failed to Mount /Vendor (no such device)
Anyone knows how to fix it ???
Click to expand...
Click to collapse
Try flashing vendor image manually before flashing the ROM.
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
raubo said:
Same here. Which vendor image should be flashed?
Could somebody give a step by step advise how to do a clean flash with this ROM, pls?
Thanks.
Click to expand...
Click to collapse
I got it installed. The vendor error message remains but the phone is up and running. And there are no problems but one: The German Fidor bank app is not installed, because the device is said to be not compatible. Usually this message comes up if the phone is rooted. Magisk is not installed. Is the phone with this ROM rooted by itself? Any ideas?
The installation seemed to be OK. But stuck in the boot logo when booting to the system. need help.
SLo
Go to recovery and clear data and reboot.
The camera from Gapp works well, but only one is work.
I try Gcam 8.1 from BSG and the Gcam from Play Store, they work will one photo only.
BTW where did you find this ROM? I can't find any in google.
I tried searching for it and couldn't find it either???