this rom phone fully hang butten not work morpho devise not conect not sport very very slow devise the best rom for zenfone phone max pro "google expirence" rom .img is good fully google this is not any bugs
1. cool, will checkpending work
1.fm radio doesn't work
2.dual 4g (vodafone & jio)
3.auto-rotate issue
4. selinux - change to enforcing
5. notification led will u change red to green because of its couldn't able to identified low battery level or any notification
6.add night light option
- OTA 311 sync
- SeLinux: Permissive->Enforcing thanks to @SagarMakhar
- Kernel: Merge 4.4.139
- Upstream changes
1. cool, will check
2. yea known
3. minor. fixed now, give feedback (clean flash)
4. done
5. dont know what you meant , led is fine totally
6. livedisplay exists
Yes.Can we install this by using red wolf recovory?
Yes you can I am on redwolf and it's installed without any hiccupsCan we install this by using red wolf recovory?
YesCan we install this by using red wolf recovory?
I have installed this but faceunlock feature is missing! Did you have the same issue?Yes you can I am on redwolf and it's installed without any hiccups
Yeah face unlock is missing but u can add it by magisk face unlock moduleI have installed this but faceunlock feature is missing! Did you have the same issue?
- OTA 311 sync
- SeLinux: Permissive->Enforcing thanks to @SagarMakhar
- Kernel: Merge 4.4.139
- Upstream changes
1. cool, will check
2. yea known
3. minor. fixed now, give feedback (clean flash)
4. done
5. dont know what you meant , led is fine totally
6. livedisplay exists
*Procedures*Most bugs are fixed I guess so why is it still Unofficial??
Is the multi touch bug fixed?
You are the most active developer in here. Hope more people join and help you.
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Yes the lineage vendor supports GSI. VoLTE will work too without flashing any additional patchdoes it support GSIs.
I tried to make a user build for myself with the code. I ran into some sepolicy issues. These arent specific to this device but also showed up with another device I tried. Looks like a bug in lineage.
When I look at the domain.te file, I see these lines at the mentioned line numbers -Code:libsepol.report_failure: neverallow on line 416 of system/sepolicy/public/domain.te (or line 8819 of policy.conf) violated by allow update_engine rootfs:file { write create setattr relabelto append unlink rename }; libsepol.report_failure: neverallow on line 413 of system/sepolicy/public/domain.te (or line 8816 of policy.conf) violated by allow recovery system_file:dir { mounton }; libsepol.report_failure: neverallow on line 260 of system/sepolicy/public/domain.te (or line 8663 of policy.conf) violated by allow update_engine update_engine:capability { sys_rawio }; libsepol.check_assertions: 3 neverallow failures occurred Error while expanding policy
Looks like there are exceptions being made for eng and userdebug builds, and hence it doesnt work with user builds.Code:# Nothing should be writing to files in the rootfs. neverallow { domain userdebug_or_eng(`-recovery -update_engine') } rootfs:file { create write setattr relabelto append unlink link rename }; # Don't allow mounting on top of /system files or directories neverallow * exec_type:dir_file_class_set mounton; neverallow { domain -init userdebug_or_eng(`-recovery') } { system_file vendor_file_type }:dir_file_class_set mounton; # Limit raw I/O to these whitelisted domains. Do not apply to debug builds. neverallow { domain userdebug_or_eng(`-domain') -kernel -init -recovery -ueventd -healthd -uncrypt -tee } self:capability sys_rawio;
I could track down the recovery issue to device/lineage/sepolicy/common/private/recovery.te. I think its the following line. There is also an update_engine.te file that might be having the other troubled policies
I could probably get rid of the offending lines from the recovery.te and update_engine.te files, but just wanted to make sure thats the best way to move forward with this.Code:allow recovery system_file:dir mounton;
1. cool, will checkpending work
1.fm radio doesn't work
2.dual 4g (vodafone & jio)
3.auto-rotate issue
4. selinux - change to enforcing
5. notification led will u change red to green because of its couldn't able to identified low battery level or any notification
6.add night light option