Closed GoogleCodeExporter closed 8 years ago
forgot to mention, Beta 14 HTC Inspire. Full wipe
Original comment by eyes2e...@gmail.com
on 18 Aug 2012 at 10:51
Original comment by MonsterBandit04
on 20 Aug 2012 at 12:17
Using R4
1: Menu
2: System settings
3: Language & input
4: Default English (US) - Android keyboard (AOSP)
5: Set up input methods
Will result in "Unfortunately, Settings has stopped"
Unable to install "SwiftKey" due to this
Wipe data/factory reset, wipe cache + dalvik done.
Original comment by fred...@cfc.se
on 3 Sep 2012 at 11:44
Using R3.
I have the same problem with SwiftKey, but for me, it happens sometimes only.
Because SwiftKey is not holding as default after restarts, I have to configure
again every time and 1 in 5 times it gives me this problem of "Unfortunately,
Settings has stopped" and I have to restart again and it works.
Original comment by guilherm...@gmail.com
on 5 Sep 2012 at 11:30
Using 5.1
Same issue with settings and swiftkey
Original comment by fred...@cfc.se
on 6 Sep 2012 at 8:20
Using R6. Fully wiped but problems persists.
Original comment by fred...@cfc.se
on 10 Sep 2012 at 8:44
[deleted comment]
I had the same issue using 7.1 after a while it started happening to all system
apps.
Original comment by m.kyle....@gmail.com
on 17 Sep 2012 at 4:36
OK I got it to work:
When installing it typically crashes at step 2 - Enable swiftkey, when clicking
"remember to press the back..."
Just go to system settings - language and input - under keyboard & input
methods:
click on default - and select swiftkey 3
select swiftkey 3 and click on the setting icon next to it.
This will get you back to the install menu of swiftkey and you will be now at
step 4 typing styles...
Continue the installation and you are good to go.
Hope this helps until a fix gets out.
Ciao
Vadim
Original comment by vti...@gmail.com
on 17 Sep 2012 at 8:59
Original comment by MonsterBandit04
on 25 Sep 2012 at 3:56
I have this same issue with CM10 (latest nightly) and i9300.
I can reproduce this issue when I try to set the input devices with "Hacker's
keyboard".
Any ideas?
Original comment by diego.vi...@gmail.com
on 9 Nov 2012 at 6:30
[deleted comment]
I was having a similar issue. After reviewing my own logcat I found out that I
had caused the issue by uninstalling the system stock app "User Dictionary".
Problem went away after I restored it.
Original comment by dzhim.co...@gmail.com
on 14 Oct 2013 at 7:57
Original issue reported on code.google.com by
eyes2e...@gmail.com
on 18 Aug 2012 at 10:49Attachments: