DU 12 - X2

gregoritto · Apr 24, 2018

shiva7864 said:
Go settings, developers option and
Enable. In and ringing and try

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Enable in band ringing

It is working! THANK YOU!!
I disabled "Enable in band ringing", restarted and WOW !!!
+1 @shiva7864

romester · Apr 25, 2018

In a previous version, I worked the Letv Remote

shiva7864 · Apr 25, 2018

romester said:
In a previous version, I worked the Letv Remote

U need to work letv remote app r8t na

thor88 · Apr 25, 2018

romester said:
In a previous version, I worked the Letv Remote

You have to switch SELinux to permissive with the magisk module "Magisk SELinux Manager" then the Letv Remote Controll will work.

CHRISTRANS · Apr 25, 2018

shiva7864 said:
Go settings, developers option and
Enable. In and ringing and try

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Enable in band ringing

That helps.
Thank you.

gregoritto · Apr 25, 2018

I don't know about Unofficial and Official procedures, but according to my experience and others on other forums (stable, VR working, etc) I vote for Official status for this ROM with leader @infrag !!
I enjoy this so much. Thanks

Immortal68 · Apr 26, 2018

For anyone still having problems with the camera focus. I managed to get mine to work by setting SELinux to permissive (you can check the status under Settings -> System -> About phone). I changed it from Enforcing with the Magisk Module "Magisk SELinux Manager" and after rebooting the phone you can go to Settings -> System -> Leeco Extras and enable the Camera Focus Fix (it crashed when trying the same thing with SELinux mode: enforcing). That fixed it for me.

edit: Changed "Mesik" to "Magisk" - where did that come from?

ThE_MarD · Apr 26, 2018

Immortal68 said:
For anyone still having problems with the camera focus. I managed to get mine to work by setting SELinux to permissive (you can check the status under Settings -> System -> About phone). I changed it from Enforcing with the Magisk Module "Mesik SELinux Manager" and after rebooting the phone you can go to Settings -> System -> Leeco Extras and enable the Camera Focus Fix (it crashed when trying the same thing with SELinux mode: enforcing). That fixed it for me.

Heyyo, nice find! Is there a chance you could please record a logcat of you using the toggle with selinux permissive? It'll give us an idea what needs to be added to selinux policies to allow focus fix toggle to work

Immortal68 · Apr 26, 2018

ThE_MarD said:
Heyyo, nice find! Is there a chance you could please record a logcat of you using the toggle with selinux permissive? It'll give us an idea what needs to be added to selinux policies to allow focus fix toggle to work

Hi ThE_MarD! I haven't used logcat before, so let me know if there's something missing.
This is what I recorded in roughly 10 seconds, turning Focus Fix off-on-off-on. All done while SELinux was set to permissive. I'm on x829 64/4GB, DU Version 13042018.

Code:

[ 04-26 23:20:15.025   842:  883 D/QC-time-services ]
Daemon: Connection accepted:time_genoff


[ 04-26 23:20:15.027   434:  440 D/QC-time-services ]
Lib:time_genoff_operation: Send to server  passed!!


[ 04-26 23:20:15.027   842:22162 D/QC-time-services ]
Daemon:Received base = 13, unit = 1, operation = 2,value = 0


[ 04-26 23:20:15.028   842:22162 D/QC-time-services ]
Daemon:genoff_opr: Base = 13, val = 0, operation = 2

[ 04-26 23:20:15.028   842:22162 D/QC-time-services ]
offset is: 1 for base: 13

[ 04-26 23:20:15.028   434:  440 E/QC-time-services ]
Receive Passed == base = 13, unit = 1, operation = 2, result = 0


[ 04-26 23:20:15.028   842:  883 E/QC-time-services ]
Daemon: Time-services: Waiting to acceptconnection


[ 04-26 23:20:15.028   434:  440 D/DrmLibTime ]
QSEE Time Listener: ATS_MODEM is set. Try to retrieve it.

[ 04-26 23:20:15.029   842:  883 D/QC-time-services ]
Daemon: Connection accepted:time_genoff


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Received base = 13, unit = 1, operation = 1,value = 0


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:genoff_opr: Base = 13, val = 0, operation = 1

[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon: genoff get for 13


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Value read from QTimer mseconds = 17632000


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Value read from RTC mseconds on boot = 52229422000


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Value read from QTimer mseconds = 17632000


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Value read from generic offset = 1472530577743


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Delta read on boot mseconds = 52229405299


[ 04-26 23:20:15.030   842:22163 D/QC-time-services ]
Daemon:Final Time = 1524777615042


[ 04-26 23:20:15.030   434:  440 D/DrmLibTime ]
QSEE Time Listener: Time GenOff - seconds: 1524777615

[ 04-26 23:20:15.030   434:  440 D/DrmLibTime ]
time_getutcsec returns 0, sec = 1524777615; nsec = 0

[ 04-26 23:20:15.030   434:  440 D/DrmLibTime ]
time_getutcsec finished! 


[ 04-26 23:20:15.031   434:  440 D/DrmLibTime ]
iotcl_continue_command finished! and return 0 

[ 04-26 23:20:15.031   434:  440 D/DrmLibTime ]
before calling ioctl to read the next time_cmd

[ 04-26 23:20:15.032   842:  883 E/QC-time-services ]
Daemon: Time-services: Waiting to acceptconnection


[ 04-26 23:20:15.068   858: 1860 I/QFP      ]
QfpCalibTest::calibTestCommand: control 22, buffer size 16, result 0

[ 04-26 23:20:16.035   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 577798262, last DSPS: 577855618, boot                         TS: 17629653770472, last boot: 17626403977128

[ 04-26 23:20:18.034   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 577863787, last DSPS: 577921154, boot                         TS: 17631652394265, last boot: 17626403977128

[ 04-26 23:20:18.034   674:  827 W/qti_sensors_hal ]
timestampCalc: TS rollover confirmed. cnt: 8, rcv: 0

[ 04-26 23:20:19.416   717:  844 I/ThermalEngine ]
Monitor : quiet_therm = 29, msm_therm = 30, ufs_therm = 29, battery_therm = 280,current_now = -232390 


[ 04-26 23:20:20.034   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 577929331, last DSPS: 577986676, boot                         TS: 17633652415506, last boot: 17631652394265

[ 04-26 23:20:23.034   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 578027637, last DSPS: 578084994, boot                         TS: 17636652604451, last boot: 17631652394265

[ 04-26 23:20:23.034   674:  827 W/qti_sensors_hal ]
timestampCalc: TS rollover confirmed. cnt: 9, rcv: 0

[ 04-26 23:20:23.785   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 578044035, last DSPS: 578109587, boot                         TS: 17637403903328, last boot: 17636652604451

[ 04-26 23:20:24.284   674:  827 W/qti_sensors_hal ]
timestampCalc: potential TS rollover detected.                         DSPS TS: 578068588, last DSPS: 578125941, boot                         TS: 17637902421606, last boot: 17636652604451

[ 04-26 23:20:24.604   821: 2912 I/LocSvc_libulp ]
ulp_msg_process_system_update: systemEvent:5 


[ 04-26 23:20:24.605   821: 2912 I/LocSvc_libulp ]
ulp_msg_process_start_req, at ulp state = 1


[ 04-26 23:20:24.605   821: 1972 I/LocSvc_api_v02 ]
---> locClientSendReq line 2102 QMI_LOC_GET_BEST_AVAILABLE_POSITION_REQ_V02

[ 04-26 23:20:24.610   821: 1974 I/LocSvc_ApiV02 ]
<--- globalRespCb line 141 QMI_LOC_GET_BEST_AVAILABLE_POSITION_REQ_V02

[ 04-26 23:20:24.610   821: 2912 I/LocSvc_libulp ]
ulp_brain_process_zpp_position_report, report ZPP position to providers,report_position = 1


[ 04-26 23:20:24.611   821: 1972 V/LocSvc_HIDL_IzatProvider ]
[onLocationChanged][67] [HS] =>>>> [HC]

[ 04-26 23:20:24.613  1515: 2083 V/LocSvc_HIDL_IzatProvider_jni ]
[onLocationChanged][136] [HC] <<= [HS]

[ 04-26 23:20:24.624   821:  821 I/LocSvc_GnssInterface ]
===> injectLocation line 232

ThE_MarD · Apr 26, 2018

Immortal68 said:
Hi ThE_MarD! I haven't used logcat before, so let me know if there's something missing.
This is what I recorded in roughly 10 seconds, turning Focus Fix off-on-off-on. All done while SELinux was set to permissive. I'm on x829 64/4GB, DU Version 13042018.

Heyyo, no worries! You can just use logcat via a PC with usb debug enabled and use...

ADB logcat | tee focusfixselinux.log

Or use an app and give it root such as MatLog or Logcat Extreme from the play store and record and perform the action and then stop and save the recording and paste it on Pastebin or hastebin and then please link it here.

It should have an entry for "selinux AVC denied" or something like that is what we need to see

Immortal68 · Apr 26, 2018

ThE_MarD said:
Heyyo, no worries! You can just use logcat via a PC with usb debug enabled and use...

ADB logcat | tee focusfixselinux.log

Or use an app and give it root such as MatLog or Logcat Extreme from the play store and record and perform the action and then stop and save the recording and paste it on Pastebin or hastebin and then please link it here.

It should have an entry for "selinux AVC denied" or something like that is what we need to see

I think I got ya. I thought I did just that in my OP though...? Anyway, here's a pastebin.com for a log taken with MatLog. Same conditions. Just to be clear, I'm only going to settings and switching the focus fix on and off while SELinux is set to permissive. That's what you asked for, right? https://pastebin.com/NCuFt029

ThE_MarD · Apr 27, 2018

Immortal68 said:
I think I got ya. I thought I did just that in my OP though...? Anyway, here's a pastebin.com for a log taken with MatLog. Same conditions. Just to be clear, I'm only going to settings and switching the focus fix on and off while SELinux is set to permissive. That's what you asked for, right? https://pastebin.com/NCuFt029

Hmm darn it's not showing an selinux entry for lepref... you may need a logcat from boot which means you'd need to do it with a PC via USB and have it already in selinux permissive and then reboot and once the phone vibrates on reboot start on the PC with "adb logcat | tee selinuxfocusfix.log" and hopefully it'll catch a log from boot and maybe give hints as to what needs to happen.

Immortal68 · Apr 27, 2018

ThE_MarD said:
Heyyo, nice find! Is there a chance you could please record a logcat of you using the toggle with selinux permissive? It'll give us an idea what needs to be added to selinux policies to allow focus fix toggle to work

ThE_MarD said:
Hmm darn it's not showing an selinux entry for lepref... you may need a logcat from boot which means you'd need to do it with a PC via USB and have it already in selinux permissive and then reboot and once the phone vibrates on reboot start on the PC with "adb logcat | tee selinuxfocusfix.log" and hopefully it'll catch a log from boot and maybe give hints as to what needs to happen.

So, I tried it with the command you gave me, but that one's giving me the error that "tee" is not a recognized command. I used "adb logcat -v long > selinuxfocusfix.log", which worked and hopefully will give you the right info as well. The log-file was so big I had to split it in 3 parts to upload it on pastebin. Hopefully this was worth it. :laugh:

Part 1
Part 2
Part 3

This is restarting my phone and going into settings -> About phone -> Leeco extras and turning Camera Focus Fix off and on again.

joseluis0209 · May 2, 2018

for when an official DU.

infrag · May 3, 2018

Immortal68 said:
So, I tried it with the command you gave me, but that one's giving me the error that "tee" is not a recognized command. I used "adb logcat -v long > selinuxfocusfix.log", which worked and hopefully will give you the right info as well. The log-file was so big I had to split it in 3 parts to upload it on pastebin. Hopefully this was worth it. :laugh:

Part 1
Part 2
Part 3

This is restarting my phone and going into settings -> About phone -> Leeco extras and turning Camera Focus Fix off and on again.

It will be fixed in next build. Hopefully today...

infrag · May 3, 2018

new Build is up.

luca_vivi · May 3, 2018

infrag said:
new Build is up.

tnx infrag, best oreo rom!

Abdel1998 · May 3, 2018

@infrag

Did you add tisot blobs also for less battery drain?

And selinux fixes for remote?

Thanks.

gregoritto · May 3, 2018

Best Oreo ROM!
Animation scale added! WOW! 0.2x is very responsive. Super

pete80pro · May 3, 2018

gregoritto said:
Best Oreo ROM!
Animation scale added! WOW! 0.2x is very responsive. Super

Without Animations it's very responsive too:laugh::laugh::laugh:

DU 12 - X2

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts