text box focuses at start when editing? :/

dan55 · February 5th, 2012, 08:58 AM

hi guys,

this seems to be a common thing now on all current gb roms, but im sure it didnt used to work this way :/

when editing any text box that already has some text in it, the cursor goes to the front of the field rather than after the existing text as i would expect.

am i confused in thinking that it used to work differently? :/
or is there a way to change this behaviour?

cheers
dan

SUroot · February 5th, 2012, 08:59 AM

I cant remember if it worked differently as ive been on gb for a long time, but I confirm the issue and that it is VERY annoying.

dan55 · February 5th, 2012, 09:04 AM

phew! thought I was losing it there :-D
....any chance of a hack? ;-)

SUroot · February 5th, 2012, 09:07 AM

Maybe but I myself have no idea what bit of code controls that

dan55 · February 5th, 2012, 09:12 AM

oh ok no worries

im guessing the google coders forgot to add the bit where it checks for textbox contents when setting focus

cheers

SUroot · February 5th, 2012, 09:28 AM

Maybe. I just dont know where to look. dGB is 45,616,039 lines of code

dan55 · February 5th, 2012, 09:30 AM

F' me! thats a lotta lines

btw: on a general rom type note: any ideas what might cause apps to fail/close, but not show FC error? can be any app at any point

sorry a bit vague i know :/

....oh, dont worry, its not dGB

cheers

SUroot · February 5th, 2012, 09:33 AM

ummm. Not really. Tried running "dmesg" from terminal after a suspected FC?

dan55 · February 5th, 2012, 09:35 AM

ok thanks - does that do similar to alogcat?

SUroot · February 5th, 2012, 09:38 AM

Not exactly. Its more kernel and driver related but may point out some errors.

dmesg - Wikipedia, the free encyclopedia

dan55 · February 5th, 2012, 09:44 AM

ah ok cool - thanks
btw: is any terminal app better than another to do this ? ta

SUroot · February 5th, 2012, 09:46 AM

dunno. I just always have used jackpal

https://market.android.com/details?id=jackpal.androidterm&feature=search_resu lt#?t=W251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0i XQ..

dan55 · February 5th, 2012, 09:47 AM

kool ta

dan55 · February 5th, 2012, 09:50 AM

theres a lot of Sony mentioned in it :/

SUroot · February 5th, 2012, 09:51 AM

Slcd?

dan55 · February 5th, 2012, 09:54 AM

:/
sony_tft lines - sony make the screen? :/

SUroot · February 5th, 2012, 09:56 AM

only the slcd ones. Its nothing to worry about anyway.

dan55 · February 5th, 2012, 10:03 AM

ah right - sorry - type of screen - i get you - a bit slow there!

dan55 · February 6th, 2012, 01:53 AM

hi Dan.
had a few odd closes just now. ran dmesg but not too
sure what I'm looking for. I did see this at the end of log
though. cheers

g), 29.3 C, 1225 mAh
<6>[ 1546.674957] binder: 181:187 transaction failed 29189, size 56-0
<6>[ 154

SUroot · February 6th, 2012, 01:59 AM

I dont think dmesg is going to give us any clues in this case. It was a longshot. May have to run a logcat constantly

dan55 · February 6th, 2012, 02:02 AM

:-) ok no worries. ta

I thought I could just run alog after the event to get logs?

SUroot · February 6th, 2012, 02:07 AM

Theres no reverse logcat, no. dmesg goes backwards but it doesnt capture everything a logcat does,

dan55 · February 6th, 2012, 02:18 AM

ah ok thanks.

so when devs say open alog and get logs after event. that isn't going to work :-\

SUroot · February 6th, 2012, 04:16 AM

not with a logcat, no. Logcat records from the instant of creation until you stop it.

dan55 · February 6th, 2012, 04:18 AM

ah ok thanks.
maybe comms issue between me and dev :-D
cheers

Football Fans: Download the 2012 Schedule App from Google Play!