Closed mbarnes-arrdude closed 4 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.93. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Hi, I'm sorry not to be able to help you much, I'll just try to answer some of your questions. First: MIPS 🎉 . Yay, I really laughed when I read it. Is this the NOVO7 tablet?
What are the more proper procedures for trying to get a weird device like this to work?
I'd say it's not so much the CPU arch but more the very old version of Android that makes it very hard to use with STF. We have an ARM-based Android 4.2.2 device here and it barely works (screen cap has severe corruption most of the time). Which version of Android is your device running? EDIT: From your logs I guess it's 4.1. Do you have any chance to update it?
Do I need to add an entry to the device database somewhere?
Nope. Unknown devices might show a bit less of useful information on the UI but should work nevertheless
I appreciate any help or pointers you might give me. I am evaluating STF for use in an in-house initiative for remote maintenance for kiosk's MCU UI adapter. So far with my high level testing, with a VPN setup, the system seems very solid with our newer displays, well within our risk tolerance for reliability. I must applaud you on your excellent project and am looking forward to diving deeper and working with it.
The problem I have is that a bunch of our units are this model... I was not involved in the decision... please be kind to me LOL
These are bare board devices for embedded displays and they are not branded. The exact model is hard to tell. It is likely a NOVO7 clone. It has the Ingenics MIPS-alike processor and similar device information to the Karbonn clone of the NOVO7. It is 4.1 as you saw.
I have not found a OS image for it above 4.1. I don't know if you know of anyone that has hacked one. It would be valuable to me for a lot of reasons to find a Lollipop or higher build (even the v4.2.2 Jellybean with the symptoms you describe might be workable), but I do not think that the toolchains released > 4.4 support this processor and I found no OTAs.
I have a weird device. It is old and unsupported by the NDK. It uses a mips processor (I can hear the groans from here).
Out of the box STF tries to load to the device the minicap exe and lib for the alternate abi
armeabi--v7a
but it fails to load the prebuilt:I have hacked a custom build of libjpeg-turbo and minicap for mips by naively adding the arch to the Application.mk files and adding the appropriate targets.
Testing minicap with autosize "seems" to work from the command line. To use it, I copied the bin and lib files into the prebuilt directory in source. In doing this I created the required directory structure. It seems to work great. STF recognizes the device, the arch, and the android version and injects my custom minicap and lib.
STF itself crashes sometimes at this point. If it does not crash, it is unable to show the screencap in the UI. Control buttons for orientation and display on/off work so the agent has some functionality.
When STF crashes it gives me this error:
When STF doesn't crash' it doesn't seem to be able to get the display info for the device:
What are the more proper procedures for trying to get a weird device like this to work?
Do I need to add an entry to the device database somewhere?