| 
 | 
	
     
     
    
    Posted at  12/7/2016 03:31:45
        
  
     
 
     
  
   
  Only Author 
    
 
  	             
 
6#
 
        
 
I decided to change  
In kernel fie rockchip-hdmi.h  
#define HDMI_AUTO_CONFIG               true                
instead of false 
 
I had to root to be able to see /cache/display.cfg file 
 
On booting it show this now in /cache/display.cfg file 
 
display=0,iface=4,enable=1,mode=1920x1080p-60,colormode=0 
display=0,iface=1,enable=0,mode=720x576i-50,colormode=0,colormode=0,colormode=0,colormode=0,colormode=0 
 
And in Android Settings - Display it shows 1920x1080x60 
 
After changing Android Display Settings to 720p@60hz file shows 
 
display=0,iface=4,enable=1,mode=1280x720p-60,colormode=0 
display=0,iface=1,enable=0,mode=720x576i-50,colormode=0,colormode=0,colormode=0,colormode=0 
 
After rebooting /cache/display.cfg file still shows the same 
display=0,iface=4,enable=1,mode=1280x720p-60,colormode=0 
display=0,iface=1,enable=0,mode=720x576i-50,colormode=0,colormode=0,colormode=0,colormode=0 
But if I go into Android Display Settings HDMI, it shows 1920x1080x60 as the default selected and highlighted resolution which is not the same as in the /cache/display.cfg 
So there is a mismatch. 
When booting there must be something that overwrites the resolution maybe from uboot, kernel or system to use a different resolution. 
 
The /cache/display.cfg file has the following permissions on my system 
owner - root 
group - root 
permissions - 600 rw 
so root user has rw permission and other users none 
Is this perhaps the problem? 
 
Or can this commit maybe interfere or something else? 
https://bitbucket.org/T-Firefly/ ... 8ebf203dc17a91c60ae 
 
So if a user has a 4K tv he can't use 720p resolution after reboot while another user with a 4K tv uses 1080p can't use it after a reboot since resolution will default to 4K, the highest one instead. |   
 
 
 
 |