yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge (Exynos) ROMs, Kernels, Rec] CobalTitan:
JUST Home button remap not work
[Xiaomi Mi 8 Guides, News, & Discussion] TheTechFixShow:
[YOUTUBE]https://youtu.be/Bf44z8xbKH4[/YOUTUBE]

Here is my easy and quick guide on how to go from the china rom to the miui Global rom, with links to the miui 10 beta for the Xiaomi Mi 8.

Disclaimer:

- It will void your warranty. If you wish to install any type of custom ROM on your smartphone and if anything goes wrong, then the manufacturer is not responsible for it.

- You may brick your phone or your phone may not power on thereafter.

- The Xiaomi Mi 8 phone may become more sluggish and laggy if you install non-optimized custom ROM on the devices.

LINKS:

STEP 1: UNLOCKING BOOTLOADER:

Application: https://en.miui.com/unlock/

Download MiUnlock Tool: http://en.miui.com/unlock/download_en.html

STEP 2: Mi Flash Tool

http://en.miui.com/thread-2197836-1-1.html

STEP 3: Global Roms

MIUI 9.5 Stable: http://en.miui.com/download-346.html

MIUI 10 Beta: https://xdaforums.com/mi-8/how-to/rom-mi-8-miui-10-global-beta-8-8-7-t3826560
[Android Q&A, Help & Troubleshooting] zoomysloppy:
1)Does once clcik root work with PC on Android 7.0?

2)If i update my phone with OTA updates will i keep root?

3)What happens if i update with root acces? Will i lose my root? Will my device be brickes?

I dont care about twrp or bootloader or whatever, i just want to root my phone and be able to change the DPI and Resolution.

Im using a Xiaomi Redmi Note 4 and i want to Root it and also be able to have Miui 10, thats why im asking.
[Moto G6 Questions & Answers] yxmikx:
Hi, I have a Motorola g6 xt1926-6, with a leyend “your device is corrupt” I try to upload so many softwares but it show me only error, the device have lock the bootloader

I need help me please
[Moto G6 Questions & Answers] stifmaster81:
Unlock the bootloader on the Motorola website, take the steps, and once unlocked when you flash the factory firmware you will be installed

Enviado desde mi moto g(6) mediante Tapatalk
[Moto G6 Questions & Answers] yxmikx:
I can not enter the system to activate the oem option, that's why I have not unlocked
[Moto G6 Questions & Answers] stifmaster81:
your Motorola goes into recovery?

Power More volume less?

Enviado desde mi moto g(6) mediante Tapatalk
[Moto G6 Questions & Answers] echo92:
Hmm, can you remember what firmware you had? Have you tried booting to recovery and tried a cache wipe or factory reset?

If your bootloader is still locked and you did not request an unlock key from Motorola, it might be worth considering visiting a service centre and getting your device looked at. You've still got the warranty, hopefully - might as well use it...
[Moto G6 Questions & Answers] Xplorer4x4:
You don't need to enter the system. Hold Volume Down and the power button then follow the steps to flash your stock firmware. You need fastboot.exe on your pc. Plug in a USB cable to the pc and phone then flash the stock firmware. Make sure when you power on the device using power + Vol Down to unlock your bootloader. The option you refer to in system does nothing on its own.

Also tell us how you ended up in this situation. I'm guessing you did something to cause the problem?
[Moto G6 Questions & Answers] DavCan:
I believe you need the bootloader unlocked in order to flash anything. I have a 1926-7 and I'm stuck in bootloader, since I can't access the operating system to allow Developer Options, I can't unlock bootloader, and my os is corrupt.

What can I do? Thanks
[Moto G6 Questions & Answers] Ragarianok:
You should be able to flash official Moto firmware whether your bootloader is unlocked or not.

Look here:

https://mirrors.lolinet.com/firmware/moto/evert/official/

Download the correct firmware for your device and flash.
[Moto G6 Questions & Answers] DavCan:
Thanks for your reply. I've tried many firmwares already, no luck. Here's the thing:

I'm stuck in Fastboot, it says "flashing_locked" , so I'm not allowed to flash. If you try the command "flashing unlock" it sends you to enable USB debugging and OEM unluck but I DO NOT have access to the operating system anymore.

I hope there's something I can do. Very costly paperweight I have now haha :crying:
[Moto G6 Questions & Answers] DavCan:
help!

I keep trying things with no luck, it seems like I fogot my car keys inside, no spare keys, and the car is bulletproof :(

fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-bf761ac-180305
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY323366HL
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 473E091F
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 351853092729596
(bootloader) meid:
(bootloader) date: 08-22-2018
(bootloader) sku: XT1926-7
(bootloader) carrier_sku: XT1926-7
(bootloader) battid: SB18C20873
(bootloader) battery-voltage: 4150
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-2/00cb:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.201.2.evert.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05300-sdm660.0
(bootloader) version-baseband: M660_23.40.01.85R EVERT_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gba3f1d6 (hud
(bootloader) kernel.version[1]: soncm@ilclbld34) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Feb 6 01:31:11 CST 2019
(bootloader) git:abl: MBM-3.0-uefi-bf761ac-180305
(bootloader) git:xbl: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:pmic: MBM-3.0-uefi-976f2e6-180305
(bootloader) git:rpm: MBM-3.0-uefi-80b016f-180305
(bootloader) git:tz: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:hyp: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:devcfg: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:cmnlib64: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:keymaster: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:prov: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) git:storsec: MBM-3.0-uefi-2c297a4-dirty-180305
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.297s
[Moto G6 Questions & Answers] DavCan:
No luck :(

No love? Can't believe there's anything I can do with this. What I was thinking I know, but... still...

I've tried the method downloading the Qualcomm drivers, putting the PC in test mode, etc. but I only get the "<Waiting for device>" and nothing else happens.

Hope you can shed some light here. Thanks
[Xiaomi Mi A2 / 6X Questions & Answers] 3omarelfouly:
hey guys, i wanna know if i will still get ota updates if i unlocked the bootloader ??

i wanna unlock it and if i didn't flash TWRP after unlocking it i will be able to install the update ??
[Xiaomi Mi A2 / 6X Questions & Answers] AsItLies:
This thread is pretty old and it's referring to a Nexus 5, but I think the info holds true. Unlocking wont' stop ota updates, and if all it is is unlocked, then the ota update should install.

It's when you install twrp, or root, or a new system image, etc... that's when the ota update won't install.

https://xdaforums.com/google-nexus-5/help/unlocking-bootloader-prevent-automatic-t3003581
[Xiaomi Mi A2 / 6X Questions & Answers] Ravirush:
When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly

My question is can get OTA update ?
[Xiaomi Mi A2 / 6X Questions & Answers] duxxyuk:
In order to maintain the OTA compatibility there is one thing to bear in mind. The system must have the same parity as a standard image.

Changes to the build.prop (camera 2) or swapping out a boot image change this parity. Put the original boot and build.prop back and you should be OK.

Perhaps the best way to think about this is the red pill or the blue pill...

As for rooting - for our Xiaomi A2's the best way to root is to :

Unlock the bootloader (this will wipe your data - ensure you have backups)

Swap the boot.img for one that is Magisk compatible (from this point your OTA is broken)

Install magisk (for the SU)

At this point to get back OTA capability one has to uninstall Magisk and put back a standard boot.img - This hasn't worked for me since going Pie (I have thus swallowed the red pill)

If you touch your build.prop or other system files IMHO you can bury the OTA.

If I want a new version of android I'll manually flash the new image and go back through the rooting process and finish by modifying my build.prop.

There are Magisk modules that provide systemless changes but I've not tested these myself - I prefer to know exactly what I'm doing with my build.prop.

To get back to standard you can always flash a standard system image and if you really want to be clean you can relock the bootloader which will reset your phone as if it was out of the box.
[Xiaomi Mi A2 / 6X Questions & Answers] Ashik_salim_:
Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.

Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..

Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.

On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.

To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.

After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.
[Xiaomi Mi A2 / 6X Questions & Answers] tnt-4-:
hi my friend. i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
[Android Software/Hacking General [Developers Only]] ValdikSS:
Tested devices

Devices which support at least 512 kbit/s SBC

1MORE iBFree

JBL Everest 310

JBL Everest 700

JBL T110BT

JBL E55BT

JBL T460BT

JBL Endurance SPRINT (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)

Skullcandy HESH 3

SoundPEATS Q30

Sony WH-H900N

Sony WI-C400

Sony MDR-1ABT

Sony MDR-ZX770BT

Sony MDR-ZX770BN

Sony MDR-XB650BT

Sony MDR-XB950B1

Sony SBH50

SVEN AP-B570MV

Syllable G600

Bluedio A/Air (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)

Bluedio T4s (Bitpool max 39. Claim to not support Dual Channel, but work if forced, 462 kbit/s. Does not conform to A2DP specification.)

Bluedio T5 (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)

Bluedio T6 (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification. Adopt Max 97220 chipset.)

Marshall Major II Bluetooth

Overdrive RealForce D1

DEXP BT-210

DEXP BT-220

DEXP BT-250

DEXP BT-260

DEXP BT-280

Edifier W288BT

Edifier W830BT

Nomi BT 211

LeEco Le Sports BT

Xiaomi MI Portable Bluetooth Speaker

Xiaomi Square Box Bluetooth Speaker 2

Sennheiser HD 4.40BT

AKG K845BT

Beyerdynamic Amiron Wireless

Bowers & Wilkins PX

Bowers & Wilkins Zeppelin Wireless

House of Marley Liberate XLBT

Harman Kardon Onyx Studio 4

Harman Kardon Aura Studio 2

QCY QY8

Panasonic RP-BT10

Jaybird X3

Logitech BT Adapter

TP-Link HA100

Xiaomi Mi Bluetooth Audio Receiver

Overfly Portable Bluetooth Receiver

KZ Wireless Bluetooth Module

Excelvan B7

Hagibis X2

Pioneer SE-E7BT

Automotive DAC Lusya bluetooth 4.0 with AK4490, NE5532

Noname automotive head unit (CSR8645 chip)

Sony DSX-A400BT automotive head unit

Devices which support SBC higher than 512 kbit/s

JBL Everest 310 (617-660 kbps)

JBL T110BT (576 kbps)

JBL Endurance SPRINT (573 kbps)

SoundPEATS Q30

DEXP BT-210 (617 kbps)

DEXP BT-220 (617 kbps)

DEXP BT-260 (617 kbps)

DEXP BT-280 (617 kbps)

Sony WI-C400 (576 kbps)

Sony MDR-ZX770BT (617-660 kbps)

Sony MDR-ZX770BN

Marshall Major II Bluetooth (617-660 kbps)

Overdrive RealForce D1 (730 kbps, dual channel, 4 subbands)

Jaybird X3

QCY QY8 (617 kbps)

Edifier W288BT (617 kbps)

Panasonic RP-BT10 (596 kbps)

LeEco Le Sports BT (617 kbps)

Nomi BT 211 (617 kbps)

Xiaomi Mi Bluetooth Audio Receiver (576 kbps)

Overfly Portable Bluetooth Receiver (617 kbps)

Automotive DAC Lusya bluetooth 4.0 with AK4490, NE5532 (576 kbps)

Devices which don't work with higher bitrates or Dual Channel

Harper HB-202 (cracklings; Beken BK3256 chip)

Sony Ericsson MW600 (high frequency distortion, cracklings; device from 2009)

Sony SBH52 (too slow to handle packet rate)

BlitzWolf BW-F2 (no sound)

Overfly mini Bluetooth receiver (no sound)
[Android Software/Hacking General [Developers Only]] ValdikSS:
Why this is important: SBC 328k and 485k vs aptX

Contrary to popular belief of aptX sound quality, in some cases it can produce worse audio quality than SBC with a standard 328k bitrate.

SBC dynamically allocates quantization bits for frequency bands, acting on a "bottom-to-top" basis. If the whole bitrate was used for the lower and middle frequencies, the upper frequencies are "cut off" (silenced).

aptX quantizes frequency bands with the same number of bits constantly, which makes it a constant bitrate codec: 352 kbps for 44.1 kHz, 384 kbps for 48 kHz. It can't "transfer bits" to frequencies that are mostly needed in them. Unlike SBC, aptX will not "cut" frequencies, but will add quantization noise to them, reducing the dynamic range of audio, and sometimes introducing crackles. SBC, on the contrary, "eats the details" - discards the quietest areas.

On average, compared to SBC 328k, aptX makes less distortion in music with a wide frequency range, but on music with a narrow frequency range and a wide dynamic range SBC 328k sometimes wins.

Let us consider a special case, a piano recording. Here's a spectrogram:

The most energy lies in the 0-4 kHz frequencies, and lasts up to 10 kHz.

The spectrogram of the file aptX file looks like this:

Here is SBC 328k:

It can be seen that the SBC 328k periodically completely cut off the range above 16 kHz, and used all available bitrates for ranges below this value. However, aptX introduced more distortions into the frequency spectrum audible by the human ear, which can be seen on the subtracted original spectrogram from the aptX spectrogram (the brighter, the more distortion):

While the SBC 328k has introduced less distortion the signal in the range from 0 to 10 kHz, and the rest has been сut:

Bitrate 485k for SBC was enough to save the entire frequency range, without cutting off the bands.

SBC 485k on this audio sample is much better than aptX in the range of 0-15 kHz, and with a smaller but still noticeable difference - at 15-22 kHz (the darker, the less distortion):

Switching to a high-bitrate SBC, you will get a sound superior to aptX most of the time, on any headphones.
[Android Software/Hacking General [Developers Only]] rohit3192:
Bro. The concepts sound amazing.

I have Le Max 2 (Oreo). I have attached Bluetooth .so files.

If you patch I will try on Sony Bluetooth system and share with my friends patched files to see how much it works.

Thanks.
[Android Software/Hacking General [Developers Only]] ValdikSS:
For some reason I can't download your file, always get 404 not found. Another person with LeEco LeMax 2 (x820) contacted me and I made a patch, but only for 32-bit library. Since your archive is >2 MB, I suppose it contains 32 and 64 bit libraries. Please write your exact OS version and build number.

Would you mind to try? Backup your files first, replace 32-bit library with the file from the archive and rename 64-bit library, so it won't be used, and follow the instructions in the second post to capture the dump and upload it to btcodecs.
[Android Software/Hacking General [Developers Only]] rohit3192:
OK .

I try. Allow me some time.

Yes both libs were in one file. Now sending you separate libs.
[Android Software/Hacking General [Developers Only]] ValdikSS:
Try these.
[Android Software/Hacking General [Developers Only]] rohit3192:
I have replaced file in /system/lib with permission.

And renamed /lib64 file as instructed.

Bluetooth switch doing nothing.

After renaming lib64 to original name the Bluetooth switch works and connects.

Build no attached.
[Android Software/Hacking General [Developers Only]] ValdikSS:
Please try the latest archive. It includes patched 64 bit libraries.
[Android Software/Hacking General [Developers Only]] rohit3192:
The new patched 64bit file worked.

Tried 486 one only.

Here is Bluetooth log. (Upload was too slow at given link so sending GD link)

Post edited: thanks [MENTION=685332]ValdikSS[/MENTION] a lot.
[Android Software/Hacking General [Developers Only]] ValdikSS:
Yes, it worked, the bitrate is 485 kbit/s. Did you hear any cracklings or interruptions?

The audio you played is of low quality. That's probably an MP3 ~160-192 kbit/s?
[Android Software/Hacking General [Developers Only]] rohit3192:
There is no crackling. Yes mp3 was of low quality that I tested.

Yet sound seems improved. I will need more time to get proper impression. I will post later here.

Also I have spread the word in few telegram channels.

Thanks
[Android Software/Hacking General [Developers Only]] chudy_85:
[MENTION=225651]op[/MENTION] here you have my lib from Huawei P9 Android 7.0

Can you check and modded to test. I be test on my LG HBS910 with aptx

https://mega.nz/#!G3gR3RrC!yNysYtkk1DhlBk-ec87bIP56aupCwKvfiWM1k32Qy7k
[Android Software/Hacking General [Developers Only]] ValdikSS:
Patched version has been added to the second post.

This sound enhancement is only for SBC codec, it won't do anything with aptX. You should disable aptX to test patched version.
[Android Software/Hacking General [Developers Only]] AdityaDharewa:
Hello

I have 1more ibfree sport headphone that supports AAC HD codec only with apple devices as company has mentioned in their site. (https://india.1more.com/collections...ore-ibfree-sport-bluetooth-earphones-with-mic)

As in your post you have mentioned 1more ibfree, that support aptx codec .

My headphone is newer version of ibfree series.

So the problem is in developer setting I can't change to AAC from SBC codec.

It stays to SBC only so I think I can get help from here from you.

So here the link to those .so files

https://mega.nz/#F!tj5AlahL!yCrNHYB-ft-zaJl2uc7kig

Phone - Le Max2 Lineage Oreo 8.1
[Android Software/Hacking General [Developers Only]] ValdikSS:
Please capture a dump and upload it to https://btcodecs.valdikss.org.ru, you'll see all codec information which the device supports.

And by the way, patched libraries for Le Max2 Oreo are already in the second post, give them a try.
[Android Software/Hacking General [Developers Only]] LeifAlbor:
Hmmm those files don't exist on my device (Pixel 2 XL, Pie 9.0 stock OS)
[Android Software/Hacking General [Developers Only]] ValdikSS:
/system/lib/libbluetooth.so and /system/lib64/libbluetooth.so for Android 9.
[Android Software/Hacking General [Developers Only]] LeifAlbor:
Done
[Android Software/Hacking General [Developers Only]] ValdikSS:
Battery consumption difference is negligible if at all. There's probably nothing you can do aside from removing the check in the code and recompile the firmware. Out of several dozens of tested devices only Bluedio headphones and Mi receiver does not report to support Dual Channel. This is A2DP standard violation and probably should not be workarounded.
[Android Software/Hacking General [Developers Only]] d3vyarth:
Both are Chinese brands, Alas:silly:. If battery consumption difference is negligible, then forcing dual channel shouldn't cause any issue.

Just one more thing, can I still flash that magisk module to bring the changes I want?
[Android Software/Hacking General [Developers Only]] ValdikSS:
I'm not sure, I'm not the author of the module and did not check how does it work. Try it anyway.
[Android Software/Hacking General [Developers Only]] jaggillararla:
Valdik for the pixel 2 xl files. Do I only need to replace the files In the lib64 and lib? Or do I need to do more? I will try to make a magisk module.

Also does the xl work with non xl pixel 2 ?
[Android Software/Hacking General [Developers Only]] d3vyarth:
It's not working
[Android Software/Hacking General [Developers Only]] ValdikSS:
These binary-patched files are device and firmware version specific. I recommend not to use any of these files for daily use. These files are only for testing Dual Channel mode with the headphones.
[Android Software/Hacking General [Developers Only]] SabinChhetri:
Anyway to get it work on Poco F1?
[Android Software/Hacking General [Developers Only]] ValdikSS:
Use LineageOS or Resurrection Remix build after 14 May 2019.
[Android Software/Hacking General [Developers Only]] rdsu:
Installed the latest LineageOs 16, on my smartphone, and try it with Tribit XBoom without success.

It seems Tribit XBoom doesn't support HD SBC...
[Android Software/Hacking General [Developers Only]] abhifx:
hi [MENTION=685332]ValdikSS[/MENTION]!

I have tested SBC HD on my chinese car stereo, It does show SBC HD support, However, the sound is distorted.

I tried this on an old device (Redmi Note 3 Pro Kenzo) with havoc OS as my current device is still stock.

Is there anything else that can be done to remove distortion and still achieve better than default SBC output as do believe that audio output in car stereo through bluetooth is definitely poor.

Further, In order to check if its not a device issue, i tested it on external bluetooth receiver which has no distortion at all.

Please advice.
[Android Software/Hacking General [Developers Only]] ValdikSS:
Have you tried Havoc OS build after 23 June (3 days ago)? Before that it had outdated patch. Or better try LineageOS, to make sure.

Most probably your car stereo is not compatible with Dual Channel mode.
[Android Software/Hacking General [Developers Only]] abhifx:
Thanks for suggestion! Havoc build is bit old and still does not have any build beyond 23 june for kenzo.

I will try Crdroid which is basically lineage + patches.

Btw thanks for the efforts, this is kind of a revolution no one is talking about and everything is open in the spirit of open source.
[Android Software/Hacking General [Developers Only]] ValdikSS:
https://issuetracker.google.com/issues/136342164 ← add stars here