Hi,
I've got this phone due a week and I'm really scared why they let to distribution something that has problems with typing on keyboard - a really big lag
I am using now the standard keyboard with qwerty OFF on portrait mode and I don't want qwerty on this mode - the phone is too small for really fast typing.
I've turned off XT9 also, I just want physical keyboard replacement without any CPU-using helps, that are for me just rubbish, only touch vibrations would be appreciated.
It should be no higher than half of the screen also.
I've used SWYPE, SwiftX and SlideIT, they're only QWERTY which I don't want on portrait mode, I can't turn off hints, which only uses CPU and gives free space away.
Is something there what I'm searching for? Can be paid.
EDIT:
Yes, I've read this topic: http://forum.xda-developers.com/showthread.php?t=1210730&highlight=keyboard&page=2
no help.
I use smart keyboard pro with t9 on portrait and azerty on landscape.
Works flawlessly, you can download dictionaries from market and apply 'themes'.
thx, installed trial now, it's fast, simplified keyboard works well, finally I can turn off full screen keyboard on landscape mode, but... is there any way to turn off hints? I really don't need them, better would be without them - more cpu for typing makes less lag.
I borked something... For some reason when my keyboard (any keyboard that uses full screen) goes full screen the font color is changing to white. If it wasn't for the white background this would not be an issue. This happens in landscape, but portrait doesn't go full screen so it works fine.
Does anyone have any idea on how to change the font color in full screen only?
As a work-a-round I have installed a keyboard manager that changes the keyboard based on orientation. I am using SlideIt in landscape and FlexT9 in portrait. Occasionally I use hackers keyboard, but having same issue there. I have a habit of switching keyboards depending on my needs at that time.
dharr18 said:
I borked something... For some reason when my keyboard (any keyboard that uses full screen) goes full screen the font color is changing to white. If it wasn't for the white background this would not be an issue. This happens in landscape, but portrait doesn't go full screen so it works fine.
Click to expand...
Click to collapse
What do you mean, ''keyboard that uses full screen''? Can you give an example of which keyboard app, which editor app (does it happen when you post on this forum, for example?), and what do you do to make it ''go full screen''?
(By the way, I am using Hackers' Keyboard. All the keys are there, and you can move the cursor with onscreen keys.)
In landscape using hackers keyboard or flext9, when the keyboard expands the entry field goes from web page/ app/ entry field to the fill screen mode where the keyboard takes up half the screen and the other half is a separate input screen, not the web page view.
Sent from my A500 using Tapatalk
Hi.
As keyboard I am using "Hackers Keyboard". 4 Row only.
I'd like to use HK as a full screen keyboard in Landscape mode, meaning in Landscape there should be only the keyboard (big) and a textbox where I am writing currently. I Portrait it should be "normal" keyboard and everything else visible (textbox, background, other text, etc).
How can I achieve that the keyboard is "big with textbox" in Landscape?
Currently it does the same as in Portrait, big keyboard and a little gap between keyboard an the upper screen. On some apps, this is not enough to display a textbox. On others it is enough.
Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
As indicated below some touchwiz native apps are affected.
List of known affected applications by changing DPI settings:
S-View (for S-View covers -- slightly misaligned but functional)
Touchwiz Stock Dialer (slightly misaligned but functional -- other non-stock options exist such as Hangouts or ExDialer)
Fingerprint lockscreen (arrow pointing to finger print scanner off center)
Exchange email (stock Samsung Email)
Stock Camera App
Just FYI to get some easy download links:
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Enable USB debugging on yer phone
-> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Samsung USB drivers you'll need installed
-> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
ADB / Fastboot installer
navigate to C:\adb\ and then run the command they give in the thread
adb shell wm density 540
(not confirmation will be sent but your phone should prompt you to 'allow' your computer to send adb commands to it.).
Restart phone
DPI settings are now at 540. original DPI settings are 640 BTW
imnoob55 said:
Hi all, please see the below thread. Only sharing the info as this was posted on the Verizon N4 forum.
http://forum.xda-developers.com/note-4-verizon/general/root-want-to-modify-dpi-t2960644
Hope this helps...
Click to expand...
Click to collapse
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
redphazon said:
I came across that thread a few hours ago. It's pretty neat to be able to drop the density and make more use of display space (could even drop it down to 384 and make it look more like a tablet), but it has its problems. Samsung apps (Dialer, camera, S Note, S-View, etc) will lose their screen alignment and/or only cover a portion of the screen when altering the density. Finding an alternate dialer was easy enough, but I'm having trouble finding a camera app similar to stock in quality, and was unsuccessful at replacing the S-View...
Click to expand...
Click to collapse
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
imnoob55 said:
Yup unfortunately that is a side-effect of doing this. Only way to do it that I am aware of conventionally would be via xposed or loading in custom TW apps, both not possible. Hangout dialer works well, for this. TW stock browser is not affected. My S-Note is not affected either, too. Dialer and S-View are (not unusable, they just are not center-aligned any longer as their height/width are set on static widths rather than proportional % when Samsung set up the layout.) Maybe they'll change that in L.
BTW I use Nova for launcher and Hangouts as my dialer. I do use an s-view case, though, which is of course impacted.
Click to expand...
Click to collapse
I'm also using Nova Launcher. I did download ExDialer at first, but I went to Hangouts Dialer instead since ExDialer has a trial period and costs money.
S Note is largely unaffected yes, but when you open the camera for copying documents, the square used for aligning the camera with the document is off-center. It doesn't seem to hurt functionality in any way, though. Oddly enough, the camera when used in S Note is fullscreen...
As far as S-View goes, I'm thinking about removing the flip cover. S-View is nice, but I'm always trying to not get smudges on the cover screen on top of the phone display, so the cover is a little bit cumbersome to me when holding it. Seeing how much better the phone looks at a lower density makes me lean even closer to just getting rid of it. That leaves me with just the camera replacement...
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jfenton78 said:
Can anyone confirm if this impacts the play store? Typically changing the dpi on the whole device would prevent the play store from downloading some apps.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
I haven't seen any problems with the Play Store yet, though I haven't been installing much of anything, either. The few apps I've installed so far gave me no trouble.
Also, just found out that the stock camera has no problems with accurate button detection when the phone is turned sideways for landscape rotation, though it's still not fullscreen. You have to guess where the buttons are on the screen in portrait when the density is changed.
Couple of tips:
if you get an error about the device being offline make sure you've got the current ADB installed. The link provided for the adb and fastboot didn't work for me because the file didn't install. The program is just an auto run zip file. you can open with 7-zip and just extract the adb files.
also if you get an error about the device being unauthorized you must select no action on the windows pop up and always perform this action. the phone should then get a pop up with the RSA key number and ask you to authorize. hope this helps.
540 DPI is pretty nice.
I was okay with the dialer and lockscreen, but the camera made me go back to 640. In vertical shooting mode, the touch points for all the icons, including the shutter button, is misaligned and is very annoying. What a shame as 540 looked AWESOME.
cj00ta said:
Exchange email is also broken... when you reply to an email, the screen font is set to eleventybillion.
-----
Sent with my Galaxy Note 4
Click to expand...
Click to collapse
Thanks! Just added to the top thread under impacted apps
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Conkrete said:
Does this effectively change the resolution? I'm curious if lowering the DPI would give positive improvement to high-end game performance. Can anyone shed some light here?
Click to expand...
Click to collapse
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
imnoob55 said:
It doesn't change the resolution. What it changes is the drawing size of on-screen content which is directly from the 'dpi setting' of the phone.
It's a little complicated to explain but this is how it works;
The phone's default screen density (DPI) setting 640, this is done because that's how many dots per inch of the physical screen there is (a phone of similar screen size would have a similar dpi). This value is stored in your phone's build.prop and is read by numerous applications, it might not match exactly the 'real' dpi of the screen but its normally very close to it.
By changing it lower in dpi you're instructing to applications you actually have a smaller screen size, thus to fit content (i.e words not being HUGE on a small screen) content is drawn to that dpi setting you're providing in build.prop.
Now to go into why we have certain issues when changing the dpi.
This is basically due to how the app did its layout sizing (do I base content on "actual size" of the screen-size or do I base it on "actual density" of the screen density in build.prop? Most apps, since they're targeting to be used with dozens of devices of all sorts of different sizes, will be designed where the layout of content is dependent upon dpi. A layout would be I want a rectangular box on the bottom that has height 10px and width 100%, so that effectively means the width is based on the proportion of the screen size (the OS controls this, its just a matter of scaling). This is why you once had 5 items to show now has 8 items to show in a listbox. The size of the listbox in this case would be based on actual density while the content (text etc.) inside would be based on actual size (scaling I would think is limited to a min/max actual size for text).
Samsung can get away with this on their stock apps because in their mind when they build their roms they are only going to be used on that specific device. They're starting to go away from this, however, and are starting to make their layouts more typical that of a normal application. You have somewhat less control of the layout going from actual size to actual density.
*keep in mind you can actually set parameters for both. Such as if I wanted something to be 10% in width but only up to 2.5 inches in actual size this effectively means that it will scale until it reaches 2.5" and then scale no longer.
I hope that makes sense. Resolution really doesn't have a role at all in this, you're always at the same resolution (4K) and this is handled by the lower-level kernel and GPU firmware. I don't think there's a way to change this at the app layer but than again I have really no background in android development.
*please if anything comes off as inaccurate please point out, I am from a XAML/.NET development background and linux/unix embedded systems and really I focused on back-end/databases/services and not really front-endy stuff. This is how it is handled in XAML though and I have seen android uses the same principals.
Click to expand...
Click to collapse
Extremely helpful and great info. Possibly the best response I've received from XDA. Thank you for the info. I have found a couple root apps that claim to change resolution but I've been hoping to find a non-root alternative.
I tried using the adb command and while it does adjust the DPI, the keyboard will shrink to a point where its impossible to actually type, but the size of the screen elements are to my liking.
I didnt see ro.sf.lcd.density in my build.prop so I added it in but it doesn't seem to be doing anything on a reboot. On my 6P I was able to adjust the DPI with this line and the keyboard wouldnt shrink so it was still usable for my thumbs.
Has anyone found a way to adjust the DPI outside of the adb command that would give more screen real estate without compromising keyboard usability? Maybe some values you guys are liking that you can suggest to me.
Thank you
pr0adam said:
I tried using the adb command and while it does adjust the DPI, the keyboard will shrink to a point where its impossible to actually type, but the size of the screen elements are to my liking.
I didnt see ro.sf.lcd.density in my build.prop so I added it in but it doesn't seem to be doing anything on a reboot. On my 6P I was able to adjust the DPI with this line and the keyboard wouldnt shrink so it was still usable for my thumbs.
Has anyone found a way to adjust the DPI outside of the adb command that would give more screen real estate without compromising keyboard usability? Maybe some values you guys are liking that you can suggest to me.
Thank you
Click to expand...
Click to collapse
Developer options > smallest width.
mitchdickson said:
Developer options > smallest width.
Click to expand...
Click to collapse
Oh i should have mentioned that as well. Shrinks the keyboard like crazy. Ideally I want a way that shrinks everything BUT Swiftkey. Today in a different thread I found you can shrink everything and scale up GBoard which may be what I end up doing but Im a bit stubborn since on the 6P I was able to shrink everything but swiftkey.
Are you talking about Swiftkey specifically? I changed the display size in Display settings, and the default Gboard keyboard stayed the same size when the display size was both Default, and then when I went up a size. It stayed the same. I expected it to get bigger, but it didn't. Unless it did, and I didn't notice, but when I put the display size back to default the keyboard stayed the same size cause it looked almost too big compared to the rest of the display. Does your default Gboard keyboard get bigger/smaller when changing the display size?