[Q] Improved Refresh-Rate on 2.1?

Search This thread
By:
Advanced…
J

jleecong

Senior Member
Aug 30, 2007
63
33
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?
 
P

paleh0rse

Senior Member
Jan 4, 2011
1,942
627
jleecong said:
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?
Click to expand...
Click to collapse

what process did you use to modify the file?
 
gedster314

gedster314

Senior Member
Sep 7, 2007
936
126
Oxnard, Ca
G

greenmky

Senior Member
Aug 4, 2010
129
7
Midland, MI
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?
 
here.david

here.david

Senior Member
Jan 6, 2009
423
29
Sonoma, CA
After clearing up all the posted suggestions listed here is what worked for me

greenmky said:
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?
Click to expand...
Click to collapse

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:
K

khaytsus

Senior Member
Apr 8, 2008
7,258
1,175
Central Kentucky
here.david said:
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
Click to expand...
Click to collapse

You do not need to remount /system to write to /sys, and if you have chmod at all (unlikely) it would not be 755, it would be 644.
 
D

DatterBoy

Senior Member
Aug 17, 2010
142
8
here.david said:
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....
Click to expand...
Click to collapse
Tried all that and it did not stick. The final CAT showed a reversion to 48000. Still don't understand how the change to the clrbootcount.sh is supposed to make it stick but it isn't working.
 
K

khaytsus

Senior Member
Apr 8, 2008
7,258
1,175
Central Kentucky
DatterBoy said:
Tried all that and it did not stick. The final CAT showed a reversion to 48000. Still don't understand how the change to the clrbootcount.sh is supposed to make it stick but it isn't working.
Click to expand...
Click to collapse

It wouldn't. The change to the clrbootcount.sh only changes the automount, the change to the /sys var is completely temporary. I assume one could also put it in the clrbootcount.sh, assuming it isn't modified later by the system (negating the change made from the clrbootcount.sh script).
 
D

DatterBoy

Senior Member
Aug 17, 2010
142
8
Yeah. not sure how anyone is getting this to work but i can't figure it out. As a warning, modifying the clrbootcount.sh and trying to incorporate the fefresh change script has force firmware into boot loop to needing a factory reset twice now. Wonder if anyone else had the same experience.

The flicker is annoying and the refresh change works, but just won't stick.
 
J

JoshMiers

Senior Member
Feb 4, 2010
58
85
To get it to stick, follow the steps on my other thread http://xdaforums.com/showthread.php?t=901791.

When you edit clrbootcount.sh, add the following to the end:
Code: 
echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings

The final file (if you also want to disable automounting), will look like:
Code: 
#!/system/bin/sh
##################################################################################
#
# File          clrbootcount.sh
# Description	Clear the bootcount variable to 0 on successful boot
#
## 
# Run potential hook first.
/data/boot_complete_hook.sh
# Zero the boot count
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
#run other commands
setprop persist.service.mount.umsauto 0
echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
 
C

cutterjohn

Senior Member
Jul 30, 2010
529
21
While I've never really looked at this, but isn't the "refresh" "rate" largely irrelevant with LCD based screens? I'd always just assumed that even assigning them a "refresh" "rate" was just a place holder to make things work and not break CRT compatibility in drivers/display engines.
 
D

DatterBoy

Senior Member
Aug 17, 2010
142
8
cutterjohn said:
While I've never really looked at this, but isn't the "refresh" "rate" largely irrelevant with LCD based screens? I'd always just assumed that even assigning them a "refresh" "rate" was just a place holder to make things work and not break CRT compatibility in drivers/display engines.
Click to expand...
Click to collapse

Don't know if that is true, but I have seen flicker on other LCD panels that could be addressed with refresh changes. The echo command does work instantly on the NC but just won't hold for me.
 
J

jleecong

Senior Member
Aug 30, 2007
63
33
I have been playing with this and while the changes in clrbootcount.sh do stick, I'm unable to get it to either set the refresh rate or run a script that sets the refresh that I KNOW works from the terminal. Seems idealy this should be set in the ROM. Back to the terminal...

I should add I'm running 1.0.1 (Auto-Nooter 2.12.25) and also tried it in Nookie Froyo.
 
You must log in or register to reply here.

Similar threads

eyeballer
[GUIDE] Install CM7 or CM10 + Recovery to EMMC - ALL NOOK COLORS! (Updated:11/19/12)
Replies
878
Views
511K
LKJEFoi234
LKJEFoi234
leapinlar
[GUIDE] Nook Color Installation Guide for CM7/CM9/CM10/CM10.1/CM10.2/CM11 on SD
Replies
793
Views
398K
H
Helmut7
nootered
[HOW-TO] : Restore Nook Color back to stock EASILY!
Replies
190
Views
185K
leapinlar
leapinlar
D
The status of Android 3.1 Honeycomb on the Nook Color
Replies
160
Views
139K
L
luigi90210
RileyGrant
  • Sticky
Dummies Guide to Fixing 'My Nook Won't Boot'
Replies
318
Views
166K
PharmD208
PharmD208

Top Liked Posts

24 Hours All time

New posts