Development - [ROM][13.0_r30][OFFICIAL] Evolution X 7.6.1 [02/12/2023] | Page 12...

Commonly asked questions & answers:

Q: Why am I getting "error cannot read" while attempting to sideload the ROM or are unable to fastboot flash vendor_boot

Q: I'm a windows user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?


Q: I'm a linux user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?

Q: Will you release builds in the update.zip format?

Q: Why is MTP not working?

Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the telegram group as a LAST RESORT.

To be continued (I'm sure).

Custom Kernels:

Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.

Obtaining root:
Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!

Root can be obtained by either one of the following methods.

Reporting bugs and submitting logs:

In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:

General system log
adb logcat > logcat.txt

Kernel log
adb shell su -c dmesg > dmesg.log

Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.

Getting involved in the development:

We've set everything up in such a way where all you need to do is install AOSP build dependencies, initialize a repo client, init the tiramisu-pixel branch of our manifest, sync the code and lunch your device (e.g lunch evolution_cheetah-userdebug); Roomservice will automatically sync all device specific dependencies for you to compile without error. There is no need to manually clone anything due to this and applies to Pixel 6, 6 Pro, 6a, 7 & 7 Pro (oriole, raven, bluejay, panther & cheetah).

Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!

AnierinB said:

It's a server side issue on googles end regarding CTS since this morning on multiple device, not just p7 series running customs. Please keep in mind this is separate from SN not passing by default without modules (which was already fixed, but now there's this).

Anyways, this was resolved. Builds will be out sometime tomorrow.

#KeepEvolving