[Q] Unfortunately Android Keyboard has stopped - General Questions and Answers

Hi Newby here!
Samsung Galaxy 7 GT-P1000
I somehow stumbled my through rooting my stock tab using odin. failed to install a few Roms for Jellybean, but eventually manager to get AOKP build 38 (android 4.04) running. Like an idiot though, the Gapps file was a newer one intended for Jellybean Rom. It went on, however I now get the 'Unfortunately, Andoid Keyboard has stopped' message. I have looked around and tried the force stop and clear cache, but sadly no fix.
what do I do now? can I just install a more recent ROM over the top?
can i install a rom thats not AOKP now I have AOKP on there?
I basically want Jellybean on my tab rather than ICS.
Can you provide me a link to the Rom and relevant Gapps Jellybean, and is it the just the same process as the initial ones I put on?
OR, can I just put an older version of Gapps on and it will resolve my issue. (I want jellybean but can live with ICS if working properly)?
Sorry for the volume of questions... I am just at a loss of what to do as I dont know what I can and cant do.
For the record I dont have Nandroid or bootstrap on here. they were not mentioned in the tutorial and I had already cleared everything off my tab so wasnt worried about losing anything on it.
Thanks in advance for any enlightenment...
As I sit here now I managed to resolve both issues. I just managed to locate and flash the correct Gapps. reset/wipe, del cache, delete dalvik cache, run akop and run replaced Gapps and hey presto.. ICS running smoothly on my GT7 P1000. Runs snapseed, chrome browser just fine. All my social apps are far better in pics than gingerbread. Loving it. Many hours lost on the steep learning curve.
One question remains.. can I flash a from on here by a different mod? Cost I have seen jellybean for the P1000. Don't know whether to quit while I'm ahead, or now I'm getting the gist, mod to paranoid androids jellybean.

Related

[Q] Galaxy 7 P1000 loop problems with AOKP

Hi all, complete newby. Have an old galaxy 7. running really slow and was getting annoyed i cant run some of the latest apps. SO decided to attempt to put a Rom up to Jellybean.
1. I put the CWMOD on using odin by following a tutorial I found. went ok
2. I followed tutorial to copy the rom to my root.
3. completed Datawipe/reset
4.cleared cache
5.cleared Dalvik cache
6. Installed zip from sd card.
It didnt work. it said it was not supported / error had occurred.
So decided to wipe again and tried again a couple of times. still did'nt work. Plan B load AOKP_p1_build 38.
I Did as above and seemed to be going okay until reboot. it returned me to a modified CWmod screen that is now turquoise in colour instead of orange. when i reboot I get the galaxy screen, then the AOKP screen, but then it jumps to the CWMod boot screen.
I dont know what to do now?? any help greatly appreciated.
UPDATE
I managed to get it running after a few resets and cache wipes. Ive noticed after the fact that I didnt use Nandroid or bootstrap or anything like that. this was because i was not bothered about losing any pictures etc.
However:
I now get the 'cannot use android keyboard' message. I stopped and cleared its cache in settings, but this hasnt helped. searching around I have realised I caused this issue by installing newer Gapps than the android build.
My questions are...
1. Can I download and install a newer AOKP build for my Galaxy 7 GT-P1000, and a newer Gapps?
2. Can someone provide me with links for the AOKP build and Gapps if so?
3. Do I follow the same process as I did to get these on?

Cyanogenmod help

**PHONE INFO BELOW**
I feel as if my situation is really unique and I can only find help by posting
Okay, so it starts like this. I rooted my phone using odin3 and it worked splendidly and everything worked such as gapps. Then I decided to try installing roms... I installed cyanogenmod 10.1 or just ten, not sure. Once I did that everything went down the toilet. I didn't know you had to flash apps so for whatever reason only my app installs I did pre rom installation worked, such as facebook, twitter, instagram. Google playstore didn't work, and neither did gmail. also my contacts wouldn't open either sometimes which was strange. Then like an idiot I installed an update, mentally I was thinking it was a stable update, little did I know it said experimental, It ridded my phone of everything... gapps are all gone, even the play store. The solution I found online was to install flashed gapps, so I did. When I click to open it, it says there is nothing to support it so it won't open. so basically I use the internet browser for everything, and it is very tedious.
What I want to happen and need helping doing:
Either-
Uninstalling cyanogenmod and putting a stock rom on there, which would be heavenly (which i've tried to do and odin always fails to fully download it)
or,
getting my gapps on my phone and having whatever mystery software to support these files on there.
PLEASE HELP ME, I'M AT THE BREAKING POINT, I CAN'T TAKE IT
**PHONE INFO**
Samsung Galaxy SIII
Sprint
Android version 4.2.2
Cyanogenmod version: 10.1-20130304-EXPERIMENTAL-d2spr-M2
Uhm, why don't you just flash a table version..
Sent from my HTC One X using xda app-developers app
Beerad875 said:
Uhm, why don't you just flash a table version..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
What does that do? Hardcore noob status
Galaxy S3 help
chrisusotattd said:
**PHONE INFO BELOW**
I feel as if my situation is really unique and I can only find help by posting
Okay, so it starts like this. I rooted my phone using odin3 and it worked splendidly and everything worked such as gapps. Then I decided to try installing roms... I installed cyanogenmod 10.1 or just ten, not sure. Once I did that everything went down the toilet. I didn't know you had to flash apps so for whatever reason only my app installs I did pre rom installation worked, such as facebook, twitter, instagram. Google playstore didn't work, and neither did gmail. also my contacts wouldn't open either sometimes which was strange. Then like an idiot I installed an update, mentally I was thinking it was a stable update, little did I know it said experimental, It ridded my phone of everything... gapps are all gone, even the play store. The solution I found online was to install flashed gapps, so I did. When I click to open it, it says there is nothing to support it so it won't open. so basically I use the internet browser for everything, and it is very tedious.
What I want to happen and need helping doing:
Either-
Uninstalling cyanogenmod and putting a stock rom on there, which would be heavenly (which i've tried to do and odin always fails to fully download it)
or,
getting my gapps on my phone and having whatever mystery software to support these files on there.
PLEASE HELP ME, I'M AT THE BREAKING POINT, I CAN'T TAKE IT
**PHONE INFO**
Samsung Galaxy SIII
Sprint
Android version 4.2.2
Cyanogenmod version: 10.1-20130304-EXPERIMENTAL-d2spr-M2
Click to expand...
Click to collapse
Which model of Galaxy S3 do you have? Settings -->About Phone
I have a i9300, with Cyanogenmod 9.1 on it. Phone model will decide which ROMs are available.
Soundwve said:
Which model of Galaxy S3 do you have? Settings -->About Phone
I have a i9300, with Cyanogenmod 9.1 on it. Phone model will decide which ROMs are available.
Click to expand...
Click to collapse
SPH-L710
re: Galaxy S3 help
Sent a message to you, chrisusotattd.
To anyone else with this problem, here is the long version of solving this issue. (I can not post links as I have not hit the 10-post minimum, so it is the long version.)
Okay, first step (important!) is to boot into recovery and wipe the Dalvik Cache. Second, wipe cache partition.
Third, wipe data/factory reset. (I did this on my phone.)
This could be part of your problem, as all the apps you installed prior to flashing Cyanogenmod are still there.
Go to the Cyanogenmod home page, hover over the 'get Cyanogenmod' link, and look under 'all devices' on the right. On the next page, select the manufacturer/vendor for your phone (Samsung). Find your Galaxy S3 version (mine is i9300) and click on the stable Cyanogenmod ROM button for your phone. (If there is not a stable version, a 'release candidate' will work too.)
Below the 'release candidate' button, you will find a link to instructions for installing Cyanogenmod. The page for this contains a link to a Clockworkmod (CWM) Recovery, which I'd recommend installing it before you flash the new ROM, if you do not already have it. (The page may be grumpy and not load. Hit refresh, it will work.)
I have a version of CWM, and it works far better than the stock recovery.
I used Odin to flash my S3 as well, so use that instead of Heimdall if you prefer. Once you flash Clockwork Recovery, you can flash the Cyanogenmod ROM thru the CWM recovery.

[Q] Custom 4.2.2 vs. Stock 4.2.2

Hi guys,
Well, after having my P5100 (Samsung G. Tab 2, 10.1) with a stock rom, I've decided to change it for a Cyanogen stable rom, dated of 2013-09-23 19:17:17. Stock rom (4.2.2) was very slow, with lots of lag on it.
I have done everything as the "manual" says, and installed the above mentioned rom. It became more fluid, and more simple. Perfect.
But i am having here an issue, that I don't know how to solve it.
The thing is that I usually read newspapers on my Tab. This works as it follows:
1. we download an app of the newspaper,
2. every time we have a new edition we receive a notification by email, saying that the new issue is available for download;
3. we open the app and start downloading;
4. after downloading, it starts installing the newspaper (since it is a bit interactive and not just a .pdf)
Since I changed to Cyanogen, with the same 4.2.2 as I had on stock rom, when the newspapper installation comes to end, the app simply closes with error. From that moment, I can't even open the app since it simply will close again with error.
Any ideas how to solve this that doesn't require getting back to stock rom?
Many thanks! :good:
QR7 said:
Hi guys,
Well, after having my P5100 (Samsung G. Tab 2, 10.1) with a stock rom, I've decided to change it for a Cyanogen stable rom, dated of 2013-09-23 19:17:17. Stock rom (4.2.2) was very slow, with lots of lag on it.
I have done everything as the "manual" says, and installed the above mentioned rom. It became more fluid, and more simple. Perfect.
But i am having here an issue, that I don't know how to solve it.
The thing is that I usually read newspapers on my Tab. This works as it follows:
1. we download an app of the newspaper,
2. every time we have a new edition we receive a notification by email, saying that the new issue is available for download;
3. we open the app and start downloading;
4. after downloading, it starts installing the newspaper (since it is a bit interactive and not just a .pdf)
Since I changed to Cyanogen, with the same 4.2.2 as I had on stock rom, when the newspapper installation comes to end, the app simply closes with error. From that moment, I can't even open the app since it simply will close again with error.
Any ideas how to solve this that doesn't require getting back to stock rom?
Many thanks! :good:
Click to expand...
Click to collapse
try wiping cache in cwm and also cache of newspaper app also
this might help you
aditya rathee said:
try wiping cache in cwm and also cache of newspaper app also
this might help you
Click to expand...
Click to collapse
Ok, I will try that!
Let's see if it works...
Thank you!
Hi there,
I've tried what you suggested, the error still happens.
I really don't know why it runs on Android 4.2.2 stock, and don't on Android 4.2.2 cyanogen.
Thanks anyway. If you remember anything else to suggest, I would appreciate.
QR7 said:
Hi there,
I've tried what you suggested, the error still happens.
I really don't know why it runs on Android 4.2.2 stock, and don't on Android 4.2.2 cyanogen.
Thanks anyway. If you remember anything else to suggest, I would appreciate.
Click to expand...
Click to collapse
yeah why not
some apps dont run in cyno rom where as they run without any problems in stock one
whatsapp is a common example of this bug it give problems in cyanogenmod roms sometimes
try older version of the newspaper app it may run
good luck :good::good:

[Q] Verizon S3 locks up every reboot on rooted 4.1.2 > 4.3

I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.

How far can I upgrade my GT-N8013?

If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Categories

Resources