Database Develop

ROM ~ 4.2.2 ~ HALO ~ ||UnofficialCarbon|| ~ WIP

{
"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"
}
Again, Built using a 1GHZ Processor with only 2gb of RAM so even if you don't like the ROM, at least appreciate the time and effort which went into this ROM!​
What is Carbon, you ask?
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.
Click to expand...
Click to collapse
What's working:
Everything which isn't in 'Not Working' section
Click to expand...
Click to collapse
What's not working:
-No Carbon specific bugs as far as i'm aware
---4.2.2 bugs---
IF IVE MISSED SOMETHING LET ME KNOW
- No WiFi
- No Bluetooth
- No ADB
- No Camcorder
- No Native playback
- To get SD working you have to go to developer options, enable then disable debugging and it will reboot with recognized sd card!
- MAKE SURE YOU DO THIS: IT WILL FIX APP INSTALLS
Click to expand...
Click to collapse
SCREENSHOTS (These are from Pico but looks the same on golfu)​
NOTES:
-->Many features might not work if you dont flash gapps. For e.g. quick settings, etc
Click to expand...
Click to collapse
This ROM was source built using my own custom device tree, but failed so i ported it using Nikhils as a base, so i'm not sure whether this counts as port or source build but i'm counting it as a source build :3
DOWNLOADS
Well this ROM has been in unreleased development for a while now and i have been making fixes and implementing those Nikhil has fixed! (This Guys a machine) So that's why we start at build 3 :3
Build #3: My 3rd Build, But your initial release as it still has a lot of bugs!
Gapps: These are Custom Gapps which fix the keyboard fc!
Kernel (NO OC): 100% Credit to Nikhil For this!
Click to expand...
Click to collapse
INSTALLATION
You should know what to be doing by now, if not this shouldn't be the first ROM you flash!
- Clean Wipe
- Flash ROM
- Flash Kernel
- Reboot
- Enable then Disable ADB
- Re-Root
- Enable and Disable and check SD is recognized
- Enjoy
Click to expand...
Click to collapse
Thanks:
7Alvi: Gave me the raw paste data for the layout of this thread! (He is from Pico :3)
Nikhil: supplying and Fixing CM10.1! Also Kernel sources (Even though i did TARGET_PREBUILT := )
However it can all be found here: https://github.com/nikhil16242
Heres the ROM source: CarbonDev
Thanks for reading guys!

[Mod Edit: Foul Language], you crazy bro, gooood job :good:

Sweeeet homie that is some nice going I'm loving it even though barely anything works I'm flashing this baby.
You're a [Mod Edit: Foul Language] machine
Sent from my HTC Desire C using xda premium

Shad0wPanda said:
Sweeeet homie that is some nice going I'm loving it even though barely anything works I'm flashing this baby.
You're a [Mod Edit: Foul Language] machine
Sent from my HTC Desire C using xda premium
Click to expand...
Click to collapse
Cheers bro, i'm 16 on the 1st July

Alright guys, I just had to clean this thread up already do to some foul language. Just so everyone knows, foul language is against the XDA forum rules. I don't want to see this kind of posting behavior again.
Stay on topic, and watch your language
Thread re-opened.

wildstang83 said:
Alright guys, I just had to clean this thread up already do to some foul language. Just so everyone knows, foul language is against the XDA forum rules. I don't want to see this kind of posting behavior again.
Stay on topic, and watch your language
Thread re-opened.
Click to expand...
Click to collapse
Thankyou Moderator!

penguin449 said:
Thankyou Moderator!
Click to expand...
Click to collapse
The installation instructions say, "Re-Root"

aashay960 said:
The installation instructions say, "Re-Root"
Click to expand...
Click to collapse
yeah, whats so hard to understand about that? the Rom isnt pre-rooted, so you have to re-root your phone or use it without root

penguin449 said:
yeah, whats so hard to understand about that? the Rom isnt pre-rooted, so you have to re-root your phone or use it without root
Click to expand...
Click to collapse
OH i thought it was a mistake So you mean, just install superSU? Or root using superboot (from this thread )

aashay960 said:
OH i thought it was a mistake So you mean, just install superSU? Or root using superboot (from this thread )
Click to expand...
Click to collapse
Root using Superboot but when it gets to " Starting apps " do a bat pull and restart then it will be fine

penguin449 said:
Root using Superboot but when it gets to " Starting apps " do a bat pull and restart then it will be fine
Click to expand...
Click to collapse
I just use the flashable root from the hasoon toolkit....I guess that's fine?
Sent from my NXT Brick

ExonakiDev said:
I just use the flashable root from the hasoon toolkit....I guess that's fine?
Sent from my NXT Brick
Click to expand...
Click to collapse
Yeah that's fine, it's all preference

penguin449 said:
Cheers bro, i'm 16 on the 1st July
Click to expand...
Click to collapse
so wat ever u gave in the not working list isnt true???

adityaiyerq said:
so wat ever u gave in the not working list isnt true???
Click to expand...
Click to collapse
If it's in the " Not Working " section then you gussed it! it isnt working but i'm working on some fixes, but failing majorly

penguin449 said:
Cheers bro, i'm 16 on the 1st July
Click to expand...
Click to collapse
Are you kidding? I turn 16 1st of July!!!!!!!!!!!!!!! Dude, we are EXACTLY the same age!!!
Sent from my HTC Desire C using xda app-developers app

uchihasparky said:
Are you kidding? I turn 16 1st of July!!!!!!!!!!!!!!! Dude, we are EXACTLY the same age!!!
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
That's OT but yeah i'm 16 today, which means i can only gain more experience in building and i'm working to bring you guys some kick ass ROMs, 4.1.2 and 4.2.2! Just wait it out! ( Restored Topic! )

supersu
hey guys, i steel have a problem with superuser i have done everything thats says about the reroot, i have root acces on the terminal emulator when i'm typing (su) but i can't get the root acces on the file manager, so i can't fix the "app not instaled" eny help please

Thread closed because the OP has been banned for continued failure to follow the rules of XDA.

[ROM][WIP] osprey AOSP 6.0.x

Hello all,
I'm trying to port an AOSP ROM to the osprey, I already made some steps but would need some help from much better skilled devs.
Here is the code: https://github.com/motogaosp
The manifest: https://github.com/motogaosp/android_manifest
At the moment the ROM starts without big problems but there are some errors while booting up.
Feel free to participate, fork the code, send pull request or whatever you think can help the project, the goal would be to have a clean AOSP ROM for our osprey.
Working:
WiFi
Bluetooth
Back camera
Front Camera
Touchscreen
Sensors:
Accelerometer
Light
Magnetic field
Orientation
Proximity
NOT working:
Sound
RIL
Mobile data (LTE/3G)
GPS
XDA:DevDB Information
MotoG 3 AOSP, ROM for the Moto G 2015
Contributors
udK
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-03-15
Last Updated 2016-03-15

What's the diff btw CAF and AOSP?? btw thank u for yo efforts!

I hope to see link soon.

Forever Alone said:
What's the diff btw CAF and AOSP?? btw thank u for yo efforts!
Click to expand...
Click to collapse
@Forever Alone: http://forum.xda-developers.com/showpost.php?p=63433600&postcount=2

is it 100% aosp without any cm patches?

Yes, from CM I use (for the moment) the build scripts part as it has all the stuff needed to include qcom repositories but this does not affect on Android itself.

udK said:
Yes, from CM I use (for the moment) the build scripts part as it has all the stuff needed to include qcom repositories but this does not affect on Android itself.
Click to expand...
Click to collapse
Any idea when will we have download link?
As you as a moderator knows already xda doesn't accept place holder.

Yousvel said:
Any idea when will we have download link?
As you as a moderator knows already xda doesn't accept place holder.
Click to expand...
Click to collapse
I don't think it's particularly considered a place holder when the source code and manifest has been posted in search for assistance to get to a user capable produce. Works In Progress are allowed and maybe the current developer finds it moot to release a link publicly that's just going to flood his thread with endless.... ("WTF, Why this no work? U said unfished product, but it have problems, I no approve") ..... yeah stuff like that.

..and the most stupid question is:
Yousvel said:
Any idea when will we have download link?
Click to expand...
Click to collapse
If you can help the project ok, otherwise go away from this thread please.
Thanks.

udK said:
..and the most stupid question is:
If you can help the project ok, otherwise go away from this thread please.
Thanks.
Click to expand...
Click to collapse
No problem brother. And thanks for answering. It's was a real pleasure to know of this project. Good luck!

Count me in, this is essentially what I've been working on with my build.
With the addition of all RRO commits but for now I'd like clean as well, I'll start forking this weekend. Thanks for this! Big help having other devs bring aosp for our device.

man , count me in ,im happy to help . I can configure the aroma installer for it ?

christopherrrg said:
Count me in, this is essentially what I've been working on with my build.
With the addition of all RRO commits but for now I'd like clean as well, I'll start forking this weekend. Thanks for this! Big help having other devs bring aosp for our device.
Click to expand...
Click to collapse
Awesome thanks!
therealduff1 said:
man , count me in ,im happy to help . I can configure the aroma installer for it ?
Click to expand...
Click to collapse
Honestly I don't think that Aroma installer would be so useful on AOSP ROM btw, feel free to work on it.

If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.

@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
{
"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"
}

l3ones said:
If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.
Click to expand...
Click to collapse
yeah i would happily join you on learning how to compile build etc

udK said:
@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
Click to expand...
Click to collapse
Good to see

therealduff1 said:
yeah i would happily join you on learning how to compile build etc
Click to expand...
Click to collapse
l3ones said:
If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.
Click to expand...
Click to collapse
Here's a push to start guys, take your time to read read read. Once you're done these just rifle ROM build questions at Google and check out other devices for an idea on how the structure works.
( Senior member but am still extremely new at building, no public builds just small CM stuff but these guides helped me put a lot together. )
http://forum.xda-developers.com/showthread.php?t=2364970
https://source.android.com/source/initializing.html
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
---------- Post added at 01:23 PM ---------- Previous post was at 01:19 PM ----------
udK said:
@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
Click to expand...
Click to collapse
Is this using msm8916 kernel source?
(I can see the screen, just unsure if custom built.)

christopherrrg said:
Is this using msm8916 kernel source?
(I can see the screen, just unsure if custom built.)
Click to expand...
Click to collapse
I started from Motorola sources (https://github.com/MotorolaMobilityLLC/kernel-msm/tree/marshmallow-6.0.0-release-osprey) and then picked some patches from https://github.com/moto8916/android_kernel_motorola_msm8916 to get the kernel booting.

Dude, you are making really quick progress. Yesterday all I saw working was the touchscreen & cameras, now we have WiFi and Bluetooth up and running? At this rate we may have a fully working AOSP ROM in no time, thanks to you!

[7.x.x][WEEKLIES] CarbonROM | cr-5.1 [sailfish]

{
"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

[RECOVERY][3.2.3][fajita][UNOFFICIAL] TWRP RECOVERY FOR ONEPLUS 6T [WIP]

{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
NOTE : THIS IS A WORK IN PROGRESS PROJECT, PROCEED AT YOUR OWN RISK.
Click to expand...
Click to collapse
Features:
Decryption working
Removed TWRP App
Adjusted clock position
Custom dark theme
Installation
Download recovery.img and twrp-installer-fajita-3.2.3-*.zip
Copy twrp-installer-fajita-3.2.3-*.zip to internal storage
Reboot to fastboot
From fastboot: fastboot boot recovery.img
From recovery: install twrp-installer-fajita-3.2.3-*.zip
Or: adb sideload twrp-installer-fajita-3.2.3-*.zip
If you are on custom recovery, simply install twrp-installer-fajita-3.2.3-*.zip (you don't have to download recovery.img)
Flash Magisk after installing recovery
Download
Builds: androidfilehost
Source code:
https://github.com/HelllGuest/twrp-fajita
Credits:
 @eng.stk
 @xls654
 @squid2
 @micky387
 @mauronofrio
@Dees_Troy
Known issues
Restoring backup (Not tested)

Changelog
01-Dec-2018:
Initial build.

Confused...there 2 twrp's now?

We have a working unofficial TWRP for the 6T.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

Wow, really? This guy posts to help and this is what he gets? While we do have a working twrp, the other thread is filled with people with issues, and random twrps being posted, so maybe his works better. Thank you sir for your work

Is It possible a recovery that support multirom?
Sent from my [device_name] using XDA-Developers Legacy app

suzook said:
Confused...there 2 twrp's now?
Click to expand...
Click to collapse
biohaz55 said:
We have a working unofficial TWRP for the 6T.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
First time seeing multiple twrp for a single device ?
If you're confused, then try both.

We dont need this.

Please, all projects are good, thanks @AnoopKumar

What are the benefit(s) of this particular recovery compared to the one(s) in the other thread? From a first glance they look basically the same.

sssarg said:
What are the benefit(s) of this particular recovery compared to the one(s) in the other thread? From a first glance they look basically the same.
Click to expand...
Click to collapse
Please take a look at the source. Maybe same, my method is different.

SpectraFun said:
We dont need this.
Click to expand...
Click to collapse
Who are you representing? Who is "we". Who put you in that position? If you personally don't need this why are you here?

sssarg said:
What's the benefit of this particular recovery compared to the one(s) in the other thread?
Click to expand...
Click to collapse
@AnoopKumar
This question is precisely why we don't normally have different TWRP threads. TWRP is arguably the MOST important part of helping users easily modify their device once they've unlocked their bootloader. Instead of having two threads with unknown differences, for the sake of the members, it would be better to create a slack or telegram group where all TWRP devs can combine their work into one tree UNTIL we have an officially maintained version. After that you can have all the versions you want because there will be a stable branch to point members to if they have a problem.
I absolutely love development and I am not in any way discouraging you from continuing your work on TWRP. However, I do ask you to consider that there will be extra work on all our parts to help new members because we have to ask what recovery they use and know if there are bugs for two different unofficial versions.
AnoopKumar said:
Please take a look at the source. Maybe same, my method is different.
Click to expand...
Click to collapse
New members aren't going to know how to check the source which is why devs normally put changelogs in the post to prevent this. They are going to see your TWRP picture at the top and think this is basically an official team release of TWRP.

AlkaliV2 said:
@AnoopKumar
This question is precisely why we don't normally have different TWRP threads. TWRP is arguably the MOST important part of helping users easily modify their device once they've unlocked their bootloader. Instead of having two threads with unknown differences, for the sake of the members, it would be better to create a slack or telegram group where all TWRP devs can combine their work into one tree UNTIL we have an officially maintained version. After that you can have all the versions you want because there will be a stable branch to point members to if they have a problem.
I absolutely love development and I am not in any way discouraging you from continuing your work on TWRP. However, I do ask you to consider that there will be extra work on all our parts to help new members because we have to ask what recovery they use and know if there are bugs for two different unofficial versions.
Click to expand...
Click to collapse
I clearly mentioned features and known issues.

This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.

I hope soon some of recoveries will have OTA support for stock rom. Redwolf or orangefox have this function, but this recoveries are for miui. This is my feature request for future if general functions will be working good. Regards
From: ONEPLUS A6013
Using: Tapatalk 6.3.2 BWS

Daviteusz said:
I hope soon some of recoveries will have OTA support for stock rom. Redwolf or orangefox have this function, but this recoveries are for miui. This is my feature request for future if general functions will be working good. Regards
From: ONEPLUS A6013
Using: Tapatalk 6.3.2 BWS
Click to expand...
Click to collapse
I will look into it.

AnoopKumar said:
This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.
Click to expand...
Click to collapse
Hold on now EVERYONE... I believe we should not take this to such a personal level. Anoop you KNOW that provide whatever differences you made, improvements and whatnot that people will be interested in what you work on, otherwise you would not necessitate it's publicity. So I'm asking as just a simple Non-dev Android enthusiast, if you will please not stoop to the level of where ignorant retorts are coming from. I know it seems unappreciative, sometimes it is, but mostly I think it comes from lack of understanding of the possible benefits of the work you provided. So being yourself, from a level of a particular skill, I believe you know what to overlook and how to directly cut to the primary topic of people's inquiries to dispel further squabbling. If people still refuse to understand, those are things to overlook and let another XDA member cope with. No reason to exhaust yourself with repetitive pessimism. Just remember most is because people don't genuinely understand what you understand.
Oh Furthermore Thank you Sir

Exactly what Causical just said ^
Thank you for all your work.
AnoopKumar I appreciate all that you are doing

AnoopKumar said:
This is really disappointing, you guys can't understand what changes i made. You guys thinking i simply cloned the repo and simply compiled. I was trying to improve it. First change i made was hex editing the prebuilt adbd so that i can exclude /system_root/system/bin/crash_dump64 because it is a duplicate file. I changed the default theme, adjusted clock position from another guys commit and some minor changes. I compiled many times for checking each and every changes. It took my time and energy. My apologies.
Click to expand...
Click to collapse
Precisely. Which is why I asked my previous question regarding the differences of this recovery compared to the ones we've seen up until now.
Many, or most, of us don't do android development, and deciphering the source code and commits to pick out how a recovery is different from another when they seem to come from the same places (yours is forked from the initial decrypt success, which makes people think it's that one with a few changes) is very difficult.
Out of the changes you mentioned in that quote, I could figure out you had changed the clock position, and had another theme available, because you had stated that already in your OP. The rest? No idea.
As @AlkaliV2 said, in this early stage it's likely going to cause more confusion than not with several unofficial TWRP recoveries with independent development, instead of the devs cooperating to come up with a single and stable unofficial recovery until a time we have a good maintained baseline.
I doubt anyone wants you to stop development, but people are obviously confused with a second thread popping up.

[ROM][10] Pixel Experience (PE) [fajita]

[ROM][10.0][DEVICE] Pixel Experience [AOSP][2020/09/30]
{
"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"
}
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera (non-stock need to be installed)
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Need to install a google camera app
Do NOT FLASH GAPPS, they are already included.
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
• Android OS version: 10.0.0_r31
• Security patch level: September 2020
• Build author/Device Maintainer: giminji
• Device Source code: https://github.com/PixelExperience-Devices
• Source code: https://github.com/PixelExperience
• Kernel is from https://github.com/AOSiP-Devices/kernel_oneplus_sdm845
• ROM Developer: jhenrique09
Here is a build I did last week. I am using Pixel Experience I built two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
I cannot wait for October security!
I did add in daydream support.
Now, let's see what I did wrong on the posting style!
Onedrive link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l Just until I can get onto android file host.
Install directions: https://wiki.pixelexperience.org/devices/fajita/install/
Summary of install:
1) Install adb and fastboot drivers
a) enable usb debugging
c) adb reboot bootloader
d) fastboot devices
Just to check you can see the fastboot
e) fastboot oem unlock <------ erases all your data! proceed past this point at your own peril!
2) adb reboot bootloader
3) fastboot boot recovery recovery.img (from twrp I use)
4) for me, now it was just install zip from either adb sideload or adb push
5) reboot phone and installed.
The link before all of this has more details.

Giminji said:
Here is a build I did last week. I am using Pixel Experience I build two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
Click to expand...
Click to collapse
Aha, taking our first steps into compiling and releasing.. Exciting stuff! And a grand learning experience. Let's start by making the download link... Well, downloadable. You've currently shared a link to an unshared file in your drive. You need to create a share link first. Always test your download links in por.. Eh, incognito mode before releasing. And look into other hosting options that provide more stability such as AFH.
Next on the priority list is adding a link to the kernel source. This is very important for us not to get into any legal trouble as we must comply with GPLv2 in that respect.
Take a look at the other ROM threads to get more familiar with the desired structure. Mostly the bottom parts are important. Like giving credit to those that made your release possible and version information.
Also, you may want to explain what this is (see other PE threads), how people must flash it and notify of any known issues/limitations, if any. Add a disclaimer perhaps, you just never know.
We'll get there together because we're an awesome community like that

Timmmmaaahh said:
Aha, taking our first steps into compiling and releasing.. Exciting stuff! And a grand learning experience. Let's start by making the download link... Well, downloadable. You've currently shared a link to an unshared file in your drive. You need to create a share link first. Always test your download links in por.. Eh, incognito mode before releasing. And look into other hosting options that provide more stability such as AFH.
Next on the priority list is adding a link to the kernel source. This is very important for us not to get into any legal trouble as we must comply with GPLv2 in that respect.
Take a look at the other ROM threads to get more familiar with the desired structure. Mostly the bottom parts are important. Like giving credit to those that made your release possible and version information.
Also, you may want to explain what this is (see other PE threads), how people must flash it and notify of any known issues/limitations, if any. Add a disclaimer perhaps, you just never know.
We'll get there together because we're an awesome community like that
Click to expand...
Click to collapse
Well, that WAS a fail on my part. Try this out please! I usually use onedrive, wanted to use google this time around.
{Mod edit}

Giminji said:
Here is a build I did last week. I am using Pixel Experience I build two weeks ago. Not sure what to put here, but you can try if you like!
September 2020 security patch should be in here. That's the only reason I do ROMs, is for the security updates.
{Mod edit}
Now, let's see what I did wrong on the posting style!
Click to expand...
Click to collapse
You been using this rom? I'm so excited to try this out, I really miss PE on my 6T
Sent from my OnePlus6T using XDA Labs

champagne66601 said:
You been using this rom? I'm so excited to try this out, I really miss PE on my 6T
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Well, I've been using the non-plus. Got my trees swapped, I also added in daydream support. I will be flashing the October security one when I find it's been promulgated.

Giminji said:
Well, I've been using the non-plus. Got my trees swapped, I also added in daydream support. I will be flashing the October security one when I find it's been promulgated.
Click to expand...
Click to collapse
I was using the last official build but I just flashed your build and everything it's working flawlessly, thank you! You did an amazing work
Sent from my OnePlus6T using XDA Labs

Thanks OP for bringing PE to fajita. Keep it up!

I can't seem to download. Appears its been removed from One Drive cloud?
HUGE thanks op for PE for the 6t!! :good
Edit added: Downloading now from the Google Drive link below the op.

Giminji said:
I have build fajita Pixel Experience unofficial, I want to make post, is there a way to do so in the roms section, but have it only for my eyes for right now? So that I can edit, view and then post when ready? I am planning to run the Pixel Experience on my device (with Daydream support) and also make the Pixel Experience ten-plus.
Also, is it okay just to gdrive the downloads?
Thanks!
Click to expand...
Click to collapse
Giminji said:
...
Click to expand...
Click to collapse
@Giminji THREAD CLOSED! Placeholder threads (i.e. those without a workable download link) are not accepted. Your currently linked folder on Onedrive is empty. The link has been removed.
Please advise the moderators team (best via the report function) to re-open your thread when ready to provide a functionable download link.

Why is Pixel Experience always the ROM to cause forum problems? lol

Causical said:
Why is Pixel Experience always the ROM to cause forum problems? lol
Click to expand...
Click to collapse
I've seen PE rom on a few past devices I've owned and it really does seem like something happens. The dev either disappears or something else. lol.
Hoping our Pixel Experience guy will stay around and just keep everything cool with the mod(s). ??
I used this build from the ops second post with the Drive link the other day and it was solid. I always return to Corvus nowadays. PE is a beast though! I've had PE+ on my other device for 6+ months. It always makes me wish I had a Pixel again which will eventually happen once I slowly gather enough funds for one thanks to covid-19. ?

fixed link!
flash713 said:
I've seen PE rom on a few past devices I've owned and it really does seem like something happens. The dev either disappears or something else. lol.
Hoping our Pixel Experience guy will stay around and just keep everything cool with the mod(s).
I used this build from the ops second post with the Drive link the other day and it was solid. I always return to Corvus nowadays. PE is a beast though! I've had PE+ on my other device for 6+ months. It always makes me wish I had a Pixel again which will eventually happen once I slowly gather enough funds for one thanks to covid-19. ?
Click to expand...
Click to collapse
It has been unlocked the thread again, try this link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l
I will post an android file host one once they approve me to do so. Long story short, my gdrive link was giving out too much info. I didn't like that, I shut down and used windows explorer letting it sync files, it did not sync, someone pointed it out to a mod, got put on hold and now thread is back!

Giminji said:
It has been unlocked the thread again, try this link: https://1drv.ms/u/s!AimL8kQOGqb5hbMjQ8DwozBF61xksA?e=UDBR2l
I will post an android file host one once they approve me to do so. Long story short, my gdrive link was giving out too much info. I didn't like that, I shut down and used windows explorer letting it sync files, it did not sync, someone pointed it out to a mod, got put on hold and now thread is back!
Click to expand...
Click to collapse
You were always good in my book bro. Thank you for sharing your work!! :good:
Same reason I don't leave Drive links. You're smart.

Hi? Can you fix SafetyNET? I like this rom, but safetynet...

SevralT said:
Hi? Can you fix SafetyNET? I like this rom, but safetynet...
Click to expand...
Click to collapse
You can fix that with the MagiskHide module
Sent from my OnePlus6T using XDA Labs

Will you become an official developer for 6T ??

Is there any instructions to install this rom?

Does any telegram group?

DimaYarosh1289 said:
Is there any instructions to install this rom?
Click to expand...
Click to collapse
Sadly, I am not very well versed yet. Best I can do.
1) Unlock bootloader
2) boot into fastboot
3) do the "fastboot boot RECOVERIMAGENAME.img
-- I usually do twrp
4) install it.
Maybe someone can help me flesh that out some, this is my first rom I made.

SevralT said:
Will you become an official developer for 6T ??
Click to expand...
Click to collapse
I am trying, but the rules to become developer for 6t on the PE website is confusing. In a few weeks when I make October 2020 with security up to date, I may look again and see if I can fulfull requirements.