[ROM][11] Project Sakura [gauguin] Mi 10i 5G/ Mi 10T Lite/ Redmi Note 9 Pro 5G [OFFICIAL]

[Falar85]

You have two other options, tap to turn on screen and tap to lock screen.. that's almost the same...

Not even close. When you take your phone with you, you want to glance at the time or notifications before you put it in your pocket without tapping the screen. Just like you want the screen to turn on when you get a notification without extra tapping.

 

[tze_vitamin]

Not even close. When you take your phone with you, you want to glance at the time or notifications before you put it in your pocket without tapping the screen. Just like you want the screen to turn on when you get a notification without extra tapping.

This is second realize, developer probably read this and there is possiblity to add. Just support their work. They know sometimes meet the needs of customers.

 

[_z3_]

Hey there. Like the ROM pretty much!! Thx 4 that!

 

[tze_vitamin]

I use over a week , ROM working perfect , I flashed yesterday new kernel Tales Waves that come out and also flash new sky hawk recovery.. phone looks awesome. I especially likes this messages on At a glance widget.
This is my Antutu on this ROM . For this CPU ,this is amazing!

 

[el.corzo]

@WallyWest : can you help with this error message please?

~/android/sakura$ lunch lineage_gauguin-userdebug
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:22 dumpvars failed with: exit status 1
Device gauguin not found. Attempting to retrieve device repository from Sakura-Devices Github (http://github.com/Sakura-Devices).
Repository for gauguin not found in the Sakura-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/default.xml
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:23 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:24 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_gauguin'
** Do you have the right repo manifest?

https://github.com/Sakura-Devices repository does not have Gauguin!
Can you fix this?

 

[AnibalSP]

@WallyWest : can you help with this error message please?

~/android/sakura$ lunch lineage_gauguin-userdebug
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:22 dumpvars failed with: exit status 1
Device gauguin not found. Attempting to retrieve device repository from Sakura-Devices Github (http://github.com/Sakura-Devices).
Repository for gauguin not found in the Sakura-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/default.xml
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:23 dumpvars failed with: exit status 1
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
build/make/core/product_config.mk:155: error: Can not locate config makefile for product "lineage_gauguin".
00:05:24 dumpvars failed with: exit status 1

** Don't have a product spec for: 'lineage_gauguin'
** Do you have the right repo manifest?

https://github.com/Sakura-Devices repository does not have Gauguin!
Can you fix this?

First of all, do you have a device tree in the folder /device/xiaomi/gauguin?
If not... do that first.

Probably you need to change the name of a few files, almost all the roms device trees are always named <rom>_<device codename>, for example, sakura_gauguin, aosp_gauguin, whatever_gauguin...

So, you need to change in your device tree ALL the files named whatever_gauguin.something, to <romcodename>_gauguin.something, then, open your <something>_gauguin.mk, and probably there will be a path to a file, named <romcodename>_gauguin.mk, change it to whatever you need, do it again for a few files with .mk at the end, and try again.


This is a mess, i know, but anyways, try watching this...

 

[el.corzo]

First of all, do you have a device tree in the folder /device/xiaomi/gauguin?
If not... do that first.

Actually that is exactly what lunch lineage_gauguin-userdebug command should do: get device specific files from other repositories.
That is the reason why I asked @WallyWest if he/she can fix it.

Probably you need to change the name of a few files, almost all the roms device trees are always named <rom>_<device codename>, for example, sakura_gauguin, aosp_gauguin, whatever_gauguin...

So, you need to change in your device tree ALL the files named whatever_gauguin.something, to <romcodename>_gauguin.something, then, open your <something>_gauguin.mk, and probably there will be a path to a file, named <romcodename>_gauguin.mk, change it to whatever you need, do it again for a few files with .mk at the end, and try again.

According to Sakura Documentation on GitHub all of this is not necessary :

GitHub - ProjectSakura/android: Manifest for syncing Project Sakura sources.

Manifest for syncing Project Sakura sources. Contribute to ProjectSakura/android development by creating an account on GitHub.

github.com

This is a mess, i know, but anyways, try watching this...

Thanks for the link. Very interesting. I am not sure if this would still work because of old Ubuntu, old Android, another ROM (Resurrection Remix) and the lack of Lineage OS for Gauguin.
By the way : how can this ROM base on top of Lineage OS if there is no Lineage for this device?

 

[AnibalSP]

Actually that is exactly what lunch lineage_gauguin-userdebug command should do: get device specific files from other repositories.
That is the reason why I asked @WallyWest if he/she can fix it.

Yeah, but that only will work if the device tree is uploaded to the github repo or whatever is it, that's why i'm telling you to download (or make) your device tree and copying it manually to the device folder

Thanks for the link. Very interesting. I am not sure if this would still work because of old Ubuntu, old Android, another ROM (Resurrection Remix) and the lack of Lineage OS for Gauguin.

I'ts a really old version of Ubuntu / ROM, but it's still almost the same thing, basically what he does is changing all the references to Lineague OS to RR and removing dependencies from L OS, but it should be fairly similar for all the roms.

By the way : how can this ROM base on top of Lineage OS if there is no Lineage for this device?

The device tree is only the config files and that type of stuff, every android rom requires all that for working, because if you compile it for ARM probably is not going to boot, but anyways, the device tree is just that, configuration files and dependencys for the SoC and hardware in general, there souldn't be anything specific for L OS or any rom, and a device tree from a ROM should work in another ROM.



Maybe all this is confusing, but my english is really bad so... If you don't understand something or whatever, sorry.


EDIT: Install the latest MIUI version and extract the blobs, or otherwise it can give issues

 

[el.corzo]

Yeah, but that only will work if the device tree is uploaded to the github repo or whatever is it, that's why i'm telling you to download (or make) your device tree and copying it manually to the device folder

The maintainer wrote me that the device and vendor trees are private.
So its not worth to loose more time on this rom.
I'll try with Palladium OS. It has the only maintainer who kindly helped.

I'ts a really old version of Ubuntu / ROM, but it's still almost the same thing, basically what he does is changing all the references to Lineague OS to RR and removing dependencies from L OS, but it should be fairly similar for all the roms.

The device tree is only the config files and that type of stuff, every android rom requires all that for working, because if you compile it for ARM probably is not going to boot, but anyways, the device tree is just that, configuration files and dependencys for the SoC and hardware in general, there souldn't be anything specific for L OS or any rom, and a device tree from a ROM should work in another ROM.

Maybe all this is confusing, but my english is really bad so... If you don't understand something or whatever, sorry.

Your English is not the problem. Problem is: all the available guides are either old or not for not-experienced.

EDIT: Install the latest MIUI version and extract the blobs, or otherwise it can give issues

No need. Some nice people extracted them already :
Pixel Experience : https://github.com/PixelExperience-Devices/device_xiaomi_gauguin
Palladium OS : https://github.com/PalladiumOS-Devices/device_xiaomi_gauguin
Did you ever extracted the BLOBs yourself? How difficult it is?

 

[AnibalSP]

The maintainer wrote me that the device and vendor trees are private.
So its not worth to loose more time on this rom.
I'll try with Palladium OS. It has the only maintainer who kindly helped.

Your English is not the problem. Problem is: all the available guides are either old or not for not-experienced.

No need. Some nice people extracted them already :
Pixel Experience : https://github.com/PixelExperience-Devices/device_xiaomi_gauguin
Palladium OS : https://github.com/PalladiumOS-Devices/device_xiaomi_gauguin
Did you ever extracted the BLOBs yourself? How difficult it is?

this could interest you

Compilation guide - ArrowOS Blog

Initialize your local repository & sync: To maintain the quality of device sources we recommend...

blog.arrowos.net

 

[el.corzo]

this could interest you

Compilation guide - ArrowOS Blog

Initialize your local repository & sync: To maintain the quality of device sources we recommend...

blog.arrowos.net

ArrowOS was my first choice. Unfortunately guide you linked is not complete (actually it is a short blog post) and the maintainer do not answer questions in thread:

[ArrowOS] [R] Xiaomi Mi 10t Lite [gauguin] [NIGHTLIES] [UNIFIED]

ArrowOS ABOUT ArrowOS is an AOSP/CAF based project started with the motto of keeping things simple, clean and neat. Website: https://arrowos.net Telegram: Channel | TG Portal/Links Github: https://github.com/ArrowOS Code Review...

forum.xda-developers.com

Pixel Experience is the only ROM that has a good, up-to-date guide that functions and all needed repositories are available.
I could build and flash it without problems. May be that is the reason why Pixel Experience is so popular and long lasting. I would definitely go with it if it had a "vanilla" version or the maintainer answered me how to compile a vanilla version.

 

[el.corzo]

this could interest you

Compilation guide - ArrowOS Blog

Initialize your local repository & sync: To maintain the quality of device sources we recommend...

blog.arrowos.net

@AnibalSP : Update --> i found another "recipe" in local repo
./arrow/.repo/manifests/README.md
following that i have managed to compile and install Arrow OS.
It works! If someone here wants to try it i can upload it somewhere.
Thank you pointing this.

 

[AnibalSP]

For some reason all the camera apps don't detect the main camera, only the macro and high field of view cameras, i will post a logcat later.

 

[nerdfail]

The maintainer wrote me that the device and vendor trees are private.
So its not worth to loose more time on this rom.
I'll try with Palladium OS. It has the only maintainer who kindly helped.

Your English is not the problem. Problem is: all the available guides are either old or not for not-experienced.

No need. Some nice people extracted them already :
Pixel Experience : https://github.com/PixelExperience-Devices/device_xiaomi_gauguin
Palladium OS : https://github.com/PalladiumOS-Devices/device_xiaomi_gauguin
Did you ever extracted the BLOBs yourself? How difficult it is?

trees being private doesn't affect the end user

 

[el.corzo]

trees being private doesn't affect the end user

Of course it does.
Do you think using the work of other developers (AOSP, Lineage, ... ) yourself but keeping your modifications/enhancements private is a social behavior?
If every one would do the same, there won't be any Free Software at all!

Philosophy of the GNU Project - GNU Project - Free Software Foundation

www.gnu.org

So not one single Custom ROM would exist.

 

[nerdfail]

Of course it does.
Do you think using the work of other developers (AOSP, Lineage, ... ) yourself but keeping your modifications/enhancements private is a social behavior?
If every one would do the same, there won't be any Free Software at all!

Philosophy of the GNU Project - GNU Project - Free Software Foundation

www.gnu.org

So not one single Custom ROM would exist.

The base tree is still public if you know where to look. And the tree isn't private because of any modifications. Kernel is still public and soon the device tree will be too.

 

[Whiskeyomega]

whats new on 5.1 (22nd June) ?

 

[prubyholl]

For some reason all the camera apps don't detect the main camera, only the macro and high field of view cameras, i will post a logcat later.

I am having the same issue. Have you managed to fix it or have some direction on something I can try, I was suspecting it's a vendor/firmware issue-based but every other ROM I have tried has the camera working fine, but Sakura is blur. Thanks for suggestions

 

[nerdfail]

I am having the same issue. Have you managed to fix it or have some direction on something I can try, I was suspecting it's a vendor/firmware issue-based but every other ROM I have tried has the camera working fine, but Sakura is blur. Thanks for suggestions

will be fixed in June End update

 

[nerdfail]

whats new on 5.1 (22nd June) ?

changlog is there on the website sir