I just completed a fresh Install of Slim Bean and Gapps based on the directions I found here: http://forum.xda-developers.com/showthread.php?t=2222626
CWM to wipe the system, then CWM to install Slim Bean and then Gapps. Reboot. After Slim Bean loaded up I got two messages, one that hung waiting for an ok: "Unfortunately Hangouts has stopped working." I assume this is google hangouts, honestly I don't know and probably don't care, but a prompt that flashes and instantly disappears reads: "Unfortunately android keyboard (AOSP) has stopped working."
Any time I try and type into a box this prompt either flashes the screen or pops up waiting for an okay. I've also noticed a light flashing when I'm in the novalauncher menu, the web browser blinks up and instantly closes(possibly because of the lack of wifi being connected, don't know), and that's about it on the problems list.
The last post on the thread, whose directions I followed exactly, is this:
jakaro
Senior Member
Thanks Meter 6
Posts: 127
Join Date: Jun 2010
my keyboard is force closing, and can't open aosp android keyboard at all
So this doesn't appear to be limited to me. Please help! I can't connect or do anything at all because I need the keyboard to get into the appstore. If someone knows of an app I could manually install that would fix this that would be lovely. This NT was previously rooted with cyanogen and I never had any trouble with the keyboard.
I haven't used that ROM but when I've had similar issues I have reflashed gApps. If it's still not working I've made a fresh download as well and when flashing again it has always worked for me. But like I said I haven't used this particular ROM.
Sent from my BNTV600 using Tapatalk 4
@RSomnambulist:
If your NT ran a different ROM before flashing Slimbean, you need to do a clean installation using CWM's "wipe /data & factory reset" and 'wipe cache".
digixmax said:
@RSomnambulist:
If your NT ran a different ROM before flashing Slimbean, you need to do a clean installation using CWM's "wipe /data & factory reset" and 'wipe cache".
Click to expand...
Click to collapse
Yep, like I said I wiped everything with CWM, top to bottom. Data, cache, and system. I'll try reflashing gapps per asawi's suggestion and let you know the results.
Related
I am trying to install the G Harmony ROM with BL 1.2[http://forum.xda-developers.com/showthread.php?t=1007455]. The install of the ROM itself is very smooth. After flashing the ROM, I tried to flash the G-apps using the file provided in the OP. The install went on smoothly. On reboot, however, I don't see any Google apps in the system anywhere. Indeed, even Titanium Backup, which was working well before I flashed the G apps, tells me I am not rooted. I tried wiping data,cache,dalvik and fixing permissions, but same result every time. I even tried flashing the CM7 G-apps, but same results. Any ideas, anyone ?
I am in the identical situation with BL1.1 or 1.2. about to try Cyanogen just to see if it's my tablet or not.
Just tried the latest cyanogen mod 7.0.3 and latest gapps. No Gapps or market from that ROM either. Dunno what we are doing wrong. Do we have to wipe our Internal SD's? I used gapps-gb-20110613-signed from cyanogen...and still no apps/market.
I also just tried wiping my SD card (internal), and formatting system. Had to nvflash back to stock. Atttempted G-harmony again. Same results. No apps will install from GoogleApps-GRJ22. It's really strange, the install appears to go fine from clockwork, then there is just nothing there.
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
hungrymr2 said:
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
Click to expand...
Click to collapse
@hungrymr2 - that is what is not happening. After flashing the ROM, I am flashing the G-apps. I would normally expect to see the google set up screen on reboot, but there is nothing - no set up screen, no G-apps.
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
hungrymr2 said:
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
Click to expand...
Click to collapse
Went back to CM7 for now.
Looks like the matter has come to the attention of the dev. Hopefully there will be a resolution soon.
Make sure you clear dalvik code and cache. Might be a good idea to format the internal sd as well. Just good practice to clear everything each time you install a new rom.
Just installed latest version. Cleared delvik/cache with latest CWR. Booted fine but many things are wrong. "android.process.media has stopped" is the first thing to pop up. The calling and people commands respond with "could not launch requested activity" Also, Im not able to sync my google acct with my contacts, etc- which is probably a lack of navigating this rom enough.
Ive flashed 4 different roms with no notable problems. what could be going on here?
a thought-ive only had to wipe dalvik/cache, in reboot options "wipe data/factory reset it an option. surely that is not necessary, ya?
apologies if i didnt find a proper related thread before posting. any help would be greatly apprectiated.
When I flash a new rom I always do a full wipe data cache and dalvik. Also make sure you aren't restoring any red system apps in titanium.....
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
in the option "wipe data/factory reset" its the factory reset part that makes me unsure its safe.
with the other roms ive run, the verbage has been slightly different and i just want to be sure im not going to brick or something.
ill look into the titanium thing thanks for the reply
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
Hi,
Managed to solve this issue by reinstalling the previous gapps and then reinstalling the firmware. Hope this info helps.
gapps-jb-20121128-signed.zip - I also had problem with this update
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
I also had problem with this update!!!!!!!
Problem with 28 Nov. GooManager received update for Jandycane 1.8
(updates jandycane 20121020 and gapps 20121011 done on 09/11/12)
........................
On 28 November GooManager automatically downloaded the following: gapps-jb-20121128-signed.zip
On the 29 November I flashed this on my first gen. Kindle Fire
As follows:
first did a Backup then wiped Cache and Dalvik and then started update - gapps-jb-20121128-signed.zip
after starting update got a Dalvik cache Directories wipe complete message (then)
Verifying Filesystem....
Verifying partition sizes...
Install ........ gapps-jb-20121128-signed.zip
Finding update package
installing
......
......
(and finally)
Installation Complete!
(then once again under this the texts)
Verifying Filesystem....
Verifying partition sizes...
But there it seems to have stopped (completed?)
And under in TWRP I have the options: Wipe Cache/Dalvik - Home - Reboot System
I decided to choose Reboot system
The following happened:
I got a message "upgrading Android apps"
then it started in the normal ("turning mirror bits") loading window
then the usual password window
but the keyboard wouldn’t open!!! I couldn’t get past the password window
also I notice that the WLAN was no longer on/active (it had been on during the process)
I tried several reboots – still the same
I eventually decide to do a restore of Backup – this was successful!
I have no idea what is or went wrong
Is there something wrong with this gapps-jb-20121128-signed.zip it certainly seems like it?????????
Any other experiences?
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
gyrfalcon said:
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
Click to expand...
Click to collapse
Hi, and thanks for replying - now I know for sure it wasn't me that screwed up, wasn't sure!
Glad to hear that it has been removed - but that's really bad - sending out a really bad update like that - lucky we didn't end up with Bricked devices - really frustrating and not a nice thought at all - I'm really grateful for whoever it is that does all this work...but...putting something like that out ... that is scary ........ don't know if I will now trust the next download(s)!!!!!!!!
who is it that does these gapps anyway?
Hi,
I do not have enough posts to post in the cyanogenmod nightlies thread to get a definitive answer, hence why this subforum. I guess my question may be rom independent anyway.
I 'upgraded' from an M release of cyanogenmod to a nightly and buggered my phone. I was forced to flash the stock firmware and then reflash the nightly to fix everything. Except my camera shows a black screen (behind the onscreen focus and options) and force closes nearly all the time. I thought it was just the nightly, but 2 months and 20+ new nightlies later, I still have the issue. In the nightles dev thread, people say the camera is fine. I know the hardware is fine, because 1 in 40 tries the camera randomly works.
I tried a factory wipe, which I now know just wipes user data. So In CWM, under 'mounts and storage' I formatted everything I could and did another factory reset, cache etc. No fix.
I guess this issue is with the rom itself, if the camera is force closing? So I'll have to use Odin or such to flash a stock rom again and flash another cyanogenmod version? But I want to check this is correct before continuing, and how I can completely wipe any trace of the current rom before flashing the stock and another nightly - so I don't get this issue again.
Thanks
So I finally found the issue, after battling with heimdall on ubuntu 14.04 for hours. Its a hardware problem.
I'm just going to leave my experience here in case someone else has the same issue, since anything to do with all the issue I am about to describe don't seem to be documented anywhere on the web clearly.
Firstly, I battled with heimdall 1.3.2 to recognise my phone on ubuntu. I kept getting;
Code:
ERROR: Failed to receive response!
After a number of threads talking about installing usblibx drivers I found one about which libs to install from terminal;
Code:
sudo apt-get install libXXXX
Code:
libusb-ocaml
libdevice-usb-perl
libhpmud0 (not sure if it's essential)
libusb-0.1-4
libusb-1.0-0
libusb-1.0-0-dev
libusb-dev
libusbprog-dev
libusb++-0.1-4c2
libusb++-dev
libusbtc08-1
libusbmuxd-dev
libusbprog0
libusbmuxd1
I installed all but couldn't find libusbmuxd1, restarted anyway, to the same error. I purged heimdall 1.3.2 and instead installed it from the Ubuntu software centre, which using
Code:
sudo apt-cache policy heimdall
showed that I had version 1.4 installed. Then I managed to find
Code:
libusbx-1.0.14_1.0.14-1_amd64.deb
floating somewhere on the internet, which finally installed the proper libusb stuff and allowed heimdall to continue without the error message.
I made a .pit file from my phone. I recommend this first. After hours searching for a stock rom (samsung has removed most of its firmware downloads? and asked links to be removed on other sites!?) came across this site
(I can't post links as a new user) - google [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall
Which explains how to flash using heimdall. After a successful flash, my phone didn't get farther than the boot animation. I booted into stock recovery with vol up-home-power to factory reset, but noticed a dead droid and red writting. Rather than continue, I wanted to fix this, so I followed the tutorial again, but this time checked repartition under the pit path, and hoped for the best. The phone stalled at the boot anim again, but this time in recovery, all was good.
I did a data wipe / factory reset, cache wipe etc, but nothing. So I stuck the stock rom zip onto the micro sd and installed it from recovery, factory reset, and rebooted. (which is odd, having to install the rom from recovery - because doesn't that kinda defeat the point of using the same image on heimdall in the first place?!?)
The phone booted! So after all that, (Having data/factory reset, wiped the cache, (wiped the dalvik cache when i had CWM before and formatted all I could in mounts and storage) flashed the stock ROM AND repartitioned the phone) i thought that would eliminate any software issues. I thought the camera would work.
Nope.
As usual, the front camera worked, but the back, now, after a pause would give the samsung error:
Code:
unknown error by errorcallback
Now, after googling this (Cyanogenmod gave a different error with no related answers on google) and being annoyed at my time lost, I took the tongue and cheek advice from some random forum commenter, to tap the camera hard.
It worked.
Apparently, the entire time the camera was suffering from a hardware issue. Something about a 'sticky shutter'. Anyways, i'm going to leave the stock ROM and take it into a shop to get it fixed. Just leaving this trail of breadcrumbs in the hope it helps someone else.
Perhaps this could be marked as 'solved'.
Same problem
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
JCNouel said:
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
Click to expand...
Click to collapse
Try flashing stock rom and see if this fixes your problem.
gsstudios said:
Try flashing stock rom and see if this fixes your problem.
Click to expand...
Click to collapse
It fixed it, but then I flashed back the AICP ROM, which is KK, and it malfunctioned again. I'm going to try with a JB Custom ROM.
Update: I flashed a JB Custom Rom (Fusion Rom) and it's working good so far.
So today i took the leap and rooted my phone. That went well and i rooted my phone succesfully. My next step was install CM11. Heres where the problems start. I used the CM11 installer and followed all of the instructions. The installer went through, it said it was succesful, and i saw the blue CM person on my phone and my phone started. As expected it made me run through all the set up options. But then, every 10 seconds i would get "google play services has stopped working" and my phone was running very slow. Going to settings, my phone was still running jellybean and nothing was new, now i was just at factory settings, google play services was broken, and my phone ran slow. I rebooted my phone. still nothing. I tried custom installing drivers and reinstalling CM11 using the installer. Same thing. Anyone have any ideas?
Android 4.3 T-Mobile Galaxy s3
Sorry for wall of txt and general un-organization. Very frustrated.
SamsungS3helpplz said:
So today i took the leap and rooted my phone. That went well and i rooted my phone succesfully. My next step was install CM11. Heres where the problems start. I used the CM11 installer and followed all of the instructions. The installer went through, it said it was succesful, and i saw the blue CM person on my phone and my phone started. As expected it made me run through all the set up options. But then, every 10 seconds i would get "google play services has stopped working" and my phone was running very slow. Going to settings, my phone was still running jellybean and nothing was new, now i was just at factory settings, google play services was broken, and my phone ran slow. I rebooted my phone. still nothing. I tried custom installing drivers and reinstalling CM11 using the installer. Same thing. Anyone have any ideas?
Android 4.3 T-Mobile Galaxy s3
Sorry for wall of txt and general un-organization. Very frustrated.
Click to expand...
Click to collapse
Install the latest version of PhilZ recovery from here:
http://forum.xda-developers.com/galaxy-s3/development/i93xx-philz-touch-t2002953
Go to this page and download a type of cm rom that you want:
http://download.cyanogenmod.org/
Put it on sdcard, go to recovery, do a full wipe (wipe data/factory reset + wipe cache + wipe dalvik cache) then install it from " install zip "
done!