Hi Everyone,
This is my first post. Please pardon me if I am starting this thread at a wrong place.
I was trying earlier to find a solution for brightness change problem in ubuntu touch OS, but by going through the forum i couldn't find any way without restarting the phone.
Restarting the phone to change brightness, really ?
It's not very practical by the way.
I just figured out that I can change the brightness of the screen in Ubuntu touch OS without having to restart it.
1) Start the adb root
2) echo "100" > /sys/devices/i2c-0/0-0040/leds/lcd-backlight/brightness
The value 100 mentioned above is just for example. The range of that value is from 0-255. 0 is completely screen off, while 255 is brightest.
Since, I have only tested this on my NEO V, just eager to know if it works for other devices as well.
People who have slightest of fear that they might be doing soemthing dangerous, should not try this on their phones.
Please let us know.
Eagerly waiting for your response
Note : Nobody takes the responsibility if you damage your phone by any means. It is always your resposbilty.
On yesterday's build, I could change it using the brightness bar in the battery menu of staus bar
Reboot is only fir make your change avaitable for the system
Sent from my Galaxy Nexus using xda app-developers app
Brightness option
Hi,
I verified for my NEO V. I don't have any brightness option.
I would assume that brightness is not available in the system bar other that nexus devices or officially released devices in ubuntu site.
Related
I have recently installed cyanogen on my desire and have found the mod to be an absolute joy to use. The one irritation however has been the automatic screen dimming. Every 6 or 7 seconds or so the screen dims itself. This can become very annoying when reading long messages or any other text. I have looked on lots of threads but have found no answer to my question. Surely there must be a simple solution to turn off this automatic dimming setting?
Thanks
HomeGrownHeroz said:
I have recently installed cyanogen on my desire and have found the mod to be an absolute joy to use. The one irritation however has been the automatic screen dimming. Every 6 or 7 seconds or so the screen dims itself. This can become very annoying when reading long messages or any other text. I have looked on lots of threads but have found no answer to my question. Surely there must be a simple solution to turn off this automatic dimming setting?
Thanks
Click to expand...
Click to collapse
I think....(not exactly sure) but that may be apart of the actual rom, if there is no setting under display then its probaly built in that way. Under settings/display you can change the screen time out if that help
reply
I've played around with all the settings myself and have so far been unsuccessful. Its not a problem really, just a bit annoying. I just find it hard to believe such an awesome mod doesn't have a simple off switch.
If anyone knows of a way to extend the screen dimming then that will help too.
I think what you're looking for is the Sleep setting. Go under Settings -> Display -> Sleep, and select a longer time interval if needed. Your current setting might be set to sleep after 15 seconds, causing the screen to dim at 6-7 seconds. Change it to maybe 1-2 minutes.
yes you can. Put the widget 'Power Control" on the home screen and you can do it easily from there. Thats how i do it.
Recently I installed cm 12 but I have a problem ie the screen backlight is always on when the screen is off........I need help.....
ananthur said:
Recently I installed cm 12 but I have a problem ie the screen backlight is always on when the screen is off........I need help.....
Click to expand...
Click to collapse
setting /display
or
setting /button/backlights
BatDroid said:
setting /display
or
setting /button/backlights
Click to expand...
Click to collapse
but the brightness adusting is also not working
Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.
Hi, I am new in XDA, but just want to share some trick on the new Xperia C5 Ultra on change of screen density to look more beautiful without root.
This is useful for those who like to have phablet screen look like table density.
I have done tested on my Xperia C5 Ultra and it work with any flaw.
Please be reminder I am just putting a guide here, I will not responsible for anything happen to your phone, damaged, brick or exploded.
Any how this is done without root and you can restore to original screen density if you don't like it.
Please follow below guide :
Before you start, please ensure you have a working adb tool install on your PC and you have driver install on your PC.
refer here if you don't http://forum.xda-developers.com/showthread.php?t=2588979
This can only be done thru the PC
Original the Xperia C5 Ultra density is 480. This guide will help to change to density 320
screen resolution remain on 1920x1080
Step by Step
1) pls enable the developer mode on your Xperia C5 Ultra
2) check the USB debugging on the developer option
3) plug in the USB and connect your phone to the PC
4) press on the PC " window" key + "X" key and select command prompt (admin)
5) in the command prompt , put in text adb after C:\windows\system32>
6) your phone share pop up message to authorize the usb debugging, select YES.
7) If step 5 & 6 don't come up any long message on the window command prompt, this mean you did not install properly the adb tool in your pc. (refer above to redo)
8) at this step , mean adb is done properly and go back to command prompt in the window
9) enter text "adb shell wm density 320" after the C:\windows\system32>. it look like this C:\windows\system32>adb shell wm density 320 and press enter key on PC
10) Now your phone have change to screen density 320. everything will look smaller now.
11) you need to re-start the Xperia C5 ultra phone and all screen size will completely change to new density 320.
12) you are done. now you can re-arrange your phone icon and have a fresh look !!
How to go back to original screen density
1) repeat the step 1 , 2, 3, 4 & 5.
2) key in C:\windows\system32>adb shell wm density 480 and press enter on pc
3) restart your phone then you will go back to original screen resolution
What works and what not work
work
- all phone function work as normal including screen capture and screen video
- so far I did not encounter any problem, tell me if you know any
- all one hand operation mode is working except the phone key dialer pad as below
not working
- the phone key dialer will not work in one hand mode. It will show error if you have set "one hand mode" on the telephone key dialer
screenshoot as below
Enjoy
Does the camera app scale properly?
No, camera resolution and function no changes. work as normal . Only icon size become smaller
kychan2015 said:
No, camera resolution and function no changes. work as normal . Only icon size become smaller
Click to expand...
Click to collapse
Did you figure out how to extend the battery life. Mine is 13 hours max?
Sorry of topics but you seems like Sony's McGuyver to me.
Whoa.. I cant thank you enough for this tip. Never knew changing of DPI is so easy without root. Everything looks so hi-res now. Seriously, everyone should do it. Sony should had done this be default.
Only glitch I see now is the sony home launcher's page indicator is a little misaligned.
I already tested and tried as your instruction. However I revert back to 480 as the phone feel warm and I afraid it will explode anytime.
I just noticed that the battery life is affected... or is it just me? also the phone is way too hot when I'm using it. hotter than when the DPI is 480
I not sure what wrong. Density and battery should be no connection. You phone is hot because many background processes is running. Try end task all not using app, I think it should be back to normal very fast.
Sent from my E5563 using XDA Free mobile app
kychan2015 said:
...Original the Xperia C5 Ultra density is 480. This guide will help to change to density 320 screen resolution remain on 1920x1080
Click to expand...
Click to collapse
I don't understand... is it supposed that: Higher ppi number gives Sharper screen !!?? But now you lower it to 320?
kychan2015 said:
I not sure what wrong. Density and battery should be no connection. You phone is hot because many background processes is running. Try end task all not using app, I think it should be back to normal very fast.
Sent from my E5563 using XDA Free mobile app
Click to expand...
Click to collapse
I reverted it back to the original and it's not as hot as it was. I think and sure it was affecting... come to think about it, if the icons are smaller, then it can accommodate more things on the screen thus making the gpu work more in terms of animation but I don't know if that's right. But it did affect my battery life when I changed it.
thejamesarnold said:
I reverted it back to the original and it's not as hot as it was. I think and sure it was affecting... come to think about it, if the icons are smaller, then it can accommodate more things on the screen thus making the gpu work more in terms of animation but I don't know if that's right. But it did affect my battery life when I changed it.
Click to expand...
Click to collapse
Technically yes it makes the gpu work a little harder to draw more things on the screen. But there shouldn't be any noticeable impact on the battery nor heat. Countless other devices changes their dpi but never or hardly were this reported. There should be other factors causing the issue for u.
Is there something between 480~320?
Sent from my E5533 using XDA Forums
So if we adjust it to make things smaller to look like a real 1080p, will it effect gaming performance? I mean fps drops?
apps problem...
i have a problem. i mean there is a problem. i set density to 320 and after that i tried to install minecraft pocket edition v13 b5 which i have taken it from original density(restore). it didnt install it. just gave an error.
Edit: i dont know why but game performances are increased.
is it not possible to do it using terminal on the phone itself?
I dont think so. It needs root i guess
alihacker4 said:
Is there something between 480~320?
Sent from my E5533 using XDA Forums
Click to expand...
Click to collapse
Looking for this as well... 480 is to big while 320 is quite small.. Any idea if we can set it somewhere between these values? Thanks in advance ..
May I request someone to post screenshots after increasing the screen density? Thank you very much in advanced.
You can pick any number you want. I use 360. Just change and try it out until you find a setting you like, you won't break anything.
different between 480ppi and 320ppi
320ppi is smaller, 480ppi is bigger
..
First thing first: thanks a lot for the /sys file to change ambient brightness! Gives me ideas of things to play with, ie the ambient brightness being different from the awake brightness is among the top of what I find the most baffling with Android Wear (to me, the point of ambient is to update less frequently, and to move the displayed face a little to avoid burn in: I don't need every last drop of battery; 16-20h is really enough; also, if it's not bright enough by day, it's also not dim enough by night...).
Otherwise, with Tasker and AutoWear, maybe using the screen off state, and setting ambient anew when you exit that state would work? Obviously, the system rewrites that file (it takes more than mere permissions to prevent root from doing what he wants) somewhere between when the screen goes off, and when it goes to ambient again after having been turned on, so with a little tinkering, and maybe some delays, it should hopefully be workable.
MuF123 said:
Hi there!,
I've been trying to set ambient back-light to maximum by echoing 255 to /sys/class/leds/lcd-backlight/brightness and then chmodding it to 444 for readonly, so noone will ever change it.
This kinda works, when I enter ambient mode it really is at 255 level. However trouble stars after entering theater mode - somehow this value gets changed. How can this be?
Any ideas how to debug this?
Click to expand...
Click to collapse
I wish I could answer your question better than this, but wearshell can query brightness values or file values through tasker by having it read your settings once every few minutes, or per minute, or whatever you like if course. if it found the value not what you want it'd fix that .. you could sideload a tasker apk that does the same, but this is inflexible and cumbersome compared to the wearshell option.
..
I have a mt6572 phone and I'm facing a problem related to brightness of my phone.
My screen brightness is always high and it burns my eyes at night.
I cant find any brightness option in my build.prop.
So I added this line to appropriate section of build.prop--
Code:
ro.lcd.min_brightness=blah(low as possible)
I rebooted my phone and nothing changed.
Still high brightness.
So,I tried this--
Code:
ro.init.screen_brightness=blah(as low as possible)
It didn't make any difference too.
I tried changing roms.
But every kk rom has the same issue(But ported from different phones).
It dont happen in LP roms.
I know about CF lumen,Darker and etc. screen controller app.I know those are great but I don't wanna use them.
I just want to get rid of it without using an app.
I will be glad if someone post a solution for me.
Regards
BatDroid
bump