[ROM][X00TD][8.1.0] LineageOS 15.1 [OFFICIAL][NIGHTLY]

Code:

/*
 * 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.
 */

• Boots
• RIL (Calls, SMS, Data)
• Fingerprint
• Wi-Fi
• Bluetooth
• Camera
• Camcorder
• Video Playback
• Audio
• Sensors
• Flash
• LED
• GPS

• You Tell me

• Download the latest build and GApps
• Reboot to recovery
• Flash the latest build and GApps
• Reboot

• OTA 316 sync (ASUS you dont let me rest continuously for a week )
• Fixed low media volume
• Fixed FM
• Fixed NFC (ZB602KL users confirm this?)
• Upstream changes

doors666 said:

does it support GSIs.

Click to expand...

Click to collapse

doors666 said:

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.

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

When I look at the domain.te file, I see these lines at the mentioned line numbers -

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;

Looks like there are exceptions being made for eng and userdebug builds, and hence it doesnt work with user builds.

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

Code:

allow recovery system_file:dir mounton;

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.

Click to expand...

Click to collapse

• OTA 311 sync
• SeLinux: Permissive->Enforcing thanks to @SagarMakhar
• Kernel: Merge 4.4.139
• Upstream changes

savijaysalem said:

pending 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

Click to expand...

Click to collapse