yashsingh1/xdaforums huggingface dataset:
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
Hi!

I was curious and tried to look for the ROM you are running. I downloaded "Le1PRO_US_X800-ROW-v48RL-CUOCO92-5.5.011S.zip" from here: https://www.androidfilehost.com/?fid=24591020540822969

I am not sure, if this exactly is your ROM, but I unpacked the system partition to check some basics (without having the device):

The ROM already contains a version of UEI QuickSet SDK (package: "com.uei.quicksetsdk.letv", app_name: "UEI Android Services SDK(LeTV)"), installed in /system:

(/system/app/UEIQuicksetSDKLeTV/UEIQuicksetSDKLeTV.apk, /system/app/UEIQuicksetSDKLeTV/arm64/UEIQuicksetSDKLeTV.odex), so there should be no need to install any other version of UEI QuickSet

I decompiled this version of QuickSet SDK and looked for the 2 API methods I need ("transmit" and "getLastResultcode") and they both seem to be present and the same implementation as for me on my LePro 3

I also looked for the original Remote Control App and found it in /system/app/LetvRemoteControl_US/ (package: "com.letv.android.remotecontrol", app_name: "Remote Control"). It also seems to use the same QuickSet API and include the same logic for turning on the IR Blaster via the sysfile /sys/remote/enable.

So at a first look (and without having tested on a real device) it seems as if everything needed for getting my module to work is already there (especially your device seems to contain the same kind of IR blaster hardware).

I don't know, why it's not working for you. If there are not any hints in logcat I have no idea.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] disk@tek@:
Thank you for the further support.

I don't use CUOCO's firmware.

But I use from the same ballpark stock based version.

I went ahead and found 1.0.008 of the SDK online and replaced mine.

It did not help and when I reverted back stock app started to give me an error.

I thought to reflash the phone with a new firmware would be a good idea and have a clean install.

And first thing I did was to check your module.

Unfortunately the symptoms are exactly the same.

When I look at a log page in xposed installer there is an absolute white list.

After I restore my phone to a usable device (since flashing erased all my data including backups for no reason) I will dig deeper into logcat and try to provide you with the info. If at the time you'll still have the will to help me. Thanks.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
Hmm.. that's strange. Normally you should see there at least some output (even when no modules are enabled).

Can you somehow check if xposed is working in general? Are other xposed modules working?
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] disk@tek@:
Yes xposed (v87) works well for other apps. GravityBox for example. But no log. I thought I might have to enable it somewhere in the app. But I couldn't find any option for that.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
If you have "adb" and the needed drivers installed on your computer (search the forums or google for how to do that) you can write all log messages of the phone (aka "logcat") into a file. In a terminal window on your computer, simply enter the following (if possible directly after turning on the phone, so that all logs from beginning of boot are captured):

adb logcat -v time '*:V' >> logcat_messages.txt

This will produce a file named "logcat_messages.txt" containing all logs. You can filter this file for entries which contain "LeEco_Infrared_Fix".

The module should log some infos (and also all errors it encounters). It should produce a log line every time a IR pattern is sent (i.e. every time you press a button on a remote control app).
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
It's not a symlink because then the first letter of the permissions would be an "l" (i.e. "lrw-rw-rw"). All files and directories under /sys/ are not "real" files on a disk, but are virtual files, provided by the kernel (or kernel modules) to provide an interface to kernel-functionality. See also: Synthetic file system

In our case, the file /sys/remote/enable is provided by the ir_maxq616 driver in the kernel. So if we write something into this "virtual" file, there will be nothing stored on any disk, but instead this code in the kernel will be called: ir_maxq616.c - Line 47.

This calls "gpio_set_value" and sets a GPIO pin of the processor to 1 (in other words: it physically causes the processor of your phone to send some voltage on a special GPIO PIN - which I guess is wired to the infrared blaster and causes the blaster to power on, or something similiar).

Can you try if you can execute this command on the phone (either in a terminal on the phone or by opening a shell from your PC via "adb shell"):

echo 1 > /sys/remote/enable

But back to the problem:

Normally the /sys/ files look just like any other normal file to applications (that's the beauty of Unix and Linux - everything is a file :)). So there must be another reason why "isFile()" returns false.

Most of the time these kind of problems are related to SE Linux policies. I guess the SE Linux policy doesn't give us access to this sys-file. This was one of the problems I had in the initial version of this module. For this reason I decided also to hook the "com.android.settings" package (System settings app) as this package had the needed permission on my phone.

Can you check the SE Linux security context of the file? Maybe your SE policy is different than the one on my LePro3?

ls -alZ /sys/remote/enable
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] disk@tek@:
I'm fine with whatever it is. :)

I've read online if it is not normal file .isFile will return a false.

There is nothing much I know about it. )

I was able to write 1 via editor with super user access on my phone with no probs.

And via adb shell with super user access aswell (but don't without it, don't know if it supposed to be like that):

shell@x1_na:/ $ ls -alZ /sys/remote/enable
/sys/remote/enable: Permission denied
1|shell@x1_na:/ $ echo 1 > /sys/remote/enable
/system/bin/sh: can't create /sys/remote/enable: Permission denied

shell@x1_na:/ $ su
root@x1_na:/ # ls -alZ /sys/remote/enable
-rw-rw-rw- system system u:object_r:sysfs_ir_enable:s0 enable
root@x1_na:/ # echo 1 > /sys/remote/enable
root@x1_na:/ #
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
Seen from a higher level view, if we just differentiate between user-space (all the processes running on a system) and kernel-space (kernel, which provides the basic APIs - aka system calls - to the userspace):

For the kernel it's not a real file: the kernel just provides all the system calls like for a file but does something different when somebody is reading or writing to this file.

For the user-space it is a file. The kernel provides everything what a normal file has. So user-space just sees a file (it looks like a file, it smells like a file, must be a file ;))

So trust me, all files in /sys/ also return true on "isFile()" if the program which calls it is allowed to access it. :)

Except the program is not allowed to access the file. And I am not talking about the "-rw-rw-rw-" permissions here (because these 3 "rw" look like everybody is allowed to access), I am talking about kernel level permission enforcement - which is done in Android via SE Linux (and indeed the "ls -alZ" command shows that this file has some special context: "sysfs_ir_enable"). So the underlying problem seems to be that the "com.android.system" process (and also not your normal user shell) is not allowed to access this file by SE Linux permissions. So it would nothing change if I remove the "isFile()" check, it would just run into an exception one step later.

You can also check that SE Linux is enabled and in "Enforcing" mode if you enter in a commandline:

getenforce

If you would set SE Linux to "Permissive" then you would be able to echo 1 into the file also without root.

So, to get it working I would either need to use root in my Xposed module (I am not really sure how this will work or is done correctly, as an Xposed module works different than normal application as their code is running within the context of other applications - does the Xposed module need root permission or does the hooked application need root? Also is it possible for a system service to request root permissions??). Or - the easier way - I can find another package on the system which has the SE Linux permission to write into the sys-file.

Or I can find a way to patch the SE Linux policy (never done that, don't know yet how this would work).

But before we try any step further:

After you have done the "echo 1 > /sys/remote/enable" as root, is the IR blaster working then normally (with my module enabled 3rd party IR apps)? Do you see IR signals (with a camera) then? If not, do you see any error messages in logcat while pressing buttons in an IR app?

P.S.: if you want to check if there still is a "1" in the file, you can easily do on the adb shell (as root):

cat /sys/remote/enable

This will simply display the contents of the file (just checking to be sure, that not some other has written back a "0" in the file while you are testing.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] disk@tek@:
This actually makes sense. So I guess the only way is to found the permission to satisfy the kernel for writing to file?

I'm not sure if I use getenforce correctly or if I'm supposed to write anything else. But here is the output:

shell@x1_na:/ $ getenforce
Enforcing
shell@x1_na:/ $ echo 1 > /sys/remote/enable
/system/bin/sh: can't create /sys/remote/enable: Permission denied

If I echo 1 > /sys/remote/enable by root the changes are kept.

And I can see the beam on a native app and on an Anymote.

In fact anymote did powered off my Philips TV.

This is a little victory :) Thanks!!!

I guess at this point I can just use Tasker to write to echo 1 > /sys/remote/enable every boot time. But that would be a crook.

Is a root permission for your module would be considered a dirt programming? Or might be you have another idea? )))

upd. Ahhh no.. After reboot I do write 1 to enabler with Tasker. But I have to force stop LeTV SDK for IR blaster to work as with the previous version of your app.

upd2. I have two shell commands in Tasker after boot + 20 seconds. echo 1 > /sys/remote/enable and am force-stop com.uei.quicksetsdk.letv Works for now. )
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] zmanfarlee:
deleted
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] doo_Z:
Anyone can help me with my Le Max 2 (5.9.20S stock CN)? The module seems doesn't working :(
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Uday sreenivasula:
Working with le1s &le1s eco,on eui 5.8 latest dev version

I tried this module on le 1s eco eui 5.8 dev,

It first got stuck at eui logo while activating the module!!!

I uninstalled Xposed and reinstalled it and then it's working perfectly for all ir apps!

Maybe that sticking at boot is a minor bug and you need to flash user data or just reinstall Xposed framework using TWRP

And you are good to go...
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] bucket19:
Can someone help me find the apk for UEI Android Services SDK(LeTV)? I am on CM and I don't have a backup of EUI to go back to in order to find this file.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] bucket19:
I have found the APK for the UEI application and I have attached it here in case others need it.

It still won't work for me though on CM 13. I have I have the QuicksetSDK installed as a system application and also have the Xposed module installed but nothing seems to be working. I have pointed a camera at the IR blaster to see if it is working and it is not.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] jayswalnirav:
It is working on le1s x509 (Indian version)
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] fakekorom:
this one https://play.google.com/store/apps/details?id=com.uei.quicksetsdk&hl=hu&rdid=com.uei.quicksetsdk

didnt help neither
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] androcheck:
You should install the QuickSet SDK that came with the stock ROM of your phone model as I don't know if LeEco made some customizations for each model. But that's just a guess. What I know for sure is that the QuickSet SDK from PlayStore cannot work, because LeEco has modified the versions shipped with their stock ROMs (including changed package name).
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Elusivo:
hi androcheck, tks for this module, it will be the best thing for my phone (ir was one of the main reasons i bought my letv le max x900+)! Ofc i was/am super disappointed that 3rd party apps dun work as i can't make use of custom ir codes like this! (also i dunno where the native app saves the custom remote codes to try and edit them...)

And unfortunately i seem to be having same issues as disk@tek@ :( i have the sdk app and also the same error in the log saying it can't find the enable file.

With the module active the apps do detect ir capabilities but the native letv remote app fails to initialize (it doesn't even display my saved remotes in the letv native app). No app produces any ir light. They also dun work even if i force 1 into the enable file. I din try to force close the sdk app, will try later today.

After disabling the module the native letv again displays my saved remotes and works normally.

Besides logcat is there any logs or something that could be useful in solving this? I really want to make this work, i even built an audio jack ir blaster in the weekend cause can't use the phone's ir, pitiful!

update: ok, can confirm, force closing the sdk does make the ir work with 3rd party apps xD not perfect but better than nothing ^^ keep up the good work :)
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] kakagi:
Thanks for your hard work.

I'm just thinking about the multicolor led notification light. is it possible to use the multicolor led using module like this in Xposed in our eui base rom? Because normal xled or other Xposed module can't change the led color while in other custom ROM we can enjoy it.

I know it's a off topic discussion but if it can be done that would be great.:)
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] supernielsen:
Thank you very much for this im running a leeco le Max 2 with custom rom, and this worked perfect..!!
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] vpclabs:
Please help

Is there any possibility that I can use this module to fix IR issue in CM 14.1 Custom ROM for le s3/ le 2

Please advice me if someone knows a way.

Thanks in advance.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] flotux:
I would be also interested in the needed steps to get IR running on the current LineageOS 13 weekly ROM. I installed the LeEco framework apk as system app together with your XPosed module but IR is not working.

Any idea?
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Surya1998:
Install gravity box module and set light as emulated, then use any third party led colour apps from googleplay.. It worked for me, but sometimes it starts to change colours on notification
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] sandy_nsk:
3rd party remote not working

Hi,

I installed this module on LE2-5.9.020S.

I tried lots of apps including peel smart, its not working. Only zapzap remote app is working. Xposed Log is empty .

No IR ray seen for other apps than zapzap.

Please help.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] HopelesRomantc91:
I couldn't find it by searching, is there a way to get this without Xposed? I have some apps that crash when Xposed Framework is installed.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Harakiri23:
Le Eco Max 2, 5.9.0.23S cuoco92 Rom. While 3rd party applications recognise the IR none of them work to actually control any of my devices - even tho the specific model # of my tv/air condition/receiver is available.

Log says successfully hooked, but also says sys/remote/enable is not a file! Strange..??

edit: Ok i read the thread, somebody else had the same issue - i edited the file and set it to 1 from 0 - then stopped the SDK Service and it works.

Please fix this, add the possibility to call your module with SU rights
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] voland:
Could you please port it to Magisk systemless Xposed built-in installer/framework? With classic Xposed module (meaning classic Installer + classic Framework) device will lose SafetyNet Pass.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] chuckrobinson47:
Works for LG VOLT (LS740) AKA X5

The built in IR blaster stopped working when i started running different ROMS. Currently the VOLT has CM12 with xposed framework 87. tested with ztest to prove it. still looking for a good ir app. thanks ANDROCHECK. I had already given up on the ir blaster. but now it's back.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] sritimes:
Fix for Le 2 on MIUI 9 (7.9.21)

Hi dev excellent work... Huge thanks.

I tried in Le 2 with 26s stock (by manunair) works like a charm.

Now trying in MIUI 9 (7.9.21) by Sagar Makhar. Not working now.

Please fix it... Missing a great module.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] dunas2331:
Will this work on le pro 3 running lineage 14?
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Serui75:
leeco x820 EUI 5.8.019S

leeco x820 EUI 5.8.019S DOES NOT WORK, please do this leeco x820 EUI 5.8.019S
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] easymik:
Please can you port it for Magisk
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Hamilton2:
I just Got this phone Let's pro 3 AI x650 a few days ago and I discovered that the Infrared App Is missing, as a matter of fact there are no leEco apps on the phone. I have downloaded over 10 remote control apps and all failed to work, please I need help
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] pratik2537:
I intall viperos Android 7.1 in le2 x526 and this module it's perfect work i tasted mi and peel remote but it's need to a selinux mod permission
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] lovesetcpu:
Where to get

"UEI Android Services SDK(LeTV)"

??
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Jaidnasim:
Not Working On lemax2 26S plz update app....Z device test says infrared working but cannot connect to any device
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Bobfish:
Working on Le S3 X626 , EUI 5.9.023s.

Apps used - Castreal IR , Sure Universal IR .
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] r0c0:
It does not work on Le S3 X522 (5.8.021s) as in it does not even boot with (only)this module enabled.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] tsongming:
Take note, that you are not within the X522 threads.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] iWheel:
End user please advise

Model lex650

Android 6.0

Patch Feb 15, 2017

EUI 5.9. 026 s

CPU Helio x27 10 core 2.6GHZ

Can someone walk me thru getting this to work?? My phone did not come with a copy of LeTV remote control app so I have nothing on there except third-party software such as peele remote control
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] D1stRU3T0R:
I guess it's not compatible with helio versions.

Update: or maybe it's working
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] iWheel:
Still not working,
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] jeetash:
Hi androcheck ... I read the entire thread .. and I'm a bit of a noob.. but just wanted to drop a line to say that I tried with a Le pro 3 running AICP rom Oreo 8.1

This room has the stock remote app which works and it also has the UEI Android services sdk app as a system app,

But when I install your module and restart .. it just gets stuck on a bootlogo.

Don't know if any here has a fix or if OP is still trouble shooting , any help will be appreciated
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] itoxygen:
Leeco Pro 1 x800 running eui 5.8.026s, Infrared is OK
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Alexandrutm:
Can you port it as a magisk module,please?

Trimis de pe al meu LEX720 folosind Tapatalk
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Neppomuk_:
Hi

I've installed the Module on LeEco Le Pro 3 with AOSP Extendet. AnyMote Smart Remote does recognize an "Andoird IR Blaster". But IR blaster does not send. Tested with another Phone Camera. The LeEco remote is installed on this custom ROM and working.

Do I need to change the SELinux state? Or anything else I can check?

Greetings
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] slgooding:
Pretty sure this module is obsolete. They got the IR working with 3rd party apps a while ago (at least with AICP and Lineage).
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] Neppomuk_:
Aktually, I think not. There were other solutions like ZaZa Remote App. As I can see, this one is supporting the nativ LeEco IR Interface. The other way is just install the LeEco API with its own App, wich is actually done in the AOSP Extended Rom for the LePro 3. So I was testing, if this xposed modul will work with this custom rom to get the my favorite IR App working, but unfortunatly it does not.

So was I can see is, that after the modul is installed, the apps find an ir blaster, but the codes were not routed throug this, so the blaster is not acting.
[LeEco Le Pro3 ROMs, Kernels, Recoveries, & Other D] kaaaxcreators:
Not working properly

X722 with nitrogenos android 9 and edxposed

LeEco_Infrared_Fix: ERROR: getSystemAvailableFeaturesHook: return value is null or wrong type: android.content.pm.ParceledListSlice@944c046
[Moto Z Questions & Answers] enetec:
Since I've ever a lot (read: hundreds....) of apps installed on my phones, I've ever used a "boot receiver editor" like "ES System Monitor" or "Manage Android Autostart" to limit unuseful apps autostart and have it a faster and with a better battery life phone...

These apps obviously need root, BUT I've seen that on Moto Z they simply... don't work! :eek:

ES System Monitor's "Optimizer" function seems to work but when you exit and re-enter all changes are lost... :rolleyes:

Manage Android Autostart instead return an error like "fail... are you sure to have root access?" when, obviously, root is granted (and SuperSU related "toast" has just benn showed... :rolleyes:).

This is not directly related to MM since on another phone with AOSP MM 6.01 installed all works fine...

Any idea on what could produce this behaviour? It seems something trying to "protect" /system from modifies... (BUT with ES File Manager I don't have any problem to modify it...) :confused:
[Moto Z Questions & Answers] reiteravi:
es file manager and other stuff are not what they used to be

sold to third party who forced crapware

i would stay away from them
[Moto Z Questions & Answers] enetec:
Uh...?! Never had issues with them...?! :confused:

Anyway in a very similar ROM they works and on Moto Z... not!

We have to understand the reason... [MENTION=6298645]erfanoabdi[/MENTION], any idea?
[Moto Z Questions & Answers] erfanoabdi:
i don't know why :confused:

but i'm ok with greenify

:laugh:
[Moto Z Questions & Answers] enetec:
Yes, Greenify does the "main" work, BUT there are apps that try to reactivate at every occasion and produce a lot of (unuseful) wakelocks... when you have a lot of apps, reduce the active receivers is very important too...

And only a *good* knowledge of our device will allow us to obtain best results... :p

Let's try again... [MENTION=490110]janjan[/MENTION]?