Latest kernel as a parameter to change the number of fake vsync.
To change value you can simply do:
Code:
echo NUMBER > /sys/module/msm_fb/parameters/fake_vsync_count
the default number is 10.
If you have best results with other number please post it here!
(also write if you overclock something)
The settings are not saved so if you have issue just reboot
Ok, underclock with roguetools to 250mhz.
I have 2 sync accounts, 4 widgets: fancy, music, tweeter and facebook (both the oficial), on two screns.
So, fake_vsync_count set to 1.
Phone off, let it cool to be sure to enter standby.
Phone on, whitescreen, giberish color screen... phone off again due to no unlock before timeout. never saw the image.
Again, phone on, white, giberish, fn+lft, counted about 20 fake_vsync_int. got the image on fn+right.
Ok, fake_vsync_count set to 20. All other maintains. Phone off....
Phone on, white, giberish, phone off... never saw the lock screen.
wait for standby and... again.
White, giberish, fn+left, counted about 20 fake_vsync_int again.
Re-attempt, this time with fn+right, got lock screen image again.
So, is the fake_vsync_counter really working ?
Info:
Clemsyn's BEST FROYO BUILD for 2.6.32 11/23/2010 STABLE
20101123 kernel. androidupdate.tgz installed. all on NAND
Everything else apears to be working good, better than ever actually...
Will try this steps with a good OC instead of UC.
UPD: and now, having the phone off while writing this post, i turned it on, and was greeted by the lockscreen. No white, no giberish. Console screen was FULL of fake_vsync_int. Top to bottom. Only a line of ds2746 in the middle.
fake v sync works (it you look in the kmsg you can see it) but there is no sleep between refresh (just for now)
question
where is this vsync file placed?
Please don't double post.
The vsync is not a file.
There is a parameter for the module msm_fb (as you can see in the first post) and the code inside the module msm_fb.
No effect here. Tried values 1, 2, 5, 15, 20, 30, 50, 100, 500, 1000
White screen allways lasts about 1 second. If it wakes up in console screen, it stays white untill i press fn+right. Cpu is at 500mhz.
V3rt!g(o) said:
No effect here. Tried values 1, 2, 5, 15, 20, 30, 50, 100, 500, 1000
White screen allways lasts about 1 second. If it wakes up in console screen, it stays white untill i press fn+right. Cpu is at 500mhz.
Click to expand...
Click to collapse
It will only really have an effect on the kaisers that haven't been overclocked and are using the heavier builds. Essentially it isn't to make the screen turn on faster or the white screen shorter. It is to make sure the phone screen actually turns on rather than being too slow and timing out and not being able to get into the phone.
damn
i set it to 20,but i dont see any diference ...but this thing afects my phone? (the white screen thing),if it is i will switch back to WM :-s
Related
[Q] [Idea] Overclocked and have the "wake-up and screen stays black" problem?
I'm running CM6.1 and using Pershoot's kernel, and running at 1.5ghz, on-demand. Probably once a day, I have the issue where a call will come in, or I'll press the power button, or I'll slide out the keyboard, and the screen will stay black (though the backlight for the soft-keys does come on).
I noticed that I can appear to interact with the screen still (answer a call by swiping where the answer slider is, even though I can't see it), which indicates that it's simply the backlight not being turned on.
For others that have the same problem, the next time it happens, try pressing your camera button to open the camera application. For me, the screen comes right up as soon as the application opens (the camera application sets your backlight to high while in it). Anyone else?
I'm going to take a look at the wakeup code this afternoon, I have an idea for a _hacky_ fix that can be done.
I also wanted to confirm - do others have the same problem if not overclocked?
I've been getting that a lot too before (more than once a day for 2 weeks) until I got desperate and wipe/reflashed CM6.1.1 and I haven't seen it in the last 3 days.
I don't know anything so maybe its coincidental. My OC settings are the same as before. The only difference this time was i wipe/factory reset before flashing CM6.1.1.
instead of flashing CM6.1.1 on top of CM6.1 which was what i did 3 weeks ago.
What does your setcpu profiles look like? Set a profile for when you turn the screen off to set the cpu to 245/245. Then set a new one at xxx/806 conservative (xxx being the freq you desire)
Test it out and let me know how it works out.
PanCubano,
Others have suspected that it has to do with the CPU being at high speed the split second before you wake the device, and I agree that it's likely the problem.
Unfortunately it's quite hard to prove that the problem has gone away.
Hi everyone!
I've installed Myn's Warm Donut and it works, but when i lock the phone with power button i have white screen! I've tried all panels! What can i do?
Thanks for the answer!
When you lock or when you turn the screen on again?
EVERY android kernel has a bug with screen wake up. If, in your case that happens, its perfectly normal, that white screen stays for like only a second and then android lock screen shows up. Press menu key and ur device will unlock. Sometimes that white screen stays, in that case just press Menu color again if that white screen still stays, you need to change the panel. Its impossible that white screen stays for infinite time. Mind to have a radio version greater than 1.65
dark_prince said:
EVERY android kernel has a bug with screen wake up. If, in your case that happens, its perfectly normal, that white screen stays for like only a second and then android lock screen shows up. Press menu key and ur device will unlock. Sometimes that white screen stays, in that case just press Menu color again if that white screen still stays, you need to change the panel. Its impossible that white screen stays for infinite time. Mind to have a radio version greater than 1.65
Click to expand...
Click to collapse
ah ok...the situation is exactly as you describe! I thought it was an only mine problem! Thanks!
i have the same bug. what panel works fine?
sicstifor said:
i have the same bug. what panel works fine?
Click to expand...
Click to collapse
Colours messed up?
white screen keeps there FOREVER?
Its time to change panel, try using Type 1 first, later try type 2 and type 3 is for exceptional cases
Every kaiser device has different panel type. Mine, HTC TyTn II KAIS130 has panel type 1 and another guy over here has same device he's using Panel 1 too. Warbyte has KAIS130 as well but he's using Panel 2. Its you who figure out that THIS panel is not working fine, lets try another. At maximum u understand it after two tries. And mostly you get a fine screen with fine colours in first try.
Only CHANGE panel if that white gibberish screen stays on for ever.
hi, im running android off my memory card and ive noticed a big battery drain, what do i need to do to fix that.
independent said:
hi, im running android off my memory card and ive noticed a big battery drain, what do i need to do to fix that.
Click to expand...
Click to collapse
Disable Location feature, disable GPS Satellites, set Screen brightness to minimum. Keep Wifi off, disable Automatic sync, keep your memory clean and use a task manager, use 2G mode if you are not using 3G. Disable Data connection and enable it only when needed
Is there any kind of mod I can do that dims my screen after say 15s of inactivity?
I don't want the screen to go off (i have it set at 5 min to turn off), but it would be good on the battery if it goes dim (the state that the screen goes 3s before going off).
Basically when I text, I feel like i'm constantly turning the screen on and off and wearing out my physical keys.
You might want to check out RootDim, but it does not have an "after 15s" rule like you were talking about, it's just always what you set it to. The horrible thing about this app is there is no "set on boot" feature and the dev refused to add one, making the app a pain in the ass to use unless you want to manually set the dim level after every reboot, maybe others don't reboot as much as me I dunno.
The brightness of the LED flashlight can be changed by modifying the value in /sys/class/leds/flashlight/brightness (or alternatively /sys/devices/platform/flashlight.0/leds/flashlight/brightness).
I've managed to vary the brightness, however there seem to be only 3 settings which stay (0, 64 and 128).
The max_brightness file is set to 255, which implies the brightness could be doubled (not that it necessarily should) - however setting it to that will increase the brightness to "very bright" and then switch off (presumably to "0") shortly after. I also tried 192, and the same things happens (I'm not sure if the brightness is set to "192" or "255" for that case before turning off).
This implies the levels are being overwritten shortly after to "0", "64" or "128" by the device/system.
Kevin (the author of TeslaCoil) writes saying that HTC devices only support 3 brightness levels (can't post outside links as under 10 posts):
ht[REMOVE_ME]tp://stackoverflow.com/questions/5970188/can-i-change-the-led-intensity-of-an-android-device
Is there any way to bypass these preset levels and have the LED at e.g. 255 or any intermediate level in the range [0,255]? I'm making the assumption that the LED's brightness can be comfortably varied without damaging it (please say if you know otherwise ).
Cheers, Arite.
Not sure if this will help, but there is a camera apk in the oxygen rom that has a high brightness mode. Might be worth having a look at that to see what level it's setting it to?
Thanks - I'll check it out. The default/normal brightness is actually 64 (I thought it was 128), and then the can be raised to 128. The level is forgotten after though (goes back to 64). Will have a look at the Oxygen camera.
Cheers, Arite.
Sent from my HTC Desire using xda app-developers app
Of course by camera apk, I did mean torch apk
Ah OK, cheers .
Arite.
Sent from my HTC Desire using xda app-developers app
I did: cat /sys/class/leds/flashlight/brightness with the brightness on normal and then high, the results were 127 and 3.
Yes, unexpected but a brightness of 3 was much higher than that of 127. When I tried setting the brightness to 3 manually, as you experienced it automatically turns off.
I can only imagine the app either uses a loop or turns off a safety somewhere before ramping up the brightness (it does require root).
Edit: Also, the source can be found here: http://code.google.com/p/n1torch/source/checkout
I tried values of 1, 2, 3 and 4: values of 1, 2, and 4 just enable the normal "64" brightness. 3 appears to be the max brightness (same as 255) and turns off shortly after.
Interesting how "3" seems to be a special value. This, and 255 can be kept on by continuously re-setting the value - so a timed loop could be written to have it "permanently" on like langers2k said. Don't think I'll do that though as there might be a good reason it get turned off shortly after.
Anyway - I think there are only 4 possible states: off, "normal", "brighter" and "max brightness" (which turns off after something like 750ms). TBH I'm not sure a LEDs intensity can be smoothly adjust from off to max - not like an incandescent bulb. It was an interesting experiment with it anyway.
Cheers, Arite.
Hi
Have been using tab 3 for three days now and just today noticed that the screen turns off itself.
When the tablet lays down on the desk just a touch near power / volume buttons turns the display off.
At first thought it was due to overclocking app (ROM toolbox ) but turned off all profiles and again screen turns off when slightly touched on the edge.
Kernel: v13-10-14.3dg541fc6 - [email protected] #9
Has anyone experienced similar issues with tab 3_8 ?
Just a shot in the dark, is your screen display setting set too soon. I think 30sec is default. I set mine to 5min. Otherwise not sure..
kindlefire39 said:
Just a shot in the dark, is your screen display setting set too soon. I think 30sec is default. I set mine to 5min. Otherwise not sure..
Click to expand...
Click to collapse
Screen timeout inset to 10 mins
This must be something with cpu-overclocking as now without any profiles on screen never goes black again.
Just need time to play with profiles / different apps or maybe some of you can share yours overclocking experience
Good to know!