Neomode Custom ROM 3.1 screen scaling fix (please ignore, apperantly this was already fixed)

[Pihkal]

Please ignore, It was brought to my attention that this was fixed before.



Hi all,

I've already posted this in the NCR 3.1 thread but for convenience of future reference I think it deserves its own thread as this is a problem many people are facing.

Most likely I'm not the only person getting annoyed by the screen scaling not being persistent (sticking after a reboot) so I decided to try to figure out how to fix it.
I've succeeded in doing this.


Here's how:

[METHOD 1, using Script Manager]

1. create a file, I've called mine scaler.sh
2. copy/paste this code into it:

echo xscale=100 >  /sys/devices/platform/rk-fb/graphics/fb0/scale
echo yscale=100 >  /sys/devices/platform/rk-fb/graphics/fb0/scale

3. Save the file and optionally chmod it using this command in the terminal:

chmod 777 yourfile

example: chmod 777 scaler.sh

4. Install Scriptmanager

https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=nl

5. Start SM and navigate to the script you've created in step 3
6. Select run as root and run on boot in SM.
7. Save and exit SM
8. Reboot

[METHOD 2, using init.d -> advantage: screen scale is correct immediatly!]

1. Download and install Root Browser

https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree

2. Navigate to /system/etc/init.d
3. Open file: 99SuperSUDaemon and add this code to the end of the file:

echo xscale=100 >  /sys/devices/platform/rk-fb/graphics/fb0/scale
echo yscale=100 >  /sys/devices/platform/rk-fb/graphics/fb0/scale

4. Save the file and reboot!

That's it, when using method 1 the screen will re-scale after boot automatically, when using method 2 the screen will have the correct scale immediatly.

Hope this helps some people who are having the same issue.

ENJOY!

Regards

[roooii]

Could you show me in which ROM this was fixed?

[Pihkal]

Could you show me in which ROM this was fixed?

I've been told someone posted something similar in the NCR 3.1 thread.
But the real solution, as this is merely a workaround, is replacing the displayd file if I remember correctly.
That can also be found in the NCR 3.1 thread.

Regards