4.0.4/
Samsung Galaxy Note
still getting "Unfortunately Samsung Keyboard stopped responding " after 20-50 characters in a new note
like the new copy/paste functionality
Hi DominicM,
I've been unable to reproduce this problem. If you could install Catlog and then attempt to reproduce the problem, it would be really helpful if you could send us those logs.
already did in this thread , http://community.logos.com/forums/t/65995.aspx
but will redo when next adding note
Entering notes error free is fine now in 2.3.7 no lockups
EXCEPT when I try and make a correction.. delete key deletes selected then freezes the software, and I get the keyboard not responding message
My pen is out and I type/use keyboard using pen
this is same both in new note and edit note mode
My pen is out and I type/use keyboard using pen this is same both in new note and edit note mode
Is this the stock Galaxy Note 1 keyboard? And you are using the s-pen that comes with the device? And when you say 'make a correction' are you typing along and then press the backspace key, or do you tap around to reposition the cursor or make a selection and then backspace? (We haven't yet gotten our hands on a Note 1, so I'm wondering if there is something specific to a sequence of events on that setup.)
Thanks for continuing to help us work out these bugs!
2.3.7 seems much better than 2.3.6, but still get delete issue
Is this the stock Galaxy Note 1 keyboard?
Yes
And you are using the s-pen that comes with the device?
And when you say 'make a correction' are you typing along and then press the backspace key
Yes that deletes character and brings up message
or do you tap around to reposition the cursor
repositioning cursor and typing new text works fine
make a selection and then backspace?
yes selection or character deletes, but brings up the keyboard not responding message
(We haven't yet gotten our hands on a Note 1, so I'm wondering if there is something specific to a sequence of events on that setup.) Thanks for continuing to help us work out these bugs!
(We haven't yet gotten our hands on a Note 1, so I'm wondering if there is something specific to a sequence of events on that setup.)
Happy to help
Thanks for the additional info.
Would you be willing to try to do another catlog for us? The one you posted on the other thread strangely didn't have much info from our app in it.
Thank you!
the whole dump or just com.logos*
All of it, if possible. It often includes error messages generated from the system (not just com.logos*) that can be helpful. You can email it to us if you would rather not post it here
....
2112.2013-03-13-06-34-46.txt
this looks better added events into it
still getting issue in 2.3.8 build 77
Hi Dominic,
Thanks for waiting, we've been pulled away from this project for a few days, so we weren't able to investigate this in 2.3.8. Looking at your logcat, I'm very happy to tell you it caught the crash with the backspace, and it will be a big help understanding the problem. Thanks!
-- David
The crash seems to be occurring inside the Samsung keyboard itself, making this quite challenging. The backspace key works similarly to the numeric keys, unlike the letter keys. Do you have the same problem when you use a number key (1, 2, etc)?
having pressed every key on keyboard, only the delete causes this
given that the key press thread has a different id than the one killed in delete action, perhaps somehow the editor is suffering amnesia, as I say the delete is happening, but then the keyboard goes unresponsive, when keyboard fires up again more data can be input into same note.
Allen Browne also has the Note 1 and has generously spent some time helping with this issue here. Sounds like this is at least specific to Android 4.0.x version of the Galaxy Note 1, as he doesn't have problems with his on 4.1.2. That doesn't really help us find out why it's a problem on your device/4.0.4 though. Are you on a carrier that hasn't updated the Note to 4.1.x?
We've done some tweaking with the app and built a few versions for you to test. We don't have high hopes, but it will rule some things out from a technical perspective. Would you mind installing these and trying them? They can install right over your existing app. Note they are named the same, so if one does happen to work, try to keep track of which one it was
http://downloads.logos.com/Android/Logos/editortest1/Logos-79.apk
http://downloads.logos.com/Android/Logos/editortest2/Logos-79.apk
http://downloads.logos.com/Android/Logos/editortest3/Logos-79.apk
Thanks so much!
Allen Browne also has the Note 1...
In the other thread - http://community.logos.com/forums/t/66255.aspx - you asked if I had a carrier that had released Android 4.1.2, David.
The answer is Yes and No. I actually have 2 of these Galaxy Notes, and my wife uses the 2nd one we bought. Hers updated automatically through the carrier (Virgin Mobile, Australia). Mine didn't. In fact it had not received the previous update either (4.0.4), so it seemed to be stuck on 4.0.3. Waited 2-3 weeks. Called the carrier who couldn't help. So, I eventually downloaded the Samsung release of 4.1.2 and used Odin on the PC to update the phone. It is slighly different: I think it was Samsung's release for Hong Kong, so I ended up with an option for the Samsung Chinese IME keyboard also.
no update as yet on kies am o2 in UK.. not jailbreaking until out of warranty
#2/3 worse - text does not get deleted and warning still shows
#1 seems same as build 78
Ok: tested on the other Galaxy Note (the one that auto-updated itself to Jelly Bean), and same response: no problem erasing characters from rich text note in BIble app (2.3.9).
