Today my Samsung keyboard changed from long hold on letter and get a symbol like a long hold on "a" would get me "@" but now when I long hold "a" I get "à, á, â, ã....". The keys would also have the symbols in the corners of the keys to show you what a long press would get you but those are also gone.
This started today, I made a text and it was working fine then a couple minutes later I made another text and the keyboard changed.
How do I get back to having a long press gives me a symbol instead of an accented character?
Exposed Wanam has an option to enable symbols. It is set to disable by default. Did you install this lately?
drewcam888 said:
Exposed Wanam has an option to enable symbols. It is set to disable by default. Did you install this lately?
Click to expand...
Click to collapse
I did about a week ago and I haven't enabled any exposed modules yet. Even if it was this app why did it make changes to the keyboard a week after the install and the module was never enabled?
sgibbers17 said:
I did about a week ago and I haven't enabled any exposed modules yet. Even if it was this app why did it make changes to the keyboard a week after the install and the module was never enabled?
Click to expand...
Click to collapse
Enable modules and check the setting in wanam. Thatbis my suggestion
Related
Has anybody been able to change the long duration for the stock keyboard? Love the keyboard, however it takes way to long to get the comma, question mark, etc. Searched for a few methods on here, but nothing has worked.
I want this change badly as well. It takes way too long to get the punctuation. I know swiftkey let's you adjust this but I love this new Samsung keyboard so much I don't want to leave it.
The stock keyboard sucks the dictionary doesn't even suggest new words added
there is an xposed framework file that can change this timeout.
I rooted the phone, installed xposed, unrooted
works great!
TheChefSLC said:
there is an xposed framework file that can change this timeout.
I rooted the phone, installed xposed, unrooted
works great!
Click to expand...
Click to collapse
Do you know which module I need to install? I had Wanam installed but didn't see it anywhere.
Techweed said:
Do you know which module I need to install? I had Wanam installed but didn't see it anywhere.
Click to expand...
Click to collapse
It is called
Samsung keyboard Short Delay
I found it in the xposed repository. I am not sure about wanam
Sent from my SAMSUNG-SM-N900A using Tapatalk
Did any one use Wanam and Gravity Box at the same time already?
Currently I was missing the quick pin unlock and Gravity Box includes this.
In Wanam, I couldn't find the option. Therefore, Wanam has the disable start sound and wake on home button settings which Gravity Box doesn't include.
Any experience?
I'm currently running both, but don't know yet if they affect each other.
I've found I can use both at the same time but many things on both don't work. Eg quick settings tiles and ordering on gravity box.
DrADP said:
I've found I can use both at the same time but many things on both don't work. Eg quick settings tiles and ordering on gravity box.
Click to expand...
Click to collapse
I actually had Gravity Box still installed, so I just reactivated it and tried.
So far, the quick pin unlock works. I hope that skipping tracks with volume buttons still works without glitches. What I had though were 2 circle batteries So I disabled the one in Gravity Box.
It's just really hard to know which settings in one of the modules affects settings of the other one.
So when I open recents now, the close all and manage apps buttons are gone from the bottom of the screen. What did I do?
Chopstix9 said:
So when I open recents now, the close all and manage apps buttons are gone from the bottom of the screen. What did I do?
Click to expand...
Click to collapse
not sure.. with all the detailed info you provided i dont see anyone being able to help you lol
Chopstix9 said:
So when I open recents now, the close all and manage apps buttons are gone from the bottom of the screen. What did I do?
Click to expand...
Click to collapse
are you using gravity box with xposed framework?
i lost recent button as well when using gravity box and messing with the hardware keys options, long press, double tap, etc
i would uninstall gravity box if you have it and see what happens.
FingerBlastJ said:
are you using gravity box with xposed framework?
i lost recent button as well when using gravity box and messing with the hardware keys options, long press, double tap, etc
i would uninstall gravity box if you have it and see what happens.
Click to expand...
Click to collapse
Nope ... no gravity box. Haven't messed with any settings in quite some time and *poof* I open recents one day and the task manager and close all buttons are gone.
Chopstix9 said:
Nope ... no gravity box. Haven't messed with any settings in quite some time and *poof* I open recents one day and the task manager and close all buttons are gone.
Click to expand...
Click to collapse
if thats the case, id install xposed frameworks, install gravity box, mess with the hardware keys options and see if that FIXES it. If not, your next option would be to do a clean wipe and flash.
FingerBlastJ said:
if thats the case, id install xposed frameworks, install gravity box, mess with the hardware keys options and see if that FIXES it. If not, your next option would be to do a clean wipe and flash.
Click to expand...
Click to collapse
Yeah I run xposed with Wanam and a couple other modules. Worth a try I reckon ... Could update to latest release while I'm at it still on NI2 that should take care of it as well ...
Chopstix9 said:
Yeah I run xposed with Wanam and a couple other modules. Worth a try I reckon ... Could update to latest release while I'm at it still on NI2 that should take care of it as well ...
Click to expand...
Click to collapse
Wanam is great for theme-ing , call, security and other tweaks, but i havent seen much about hardware keys in there, your best bet is gravity box for your recent key to come back.
FingerBlastJ said:
Wanam is great for theme-ing , call, security and other tweaks, but i havent seen much about hardware keys in there, your best bet is gravity box for your recent key to come back.
Click to expand...
Click to collapse
Understood re: Wanam ... was just saying I have it in reply to the suggestion I install xposed. Will give it a try.
Didn't make any changes to the phone and *poof* just as mysteriously as they disappeared, they are back ... *shrug*
Has anyone figured out how to turn on on-screen buttons instead of using the capacitive/physical buttons? In the control center, there's option to turn on "virtual button" and it allows you to disable the capacitive/physical buttons, but nothing shows up on the screen.
It's under accessibility
LeEco Pro3
toanau said:
It's under accessibility
LeEco Pro3
Click to expand...
Click to collapse
That only allows you to disable the hard buttons though, doesn't enable soft ones (on screen nav buttons). There's a way to enable them by default editing the build.prop but people were saying it didn't work on emui for some reason. One guy said it works fine, so I don't know. Requires root too though. No root in sight for US variants so far.
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
Are you rooted? Do you have the US model?
Sent from my SM-P600 using XDA-Developers mobile app
toanau said:
Are you rooted? Do you have the US model?
Sent from my SM-P600 using XDA-Developers mobile app
Click to expand...
Click to collapse
I can answer for him lol. Yes, hes rooted, otherwise it wouldnt be possible, and no, because us model cant be rooted atm
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
Please remember, I'd like to extend the button backlight time
Klara Kaiser said:
Please remember, I'd like to extend the button backlight time
Click to expand...
Click to collapse
If I understood that correctly, then you don't need to use softkeys. After the latest update, if you go to accessibility, there is an option for enabling the button backlight as long as the phone screen is on. I attached a picture clearly showing the option if it might help.
p_pal2000 said:
If I understood that correctly, then you don't need to use softkeys. After the latest update, if you go to accessibility, there is an option for enabling the button backlight as long as the phone screen is on. I attached a picture clearly showing the option if it might help.
Click to expand...
Click to collapse
Was exactly what I'm looking for, but I haven't this setting option. Are you at 5.8.0.19S? I'm still on 18S.
So I have to wait
Yep I'm on 19S. I thought all US models had gotten the update, but I forgot that this phone came out in other countries previously ( -_- ). So I suppose you just have to wait a few more days/weeks and hopefully you get the update.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
DANG...WORK FOR ME, US VERSION CONVERTED TO CHINESE AND whammmmm.:good:
THANKS A LOT.
johnkchiu said:
Has anyone figured out how to turn on on-screen buttons instead of using the capacitive/physical buttons? In the control center, there's option to turn on "virtual button" and it allows you to disable the capacitive/physical buttons, but nothing shows up on the screen.
Click to expand...
Click to collapse
Like this?
Install SimpleControl
OR you can Flash CM13 rom they have option for on screen navigation key and disable the hardware one, or you can keep the hardware as stock rom.
This rom I was using it I found it best CM13 rom by far: CM13 LEX720 by Team Superluminal
Nova Launcher also can show the software buttons
Tonnex said:
Nova Launcher also can show the software buttons
Click to expand...
Click to collapse
Where is the option in Nova Launcher? I can't find it.
4K2K said:
I got it working by adding qemu.hw.mainkeys=0 on build.prop.
From there, I got physical buttons to not work by modifying synaptics_dsx.kl file in /System/USR/KEYLAYOUT.
You simply put # in front of all the listed entries (e.g., # key 158 BACK VIRTUAL.)
From there, I also disabled button back light by modifying an another system file. I forgot which file it is.
After those three steps, it is as if it came with soft keys without physical buttons.
Click to expand...
Click to collapse
so far this worked, did you remember what file the backlight keys are controlled by?
Klara Kaiser said:
Please remember, I'd like to extend the button backlight time
Click to expand...
Click to collapse
There isn't a file. He said "he cant remember" because he is lying
The backlight controls are driven by two files in /sys/class/leds/button-backlight. Files in the /sys folder are pseudo files created at runtime from the kernal. You would need to mod the kernal to permanently turn the lights off.
I'm running the Oreo beta with just Magisk 4.13 installed. No TWRP or any other mods, even running the stock camera.
So in the gboard options under virtual keyboards I have the Voice Input Key enabled and Google Voice Typing enabled but the damn button isn't anywhere to be found on the keyboard.
I tried enabling the Japanese input and then holding the space key to choose a 2nd inpute option but Google voice typing isn't even on the list there. Anyone have an idea what's going on here?
bavarianblessed said:
I'm running the Oreo beta with just Magisk 4.13 installed. No TWRP or any other mods, even running the stock camera.
So in the gboard options under virtual keyboards I have the Voice Input Key enabled and Google Voice Typing enabled but the damn button isn't anywhere to be found on the keyboard.
I tried enabling the Japanese input and then holding the space key to choose a 2nd inpute option but Google voice typing isn't even on the list there. Anyone have an idea what's going on here?
Click to expand...
Click to collapse
It shows up in the suggestion bar for me. I am on Oreo beta 1 and not rooted. Note the yellow arrow on the attachment.
nrage23 said:
It shows up in the suggestion bar for me. I am on Oreo beta 1 and not rooted. Note the yellow arrow on the attachment.
Click to expand...
Click to collapse
Yep, the bar I have disabled
I hate all assisted typing features, turn them off first thing out of the box. Guess I'll find a different keyboard to use.
Thanks nrage