Just wanted to leave it here, incase it would be useful for someone.
So, i have this cheap y88x Dragon Touch 1024*600 tablet for my kids and it was working fine when the other day it was dropped and the LCD was broken (touch was working). I tried everywhere but couldn't find the compatible LCD (no model number etc, one was found but that was like £22) but after few weeks i got the one on aliexpress which looks compatible.
Long story short, that screen turned out to be 800*480, which messed the keyboard, touch and everything else.
I was sent the latest firmware Y88X-XZ-V5-AL-TZX-20150326 (dragontouch support is good and fast) which was easy to open in Dragonface-2.1.2.
There i changed the sys_config file, changed the lcd_x to 800 and lcd_y to 480, left the touch screen to 1024x600
also, in build.prop added following lines
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,ad
b
Saved the image and using PheonixUsbPro, applied the img. Right away the systemui started to crash but i was able to access adb (run kingo tool if adb not connecting, you dont have to root as its aleady rooted).
change the dpi to 120 using following command
Code:
adb shell am density 120
And thats it. Everything came back to normal, the touch was picking up correct points, the UI looks ok, kids can play minecraft etc etc!
Related
Note: This is NOT the regular hidden (crappy) camera app
1. Get Rooted
2. Remove (temporarily) your password (i made the mistake of not doing this..grrr)
3. Grab ROM Toolbox (lite will work)
4. Open ROM Toolbox (yes... allow Superuser)
5. Slide/tab over to performance and select build.props Tweaks
6. Slide your LCD Density down to 200. VM Heap stays same (mine is 256m)
7. Hit apply at the bottom...and reboot.
8. When it comes up at lockscreen...slide finger left and away from lock...
9. Magically, there is now a Camera icon.
10. This camera has options...video, upload to youtube, etc...
* I have paid the 15$ to remove ads...so maybe if yours does not have the same result.
So, what gives here? Is this the picture/video app that runs on the upperclass large Kindle Fire HDs?
Did I just miss this in the update?
I read all these articles about camera...and then this is here the whole time.
When you return to stock LCD Density it goes away. WTF?
I hope someone finds this useful.
Reference step # 2 - If you are wondering, the reason that I even found this, was cause I was playing with ROM Toolbox...and I changed my LCD Density the WRONG way to 300 (DONT DO THIS). Then I could not even login with my normal password, cause all of the keys were not visible. So I had to sys restore...all lame.
cyates98 said:
Note: This is NOT the regular hidden (crappy) camera app
1. Get Rooted
2. Remove (temporarily) your password (i made the mistake of not doing this..grrr)
3. Grab ROM Toolbox (lite will work)
4. Open ROM Toolbox (yes... allow Superuser)
5. Slide/tab over to performance and select build.props Tweaks
6. Slide your LCD Density down to 200. VM Heap stays same (mine is 256m)
7. Hit apply at the bottom...and reboot.
8. When it comes up at lockscreen...slide finger left and away from lock...
9. Magically, there is now a Camera icon.
10. This camera has options...video, upload to youtube, etc...
* I have paid the 15$ to remove ads...so maybe if yours does not have the same result.
So, what gives here? Is this the picture/video app that runs on the upperclass large Kindle Fire HDs?
Did I just miss this in the update?
I read all these articles about camera...and then this is here the whole time.
When you return to stock LCD Density it goes away. WTF?
I hope someone finds this useful.
Reference step # 2 - If you are wondering, the reason that I even found this, was cause I was playing with ROM Toolbox...and I changed my LCD Density the WRONG way to 300 (DONT DO THIS). Then I could not even login with my normal password, cause all of the keys were not visible. So I had to sys restore...all lame.
Click to expand...
Click to collapse
What? I smell fake build prop
Sent from my KFTT
uhhhh no
dank101 said:
What? I smell fake build prop
Sent from my KFTT
Click to expand...
Click to collapse
Thin has nothing to do with any build...all that it does is change the display. Font to pixel ratio or some crap. I just find it flippin interesting that it actually displays a diff unlock screen. Then, when set back, it reverts.
Why doesn't my stock unlock screen have a camera Icon?
Very nice Lockscreen now. Do you know what kind of entries we can change in the prop tweaks?
But when i change the LCD Value, the Auto Brightness Buttons in the Notificationbar are unvisble and the Brightness are very high.
Sent from my Kindle Fire HD, rooted, Whatsapp, GoLauncher|HD and Play Store
Camera in lock screen
matzew said:
Very nice Lockscreen now. Do you know what kind of entries we can change in the prop tweaks?
But when i change the LCD Value, the Auto Brightness Buttons in the Notificationbar are unvisble and the Brightness are very high.
Sent from my Kindle Fire HD, rooted, Whatsapp, GoLauncher|HD and Play Store
Click to expand...
Click to collapse
What a surprise and how odd to see the camera in the lock screen (I didn't know existed). I too am rooted and using the Go Launcher EX HD and have been using the ICS camera from market.:laugh:
I liked this but it ended up messing up my keyboard, so I went back to normal screen density.
I changed the Value to the standard too because the Autobrightness wont working
Sent from my Kindle Fire HD, rooted, Whatsapp, GoLauncher|HD and Play Store
I'm keeping dpi @210 - it provides more benefits then problems - now all apps behaves as a tablet version in contrast to phablet @240. I'm not using the native keyboard anyway so I don't mind if it messed up after the dpi change. The only problem - black lock screen, but it's more funny with a camera icon on it.
Can people with an hdmi cable please go in to terminal emulator and execute the following command?
am display-size 1920x1080
Let me know how it looks...on my TV it is all zoomed in, doesn't look right, if your TV has a PC setting, use that.. I want to see if it is just my TV or not
To go back to how it was enter
am display-size reset
This is a possible(though not ideal) workaround when using hdmi
Would like to have people test it with different TVs/monitors
If you have a screen that supports it, you can use this command for 1440p
am display-size 2560x1440
the_boo said:
Can people with an hdmi cable please go in to terminal emulator and execute the following command?
am display-size 1920x1080
Let me know how it looks...on my TV it is all zoomed in, doesn't look right, if your TV has a PC setting, use that.. I want to see if it is just my TV or not
To go back to how it was enter
am display-size reset
This is a possible(though not ideal) workaround when using hdmi
Would like to have people test it with different TVs/monitors
If you have a screen that supports it, you can use this command for 1440p
am display-size 2560x1440
Click to expand...
Click to collapse
for my dell 30 inch it zoomed it also
2560x1440 full screen stretched it. looks good nothing looks cutoff and the whole screen is being used.
Just watched a video and did a side by side comparison with my other monitor and nothing looked cutoff using mxplayer
1900x1080 zoomed in
2560x1600 did not do anything.
Although what I did notice was there is an extra space below my launcher in tablet mode but it doesn't show on the monitor only on the N10 itself but I use expanded mode also so its not that much of a problem imo
shadowblade330 said:
for my dell 30 inch it zoomed it also
2560x1440 full screen stretched it. looks good nothing looks cutoff and the whole screen is being used.
Just watched a video and did a side by side comparison with my other monitor and nothing looked cutoff using mxplayer
1900x1080 zoomed in
2560x1600 did not do anything.
Although what I did notice was there is an extra space below my launcher in tablet mode but it doesn't show on the monitor only on the N10 itself but I use expanded mode also so its not that much of a problem imo
Click to expand...
Click to collapse
Yeah, when you are done you can run the reset command to make it normal again...
There is some cutoff on my phillips 42" lcd, it must be dependent on how the screen handles it...
No one else else? Man I figured there would be a few more people...
the_boo said:
No one else else? Man I figured there would be a few more people...
Click to expand...
Click to collapse
My tablet went onto the charger when I got home from work, otherwise I would try it.
I'll be trying this when I get home in a couple hours.
Sent from my GT-N7105 using Tapatalk 2
Awesome, looking forward to what you find!
I am also curious as to what people will be seeing.
My first impression is that it might actually be working...
Sent from my GT-N7105 using Tapatalk 2
Sheolrock said:
My first impression is that it might actually be working...
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Awesome... Must be my TV then... I'll try it on a buddy's tv in awhile... I'd try it on my monitor but it only has dvi...
the_boo said:
Can people with an hdmi cable please go in to terminal emulator and execute the following command?
Click to expand...
Click to collapse
Thanks this is great.
I just tried it:
Nexus 10: rooted Stock 4.2.2
HDTV: Samsung PN58C8000
HDTV screen size set to: 16x9
Player: MX Player Pro
Observations:
> First attached the HDMI cable before running the display-size command. I could not for some reason get the N10 terminal to accept the enter command. The enter button lit up on both the N10 and HDTV screens but the enter did not happen. Not sure what may be going on there.
> Second attempt with the HDMI cable disconnected I executed the "am display-size 1920x1080" command and the N10 screen adjusted to the new dimensions. Mainly every thing looked like it was zoomed in. Then I attached the HDMI cable and it seemed to fit perfectly without any overscan that I notice.
> Using MX Player I started video playback and it played full screen on the HDTV.
This looks like a great solution. I did have some problems but I use a combination of products so that I never have to see the notification and status bars one being "full!screen". The display change seemed to mess up full!screen's functionality. So in the end I had to reboot before issuing the "am display-size reset" command but I think that is a problem specific to my setup.
The reboot did NOT reset the display back to normal, I had to issue the reset in a terminal and then all was well. This is not an problem just an observation.
I also use both "SideBar" and the PIE feature of "LMT" and they worked with the changed resolution.
I am going to play around with this more but I think it would be very convenient to use SManager and its desktop script widgets to perform the display set and reset. The SManager Pro version can "Execute scripts from widgets without opening console". I already own SManager Pro.
If you really wanted to get fancy you may be able to have a script that accepts a video file path and or video stream URL, sets the display, starts MX Player passing the file path/url and then when MX Player ends resets the display. This idea needs more thinking and development before the fancy script would be useful.
Here is how to start an app in a script and here is the MX Player API details. I have not tried this yet but was going to for a completely different application.
I have some playing around to do, but this is important information.
Thanks again.
Doug
Sweet... Thanks for all the info... If anyone wants to try setting a script... Be my guest but it won't be me lol
I can adjust my display size while plugged in but I do get over scan... Mabey I'll try setting the size, then plugging in
could this be something that can be tied to Tasker? I don't have Tasker to find out (nor a microHDMI to HDMI cable!) so I don't know, but what about a tasker trigger for detection of the HDMI cable to send the "am display-size 1920x1080" command and then when the HDMI is removed send "am display-size reset"
Perhaps given 3DSammy response this might not be possible if the command has to be sent before connection to the TV...
I wrote the toggle script I was suggesting "HDMI Fullscreen Toggle Script".
Might have to try this out on stock rom and see how it goes... I'm guessing it's my TV but Mabey it's the rom... I get over scan on my phillips 42" lcd
Works for me. Thanks
Been trying just now, it does work with MX player on our lg plasma, however when set to 1080 n10 screen loses its nav bar so I can't exit MX player or navigate around, forced to reboot. but proof of concept nevertheless.
Sent from my Nexus 7
bkmaracas said:
Been trying just now, it does work with MX player on our lg plasma, however when set to 1080 n10 screen loses its nav bar so I can't exit MX player or navigate around, forced to reboot. but proof of concept nevertheless.
Sent from my Nexus 7
Click to expand...
Click to collapse
You lose your nav bar? That's weird... I don't lose mine... You can use LMT launcher or gmd gesture controls though...
Indeed, n10 is pure stock. Reboot resets everything so for a film watch session its ok. Am sure this knowledge will spread and media players like mxplayer can include that trick in future.
What would be nice now is to smooth out the little jitters I get when playing back a blue ray via HDMI now we can go full full screen.. Preferably non root as the old fella would get more confused.. Its almost perfect so being close is bit irritating
Sent from my Nexus 7
bkmaracas said:
Indeed, n10 is pure stock. Reboot resets everything so for a film watch session its ok. Am sure this knowledge will spread and media players like mxplayer can include that trick in future.
What would be nice now is to smooth out the little jitters I get when playing back a blue ray via HDMI now we can go full full screen.. Preferably non root as the old fella would get more confused.. Its almost perfect so being close is bit irritating
Sent from my Nexus 7
Click to expand...
Click to collapse
Huh... According to 3DSammy it doesn't reset with a reboot... That's weird as well...
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.
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
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.