Develop Bugs

Samsung keyboard auto correct broken.

So I noticed recently that the samsung keyboard auto correct no longer functions.
I noticed this on ICS and now JB.
Does anyone know why this happened? I have searched the net but no solid answers.
And please before you respond with telling me to try another keyboard like every other thread that I have found I do not care and I am in no way interested in any kbs but the samsung one.
I am trying to get a solid answer if this has affected everyone or just some. Did samsung change the kb or is this just a bug that affects all or maybe just some?
Please if you have good info post. This is driving me insane and I hope to find a resolution.
Sent from my SPH-L710 using xda app-developers app

No one is having this issue?
Sent from my SPH-L710 using xda app-developers app

I have forever. I'm one of the people who has made serval threads. You are forced to another keyboard. Samsung will help you in no way, they claim its a 3rd party app that they don't support when it's their own ****. Once I updated to li3 the Samsung keyboard along with the swype added in, are both broken and won't auto correct. It followed through to lj7 (jb). In the end I gave up because devs don't know any software tweak to fix it, Samsung support is worthless, their only excuse is it will be fixed in the next update from some reps, and yet wasn't.
In the end I was forced to use SwiftKey 3 =/ sorry to say it but go give the free version a try. There's no frustration due to no auto correct. It has 0 lag, 200% better than the Samsung keyboard, auto corrects much better, and ya. Try it out, if you hate it then un install, if you love it, thank me and buy the full version XD. I belive the free version is a 14 day trial

Yeah the stock keyboard sucks big time so I switched to Swiftkey 3 also.

I noticed the problem about the time that I upgraded to ICS as well and still having problems on JB so at this point it is a useless keyboard.
It is such a shame that it seems no one cares. I went and looked at a note 2 at BB today and it seems those as well are not auto correcting either. I wonder if they for some reason removed the feature when they added new options to the keyboard in ICS.
I wish we could just get a straight answer from someone even if it is just telling us they do not plan to bring it back.
I wish there was source available for the keyboard as we could fix it but it that is not going to happen. And I really don't enjoy using smali lol.
Sent from my SPH-L710 using xda app-developers app

Android 4.2 Issues on Galaxy Nexus

Hello Guys
Let's share the bugs that everyone experiencing with the new stock JOP40C Android 4.2 for Galaxy Nexus
I'll go first
I have a problem when in a call the phone keeps doing a weird vibration and once i done the call i find the phone on the homescreen and have to go to the notifications menu to hang up
the other issue is randomly force close for the launcher and some apps
the camera is very laggy when rotating from landscape to portrait
anybody experiencing those issues ?
Ok guys anybody experiencing random reboot on the stock android 4.2 Galaxy Nexus
You can star this for Google to fix : http://code.google.com/p/android/issues/detail?id=39912​

I am not. Also, and unrelated, I'd like to point out the redundancy of your title. Android 4.2 issues on, say android 4.0.4 would be revolutionary, but as you've directed this... Anyways, did you update ota, or flash the image manually? I've read of many issues from the image flashes prior to ota, that I haven't experienced at all since my ota on my drive home.

In stock browser in full screen mode i'm having a weird effect on loading bar on top, don't know if thats supposed to be like that or not.. just strange and sometimes the adress bar becomes bugged strange behavour

Yeah you might wanna reword that title...
Anyway, this update SUCKS!!!!!!! I was trying to be positive about it... Focusing on the cool new stuff... But then that shifted to at least neutral with the crappy changes.... But now this just sucks!!!!!!!!! I just got my first launcher FC EVER!!!! On my galaxy nexus.
No root, never flashed, been stock all the way on this phone just like any regular user. I used to root on my tmobile g2 but decided to keep my gnex all stock.
So what he hell!?!?! Force closing stock launcher!?!?!? Are you freaking kidding me?!? This update is turning into a total joke, its not funny google! Your pulling anAPPLE move on your most loyal customers(nexus customers!)
EDIT: this is a rant.. I was pissed at how badly 4.2 has screwed my phone up. But no i didnt mean the part about being as bad as apple..
I do think 4.2 sucks though. Especially compared to 4.1.2, in my experience they seemed to have sacrificed new features and "style" over stability with 4.2

roadrunnerx7 said:
Yeah you might wanna reword that title...
Anyway, this update SUCKS!!!!!!! I was trying to be positive about it... Focusing on the cool new stuff... But then that shifted to at least neutral with the crappy changes.... But now this just sucks!!!!!!!!! I just got my first launcher FC EVER!!!! On my galaxy nexus.
No root, never flashed, been stock all the way on this phone just like any regular user. I used to root on my tmobile g2 but decided to keep my gnex all stock.
So what he hell!?!?! Force closing stock launcher!?!?!? Are you freaking kidding me?!? This update is turning into a total joke, its not funny google! Your pulling anAPPLE move on your most loyal customers(nexus customers!)
Click to expand...
Click to collapse
Drama queen, much?
Sent from my Galaxy Nexus using xda premium

"the camera is very laggy when rotating from landscape to portrait" --> Yes, this is extremely annoying.
And also I find that when the camera shot in landscape mode, about 10% of the upper and lower part of the viewfinder are cropped (i.e. the things you actually shot are more than what you saw in the camera app)

1). I don't have problem with phone call
2). Yes, launcher FCed! But only happened once after first reboot after flashing factory image.

DirgeExtinction said:
Drama queen, much?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, just needed to rant
Plus the fc had just happened like 5min before i posted that. It was weird... I was browsing here on chrome, then pressed the home button and tried opening the launcher, and it got stuck loading for like 10sec... Then fc'd. Soo i tried again and it got stuck again and fc'd. Third time it finally worked.
I expect these things on rooted devices or custom launchers... But on stock its just sad, especially when it's never happened before the ota.

Mines running very stable.
Sent from my Galaxy Nexus using xda premium

https://code.google.com/p/android/issues/detail?id=39595&colspec=ID Type Status Owner Summary Stars
make sure you star this to take google's attention

Soldier 2.0 said:
Mines running very stable.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same I have no issues so far!

got no issues at all ! amazing battery enhancement for me ! from 2:3 hours of screen on time (from 100-10)to 3:2 hours of screen on time from (80-1%) charging to 100 and testing it out now ! m happy and the phone always sleeps even when the screen is on i found this part funny ! i still think its a bug !

SupaDupaFly24 said:
Same I have no issues so far!
Click to expand...
Click to collapse
I have no problems too, but i have an question, in camera setting the maximum picture size should be 5 MP ?
Sent from my Galaxy Nexus using xda app-developers app

yev.gavrikov said:
I have no problems too, but i have an question, in camera setting the maximum picture size should be 5 MP ?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yep

Flickering in Notification Bar
I have observed one strange thing on takju 4.2, If the notification window in already pulled down and and suddenly some new notification comes(like sms, email etc), all the notifcations start flickering wildly till I clear them all.
I am on stock no rooting nothing.

GNEX 4.2 default browser
Hi
Really hope someone can answer this for me, I've got a stock GNEX just got 4.2 by deleting my Google Services Framework cache and hitting update. Everything seems to be ok, but I still have the stock (blue icon) browser, I thought the default browser is chrome on 4.2. Also I don't seem to be able delete it, no biggie just annoying to have an app that I'm never going to use.
Anyway to remove it manually without rooting etc..
Many Thanks in advance to anyone that can answer this

Only issue I've noticed so far is the camera rotation is indeed very slow on my phone too.

Now, in 4.2, every notification makes my phone vibrate. This doesn't happen with earliers versions. I don't know if it is a "new feature", but I don't like it.

pookieman123 said:
Hi
Really hope someone can answer this for me, I've got a stock GNEX just got 4.2 by deleting my Google Services Framework cache and hitting update. Everything seems to be ok, but I still have the stock (blue icon) browser, I thought the default browser is chrome on 4.2. Also I don't seem to be able delete it, no biggie just annoying to have an app that I'm never going to use.
Anyway to remove it manually without rooting etc..
Many Thanks in advance to anyone that can answer this
Click to expand...
Click to collapse
According to Google : Chrome is not part of the AOSP but for the new devices such as Nexus 4,7,10 it's the default browser but old devices like Galaxy Nexus i guess for now the default browser will be the Android Browser , who knows maybe with next major release of Android that will change
As for how to delete the default browser you need root privilege to delete the app apk from the system apps using something like Root Explorer

I had three soft reboots already since yesterday (at least that I noticed, maybe more while I wasn't looking). This is a clean install (flash_all.sh from the factory image).
To hell with it, I'm going back to my beloved CM10.

keyboard reverts to default after reboot

I'm using Swifkey 4 (BTW, if you aren't using this, you're missing out) and randomly the keyboard started to revert back to the default after I reboot. Very annoying.
Any suggestions?

seanvree said:
I'm using Swifkey 4 (BTW, if you aren't using this, you're missing out) and randomly the keyboard started to revert back to the default after I reboot. Very annoying.
Any suggestions?
Click to expand...
Click to collapse
It's an issue with SwiftKey. It's not sticking with reboots. Hopefully they fix it in the next release.

Towle said:
It's an issue with SwiftKey. It's not sticking with reboots. Hopefully they fix it in the next release.
Click to expand...
Click to collapse
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....

Yeah I'm having the same issue, was working fine on SwiftKey Flow Beta. I just uninstalled the android and swyoe keyboard that came with wicked.
Sent from Flip's S3

bobolinko said:
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....
Click to expand...
Click to collapse
If it's not a SwiftKey problem, my phone just coincidentally started doing this the second I installed SwiftKey 4.. And coincidentally stops doing it whenever I set a different keyboard as default.

bobolinko said:
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....
Click to expand...
Click to collapse
How do you "freeze the stock" Keyboard?

seanvree said:
How do you "freeze the stock" Keyboard?
Click to expand...
Click to collapse
Either uae titanium backup and look for the keyboard, click on it and you have an option to freeze. Or go to settings>application manager> swipe all the way to the right and look for the keyboard, click on it and it gives you the option of disabling it.
Also I did a fresh install of my rom and now it's sticking after reboots
Sent from Flip's S3

Towle said:
If it's not a SwiftKey problem, my phone just coincidentally started doing this the second I installed SwiftKey 4.. And coincidentally stops doing it whenever I set a different keyboard as default.
Click to expand...
Click to collapse
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
I cannot speak for the previously mentioned workaround (either for our against) , but I have one that has worked for me. Backup your SwiftKey installation with TiBu, uninstall it, reboot, then restore SwiftKey with TiBu. I hope one of these solutions work for you.

driftinganomaly said:
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
I cannot speak for the previously mentioned workaround (either for our against) , but I have one that has worked for me. Backup your SwiftKey installation with TiBu, uninstall it, reboot, then restore SwiftKey with TiBu. I hope one of these solutions work for you.
Click to expand...
Click to collapse
I've the same problem with android 4.1.2 MA2 and galaxy s3.
Probably it depends on Swiftkey and not Android itself....

umberto.sulla said:
I've the same problem with android 4.1.2 MA2 and galaxy s3.
Probably it depends on Swiftkey and not Android itself....
Click to expand...
Click to collapse
Did you try the workaround that I mentioned?

FYI: I had he same issue with SlideIt keyboard on 4.1.1. Froze it with TiBu as suggested and it is gone now. Thanks for the suggestion!

at&t I747 w.Swype (from play store)
driftinganomaly said:
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
Click to expand...
Click to collapse
I just noticed this was the T-Mobile galaxy s3 forum, but I found this through Google, but on my stock at&t I747 when I reboot not only is Swype no longer default, but most of my defaults are reset, so I asked someone @ the at&t store, and they nonchalantly replied, "yeah that's normal". So, reading this response that it's a 4.1.1 issue on xda puts my mind at ease.
I can now just chock it up to another one of those wonderful phenomena (bugs) on this device.
Please excuse any typos, as I wrote this using my gs3 using chrome

If you are rooted, the problem is quite trivial to resolve.

Thank God the guy you spoke to was intelligent enough to give you the right answer. Hes right. Swiftkey Team said any OS under 4.1.2 was affected by that bug.
Sent from my SGH-T999 using Tapatalk 4 Beta

I use ADW paid launcher and when I reboot, I have to choose the default launcher each time. I have Swype and I have the same problem. I've reset the device to full factory a few times and the problem still comes back. I thought that it was only me.
Glad to know I'm not alone.

I reinstalled the rom and didn't choose samsung keyboard but the other one listed, nothing else selected and reboot the phone. Installed SwiftKey and don't have problems anymore with swift not sticking after reboot.
Sent from my SGH-T999

[Q] Samsung keyboard issue (Stock JB 4.1.2)

For anyone else using the stock samsung keyboard on sotck 4.1.2, does the autocorrect function properly? For example, if you write "tgat" instead of "that", will it autocorrect? I'm running the stock Koodo 4.1.2, and the keyboard will not correct it. Although it will show the correct "that" in the prediction bar, and highlight with a slightly darker blue. However, in order to correct it I have to press on the correct word, thereby taking away the usefulness of autocorrect.
Have you guys encountered such an issue? Is there any fix for this problem?
Otherwise, I'm quite liking the stock samsung keyboard.

taxidriver9 said:
For anyone else using the stock samsung keyboard on sotck 4.1.2, does the autocorrect function properly? For example, if you write "tgat" instead of "that", will it autocorrect? I'm running the stock Koodo 4.1.2, and the keyboard will not correct it. Although it will show the correct "that" in the prediction bar, and highlight with a slightly darker blue. However, in order to correct it I have to press on the correct word, thereby taking away the usefulness of autocorrect.
Have you guys encountered such an issue? Is there any fix for this problem?
Otherwise, I'm quite liking the stock samsung keyboard.
Click to expand...
Click to collapse
I can confirm this issue on jedi mind trick rom

I've seen that happen for awhile on many roms ....for the 10 minutes I use it after flashing, then I install my backup of Smart Keyboard Pro and all is well!
But yeah....not sure if there's a solution. I've played with stocks settings and it doesn't change. Just a poor keyboard.
Sent from my cell phone telephone....

I like the look of the keyboard, I just can't use it because if the auto correct
Sent from my SGH-T989 using Tapatalk 2

[Q] Android 4.2.2 Keyboard AOSP

Hey All,
Jelly Beer's 4.2.2 update worked great on my Samsung S3. However, I went out and purchased a new Note 2 GT-N7100 T-Mobile T889. I love the phone. The only problem is that I got used to the keyboard that the guys included in with Jelly Beer 4.2.2 update. In the Input settings, the keyboard is listed as Android keyboard (AOSP). That's the keyboard that I want.
The one that came with the Note 2 is Samsung's own and it's awful. Yes, yes, yes, I've installed just about every other keyboard out there. I've purchased the paid versions and all. Still, nothing does the job as well as the keyboard AOSP. I was literally going to toss the phone because I can't type on it. Then I started to use the gesture part of it, and I'm getting used to that. However, I still want the AOSP one. I've looked all over in the Play store and nothing.
Does anyone have the direct link or the actual .apk that I can download?
Would really appreciate it.

Google keyboard from the play store https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
Sent from my SGH-T889 using Tapatalk 4

cre8nkhaos said:
Hey All,
Jelly Beer's 4.2.2 update worked great on my Samsung S3. However, I went out and purchased a new Note 2 GT-N7100 T-Mobile T889. I love the phone. The only problem is that I got used to the keyboard that the guys included in with Jelly Beer 4.2.2 update. In the Input settings, the keyboard is listed as Android keyboard (AOSP). That's the keyboard that I want.
The one that came with the Note 2 is Samsung's own and it's awful. Yes, yes, yes, I've installed just about every other keyboard out there. I've purchased the paid versions and all. Still, nothing does the job as well as the keyboard AOSP. I was literally going to toss the phone because I can't type on it. Then I started to use the gesture part of it, and I'm getting used to that. However, I still want the AOSP one. I've looked all over in the Play store and nothing.
Does anyone have the direct link or the actual .apk that I can download?
Would really appreciate it.
Click to expand...
Click to collapse
I am wanting the same thing.
yes, there is a google keyboard in the app store. but its not the same as AOSP, AOSP has the symbols as long hold on the letter keys. and you can long press the "." and slide to choose ?! and others.
I tried pulling out the aosp keyboard from carbon rom, if I just install it, it works, but no sliding to type (like swype) and if I move it to system/app and set permissions, then reset, it just force closes... so... it kind of works... but I would really like to be able to slide type.