I am using the latest HTC TOUCH DIAMOND android port released 9/9/9 released at connect-utb and after having to add the ramaddr line to the startup then change the startup.txts name to default.txt and starting it up the command line runs and the penugin comes up then after a bit of alot of text scrolling it goes to a complete black screen except a "_" underscore blinking at the very top left.. If anyone has a default.txt that works for the htc touch diamond with this release id love to have it.. any help? it just sit sthere and every now and then the underscore unfreezes and blinks a few time then freezes for awhile. how do i get past this i want to play with android!
Anyone help please?.
Also its a diam500 and heres my startup.txt that im using..
Code:
set RAMSIZE 0x06000000
set ramaddr 0x10000000
set MTYPE 1805
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Hitachi 2=Topoly 3=Samsung
# mddi.width - width of the scaled display
# mddi.height - height of the scaled display (these should be multiples of 16 for the camera to work I think)
set cmdline "msmts_calib=115.105.863.911 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 ppp.apn=movistar.es ppp.username=MOVISTAR ppp.password=MOVISTAR no_console_suspend"
#set cmdline "no_console_suspend"
# fbcon=rotate:1
# console=ttyMSM0"
boot
Hello, i have the 1cm dead touchscreen zone in the top and bottom, not good for the android taskbar...
Can we recalibrate the resolution / screen parameter to reduce a little the screen height to fix the problem ??
Thank you.
same problem here .. heeeelp
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
I7V said:
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
Click to expand...
Click to collapse
Than You, i had no success with NOMONE Resolution Changer, impossible to install for me tough Play Store (not allowed in my country) and the multiple apk found on the net was not good, an error 'probleme with parsing installer' something like this.
I found "Resolution Changer Pro" who work very well, the perfect resolution for me is : 970 x 768.
Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
I need to resize the screen of my Nexus 7 (2013) in order to fit with the car-dash enclosure where i'm willing to install it.
The enclosure i bought was supposed to fit for the nexus display but regrettably whilst the latter is of abt 15.3cm wide x 9.5 cm "tall" (sorry for my english) the enclosure has a window of 15.3 cm wide but only 8.7 cm tall which would make impossible the access to the softkeys.
In view of the above and considering also that there is no space available to enlarge the window of the enclosure i thought and hoped it would have been easier to resize the screen.
Now the question is: considering that the measures reported are relevant to the device in landscape mode may i kidly ask you the command variables that i have to amend to cut off the 0.8 cm on the bottom side of the screen (again landscape mode).
Thanks a lot in advance for your help!
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
eric_thefool said:
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
!
Click to expand...
Click to collapse
Did you solve the problem?
davis_llb26 said:
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
Click to expand...
Click to collapse
Did u get through with this problem..??
i too have the same problem but mine is 25% of the screen so i can use whats app and all other app but the plain box is disturbing me too...
Confirm the adb route works without root!
silvake said:
Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
Click to expand...
Click to collapse
A long time since the original post and answers, but I thought it should be noted that this method works well. Thanks silvake.
My Mecer tablet stopped responding in the top 2-3cm after many years of loyal service. Could have been a drop or simply age. It is still useful and wish to give it to someone in need. So searching around and several different sites yielded some results. Note this is not a mainstream device so rooting was not an option nor attempted. Indeed drivers and any info is sparse for this device.
For anyone attempting this, I will outline my method and steps.
1. Enable USB debugging. There are many tutorials. Settings->About->Build number(tap x 7); Developer Options->USB debugging
2. Connect device with USB Cable. Give permission on device. You will need to make sure that windows installs drivers. At first windows failed to install all drivers. Not sure how it managed, but it connected eventually.
3. Download adb: https://android.izzysoft.de/downloads.php. I used https://android.izzysoft.de/downloads.php?file=adb-binaries-windows-29.0.4.zip. Decompress to desired folder. Open cmd to the folder.
4. Run adb.exe with 'adb devices' and confirm device is listed. First attempt showed:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0123456789ABCDEF unauthorized
I had to give permission on the device. Reconnected USB.
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
List of devices attached
0123456789ABCDEF device
Success! Device is now connected.
Next get the current display stats:
Type 'adb shell'
Confirm connection. Mine showed: [email protected]:/ #
Type: ‘dumpsys display | grep mBaseDisplayInfo’
Below is the capture of the operation:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # dumpsys display | grep mBaseDisplayInfo
mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 800 x 1280, real 800 x 1280, largest app 800 x 1280, smallest app 800 x 1280, 55.84 fps, rotation0, density 190 (190.0 x 190.0) dpi, layerStack 0, type BUILT_IN, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
This is not really required but helps to determine the current stats to make a guess on the number of pixels to adjust the screen by.
Next is the command to adjust the screen. The 4 numbers are the coordinates. Since mine was the top area I adjusted only that.
Type: wm overscan 0,50,0,0
The update is live and you should see the screen drop 50 pixels from the top.
This was not enough for me so repeat until the pull down of the status bar starts working again.
Here is the whole list to adjust the screen until everything is working again:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # wm overscan 0,50,0,0
[email protected]:/ # wm overscan 0,70,0,0
[email protected]:/ # wm overscan 0,80,0,0
[email protected]:/ # wm overscan 0,100,0,0
[email protected]:/ # wm overscan 0,200,0,0
[email protected]:/ # wm overscan 0,120,0,0
[email protected]:/ # wm overscan 0,140,0,0
[email protected]:/ # wm overscan 0,150,0,0
[email protected]:/ # wm overscan 0,160,0,0
[email protected]:/ # wm overscan 0,170,0,0
[email protected]:/ # wm overscan 0,180,0,0
[email protected]:/ # wm overscan 0,190,0,0
[email protected]:/ # wm overscan 0,195,0,0
[email protected]:/ # exit
So I had to move the screen 195 pixels down until the dead touchscreen area was excluded.
Screen is obviously smaller but the frustration of having to rotate the device 180 to be able to pull down the status bar is removed. Much worth it.
Now a child in need of education can still learn and we have saved the device from landfill and reduced the carbon footprint.
You might have to adjust the pixel density to compensate for the loss, but I left it untouched. Your results will vary so I cannot assist.
Excerpt from another site:
"Additionally decreasing the density through the settings (Display & lights > screen > LCD density) or the wm command helped compensating for the lost display area:
wm density 360"
Hope this helps someone as it helped me.
T
Hello amazing people,
I am looking for your guide/advice for solving a screen resolution issue.
I am using a 4:3 ratio screen with a LCD driver on Radxa Zero.
the poblem is that the screen looks stretched laterally. I think its due to aspect ratio becuase the lcd is of 4:3 aspect ratio.
can anyone help me how can I change the aspect ratio using adb?
I have worked with size and density but failed to produce any results.
Many thanks to this amazing community.
the side of may cellphone is not working
Hi all, urgently need help with displaying output form Raspberry Pi to my HDMI monitor! I'm trying to boot Pi 3B with USB and display onto an HDMI monitor, but all the output I see is a black screen.
Tools:
- 1x USB (flashed via Etcher with Debian Stretch with Raspberry Pi Desktop)
- 1x monitor (connected via HDMI-HDMI 1.5m cable): 1024x768
- 1x Raspberry Pi 3B model (connected to 5V supply)
I've referenced many relevant threads, changed my "config.txt" file accordingly, but it doesn't seem to fix the problem.
Here's my config.txt file:
program_usb_boot_mode=1
# For more options and information see
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=16
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=11
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
Any assistance is greatly appreciated!!
On Android head units, the orientation typically defaults to landscape. And has disabled auto-rotation, the screen will always remain in a landscape mode. This effectively means you can't use any software on Google Play Store or other places to change this default because auto-rotation is disabled (they at best, can reverse the screen but cannot rotate it). I need to change this feature to portrait for the custom firmware I placed on my head unit (which is using Android 10).
In my attempts to work out how to do this, I have gathered some information, but I have not got enough experience or knowledge to know how to do this. I really need some with experience who likes these challenges.
I believe in order to do this correctly, this needs to be done at root, and place in one of these locations in Magisk
(1) /data/adb/post-fs-data.d (think it needs to be here)
or
(2) /data/adb/service.d/
and the command syntax would look it something like this (3)
adb shell settings put system accelerometer_rotation 0 # auto-rotation, 0 disable, 1 enable
adb shell settings put system user_rotation 0 # actual-rotation, clockwise, options 0[0°], 1[90°],2[180°],3[270°]
source:- https://stackoverflow.com/questions/25864385/changing-android-device-orientation-with-adb
or (4)
content insert --uri content://settings/system --bind name:s:accelerometer_rotation --bind value:i:0
content insert --uri content://settings/system --bind name:s:user_rotation --bind value:i:0
or (5)
import android.provider.Settings;
// You can get ContentResolver from the Context
Settings.System.putInt(getContentResolver(), Settings.System.ACCELEROMETER_ROTATION, 0);
Settings.System.putInt(getContentResolver(), Settings.System.USER_ROTATION, 0);
or something else (Other source documents)
How to change Android default-natural orientation?
I have my device running android Jellybean 4.2.2 with Landscape as the default/natural orientation. How can I change the default/natural orientation of the same to portrait? Here is what I have t...
android.stackexchange.com
Disable Screen Rotation Landscape Mode in Android React Native
Disable Screen Rotation Landscape Mode in Android React Native. This tutorial explains how to disable screen rotation landscape mode in android react native application. There are two different types of orientation in android device, Portrait mode and Landscape mode. Portrait mode is default...
www.skptricks.com
Set Android default orientation to portrait mode - Boundary Devices
The default screen orientation for the Android-ready Nitrogen and Nitrogen53 is landscape. That’s fine for most people, but say you want it in portrait. Or upside down, or whatever. That’s a problem, since Android usually takes rotation instructions from code that expects motion sensor input...
boundarydevices.com
or (6)
There is an existing module I should be using ?
Thank you for any time you invest on this.
I have also been wondering if Magisk can do this, would be of value to have the ability to inject landscape or portrait as default, and the ability to turn on/off auto rotate would make this more appealing/useful code for developers and fix my issue?
Anyway, just an idea without the skill/knowledge to make it happen.
Recently switched my Pi4 over to the 64 bit Pi OS. I have a 7" Raspberry monitor that is displaying upside down so I have to turn my monitor 180. I tried display_rotate=2 in config.txt but no joy. Then I tried lcd_rotate=2 but still no joy. Then I tried display_rotate=2 AND lcd_rotate=2 in the config.txt During the reboot process I got a very short display that was correct but when it finished the reboot I was right back to being upsidedown. This was not an issue when I was running Raspbian Buster, the previous OS. Any fix or suggestions are greatly appreciated.
In the terminal
sudo nano /boot/config.txt
Then add the line:
lcd_rotate=2
Thats what is seen on the forums
Open the Terminal screen.
Access the config file using sudo nano /boot/config.txt
Enter a new line with the text display_rotate=2 (CASES OF NON-TOUCH DISPLAYS)
Press CONTROL+X then Y then ENTER to Save
Type sudo reboot to reboot and your LCD will be rotated!
To set screen orientation when in console mode, you will need to edit the kernel command line to pass the required orientation to the system.
sudo nano /boot/cmdline.txt
To rotate by 90 degrees clockwise, add the following to the cmdline, making sure everything is on the same line, do not add any carriage returns. Possible rotation values are 0, 90, 180 and 270.
video=DSI-1:[email protected],rotate=90
—— assuming you dont have a built in display and you are using HDMI?
The DSI text should be changed to HDMI
FOR NON TOUCH DISPLAYS
———
Launch the terminal and execute the commandaccording to the rotation you want.
DISPLAY=:0 xrandr --output HDMI-1 --rotate right
DISPLAY=:0 xrandr --output HDMI-1 --rotate left
DISPLAY=:0 xrandr --output HDMI-1 --rotate inverted
To reset rotation back to normal, use the command
DISPLAY=:0 xrandr --output HDMI-1 --rotate normal
Kenora_I said:
Open the Terminal screen.
Access the config file using sudo nano /boot/config.txt
Enter a new line with the text display_rotate=2 (CASES OF NON-TOUCH DISPLAYS)
Press CONTROL+X then Y then ENTER to Save
Type sudo reboot to reboot and your LCD will be rotated!
Click to expand...
Click to collapse
Thanks for the reply. However, I tried this and it did not rotate.
Kenora_I said:
To set screen orientation when in console mode, you will need to edit the kernel command line to pass the required orientation to the system.
sudo nano /boot/cmdline.txt
To rotate by 90 degrees clockwise, add the following to the cmdline, making sure everything is on the same line, do not add any carriage returns. Possible rotation values are 0, 90, 180 and 270.
video=DSI-1:[email protected],rotate=90
—— assuming you dont have a built in display and you are using HDMI?
The DSI text should be changed to HDMI
Click to expand...
Click to collapse
I am not using HDMI. As I mentioned, I'm using the official 7" Raspberry non-touch display.