Closed GoogleCodeExporter closed 9 years ago
Is this consistent, or only after a fresh installation or upgrade? See
http://code.google.com/p/hackerskeyboard/wiki/FrequentlyAskedQuestions#It_doesn'
t_work_right_after_upgrading for a known issue, but I'm unsure if that's the
one you're seeing.
Any chance you could look at log messages, for example with aLogcat? See
http://code.google.com/p/hackerskeyboard/wiki/FrequentlyAskedQuestions#It_doesn'
t_work_right_after_upgrading for info about the debugging tools.
Original comment by Klaus.We...@gmail.com
on 21 Jun 2011 at 1:57
yes, I've upgraded the application while it was active, I somehow missed that
bit of the FAQ. How can I repair the installation? When the 1.20 patch was
released, I made sure to switch to the Multitouch keyboard before running the
update, but the problematic behavior is still occurring. I have not tried
removing the app and reinstalling it. Is that the right approach?
I can get you some logs if you like but, why would it only express this
behavior while in a particular app? seems odd to me.
thanks!
Original comment by kaishi.a...@gmail.com
on 21 Jun 2011 at 8:06
I still haven't figured out the correct repair method to fix this problem.
Should I remove the app and reinstall? or, would you prefer I produce some
logged output before I proceed? The behavior I described is extermely
frustrating.
Also, as I mentioned before, it only happens to me in AndChat. Googletalk,
gmail, terminal emulator, etc. never exhibit symptoms yet AndChat does. I can't
provide an explanation for that.
Original comment by kaishi.a...@gmail.com
on 27 Jun 2011 at 1:56
I've attempted to fix this issue several ways.
1) I selected a different keyboard, then disabled the app, then upgraded it.
No success.
2) I uninstalled the app entirely, removed the settings, and reinstalled it.
No success.
I would like to assist in fixing this issue so I will attempt to install a
logging app to collect data for a more detailed report. I would like to know
if there is anything else I should try.
Original comment by kaishi.a...@gmail.com
on 29 Jun 2011 at 2:38
I wiped and reloaded my entire device. The keyboard behavior is no better.
I'm confident that the issue is related to a different bug in either the
keyboard or AndChat. I'm not sure which.
I also installed aLogCat and didn't find any hits for the string that the FAQ
said I would see.
I'm also running 2.3.3 now, rather than 2.2.2
Original comment by kaishi.a...@gmail.com
on 4 Aug 2011 at 2:22
The known issue during updates normally fixed itself by restarting both the
keyboard application and the current input-using application, it definitely
shouldn't persist across system restarts or show up so persistently. However,
I'm not sure what exactly was going on to trigger it. It's possible that
AndChat triggers the same bug repeatedly, but I think it's more likely to be a
different issue.
Did aLogCat show any messages from PCKeyboard (Hacker's Keyboard generally logs
under that log tag) or LatinIME? Especially any information about exceptions
would be useful, including if you see any errors from AndChat.
Note that AndChat's Market description says: *** Having disappearing text
issues? So sorry to say I haven't been able to track down the cause of this :(
It occurs with some keyboards and not with others! A temporary solution is to
hide the keyboard which should show the text typed so far. Again, so sorry I
haven't been able to fix this :( ***
Original comment by Klaus.We...@gmail.com
on 4 Aug 2011 at 11:48
See also http://www.andchat.net/bugs/task/39
Let me know if you see any relevant-looking logs. According to that bug it also
affects other keyboards including the stock Gingerbread one.
Original comment by Klaus.We...@gmail.com
on 4 Aug 2011 at 11:51
I'll close this bug for now considering that it apparently also affects other
keyboards, and is mentioned in AndChat's Market description as a known bug.
Please reopen if you find any additional clues about what's going on that
indicate it's due to the keyboard doing something wrong.
Original comment by Klaus.We...@gmail.com
on 26 Sep 2011 at 10:21
Original issue reported on code.google.com by
kaishi.a...@gmail.com
on 20 Jun 2011 at 7:20