Hi mates, after some testing i have made a patch to get working IR in roms wich doesnt have it included.
Need selinux permissive or Sepolicy exception with enforcing
ROM maintainers need to enable HSL in kernel
Installation:
-Flash with Twrp
-Nothing more
Download:
-Patch (Updated 26-05-2017)
I'm on Omni though, but still....the same as before, it crashes upon updating....sorry if not helpful, thanks for your effort
Just scanned through logcat, first sign of trouble is once again "no permission on read/write serial port".
I will enable the serial port in next build
Sent from my LEX720 using Tapatalk
It says: "Unable to Initialize" on AOKP how to do you about updating after flashing it through TWRP
Nice work! Thanks!
Installing on AOSPExtended with Black Screen 1.8.5 worked. But after doing the update of the app I had also "Unable to Initialize" and it was not possible to pair with any device. There is no option for it.
Hi,
I have installed it with your RR rom on my x720, but unfortunately it doesn't work and also I don't get any bug message at the first time.
It opens normally but at universal remote it doesn't record any data from IR sensor.
smae said:
Hi,
I have installed it with your RR rom on my x720, but unfortunately it doesn't work and also I don't get any bug message at the first time.
It opens normally but at universal remote it doesn't record any data from IR sensor.
Click to expand...
Click to collapse
Clean data and cache of the app and open again
Updated
villarleg said:
Updated
Click to expand...
Click to collapse
Now it is fully working...
Thanks a looot :good:
Hi. How do I move remote app data for other Rom?
Sorry for my bad English.
Tapatalkkal küldve az én LEX720 eszközömről
bankizsolt said:
Hi. How do I move remote app data for other Rom?
Sorry for my bad English.
Tapatalkkal küldve az én LEX720 eszközömről
Click to expand...
Click to collapse
Backup both Remote Control and UEI Android services SDK(LeTV) using Titanium backup and restore them (Data only) in the new rom (after installing the patch using twrp).
Any one test this patch on LineageOS 14.1 Rom?
How ti enable hsl in kernel?
I'm on LOS 14.1 and it says unable ti initialize
sweetboy02125 said:
Any one test this patch on LineageOS 14.1 Rom?
Click to expand...
Click to collapse
danielexda said:
How ti enable hsl in kernel?
I'm on LOS 14.1 and it says unable ti initialize
Click to expand...
Click to collapse
Enable HSL its for devs only, i think lineage doesnt have it enabled in kernel, so you need to flash another kernel and change selinux to permissive
Can I turn this to permissive by kernel audiutor?
villarleg said:
Enable HSL its for devs only, i think lineage doesnt have it enabled in kernel, so you need to flash another kernel and change selinux to permissive
Click to expand...
Click to collapse
danielexda said:
Can I turn this to permissive by kernel audiutor?
Click to expand...
Click to collapse
Flashing another kernel will change it to permissive (if it's a permissive kernel), and if it's an enforcing kernel it'll have the selinux patches so there's no need to change it to permissive yourself, just flashing the kernel is enough
I change ti permissive by an apk bit it doesn't funciton
danielexda said:
I change ti permissive by an apk bit it doesn't funciton
Click to expand...
Click to collapse
Your kernel needs to have the serial port patch
Can you tell me which kernel i have to install?
Related
SM-N910F - Stock Kernel
Root Android 5.1.1
We have here 2 kernel variants
Original Samsung SE enforced kernel, repacked with a patched sepolicy through SuperSU 2.50
- Recommended kernel as it runs in enforced mode if you are concerned about security
- Recommended method by Chainfire
- Supports only SuperSU 2.50 app for root
- You must update to SuperSU 2.50 before flashing kernel or you end up in a bootloop
- TIMA SecurityLogAgent service still needs to be freezed
- Selinux runs in enforced mode
- Private mode can be used
Click to expand...
Click to collapse
Compiled from stock sources permissive kernel, with NTFS support
- huge drop in security, as it runs in permissive mode
- will allow you to run any superuser app
- supports ntfs mount (needs NTFS helper for the mount ntfs binary or get them from xda or from download link
- selinux is forced to permissive because of new Android 5.1.1 restrictions
- Private mode relies on Selinux and can no more be enabled
- TIMA SecurityLogAgent service needs to be freezed as new Android 5.1.1 detects changes in kernel/SE and warns you about them
Click to expand...
Click to collapse
Why a custom kernel or a modified boot image will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
In permissive mode, it is impossible to use any KNOX protected features and system will triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007. That's why those services must be disabled.
Seems it is not Samsung to blame, but really Google.
Chainfire came with a new approach to avoid compiling the kernel and to be able to run in enforced mode: patching the sepolicy in ramdisk to allow root while still running a stock enforced kernel. This needs version 2.50+ of SuperSU, and won't support, currently, any other root application. This needs a complex procedure documented by Chainfire. It needs rooting the reference device under 4.4 - 5.0.1 enforced mode, patching the 5.1.1 sepolicy under that reference device and export the patched sepolicy to the 5.5.1 boot image of the device. The good part is that we only need to repack boot image with a changed sepolicy, without modifying anything else, mainly the kernel.
Credits
@Chenglu
@Chainfire
Emotroid-Team
XDA:DevDB Information
Android 5.1.1 Kernel, Stock, Root, Enforced and Permissive, Kernel for the Samsung Galaxy Note 4
Contributors
Phil3759
Kernel Special Features: stock, enables root for 5.1.1
Version Information
Status: Stable
Created 2015-09-23
Last Updated 2015-10-30
Download + source diff
- flash kernel in recovery (zip) or odin (tar)
- flash SuperSU v2.50+ for enforced kernel or any root app for permissive kernel
Link:
https://mega.nz/#F!RV8wGT6C!rsfnBrjuqukBNLgLxIgNIA
More original third party releases by @_alexndr (untested by me): https://www.androidfilehost.com/?w=files&flid=45166
FAQ and fixes
How to fix the security notice popup for the permissive recompiled kernels ?
Using Titanium backup, freeze this service: SecurityLogAgent
How to fix Screen Mirroring after root for permissive kernels ?
This is not related to the kernel, but affects some Samsung devices with root
For the fix, check here: http://forum.xda-developers.com/showpost.php?p=63004244&postcount=11
How to fix my wifi passwords not saved on reboot / wifi disconnect for permissive kernels ?
Add this line in /system/build.prop
Code:
ro.securestorage.support=false
What changes are done to the permissive kernel before compiling?
selinux permissive to enable root
NTFS stock Samsung implementation enabled in kernel (needs OTG helper probably)
History changes for permissive kernels
v1.0
N910P-VPU4COG5 kernel sources + N910F-XXU1COH4 ramdisk
v1.1
revert properties to defaults: if you have issues saving wifi passwords, add this line to /system/build.prop or revert to 1.0
v2.0
N910-F latest stock sources
back to ro.securestorage.support=false for wifi password issues in permissive mode
Click to expand...
Click to collapse
Sources:
post 2 with download link
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
antz_77 said:
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
Click to expand...
Click to collapse
added a zip file
Which App for Root can i use for example?
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
patensas said:
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
Click to expand...
Click to collapse
PhilZ Touch 6.59.0 works perfectly with 5.1.1 by the way, even time with Time Daemon load
Why a custom kernel will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
So, for now, and maybe also in near future, no other way to root will be possible except using a custom kernel in a selinux permissive state. Sure some vulnerabilities could be found and used, but will probably be patched by Google.
Seems it is not Samsung to blame, but really Google.
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
parisien99 said:
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
Click to expand...
Click to collapse
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
robotnikz said:
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
Click to expand...
Click to collapse
Not related to the custom kernel
http://forum.xda-developers.com/showpost.php?p=61396065&postcount=66
Or just do this:
In build.prop, add this line and reboot device
Code:
wlan.wfd.hdcp=disable
It works perfectly with my Samsung Smart TV
[N910F][Kernel][Stock][Root] Android Stock 5.1.1 Kernel for root
Hi !
Thank you @Phil.
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Guillaume59610 said:
Hi !
Thank you
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Click to expand...
Click to collapse
I didn't test, but normally, there are no significant changes between those micro letters. Probably just the branded stuff
Can you upload stock boot.img from COI3 ? I will look at it then
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Guillaume59610 said:
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Click to expand...
Click to collapse
ramdisk changes don't seem relevant
Until we have new kernel sources for N910F, there is no need to recompile
I am using it heavily since a few days without any issue or bug I could spot
Ok, thanks @Phil !
only for F
cant't work on 910C ?
crazydeepman said:
only for F
cant't work on 910C ?
Click to expand...
Click to collapse
No way. The 910C use exynos chip. You have to request on exynos subforum.
"If it compiles, it is good, if it boots up it is perfect"
Best kernel I have seen, until now! - Works without any problems also with German (DBT) ROM: N910FXXU1COI3, that also contains final fixes for StageFright and a better fingerprint support.
THX Phil!
P.S.: Every update is welcome...
Added some info in post 1 on what changed in Android 5.0 that probably will make it near impossible to root a stock ROM while having even the option to run in enforced mode when needed. Any other way that could be found in the future will mean using kernel vulnerabilities. This obviously will be fixed asap by google. At the end, it will be probably simpler and safer (stability wise) to choose between root and a selinux enforced device, not both
This also makes it impossible to use any KNOX protected features and triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007
That's why those services must be disabled
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
Click to expand...
Click to collapse
LeEco Letv Remote Control App flashable zip download : https://www.androidfilehost.com/?fid=889764386195898642
Make Sure your Selinux Mode is Permissive.
Does this work on Lineage?
SCrid2000 said:
Does this work on Lineage?
Click to expand...
Click to collapse
Yes
Can this be used on any rom ?
bhai cnt select settop box it say select state or city that comes written in chinese hel plz hehe
AjaYKumaR91240 said:
bhai cnt select settop box it say select state or city that comes written in chinese hel plz hehe
Click to expand...
Click to collapse
And me, I get it with every version I ve tried, the only time I could get a non Chinese set top box list was on the factory ROM.
Its working perfect,Could you port camera as well..!!?
does it work on Resurrection Remix ROM?
Sauravk554 said:
does it work on Resurrection Remix ROM?
Click to expand...
Click to collapse
Yes and no - RR comes with Letv remote already, but for cable boxes I can only get a list of Chinese regions, whether I use the version that RR comes with or the one in this thread.
I can't flash it
I'm using Resurrection Remix 5.8.3 on my Samsung Galaxy grand.
Edit: successfully flashed on my redmi note 3
zaza remote works perfectly is is better than leeco's remote app
rohitjaiswal said:
Make Sure your Selinux Mode is Permissive.
Click to expand...
Click to collapse
How do I set selinux to permissive? I am running LineageOS 14.1
Its not working for RR 5.8.3,I guess its not working because I can't change selinux from enforcing to permissive.How do I unzip this Remote file?
raj8655 said:
Its not working for RR 5.8.3,I guess its not working because I can't change selinux from enforcing to permissive.How do I unzip this Remote file?
Click to expand...
Click to collapse
Y dou need to unzip just flash the zip file using twrp
hkee96 said:
Y dou need to unzip just flash the zip file using twrp
Click to expand...
Click to collapse
Because I don't need that app,how can I remove that?
raj8655 said:
Because I don't need that app,how can I remove that?
Click to expand...
Click to collapse
Use system app removers like uninstall from ps
This works very well on Lineage 14.1, but I have a question...! Why Selinux Mode need to be Permissive?
I found this apk of letv remote control. It works without root and can be used to connect leeco tv.
Use the link below.
http://download.scloud.letv.com/remotecontrol/api/v1/jump
chinese remote
Has anyone else had this app randomly lose their remotes when they update Lineage?
I have long sought a way to pass the safetynet. Finally I found a solution. I found a project made for Xiaomi Mi5 and i have ported it on Leeco Le Pro3.
Original Project by @coronafire : https://forum.xda-developers.com/mi-5/how-to/mi-5-passing-safetynet-unlocked-t3557845
Actually i have made the mod only for Le Max 2 and Le Pro 3. I have tested only on Le Max 2, because i have no Leeco device in this moment and I someone have test it on Le Pro 3 with succes ( ZIP4). This mod will not work if you have xposed on your phone.
I have built a github project and if you want you can add more Leeco device.
Github Project: https://github.com/mauronofrio/magisk-leeco-safetynet-props/tree/master
What this mod do?
- This mod set some props and enable magisk hide (If you don't enable magisk hide your phone can't pass Safetynet check). This mod will survive future updates and in general it will survive if you don't make a wipe data.
How to install:
You need to have already installed magisk on your phone. You can find it on official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk direct link: http://tiny.cc/latestmagisk
Just download the zip and flash it in TWRP
DOWNLOAD
Safetynet Pass for Le Pro 3 (Zip 4) MEGA
Safetynet Pass for Le Pro 3 (Zip 4) AFH
If you test it please comment and/or give me a feedback
Sorry for a dumb question, but I assume you need to install magisk first?
Sent from my LEX727 using XDA Labs
llblwskydrgn said:
Sorry for a dumb question, but I assume you need to install magisk first?
Sent from my LEX727 using XDA Labs
Click to expand...
Click to collapse
Yes, i forget to write it
I'm on AICP, which have default Magisk. Downloaded lastest version from Play Store. On settings of Magisk I have "Magisk Hide", which make "SafetyNet Correct".
marik1 said:
I'm on AICP, which have default Magisk. Downloaded lastest version from Play Store. On settings of Magisk I have "Magisk Hide", which make "SafetyNet Correct".
Click to expand...
Click to collapse
Yes but on rom stock based you need of this zip to pass safetynet check
Does this also work on Lineage OS?
Moritz Bayerl said:
Does this also work on Lineage OS?
Click to expand...
Click to collapse
Yes
First of all thank you very much. I'll try that in a second.
---------- Post added at 10:50 AM ---------- Previous post was at 10:44 AM ----------
Alright so I just installed it but still the cts profile check fails.
I guess I'll need another kernel.
mauronofrio said:
Yes
Click to expand...
Click to collapse
Does it mean I can use Android Pay with LineageOS?
sweetboy02125 said:
Does it mean I can use Android Pay with LineageOS?
Click to expand...
Click to collapse
Yes
Sadly it just don't work for me. Any ideas?
Moritz Bayerl said:
Sadly it just don't work for me. Any ideas?
Click to expand...
Click to collapse
What rom do you have? Do you have magisk installed? Do you have xposed installed?
Magisk installed on lineage os 7.1.2 and no xposed
Moritz Bayerl said:
Magisk installed on lineage os 7.1.1 and no xposed
Click to expand...
Click to collapse
I don't know why.
It says that cts profile would not match
Moritz Bayerl said:
It says that cts profile would not match
Click to expand...
Click to collapse
MMM but you have only magisk on your phone or you also have superuser? If you have both is normale that you have cts mismatch
mauronofrio said:
Yes
Click to expand...
Click to collapse
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
sweetboy02125 said:
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
Click to expand...
Click to collapse
This is a permanent fix. You will lose it only if you make a wipe data or unistall magisk
sweetboy02125 said:
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
Click to expand...
Click to collapse
Tell me if you try this mod and if it works
Moritz Bayerl said:
It says that cts profile would not match
Click to expand...
Click to collapse
I have made another zip, try this: https://mega.nz/#!cA1TUBQb!5vDJKFjPq3lTVqFZxopHGc-YWWoJzW4KhSZjPiIsnFg
Here are patch sets for speaker working on ze60xkl pie ROMs
<Link>
ZE600KL : http://www.mediafire.com/folder/5l0hwa9n7aice/ze600kl
ZE601KL : http://www.mediafire.com/folder/r8wbjbqjjh46j/ze601kl
<Notice>
These patch sets are only for ZE60xKL model on pie custom rom users.
DO NOT apply these for other models or Andoroid versions.
<Patch Files>
1) Kernel Packages (be careful for mistaking model).
- ze600kl-spk-pie-kernel-v1.zip (for ZE600KL(Z00L))
- ze601kl-spk-pie-kernel-v1.zip (for ZE601KL(Z00T))
2) ze60xkl-spk-pie-libs-v1-01.zip (for both ZE600KL and ZE601KL)
<Install Instructions>
1. Download 2 patches (#1 and #2) to any folder
2. Reboot recovery (TWRP)
3. Flash 2 files
4. Reboot system and you can fun sound from device
<Tested Roms>
- Lineage OS
- CrDroid
- AEX
<Features>
- Add speaker sound stream to your rom
- Stereo mic support
<Known Issue>
- Noisy sound with bluetooth and enabling reverb
<Source Code>
https://github.com/zekken1977?tab=repositories
<Change log>
[2019-05-05: v1.0]
- Add tfa9887 driver
[2019-05-26: v1.01]
- Rebased on firekernel r2.10
Finally thank you for helping to test my patch
@Rayonecma, @celtic1453, @fabricio6791 and @ndrancs
First Release On : 2019-05-05
Last Update On : 2019-05-26
Τhanks
Works ok for the ZE600KL
Sent from my MI PAD 4 using Tapatalk
test on ze601kl... working friend
And... For my ze601kl it's working too... ???
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
fabricio6791 said:
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
Click to expand...
Click to collapse
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Ze60xkl sound patch
Thx a lot, i've made patch for oreo, but i didn't find any time to work on the pie version .
Great job !!!
You are awesome! Thank you for this work ^-^
zekken1977 said:
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Click to expand...
Click to collapse
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
[email protected] said:
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
Click to expand...
Click to collapse
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
zekken1977 said:
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
Click to expand...
Click to collapse
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
zekken1977 said:
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
Click to expand...
Click to collapse
I guess, the Devs will implement this driver in to their ROM. But it is more prudent to have a Patch (Like we had upto Oreo). Reason being, there are tens of ROMS. Convincing each dev will be counter productive. The patch can be applied more efficiently.
We'll have to wait and see when the SEPolicy enforcement occurs.
About update patch
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Workaround
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
zekken1977 said:
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Click to expand...
Click to collapse
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Superbezo said:
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Click to expand...
Click to collapse
OK. I'll update but next version will be available on this weekend.
And about source code, please see the link in my 1st post
Thanks
Can you make sound patch for Zenfone Selfie Z00UD (Z00T)?
Because I will try this rom (https://forum.xda-developers.com/zenfone-2-laser/development/rom-prometheusoneui-z00t-t3929198) to my Zenfone Selfie Z00UD (Z00T), but the sound patch only for Zenfone 2 Laser ZE601KL (Z00T). Thanks in advance!
ManOfFeel said:
Zenfone Selfie did not have speaker issue lol
Click to expand...
Click to collapse
But, the prometheusoneui said that need to flash sound patch
fuady7 said:
But, the prometheusoneui said that need to flash sound patch
Click to expand...
Click to collapse
Hi, my patch made for drive spk amp device tfa9887 which mounts on only ZE600 or ZE601KL.
So I guess this patch isn't valuable for other zenfones.
I checked Z00UD schematic and I couldn't find tfa amp.
If you are facing sound issue, my patch can't improve your problem.
Hello, i'll glad to know if someone else encountered the same issue:
I have tested this patch with los ans crdroid with thé same results.
I flashed successfully the ROM & patch and all was working fine (sound ,data ans GSM connexion) for few hours. Then the phone freezes and after reboot,no GSM network détectéd at all... The only way to recover was to do a factory reset with twrp or revert back to oreo backup... Any idea?
Dear OnePlus Lovers,
did anyone of you get the Viper4Android FX Tool to work.
I tried nearly all possible way to set SELinux in permissive mode but nothing works.. it says everytime i have to install the driver but the magisk module is already installed..
Maybe any suggestions?
How did you root?
I did what everyone is telling. I just searched in the GSI Thread.
But only for you.
Post in thread 'GSIs status + boot dump' https://forum.xda-developers.com/t/gsis-status-boot-dump.4316479/post-85472945
drumntetri5 said:
I did what everyone is telling. I just searched in the GSI Thread.
But only for you.
Post in thread 'GSIs status + boot dump' https://forum.xda-developers.com/t/gsis-status-boot-dump.4316479/post-85472945
Click to expand...
Click to collapse
im curious if your in-display FingerPrint scanner works and also Auto brightness ? Currently used GT Neo with Corvus GSI
Fingerprintsensor is working very fine.
On my Xiaomi Mi9T Pro after flashing magisk it was not useable.
For the automatic lightsensor I can't say anything because I'm not using it.. but after I activated right now it's dimming the light down..
Hi, did you make it work?
drumntetri5 said:
Dear OnePlus Lovers,
did anyone of you get the Viper4Android FX Tool to work.
I tried nearly all possible way to set SELinux in permissive mode but nothing works.. it says everytime i have to install the driver but the magisk module is already installed..
Maybe any suggestions
Click to expand...
Click to collapse
sakarya1980 said:
Hi, did you make it work?
Click to expand...
Click to collapse
Sadly, no.. and at the moment I'm afraid to dig deeper into this because we don't have TWRP...