Develop Bugs

LCD Density Changer?

Has anyone been able to get any density changer apps working on their Nitro HD? I've tried all of the following, and none seem to work. It's possible there is a problem with my su access, so if anyone HAS gotten any of these to work, please let me know. That at least tells me I definitely have an su problem...
DPI Changer
LCD Resolution
LCDDensity
Root Tools

Never mind; my build.prop file was set to read only.

Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?

[email protected] said:
Excuse my ignorance, but what exactly are they for? Does the density changes only the size of text or everything including graphic become bigger/smaller?
Click to expand...
Click to collapse
wondering the same thing as well.

aquariuz23 said:
wondering the same thing as well.
Click to expand...
Click to collapse
For the most part, yes. Decreasing the LCD Density is like increasing your desktop's resolution. Icons and text become smaller, though apps that are written to scale to any resolution will usually appear the same.

Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?

I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.

[email protected] said:
Hmmm...I do see some issues with current density, for instance the avatars in Talk don't stretch to fit the square.
So witch tool would you suggest?
Click to expand...
Click to collapse
Actually, I'm not sure any of the tools above would work; part of the problem I am sure is that the build.prop file was not only read only, but there wasn't an entry for the LCD Density - so if the apps work by simply retrieving and editing the property, they aren't going to work. I just edited the file directly with a text editor, saved, and restarted the phone. Some of the apps would then at least report the new value, but still didn't seem to successfully update it. I quit looking because I got the density I wanted (about 270, down from the native 320).
As for compatibility with other apps, if they don't quite look correct it is because they aren't written well, and a different density changing app isn't going to do you any good. Again, it's like changing the resolution on your computer - it doesn't matter how you change your resolution - once it's set it is what it is, and apps that don't accommodate it just aren't going to look good.
Namuna said:
I tried DPI Changer the other and couldn't get it to work, thanks for the heads-up about the build.prop!
The Nitro also already has the "Screen Optimization" util (Settings > Display > Screen Optimization) that resizes checked apps to the Nitro's display. It helped with a few games, but some games just won't work (like Asphalt 5)...But now with the Density changer, maybe I'll give it another try.
Click to expand...
Click to collapse
The Screen Optimization utility only seems to address apps that are written to a specific resolution - not pixel density. In this sense, the LCD Density is actually more like changing your computer's DPI - I didn't use that analogy first because more people are more familiar with changing a desktop's resolution. The fact is that LCD screens have a set resolution, and you cannot increase or decrease that resolution through software. The Nitro's extremely high resolution (1280x720) just isn't common enough in phones (most software would see it as a tablet) to be accounted for in all apps - particularly older ones. So, the screen optimization app that is built-in will automatically stretch apps to take up the entire 1280x720 pixels, even if the app only renders (for instance) 800x480 pixels .

[Q] ROM 4.10.12 ODJDub HD Express 2.0 - Widgets and icons small

I install this rom and is really good, the only bad things is: when i put a widget, this is too small, example, the tunein radio the buttons when i press play open the app and when i press stop is like a press play. i wanna put images to explain better but i don't now how. how i can make perfect this rom with out this issue?

realmotaro said:
I install this rom and is really good, the only bad things is: when i put a widget, this is too small, example, the tunein radio the buttons when i press play open the app and when i press stop is like a press play. i wanna put images to explain better but i don't now how. how i can make perfect this rom with out this issue?
Click to expand...
Click to collapse
the ROM may have the LCD density set too low, try downloading LCD density from the market and set it at 240 which is usually the default for most phones, including the evo... play with the density set it to different levels to see if any of them change the look of things..

evol4g said:
the ROM may have the LCD density set too low, try downloading LCD density from the market and set it at 240 which is usually the default for most phones, including the evo... play with the density set it to different levels to see if any of them change the look of things..
Click to expand...
Click to collapse
Don't do that. The LCD density is already set at 240. Any widgets you use from the market are gonna be too small. This rosie was modded to fit our phones. Normally the rosie for the tablet is 160 dpi, but that will screw up the dialer and make resizing impossible. This is a known issue for the Express and widgets. My old thread was closed due to stupid red tape, it was discussed in it, but that thread was reopened, so you can search it again for info and tips. Hopefully, when I get some time, I will ask for people to post what widgets they need resized and I can fix them for you.
Hope this was helpful.

[Q] build.prop editing?

I'm having issues editing the build.prop file. For example, changing lcd density from default 320 to 160 yielded no results. I re-open build.prop, and the changes I made are still there. Something seems to be overriding the changes...any ideas?
EDIT: I thought I was on the Q/A board, my bad. Please move B.Jay when you get a chance
EDIT 2: Figured it out, there are 2 "ro.sf.lcd_density=360" lines by default, and the top most was overriding the one under ADDITIONAL_BUILD_PROPERTIES.
Not a good idea to set density at 160, system UI and Samsung keyboard crashes endlessly.

LvDisturbed1 said:
EDIT: I thought I was on the Q/A board, my bad. Please move B.Jay when you get a chance
Click to expand...
Click to collapse
Done.

DPI changes

Hi all,
I have read all the threads about DPI-changes but couldn't find a definite answer. Currently i am on firmware 1.95.401.4, build.prop says
Code:
ro.sf.lcd_density=640
(see screenshot) using Dev-Check it says dpi is 571.
I played around with DPI values a little and found that changing to a value lower than 530 the button in the camera will slide to the left, or in the screenshot downwards (see second screenshot, DPI is 471).
There are some other threads about changing DPI values which say the htc lockscreen will 'break', i did not encounter this problem, besides the button in camera i had no problems.
Long story short, my questions,
why is there the difference between those two values, what am i getting wrong?
(build.prop vs Dev-Check)
anyone encounterd other problems beside camera button by changing DPI to a value lower than 530?
if you have changed the DPI, what is your current value?

Dev Check just calculates the correct DPI for your device. But HTC just set another (higher) DPI, because then more icons can be displayed.

Might not be much use but I believe Nougat / Android 7 supports different DPI scaling (much anticipated feature!)

I want to change my DPI to lower then 530, but the camera button problem bugs me, it still appears in the latest HTC camera 8.50.917991.
Is there a workaround or different camera apk for this issue? I am not rooted and on Nougat.
Thanks

Capacitive button brightness?

Is there a way to customize the capacitive button’s brightness?(maybe by editing XML or all file?) I found an app in play store that can set brightness to maximum but there's still some minor bug. Plus I'd prefer to modify the system file on my own than having an app running background the whole time.
Any help would be appreciated.

BrianKuo1853 said:
Is there a way to customize the capacitive button’s brightness?(maybe by editing XML or all file?) I found an app in play store that can set brightness to maximum but there's still some minor bug. Plus I'd prefer to modify the system file on my own than having an app running background the whole time.
Any help would be appreciated.
Click to expand...
Click to collapse
the brightness is controlled by the light sensor..the darker it is the lower the brighter the higher the brightness of the capactive buttonbrightness.
back on the m7 there was a seperate array in framework-res.apk that you could easily configure.
Now it's working a bit different. only way to modify is add some custom code in AutomaticBrightnessController (services.jar).
..or flash our rom, we have it configurable:

j to the 4n said:
the brightness is controlled by the light sensor..the darker it is the lower the brighter the higher the brightness of the capactive buttonbrightness.
back on the m7 there was a seperate array in framework-res.apk that you could easily configure.
Now it's working a bit different. only way to modify is add some custom code in AutomaticBrightnessController (services.jar).
..or flash our rom, we have it configurable:
Click to expand...
Click to collapse
ayyy
I worked around a little bit, found the file at /sys/class/led/button-backlight
Hope this helps anyway.

BrianKuo1853 said:
ayyy
I worked around a little bit, found the file at /sys/class/led/button-backlight
Hope this helps anyway.
Click to expand...
Click to collapse
Could have tell you that...but as said once the lightsensor value changes the file will change.
you could change it to your desired value..then chmod it to read only...but I doubt you will find a satisfying value that fits in the dark and bright