I have an Allwinner A20 tv box, I trying to use it on a device with an old, low res, 4:3, 5" screen. It works but I have a few problems - firstly the box has "pal" and ntsc" settings for use with AV out, but when connected the picture is squashed inwards so circles are represented as ovals. I ve tried to mod the aspect ratio/resolution but nothing works, the picture is always distorted.
On top of that everything is too small for the screen, it is readable but things really need to appear bigger, so I also played about with the dpi, this does make things bigger and a better match for the screen, even though the device doesnt actually have a screen itself.
I ve done both these mods with several apps and modding the build prop and I always get "sorry systemGUI has stopped", constantly - when you close it, it opens again straight away. Clearly settings doesnt like these mods, so I m trying to work what I need to change so it DOES accept them.
Can anyone tell me how I can successfully mod the setting.db and get this working at the correct aspect ratio and a dpi that is suitable for use on a low res screen ?
Thanks
Anyone ?
typos1 said:
Anyone ?
Click to expand...
Click to collapse
Did you ever figure it out?
And if so how as I have a Vega S89 Elite (Clone) and it has the same text-is-too-small-on-a-sd-tv problem, thanks.
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.
Hello all,
I have an Intermec CN51 running Android 4.2.2 that had its digitizer replaced because the touch screen wasn't functioning correctly.
After replacing it, it appeared it's not the digitizer but the OS that's the problem, it wouldn't respond to touches lower than just above the buttons in the bottom, which was also the initial problem.
After having tried factory reset, OS updates and some calibration tools from the app store all of which didn't work, I managed to find a way to sort of fix it. By rooting the device and editing this file: /sys/touch_calib/x_y_min_max
Its original content were these values:
Code:
433,216 3636,3823
And I found by changing it to 433,416 3636,3823 it now responds in the area it didn't before. I noticed that the values affect the calibration in this order from left to right: left, down, right, top.
However, it still has minor deviations and I guess it's because the values are simply not correct. Now my question is, what exactly are these values and what should they be at?
I know they basically determine the area in which touches are allowed, the display has a resolution of 480x800 but I can't figure out the relation between that and the values.
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
Hello,
I'm currently working on a Visible Light Communication project and need some help to programm a fast blinking (>200Hz) LED Flashlight. My device is a HUAWEI CUN-L21 with firmware B115.
I already programmed an app using Android SDK that turns the Flashlight on and off with a specific delay using Thread.sleep(delay). The problem is, that even if I set the delay to just a few milliseconds, the max. frequency I get is around 35Hz which is too low. So I read an article that says that the low frequency is not because of the characteristics of the LED but because of its Android architecture. To raise the flicker frequency I have to combine the switch function of the Linux kernel with an interrupt function and package it as a Linux driver. Therefore I downloaded the Linux kernel for my device (kernel 3.10) from the HUAWEI website and looked into the led drivers. There are so many and I don't know where I should programm the functions. I looked into the heartbeat trigger and it seems to be a little bit like the funktion I need.
So here is my question: Can anybody help me to modify a led driver so that the Camera LED flashlight will blink in different frequencies higher than 200Hz? Where to I have to start?
PS: I tried to root the device but it failed because I couldn't enter the recovery mode after flashing a TWRP that doesn't work form this post: https://forum.xda-developers.com/android/help/root-huawei-y5-ii-cun-l21-l03-t3536329
Many people seem to have the same problem while rooting the HUAWEI CUN-L21.
Thanks and if I forgot any usefull information, please tell me.
No response?
Is there no one that can help?