We have shared the official Honor 4X Che1-L04 Stock ROM Firmware (Flash File) on this page. The Stock ROM comes in a zip package and contains USB Driver, Firmware, Flash Tool, and How-to Flash Manual.
[*] Backup: If you are going to flash the above firmware on your Honor Device, then we recommend taking a backup of your data from the device, as flashing the ROM (firmware) will wipe the data from the device.
I know this seems obvious but you did not mention, have you connected your smart device to the keyboard with an audio cable? Have you confirmed the cable is working correctly and connected the the proper jacks?
By the way, the Casio compatibility page (accessed from my desktop computer) correctly recognizes the brands and models of my tablet and smartphone, and states they are compatible. (I have no idea where it got that data.) Chordana Play is running on my tablet.
The idea behind using a different tablet is to eliminate the possibility of a flaw in that particular tablet. But since you also have a phone, that will suffice. Another possibility is the keyboard itself may be malfunctioning. Have you called Casio tech support? They have access to these products and can walk you through the process. Sometimes they send people to this forum for assistance, but in this case, we don't have anyone here who has access to an LK-265.
I've been servicing electronic equipment on and off for 60 years. (I'm a degreed EE, a technical writer, and hold an amateur license.) The most-important thing I've learned is that the answer to most problems is staring you in the face, but you don't recognize it.
When I plug headphones into the tablet with Keyboard Link turned off, both channels play the music at the same level. When I turn Keyboard Link on, the music comes mostly from the right channel. (It's still on the left, at a much lower level.) The control data are supposed to be on the left channel, but I don't hear anything "digital". (It might be at too low a rate to have significant audible components.)
When headphones are connected to the smartphone (a Samsung Luna), and Keyboard Link is activated, buzzing noises (presumably the control data) come from the right channel, with the music on the left. And I continue to get level-error messages -- both plus and minus.
Despite a great deal of experimentation, I still can't get the keys to light. I'll have to report this failure in the review. It's particularly annoying, because Casio explicitly states that my smartphone is compatible.
Now I'm going to get on my high horse, because I'm entitled to. I worked for Bendix Field Engineering almost 40 years ago. I was on a team installing new klystrons and their step tuners at various sites. Though the klystrons had been aligned before they left Varian, they didn't begin to meet their specs. No amount of fiddling -- by our team or the NASA engineers -- could make them meet specs. We had to get "dispensation" from NASA so that some of the klystrons could be used.
Then, one day I saw one of the techs toss an HP point-contact diode into the trash. "It's no good." The light suddenly went on. Maybe the klystrons were properly tuned, but we weren't measuring them properly. When I switched to an HP thermocouple meter, every channel of every klystron was dead-on, or needed only minor adjustment.
I work nights at a chain store to supplement my income. Our cash registers' IBM software is thoroughly screwed up. It's sometimes hard to use, and doesn't always behave in a consistent or "logical" manner. It even steals money from customers, as it did to me the other day. (I have to report it tonight.)
Competition is a good thing, but most companies rush products to market, then leave it to user groups to pick up the pieces when said products don't work right. (Sony had major problems with the Android software in its 930D series TVs. I consider myself lucky that mine works, and have no intention of "updating" the firmware.) This is inexcusable. I long ago grew tired of buying ill-conceived or poorly executed products, then having to troubleshoot them. I don't get paid for this.
That compatibility message you are getting is coming from the Android Operating System, and is only accurate insofar as the internal features of the device (your phone) on which it and the app in question (in this case ChordanaPlay) are running, but neither the Android OS nor typical app have the ability to look beyond the device's I/O ports to report on compatibility with connected devices (in this case, the LK-265). When you attempt to download/install an app, the GooglePlay site checks the OS on your device to see what hardware features it is configured for, and if there is a problem, the app refuses to download/install and generates an incompatibility message. For instance, if an app requires GPS capabilities, but your device (phone/tablet) does not have GPS capabilities, the app will refuse to download/install; the same if the app requires a 10 inch screen, but your device only has an 8 inch, and so on, but these are all internal features. If GooglePlay were to check compatibility between the device (phone/tablet) or app and any connected device (keyboard, etc), it would require you to have that device connected prior to starting the download. I am not aware of any current apps that do this. In this case, you have to rely upon the compatibility lists from the hardware manufacturers and app authors. This situation is exacerbated by the typical practice of each Android device manufacturer running their own particular "flavor" of a given Android OS version. Where PC/MAC devices use updatable "drivers" to interface the hardware to the OS, Android device manufacturers modify their device's OS, or pay to have it modifed, to run with their devices' particular chip sets. This is the current fact of life, of Android technology, that has kept it from achieving the widespread acceptance, in the music production field, as that enjoyed by Apple iOS technology, but such are the differences between a "well controlled", but oft maligned, architecture (Apple) and a "free-reign/every man for himself", popularly praised, environment (Android).
I have spent the past several hours reading through user reviews of the LK-265/ChordanaPlay system. The pros/cons were pretty evenly split. Interestingly, all of the cons were for reasons other than the problem you are having - such things as: didn't like springy feel of keys, lack of backlighted LCD screen, no USB MIDI port - but the LK-260 does have, sound from the LK-265's speakers, during App Play mode, is only mono, because the right stereo channel is used for signaling/control, and so forth - basically, design features. From the pros side, it was immediately obvious that most of these users were new to music keyboard technology and did good to know how to plug the thing in and turn it on, but yet they had it up and running with ChordanaPlay. To me, that was an imperative to discount "user error" for someone of your experience. So, that leaves either defective equipment of a compatibility problem. Yes! It could be a bad audio cable, or bad audio connector on the keyboard, etc, but I checked the compatibility for ChordanaPlay on the GooglePlay site and came up with this:
The accompanying Casio disclaimer is: " It is recommended to check the operation on the above smartphones / tablets and use them. Please understand that we do not guarantee the operation on smartphones / tablets not listed." You will notice that the Samsung Luna is not on this list. There is every likelihood that the ChordanaPlay app is not fully compatible with the Luna's particular "flavor" of the "Marshmallow" OS, but just enough so as not to generate a compatibility error message, or there is an incompatibility between the Luna's audio I/O and the LK-265's I/O - most likely at the app or OS interface with the Luna's audio I/O port. I know this is not at all what you wanted to hear, but I currently have four Android devices (3 tablets, and a phone), the oldest, a 10 year old Samsung Galaxy 10 Tab 2; the newest - a phone approx. one year old, and I have continually fought these problems throughout it all. I have never had anywhere near these kinds of problems with my iPad-3, but another fact of life with any tablet/phone, other than the full Windows based devices, is that the more you try to interface it to the outside world, the more problems you are going to have. These things really were intended to run primarily stand-alone.
I wish I had better words for you, but as BradMZ stated above, with the exception of Casio's Mike Martin, we are just a bunch of "civilian" volunteers, here to help out as best we can. When Casio Support refers users here, they have no way of knowing our current knowledge of, or experience with, any particular device - particularly newer technology. With the LK-265/Chordana system, you are probably the only user currently accessing this forum that has had any experience with it.
BTW - This forum is privately owned and administered and has no financial or corporate connection with Casio-US or Casio-International - other than permission to use the name. Casio-US' Mike Martin checks in from time to time in the guise of a technical advisor or support consultant. While there may be other members, who are Casio employees, there participation here is strictly that - members. Their presence here has no official connection with Casio.
In the case of the Samsung Luna, it appears the headphone channels are reversed. (The data appear on the right channel, not the left.) Whatever the installer can or can't do, it apparently isn't able to evaluate headphone wiring! (No, I'm not going to wire up a reverser. (Come to think of it... I might have one I created for my ASUS 3D glasses.))
I didn't want to tell you the name of the tablet (because it would cause a violent negative reaction) but it's a Polaroid, designed by Southern Telecom. I work for a store that sells it, and bought it on impulse for $40. There are a few good things one can say about it, but "elegant operation" isn't one of them. One must be patient.
c80f0f1006