I was messing around with the LCD density of my phone and I set it to the lowest and now I am unable to unlock my phone. The screen cuts off the bottom and I am unable to access 0 and OK to unlock. Is there any alternate way to change LCD density? I can't edit the build.prop since I can't unlock the phone and enable a usb connection to my computer. halp?
Is there any way I can get the build.prop using adb or soemthing?
Related
Im making a tablet rom for the ray and i have faced one problem, if i lower the screen density in the build.prop to 160(like a tablet) when i call someone or get a call the phone says the process com.android.phone has stopped.
i thought maybe i can change the phone.apk to a tablets one and then which one?
Thank you for the help.
Why not use screen density 240?
When you lower the pixel density more things fit in screen with the modding i did to the framework-res in 240 not everything fits the screen for example the lock screen.
The Ray has a small screen, why do you want to make it smaller?
I doubt that what you are doing has any practical usage.
Hello all,
this is my first post here so be gentle :cyclops:
I've bought Rikomagic MK802II with Android 4.0.4. with HDMI.
I want to rotate screen to portrait mode. I spent days trying to make it work but without success.
Device came without "Auto-rotation" option in settings. It is somehow locked to landscape rotation.
I tried to do:
1) Unpacked original IMG file, then unpacked system and changed build.prop.
- I've added "ro.sf.hwrotation=90" to build.prop file and flashed the device.
- after rebooting system stuck at loading screen
2) Again fresh start from original IMG file.
- changed "config_AllowAllRotation" from "false" to "true" in framework-res.apk
- packed all and flashed the device
- after reboot system running OK but still in landscape
3) Made file local.prop in /data/.
- In it I've added:
launcher.force_enable_rotation=true
qemu.sf.lcd_density=160
- nothing helped...
4) Changed settings.db.
- changed user_rotation from 3 to 0 (to 1 also)
- after rebooting screen is still in landscape but settings.db doesn't have anymore this row: user_rotation and 20 next rows too.
I also spot some AutoRotationController.smali file but I don't know is everything about it or?
How I testing portrait mode:
- Tried with Rotation locker application
- made my app which have orientation to portrait (tested it on my tablet and on my smartphone and in emulator and in all cases app is in portrait except on MK802II).
Does anyone know what is needed to be changed to get portrait rotation? No matter locked portrait rotation or Auto rotation enable. Just possibility to rotate screen to portrait.
Are there some parameters needed to be changed or some features to be added or something else?
Are there some group of parameters considering to screen rotate?
Any luck with the rotation? Same story on the mk802 fw.
Cheers,
Martijn
Still no luck. I didn't gave up but I need to learn more about android to better understand the problem about rotation and to to prevent/allow screen rotation. That is hard way for me but only because I didn't get any help on the forums and cannot find any blog on the net who have this there written down.
I'm guessing all your previous attempts to configure or manipulate the devices screen orientation are unsuccessful probably because all these system settings, configurations and used apps rely on a hardware feedback of sum sort.
Which probably is absent on these devices.
I don't believe an android stick as this comes with a gyroscopic sensor (hardware). Thus not able to supply or react to the correct information.
I don't think its impossible though, it just needs a more low-level programatically approach.
Good luck :good:
And please share your solution if you get it solved. I can imagine more people are facing this problem.
Semi - Solution
Hello,
I have been working with one of these devices recently and also needed to display something in Portrait mode.. Alas it's locked in to landscape.
Instead, I figured out a work around. I built an application that is landscape, but the internal objects are rotated 90 degrees. The app I am working on (and hope to have in the app store soon) is a web browser kiosk style app. This application design would allow you to display something in portrait mode even if the devices is locked to landscape. Added bonus, with the way I have it set up I am able to also set it to 180 degrees or 270 degrees (this is useful if the picture needs to be flipped on a projector lets say)
Just thought I'd share what I figured out so far. I'll post the link once I have the app ready for prime time.
Hi - Easy DPI Changer app... Good rating in Android store, very few reports of it bricking phones, but I have a very important, but basic question:
Is it possible to set the resolution DPI too high or too low, making the phone unusable?
For example, if I set the DPI to 1 might the phone become impossible to use because the buttons appear off the screen?
Supposing I set it to 1000? Might the phone crash and boot loop before being able to set it back to a safe DPI?
I'm not looking to set crazy DPIs and brick my phone, but I just don't know what sensible DPIs are!
Any thoughts appreciated, Ta!
Hi guys,
The default for the Asus 3 Zoom is resolute 1080x1920, density 480. I found that you can change the resolution to 900X1600 at 408 density no problem. This would further save your battery. At the ADB:
adb shell density 408
adb shell size 900x1600
To reset:
adb shell wm size reset
adb shell wm density reset
Afterwards DO NOT adjust the the "Display Size" under "Display" in settings on your phone. If you change that you will get a repeated error to the Asus Launcher and it wont be able to reload until you go back into ADB and type "adb shell density 408" again. Since that requires a PC it will be annoying.
NVM. In 900x1600, the bottom part of the touch screen becomes very insensitive. I guess it is best to just keep everything at default.
In fact I find myself typing better at 540 density.
NVM on the 540 density. The camera app will crush when you enter portrait mode. Leave the screen size and density at default until/unless Asus fix their camera app.
I used Easy DPI Changer App. so far no issues...
FYI, even if you lower the resolution, all it does is stressing the gpu less. In real world usage, the difference is minimal since most of the battery consumption is via screen on time, and all the pixels will light up even with lowered resolution.
This has been proven time and time again that it helps your gpu sensitive apps, such as games, perform better. Battery life savings will be negligible.
Besides, why are we worring about battery life with this phone anyways?
I changed the digitizer and display in my phone. The digitizer seems to think its resolution is larger (1080x1920) than the real display resolution (720x1280), so my touch is misplaced. I know how to change the display (physical) resolution using wm size, but that scales the digitizer resolution proportionally.
How do I change the digitizer resolution?
Output of dumpsys SurfaceFlinger: pastebin.com/gXnfxJKv
Output of dumpsys display: pastebin.com/bwkjXHxH
(The phone is Lenovo A7000, but that shouldn't matter. The error persists after upgrading firmware, rebooting etc. I haven't flashed/rooted - yet.)
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
ramiabouzahra said:
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
Click to expand...
Click to collapse
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Xellos0 said:
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Click to expand...
Click to collapse
SurfaceFlinger is integrated into the GPU if I am correct, so good luck with changed that
Other than that, at the time of writing, I can't come up with a solution.
Wish you best of luck
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
OJKLLC said:
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
Click to expand...
Click to collapse
& to clarify when in 4K all the time mode with the ABD/Shell command it's not like I can use the whole screen to touch but it'll scale that touch to 1960 by 1080, not the touch for my case is 100% accurate to where I place my finger, issue is that its only sampling 1960 by 1080 of the pixels aka just 1 corner so only useable quarter of the touchscreen with the other 75% completely dead