Forwarded from Amir
Kind of beta build?
device:
* re-enable google photos spoof (YAAP official has it disabled)
* enable IO prefetch (not sure how well or if it works)
* disable proximity check for sensors (dt2w, fod)
* enable increased touch sensitivity, this simply turns on game mode with '1 2 2 0' setting (thanks to Barny Syberia dev)
- Option for this under Display settings
* fixed fingerprint down ripple anim (thanks to RealJohnGalt YAAP dev)
* switch to qcom common adreno and media blobs (OpenGL driver version now 0530.46)
* enable proximity sensor during AOD, screen will turn off now if in pocket while AOD
* checkout xiaomiparts to penglezos' and bring back HBM and DC dim settings
* few other minor changes https://github.com/pwnrazr/device_xiaomi_raphael/commits/thirteen
kernel:
https://github.com/pwnrazr/kernel_raphael_sm8150/commits/inline-casefold-erofs
test:
Anything related to media (videos, HDR)
Games
pickup gestures
Due to new blobs and different xiaomiparts you will likely need to flash package cache and shader cache cleaner or run command:
Shader cache:
device:
* re-enable google photos spoof (YAAP official has it disabled)
* enable IO prefetch (not sure how well or if it works)
* disable proximity check for sensors (dt2w, fod)
* enable increased touch sensitivity, this simply turns on game mode with '1 2 2 0' setting (thanks to Barny Syberia dev)
- Option for this under Display settings
* fixed fingerprint down ripple anim (thanks to RealJohnGalt YAAP dev)
* switch to qcom common adreno and media blobs (OpenGL driver version now 0530.46)
* enable proximity sensor during AOD, screen will turn off now if in pocket while AOD
* checkout xiaomiparts to penglezos' and bring back HBM and DC dim settings
* few other minor changes https://github.com/pwnrazr/device_xiaomi_raphael/commits/thirteen
kernel:
https://github.com/pwnrazr/kernel_raphael_sm8150/commits/inline-casefold-erofs
test:
Anything related to media (videos, HDR)
Games
pickup gestures
Due to new blobs and different xiaomiparts you will likely need to flash package cache and shader cache cleaner or run command:
Shader cache:
for i in "$(find /data -type f -name '*shader*')"; doPackage cache:
rm -f $i
done
rm -rf /data/system/package_cache
Forwarded from Amir
Forwarded from Muhammad Al-Arabi 🇧🇩
There are two ways you can get logs.
The non-rooted way (you will need a PC)
1. Download the latest platform-tools for your operating system
• Windows
• Linux
2. Extract the zip to a folder and move into that folder in Command Prompt or Terminal:
3. Plug in your device and accept the debugging prompt (turn on ADB in Settings > Developer Options if you don't see it).
4. Verify your device is recognized by typing
5. Take your log:
• logcat:
• dmesg:
6. Send the logs here and tag the maintainer.
The rooted way
1. Install termux or any other terminal app
2. Type
3. Type
4. Take your log:
• logcat:
• dmesg:
5. Send the logs here.
Other way
= HOW TO TAKE LOGS =
[ if rom stuck on boot animation or need regular logs ]
0. in twrp mount System and delete file /system/phh/secure and then reboot
1. while you see bootanimation connect phone to PC
2. adb logcat -d all > logs.txt
[ if rom not allowing adb (device unauthorized) ]
0. reboot to twrp
1. connect phone to the PC
2. run command from
*nix: adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
windows: adb push C:\Users\%PutHereYourUsername%\.android\adbkey.pub /data/misc/adb/adb_keys
3. now you can take logcat logs
[ if phone stuck/bootloop at splash ]
0. reboot to twrp right after stuck-splash or bootloop
1. try to find that logs:
/sys/fs/pstore/console-ramoops
/proc/last_kmsg
/proc/kmsg
2. copy logs to PC
(for sample, with command "adb pull /proc/last_kmsg lastkmsg.txt")
Or get logs without pc using this app:
https://play.google.com/store/apps/details?id=com.tortel.syslog
The non-rooted way (you will need a PC)
1. Download the latest platform-tools for your operating system
• Windows
• Linux
2. Extract the zip to a folder and move into that folder in Command Prompt or Terminal:
cd <folder_location>
3. Plug in your device and accept the debugging prompt (turn on ADB in Settings > Developer Options if you don't see it).
4. Verify your device is recognized by typing
adb devices
5. Take your log:
• logcat:
adb logcat -d > test.log
• dmesg:
adb shell dmesg >
dmesg
6. Send the logs here and tag the maintainer.
The rooted way
1. Install termux or any other terminal app
2. Type
su
3. Type
cd /sdcard
4. Take your log:
• logcat:
logcat -d > logcat.log
• dmesg:
dmesg >
dmesg5. Send the logs here.
Other way
= HOW TO TAKE LOGS =
[ if rom stuck on boot animation or need regular logs ]
0. in twrp mount System and delete file /system/phh/secure and then reboot
1. while you see bootanimation connect phone to PC
2. adb logcat -d all > logs.txt
[ if rom not allowing adb (device unauthorized) ]
0. reboot to twrp
1. connect phone to the PC
2. run command from
*nix: adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
windows: adb push C:\Users\%PutHereYourUsername%\.android\adbkey.pub /data/misc/adb/adb_keys
3. now you can take logcat logs
[ if phone stuck/bootloop at splash ]
0. reboot to twrp right after stuck-splash or bootloop
1. try to find that logs:
/sys/fs/pstore/console-ramoops
/proc/last_kmsg
/proc/kmsg
2. copy logs to PC
(for sample, with command "adb pull /proc/last_kmsg lastkmsg.txt")
Or get logs without pc using this app:
https://play.google.com/store/apps/details?id=com.tortel.syslog
👍4❤1👎1
WAFFLES-230312_113810-4a57e9abf7.zip
18.7 MB
new fod implementation
wont work on syberia or evo as tested by users
Edit: works on syberia and Evo now as confirmed by users
wont work on syberia or evo as tested by users
Edit: works on syberia and Evo now as confirmed by users
❤12🔥3