[Q] Keyboard Issues in CM10 (Q,A,W Not Working) - Captivate General

I've been going back and forth from stock to CM7.2, to CM9, CM10, Hellybean, etc... and I am having a problem with the Keyboard in anything past 7.2 or stock. The "Q" "A" "W" keys will sometimes not work. I have the close out the messaging app or whatever I am using and wait 5 minutes before the keys are operational again. I've also tried multiple kernel/rom combinations and still seem to get it.
I can not repeat this problem in Stock or CM 7.2, nor can I find a calibration option for the keyboard/screen.
Currently, I am running CM 10 stable with Semaphore 2.5.0 kernel. Any ideas?

fitch220 said:
I've been going back and forth from stock to CM7.2, to CM9, CM10, Hellybean, etc... and I am having a problem with the Keyboard in anything past 7.2 or stock. The "Q" "A" "W" keys will sometimes not work. I have the close out the messaging app or whatever I am using and wait 5 minutes before the keys are operational again. I've also tried multiple kernel/rom combinations and still seem to get it.
I can not repeat this problem in Stock or CM 7.2, nor can I find a calibration option for the keyboard/screen.
Currently, I am running CM 10 stable with Semaphore 2.5.0 kernel. Any ideas?
Click to expand...
Click to collapse
What keyboard are you using and are you restoring it with tibu or doing a fresh install?

BWolf56 said:
What keyboard are you using and are you restoring it with tibu or doing a fresh install?
Click to expand...
Click to collapse
I am doing a fresh install, wiping cache/data/dalvik each time. I don't use a TiBu/nandroid backup. The keyboard is the stock CM one.

fitch220 said:
I am doing a fresh install, wiping cache/data/dalvik each time. I don't use a TiBu/nandroid backup. The keyboard is the stock CM one.
Click to expand...
Click to collapse
Have you tried different keyboards (from the market)?

BWolf56 said:
Have you tried different keyboards (from the market)?
Click to expand...
Click to collapse
I got Swype installed and the problem went away. It seems that it is only the stock android keyboard (ASOP) that comes with cyanogenmod.
Anyone know why this would happen, and if there is some set of files I need to clear maybe?

Clear the keyboard data, delete the LatinIME.apk and /system/lib/libjni_latinime.so, then install the 4.2 keyboard: http://forum.xda-developers.com/showthread.php?p=33506020

Related

[Q] About to throw this XOOM into the wall

Hi there,
I have a UK WiFI xoom, and everything was working fine. I installed the ICS AOSP rom, and no issues.
The problem started when I updated the AOSP ICS rom, and the gapps, Now I DONT HAVE MARKET access. The loading circle just goes round and round till it says 'connection timed out - retry'. The GTALK doesnt connect either, it just says 'signing in' till it goes 'offline'.
Right now, I am on the EOS Wifi ICS rom.
Here's what I HAVE done so far to fix it based on ideas in this forum and others (trust me, I search before I post:
- Factory reset, wipe cache, dalvik before every rom install
- Installed every single ICS rom there is, with the recommended google apps
- wiped data on the google services framework
- Installed different version of gapps
- Shut down the firewall on the HOME NETWORK.
It just doesnt work anymore. It used to connect fine to the home Wifi earlier but something just went wrong somewhere and i cant track it down.
Any help would be appreciated.
you have any more info like does your xoom show you are connected to your wifi? do you have any other wireless devices and are they accessing the internet fine? are you flashing the right gapps package?
yea, Wifi is connected fine. Alternate markets like 'slideme', and browser, gmail, maps app etc work fine without problems.
I have flashed the latest gapps package as recommended by EOS rom makers (v. 10 i believe)
after installing the eos mod, did u restart before installing the gaps?
load a stock backup then reinstall your current flavor and gapps
pr1vate piles said:
after installing the eos mod, did u restart before installing the gaps?
Click to expand...
Click to collapse
No I Didn't restart.
load a stock backup then reinstall your current flavor and gapps
Unfortunately, I didnt make a backup. I am an idiot I know!
Just quickly, 10.4 is the latest Gapps to use with EOS.
TheStickMan said:
Just quickly, 10.4 is the latest Gapps to use with EOS.
Click to expand...
Click to collapse
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used
inshadesofgrey said:
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used
Click to expand...
Click to collapse
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!
ok- will try and respond with results. thanks for the patience/
okantomi said:
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!
Click to expand...
Click to collapse
Hi - I did the steps exactly as you said (with a full data wipe). Still getting nowhere?
Any more ideas?
Go back to stock US recovery ROM. Start again.
Also no idea how to fix it (as nothing previously worked), but the symptoms seem similar to when you haven't accepted the agreement that pops up on new google framework (?) version. Won't let you use market or gtalk.. has happened to me before.
Before flashing, try an extra wipe: wipe system (in some recoveries also called "format system" ). I have been saved by this more than once.
Tapatalking
I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk
Krypt2Nyte said:
I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk
Click to expand...
Click to collapse
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j
You can only go back to 3.0 or whatever it is. t will update to 3.2, and then hopefully ICS.
On tablet, so can't quickly find original motorola dev website - try Googling. Here is link to post with hosted firmwares anyway..
http://forum.xda-developers.com/showthread.php?t=1049485
Also check second post there, for using fast boot to install.
inshadesofgrey said:
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j
Click to expand...
Click to collapse
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.
inshadesofgrey said:
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.
Click to expand...
Click to collapse
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).
I had a similar issue on my DHD. It turned out that your language needs to be US English.
Hope this helps
okantomi said:
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).
Click to expand...
Click to collapse
this is very very strange. I can open all other google services and sign in from the browser but not the market.android.com, its just NOT opening the signin page

How to troubleshoot issues

Ok I have been learning how to and moving forward with flashing different ROMs.
I am currently running a 2.3.6 GB on my Infuse.
I am looking to go to ICS however I want to understand better certain issues I am having with my phone.
Its not every time but I will click to open my applications and wait but nothing happens.
If I lock my screen and then re-open my applications will be there. (this part is consistent)
Now Im also getting a lot of Force Closes - I even uninstalled and re-installed applications and still get the same force close when I try to open with one exception where that fixed the problem.
I tried the fixed permissions from Recovery mode but that did not help.
So I have better than 50% of the time where my applications wont open but locking and unlocking causes it to pop open.
I have several applications that i keep getting force close on.
I also have times when things seem sluggish and times when I go to unlock my phone and its froze so that I have to pull the battery.
I use the Go Launcher and its utilities like Power Master and Task Master to manage battery and tasks and it seems to do a good job and has a lot of people recommending them.
What I would like is a way to be able to evaluate and determine what may be going on and resolve it.
Any guidance would be greatly appreciated.
Thanks.
If one Rom doesn't work for you, try another one until you find one you can settle on for a while.
Remember to always do the appropriate wipes when switching roms, and be careful when restoring apps & data, as it can sometimes cause issues.
I would recommend to give JB a try if you haven't yet.
Sent from my sweet & buttery Infuse
andros11 said:
If one Rom doesn't work for you, try another one until you find one you can settle on for a while.
Remember to always do the appropriate wipes when switching roms, and be careful when restoring apps & data, as it can sometimes cause issues.
I would recommend to give JB a try if you haven't yet.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I was going to go to JB but have heard its still a bit buggy.
I used Go Backup to restore applications this time around.
I have used a variety of Backup and Restore options to include nandroid, Titanium, AppExtractor however Go Backup seemed to do my apps, sms, mms, contacts and so forth the best.
If you can refer a better process for application backup and restore when upgrading / changing ROMs Im all ears.
Not buggy for me. Cm10 & paranoid android are pretty solid.. have not tried the others but I believe they perform well too.
I use mybackup pro, just personal preference. I find it simple and works for me.
Sent from my sweet & buttery Infuse
I have tried CNA , MIUI, PA, CM10 and Cypher AOKP ROM (my current one). All are pretty stable. Just be aware most, if not all, are MTD based and going back to ICS (different format) can be a process. Also back up EFS using Infuse toolkit just in case your IMEI disappears.
Sent from my SGH-i997 using xda premium
I suspect your problem is related to Go Launcher and the other Go apps, particularly if you are using one of their builds from the last 6 months. If I were you, I'd backup and do a full wipe and install of one of these GB ROMs: http://forum.xda-developers.com/showthread.php?t=1613523. Restore all your apps except the Go apps and see how things run. Go Launcher provides more functionality than any other free launcher, so you'll have to get used to that. I moved to the free ADW launcher when I was on GB - it's kind of simple, but there are some nice themes available for it.
Also, don't use the GO utilities!
Of course, you could move to a JB ROM. They are all pretty good and stable. JB, however, has some irritating bugs and some apps don't function properly on it. I'm using Paranoid Android 2.0. It's really good, but not quite as fast as the straight CM10...
Whizzpopper said:
I suspect your problem is related to Go Launcher and the other Go apps, particularly if you are using one of their builds from the last 6 months. If I were you, I'd backup and do a full wipe and install of one of these GB ROMs: http://forum.xda-developers.com/showthread.php?t=1613523. Restore all your apps except the Go apps and see how things run. Go Launcher provides more functionality than any other free launcher, so you'll have to get used to that. I moved to the free ADW launcher when I was on GB - it's kind of simple, but there are some nice themes available for it.
Also, don't use the GO utilities!
Of course, you could move to a JB ROM. They are all pretty good and stable. JB, however, has some irritating bugs and some apps don't function properly on it. I'm using Paranoid Android 2.0. It's really good, but not quite as fast as the straight CM10...
Click to expand...
Click to collapse
Funny you should show those ROMs as I am using that very ROM - Option C version
Man I really like the Go Launcher and my wife doesnt seem to be having a problem with it.
Oh well I was looking to maybe make the move up to ICS so maybe I will do that tonight.
Also can you use Heimdal to install those packages or just Odin?
mikefarr said:
Funny you should show those ROMs as I am using that very ROM - Option C version
Man I really like the Go Launcher and my wife doesnt seem to be having a problem with it.
Oh well I was looking to maybe make the move up to ICS so maybe I will do that tonight.
Also can you use Heimdal to install those packages or just Odin?
Click to expand...
Click to collapse
Neither. I believe ODIN and Heimdall are more for recovery.
If you have GB now, download the ROM(s) to your phone and go to CWM and install the zip. Make sure you follow the instructions on the OP of the ROM (wipe/factory reset, etc). Don't forget to install GAPPS too.
And if you want to flash JB, go to http://forum.xda-developers.com/showthread.php?t=1878458 (great guide, also shows how to go from GB to ICS first...follow those instructions).
psal217050 said:
Neither. I believe ODIN and Heimdall are more for recovery.
If you have GB now, download the ROM(s) to your phone and go to CWM and install the zip. Make sure you follow the instructions on the OP of the ROM (wipe/factory reset, etc). Don't forget to install GAPPS too.
And if you want to flash JB, go to http://forum.xda-developers.com/showthread.php?t=1878458 (great guide, also shows how to go from GB to ICS first...follow those instructions).
Click to expand...
Click to collapse
Thanks to all that have helped me with this.
Now if it turns out it is the Go Dev Team programs thats my problem I will need some good replacement recommendations :laugh:
mikefarr said:
Thanks to all that have helped me with this.
Now if it turns out it is the Go Dev Team programs thats my problem I will need some good replacement recommendations :laugh:
Click to expand...
Click to collapse
Ok I was reviewing the link you gave to upgrade and had a couple of questions.
9. Flash ICS, then ICS Gapps - this step refers to ICS Gapps
Once it boots into ICS, turn off and remove your external sdcard.- Why do you have to pull your external sdcard?
The in the section for going to JB it says
5. Flash Gapps - Is this a different Gapps file?
Just curious...
Having the SD card has been known to cause problems...best to remove...you can put it in later. ICS and JB have different GAPPS. Look for the link to the correct GAPPS on the IP of the ROM you decide to use.
Sent from my SGH-i997 using xda premium
Thank you for clarifying that psal.
I'll add those details to the guide.
Sent from my sweet & buttery Infuse
psal217050 said:
Having the SD card has been known to cause problems...best to remove...you can put it in later. ICS and JB have different GAPPS. Look for the link to the correct GAPPS on the IP of the ROM you decide to use.
Sent from my SGH-i997 using xda premium
Click to expand...
Click to collapse
Can you recommend a good ICS ROM?
Also when I tried to make sure I had the device driver installed it is not showing me the Samsung Common.
I guess I hear Entropy has a top JB and also heard good stuff on Th3Bill's JB.
Thanks
mikefarr said:
Can you recommend a good ICS ROM?
Also when I tried to make sure I had the device driver installed it is not showing me the Samsung Common.
I guess I hear Entropy has a top JB and also heard good stuff on Th3Bill's JB.
Thanks
Click to expand...
Click to collapse
My USB drivers say USB Composite Device. If you are going to leap from ICS to JB, it probably doesn't matter which one you flash...most of them are really good (I used UNi-yuma-PoRN when I was on ICS). I have used several of the JB's and everyone likes what they like. Try them all and see which one you like best.
psal217050 said:
My USB drivers say USB Composite Device. If you are going to leap from ICS to JB, it probably doesn't matter which one you flash...most of them are really good (I used UNi-yuma-PoRN when I was on ICS). I have used several of the JB's and everyone likes what they like. Try them all and see which one you like best.
Click to expand...
Click to collapse
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.
mikefarr said:
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.
Click to expand...
Click to collapse
ICS GAPPS were used across the ICS ROMs. Some played around and created inverted GAPPS (black screen, white letters) but ICS had GAPPs and JB has GAPPS. Not sure why...probably due to the different file formats.
Also the mirror in the first link on the OP is down...some upgrades. Try the other mirror
UnipOrnB40a.zip - 326.47 MB
psal - nice work, brother - you're gonna own this place before long :good:
mikefarr- keep on keepin' on, you are on the right track.
andros11- the guide is great - can't wait for the movie :good:
mikefarr said:
Ok I went to look up your yuma.
I found it however when I click to download it says it couldnt find it.
Is the gapp just based on the flavor ie. gapp for ICS, gapp for JB and so forth or are they more specific to the ROM?
Hopefully can flash one tonight but if not - tomorrow.
Click to expand...
Click to collapse
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7
mikefarr said:
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7
Click to expand...
Click to collapse
I just re-downloaded it from that link without a problem. You might need to clear cookies, cache, etc from your browser and retry it. Of course I downloaded to PC and moved the file over to the phone. And you are on GingerBread?
Google has a lot of suggestions:
http://www.google.com/search?hl=en&...09.309.3-1.1.0.les;..0.0...1c.1j2.27RSU95e5S8
mikefarr said:
I have tried 3 times to install the 07.28 ver of this ROM
http://forum.xda-developers.com/showthread.php?t=1601844
All 3 times it failed with a error Status 7
Click to expand...
Click to collapse
Ok I tried another ROM - RemICS-UX and got the same error status 7.
Something else is wrong or Im missing something grrrrr.

Unfortunately, Android keyboard has stopped

I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith
kelkin said:
I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith
Click to expand...
Click to collapse
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.
iElvis said:
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.
Click to expand...
Click to collapse
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith
kelkin said:
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith
Click to expand...
Click to collapse
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.
I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip
phattychops said:
I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip
Click to expand...
Click to collapse
Same here.. Browser won't open, home and recent apps key don't work also... glad it isn't just me.. So you're fine if you don't install gapps?
-Keith
iElvis said:
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.
Click to expand...
Click to collapse
I can't even log into my google account, I can't get a keyboard to appear to type with.
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I can't seem to find Wipe "System" in the Factory Reset. The only options I am given to wipe are the data and cache which I have tried doing and afterwards reinstalling CM10 and GAPPS-jb-20121011-signed.zip yet the "Unfortunately Android's Keyboard (ASOP) has stopped working" still pops up
I know you have tried one of these but ill quote what Inflatedtitan gave to me when i had the same problem.
"Sounds like there could be a few problems so were gonna go with the most popular ones lol..
1. Sounds like you didn't wipe everything in twrp before you flashed. Make your you always wipe cache, dalvick, factory reset, and system. Then flash Rom followed by gapps.. then reboot
2. Have you restored from a titanium backup? If so, make sure next time its ONLY user apps.. if you restore system apps and data, think of your system settings from one Rom clashing with the system files from your new Rom. They won't play nice together. Only backup and restore user apps+data
3. If the above steps were taken correctly, I would delete the Rom.zip from phone. Maybe download using a different browser. Chrome browser is notorious for corrupting roms.. you could have had a bad download
Sent from my HTC One XL using Tapatalk 2"
With these steps I got my ROM working so maybe it could help you.
The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X
Same Problem Over Here
majortaylor said:
The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X
Click to expand...
Click to collapse
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?
xdagee said:
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?
Click to expand...
Click to collapse
Ask in the I9000 forums
Sent from my HTC One XL using xda app-developers app
phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I had the same problem as others here, keyboard would stop working as soon as my One X started. The above fixed it. I only wiped System, did not Factory Reset. Make sure you're using the above version JB Gapps.
I've seen this issue when I accidentally forget to wipe something. I've found I have to wipe, flash previously working Rom, THEN go back, wipe and install new rom.
Sent from my HTC One X+ using xda app-developers app

[Q] Pac 4.3.0 Aosp Keyboard has stopped

Hello, I thought I'd try to post this here to see if any one else is experiencing this issue. I am running PAC 2.3.0, the 8/20/13 release. I have my tablet updated to the 4.2 boot loader via Version US_V10.6.1.15.3, and flashed this with TWRP 2.6 after wiping system, data cache and dalvik. After flashing the rom and the most current gapps (8/12/2013) every thing boots fine. Then I get to the setup screen and there is an error message displaying the AOSP keyboard has stopped.
I hit ok then try to enter my wifi password and some error just flickers too fast to see. I attach the keyboard dock and still no luck for typing. The home and other keys seem to function properly. After skipping through the setup I notice that the choose keyboard lay out notification in the status bar, but when choosing it the error message pops up that Settings has stopped. I have downloaded this twice onced on my pad and once from the pc. Nothing seems to be diffrent.
I know that this is still early in the game for 4.3 but, I can't be the only one experiencing this. I haven't seen any other posts on this, so if any of you out there have any ideas I am all ears. Thanks in advance.
It happened to be, but only when I tried swiping. What you are experiencing seems to be a bit more complex.
Are you able to install a different keyboard, like Go Keyboard?
I haven't tried that. I'll give it a shot.
Sent from my TF300T using XDA Premium HD
That happened to me as well but I flashed again,the rom and gapps and it worked fine
mikep2323 said:
That happened to me as well but I flashed again,the rom and gapps and it worked fine
Click to expand...
Click to collapse
I will give it another try.
thanks!
JakaraRuus said:
I will give it another try.
thanks!
Click to expand...
Click to collapse
I tried again last night. I did a dirty flash over 23 with a dalvik and cache wipe and a re-flash of the latest gapps. same deal. Then I tried with a full wipe and flash of the rc1 from 8/25 same thing except now it tells me who to blame when the keyboard stops. lol.
I have a d2vzw galaxy S III and it give the same keyboard error. So it isn't just our build.
*I found a solution a while ago, but have been too busy to post. I downloaded the official PA gApps for 4.3. Problem solved. The gApps on goo.im were form 4.2.2.*
Admin please close

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

Categories

Resources