FORUMS

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

[Q] Improved Refresh-Rate on 2.1?

60 posts
Thanks Meter: 33
 
By jleecong, Member on 5th January 2011, 05:14 PM
Post Reply Subscribe to Thread Email Thread
Per the Nookie Froyo thread they have a suggestion to increase the refresh rate to 68000 to stop/reduce flicker.

I noticed a similar flicker on "stock" 2.1 and checked /sys/devices/omapdss/display0/timings only to find out it is also set at 48000. I increased it to 68000, but it is reset after each reboot.

What is the proper refresh rate? Anyone else notice a flicker on the stock ROM?
 
 
5th January 2011, 09:25 PM |#2  
Senior Member
Thanks Meter: 632
 
Donate to Me
More
Quote:
Originally Posted by jleecong

Per the Nookie Froyo thread they have a suggestion to increase the refresh rate to 68000 to stop/reduce flicker.

I noticed a similar flicker on "stock" 2.1 and checked /sys/devices/omapdss/display0/timings only to find out it is also set at 48000. I increased it to 68000, but it is reset after each reboot.

What is the proper refresh rate? Anyone else notice a flicker on the stock ROM?

what process did you use to modify the file?
5th January 2011, 09:56 PM |#3  
OP Member
Thanks Meter: 33
 
More
Quote:
Originally Posted by paleh0rse

what process did you use to modify the file?

I used the following from the thread I linked.
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
5th January 2011, 09:59 PM |#4  
Senior Member
Thanks Meter: 632
 
Donate to Me
More
Quote:
Originally Posted by jleecong

I used the following from the thread I linked.

Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

Did you su and mount as r/w first?
The Following User Says Thank You to paleh0rse For This Useful Post: [ View ]
5th January 2011, 10:04 PM |#5  
Senior Member
Flag Central Kentucky
Thanks Meter: 1,160
 
More
Quote:
Originally Posted by paleh0rse

Did you su and mount as r/w first?

You don't remount /sys
5th January 2011, 10:23 PM |#6  
Member
Thanks Meter: 2
 
More
so does anyone know how to make this stick after boot?
6th January 2011, 12:23 AM |#7  
Member
Thanks Meter: 83
 
More
Quote:
Originally Posted by dennisi01

so does anyone know how to make this stick after boot?

See the thread I just made: http://forum.xda-developers.com/showthread.php?t=901791
The Following User Says Thank You to JoshMiers For This Useful Post: [ View ]
6th January 2011, 01:11 AM |#8  
gedster314's Avatar
Senior Member
Oxnard, Ca
Thanks Meter: 114
 
More
Quote:
Originally Posted by jleecong

I used the following from the thread I linked.

Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

Quote:

Originally Posted by dennisi01
so does anyone know how to make this stick after boot?
See the thread I just made: http://forum.xda-developers.com/showthread.php?t=901791


Thank you both. Seems to work. Now I know how to run my own scripts afterboot.
6th January 2011, 06:37 AM |#9  
Senior Member
Thanks Meter: 8
 
More
Does that mean we add the
Quote:

adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

at the end of the clrbootcount.sh text to have it run that command to fix the refresh and make it stick?
6th January 2011, 10:24 AM |#10  
Senior Member
Flag Midland, MI
Thanks Meter: 7
 
More
I did this (as I posted in the nook flicker thread):

I did a CAT on immediately after, and it had defaulted instead to 66461 instead of 68000 (maximum rate for the chip?)

Of course it also cleared upon reboot. Should I have seen a flicker improvement right away?
6th January 2011, 11:08 AM |#11  
here.david's Avatar
Senior Member
Flag Sonoma, CA
Thanks Meter: 30
 
More
Talking After clearing up all the posted suggestions listed here is what worked for me
Quote:
Originally Posted by greenmky

I did this (as I posted in the nook flicker thread):

I did a CAT on immediately after, and it had defaulted instead to 66461 instead of 68000 (maximum rate for the chip?)

Of course it also cleared upon reboot. Should I have seen a flicker improvement right away?

I also get 66461
------------------------
increase the refresh rate to 68000/66461 to stop/reduce flicker.
---------------------------------------------------------------------------
adb pull /system/bin/clrbootcount.sh

gedit clrbootcount.sh (assume you stay in specific dir)

add this to end of file and save
---------------------------------------------------
#run other commands
setprop persist.service.mount.umsauto 0
---------------------------------------------------
NEXT

adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push clrbootcount.sh /system/bin/clrbootcount.sh
adb shell chmod 755 /system/bin/clrbootcount.sh
adb shell mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system
adb shell reboot
--------------
NEXT

adb shell - NOW AT THE su # PROMPT (HAD NO LUCK WITH THE ADB SHELL and then commands all in one line)

cat /sys/devices/omapdss/display0/timings

mount -o remount,rw /dev/block/mmcblk0p5 /system

chmod 0755 /sys/devices/omapdss/display0/timings

echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

mount -o ro,remount -t ext2 /dev/block/mmcblk0p5 /system

reboot
-----------------------------------------------
NEXT

cat /sys/devices/omapdss/display0/timings
66461,1024/70/200/40,600/10/11/10
----------------------------------------------
Three reboots and I still have the changes...

Read all the posting listed if you want/need more details....
Last edited by here.david; 6th January 2011 at 11:11 AM.

Read More
Post Reply Subscribe to Thread

Tags
nook nookcolor
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes