Hi all.
Suddenly, the "Space Key" does not appear in Full Qwerty Keyboard.
Now ".com" & "/" appear instead of "Space Key".
(plz see the attached file)
I want to change from ".com" & "/" to "Space Key",, how ever i don't know the way.
Could u give the solution?
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Thank you very much for your solution!
My "CurrentET9Style" is 6.
After revise from 6 to 0, Back to normal keyboard.
Thank you !!!
mjcole2003 said:
i had exact same problem. apparently you have to do a registry change to fix it. HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
Your variable might not be 1 but when my screen was as yours it was a 2. Laater it switched on its own to a 9 so dont lose this registry change because your probably going to have to do it again. I noticed when i added new contact or something to that effect it changed the variable
Click to expand...
Click to collapse
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
thanks ,i think i get it.
supdawg said:
Did you install the tweak cab from ppgeeks? if so, that is your issue. It was in the 1st post
Click to expand...
Click to collapse
who's first post? I did install the tweak cab from ppcgeeks and would like to read that 1st post. If i uninstall the tweak will it fix the reacurring problem or do i have to hard reset? Thanks
when i changed to "autocomplete" I had the same problem with the space key being gone until i put the registry back the way it was...Tj
Keep CurrentET9Style = 0 ??
Changed HKLM\Software\Tegic\eT9\Ime.change CurrentET9Style from 1 back to 0
This works temporarily, but when I click on the time in a calendar entry, it switches to numbers, and does not switch back unless I re-edit the registry. Is there any way to keep the setting from changing at all? I want it to stay at CurrentET9Style = 0.
Anybody?
Hi everyone. Okay, first let me just say that the "FixStuckTP2Keyboard.cab" is fine and it does work. But it reverts your keyboard back to the "eT9" and you probably did a registry hack to change it from that in the first place (changed it to "COMP") am I right? Not to knock that cab, like I said it works just fine but I did NOT want to "install" a cab file everytime this happened (after it would change it back to "eT9" I would have to go back into the registry and change it to "COMP" again.)
Let me tell you HOW this is happening in the first place, it has something to do with Opera. You can test this very easily. First get your keyboard working properly, then open Opera. Type something in the address bar or just tap the address bar and BAM! Your keyboard is stuck in that mode. Now I don't know why this happens, that mode is getting stuck in memory for some strange reason and it will NOT let go.
I'm assuming this is ONLY happening to those of us who have used the registry (or a program or cab) to change the keyboard to "COMP" instead of "eT9" since changing it back to "eT9" solves the problem.
There are three solutions:
1.) ONLY use the slide-out keyboard when using Opera.
2.) Use the FixStuckTP2Keyboard.cab
3.) Use the MortScripts I created.
Use "KB-OFF (eT9).mscr" to force the "eT9" info into the registry. Then use "KB-ON (COMP).mscr" to enter the "COMP" info back into the registry, then do a soft reset.
You can rename these files if you like.
Yeah I know it sucks to have to do a reset just to get the use of your spacebar back just because you used the virtual keyboard when using Opera but hey, what are you gonna do?
UPDATE: Just noticed that "sometimes" my scripts don't work if you click on them one after another (again for some strange reason). If this happens to you just click on "KB-OFF" soft reboot then click on KB-ON" & reboot. Weird I know.
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
xlJohnnyIcelx said:
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
Click to expand...
Click to collapse
How about you try to flash back to the stock rom using the lg flash tool?
I fixed it with a work around. I used exposed additions to force haptic feedback and also to map the q button key. Hopefully if anyone else has this problem it will help them.
Recently some users including me are having issues with BT Connection, device search, setting device name and making changes persistent.
BT MODULES THAT IT WAS TEST ON:
SD-968 - [HA] [MCU MTCE 2.75] Firmware 20180201 and few earlier = WORKS
MD725 - [??] [MCU ???] Oreo Firmware = DO NOT WORK (According to feedback) LogCat needed to see if Firmware communicate with BT Module at all.
METHOD 1 (SHORTER):
1. Force Stop BT app
2. Clear DATA and CACHE for BT app
METHOD 2 (LONGER):
Here are the steps I've done to make it work.
1. Boot device (restart if it was not in deep sleep)
2. Directly go to system BT settings (drop notification and tap on BT)
3. Set Device name and PIN
4. Press refresh
5. Go to Home Screen (Home Button)
6. Open BT App -> Configuration
7. Name and PIN should be entered now
8. Disable/enable Auto Connect and exit app
9. reenter app and configuration to enable Auto connect
10. Make sure that all previous BT profiles for HU are deleted on phone and that phone is visible for all devices (usually when BT configuration is open device is visible)
11. Try to search for devices. It should fail (it failed for me)
12. Go to factory settings
13. Change BT Device even it is wrong one (I have SD-968 I changed to MD725)
14. Tap Apply -> Exit -> CANCEL on reboot prompt (without doing step 13 there will be no scheduled restart)
15. Reenter Factory settings and set correct BT Module (I have SET SD-968) Tap Apply -> Exit -> and Confirm REBOOT
16. After Reboot Go to BT App and try to search for phone it should be found (make sure it is visible like in step 10)
17. If all is OK you should see the phone and you should be able to use it normally (it worked for me)
Attached pictures of some steps for METHOD 2.
NOTE: I'm ATM at HA 6.0.1 Firmware from 20180201 and issue happened after upgrade. Also from what I see Users have same issue with and after Oreo update. Hope I helped
Thanks for the info. Have you tried this method also for oreo rom as well ?
A step that worked for me was to clear data and cache for bluetooth app..
julien_blanche said:
Thanks for the info. Have you tried this method also for oreo rom as well ?
Click to expand...
Click to collapse
Haven't updated to Oreo yet.
Phycopat said:
A step that worked for me was to clear data and cache for bluetooth app..
Click to expand...
Click to collapse
Good point it didn't worked for me but, it can also help. Added to main post.
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
I definitely have the BT issue. I have an Xtrons(GS) MTCD/E PX5 Oreo and an Xtrons brand OBDII. They won't talk or disconnect. I'll try this tomorrow morn and report back.
Click to expand...
Click to collapse
I have same GS MTCE 2.75 PX5 OREO but an old OBD2, give HU same password as OBD2 adapter..
jdisco1 said:
You can trigger a reboot with "hctreboot" in factory settings. Does that work instead of doing steps 12-15?
Click to expand...
Click to collapse
Point of 12-15 is that HU re init Module itself along with software. Not sure if it works that way on MTCD/E but usually it works on modular systems.
Tried with PX5 oreo installed with no luck. Both methods are not working for me.
PekeMM said:
Haven't updated to Oreo yet.
Click to expand...
Click to collapse
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
I'm sorry, but as I wrote I have SD-968 BT module not MD725. I'll update main thread with so far know to work devices.
Any news?
JonatanP said:
Any news?
Click to expand...
Click to collapse
Not that I know, I'll be back from Trip on Sunday, so I hope I'll finally finish the tests and upgrade to Oreo in April.
seems to be the same
The solution is to go back to android 6, the problem is that it is not as fluid in my case as android 8.
Hi, same problem here....
I can not use my ODB2 connector on my Android 8 radio either.
Is there an adapter that works?
Is there a trick to make it work?
Greetings and thank you!!
Hi..any update on how to get the bluetooth working on android 8..
Mtcd ksp px5
warata said:
What???(I thought that this was a trick for oreo)
In my unit BT(MD725) works without any tricks for MM.
I tried your trick with 2 kinds of oreoROM(HA and GS) but BT did not work.
Thanks anyway
Click to expand...
Click to collapse
if you still have android 8 installed, try going to factory setting and change the BT Device even it is wrong one (anything other then MD725) tap apply and exit and reboot.
after reboot change the BT device back to the original one (MD725) tap apply and exit and reboot.
after reboot go to the system BT and try to search if the phone name appears let me know.
i still didn't try the above method on android 8, but if anyone with MD725 module is still using android 8 please try and update us.
thanks
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
macoloco said:
i was having problem with bt too...
here you can read my post https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
now i have Oreo Rom in a px5 board (32+4) with MD725 BT module working well
Click to expand...
Click to collapse
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
bjt2 said:
Thanks, you said in that thread ".i have found a directory where all manufactures update.zip where listed
Go there , pickup last LM version" could you say where this directory is? Once there what do you do with that file?
Click to expand...
Click to collapse
i wrote all my procedure here
https://forum.xda-developers.com/showpost.php?p=77525417&postcount=791
and here
https://forum.xda-developers.com/showpost.php?p=77538182&postcount=796
Dasaita MMCNP - BT connection problem
Hi, I have Dasaita HA2106-V840-8 a problem with Bluetooth connectivity. First time I managed to connect my phone to Dasaita MMCP (car_kit), but after a few days the devices failed to connect. I guess my device has embedded SD968 BT chip, in accordance with the description.
When I enter the name of the device and new PIN in BT settings, and then turn on finding the device, they are not visible to each other. I tried this other day too, but when I turned MMCP, entered settings was gone (not memorized). No name, no PIN, but also there is no connection. Search doesn't have results. At the end I tried to unpair devices and pair them again, but I get a message on my phone "Unable to communicate with CAR_KIT".
When I entered in settings for BT (settings/car/factory setting/application-choose...) it was set to WQ_BC6. And then I tried to set up SD_BC6, reboot, search BT, nothing was found again. Then I returned to WQ_BC6, reboot, search BT, without success. In the end, I tried to set up SD968, but it's not worth it anyway, MMCP does not see a mobile phone. I also tried several phone models without success. I also went to the BT application and clear data and cache, but always the same thing - BT devices do not see each other. I'm not even sure BT is ON because it doesn't have a special slider to move On/Off.
What should I do? Please help me!
Hello all,
After finally updating my PX5 to the latest MCU and firmware (according to Hall9k) using his mod application, I am now experiencing low volume on everything (radio on max is pretty low volume when you're on the highway) and bluetooth settings always reset to empty settings and will not find my phone and my phone will not find the PX5.
I've tried resetting wifi and bluetooth settings, no luck. I've tried resetting the unit back to factory settings, erasing all data, no luck. I found a post regarding the bt issue and followed all his steps (changing the bt device and reverting back to it, etc.) but no luck. I found a post which said the device somehow needed to be an other one than previously set, so I've tried all the devices in the list, but no luck. Only at the parrot device, the bt settings were automatically reverted back to factory default (Car... something), but it wouldn't connect. Normally my device was on SD-968 I believe (not currently in my car).
So, that's my main issue now. How can I get BT to connect, without rolling back to Android 6.0.1? Because on 6 it worked.
And second, how can I get the volume louder? Again, after updating the volume somehow seems limited.
I don't want to go back to 6, if there's an other way, because 6 had its own problems...
I'm really lost here and have spend many hours in the car, trying everything I could find online (even manually clearing cash and storage of the bt settings, etc). There must be a way this should be fixed.
My Android 9 fw is from November (Hal9k send that one to me)
My MCU is MTCE_GS_V3.17bd_3
I tried upgrading my MCU from MTCE_WWW_v2.85d_1 . Now, no matter what MCU I flash the Bluetooth never works. It doesn't find any available devices. Does anyone have a copy of this original MCU file? I believe my HU is the Eonon GA9165A
UPDATE: (FIXED) I figured out that I had to re-select the correct Bluetooth in "Factory Settings"
Now I want to know what is the most up to date MCU file I should be using for my HU?
I've tried a few that I thought were correct and some of them worked, while some of them messed the physical buttons.
Also, is there anything else I need to change in "Factory Settings?"
I noticed alotmany options in there but I don't know if any have been changed, besides BT.
I found that I had to change the Bluetooth in Factory Settings
fuih8u said:
I found that I had to change the Bluetooth in Factory Settings
Click to expand...
Click to collapse
Thats quite right