In the dev options there's an input field 'smallest width' - set it to like 450px, then in accessibility change text size to large or huge, whichever is best for you.
You can also do this through ADB.
To retrieve the current density:
adb shell wm density
Click to expand...
Click to collapse
To set a new density (replace 450 with desired density):
adb shell wm density 450
Click to expand...
Click to collapse
You should force quit the launcher (or reboot) after you update the density... Sometimes it doesn't react well to the change.
sevnsevn said:
You can also do this through ADB.
To retrieve the current density:
To set a new density (replace 450 with desired density):
You should force quit the launcher (or reboot) after you update the density... Sometimes it doesn't react well to the change.
Click to expand...
Click to collapse
What else can you do through adb that you can't do through settings?
I just wanted to confirm that this works up to 450 (auto changes to 449), however when doing this, it glitches out the dock some times where the icons get condensed in the middle, but on reboot they go back to normal until an app is opened, any higher than 449dpi and the phone completely glitches out, at 480 the labels in the app draw start to get cut off, and at 500 the app drawer won't even open.
This is just from testing on mine, which is a Pulse colour model (known to have way more issues than Eclipse Black) so your mileage may vary.
bANONYMOUS said:
I just wanted to confirm that this works up to 450 (auto changes to 449), however when doing this, it glitches out the dock some times where the icons get condensed in the middle, but on reboot they go back to normal until an app is opened, any higher than 449dpi and the phone completely glitches out, at 480 the labels in the app draw start to get cut off, and at 500 the app drawer won't even open.
This is just from testing on mine, which is a Pulse colour model (known to have way more issues than Eclipse Black) so your mileage may vary.
Click to expand...
Click to collapse
I have this same problem on my Redmagic 6. Did you find any solution to this? Also, dial pad in phone app slides to the left side when I change width value.
Related
NightStand is a simple alarm clock application with large numbers to be easily seen.
It allows for the phone to dim the screen but keeps it from turning off for that middle of the night glance to see what time it is.
Features Include:
Alarm with 8 sounds
Custom Color of the Digits
5 Minute Snooze Button
Solve an easy math problem to help you wake up (to you turn alarm off)
Automatically runs on AC power (optional)
Keep the device awake or let it go to sleep (optional)
12/24 Hour setting
How To Use:
When you run the application click on the configure button (upper right corner) to set all the settings
Three sliders allow you to set the custom color.
Alarm toggle to set the alarm and the sound.
AC Toggle to set Auto mode.
When the alarm is going off, click the snooze button to snooze or click anywhere on the screen to stop the alarm.
Update 1.1
The alarm should now go off regardless of what phase the phone is in (device awake or sleep), the app is running or not.
Screen is flipped
Update 1.2
Added an option to flip the screen
Update 1.2.1
Minor Update to start NightStand with correct orientation, Flip Screen option takes effect right away
Updated to work on HD2
Update 1.2.2
Fixed shifted screen on WVGA resolution (I think)
Added toggle for math question on exit
Phone stays awake while alarm is going off (for heavy sleepers like myself )
Looks nice.
A couple of issues on my TP2. The display is rotated the wrong way, and sliding the keyboard our causes it to get distorted. I'd prefer to use it with the keyboard out as I can tilt my phone .
I like it though, nice start.
P.S. let me know if you want the thread moving to the Development & Hacking apps forum from the Diamond one.
Dave
I just uploaded an updated version, try it out and let me know if it works better with the keyboard out.
Thanks
It crashes if you run the app with the keyboard out, and it is still upside down if I open the Keyboard after running the app.
Ta
Dave
it rotates correctly on my tp2, thanks just what i was looking for
Awesome work!I really like the big number.but,why not add a toggle button to turn off the backlight in the settings.I think it will waste lots of power when the device keeps dim.Perhaps you can add a sensor to lighten the lcd when we want to see what's the time now.
This Doesnt Work on my HTC HD2 even tho it suports WVGA Screens, WHY??
thanx.
hermanm said:
NightStand is a simple alarm clock application with large numbers to be easily seen.
It allows for the phone to dim the screen but keeps it from turning off for that middle of the night glance to see what time it is.
Features Include:
Alarm with 8 sounds
Custom Color of the Digits
5 Minute Snooze Button
Solve an easy math problem to help you wake up (to you turn alarm off)
Automatically runs on AC power (optional)
12/24 Hour setting
How To Use:
When you run the application click on the configure button (upper right corner) to set all the settings
Three sliders allow you to set the custom color.
Alarm toggle to set the alarm and the sound.
AC Toggle to set Auto mode.
When the alarm is going off, click the snooze button to snooze or click anywhere on the screen to stop the alarm.
Click to expand...
Click to collapse
DaveShaw said:
It crashes if you run the app with the keyboard out, and it is still upside down if I open the Keyboard after running the app.
Ta
Dave
Click to expand...
Click to collapse
same here. Great work though! Love it.
XDAPPCgeeks said:
it rotates correctly on my tp2, thanks just what i was looking for
Click to expand...
Click to collapse
does yours work when u slide open the keyboard and tilt it? i know i can use changescreen to change to rotation but it doesn't work with the keyboard open.
edit: i've jus hard reset and it works fine now even with keyboard open. Sorry for any inconvenience.
Same here, on my HD2 it's a nasty mix of colour. it needs something else to add?
remotek said:
This Doesnt Work on my HTC HD2 even tho it suports WVGA Screens, WHY??
thanx.
Click to expand...
Click to collapse
same here, on my HD2 I've got only two color squares in the corners and one big rectangle in the middle... so no clock. settings and exit "square" button work well.
Not working on my HD2 either. Two boxes of colour on each side of the left hand side of the screen - one to change settings and one to exit plus a big box in the middle which is meant to be the digits i guess.
I got an error starting the program:
Can't find PInvoke DLL 'libgles_cm.dll'.
I got the same error on my omnia.
Can't find PInvoke DLL 'libgles_cm.dll'.
Please try to fix it. This is the program that I have been waiting for. Too Cool.
Robb
I got an error starting the program:
Can't find PInvoke DLL 'libgles_cm.dll'. (using HTC wm 6.1)
If you get the libgles_cm error i just uploaded a cab, give it a try
I got this error message when opening this program:
"MissingMethodException
This application requires a newer version of the Microsoft® .NET Compact Framework than the version installed on this device."
Please help.
you need .net 3.5
1.1 now has the correct orientation, but the display is messed up if I put the phone in Landscape and then open it.
Only a minor annoyance.
Dave
any way you could send me some screenshots so i can see if i can fix it..
Ok now working on my Omnia after installing 1.1 and the libgs cab you posted.
Two things.
First, if you have SPB Mobile Shell 3.0.1 installed, the app comes up but is shifted slightly. I believe this is because they do something with the top windows start bar. Not a huge deal but something I thought you could check into.
Secondly, Could you have a setting to determine which way to have the screen flip? I would like it 180 from where it is now. My power plug ends up on the bottom and so the phone won't sit level. If it was landscape but the other way, it would be perfect for the omnia.
Thanks,
Robb
My hd2 motion sensor is tilted for every rom is there any way to fix/calibrate it?
Sent from my HTC HD2 using XDA
joshu111 said:
My hd2 motion sensor is tilted for every rom is there any way to fix/calibrate it?
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
As far as I know, no...
joshu111 said:
My hd2 motion sensor is tilted for every rom is there any way to fix/calibrate it?
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
I have the same issue and after a lot of searching found this:
How to Calibrate the g-sensor
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Install an app that displays sensor information along with pitch and roll. (such as SensorDebug from Android market)
Put your phone on a level surface such as the floor or a table.
Note your pitch and roll values.
Use rootexplorer or similar file manager to edit /data/misc/AK8973Prms.txt file. (open in text editor) (For ASTRO CHECK POST 70 in page 7)
You will see AOFFSET.x and AOFFSET.y at the bottom. (May be on top if you autocalibrated previously)
y affects pitch and x affects roll, there is about 4 to 1 ratio.
What you are trying to do is make pitch and roll 0 with minimum flicker.
Press and hold home button to switch between rootexplorer and sensordebug. Your changes will be reflected in realtime (with most builds). Go back and forth a few times to get perfect result. (You can press and hold home button to go back and forth) If you think changing values don't have an affect, try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting, use different sensor app and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
For example:
If pitch is 3 and roll is -1
you may start by
AOFFSET.x=4
AOFFSET.y=-12
Then adjust with 1 increments to get rid of flicker.
It is best to adjust one value at a time.
You can use gpsstatus or bubble app (to find bubble app search the market for bz.ktk.bubble and enable "show angle" from bubble apps settings.) for visual check of orientation calibration. Because of the protruding camera lens of hd2, there can be 1 degree difference between sideways and normal orientation. (It seems you can adjust in about 0.25 degree increments by each 1 increment of AOFFSET and compansate by lowering AOFFSET=y by 2 that gives 0 degrees in both normal and sideways orientation in bubble app)
- You don't need to reboot for most builds (if there is no affect check post 11)
- You don't need to kill/restart akmd
- You don't even need to close sensor app
- Because of not perfect kernel/build support for sensors, you may see them freeze when you move the phone (TS will also freeze). With evo kernels, just wait a few seconds and it will resume. (With nexus kernels they may freeze until sleep/wakeup) Interestingly the values of AK8973Prms.txt affect shake/move freezes. I wrote about this in post 10 and 11.
IT IS A GOOD IDEA TO BACKUP COMPLETE ANDROID FOLDER BEFOREHAND just in case something goes wrong. Chefs say you shouldn't auto calibrate your g-sensor under Android because with many people it gets messed up. Also good idea to backup your /data/misc/AK8973Prms.txt
Click to expand...
Click to collapse
Sorry can remember where it got it from... but if this post helps you, hit thanks
Aoffset.x=14
Aoffset.y=-26
Aoffset.z=10
Is my tweaked zeroed values. It should give you almost perfect level. If not then adjust it by increments ±1or 2
It wierdly off balance and you can’t exactly zero it in non sense versions for some reason.
Oh and remember that if you want to try to make it level yourself, make sure to take off case and balance it on the camera frame or move the camera out of the way on the edge of the table so the protruding camera doesn't interfere with calibration.
Thank you very much
Sent from my HTC HD2 using XDA
same thing happened to me
So coming from a iPhone 6 plus, there are one thing that I miss about the Apple The fact that I could type heaps faster on the touchscreen while even if I tried countless 3rd party keyboards (Swiftkey, Google Keyboard, Ect...) but I recently downloaded the "SGS Touchscreen Booster from the Google play store. No root is needed for this app.
My current settings are: <recommend using the s-pen to get the exact value>
Sensitivity* 80
Duration to register touch* 0
Minimum motion* 0
Motion filter* 70
Multi-touch points* 5
{check} Start service on boot
There should be a huge decrease in the lag that the keyboard from the inputs.
Feel free to share your own settings, as these were the ones I got from a random blog and it seems to work great on my phone.
Thanks for recommending this app! I found when I typed really fast the keyboard struggles to keep up and would as a result somehow replicate some words I type. So far it hasn't happened after installing this and the keyboard seems to register a lot faster!
There is also a higher-sensitivity mode built in for when wearing gloves etc...
Settings > Display and wallpaper > Increase touch sensitivity
I haven't tested it for more than a couple of minutes but it did seem to make a difference
Near the bottom of the app window, it states that "*Less value means more sensitivity". You're suggesting changing sensitivity from default value of 40 to 80 meaning reducing sensitivity. It doesn't make any sense here. The only settings reducing the keyboard lag seem to be duration to register and minimum motion settings. Someone correct me if I am wrong please?
I've actually had a lot of success using the Fleksy keyboard. I haven't been able to text without looking at the phone in so long. It's a breath of fresh air.
Sent from my SM-N915T using XDA Free mobile app
I've tried this but when on the phone wakes up in my pocket and dings as the screenew constantly tries to unlock as I'm walking
umair239 said:
Near the bottom of the app window, it states that "*Less value means more sensitivity". You're suggesting changing sensitivity from default value of 40 to 80 meaning reducing sensitivity. It doesn't make any sense here. The only settings reducing the keyboard lag seem to be duration to register and minimum motion settings. Someone correct me if I am wrong please?
Click to expand...
Click to collapse
Yeah I noticed that, I assumed it was to balance out all the other settings that you have changed. I feels great to me actually. As the optimized/super optimized presets seem to jittery to me. Well its just my preference to go with these settings, as I found them on a online blog and worked flawless with me.
Hello guys,
So, I changed the default dp of 423 to 480 and noticed that the long press action of the home button (Now on Tap) stopped working. When I changed it back to default (423dp) it started working normally. I began to slowly increase the dp value and noticed that it works until 479dp. It stops working at 480. Also, 479 is the last value where the stock launcher column size is 5, if you set it to 480 the column size increases to 6, maybe that has something to do. I don't know why this is happening and if it can be solved. If any of you has a clue I would love to hear it
agus97v said:
Hello guys,
So, I changed the default dp of 423 to 480 and noticed that the long press action of the home button (Now on Tap) stopped working. When I changed it back to default (423dp) it started working normally. I began to slowly increase the dp value and noticed that it works until 479dp. It stops working at 480. Also, 479 is the last value where the stock launcher column size is 5, if you set it to 480 the column size increases to 6, maybe that has something to do. I don't know why this is happening and if it can be solved. If any of you has a clue I would love to hear it
Click to expand...
Click to collapse
Usually when I change resolution and density with wm size 1080x1920 and wm density the capacitive buttons simply stop working entirely. This is fixed with miPOP though, so that's one good use for it
I have no idea how the capacitive buttons are handled. I always guessed they were an extension of the touchscreen, and this does nothing but prove this: the phone thinks they are farther down, maybe?
agus97v said:
Hello guys,
So, I changed the default dp of 423 to 480 and noticed that the long press action of the home button (Now on Tap) stopped working. When I changed it back to default (423dp) it started working normally. I began to slowly increase the dp value and noticed that it works until 479dp. It stops working at 480. Also, 479 is the last value where the stock launcher column size is 5, if you set it to 480 the column size increases to 6, maybe that has something to do. I don't know why this is happening and if it can be solved. If any of you has a clue I would love to hear it
Click to expand...
Click to collapse
I'm guessing you are on the stock rom?
I've had this problem before. I tried to set the dpi of my screen to 450 just to see what it was like so i used
Code:
wm density 450
but I couldn't get to google afterwards. It's been a problem ever since I got the phone (MM B20).
I would just keep it at 480.
Choose an username... said:
Usually when I change resolution and density with wm size 1080x1920 and wm density the capacitive buttons simply stop working entirely. This is fixed with miPOP though, so that's one good use for it
I have no idea how the capacitive buttons are handled. I always guessed they were an extension of the touchscreen, and this does nothing but prove this: the phone thinks they are farther down, maybe?
Click to expand...
Click to collapse
I thought the same thing about the phone thinking the buttons are farther down but I don't think that's the case because only the long press action of the home button doesn't work. Single touch works on every button and long pressing on recent apps to open multi-window mode also works well.
I tried with miPOP but I think that long press actions aren't enabled on it. Or at least I can't get them to work.
Also, I changed the dp value from Developer Options and not using wm size or wm density.
awsomjgp said:
I'm guessing you are on the stock rom?
I've had this problem before. I tried to set the dpi of my screen to 450 just to see what it was like so i used but I couldn't get to google afterwards. It's been a problem ever since I got the phone (MM B20).
I would just keep it at 480.
Click to expand...
Click to collapse
Yes, I'm on stock running Nougat 7.1.1
Don't laugh to hard about this, but I like to play Clash Royale in full screen. I can't for the life of me get it to fill the entire screen (app is not listed under the options to make app full screen). Any ideas how to force this?
This. I already asked this question but people don't understand what I want. I want Google chrome to use the entire screen ignoring the notch underneath. Also, I don't want a black bar up at the top, pretending the notch isn't there and making a huge black bezel.
jkeith1 said:
Don't laugh to hard about this, but I like to play Clash Royale in full screen. I can't for the life of me get it to fill the entire screen (app is not listed under the options to make app full screen). Any ideas how to force this?
Click to expand...
Click to collapse
Great question. I have not found an answer yet either.
But I would also like to do the opposite. There are some apps that I don't want to run in full screen where i want the buttons and top bar to always be visible.
It would be nice if we could "force" which mode we want.
I can only assume this is a developer option in coding.
I think I may have found an answer. I'll give it a try when I get home tonight.
adb shell settings put global policy_control immersive.full=com.android.chrome
Source: https://www.howtogeek.com/302194/ho...to-fullscreen-immersive-mode-without-rooting/
dybrn said:
I think I may have found an answer. I'll give it a try when I get home tonight.
adb shell settings put global policy_control immersive.full=com.android.chrome
Source: https://www.howtogeek.com/302194/ho...to-fullscreen-immersive-mode-without-rooting/
Click to expand...
Click to collapse
Let me know how it goes. I'm not sure if it's an immersive issue or a ratio issue
jkeith1 said:
Let me know how it goes. I'm not sure if it's an immersive issue or a ratio issue
Click to expand...
Click to collapse
It sort of worked but does not give the full results desired.
These two gave me the closest results for chrome
adb shell settings put global policy_control immersive.full=com.android.chrome
adb shell settings put global policy_control immersive.navigation=com.android.chrome
What I believe is happening from my observations:
- Only one app gets the "immersive" variable override at a time. As soon as you set the variable to point to a different app, the policy for the previous is lost.
- The bars are being hidden/shown for apps where the immersive value is not hard coded to force a state.
- When the value is not forced by the app, the window is not streched into the hidden area for the top bar but it is for the navigation bar.
+ The policy setting persists across reboots.
- When the topbar disappears, the window below DOES NOT not expand up to fill in the gap.
+ The top bar can be hidden/set to visible in some apps
+ The navigation bar can be hidden/set to visible in some apps
+When the navigation disappears, the window DOES expand to fill in the lower gap. (this is good)
- Hard Coded values of the Immersive variable in the app does not override the policy variable.
Hope this helps someone.
I'll keep searching for a better answer and post if I find one.
My notes and tests...
From the article:
There are three different kinds of fullscreen modes we can use with the immersive command.
* immersive.full: hides the status bar on top of the screen and the navigation bar on the bottom, if your phone uses virtual navigation buttons. This is what most people want when they think of a fullscreen app.
* immersive.status: hides only the status bar on top.
* immersive.navigation: hides only the navigation bar on the bottom.
* immersive.off: shows top bar and navigation bar
---------- Test 1 ------------
Attempt with Chrome:
I ran the command:
adb shell settings put global policy_control immersive.full=com.android.chrome
* The top bar dissappeared but the window did not expand into the notch area.
* The bottom navigation dissappeared
* The setting persisted after rebooting of the phone
--------- Test 2 -------------
Attempt with Clash
I ran the command:
adb shell settings put global policy_control immersive.status=com.supercell.clashofclans
* Had no effect on Clash - navigation did not reappear
* fullscreen for chrome was reverted
I ran the command:
adb shell settings put global policy_control immersive.off=com.supercell.clashofclans
still no luck they must hard code the value.
---------- Test 3 ---------------
Attempt with Kindle when reading a book.
When kindle is open and selecting books the app acts as desired and notch can be seen.
but when I open a book and go into fullscreen read mode the notch is not there (as if immersive.full is hardcoded in that state)
I ran the command:
adb shell settings put global policy_control immersive.navigation=com.amazon.kindle
* No effect when reading
* reverted setting for chrome to show top and bottom bars again.
* Lost my notch when viewing books list
I tried all the suggested immersive modes and it doesn't appear to work for Clash Royale, but does for some apps. It may be possible to edit the manifest file in the Clash Royale apk to force the aspect ratio, but I've not had much luck finding the correct values to edit.
dybrn said:
- Only one app gets the "immersive" variable override at a time. As soon as you set the variable to point to a different app, the policy for the previous is lost.
[/HIDE]
Click to expand...
Click to collapse
Thanks for the help. I just tested adding multiple package names separated by comma to the immersive.navigation variable and it works.
So for example, if you want to have both Pokemon Go and Pikmin Bloom in immersive mode, you can type
adb shell settings put global policy_control immersive.navigation=com.nianticlabs.pokemongo,com.nianticlabs.pikmin
Hope this helps.