Resolution on 1920x1080 lcd monitor only 960x460?

I have a MX 3 android TV box that I have plugged into a Hanns.G HT231 multi 10 touch HD monitor so I can make a big mixing console using Lemur. The problem is that on the android app the display isn't the correct size as the mixer is too big and will not fit on my screen without scrolling up and down and side to side. In Lemur in the "settings" page the resolution says its 960x460 and I can't find away of changing this. In the Lemur editor on my windows PC I have set "Manage resolution" to be 1920x1080 and I can see this change in the editor.

How can I set Lemur to display the correct resolution on my Monitor?

first of all, I have no answer to your question. And I guess most Lemur users don't know either.

But the idea is brilliant. I was thinking about buying an all-in-one touch-monitor/Android computer like the Acer DA220HQL (around 230 SFR or Dollars) to run Lemur at 1080p resolution. That would be just great if it works. I guess we just have to wait until there are more Lemur users with such devices who can tell how it works (resolution, graphics, CPU power, wifi).

my android device is rooted so i am looking for a way to change the resolution either by the android operating system itself or through lemur.

I get a similar quasi-halved (or quartered, by area) resolution with my rooted Nook HD running CyanogenMod: 1440x900 screen, but Lemur sees it as 720x370.

No problems with the display on my Asus tablet, which is 1920x1080 and Lemur sees it as 1920x988 (I'm guessing the Android bottom bar accounts for the shorter vertical).

first, what does "rooted" mean? I have no experience with Android devices.

Second, what Asus tablet are you using? Does Lemur run well? Does the graphics stutter or do you have high CPU usage when you run a Lemur template with 200 Knob objects?

Rooting just means gaining "privileged control" (administrator-level permissions, etc.). It's not essential, but in the case of my Nook tablet, it was stuck on Android 4.0 which won't run Lemur. So, I replaced the firmware.

My Asus is a P1801-T. It's usually sold as part of an all-in-one PC. With Lemur 5.2, it won't display certain font sizes properly, but Liine have told me this will be fixed in the next release.

Phil999 wrote:Does Lemur run well? Does the graphics stutter or do you have high CPU usage when you run a Lemur template with 200 Knob objects?

I haven't tested it a great deal, but I can tell you that it grinds to halt when I try to run this mixer...

https://liine.net/en/community/user-library/view/405/

Oh, and there's a deleting projects issue that I've posted about elsewhere.

I see. This mixer template is indeed a bit heavy, but it runs fairly well on an iPad2. A bit slow, but it's running. So I guess in order to run it smoothly the Android device must have some decent CPU/GPU. And quite some processing power for larger templates.

Thank you for this info. Looks like it is not that easy to have a big screen Lemur.

Try with 1890x980, if that works for you please comment.
Adrián

Would love to try that Jazzbeat but the resolution isn't changing no matter what I say.

Lemur can work at any size, but resolution is set per-project. Use Lemur Editor to set the resolution of your project or to resize an existing project. You can see the resolution of your particular device in the Lemur app settings screen. Use the values displayed there in the Lemur Editor.

In some cases, the resolution of the device might be wrongly reported from Android OS to Lemur. You can always use whatever resolution you like in Lemur Editor and send that template to Lemur, effectively forcing whatever resolution you like.

For others experiencing incorrect resolutions, the following app seems to have solved this for me (requires root on 4.3+). You have to confirm new settings within a time period, so it will restore the native settings if something goes amiss. Even so, be careful how you use it:

https://play.google.com/store/apps/details?id=com.nomone.resolution_changer

Curiously, on my tablet (Nook HD running CyanogenMod) all I had to do was alter the DPI slightly, from 240 to 238, not change the resolution.

Screenshot at native settings: http://i.imgur.com/S6ZREe4.png

Screenshot at "NOMoned" settings: http://i.imgur.com/CkggI9i.png

nick_liine wrote:Lemur can work at any size, but resolution is set per-project. Use Lemur Editor to set the resolution of your project or to resize an existing project. You can see the resolution of your particular device in the Lemur app settings screen. Use the values displayed there in the Lemur Editor.

In some cases, the resolution of the device might be wrongly reported from Android OS to Lemur. You can always use whatever resolution you like in Lemur Editor and send that template to Lemur, effectively forcing whatever resolution you like.

Hi Nick, trouble here is that Lemur imposes minimum height/width on all objects, and if a template is made for something larger, and utilizes these minimum size requirements, then you try to re-size the template to a smaller resolution or you're SOL, stuck rebuilding the entire thing from a UI standpoint

Ozymandias wrote:For others experiencing incorrect resolutions, the following app seems to have solved this for me (requires root on 4.3+). You have to confirm new settings within a time period, so it will restore the native settings if something goes amiss. Even so, be careful how you use it:

https://play.google.com/store/apps/details?id=com.nomone.resolution_changer

Curiously, on my tablet (Nook HD running CyanogenMod) all I had to do was alter the DPI slightly, from 240 to 238, not change the resolution.

Screenshot at native settings: http://i.imgur.com/S6ZREe4.png

Screenshot at "NOMoned" settings: http://i.imgur.com/CkggI9i.png

Just saw what studiodaz was doing with his setup last week and immediatley bought something similar. I am rooted and fighting like hell to get the resolution to change but it won't budge, or if it does it wont sustain the changes no matter which app i use

Ozymandias wrote:For others experiencing incorrect resolutions, the following app seems to have solved this for me (requires root on 4.3+). You have to confirm new settings within a time period, so it will restore the native settings if something goes amiss. Even so, be careful how you use it:

https://play.google.com/store/apps/details?id=com.nomone.resolution_changer

Curiously, on my tablet (Nook HD running CyanogenMod) all I had to do was alter the DPI slightly, from 240 to 238, not change the resolution.

Same story here, I tried maybe 10 different apps for adjusting pixel density on a rooted MX3 TV box but only when I tried that one did it actually take effect; even stranger was that I had to explicitly allow it su/root access (it was blocked by default with no dialog asking for permission) where as the others prompted me to grant permission.

I just changed my resolution from 240 to 239 and suddenly lemur recognized the correct screen size, much thanks for this I was about ready to tear into the APK and try to hard code the values myself.

Here is traxus control traktor (regretabbly built in a 4:3 aspect ratio) running on an Acer 23 inch monitor, with iPad 2 for size comparison:

11025987_1539892776290784_3479989552794894443_n.jpg

I have Lemur running on a 1920x1080 27" ASUS touchscreen with a Tronfy Android box. The NOMone resolution changer fixes the problem of the wrong resolution, but this needs to be rerun every time the system is switched on.

Is there a permanent solution for this? Is it an Android OS bug or a Lemur bug? Or is there a better Android box that I should be using?

Hoping that this was a bug in Android version 4, I purchased a new Android TV box running Android version 5.1 "Lollypop." (The YCCTEAM Kodi i68)

Unfortunately, the problem is still there. This seems to be a bug in Lemur. Liine have told me that this is not a supported use case so I am not hopeful for a fix. ("But let us know what you find.")

We have used the "NOMone resolution changer" app to change Android resolution and it works –- as long as the unit is on. You just change it from 1920x1080 at 240dpi to 238 dpi and it looks great. But as soon as we restart it reverts to to giant type mode, 960x486. I tried changing the project to the 960x486 resolution that Lemur wants to use, but not only does it look awful, the text doesn't fit on the screen even at 8pt (the minimum).

I created this system for a big name client and we are very frustrated. He is a long-time Lemur user (since the hardware). I'm on the hook to make this work and I have run out of ideas. If possible, please look at Lemur on an Android TV box (around $90) and 1080 HDTV (around $99). I will send you this Android box for testing although I am in the USA. This is a killer system if we can make it work.

Thank you for your help.

If you're getting desperate, you might want to look at using a TV box with a CyanogenMod build available for it. Since version 12.1, CM now has DPI adjustment built into the system settings, so you don't have to rely on an app to alter it.

Ozymandias wrote:If you're getting desperate, you might want to look at using a TV box with a CyanogenMod build available for it. Since version 12.1, CM now has DPI adjustment built into the system settings, so you don't have to rely on an app to alter it.

Yes, very interested! I'll check this out. Looks like the Google Nexus is the one to use? Thank you.

Have been trying to install Cyanogen on a Google Nexus Player but it's not working.

Ugggh are we ever going to fix this bug? I will personally buy a TV set box and ship it to Liine if it means fixing the bug.