DroiX Christmas Sale - Give the gift of Tech

Terry West

New Member
Jan 9, 2015
11
1
1
I have recently 'migrated' from an IMX6 to a T8 - both connected to the same (Panasonic) TV which, conveniently, has an on-screen display showing it's input resolution & refresh rate whenever they change.
The IMX6 display is set to 'auto-detect best TV resolution', detects 1080p @60Hz and the TV confirms that that is what it receives.
The T8, on the other hand, when display is set to 'auto-detect', detects only 720p @60Hz and again the TV confirms that that is its input. If, however, I manually select 1080p @60Hz, the TV confirms that this setting is applied and the setting will then persist perfectly until the T8 is shut down. On restart, however, the T8 always reverts to 720p @60Hz and, if I want 1080p, I must manually set it as before.
What I have noticed, though, is that the T8 initially boots into the 1080p @60Hz with which it was shut down but that at the moment the boot-up screens change from the static Droidbox logo to the (rather strange) animated gridded spheroidal, the resolution immediately changes down to 720p @60Hz - and this setting then persists when boot is complete. My impression, therefore, is that the animation forces 720p and fails to restore 1080p once it is finished.
I offer these observations to discover whether others can confirm them and, if so, to suggest that the Droidbox developers take note with a view to correcting what seems to me to be an irritating flaw in an otherwise excellent box.
 
Last edited:

Terry West

New Member
Jan 9, 2015
11
1
1
Thanks for your reply but please read mine again ... that's clearly what I describe having done! Nevertheless, as you say, it SHOULD stay like that until you change it - even after a reboot - but it doesn't!
 

David Savage

Well-Known Member
Aug 3, 2014
2,631
993
113
Somewhere over the rainbow
Ok, I did read your post....I have a T8 with a Panasonic GT50 and once I've set the screen in the display,its done, I've never had to change it. I also have a imx6 as well and like you said stays at 1080p 60hz.
Turn off auto detect see if this helps..if you've done this, try going into setting, more then more setting, and display see if there's any adjustments there.

Dave
 

ChrisM

Guest
Staff member
Jul 15, 2014
4,069
655
113
Cardiff, UK
ChrisMerriman.com

I've recorded how it goes on my T8. Can you copy it stage by stage, reboot and see if the problems reoccur. Ignore any video weirdness you see going on, the video recording gets confused by resolution changes.
 

Terry West

New Member
Jan 9, 2015
11
1
1
Perhaps I should make it plain that I am an experienced Android developer and very familiar with how to set up an Android box and I think it's pretty clear from my first post that I already know how to disable HDMI auto-detection and to set the HDMI Output Mode Setting. I am not therefore looking for instructions on how to do this - that was not the point of my post.
My point was that a 1080p display setting doesn't persist across a reboot on my T8 - and that this seems to be because the resolution, which is initially correct at 1080p while the static Droidbox logo is showing, is reset down to 720p by the animated spheroid before it starts running.
Dave: There are no other resolution adjustments in the 'standard' Android Display Settings within "More Settings".
SS: Your video, unfortunately, is irrelevant as it shows a 720 setting persisting across a reboot - just as it does on my box. Do you perhaps have one similar which demonstrates that your T8 retains a manually-set 1080 resolution across a reboot?
 
Last edited:
  • Like
Reactions: Eddyad

David Savage

Well-Known Member
Aug 3, 2014
2,631
993
113
Somewhere over the rainbow
Like I said in my post, my T8 stays at 1080p @ 60hz all the time even after reboot. That's what I don't understand, so I don't no what the problem was. As for the video SS was showing you how to set any resolution being 720p or 1080.
Wish you all the best in finding a solution to this, good luck.
 

ChrisM

Guest
Staff member
Jul 15, 2014
4,069
655
113
Cardiff, UK
ChrisMerriman.com
Terry, sorry to have annoyed you. The video was meant as in instruction, nor as showing 1080. I asked you to compare yours, step by step. Amend if needed. Compare at which point something differed.
 

Terry West

New Member
Jan 9, 2015
11
1
1
Not annoyed ... but definitely frustrated.
I suppose the bottom line is that what I am trying to do is to:
a) Discover if what appears to be a bug in the firmware of my box can be reproduced by others.
b) If so, to report it as a confirmed bug
c) To offer a clue to where it's correction might be sought.
... all in the interests of hoping to contribute to making an already excellent box better!
Am I barking up the wrong tree here in this forum? Perhaps there is another mechanism for bug-reporting that I have not yet come across - if so, I would be delighted to use it.
In the meanwhile, colrob1 seems to confirm that his box behaves the same as mine, suggesting that there is indeed a bug. However, DS doesn't see it, suggesting not. It will be interesting to hear from SS how his box behaves.
SS: Following your video step by step, amended as needed to set a 1080 instead of 720 resolution, my box differs as I have already described - the 1080 setting does not persist after the re-boot.
 

David Savage

Well-Known Member
Aug 3, 2014
2,631
993
113
Somewhere over the rainbow
Have you tried another HDMi cable or even change the HDMi slot its in the tv. Say HDMi 1, I have my box going to a Oppo blu ray player and then the tv. My player is already set as well to 1080p@60hz.
 

Terry West

New Member
Jan 9, 2015
11
1
1
DS: Yes, I've changed both HDMI cable and HDMI slot - first thing I tried! Interesting that your box is not directly connected to a TV, though ... perhaps that's why you don't have the same problem as colrob1 and I. For interest, what resolution do you get if you set HDMI auto-detection ON?
 

ChrisM

Guest
Staff member
Jul 15, 2014
4,069
655
113
Cardiff, UK
ChrisMerriman.com
HDMI mode auto detecting the wrong resolution seems to happen when the set doesn't return an accurate list. Turning this mode off obviously helps in situations where the wrong mode has been autoselected, but only when it survives the reboot.
@Terry West - Can we organize a remote control session during office-ish hours at all? I'd like to see whether the control method has any effect on the selected resolution being stored. I've seen the screen scale not being saved if you use a non-standard return/go back button, so wondering if we can narrow down how it occurs with me click on things instead. The number is at the top of https://DroidBOX.co.uk
 

marok

New Member
Mar 9, 2015
3
2
3
Don't know whether this helps, but this info was on another thread and may be relevant to your problem:-

Once you manually select 1080p @60Hz, make sure you use the return/go back button to exit the config area, otherwise it won't survive a reboot. If you're not certain about which key to press, turn off Auto Hide for the on screen buttons, and click the return/goback arrow there to save screen scales.
 

Terry West

New Member
Jan 9, 2015
11
1
1
Sorry for my absence ... I seem to have lost my email notifications for new messages here and assumed that the thread had died for lack of interest! My mistake.
SS: We could certainly try a remote control session if you think it would help but, to be honest, I doubt it will as I'm pretty sure that nothing I do is "non-standard". (Also, I'd need more detailed instructions as to how we would go about setting it up!). I think it might be more useful if I were to try and produce a video similar to yours that demonstrates more clearly the behaviour that I have been trying to describe. I'll have a go later today and post it here if/when I can.
 

Terry West

New Member
Jan 9, 2015
11
1
1
Not the best video in the world but the best I could do with a camera and, I think, shows clearly enough what I have been trying to describe.
Note:
1. The top-left corner of the TV displays the resolution it's receiving from the T8 each time it changes.
2. The T8's "HDMI auto-detection" sets its resolution to 720p @ 60Hz in spite of a) the TV being perfectly happy with 1080p @ 60Hz as a "manual" setting and b) that my IMX6, when connected to the same TV, sets its resolution to 1080p @ 60Hz when on "auto".
3. When the T8 is shut down, "HDMI auto-detection" is OFF and its resolution is manually set to 1080p @ 60Hz
4. On reboot, the T8 starts at the droidbox static logo with the same 1080p @ 60Hz resolution with which it was shut down. However, just before the start of the 'spheroid' animation, the resolution changes spontaneously to 720p @ 60Hz, the droidbox logo becomes briefly distorted before the animation starts and 720p @ 60Hz then persists as the T8's output resolution once the boot process has completed.

As I have suggested before, I believe this is a firmware bug amenable to correction by the droidbox developers - can anyone suggest an alternative explanation?
 

8bitDev

Moderator
Jul 2, 2015
706
117
43
Not the best video in the world but the best I could do with a camera and, I think, shows clearly enough what I have been trying to describe.
Note:
1. The top-left corner of the TV displays the resolution it's receiving from the T8 each time it changes.
2. The T8's "HDMI auto-detection" sets its resolution to 720p @ 60Hz in spite of a) the TV being perfectly happy with 1080p @ 60Hz as a "manual" setting and b) that my IMX6, when connected to the same TV, sets its resolution to 1080p @ 60Hz when on "auto".
3. When the T8 is shut down, "HDMI auto-detection" is OFF and its resolution is manually set to 1080p @ 60Hz
4. On reboot, the T8 starts at the droidbox static logo with the same 1080p @ 60Hz resolution with which it was shut down. However, just before the start of the 'spheroid' animation, the resolution changes spontaneously to 720p @ 60Hz, the droidbox logo becomes briefly distorted before the animation starts and 720p @ 60Hz then persists as the T8's output resolution once the boot process has completed.

As I have suggested before, I believe this is a firmware bug amenable to correction by the droidbox developers - can anyone suggest an alternative explanation?
This is happening because of TV set,try putting the lower than 60hz refresh rate,with same 1080p(i)resolution