yashsingh1/xdaforums huggingface dataset:
[Nexus S General] onthecouchagain:
Okay, folks, my video is finally uploaded

:

[YOUTUBE]RUZdvr6Pdjk[/YOUTUBE]

As you can see, I can even tell when the glitch will happen depending on if the underline disappears or not whilst typing. When it does disappear, no matter what you press (be it letter or the space bar) it duplicates the first letter. As Ryandi predicted earlier, I think it has something specifically to do with a glitch with the space bar.

The reason I don't think it has to do with typing speeds or the sensitivity of the Nexus S screen is firstly, I'm demonstrating the glitch very slowly. I even pause to talk about it before the moment I demo the problem. Secondly, I don't believe it has to do with the screen sensitivity for two reasons: 1) I cannot recreate this problem on Smart Keyboard Pro, try as I may; and 2) it only happens with the first letter or the last letter of words, not coincidentally prior to or after using the space bar. It never double hits the letters in between words. For example, I never get "thhis" or "thiis," I only ever get "tthis" or "thiss".

The core issue is with the Android keyboard itself, and more specifically, has something to do with the space bar.

I've reported this to Google here http://code.google.com/p/android/issues/detail?id=14755 and here at the Google Help Forum: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4d8d957040f12326&hl=en. If you people would be kind enough to visit the links and star the report or even add your own two cents, especially if you're experiencing this glitch yourself, that would be fantastic.

Thanks for watching.

EDIT: For those who can't recreate it, that's interesting. Are you sure you're following the procedure? Type the first word, then the first letter of the second word, then backspace/erase that first letter AND THE SPACE (from the space bar press after the first word), then hit space again and finish the second word (or as demoed in the video, you don't even need to actually finish the second word). Also keep an eye out for the underline; if the underline disappears, the glitch is about to happen. It doesn't always happen, I agree, and it pops up randomly (imagine finishing an email or a text and seeing the message littered with these randomly double-lettered words). I've had people (here and at other forums) report that they get this too; some even report that they get two double-letter hits, for example like "ththis". I've seen this too, sadly. Given that this is more software related, I'm quite certain all of us should be able to recreate this glitch. If truly not, then I suppose it could be exclusive to a few phones--but that doesn't seem to make sense unless we got different software versions of the keyboard? I don't know. In either case, the issue is very real for some. I hope you'll all star my report in the link above. Thanks again.
[Nexus S General] ryandi7:
I couldn't replicate this since I wasn't fluent with my Wildfire's screen size to begin with. But instead, I tried typing good game repeatedly very quickly and I saw a lot of "ggood" but no "ggame". This might have to do with how we thumbtype differently, but the issue is definitely there.

Oh and wow looking at your video, it seems that you finally got to the root of the problem, now we'll just have to wait until Google finally acknowledges the issue.

Edit: I found out how to always get the first letter to not be underlined.

Apparently if the Space is still being pressed while keying the next letter, the next letter will almost always not have an underline.

This explains how the multitouch and space are not behaving as they should and why it affects more people who type fast as opposed to everyone (people who type fast tend to trigger more multitouch presses). I can always reproduce this with my Wildfire, but since it's a different phone YMMV.
[Nexus S General] onthecouchagain:
It was your suggestion that steered me to discover how to recreate the glitch, so kudos to you.

EDIT: Holy moly, you're right. I can recreate the glitch that starts the glitch. ... incredible. Ryandi, hope you'll add your new discovery to the Google Help Forum link and report link above.

Or better yet, here: I've reported this to Google here http://code.google.com/p/android/issues/detail?id=14755 and here at the Google Help Forum: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4d8d957040f12326&hl=en.
[Nexus S General] ryandi7:
I've edited my previous post with another interesting find, try to see if you can replicate it.

And I'm also seeing a lot of "ththis" in addition to just "tthis" like you mentioned above. This keyboard is weird for sure.
[Nexus S General] onthecouchagain:
Yes. I saw the edit, and edited my response as well. Take a look. Great new discovery. I've also witnessed the "ththis" phenomenon, even with the end of words, like "thisis". Wonky.
[Nexus S General] ryandi7:
I'm also starting to think that this might have to do with word-prediction as well, since underline is exclusive when word-prediction is turned on right? Would you try reproducing the issue with word-prediction turned off?
[Nexus S General] onthecouchagain:
Yes. Can still recreate with Suggestions turned off. The underline still exists with Suggestions off.
[Nexus S General] dinan:
Ok, after watching the video, I can replicate it on my phone as well. It only happens after I press a space and then the next letter really fast. If I type Hello, then space, pause, then t for there, it won't do it, but if I type Hello, then space and t very quickly, it'll do it.

I always hated the space bar with the keyboard and I thought it was due to it being so small but I guess it's also because of this glitch. Another reason I use swype =\
[Nexus S General] onthecouchagain:
Thank you for watching and trying. Please star the report here: http://code.google.com/p/android/issues/detail?id=14755 and here if you'd like, add your two cents at the Google Help Forum here: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4d8d957040f12326&hl=en.
[Nexus S General] ryandi7:
When you type quickly, you tend to press t before lifting your thumb off Space, that's the reason it happens
[Nexus S General] dinan:
I thought this was the reason too, so I tried it typing with only 1 finger so I was pressing space with my thumb and then pressing T as quickly as I could and it still produced the glitch... my thumb was definitely off the screen between the space and T, I didn't 'drag' my thumb across to the T.
[Nexus S General] ryandi7:
Hmm interesting. Then could it be a small timeout frame after pressing space? I'm really not sure.
[Nexus S General] onthecouchagain:
Android 2.3 keyboard glitch: please star report

[youtube]RUZdvr6Pdjk[/youtube]

If you haven't seen it yet, with the help of XDA member Ryandi, I've discovered an odd glitch with the stock Android 2.3 Gingerbread keyboard, as demonstrated in the video. The keyboard sometimes generates two letters of the first letter of words (for "eexample"). We believe it has something to do with the space bar.

The video was made by me to demonstrate how to actually recreate the issue. But this issue does occur while in normal typing, and as you can imagine, can be very frustrating. It's been corroborated by many members here and at other forums. The problem is real. Edit: Also, watch the suggestion bar. Clearly I've only hit the letter once in the suggestion bar. The suggestion bar shows "th" but the written area shows "tth"; likewise, the second example the suggestion bar shows "fq" and the written shows "ffq".

To recreate it yourself, follow these steps, as observed in the video:

Try to type two words. In the video, I use "Hello there" as an example. Before you begin typing the next word, try to hit the space bar and the first letter of the next word in rapid succession. You'll notice that sometimes the underline disappears (refer to the video); when that happens, as you continue typing the second word, the glitch will happen, and you'll get a double register of that first letter. In other words, it should result in "Hello tthere" (if you finish typing. As demoed in the video, you don't even need to actually finish typing the second word when the glitch happens.)

(If you want to read more extensively about this, it's being discussed on this thread more in depth: http://xdaforums.com/showthread.php?t=932838&page=13)

Anyway, the important thing, and the reason why I created a new thread about this, is that I've filed a report to Google at their code site:

http://code.google.com/p/android/issues/detail?id=14755

and at their Help Forum:

http://www.google.com/support/forum/p/Google+Mobile/thread?tid=4d8d957040f12326&hl=en

Please visit the links and star the report, and if you'd like, add your two cents, especially if you're also experiencing this bug. Since I believe it's a software related bug, it should be universal on all our Nexus S' (unless of course, it's possible we have different software versions of the keyboard on our phones).

Thanks.
[Nexus S General] DumbUglyDragon:
I've been following your thread for sometime and I'm glad you've finally posted a video. I would've liked to have tested it on my Nexus S, but I returned it due to the different bugs I was having -keyboard not being one I remember lol.

But anyways, I tested it on a few other devices to try and get you some data.

I could not replicate the problem on my Nexus One using CM7 and the GB keyboard.

However, after trying for a good 20 minutes on my Viewsonic gTablet running the GB keyboard with the VegaN ROM, I was able to get the first letter to show up without the underline. The way I got it to do so was holding down the space while pressing the next key (ie pressing space and "g" at the same time). Here's the strange part - after a few letters, even without the underline, the autotext would start to populate words anyhow. I could not replicate the duplicate letter generation.

I'm thinking its not hitting my Nexus One because the multitouch on it is wonky.

One theory on the no underline issue - maybe the hover sensitivity of the Nexus S isn't registering the release of the space as fast as you type? I don't know - how slowly can you replicate the problem? Try a slow 1 finger type. As far as the double letter I'm a bit baffled... How sure/unsure are we that this is affected other devices the same way?
[Nexus S General] AllGamer:
hmm... i actually like it as it is

i think the problem is the fast repeat rate

it's more like a feature request, to allow the change of repeat rate speed

the SAMOLED screen is hyper sensitive, you don't even need to make contact with the screen, and it can already register your touch to the button/icons/inertia scrolls

i love it!

that's why i don't like devices with SLCD screens, they are not as responsive
[Nexus S General] jaker.the.skater:
I starred the link so that this will hopefully be fixed for you guys with the issues, but I have to say, I don't have this issue. I tried several times to recreate it with the examples you gave but it just wouldn't happen.
[Nexus S General] onthecouchagain:
Did you watch the video? The glitch demonstrated in the video has little or nothing to do with the over sensitivity of the screen. I say this for two reasons. 1) I cannot recreate the glitch with Smart Keyboard Pro. I've tried many times. And 2) it explains why it only ever happens to first letters of words. It's not a coincidence those letters are pressed after a space bar hit. You never get the words in between double repeating. For example, you never get "thhis" or "thiis," you only ever get "tthis".

Edit: Also, watch the suggestion bar. Clearly I've only hit the letter once in the suggestion bar. The suggestion bar shows "th" but the written area shows "tth."

However, I don't discount that the over sensitive screen aggregates the problem. But the glitch is real and it has a lot, if not everything, to do with the keyboard software.

Yeah, some people can't recreate it, and others can. I'm not sure why. If it has to do with the software, as I predict, then everyone should be able to recreate it, unless there are different software versions of the keyboard floating in our Nexus S'. I don't know. But thank you for starring the report nonetheless.
[Nexus S General] onthecouchagain:
Thanks for investigating. I've found threads in Droid Incredible forums that show the same problem. I didn't inquire, but I don't believe they were running any sort of Gingerbread keyboard, but they could've been. I don't know.

And yes, that's how Ryandi discovered you can recreate the missing underline; the closer in time you type the next letter after the space, the more likely it'll generate the "no-line" letter, resulting in the glitch.

I don't know how deep this goes, but I believe it is software related. And if so, should be able to be recreated on any Nexus S (and I suppose, in theory, any Gingerbread keyboard ROM--not sure). I do agree multitouch has something to do with it all too.
[Nexus S General] AllGamer:
yes, i did watch the video, and it doesn't happen in my SNS, i type fast using dual thumbs, and i don't need to correct the words i type

except for times when the phone lags, and you typed like a whole line of things, and it missed to pick up some of the letter i typed too fast

however i disable auto space, auto change, auto capital, auto completion, auto etc

i do have enable prediction, but i don't really use it, as i just look at it for reference for times when i doubt the spelling of some words

maybe that's what's causing those duplicates?
[Nexus S General] DumbUglyDragon:
Speak of the devil.... was just replying to a text on my Nexus One, and low and be hold i some how got a "bback" instead of a "back" :lol: I guess its software! :p
[Nexus S General] onthecouchagain:
Maybe.

For what it's worth, here are my settings:

Vibrate: unchecked

Sound: unchecked

Pop up: checked

Touch to Correct: checked

Auto Cap: checked

Show settings key: Always hide

Voice input: disabled

Input Languages: "English (United States)" selected

Quick Fixes: check

Show suggestions: check

Auto-Complete: check

I've recreated the glitch even with "Show Suggestions" turned off.
[Nexus S General] onthecouchagain:
Thank you. I hope you'll star my report to Google (found here for your convenience so you don't have to backtrack pages: http://code.google.com/p/android/issues/detail?id=14755). Please share add your experience too in a reply if you'd like.

As I've said, I assure everyone, this is not a conspiracy. Sadly, this glitch is quite real.
[Nexus S General] Xandlinger:
I followed your instructions to the letter and cannot reproduce this bug.

Now about the holding down the space bar thing, I CAN reproduce that, BUT it doesn't cause ANY errors whatsoever. The underline WILL be gone, but once I actually finish and get to about G-A-M, the underline REAPPEARS and suggests game.

Edit: I was pausing so I tried to recreate it by typing both ways quickly, but still cannot reproduce it. This is interesting.

EDIT EDIT: I just encountered the issue! I CANNOT reproduce this with the stock keyboard that came with my Nexus S. However, I CAN reproduce this error with the modified apk that was posted in the general forums a little bit ago. I have also got "Good gagame" as well.

Edit edit edit: After switching back to the Android Stock Keyboard... I can now recreate the issue. Well this is disappointing. Getting both "Good ggame" and "Good gagame."
[Nexus S General] irishrally:
I reproduced: good ggame but only after I typed it very quickly.
[Nexus S General] gogol:
I star it because I think this is a bug even though I cannot reproduce it here.
[GT540 Optimus Themes and Apps] EoinSheehy:
Ok has anyone managed to (successfully) change their battery icon on 2.2.1. I've tried various times but it always ends in boot loops or no battery indicator at all. They've mostly come from the UOT Kitchen, but I've no idea how to properly 'install' them as such.

Any ideas?
[GT540 Optimus Themes and Apps] joostvhoek:
There is an app for sgs to change battery icon. Maybe that app can help you.

Joost
[GT540 Optimus Themes and Apps] EoinSheehy:
Thanks, I'll give it a try once I get to a computer, just one question, the stock battery icon goes down in 10%, would it make a difference if I then added a battery icon that moves in 1%?
[GT540 Optimus Themes and Apps] EoinSheehy:
Also that link doesn't seem to work for me. This is what I get:
[GT540 Optimus Themes and Apps] keewanchoapsss:
Well it would probably make the battery icon flash when on screen. But what you can do is, say the battery icon is meant for 1% accuracy then you can use the more accurate icons and place them on the 10% blocks so you can see where your battery is more clearly. Does that make sense?
[G1 General] mackdaddy187:
Hey guys I just got a G1 for real cheap and fund out its back button does not work. I opened the phone up and the metal contact the button clicks on is broken.

Is there any way I can assign the back button to some other button? I will probably do it to the click wheel since I don't plan to use it for navigation.

Thanks

Edit: is there a way to remap the trackball as the back key?
[G1 General] RichieDaze:
Try this thread [MOD] Remap Any Key on Your G1 (v3, Now can play/pause/skip Music with Camera Key)
[G1 General] dhkr234:
The next step after finding the cause of the problem, is REPAIRING it. You know how a button works? There are two contacts on it, when the button is UP, the contacts are disconnected from each other, when the button is DOWN the contacts are CONNECTED to each other. You just need to rig something up to connect/disconnect the two contacts.
[Continuum Android Development] trailblazer101:
If any dev manages to stumble across this, may you please help me get back up to Baseband DJ20 or DL17? Currently i am at DL09... If there is a update patch from DL09 to one of those, that would be perfect :D

Thank you in advance! :D
[XPERIA X1 Q&A, Help & Troubleshooting] tmp005:
Hello everyone :-)

1. I am interested in keys remapping and changing some defaults in the 826x but don't know to grab it. Always what I wanted was to wipe out Windows Default Dialer/Phone software and exchange it to the Resco Contact Manager. I don't mean to change "Green Phone Button" but to make dialer (keypad) from this software as default in whole "system". After I had remapped (using AEB Plus) Green key to for example to "Favorites" from Resco CM software, I overridden default (important) action of this key as well - accepting connections. My key was calling Favorites from Resco CM but wasn't accepting connections. Is there any possibility to merge this two interactions into one button? Would be greater to set green button default to "Keypad" panel from this Resco CM.

2. After I have remapped some keys using AEB Plus I've lost this sweet Resco Task Manager (is this correct name?) from 826x ROM. I've tried to restore it by mapping it to the XPanel button, but don't know what to set exactly under this button - which executable? I've tried to use app called uTask Configurator but don't know how to use it correctly :(

3. What may be the reason of fact that I am not able to Map the keys in mine PocketMusic player? In stock rom I mapped my keys for usage in music player, but now when I try to do it - app (PocketMusic) does not recognizes pressed keys? No info about pressed key is showed.

4. How to set "turning screen off during call" or "blocking phone during call" in the quickest way? I need to set something like that, but don't want to use third party apps like S2U2? Maybe there is any REGISTRY method?

Thanks in advance for any replies.
[Nook Color Android Development] killahrey:
Hey guys, Im not usually one to start threads but I havent seen one of these here for the NC,

What I got here is a system img of a Honeycomb sdk dump.

Gotta give thanks were its due, so thank Peter Alfonso, you might know him form his Bugless Beast roms.

Hope a great dev (maybe samuel...) could have a look see what they might be able to do with this.

Hopefully we could have Honeycomb running on the Nook Color soon!

DOWNLOAD HERE

Good luck!
[Nook Color Android Development] cainhunpi:
Om not evev going to touch it. Because I know it will run unusuably slow. Just wait for the source code

Nook Color via Xda App
[Nook Color Android Development] philburkhardt:
This isn't an image of Honeycomb that's meant to run on your device. It's an SDK dump for devs to toy with.

Edit: I just read that someone has an early build working. Buggy, but working. Man, these devs work fast!
[HD2 General] ashwanimishra:
Hello,

My HD2 was working fine till yesterday, suddenly since today phone started freezing intermittently.

Now after hard reset with factory Rom, my phone is not even searching for any mobile network and doesnt lets me activate phone mode under settings tab.

Time to Time i also keep on receiving Credential.exe crashing msg.

Kindly help! i am unable to use the phone now.
[HD2 General] htcphonelover:
I have the same problem. You may follow this post to see any expert can solve this matter. Hopefully with their experience, we can get our phone back to work.

http://xdaforums.com/showthread.php?p=11008994#
[Droid Incredible General] userjf:
Regarding the Incredible Radio Firmware 2.15, has anyone used all of these enough to know if the 11.19 really is the best as compared to 9.01 and 7.28?

There are so many conflicting reports, I would like to know if there have been any reliable results determined by someone who really knows how to compare them.

Thanks.
[Droid Incredible General] farkmeil:
I would also like some info on this. Anyone knowledgable in this area?
[Droid Incredible General] Smokeey:
I don't know the first thing about radios....please enlighten us.
[Droid Incredible General] cuban11182:
I tried all three with the phone in the same location. I did two tests with speed test and i watched the signal in dbs. I determined that based on my location (Tampa) the 7.28 worked the best in my location. Just my $0.02.
[Droid Incredible General] smtom:
Check out the Radio Threads

FWIW, there are at lease two very good threads devoted to radios.

Many opinions and much anecdotal evidence is found in them - they are worth a studious look.

Read the entire threads.

Why? experiences by radio vary widely based on geography, ROM, PRL, and a host of other things.
[Droid Incredible General] POQbum:
I'd say bottom line, there is not a noticeable difference to even bother thinking about it.

Spend hours reading through, I've read a lot (entire threads) and tried them. Some people say GPS finds quicker, some say slower, some say better signal, worse, faster, same, blah blah

You'll hear so much if you read everything, but there is not a significant number going in one direction.

The 7.28 does just dandy.
[Droid Incredible General] userjf:
Exactly, all those conflicting words to describe the exact same firmware on the exact same hardware, and often the same ROM. Flashing radio firmware is probably the riskiest thing you can do to the Inc. A corrupt ROM without a backup, you loose your apps and contacts. Too bad. A corrupt or mistake with firmware, and the phone will never ever power on again. Period.

Scary stuff.
[Droid Incredible General] dpwhitty11:
In my area, 11.19 is the best.

It really just depends.

Just try them all out for a few days each and see which one you like best.
[Droid Incredible General] titans808:
In my area 7.28 works the best. I had incredibly slow 3g with the other radios. Just install one and experiment with it people get mixed results
[Droid Incredible General] csseale:
Results may vary........
[Droid Incredible General] gtdrew:
Been running 7.28. Haven't felt the need to risk changing it especially with all the conflicting advice.
[Droid Incredible General] najaboy:
There are so many conflicting reports because there is no hard and fast answer to a question such as the one you posted. The same baseband version is going to give dramatically different performance on to pieces of identical hardware due to external variables. When it comes to radio performance, relying on the anecdotes of others wouldn't be the smartest thing to do and a waste of time.

Try each version for yourself and see what works best in your particular circumstance.