title: How init.rc setprop works
body: <p>I have android 8 from nxp and using it on sabresd board.
  I am trying to change dpi settings through setprop settings
  So I have put this iside init.${hardware}.rc on boot event</p>
  
  <pre><code># Set the density to 160dpi, default 128dpi is not good
  # Set the density to 128 dpi for 480x800, 7 inch.
   setprop ro.sf.lcd_density 128
  </code></pre>
  
  <p>The device works fine and if I do this</p>
  
  <pre><code>wm density
  Physical density:128
  </code></pre>
  
  <p>Now I put this dpi setting in kernel command line</p>
  
  <pre><code>androidboot.sf.lcd_density=128
  </code></pre>
  
  <p>but I do not see device to be in 128 dpi setting. Also </p>
  
  <pre><code>wm density
  Physical density:160
  </code></pre>
  
  <p>Now this baffles me.Who gave 160dpi settings?</p>
  
  <ol>
  <li><p>How putting setprop in init.$hardware.rc affects the display but not in kernel command line.</p></li>
  <li><p>Who really processes setprop.
  I tried putting prints like this</p>
  
  <p>on boot<br>
  exec /system/bin/echo "Trigger test E"</p></li>
  </ol>
  
  <p>I saw nothing, so does that mean boot event never happened?</p>