Search results

Hi! :) There might be other problems, but the most obvious one would be a missing permission (as the system throws a SecurityException). Does the app, which tries to bind the SmartcardService declare the permission it uses in its AndroidManifest? You would need this: <uses-permission...

Hi! :) The code was changes slightly in recent Android versions. I've updated the module to version "0.4". Now it should work also with newer Android versions (as far as I see in the code it should also work with Android 9 now). You can find the updated sourcecode here...

Hi codeworkx, hi qqzwc thanks for the ping. Haven't been on xda for some time now. :) Regarding NFC card emulation: I haven't looked into this issue for months now (and to be honest, also lost hope and interest in this topic). Back in January I did clean installs of this ROM and OmniRom but...

Hi darkobas! :) I'd like to be able to build the 7.1.2 OmniRom build for my LEX720 (I want to debug NFC host card emulation problems - see previous post). Unfortunately the "breakfast zl1" command aborts with "vendor/leeco/zl1/zl1-vendor.mk" does not exist. Stop. I see this is referenced...

Hi! Thank you for your kind response. Sorry, please don't get your hopes too high. I am a developer in may day job but I haven't worked with Android for some longer time now and I have not the resources or time to maintain a ROM. :( The reason why I wanted to be able to build this ROM is...

Help to build myself Hi! I am trying to build this ROM myself. I have already setup my (build) machine, installed all needed tools, setup ccache, etc. Then I initialized and synced the OmniROM repositories via: repo init -b android-7.1 repo sync source build/envsetup.sh breakfast zl1 The...

Regarding your logcat: I'm not totally sure, but it looks for me like this means the client (IR remote app) tries to use a deviceId/functionId combination (64028/0), which the QuickSet SDK doesn't know of. Are you testing with the original LeEco Remote app / QuickSet SDK service combination or...

trizex Thanks for your reply. :) darkobas: which kernel did you test with? Did you test with your EAS kernel? I did a quick grep over the source and the only occurrences of "ttyHSL" I found were in: Documentation/devicetree/bindings/tty/serial/msm_serial.txt...

Hi, I've decompiled the QuickSet SDK and this log message only appears in this context (where "file" is the serial device file under /dev which is used to send commands to the IR system): if (file != null && file.canRead() && file.canWrite()) { ... does some stuff here return; // and...

Hi darkobas! Thanks for looking into this. :) I also realized that lirc is very probably not an option for the IR chip used in the LEX720 device. The lirc kernel driver would need to implement the proprietary serial protocol which is currently done by the QuickSetSDK in userspace (altough it...

Hi! Sorry for the delayed answer. First of all the ROM you are using must have the SmartcardService (=implementation of OpenMobile API), the corresponding library (org.simalliance.openmobileapi.jar) and permission manifest (org.simalliance.openmobileapi.xml) installed. I downloaded...

Sorry, no idea. I don't have a Le1s at hand and without any logs it's hard to say anything about the cause. You could try to capture the logcat output on your computer when the phone is booting up. Try to start the logcat as early as possible (shortly after power-on): adb logcat -v time '*:V' >...

Hi! :) To clearify a little bit: The entry "System Image" you see in TWRP's backup screen, is not a separate partition. This is just a different mode to backup the "system" partition. So in short: "System" and "System Image" backup the same "/system" partition, just with different methods...

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

I noticed that the battery info only is shown, if the "Phone Audio" profile is enabled. If I only use "Media Audio" and disable "Phone Audio" it doesn't display the battery icon (at least this is what I noticed with my Aukey headset). See also the attached screenshot.

Hi Swastik Raj Chauhan, hi codeworkx! :) Thanks for pinging! Some users of my Xposed module reported that it works on the Le 2, so in principle it should be possible (see the "Reported to work with following devices" section in this posting: [MOD][Xposed] Make Infrared Blaster working with all...

I really can't answer that. I am wondering myself.

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

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

Whithout any further infos I have no idea what could be the problem here. You could save the logcat (Android log file) like I explained here: http://forum.xda-developers.com/showpost.php?p=70096764&postcount=37 In the resulting logfile we should see, if the module gets loaded and what happens...

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

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?

Hi! Thanks for your great work! :) I just noticed in the first post that you also removed the app "UEIQuickSDKLeTV". If this means that you have removed the app "UEI Android Services SDK(LeTV)" (package name: com.uei.quicksetsdk.letv, installed in folder: /system/app/UEIQuicksetSDKLeTV/) then...

Hi! I've created an Xposed module for my LeEco Le Pro 3 phone, so that I can use the IR blaster not only with the included Remote control app from LeEco but with any other 3rd party infrared app from the Play Store which uses the standard Android ConsumerIR API (for example like RCoid). As...

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

Hi! :) Thanks for the details. What I didn't expect, is the fact that the native app stops working after enabling my module. It should not interfere with other apps (at least that's what I thought). May I ask what "native" app exactly you are using? Is this the same LeEco Remote Control App as...

Hi! Can you verify that the infrared blaster is really not emitting infrared? (You can easily check this by looking at it with another phone's camera as digital cameras can see infrared light - while human eyes cannot). Do you really have the system app "UEI Android Services SDK(LeTV)"...

You're welcome! :)

No, but it needs the Magisk framework installed (as it's a Magisk module). :)

Interesting! Thanks for the feedback! Could you tell me which build you are running (where did you download CM13)? Also I would be curious if under the installed apps, is there anything like "UEI Android Services SDK(LeTV)" or "QuickSet SDK" or similiar? It has to be, because otherwise my...

Hi! I'm not running CM yet, but I've done lots of debugging of the IR blaster. Maybe this can get the IR blaster working also on CM: First some preconditions: Check if the running kernel provides the serial device file: /dev/ttyHSL1 (just check as root if this file exists) Check if the...

Hi! I've created an Xposed module for my LeEco Le Pro 3 phone, so that I can use the IR blaster not only with the included Remote control app from LeEco but with any other 3rd party infrared app from the Play Store which uses the standard Android ConsumerIR API (for example like RCoid). XDA...

Updated original post, added version 1.1 APK. Published new source on Github and uploaded new version also into Xposed repository. Just search in the Xposed installer app under "Download" for "LeEco Infrared Fix". Enough for today! :)

Hi, jhakjhuk1853, kedaranmol and serc! :) Thanks for reporting back! I will clean up the code (remove a little bit of the debug logging I've included for the case if it wouldn't work), and will make a new clean 1.1 release (and also release the source again). I'm glad you like it! At the...

Hi, serc, reversegear, kedaranmol, jhakjhuk1853! I've extended the module so that it now also fakes the availability of standard Android Infrared API. So now all Infrared apps should think infrared is available. I attached it to this posting below. Update: removed attachement, use final version...

I am currently playing around and testing.. :) I am trying to hook also all the relevant PackageManager methods, so that for an app everything looks like if there is a standard infrared HAL implementation available. Not sure, if this would work for the X526. If the IR blaster hardware or the...

One thought: could you test with an app like z-device test if the phone advertises having infrared capabilities to apps? Because this is the case with the LePro 3. It has the Infrared API included (so all infrared apps install and work fine), but just didn't do anything. My module only works...

Done. Published it into Xposed repo. :) Just search for "LePro 3 Infrared Fix". Also I would like to get feedback from LePro3 users if it's working on the newer EUI versions for the american version. (And please include logs if it's not working.) And when we finally have a working cyanogenmod...

Hi, thanks for the feedback. Good idea, I will it submit to the Xposed repo. :good: Yes, it's very likely that this might not work well on other devices (or even other EUI versions) as the tricks needed to get this working are very specific targeted. But in the other side (under the assumption...

It was less work than expected. Now it seems to work for me perfectly. I cleaned up the code, published it on Github and made a new thread for the Xposed module (I think this thread should stay more focused on the technical backgrounds while the new thread will be dedicated to the Xposed...

Update: Dec 6th, 2016: published version 1.1, works now with more LeEco phones. Btw, module was renamed to "LeEco Infrared Fix". Hi! I've created the Xposed module "LeEco Infrared Fix" for the LePro 3 (but seems to work on other LeEco phones too) which tries to make the IR blaster (the...

First breakthrough: I've created a (still very, very alpha) Xposed module which hooks the ConsumerIrService class and tries to bind the QuickSet SDK service to send the Infrared commands which it has received over the standard Android Infrared API using the QuickSet SDK API (so it acts like a...

I don't know. I could imagine that you might want to access coarse location so that the app can offer you remotes for cable providers in your region? Also, I could imagine internet access might be needed for downloading new remotes and speech recognition. But I didn't really look what exactly...

Ok, I found another possible way to use the Infrared blaster (for sending): Instead of directly communicating over the serial line, I tried to bind to the QuickSet SDK service from within my own test-app. As the QuickSet SDK service is not protected with a permission this should be possible and...

I don't think that LeEco is doing something bad here, but to be honest I also find it a little bit frightening what permissions the remote app is claiming. It seems like a lot of these permissions aren't used, but I didn't really look into this. Also for voice control you don't need the...

Short background excursion: Android itself has nothing to do with telephony. In fact every smartphone consists of two totally separated computers, one is running android (on our case the Snapdragon 821 chip) and the other chip is running a proprietary mini operating system, which is in most...

Okay, if anybody else wants to try to debug the serial communication with the infrared blaster chip, I attached the Xposed module I've written for this purpose. I've used it on my LEX720 running 5.8.018S. If you are running a newer EUI version it might work or not (depends if they have...

Thanks, I must have overlooked it. :) Similar situation here: good overall development experience (outside of Android world), built other ROMs, but never ported from scratch

Thanks for your offer! :) Unfortunately what we need is (mostly) not found in the installed ROM. The interesting files would be the build configuration and Makefiles that were used to produce the build. Thansk for your work! I saw your repository on Github. Do you know if dr4stic has published...

Does anybody know where to find the device tree of this build? (github?). So that we can actually build it and work with it and not just download it. I don't speak chinese and also with Google translate I didn't find anything in the bbs.ydss.cn forum. Without the device tree we will always be...