Related
I find the screen is too bright in dark areas even when set to the lowest setting. Is there anyway to lower it even more? I dont like how its 50% brightness or 0% brightness.
are there any 3rd party programs that have more control over the backlight?
http://www.omegaone.com/pocketpc/default.htm is one of the best software companies in my opinion. Here is some software which allows you to fine tune screen brightness http://www.omegaone.com/batterypack/pro/default.htm download a trial and install it and you then have to go into Start - Settings - Today - Items (tab at bottom) - Then tap Battery bar - Then select Customize - Select Brightness from one of the drop-down menus so you can have it adjusted on the home screen. I have the previous version and I find it great. If you have any problems let me know.
nice program, but I cant seem to get it to control the brightness. The switch keeps snapping back to the left most side. Maybe its not compatible with Blue Angels?
What operating system are you using?
WM2003se
I added rom and radio info to my sig
I just did a hard reset to make sure there wasnt any programs conflicting but that didnt fix it
It is just that I have upgraded my Blueangel to Tu-Ma 1.3 (WM5) and it allows you to change the brightness in 10% increments. So a thought is that you might want to upgrade yours. Here is the link explaining how to do it http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM5_WizardPort_v1.3-TuMa
Will keep a look out for screen brightness changing programs but at the moment a upgrade is all i can suggest.
WM5 natively allows you to do that? Or do you need battery pack pro?
Ive seriously considered upgrading but am worried about incompatibilities with alot of the programs Im using. Especially morphgear and Fpsce.
Yes it natively allows you to do that. About compatibility I have run programs designed for Windows Mobile 2002 with no problems but I know that some software just isn't compatible. So it depends on how much you use those programs that aren't compatible with WM5 whether it is worth upgrading.
Ok I have seen a lot of confusion over the months regarding the LCD Panel fitted to the Kaiser, I will attempt to answer most of these issues here.
Hardware: The kaiser series is fitted with a 2.8 inch 240x320 TFT LCD panel, which means that it 240 pixels wide by 320 pixels deep, the optimum density of this LCD panel is 143 Pixels per Inch.
Resolution: This refers to the screen resolution that the Operating System will use to display on the LCD panel, the 3 most common being 240x320, 320x428 and 320x480, the reason this is possible is that the OS is capable of fooling the display into using the fixed 240x320 panel to display more pixels, ( it does not really have more pixels, it just looks like it).
DPI: DPI or Dots Per Inch, also known as Density, and correctly known as PPI or Pixels Per Inch, this refers to the number of pixels the screen displays in a One Inch Square on the screen. As I noted above, the actual PPI of the LCD panel is 143 PPI, this is fixed by the hardware, and cannot really be changed, however since the LCD is software driven, it can be persuaded to look as if it is displaying more or less pixels in that same area.
Panel Type: This refers to the actual LCD panel fitted to your device, there are 3 types fitted to the Kaiser series, one manufactured by Sony, the other two by Topoly. While the 3 different types of panel are functionally identical, they differ at the electronic level. On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, so the panel type must be set in the parameters passed to the kernel at boot time, either in default.txt when booting from SD, or hardcoded in the NBH when booting from Nand. Also there is no easy way of telling which panel type is fitted to any given Kaiser, since the panel type was chosen by HTC depending on price and availability and stock at the time of manufacture, so any model of Kaiser can have any of these types fitted.
The main problems encountered with the display are usually solved by changing the Panel Type, either by editing default.txt, or reflashing the correct NBH, ( note that you can also edit the kernel parameters of an NBH using a Hex Editor, however this would be a relatively advanced method, since an error could cause major issues).
Changing screen resolution and density: As noted above there are 3 main resolutions used, 240x320, 320x428 and 320x480. These easy to change either by editing default.txt, or flashing an NBH, depending on how you run Android, resolution is usually a personal choice. Density is not as easy to change, although Rogue Tools by Myn, (available in Market, and discussed here: http://forum.xda-developers.com/showthread.php?t=667581), is excellent for this purpose, there are various common PPI settings, and again mostly personal choice, a little experimentation with resolution and density will allow you to find what you prefer.
Hope this helps clear things up a little
Thanks for this, it helps alot!
vertical lines issue
just to add to the above: the vertical lines issue some have is related to choosing the wrong panel type. Chosing the correct one will solve the problem.
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Dark-Side said:
Wrong panel make errors display, ok! But Can it lead to additional consumption of the battery?
Click to expand...
Click to collapse
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
zenity said:
I suspect it may, since display errors such as vertical streaks, pixel errors, colour issues etc are actually caused by a mismatch between the OS drivers and the actual physical electronics, and it's possible that the panel may demand more power than it would normally, I'd have to bench test this to be sure, but it's probably easier just to use the correct panel type setting.
The correct panel type should lead to a 'normal' demand on the battery.
Click to expand...
Click to collapse
I use panel 2... I go to use panel 3 to test this. panel 1 make for me pixel errors. I'll report here.
Thank you
EDIT: no difference between panel 2 or 3 on my kais130
Thanks! That helps a lot.
I havd a thought, which is to change a physical LCD panel for my kaiser, HVGA or VGA... Is that possible? I would look into some electronic files later...
i guess that our chip has max resolution only 320x240 so no higher resolution
but as I look in the pdadb.net there are some devices with higher resolution and same chipset as ours so perhaps it is possible
It is unlikely to be possible to use another panel, since there are a lot of differences with the interface, it's not just the chipset, but how it's wired, plus higher resolution panels may need extra address lines which are not present in our kaisers.
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
zenity said:
For those of you experimenting with LCD Density settings. You may wish to try the following density settings.
100
121
144
169
196
Remember, pixels are square, so the density settings should reflect this, also the extreme ends of this table are just that, extreme
Click to expand...
Click to collapse
density 106 works very well with 240x320 if the build is designed for 320x480. I'm using that on the CyanogenMod port. Haven't tried it with other builds though. I did try 107 once with another build but that did not turn out very well.
106? that should really look a little blurry, but I think it depends on the resolution that the build was designed for, however I think I'd find it a little small personally, have you tried 100? it should look clearer than 106, although I have noticed that some people just prefer a certain density regardless of the actual mathematically 'correct' one.
zenity said:
...
Panel Type:....
.... On Windows Mobile this difference can be detected by the OS, however on Android this is not possible, ...
Click to expand...
Click to collapse
So how do I detect which panel in winmo?
I don't like the idea of just stabbing blindly in the dark and hoping I get it right.
Basically? Stab in the dark, there is no way in wm or android to know which type is fitted, type 2 seems most common, and is usually a 'safe' default, if the graphics/colours are wrong, you probably have type 1, if you have issues waking from sleep then you probably have type 3. So try panel 2 first.
Sent from my HTC Dream using Tapatalk
I'm running Android on my HTC Tilt and am using panel 2. I tried panel 1 and the colors were off so Panel 2 seems good.
But the problem I am having is that when I open up the dialer, it doesn't fit correctly on the screen, the bar which shows which numbers you have entered covers up the numbers 1,2,3 and the sides are cropped.
Everything else seems to be fine why is the dialer messed up?
Should I try changing density its at default right now.
I personally like to use 110, but every time I open detail application on Market, it gave me force close. Facebook for Android does that too (I mean FC) whenever I open detail message or upload picture from gallery.. I've tried 106, 104 and 100 and still having the same problem.. it's not happening when I use 120 for density, everything seems work properly normal.. is that common or I have to do something to fix that problem?
Thats not normal behaviour for market, although it has been known to be a little flakey on some builds, however this is unlikely to be related to lcd density, since density only affects the visual appearance of the screen, not the OS itself.
Which Panel?2 or 3?
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
stajan said:
Am using HTC Tytn II and recently i tried almost all Android builds(donut,eclair,froyo) on my device.panel 1 shows some pixel errors and panel 2 and 3 makes no big difference for me, both settings showing a white flash screen on wake up!
and panel 3 i feel little smudge,not sure.panel 2 wake up with white flash screen and follows by grains(just like noisy TV screen).All these for two seconds.after that TYTN II behave normally.Any body can help me please?
Click to expand...
Click to collapse
As previously stated, panel 2 is the most common of all.
As for the white flash and grainy display, this is due to the fact that we have to "fake v-sync" in order to display anything on our screens. Remember, Android was not designed for our Kaisers, but developers got it to run, piece by little piece, really well on our devices. There will always be drawbacks to this as the hardware doesn't really meet the requirements of what Android was developed for.
If you want to see whats going on when you have a white screen or snow, slide the keyboard open and press "Fn-left softkey". this brings up a screen that shows you what Android is doing.
To return to the main screen, press "Fn-right softkey".
Hope this helps...
hello,
since the leaked Froyo Updates the screen is a little bit darker then before. Is it possbile to increase the screen brightness on froyo roms ?
Maybe this seems to be the reason Froyo saves more power then Eclair.
any ideas ?
thanks
Just go to settings/display/uncheck auto brightness and move the slider to your liking.
i have already moved the slider to maximum brightesns - but it not as bright as before with Eclair.
yeah. i have noticed this one too. have compared several times the brightness of the eclair to froyo and there is a great difference comparing the 100% brightness
Hmm, strange. I know by default the Froyo version has night mode on by default. I wonder if that has anything to do with it?
Try to use this app;ledefy
Is there someone who has already found a real solution? The thing with the brightness is very, very bad.
The screen goes dark after the vibration on boot progress. The kernel is load before, isn't it? Then normally this should be no problem to increase the screen brightness for the devs?
In hope, greetz from Germany!
echo 1 > /sys/class/leds/lcd-backlight/als
Click to expand...
Click to collapse
or use ledefy
slph said:
echo 1 > /sys/class/leds/lcd-backlight/als
Click to expand...
Click to collapse
How you can set this value after boot? Is there any init folder from where you could run a script?
download terminal emulator and run this command, this should fix the brightness (it did it for me) providing that your phone is rooted!
zakoo2 said:
download terminal emulator and run this command, this should fix the brightness (it did it for me) providing that your phone is rooted!
Click to expand...
Click to collapse
Right, but I won't do that each time after I rebooted my phone.
Great! Works fine....there's a way to auto execute this command on startup?
I don't know how to execute this command on startup but i'm using the ledefy app (ledefy.com). There you can set the increase brigthness fix and autostart on startup.
Furthermore it will give you a nice battery icon in the status bar with 1% steps and various other fixes...
ledefy does not work on CM7
becaus every time i switch of my screen, the brightness will be decreased to the CM7 default brightness. If i switch on my screen i can increas brightness again with ledefy.
What exactly does this line?
"echo 1 > /sys/class/leds/lcd-backlight/als"
Is it setting backlight fix to a MAX or is it increasing the range of control?
If it is increasing the range - is it works for automatic or manuel or both?
What is the default value to go back?
This is a two part question. What screen brightness do you usually leave your phone at? I leave mine on what seems to be 0 (see next paragraph for explanation) and my screen still always uses around 60-70% of my battery. I don't understand how it can use that much without the backlight on.
Next question - When adjusting the screen brightness and the slider is all the way to the left is that 0? I'm asking because every widget out there when set to 0 is a a few times brighter than when I manually move the slider all the way to the left. Also, after using a widget to toggle to 0 and I check in the display settings, the slider isn't all the way to the left.
So I'm wondering what is true 0? What the widgets set it to or with the slider all the way to the left? Could the slider being all the way to the left actually be hurting my battery life?
No zero on the slider is technically not zero. You can confirm this checking your brightness sysfs file. You have to decompile framework and adjust some numbers. We can take it down to true zero or slightly above which would be much dimmer.
I did this for the atrix. Im surprised it hasnt been done yet for the nexus.
I know it is not actually 0 because if it was I wouldn't be able to see anything on the screen.
Is there anyone that has insight on my questions though?
I dont understand your question. Zero is not true zero unless we mod the framework. So your backlight is not "off". I dont know why youre getting so much drain.
But we should mod this anyway. Use root explorer and go to sys/devices/omapdss/display0/a6e8aa0 and open the brightnesd file. Note that value with your slider at zero and you will see a reading of 30 (0-255). So we can lower that down to maybe 5-10 and zero on the slider will be much dimmer = battery saving.
I have a similar problem. The max brightness is piercing and the min brightness is just a tiny bit too dim.
I have tried used root explorer to change the maximum brightness from 255 to 100 hoping that the slider may be more granular after. For some reason however I cannot update the max brightness file. I have ensured that it is r/w mounted and tried changing the permissions too. It says that the changes have been made and the original backed up. When I reopen the file it hasn't changed.
BTW, my 'brightness' file is at 10 when placed at the minimum brightness.
Try the newest AOKP.
Brightness controls.
I actually have NEVER used auto brightness...even back in my OG days.
And my X days.
Even when custom auto-brightness options were around I ignored them.
I'd simply keep it at around %20 of the default lowest value.
BUT...this is slightly annoying when you step into the sun and can't see anything.
With the newest AOKP you can even set the amount of brightness changes.
I set up four values.
I've mine set up for a pitch black room to lowest.
Average room to my previous 20%ish.
Bright (sunny) to 100/255
SUPER sunny to 240/255.
I didn't notice any added drain today.
But this was my first test.
I think this feature was actually kanged from CM9, but I'm not certain.
So far I have resisted the temptation to get flash happy and I am on stock 4.0.2 but rooted. Do I have any options without changing ROM?
aidanbree said:
I have a similar problem. The max brightness is piercing and the min brightness is just a tiny bit too dim.
I have tried used root explorer to change the maximum brightness from 255 to 100 hoping that the slider may be more granular after. For some reason however I cannot update the max brightness file. I have ensured that it is r/w mounted and tried changing the permissions too. It says that the changes have been made and the original backed up. When I reopen the file it hasn't changed.
BTW, my 'brightness' file is at 10 when placed at the minimum brightness.
Click to expand...
Click to collapse
We cant change that brightness file with root explorer, even mounted, unless we mod the driver first. It will likely just revert right back to its previous value.
However it is possible i bet to edit the driver. Would be a cool project. You could also try to echo your desired value in terminal. ie echo 255 > brightness. But you prob will get the same result as using root explorer.
Maybe ill look at the driver with my limited skills heh. Or the alternative is to mod the framework which is def possible to fix this, and easier. We did exactly this on the atrix. And the sgs2 had it done too.
Edit: i think i found the code for your granular request. Check lines 30 or so.
https://github.com/ogdobber/android...0/include/linux/platform_data/panel-s6e8aa0.h
Still would be easier to do in framework instead.
I know this is possible in CM9's display settings, but I'm currently running AOKP. Is there any other way to lower the minimum screen brightness?
I've given Tasker root permissions, approved it as a device administrator, and approved it as an accessibility service. Still, when I use a task to lower the brightness to very low levels, the brightness will only hold for a fraction of a second before it ramps up to the factory minimum.
So is there some system component I can modify to allow lower brightness, or is this only available as a ROM control like in CM9?
byrong said:
So is there some system component I can modify to allow lower brightness, or is this only available as a ROM control like in CM9?
Click to expand...
Click to collapse
FWIW the lowest possible brightness setting can't be altered via the CM9 settings, only the auto brightness levels, both sensor input levels ("bins") and the brightness level associated with that input/bin. The minimum value of 19 for the lowest slot can't be lowered further. There are other display parameters (related to brightness) that can also be altered in the CM9 settings, but it won't accept a value less than 19.
Edit: I see from a link in your sig that you're familiar with the custom levels
Yes we can do it in the frameworks to go lower than 19. I did it on other phones. I'm not sure why it hasnt been done yet for nexus, and ive been too lazy myself.
But we can even take it down to zero or 4-5 etc so its much dimmer at night. Its on my to do list.
Also i posted some kernel code in a similar thread where this question was already asked. But mod the framework is much quicker.
RogerPodacter said:
Yes we can do it in the frameworks to go lower than 19. I did it on other phones. I'm not sure why it hasnt been done yet for nexus, and ive been too lazy myself.
But we can even take it down to zero or 4-5 etc so its much dimmer at night. Its on my to do list.
Also i posted some kernel code in a similar thread where this question was already asked. But mod the framework is much quicker.
Click to expand...
Click to collapse
I should have clarified more clearly that my post above was regarding doing it via the CM settings.
I'll mod mine...at some point...but like you, too lazy for something that won't blow me away.
You want this app, works great https://play.google.com/store/apps/...yZy5wcm9qZWN0dm9vZG9vLmRpc3BsYXlmaWx0ZXIiXQ..
Sent from my Galaxy Nexus GSM using Tapatalk expect possible typos
I'm an idiot; I just found it in AOKP. It's in the custom backlight settings.
My experience does not mirror you guys. When I decrease the "screen dim level" in the custom brightness settings, it applies globally. I just did it in AOKP the same way I used to in CM9 and now with Tasker I've taken the screen all the way down to 1
Is there any way to decrease the minimum brightness on stock?
aidanbree said:
Is there any way to decrease the minimum brightness on stock?
Click to expand...
Click to collapse
Yes with above linked app. I confirm it works on stock
Sent from my Galaxy Nexus using Tapatalk
I've used a similar app called Screen Filter. My only problem with these types of apps is that I find the black/gray filter they use greatly decreases contrast at low brightness levels (more so than a "true" brightness level at an equivalent setting). Still, if you are running a setup in which they are your only option, they certainly beat having nothing.
The problem with using a screen filter is that it limits the maximum brightness when in sunlight.
I only want to affect the minimum as it is too bright.
Has anyone been able to do this on a stock rom? I too think that the minimum brightness is too high, but I don't want to use the above linked program because it also affects the maximum brightness too. I would like to be able to set custom light levels as per cm9/cm10 and pretty much any custom ROM right now, albeit with my stock ROM. Any flashable zips out there?
Cheers,
Dan