Skip to content

Instantly share code, notes, and snippets.

View ThEMarD's full-sized avatar

Marc Bourgoin ThEMarD

  • Alberta, Canada eh?
View GitHub Profile
@ThEMarD
ThEMarD / after_patch_open_gapps_log
Created October 20, 2018 05:19
OpenGapps /vendor/build.prop patch, before and after https://github.com/opengapps/opengapps/pull/676
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 9
ROM Build ID | lineage_x2-userdebug 9 PPR2.181005.003 1cdc875df4 test-keys
ROM Version increment | 1cdc875df4
ROM SDK version | 28
ROM/Recovery modversion | 16.0-20181018-UNOFFICIAL-x2
Device Recovery | TWRP 3.2.3-1-32aef7a2
Device Name | le_x2
Device Model | x2
@ThEMarD
ThEMarD / gist:cd31bb69731ef004891b128832ed92c3
Last active April 5, 2023 14:00
How to logcat Audio stuff from stock ROMs
Some stock ROMs don't want you using audio logcat level 7 which is required for the audio logs... so for that? You'll need to root your stock ROM with something like Magisk and then use adb with these commands:
adb shell
su
stop
setprop sys.init_log_level 7
logcat -G 4M
start
exit
@ThEMarD
ThEMarD / gist:0d6041fd38d6147e99130307e094f807
Last active May 8, 2023 04:36
How to use acdb_get & get_snd_names
First you'll need to clone acdb_extract. I used the one by J510-Dev which is originally based on the one by luca020400.
git clone https://github.com/J510-Dev/acdb_extract
Then, as the README says you must generate the acdb header. For Qualcomm devices? The stock audio hal would be audio.primary.msm8996.so which is found on my stock ROM from /system/lib/hw/audio.primary.msm8996.so which I could just copy into the acdb_get folder... so for example, I'd use this:
./generate_acdb_data.sh audio.primary.msm8996.so
which will generate a file called acdb_data.h which is needed for the next step.
Since acdb_extract doesn't require being built in the AOSP environment? You can just build it using...
@ThEMarD
ThEMarD / System Information
Created May 25, 2019 19:26
Steam on Linux Mint
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
CPU Family: 0x6
@ThEMarD
ThEMarD / gist:f3df65b91c8cf58c685a70b044060d7e
Created August 22, 2019 02:37
Older method to doing perfect kangs with extract-files.sh script
Create a dummy folder to Kang blobs like
device/dummy/dummy
Then copy proprietary-files.txt, extract-files.sh and setup-makefiles.sh from any device. A device that doesn't use a shared commonized device tree does make it easier.
Rename the stuff in the two .sh files to dummy as vendor and device name.
Update necessary proprietary-files in dunmy device tree for kang
@ThEMarD
ThEMarD / build.prop
Created December 25, 2019 19:38
s2 eui rom 30s build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.letv.release.tag=
ro.letv.product.info=
ro.letv.release.branch=s2_stable_5.9_20161010
ro.letv.release.date=2018-09-09
ro.letv.eui=5.9
ro.letv.release.version=6.0.030S
ro.le.mtpname=Le 2
@ThEMarD
ThEMarD / build.prop
Created December 26, 2019 02:14
x2 EUI ROM 30s
# begin build properties
# autogenerated by buildinfo.sh
ro.letv.release.branch=ruby_dev_leui
ro.letv.release.version=6.0.030S
ro.letv.release.version_date=5.8.001D_09093
ro.product.letv_model=Le X820
ro.product.letv_name=乐Max2
ro.build.id=FEXCNFN6003009092S
ro.build.display.id=FEXCNFN6003009092S release-keys
@ThEMarD
ThEMarD / build.prop
Created December 26, 2019 02:14
zl1 EUI ROM 30s
# begin build properties
# autogenerated by buildinfo.sh
ro.letv.release.branch=ruby_dev_leui
ro.letv.release.version=6.0.030S
ro.letv.release.version_date=5.8.001D_09093
ro.product.letv_model=
ro.product.letv_name=
ro.build.id=WAXCNFN6003009091S
ro.build.display.id=WAXCNFN6003009091S release-keys
@ThEMarD
ThEMarD / Regen vendor blobs
Last active May 8, 2023 04:42
Regen vendor blobs
Make sure the device's and/or commonized device proprietary-files are updated with the same blobs that you want in your proprietary vendor repo.
In my example, I'll use the LeEco Le Max 2 (x2), so I would then copy the current LeEco msm8996-common and then x2 blobs (just to clarify, I mean the blobs themselves within the proprietary folder) to the desktop in a folder named vendorblobs
Then open terminal in the device tree and...
./extract-files.sh ~/Desktop/vendorblobs/ | tee ~/Desktop/extractor.log
Check extractor.log to ensure it worked ok and there was no errors / not found.
@ThEMarD
ThEMarD / Update Ubuntu's platform-tools package manually.txt
Last active November 3, 2023 20:09
Update Ubuntu's platform-tools package manually
If you've installed adb and fastboot via apt install on Ubuntu and realize they're old versions, then here is how to manually update them.
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/lib/android-sdk/platform-tools/
sudo cp platform-tools/fastboot /usr/lib/android-sdk/platform-tools/
check that it worked with:
adb --version