[8.1.x][OFFICIAL PREVIEW] CarbonROM | cr-6.1 [berkeley] - Honor View 10 ROMs, Kernels, Recoveries, & Other D

{
"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.
Pre-Disclaimer:
THIS IS AN DEV PREVIEW BUILD. The intent is to showcase what is coming up soon.
Please keep any problems with those builds in this thread, we don't accept any bugreports for preview builds anywhere else.
Also, we know this works on other treble devices. Please be aware that we can only provide limited support for those.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Notice:
This build includes GApps for now.
Before you flash, make sure you're on the latest 8.x stock builds, then flash the system.img in fastboot.
Download Mirror
Changelog
GitHub
Gerrit
Device and Kernel sources
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 Honor View 10
Contributors
Myself5, CarbonROM, berkeley-dev Team
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-02-22
Last Updated 2018-04-15

Many thanks for bring us this ROM
Enviado desde mi BKL-L09 mediante Tapatalk

Great. Now development has gained speed. Love to see these roms for our beloved v10

Nice job in the release Chris!

Sweet. Nice job

Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?

Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?

shihabsoft said:
Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?
Click to expand...
Click to collapse
Not yet, but we're working on it.
sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
I guess you could. I honestly didn't try.

Myself5 said:
Not yet, but we're working on it.
I guess you could. I honestly didn't try.
Click to expand...
Click to collapse
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device

sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
U can try flashing like a img in install menu. But idk if it works [emoji17]
Enviado desde mi BKL-L09 mediante Tapatalk

What its caffeine?
When you implement fingerprint gestures?

VivekBhagat said:
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device
Click to expand...
Click to collapse
Most vendors define those gestures as keyevents. Huawei obviously uses an API to perform them (and not native Linux keyevents support). Anyways, you have a plethora of third party apps that can do this for you.

Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.

BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
Interceptor777 said:
Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.
Click to expand...
Click to collapse
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you

BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Fingerprint gestures should be in the next build

download link not working...

ink718 said:
download link not working...
Click to expand...
Click to collapse
It's working. Just downloaded.

Myself5 said:
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you
Click to expand...
Click to collapse
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)

Interceptor777 said:
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)
Click to expand...
Click to collapse
I never said it can't be disabled
As a slight OT: its not mandatory to fully disable AVB on ROMs that are designed for taimen. taimen ROMs ship vbmeta images, that contain the AVB signatures. Due to the design its necessary to disable AVB for /vendor, which is done in the kernel by removing the AVB mount flag in the dtb. Although we're currently looking into properly generating the vendor avb signatures too.
Nonetheless, flashable GApps are likely going to cross those plans and will require to disable AVB on system. Therefore, I'd be happy if you could share that AVB disabler zip me (or release it to the public) so that @frap129 and me can do some testing with seperate GApps.
Now on to your question. I just spent an hour trying to gather some facts for the following statement:
Treble is not supposed to give you "one ROM for all devices", nor will it ever be able to provide just that.
Trebles requirement is that you can use "stock AOSP" on the device. Yes. HOWEVER: That doesn't mean it has to the be same single AOSP image for every device. Treble still requires configurations on that System image.
The system images VNDK is configured to work with an 8.0 treble vendor. That would mean you need to use an 8.0 vendor on your Pixel too.
The compatibility matrix and the manifest.xml on system specify what HAL treble has to expect/load from /vendor. Those likely differ.
There will always be some small overlay differences, features that one device supports which the other doesn't or configs that differ. Auto-brightness steps would be a good example for that.
It is true, that this ROM works on multiple devices, yes. So far, those are pretty much all very similiar in terms of HALs to load and hardware. There is barely any difference between the View 10, Mate 10, Mate 10 Pro and others. Things that are different are handled in the kernel (like the Display Technology) and don't affect HALs.
TL;DR + My personal opinion: Whereas treble ROMs might boot (assuming you match all those requirements) a "common ROM for all devices" (which I am starting to think is what everyone expects from treble) is not what you want to use, nor what treble has been designed for.

A new build (systemCarbon_20180303.img) has been uploaded.
It includes support for the US Model, and Fingerprint Gestures. To enable them, go to Settings -> CarbonFibers -> Buttons and tick enable navbar. That will disable the navbar and automatically enable the FPC gestures.
Additionally some new features got merged to the codebase. Happy flashing

Related

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who's back? We're back.
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub and at CarbonROM Gerrit
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
We only support Dynamic GApps, reports on force closes with any other packages will be ignored.
Downloads:
Personal/Test Builds
Official Builds
Dynamic Gapps
CarbonROM's GitHub
CarbonROM 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 for the OnePlus One, ROM for the OnePlus One
Contributors
darjwx, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Created 2017-04-08
Last Updated 2017-05-30
Reserved
Feel free to post any bug you find on a proper way:
1. Build you are running
2. Mods you are using: music mods, magisk, whatever.
3. How to reproduce it.
4. Logcat, ksmeg... if applicable.
I would like this thread to be an example of a development thread so please:
1. Be respectful with each other.
2.READ a couple of times the OP before posting. If there is anything that is not in the op and should be there just let me know.
3. Search before posting, maybe your question is already answered.
4. Features request are allowed, but it doesn't mean I will fulfill all of them. And they are not they reason behind this thread.
That's all for now. Enjoy CarbonRom
Huge thanks to @Myself5 and @kwoktopus for the help, and to the whole CarbonRom team in general.
Also to @Setting.Out for being an awesome tester.
Known bugs:
1. Panorama force closes on default camera.
2. Search inbuilt in settings sometimes crash.
3. Automatic scheduled night light does not work.
Use the customised schedule option for now.
Please report any bug you find on a proper way.
Screnshots:
First
I have been building this for a while now, but I didn't make a xda thread so here it is.
Please READ the op and the reserved post.
darjwx said:
I have been building this for a while now, but I didn't make a xda thread so here it is.
Please READ the op and the reserved post.
Click to expand...
Click to collapse
About time.. Lol
Good job, I'll try this soon..
awesome, carbon is here
Thanks a lot. Only 2 questions.
Support substratum?
And are rooted or need to flash any zip for it.?
Again. Thanks
Enviado desde mi A0001 mediante Tapatalk
vpimentel said:
Thanks a lot. Only 2 questions.
Support substratum?
And are rooted or need to flash any zip for it.?
Again. Thanks
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
Substratum is supported. (Root and rootless mode)
If you want root you have to flash it separately.
Am i the only one getting stuck at the "Format system" part on the installation procedure of the rom?
I tried to install it two times with different recoveries (latest unofficial twrp tugapower and another one which i don't remember the name) and it happens the same problem, however with other roms this doesn't happen.
Maybe there is something wrong with the updater-script or i had a bad download, can anyone confirm? Anyway i'm going to see if a recovery log of the event has been stored, because i had to force a reboot.
mustang_ssc said:
Am i the only one getting stuck at the "Format system" part on the installation procedure of the rom?
I tried to install it two times with different recoveries (latest unofficial twrp tugapower and another one which i don't remember the name) and it happens the same problem, however with other roms this doesn't happen.
Maybe there is something wrong with the updater-script or i had a bad download, can anyone confirm? Anyway i'm going to see if a recovery log of the event has been stored, because i had to force a reboot.
Click to expand...
Click to collapse
I forget to post it. It takes quite a lot to get flashed. I have been investigating it but i could not found the problem. I will continue looking though.
Well, I just installed and configured the ROM. And I come to contribute what in my point of view, would come well to implement if possible
1 can choose single-double actions-keeping the touch of the physical buttons. In addition to being able to remove the illumination of said buttons.
2 you can apply the blur / blur effect to the notifications panel
3 at least two levels of screen size settings.
And for the moment is what made in lack of other roms ..... anything I fell in mind the comment here
Edit: 4 possibility to choose how many columns are desired in the Settings
Enviado desde mi A0001 mediante Tapatalk
vpimentel said:
Well, I just installed and configured the ROM. And I come to contribute what in my point of view, would come well to implement if possible
1 can choose single-double actions-keeping the touch of the physical buttons. In addition to being able to remove the illumination of said buttons.
2 you can apply the blur / blur effect to the notifications panel
3 at least two levels of screen size settings.
And for the moment is what made in lack of other roms ..... anything I fell in mind the comment here
Edit: 4 possibility to choose how many columns are desired in the Settings
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
1. You can choose double tap and long press actions. I will look into single press actions.
2. I don't think that will be merged.
3. I will look into it.
4. That's been reviewed on gerrit.
Hello ! Is this ROM contains :
- 3 state location in status bar ;
- Force volume keys to control media stream ;
- mute intellegent (flip to silent) ?
These options are very important for me. Thanks !
darjwx said:
I forget to post it. It takes quite a lot to get flashed. I have been investigating it but i could not found the problem. I will continue looking though.
Click to expand...
Click to collapse
Ok, just to let know everyone: for me it took 9 minutes and 30 seconds to be completed the instalation.
Here you have a recovery log of the installation process in case it can be helpful: http://pasted.co/059b7a93, although i don't see much relevant information besides this:
Code:
carbonrom.org
Formatting /system
Formatting /system
Creating filesystem with parameters:
on those lines (2294 and 2295) It seems that the "formatting /system" procedure is done twice, but i don't find it logical as it's not repeated on the updater-script of your rom, so maybe it's not a problem.
I saw that the content of the zip of your rom (system directory) is packed like the Kit Kat days, i mean in the system directory of your rom contains everything there but in other roms like Resurrection Remix and all the ones i have saw from Android 5.1 to 7.1 are packed as "system.new.dat" and in the system directory there is only the build-prop, so i think, from my low dev skills, that might be the source of the problem. Also the updater-script of your rom compared for example with the one from Resurrection Remix Nougat differs on the mount and format procedures of Data and System.
Besides that pretty solid rom :good:
I will be traveling for a few days today, so I won't be able to work on this.
Sorry guys, i will look into those things when i came back.
mustang_ssc said:
Ok, just to let know everyone: for me it took 9 minutes and 30 seconds to be completed the instalation.
Here you have a recovery log of the installation process in case it can be helpful: http://pasted.co/059b7a93, although i don't see much relevant information besides this:
on those lines (2294 and 2295) It seems that the "formatting /system" procedure is done twice, but i don't find it logical as it's not repeated on the updater-script of your rom, so maybe it's not a problem.
I saw that the content of the zip of your rom (system directory) is packed like the Kit Kat days, i mean in the system directory of your rom contains everything there but in other roms like Resurrection Remix and all the ones i have saw from Android 5.1 to 7.1 are packed as "system.new.dat" and in the system directory there is only the build-prop, so i think, from my low dev skills, that might be the source of the problem. Also the updater-script of your rom compared for example with the one from Resurrection Remix Nougat differs on the mount and format procedures of Data and System.
Besides that pretty solid rom :good:
Click to expand...
Click to collapse
It's packed like that because the builds are file based. Other ROMs are block based and that's why you see the .New.dat files.
File based builds are normally slower than block based. That partially explain why it takes so much. But 10 minutes is a lot even for a file based build imo.
I returned home yesterday. I have been comparing some carbon stuff with omnirom ones, which is also file based, but no luck yet.
Meanwhile, I have got a test build with oneplus2 doze package added. It seems to be working fine. I'm running it atm.
https://www.androidfilehost.com/?fid=745425885120724125
Testing right now a 7.1.2 build. If all goes well (it should) I will post the link tomorrow .
New 7.1.2 build.
I have been running it since yesterday and I have not found any problem. If you flash this, please use an updated gapps package. Dynamic gapps are not updated yet, so I suggest to use @Setting.Out slim revisted gapps.
https://www.androidfilehost.com/?fid=673368273298947282

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

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Notice:
You must NOT use the SonyOpenDevices ODM image. If you come from a ROM that uses it, please flash the stock OEM image first.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia XZ1
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-04-01
Last Updated 2018-09-07
also for g8342 dual?
Gesendet von meinem G8342 mit Tapatalk
My Dream out right now! ,[emoji7][emoji7]
What exactly is the install process?
Is this a flashable zip?
If so, can we flash it directly over stock or do we have to convert to AOSP via fastboot first?
Does everything work correctly (e.g. the fingerprint scanner)?
N1ghtr08d said:
What exactly is the install process?
Is this a flashable zip?
If so, can we flash it directly over stock or do we have to convert to AOSP via fastboot first?
Does everything work correctly (e.g. the fingerprint scanner)?
Click to expand...
Click to collapse
Hi this is a flashable zip but has the same bugs as all the other roms, it is because it is all bild from tje same sources.
yoyoyed said:
Hi this is a flashable zip but has the same bugs as all the other roms, it is because it is all bild from tje same sources.
Click to expand...
Click to collapse
Can it be flashed on top of stock or do we have to convert to AOSP manually first THEN flash this?
N1ghtr08d said:
What exactly is the install process?
Is this a flashable zip?
If so, can we flash it directly over stock or do we have to convert to AOSP via fastboot first?
Does everything work correctly (e.g. the fingerprint scanner)?
Click to expand...
Click to collapse
As written in the OP, you need to flash the ODM image, then you can flash the zip in TWRP as usual.
FPC is a bit finicky at the moment, but should be better in the next Weekly.
Fingerprint working(sometime can't use fingerprint hardware error, have to reboot)
Smooth on light use, but laggy on hard use such as play game
App launch speed slow on me
Yeah I read the OP but I'm only asking that because flashing the OEM vendor image is something done while flashing all of the AOSP files, not something you do with stock.
I'm assuming that we have to be running AOSP already or switch over to it via fastboot with another ROM and then flash this ROM. Please correct me if I'm wrong because I'm sick of flashing and fixing on this phone, it's a pain.
Also, what is FPC?
N1ghtr08d said:
Yeah I read the OP but I'm only asking that because flashing the OEM vendor image is something done while flashing all of the AOSP files, not something you do with stock.
I'm assuming that we have to be running AOSP already or switch over to it via fastboot with another ROM and then flash this ROM. Please correct me if I'm wrong because I'm sick of flashing and fixing on this phone, it's a pain.
Also, what is FPC?
Click to expand...
Click to collapse
I did full wipe on aosp rom clean all parts and flashed this rom and it workt wichout flashing oem.
On stock i donnot now.
Fpc is finger print i think.
Are there any special mods in this rom? Like any kind of custom settings?
https://drive.google.com/file/d/1_YF3YydBMLa42IXFcsZwbRA9gqlT1Gxh/view?usp=drivesdk
Here benchmark result
N1ghtr08d said:
Are there any special mods in this rom? Like any kind of custom settings?
Click to expand...
Click to collapse
Yes
eggimong said:
Fingerprint working(sometime can't use fingerprint hardware error, have to reboot)
Smooth on light use, but laggy on hard use such as play game
App launch speed slow on me
Click to expand...
Click to collapse
How long have you had this ROM installed and how many times have you had to reboot?
N1ghtr08d said:
How long have you had this ROM installed and how many times have you had to reboot?
Click to expand...
Click to collapse
I used this rom about 12 hours, i had to reboot 2 times
After L speed... i think sony's aosp cpu performance is very poor
We need custom stock rom. Mn.in Project eXistenz, RXSW, Fragment ROM, MoonWalker. But @Myself5 i use your project carbonrom on z3. And he is the best custom rom for this phone. I hope so for xz1 will be be.
Full OMS support ? What is the difference between the atv version and the regular arm64 version of gapps?
kojak1989 said:
Full OMS support ? What is the difference between the atv version and the regular arm64 version of gapps?
Click to expand...
Click to collapse
Do you mean the Android TV gapps?
Hi.....
Write to me exactly the installation steps please, what to clean in recovery, what not ... etc ... what is oem? is SW_binaries_for_Xperia_AOSP_O_MR0_4.4 ??
Im in 12.119 rom, what should I do exactly? if flash zip rom and gapps simple, i have bootloap ... stay with sony logo.. thanks

[GSI][12] LineageOS 19.x GSI (A64B/64B)

{
"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"
}
Background:
This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Click to expand...
Click to collapse
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Must-read:
You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST and identify/report issues there, before moving onto other GSIs that are based on his work, including this one.
If you do find bugs on this GSI and want to report, then you MUST try reproducing on AOSP, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all PHH-based GSIs, which you should let PHH know, not me. I might silently ignore your report if you skip this.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out these repos, where most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building, including patches from PHH
sas-creator - generates VNDKLite and secure variants, can be used without a building environment
Donate?
https://paypal.me/AndyCGYan
Reserved
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
GAPPS builds are offered as-is without guarantees. Read #10 for more.
/system is RO on regular builds and RW on VNDKLite builds. VNDKLite builds can be used on most non-VNDKLite devices as well.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Magisk support should be on par with A11 (thanks @eremitein). The "abnormal state / unsupported SU" warning can be ignored. For devices that still don't play well with Magisk (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
Initial builds are based on PHH v400.c and November security patches.
Sigh, I don't really want to make a thread this early...
BTW, 32-bit and A-only users, you should really move on.
Big work thank You
Hey How to flash this Gsi Guys can someone answer me????
Thank you so much. Are gapps included ?
walid77dz said:
Thank you so much. Are gapps included ?
Click to expand...
Click to collapse
From an earlier post...
AndyYan said:
32*/A32* users, I'm not stopping your monthly builds just yet, but 32-bit is getting phased out, and you should upgrade soon. Similar goes for A-only. Ideally in the future we'll only have 64B, making room for other much needed variants such as GAPPS.
Click to expand...
Click to collapse
Their deprecation does seem likely now, so I'll try a GAPPS build or two when I have time.
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Avraham Tsaban said:
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Click to expand...
Click to collapse
I am using it as my daily driver - I enabled Gallery and LiveDisplay for just that purpose.
Out of curiosity I did try a dirty install from 18.1. It booted and most apps work, to my surprise, but Messaging won't allow me to select contacts properly no matter what, and that was a blocker, so don't.
People who love LOS, insist on using GAPPS with it, and had been asking me for such builds all this time - I now have a lil something for you, a test LOS19 build with GAPPS built-in. It's intentionally in the "personal" flavor to discourage use as your daily driver, but also shared-blocks (unlike previous "personal" builds) to save some space.
It was more trivial to build than I thought, but that doesn't mean I'll build it alongside vanilla yet...
Every variant takes disk space and build time
The image itself is huge and won't fit in even slightly older devices
Too many archs/variants confuse users
I cannot make any guarantees about it
I've seldom mentioned the last point, yet it's critical - I'm in China and I don't use GAPPS at all, so I have little idea about what counts as "properly working" for GAPPS and how to troubleshoot them. Even if I do eventually build with GAPPS, I can only provide builds as-is, and you'll have to help each other out on GAPPS-related/-induced issues. At the end of the day, I still recommend using other ROMs that are built around GAPPS, e.g. @ponces ' PE, for a more cohesive experience and better support.
For now, all I know is this test build logs in (after registering the device here), can open Play Store and download apps, nothing beyond that.
Huawei P20L mobile data doesn't work
confirmed working on huawei mediapad m5 (cmr-w09 model name)
thx so much AndyYan
first degoogled android 12
su working via phh su app - magisk wasn't working proper
I do the installation through fastboot, because I don't have twrp, The installation is successful, but when I start to start the installation it gives an error: Invalid sparse file format at header magic, and after that it installs normally, but when I start the system, it gets stuck in the logo of the manufacturer of my device, Any solution?
Flashed this ROM on my Oneplus 9 Pro and was surprised how great and smooth it is.
I read on a thread how to fix fingerprint issue on GSI ROM by editing /vendor/build.prop, tried it and ended up in bootloop and I have to start all over.
What's the right way to do this?
Thanks in advance.
Geoz said:
fix fingerprint issue on GSI ROM
Click to expand...
Click to collapse
You don't - no A12 GSIs support UDFPS yet.
AndyYan said:
You don't - no A12 GSIs support UDFPS yet.
Click to expand...
Click to collapse
Good to know. I appreciate you taking the time to explain this.
Thanks.
Geoz said:
Good to know. I appreciate you taking the time to explain this.
Thanks.
Click to expand...
Click to collapse
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
AndyYan said:
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
Click to expand...
Click to collapse
What of if I use Lineage OS as the base?
Thanks again.
Geoz said:
What of if I use Lineage OS as the base?
Thanks again.
Click to expand...
Click to collapse
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
AndyYan said:
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
Click to expand...
Click to collapse
First time on GSI ROM but I'm really impressed. I've learned a lot from you in a very short time. All information I read on the internet is not valid rather from a developer like you.
I appreciate you.

Development [ROM][OFFICIAL][oriole][12L] StatiXOS v5.2

{
"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"
}
StatiXOS for Google Pixel 6 (oriole)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
None!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
1. Download the image
2. Reboot your Pixel 6 to bootloader mode and plug it in to your computer
3. Now open up your Terminal (macOS and Linux) or Command Prompt (Windows) and download the firmware from the links below.
4. Once downloaded, type in fastboot -w to make sure your /data is formatted
5. Now type in fastboot update <location of the firmware>, things will be automated from this point on.
6. Profit!
Spoiler: Stay in touch with our Telegram channels!
Official Chatroom
Official Releases & Announcements Channel
​
Credits to Anay Wadhera (check him out https://github.com/anayw2001) for the builds. He's the main developer bringing you StatiXOS for the Google Pixel 6. As a part of StatiXOS, I am posting on behalf of him here
Note: Please keep in mind that this is being actively worked on. Updates would arrive as things are fixed so please be patient and if you report a bug, please be sure to explain what caused it and a logcat.
Prerequisite firmware: Latest stock release
Android version: 12.1.0
Linux Kernel Version: 5.10.101
Source code: GitHub
Code Review: Gerrit
Reserved.
Very excited for this, do you have a features list? Also does esim work ?
ne0ns4l4m4nder said:
Very excited for this, do you have a features list? Also does esim work ?
Click to expand...
Click to collapse
We focus more on ironing out AOSP inconsistencies and emphasis more towards a Pixel experience while keeping everything open-source
Edit: Anay told me that eSIM is untested so let us know if it works!
Nice, I liked your 4a build
Since ProtonAOSP and StatixOS are both based on AOSP, what's the difference between them exactly?
I'm tempted to try StatixOS but I'm currently on ProtonAOSP, that's why I'm wondering
Great job, thanks !
flyl0 said:
Since ProtonAOSP and StatixOS are both based on AOSP, what's the difference between them exactly?
I'm tempted to try StatixOS but I'm currently on ProtonAOSP, that's why I'm wondering
Click to expand...
Click to collapse
I noticed custom grids and the battery usage display is different. Advanced restart and uses lineage recovery. Seems a bit closer to stock overall than Proton but it's the first build.
Androbots said:
Google Pixel 6 is the first device to ship with a fully featured GKI aka Generic Kernel Image. Much like Project Treble, in simple terms, a Generic Kernel Image has external proprietary drivers while the actual Linux kernel source is kept vanilla thus making kernel upgrades a reality and even a potential option to run the mainline Linux kernel! One of our team members, Vaisakh (@m_vaisakh, https://github.com/mvaisakh) took a stab at compiling the gs101 kernel with his fork of GCC and was successful. However, he doesn’t have a device to test his changes on and we think you guys can really help us get things going!
Here’s the crowdfund link that StatiXOS is doing for @m_vaisakh:
Google Pixel 6 for StatiXOS dev: Vaisakh Murali
Help us get fellow StatiXOS dev Vaisakh Murali a Google Pixel 6 for development!
www.paypal.com
His kernel source: https://github.com/mvaisakh/pixel6
We really appreciate your support.
Thanks,
StatiX team
Click to expand...
Click to collapse
Does this build modded the Modem carrier configs i.e. Enabled 5G on all countries?
Thank you very much for your work, working great !! sorry, is there any way to get this recovery in .img? Thank you!
Also wondering about custom accent colors?
flyl0 said:
Since ProtonAOSP and StatixOS are both based on AOSP, what's the difference between them exactly?
I'm tempted to try StatixOS but I'm currently on ProtonAOSP, that's why I'm wondering
Click to expand...
Click to collapse
They are just different ROMs.
peter_betos said:
Does this build modded the Modem carrier configs i.e. Enabled 5G on all countries?
Click to expand...
Click to collapse
I am certain that we don't ship anything like that.
SirNacho said:
Thank you very much for your work, working great !! sorry, is there any way to get this recovery in .img? Thank you!
Click to expand...
Click to collapse
Nope.
ne0ns4l4m4nder said:
Also wondering about custom accent colors?
Click to expand...
Click to collapse
We definitely don't plan on adding that any time soon since Monet takes care of accents.
Androbots said:
They are just different ROMs.
I am certain that we don't ship anything like that.
Nope.
We definitely don't plan on adding that any time soon since Monet takes care of accents.
Click to expand...
Click to collapse
I know they are different roms
But what are the differences exactly? because it looks very very similar..
Those on ProtonAOSP might be interested in trying this custom ROM unless there is hardly any difference between the two builds .. I don't mean to sound disrespectful by saying that of course
Edit : Posting some screenshots and exact features of the rom would not have been too much too..
Anyway thanks for the hard work!
I also would like to see any kind of feature list!
I appreciate your work but you have not given us any reason to go through the effort to flash this ROM. What do we gain? What do we lose? Why would I switch from stock to this? Why would I switch from a ROM like ProtonAOSP which gives me thorough documentation on what it does and what it doesn't do?
I mean no disrespect and I understand that a lot of work must have been put into this. But give us SOMETHING to go on!
Here's some screenshots from their site:
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)
downloads.statixos.com
flyl0 said:
I know they are different roms
But what are the differences exactly? because it looks very very similar..
Those on ProtonAOSP might be interested in trying this custom ROM unless there is hardly any difference between the two builds .. I don't mean to sound disrespectful by saying that of course
Edit : Posting some screenshots and exact features of the rom would not have been too much too..
Anyway thanks for the hard work!
Click to expand...
Click to collapse
clipcarl said:
I also would like to see any kind of feature list!
I appreciate your work but you have not given us any reason to go through the effort to flash this ROM. What do we gain? What do we lose? Why would I switch from stock to this? Why would I switch from a ROM like ProtonAOSP which gives me thorough documentation on what it does and what it doesn't do?
I mean no disrespect and I understand that a lot of work must have been put into this. But give us SOMETHING to go on!
Click to expand...
Click to collapse
Well as far I know, ProtonAOSP doesn't have smartspace; which controls lockscreen weather, and other extras like a stopwatch counter, upcoming calendar events, and upcoming alarms. Everything we do is open-source and public for anyone to reuse, or modify. While we are there, we don't have a paywall that has "early access" stuff behind it. This is solely our hobby project and we don't intend to make a profit out of it. We post regular automated updates using our in-ROM OTA updater once official builds are seeded which usually happens after Google source gets relatively stable and free of super massive changes. We have our own changelog system as well located here: https://downloads.statixos.com/changelog/ and screenshots here: https://downloads.statixos.com/screenshots/. You can also keep track of our automated build instances here: https://buildkite.com/statixos. As of now, the changelog is empty since we haven't started an official rollout and screeshots provided are definitely non-final as well.
Our aim as a custom ROM - especially for Google Pixels - is to maintain the "Pixel experience" that really sets the phone apart from the competition with some quality-of-life improving features on top of it like say something as simple as double tap to sleep in the Launcher.
At the end of the day, we all have our own lives to take care of. Most of us are university students and some of us even have part-time jobs and sometimes, things come in our way and we have no other choice but to make our users wait - which we don't like either. We try the best we can in our limited free time to bring you this project for 4 years now and counting! Thank you for your understanding.
Do you guys have pixel launcher included? Only thing I'm missing with proton. Thanks for the hardwork and great looking ROM!
Xdevillived666 said:
Do you guys have pixel launcher included? Only thing I'm missing with proton. Thanks for the hardwork and great looking ROM!
Click to expand...
Click to collapse
No it's not included but you can install the one found in this thread
Modules Repository | #TeamFiles
All the files you need for customizing your Android device! #TeamFiles chat: @fileschat #TeamFiles announcements: @teamfilesannouncements More from #TeamFiles: @filesfederation Off-topic Group: @TeamFilesOT
t.me
Double tap to sleep on lock screen?
peter_betos said:
Does this build modded the Modem carrier configs i.e. Enabled 5G on all countries?
Click to expand...
Click to collapse
Wow is this a possibility?

Development [ROM][13][UNOFFICIAL] LineageOS 20 [Sunny][Mojito]

{
"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"
}
Code:
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.
About
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Download
- 20230524
Notes
- Don't change kernel.
- Custom recoveries are not allowed to be used.
- Custom kernels are not allowed to be used.
- Inlined with NetErnels.
- SafetyNet is OK.
- Signature Spoofing is OK.
- SELinux is enforcing.
- Encryption is enabled by default so decrypting is not allowed.
- Only use Lineage recovery to flash/format.
- 14.0.3.0 FW is recommended to use.
Flashing instructions
- Download ROM zip, recovery zip and fw if needed.
- Boot to bootloader.
- Run fastboot update LOS20_Recovery_*.zip , according to the build downloaded.
- Run fastboot reboot recovery
- Flash FW if needed (reboot to recovery after flashing)
- Format data with the recovery.
- Click Apply Update.
- Select your preferred method (Sideload/SDCard)
(For Sideload run : adb sideload lineage*.zip)
(For SDCard just select the zip from where you saved it)
- Reboot to system
Update Instructions
- Download ROM zip
- Flash FW if updated (reboot to recovery after flashing)
- Click Apply Update.
- Select your preferred method (Sideload/SDCard)
- Reboot to system
GPL Compliance
- Kernel Source : https://github.com/NetErnels/android_kernel_xiaomi_sunny
Telegram Support
- My PM
- Support Chat
Changelogs
24-May-2023
-- Device Changelog --
Updated blobs to V14.0.3.0.SKGMIXM
Set override_doze_mode prop
Switched to User Build
Added Implementation of ST2W (Single Tap to Wake)
Inherited common perf components from AOSPA
Inherited common Adreno components (updates adreno blobs to [email protected])
Drop perf blobs listing since its inherited from common
Drop Thermal Profiles/Doze from XiaomiParts
Drop PowerOffAlarm.
-- ROM Changelog --
May 2023 Security Patch (r43)
Recovery is now able to flash unsigned zips (magisk , fw , etc).
Removed some more logspam.
Switched to PIHooks for SafetyNet/Play Integrity.
Dropped Google Photos Spoofing.
Dropped Updater.
Ported CLO's Boost Framework.
Updated Prebuilts GApps.
Added MicroG build.
Switch to AVC 3.1 for screen recorder.
Compile for Perf.
Disable ripple animation on unlock.
Remove default aspect ratio limit for old apps.
Change the default value of sync mode to NORMAL.
Require unlocking to use sensitive QS tiles.
Add support for unlinked ringer streams
Enable media background turbulence.
Enable media player surface ripple on button press.
Add kill action to app shortcuts popup
Introduce overview scrolling scale animation.
Show clear all button in recents overview.
Add uninstall button to system. shortcuts.
Only warn on SPL downgrade.
Added Pixel Charger.
Added some missing spanish strings.
Make kernel version clickable.
Expose radio info (##4636##).
WiFi: Remove country code checking.
Move Extra Dim feature to display.
Add a preference to battery optimization page.
Open app when clicking on icon in App Info.
Finally.
I'm gonna have to wait a bit, my device is still locked and I want to wait and see a bit before I **** something up.
What isn't working yet? Really dumb to ask at this point, but what is missing from the ROM to become official?
ChristianWS said:
Finally.
I'm gonna have to wait a bit, my device is still locked and I want to wait and see a bit before I **** something up.
What isn't working yet? Really dumb to ask at this point, but what is missing from the ROM to become official?
Click to expand...
Click to collapse
everything is working... i'm using this rom since release and i finally found my daily driver rom...
maybe you will face some lags on apps but can be easily fixed by adding some props to build.prop (i'll do on next build)
About Official... LineageOS Requeriments are very strict and i'm not a experienced developer (i'm just learning) so i can't make this official
So , i'll provide monthly updates as long as i have server to build it.
Long Live LineageOS...
Cant wait to use it as a daily driver..
@alonsoj636 this is awesome!
many of us have been waiting for this for so long! a true ROM diamond!
..and I'm gonna look into it soon, I need to have a few days off to tinker around with it.
I wonder if it's still possible with haystack needle to get signature spoofing working and with it microG.
also, i guess, after flashing FW 13.x there is no way back to 12.x and lower due to anti-rollback protections.. so it's a one-way ticket to flash.
Zirila said:
@alonsoj636 this is awesome!
many of us have been waiting for this for so long! a true ROM diamond!
..and I'm gonna look into it soon, I need to have a few days off to tinker around with it.
I wonder if it's still possible with haystack needle to get signature spoofing working and with it microG.
also, i guess, after flashing FW 13.x there is no way back to 12.x and lower due to anti-rollback protections.. so it's a one-way ticket to flash.
Click to expand...
Click to collapse
since i use Google Services i didn't look at spoofing and microg but you can always try
For next build i'll look into it
About anti - rollback you can downgrade MIUI but you should ALWAYS choose the correct variant that the phone came with (Global , India , Indonesia , EEA , etc) and avoid locking the bootloader
alonsoj636 said:
About Official... LineageOS Requeriments are very strict and i'm not a experienced developer (i'm just learning) so i can't make this official
Click to expand...
Click to collapse
Beggars can't be choosers and all of that, and I know LineageOS requirements are strict, but it doesn't really spark much confidence.
Let me rephrase that: what is missing from the ROM becoming official?
Hey, i have redmi note 10 pro, and I would love to use lineage 19 on my device. As redmi note 10 and 10 pro are so similar, can please tell if you faced issues while porting it, or was the process straight forward? ( I have never ported a rom before and have little knowledge).
Thank you!
ChristianWS said:
Beggars can't be choosers and all of that, and I know LineageOS requirements are strict, but it doesn't really spark much confidence.
Let me rephrase that: what is missing from the ROM becoming official?
Click to expand...
Click to collapse
i already answered you... everything is working and this ROM is stable enough to be official. But since I don't meet the requirements and I don't have much time to maintain it it will not be possible from my side... Maybe another developer can take Official LineageOS but meanwhile , i will maintain Unofficial.
Stan m said:
Hey, i have redmi note 10 pro, and I would love to use lineage 19 on my device. As redmi note 10 and 10 pro are so similar, can please tell if you faced issues while porting it, or was the process straight forward? ( I have never ported a rom before and have little knowledge).
Thank you!
Click to expand...
Click to collapse
They are completely different devices.
This is only for Redmi Note 10 (mojito/sunny)
alonsoj636 said:
They are completely different devices.
This is only for Redmi Note 10 (mojito/sunny)
Click to expand...
Click to collapse
Yeah. I am not asking if I can use this rom for my device. I am saying as they are similar, I just want to know if you had any problems during developing this rom. If you didn't have any problems, chances are I wont have problems either.
Thank you!
Stan m said:
Yeah. I am not asking if I can use this rom for my device. I am saying as they are similar, I just want to know if you had any problems during developing this rom. If you didn't have any problems, chances are I wont have problems either.
Thank you!
Click to expand...
Click to collapse
i didn't have any problems
alonsoj636 said:
i didn't have any problems
Click to expand...
Click to collapse
So downloaded lineage 19 source code, device tree, oss vendor, and complied them. That is all right?
Thank you!
Stan m said:
So downloaded lineage 19 source code, device tree, oss vendor, and complied them. That is all right?
Thank you!
Click to expand...
Click to collapse
device tree + common device tree + kernel tree + vendor tree + common vendor tree... i suggest to ask in your device community because this is a off-topic conversation
alonsoj636 said:
i already answered you... everything is working and this ROM is stable enough to be official. But since I don't meet the requirements and I don't have much time to maintain it it will not be possible from my side... Maybe another developer can take Official LineageOS but meanwhile , i will maintain Unofficial.
Click to expand...
Click to collapse
Okay, let me rephrase that again: what requirements aren't being met?
ChristianWS said:
Okay, let me rephrase that again: what requirements aren't being met?
Click to expand...
Click to collapse
Why don't you read the requirements yourself. Then it will be absolutely clear.
ChristianWS said:
Okay, let me rephrase that again: what requirements aren't being met?
Click to expand...
Click to collapse
time : i don't have enough time to take care of lineage os ... i just can do builds when i get time.
interest : i'm not currently interested on submitting any ROM to Official Status (reason : i don't care about official rules)
why the traffic network is on the center?
y'know our devices camera is on center right?
FNTX0230 said:
why the traffic network is on the center?
y'know our devices camera is on center right?
Click to expand...
Click to collapse
i have the device i know
ask lineage os developers , they doesn't allow the customization of the traffic monitor

Categories

Resources