Hi Igot 3 diffrents tablets, and in the first one I have a 2 dead black pixels one next to the other like a little very little black spot. I tried all soft where but nothing work, is there anythinhg I can do?? And in my second tablet is something like the resulotion of the screen is not sharp, like is 800 on 600 or something and not 1280 on 720, is there anyway to fix it??? The 3rd ta let has no issues at all thank u
Nothing you can probably do about the first one. Black pixels = dead pixels. Software can only affect stuck or "lazy" pixels, and even then it won't necessarily fix anything. On the second one, go to Settings>Accessibility and make sure that the option "Large text" is unchecked. Or go to Settings>Display and set the "Font size" to Normal (these two options affect the same setting, that is, choosing "Huge" as the font size will turn on the "Large text").
On the second thought, you might have to change your DPI settings. (You will need root) Download and open ES File Explorer, open "Tools" and turn on the "Root Explorer", then go to /system and open build.prop with ES Note Editor. Find a line "ro.sf.lcd_density=XXX". Set it to 160 if there's any other value in place of XXX. Make sure the changes are saved and reboot your tablet. It should be back to normal afterwards
re
Duchman said:
Nothing you can probably do about the first one. Black pixels = dead pixels. Software can only affect stuck or "lazy" pixels, and even then it won't necessarily fix anything. On the second one, go to Settings>Accessibility and make sure that the option "Large text" is unchecked. Or go to Settings>Display and set the "Font size" to Normal (these two options affect the same setting, that is, choosing "Huge" as the font size will turn on the "Large text".
On the second thought, you might have to change your DPI settings. (You will need root) Download and open ES File Explorer, open "Tools" and turn on the "Root Explorer", then go to /system and open build.prop with ES Note Editor. Find a line "ro.sf.lcd_density=XXX". Set it to 160 if there's any other value in place of XXX. Make sure the changes are saved and reboot your tablet. It should be back to normal afterwards
Click to expand...
Click to collapse
thanks- its already in 160... there anything else i can do//??
bennnnnn said:
thanks- its already in 160... there anything else i can do//??
Click to expand...
Click to collapse
Could you post a screenshot? Is it running the same ROM as the other two tablets?
Yes katkiss 4.4 30 stable
bennnnnn said:
Yes katkiss 4.4 30 stable
Click to expand...
Click to collapse
So uhm, what about screenshot?
Related
I want to know how to change the Lcd Density from 160 to 140. Im using Zpad clean rom. I Went to System/Build.prop and I didnt see the Ro.density text or what ever it is. LCD Density for root works but it resets after restart. Anyone know how?
Figured it out. In system/Build.prop using Root Explorer I just made my own line and put ro.sf.lcd_density=140 and then saved and rebooted the tablet. Seems to have worked. If somone decides to change density like this dont forget to make a backup just in case.
EDIT: EHHH. Slide down bar was buggy and pissed me off and some apps wher windowed a bit so i gave in and just bought LCD Density changer from Market for a buck and use that. Works great.
HorsexD said:
Figured it out. In system/Build.prop using Root Explorer I just made my own line and put ro.sf.lcd_density=140 and then saved and rebooted the tablet. Seems to have worked. If somone decides to change density like this dont forget to make a backup just in case.
EDIT: EHHH. Slide down bar was buggy and pissed me off and some apps wher windowed a bit so i gave in and just bought LCD Density changer from Market for a buck and use that. Works great.
Click to expand...
Click to collapse
works well for me by changing the system/build.prop to 140.
Changed to 140 also and it makes some apps not fill screen but not a big hitter actually see more on screen with browsers and other apps. Especially with apps like settings and ROM Manager, etc....
Also went down and trying currently at 130. Here are screen shots of what it is like at default and 130. I kind of like seeing more of the screen.
Here are the setting I used in the build.prop file
ro.sf.lcd_density=130
Running Vegan 5.1 here are screenshots before and after
Screenshots below default and 130 settings:
Yeh lcd density app same as just changing it in build.prop. Slide down bar not full screen anymore when set too 140 on zpad clean rom. Wonder why.. Hmmm... worked b4 so now no point in the app except faster changes. Oh well.
Have you checked Spare Parts app to see if you have "Compatibility Mode" checked or unchecked?
I believe Unchecked should open things back to full screen.
I unchecked compatibility it at 130 and 140. No effect to Android notifications.
Hi,
i´m a little confused. I tried to change the dpi settings on my new mediapad t5 under system -> developer options -> smallest width to 800 (and i tried 700,that was changed to 702) but when i reboot it is resetted to 566.
I also tried to chage it with the tool "minimal_adb_fastboot_1.4.3_portable" and used the command adb shell wm density 800 && adb reboot the device does a reboot but the value is not changed. i dont want to root the device right now. how can i change the dpi without rooting, what did i wrong?
That's "normal" I can't keep it when I reboot too.
for my end I'm ok rooting but I didn't found a way to make it stay after a reboot.
I'm really waiting for custom rom... Really good tablet but not-so-good EMUI8...
is it possible to have a start script that will set the dpi to 700 on every boot? does someone know how to implement a startscript without root?
Also trying to achieve this now. But get the same problem.
It's set to normall again after rebooting.
From the other side, USB debugging is also not holding it's settings. So don't know if it's related to each other somehow.
I also noticed that the left side icons in the settings menu dissapear when changing dpi setting above 640?
So far rebooting is the only way to get them back (resetting dpi) for me.
Annyone found a sollution already for this? Or can someone confirm rooting will help (keeping the stock ROM)?
I am also looking for solution but no clue !
The only solution is Polished Custom Rom and it's not available yet!
I am using this tab for Netflix and Prime only. So, right now I am happy with EMUI 8.
Sent from my ELE-AL00 using Tapatalk
Hey guys, this has already been asked in this forum somewhere.. I've changed my dpi to a usable setting although I'm not sure what it's actually set to!
Use Quickshortcutmaker, grab it from play store. You can create a home screen icon to open vision settings. Open the settings and set everything to small.
I've done this and it persists through a reboot. I can't tell you if it's 700 but it's way better than the insane huge stock settings
Some apps don't show enough screen to access all the interaction buttons. You can't scroll to get to those buttons. This happens with several Topo Map apps.
They are not compatible with the HU screen resolution (DPI setting). You could change the DPI on the HU but that will mess up the display for everything else.
nic2k said:
They are not compatible with the HU screen resolution (DPI setting). You could change the DPI on the HU but that will mess up the display for everything else.
Click to expand...
Click to collapse
Thanks, Nick. I will try anything. How do I change the DPI on the HU, please?
Should be under display in the Android settings menu.
nic2k said:
Should be under display in the Android settings menu.
Click to expand...
Click to collapse
Ya you'de think. All I see is font size.
sonof40 said:
Ya you'de think. All I see is font size.
Click to expand...
Click to collapse
If you're rooted, you can use easy dpi changer app from the play store to set a custom dpi. That's what I do
So you don't see anything to do with display density? This is annoying maybe they found a way to keep people from messing up their display or it could be under the factory settings.
I tried factory settings months ago. No luck.
I would try rooting but I'm afraid of bricking as I'm not very tech.
Is there a foolproof way to do it?
Hi,
I just bought a joying UIS7862, 6GB+128GB,10.1" 1920x1200 head unit. I am not sure what type this unit is, is it a TS10?
The problem is that in third party applications everything is very small, small fonts, small details. This applies to apps like tidal, google maps, chrome etc. It is basically impossible to use these apps comfortably.
There is no "font size" or "display size" option in the device settings.
I solved the problem by changing the "smallest width" setting in the developer options from 1200 to 700. The apps look good now. the built-in apps also look good, except for the EQ app and the built-in launcher.
The launcher is not displayed at all, however, this problem can be easily solved by installing another launcher such as car web guru, which works great.
The real problem is with the EQ application which does not scale well. Some controls are out of screen, others are displayed incorrectly.
Is there an alternative application that supports dsp functions (dsp version of this device is dsp55) and will be displayed correctly?
Maybe someone has another way to solve the problem I described.
Marek.
I've done the same change on my 11.6 version. Did you do a full system reboot after changing the dpi setting? I had the same issue until I did a full reboot, then the system apps changed to the appropriate dpi scaling. You may want to change the dpi in small increments as well until everything looks correct.
WestonWW said:
I've done the same change on my 11.6 version. Did you do a full system reboot after changing the dpi setting? I had the same issue until I did a full reboot, then the system apps changed to the appropriate dpi scaling. You may want to change the dpi in small increments as well until everything looks correct.
Click to expand...
Click to collapse
What do you mean by 'full reboot"? All other system aps scale well, only eq app doesn't.
Just the Reboot from the top drop down menu. I guess I had not noticed if the EQ app was significantly larger in scale after the dpi change.
You missed the FYT forum listing your device....
Yet another.
Requested mod moves to FYT.
marchnz said:
You missed the FYT forum listing your device....
Click to expand...
Click to collapse
Sorry, I was not aware that my device is FYT. I am new to this...
WestonWW said:
Just the Reboot from the top drop down menu. I guess I had not noticed if the EQ app was significantly larger in scale after the dpi change.
Click to expand...
Click to collapse
I think I did it before, but to be sure I did a reboot today few times. It didn't help.
This happened on my 10 inch joying (airmont sc9853i). I hated it so much. Here's what I did. Should work for you.
Enable ADB by.... (or using Termux app)
- going to settings > system > developer options > 3368 > confirm
- at the top of the screen on right, tap three dots overflow menu icon > USB computer connection > pick the 2nd one (usually the one not selected on restarts)
- under where it says developer option, inline where it says "On", make sure that toggle switch is "ON"
- scroll down to, USB debugging, enable
Find the OTG port on the back of your unit. plug in a laptop with adb installed properly so you can 'adb shell'
From that shell, type enter the command 'wm' to being up its help.
what you are looking for is the correct "wm overscan [LEFT,TOP,RIGHT,BOTTOM]"
"wm overscan 10,0,0,0" worked great for me
dont worry about any white bars, they will go away after the screen redraws (switch apps or something)
I never adjusted any fonts or dpi in the system
hths
Thank you. And what about smallest width setting? Should it go back to 1200 as it was originally?
yegolebi said:
Thank you. And what about smallest width setting? Should it go back to 1200 as it was originally?
Click to expand...
Click to collapse
Yea. See if it makes any weird apps better. If not, leave it.
It turned out that the overscan setting didn't solve my problem, however Your answer pointed me in right direction. Thank you.
What was that right direction, post what you learnt so others may prosper
I mean that I started to experiment with adb and wm command, which I was not aware of before. Then I had the idea that I will use tasker to change DPI each time the eq app started and change it back on the exit. But this didn't work. Tasker can not change DPI in my case. I get error 1 message. So when I want to use this app I manually change DPI. The truth is I don't mess much with those settings once I've sett it to my liking....
WestonWW said:
I've done the same change on my 11.6 version. Did you do a full system reboot after changing the dpi setting? I had the same issue until I did a full reboot, then the system apps changed to the appropriate dpi scaling. You may want to change the dpi in small increments as well until everything looks correct.
Click to expand...
Click to collapse
Hi may I know what do you changed to ? I
I believe I set it to 720p (1280x720), common resolutions seem to work the best. I've since exchanged this unit for the new 11.6 slim so I can't say for sure.
I always found stock pixel color saturation to be a bit washed out. I prefer the look of more saturated color palette. Even choosing "adaptive" color on display options is still not good enough for me.
If you're rooted and want to increase color saturation do the following:
Open any Android terminal with root capabilities, I personally use Termux.
Type "su" and hit enter to grant root privileges. I don't know if it's a necessary step, but I change the directory to the root of the phone by typing "CD /". Then I copy and paste the below code into the terminal. I personally set my "x.x" to 1.25. hit enter and it will automatically take effect. You can change the values at anytime afterwards to go higher or lower. Values will go back to stock after a reboot using this method, so if you don't like it, just reboot to go back to stock values.
"service call SurfaceFlinger 1022 f X.X" (x.x sets saturation up to 2.0)
I HAVE NOT TESTED THIS, but in the past I have used this code to permanently set the saturation level on boot:
Setprop persist.sys.sf.color_saturation X.X
using this, the saturation level will remain to the chosen value on boot. Again, I have not tested this on the pixel 7 Pro.
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
works - thank you!
Ghisy said:
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
Click to expand...
Click to collapse
I'm sure it could but that's beyond my capabilities lol l
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Attinderkahlon said:
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Click to expand...
Click to collapse
I believe 1.0 is the stock value. So you can either enter the line again and replace whatever previous value you used with 1.0, or you could just reboot the device and it'll go back to the stock saturation settings.
jaseman said:
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
Click to expand...
Click to collapse
It could have a negative effect on battery life....but I would guess its minimal. Been using a custom saturation value for 2 days now, no known issues.
I haven't checked yet but going by previous devices, there is probably a way to access other color modes using tasker. "boosted" has been taken away from the menu, my guess is its still there and can be accessed with tasker. I'll check it if i keep the phone.
Thank you for this, legit the only thing driving me crazy was the dull colors now it looks more like I wanted. You da man.
Glad I could help!
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Curiousn00b said:
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Click to expand...
Click to collapse
I've been using this mod since the OnePlus 6T....so it's been a thing for a while at least for me.
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Unable to set up after boot, i get the setprop inaccessible
System is read-only for now. There's no rw mount mod so can't really edit build prop to set it on boot. We'll just have to wait for twrp or any system rw mount mod
xgerryx said:
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Click to expand...
Click to collapse
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Pain-N-Panic said:
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Click to expand...
Click to collapse
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
xgerryx said:
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
Click to expand...
Click to collapse
Glad ya got it working! Yeah I'm sure it's possible, having to run the script everytime you boot is kind of annoying
I wish we could adjust the white balance. This screen is so yellow looking