This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Prague power profile.
Do I need it?
Well, better having than don't.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in there, if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a PRA-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay from the Downloads session.
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-PRA.apk
XDA:DevDB Information
[Overlay] Dil3mm4's Overlays for Prague Series devices (all variants), Device Specific App for the Huawei P8lite/P8 Lite
Contributors
Dil3mm4
Version Information
Status: Stable
Created 2018-06-26
Last Updated 2018-06-26
Definitely will be useful. Thanks a lot, Dil3mm4!
Hi Dil3mm4,
Thanks for your work, but I'm not sure what this app does exactly, will it help me for example with substratum themes? Thanks
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Graveen said:
Hi @Dil3mm4 let me understand correctly:
- i'm under LineageOS 14.1 (Haky86 version). Am i concerned with your fixes ?
- i plan to go to LOS 15.1. Should i flash LOS 15.1 before, then install your fixes ?
- if i can go to LOS15.1 from Prject Treble, what device should i choose ? A or A/B ? I assume this is ARM64.
Thank you VM back in the ROM selection after 1 year, and i have things to understand
Click to expand...
Click to collapse
Our device is arm64 A only (PRA-LX1 is my device)
If the APK is included in the rom u want to flash just run the command below, if not, after flashing just install the overlay according to the instructions. Have a nice day!
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
mannas said:
I will probably make a question that doesn't make sense since it's probably hardware related. But will this overlay add 5ghz support to our devices?
Click to expand...
Click to collapse
Nope
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
Hey Dilemma! I have an issue with all the Treble Roms. After listening to music for a while, the playback stops and I have to restart it, or when I plug a headphone in and then out, sound usually doesnt come out of the speaker. Will this overlay fix the issues I have with treble Roms? Thanks in advance
Please help with a little overlay
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
I don't have PRA, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Click to expand...
Click to collapse
Hello Dil3mm4.
Sorry to send you PM, i see after sending that's not ok. I really want to solve Overlay issue for my Huawei Fig-LX1.
I try to join Telegram group indicated by you but could not find it. Maybe is not existing anymore. So - my last chance is you to respond here.
I just want you to make an overlay for my phone to work better with Phusson Treble 8.1. Just tell me what files do you need and i will do it.
Maybe you answer me.
Thanks!
Hi, by fixing BLE, you mean bluetooth low energy, like huawei band, fossil Q ?
thanks
Thanks! U did great!
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Traceur017 said:
Hi
I've tried to install this file but after I've enter the code, it says system is readable only.
I've tried with adb shell and terminal(booth of them rooted) and it didn't work
I've even tried to mount system as rewritable but it didn't work.
I'm on Aex 6.6 latest version(and I was on PRA-LA1 8.0.0.370 C185 before i flashed this custom rom)
What should I do to fix this error?
Click to expand...
Click to collapse
install terminal emulator , put the .APK (be sure to rename the last build taking the -P ) in the mencioned directory but first run the following command:
su
mount -o remount,rw /vendor
after this you can run the command for the apk.
It worked for me. or at least.. didnt gave an error... so.. lolol
I think I've installed it correctly but How can I see changes? Nothing added!
Hello, I have a PAR-AL00 device. Can you make an overlay for me.and Telegram group @GSI_HI6250, I can't find it.Thank you verymuch.
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
I can't find it where is it?
artus777 said:
I don't understand, where is the overlay link?
Edit : Sorry, I didn't know it was in the download tab.
Click to expand...
Click to collapse
Is this overlay necessary under Lineage 18.1 (PRAGUE device and EMUI 8.0.0.390)?
@Dil3mm4 Thread closed! Please advise the moderators team (best via the report function) to re-open the thread when ready to provide a download link for this former DevDB thread.
Regards
Oswald Boelcke
Senior Moderator
Related
This thread was formerly "[ROM][9] LineageOS 16.0 + AOSPExtended + PixelExperience // personal builds" - yes, once again, the title can't fit the full names of all these ROMs :/
This thread hosts personal builds of LOS 16.0 and other Android 9 (Pie) ROMs for Mix 2, currently built from @wight554 's trees. Similar to Oreo, full credits to Wight and others behind the scene for the bringup, allowing us to build upon the awesome work.
Currently I build the following ROMs, usually monthly (in sync with security patch):
LineageOS 16.0
ResurrectionRemix 7
AOSPExtended 6
PixelExperience 9
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
...
What's working:
Everything?
Instructions:
Coming from official MIUI? Since the new encryption has been implemented, you only need to wipe (not format) /data.
Flash any Pie firmware (firmware Stable V10.4.1.0 recommended) for builds starting from May, or firmware Stable V10.0.2.0 otherwise.
Use official TWRP or OrangeFox.
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies to Pie
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "9" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
https://github.com/wight554/
About "official" status:
Currently I don't plan to apply for "official" for any of these ROMs, because 1) Wight is the actual maintainer who did the bringup and maintenance work, and 2) I like to be able to apply changes at will to the OS itself without restrictions from the official team.
Donation:
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 16.0, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, wight554, Cozzmy13
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V10.4.1.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2018-09-25
Last Updated 2019-09-27
Reserved
Just an additional note: I'm not as enthusiastic about building ROMs as I was early this year, so expect less regular updates and/or unanswered fix/feature requests. I'm just a builder, not nearly as capable of Demon or Wight doing all the heavy lifting, so I'll only do what my ability/time permits.
Thanks for all your work, Andy
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Fairtex said:
Works like a charm. Only thing I noticed that traffic on the status bar won't be displayed.
Click to expand...
Click to collapse
Statusbar customizations like network traffic aren't merged yet, just wait.
Can we have that slide down gesture to bring the notification bar down like we had in PE Oreo? Thanks
Hey,i have a question. Is it possible to port full screen gestures from miui 10 to los 16?
Are the quick settings on the status bar still a bit off on PE edition?
Folks who have tried, please do let me know about the battery consumption. This build added some CPU governors to the kernel and defaulted little cluster to one of them, and I'm not sure of its actual impact. It's my first time fiddling with kernels and I can't guarantee the change will be satisfactory.
Fairtex said:
Are the quick settings on the status bar still a bit off on PE edition?
Click to expand...
Click to collapse
I acknowledge the lack of padding there, but I don't quite want to look into it now. It's supposed be a problem for PE upstream anyway.
Greetings!
I've downloaded the rom last night. And until now, I have no problem: the camera works perfectly, the sound sound good and gaming performance are good.
The thing which attracted me was the mention of "Lineage OS" and I'm not disappointing to see that it's so close of the official and stable version . I'm blind in context of "find the bugs", so maybe we could find some but this is not my domain.
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Install custom navigation bar .Its work fine
Wysłane z mojego MI MIX 2 przy użyciu Tapatalka
jimmys121979 said:
Is it possible to have the full screen for apps in this rom? I mean the option without the bars on the top and the botom of the screen
Click to expand...
Click to collapse
Expanded Desktop is a feature that will surely be merged in the future. As the other user said, there are 3rd-party apps that can achieve the same goal. I myself am using Tiles since it places a shortcut in Quick Settings.
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
MrSammyMcG said:
Hi I haven't touched this kind of thing I'm a few months and I forget some of the finer details.
I have a few questions.
Firstly, do you have to add treble to your mix 2 to get this to run, or is that optional? If so can someone please send me a link to the thread. Would be greatly appreciated.
Secondly, I am on RR6 based on 8.1, if I just do a general wipe and flash the new ROM and gapps over the top, will this cause issues?
Lastly, I am on Icemans TWRP, do I HAVE to use the one suggested in the description (I did read it before someone yells at me, I just want to know if I HAVE to, because I'd need to set up ADB on a PC again and that would be a real pain in the behind).
Many thanks in advance as usual guys. Love your work and appreciate your patience and effort with this kind of thing. God bless
Click to expand...
Click to collapse
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
AndyYan said:
Treble is built into the ROM itself, you don't need to flash anything to achieve it.
Judging from the fact that you're using a super old TWRP though, you likely are on an old/unencrypted RR, and thus will need DecScript if you don't want to format /data (read OP).
That TWRP is MANDATORY, though most TWRP builds allows flashing images within ("install image" option), so you might not need a PC.
Click to expand...
Click to collapse
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
MrSammyMcG said:
That was really helpful thanks. I am running unencrypted and what do you mean treble is but into the rom? Is it old style with device drivers built in or will flashing the new ROM flash the drivers to whatever partition they have to go to and give me treble?
Click to expand...
Click to collapse
This is Treble-enabled but this is NOT a GSI (Generic System Image). You still flash as you would do a regular ROM, just with a Treble-enabled recovery.
Quick update to sync with Wight's updated battery data - from this build on you're supposed to use newer firmwares. OP has been updated with the mandatory new firmware requirement and TWRP build from Wight.
Thanks for your work,I have used aex for two days.It is very nice.But I notice a small problem that sometimes the fingerprint unlock is very slow and I have to touch several times to unlock it.Is it a bug of this rom?
Duble tap on screen for wake up dosent works too
LINEAGE OS
This is an Alpha build of lineageos15.1
Working:
-RIL
-Bluetooth
-Camera (at least 1 of them)
Not Working:
-Probably selinux (did not try enforcing kernel yet)
-Probably encryption (logcat says it works...)
-Wlan (maybe bcs some files from vendor/vendor_system in /system are missing)
-2nd camera (fix could be to use micamera app)
-Probably more
Instructions:
-Download V9.6.11.0.ODLMIFF_8.1 original rom
-go to V9.6.11.0.ODLMIFF/images
-Replace boot.img, with boot.img
-Replace system.img and system_other.img with system.img
-use the flash_all script. THIS WILL WIPE ALL YOUR DATA, EVERYTHING! if you want to go back now (or later) just put the original images back again and use flash_all_except_storage
-Directly after the device reboots by itself, press vol up + power (u might have to hold it until device reboots again) to enter los recovery
-"factory reset--> wipe data"
-If you want TWRP "advanced-->reboot bootloader" and flash TWRP accordingly to thread, then u can flash gapps/mods.
-reboot
-give it time to boot
Source:
ROM
Device branch "los15"
msm8953-device
Kernel
To finish, I WON'T CONTINUE THIS ROM the trees are working, P vendor is there, an adaption to los16 should be possible based on that. Also, i prefer OMNIROM (which i will try to build next).
Thanks goes to:
-Google for the search engine as well as for the source code
-Cozzmi13 for taking some time to show me the basics.
-Lineageos
-Github
-ada12 for offering his help
thankssss
im wait until wlan fix, but thanks for your effort
CreateYourDream said:
im wait until wlan fix, but thanks for your effort
Click to expand...
Click to collapse
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
It would be nice to have logs, then I could help.
If you ever need help with your omnirom build i would love to help out with everything that i can. Daisy really needs more support to be a very good device.
hi!
anyone know, is this build of LOS 15.1 support correct notch area?
and what about Onmi build?
i want give possible help if need)
Thanks for your work, I hope soon More roms for this great device
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
wertus33333 said:
I NEED TESTERS
I am building omni now, so cant go back to los and test but if someone can test i might be able to fix it.
TEST:
-download attached zip
-open on pc or device
-copy the files to the corresponding folder (the folder they are in) in "/system" with a root file manager or adb. CAREFUL do not overwrite files already existing. PLEASE only copy the things in etc (especially etc/firmware/wlan/prima/WCNSS_cfg.dat) first, reboot, check if working, if doesnt work, copy other things.
-set permissions accordingly to other files in same folder
-reboot and check if wifi works
Click to expand...
Click to collapse
not worked
and usb-tethering too
eremitein said:
sometimes after tapping screen blink with red border
Click to expand...
Click to collapse
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Can anyone give me the logs for the bugs?
Is this Rom abandoned?
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
Yup. This phone is abandoned in general, which is a shame
eremitein said:
ok, installed)
not work:
sound jack (and fm-radio because headset not detected);
notch not apply;
charger led;
wi-fi
bug: sometimes after tapping screen blink with red border
other thing worked in first try. quick and stable but it's very outdated)
.
Click to expand...
Click to collapse
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Nice to know: The blinking red borders show layout updates, they flash in all eng (=developer) builds. If changing the build variant to userdebug (debuging enabled) or user (oem/production builds with few debuging enabled) they vanish.
ghanipradita said:
Is this Rom abandoned?
Click to expand...
Click to collapse
kftX said:
Yup. This phone is abandoned in general, which is a shame
Click to expand...
Click to collapse
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience. Also, all of us do this in our spare time and therefore it can take time. If you want to speed up the build, supply logs (clean install rom, install adb on pc, execute
Code:
adb bugreport > bugreportDATE.txt
or
Code:
adb logcat > logcatDATE.txt
, share the reports), error descriptions (like @eremitein) and/or read on how to build a rom for a device yourself.
eremitein said:
I understood why this is happening
I saw the same behavior in the AEX build, which
used the build type "eng"
you also
Click to expand...
Click to collapse
oh, you already saw this xD
wertus33333 said:
Nope, it is not abandoned but we are very few people working on it and none of us has great android experience.
Click to expand...
Click to collapse
Editing this out of respect even though none was shown.
Also, I would love to help but with the lack of a proper working TWRP (encryption, restore backup issues) I really can't give it the time needed with all the stuff I'd have to reinstall every time, since I need my phone up and working nearly 100% of the time. If a decent version TWRP is released, I'll gladly help.
Glad you're still working on this though, just don't act like we should've known that you still where when the thread was dead for months. Good luck.
wertus33333 said:
Thanks for testing. saksham is working on a new build (with updated vendor, etc), will let you know if we need testers.
Click to expand...
Click to collapse
successful build, always happy to help
is there any reason you build los 15.1 instead of 16?
skyline91 said:
is there any reason you build los 15.1 instead of 16?
Click to expand...
Click to collapse
At the time i built the rom only 8.1 vendor (8.1 official rom) was avaiable. as i'm not really experienced with android it was easier to build 8.1 rom instead of trying to port vendor to 9.0 (while 9.0 vendor would have defenitely be officially out in a month or 2 ) and build los16. porting the device tree from 15.1 to 16.0 should be easy. Also, i don't like los, i want omni .
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
Click to expand...
Click to collapse
Images
Possibly the fastest [clean] ROM for our device, benchmarks coming soon .
Click to expand...
Click to collapse
Features
Google's exclusive features for Pixel devices (except Music Ticker and Call Screening)
Lawnchair launcher
Spoofed stock device to pass SN
Widevine L3
Faster encryption device-wide
Daydream VR
Fast, optimised Zest Kernel
EAS
Markup screenshot editing
Google Sound Picker
Google Wallpapers
Digital Wellbeing
Optimised GPU rendering for Pie
Custom Clang and GCC toolchains for building - optimised LLVM with PGO, and GCC 9.1
OpenGApps pico included
GCam HDR+ support
Click to expand...
Click to collapse
Installation instructions
* Go download https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-yoshino.
* Unzip the download to get an .img file.
* Install fastboot (drivers for this can be gotten from Google directly), drivers for flashmode for Windows can be gotten from newflasher.
* Enter your command prompt or terminal whatever and fastboot flash oem THEFILEYOUEXTRACTED.img.
* Find a decent TWRP and flash it.
* Download the ROM for your device. They are all in this folder https://jenkins.cosmic-os.org/job/zfsodp-core/ws/lastbuild so click the one for your codename (eg. G8141 is single sim maple and G8142 is dual sim maple).
* Flash it in TWRP and wipe internal storage and format data (the option that has red text and makes you type yes).
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is on my Jenkins job.
Click to expand...
Click to collapse
FAQ
PM me in XDA's Sony group.
Click to expand...
Click to collapse
Special Thanks To
Code:
* @kholk for his kernel advise
* @Sultanxda for his kernel advise
* @deletescape for Lawnchair
XDA:DevDB Information
Zest-flavoured SODP, ROM for the Sony Xperia XZ Premium
Contributors
LazerL0rd, The entire SODP team
Source Code: https://github.com/ZfSODP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Sony OSS OEM binaries
Based On: SODP
Version Information
Status: Beta
Beta Release Date: 2019-07-06
Created 2019-07-06
Last Updated 2019-08-10
Reserved
Reserved
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
del
Can I flash the kernel through twrp, then flash the zip?
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Give it a week or so mate, lazerl0rd is studying/having exams for a while.
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Any screenshot of the performance?
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
still on logo android !/
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Moarten said:
I was on latest stock when flashing (following every step), when it boots and show the sony logo, it gets distorted (characters in the top and middle) and then reboots. I've reflashed stock, wiped everything including system, tried older twrp, and even flashed the G8142 image on my G8141, but i keep getting the distorted sony logo followed by a reboot. Is there anything else i have to do?
I had this issue before with AOSP but i never figured out how to fix it.
G8141, unlocked bootloader, .80 stock, twrp 3.3.1.0 and 3.2.3.0
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too.
Laplacetor said:
nice, try tonight:good:
----------------------------------------------------------------------------------------------
HAVE BEEN DELETED, I don't know what happen, his own website and his kernel is also deleted.
I have the same as the #5, but a bit different, there were 4 identical page on the screen, such like 4 1080p in a 4k screen, I think the 120HZ 1080p display driver is the reason.
Click to expand...
Click to collapse
Psychoticism said:
Hey the Download Link is unavailable. Also your website is 404. I can't obtain your Kernel -OR- rom
Click to expand...
Click to collapse
Try again, a few of the previous builds were bootlooping, I'll try update instructions too. ROM isn't on my website and never was .
wolfmanstr said:
Can I flash the kernel through twrp, then flash the zip?
Click to expand...
Click to collapse
Don't use my stock kernel with this.
Sjll said:
Hey, have you tested the performance of EAS kernel ?
Could you please test the scores of GeekBench ?
BTW, you'd better remove the rqbalance in devices tree and disable cpu_quiet in kernel.
Besides, you need to replace the PowerHal in common. The PowerHal of SODP doesn't support EAS, you need to port it from Pixel 2.
All in all, well done!
Click to expand...
Click to collapse
It performs better, battery is decent now (after a load of changes). We now (as of today) have a Power HAL (libperfmgr) which supports DT2W on supported devices too. I may or may not update it to version 1.3.
SilverGamer_YT said:
Any screenshot of the performance?
Click to expand...
Click to collapse
No, it's EAS and you could test it out.
tronganhha29 said:
It was stopped at the android logo, it ran all night and did not enter the system. please help me!
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
CRNO said:
still on logo android !/
Click to expand...
Click to collapse
Yeah, I fixed that a while ago - try again please.
Laplacetor said:
SOME Screenshots here. driveDOTgoogleDOTcom/folderview?id=1rrF_kQA5sU_FIlXxERuZG0dxiX3xHn1m(Sorry but I cannot put link before I have 10 post)
It broken easily if screen off so please hold it on all the time.
With 120Hz all the gpu text showed obvious frame fluctuation.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now.
Sjll said:
EAS is not stable on SODP. GPU of MSM8998 is hard to afford 120Hz.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get lag" and like our phone can handle it on UI, at least. The worst case is battery but IIRC it wasn't too different from 60Hz. Anyways it's 90Hz now. EAS seems stable, here. The bugs we have aren't really EAS related.
undefine said:
Smooth, fast(20sec boot time including 5 second bootloader unlocked nag!) and clean rom thanks a lot! Sadly not going to be my daily driver because lack of features, and my device overheats sadly because of 120hz. Also it takes me 3 reboots to get into recovery any idea why?
Advices:
Get rid of pre installed google, allow users to install separately.
JamesDSP should be stabilized, I just get FC all time can't get it to work. (Would be better to just remove as well and allow user to install separately)
Default DPI is too low, should be 420 for ease of use.
Sony camera should be added, as in Sjll's LineageOS. ***
Ancient app logos (kitkat calendar calculator etc) should be updated.
Device-wide dark mode which includes Phone, Calendar, Settings and Files should be made. **
Phone application should be de-google-ified, Spam filter inside just feeds Google with private call data. ***
Option to switch resolution and frame rate on the go.
Click to expand...
Click to collapse
I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least. I changed up the thermal driver so it should be good now. Btw those thermal modules in Magisk won't change a thing as I use sultan's thermal framework now - not RQBalance stuff. DPI has an option on setup under "vision", choose what you like. I added GCam instead, it's gonna be better quality than Sony's crappy cam app. Ancient app logos aren't gonna be updated, these are ASOP packages - instead I'm replacing them with Google packages. Also I made everything Squircle shaped too. Device-wide dark mode will be coming soon, needs some kanging [with original authorship] from Q. Phone application should be de-google-ified -> you can turn off the spam filter and install any Dialer you want. I'm not dealing with darkening AOSP's package so that's why I'm using Googles. Google can get your data if Play Services is installed anyways. Option to switch resolution and frame rate on the go -> idk why SODP removed that.
Astoras said:
Heyo, wondering if you can add a quick and dirty CIFS kernel module. There are some universal versions floating around online.
Signing them is above my skill level. I don't know if the signing process has to be implemented on a device by device level. If that is an impediment, maybe consider removing the requirement for kernel modules to be signed in the first place? I don't know, I'm no expert.
Just a PSA. Someone got rclone mounts working via Magisk. Can be found in repo. Sadly, no support for cifs or nfs. But webDav works. The largest downside is that the mounts can't be mounted directly onto sdcard. Something the cifs kernel module did no problem. With rclone you'll need an app with root browsing capability. Or at least full access to /storage.
UPDATE: The rclone Magisk version has been updated to support direct sdcard mounts! Yay! So, there isn't really a need for a cifs module.
However, I'm certain the performance will be better with a cifs module. So, it's not necessary, but could be a cool benefit if added.
Thanks for all the work! It doesn't go unnoticed.
Click to expand...
Click to collapse
For Android kernels, you can't just chuck a module in. But I'll add it to the kernel config for ya.
CRNO said:
i hope you add other version special 90hz because 120hz make my device overheats and thank you
Click to expand...
Click to collapse
Already done. And - "I don't get all this 120Hz issue, it's not as simple as "set 120Hz get overheat" and like our phone can handle it on UI, at least."
Hi!
First: I am NOT a dev or contributor of this rom. Please visit before going ahead: https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4205461/
Second: You do anything at your own risk and should know how to recover a non booting device!
Just playing around with this rom on my SHT-AL09, tested on version 20210317 so far:
Working
- Mobile network including 4G (German carrier Telekom)
- Outgoing & Incoming calls
- Bluetooth
- 2,4 & 5g Wifi
- Front & Back camera
- Video recording
- MTP
- SDcard
- GPS (seems to be working on Telegram)
- Fingerprint reader
Not Working:
- Mobile network icon shows no signal strength
- VoLTE
- VoWIFI
How to install:
- Make a backup.
- Device needs to have bootloader unlocked.
- Visit the above link again --> sourceforge --> lineage-18.x and download version "...treble_arm64_bv*" + unpack it.
- Visit: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ (I have done it via bootloader method.)
How to update:
- Dont know yet.
Unfortunately I cant get TWRP to work, so I cant test gapps or root. If you have a clue, please let me know - thx!
So you tested a GSI Lineage ROM on the your M5, is it rooted? Should be great to see magisk included in any room, i use Phh treble Quack, it's pre-rooted with su.
Hi @massima
according to this post by one of the dev's Magisk is broken and supersu should be used instead. I can confirm that this works. You do not need working TRWP, just install the app from fdroid, as mentioned.
For me the rom works well, but as I use the tablet without gapps and only as a youtube player (YT Vanced works fine!), I have not really tested "real world szenarios" yet. Also I cannot say something regarding camera quality and battery performance in comparsion to the stock rom, as I went straigt to Linage 15.1 when I got the tablet in 2018.
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
massima said:
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
Click to expand...
Click to collapse
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
spoo333 said:
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
Click to expand...
Click to collapse
This is the link, just search your device mine is the M5 8" wifi (sht-w09). You can flash a vanilla (no gapps), the gapps version (be aware is Read Only). if you need a rewritable System partition download the vndklite version (arm64-AB-gapps-vndklite is 2,9Gb but it will not fit in the standard partition <2,9GB ).
I haven't ever tested the bluetooth so i can't say if it works.
Thanks for your reply and the link. I'll check it out if I can figure out the flashing etc.
Flashing seems relatively straightforward. Curious if Bluetooth works. Mine is the CMR-W09-C432
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Steffe89 said:
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Click to expand...
Click to collapse
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
toystory2000 said:
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
Click to expand...
Click to collapse
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Besuz said:
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Maybe.... According to many posts v21 brings stable magisk support to android 11 so that is a little contradictory....
Anyhow, I'm not really interested in root. I want try and see if magisk with universal patch could make root-hating apps and widewine L1 drm work.
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
Thanks a lot
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
spoo333 said:
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
Click to expand...
Click to collapse
sorry, meant to write: ... not "fastboot flash ramdisk patched_boot.img" but "fastboot flash recovery_ramdisk patched_boot.img"
I am not really sure that I did I correctly, but yes. I followed these instructions https://topjohnwu.github.io/Magisk/install.html#Huawei.
I think the problem is that I failed to remove phh-
Perhaps try again and check that you've got recovery_ramdisk as the target?
I'm also curious because I'm currently on Openkirin and would like to try what you've been doing. Currently have Magisk installed and wouldn't want to be without it because of Adaway etc.
Do you mind describing your steps: you had official Huawei 9.1 installed, then unlocked the bootloader, flashed Phhusson and then added Gapps?
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
massima said:
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
Click to expand...
Click to collapse
Massima, that's encouraging to hear re bluetooth. Hope Bluetooth headphones would work too...
HELLo everyone...
After several weeks, months and before Android 12 released, i decided to share this ROM to this A51 community. Hopefully you guys enjoy it and don't offend me if the ROM is bad, so....let's get it ON.
Things to do before flashing:
1. Make sure you're on binary 5 (this ROM tested and using binary 5 vendor, so to avoid any broken or whatever error flash your device with latest firmware).
2. Backup your IMEI (highly recommended).
Flashing:
1. Clean flash is recommended. Flash kernel, flash J4F vendor and system.img, flash multy disabler (if necessary) then full wipe and also you can perform "typing YES" format. Reboot to recovery again, then flash as usual you guys always do (Magisk etc.).
ROM Features from S20 and Note 20 line up:
1. Samsung Dex (not full features coz need fix at kernel level).
2. Flagship live blur
3. Flagship edge lighting style
4. AirCommand (S pen)
5. LiveDrawing
6. Multy screen resolutions (HD+ - FHD+ - WQHD+)
7. 1000++ system fonts
8. Flagship sound quality and effects
9. Camera features unlocked (pro video etc.)
10. All original A51 features
11. Common tweaks here and there and so many possibility to unlock another S20 features
Bugs:
Minor glitch in pro mode video, and not really remember and deep testing everything, but hopefully still acceptable (hopefully ) but yeah..nothing's perfect, if you found one let's discuss together in A51 telegram group: https://t.me/samsunga51
Hall of Fame:
@MrWaehere for his awesome CRB kitchen
@VDavid003 and his rom TreeUI for my inspiration and countless help
@Yillié and his OFox recovery and also countless help and advise and ideas
@BlassGO and his Dynamic Installer, patches, advise and countless contributions (thanks for making AirCommand even greater lol)
@manudinath and his projects.
@Winb33 for fonts mod
@topjohnwu for Magisk
@ianmacd for multy disabler and TWRP
Stock Kernel Source
PM me if i forgot to mention someone.
Advise and Tips:
- It's normal during first boot if lags occurs, give the ROM some times to settle, finish your setup, update your apps and you good to go..
- It's better to avoid update in Galaxy store related to system app, such as MDE Service Framework, Samsung Core Services etc. It might causing conflict due to mixed up firmware. But anyway it's up to you.
- Please do not complain regarding app missing (getting debloated) and related to debloat. Because it's very hard to acomodate every person's taste. Bloatware is very Objective and absurd for each person and I know it's supposed to be using Aroma installer or any script but i don't have time that much to do that.
Download link:
**when you click this link and downloading, that's mean you're agree to all the consequences and i'm not responsible to anything - do with your own risk**
LINK
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Yillié said:
Pero peeps. Sorry for not being able to test all the stuff properly xD.
Click to expand...
Click to collapse
nah, you have doing so great/ thank you s much for everything.
Testing .
perro
Ole its already, nice
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
Ia possible wirh This vendor run fingerprint perfectly in havoc
Badger50 said:
@jagpanzer Please check your PM inbox. Thank you.
-Regards: Badger50
Click to expand...
Click to collapse
If run for You send details my friend
Someone knows how to pass CTSprofile in magisk with this rom?
gobblefunk said:
Quick question, what am i supposed to select while flashing J4F.img in TWRP, boot, recovery, optics img, prism img or super.
Click to expand...
Click to collapse
system and vendor.
BlassGO said:
Ole its already, nice
Click to expand...
Click to collapse
mhm...thanks for everything
jagpanzer said:
system and vendor.
Click to expand...
Click to collapse
Kernel 11 support this ROM?
Magisk 23.1
Download Magisk 706a4922 alpha apk
Download File Magisk 706a4922 alpha apk
apkadmin.com
Changelog magisk 23.1
DOWNLOAD VERSion ALPHA:
Magisk v23.1 (706a4922-alpha)
Changelog:
• Switch to zygisk to execute the deny list,
• Magiskhide has been completely removed
• Denylist Added
• Restart to take effect after changing the switch state of zygisk
• Major changes, some problems may occur, temporarily not pushed to the update channel
Others changes in APK:
[General] supports pure 64-bit devices
-[General] Support Android 12 emulator
-[Zygisk] code injection framework
-[General] Remove MagiskHide
-[General] Support simulator loading module
-[MagiskBoot] supports zImage format
-[MagiskBoot] Add zopfli encoder
-[MagiskInit] supports boot configuration
-[App] Repair installation function will now check whether the script under /data/adb/magisk/ is not updated
-[MagiskInit] supports some Meizu devices
-[MagiskSU] If supported by the kernel, use isolated devpts
-[MagiskSU] Fix pts configuration code, no additional sepolicy rules are now required
-[MagiskBoot] supports v4 boot image header format
-[MagiskInit] Support some OnePlus and Opal devices Oplus.fstab
-[App] The update module needs to be restarted, mark deletion is not allowed
-[App] Delete online warehouse
-[App] Add mount information to the saved log file
-[App] Adapt to Android 12 API level
-[App] Display running waiting pop-up window when hiding/resuming the application
-[Stub] Open source obfuscation function
-[Script] View and display the sepolicy rule folder of the module
-【App】Hide the screen overlay when you need to pop up the window. Android 12+
-[App] Delete the floating bottom bar and change it to a general bottom operation bar
-[General] Support compilation cache
-[General] Added rejection list function
-[App] Delete DoH
-[App] Delete SafetyNet
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Bluetooth connect error
hacker812c said:
Kernel 11 support this ROM?
Click to expand...
Click to collapse
during testing i only test with BF2. you can try
Arya1999 said:
Can you please also make this rom for M30s ??
Because both have similar specs and same soc !
Click to expand...
Click to collapse
sorry, no time.
Inomjon6940🇺🇿 said:
Bluetooth connect error
Click to expand...
Click to collapse
last time i try with old BT 4.0 earphone was fine and also BT call. will test again, on last build i've made changes and could be broke something